A rare character processing method and device, a storage medium and an electronic device

Abstract

The specification discloses a rare character processing method and device, a storage medium and an electronic device, wherein the method comprises the following steps: acquiring a rare character user name and a certificate sequence input by a user terminal for an information checking service; performing rare character code conversion processing on the rare character user name to obtain a rare character name list; performing user information checking based on the rare character name list and the certificate sequence through the information checking service to obtain an information checking result.

Description

Technical Field

[0001] This specification relates to the field of computer technology, and in particular to a method, apparatus, storage medium, and electronic device for processing rare characters. Background Technology

[0002] With the development of computer technology, electronic devices are gradually able to provide users with intelligent services, assisting users to complete tasks quickly and accurately. However, in daily life, there are still many rare characters, variant characters, and local special characters that are still in use, and users have a need to use these rare characters. Summary of the Invention

[0003] This specification provides a method, apparatus, storage medium, and electronic device for processing uncommon characters. The technical solution is as follows:

[0004] Firstly, this specification provides a method for processing uncommon characters, the method including:

[0005] Retrieve the username and document sequence containing uncommon characters entered for the information verification service;

[0006] The uncommon character usernames are processed by uncommon character encoding to obtain a list of uncommon character names corresponding to the uncommon character usernames;

[0007] Based on the list of rare character names and the document sequence, user information is verified through the information verification service to obtain the information verification result.

[0008] Secondly, this specification provides a device for processing uncommon characters, the device comprising:

[0009] The information acquisition module is used to acquire the uncommon character username and document sequence entered by the user on the client side for the information verification service;

[0010] The uncommon character processing module is used to perform uncommon character encoding processing on the uncommon character user names to obtain a list of uncommon character names corresponding to the uncommon character user names;

[0011] The information verification module is used to verify user information through the information verification service based on the list of rare character names and the document sequence, and obtain the information verification result.

[0012] Thirdly, this specification provides a computer storage medium storing a plurality of instructions adapted for loading by a processor and executing the above-described method steps.

[0013] Fourthly, this specification provides an electronic device that may include: a processor and a memory; wherein the memory stores a computer program adapted to be loaded by the processor and to execute the above-described method steps.

[0014] The beneficial effects of the technical solutions provided in some embodiments of this specification include at least the following:

[0015] In one or more embodiments of this specification, the electronic device obtains the uncommon character username and document sequence entered by the user for the information verification service. By performing uncommon character encoding processing on the uncommon character username, a list of uncommon character names corresponding to the uncommon character username is obtained. One or more uncommon character names in the list of uncommon character names are highly likely to be accurately identified by the information verification service using uncommon character encoding. This avoids the situation where the information verification cannot be combined with the document sequence due to the inability to recognize uncommon characters. Subsequently, user information can be verified through the information verification service based on the list of uncommon character names and the document sequence. The entire uncommon character processing process reduces manual operation by the user, ensures the normal operation of the information verification service, improves the robustness of the information verification service, and facilitates the use of uncommon character names by users in information verification scenarios. Attached Figure Description

[0016] To more clearly illustrate the technical solutions in this specification or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this specification. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0017] Figure 1 This is a schematic diagram of a rare character processing system provided in this manual;

[0018] Figure 2 This is a flowchart illustrating a method for handling uncommon characters provided in this manual;

[0019] Figure 3 This is a flowchart illustrating another method for handling uncommon characters provided in this manual;

[0020] Figure 4 This is a schematic diagram of the structure of a rare character processing device provided in this manual;

[0021] Figure 5 This is a structural diagram of a rare character processing module provided in this manual;

[0022] Figure 6 This is a schematic diagram of the structure of a character processing unit provided in this specification;

[0023] Figure 7 This is a schematic diagram of the structure of an electronic device provided in this specification;

[0024] Figure 8 This is a schematic diagram of the operating system and user space provided in this manual;

[0025] Figure 9 yes Figure 8 Architecture diagram of the Android operating system in China;

[0026] Figure 10 yes Figure 8 Architecture diagram of the iOS operating system. Detailed Implementation

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

[0028] In the description of this specification, it should be understood that the terms "first," "second," etc., are used for descriptive purposes only and should not be construed as indicating or implying relative importance. In the description of this specification, it should be noted that, unless otherwise expressly specified and limited, "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or device that includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to these processes, methods, products, or devices. Those skilled in the art can understand the specific meaning of the above terms in this specification based on the specific circumstances. Furthermore, in the description of this specification, unless otherwise stated, "multiple" means two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, and B alone. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship.

[0029] In related technologies, these rare characters, variant characters, and local unique characters are not fully included in the common character encoding set. In scenarios such as information verification, some information verification services usually only support character recognition within the range of common character encoding sets. Even if the electronic device used by the user supports the recognition of rare characters, the information verification service may fail if the electronic device directly requests the information verification service because it cannot recognize rare usernames or the rare encoding method supported by the electronic device is inconsistent with the rare encoding method supported by the information verification service.

[0030] The present specification will now be described in detail with reference to specific embodiments.

[0031] Please see Figure 1 This is a schematic diagram illustrating a scenario for a system for processing uncommon characters provided in this manual. Figure 1 As shown, the rare character processing system may include at least a client cluster and a service platform 100.

[0032] The client cluster may include at least one client, such as Figure 1 As shown, it specifically includes client 1 corresponding to user 1, client 2 corresponding to user 2, ..., client n corresponding to user n, where n is an integer greater than 0.

[0033] Each client in a client cluster can be an electronic device with communication capabilities, including but not limited to: wearable devices, handheld devices, personal computers, tablets, in-vehicle devices, smartphones, computing devices, or other processing devices connected to a wireless modem. Electronic devices may have different names in different networks, such as: user equipment, access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication equipment, user agent or user device, cellular phone, cordless phone, personal digital assistant (PDA), and electronic devices in 5G networks or future evolved networks.

[0034] The service platform 100 can be a standalone server device, such as a rack-mount, blade, tower, or cabinet-type server device, or a workstation, mainframe, or other hardware device with strong computing power; or it can be a server cluster composed of multiple servers. The servers in the service cluster can be composed in a symmetrical manner, wherein each server is functionally and hierarchically equivalent in the transaction chain, and each server can provide services independently. The independent provision of services can be understood as not requiring the assistance of other servers.

[0035] In one or more embodiments of this specification, the service platform 100 can establish a communication connection with at least one user terminal in the user terminal cluster. Based on this communication connection, data interaction is completed during the processing of rare characters. For example, the service platform 100 can provide one or more types of information verification services, such as identity verification services, real-name authentication services, etc. Users can input rare character usernames and document sequences into the information verification services provided by the service platform through their user terminals. The rare character encoding methods supported by the user terminals may be different from those required by the information verification services. After obtaining the rare character usernames and document sequences input by the user, the user terminals can perform rare character transcoding processing on the rare character usernames to obtain a list of rare character names corresponding to the rare character usernames that the information verification services can recognize. The list of rare character names contains one or more rare transcoded names after rare character transcoding processing.

[0036] Based on the list of rare character names and the document sequence, user information is verified through the information verification service to obtain the information verification result.

