Contact information processing method, storage medium, and vehicle

Abstract

The application discloses a contact information processing method, which comprises the following steps: receiving contact information in a mobile terminal address book, determining that the contact information is contact information with multiple phonetic characters in name information; creating multiple index records for the contact information based on the name information of the contact information; and querying the contact information according to the multiple index records based on the pronunciation of the multiple phonetic characters input by a user. The multiple phonetic characters in the received contact information are identified, and multiple index records corresponding to different pronunciations of the multiple phonetic characters are created for the contact information containing the multiple phonetic characters, the multiple index records jointly form a query channel between any standard pronunciation of the multiple phonetic characters and the corresponding contact information, comprehensive coverage of the query is realized, different recognitions and pronunciation habits of the user for the multiple phonetic characters are adapted, the diversified recognition habits of the user are more fitted, efficient query of the address book contact information synchronized across devices is realized, and the vehicle communication experience of the user is improved.

Description

Technical Field

[0001] This application relates to the field of information processing technology, specifically to a contact information processing method, a storage medium, and a vehicle. Background Technology

[0002] With the continuous development of vehicle intelligence technology, data interconnection and collaboration between in-vehicle information systems and mobile terminals, especially the efficient and reliable synchronization of contact information across devices, has become one of the key requirements for improving the in-vehicle intelligent experience. Currently, the function of synchronizing contact information across devices mainly relies on Bluetooth communication technology. For example, the Phone Book Access Profile (PBAP) protocol is used to synchronize contact information between mobile terminals and vehicle terminals, thereby enabling contact lookup and call functions on the vehicle terminal.

[0003] However, in practical applications, synchronizing contact information between vehicle and mobile terminals using the traditional PBAP protocol has certain limitations. For example, after transmitting contact information from the mobile terminal to the vehicle terminal via PBAP, the vehicle terminal needs to determine its own method for parsing the mobile terminal's contact information. Because the parsing method used by the vehicle terminal differs from that used by the mobile terminal, the parsing results for contact information with surnames containing multiple pronunciations may differ. This prevents users from quickly locating the corresponding contacts on the vehicle terminal based on their phone's contact grouping habits, impacting the user experience and increasing operational risks in driving scenarios.

[0004] Therefore, how to achieve efficient querying of contact information synchronized across devices to improve user experience has become an urgent problem to be solved. Summary of the Invention

[0005] In view of this, embodiments of this application provide a contact information processing method, storage medium, and vehicle. By identifying contact information containing polyphonic characters in the name information obtained by the vehicle terminal, and creating multiple index records for the identified polyphonic characters, including all different pronunciations of the polyphonic characters, users can query the contact information corresponding to the polyphonic characters by any pronunciation of the polyphonic characters, thereby improving the efficiency of contact information query.

[0006] In a first aspect, embodiments of this application provide a method for processing contact information in a cross-device address book. The method includes: receiving contact information from the address book of a mobile terminal, wherein the contact information includes at least the contact's name information; determining that the contact is a contact whose name information contains a polyphonic character; creating multiple index records for the contact based on the contact's name information, wherein the multiple index records correspond to multiple different pronunciations of the polyphonic character; and querying the contact information based on the pronunciation of the polyphonic character input by the user, according to the multiple index records.

[0007] As one possible implementation of the first aspect, the multiple index records include at least multiple different pronunciations of polyphonic characters in the contact's name information and association identifiers, wherein the association identifiers are used to associate multiple index records and contact information of the same contact. The method further includes: grouping the multiple index records into corresponding groups according to the multiple different pronunciations to achieve multi-group coverage of index records of the same contact; querying contact information based on the pronunciation of polyphonic characters input by the user and multiple index records includes: determining the group in which the index record corresponding to the pronunciation is located based on the pronunciation of the polyphonic characters; searching for the index record corresponding to the pronunciation in the group; and querying contact information based on the association identifiers in the index records.

[0008] As one possible implementation of the first aspect, identifying a contact person whose name contains a character with multiple pronunciations includes: The name information of the contact person is segmented into words to extract the target information, which is the surname or the first character of the name. Based on the target information, the contact person is identified as one whose name contains a polyphonic character.

[0009] As one possible implementation of the first aspect, the target information is the surname portion of the name information. The process of performing word segmentation on the contact's name information to extract the surname information includes: determining the structural type of the contact's surname based on the name information; and performing word segmentation on the name information according to the structural type of the surname to extract the contact's surname information.

[0010] As one possible implementation of the first aspect, determining the structural type of a contact's surname based on name information includes: determining the length of the name information using the forward maximum matching method; when the length of the name information is 1, determining that the contact's surname is a single-character surname; when the length of the name information is greater than or equal to 2, determining the extraction window length based on the length of the name information; extracting candidate strings of the corresponding length from the name information according to the extraction window length, and performing compound surname matching on the candidate strings; if the match is successful, determining that the contact's surname is a compound surname; if the match is unsuccessful, decreasing the extraction window length by 1, and repeating the above steps; when the extraction window length is reduced to 2, and the compound surname matching is still unsuccessful, determining that the contact's surname is a single-character surname.

[0011] As one possible implementation of the first aspect, after extracting candidate strings of the appropriate length from the name information, it also includes: performing boundary validity checks and Chinese character verification on the candidate strings based on the length of the candidate strings and the length of the name information.

[0012] As one possible implementation of the first aspect, the target information is the surname of the name information. Based on the target information, determining the contact person as the contact person whose name information contains polyphonic characters includes: firstly identifying polyphonic characters in the target information with compound surnames, and then identifying polyphonic characters in the target information with single surnames, so as to determine the contact person whose name information contains polyphonic characters.

