Detailed Description
In order to make those skilled in the art better understand the technical solutions in the present specification, the technical solutions in the embodiments of the present specification will be clearly and completely described below with reference to the drawings in the embodiments of the present specification, and it is obvious that the described embodiments are only a part of the embodiments in the present specification, and not all of the embodiments. All other embodiments that can be obtained by a person skilled in the art on the basis of one or more embodiments of the present description without inventive step shall fall within the scope of protection of the embodiments of the present description.
One embodiment provided by the present specification can be applied to a client/server system architecture. The client can comprise terminal equipment used by the counter or the insured, such as a smart phone, a tablet computer, intelligent wearable equipment, a personal computer and the like. The client can be provided with a communication module and can be in communication connection with a remote server to realize data transmission with the server. The server may include an application server corresponding to a specific application installed on the client, for example, an application server of a certain payment application installed on the user terminal, the payment application may provide insurance services such as insurance declaration, loss assessment, viewing progress, claim settlement payment, and the like, and may have business interaction with a server on the insurance company side. Of course, the server in other implementation scenarios may also include or be an insurance company side server, for example, the user terminal may be directly in communication link with the insurance company server. The server may include a single computer device, or may include a server cluster formed by a plurality of servers, or a server structure of a distributed system.
In the conventional insurance business, there are many user information of an insured person indirectly obtained through a non-insurance company side. It should be noted that the user information mentioned in some embodiments in this specification, such as the user information of the person under notice or the insured life, may generally include, but is not limited to, citizenship information, contact information such as telephone or address, social relationship information, family relationship information, income and credit information, etc. The reliability of the information is hard to guarantee, for example, in order to make the user be subsequently maintained or illegally replace the user to handle insurance business, the insurance mobile phone or address information provided by the intermediary service side of the insurance company is false, and the phenomenon can cause the insurance company to lack real information to contact and service the user or evaluate the user, and the like. In the existing scheme, a plurality of hidden terms or steps are used for acquiring information of an insured person, even if the insured person does not agree, messages such as claim settlement progress and the like are sent to an intermediary party or other users, or user data such as a mobile phone number of the insured person is sent to an insurance company, and the processing scheme cannot enable the user to obtain more definite authorization perception experience.
Generally, most insurance companies can require the insurance person to be insured when a certain insurance business reports the insurance, or the insured has a certain designated relationship, so as to prevent other people from arbitrarily imitating the reports as much as possible, which causes unnecessary waste of business resources and fraud risk. In most of the current actual insurance reporting links, most of the reporting persons adopt a calling mode to make insurance reports. For an insurance company, only the number of the incoming call of the announcer can be known, the identity of the announcer can be verified orally through a telephone, whether the announcer is an insured or a trusted person cannot be completely determined, and the insurance company has larger safety and privacy risks.
The embodiment of the specification provides another data processing method for verifying the user information stored and recorded by the insurance company based on the development and application of the internet technology. In some embodiments of the scheme, the offline telephone report can be guided to online identity authentication, authorization and business processing, the user information can be reasonably and legally acquired on the premise that the user is definitely authorized by using insurance business information provided by a trusted third party application, the user information is verified, the verification, cleaning and the like of user information data on one side of an insurance service party are effectively assisted, and the wind control capability and the insurance service capability of an insurance company are improved. In some embodiments of the present specification, the applicant may generally refer to a person who initiates a claim settlement request to an insurance company through a telephone, a network, or the like, and during subsequent business processing, the applicant may also apply for a claim settlement progress or the like at its own terminal. The insured life can refer to the person under insurance contract, which is obligated to pay insurance premium, and when the insurance accident happens or the insurance expires, the insured life is entitled to request the loss compensation or receive the insurance payment from the insurer according to the insurance contract. In some implementation scenarios in this specification, the reporter may be an insured or a non-insured, and the first terminal and the second terminal described below may be the same terminal; in other application scenarios, the vehicle may not be the same person, for example, a person reporting a case is a driver, and the vehicle insurance business is equivalent to a user of the vehicle. Of course, the applied insurance business is not limited to the car insurance claim settlement scene, and all or part of the embodiments of the present specification may be implemented in other insurance categories or other insurance links (such as insurance application).
The following describes embodiments of the present specification by taking a specific application scenario of claims settlement. Specifically, fig. 1 is a schematic flowchart of an embodiment of the processing method for verifying the user information provided in this specification. Although the present specification provides the method steps or apparatus structures as shown in the following examples or figures, more or less steps or modules may be included in the method or apparatus structures based on conventional or non-inventive efforts. In the case of steps or structures which do not logically have the necessary cause and effect relationship, the execution order of the steps or the block structure of the apparatus is not limited to the execution order or the block structure shown in the embodiments or the drawings of the present specification. When the described method or module structure is applied to a device, a server or an end product in practice, the method or module structure may be executed sequentially or in parallel according to the embodiments or the method or module structure shown in the drawings (for example, in the environment of parallel processors or multi-thread processing, or even in the environment of distributed processing and server cluster).
Of course, the following description of the embodiments does not limit other extensible solutions based on the present description. In a specific embodiment, as shown in fig. 1, in an embodiment of the processing method for verifying user information provided in this specification, the method may include:
s0: the insurance server sends the report user information of the report person to the application server.
When initiating a claim, the person who reports can call in the insurance company by telephone and the insurance company customer service staff answers the call. In the telephone link of the interaction between the insurance company and the reporting person, the reporting person may be required to provide some necessary information, or some information actively provided by the reporting person, or may be combined with the related information of the reporting person inquired by the insurance company side, which may be collectively referred to as reporting user information. The application user information may specifically include the mobile phone number of the application, the mobile phone number of the insured (which may be fake), the identity number of the insured, the address of the insured, the telephone of the emergency contact of the insured, etc. The processing terminal (which may be a customer service terminal or a server, and may be collectively referred to as an insurance server herein) on the insurance company side can record the information of the reporting users.
The insurance server may send the report user information to the application server. The application server may include a processing device of a service party having a business relationship with an insurance company, such as a server of a payment application that can provide insurance services such as insurance application and claims. Generally, the application server described in this embodiment of the present disclosure may generally have at least a real-name authentication capability, for example, for a user who registers an application on the application server, the real-name authentication may be performed when the application is registered, and the application is allowed to be registered only after the real-name authentication is passed, so as to obtain a corresponding application account. The real-name authentication generally refers to a verification and verification of authenticity of user data, and may include verification of names, identity cards or other certificates, and may also include mobile phone numbers, bank accounts, vehicle information, house property information and the like corresponding to the user names or certificate numbers, and may be combined with images, videos, sounds, face recognition, fingerprint recognition and the like to perform real-name authentication. The application server may specifically include various architecture forms, and may be a single processing server, a server cluster, or a server of a distributed system.
The above-mentioned report user information may include various types of information. In another embodiment provided by the present specification, in consideration of the popularization and application of the mobile phone number in the existing society and the general use of the telephone for insurance coverage, in another embodiment, the coverage user information may include the mobile phone number. The mobile phone number is used for processing identity authentication, verification and the like, so that the user information can be verified more quickly and efficiently, and the method is also suitable for more application scenes.
In the application scenario of this embodiment, the insurance server may send all the acquired insurance user information to the application server for the application server to check the application account, or may only send part of the necessary field information content for processing, such as the mobile phone number of the insured or the identity number of the insured, or may include the mobile phone number of the incoming call or the identity number of the register provided by the register.
S2: the application server confirms whether a first application account number of the reporting person exists or not based on the reporting user information.
The application server receives the report user information sent by the insurance company side, and can inquire whether an application account number of a report exists in the application server or a database associated with the application server (here, the application account number corresponding to the report is called a first application account number, correspondingly, the application account number corresponding to the insured is called a second application account number, and if the report is the insured, the first application account number is the same as the second application account number, or the first terminal and the second terminal are the same terminal). In the application scenario of this embodiment, it may be assumed that the insured has registered an application, and an application account of the insured is stored on the application server side. In other embodiments, when checking whether the application account of the applicant exists, the application server may also check whether the application account of the insured exists. If the insured has no application account number, the process can be transferred to a set conventional or traditional insurance processing flow, for example, business personnel of an insurance company continue to answer the incoming call to carry out corresponding reply processing.
In this embodiment, whether there is a corresponding application account may be queried on the application server side based on the report user information, for example, whether there is an application account corresponding to the mobile phone number or an application account owned by the user corresponding to the mobile phone number is queried according to the mobile phone number of the reporter. If so, the person applying the content can further apply the content application on the terminal to check the related information of the claim. Moreover, the application server usually has some information verification or authentication capabilities for the user registering the application account, for example, the user who requires the application registration needs real-name authentication, which may include a real name, a mobile phone number, or user information authentication implemented based on a video image, an iris or a fingerprint. Thus, in another embodiment:
s20: the application server at least has real-name authentication capability, and the application server performs real-name authentication on the report user information;
correspondingly, when the real-name authentication is passed, the processing of confirming whether the first application account number of the person in registration exists is executed.
If the application server records user information of an administrator and can perform real-name authentication, the administrator registers a corresponding application account in the application server or an application belonging to the application server under normal conditions. Therefore, in some implementation scenarios, if the application server can perform verification processing of real-name authentication on the dockee, it may correspondingly confirm that the first application account of the dockee exists. Certainly, in other implementation scenarios, the application server may perform real-name authentication on the reporter, and as for whether the account of the first application exists, the query needs to be performed, and the query result may exist or may not exist.
Therefore, at least some identity information of the reporter can be checked on one side of the application server based on the reporting user information such as the mobile phone number and the like provided by the reporter. For example, if the reporter claims that the reporter is an insured and uses a mobile phone of the reporter to report, the application server can determine whether the reporter is the insured or whether the information reported by the reporter is false or not according to whether the number of the mobile phone of the incoming call of the reporter corresponds to the identity card or not. For example, if the dockee is an insured, further processing may continue; if the application is a non-insured person, corresponding insurance business processing can be further carried out based on identity relation authentication, authorization processing and the like with the insured person; if the information reported by the reporter is false, the request can be refused or the processing operation such as manual verification and the like can be further carried out. Of course, it is also possible to query whether the first application account of the dockee exists when the verification result passes.
S4: if the first application account number exists, whether the first application account number is authorized to use for declaring the insurance service is confirmed, and the first terminal logged in based on the first application account number reports the insurance service after the authorization is confirmed.
If the person who reports the insurance policy is determined to have the corresponding first application account number in the application server, the person who reports the insurance policy can log in the first terminal, report the insurance policy through the first terminal. The confirmation of whether the insurance business is authorized to be declared by using the first application account specifically may include authorization performed by the application server based on an authorization instruction of the first application account. After the person who submits the insurance application confirms the authorization, the person who submits the insurance application can log in the first terminal. In this embodiment, authorizing the first application account to declare an insurance service generally refers to submitting data required for insurance service handling, claim settlement and the like through the first application account, for example, authorizing a certain payment application to declare an insurance claim online. After the authorization is passed, the person then uploads the assessment loss image, fills in the person's information, etc. through the payment application of the first terminal.
Generally, the user may use the first terminal to submit data information required for the application, such as an image of the car damage, an identity document, an insurance policy number, and the like. The person who submits the information has the first application account, and can acquire or submit the required data information through the first terminal logged in by the first application account after the first application account agrees to authorize. The data information can be uploaded to an insurance company, or can be simultaneously uploaded to the application server, and the insurance company can carry out claim settlement processing according to the data information submitted by the first terminal.
S6: and the first terminal acquires a business processing request, and the business processing request is sent to a second terminal for requesting processing authorization logged by a second application account of the insured.
The service processing request may generally include viewing the claim settlement progress, and may also include other claim settlement service information, such as a claim payment amount, a claim payment time, an issuing account, and the like.
If the person who reports wants to check insurance service requests such as claim settlement progress through the first terminal, the first terminal can send the insurance service requests to the second application of the insured. In this embodiment, an application account that the insured logs in may be referred to as a second application account, and a terminal device that the corresponding second application account logs in may be referred to as a second terminal. In some embodiments, when the reporter and the insured are different users, the corresponding first application account and second application account may be different application accounts. The first terminal logged in by the first application account and the second terminal logged in by the second application account may be different terminal devices, and in some embodiments, may also be the same terminal device, for example, the reporter logs in the same terminal by using the second application account after the current terminal logs out of the first application account, or the reporter and the insured are the same person.
For example, in one application scenario of the present embodiment, the applicant is not an insured life. The person who reports can report on the basis of the payment application after authorizing at the present car of the accident, submit relevant insurance business information and upload the vehicle damage picture of the accident. If the claiming person needs to check the claim settlement progress and the like on the car damage site or after a period of time, the insurance service request can be sent to one side of the insured life, and the insured life confirms whether the claiming person is authorized to check the claim settlement progress through the second application account. Of course, if the applicant is an insured, the authorization may be prompted directly in the application or the business process request may be authorized by default or responded directly based on the determined applicant is an insured, and the result is fed back.
The service processing request may be a service processing request initiated in the process of claim settlement, for example, a user wants to check the claim settlement progress through the first application of the first terminal.
S8: and the second terminal performs information verification on the insured corresponding to the service processing request through the application server.
The second terminal may select whether to authorize the dockee to view insurance service requests for case information, claim settlement progress, etc. within the application. If authorization is selected, verification of the insured is triggered. The specific verification can be performed by the application server, and the second terminal can send a message of a verification request to the application server, so that the application server verifies some information (information required to be verified can be agreed in advance) of the insurer based on the verification request. The information verification for the insured can include verifying the mobile phone number, real name and the like of the insured, for example, the mobile phone number and/or the identity card number of the insured can be required to be input on the second terminal, the second terminal sends the verified information to the application server, the application server can verify the insurance order, name and the like of the insured based on the identity card number, or verify whether the mobile phone number of the insured input on the second terminal is correct based on the correspondence between the identity card number and the mobile phone number of the insured stored in the application server, and the like. In other embodiments, other information of the insurer can be verified, and other predetermined verification methods can be used to verify the designated information. Therefore, in some embodiments, the information verification of the insured corresponding to the service processing request includes at least verifying the mobile phone number of the insured.
In this embodiment, the application server may perform identity verification on the insured after receiving the verification request of the insured. The identity verification described in some embodiments may include verification or verification of the insured's true identity information, such as confirming the insured's true cell phone number, true name authentication, etc., although other verification information may be included. The verification mode can be preset, the application server can basically store and record the information of the insured to verify, and the verification can be carried out based on the information provided by the counter or the insured. For example, in an embodiment, the performing, by the application server, information verification on the insured corresponding to the business processing request may include:
s80: the application server checks whether the corresponding relation between the mobile phone number of the insured person and the ID card number is correct or not by using real-name authentication.
The application server may return the verification result to the second terminal that the insured logs in. The returned verification result in the embodiment may be information for verifying the user, and may not include specific verification information, thereby avoiding the problem of revealing the privacy of the user under some implementation conditions. Therefore, in another embodiment of the method provided in this specification, the performing, by the application server, information verification on the insured corresponding to the business processing request may include:
s82: the verification result returned by the application server is a field for representing the successful or failed verification of the insured.
For example, the returned verification result may only include "yes" or "no" whether the verified user information passes, or "verification success", "verification failure", or the like. The verification result here may not contain relevant information of the insured or set information belonging to the insured privacy, and only returns the result of success or failure of verification to the insured. Therefore, the user information can be checked under the condition of effectively guaranteeing the privacy of the user.
S12: when the verification is successful, the second terminal determines that the service processing request of the first terminal is successfully authorized; and the second application account number confirms whether the verified information of the insured is authorized to be sent to the insurance server.
If the application server successfully verifies the insured, the second terminal can determine that the insurance service request sent by the counter is successfully authorized, and at the moment, the counter has a certain right item on the first terminal to check the relevant information of the case.
It should be noted that in some embodiments, the authorization of the insurance business of the applicant by the insured may be an authorization with a certain right item or an authorization of partial information. For example, it may be set that information that can be seen by the person making the application is deleted in the process of claim settlement, or some restrictions are made on insurance services that can be applied for viewing by the person making the application, etc.
In this embodiment, when the insured succeeds in verification, the second application account may also be requested to authorize or not to feed back the verified information of the insured to the insurance server side. The application server checks the information of the insured, and after the information is successfully checked, the authenticity of the appointed information of the insured is verified, for example, the real mobile phone number of the insured is obtained or verified. At this time, the application server may request whether the second application account is authorized to send the information of the insured after the verification is successful, such as the real phone number, to the insurance company side, so that the insurance company side obtains the real and reliable information of the insured based on the information verified by the authorization of the insured and the real name authentication of the application server.
When requesting authorization of the second application account, the request authorization interface may be directly exposed within an application of the second terminal (e.g., a certain payment application), as shown in fig. 2. Of course, in other embodiments, other methods may be used to request authorization, for example, short message acquisition combined with language, image, biometric features, etc. to request authorization and confirm authorization.
In this embodiment, the insurance business request is triggered by the motivation or requirement that the reporter wants to view the case information, and the reporter notifies the insured to request the insurance business. If the insured executes authorization, some identity information verification of the insured can be completed, and the real information of the insured can be determined in the verification process. Therefore, the requirement of the counter is utilized, the authorization and the information verification of the insured can be obtained reasonably and compliantly, the information of the verified person can be returned to the insurance company, and the information of the insured stored at one side of the insurance company can be verified. Accordingly, the method may further comprise:
s14: after the second application account is authorized, the application server sends the verified information of the insured to the insurance server;
s16: the insurance server verifies the stored user information of the insured based on the verified information of the insured.
The application server can confirm the real user information of the insured in the process of identity verification of the insured. The identity verification and authorization process in this embodiment is an authentication process in the case that the insured is approved/authorized, and in this process, whether part of the real user information of the insured, such as the mobile phone number, can be asked to the insurance company, so that the insurance company can better perform subsequent notification, claim settlement, and the like. Because of both the insured's own real information and the insured's interest in itself, the insured will typically authorize the return of their own real user information to the insurer. And the insurance company can verify the information of the insured stored at the insurance server side, such as whether the reserved contact number is correct, whether the information is updated, etc., based on the real user information returned from the application server.
The application server can record the specific authorized content and can perform corresponding authority control. The first terminal may view the claim settlement progress through the payment application based on the success of the service request authorization. Of course, the second terminal can also use the payment application to view related administrative information such as the progress of claim settlement. Fig. 3 is a schematic view of an application scenario of an embodiment of verifying identity information of an insured life in claims provided in this specification. As shown in fig. 3, the content authorized and recorded by the application server may include:
1. the person reporting the case is authorized: the person reporting the case can obtain and look over the case information, look over the progress of claim settlement through paying the application (can set up the person reporting the case can't look over the amount of claim settlement);
2. identity confirmation of the insured: the information such as the insured's real cell phone number is verified and the insured can also use the payment application to view the claim settlement progress (the insured can be set to see the claim settlement amount, or even the full details of the case);
3. some information of the insured, such as the cell phone number, flows back to the insurer. The application server can obtain the mobile phone number actually used by the insured at that time (for example, the mobile phone number is required for check in some insurance business scenes).
The scheme of the embodiment of the specification can verify the identity of the insured life in the insurance application link by utilizing the real-name authentication capability of the third party application, and the real identity information of the insured life can be obtained and confirmed reasonably according to the compliance in the verification process. Under the premise of the authorization of the insured, the information of the real user of the insured can be returned to the insurance company, and the insurance company performs data cleaning, verification and the like, thereby providing better insurance service. By utilizing the embodiment, the real user information of the insured can be reasonably obtained in normal business processing by utilizing the requirement of the insurance business and the authorization authentication process of the insured by utilizing the reporter, such as the real mobile phone number, so that the problem that the insured obtains the user information of the insured under the condition that the insured obtains the user information by illegal means or does not obtain the user agreement can be reduced, the satisfaction degree of the cooperation of the insured operating personnel and third party application is improved, and simultaneously, the quality of the insurance business service of the insured company and the privacy information authorization perception experience of the user are also improved.
The embodiment of the verification user information processing method provided by the specification is described in the aspect of multi-side interaction of the first terminal logged in by the counter/the second terminal logged in by the insured, the application server and the insurance server. Based on the foregoing description of the multi-side interaction embodiment, this specification may further provide an embodiment of a processing method for verifying user information, which may be used for a server, where the server may include, but is not limited to, the application server described in the foregoing embodiment. Specifically, as shown in fig. 4, in one embodiment, the method may include:
s20: the application server confirms whether a first application account number of the reporting person exists or not based on reporting user information, wherein the reporting information comprises information which is determined by the insurance server based on the telephone reporting of the reporting person and at least comprises one of the reporting person and the insured;
s22: if yes, authorizing to use the first application account number to declare insurance business based on an authorization instruction;
s24: the application server carries out information verification on the corresponding insured based on the received business processing request sent by the second terminal logged in by the insured;
s26: the application server returns the verification result to the second terminal, and sends an authorization request for sending the verified information of the insured to the insurance server to a second application account which logs in the second terminal if the verification is successful;
s28: after the second application account is determined to be authorized, the application server sends the verified information of the insured to an insurance server, so that the insurance server verifies the stored user information of the insured based on the verified information of the insured.
The application server guides the traditional telephone application claims to the on-line to verify the real information of the user through the identity verification of the terminal and the server, and utilizes the reasonable compliance of the requirements of the application person (the application person can be an insured person) to obtain the authorization of the insured person, so that the user information is returned to an insurance company, the insurance business experience of the user is effectively improved, and the insurance business risk of the insured person is reduced.
It should be noted that, in the processing method at the application server side in the embodiment of the present specification, other embodiments may also be included according to the description of the method embodiment of the multi-side interaction between the first terminal logged in by the counter/the second terminal logged in by the insured, the application server, and the insurance server. The specific implementation manner may refer to the description of the related method embodiment, and is not described in detail herein.
The above embodiment describes an implementation on the side of the application server when verifying user information. As mentioned above, in some other embodiments, the above-mentioned process of verifying the user information may be performed by a terminal device, such as a mobile phone client according to a certain payment application. The terminal device may be a first terminal or a second terminal. When the person to be reported is not the same person as the insured, the terminal equipment can be different terminal equipment, or different terminals or the same terminal which log in different application accounts. The terminal equipment can be the same terminal equipment when the counter and the insured are the same person. Specifically, an embodiment of a processing method for verifying user information, which can be applied to a terminal device and is provided by the present specification, may include:
s30: the method comprises the steps that a first terminal logged in by a reporter uses a first application account to declare insurance business after authorization, wherein the authorization comprises authorization confirmed by an application server when confirming that the first application account of the reporter exists based on reporting user information when the reporter is on a telephone report;
s32: the first terminal acquires a service processing request, and the service processing request is sent to a second terminal for requesting processing authorization logged in by a second application account of the insured;
s34: the second terminal performs information verification on the insured corresponding to the service processing request through the application server:
s36: when the verification is successful, the second terminal determines that the service processing request of the first terminal is successfully authorized; and the second application account number confirms whether the verified information of the insured is authorized to be sent to an insurance server, so that the insurance server verifies the stored user information of the insured based on the verified information of the insured after the second application account number is authorized.
Based on the above description of the multi-side interaction embodiment, in another embodiment of the method, the user information of the dockee at least includes a mobile phone number of the dockee; the information verification of the insured corresponding to the service processing request comprises at least verification of the mobile phone number of the insured.
In another embodiment of the method, the verification result returned by the application server received by the second terminal is a field representing the successful or failed verification of the insured.
It should be noted that, in the method at the side of the application server or the terminal device in the embodiment of the present specification, the description according to the method embodiment of multi-side interaction may further include other implementation manners. The specific implementation manner may refer to the description of the related method embodiment, and is not described in detail herein.
In the scheme of the embodiment, the services of telephone reporting, insurance leaving, claim settlement and the like under the subscriber line are transferred to the application of the on-line terminal, and identity information verification, authorization confirmation and the like can be carried out in the reporting stage of the subscriber, so that the condition that messages such as claim settlement progress and the like are sent to the subscriber without the consent of the reporting person/insured can be effectively avoided, and the condition that subscriber data such as mobile phone numbers and the like are sent to the insurance company without the consent of the insured can be avoided. By utilizing the implementation scheme of the specification, the user can be guided to the online application for processing insurance business, the information of the insured can be verified based on the real-name authentication of the application server, and the insured usually authorizes the real user data to be transmitted back to the insurance company due to the consideration of common interests, so that the real and effective user information of the user can be obtained at one side of the insurance company, the user information stored in the insurance company can be cleaned, and the wind control and insurance service capacity can be better improved.
In the present specification, each embodiment of the method is described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. Reference is made to the description of the method embodiments.
The method embodiments provided in the embodiments of the present specification may be executed in a mobile terminal, a computer terminal, a server, a distributed system, a blockchain network, or a similar computing device. Taking the example of running on a server, fig. 6 is a hardware structure block diagram of a processing method for verifying user information according to an embodiment of the present invention. As shown in fig. 6, the server 10 may include one or more (only one shown) processors 102 (the processors 102 may include, but are not limited to, a processing device such as a microprocessor MCU or a programmable logic device FPGA, etc.), a memory 104 for storing data, and a transmission module 106 for communication functions. It will be understood by those skilled in the art that the structure shown in fig. 6 is only an illustration and is not intended to limit the structure of the electronic device. For example, the server 10 may also include more or fewer components than shown in FIG. 6, and may also include other Processing hardware, such as a GPU (Graphics Processing Unit), or have a different configuration than shown in FIG. 6, for example.
The memory 104 may be used to store software programs and modules of application software, such as program instructions/modules corresponding to the search method in the embodiment of the present invention, and the processor 102 executes various functional applications and data processing by running the software programs and modules stored in the memory 104, that is, implements the processing method for verifying user information. The memory 104 may include high speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, the memory 104 may further include memory located remotely from the processor 102, which may be connected to the computer terminal 10 over a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.
The transmission module 106 is used to receive or transmit data via a network. Specific examples of the network described above may include a wireless network provided by a communication provider of the computer terminal 10. In one example, the transmission module 106 includes a Network adapter (NIC) that can be connected to other Network devices through a base station to communicate with the internet. In one example, the transmission module 106 may be a Radio Frequency (RF) module, which is used to communicate with the internet in a wireless manner.
Based on the processing method for verifying the user information, the specification further provides a processing device for verifying the user information. The apparatus may comprise a system (including a distributed system), software (applications), modules, components, servers, clients, etc. that utilize the methods described in the embodiments of the present specification in conjunction with any necessary equipment to implement the hardware. Based on the same innovative concept, the processing device in one embodiment provided in the present specification is as described in the following embodiment. Since the implementation scheme for solving the problem of the apparatus is similar to that of the method, the implementation of the specific processing apparatus in the embodiment of the present specification may refer to the implementation of the foregoing method, and repeated details are not repeated. Although the means described in the embodiments below are preferably implemented in software, an implementation in hardware, or a combination of software and hardware is also possible and contemplated. Specifically, as shown in fig. 7, fig. 7 is a schematic block structure diagram of an embodiment of a processing apparatus for verifying user information, which may be used on a server side and provided in this specification, and specifically includes:
the application account number confirmation module 20 may be configured to confirm whether the first application account number of the applicant exists based on the application user information, where the application information includes information that the insurance server determines based on the application of the applicant, and that the information includes at least one of the applicant and the insured;
the application authorization module 21 may be configured to authorize, based on an authorization instruction, to use a first application account of an applicant to apply insurance service when it is determined that the first application account exists;
the verification module 22 may be configured to perform information verification on a corresponding insured based on a received service processing request sent by a second terminal that the insured logs in;
the verification feedback module 23 may be configured to return a verification result to the second terminal, and send, when the verification is successful, an authorization request to the second application account logged in the second terminal, to determine whether to authorize sending the verified information of the insured person to the insurance server;
the information feedback module 24 may be configured to send the verified information of the insured to the insurance server after determining that the second application account is authorized, so that the insurance server verifies the stored user information of the insured based on the verified information of the insured.
As described in the foregoing method embodiment, in another embodiment of the apparatus, the apparatus may further include:
a real-name authentication module 25, configured to perform real-name authentication on the report user information;
accordingly, the application account confirmation module 20 performs a process of confirming whether the first application account of the dockee exists when the real name authentication passes.
As described in the previous method embodiment, in another embodiment of the apparatus, the user information of the dockee comprises at least a mobile phone number of the dockee; correspondingly, the information verification of the corresponding insured comprises at least the verification of the mobile phone number of the insured.
In another embodiment of the apparatus, as described in the previous method embodiment, the verification feedback module 23 returns the verification result as a field indicating the success or failure of the verification of the insured.
As described in the foregoing method embodiment, in another embodiment of the apparatus, the performing, by the verification feedback module 23, information verification on the insured corresponding to the business processing request includes: and checking whether the corresponding relation between the mobile phone number of the insured person and the identity card number is correct or not by using real-name authentication.
As shown in fig. 8, fig. 8 is a schematic block structure diagram of an embodiment of a processing apparatus for verifying user information, which can be used on a terminal device side and provided in this specification, specifically including:
the application account authorization module 30 may be configured to authorize, based on the declaration person, to declare the insurance service using the first application account, where the authorization includes authorization that the application server confirms, based on the declaration user information of the declaration person at the time of telephone declaration, that the first application account of the declaration person exists;
the request forwarding module 31 may be configured to obtain a service processing request, and send the service processing request to a second terminal logged in by a second application account of the insured to request processing authorization;
the verification request module 32 may be configured to perform information verification on the insured corresponding to the service processing request through the application server:
the authorization and service processing module 33 may be configured to determine that the service processing request is successfully authorized when the insured checks successfully; and confirming whether the verified information of the insured life is authorized to be sent to an insurance server, so that the insurance server verifies the stored user information of the insured life based on the verified information of the insured life after the second application account is authorized.
The method or apparatus provided in this specification may be implemented in a computer by executing corresponding program instructions by a processor, for example, implemented on a PC side using a c + + language of a windows operating system, or implemented in other hardware necessary for an application design language set corresponding to, for example, linux, android, and iOS systems, or implemented in processing logic based on a quantum computer. Specifically, in an embodiment of the processing device for verifying the user information, which implements the method or the apparatus described above, the processing device may be the application server described above, and in a specific embodiment, the server may include a processor and a memory for storing processor-executable instructions, and when the processor executes the instructions, the processor implements:
confirming whether a first application account number of the reporter exists or not based on the report user information, wherein the report information comprises information which is determined by the insurance server based on the telephone report of the reporter and at least comprises one of the reporter and the insured;
when determining that a first application account of a reporter exists, authorizing to use the first application account to declare insurance business based on an authorization instruction;
based on a received service processing request sent by a second terminal logged in by the insured, carrying out information verification on the corresponding insured;
returning the verification result to the second terminal, and sending an authorization request for sending the verified information of the insured to the insurance server to a second application account which logs in the second terminal when the verification is successful;
and after determining that the second application account is authorized, sending the verified information of the insured to an insurance server, so that the insurance server verifies the stored user information of the insured based on the verified information of the insured.
Similarly, in another embodiment of the processing device for verifying the user information, which implements the method or apparatus described above, the processing device is a terminal device, such as a mobile terminal according to a mobile phone with a certain payment application. In a specific embodiment, the terminal device may include a processor and a memory for storing processor-executable instructions, and when the processor executes the instructions, the processor implements:
the insurance business is declared by using the first application account number based on the authorization obtained by the reporting person, wherein the authorization comprises the authorization confirmed by the application server when the first application account number of the reporting person exists based on the reporting user information of the reporting person during the telephone reporting;
acquiring a business processing request, and sending the business processing request to a second terminal logged by a second application account of the insured to request processing authorization;
and the application server carries out information verification on the insured corresponding to the service processing request:
when the insured succeeds in verification, the service processing request is determined to be successfully authorized; and confirming whether the verified information of the insured life is authorized to be sent to an insurance server, so that the insurance server verifies the stored user information of the insured life based on the verified information of the insured life after the second application account is authorized.
The instructions described above may be stored in a variety of computer-readable storage media. The computer readable storage medium may include physical devices for storing information, which may be digitized and then stored using an electrical, magnetic, or optical media. The computer-readable storage medium according to this embodiment may include: devices that store information using electrical energy, such as various types of memory, e.g., RAM, ROM, etc.; devices that store information using magnetic energy such as hard disks, floppy disks, tapes, core memories, bubble memories, and usb disks; devices that store information optically, such as CDs or DVDs. Of course, there are other ways of storing media that can be read, such as quantum memory, graphene memory, and so forth. The instructions in the devices or servers or clients or systems described below are as described above.
The terminal device types can comprise a mobile terminal, a special vehicle insurance device, a vehicle-mounted interaction device, a personal computer, an intelligent wearable device and the like.
The specification also provides a processing system for verifying the user information, and the system can complete the verification of the insured information by combining the interaction, authorization, verification and other processing of the terminal equipment at the user side and the application server. In particular, sensitive and important information such as a mobile phone number of an insured person is verified and verified, and the verified user information is returned to an insurance company in a legal and compliant way. In a specific embodiment, the processing system may include:
an application server, wherein a processor on the application server executes executable instructions stored in a memory to implement the steps of the method according to any one of the embodiments of the present disclosure;
and the processor of the terminal device executes the executable instructions stored in the memory to realize the steps of the method of any one embodiment in the specification.
It should be noted that, the apparatus, the processing device, the server, the terminal device, the system, and the like described above in this embodiment of the present disclosure may also include other embodiments according to the description of the related method embodiment, for example, the user information of the counter at least includes a mobile phone number, and whether the corresponding relationship between the mobile phone number of the insured person and the identity number is correct or not is checked by using real-name authentication when the insured person checks, and the like. The specific implementation manner may refer to the description of the method embodiment, and is not described in detail herein.
The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the hardware + program class embodiment, since it is substantially similar to the method embodiment, the description is simple, and the relevant points can be referred to the partial description of the method embodiment.
The foregoing description has been directed to specific embodiments of this disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims may be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing may also be possible or may be advantageous.
Although the embodiments herein provide method steps as described in embodiments or flowcharts, additional or fewer steps may be included based on conventional or non-inventive efforts. The order of steps recited in the embodiments is merely one manner of performing the steps in a multitude of orders and does not represent the only order of execution. When an actual apparatus or client product executes, it may execute sequentially or in parallel (e.g., in the context of parallel processors or multi-threaded processing) according to the embodiments or methods shown in the figures.
Although the content of the embodiments of the present specification refers to the operations and data descriptions of data acquisition, storage, interaction, calculation, judgment, and the like, such as payment application, verification of mobile phone number, claims viewing, request authorization, and the like, the embodiments of the present specification are not limited to compliance with industry communication standards, standard database data syntax, communication protocols, and standard data models/templates or the situations described in the embodiments of the present specification. Certain industry standards, or implementations modified slightly from those described using custom modes or examples, may also achieve the same, equivalent, or similar, or other, contemplated implementations of the above-described examples. The embodiments using these modified or transformed data acquisition, storage, judgment, processing, etc. may still fall within the scope of the alternative embodiments of the present description.
In the 90 s of the 20 th century, improvements in a technology could clearly distinguish between improvements in hardware (e.g., improvements in circuit structures such as diodes, transistors, switches, etc.) and improvements in software (improvements in process flow). However, as technology advances, many of today's process flow improvements have been seen as direct improvements in hardware circuit architecture. Designers almost always obtain the corresponding hardware circuit structure by programming an improved method flow into the hardware circuit. Thus, it cannot be said that an improvement in the process flow cannot be realized by hardware physical blocks. For example, a Programmable Logic Device (PLD), such as a Field Programmable Gate Array (FPGA), is an integrated circuit whose Logic functions are determined by programming the Device by a user. A digital system is "integrated" on a PLD by the designer's own programming without requiring the chip manufacturer to design and fabricate application-specific integrated circuit chips. Furthermore, nowadays, instead of manually manufacturing an Integrated Circuit chip, such Programming is often implemented by "logic compiler" software, which is similar to a software compiler used in program development and writing, but the original code before compiling is also written by a specific Programming Language, which is called Hardware Description Language (HDL), and HDL is not only one but many, such as ABEL (Advanced Boolean Expression Language), AHDL (alternate Hardware Description Language), traffic, CUPL (core universal Programming Language), HDCal, jhddl (Java Hardware Description Language), lava, lola, HDL, PALASM, rhyd (Hardware Description Language), and vhigh-Language (Hardware Description Language), which is currently used in most popular applications. It will also be apparent to those skilled in the art that hardware circuitry that implements the logical method flows can be readily obtained by merely slightly programming the method flows into an integrated circuit using the hardware description languages described above.
The controller may be implemented in any suitable manner, for example, the controller may take the form of, for example, a microprocessor or processor and a computer-readable medium storing computer-readable program code (e.g., software or firmware) executable by the (micro) processor, logic gates, switches, an Application Specific Integrated Circuit (ASIC), a programmable logic controller, and an embedded microcontroller, examples of which include, but are not limited to, the following microcontrollers: ARC 625D, atmel AT91SAM, microchip PIC18F26K20, and Silicone Labs C8051F320, the memory controller may also be implemented as part of the control logic for the memory. Those skilled in the art will also appreciate that, in addition to implementing the controller in purely computer readable program code means, the same functionality can be implemented by logically programming method steps such that the controller is in the form of logic gates, switches, application specific integrated circuits, programmable logic controllers, embedded microcontrollers and the like. Such a controller may thus be considered a hardware component, and the means included therein for performing the various functions may also be considered as a structure within the hardware component. Or even means for performing the functions may be regarded as being both a software module for performing the method and a structure within a hardware component.
The systems, devices, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions. One typical implementation device is a computer. In particular, the computer may be, for example, a personal computer, a laptop computer, a vehicle-mounted human-computer interaction device, a cellular telephone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.
Although embodiments of the present description provide method steps as described in embodiments or flowcharts, more or fewer steps may be included based on conventional or non-inventive means. The order of steps recited in the embodiments is merely one manner of performing the steps in a multitude of orders and does not represent the only order of execution. When an actual apparatus or end product executes, it may execute sequentially or in parallel (e.g., parallel processors or multi-threaded environments, or even distributed data processing environments) according to the method shown in the embodiment or the figures. The terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, the presence of additional identical or equivalent elements in processes, methods, articles, or apparatus that include the recited elements is not excluded.
For convenience of description, the above devices are described as being divided into various modules by functions, and are described separately. Of course, when implementing the embodiments of the present specification, the functions of each module may be implemented in one or more pieces of software and/or hardware, or a module that implements the same function may be implemented by a combination of multiple sub-modules or sub-units, or the like. The above-described embodiments of the apparatus are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, 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.
Those skilled in the art will also appreciate that, in addition to implementing the controller in purely computer readable program code means, the same functionality can be implemented by logically programming method steps such that the controller is in the form of logic gates, switches, application specific integrated circuits, programmable logic controllers, embedded microcontrollers and the like. Such a controller may therefore be considered as a hardware component, and the means included therein for performing the various functions may also be considered as a structure within the hardware component. Or even means for performing the functions may be regarded as being both a software module for performing the method and a structure within a hardware component.
The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include forms of volatile memory in a computer readable medium, random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.
Computer-readable media, including both permanent and non-permanent, removable and non-removable media, may implement the information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static Random Access Memory (SRAM), dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), read Only Memory (ROM), electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.
As will be appreciated by one skilled in the art, embodiments of the present description may be provided as a method, system, or computer program product. Accordingly, the embodiments described herein may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, embodiments of the present description may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and so forth) having computer-usable program code embodied therein.
The embodiments of this specification may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The described embodiments may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.
The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the system embodiment, since it is substantially 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. In the description of the specification, reference to the description of "one embodiment," "some embodiments," "an example," "a specific example," or "some examples" or the like means that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the embodiments of the specification. In this specification, the schematic representations of the terms used above are not necessarily intended to refer to the same embodiment or example. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples. Furthermore, various embodiments or examples and features of different embodiments or examples described in this specification can be combined and combined by one skilled in the art without contradiction.
The above description is only an example of the embodiments of the present disclosure, and is not intended to limit the embodiments of the present disclosure. Various modifications and variations to the embodiments described herein will be apparent to those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the embodiments of the present specification should be included in the scope of the claims of the embodiments of the present specification.