[0037] It should be noted that the service platform 100 establishes a communication connection with at least one client in the client cluster via a network for interactive communication. This network can be a wireless network or a wired network. Wireless networks include, but are not limited to, cellular networks, wireless LANs, infrared networks, or Bluetooth networks. Wired networks include, but are not limited to, Ethernet, universal serial bus (USB), or controller area networks. In one or more embodiments of the specification, technologies and / or formats including Hyper Text Markup Language (HTML), Extensible Markup Language (XML), etc., are used to represent data exchanged over the network (such as target compressed packets). Furthermore, conventional encryption technologies such as Secure Socket Layer (SSL), Transport Layer Security (TLS), Virtual Private Network (VPN), and Internet Protocol Security (IPsec) can be used to encrypt all or some links. In other embodiments, customized and / or dedicated data communication technologies can be used to replace or supplement the aforementioned data communication technologies.

[0038] The rare character processing system embodiments provided in this specification and the rare character processing methods described in one or more embodiments belong to the same concept. The execution entity corresponding to the rare character processing method involved in one or more embodiments of this specification can be an electronic device, which can be the aforementioned service platform 100; the execution entity corresponding to the rare character processing method involved in one or more embodiments of this specification can also be the electronic device corresponding to the client (in some embodiments, it can also be referred to as the user terminal's electronic device), specifically determined based on the actual application environment. The implementation process of the rare character processing system embodiments can be detailed in the following method embodiments, and will not be repeated here.

[0039] based on Figure 1 The following is a detailed description of the method for handling rare characters provided in one or more embodiments of this specification, as illustrated in the scene diagram.

[0040] Please see Figure 2 This document provides a flowchart illustrating a method for processing uncommon characters, one or more embodiments of which can be implemented using a computer program and run on an uncommon character processing device based on the von Neumann architecture. The computer program can be integrated into an application or run as a standalone utility application. The uncommon character processing device can be an electronic device.

[0041] Specifically, the methods for handling rare characters include:

[0042] S102: Obtain the uncommon character username and document sequence entered for the information verification service;

[0043] The aforementioned usernames containing uncommon characters can be understood as usernames that contain uncommon characters, typically composed of both common and uncommon characters;

[0044] The document sequence is the serial number information in the user's document information, which can be used to prove the user's identity during information verification, such as serial number, serial code, etc.

[0045] Indicatively, the document sequence may be a combination of one or more of the following: an identity code sequence, a driver's license number sequence, an academic certificate number sequence, a graduation number sequence, etc., used to prove the user's identity during information verification.

[0046] Understandably, electronic devices can provide rare character input components so that users can input rare character usernames through these components. In other words, if a user's username contains rare characters, the electronic device can support the input, display, and other functions of the rare character username.

[0047] Furthermore, the electronic device can support the current target user to directly input their username using uncommon characters. Combined with the document sequence entered by the target user, if the target user has an information verification need, the device can provide the target user with an uncommon character input component. The target user can then enter their username using uncommon characters and the document sequence on the electronic device. Based on the username and document sequence, the user can request an information verification service to conduct information verification.

[0048] Indicatively, if a target user has an information verification need, the target user can input a rare character username through the rare character input component of an electronic device, and simultaneously input an identity code sequence used to prove the user's identity as a document sequence, to request an information verification service based on the rare character username and the identity code sequence. The electronic device can execute the rare character processing method of one or more embodiments of this specification to perform rare character transcoding processing on the rare character username to obtain a list of rare character names, and perform user information verification through the information verification service based on the rare character name list and the identity code sequence to obtain the information verification result;

[0049] Optionally, the rare character input component may be different from the common character input component. Common character input components usually cannot directly support rare character input, and the common character library corresponding to the common character input component does not cover rare characters. In one or more embodiments of this specification, the rare character input component can be understood as a special input component for rare characters. The rare character library managed by the rare character input component can usually cover rare characters that do not exist in the common character library.

[0050] Optionally, the rare character input component can rely on a common character library to encode rare characters by using common characters as the basis for the common character set, thereby supporting users to directly input rare characters. The rare character encoding method includes, but is not limited to, one or more of the following: "all uppercase pinyin" encoding method, "first letter uppercase pinyin" encoding method, "lowercase pinyin" encoding method, "pinyin with full-angle brackets" encoding method, "pinyin with half-angle brackets" encoding method, "pinyin with square brackets" encoding method, "pinyin with / without tone" encoding method, "one character split into multiple characters" encoding method, etc. For example, when a user intends to input a rare character in a user's name, the rare character input component of the electronic device can be triggered to input the rare character using the "one character split into multiple characters" method, thereby completing the input of the rare character user's name.

[0051] It should be noted that the rare character input component supports at least one of the two methods mentioned above.

[0052] In illustrative purposes, the electronic device may be a user terminal used by the target user;

[0053] In illustrative terms, the electronic device can be a service platform that provides a rare character input component to user terminals used by several users. This rare character input component is used in conjunction with a multi-encoding rare character library as described in some embodiments to provide the target user with the ability to input rare characters of at least one rare encoding type. Typically, the target user can input at least a rare character username using the rare character input component on their user terminal. The user can select the desired rare encoding type from one or more rare encoding types supported by the rare character input component to input the rare character username. The service platform can obtain the rare character username and / or the input document sequence entered by the target user when the user terminal receives the rare character username input through the rare character input component (e.g., the user terminal can send the rare character username / document sequence to the service platform).

[0054] S104: Perform rare character encoding processing on the rare character usernames to obtain a list of rare character names corresponding to the rare character usernames;

[0055] In some implementation scenarios, rare characters (symbols) mainly refer to characters that are not within the scope of commonly used character encoding sets. For example, characters that are not within the scope of the commonly used GBK character (encoding) set (1995) can be regarded as rare characters (symbols). Usually, common devices and corresponding information verification services support the GBK character (encoding) set.

[0056] Understandably, some information verification services typically only support character recognition within the range of commonly used character encoding sets. Even if electronic devices support the recognition of uncommon characters, directly requesting information verification services by electronic devices may fail to recognize uncommon usernames or may result in the inability to recognize uncommon characters due to inconsistencies between the uncommon encoding methods supported by the electronic devices and those supported by the information verification services. Consequently, they may be unable to combine the document sequence with the information verification process.

[0057] In some implementation scenarios, some servers providing information verification services use uncommon character recognition methods that fit (or combine) uncommon character encoding methods based on common character sets. These uncommon character encoding methods encode uncommon characters by using common characters as the basis for encoding uncommon characters. The information verification service server can then recognize uncommon characters from the encoded sequence. Uncommon character encoding methods include, but are not limited to, "all-caps Pinyin" encoding, "first-letter capitalized Pinyin" encoding, "lowercase Pinyin" encoding, "Pinyin with full-angle brackets" encoding, "Pinyin with half-angle brackets" encoding, "Pinyin with square brackets" encoding, "Pinyin with / without tone marks" encoding, "one character split into two" encoding, etc.

[0058] In one or more embodiments of this specification, the electronic device supports users directly inputting uncommon character usernames, which is generally more direct and efficient than instructing users to use the aforementioned uncommon encoding methods. By adopting the uncommon character processing method described in this specification, after supporting users to directly input uncommon character usernames, it is not necessary to directly request the information verification service to process the uncommon character usernames. Usually, the server corresponding to the information verification service cannot directly recognize uncommon character usernames. The electronic device can use automatic transcoding to convert the original uncommon character usernames into uncommon character names corresponding to the aforementioned "(uncommon encoding method based on common character sets and uncommon characters) uncommon character encoding method". There can be one or more common uncommon character encoding methods, thereby generating a list of uncommon character names. One or more uncommon character names in the list of uncommon character names are highly likely to be accurately identified by the information verification service using the uncommon character encoding method, thus avoiding the inability to recognize uncommon characters and thus preventing the inability to combine them with the document sequence for subsequent information verification.

[0059] Optionally, the rare character transcoding process for the rare character username can be performed by querying the target rare character in the rare character username, then using at least one rare character encoding method as the rare character transcoding method to transcode the target rare character, obtaining the transcoded rare character, and updating the original rare character username to obtain the rare character name. One or more rare character names constitute a rare character name list.

[0060] In one or more embodiments of this specification, the rare character encoding method used for rare character transcoding of the user name is different from the original rare character encoding method corresponding to the rare character user name.

[0061] S106: Based on the list of rare character names and the document sequence, verify user information through the information verification service to obtain the information verification result.

[0062] The information verification service can be a real-name information verification and authentication service, a financial information verification and authentication service, a shopping information verification and authentication service, a resource information verification and authentication service, etc. The information verification service is provided by the corresponding server. For example, the server corresponding to the information verification service can be the device corresponding to a bank service institution that provides financial information verification; the server corresponding to the information verification service can be the device corresponding to a resource service institution that provides resource information verification (such as gas resources, electricity resources, water resources, etc.); the server corresponding to the information verification service can be the device corresponding to a transportation service institution that provides transportation information verification, and so on.

[0063] To illustrate, taking the device corresponding to the service provider offering real-name information verification and authentication services as an example, the information verification service can provide real-name information verification and authentication capabilities. The target user of the electronic device can input a username with rare characters and a document sequence for the information verification service. The electronic device will then automatically convert the username with rare characters to obtain a list of rare character names. The electronic device will then request the information verification service to perform real-name information verification and authentication based on one or more rare character names in the list of rare character names and the document sequence, using a set real-name information authentication mechanism to determine whether the verification is successful and thus obtain the information verification result. For example, the information verification service can use a set real-name information authentication mechanism to verify the authenticity and legality of the information based on one or more rare character names in the list of rare character names and the document sequence.

[0064] Indicatively, an electronic device can select one rare character from a list of rare character names and combine it with a document sequence to perform multiple verifications of user information through the information verification service to obtain the current information verification result. This can be understood as the electronic device requesting user information verification from the information verification service one rare character name and one document sequence from a list of rare character names to obtain the information verification result.

[0065] In one feasible implementation, after the electronic device obtains the uncommon character username and document sequence input for the information verification service, before performing the uncommon character transcoding process on the uncommon character username, it verifies the user information based on the uncommon character username and the document sequence through the information verification service to obtain the information verification result.

[0066] For example, the information verification result includes two types: information verification failure type and information verification success type. The electronic device determines that the information verification result is either information verification failure type or information verification success type.

[0067] Furthermore, if the information verification result is an information verification failure type, the electronic device performs the step of performing rare character transcoding on the rare character user name to obtain a list of rare character names corresponding to the rare character user name;

[0068] Optionally, if the information verification result is an information verification failure type, that is, the information verification service fails to verify, the electronic device can call the rare character conversion service to perform rare character conversion processing on the rare character username.

[0069] Furthermore, if the information verification result is of the information verification success type, then the information verification result of the information verification success type is output.

[0070] Understandably, based on the above implementation method, in the event of information verification failure, the system can switch to uncommon character processing for automatic uncommon character transcoding, which can realize online verification of one character with multiple codes, improve the intelligence of uncommon character processing, and ensure the effectiveness of information verification.

[0071] Optionally, if the electronic device is a client used by the target user, the client can perform a step of uncommon character transcoding of the uncommon character username to obtain a list of uncommon character names corresponding to the uncommon character username. Then, the client sends the list of uncommon character names to the service platform to instruct the service platform to verify the user information through the information verification service based on the list of uncommon character names and the document sequence, thereby obtaining the information verification result.

[0072] Optionally, if the electronic device is a service platform, the service platform may execute the uncommon character processing method of one or more embodiments of this specification and send the information verification result to the user terminal.

[0073] In one or more embodiments of this specification, the electronic device obtains the uncommon character username and document sequence entered by the user for the information verification service. By performing uncommon character encoding processing on the uncommon character username, a list of uncommon character names corresponding to the uncommon character username is obtained. One or more uncommon character names in the list of uncommon character names are highly likely to be accurately identified by the information verification service using uncommon character encoding. This avoids the situation where the information verification cannot be combined with the document sequence due to the inability to recognize uncommon characters. Subsequently, user information can be verified through the information verification service based on the list of uncommon character names and the document sequence. The entire uncommon character processing process reduces manual operation by the user, ensures the normal operation of the information verification service, improves the robustness of the information verification service, and facilitates the use of uncommon character names by users in information verification scenarios.

[0074] Please see Figure 3 , Figure 3 This is a flowchart illustrating another embodiment of a method for processing rare characters proposed in one or more embodiments of this specification. Specifically:

[0075] S202: Obtain the username and document sequence containing uncommon characters entered for the information verification service;

[0076] For details, please refer to the method steps of one or more embodiments of this specification, which will not be repeated here.

[0077] S204: Obtain the target rare character in the rare character username, and determine at least one rare character encoding type for the target rare character;

[0078] The username containing rare characters is usually composed of common characters and rare characters. The rare characters in the username are also the target rare characters.

[0079] The rare character encoding type is used to indicate that the target rare character will be encoded according to the rare character encoding method corresponding to the rare character encoding type.

[0080] Optionally, the electronic device can pre-maintain a multi-encoding rare character library, which consists of several rare character objects, multiple rare encoding methods corresponding to each rare character object, and rare characters of the rare character object under each rare encoding method;

[0081] This is illustrated by pre-obtaining the uncommon encoding methods supported by several servers (providing corresponding services) in a real-world environment. Then, for several uncommon character objects, the uncommon characters under each uncommon encoding method are determined, thus constructing a multi-encoding uncommon character library. This multi-encoding uncommon character library is then updated and maintained. The uncommon characters corresponding to the same uncommon character object differ under different uncommon encoding methods. Using this multi-encoding uncommon character library, uncommon character processing can be quickly achieved, improving transcoding efficiency.

[0082] In one feasible implementation, the electronic device can determine the native rare character encoding type corresponding to the rare character username, query at least one reference rare character encoding type corresponding to the target rare character based on the multi-encoding rare character library and the native rare character encoding type, and then determine at least one rare character transcoding type corresponding to the target rare character based on the at least one reference rare character encoding type.

[0083] As an illustration, in a multi-encoding rare character library, you can query the reference rare character encoding type associated with the rare character object corresponding to the target rare character. Assuming there are n rare character encoding types associated with the rare character object corresponding to the target rare character in the multi-encoding rare character library, the reference rare character encoding type is the remaining rare character encoding type other than the original rare character encoding type among the n rare character encoding types.

[0084] That is, the electronic device can determine at least one reference rare character encoding type other than the original rare character encoding type based on a multi-encoding rare character library;

[0085] In one feasible implementation, the default uncommon encoding type supported by the information verification service can also be considered. The default uncommon encoding type is the uncommon encoding type supported by the server corresponding to the information verification service. It can be understood that usually only uncommon characters encoded by the default uncommon encoding type can be normally recognized by the information verification service.

[0086] Indicatively, at least one default uncommon encoding type corresponding to the information verification service can be obtained, and at least one reference uncommon encoding type corresponding to the target uncommon character, other than the original uncommon encoding type and matching the default uncommon encoding type, can be determined based on the multi-encoding uncommon character library.

[0087] For example, uncommon encoding methods that are compatible with the default uncommon encoding type can be included in the selection of reference uncommon encoding types. Uncommon encoding methods that are compatible with the default uncommon encoding type can be understood as encoding using a compatible uncommon encoding method that can be recognized by the uncommon character recognition mechanism for the default uncommon encoding type in the information verification service.

[0088] For example, the selection of a reference rare encoding type can include rare encoding methods that are the same as the default rare encoding type.

[0089] Furthermore, after querying at least one reference rare encoding type corresponding to the target rare character based on the multi-encoding rare character library and the original rare encoding type, the electronic device then determines at least one rare transcoding type corresponding to the target rare character based on at least one reference rare encoding type, that is, determines the rare transcoding type from at least one reference rare encoding type, thereby obtaining the rare character under the corresponding rare transcoding type from the multi-encoding rare character library.

[0090] In one feasible implementation, the electronic device performing the step of determining at least one rare encoding type corresponding to the target rare character based on the at least one reference rare encoding type may be: the electronic device using all the reference rare encoding types as at least one rare encoding type corresponding to the target rare character;

[0091] In one feasible implementation, when there are multiple reference rare coding types, the electronic device can comprehensively evaluate the reference rare coding type by combining the historical verification processing dimension and / or coding error dimension after each adoption of the reference rare coding type for rare transcoding.

[0092] Specifically, the electronic device performing the step of determining at least one rare transcoding type corresponding to the target rare character based on the at least one reference rare encoding type can be as follows: determining at least one rare transcoding type corresponding to the target rare character based on the at least one reference rare encoding type can be as follows: obtaining historical verification record parameters corresponding to each of the reference rare encoding types for the information verification service and / or the encoding error coefficient for the rare character user name, and determining at least one rare transcoding type corresponding to the target rare character based on the historical verification record parameters and / or the encoding error coefficient.

[0093] Optionally, the electronic device can obtain historical verification record parameters corresponding to each of the reference uncommon encoding types for the information verification service, and filter multiple reference uncommon encoding types based on the historical verification record parameters to select the better uncommon transcoding type;

[0094] Indicatively, historical verification record parameters can be parameters that reflect the verification processing level of information verification services after being encoded using a certain reference uncommon coding type. Historical verification record parameters include, but are not limited to, fitting one or more of the following reference numbers: historical verification pass rate parameter that reflects the verification processing pass rate, historical verification feedback time parameter that reflects the verification processing efficiency, and historical verification consumption rate that reflects the verification processing resource consumption.

[0095] For example, the historical verification recommendation value can be quantified from the historical verification dimension for each reference uncommon coding type based on the historical verification record parameters. When there are one or more historical verification record parameters, the value can be calculated as the historical verification recommendation value by weighted fitting of the values ​​of the historical verification record parameters. That is, a weight value is set for each type of verification record parameter, and the sum of the products of the historical verification record parameter and the weight value is calculated as the historical verification recommendation value.

[0096] Optionally, the electronic device can obtain the encoding error coefficients corresponding to each of the reference rare encoding types for the information verification service, and filter multiple reference rare encoding types based on the encoding error coefficients to select the better rare transcoding type;

[0097] As an illustration, the encoding error coefficient can be an error coefficient set by experts based on actual application conditions using an expert-side service for each reference uncommon encoding type; generally, the lower the value of the error coefficient, the better the transcoding effect of the uncommon transcoding type.

[0098] Optionally, the electronic device can obtain the encoding error coefficient and historical verification record parameters corresponding to each of the reference rare encoding types for the information verification service, and filter multiple reference rare encoding types based on the two dimensions of encoding error coefficient and historical verification record parameters to select the better rare transcoding type;

[0099] As an illustration, error filtering thresholds and historical verification thresholds can be set for the encoding error coefficient and historical verification record parameters respectively. Reference rare encoding types with encoding error coefficients higher than the error filtering thresholds and reference rare encoding types with historical verification record parameters lower than / higher than the historical verification thresholds can be filtered out. The remaining reference rare encoding types are used as the better rare transcoding types.

[0100] In a schematic manner, a first weight value and a second weight value can be set for the encoding error coefficient and the historical verification record parameter, respectively. The first product of the encoding error coefficient and the first weight value, and the second product of the historical verification record parameter and the second weight value are calculated. These two products are then used as quantitative recommendation parameters for reference rare encoding types. The recommendation priority of the reference rare encoding types is determined according to the order of these quantitative recommendation parameters. Based on the recommendation priority of the reference rare encoding types, at least one rare transcoding type corresponding to the target rare character is determined (e.g., selecting a specified number of reference rare encoding types with high priority as rare transcoding types). That is, based on the historical verification record parameter and the encoding error coefficient, the recommendation priority of each of the reference rare encoding types is determined, and based on the recommendation priority of the reference rare encoding types, at least one rare transcoding type corresponding to the target rare character is determined.

[0101] Understandably, by combining the historical verification processing dimensions and / or encoding error dimensions after adopting reference rare encoding types for rare character transcoding in previous times, the effectiveness of various reference encoding types and corresponding transcoding methods before automatic transcoding has been quantified, the rare character processing process has been optimized, and the standardization and intelligence of rare character processing have been improved. It is possible to select the rare transcoding type and corresponding transcoding method that is more suitable for information transcoding services for rare character transcoding.

[0102] S206: Obtain the rare encoded characters of each of the rare transcoding types corresponding to the target rare character;

[0103] As an illustration, an electronic device can search for rare encoded characters of various rare encoding types corresponding to a target rare character in a multi-encoding rare character library.

[0104] In one feasible implementation, when a target user inputs a rare character username and document sequence on the user terminal, the rare character input component or an information verification interface for input is typically triggered first. The target user initiates an information input request for the information verification service through a triggering mechanism. For example, the target user can typically select an information verification service first, and then input the rare character username and document sequence. After detecting the information input request from the target user, the electronic device can update the multi-encoding rare character library stored locally on the user terminal to obtain the updated multi-encoding rare character library. By updating the multi-encoding rare character library, it is possible to at least ensure that the user can accurately and conveniently input the rare character username, and in one or more embodiments, to ensure accurate transcoding of rare character processing.

[0105] Optionally, the electronic device can be a service platform. After detecting the information input request from the target user on the user terminal, the service platform can also perform a character library update process on the multi-encoding rare character library stored locally on the user terminal to obtain the updated multi-encoding rare character library.

[0106] Indicatively, the service platform can determine the font version information of the multi-encoding uncommon font library stored locally on the user's end, detect the updated version of the multi-encoding uncommon font library based on the font version information, obtain the font update file corresponding to the updated version, and perform font update processing on the multi-encoding uncommon font library stored locally on the user's end based on the font update file.

[0107] Optionally, the electronic device can be a user terminal. After detecting the information input request from the target user on the user terminal, the user terminal or service platform can actively request to update the multi-encoded rare character library stored locally on the user terminal to obtain the updated multi-encoded rare character library.

[0108] In a schematic manner, the user client can determine the font version information of the multi-encoding uncommon font library stored locally on the user client. By sending the font version information to the service platform, the user client actively requests the service platform to detect the updated version of the multi-encoding uncommon font library based on the font version information, thereby obtaining the font update file corresponding to the updated version. The service platform then sends the font update file to the user client, and the user client updates the multi-encoding uncommon font library stored locally on the user client based on the font update file.

[0109] As an illustration, the electronic device may perform character update processing on a multi-encoding rare character library as follows: The electronic device (such as a service platform) obtains the saved character library version information of the multi-encoding rare character library, then detects the updated version of the multi-encoding rare character library based on the character library version information, obtains the character library update file corresponding to the updated version, and performs character update processing on the multi-encoding rare character library based on the character library update file.

[0110] Furthermore, the multi-encoding font library can be pre-collected and organized by the font library maintenance terminal to complete the update and maintenance process of the multi-encoding font library. When the multi-encoding font library needs to be updated online, the font library maintenance terminal can use a script to process the multi-encoding font library offline into JSON format, forming an offline multi-encoding font library, which is stored in a CDN (Content Delivery Network). The multi-encoding font library can carry font files of rare characters. Then, the font library address and font file address of the offline multi-encoding font library are updated in the version record table that records the font library version information.

[0111] Indicatively, the system can obtain the version information of the saved multi-encoding rare character set, and determine whether a character set update is needed by detecting the version information. If a character set update is needed, the system queries the version record table for the character set address and font file address of the multi-encoding character set to be updated. Then, based on the character set address and font file address, the system retrieves the offline multi-encoding character set to update the original multi-encoding character set data. Furthermore, once the character set data update is complete, an update completion message can be output. Then, the user can input the rare character username and document sequence for the information verification service on the user terminal. At this time, the electronic device can obtain the rare character username and document sequence input by the current target user for the information verification service, and then execute the rare character processing method of one or more embodiments of this specification.

[0112] S208: Perform rare character transcoding processing on the rare character username based on the rare encoded characters of each of the rare transcoding types to obtain at least one rare transcoded name, and generate a list of rare character names containing the rare transcoded names.

[0113] As an illustration, the electronic device performs transcoding update processing on the target rare characters in the rare character username based on the rare encoded characters of each of the rare encoding types, and can obtain at least one rare transcoded name.

[0114] S210: Based on the list of rare character names and the document sequence, the user information is verified through the information verification service to obtain the information verification result.

[0115] For details, please refer to the method steps in other embodiments of this specification, which will not be repeated here.

[0116] In one or more embodiments of this specification, the electronic device obtains the uncommon character username and document sequence entered by the user for the information verification service. By performing uncommon character encoding processing on the uncommon character username, a list of uncommon character names corresponding to the uncommon character username is obtained. One or more uncommon character names in the list of uncommon character names are highly likely to be accurately identified by the information verification service using uncommon character encoding. This avoids the situation where the information verification cannot be combined with the document sequence due to the inability to recognize uncommon characters. Subsequently, user information can be verified through the information verification service based on the list of uncommon character names and the document sequence. The entire uncommon character processing process reduces manual operation by the user, ensures the normal operation of the information verification service, improves the robustness of the information verification service, and facilitates the use of uncommon character names by users in information verification scenarios.

[0117] The following will combine Figure 4 This manual provides a detailed introduction to the uncommon character processing device. It should be noted that... Figure 4The uncommon character processing device shown is used to execute this instruction manual. Figures 1-3 The methods of the embodiments shown are illustrated only in connection with this specification for ease of explanation. For specific technical details not disclosed, please refer to this specification. Figures 1-3 The example shown.

[0118] Please see Figure 4 This diagram illustrates the structure of the uncommon character processing device described in this specification. The uncommon character processing device 1 can be implemented as all or part of a user terminal through software, hardware, or a combination of both. According to some embodiments, the uncommon character processing device 1 includes an information acquisition module 11, an uncommon character processing module 12, and an information verification module 13, specifically used for:

[0119] Information acquisition module 11 is used to acquire the uncommon character username and document sequence entered by the user terminal for the information verification service;

[0120] The uncommon character processing module 12 is used to perform uncommon character encoding processing on the uncommon character user name to obtain a list of uncommon character names corresponding to the uncommon character user name;

[0121] The information verification module 13 is used to verify user information through the information verification service based on the list of rare character names and the document sequence, and obtain the information verification result.

[0122] Optional, such as Figure 5 As shown, the uncommon character processing module 12 includes:

[0123] The character processing unit 121 is used to obtain the target rare character in the rare character username and determine at least one rare character encoding type for the target rare character;

[0124] Character transcoding unit 122 is used to acquire rare encoded characters of each rare transcoding type corresponding to the target rare character;

[0125] The character transcoding unit 122 is further configured to perform rare character transcoding processing on the rare character username based on the rare encoded characters of each rare transcoding type, to obtain at least one rare transcoded name, and generate a list of rare character names containing the rare transcoded names.

[0126] Optional, such as Figure 6 As shown, the character processing unit 121 includes:

[0127] The type processing subunit 1211 is used to determine the original rare character encoding type corresponding to the rare character user name, and query at least one reference rare character encoding type corresponding to the target rare character based on the multi-encoding rare character library and the original rare character encoding type;

[0128] The type determination subunit 1212 is used to determine at least one rare transcoding type corresponding to the target rare character based on the at least one reference rare encoding type.

[0129] Optionally, the type processing subunit 1211 is used for:

[0130] Based on a multi-encoding rare character library, determine at least one reference rare character encoding type other than the original rare character encoding type; or,

[0131] Obtain at least one default uncommon encoding type corresponding to the information verification service, and determine at least one reference uncommon encoding type that matches the default uncommon encoding type, other than the original uncommon encoding type, based on the multi-encoding uncommon character library.

[0132] Optionally, the type-determining subunit 1212 is used for:

[0133] Use all the aforementioned rare encoding types as at least one rare transcoding type corresponding to the target rare character; or,

[0134] Obtain historical verification record parameters corresponding to each of the reference rare encoding types for the information verification service and / or encoding error coefficients for the rare character user name, and determine at least one rare transcoding type corresponding to the target rare character based on the historical verification record parameters and / or encoding error coefficients.

[0135] Optionally, the character encoding unit 122 is used for:

[0136] Search for rare characters of each rare encoding type corresponding to the target rare character in a multi-encoding rare character library.

[0137] Optionally, the device 1 is further configured to:

[0138] After detecting the input request of the target user on the user terminal, the multi-encoding rare character library stored locally on the user terminal is updated to obtain the updated multi-encoding rare character library.

[0139] Optionally, the device 1 is further configured to:

[0140] Determine the font version information of the multi-encoding rare font library stored locally on the user terminal;

[0141] Based on the font version information, detect the updated version of the multi-encoding rare font library and obtain the font update file corresponding to the updated version;

[0142] The font update process is performed on the multi-encoding uncommon font library stored locally on the user terminal based on the font update file.

[0143] Optionally, the character encoding unit 122 is further configured to:

[0144] Based on the rare encoded characters of each of the aforementioned rare encoding types, the target rare characters in the rare character username are transcoded and updated to obtain at least one rare transcoded name.

[0145] Optionally, the device 1 is further configured to:

[0146] The information verification service verifies user information based on the uncommon character username and the document sequence to obtain the information verification result.

[0147] The information verification result is determined to be either an information verification failure or an information verification success.

[0148] It should be noted that the rare character processing device provided in the above embodiments is only illustrated by the division of the above functional modules when executing the rare character processing method. In practical applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above. In addition, the rare character processing device and the rare character processing method embodiments provided in the above embodiments belong to the same concept, and the implementation process is detailed in the method embodiments, which will not be repeated here.

[0149] The serial numbers in this specification are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0150] In one or more embodiments of this specification, the electronic device obtains the uncommon character username and document sequence entered by the user for the information verification service. By performing uncommon character encoding processing on the uncommon character username, a list of uncommon character names corresponding to the uncommon character username is obtained. One or more uncommon character names in the list of uncommon character names are highly likely to be accurately identified by the information verification service using uncommon character encoding. This avoids the situation where the information verification cannot be combined with the document sequence due to the inability to recognize uncommon characters. Subsequently, user information can be verified through the information verification service based on the list of uncommon character names and the document sequence. The entire uncommon character processing process reduces manual operation by the user, ensures the normal operation of the information verification service, improves the robustness of the information verification service, and facilitates the use of uncommon character names by users in information verification scenarios.

