Customer one-code-through identity recognition method and system for insurance service

Abstract

The invention relates to a customer one-code identity recognition method and system for insurance business. According to the method, a client ONEID is constructed based on a client unique identity recognition technology, and a client code is constructed by the client ONEID based on a client two-dimensional code technology; the identity recognition method comprises the steps of recognizing and collecting identity elements when a client reaches a service scene for the first time, generating a general mapping rule based on the identity elements and a client ONEID, and storing the general mapping rule in a cache to form stock data; and when the client needs identity recognition in the business scene, executing an identity recognition process: matching the input identity elements with the stock data layer by layer according to the priority by following a user ID recognition priority strategy and a user ID similarity strategy, if the input identity elements are consistent with the stock data, recognizing a matched client ONEID, and otherwise, creating a new ONEID. Compared with the prior art, the method has the advantages of reducing safety risks, improving recognition efficiency, improving user experience and the like.

Description

Technical Field

[0001] This invention relates to the field of identity recognition technology, and in particular to a customer one-code identity recognition method and system for insurance business. Background Technology

[0002] As the insurance industry accelerates its digital transformation, customer outreach channels are expanding from traditional offline branches to multiple platforms such as apps, mini-programs, and agent mobile devices, covering the entire lifecycle of insurance, including underwriting, claims, policy maintenance, and renewal. However, most insurance institutions' customer identification technologies remain stuck in traditional models, failing to develop integrated solutions suitable for multiple scenarios and the entire process. This presents a significant contradiction with the industry's high demands for risk control, operational efficiency, and customer experience.

[0003] In terms of security and risk control, traditional verification methods are insufficient to defend against new types of risks. The nature of insurance business dictates a high degree of reliance on identity verification, making identity recognition a core aspect of risk control. However, existing technologies have multiple security shortcomings: The risks of identity theft and fraud are prominent: Traditional identity verification relies on manual review combined with paper materials. It depends on the visual inspection of ID cards, insurance policies, medical records and other materials by the reviewers. This is difficult to deal with increasingly covert forgery and impersonation methods, and there are data silos between different insurance companies and different business lines.

[0004] The risk of sensitive data leakage is significant: There are inherent security vulnerabilities in the storage and circulation of paper materials. Materials containing core privacy information are easily lost in archives or illegally copied during cross-departmental transfers. Furthermore, the risk of data leakage is further amplified when data is manually entered due to issues such as information screenshots and lax system access control.

[0005] In terms of operational efficiency, the continuity of insurance business processes depends on the efficient flow of identity information, but under the existing technology system, identity verification has become a bottleneck in the process.

[0006] Manual operation leads to both inefficiency and accuracy: In core scenarios such as insurance application and claims, customer information needs to be transferred through multiple stages, including paper filling, agent collection, office staff entry and system verification. If there are errors, repeated communication is required through telephone, offline supplementary materials, etc., which results in long time consumption and low efficiency in identity verification for a single policy.

[0007] Inconsistent information across channels: When customers conduct business through different channels such as APP, offline outlets, and salespersons, their identity information often appears in multiple versions. There is a lack of a unified identity information association mechanism, and manual verification is required for each version.

[0008] In terms of customer experience, cumbersome processes and service gaps reduce satisfaction. The ease of identity verification directly affects customers' perception of insurance services. Problems such as repetitive verification and fragmented processes in the existing model have become the main causes of customer churn.

[0009] Excessive burden on customers: The same customer needs to provide identity materials repeatedly in different business scenarios, and even needs to verify mobile phone numbers or fill out forms repeatedly in different stages of the same business.

[0010] Delayed service response from sales representatives: Because customer identity information is stored on multiple platforms and lacks a unified identifier, agents have to switch between multiple systems to query information when providing services, making it difficult to quickly obtain the identity information submitted by customers through online channels, which leads to customer dissatisfaction.

[0011] In summary, the insurance industry's demand for identity verification has evolved from simple verification to a secure, controllable, efficient, and seamless end-to-end solution. However, the traditional technology model's triple shortcomings in risk control, operational efficiency, and customer experience have become the core bottlenecks restricting the industry's digital transformation. Summary of the Invention

[0012] The purpose of this invention is to overcome the shortcomings of the existing technology and provide a customer identification method and system for insurance business.

[0013] The objective of this invention can be achieved through the following technical solutions: According to one aspect of the present invention, a customer identification method for insurance business is provided. This method constructs a customer ONEID based on customer unique identification technology and constructs a customer code based on the customer ONEID using customer QR code technology. The identification method includes the following steps: When a customer first engages with a business scenario, identity elements are identified and collected. Based on these identity elements and the customer's ONEID, a general mapping rule is generated and stored in the cache to form existing data. When a customer needs to identify themselves in a business scenario, the identification process is executed: following the user ID identification priority strategy and user ID similarity strategy, the input identity elements are matched with the existing data layer by layer according to priority. If a match is found, the matching customer ONEID is identified; otherwise, a new ONEID is created.

[0014] As a preferred technical solution, the user ID recognition priority strategy is as follows: The system prioritizes identity elements based on their relevance, with stronger relevance resulting in higher priority. This constructs a hierarchical identification chain from ID number to scenario-related information. ID number is prioritized as the primary identification element due to its official authority and uniqueness. Subsequent elements include name, mobile phone number, cross-platform user unique identifier, scenario-specific user identifier, and terminal association identifier. The system also supports custom expansion of elements and adjustment of levels based on business scenario needs. By matching matching information from existing data layer by layer, all potentially associated customer ONEIDs are initially screened, forming a candidate pool.

