Data transmission method, vehicle and electronic equipment

Abstract

The invention provides a data transmission method, a vehicle and electronic equipment, and relates to the technical field of automobile communication. The method comprises the following steps: sending an address book data acquisition request for an address book to a mobile terminal; receiving address book basic data returned by the mobile terminal based on the address book data acquisition request, wherein the address book basic data comprises other contact data except the contact head portrait data; sending a head portrait data acquisition request to the mobile terminal based on the address book basic data; and receiving contact head portrait data returned by the mobile terminal based on the head portrait data acquisition request. According to the embodiment of the invention, the reachable time of the vehicle address book function can be shortened, the user experience is improved, the data transmission efficiency is improved, and the data processing pressure of the vehicle is relieved.

Description

Technical Field

[0001] This application relates to the field of automotive communication technology, specifically to a data transmission method, a vehicle, and electronic equipment. Background Technology

[0002] With the rapid development of intelligent vehicle systems, more and more vehicles are equipped with them. These systems allow vehicles to communicate with mobile devices such as smartphones, transmitting data from the mobile devices to the vehicle, thus enabling data sharing between the two. For example, a vehicle can retrieve contact information from a smartphone via Bluetooth. Users can then directly access contact information through the vehicle's voice control and app search functions to make calls, significantly improving communication convenience while driving.

[0003] However, traditional contact data transmission methods primarily involve mobile devices like smartphones simultaneously transmitting all contact data to the vehicle. Consequently, the vehicle must wait for all data transmission to complete before providing contact lookup and calling functions, resulting in a longer availability time and a reduced user experience. Furthermore, this simultaneous data transmission method also leads to low data transmission efficiency. Summary of the Invention

[0004] In view of this, the embodiments of this application aim to provide a data transmission method, a vehicle, and an electronic device to solve the problems of long access time and low data transmission efficiency of the vehicle-side address book function in the prior art.

[0005] In a first aspect, one embodiment of this application provides a data transmission method applied to a vehicle. The method includes: sending a contact data acquisition request to a mobile terminal; receiving basic contact data returned by the mobile terminal based on the contact data acquisition request, wherein the basic contact data includes other contact data besides contact avatar data; sending an avatar data acquisition request to the mobile terminal based on the basic contact data; and receiving contact avatar data returned by the mobile terminal based on the avatar data acquisition request.

[0006] The data transmission method provided in this application, when the vehicle obtains contact data from the mobile terminal, first acquires basic contact data (i.e., contact data other than contact avatar data), and then acquires contact avatar data, thus achieving asynchronous acquisition of basic contact data and contact avatar data based on a chronological order. This asynchronous acquisition allows the vehicle to provide contact functions such as contact query and contact calling to the user immediately after acquiring the basic contact data, without waiting for all contact avatar data to be acquired. This shortens the time to access the vehicle's contact function, reduces user waiting time, and improves user experience. Furthermore, the phased data transmission reduces the amount of data transmitted in a single transmission, avoiding data transmission congestion caused by excessively large data volumes in traditional synchronous data transmission methods. Therefore, it ensures smooth data transmission and improves data transmission efficiency. In addition, by asynchronously acquiring basic contact data and contact avatar data based on a chronological order, it also facilitates sequential scheduling of the vehicle using the same communication link, reducing the complexity of coordination between multiple communication links. For vehicle systems with limited memory and computing resources, this alleviates the data processing pressure on the vehicle.

[0007] In conjunction with the first aspect, in some implementations of the first aspect, the contact data acquisition request includes avatar request identification information, and the basic contact data also includes avatar identification information corresponding to the contact returned by the mobile terminal based on the avatar request identification information. The avatar identification information is used to indicate whether there is avatar data corresponding to the contact in the mobile terminal. Accordingly, based on the basic contact data, sending an avatar data acquisition request to the mobile terminal includes: determining that the avatar identification information is the target contact of the target information, the target information being used to indicate that there is avatar data of the contact in the mobile terminal; and sending an avatar data acquisition request for the target contact to the mobile terminal.

[0008] In this way, by retrieving contact avatar data from target contacts with avatars, the efficiency of avatar data acquisition can be improved, and unnecessary data requests and transmissions can be reduced, thereby further improving data transmission efficiency. Furthermore, by adding avatar request identifier information to the contact data retrieval request and adding avatar identifier information to the basic contact data, it is possible to extend existing parameters of existing communication protocols (such as PropertySelector parameters based on Bluetooth PBAP) with new fields, thus without modifying the underlying architecture of existing communication protocols. This allows for broad adaptation to existing mobile terminals and in-vehicle systems, demonstrating good versatility and scalability.

[0009] In conjunction with the first aspect, in some implementations of the first aspect, sending a request to the mobile terminal to obtain the avatar data of the target contact includes: obtaining contact identification information corresponding to the target contact; and sending a request to the mobile terminal to obtain the avatar data of the target contact based on the contact identification information corresponding to the target contact.

[0010] In this way, by setting contact identification information for a contact and using the contact identification information to send a request to the mobile terminal to obtain the avatar data of the target contact, targeted avatar data acquisition can be achieved, improving the convenience and accuracy of obtaining avatar data from target contacts with avatars.

[0011] In conjunction with the first aspect, in some implementations of the first aspect, after receiving the basic address book data returned by the mobile terminal based on the address book data retrieval request, the method further includes: extracting contact name information, contact communication information, and avatar identification information from the basic address book data, and determining the contact identification information; and storing the contact identification information, contact name information, contact communication information, and avatar identification information in the database accordingly. Correspondingly, after receiving the contact avatar data returned by the mobile terminal based on the avatar data retrieval request, the method further includes: storing the contact avatar data in the database at the avatar data storage location corresponding to the target contact, based on the contact identification information corresponding to the target contact.

[0012] In this way, by storing the relevant data of the contacts in the address book in a structured manner and storing the contact avatar data in the database asynchronously, it is not only convenient for the vehicle to manage and query the address book data, but also provides a solid foundation for the vehicle to implement the core address book function before obtaining complete contact avatar data.

[0013] In conjunction with the first aspect, in some implementations of the first aspect, after receiving the basic address book data returned by the mobile terminal based on the address book data acquisition request, the method further includes: in response to a communication request instruction for a first contact, obtaining contact communication information corresponding to the first contact from the basic address book data, wherein the first contact is any contact in the address book; and sending a communication request to the first contact based on the contact communication information corresponding to the first contact.

[0014] In this way, once the vehicle receives the basic contact data returned by the mobile terminal, the contact function can be provided normally, which can shorten the time it takes for the vehicle's contact function to become available, reduce the user's waiting time, and thus improve the user experience.

[0015] Secondly, one embodiment of this application provides a data transmission method applied to a mobile terminal. The method includes: receiving a contact data retrieval request sent by a vehicle for a contact list; responding to the contact data retrieval request, sending basic contact list data to the vehicle, the basic contact list data including other contact data besides contact avatar data; receiving an avatar data retrieval request sent by the vehicle based on the basic contact list data; and responding to the avatar data retrieval request, sending contact avatar data to the vehicle.