[0151] This specification also provides a computer storage medium capable of storing multiple instructions adapted to be loaded and executed by a processor as described above. Figures 1-3The method for handling rare characters in the illustrated embodiment can be found in the following documentation for a detailed execution process: Figures 1-3 The specific details of the illustrated embodiments will not be elaborated here.

[0152] This specification also provides a computer program product that stores at least one instruction, said at least one instruction being loaded and executed by the processor as described above. Figures 1-3 The method for handling rare characters in the illustrated embodiment can be found in the following documentation for a detailed execution process: Figures 1-3 The specific details of the illustrated embodiments will not be elaborated here.

[0153] Please refer to Figure 7 This diagram illustrates a structural block diagram of an electronic device provided in an exemplary embodiment of this specification. The electronic device in this specification may include one or more components such as a processor 110, a memory 120, an input device 130, an output device 140, and a bus 150. The processor 110, memory 120, input device 130, and output device 140 may be connected via the bus 150.

[0154] Processor 110 may include one or more processing cores. Processor 110 connects to various parts of the electronic device via various interfaces and lines, and performs various functions and processes data of electronic device 100 by running or executing instructions, programs, code sets, or instruction sets stored in memory 120, and by calling data stored in memory 120. Optionally, processor 110 may be implemented using at least one hardware form of digital signal processing (DSP), field-programmable gate array (FPGA), or programmable logic array (PLA). Processor 110 may integrate one or more of the following: central processing unit (CPU), graphics processing unit (GPU), and modem. The CPU primarily handles the operating system, user interface, and applications; the GPU is responsible for rendering and drawing the displayed content; and the modem handles wireless communication. It is understood that the modem may also not be integrated into processor 110 and may be implemented separately through a communication chip.