[0015] As a preferred technical solution, the user ID similarity strategy is as follows: For candidate ONEIDs in the candidate pool, multi-dimensional similarity is calculated based on the combined features of identity elements, and a dual judgment mechanism of element matching degree and scene adaptability is constructed. First, the identity elements are quantitatively compared using a string similarity algorithm to generate a single-element similarity score; then, the overall similarity ratio is calculated by combining the element combination weights. Based on this, the preset similarity ratio threshold is dynamically adjusted by integrating business scenarios; Select customer ONEIDs from the candidate pool whose overall similarity ratio is higher than the preset similarity ratio threshold.

[0016] As a preferred technical solution, dynamically adjusting the preset similarity ratio threshold in conjunction with business scenarios specifically includes: The higher the risk of the business scenario, the higher the preset similarity ratio threshold should be. The higher the authority of the channel, the lower the preset similarity ratio threshold; The higher the relevance between the salesperson and the customer, the lower the preset similarity threshold. The more recently the customer's identity elements were updated, the lower the preset similarity ratio threshold should be; The higher the customer's historical transaction frequency in the current business type, the lower the preset similarity ratio threshold.

[0017] As a preferred technical solution, the identity verification process specifically includes: The main line of judgment is performed sequentially to determine whether the input identity elements contain the first identity element, the second identity element, the third identity element, the fourth identity element, and the fifth identity element. If none of them are contained, a new ONEID is created and returned. In addition to the first identity element, if an identity element is determined to be included, the corresponding matching and matching detection are performed to obtain the matching result. At this time, it is determined whether the current input parameters contain a parameter with a higher priority than the parameter determined to be included. If not, the ONEID with the highest confidence in the matching result is returned. If so, it is necessary to determine whether the corresponding identity element of the current matching result contains a parameter with a higher priority than the parameter determined to be included. If so, a new ONEID is created and returned. Otherwise, the ONEID with the highest confidence in the matching result is returned.

[0018] When the input parameters include the first identity element, the three-element hierarchical matching process and matching detection of the first identity element are directly executed to obtain the matching result, and finally the ONEID with the highest confidence in the matching result is returned; The priority of the first identity element, the second identity element, the third identity element, the fourth identity element, and the fifth identity element decreases in that order.

[0019] As a preferred technical solution, the specific process of constructing a customer code using the customer's ONEID includes: The customer code validity period is set, and the customer ONEID and the customer code validity period constitute a unique customer identifier. Then, a dynamic QR code is generated from this unique customer identifier using the SM4 encryption algorithm.

[0020] The customer code has a dynamic validity period, which is generated by the server's precise timestamp, the business scenario's preset validity period, the SM4 encryption algorithm, a random factor, and the business identifier.

[0021] As a preferred technical solution, the application process of the customer code includes: In a QR code scanning scenario, the application process includes: After a user scans a QR code, identity authentication is performed; after authentication, customer identity is identified, and a customer ONEID is retrieved or generated; based on the customer ONEID, current customer behavior information is recorded. In the scenario of presenting a code, the application process includes: The client performs identity authentication, collects the information entered during authentication, and identifies the customer after authentication. Based on the identification result, it calls or generates the customer's ONEID and generates a corresponding customer code. After the staff scans the customer code, the background records the current customer behavior information.

[0022] As a preferred technical solution, the authentication method is adjusted according to the business scenario during identity authentication. The business scenarios include activity scenarios, basic service scenarios, and value-added service scenarios. In activity scenarios, the first authentication plus the second authentication is used by default. In basic service scenarios, the first authentication is used by default. In value-added service scenarios, the first authentication plus the second authentication is used by default. The first authentication is a combination of ID number and facial recognition. The second authentication is SMS verification.

[0023] As a preferred technical solution, the customer code is equipped with an automatic refresh mechanism and an anti-screenshot mechanism. The automatic refresh mechanism is that the customer code is automatically refreshed at preset intervals, and historical customer codes are automatically invalidated. The anti-screenshot mechanism is that the customer code is not allowed to be screenshotted, and other scanning channels besides the matching scanning channels cannot recognize the QR code content.

[0024] According to another aspect of the present invention, a customer identification system with a single code for insurance business is provided, the system comprising a data layer, a service layer and an application layer; The data layer is used for storing and caching existing data; The service layer integrates user ID recognition priority strategy, user ID similarity strategy, encryption algorithm and third-party integration capabilities to complete identity recognition service, customer code generation service and identity authentication service; The application layer includes a customer QR code component and a scan component, which can be integrated into insurance apps, mini-programs, and H5 pages via page embedding or API interface to meet the customer code generation and scanning needs of online business scenarios.

[0025] Compared with the prior art, the present invention has the following beneficial effects: 1. In this invention, a customer ONEID is constructed and stored when the business scenario is first accessed. Subsequently, identity elements are matched according to the user ID identification priority strategy and the user ID similarity strategy. This avoids the identity confusion caused by the repeated creation of numbers in multiple systems in the traditional way, and saves customers from repeatedly submitting information. At the same time, layered matching reduces invalid verification and greatly improves the efficiency of identity recognition. This solution integrates customer unique identity recognition technology and customer QR code technology to meet the real-time identity verification needs of customer business activities, basic services, value-added services and other business scenarios. It covers the trajectory record of the entire customer journey and solves the triple shortcomings of traditional mode in terms of risk, efficiency and experience. It reduces security risks, improves recognition efficiency and enhances user experience.