[0013] As a possible implementation of the first aspect, the method further includes: creating a polyphonic character database, wherein the polyphonic character database stores polyphonic character data records including all polyphonic characters, each polyphonic character data record including at least one polyphonic character information and all standard pronunciations associated with the polyphonic character, wherein determining that a contact person is a contact person whose name information contains a polyphonic character includes: matching the name information with the polyphonic character information in the polyphonic character database; determining that the successfully matched contact person is a contact person whose name information contains a polyphonic character, wherein creating multiple index records for the contact person based on the contact person's name information includes: determining all standard pronunciations of the polyphonic characters in the name information according to the polyphonic character database based on the name information; creating multiple index records for the contact person based on all standard pronunciations of the polyphonic characters.

[0014] Secondly, embodiments of this application provide a computer-readable storage medium storing a computer program for performing the contact information processing method described in the first aspect.

[0015] Thirdly, embodiments of this application provide a vehicle including a processor; and a memory for storing processor-executable instructions, wherein the processor is used to execute the contact information processing method described in the first aspect above.

[0016] This application provides a contact information processing method, storage medium, and vehicle. The method identifies polyphonic characters in the received contact information and creates multiple index records for each polyphonic character, each corresponding to a different pronunciation. These index records collectively form a query channel between any standard pronunciation of the polyphonic character and the corresponding contact information, achieving comprehensive query coverage. This adapts to users' different understandings and pronunciation habits of polyphonic characters, better aligning with diverse user cognitive habits, and enabling efficient querying of contact information synchronized across devices, thus improving the user's in-vehicle communication experience. Furthermore, it fundamentally eliminates the problem of grouping discrepancies after synchronizing contact information across terminals, eliminating the need for users to repeatedly switch groups to search due to differences in grouping or pronunciation habits while driving, reducing operational risks. Attached Figure Description

[0017] To more clearly illustrate the technical solutions of the embodiments of the present invention, the accompanying drawings used in the embodiments will be briefly introduced below. It should be understood that the following drawings only show some embodiments of the present invention and should not be regarded as a limitation on the scope. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.

[0018] Figure 1 This is a schematic diagram of the structure of a contact information processing system provided in an exemplary embodiment of this application.

[0019] Figure 2 This is a flowchart illustrating a contact information processing method provided in an exemplary embodiment of this application.

[0020] Figure 3 This is a flowchart illustrating a polyphonic character recognition method provided in an exemplary embodiment of this application.

[0021] Figure 4 This is a flowchart illustrating a method for extracting the surname from name information according to an exemplary embodiment of this application.

[0022] Figure 5 This is a schematic diagram of the structure of a contact information processing device provided in an exemplary embodiment of this application.

[0023] Figure 6 This is a block diagram of an electronic device for processing contact information provided in an exemplary embodiment of this application. Detailed Implementation

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

[0025] Application Overview Cross-device (between vehicle and mobile devices) contact information synchronization primarily relies on the Bluetooth Phonebook Access Protocol (BIP). The BIP is a client-server protocol based on Bluetooth technology. Its core function is to allow client devices to access contact data from a server device, thereby enabling cross-device contact information synchronization. For example, in an in-vehicle scenario, the BIP bridges the data synchronization gap between the vehicle and mobile devices, allowing the vehicle to securely access and synchronize contact information from the mobile device's address book. Based on this, the vehicle can provide users with integrated in-vehicle communication functions, including contact information management and querying.

[0026] Currently, when synchronizing contact information across devices using the Bluetooth phonebook access protocol, the following process is typically employed: First, the vehicle terminal and the mobile terminal establish a Bluetooth connection based on the Bluetooth phonebook access protocol; then, the mobile terminal transmits key contact data, such as the names and phone numbers of contacts in its address book, to the vehicle terminal. The vehicle terminal uses its built-in parsing algorithm to parse the received contact data and stores the parsing results and contact data in a local database to enable grouped display and retrieval of contacts.

[0027] However, because the Bluetooth phonebook access protocol only specifies the data transmission of basic fields such as name and phone number, and does not define dedicated transmission fields for auxiliary retrieval information such as the first letter of the contact's pinyin, the vehicle terminal needs to parse the received contact data itself. In practical applications, due to differences in the polyphonic character parsing algorithms used by different mobile terminal manufacturers, the mainstream parsing algorithm used by the vehicle terminal (e.g., tinypinyin) is also different from the parsing algorithm used by the mobile terminal. This means that the parsing results of the same polyphonic character may be inconsistent on different terminals, making it impossible for users to quickly locate target contacts on the vehicle terminal based on their contact grouping and retrieval habits on the mobile terminal. This affects the user experience and also increases the operational risks in driving scenarios.

[0028] To address the aforementioned technical issues, this application's embodiments creatively identify contact information containing polyphonic characters in the name information obtained from the vehicle terminal, and create multiple index records for the identified polyphonic characters, including all their different pronunciations. This allows users to query the contact information corresponding to a polyphonic character using any of its pronunciations, thereby improving the efficiency of contact information retrieval and enhancing the user experience.

[0029] Various non-limiting embodiments of this application will now be described in detail with reference to the accompanying drawings.

[0030] Exemplary Contact Information Processing System Figure 1 This is a schematic diagram of the structure of a contact information processing system provided in some embodiments of this application, such as... Figure 1 As shown, the contact information processing system 100 may include at least one mobile terminal 110 and a vehicle terminal 120. The vehicle terminal 120 includes a display device 121 and a control system 122.

[0031] In some embodiments, the control system 122, as the core control module of the vehicle terminal, is mainly responsible for managing the communication connection between the vehicle terminal and the mobile terminal, receiving, parsing, and processing data from the mobile terminal, thereby achieving cross-device data synchronization. For example, the control system 122 may be the vehicle terminal's infotainment system or in-vehicle intelligent interconnection system.

[0032] Display device 121 serves as the human-machine interface for the vehicle terminal, primarily responsible for visualizing data synchronized to the mobile terminal based on user interactions. For example, display device 121 can be used to present parsed contact information from the mobile terminal for user viewing.

[0033] In some embodiments, the display device 121 may include at least one display screen. For example, the display device may include a central touch display screen or a secondary display screen located in the front passenger seat or the rear of the vehicle.