[0155] The memory 120 may include random access memory (RAM) or read-only memory (ROM). Optionally, the memory 120 may include a non-transitory computer-readable storage medium. The memory 120 may be used to store instructions, programs, code, code sets, or instruction sets. The memory 120 may include a program storage area and a data storage area. The program storage area may store instructions for implementing an operating system, instructions for implementing at least one function (such as touch functionality, sound playback functionality, image playback functionality, etc.), instructions for implementing the various method embodiments described below, etc. The operating system may be the Android system, including systems deeply developed based on the Android system, the iOS system developed by Apple Inc., including systems deeply developed based on the iOS system, or other systems. The data storage area may also store data created by the electronic device during use, such as phonebook data, audio and video data, chat log data, etc.

[0156] See Figure 8 As shown, the memory 120 can be divided into operating system space and user space. The operating system runs in the operating system space, while native and third-party applications run in the user space. To ensure that different third-party applications can achieve good running performance, the operating system allocates corresponding system resources for each application. However, different application scenarios within the same third-party application have different requirements for system resources. For example, in local resource loading scenarios, third-party applications have high requirements for disk read speed; in animation rendering scenarios, third-party applications have high requirements for GPU performance. Since the operating system and third-party applications are independent of each other, the operating system often cannot promptly perceive the current application scenario of a third-party application, resulting in the operating system's inability to adapt system resources accordingly to the specific application scenario of the third-party application.