[0016] The data transmission method provided in this application asynchronously sends basic contact data (i.e., all contact data except for contact avatars) first, and then sends the contact avatars, when sending contact data from a mobile terminal to a vehicle. This asynchronous transmission allows the vehicle to provide contact lookup and calling functions to the user immediately after the mobile terminal completes the transmission of the basic contact data, without waiting for all contact avatars to be sent. This shortens the time to access vehicle contact functions, reduces user waiting time, and improves user experience. Furthermore, the phased data transmission reduces the amount of data transmitted in a single transmission, avoiding data congestion caused by excessive data volume in traditional synchronous transmission methods. This ensures smooth data transmission and improves efficiency. Moreover, asynchronously sending basic contact data and contact avatars based on time sequence facilitates sequential transmission using the same communication link, reducing the complexity of coordination between multiple communication links. This alleviates data processing pressure on mobile terminal systems with limited memory and computing resources.

[0017] In conjunction with the second aspect, in some implementations of the second aspect, the contact data acquisition request includes avatar request identification information. Accordingly, sending basic contact data to the vehicle includes: based on the avatar request identification information, querying whether there is avatar data corresponding to the contact in the contact list, and obtaining the query result; determining the avatar identification information corresponding to the contact based on the query result; and sending the basic contact data containing the avatar identification information to the vehicle.

[0018] In this way, the mobile terminal queries the address book to see if there is a corresponding contact's profile picture data. Based on the query results, it determines the profile picture identifier information corresponding to the contact, and then sends the basic address book data containing the profile picture identifier information to the vehicle. This allows the vehicle to easily determine which contacts have profile pictures based on the profile picture identifier information, and then perform targeted acquisition of contact profile picture data. This can improve the efficiency of profile picture data acquisition and reduce unnecessary data requests and transmissions, thereby further improving data transmission efficiency.

[0019] In conjunction with the second aspect, in some implementations of the second aspect, the avatar data acquisition request includes contact identification information corresponding to the target contact. Accordingly, sending contact avatar data to the vehicle includes: acquiring contact avatar data corresponding to the target contact based on the contact identification information; and sending the contact avatar data corresponding to the target contact to the vehicle.

[0020] In this way, by using contact identification information to specifically obtain the contact image data corresponding to the target contact, and sending the contact image data of the target contact to the vehicle, targeted image data sending is achieved, which improves the convenience and accuracy of obtaining image data of target contacts with images.

[0021] Thirdly, one embodiment of this application provides a data transmission device applied to a vehicle. The device includes: a first request module, configured to send a contact data retrieval request to a mobile terminal; a first receiving module, configured to receive basic contact data returned by the mobile terminal based on the contact data retrieval request, wherein the basic contact data includes other contact data besides contact avatar data; a second request module, configured to send an avatar data retrieval request to the mobile terminal based on the basic contact data; and a second receiving module, configured to receive contact avatar data returned by the mobile terminal based on the avatar data retrieval request.

[0022] Fourthly, one embodiment of this application provides a data transmission apparatus applied to a mobile terminal. The apparatus includes: a third receiving module for receiving a contact data retrieval request sent by a vehicle; a first sending module for sending basic contact data to the vehicle in response to the contact data retrieval request, the basic contact data including other contact data besides contact avatar data; a fourth receiving module for receiving an avatar data retrieval request sent by the vehicle based on the basic contact data; and a second sending module for sending contact avatar data to the vehicle in response to the avatar data retrieval request.

[0023] Fifthly, one embodiment of this application provides a vehicle, the vehicle comprising: a first processor; a first memory for storing instructions executable by the first processor; the first processor being configured to execute the data transmission method described in the first aspect.

[0024] In a sixth aspect, one embodiment of this application provides an electronic device, the electronic device comprising: a second processor; a second memory for storing instructions executable by the second processor; the second processor being configured to execute the data transmission method described in the second aspect.

[0025] In a seventh aspect, one embodiment of this application provides a computer-readable storage medium storing a computer program for performing the data transmission method described in the first or second aspect.

[0026] Eighthly, one embodiment of this application provides a computer program product including instructions that, when executed on an electronic device, cause the electronic device to implement the data transmission method described in the first or second aspect. Attached Figure Description

[0027] The above and other objects, features, and advantages of this application will become more apparent from the more detailed description of the embodiments of this application in conjunction with the accompanying drawings. The drawings are provided to further illustrate the embodiments of this application and form part of the specification. They are used together with the embodiments of this application to explain this application and do not constitute a limitation thereof. In the drawings, the same reference numerals generally represent the same components or steps.

[0028] Figure 1 The diagram shown is a flowchart of a data transmission method provided in an embodiment of this application.

[0029] Figure 2 The diagram shown is a flowchart of a data transmission method provided in another embodiment of this application.

[0030] Figure 3 The diagram shown is an architectural schematic of an in-vehicle system provided in an embodiment of this application.

[0031] Figure 4 The diagram shown is an architectural schematic of a mobile terminal system provided in an embodiment of this application.

[0032] Figure 5 The diagram shown is a flowchart of a data transmission method provided in another embodiment of this application.

[0033] Figure 6 The diagram shown is a structural schematic of a data transmission device provided in an embodiment of this application.

[0034] Figure 7The diagram shown is a structural schematic of a data transmission device provided in another embodiment of this application.

[0035] Figure 8 The diagram shown is a structural schematic of an electronic device provided in an embodiment of this application. Detailed Implementation

[0036] 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.

[0037] Furthermore, to better illustrate this application, numerous specific details are provided in the following detailed embodiments. Those skilled in the art should understand that this application can be implemented even without certain specific details. In some instances, methods and means well-known to those skilled in the art have not been described in detail in order to highlight the main points of this application.

[0038] It should be noted that similar labels and letters in the following figures indicate similar items. Therefore, once an item is defined in one figure, it does not need to be further defined and explained in subsequent figures.

[0039] Furthermore, the terms “first,” “second,” “third,” and “fourth” are used only for distinguishing descriptions and should not be interpreted as indicating or implying relative importance.

[0040] In related technologies, vehicles and mobile terminals such as smartphones can establish a connection via Bluetooth. After a successful Bluetooth connection, the vehicle can obtain contact data from the mobile terminal based on the Phone Book Access Profile (PBAP). Users can then directly access contact information within the vehicle to make calls through voice control, application search, and other methods, greatly improving the convenience of communication while driving. However, with the widespread adoption of smart mobile terminals, the amount of contact data in mobile terminal address books is growing rapidly. Especially when a large number of contacts include profile pictures, existing data transmission methods reveal significant shortcomings. During PBAP-based data transmission, basic contact data (such as name and phone number) and profile picture data are usually transmitted simultaneously. Since profile picture data is multimedia data, its volume is far greater than that of basic text information, leading to a significant increase in overall data download time. Actual testing shows that if a mobile terminal stores 1000 contacts, all with profile pictures, it takes more than one minute for the vehicle to complete the entire data download. During this lengthy download period, the vehicle cannot provide contact lookup and calling services to users because it has not obtained complete contact data. For example, if a user immediately calls Zhang San via voice command after connecting their phone to the vehicle via Bluetooth, the operation will fail because the vehicle's database does not contain the corresponding contact information. This "data acquisition vacuum period" after a successful connection severely impacts the user experience and violates the core requirements of "convenience and efficiency" for in-vehicle Bluetooth communication. Furthermore, because traditional data synchronization methods require transmitting all contact data at once, the amount of data transmitted in a single step is excessively large, easily causing data transmission congestion and resulting in low data transmission efficiency.