[0026] 2. In this invention, the user ID recognition priority strategy uses the correlation of identity elements as the core sorting logic, reducing the risk of misjudgment due to unordered matching of traditional elements; it supports custom extended elements to adapt to different insurance business scenarios, avoiding efficiency losses caused by rigid processes; and high-priority elements are accurately matched, reducing the submission of redundant customer information.

[0027] 3. In this invention, the user ID similarity strategy dynamically adjusts the preset similarity ratio threshold by integrating business scenarios; through multi-dimensional similarity calculation and scenario-based threshold adjustment, it avoids the accuracy problem of traditional single-dimensional matching; comprehensive similarity judgment reduces manual verification steps and improves identity recognition efficiency; accurate matching can be completed without requiring customers to provide additional information, avoiding the cumbersome experience of traditional repeated verification. The threshold is dynamically adjusted based on dimensions such as business risk and channel authority; the threshold is increased in high-risk scenarios to ensure security, and the threshold is lowered for authoritative channels to simplify the process; a balance is found between risk and convenience, while reducing unnecessary authentication operations for customers.

[0028] 4. In this invention, the results are returned by judging the elements in order of priority and combining the confidence level, avoiding the risk of missed judgments and misjudgments caused by the disordered verification of traditional processes; the clear judgment logic reduces invalid steps and improves the response speed of identity recognition; customers do not need to repeatedly fill in information, and high-priority elements are matched first, shortening the customer's waiting time.

[0029] 5. In this invention, customer codes are generated using SM4 encryption and dynamic validity periods, avoiding the risks of easy tampering and theft associated with traditional static QR codes, thus improving security. The authentication method is adapted to different insurance business scenarios: strong authentication is used for basic service scenarios, while a combination of strong and weak authentication is used for promotional or value-added scenarios. This avoids the problems of traditional unified authentication being too strict and affecting efficiency, or too lenient and increasing risk, thus balancing risk and efficiency. SMS verification serves as a supplement to weak authentication, reducing complex operations for customers in non-core scenarios while ensuring the security of core services. Customer codes enable omnichannel identity recognition, supporting different authentication strengths for different scenarios. Customer codes cover multiple scenarios in the customer journey, including three core business scenarios: marketing activities, basic services, and value-added services. Automatic refresh and anti-screenshot mechanisms for customer codes avoid the risks of long-term validity and easy screenshotting and theft associated with traditional QR codes. Attached Figure Description

[0030] Figure 1 This is a schematic diagram illustrating the steps involved in a customer's initial contact with the business scenario in this invention. Figure 2 This is a schematic diagram of the identity recognition process steps in this invention; Figure 3 This is a diagram illustrating the specific process of identity recognition in the embodiment; Figure 4 This is a schematic diagram of the customer code generation steps in the embodiment. Detailed Implementation

[0031] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of the present invention.

[0032] In the insurance sector, the lack of a unified customer identification code for insurance business leads to the following three problems: First, in terms of security, traditional identity verification relies on manual review or paper materials, which are prone to forgery and impersonation; paper materials are also difficult to store and share, posing a risk of sensitive data leakage. Second, in terms of efficiency, manual entry of customer information is prone to errors, leading to repeated communication or process delays; business processing relies on offline submission of materials, which is time-consuming and increases operating costs. Third, in terms of user experience, customers need to provide documents or fill out forms multiple times, making the process cumbersome; agents have difficulty quickly retrieving historical records, resulting in slow service response and decreased customer satisfaction.

[0033] Example 1 In this embodiment, a customer identification method using a unique customer identification code is adopted. This method constructs a customer ONEID based on customer unique identification technology and constructs a customer code based on the customer ONEID using customer QR code technology. The method steps include: like Figure 1 As shown, when a customer first engages with a business scenario, identity elements are identified and collected. Based on these identity elements and the customer's ONEID, a general mapping rule is generated and stored in the cache to form existing data. like Figure 2 As shown, when a customer needs to identify themselves in a business scenario, the system follows the user ID recognition priority strategy and the user ID similarity strategy, matching the input identity elements with the existing data layer by layer according to priority. If a match is found, the matching customer ONEID is identified; otherwise, a new ONEID is created.

[0034] The user ID recognition priority strategy is as follows: The system prioritizes identity elements based on their relevance, with stronger relevance resulting in higher priority. This constructs a hierarchical identification chain from ID number to scenario-related information. ID number is prioritized as the primary identification element due to its official authority and uniqueness. Subsequent elements include name, mobile phone number, cross-platform user unique identifier, scenario-specific user identifier, and terminal association identifier. The system also supports custom expansion of elements and adjustment of levels based on business scenario needs. By matching matching information from existing data layer by layer, all potentially associated customer ONEIDs are initially screened, forming a candidate pool.