[0157] In order for the operating system to distinguish the specific application scenarios of third-party applications, it is necessary to establish data communication between the third-party applications and the operating system. This would allow the operating system to obtain the current scenario information of the third-party applications at any time, and then perform targeted system resource adaptation based on the current scenario.

[0158] Taking the Android operating system as an example, the programs and data stored in memory 120 are as follows: Figure 9As shown, the memory 120 can store the Linux kernel layer 320, the system runtime library layer 340, the application framework layer 360, and the application layer 380. The Linux kernel layer 320, system runtime library layer 340, and application framework layer 360 belong to the operating system space, while the application layer 380 belongs to the user space. The Linux kernel layer 320 provides low-level drivers for various hardware components of the electronic device, such as display drivers, audio drivers, camera drivers, Bluetooth drivers, Wi-Fi drivers, and power management. The system runtime library layer 340 provides support for key features of the Android system through several C / C++ libraries. For example, the SQLite library provides database support, the OpenGL / ES library provides 3D graphics support, and the Webkit library provides browser kernel support. The system runtime library layer 340 also provides the Android runtime library, which mainly provides core libraries that allow developers to write Android applications using the Java language. The Application Framework Layer 360 provides various APIs that may be used when building applications. Developers can also use these APIs to build their own applications, such as activity management, window management, view management, notification management, content provider, package management, call management, resource management, and location management. At least one application runs in the Application Layer 380. These applications can be native applications that come with the operating system, such as contacts, SMS, clock, and camera apps; or third-party applications developed by third-party developers, such as games, instant messaging, and photo editing apps.