[0041] In summary, existing technologies lack asynchronous transmission strategies for contact basic information and profile picture data, making it impossible to complete data synchronization while ensuring the priority availability of core address book functions. Therefore, an optimized address book data acquisition solution is urgently needed.

[0042] Based on this, and to solve the aforementioned technical problems, this application provides a data transmission method, a vehicle, and an electronic device. In this data transmission method, when the vehicle obtains contact data from a mobile terminal, it first obtains basic contact data (i.e., contact data excluding contact avatars) and then obtains the contact avatars, thus achieving asynchronous acquisition of basic contact data and contact avatars based on their temporal order. This asynchronous acquisition of basic contact data and contact avatars allows the vehicle to provide contact functions such as contact lookup and contact calling to the user immediately after obtaining the basic contact data, without waiting for all contact avatars to be acquired. This shortens the time required for the vehicle's contact function to be available, reduces user waiting time, and improves user experience. Furthermore, since the phased data transmission reduces the amount of data transmitted in a single transmission, it avoids data transmission congestion caused by excessively large data volumes in traditional synchronous data transmission methods. Therefore, it ensures smooth data transmission and improves data transmission efficiency. Furthermore, by asynchronously acquiring basic address book data and contact avatar data based on time sequence, it is also convenient for vehicles to use the same communication link for sequential scheduling, reducing the complexity of coordination between multiple communication links. For vehicle systems with limited memory and computing resources, this can alleviate the data processing pressure on the vehicle.

[0043] The following is combined Figures 1 to 5 The data transmission method provided in this application is described in detail.

[0044] Figure 1 The diagram shown is a schematic flowchart of a data transmission method provided in an embodiment of this application. This method can be applied to vehicles. Figure 1 As shown, the method may include the following steps.

[0045] S110, send a request to the mobile terminal to retrieve contact data from the contact list.

[0046] In some examples, the mobile terminal can be an electronic device such as a mobile phone, tablet, or smart wearable device that communicates with the vehicle. This electronic device can wirelessly access the network and has independent processing capabilities. The mobile terminal may store an address book, which may contain information about at least one contact. The contact information may include the contact's name, phone number, and possibly a photo.

[0047] For example, before sending a request to retrieve contact data to a mobile terminal, the vehicle can establish a communication connection with the mobile terminal via Bluetooth and implement an application-layer connection based on PBAP to ensure that the vehicle and the mobile terminal have the ability to interact with each other. Specifically, the user turns on the vehicle's Bluetooth and pairs it with the mobile phone. After the Bluetooth connection between the two parties is established, the vehicle automatically triggers a PBAP connection request. After the mobile phone responds, the PBAP connection is completed. At this time, the vehicle is the client and the mobile phone is the server.

[0048] Furthermore, after establishing a communication connection with the mobile terminal, the vehicle, acting as a client in PBAP, can construct a contact data retrieval request and send it to the mobile terminal via Bluetooth. This contact data retrieval request can take the form of a data packet requesting contact information from the address book. The PropertySelector parameter of this request packet can include flags indicating the requested contact's "name," "phone number," or other basic contact data. By setting these flags to 1, the vehicle requests this information from the mobile terminal.

[0049] It should be noted that, in addition to Bluetooth, data can also be transmitted between the vehicle and the mobile terminal via other communication methods such as Wi-Fi hotspots, which are not limited here.

[0050] S120, Receive basic contact data returned by the mobile terminal based on the contact data acquisition request. The basic contact data includes other contact data except for the contact's avatar data.

[0051] In some examples, the basic contact data can be data that enables the vehicle to provide normal contact functions such as contact lookup and contact calling. This basic contact data may include contact names, phone numbers, etc., but does not include contact avatar data.

[0052] For example, after a vehicle sends a contact data retrieval request to a mobile terminal, the mobile terminal can encapsulate basic contact data such as contact names and phone numbers into a response data packet according to the contact data retrieval request, and send the response data packet to the vehicle. After receiving the response data packet, the vehicle can parse the basic contact data and obtain other contact data such as contact names and phone numbers, except for contact avatar data.

[0053] Furthermore, since in PBAP-based Bluetooth communication, a vehicle can only retrieve data for one contact at a time, the vehicle can, according to the execution logic of steps S110 to S120 above, cyclically send contact data retrieval requests to the mobile terminal for each contact in the mobile terminal's address book, and receive the basic contact data for each contact, until the basic contact data for all contacts in the address book is retrieved. Of course, in other communication methods, the vehicle can also retrieve the basic contact data for all contacts in the mobile terminal's address book with a single request; this is not limited here.

[0054] It should be noted that once the vehicle obtains the basic contact information, it can provide contact functions such as contact search and contact calling.

[0055] Based on this, in some embodiments, after step S120 above, the method may further include: in response to a communication request instruction for a first contact, obtaining contact communication information corresponding to the first contact from the basic data of the address book, wherein the first contact is any contact in the address book; and sending a communication request to the first contact based on the contact communication information corresponding to the first contact.

[0056] In some examples, the communication request instruction can be an instruction to perform communication operations such as information retrieval or calling the first contact. This communication request instruction can be triggered by the user, and user triggering methods include, but are not limited to, voice input triggering and vehicle screen button triggering. The communication request instruction can also be an instruction automatically generated by the vehicle, such as when the vehicle automatically generates a communication request instruction for the first contact in a specific emergency situation. The communication request instruction can also be a received instruction sent from a mobile terminal; for example, a user triggers a communication request for the first contact on a mobile terminal, which then sends the communication request to the vehicle, triggering the generation of the communication request instruction for the first contact.

[0057] Additionally, contact information can be information that enables communication with the contact person, such as a phone number. The vehicle can send a communication request to the first contact person using the contact information corresponding to that first contact, for example, by dialing the first contact person's phone number.

[0058] For example, after obtaining basic contact information, if the vehicle receives the user's voice input "Call Zhang San", the vehicle can query the phone number of the contact "Zhang San" from the obtained basic contact information, and then call the contact "Zhang San" by dialing the phone number of the contact "Zhang San".

[0059] In this way, once the vehicle receives the basic contact data returned by the mobile terminal, the contact function can be provided normally, which can shorten the time it takes for the vehicle's contact function to become available, reduce the user's waiting time, and thus improve the user experience.

[0060] S130 sends a request to the mobile terminal to obtain avatar data based on the contact list data.

[0061] For example, after receiving basic contact data, the vehicle can initiate an asynchronous task in the background to construct a profile picture data retrieval request and continue sending the request to the mobile terminal based on the previously established communication connection. This profile picture data retrieval request can be used to request the retrieval of contact profile picture data. The format of this request could be, for example, a request data packet for contact profile picture data in the contact list, which could be a PBAP-based request data packet.

[0062] S140, Receive the contact avatar data returned by the mobile terminal based on the avatar data acquisition request.

[0063] In some examples, contact avatar data can be based on image data in a specific image format, such as JPEG or JPG. This contact avatar data can be the image data corresponding to the avatar set for the contact on the mobile device.

[0064] For example, after a vehicle sends a request to a mobile terminal to obtain avatar data, the mobile terminal can obtain the contact's avatar data according to the request, encapsulate the contact's avatar data into a response data packet, and send the response data packet to the vehicle. After receiving the response data packet, the vehicle can parse and obtain the contact's avatar data.