[0034] In some embodiments, at least one mobile terminal 110 can be connected to the vehicle 120 via a wired connection or a wireless connection. For example, at least one mobile terminal 110 can transmit data via Bluetooth phonebook access protocol or transmit data from the mobile terminal to the vehicle terminal via USB.

[0035] In some embodiments, at least one mobile terminal 110 may include any one or more of a mobile phone terminal, a tablet computer terminal, a laptop computer terminal, a personal computer terminal, and a wearable smart device (e.g., a smartwatch, a smart bracelet).

[0036] In some embodiments, the contact information processing method described below can be executed by the control system 122 in the contact information processing system.

[0037] Exemplary contact information processing method To further illustrate the specific process of cross-device contact information processing, this application also provides a flowchart of a contact information processing method. Figure 2 ).

[0038] In some embodiments, such as Figure 2 As shown, the control device 122 can perform the following steps: S210: Receive contact information from the address book of the mobile terminal.

[0039] Contact information can be from the mobile device's address book, used to achieve contact information synchronization across devices.

[0040] In some embodiments, the contact information includes at least the contact person's name. For example, the contact information may include the contact person's name and telephone number, such as name: Zang Moumou, telephone number: 13800138000. The contact information may also include the contact person's name, telephone number, and email address, etc. This application does not specifically limit the content of the contact information.

[0041] In some embodiments, the mobile terminal may be a mobile phone terminal, a tablet computer terminal, a laptop computer terminal, etc. More details about mobile terminals can be found here. Figure 1 The relevant descriptions in the embodiments are not repeated here.

[0042] In some embodiments, a communication link between the vehicle terminal and the mobile terminal can be established via Bluetooth, for example, the Bluetooth Phonebook Access Protocol, to transmit contact information; data exchange and transmission between the vehicle terminal and the mobile terminal can also be achieved via wireless Wi-Fi or USB. This application does not specifically limit the specific implementation method of cross-device data transmission.

[0043] In some embodiments, the vehicle terminal may respond to the user's command to synchronize the address book, actively send a request to the mobile terminal, and receive contact information from the mobile terminal; it may also automatically push contact information from the address book to the vehicle terminal after establishing a communication connection with the mobile terminal.

[0044] S220. Identify the contact person as someone whose name contains a character with multiple pronunciations.

[0045] In some embodiments, such as Figure 3As shown, the processing of name information and the recognition of contacts with polyphonic characters can be achieved through the following steps, namely, S220 may include the following steps: S221. Perform word segmentation on the contact person's name information and extract the target information from the name information.

[0046] Considering that in practical applications, users mainly query contact information by the first character of the name or the pronunciation of the contact's surname, in some embodiments, the target information can be the surname or the first character of the name. It can identify whether the pronunciation of the first character of the contact's name or the pronunciation of the surname is a polyphonic character, and identify the contact whose first character or surname is a polyphonic character as the contact whose name contains polyphonic characters.

[0047] For example, if the received contact's name is "Le Yi," the character "Le" is extracted from the contact's name. This character is then identified as a polyphonic character, meaning the contact is classified as having a polyphonic character in their name, and thus marked as such. It should be noted that the above example of identifying polyphonic contacts by extracting the first character or surname is merely one example. Identification can also be achieved by extracting other parts of the name information; for instance, the entire name information can be used for character-by-character identification. This application does not specifically limit this approach.

[0048] In some embodiments, before performing the polyphonic character recognition process in S220, the name information in the received contact information can be preprocessed. For example, the name information to be processed can be cleaned and standardized. For instance, regular expressions or string filtering functions can be used to remove interfering characters (e.g., spaces, tabs, etc.) from the contact information, and only Chinese characters, English letters, and numbers can be retained for non-Chinese characters in the name information. This achieves the unification and standardization of contact data, ensures the standardization of the name string, provides a clean and reliable data source for the subsequent polyphonic character recognition process, avoids the influence of special characters on the polyphonic character recognition process, and ensures the accuracy of polyphonic character recognition.

[0049] In some embodiments, a surname extraction model can be constructed to extract the surname from name information. For example, the surname extraction model can be a deep learning model.

[0050] Considering the diversity of surnames, in order to further improve the accuracy of surname extraction, in some embodiments, such as Figure 4 As shown, S221 may include the following sub-steps: S2211. Based on the name information, determine the structure type of the contact person's surname.

[0051] S2212. Based on the structure type of the surname, perform word segmentation on the name information to extract the surname information of the contact person.

[0052] As an example, the structure of a contact's surname can include single-character surnames and compound surnames.

[0053] To ensure the accuracy of identifying contacts with polyphonic characters, we can first determine the structural type of the surname in the name information, and then extract the surname information based on the structural type of the surname.

[0054] In some embodiments, the word segmentation process for name information can be implemented using the forward maximum matching method to extract target content from the name information. Target content refers to the portion of the name information extracted for subsequent recognition of polyphonic characters. For example, the surname or the first character of the name information.

[0055] In some embodiments, the longest matching principle can be used to match polyphonic characters. This means prioritizing the matching of compound surnames (polyphonic characters with compound characters), identifying them, and then matching single-character surnames (polyphonic characters with single-character surnames). This avoids misidentifying compound surnames as single-character surnames and ensures the accuracy of compound surname recognition. By employing a word segmentation method that combines the structural type of the surname, contact name information containing compound surnames can be processed more robustly, laying a more reliable data foundation for the subsequent polyphonic character recognition process, thereby ensuring the accuracy of polyphonic character recognition.

[0056] In some embodiments, after extracting candidate compound surname strings, boundary validity checks and Chinese character verification can be performed on the candidate compound surname strings. Specifically, three checks can be performed based on the length of the candidate compound surname string and the total length of the name corresponding to the candidate compound surname string. The first check determines whether the length of the candidate compound surname string exceeds the length of the name information. If it does, the compound surname string is deemed invalid and truncated again. The second check determines whether the length of the candidate compound surname string is less than 2 characters. If it is less than 2 characters, the compound surname string is deemed invalid and truncated again. The third check iterates through each character in the candidate compound surname string and determines whether the encoding of each character is within the range of Chinese character encoding (0x4e00-0x9fa5). Only candidate compound surname strings that pass all three checks will proceed to the subsequent polyphonic compound surname recognition process.