[0035] The user ID similarity strategy is as follows: For candidate ONEIDs in the candidate pool, multi-dimensional similarity is calculated based on the combined features of identity elements, and a dual judgment mechanism of element matching degree and scene adaptability is constructed. First, the identity elements are quantitatively compared using a string similarity algorithm to generate a single-element similarity score; then, the overall similarity ratio is calculated by combining the element combination weights. Based on this, the preset similarity ratio threshold is dynamically adjusted by integrating the risk of business scenarios. The higher the risk, the higher the preset similarity ratio threshold. Select customer ONEIDs from the candidate pool whose overall similarity ratio is higher than the preset similarity ratio threshold.

[0036] In a QR code scanning scenario, the steps of this identity verification method include: The user performs the scanning action; User authentication is performed on the client side; Perform customer identification; Record current customer behavior information; In the scenario of presenting a code, the steps of this identity recognition method include: After authentication, the system collects the information entered by the customer during authentication, performs customer identification, and, based on the identification results, calls or generates the customer's ONEID and generates a corresponding customer code. After the staff scans the customer code, the background records the current customer behavior information.

[0037] The specific process of customer identification includes: The main line of judgment is performed sequentially to determine whether the input identity elements contain the first identity element, the second identity element, the third identity element, the fourth identity element, and the fifth identity element. If none of them are contained, a new ONEID is created and returned. In addition to the first identity element, if an identity element is determined to be included, the corresponding matching and matching detection are performed to obtain the matching result. At this time, it is determined whether the current input parameters contain a parameter with a higher priority than the parameter determined to be included. If not, the ONEID with the highest confidence in the matching result is returned. If so, it is necessary to determine whether the corresponding identity element of the current matching result contains a parameter with a higher priority than the parameter determined to be included. If so, a new ONEID is created and returned. Otherwise, the ONEID with the highest confidence in the matching result is returned.

[0038] When the input parameters include the first identity element, the three-element hierarchical matching process and matching detection of the first identity element are directly executed to obtain the matching result, and finally the ONEID with the highest confidence in the matching result is returned.

[0039] The priority of the first identity element, the second identity element, the third identity element, the fourth identity element, and the fifth identity element decreases in that order.

[0040] Furthermore, the input parameters are not limited to the first to fifth identity elements, but also include other identity elements. In this embodiment, the identity elements are given examples and their priorities are defined, as shown in Table 1. The smaller the priority number, the higher the priority.

[0041] In Table 1, for the ID number category, ID number + ID type + name are unique. If the name or ID does not match, it will be matched with other elements and the customer data will be tagged for subsequent data governance processes. For the mobile phone number category, certified mobile phones have higher priority than uncertified mobile phones. UNIONID and OPENID are unique elements for identifying customers in the WeChat system and are highly unique. Device fingerprint ID, uncertified mobile phone number, email address and address are all auxiliary identification elements. When there are no high-priority matching parameters, these auxiliary identification elements can also be used as customer identification elements.

[0042] During identification, the principle of high similarity between user IDs is followed: User ONEID overall identification logic: Existing customers are matched sequentially from highest to lowest priority. If a high-priority customer is successfully matched, that customer is identified. If no match is found, the matching continues with lower-priority customers. If no matching is found for any of the identified features, a new ONEID is created. User ONEID overall identification details: Document recognition rules: If document information conflicts with existing customer information, such as the same document number but different document type or name, it must meet the requirement that any non-unique element matches in order to be matched as the same ONEID; For example: An existing customer has the following information: ID 1 + Zhang San + Mobile Phone A. When a new customer registers, they enter ID 1 + Li Si + Mobile Phone A. While the matching of these elements doesn't match, the ID and mobile phone number match, so they can be considered the same customer. Non-unique ID identification rules: Since non-unique IDs have a one-to-many relationship with people, there is no matching conflict. As long as the matching customer information is consistent, it can be regarded as the same customer. For example: If the existing customer is: ID 1 + Zhang San + UNIONIDA, then when a customer registers, if the entered UNIONIDA matches the UNIONID, they can be considered the same customer. Extreme value rule: Identify customers based on the last four digits of their ID number / last four digits of their mobile phone number + gender + surname + date of birth; 2.4 Mobile phone number recognition rules: Salesperson ID numbers must be filtered out, salesperson mobile phone numbers must be excluded, and customers with verified mobile phone numbers should be recognized first.

[0043] Table 1 User ID Identification Priority Principles In this embodiment, the customer one-code system architecture and functions of the insurance business are divided into three major scenarios: activity scenario, basic service scenario, and value-added service scenario; two types of customers: formal customers and potential customers; formal customers are customers who have already purchased insurance products or enjoyed insurance services, and enjoy services such as policy management, claims, renewal, and value-added services; potential customers are customers who have not purchased insurance products or enjoyed insurance services, and can be converted into formal customers through communication.

[0044] The methods for generating and managing customer access codes include: The underlying principle for generation is: customer ONEID, code validity period, and encryption algorithm; The code can be obtained through: the official unified entry point, the mini-program entry point, and the business scenario entry point; Security control methods include: automatic code refresh, anti-tampering, anti-replay, security authentication, and two-factor authentication. When using the customer's unified code: Use cases for displaying codes (customer code or family code): Business scenarios involving offline interactions with salespersons or service personnel, such as booking events and check-in verification. Family code functionality is supported; for example, when the insured and beneficiary are minors or elderly individuals, guardians or family members can apply for a family code. QR code scanning usage scenarios: Customers can scan the business scenario code to apply for and complete related business on their own, such as: security maintenance acceptance, service evaluation, etc. Service extension: Based on the customer's identity information with the insurance company, provide customers with convenient inquiry services, such as policy inquiry and personal rights inquiry.