[0065] Furthermore, since in PBAP-based Bluetooth communication, a vehicle can only retrieve data for one contact at a time, the vehicle can, according to the execution logic of steps S130 to S140 above, cyclically send a request to the mobile terminal to retrieve the avatar data for each contact in the mobile terminal's address book, and receive the avatar data for each contact, until the avatar data for all contacts in the address book is retrieved. Of course, in other communication methods, the vehicle can also retrieve the avatar data for all contacts in the mobile terminal's address book with a single request; this is not limited here.

[0066] The data transmission method provided in this application, when the vehicle obtains contact data from the mobile terminal, first acquires basic contact data (i.e., contact data other than contact avatar data), and then acquires contact avatar data, thus achieving asynchronous acquisition of basic contact data and contact avatar data. This asynchronous acquisition allows the vehicle to provide contact functions such as contact query and contact calling to the user immediately after acquiring the basic contact data, without waiting for all contact avatar data to be acquired. This shortens the access time for vehicle contact functions, reduces user waiting time, and improves user experience. Furthermore, since phased data transmission reduces the amount of data transmitted in a single transmission, it avoids data transmission congestion caused by excessively large data transmission volumes in traditional synchronous data transmission methods. Therefore, it ensures smooth data transmission and improves data transmission efficiency. In addition, by asynchronously acquiring basic contact data and contact avatar data based on time sequence, it also facilitates sequential scheduling of the vehicle using the same communication link, reducing the complexity of coordination between multiple communication links. For vehicle systems with limited memory and computing resources, this alleviates the data processing pressure on the vehicle.

[0067] In addition, since not all contacts have profile pictures in real-world scenarios, in order to improve the efficiency of obtaining profile picture data, we can obtain the profile picture data of contacts who have profile pictures.

[0068] Based on this, in some other embodiments of this application, the aforementioned contact data acquisition request includes avatar request identification information, and the contact basic data also includes avatar identification information corresponding to the contact returned by the mobile terminal based on the avatar request identification information. The avatar identification information is used to indicate whether there is avatar data of the contact corresponding to the contact in the mobile terminal. Accordingly, the aforementioned step S130 (sending an avatar data acquisition request to the mobile terminal based on the contact basic data) may specifically include: determining that the avatar identification information is the target contact of the target information, the target information being used to indicate that there is avatar data of the contact in the mobile terminal; and sending an avatar data acquisition request for the target contact to the mobile terminal.

[0069] In some examples, the avatar request identifier information can be an identifier bit that indicates a request to retrieve the avatar identifier information corresponding to a contact. Specifically, the avatar identifier information can be information used to indicate whether contact avatar data corresponding to the contact exists in the mobile terminal, such as indicating whether the contact "supports avatars," that is, whether the contact has corresponding avatar data.

[0070] For example, in a PBAP-based Bluetooth connection, when the vehicle constructs a request to obtain contact data, in addition to setting an identifier in the PropertySelector parameter of the request data packet for requesting basic contact data such as "name" and "phone number", an identifier can also be set for requesting the avatar information corresponding to the contact. For example, the 32nd bit in the PropertySelector parameter can be preset as the identifier for "whether avatar is supported". By setting this identifier to 1, it can be indicated that the information corresponding to the "whether avatar is supported" field is requested.

[0071] After the vehicle sends a contact data retrieval request containing the avatar request identifier (such as a value of 1 in the "Avatar Support?" flag) to the mobile terminal, the mobile terminal can sequentially query each contact in the contact list (or the current contact targeted by the contact data retrieval request) to see if it has avatar data, and generate avatar identifier information based on the query results. For example, for contacts without avatars, an avatar identifier of "Avatar Support: No" can be generated; for contacts with avatars, an avatar identifier of "Avatar Support: Yes" can be generated.

[0072] After generating avatar identification information, the mobile terminal can return basic contact data containing that avatar identification information to the vehicle. The vehicle can then parse the avatar identification information from the basic contact data to determine which contacts have avatars and which do not. For target contacts with avatars, the vehicle can further request their avatar data from the mobile terminal.

[0073] In some examples, the target contact can be a contact with a profile picture, that is, a contact whose profile picture identification information is the target information. The target information can be information that can characterize the existence of a contact's profile picture data on the mobile terminal, such as "Does it support profile pictures: Yes". For example, if the profile picture identification information corresponding to a certain contact is "Does it support profile pictures: Yes", then the contact can be determined as the target contact, and the vehicle can then send a request to the mobile terminal to obtain the profile picture data of the target contact.

[0074] Specifically, the vehicle can start a background thread to execute a query statement to find the target contacts whose avatar identification information is the target information (such as the value of "Does it support avatars" being "yes"). It can then obtain a list of target contacts that only contain the target contacts, and for each target contact in the list, it can construct a request data packet that only requests the contact's avatar data and send the request to the mobile terminal.

[0075] It should be noted that, in PBAP-based Bluetooth communication, a vehicle can only retrieve data for one contact at a time. Therefore, the vehicle can sequentially send a request to the mobile terminal for each target contact in the target contact list, and receive the contact image data for each target contact, until the contact image data for all target contacts in the target contact list is retrieved. Of course, in other communication methods, the vehicle can also retrieve the contact image data for all target contacts in the target contact list with a single request; this is not limited to this method.

[0076] In this way, by retrieving contact avatar data from target contacts with avatars, the efficiency of avatar data acquisition can be improved, and unnecessary data requests and transmissions can be reduced, thereby further improving data transmission efficiency. Furthermore, by adding avatar request identifier information to the contact data retrieval request and adding avatar identifier information to the basic contact data, it is possible to extend existing parameters of existing communication protocols (such as PropertySelector parameters based on Bluetooth PBAP) with new fields, thus without modifying the underlying architecture of existing communication protocols. This allows for broad adaptation to existing mobile terminals and in-vehicle systems, demonstrating good versatility and scalability.

[0077] Furthermore, it should be noted that the data interaction of the above PBAP is based on the Object Exchange (OBEX) protocol. The request data packets sent by the vehicle and the response data packets returned by the mobile terminal both conform to the request-response interaction specification of the OBEX protocol. The newly added "whether to support avatars" field can be implemented by extending the PropertySelector parameter of PBAP. This field can occupy the preset bits in the 64-bit attribute identifier, thereby ensuring protocol compatibility.

[0078] In addition, to facilitate the querying and retrieval of data corresponding to each contact, a corresponding contact identification information, such as a contact number, can be set for each contact, and then the data can be queried and retrieved using this contact identification information.

[0079] Based on this, in some other embodiments of this application, the above-mentioned sending a request to the mobile terminal to obtain the avatar data of the target contact may specifically include: obtaining contact identification information corresponding to the target contact; and sending a request to the mobile terminal to obtain the avatar data of the target contact based on the contact identification information corresponding to the target contact.

[0080] In some examples, contact identification information can be information that uniquely identifies a contact, such as a contact number. For instance, in PBAP-based Bluetooth communication, each contact can be numbered according to the order in which their corresponding address book basic data is received. For example, if the first address book basic data received by the vehicle is for contact "Zhang San," then the number corresponding to contact "Zhang San" can be set to "1"; if the second address book basic data received by the vehicle is for contact "Li Si," then the number corresponding to contact "Li Si" can be set to "2," and so on. Correspondingly, the mobile terminal also records the order of each contact when sending their corresponding address book basic data, and then numbers each contact according to the same numbering rule.