[0057] S222. Based on the target information, identify the contact person whose name contains a character with multiple pronunciations.

[0058] In some embodiments, the length of the input name information can be determined first using a forward maximum matching algorithm. Based on the determination result, a corresponding matching strategy is adopted to identify polyphonic surnames. For example, if the length of the name information is less than 1 or empty, an empty result is returned, indicating that the surname cannot be extracted from the name information; if the length of the name information is 1, the name is directly treated as a single-character surname for polyphonic character identification; if the length of the name information is greater than or equal to 2, based on the length of the name information, the maximum extraction window length for matching compound surnames is first determined, the maximum extraction window length is reduced to 2 characters, and candidate strings are extracted sequentially for matching compound surnames to identify polyphonic compound surnames.

[0059] Specifically, the name information to be identified is obtained, and the character length of the name information is calculated. ,Will Compared with the preset length threshold of compound surnames Comparison, for example, It can be set to 4 to adjust the character length. With the preset length threshold Compare the two values ​​and take the smaller value as the initial matching window length. Specifically, it can be done through Implementation, starting from the initial matching window length Begin with iterative decreasing matching. Specifically, starting from the beginning of the name information to be processed, extract a length of... The continuous string is selected as the first candidate compound surname string; this first candidate compound surname string is then matched against polyphonic compound surnames. If a match is found, the first candidate compound surname string is determined to be a polyphonic compound surname string; if no match is found, the matching window length is adjusted. Subtract 1, that is Then, the matching process for polyphonic surname strings is repeated. If the matching window length is reduced to the preset minimum length threshold of 2 and no match is found, the candidate surname string is determined to be a single-character string, that is, the surname in the name information to be identified is a single-character surname and does not belong to polyphonic surnames.

[0060] In some embodiments, a polyphonic character database can be created, and polyphonic characters in name information can be identified based on the database. For example, the polyphonic character database can store polyphonic character data records including all polyphonic characters, with each record containing at least one polyphonic character and all standard pronunciations associated with that character. The extracted content to be identified (e.g., surname or first character) can be matched with the polyphonic surname information in the polyphonic surname database to achieve polyphonic character identification.

[0061] In some embodiments, each polyphonic character data record in the polyphonic character database may include a surname character, a surname type identifier, and a pronunciation list. Specifically, the pronunciation list may include the complete pinyin of the polyphonic character, the first letter of the pinyin, and the frequency of use. The frequency of use is a floating-point number between 0 and 1, used to sort multiple polyphonic character data records for the same polyphonic character.

[0062] Specifically, the identification information (e.g., surname or first character) extracted from the name information to be identified can be matched sequentially with polyphonic character data records in the polyphonic character database. If the match is successful, the contact person corresponding to the name information will be identified as a contact person with polyphonic characters; if the match is unsuccessful, the contact person corresponding to the name information will be an ordinary contact person with monophonic characters.

[0063] In some embodiments, the polyphonic character data records in the polyphonic character database can be divided into single-surname polyphonic character data records and compound-surname polyphonic character data records. A single-surname polyphonic character index table and a compound-surname polyphonic character index table are constructed based on these two sets of data. The extracted string to be identified (e.g., the surname string or the first character of the given name) is first matched against the compound-surname polyphonic character index table to identify the polyphonic characters. Then, the unmatched information is matched against the single-surname polyphonic character index table to identify the polyphonic characters of single-surnames, avoiding misidentification of compound surnames as single-surname polyphonic characters and ensuring the accuracy of polyphonic character identification for compound surnames.

[0064] To improve the overall efficiency of polyphonic character recognition and reduce invalid matches during the recognition process, in some embodiments, the in-memory index structure of the polyphonic character database may also include a fast lookup set. For example, the fast lookup set includes the first character of the polyphonic characters in single-surname polyphonic character data records and compound-surname polyphonic character data records. This fast lookup set can be implemented using a HashSet data structure.

[0065] Specifically, in the process of recognizing polyphonic characters based on a polyphonic character database, the string to be recognized can be filtered first by using a fast lookup set. The first character of the string to be recognized is matched with the characters in the fast lookup set to achieve fast filtering of polyphonic character information. If the match is successful, the recognition of other characters in the string to be recognized is then performed. If the match is unsuccessful, the contact person corresponding to the string to be recognized is directly marked as a monophonic contact person to avoid invalid matching processes and improve recognition efficiency.

[0066] It should be noted that the specific structure and form of the polyphonic characters stored in the polyphonic character database described in the above embodiments are merely examples. This application does not specifically limit the specific structure and form of the content stored in the polyphonic character database.

[0067] In some embodiments, the polyphonic character database may be stored in the vehicle's local memory.

[0068] In some embodiments, the cloud server includes a dynamically updated polyphonic character dictionary. Extracted information to be identified (e.g., the surname or first character of a name) can be sent to the cloud server via the network. The cloud server then searches for polyphonic characters in the dictionary, matching the information to be identified against the polyphonic characters in the dictionary to achieve recognition of the polyphonic characters in the information to be identified, and returns the recognition result to the vehicle. This recognition method reduces the amount of local storage space required in the vehicle. Furthermore, directly utilizing the latest polyphonic character dictionary in the cloud ensures the timeliness and accuracy of the recognition.

[0069] In some embodiments, a dedicated polyphonic character recognition model can be constructed to achieve intelligent recognition of polyphonic characters in name information. Specifically, the polyphonic character recognition model can be a deep learning network model trained on training samples based on a large amount of labeled data, such as a recurrent neural network model (RNN) or a long short-term memory network model (LSTM). For example, the training samples used to train the polyphonic character recognition model may include a large amount of known polyphonic character information covering different structural types and the different correct pronunciation labels corresponding to the polyphonic characters.