[0045] A comparison between the current situation and the situation after customers have implemented the unified QR code system: Current status on the left: Check-in scenario: After arriving at the event venue, customers need to scan the event verification service code with WeChat, then select to log in with their registration information or enter their information to register, and complete the check-in process through manual verification. This process is time-consuming and labor-intensive. Gift collection scenario: When customers collect gifts, service personnel manually register the information, which can lead to human error and difficulties in sharing the information.

[0046] After applying the Customer One-Code Pass on the right: Check-in scenario: After registering on behalf of customers, an invitation letter is sent to the customers. When the customers arrive at the venue, they can scan the QR code (the event verification service code) with WeChat for automatic verification. It supports one-code scanning, allowing customers to quickly verify their information. The sales staff can also see relevant customer information (such as historical event participation records, registration records, etc.), improving the customer experience. Gift redemption scenario: When customers redeem gifts, they show a code for verification, and the system registers the information in real time, achieving overall efficiency, convenience, security, reliability, and support for multiple scenarios.

[0047] In this embodiment, the first identity element is the ID number, the second identity element is the mobile phone number, the third identity element is the UNIONID, the fourth identity element is the OPENID, and the fifth identity element is the device fingerprint ID.

[0048] In this embodiment, the identity recognition process is as follows: Figure 4 As shown, it is: S1. Determine whether the input parameter contains an ID number. If it does, continue to step S11; otherwise, proceed to step S2. S11. Set the hierarchical behavior: the first level behavior is 3-element matching; the second level behavior is 2-element matching; the third level behavior is 1-element matching; perform the first level behavior, the second level behavior, and the third level behavior in sequence. If a certain level behavior is successfully matched, record the current level number and jump to step S12; otherwise, jump to step S2. Three elements refer to the type of document, document number, and name; two elements refer to the document number and name; one element refers to the document number.

[0049] S12. Check if the current level of matching matches a customer and there is no data conflict; if yes, proceed to step S8; if no, return to step S11 and execute the next level of behavior. S2. Determine if the input parameter contains a mobile phone number; if it does, proceed to step S21. S21. Determine if the phone number and name match successfully; if yes, proceed to step S22; if no, proceed to step S3. S22. Determine whether a customer is matched and there is no data conflict. If yes, proceed to step S6; otherwise, proceed to step S3. S3. Determine whether the input parameter contains UNIONID. If it does, proceed to step S31; otherwise, proceed to step S4. S31. Perform UNIONID matching and check if the match is successful. If successful, proceed to step S6; otherwise, proceed to step S4. S4. Determine if the input parameter contains OPENID; if yes, proceed to step S41; otherwise, proceed to step S5. S41. Based on OPENID and its source, perform a match and check if the match is successful. If successful, proceed to step S6; otherwise, proceed to step S5. S5. Determine whether the input parameters include the device fingerprint ID; if yes, continue to execute S51; otherwise, if none of the input parameters match, create and return a new ONEID. S51. Determine whether the device fingerprint and the name or single device fingerprint match successfully. If yes, continue to step S52; otherwise, create and return a new ONEID. S52. Determine if a customer is matched and there is no data conflict; if yes, proceed to step S6; if no, create and return a new ONEID. S6. Determine if there are any high-priority parameters in the input parameters; if so, then proceed; otherwise, jump to step S8. S7. Determine if the matched existing customers have high priority parameters. S8. Check if multiple ONEIDs are matched. If so, return the ONEID with the highest confidence; otherwise, return the unique ONEID.

[0050] In the above steps, the matching results include the data pairs of the matched customers and ONEIDs.

[0051] This solution integrates customer unique identification technology and customer QR code technology, and combines insurance business data and operations to flexibly apply it to activities, basic services and value-added services, significantly improving the customer experience.

[0052] The implementation and application principles of the technical components are as follows: 1. Customer Identity ONEID Recognition Steps 1.1 Define Standard Customer ONEID: First, define the standard ONEID format, consisting of a 2-digit business identifier and an ID generated by the Snowflake algorithm, ensuring that each user has a unique identifier; define the ONEID data structure, including a unique identifier and an extended association information layer; the extended association information layer includes an original identity association sublayer, an identity change record sublayer, and an access control sublayer; the original identity association sublayer is used to associate the customer's original identifier in different business scenarios, including necessary user information and association relationship information; the identity change record sublayer records the change history of ONEID and associated information, ensuring that identity is traceable; the access control sublayer defines the identity permissions corresponding to ONEID, supporting access and function control of the business system.

[0053] 1.2 Configure identity recognition strategy: Identify user identification elements, generate general mapping rules and store them in the cache REDIS; ONEID recognition follows the user ID recognition priority strategy and user ID high similarity strategy, matching the incoming user ID with the existing data layer by layer according to priority. If a match is found, the matching customer ONEID is identified; otherwise, a new ONEID is created.

[0054] 1.3 Identify customers based on user ID priority strategy: Customer information is generated during business operations. The customer's ONEID is identified according to the priority order, which is: customer document type, document number, name, mobile phone number, WeChat UNIONID, OPENID, device fingerprint ID, etc. (custom extensions are supported). All ONEID information that meets the conditions is identified.