[0159] Taking the operating system as an example (iOS), the programs and data stored in memory 120 are as follows: Figure 10As shown, the iOS system includes: Core OS layer 420, Core Services layer 440, Media layer 460, and Cocoa Touch layer 480. Core OS layer 420 includes the operating system kernel, drivers, and low-level program frameworks. These low-level program frameworks provide hardware-level functionality for use by the program frameworks located in Core Services layer 440. Core Services layer 440 provides system services and / or program frameworks required by applications, such as Foundation framework, account framework, advertising framework, data storage framework, network connectivity framework, geolocation framework, motion framework, etc. Media layer 460 provides applications with audiovisual interfaces, such as interfaces related to graphics and images, audio technology, video technology, and AirPlay (wireless playback of audio and video transmission technologies). Cocoa Touch layer 480 provides various commonly used interface-related frameworks for application development and is responsible for user touch interaction on electronic devices. Examples include local notification services, remote push services, advertising frameworks, game tool frameworks, message user interface (UI) frameworks, UIKit frameworks, map frameworks, and so on.

[0160] exist Figure 10 The framework shown includes, but is not limited to, the base framework in the core service layer 440 and the UIKit framework in the touchable layer 480. The base framework provides many basic object classes and data types, offering the most basic system services to all applications, and is independent of the UI. The UIKit framework, on the other hand, provides a basic UI class library for creating touch-based user interfaces. iOS applications can use the UIKit framework to provide their UI, thus providing the application's infrastructure for building user interfaces, drawing, handling user interaction events, responding to gestures, and so on.