[0070] It should be noted that the methods for extracting the content to be identified from name information and the methods for identifying polyphonic characters provided in the above embodiments are merely examples. The identification of polyphonic characters in name information can also be achieved through any other feasible methods. This application does not specifically limit the extracted content to be identified and the method for identifying polyphonic characters.

[0071] In some embodiments, to improve the system's ability to adapt to personalized contact information, the vehicle terminal can provide the function of allowing users to customize surnames with multiple pronunciations. Specifically, when encountering rare characters or surnames with multiple pronunciations that the system cannot recognize, users can manually enter key information about the contact through the interactive interface provided by the display device on one side of the vehicle terminal (e.g., the central touch screen), such as surname information, the pronunciation of the surname, and the first letter of the pinyin for the surname.

[0072] In some embodiments, after the user enters and confirms the contact information, a polyphonic character data record can be generated and stored in the polyphonic character database on the vehicle's local machine.

[0073] In some embodiments, the polyphonic character database can be constructed as a structured database in Extensible Markup Language (XML) format.

[0074] In some embodiments, the polyphonic character database supports dynamic updates via Over-The-Air Technology (OTA) upgrades or cloud synchronization mechanisms. This allows for the addition of new polyphonic character information and timely correction of stored data, ensuring the accuracy and comprehensiveness of the database. Specifically, updated polyphonic character data can be periodically retrieved from a remote server (cloud server) and synchronized with the cloud server. Corresponding changes to the cloud-based data records are then updated in the polyphonic character database, such as newly added pronunciation information or corrected pronunciation information for previous polyphonic characters, enabling lightweight and rapid dynamic updates. For example, the data in the polyphonic character database can be updated monthly via the cloud server to adapt to different polyphonic character surname recognition scenarios.

[0075] In some embodiments, to ensure the robustness of the polyphonic character database update process and the continuity of the system's polyphonic character recognition service, a complete update mechanism including version verification, backup, and rollback is introduced to update the polyphonic character database. Specifically, before updating the data in the polyphonic character database, the version number and integrity of the updated data can be verified using a hash value verification method. Before updating the data, the current data in the polyphonic character database is automatically backed up to a historical version snapshot. After the backup is complete, the update information is atomically written to the polyphonic character database. During the update process, if an anomaly such as data verification failure or write error occurs, a rollback process is immediately triggered. Based on the backed-up historical version snapshot, the polyphonic character database is restored to its state before the update. The system can immediately return to a stable working state, thereby ensuring the availability of the recognition service.

[0076] To avoid blocking the contact information query process during the update process, an asynchronous approach can be adopted to update the polyphonic character database.

[0077] S230. Based on the contact's name information, create multiple index records for the contact.

[0078] Multiple index records can be constructed for contacts whose names contain polyphonic characters, and are used to query information about contacts with polyphonic characters.

[0079] When a vehicle terminal synchronizes contact information from a mobile terminal via PBAP, this protocol primarily transmits core fields such as name and phone number, without defining dedicated fields for carrying pinyin or the first letter of pinyin. Therefore, the vehicle terminal needs to parse the received Chinese names itself to generate a query index (such as the first letter of pinyin). However, for names containing polyphonic characters, the local parsing libraries or algorithms of the vehicle terminal and the mobile terminal may differ, leading to inconsistent parsing results for the same polyphonic character. Therefore, this application adopts differentiated parsing and index creation methods for contact information including and excluding polyphonic characters.

[0080] In some embodiments, for contact information whose name information includes polyphonic characters, for the identified polyphonic characters in the name information, all common pronunciations and the first letter of the pinyin for the polyphonic characters are obtained. For example, all common pronunciations of the polyphonic characters can be queried and matched from a polyphonic character database. Based on the first letter of the pinyin for the polyphonic character and all common pronunciations, multiple index records for the contact person with the polyphonic character are constructed. These multiple index records together constitute a query channel from any standard pronunciation of the polyphonic character to the contact information, so that the user can match the corresponding index record and locate the target contact information regardless of any standard pronunciation of the polyphonic character.

[0081] By building a polyphonic character database at the software level of the vehicle terminal, the process of segmenting name information, recognizing polyphonic characters, and creating index records based on the polyphonic character database is realized. This makes the entire polyphonic character process unnecessary to modify the PBAP protocol or upgrade the hardware, significantly reducing the development difficulty and making it suitable for large-scale promotion.

[0082] In some embodiments, the index record includes at least an association identifier, surname characters, and complete pinyin. The association identifier is used to link multiple index records of the same contact person as well as that contact person's information. By adding a unified association identifier to multiple index records, associations are established between index records of the same contact person and between index records and corresponding contact information, thereby achieving unified management of contact information and improving the efficiency and accuracy of contact information retrieval. For example, an index record may include a contact ID, association identifier, surname characters, surname type, complete pinyin, first letter of pinyin, pronunciation index (the position of the pronunciation in the list; a pronunciation index of 0 indicates the first pronunciation), whether it is a primary record (set to 1 indicates a primary record), and creation time, etc.

[0083] Specifically, an association identifier can be generated based on the surname character, phone number, and timestamp according to the association identifier generation rule. Exemplarily, the rule for generating the association identifier is: surname character (removing spaces) + underscore separator + the first 8 digits of the MD5 hash value of the phone number + underscore separator + synchronization timestamp (in milliseconds). Specifically, based on the surname string, all space characters therein are removed as the first part of the association identifier; based on the phone number information in the contact information (when there are multiple phone numbers, the first phone number is taken), the hash value is calculated using the Message Digest Algorithm 5 (MDA5) algorithm, and the first 8 hexadecimal characters of the hash value are extracted as the second part of the association identifier; based on the current system time, the millisecond-level timestamp is obtained as the third part of the association identifier. For example, if the contact information is: Name: Zang Moumou; Phone: 13800138000, and the timestamp is 1704067200000, the corresponding generated association identifier is: Zang_a1b2c3d4_1704067200000.