[0055] 1.4 Customer selection based on user ID similarity strategy: The similarity ratio is calculated based on the combination of customer identification elements such as ID card, name, mobile phone, UNIONID, OPENID, and device fingerprint ID. Customer selection is supported based on business scenarios, similarity ratio, channels, salespersons, time, and other dimensions, and the customer ONEID is finally confirmed.

[0056] like Figure 4 As shown, the specific process of constructing a customer code from a customer's ONEID includes: The customer code validity period is set, and the customer ONEID and the customer code validity period constitute a unique customer identifier. Then, a dynamic QR code is generated from this unique customer identifier using the SM4 encryption algorithm.

[0057] The customer code has a dynamic validity period, which is generated by the server's precise timestamp, the business scenario's preset validity period, the SM4 encryption algorithm, a random factor, and the business identifier.

[0058] The application process of the customer code includes: In a QR code scanning scenario, the application process includes: After a user scans a QR code, identity authentication is performed; after authentication, customer identity is identified, and a customer ONEID is retrieved or generated; based on the customer ONEID, current customer behavior information is recorded. In the scenario of presenting a code, the application process includes: The client performs identity authentication, collects the information entered during authentication, and identifies the customer after authentication. Based on the identification result, it calls or generates the customer's ONEID and generates a corresponding customer code. After the staff scans the customer code, the background records the current customer behavior information.

[0059] During identity verification, the verification method is adjusted according to the business scenario. Business scenarios include event scenarios, basic service scenarios, and value-added service scenarios. In event scenarios, the first authentication plus the second authentication is used by default. In basic service scenarios, the first authentication is used by default. In value-added service scenarios, the first authentication plus the second authentication is used by default. The first authentication is a combination of ID number and facial recognition. The second authentication is SMS verification.

[0060] The customer code is equipped with an automatic refresh mechanism and an anti-screenshot mechanism. The automatic refresh mechanism refreshes the customer code automatically at preset intervals, and historical customer codes automatically expire. The anti-screenshot mechanism prevents screenshots of the customer code and prevents other scanning channels from recognizing the QR code content.

[0061] Technical core description: This solution integrates customer unique identification technology and customer QR code technology, combined with insurance business data and operations, and can be flexibly applied to business activities, basic services, and value-added service scenarios to improve customer operational efficiency.

[0062] The implementation and application principles of the technical components are as follows: 1. Customer Identity ONEID Recognition Steps 1.1 Define Standard Customer ONEID: First, define the standard ONEID format (2-digit business identifier + snowflake algorithm) to ensure that each user has a unique identifier. Define the ONEID data structure, including necessary user information, association relationships, change relationships, permissions, etc.

[0063] 1.2 Configure identity recognition strategy: Identify user identification elements, generate general mapping rules and store them in the cache REDIS; ONEID recognition follows the user ID recognition priority strategy and user ID high similarity strategy, matching the incoming user ID with the existing data layer by layer according to priority. If a match is found, the matching customer ONEID is identified; otherwise, a new ONEID is created.

[0064] 1.3 Identify customers based on user ID priority strategy: Customer information is generated during business operations. The customer's ONEID is identified according to the priority order, which is: customer document type, document number, name, mobile phone number, WeChat UNIONID, OPENID, device fingerprint ID, etc. (custom extensions are supported). All ONEID information that meets the conditions is identified.

[0065] 1.4 Customer selection based on user ID similarity strategy: The similarity ratio is calculated based on the combination of customer identification elements such as ID card, name, mobile phone, UNIONID, OPENID, and device fingerprint ID. Customer selection is supported based on business scenarios, similarity ratio, channels, salespersons, time, and other dimensions, and the customer ONEID is finally confirmed.

[0066] 2. Steps for generating and applying the Customer One-Code Pass component 2.1 Customer Code Component Generation: The customer code component includes a customer QR code component and a customer scan component, supporting generation via web page or API interface. The format is embedded into apps, mini-programs, and H5 pages. A dynamic QR code is generated using the national cryptographic SM4 encryption algorithm based on the customer's unique identifier (ONEID + validity period); a scan component is implemented based on JSQR.

[0067] 2.2 Customer Code Service Target (Customer Scope): Existing customers: Customers who already hold a Taiping Life Insurance policy can enjoy services such as policy management, claims processing, and renewal.

[0068] New customers: Customers who are contacting Taiping Life Insurance for the first time can complete the insurance application, participate in activities, and other operations by scanning a QR code.

[0069] Prospective customers: Potential customers who learn about the product and calculate premiums by scanning a QR code, and are gradually converted into formal customers.

[0070] Partners: Third-party institutions such as banks and medical institutions can access Taiping's service ecosystem by scanning a QR code.

[0071] 2.3 Security Management and Risk Control Technologies for Customer Codes: Customer code authentication scenarios: Marketing service scenarios, strong authentication + weak authentication; Basic service scenarios, strong authentication; Value-added service scenarios, strong authentication + weak authentication.

[0072] Strong authentication method: facial recognition + ID number authentication + SMS verification; Weak authentication method: SMS verification.

[0073] Customer code automatic refresh: The customer code is automatically refreshed every minute, and historical customer codes automatically expire.

[0074] Customer code anti-tampering: The customer code is generated based on dynamic validity period and SM4 encryption algorithm, which is not easy to crack or tamper with.

[0075] Customer code screenshot prevention: Customer codes do not allow screenshots, and other scanning tools cannot recognize the QR code content.