[0081] Based on this, after determining the list of target contacts with profile pictures, the vehicle can obtain the contact identification information (such as number) corresponding to each target contact. Based on the contact identification information, the vehicle can construct a targeted profile picture data acquisition request. The request may include the contact identification information corresponding to the target contact in order to request the acquisition of the contact profile picture data of the target contact corresponding to the contact identification information.

[0082] In this way, by setting contact identification information for a contact and using the contact identification information to send a request to the mobile terminal to obtain the avatar data of the target contact, targeted avatar data acquisition can be achieved, improving the convenience and accuracy of obtaining avatar data from target contacts with avatars.

[0083] In addition, to facilitate the management and retrieval of contact data in vehicles, the contact-related data obtained from mobile terminals can be stored in a structured manner.

[0084] Based on this, in some other embodiments of this application, after step S120 (receiving basic contact data returned by the mobile terminal based on the contact data acquisition request), the method further includes: extracting contact name information, contact communication information, and avatar identification information from the basic contact data, and determining the contact identification information; storing the contact identification information, contact name information, contact communication information, and avatar identification information in the database accordingly. Additionally, after step S140 (receiving contact avatar data returned by the mobile terminal based on the avatar data acquisition request), the method further includes: storing the contact avatar data in the database at the avatar data storage location corresponding to the target contact, based on the contact identification information corresponding to the target contact.

[0085] In some examples, the contact name information may be at least one of the contact's name, nickname, alias, etc. The contact communication information and avatar identification information have been explained in the previous embodiments and will not be repeated here. Furthermore, the method for determining the contact identification information may be based on the order in which the basic address book data was received; details can be found in the relevant content of the previous embodiments and will not be repeated here.

[0086] In some examples, the vehicle may store contact identification information, contact name information, contact communication information, and avatar identification information in a structured manner. The database may be a structured database, such as an SQLite database.

[0087] For example, after receiving the basic contact data, the vehicle can extract the contact's name, phone number, and "whether a profile picture is supported" field from the basic contact data, and store the above information in a local database in conjunction with the corresponding number for each contact. The storage format of the contact-related data in the database can be as shown in Table 1 below.

[0088] Table 1 When the value of the "Whether to support avatars" field is "No", the value of the "Avatar Data" field is left blank; when the value of the "Whether to support avatars" field is "Yes", the value of the "Avatar Data" field is temporarily stored as a placeholder and will be added later.

[0089] After the vehicle completes the acquisition and storage of basic contact data for all contacts in the address book, the vehicle's local database already contains basic information such as complete contact names and phone numbers from the mobile terminal's address book. Only the "avatar data" field for some contacts is missing, but this does not affect the user's ability to trigger the core address book function of making calls through voice calls, contact searches, etc. on the vehicle.

[0090] Furthermore, after the vehicle receives the contact avatar data of the target contacts (such as "Li Si" and "Xie Wu" in Table 1 above), it can match the corresponding records in the local database according to the contact identifier information of the target contact (such as numbers "2" and "3"), and store the contact avatar data in the corresponding avatar data storage location. For example, for Table 1 above, the contact avatar data of "Li Si" is written to the field value position corresponding to the "avatar data" field in the data record corresponding to number "2", and the contact avatar data of "Xie Wu" is written to the field value position corresponding to the "avatar data" field in the data record corresponding to number "3". In this way, the vehicle can realize the complete acquisition and storage process of contact data with avatars. In addition, since the vehicle's local database adopts a structured storage method, an index with "number" as the primary key is established for the relevant data of the contacts, which can ensure fast matching and writing when storing contact avatar data.

[0091] In this way, by storing the relevant data of the contacts in the address book in a structured manner and storing the contact avatar data in the database asynchronously, it is not only convenient for the vehicle to manage and query the address book data, but also provides a solid foundation for the vehicle to implement the core address book function before obtaining complete contact avatar data.

[0092] Based on the above embodiments describing the data transmission method executed on the vehicle side, the data transmission method executed on the mobile terminal side will now be described in detail.

[0093] Figure 2 The diagram shown is a schematic flowchart of a data transmission method provided in another embodiment of this application. This method can be applied to a mobile terminal, such as a mobile phone, tablet computer, smart wearable device, or other electronic device. Figure 2 As shown, the method may include the following steps.

[0094] S210 receives a request from the vehicle to retrieve contact data from the contact list.

[0095] In some examples, the mobile terminal may have an address book that can include information about multiple contacts, such as their names, phone numbers, and profile pictures.

[0096] For example, taking Bluetooth communication as an example, after the vehicle and the mobile terminal establish a Bluetooth connection, the mobile terminal, as the server in PBAP, can receive the contact data retrieval request sent by the vehicle for the contact book, so as to obtain basic contact data in the mobile terminal, such as basic information such as name and phone number other than the contact's avatar.

[0097] S220, in response to a request to obtain contact data, sends basic contact data to the vehicle, which includes contact data other than contact photos.

[0098] For example, after receiving a contact data retrieval request from a vehicle, the mobile terminal can parse the request data packet of the contact data retrieval request, traverse the contact list in the local contact book, query and retrieve the basic contact data corresponding to each contact, such as the contact name, phone number and other basic information, and construct the basic contact data into a response data packet and send it to the vehicle.

[0099] In some embodiments, the above-mentioned contact data acquisition request may include avatar request identification information. Accordingly, the step S220 of sending basic contact data to the vehicle may specifically include: querying whether there is avatar data corresponding to a contact in the contact list based on the avatar request identification information, and obtaining the query result; determining the avatar identification information corresponding to the contact based on the query result; and sending the basic contact data containing the avatar identification information to the vehicle.

[0100] For example, if the mobile terminal parses the avatar request identifier information from the received contact data retrieval request, such as setting the "whether avatars are supported" flag to 1 in the PropertySelector parameter of the request data packet, then it can query whether each contact (or the current contact targeted by the contact data retrieval request) has an avatar when traversing the contact list, i.e., whether corresponding contact avatar data exists. If the contact has an avatar, then the avatar identifier information corresponding to the contact can be determined as the target information, for example, by adding a "whether avatars are supported" field to the response data packet and marking its value as "yes"; conversely, if the contact does not have an avatar, then the avatar identifier information corresponding to the contact can be determined as other information, for example, by adding a "whether avatars are supported" field to the response data packet and marking its value as "no".

[0101] After determining the avatar identification information corresponding to a contact, the mobile terminal can encapsulate the avatar request identification information of that contact, along with basic information such as the contact's name and phone number, into a response data packet, and then send the response data packet to the vehicle as basic address book data.

[0102] In some specific examples, after receiving a request to retrieve contact data, the mobile terminal can iterate through its local contact list. For contacts without profile pictures (such as "Zhang San," number 12345678901), it generates a response data packet in vCard format containing "Name: Zhang San," "Number: 12345678901," and "Supports profile picture: No." For contacts with profile pictures (such as "Li Si," number 01987654321), it generates a response data packet in vCard format containing "Name: Li Si," "Number: 01987654321," and "Supports profile picture: Yes," without attaching the actual profile picture data. The mobile terminal then sends the generated response data packet to the vehicle so that the vehicle can retrieve the data contained within.