[0084] In some embodiments, the main record in the index record of polyphonic characters can be determined according to the user's usage habits, that is, the habitual pronunciation of the polyphonic character by the user is recorded, and when querying the corresponding polyphonic character contact next time, the contact information is preferentially queried through this index record.

[0085] It should be noted that the above-described manner of creating the index record and the content included in the index record are merely examples. This application does not specifically limit the manner of creating the index record and the specific content included in the index record, and can be flexibly set according to actual needs.

[0086] Considering that in the actual application process, due to the habit differences of different users, for the same polyphonic character, users may input different pronunciations for querying. In view of this, in some embodiments, according to multiple different pronunciations of the polyphonic character, multiple index records of the polyphonic character are grouped into corresponding groups, achieving multi-group coverage of the index records of the same polyphonic character contact, making the grouping more in line with the diverse cognitive habits of users, and improving the applicability of the grouping. Exemplarily, for a contact named "Le Jia", it can be grouped into the "L" group and the "Y" group.

[0087] In some embodiments, for contact information of contacts whose name information does not include polyphonic characters (single-surname contacts), a conventional pinyin parsing library is used to perform pinyin conversion on the name information of the contacts, such as the tinypinyin parsing library.

[0088] In some embodiments, a database transaction mechanism can be used to batch insert multiple index records to ensure atomic operations.

[0089] In some embodiments, data cleanup is performed before creating a new index record to ensure data consistency. Specifically, based on the contact ID and associated identifier, the system can query the Pinyin parsing record table to see if an old parsing record for that contact exists. If it does, a database transaction is initiated, all matching old records (the matching condition is that the contact ID or associated identifier is the same) are deleted, and after the transaction is committed, the new record creation operation is performed to avoid duplicate records and dirty data issues.

[0090] S240. Based on the pronunciation of polyphonic characters input by the user, query contact information according to multiple index records.

[0091] In some embodiments, based on user-input search keywords, the keywords can be converted into pinyin and the first letters of the pinyin. The corresponding index record is then determined based on the pinyin and / or the first letters of the pinyin, and the relevant contact information is retrieved from the database based on the index record. The query criteria can be name information containing the keywords, the complete pinyin of the keywords, or the first letters of the keywords.

[0092] In some embodiments, the index record table is queried for all multiple index records that match the first letter. The duplicates are removed by association identifier and contact ID, and only one record is kept for display. This ensures that the same contact is displayed only once in multiple groups, achieving compatibility across multiple groups while avoiding duplicate display.

[0093] In summary, by identifying polyphonic characters in the received contact information, multiple index records are created for contacts containing polyphonic characters, each corresponding to a different pronunciation. These multiple index records together form a query channel between any standard pronunciation of the polyphonic character and the corresponding contact information, achieving comprehensive query coverage. This adapts to users' different understandings and pronunciation habits of polyphonic characters, better catering to diverse user cognitive habits and enabling efficient querying of contact information synchronized across devices, thus improving the user's in-vehicle communication experience. Furthermore, it fundamentally eliminates the problem of grouping discrepancies after synchronizing contact information across devices, eliminating the need for users to repeatedly switch groups to search due to differences in grouping or pronunciation habits while driving, reducing operational risks.

[0094] To further illustrate the overall application process of the contact information processing method, the following describes the application process of the contact information processing method provided in this application dynamically through a specific driving scenario.

[0095] User Xiao Wang is driving his vehicle. His phone automatically connects to the car's infotainment system via Bluetooth, and the system automatically synchronizes his contacts. Xiao Wang wants to call his friend "Shan Yunfei." While driving, Xiao Wang tries to contact Shan Yunfei. After the contact information synchronization is complete, the system recognizes "Shan Yunfei" as a contact with a polyphonic character (the surname "Shan" matches the local polyphonic character database) and creates two index records for it: 'Shan' and 'Dan'. These records are then categorized into the "S" and "D" groups, respectively. When Xiao Wang enters his preferred pronunciation of "Shan Yunfei's" surname, "Shan," the system uses its query engine to locate the "S" group, quickly finds the index record for "Shan," and then uses the associated contact identifier to locate the complete contact information for "Shan Yunfei" in the data. The system then retrieves the corresponding contact information and makes the call to Shan Yunfei. One day, Xiao Wang's friend Xiao Li was driving Xiao Wang's car and wanted to contact Shan Yunfei. However, Xiao Li's usual pronunciation of "Shan Yunfei" was "Dan". Since two index records, 'Shan' and 'Dan', were created in the database for "Shan Yunfei", after Xiao Li entered "Dan" in the contact search box on the car screen, the system would use the query engine to locate the "D" group, quickly find the index record for "Dan", and then locate the position of "Shan Yunfei's" complete contact information in the data through the association identifier of the associated contact, and obtain the corresponding contact information to call Shan Yunfei.

[0096] Exemplary contact information processing device The above text combined Figures 1-4 The method embodiments of this application have been described in detail. The contact information processing device embodiments of this application are described in detail below. It should be understood that the descriptions of the method embodiments correspond to the descriptions of the device embodiments; therefore, any parts not described in detail can be referred to the foregoing method embodiments. Figure 5 This is a schematic diagram of a system module of a contact information processing device according to some embodiments of this application.

[0097] As shown in the figure, the contact information processing device may include an information receiving module 510, a contact identification module 520, an index creation module 530, and an information query module 540.

[0098] The information receiving module 510 is configured to receive contact information from the address book of the mobile terminal.

[0099] The contact identification module 520 is configured to identify contacts whose names contain characters with multiple pronunciations.

[0100] The index creation module 530 is configured to create multiple index records for a contact based on the contact's name information.

[0101] The information query module 540 is configured to query contact information based on the pronunciation of polyphonic characters entered by the user and according to multiple index records.