[0076] 2.4 Customer Code Application Steps: Supports two scanning methods: (customers actively scan codes provided by sales representatives and service personnel) and (customers provide their own customer codes, which sales representatives and service personnel then scan). It is applied to three major scenarios: marketing services, basic services, and value-added services. For example, in the marketing service scenario, when a customer registers to visit a Taiping Home activity, the system collects customer information, generates a customer ONEID, and produces a customer code. The customer can present this customer code to participate in any business activity such as Taiping Home, cell cryopreservation, and educational lectures. It is used for identity verification scenarios such as activity reservations, check-in verification, check-in assistance, and gift collection. In addition, the customer code supports extended query capabilities for customer identity, policy, and behavioral trajectory information.

[0077] In this method, the customer unified code solution integrates customer unique identification technology to generate a universal customer ONEID and QR code component. This meets the real-time identity verification needs of customer business scenarios such as operations, basic services, and value-added services, covering the entire customer journey's trajectory recording. The innovative value of this technology is mainly reflected in optimizing the customer experience process, improving customer operation efficiency, and expanding the customer ecosystem. The core advantages of the technology are as follows: 1. Unified Customer Identity Authentication: Enables omnichannel identity recognition through customer codes, supporting different authentication strengths for different scenarios.

[0078] 2. Full customer journey coverage: Achieve multi-scenario coverage of the customer journey, including three core business scenarios: marketing activities, basic services, and value-added services.

[0079] 3. Open ecosystem access: Supports insurance company customers to access third-party services by scanning the scenario codes of third-party institutions (such as airlines and hospitals).

[0080] Example 2 In this embodiment, a customer identification system with a unified code for insurance business is adopted, which includes a data layer, a service layer, and an application layer. The data layer is used for storing and caching existing data; The service layer integrates user ID recognition priority strategy, user ID similarity strategy, encryption algorithm and third-party integration capabilities to complete identity recognition service, customer code generation service and identity authentication service; it supports insurance company customers to access third-party services by scanning the scenario codes of third-party institutions (such as airlines and hospitals).

[0081] The application layer includes a customer QR code component and a scan component, which can be integrated into insurance apps, mini-programs, and H5 pages via page embedding or API interface to meet the customer code generation and scanning needs of online business scenarios.

[0082] The three-tier architecture has a clear division of labor: the data layer ensures the secure storage of existing data, the service layer centrally manages core strategies to reduce cross-system collaboration losses, and the application layer integrates and adapts to multiple terminals such as insurance apps and mini-programs, so that customers can use it without switching platforms, optimizing customer experience and comprehensively solving the three shortcomings of traditional decentralized systems.

[0083] Specifically, it includes a customer identity ONEID recognition module and a customer unified code management module: The customer identity ONEID recognition module includes a ONEID definition unit, which designs a unique format for a 2-digit business identifier and the Snowflake algorithm, and determines the data structure containing user information, association relationships, etc.; an identification strategy configuration unit, which identifies user elements, generates mapping rules and stores them in Redis, and formulates user ID priority and high similarity matching strategies; and an identity matching unit, which matches the input user ID with the existing data according to priority order and similarity logic, and outputs the existing ONEID or creates a new ONEID.

[0084] Customer One-Code Management Module: Includes a customer code generation unit, which generates dynamic QR codes based on ONEID and validity period using the national cryptographic standard SM4, develops a scan component, and supports embedding into APP, mini-program, and H5 platforms; a security management unit, which implements scenario-based strong and weak authentication, automatic customer code refresh every minute, anti-tampering, and anti-screenshot; and an application unit, which supports both scanning and being scanned, serving four types of customers: existing customers, new customers, prospective customers, and partners, and can be applied to activities, basic, and value-added service scenarios, synchronously recording customer behavior and supporting extended queries of information such as identity, policy, and behavior trajectory.

[0085] The specific implementation process of this system is the same as in Example 1.

[0086] This system integrates customer unique identification technology and customer QR code technology to achieve efficient identification of customer identities and secure application of customer codes in insurance business scenarios, thereby improving customer management efficiency.

[0087] The above description is merely a specific embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any person skilled in the art can easily conceive of various equivalent modifications or substitutions within the technical scope disclosed in the present invention, and these modifications or substitutions should all be covered within the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims.

Claims

1. A method for the identity recognition of a customer one code in the insurance business, characterized in that, The method is based on customer unique identity recognition technology to build customer ONEID, and based on customer two-dimensional code technology, customer ONEID is used to build customer code; The identity recognition method comprises the following steps: When the customer first accesses the business scene, the identity elements are recognized and collected, the general mapping rule is generated based on the identity elements and the customer ONEID, and is stored in the cache to form the inventory data; When the customer needs identity recognition in the business scene, the identity recognition process is executed: following the user ID recognition priority strategy and the user ID similarity strategy, the input identity elements are matched with the inventory data layer by layer according to the priority, if the matching is consistent, the matched customer ONEID is recognized, otherwise, a new ONEID is created.