[0103] In this way, the mobile terminal queries the address book to see if there is a corresponding contact's profile picture data. Based on the query results, it determines the profile picture identifier information corresponding to the contact, and then sends the basic address book data containing the profile picture identifier information to the vehicle. This allows the vehicle to easily determine which contacts have profile pictures based on the profile picture identifier information, and then perform targeted acquisition of contact profile picture data. This can improve the efficiency of profile picture data acquisition and reduce unnecessary data requests and transmissions, thereby further improving data transmission efficiency.

[0104] S230 receives a request from the vehicle to obtain avatar data based on the contact list.

[0105] For example, after the mobile terminal sends the basic contact data of all contacts in the address book to the vehicle, it can receive a request to obtain the avatar data asynchronously sent by the vehicle, so as to further obtain the avatar data of the contacts.

[0106] S240, in response to the request to obtain avatar data, sends the avatar data of the contact person to the vehicle.

[0107] For example, after receiving a request to obtain avatar data, the mobile terminal can extract the avatar data of the corresponding contact and send the avatar data to the vehicle.

[0108] In some embodiments, the avatar data acquisition request may include contact identification information corresponding to the target contact. Accordingly, sending the contact avatar data to the vehicle in step S240 may specifically include: acquiring the contact avatar data corresponding to the target contact based on the contact identification information; and sending the contact avatar data corresponding to the target contact to the vehicle.

[0109] In some examples, the target contact can be a contact with a profile picture.

[0110] For example, a mobile terminal can obtain the request data packet corresponding to the request by parsing the avatar data, extract the contact identification information, such as the contact number, and then extract the contact avatar data of the target contact with the avatar based on the contact identification information, and send the contact avatar data as a response data packet to the vehicle.

[0111] In this way, by using contact identification information to specifically obtain the contact image data corresponding to the target contact, and sending the contact image data of the target contact to the vehicle, targeted image data sending is achieved, which improves the convenience and accuracy of obtaining image data of target contacts with images.

[0112] It should be noted that for the parts of the mobile terminal-side embodiments not described in detail, please refer to the relevant parts of the aforementioned vehicle-side embodiments, which will not be repeated here.

[0113] The data transmission method provided in this application asynchronously sends basic contact data (i.e., all contact data except for contact avatars) first, and then sends the contact avatars, when sending contact data from a mobile terminal to a vehicle. This asynchronous transmission allows the vehicle to provide contact lookup and calling functions to the user immediately after the mobile terminal completes the transmission of the basic contact data, without waiting for all contact avatars to be sent. This shortens the time to access vehicle contact functions, reduces user waiting time, and improves user experience. Furthermore, the phased data transmission reduces the amount of data transmitted in a single transmission, avoiding data congestion caused by excessive data volume in traditional synchronous transmission methods. This ensures smooth data transmission and improves efficiency. Moreover, asynchronously sending basic contact data and contact avatars based on time sequence facilitates sequential transmission using the same communication link, reducing the complexity of coordination between multiple communication links. This alleviates data processing pressure on mobile terminal systems with limited memory and computing resources.

[0114] Based on the above embodiments, the following is combined with Figure 3 and Figure 4 To illustrate the system architecture used in the embodiments of this application, a specific example will be given.

[0115] Figure 3 The diagram shown is an architectural schematic of an in-vehicle system provided in one embodiment of this application. This in-vehicle system can be configured in a vehicle.

[0116] like Figure 3As shown, the vehicle-mounted system 300 may include a first Bluetooth communication unit 301, a PBAP processing unit 302, an asynchronous task scheduling unit 303, and a data storage unit 304. The first Bluetooth communication unit 301 is used to establish a wireless communication connection with the mobile terminal and to transmit data based on this wireless communication connection. The PBAP processing unit 302 is used to construct request data packets, parse response data packets, and extend protocol fields. The asynchronous task scheduling unit 303 is used to initiate and manage the request and update tasks for contact avatar data in the vehicle background. The data storage unit 304 is used to store relevant contact data, such as basic address book data and contact avatar data.

[0117] Figure 4 The diagram shown is an architectural schematic of a mobile terminal system provided in an embodiment of this application.

[0118] like Figure 4 As shown, the mobile terminal system 400 may include a second Bluetooth communication unit 401, a PBAP service unit 402, and a contact data management unit 403. The second Bluetooth communication unit 401 is used to establish a wireless communication connection with the vehicle and to transmit data based on this wireless communication connection. The PBAP service unit 402 is used to receive vehicle requests and generate responses according to protocol specifications. The contact data management unit 403 is used to parse relevant contact data, determine whether a profile picture exists, and extract the corresponding contact profile picture data.

[0119] Based on the above embodiments, the following is combined with Figure 5 To better illustrate the specific implementation process of the data transmission method, let's take a concrete example.

[0120] Figure 5 The diagram shown is a flowchart of a data transmission method provided in another embodiment of this application.

[0121] like Figure 5 As shown, taking 1,000 contacts (500 of which have profile pictures) stored in a user's mobile phone address book as an example, the data transmission method provided in this embodiment may include the following main processes.

[0122] The user activates the vehicle's Bluetooth and sends a pairing request to their phone. After confirming the connection, the phone sends a Bluetooth connection success response to the vehicle. Once the Bluetooth connection is established, the vehicle automatically triggers a PBAP application layer connection request. The phone responds and completes the PBAP connection. At this point, the vehicle acts as the client, and the phone acts as the server.

[0123] The vehicle's PBAP processing unit constructs a request data packet for contact information in the address book. In the PropertySelector parameter of this request data packet, in addition to the flags for requesting "name" and "phone number", the 32nd bit (preset as the "whether to support avatar" flag) is set to 1, indicating that the information in this field is requested. It is then sent to the mobile phone via the first Bluetooth communication unit.

[0124] Upon receiving the request, the phone's PBAP service unit calls the contact data management unit to traverse the local contact list and parse the relevant contact data to determine the presence of an avatar. For contacts without avatars (e.g., Zhang San, number 12345678901), a response data packet in vCard format is generated, containing "Name: Zhang San", "Number: 12345678901", and "Avatar Support: No". For contacts with avatars (e.g., Li Si, number 01987654321), a response data packet in vCard format is generated, containing "Name: Li Si", "Number: 01987654321", and "Avatar Support: Yes", without attaching avatar data. The response data packet is then sent to the vehicle via the second Bluetooth communication unit.

[0125] After the vehicle receives the response data packet, the PBAP processing unit parses out the basic data, and the data storage unit writes it into the SQLite database, forming two records as shown in Table 2 below: Table 2 Repeat the above steps to obtain basic data, requesting basic data for all contacts in a loop. In this way, the vehicle can complete the storage of basic data for 1000 contacts within 10 seconds. At this point, the vehicle's core address book function is ready. If the user enters "Call Zhang San" via voice input on the vehicle, the vehicle can immediately match Zhang San's number from the database and trigger the call. Successful operation indicates that the core address book function is working properly.