[0102] In some embodiments, the contact information includes at least the contact's name.

[0103] In some embodiments, a communication link between the vehicle terminal and the mobile terminal can be established via Bluetooth, for example, the Bluetooth Phonebook Access Protocol, to transmit contact information; data exchange and transmission between the vehicle terminal and the mobile terminal can also be achieved via wireless Wi-Fi or USB. This application does not specifically limit the specific implementation method of cross-device data transmission.

[0104] In some embodiments, the vehicle terminal may respond to the user's command to synchronize the address book, actively send a request to the mobile terminal, and receive contact information from the mobile terminal; it may also automatically push contact information from the address book to the vehicle terminal after establishing a communication connection with the mobile terminal.

[0105] In some embodiments, the contact identification module 520 is further configured to perform word segmentation processing on the contact's name information and extract the surname information from the name information. Specifically, it can identify whether the pronunciation of the first character in the contact's name information or the pronunciation of the surname is a polyphonic character, and identify contacts whose first character in their name information or the pronunciation of their surname is a polyphonic character as contacts whose name information contains polyphonic characters.

[0106] In some embodiments, a data preprocessing module is also included. The data preprocessing module is configured to preprocess the name information in the received contact information. For example, the name information to be processed can be cleaned and standardized. For example, regular expressions or string filtering functions can be used to remove interfering characters (e.g., spaces, tabs, etc.) in the contact information, and only Chinese characters, English letters and numbers can be retained for non-Chinese characters in the name information, so as to achieve the unification and standardization of contact data, ensure the standardization of name strings, provide a clean and reliable data source for the subsequent polyphonic character recognition process, avoid the influence of special characters on the polyphonic character recognition process, and ensure the accuracy of polyphonic character recognition.

[0107] In some embodiments, the contact determination module 520 is further configured to determine the structure type of the contact's surname based on the name information; and to perform word segmentation processing on the name information according to the structure type of the surname to extract the contact's surname information.

[0108] In some embodiments, the longest matching principle can be used to match polyphonic characters. This means prioritizing the matching of compound surnames, identifying polyphonic compound surnames, and then matching single-character surnames, identifying polyphonic single-character surnames. This avoids misidentifying polyphonic compound surnames as single-character surnames, ensuring the accuracy of compound surname recognition. By employing a word segmentation method that combines the structural type of the surname, contact name information containing compound surnames can be processed more robustly, laying a more reliable data foundation for the subsequent polyphonic character recognition process, thereby ensuring the accuracy of polyphonic character recognition.

[0109] In some embodiments, a polyphonic character database can be created, and polyphonic characters in name information can be identified based on the polyphonic character database.

[0110] In some embodiments, the polyphonic character data records in the polyphonic character database can be divided into single-surname polyphonic character data records and compound-surname polyphonic character data records. A single-surname polyphonic character index table and a compound-surname polyphonic character index table are constructed based on these two sets of data. The extracted string to be identified is first matched against the compound-surname polyphonic character index table to identify the polyphonic characters. Then, the unmatched information is matched against the single-surname polyphonic character index table to identify the polyphonic characters of single-surnames, avoiding misidentification of compound surnames as single-surname polyphonic characters and ensuring the accuracy of polyphonic character identification for compound surnames.

[0111] In some embodiments, the polyphonic character data records stored in the polyphonic character database can be constructed as a memory index structure. The string to be identified extracted from the name information is searched for in the polyphonic character data records stored in the polyphonic character database through the index, and matched with the polyphonic character information in the polyphonic character data records to realize the identification of the contact person whose name contains polyphonic characters.

[0112] In some embodiments, the contact identification module 520 is further configured to identify a contact whose name contains a polyphonic character based on the surname information. For example, a forward maximum matching algorithm can be used to first determine the length of the input name information, and then a corresponding matching strategy can be adopted to identify the polyphonic surname based on the result of the length determination. For example, if the length of the name information is less than 1 or empty, an empty result is returned, indicating that the surname cannot be extracted from the name information; if the length of the name information is 1, the name is directly treated as a single-character surname for polyphonic character identification; if the length of the name information is greater than or equal to 2, based on the length of the name information, the maximum window length for matching compound surnames is first determined, the maximum window length is reduced to 2 characters, and candidate strings are extracted sequentially for compound surname matching to identify polyphonic compound surnames.

[0113] In some embodiments, the index creation module 530 is further configured to, for contact information whose name information includes polyphonic characters, obtain all common pronunciations and the first letter of the pinyin for the identified polyphonic characters. For example, it can query and match all common pronunciations of polyphonic characters from a polyphonic character database. Based on the first letter of the pinyin and all common pronunciations of the polyphonic character, it constructs multiple index records for the contact person with the polyphonic character. These multiple index records together constitute a query channel from any standard pronunciation of the polyphonic character to the contact information, enabling the user to match the corresponding index record and locate the target contact information regardless of any standard pronunciation of the polyphonic character.

[0114] In some embodiments, the information query module 540 is further configured to: convert user-inputted search keywords into pinyin and the first letters of the pinyin, determine the corresponding index record based on the pinyin and / or the first letters of the pinyin, and query the corresponding contact information in the database based on the index record. The query conditions may be name information containing the keywords, the complete pinyin of the keywords, or the first letters of the keywords.

[0115] It should be understood that specific limitations regarding the apparatus can be found in the limitations regarding the method described above, and will not be repeated here. Each module in the aforementioned apparatus can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in hardware or independently of the processor in a computer device, or stored in software in the memory of a computer device, so that the processor can call and execute the operations corresponding to each module.

[0116] Exemplary electronic devices and computer-readable storage media This application also provides an electronic device, such as Figure 6 As shown. The electronic device 600 provided in this application includes a memory 610, a processor 620, and an input / output interface 630. The memory 610, processor 620, and input / output interface 630 are connected via internal connection paths. The memory 610 stores instructions, and the processor 620 executes the instructions stored in the memory 610 to control the input / output interface 630 to receive input data and information, and output operation results and other data.