2. The insurance business oriented customer one code identification method according to claim 1, wherein, The user ID recognition priority strategy comprises the following steps: Taking the relevance of the identity elements as the core sorting logic, the stronger the relevance, the higher the priority, a hierarchical identification link from the certificate number to the scene-related information is constructed; the certificate number is used as the first-level identification element, because it has official authority and uniqueness; the name, mobile phone number, cross-platform user unique identifier, scene user identifier and terminal association identifier are used as subsequent hierarchical elements; meanwhile, the elements can be customized and extended according to the business scene requirements, and the hierarchical level can be adjusted, the customer ONEID that meets the conditions in the inventory data is preliminarily screened out through layer-by-layer matching, and a candidate pool is formed.

3. The insurance business oriented customer one code identification method according to claim 2, wherein, The user ID similarity strategy comprises the following steps: For the candidate ONEID in the candidate pool, the multi-dimensional similarity is calculated based on the combination characteristics of the identity elements, and a dual judgment mechanism of element matching degree and scene adaptability is constructed; Firstly, the identity elements are quantitatively compared through the string similarity algorithm to generate a single-element similarity score; then, the comprehensive similarity proportion is calculated by combining the element combination weight; On this basis, the preset similarity proportion threshold is dynamically adjusted by fusing the business scene; The customer ONEID with the comprehensive similarity proportion higher than the preset similarity proportion threshold is selected from the candidate pool.

4. The insurance business oriented customer one code identification method according to claim 3, wherein, The preset similarity proportion threshold dynamically adjusted by fusing the business scene comprises the following steps: The higher the risk of the business scene, the higher the preset similarity proportion threshold; The higher the channel authority, the lower the preset similarity proportion threshold; The higher the association degree between the business staff and the customer, the lower the preset similarity proportion threshold; The closer the update time of the customer identity elements, the lower the preset similarity proportion threshold; The higher the historical handling frequency of the customer in the current business type, the lower the preset similarity proportion threshold.

5. The insurance business oriented customer one code identification method according to claim 1, wherein, The identity recognition process comprises the following steps: Whether the first identity element, the second identity element, the third identity element, the fourth identity element and the fifth identity element are contained in the input identity elements is sequentially judged, if none of them is contained, a new ONEID is created and returned; In addition to the first identity element, if a certain identity element is judged to be contained, the corresponding matching and matching detection are performed to obtain a matching result, at this time, it is judged whether there is a parameter with a higher priority than the parameter judged to be contained in the current input parameter, if not, the ONEID with the highest confidence in the matching result is returned; if so, it is judged whether there is a parameter with a higher priority than the parameter judged to be contained in the corresponding identity element of the current matching result, if so, a new ONEID is created and returned; otherwise, the ONEID with the highest confidence in the matching result is returned. When the first identity element is contained in the input parameter, the three-element level matching process and matching detection of the first identity element are directly performed to obtain a matching result, and finally the ONEID with the highest confidence in the matching result is returned. The priority of the first identity element, the second identity element, the third identity element, the fourth identity element and the fifth identity element decreases in turn.

6. The insurance business oriented customer one code identification method according to claim 1, wherein, The specific process of constructing the customer code from the customer ONEID includes: setting a customer code validity period, constructing a customer unique identifier from the customer ONEID and the customer code validity period, and generating a dynamic two-dimensional code from the customer unique identifier through an SM4 encryption algorithm; The customer code validity period is a dynamic validity period, and the dynamic validity period is generated by a service end precise timestamp, a business scenario preset validity time length, an SM4 encryption algorithm, a random factor and a business identifier.

7. The insurance business oriented customer one code identification method according to claim 6, wherein, The application process of the customer code includes: In the code scanning scenario, the application process includes: The user end performs a code scanning behavior, performs identity authentication, performs customer identity recognition after authentication, calls or generates a customer ONEID, and records current customer behavior information based on the customer ONEID; In the code presenting scenario, the application process includes: The user end performs identity authentication, collects information input during authentication, performs customer identity recognition after authentication, calls or generates a customer ONEID based on the identity recognition result, and generates a corresponding customer code, and the staff scans the customer code, and the background records current customer behavior information.

8. The insurance business oriented customer one code identity recognition method according to claim 7, characterized in that, The identity authentication is adjusted according to a business scenario; the business scenario includes an activity scenario, a basic service scenario and a value-added service scenario; The first authentication plus the second authentication is used by default in the activity scenario, the first authentication is used by default in the basic service scenario, and the first authentication plus the second authentication is used by default in the value-added service scenario; The first authentication is a certificate number combined with a face authentication; and the second authentication is an SMS verification.

9. The insurance business oriented customer one code identity recognition method according to claim 7, characterized in that, The customer code is provided with an automatic refreshing mechanism and a screenshot prevention mechanism; the automatic refreshing mechanism is that the customer code is automatically refreshed every predetermined time length, and the historical customer code is automatically invalidated; and the screenshot prevention mechanism is that the customer code is not allowed to be screenshot, and the two-dimensional code content cannot be recognized by other code scanning channels except the matching code scanning channel.

10. A customer one-card identification system for insurance business, characterized in that, The system applies the customer one-code identity recognition method for insurance business as claimed in any one of claims 1-9, and the system includes a data layer, a service layer and an application layer; The data layer is used for storing and caching inventory data. The service layer integrates user ID recognition priority strategy, user ID similarity strategy, encryption algorithm and third-party capability, and is used for completing identity recognition service, customer code generation service and identity authentication service. The application layer includes a customer two-dimensional code component and a scan component, supports integration into an insurance APP, a small program and an H5 page in a form of page embedding or an API interface, and meets customer code generation and code scanning requirements of an online business scene.

Images