CN112686763A - Policy verification method, client, server and storage medium - Google Patents
Policy verification method, client, server and storage medium Download PDFInfo
- Publication number
- CN112686763A CN112686763A CN202011619021.3A CN202011619021A CN112686763A CN 112686763 A CN112686763 A CN 112686763A CN 202011619021 A CN202011619021 A CN 202011619021A CN 112686763 A CN112686763 A CN 112686763A
- Authority
- CN
- China
- Prior art keywords
- policy
- page
- identification information
- screen capture
- server
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Abstract
The application discloses a policy validation method, a client, a server and a storage medium, wherein the method comprises the following steps: when a policy-preserving verification request initiated by a user in an application program is received, verifying a URL (uniform resource locator) address input by the user in the application program; when the URL address input by the user does not belong to the blacklist address, switching to a page corresponding to the URL address, and popping up a screen capture key preset in an application program; when the screen capture key function is triggered, acquiring unique identification information from a server, then capturing a screen of a page to obtain a screenshot of the page, and inserting the unique identification information during screen capture; and uploading the page screenshot and the URL address serving as policy verification information to a server. Through the mode, the situation of policy making can be effectively reduced.
Description
Technical Field
The present application relates to the technical field of policy validation, and in particular, to a policy validation method, a client, a server, and a storage medium.
Background
In the insurance industry, policy refers to the official written proof that an insured life contracts with an insurance company. The policy completely records the right obligation and responsibility of both parties of the insurance contract. The content of the policy record is the basis for the contract parties to fulfill. The policy is proof of the establishment of an insurance contract. The electronic insurance policy refers to an electronic insurance policy with an electronic insurance company electronic signature issued by an insurance company to an insured person by means of digital signature software and an enterprise digital certificate which conform to a PKI system. The electronic insurance policy has the same legal effectiveness as the paper insurance policy, and the electronic insurance policy can be used as the paper insurance policy after being subjected to color printing. Each insurance company has established a policy inquiry system, opens network inquiry and telephone inquiry, and can provide electronic policy inquiry service.
Currently, policy is applicable in many fields. For example, in the loan, the credit line of each person depends on the effective income and the asset guarantee value provided by the person in the application program, the credit line is in positive correlation with the income and the guarantee assets of the applicant, namely, the higher the income and the guarantee assets, the higher the obtained line is, therefore, the applicant can provide the asset guarantee to add credit to obtain the higher credit line, and the asset guarantee includes fixed assets such as house property, automobile and the like and also includes mobile assets such as insurance policy and the like. When the insurance policy is used as the mobile property for loan, the authenticity of the insurance policy needs to be verified, and the loan holder is prevented from forging the insurance policy to achieve the purpose of increasing the credit loan amount.
Disclosure of Invention
The application provides a policy verification method, a client, a server and a storage medium, which are used for solving the existing problem of policy counterfeiting.
In order to solve the technical problem, the application adopts a technical scheme that: providing a policy validation method, which is applied to a client; the method comprises the following steps: when a policy-preserving verification request initiated by a user in an application program is received, verifying a URL (uniform resource locator) address input by the user in the application program; when the URL address input by the user does not belong to the blacklist address, switching to a page corresponding to the URL address, and popping up a screen capture key preset in an application program; when the screen capture key function is triggered, acquiring unique identification information from a server, then capturing a screen of a page to obtain a screenshot of the page, and inserting the unique identification information during screen capture; and uploading the page screenshot and the URL address serving as policy verification information to a server.
As a further improvement of the present application, the URL address includes a white list address, a black list address and other addresses; when detecting that screen capture button function is triggered, obtain only identification information from the server, carry out the screen capture to the page again, obtain the page screenshot to insert only identification information when the screen capture, include: when the URL address belongs to a white list address, if the screen capture key function is triggered, acquiring unique identification information from a server, then carrying out screen capture on a page to obtain a normal page screenshot, and inserting the unique identification information into the normal page screenshot; when the URL address belongs to other addresses, if the screen capture key function is triggered, generating abnormal identification information, then carrying out screen capture on the page to obtain an abnormal page screenshot, and inserting the abnormal identification information into the abnormal page screenshot.
As a further improvement of the present application, after the URL address input by the user in the application program is verified when a policy verification request initiated by the user in the application program is received, the method further includes: and when the URL address belongs to the blacklist address, switching to the page corresponding to the URL address is prohibited.
As a further improvement of the application, when it is detected that the screen capture key function is triggered, the unique identification information is obtained from the server, then the screen capture is carried out on the page, the screenshot of the page is obtained, and the unique identification information is inserted during the screen capture, and the method comprises the following steps: when the screen capture key function is detected to be triggered, a screen capture request is initiated to a server; receiving unique identification information fed back by the server, and generating watermark information according to the unique identification information; and intercepting the page to obtain a page screenshot, and inserting the watermark information into the page screenshot.
In order to solve the above technical problem, the present application adopts another technical solution that: providing a policy validation method, which is applied to a server; the method comprises the following steps: after policy protection verification information sent by a server is received, analyzing the page screenshot, wherein the policy protection verification information comprises the page screenshot and a URL (uniform resource locator) address; when watermark information generated according to the unique identification information exists in the page screenshot, verifying whether the URL address belongs to a blacklist address or not; if yes, issuing information of the insurance policy exception to the client; if not, the watermark on the page screenshot is removed, the page screenshot is stored, and then the information that the policy-preserving verification passes is issued to the client.
As a further improvement of the present application, the method further comprises: and when a screen capture request sent by the client is received, generating unique identification information corresponding to the screen capture request and issuing the unique identification information to the client.
As a further improvement of the application, after policy validation information sent by the server is received, the page screenshot is analyzed, and after the policy validation information comprises the page screenshot and the URL address, the method further comprises the following steps: and when watermark information generated according to the abnormal identification information exists in the screenshot of the page, marking the policy-preserving verification information to be abnormal.
In order to solve the above technical problem, the present application adopts another technical solution that: there is provided a client comprising a processor, a memory coupled to the processor, the memory having stored therein program instructions which, when executed by the processor, cause the processor to perform the steps of the policy verification method according to any one of the preceding claims.
In order to solve the above technical problem, the present application adopts another technical solution that: there is provided a server, the client comprising a processor, a memory coupled to the processor, the memory having stored therein program instructions which, when executed by the processor, cause the processor to perform the steps of the policy validation method according to any one of the preceding claims.
In order to solve the above technical problem, the present application adopts another technical solution that: there is provided a storage medium storing a program file capable of implementing the policy verification method of any one of the above.
The beneficial effect of this application is: according to the policy protection verification method, when a user initiates a policy protection verification request, whether a URL (Uniform resource locator) address input by the user is a blacklist address or not is verified, if not, switching to a page corresponding to the URL address is allowed, and then screen capturing is carried out on the page, so that a page screenshot of an electronic policy protection is obtained, in addition, during screenshot, unique identification information of the policy protection verification is obtained, the unique identification information is inserted into the page screenshot, and the page screenshot and the URL address are uploaded to a server for verification.
Drawings
FIG. 1 is a schematic structural diagram of a policy validation system according to an embodiment of the present application;
FIG. 2 is a schematic flow chart diagram illustrating a policy validation method according to a first embodiment of the present application;
FIG. 3 is a schematic flow chart diagram illustrating a policy validation method according to a second embodiment of the present application;
FIG. 4 is a schematic flow chart diagram illustrating a policy validation method according to a third embodiment of the present application;
FIG. 5 is a schematic flow chart diagram illustrating a policy validation method according to a fourth embodiment of the present application;
FIG. 6 is a functional block diagram of a policy validation device according to a first embodiment of the present application;
FIG. 7 is a functional block diagram of a policy validation device according to a second embodiment of the present application;
FIG. 8 is a schematic structural diagram of a client according to an embodiment of the present application;
FIG. 9 is a schematic structural diagram of a server according to an embodiment of the present application;
fig. 10 is a schematic structural diagram of a storage medium according to an embodiment of the present application.
Detailed Description
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
The terms "first", "second" and "third" in this application are used for descriptive purposes only and are not to be construed as indicating or implying relative importance or implying any indication of the number of technical features indicated. Thus, a feature defined as "first," "second," or "third" may explicitly or implicitly include at least one of the feature. In the description of the present application, "plurality" means at least two, e.g., two, three, etc., unless explicitly specifically limited otherwise. All directional indications (such as up, down, left, right, front, and rear … …) in the embodiments of the present application are only used to explain the relative positional relationship between the components, the movement, and the like in a specific posture (as shown in the drawings), and if the specific posture is changed, the directional indication is changed accordingly. Furthermore, the terms "include" and "have," as well as any variations thereof, are intended to cover non-exclusive inclusions. For example, a process, method, system, article, or apparatus that comprises a list of steps or elements is not limited to only those steps or elements listed, but may alternatively include other steps or elements not listed, or inherent to such process, method, article, or apparatus.
Reference herein to "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment can be included in at least one embodiment of the application. The appearances of the phrase in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. It is explicitly and implicitly understood by one skilled in the art that the embodiments described herein can be combined with other embodiments.
Fig. 1 shows a schematic structural diagram of a policy validation system according to an embodiment of the present application. As shown in fig. 1, the policy validation system comprises a plurality of clients 1 and a server 2, the clients 1 are in communication connection with the server 2, a user accesses an official website of an insurance company by inputting a URL address on the client 1 and finds a page where an electronic policy is located, then screen-capturing is performed on the page of the electronic policy to obtain a page screen capture, and when the screen capture is performed, unique identification information is obtained from the server 2, the unique identification information is inserted into the page screen capture, the page screen capture and the URL address are uploaded to the server 2 as policy validation information, the policy validation information is validated by the server 2, and when the validation is passed, the validated information is sent to the client 1 to inform the user that the policy validation is passed.
Fig. 2 is a schematic flowchart of a policy verification method according to a first embodiment of the present application. It should be noted that the method of the present application is not limited to the flow sequence shown in fig. 2 if the results are substantially the same. As shown in fig. 2, the method is applied to a client, and includes the steps of:
step S101: and when a policy-preserving verification request initiated by the user in the application program is received, verifying the URL address input by the user in the application program.
Generally, the policy in this embodiment is an electronic policy. Compared with paper insurance policy, the electronic insurance policy is more convenient for users to carry and look up, and the electronic insurance policy can be directly uploaded when data submission and verification are carried out.
In step S101, after initiating the policy validation request, the user needs to go to the page where the electronic policy is located to obtain the electronic policy, and usually, the client may query the policy information of the user on the APP pushed by the insurance company, or query the electronic policy information on the website of the insurance company, and go to the page where the electronic policy is issued by the authority to obtain the electronic policy in real time by requiring the user to initiate the policy validation request, so that when receiving the policy validation request initiated by the user, it is validated whether the URL address input by the user is the URL address meeting the requirement.
Step S102: and when the URL address input by the user does not belong to the blacklist address, switching to a page corresponding to the URL address, and popping up a screen capture key preset in the application program.
Note that the blacklist address is preset. Typically, insurance company's website typically includes friend links to some external websites, such as: the method comprises the steps that QQ space, microblogs and the like, in the existing policy making scheme, a fake making person uploads fake policy pictures on the QQ space or the microblogs, and the fake making person skips to the QQ space or the microblogs through a friend link on an official website of an insurance company to intercept and upload the fake policy pictures, so that the purpose of making fake is achieved. Therefore, in this embodiment, URL addresses of websites such as the QQ space and the microblog are set as blacklist addresses, so that a user is prevented from entering such websites to capture a fake policy image when performing policy validation. And when the URL address input by the user does not belong to the blacklist address, switching to the page corresponding to the URL address and outputting and displaying.
Step S103: when the screen capture key function is triggered, the unique identification information is obtained from the server, then the screen capture is carried out on the page, the screenshot of the page is obtained, and the unique identification information is inserted during the screen capture.
In step S103, a screen capture key configured in advance in the application program is used for performing a screen capture operation, and a current page may be captured according to a preset rule, specifically, when it is detected that the screen capture key function is triggered, unique identification information is obtained from the server, and the unique identification information is used for identifying the policy validation of this time, and then a screen capture operation is performed on the currently displayed page to obtain a page capture, and in the screen capture process, the unique identification information is inserted into the page capture as a watermark to obtain a page capture with a watermark. In this embodiment, the screen capture function is realized by setting a preset screen capture key in the application program, and the captured page screenshot can be inserted with the unique identification information as required to obtain the page screenshot with the unique identification information.
Step S104: and uploading the page screenshot and the URL address serving as policy verification information to a server.
In step S104, after the page screenshot is obtained, the page screenshot and the URL address are uploaded to the server as policy validation information for validation.
The policy maintenance verification method of the first embodiment of the application verifies whether the URL address input by the user is a blacklist address or not when the user initiates a policy maintenance verification request, if not, switching to the page corresponding to the URL address is allowed, and then the page is subjected to screen capturing, so that the page screenshot of the electronic policy is obtained, and in screenshot, the unique identification information of the policy maintenance verification is obtained, the unique identification information is inserted into the page screenshot, and the page screenshot and the URL address are uploaded to the server for verification.
Further, in some embodiments, after step S101, the method further includes: and when the URL address belongs to the blacklist address, switching to the page corresponding to the URL address is prohibited.
Specifically, by setting the blacklist address, the possibility that the user intercepts a fake electronic policy by using the blacklist address is reduced.
Fig. 3 is a flowchart illustrating a policy validation method according to a second embodiment of the present application. It should be noted that the method of the present application is not limited to the flow sequence shown in fig. 3 if the results are substantially the same. As shown in fig. 3, the method comprises the steps of:
step S201: and when a policy-preserving verification request initiated by the user in the application program is received, verifying the URL address input by the user in the application program.
In this embodiment, step S201 in fig. 3 is similar to step S101 in fig. 2, and for brevity, is not described herein again.
Step S202: and when the URL address input by the user does not belong to the blacklist address, switching to a page corresponding to the URL address, and popping up a screen capture key preset in the application program.
In this embodiment, step S202 in fig. 3 is similar to step S102 in fig. 2, and for brevity, is not described herein again.
Step S203: when the URL address belongs to a white list address, if the fact that the screen capture key function is triggered is detected, the unique identification information is obtained from the server, then screen capture is conducted on the page, a normal page screenshot is obtained, and the unique identification information is inserted into the normal page screenshot.
It should be noted that, in this embodiment, the URL address includes a blacklist address and a non-blacklist address, where the non-blacklist address includes a whitelist address and other addresses, where the whitelist address includes URL addresses of all insurance company official networks, and the blacklist address, the whitelist address and the other addresses are all preset.
In step S203, when the URL address input by the user is the white list address, after switching to the page corresponding to the URL address, a screen capture key of the application program is popped up, and the user can capture the current page by operating the screen capture key, and then insert the unique identification information obtained from the server into the captured page picture to obtain a normal page screenshot.
Step S204: when the URL address belongs to other addresses, if the screen capture key function is triggered, generating abnormal identification information, then carrying out screen capture on the page to obtain an abnormal page screenshot, and inserting the abnormal identification information into the abnormal page screenshot.
In step S204, when the URL address input by the user is another address, after switching to the page corresponding to the URL address, a screen capture key of the application program is popped up, when the user triggers the function of the screen capture key, the abnormal identification information is generated, then the screen capture is performed on the page, and then the abnormal identification information is inserted into the captured page picture, so as to obtain an abnormal page screen capture. The abnormal identification information comprises a preset abnormal identification code and the time for generating the abnormal identification information, so that the server can conveniently and quickly acquire related information when analyzing the abnormal screenshot of the page.
Step S205: and uploading the page screenshot and the URL address serving as policy verification information to a server.
In this embodiment, step S205 in fig. 3 is similar to step S104 in fig. 2, and for brevity, is not described herein again.
The policy maintenance verification method of the second embodiment of the application is based on the first embodiment, by dividing the white list address and other addresses, when the URL address is the white list address, switching to the page corresponding to the URL address, and popping up the screen capture key, allowing the user to perform screen capture operation, and when the URL address is other addresses, if the user initiates screen capture operation, inserting abnormal identification information into the captured page picture, and if the user uploads the abnormal page screen capture for verification, quickly confirming that the page screen capture is abnormal through the abnormal identification information, so that the verification of the electronic policy maintenance is more accurate, and after verifying that the page screen capture with the abnormal identification information exists, the user can continue to pay attention to the user, or the user is marked as a hidden trouble user, and more detailed verification is performed on the information uploaded by the user.
Fig. 4 is a flowchart illustrating a policy validation method according to a third embodiment of the present application. It should be noted that the method of the present application is not limited to the flow sequence shown in fig. 4 if the results are substantially the same. As shown in fig. 4, the method includes the steps of:
step S301: and when a policy-preserving verification request initiated by the user in the application program is received, verifying the URL address input by the user in the application program.
In this embodiment, step S301 in fig. 4 is similar to step S101 in fig. 2, and for brevity, is not described herein again.
Step S302: and when the URL address input by the user does not belong to the blacklist address, switching to a page corresponding to the URL address, and popping up a screen capture key preset in the application program.
In this embodiment, step S302 in fig. 4 is similar to step S102 in fig. 2, and for brevity, is not described herein again.
Step S303: and when the screen capture key function is detected to be triggered, initiating a screen capture request to the server.
In step S303, when the user triggers the screen capture button function, a screen capture request is sent to a server, which is a server for verifying the authenticity of the policy.
Step S304: and receiving the unique identification information fed back by the server, and generating watermark information according to the unique identification information.
In step S304, after receiving the screen capture request, the server generates unique identification information for the policy validation at this time, and sends the unique identification information to the client, and after receiving the unique identification information fed back by the server, the client generates watermark information according to the unique identification information.
Step S305: and intercepting the page to obtain a page screenshot, and inserting the watermark information into the page screenshot.
In step S305, after the page is intercepted to obtain the page screenshot, the watermark information is inserted into the page screenshot. In some embodiments, watermark information may also be inserted into each picture by identifying all pictures in the page shot.
It should be noted that, in order to avoid modifying the watermark information after the user finds the watermark information on the page screenshot, in some embodiments, the watermark information is hidden after being inserted into the page screenshot, so as to ensure that the watermark information is invisible to the naked eye, and reduce the possibility of finding the watermark information by the user, for example, by setting the watermark to be completely transparent.
Step S306: and uploading the page screenshot and the URL address serving as policy verification information to a server.
In this embodiment, step S306 in fig. 4 is similar to step S104 in fig. 2, and for brevity, is not described herein again.
The policy maintenance verification method of the third embodiment of the application is based on the first embodiment, requests the unique identification information from the server when a screen capture request is initiated, and inserts the watermark information into the page screen capture after the unique identification information is generated.
Fig. 5 is a flowchart illustrating a policy validation method according to a fourth embodiment of the present application. It should be noted that the method of the present application is not limited to the flow sequence shown in fig. 5 if the substantially same result is obtained. As shown in fig. 5, the method is applied to a server, and includes the steps of:
step S401: and after receiving policy validation information sent by the server, analyzing the page screenshot, wherein the policy validation information comprises the page screenshot and the URL address.
In step S401, after receiving the policy validation information sent by the client, the page screenshot in the policy validation information is analyzed, so as to determine whether watermark information generated according to the unique identification information exists in the page screenshot. If yes, go to step S402. If the page screenshot does not exist, the page screenshot is abnormal, and the page screenshot may be a fake electronic insurance policy screenshot.
Step S402: and when watermark information generated according to the unique identification information exists in the page screenshot, verifying whether the URL address belongs to a blacklist address. If yes, go to step S403; if not, go to step S404.
In step S402, when watermark information generated according to the unique identification information exists in the page screenshot, it is verified whether the URL address in the policy validation information is a blacklist address, and double validation is performed to ensure that the validation result is accurate.
Step S403: and issuing the information of the insurance policy exception to the client.
In step S403, when the URL address belongs to the blacklist address, it indicates that the verification information of the electronic policy is abnormal, and therefore, the information of the policy abnormality is issued to the client. In addition, after the information of the insurance policy abnormity is issued to the client, the user information which initiates the insurance policy verification request is also obtained, the user information is labeled, for example, the time and the times of user verification failure are labeled, and after a period of events are counted, the risk coefficient of the user can be analyzed through a wind control model.
Step S404: and after the watermark on the page screenshot is removed, the page screenshot is stored, and then the information that the policy validation passes is issued to the client.
In step S404, when watermark information generated according to the unique identification information exists in the page screenshot and the URL address is verified to belong to the blacklist address, it indicates that the electronic policy recorded in the page screenshot is authentic, the watermark on the page screenshot is removed, the page screenshot from which the watermark is removed is saved, so as to record the electronic policy, and information that the policy verification passes is sent to the client to inform the user that the policy verification passes.
The policy maintenance verification method of the fourth embodiment of the application performs double verification on the page screenshot and the URL address in the policy maintenance verification information sent by the client, so that the accuracy of policy maintenance verification is improved.
Further, the policy validation method further comprises: and when a screen capture request sent by the client is received, generating unique identification information corresponding to the screen capture request and issuing the unique identification information to the client.
Specifically, when the screen capture key function is triggered, the client sends a screen capture request to the server, after receiving the screen capture request, the server generates unique identification information of policy validation at the moment according to the screen capture request, and then sends the unique identification information to the client, and after capturing the page screen capture of the page, the client inserts the unique identification information into the page screen capture, so that the identifiability of the page screen capture is improved.
Further, before issuing the unique identification information to the client, the method further includes: the unique identification information is encrypted. The encrypted unique identification information is more difficult to crack, and the situation that a user inserts the unique identification information into a fake electronic policy picture after intercepting the unique identification information to impersonate a real electronic policy picture is further avoided.
Further, after step S401, the method further includes: and when watermark information generated according to the abnormal identification information exists in the screenshot of the page, marking the policy-preserving verification information to be abnormal.
In this embodiment, when the URL address is another address, after switching to a page corresponding to the URL address, if it is detected that the screen capture key function is triggered, the client generates abnormal identification information, generates watermark information according to the abnormal identification information, and inserts the watermark information into the captured picture to obtain an abnormal page screenshot. Therefore, when the server detects that watermark information generated according to the abnormal identification information exists in the page screenshot, the server marks the exception of the policy-keeping verification information and then sends the verification failure information to the client. And moreover, user information of the user who fails in the policy validation can be recorded, and after the statistics is carried out for a period of time, the risk coefficient of the user is analyzed according to the recorded result.
Fig. 6 is a functional block diagram of a policy validation device according to a first embodiment of the present application. As shown in fig. 6, the apparatus 60 includes a first authentication module 61, a switching module 62, a screen capture module 63, and an upload module 64.
The first verification module 61 is used for verifying the URL address input by the user in the application program when receiving a policy verification request initiated by the user in the application program;
the switching module 62 is configured to switch to a page corresponding to the URL address and pop up a screen capture key configured in advance in the application program when the URL address input by the user does not belong to the blacklist address;
the screen capturing module 63 is configured to obtain unique identification information from the server when it is detected that the screen capturing key function is triggered, capture a screen of the page to obtain a screenshot of the page, and insert the unique identification information during the screen capturing;
and the uploading module 64 is used for uploading the page screenshot and the URL address as policy verification information to the server.
Optionally, the URL address includes a white list address, a black list address, and other addresses; when the screen capture module 63 detects that the screen capture key function is triggered, unique identification information is obtained from the server, then the screen capture is performed on the page, a page screen capture is obtained, and the operation of inserting the unique identification information during screen capture can also be: when the URL address belongs to a white list address, if the screen capture key function is triggered, acquiring unique identification information from a server, then carrying out screen capture on a page to obtain a normal page screenshot, and inserting the unique identification information into the normal page screenshot; when the URL address belongs to other addresses, if the screen capture key function is triggered, generating abnormal identification information, then carrying out screen capture on the page to obtain an abnormal page screenshot, and inserting the abnormal identification information into the abnormal page screenshot.
Optionally, when the first verification module 61 receives a policy validation request initiated by the user in the application program, and after verifying an operation of the user on the URL address input in the application program, the switching module 62 is further configured to prohibit switching to a page corresponding to the URL address when the URL address belongs to a blacklist address.
Optionally, when detecting that the screen capture key function is triggered, the screen capture module 63 obtains the unique identification information from the server, then performs screen capture on the page to obtain a screenshot of the page, and inserts the unique identification information during screen capture, which may also be: when the screen capture key function is detected to be triggered, a screen capture request is initiated to a server; receiving unique identification information fed back by the server, and generating watermark information according to the unique identification information; and intercepting the page to obtain a page screenshot, and inserting the watermark information into the page screenshot.
Fig. 7 is a functional block diagram of a policy validation device according to a second embodiment of the present application. As shown in fig. 7, the apparatus 70 includes a parsing module 71, a second verification module 72, a first processing module 73 and a second processing module 74.
The analysis module 71 is configured to analyze the page screenshot after receiving policy validation information sent by the server, where the policy validation information includes the page screenshot and the URL address;
the second verification module 72 is configured to verify whether the URL address belongs to a blacklist address when watermark information generated according to the unique identification information exists in the page screenshot;
the first processing module 73 is configured to issue a policy exception message to the client when the URL address belongs to the blacklist address;
and the second processing module 74 is configured to, when the URL address does not belong to the blacklist address, remove the watermark on the page screenshot, store the page screenshot, and then issue the information that the policy validation passes to the client.
Optionally, the apparatus 70 further includes a generating module 75, configured to execute an operation of generating unique identification information corresponding to the screen capturing request and issuing the unique identification information to the client when the screen capturing request sent by the client is received.
Optionally, after receiving policy validation information sent by the server, the parsing module 71 parses the page screenshot, where the policy validation information includes the page screenshot and the URL address, and the second validation module 72 is further configured to perform an operation of marking that the policy validation information is abnormal when watermark information generated according to the abnormal identification information exists in the page screenshot.
For other details of the technical solution implemented by each module in the policy validation apparatus in the above embodiment, reference may be made to the description of the policy validation method in the above embodiment, and details are not described here again.
It should be noted that, in the present specification, the embodiments are all described in a progressive manner, each embodiment focuses on differences from other embodiments, and the same and similar parts among the embodiments may be referred to each other. For the device-like embodiment, since it is basically similar to the method embodiment, the description is simple, and for the relevant points, reference may be made to the partial description of the method embodiment.
Referring to fig. 8, fig. 8 is a schematic structural diagram of a client according to an embodiment of the present application. As shown in fig. 8, the client 80 includes a processor 81 and a memory 82 coupled to the processor 81.
The memory 82 stores program instructions that, when executed by the processor 81, cause the processor 81 to perform the steps of the policy verification method in the first, second, and third embodiments.
The processor 81 may also be referred to as a CPU (Central Processing Unit). The processor 81 may be an integrated circuit chip having signal processing capabilities. Processor 81 may also be a general purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
Referring to fig. 9, fig. 9 is a schematic structural diagram of a client according to an embodiment of the present application. As shown in fig. 9, the server 90 includes a processor 91 and a memory 92 coupled to the processor 91.
The memory 92 stores program instructions that, when executed by the processor 91, cause the processor 91 to perform the steps of the policy verification method in the fourth embodiment described above.
The processor 91 may also be referred to as a CPU (Central Processing Unit). The processor 91 may be an integrated circuit chip having signal processing capabilities. The processor 91 may also be a general purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
Referring to fig. 10, fig. 10 is a schematic structural diagram of a storage medium according to an embodiment of the present application. The storage medium of the embodiment of the present application stores a program file 11 capable of implementing all the methods described above, where the program file 11 may be stored in the storage medium in the form of a software product, and includes several instructions to enable a computer device (which may be a personal computer, a server, or a network device) or a processor (processor) to execute all or part of the steps of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a mobile hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, or terminal devices, such as a computer, a server, a mobile phone, and a tablet.
In the several embodiments provided in the present application, it should be understood that the disclosed client, server, apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, a division of a unit is merely a logical division, and an actual implementation may have another division, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit. The above embodiments are merely examples and are not intended to limit the scope of the present disclosure, and all modifications, equivalents, and flow charts using the contents of the specification and drawings of the present disclosure or those directly or indirectly applied to other related technical fields are intended to be included in the scope of the present disclosure.
Claims (10)
1. A policy validation method is applied to a client; the method comprises the following steps:
when a policy-preserving verification request initiated by a user in an application program is received, verifying a URL (uniform resource locator) address input by the user in the application program;
when the URL address input by the user does not belong to the blacklist address, switching to a page corresponding to the URL address, and popping up a screen capture key preset in the application program;
when the screen capture key function is triggered, acquiring unique identification information from a server, then capturing the screen of the page to obtain a page screenshot, and inserting the unique identification information during screen capture;
and uploading the page screenshot and the URL address serving as policy verification information to the server.
2. The policy validation method according to claim 1, wherein the URL address comprises a white list address, a black list address and other addresses;
when the screen capture key function is triggered, acquiring unique identification information from a server, then capturing the screen of the page to obtain a page screenshot, and inserting the unique identification information during screen capture, wherein the screen capture key function comprises the following steps:
when the URL address belongs to a white list address, if the screen capture key function is triggered, acquiring the unique identification information from the server, then capturing the screen of the page to obtain a normal page screenshot, and inserting the unique identification information into the normal page screenshot;
and when the URL address belongs to other addresses, if the screen capture key function is triggered, generating abnormal identification information, then carrying out screen capture on the page to obtain an abnormal page screenshot, and inserting the abnormal identification information into the abnormal page screenshot.
3. The policy validation method according to claim 1, wherein said receiving a policy validation request initiated by a user in an application program, after validating a URL address entered by the user in the application program, further comprises:
and when the URL address belongs to a blacklist address, switching to a page corresponding to the URL address is prohibited.
4. The policy validation method according to claim 1, wherein when it is detected that the screen capture button function is triggered, acquiring unique identification information from a server, then performing screen capture on the page to obtain a page screen capture, and inserting the unique identification information during screen capture, comprises:
when the screen capture key function is detected to be triggered, a screen capture request is sent to the server;
receiving the unique identification information fed back by the server, and generating watermark information according to the unique identification information;
and intercepting the page to obtain the page screenshot, and inserting the watermark information into the page screenshot.
5. A policy validation method is applied to a server; the method comprises the following steps:
after policy maintenance verification information sent by a server is received, analyzing a page screenshot, wherein the policy maintenance verification information comprises the page screenshot and the URL address;
when watermark information generated according to the unique identification information exists in the page screenshot, verifying whether the URL address belongs to a blacklist address or not;
if yes, issuing information of the insurance policy exception to the client;
if not, the watermark on the page screenshot is removed, the page screenshot is stored, and then the information that the policy-preserving verification passes is issued to the client.
6. The policy validation method according to claim 5, further comprising:
and when a screen capture request sent by the client is received, generating the unique identification information corresponding to the screen capture request and issuing the unique identification information to the client.
7. The policy validation method according to claim 5, wherein after receiving policy validation information sent by a server, parsing a page screenshot, wherein the policy validation information includes the page screenshot and the URL address, further comprising:
and when watermark information generated according to the abnormal identification information exists in the screenshot of the page, marking the exception of the policy-keeping verification information.
8. A client, characterized in that the client comprises a processor, a memory coupled to the processor, in which memory program instructions are stored, which program instructions, when executed by the processor, cause the processor to carry out the steps of the policy validation method according to any of claims 1-4.
9. A server, characterized in that the client comprises a processor, a memory coupled to the processor, in which memory program instructions are stored which, when executed by the processor, cause the processor to carry out the steps of the policy validation method according to any of claims 5-7.
10. A storage medium storing a program file capable of implementing the policy verification method according to any one of claims 1 to 4 or the policy verification method according to any one of claims 5 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011619021.3A CN112686763A (en) | 2020-12-31 | 2020-12-31 | Policy verification method, client, server and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011619021.3A CN112686763A (en) | 2020-12-31 | 2020-12-31 | Policy verification method, client, server and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112686763A true CN112686763A (en) | 2021-04-20 |
Family
ID=75453695
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011619021.3A Pending CN112686763A (en) | 2020-12-31 | 2020-12-31 | Policy verification method, client, server and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112686763A (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113590564A (en) * | 2021-07-29 | 2021-11-02 | 挂号网（杭州）科技有限公司 | Data storage method and device, electronic equipment and storage medium |
| CN115203748A (en) * | 2022-09-14 | 2022-10-18 | 北京锘崴信息科技有限公司 | Financial privacy information auditing method and device based on information credibility verification |
| EP4318364A4 (en) * | 2021-04-23 | 2024-04-10 | Ant Shengxin Shanghai Information Tech Co Ltd | Insurance verification method and apparatus for electronic device |
-
2020
- 2020-12-31 CN CN202011619021.3A patent/CN112686763A/en active Pending
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP4318364A4 (en) * | 2021-04-23 | 2024-04-10 | Ant Shengxin Shanghai Information Tech Co Ltd | Insurance verification method and apparatus for electronic device |
| CN113590564A (en) * | 2021-07-29 | 2021-11-02 | 挂号网（杭州）科技有限公司 | Data storage method and device, electronic equipment and storage medium |
| CN113590564B (en) * | 2021-07-29 | 2024-03-01 | 挂号网（杭州）科技有限公司 | Data storage method, device, electronic equipment and storage medium |
| CN115203748A (en) * | 2022-09-14 | 2022-10-18 | 北京锘崴信息科技有限公司 | Financial privacy information auditing method and device based on information credibility verification |
| CN115203748B (en) * | 2022-09-14 | 2022-12-13 | 北京锘崴信息科技有限公司 | Financial privacy information auditing method and device based on information credibility verification |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20210081551A1 (en) | Method, apparatus, and electronic device for blockchain-based recordkeeping | |
| CN110233739B (en) | Identity management method, identity management device and storage medium | |
| CN112686763A (en) | Policy verification method, client, server and storage medium | |
| CN110851879B (en) | Method, device and equipment for infringement and evidence preservation based on evidence preservation block chain | |
| JP2020511059A (en) | Information authentication method and system | |
| CN111343142B (en) | Data processing method and device based on block chain network and storage medium | |
| CN112217835B (en) | Message data processing method and device, server and terminal equipment | |
| JP6880055B2 (en) | Message anti-counterfeiting implementation method and device | |
| KR102241246B1 (en) | A stamp authority system based on blockchain for verifying the authenticity of issued documents | |
| CN109447809B (en) | Video active identification method combined with block chain | |
| EP3792792A1 (en) | Tampering detection method for paper copy and apparatus and non-transitory computer-readable storage medium | |
| CN110599207A (en) | Invoice verification method, invoice verification device, invoice verification server and storage medium | |
| EP3955145A1 (en) | Blockchain-based electronic signature method and apparatus | |
| US20200057871A1 (en) | Apparatuses and methods for signing a legal document | |
| CN113205340A (en) | Data processing method and related device for bank-enterprise direct connection platform | |
| CN110599211A (en) | Ticket information processing method and device and computer equipment | |
| CN111200591A (en) | Multiple man-machine verification method, device, equipment and storage medium | |
| CN107566410A (en) | A kind of data save message request treating method and apparatus from damage | |
| CN110598449B (en) | Data processing method and device for performing insurance function, storage medium and computer equipment | |
| CN114172689A (en) | Information processing method and device | |
| US20080276094A1 (en) | Communication terminal device, server apparatus, data management method and recording medium | |
| CN112966197B (en) | Method, device, equipment and storage medium for displaying page electronic signature | |
| KR101669120B1 (en) | Device for verifying caller facsimile and method thereof | |
| CN112950416B (en) | Electronic evidence processing method and device based on blockchain and readable medium | |
| CN111291335B (en) | Bill data processing method and device, computer 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 |