[0126] Subsequently, the vehicle's asynchronous task scheduling unit starts a background thread to execute an SQL query in the database: "SELECT number FROM contact table WHERE whether avatar is supported = 'yes'", to obtain a list of the numbers of the 500 contacts with avatars.

[0127] Based on a list of contact numbers, the vehicle sequentially constructs a PBAP request data packet requesting only the contact's image for each contact with an image, and sends the request to the mobile phone. Upon receiving the request, the mobile phone's contact data management unit extracts the corresponding contact's image data (JPEG format) according to the contact number and transmits it to the vehicle.

[0128] After the vehicle receives the headshot data, the data storage unit matches the relevant records in the database with the number and writes the headshot data into the "Headshot Data" field of the corresponding contact, thus updating the value of that field in the database.

[0129] Repeat the steps described above to retrieve profile picture data, looping through all contacts with profile pictures. The background asynchronous task initiated by the asynchronous task scheduling unit can complete the download and update of profile picture data for all 500 contacts within 30 seconds, ensuring that the profile pictures are displayed correctly when the user subsequently views the contacts in the vehicle.

[0130] In summary, compared with the prior art, the data transmission method provided in this application can mainly achieve the following technical effects.

[0131] First, it shortens the availability time of core address book functions: by transmitting basic address book data and contact avatar data in stages, the vehicle can complete the acquisition of basic data such as the names and phone numbers of all contacts within seconds. After connecting via Bluetooth, users can immediately use core functions such as voice calls and contact search without waiting for the long avatar download process, completely eliminating the "data acquisition vacuum period".

[0132] Secondly, the user experience has been optimized: the immediate availability of core communication functions greatly improves the ease of use of in-vehicle Bluetooth and avoids the frustration caused by operation failures; at the same time, the asynchronous acquisition of contact avatar data is completed in the background, without affecting the normal use of other vehicle functions.

[0133] Third, it improves data transmission efficiency: targeted, phased data acquisition requests reduce the amount of data transmitted in a single transmission, avoiding transmission congestion caused by excessively large contact avatar data in traditional synchronous transmission; the background execution of asynchronous tasks enables reasonable allocation of resources, ensuring the smooth operation of the vehicle's main process.

[0134] Fourth, it has good compatibility with existing protocols: by extending the existing parameters of PBAP to add new fields, there is no need to modify the underlying architecture of Bluetooth and PBAP. It can be adapted to existing mainstream mobile terminals and vehicle systems, and has good universality and scalability.

[0135] The above text combined Figures 1 to 5 The embodiments of the data transmission method of this application are described in detail below, in conjunction with... Figure 6 and Figure 7 This application provides a detailed description of embodiments of the data transmission apparatus. It should be understood that the descriptions of the data transmission method embodiments correspond to the descriptions of the data transmission apparatus embodiments; therefore, any parts not described in detail can be found in the foregoing method embodiments.

[0136] Figure 6The diagram shown is a structural schematic of a data transmission device according to an embodiment of this application. This device can be applied to vehicles. Figure 6 As shown, the data transmission device 600 provided in this embodiment includes: The first request module 601 is used to send a request to the mobile terminal to obtain contact data from the contact list. The first receiving module 602 is used to receive basic contact data returned by the mobile terminal based on the contact data acquisition request. The basic contact data includes other contact data except for the contact's avatar data. The second request module 603 is used to send a request to the mobile terminal to obtain avatar data based on the basic contact list data. The second receiving module 604 is used to receive the contact avatar data returned by the mobile terminal based on the avatar data acquisition request.

[0137] In one embodiment of this application, the contact data acquisition request includes avatar request identification information. The basic contact data also includes avatar identification information corresponding to a contact returned by the mobile terminal based on the avatar request identification information. The avatar identification information is used to indicate whether there is avatar data of a contact corresponding to the contact in the mobile terminal. Accordingly, the second request module 603 is further configured to: determine that the avatar identification information is the target contact of the target information, the target information being used to indicate that there is avatar data of the contact in the mobile terminal; and send an avatar data acquisition request for the target contact to the mobile terminal.

[0138] In one embodiment of this application, the second request module 603 is further configured to: obtain contact identification information corresponding to the target contact; and send a request to the mobile terminal to obtain the avatar data of the target contact based on the contact identification information corresponding to the target contact.

[0139] In one embodiment of this application, the device further includes: an extraction module, used to extract contact name information, contact communication information and avatar identification information from basic address book data, and to determine contact identification information; a first storage module, used to store the contact identification information, contact name information, contact communication information and avatar identification information into a database; and a second storage module, used to store the contact avatar data into the database at the avatar data storage location corresponding to the target contact based on the contact identification information corresponding to the target contact.

[0140] In one embodiment of this application, the device further includes: an acquisition module, configured to acquire contact communication information corresponding to the first contact from the basic data of the address book in response to a communication request instruction for the first contact, wherein the first contact is any contact in the address book; and a communication module, configured to send a communication request to the first contact based on the contact communication information corresponding to the first contact.

[0141] Figure 7 The diagram shown is a structural schematic of a data transmission device according to another embodiment of this application. This device can be applied to a mobile terminal. Figure 7 As shown, the data transmission device 700 provided in this application embodiment includes: The third receiving module 701 is used to receive a contact data retrieval request sent by the vehicle for the contact book. The first sending module 702 is used to send basic contact data to the vehicle in response to a contact data acquisition request. The basic contact data includes other contact data except for the contact's avatar data. The fourth receiving module 703 is used to receive a request for obtaining avatar data sent by the vehicle based on the address book basic data; The second sending module 704 is used to send contact person's photo data to the vehicle in response to the photo data acquisition request.

[0142] In one embodiment of this application, the contact data acquisition request includes avatar request identification information. Accordingly, the first sending module 702 is further configured to: query whether there is avatar data corresponding to a contact in the contact list based on the avatar request identification information, and obtain a query result; determine the avatar identification information corresponding to the contact based on the query result; and send the basic contact data containing the avatar identification information to the vehicle.

[0143] In one embodiment of this application, the avatar data acquisition request includes contact identification information corresponding to the target contact. Accordingly, the second sending module 704 is further configured to: acquire avatar data corresponding to the target contact based on the contact identification information; and send the avatar data corresponding to the target contact to the vehicle.

[0144] Below, for reference Figure 8 This describes an electronic device according to embodiments of the present application. Figure 8 The diagram shown is a structural schematic of an electronic device provided in an exemplary embodiment of this application.

[0145] like Figure 8 As shown, the electronic device 800 includes one or more processors 801 and memory 802.

[0146] The processor 801 may be a central processing unit (CPU) or other form of processing unit with data processing capabilities and / or instruction execution capabilities, and may control other components in the electronic device 800 to perform desired functions.

[0147] The memory 802 may include one or more computer program products, which may include various forms of computer-readable storage media, such as volatile memory and / or non-volatile memory. The volatile memory may include, for example, random access memory (RAM) and / or cache memory. The non-volatile memory may include, for example, read-only memory (ROM), hard disk, flash memory, etc. One or more computer program instructions may be stored on the computer-readable storage medium, and the processor 801 may execute the program instructions to implement the data transmission methods and / or other desired functions of the various embodiments of this application described above. The computer-readable storage medium may also store various content such as basic address book data and contact avatar data.

[0148] In one example, the electronic device 800 may also include an input device 803 and an output device 804, which are interconnected via a bus system and / or other forms of connection mechanism (not shown).