[0161] The methods and principles for implementing data communication between third-party applications and the operating system in the iOS system can be found in the Android system, and will not be repeated here.

[0162] The input device 130 is used to receive input instructions or data, and includes, but is not limited to, a keyboard, mouse, camera, microphone, or touch device. The output device 140 is used to output instructions or data, and includes, but is not limited to, a display device and a speaker. In one example, the input device 130 and the output device 140 can be combined into a touch screen, which is used to receive touch operations from the user using a finger, stylus, or any suitable object on or near it, and to display the user interface of various applications. The touch screen is usually located on the front panel of the electronic device. The touch screen can be designed as a full-screen, curved screen, or irregularly shaped screen. The touch screen can also be designed as a combination of a full-screen and a curved screen, or a combination of an irregularly shaped screen and a curved screen; this specification does not limit this.

[0163] In addition, those skilled in the art will understand that the structure of the electronic device shown in the above figures does not constitute a limitation on the electronic device. The electronic device may include more or fewer components than shown, or combine certain components, or have different component arrangements. For example, the electronic device may also include radio frequency circuits, input units, sensors, audio circuits, wireless fidelity (WiFi) modules, power supplies, Bluetooth modules, etc., which will not be described in detail here.

[0164] In this specification, the entity executing each step can be the electronic device described above. Optionally, the entity executing each step can be the operating system of the electronic device. The operating system can be Android, iOS, or other operating systems; this specification does not limit this.

[0165] The electronic device described in this manual may also be equipped with a display device. This display device can be any device capable of displaying information, such as a cathode ray tube display (CR), a light-emitting diode display (LED), an e-ink screen, a liquid crystal display (LCD), or a plasma display panel (PDP). Users can use the display device on electronic device 101 to view displayed text, images, videos, and other information. The electronic device may be a smartphone, tablet computer, gaming device, AR (Augmented Reality) device, automobile, data storage device, audio playback device, video playback device, laptop, desktop computing device, or wearable device such as an electronic watch, electronic glasses, electronic helmet, electronic bracelet, electronic necklace, or electronic clothing.

[0166] exist Figure 7 In the illustrated electronic device, which can be a terminal, the processor 110 can be used to call the application stored in the memory 120 and specifically perform the following operations:

[0167] Retrieve the username and document sequence containing uncommon characters entered for the information verification service;

[0168] The uncommon character usernames are processed by uncommon character encoding to obtain a list of uncommon character names corresponding to the uncommon character usernames;

[0169] Based on the list of rare character names and the document sequence, user information is verified through the information verification service to obtain the information verification result.

[0170] In one embodiment, when the processor 110 performs the uncommon character transcoding process on the uncommon character username to obtain a list of uncommon character names corresponding to the uncommon character username, it performs the following operations:

[0171] Obtain the target rare character from the rare character username, and determine at least one rare character encoding type for the target rare character;

[0172] Obtain the rare encoded characters of each rare encoding type corresponding to the target rare character;

[0173] Based on the rare encoded characters of each of the rare transcoding types, the rare character usernames are transcoded to obtain at least one rare transcoded name, and a list of rare character names containing the rare transcoded names is generated.

[0174] In one embodiment, the processor 110, when determining at least one rare encoding type for the target rare character, performs the following steps:

[0175] Determine the native rare character encoding type corresponding to the rare character username, and query at least one reference rare character encoding type corresponding to the target rare character based on the multi-encoding rare character library and the native rare character encoding type;

[0176] Based on the at least one reference rare encoding type, at least one rare transcoding type corresponding to the target rare character is determined.

[0177] In one embodiment, when the processor 110 executes the query based on the multi-encoding rare character library and the original rare character encoding type to find at least one reference rare character encoding type, it performs the following steps:

[0178] Based on a multi-encoding rare character library, determine at least one reference rare character encoding type other than the original rare character encoding type; or,

[0179] Obtain at least one default uncommon encoding type corresponding to the information verification service, and determine at least one reference uncommon encoding type that matches the default uncommon encoding type, other than the original uncommon encoding type, based on the multi-encoding uncommon character library.

[0180] In one embodiment, the processor 110 performs the following steps when determining at least one rare encoding type corresponding to the target rare character based on the at least one reference rare encoding type:

[0181] Use all the aforementioned rare encoding types as at least one rare transcoding type corresponding to the target rare character; or,

[0182] Obtain historical verification record parameters corresponding to each of the reference rare encoding types for the information verification service and / or encoding error coefficients for the rare character user name, and determine at least one rare transcoding type corresponding to the target rare character based on the historical verification record parameters and / or encoding error coefficients.

[0183] In one embodiment, when the processor 110 executes the step of obtaining the rare encoded characters of each rare encoding type corresponding to the target rare character, it performs the following steps:

[0184] Search for rare characters of each rare encoding type corresponding to the target rare character in a multi-encoding rare character library.

[0185] In one embodiment, before the processor 110 performs the step of obtaining the uncommon username and document sequence input for the information verification service, it further performs the following steps:

[0186] After detecting the input request of the target user on the user terminal, the multi-encoding rare character library stored locally on the user terminal is updated to obtain the updated multi-encoding rare character library.

[0187] In one embodiment, when the processor 110 performs the character library update process on the multi-encoding uncommon character library stored locally on the user terminal, it executes the following steps:

[0188] Determine the font version information of the multi-encoding rare font library stored locally on the user terminal;

[0189] Based on the font version information, detect the updated version of the multi-encoding rare font library and obtain the font update file corresponding to the updated version;

[0190] The font update process is performed on the multi-encoding uncommon font library stored locally on the user terminal based on the font update file.

[0191] In one embodiment, when the processor 110 performs rare character transcoding processing on the rare character username based on the rare character encoding of each of the rare encoding types to obtain at least one rare transcoded name, it performs the following steps:

[0192] Based on the rare encoded characters of each of the aforementioned rare encoding types, the target rare characters in the rare character username are transcoded and updated to obtain at least one rare transcoded name.

[0193] In one embodiment, before performing the uncommon character encoding conversion process on the uncommon character username, the processor 110 further performs the following steps:

[0194] The information verification service verifies user information based on the uncommon character username and the document sequence to obtain the information verification result.