[0117] It should be understood that in the embodiments of this application, the processor 620 may be a general-purpose central processing unit (CPU), GPU, FPGA, microprocessor, application-specific integrated circuit (ASIC), or one or more integrated circuits to execute related programs in order to implement the technical solutions provided in the embodiments of this application.

[0118] The memory 610 may include read-only memory and random access memory, and provides instructions and data to the processor 620. A portion of the processor 620 may also include non-volatile random access memory. For example, the processor 620 may also store device type information.

[0119] In implementation, each step of the above method can be completed by the integrated logic circuits in the hardware of the processor 620 or by instructions in software form. The method for controlling a vehicle motor disclosed in the embodiments of this application can be directly implemented by a hardware processor, or by a combination of hardware and software modules in the processor. The software modules can be located in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. This storage medium is located in memory 610, and the processor 620 reads the information in memory 6610 and completes the steps of the above method in conjunction with its hardware. To avoid repetition, it will not be described in detail here. This application also provides a computer program product, including a computer program / instructions. When the computer program / instruction processor in the computer program product provided in this application is executed, the contact information processing method provided in this application can be implemented.

[0120] All of the above-mentioned optional technical solutions can be combined in any way to form optional embodiments of this application, and will not be described in detail here.

[0121] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0122] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0123] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0124] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0125] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0126] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program verification codes, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0127] It should be noted that in the description of this application, the terms "first," "second," "third," etc., are used for descriptive purposes only and should not be construed as indicating or implying relative importance. Furthermore, in the description of this application, unless otherwise stated, "a plurality of" means two or more.

[0128] The above description is merely a preferred embodiment of this application and is not intended to limit this application. Any modifications or equivalent substitutions made within the spirit and principles of this application should be included within the protection scope of this application.

Claims

1. A method for processing contact information, characterized in that, Applied to a vehicle system, the method includes: Receive contact information from the address book of a mobile terminal, wherein the contact information includes at least the contact's name; The contact person is identified as someone whose name contains a character with multiple pronunciations. Based on the contact's name information, multiple index records are created for the contact, wherein the multiple index records correspond to multiple different pronunciations of the polyphonic character; Based on the pronunciation of the polyphonic character input by the user, the contact information is retrieved according to the multiple index records.

2. The contact information processing method according to claim 1, characterized in that, The multiple index records include multiple different pronunciations of polyphonic characters in the contact's name information and associated identifiers, wherein the associated identifiers are used to associate multiple index records of the same contact with the contact information. The method further includes: Based on the multiple different pronunciations, the multiple index records are grouped into corresponding groups to achieve multi-group coverage of index records for the same contact person. The process of querying the contact information based on the pronunciation of the polyphonic character input by the user, according to the multiple index records, includes: Based on the pronunciation of the polyphonic character, determine the group in which the index record corresponding to the pronunciation belongs; Search the index record corresponding to the pronunciation in the group; The contact information is retrieved based on the associated identifier in the index record.

3. The contact information processing method according to claim 1, characterized in that, Determining that the contact person is one whose name contains a character with multiple pronunciations includes: The name information of the contact person is processed by word segmentation to extract target information from the name information, wherein the target information is the surname part or the first character part of the name information; Based on the target information, the contact person is determined to be the contact person whose name contains a character with multiple pronunciations.

4. The contact information processing method according to claim 3, characterized in that, The target information is the surname portion of the name information. The step of performing word segmentation on the contact person's name information and extracting the target information from the name information includes: Based on the name information, determine the structure type of the contact person's surname; Based on the structure type of the surname, word segmentation is performed on the name information to extract the surname information of the contact person.

5. The contact information processing method according to claim 4, characterized in that, The determination of the structure type of the contact person's surname based on the name information includes: The length of the name information is determined by the positive maximum matching method; When the length of the name information is 1, the surname of the contact person is determined to be a single-character surname; When the length of the name information is greater than or equal to 2, the extraction window length is determined based on the length of the name information; Based on the extraction window length, candidate strings of a corresponding length are extracted from the name information, and the candidate strings are matched for compound surnames. If the match is successful, it is determined that the surname of the contact person is a compound surname; If no match is found, the extraction window length is reduced by 1, and the above steps are repeated. When the extraction window length is reduced to 2, and the matching of compound surnames is still unsuccessful, the surname of the contact person is determined to be a single-character surname.

6. The contact information processing method according to claim 5, characterized in that, After extracting candidate strings of the corresponding length from the name information, the process further includes: Based on the length of the candidate string and the length of the name information, the candidate string is subjected to boundary validity checks and Chinese character verification.

7. The contact information processing method according to claim 3, characterized in that, The target information is the surname of the given name information, and determining the contact person as having a polyphonic character in the given name information based on the target information includes: Prioritize the identification of polyphonic characters in the target information of compound surnames, and then identify polyphonic characters in the target information of single surnames, in order to determine the contact persons whose name information contains polyphonic characters.

8. The contact information processing method according to claim 1, characterized in that, The method further includes: A polyphonic character database is created, wherein the database stores polyphonic character data records including all polyphonic characters, and each polyphonic character data record includes at least one polyphonic character information and all standard pronunciations associated with that polyphonic character. The step of determining that the contact person is a contact person whose name information contains a character with multiple pronunciations includes: The name information is matched with the polyphonic character information in the polyphonic character database; The successfully matched contacts are those whose names contain characters with multiple pronunciations. The step of creating multiple index records for the contact based on the contact's name information includes: Based on the name information, determine all standard pronunciations of the polyphonic characters in the name information according to the polyphonic character database; Based on all the standard pronunciations of the polyphonic character, create multiple index records for the contact.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program for performing the contact information processing method according to any one of claims 1 to 8.

10. A vehicle, characterized in that, The vehicles include: processor; Memory used to store the processor's executable instructions. The processor is used to execute the contact information processing method according to any one of claims 1 to 8.

Images