[0149] The input device 803 may include, for example, a keyboard, a mouse, etc.

[0150] The output device 804 can output various information to the outside, including basic address book data, contact avatar data, etc. The output device 804 may include, for example, a display, speaker, printer, and communication network and its connected remote output devices, etc.

[0151] Of course, for the sake of simplicity, Figure 8 Only some of the components of the electronic device 800 relevant to this application are shown in this illustration; components such as buses, input / output interfaces, etc., are omitted. In addition, the electronic device 800 may include any other suitable components depending on the specific application.

[0152] In addition to the methods and apparatus described above, embodiments of this application may also be computer program products, which include computer program instructions that, when executed by a processor, cause the processor to perform the steps of the data transmission methods according to the various embodiments of this application described above.

[0153] The computer program product can be written in any combination of one or more programming languages ​​to perform the operations of the embodiments of this application. The programming languages ​​include object-oriented programming languages ​​such as Java and C++, as well as conventional procedural programming languages ​​such as C or similar languages. The program code can be executed entirely on the user's computing device, partially on the user's computing device, as a standalone software package, partially on the user's computing device and partially on a remote computing device, or entirely on a remote computing device or server.

[0154] Furthermore, embodiments of this application may also be computer-readable storage media storing computer program instructions thereon, which, when executed by a processor, cause the processor to perform the steps of the data transmission methods according to various embodiments of this application described above.

[0155] The computer-readable storage medium may be any combination of one or more readable media. A readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may be, for example, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of readable storage media (a non-exhaustive list) include: an electrical connection having one or more wires, a portable disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof.

[0156] The basic principles of this application have been described above with reference to specific embodiments. However, it should be noted that the advantages, benefits, and effects mentioned in this application are merely examples and not limitations, and should not be considered as essential features of each embodiment of this application. Furthermore, the specific details disclosed above are for illustrative and facilitative purposes only, and are not limitations. These details do not limit the application to the necessity of employing the aforementioned specific details for implementation.

[0157] The block diagrams of devices, apparatuses, devices, and systems involved in this application are merely illustrative examples and are not intended to require or imply that they must be connected, arranged, or configured in the manner shown in the block diagrams. As those skilled in the art will recognize, these devices, apparatuses, devices, and systems can be connected, arranged, and configured in any manner. Words such as “comprising,” “including,” “having,” etc., are open-ended terms meaning “including but not limited to,” and are used interchangeably with them. The terms “or” and “and” as used herein refer to the terms “and / or,” and are used interchangeably with them unless the context clearly indicates otherwise. The term “such as” as used herein refers to the phrase “such as but not limited to,” and is used interchangeably with it.

[0158] It should also be noted that in the apparatus, equipment, and methods of this application, the components or steps can be disassembled and / or recombined. These disassemblies and / or recombinations should be considered as equivalent solutions of this application.

[0159] The above description of the disclosed aspects is provided to enable any person skilled in the art to make or use this application. Various modifications to these aspects will be readily apparent to those skilled in the art, and the general principles defined herein can be applied to other aspects without departing from the scope of this application. Therefore, this application is not intended to be limited to the aspects shown herein, but rather to be accorded the widest scope consistent with the principles and novel features disclosed herein.

[0160] The above description has been given for illustrative and descriptive purposes. Furthermore, this description is not intended to limit the embodiments of this application to the forms disclosed herein. Although numerous exemplary aspects and embodiments have been discussed above, those skilled in the art will recognize certain variations, modifications, alterations, additions, and sub-combinations thereof.

Claims

1. A data transmission method, characterized in that, Applied to vehicles, the method includes: Send a request to the mobile terminal to retrieve contact data from the address book; The mobile terminal receives basic contact data returned based on the contact data acquisition request. The basic contact data includes other contact data besides the contact's profile picture. Based on the contact list data, a request to obtain avatar data is sent to the mobile terminal; Receive the contact avatar data returned by the mobile terminal based on the avatar data acquisition request.

2. The method according to claim 1, characterized in that, The contact data acquisition request includes avatar request identification information, and the contact basic data also includes avatar identification information corresponding to the contact returned by the mobile terminal based on the avatar request identification information. The avatar identification information is used to indicate whether there is contact avatar data corresponding to the contact in the mobile terminal. The step of sending a profile picture data retrieval request to the mobile terminal based on the contact list basic data includes: Based on the contact list data, the avatar identification information is determined to be the target contact of the target information, and the target information is used to characterize the existence of contact avatar data in the mobile terminal. Send a request to the mobile terminal to obtain the profile picture data of the target contact.

3. The method according to claim 2, characterized in that, Sending a request to the mobile terminal to obtain the profile picture data of the target contact includes: Obtain the contact identifier information corresponding to the target contact; Based on the contact identifier information corresponding to the target contact, a request to obtain the avatar data of the target contact is sent to the mobile terminal.

4. The method according to claim 3, characterized in that, After receiving the basic contact data returned by the mobile terminal based on the contact data retrieval request, the method further includes: Extract contact name information, contact communication information, and avatar identification information from the basic address book data, and determine contact identification information; The contact identification information, the contact name information, the contact communication information, and the avatar identification information are stored in the database accordingly; After receiving the contact avatar data returned by the mobile terminal based on the avatar data acquisition request, the method further includes: Based on the contact identifier information corresponding to the target contact, the contact's avatar data is stored in the database at the avatar data storage location corresponding to the target contact.

5. The method according to any one of claims 1 to 4, characterized in that, After receiving the basic contact data returned by the mobile terminal based on the contact data retrieval request, the method further includes: In response to a communication request instruction for a first contact, contact communication information corresponding to the first contact is obtained from the basic contact data, wherein the first contact is any contact in the contact list; Based on the contact communication information corresponding to the first contact, a communication request is sent to the first contact.

6. A data transmission method, characterized in that, Applied to a mobile terminal, the method includes: Receives a request from the vehicle to retrieve contact data from the address book; In response to the contact data acquisition request, basic contact data is sent to the vehicle, which includes contact data other than contact avatar data; Receive the avatar data acquisition request sent by the vehicle based on the address book basic data; In response to the avatar data acquisition request, contact avatar data is sent to the vehicle.

7. The method according to claim 6, characterized in that, The contact data acquisition request includes avatar request identification information, and the sending of basic contact data to the vehicle includes: Based on the avatar request identifier information, query whether there is avatar data for a contact in the address book that corresponds to the contact, and obtain the query result; Based on the query results, determine the avatar identification information corresponding to the contact person; Send basic address book data containing the avatar identification information to the vehicle.

8. The method according to claim 6, characterized in that, The profile picture data acquisition request includes contact identifier information corresponding to the target contact, and sending the contact profile picture data to the vehicle includes: Based on the contact identifier information, obtain the contact avatar data corresponding to the target contact; Send the contact avatar data corresponding to the target contact to the vehicle.

9. A vehicle, characterized in that, include: First processor; A first memory for storing executable instructions of the first processor; The first processor is configured to execute the data transmission method according to any one of claims 1 to 5.

10. An electronic device, characterized in that, include: Second processor; A second memory for storing executable instructions of the second processor; The second processor is configured to execute the data transmission method according to any one of claims 6 to 8.

Images