[0195] The information verification result is determined to be either an information verification failure or an information verification success.

[0196] In one embodiment, the processor 110 further performs the following steps when executing the rare character processing method:

[0197] If the information verification result is an information verification failure type, then the step of performing rare character transcoding on the rare character username to obtain the rare character name list corresponding to the rare character username is executed;

[0198] If the information verification result is of the "information verification successful" type, then output the information verification result of the "information verification successful" type.

[0199] In one or more embodiments of this specification, the electronic device obtains the uncommon character username and document sequence entered by the user for the information verification service. By performing uncommon character encoding processing on the uncommon character username, a list of uncommon character names corresponding to the uncommon character username is obtained. One or more uncommon character names in the list of uncommon character names are highly likely to be accurately identified by the information verification service using uncommon character encoding. This avoids the situation where the information verification cannot be combined with the document sequence due to the inability to recognize uncommon characters. Subsequently, user information can be verified through the information verification service based on the list of uncommon character names and the document sequence. The entire uncommon character processing process reduces manual operation by the user, ensures the normal operation of the information verification service, improves the robustness of the information verification service, and facilitates the use of uncommon character names by users in information verification scenarios.

[0200] Those skilled in the art will understand that all or part of the processes in the above embodiments can be implemented by a computer program instructing related hardware. The program can be stored in a computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods. The storage medium can be a magnetic disk, optical disk, read-only memory, or random access memory, etc.

[0201] It should be noted that the information (including but not limited to user device information, user personal information, etc.), data (including but not limited to uncommon character user names, user names and document sequences, etc.) and signals involved in the embodiments of this specification are all authorized by the user or fully authorized by all parties, and the collection, use and processing of related data must comply with the relevant laws, regulations and standards of the relevant countries and regions. For example, the object characteristics, interaction behavior characteristics and user information involved in this specification were all obtained under full authorization.

[0202] The above-disclosed embodiments are merely preferred embodiments of this specification and should not be construed as limiting the scope of this specification. Therefore, any equivalent variations made in accordance with the claims of this specification shall still fall within the scope of this specification.

Claims

1. A method for processing uncommon characters, the method comprising: Retrieve the username and document sequence containing uncommon characters entered for the information verification service; Obtain the target rare character in the rare character username, determine the original rare character encoding type corresponding to the rare character username, and query at least one reference rare character encoding type corresponding to the target rare character based on the multi-encoding rare character library and the original rare character encoding type; Obtain historical verification record parameters corresponding to each of the reference rare encoding types for the information verification service and / or encoding error coefficients for the rare character user name, and determine at least one rare transcoding type corresponding to the target rare character based on the historical verification record parameters and / or encoding error coefficients; Obtain the rare encoded characters of each rare encoding type corresponding to the target rare character, perform rare character encoding processing on the rare character username based on the rare encoded characters of each rare encoding type, obtain at least one rare encoded name, and generate a list of rare character names containing the rare encoded names; Based on the list of rare character names and the document sequence, user information is verified through the information verification service to obtain the information verification result; The multi-encoding rare character library includes rare character objects, rare encoding methods corresponding to the rare character objects, and rare characters of the rare character objects under the rare encoding methods. The reference rare encoding type is a rare encoding type that is different from the original rare encoding type. The reference rare encoding type does not include the original rare encoding type.

2. The method according to claim 1, wherein querying at least one reference rare character encoding type corresponding to the target rare character based on the multi-encoding rare character library and the original rare character encoding type includes: Based on a multi-encoding rare character library, determine at least one reference rare character encoding type other than the original rare character encoding type; or, Obtain at least one default uncommon encoding type corresponding to the information verification service, and determine at least one reference uncommon encoding type that matches the default uncommon encoding type, other than the original uncommon encoding type, based on the multi-encoding uncommon character library.

3. The method according to claim 1, wherein obtaining the rare encoded characters of each rare encoding type corresponding to the target rare character includes: Search for rare characters of each rare encoding type corresponding to the target rare character in a multi-encoding rare character library.

4. The method according to claim 2, further comprising, before obtaining the uncommon character username and document sequence input for the information verification service: After detecting the input request of the target user on the user terminal, the multi-encoding rare character library stored locally on the user terminal is updated to obtain the updated multi-encoding rare character library.

5. The method according to claim 4, wherein the step of updating the multi-encoding rare character set stored locally on the user terminal includes: Determine the font version information of the multi-encoding rare font library stored locally on the user terminal; Based on the font version information, detect the updated version of the multi-encoding rare font library and obtain the font update file corresponding to the updated version; The font update process is performed on the multi-encoding uncommon font library stored locally on the user terminal based on the font update file.

6. The method according to claim 1, wherein the step of performing rare character transcoding processing on the rare character username based on the rare encoded characters of each of the rare encoding types to obtain at least one rare transcoded name includes: Based on the rare encoded characters of each of the aforementioned rare encoding types, the target rare characters in the rare character username are transcoded and updated to obtain at least one rare transcoded name.

7. The method according to claim 1, further comprising, before performing rare character encoding processing on the rare character username: The information verification service verifies user information based on the uncommon character username and the document sequence to obtain the information verification result. The information verification result is determined to be either an information verification failure or an information verification success.

8. The method according to claim 7, further comprising: If the information verification result is an information verification failure type, then the step of performing rare character transcoding on the rare character username to obtain the rare character name list corresponding to the rare character username is executed; If the information verification result is of the "information verification successful" type, then output the information verification result of the "information verification successful" type.

9. A device for processing uncommon characters, the device comprising: The information acquisition module is used to acquire the uncommon character username and document sequence entered by the user on the client side for the information verification service; The uncommon character processing module is used to obtain the target uncommon character in the uncommon character user name, determine the original uncommon character encoding type corresponding to the uncommon character user name, query at least one reference uncommon character encoding type corresponding to the target uncommon character based on the multi-encoding uncommon character library and the original uncommon character encoding type; obtain historical verification record parameters corresponding to each of the reference uncommon character encoding types for the information verification service and / or encoding error coefficients for the uncommon character user name, and determine at least one uncommon character transcoding type corresponding to the target uncommon character based on the historical verification record parameters and / or encoding error coefficients; Obtain the rare encoded characters of each rare encoding type corresponding to the target rare character, perform rare character encoding processing on the rare character username based on the rare encoded characters of each rare encoding type, obtain at least one rare encoded name, and generate a list of rare character names containing the rare encoded names; The information verification module is used to verify user information based on the list of rare character names and the document sequence through the information verification service, and obtain the information verification result; The multi-encoding rare character library includes rare character objects, rare encoding methods corresponding to the rare character objects, and rare characters of the rare character objects under the rare encoding methods. The reference rare encoding type does not include native rare encoding types.

10. A computer storage medium storing a plurality of instructions adapted for loading by a processor and executing the steps of the method as claimed in any one of claims 1 to 8.

11. A computer program product storing at least one instruction, said at least one instruction being loaded by a processor and executing the steps of the method as claimed in any one of claims 1 to 8.

12. An electronic device, comprising: A processor and a memory; wherein the memory stores a computer program adapted to be loaded by the processor and to execute the steps of the method as described in any one of claims 1 to 8.

Images