A method and device for processing call information of multiple in-vehicle Bluetooth devices

Abstract

The present application provides a method and device for processing call information of multiple in-vehicle Bluetooth devices. The method includes determining preliminary screened call information based on the call information of the first cycle and the call information of the second cycle, and transmitting the preliminary screened call information into the corresponding device instance based on the device address. The preliminary screened call information includes call status, call identifier, and device address; selecting the valid call information corresponding to the device instance according to the call list, call identifier, and call status in each device instance, and updating the call list in the device instance; performing secondary screening on the valid call information in each device instance based on the device address in the order of reception time to obtain target call information, so that the call interface is displayed based on the target call information, thereby solving the technical problem that the call information corresponding to the mobile phone in a call cannot be displayed on the call interface in the case of connecting multiple Bluetooth devices.

Description

Technical Field

[0001] This application relates to the technical field of data processing, and particularly to a method and device for processing call information of multiple in-vehicle Bluetooth devices. Background Art

[0002] With the rapid development of technology and the popularity of smart phones, modern cars have not only become a means of transportation, but have gradually evolved into an intelligent mobile space integrating multiple functions such as driving, entertainment, and communication. In this transformation process, in-vehicle Bluetooth technology, as an important bridge connecting cars and smart phones, has become increasingly prominent. To improve the communication convenience and driving safety of drivers, many automobile manufacturers have integrated dual Bluetooth module technology into their vehicle models. This innovative design allows drivers to connect two mobile phones to the in-vehicle system simultaneously, achieving unprecedented communication flexibility. The dual Bluetooth module allows users to connect two mobile phones simultaneously and freely choose to answer calls from either phone.

[0003] Traditional Bluetooth device designs follow the principle of establishing an audio connection with only a single device at a time. Therefore, when a user connects two mobile phones simultaneously and the first call starts, the in-vehicle Bluetooth system usually establishes an audio connection with the phone initiating the call and pauses the audio connection with the second phone. This means that during the first call, the audio of the second phone will not be played through the car stereo unless, after the first call ends, the user chooses to switch the audio of the second phone to the car stereo system. However, in related technologies, it is not possible to display the call information corresponding to the phone in the call interface during a call when multiple Bluetooth devices are connected, so that users can clearly understand the call status of the current call phone. Summary of the Invention

[0004] In view of the above-mentioned disadvantages of the related technologies, this application provides a method and device for processing call information of multiple in-vehicle Bluetooth devices to solve the technical problem that the call information corresponding to the phone in the call interface cannot be displayed when multiple Bluetooth devices are connected.

[0005] The present application provides a method for processing call information of multiple in-vehicle Bluetooth devices. The method for processing call information of multiple in-vehicle Bluetooth devices includes: determining preliminary screening call information based on the call information of the first cycle and the call information of the second cycle, and transmitting the preliminary screening call information into the corresponding device instance based on the device address, where the preliminary screening call information includes a call status, a call identifier, and the device address; selecting the valid call information corresponding to the device instance according to the call list in each device instance, the call identifier, and the call status, and updating the call list in the device instance; performing secondary screening on the valid call information in each device instance based on the device address in sequence according to the reception time order to obtain target call information, so that the call interface is displayed based on the target call information.

[0006] In an embodiment of the present application, selecting the valid call information corresponding to the device instance according to the call list in the device instance, the call identifier, and the call status, and updating the call list in the device instance includes: if there is no call information record in the call list of the device instance, taking the preliminary screening call information as the valid call information and adding it to the call list; if there is a call information record in the call list of the device instance and the call information record does not include the call identifier, taking the preliminary screening call information as the valid call information based on the call status and adding it to the call list; if there is a call information record in the call list of the device instance and the call information record includes the call identifier, comparing the call status of the call information record with the same call identifier and the preliminary screening call information. If the call status is different, taking the preliminary screening call information as the valid call information, and modifying the call list based on the valid call information.

[0007] In an embodiment of the present application, the call status includes in call, waiting, and hung up. Selecting the valid call information corresponding to the device instance according to the call list, the call identifier, and the call status in each device instance, and updating the call list in the device instance includes: If there is a call information record in the call list of the device instance, the call identifier is not included in the call information record, and the call status of the preliminary screened call information is in call or waiting, then the preliminary screened call information is used as the valid call information and added to the call list, and the call status includes in call, waiting, and hung up; If there is a call information record in the call list of the device instance, the call identifier is included in the call information record, and the call status of the preliminary screened call information is in call or waiting, then the call information record with the same call identifier and the preliminary screened call information are compared for call status. If the call status is different, the preliminary screened call information is used as the valid call information, and the call list is modified based on the valid call information; If there is a call information record in the call list of the device instance, the call identifier is included in the call information record, and the call status of the preliminary screened call information is hung up, then the preliminary screened call information is used as the valid call information, and the call information record in the call list with the same call identifier as the valid call information is removed from the call list.

[0008] In an embodiment of the present application, the method for processing call information of in-vehicle multiple Bluetooth devices further includes displaying device variables, the occupancy status of the in-vehicle audio, and the occupied device address; performing secondary screening on the valid call information in multiple device instances in sequence based on the receiving time and the device address to obtain target call information, including: if no call information is currently displayed on the call interface, the display device variable is empty; if the in-vehicle audio occupancy status is occupied and the device address of the valid call information is the same as the occupied device address, the valid call information is used as the target call information, and the display device variable is assigned a value based on the device address of the target call information; if the in-vehicle audio occupancy status is occupied and the device address of the valid call information is different from the occupied device address, it is determined whether the display device variable is empty. If the display device variable is empty, the valid call information is used as the target call information, the display device variable is assigned a value based on the device address of the target call information, and the occupied device address is updated based on the device address of the target call information; if the in-vehicle audio occupancy status is unoccupied and the display device variable is empty, the valid call information is used as the target call information, and the display device variable is assigned a value based on the device address of the target call information; if the in-vehicle audio occupancy status is unoccupied and the display device variable is not empty, it is determined whether the device address of the valid call information is equal to the display device variable. If they are equal, the valid call information is used as the target call information.

[0009] In an embodiment of the present application, the call interface is displayed based on the target call information, including: if the call status of the target call information is in a call, a call-in progress interface is displayed on the call interface based on the target call information; if the call status of the target call information is waiting, a dialing interface or an incoming call interface is displayed on the call interface based on the target call information; if the call status of the target call information is hung up, a hung-up interface is displayed on the call interface.

[0010] In an embodiment of the present application, if the call status of the target call information is hung up, after the hung-up interface is displayed on the call interface, it further includes: reading the call list corresponding to the target call information. If the call list corresponding to the target call information is empty, the display device variable is set to be empty; if there are still call information records in the call list corresponding to the target call information, new target call information is selected based on the call information records, and the call interface is displayed based on the new target call information.

[0011] In one embodiment of the present application, the method for processing call information of in-vehicle multi-Bluetooth devices further includes: if it is detected that the audio transmission state changes, re-acquire the vehicle audio occupancy state and the occupied device address; if the display device variable is empty, assign a value to the display device variable based on the occupied device address, and use the valid call information with the same device address as the occupied device address as the target call information; if the display device variable is not empty and the display device variable is different from the occupied device address, assign a value to the display device variable based on the occupied device address, and use the valid call information with the same device address as the occupied device address as the target call information; if the display device variable is not empty and the display device variable is the same as the occupied device address, use the valid call information with the same device address as the occupied device address as the target call information.

[0012] In one embodiment of the present application, the method for processing call information of in-vehicle multi-Bluetooth devices further includes: when adding the valid call information to the call list, record the current system time as the call start time; when the call interface is displayed, obtain the call duration based on the call start time and the current system time, and display the call duration.

[0013] In one embodiment of the present application, determining the preliminary screening call information according to the call information in the first period and the call information in the second period includes: if at least one of the call status, call identifier, or device address in the second period is different from the call status, call identifier, or device address in the first period, use the call information in the second period as the preliminary screening call information.

[0014] An embodiment of the present application further provides an in-vehicle multi-Bluetooth device call information processing apparatus, where the in-vehicle multi-Bluetooth device call information processing apparatus includes: an information preliminary screening module, configured to determine preliminary screening call information according to the call information in the first period and the call information in the second period, and transmit the preliminary screening call information into the corresponding device instance based on the device address, where the preliminary screening call information includes a call status, a call identifier, and the device address; a list update module, configured to select the valid call information corresponding to the device instance according to the call list, the call identifier, and the call status in each device instance, and update the call list in the device instance; an information display module, configured to perform secondary screening on the valid call information in each device instance in sequence according to the reception time based on the device address to obtain target call information, so that the call interface is displayed based on the target call information.

[0015] An embodiment of the present application further provides an electronic device, which includes: one or more processors; a storage device for storing one or more programs, and when the one or more programs are executed by the one or more processors, the electronic device implements the method for processing call information of multiple in-vehicle Bluetooth devices as described in any one of the above embodiments.

[0016] An embodiment of the present application further provides a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor of a computer, the computer is enabled to execute the method for processing call information of multiple in-vehicle Bluetooth devices as described in any one of the above embodiments.

[0017] Advantages of the present application: An embodiment of the present application provides a method and device for processing call information of multiple in-vehicle Bluetooth devices. The method determines preliminary screening call information according to the call information in the first period and the call information in the second period, and passes the preliminary screening call information into the corresponding device instance based on the device address. The preliminary screening call information includes call status, call identifier, and device address; selects the valid call information corresponding to the device instance according to the call list, call identifier, and call status in each device instance, and updates the call list in the device instance; performs secondary screening on the valid call information in each device instance in sequence based on the device address according to the reception time sequence to obtain target call information, so that the call interface is displayed based on the target call information. This method can reduce the processing of duplicate information by screening the call information, improve the response speed and resource utilization efficiency of the system, and can make the in-vehicle display screen reflect the change of the call status in time by updating the call information status in real time, improving the coherence of the user experience.

[0018] It should be understood that the above general description and subsequent detailed description are only exemplary and explanatory, and cannot limit the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] Figure 1 is a schematic diagram of an implementation environment of a method for processing call information of multiple in-vehicle Bluetooth devices shown in an exemplary embodiment of the present application;

[0020] Figure 2 is a flowchart of a method for processing call information of multiple in-vehicle Bluetooth devices shown in an exemplary embodiment of the present application;

[0021] Figure 3 is a flowchart of preliminary screening shown in an exemplary embodiment of the present application;

[0022] Figure 4 is a flowchart of secondary screening shown in an exemplary embodiment of the present application;

[0023] Figure 5It is a flowchart for updating a call interface shown in an exemplary embodiment of the present application;

[0024] Figure 6 It is a block diagram of a vehicle-mounted multi-Bluetooth device call information processing device shown in an exemplary embodiment of the present application;

[0025] Figure 7 It is a schematic structural diagram of an electronic device shown in an exemplary embodiment of the present application. Detailed implementation manners

[0026] The following uses specific specific examples to illustrate the implementation manners of the present application. Those skilled in the art can easily understand other advantages and effects of the present application from the content disclosed in this specification. The present application can also be implemented or applied through other different specific implementation manners. Various details in this specification can also be modified or changed based on different viewpoints and applications without departing from the spirit of the present application. It should be noted that, without conflict, the following embodiments and the features in the embodiments can be combined with each other.

[0027] It should be noted that the diagrams provided in the following embodiments only illustrate the basic concept of the present application in a schematic manner. Therefore, only the components related to the present application are shown in the diagrams, rather than being drawn according to the number, shape, and size of the components in actual implementation. The type, quantity, and ratio of each component in actual implementation can be arbitrarily changed, and the component layout type may also be more complex.

[0028] It should be noted that in the present application, "first", "second", etc. are only used to distinguish similar objects, and are not intended to limit the order or sequence of similar objects. The described "including", "having", etc. are deformed, indicating that the scope covered by the subject of this word is not exclusive except for the examples shown by this word.

[0029] It can be understood that the various numerical numbers, step numbers, etc. recorded in the present application are for the convenience of description and are not used to limit the scope of the present application. The size of the reference numbers in the present application does not mean the sequence of execution order. The execution order of each process should be determined by its function and internal logic.

[0030] In the following description, a large number of details are explored to provide a more thorough explanation of the embodiments of the present application. However, it is obvious to those skilled in the art that the embodiments of the present application can be implemented without these specific details. In other embodiments, well-known structures and devices are shown in the form of block diagrams rather than in detail to avoid making the embodiments of the present application difficult to understand.

[0031] Embodiments of the present application respectively provide a method for processing call information of multiple in-vehicle Bluetooth devices, a device for processing call information of multiple in-vehicle Bluetooth devices, an electronic device, a computer-readable storage medium, and a computer program product. These embodiments will be described in detail below.

[0032] Please refer to Figure 1 , Figure 1 which is a schematic diagram of the implementation environment of a method for processing call information of multiple in-vehicle Bluetooth devices shown in an exemplary embodiment of the present application.

[0033] As Figure 1 shown, the implementation environment may include a vehicle-mounted system 101, a first device 102, and a second device 103. The first device 102 and the second device 103 are connected to the vehicle-mounted system 101 based on Bluetooth. The vehicle-mounted system 101 periodically obtains the call information of the first device 102 and the second device 103 based on Bluetooth phone broadcast, and performs a primary screening on the obtained call information to obtain the preliminarily screened call information. Then, based on the change of the call status in the preliminarily screened call information, the valid call information corresponding to each device is selected, and the valid call information is further screened twice based on the device address and the display device variable to obtain the target call information. The vehicle-mounted system 101 displays the call interface on the vehicle-mounted display screen based on the target call information.

[0034] In an embodiment of the present application, performing a primary screening on the obtained call information to obtain the preliminarily screened call information includes determining the preliminarily screened call information according to the call information of the first period and the call information of the second period. The periodically obtained call information is used as the call information of the first period and the call information of the second period. For example, the previous period is used as the first period, and the current period is used as the second period, that is, the first period is the previous period of the second period.

[0035] Please refer to Figure 2 , Figure 2 which is a flowchart of a method for processing call information of multiple in-vehicle Bluetooth devices shown in an exemplary embodiment of the present application. This method can be applied to Figure 1 the implementation environment shown, and this method can also be applicable to other exemplary implementation environments and be specifically executed by devices in other implementation environments. This embodiment does not limit the implementation environment applicable to this method.

[0036] As Figure 2 shown, in an exemplary embodiment, the method for processing call information of multiple in-vehicle Bluetooth devices at least includes steps S210 to S230, which are introduced in detail as follows:

[0037] Step S210: Determine the preliminarily screened call information based on the call information of the first period and the call information of the second period, and transmit the preliminarily screened call information into the corresponding device instance based on the device address. The preliminarily screened call information includes call status, call identifier, and device address.

[0038] In an embodiment of the present application, the call information of the connected vehicle Bluetooth device is periodically obtained through Bluetooth phone broadcast. By adding a new device class (device class), it is used to store the call information of the Bluetooth phone. The call information includes call status, call identifier, device address, call duration, and other relevant call information (such as call number, etc.). Among them, the call duration can be obtained by starting to count from the time when the call is connected.

[0039] In an embodiment of the present application, the call information of the connected vehicle Bluetooth device is obtained through Bluetooth phone broadcast every 2S.

[0040] In an embodiment of the present application, the first period is the previous period of the second period. If the received call information is the first call information received after the vehicle Bluetooth device is connected, then this first call information is used as the preliminarily screened call information. If the received call information is not the first call information received after the vehicle Bluetooth device is connected, then this call information is compared with the call information of the previous period to determine the preliminarily screened call information, that is, determine the preliminarily screened call information based on the call information of the first period and the call information of the second period.

[0041] In an embodiment of the present application, if at least one of the call status, call identifier, or device address in the second period is different from the call status, call identifier, or device address in the first period, then the call information in the second period is used as the preliminarily screened call information.

[0042] Step S220: Select the valid call information corresponding to the device instance according to the call list, call identifier, and call status in each device instance, and update the call list in the device instance.

[0043] In one embodiment of the present application, selecting the valid call information corresponding to the device instance according to the call list, call identifier, and call status in the device instance, and updating the call list in the device instance includes: if there is no call information record in the call list of the device instance, taking the preliminarily screened call information as the valid call information and adding it to the call list; if there is a call information record in the call list of the device instance and the call information record does not include the call identifier, taking the preliminarily screened call information as the valid call information based on the call status and adding it to the call list; if there is a call information record in the call list of the device instance and the call information record includes the call identifier, comparing the call status of the call information record with the same call identifier and the preliminarily screened call information. If the call statuses are different, taking the preliminarily screened call information as the valid call information and modifying the call list based on the valid call information.

[0044] In one embodiment of the present application, the call status includes in call, waiting, and hung up. Selecting the valid call information corresponding to the device instance according to the call list, call identifier, and call status in each device instance, and updating the call list in the device instance includes: if there is a call information record in the call list of the device instance, the call information record does not include the call identifier corresponding to the preliminarily screened call information, and the call status of the preliminarily screened call information is in call or waiting, taking the preliminarily screened call information as the valid call information and adding the valid call information to the call list, where the call status includes in call, waiting, and hung up; if there is a call information record in the call list of the device instance and the call information record includes the call identifier corresponding to the preliminarily screened call information, and the call status of the preliminarily screened call information is in call or waiting, comparing the call status of the call information record with the same call identifier and the preliminarily screened call information. If the call statuses are different, taking the preliminarily screened call information as the valid call information and modifying the call status of the call information record in the call list based on the call status of the valid call information; if there is a call information record in the call list of the device instance and the call information record includes the call identifier corresponding to the preliminarily screened call information, and the call status of the preliminarily screened call information is hung up, taking the preliminarily screened call information as the valid call information and removing the call information record in the call list with the same call identifier as the valid call information from the call list.

[0045] In one embodiment of the present application, when the device is in the waiting state, the device may be in the process of dialing or receiving an incoming call, and a dialing interface or an incoming call interface can be displayed on the call interface based on the target call information.

[0046] Please refer to Figure 3 , Figure 3 which is the preliminary screening flowchart shown in an exemplary embodiment of the present application. In Figure 3 the preliminary screening includes a primary screening and a process of selecting valid call information. First, inFigure 3 On the left side, duplicate call information is screened out through a single screening. In the single screening, the call identifier, call status, and device address in the current cycle (the second cycle) are compared with those in the previous cycle (the first cycle) to obtain the initially screened call information, including: determining whether the call status (callState) in the current cycle is the same as the call status (lastCAllState) in the previous cycle. If they are the same, then determining whether the call identifier (uuid) in the current cycle is the same as the call identifier (lastUUid) in the previous cycle. If they are the same, then determining whether the device address (addr) in the current cycle is the same as the device address (lastAddr) in the previous cycle. If they are the same, it indicates that this piece of original call information is duplicate information of the original call information in the previous cycle, and the original call information in the current cycle is screened out and not passed to the next step. If any one of the call identifier, call status, and device address in the current cycle is different from that in the previous cycle, then this piece of original call information in the current cycle is regarded as valid call information, and lastCAllState is assigned a value based on callState, lastUUid is assigned a value based on uuid, and lastAddr is assigned a value based on addr.

[0047] Figure 3 The right part is the process of selecting valid call information. The initially screened call information obtained through a single screening is input into device class instances differentiated by each device address. In this embodiment, it includes a first device instance and a second device instance, and the initially screened call information is selected and screened based on each device instance. Among them, after a Bluetooth device successfully connects to the in-vehicle unit, a device instance corresponding to this device is established with the device address of the Bluetooth device. For example, the first device corresponds to the first device instance, and the second device corresponds to the second device instance. When the Bluetooth device disconnects, its corresponding device instance will also be removed, thus ensuring that the device instance is always consistent with the device of the connected phone Bluetooth. Call-related information such as call duration, call status, and call identifier related to this device can be stored in the device instance, thereby effectively managing and using call information.

[0048] In an embodiment of the present application, the initially screened call information obtained through a single screening is input into device class instances differentiated by respective device addresses. In this embodiment, it includes a first device instance and a second device instance. Selective screening of the initially screened call information is performed based on each device instance, including: when a piece of initially screened call information (addrclientCall) is passed into the corresponding device instance, it is necessary to determine whether the call list (callList) in the current device instance is empty. If the call list is empty, it indicates that no calls have been recorded for this device before. Then, this piece of initially screened call information is added to the call list and passed as valid call information to the next round of secondary screening. If the call list is not empty, that is, there are call information records in the call list, then the call list is traversed based on the call identifier (uuid). If there is no call information record with the same call identifier as this piece of initially screened call information in the call list, it is necessary to determine whether to add it to the call list according to the call status of the newly passed-in initially screened call information. If the call status of this piece of initially screened call information is hung up, there is no need to add it. If the call status of this piece of initially screened call information is in a call or waiting, then this piece of initially screened call information needs to be added to the call list and passed as valid call information to the next round of secondary screening. If there is a call information record with the same call identifier as this piece of initially screened call information in the call list, it is necessary to determine whether the call status of this piece of initially screened call information has changed. If the call status of this piece of initially screened call information has changed compared to the call status of the call information record with the same call identifier, and the call status of this piece of initially screened call information is hung up, then the call information record corresponding to its call identifier needs to be removed from the call list, and this piece of initially screened call information is passed as valid call information to the next round of secondary screening. If the call status of this piece of initially screened call information has changed compared to the call status of the call information record with the same call identifier, and the call status of this piece of initially screened call information is not hung up, then the call status of the call information record with the same call identifier is updated based on the call status of this piece of initially screened call information, and the initially screened call information is passed as valid call information to the next round of secondary screening. Through Figure 3 the initial screening in

[0049] In an embodiment of the present application, when adding valid call information to the call list, the current system time is recorded as the call start time; when the call interface is displayed, the call duration is obtained based on the call start time and the current system time, and the call duration is displayed.

[0050] In an embodiment of the present application, when adding new call information to the call list, the system time at the time of addition is recorded as the call start time, so that the call duration displayed on the call interface of the in-vehicle display screen is obtained by subtracting the call start time from the current system time for display.

[0051] In an embodiment of the present application, since the call duration cannot be directly obtained through Bluetooth phone broadcasts, a self-timing method can be adopted. Record the current system time when receiving the status in the first call of each call, and the call duration is the difference between the current system time and the call start time.

[0052] The relevant call start time is recorded in each call information record in the call list of the Device class. Whenever there is a change in the call status, we can calculate the call duration by subtracting the call start time from the current time and display it on the application interface.

[0053] Step S230, perform secondary screening on the valid call information in each device instance based on the device address in the order of reception time to obtain the target call information, so that the call interface is displayed based on the target call information.

[0054] In an embodiment of the present application, obtain the display device variable, the in-vehicle audio occupancy status, and the occupied device address, and perform secondary screening on the valid call information in multiple device instances based on the device address in the order of reception time to obtain the target call information, including: if the call interface does not currently display call information, assign an empty value to the display device; if the in-vehicle audio occupancy status is occupied and the device address of the valid call information is the same as the occupied device address, use the valid call information as the target call information and assign a value to the display device variable based on the device address of the target call information; if the in-vehicle audio occupancy status is occupied and the device address of the valid call information is different from the occupied device address, determine whether the display device variable is empty. If the display device variable is empty, use the valid call information as the target call information, assign a value to the display device variable based on the device address of the target call information, and update the occupied device address based on the device address of the target call information; if the in-vehicle audio occupancy status is unoccupied and the display device variable is empty, use the valid call information as the target call information and assign a value to the display device variable based on the device address of the target call information; if the in-vehicle audio occupancy status is unoccupied and the display device variable is not empty, determine whether the device address of the valid call information is equal to the display device variable. If it is equal, use the valid call information as the target call information.

[0055] In an embodiment of the present application, if the in-vehicle audio occupancy status is occupied and the device address of the valid call information is different from the occupied device address, then it is determined whether the display device variable is empty. If the display device variable is not empty, then it is determined whether the device address of the valid call information is equal to the display device variable. If they are equal, the valid call information is used as the target call information.

[0056] In an embodiment of the present application, the call interface is displayed based on the target call information, including: if the call status of the target call information is in a call, then the in-call interface is displayed in the call interface based on the target call information; if the call status of the target call information is waiting, then the dialing interface or the incoming call interface is displayed in the call interface based on the target call information; if the call status of the target call information is hung up, then the hung-up interface is displayed in the call interface.

[0057] In an embodiment of the present application, if the call status of the target call information is hung up, after the hung-up interface is displayed in the call interface, it further includes: reading the call list corresponding to the target call information. If the call list corresponding to the target call information is empty, then the display device variable is set to be empty; if there are still call information records in the call list corresponding to the target call information, then new target call information is selected based on the call information records, and the call interface is displayed based on the new target call information.

[0058] In an embodiment of the present application, when a call of a Bluetooth device is hung up, the Bluetooth device may still be making other calls at the same time. Therefore, when the call status of the target call information is hung up, the call list corresponding to the target call information is read, that is, it is detected whether the Bluetooth device corresponding to the target call information is still making other calls. If the Bluetooth device is not making other calls, the call list corresponding to the target call information is empty, and at this time, the call interface of the Bluetooth device is no longer displayed and the display device variable is set to be empty. If the Bluetooth device is making other calls, there are still call information records in the call list corresponding to the target call information, and then the call information is selected from the call information records as the target call information, and the call interface is displayed based on the new target call information.

[0059] Please refer to Figure 4 , Figure 4It is the secondary screening flowchart shown in an exemplary embodiment of the present application. After the initial screening, the valid call information when the call status of each device instance changes is obtained. However, in the case of multi-Bluetooth phone calls, when the first call starts, the Bluetooth device usually establishes an audio connection with the mobile phone. At this time, the in-vehicle display screen shows the call interface related to the first device, and the audio of the second device will not be played through the Bluetooth device, so there is no need to display the call interface related to the second device. When the call of the first device ends and the second device switches the phone audio to the in-vehicle audio, the call interface of the second device is displayed. The role of secondary screening is to update the call information that needs to be displayed to the call interface of the in-vehicle display screen and at the same time filter out the call information that does not need to be displayed. To perform secondary screening, first, a display device variable phoneDevice needs to be set. The display device variable is the device address corresponding to the device for which the call interface needs to be displayed currently. The obtained valid call information is input into the secondary screening process in sequence based on the reception time. When a piece of valid call information (preliminary screening result) is passed into the secondary screening, it is necessary to determine whether the device currently occupying the in-vehicle audio output is the device corresponding to this piece of valid call information. If so, this piece of valid call information needs to be used as the target call information for displaying the call interface on the in-vehicle display screen, and phoneDevice is assigned the device address corresponding to this piece of valid call information. If phoneDevice is empty, it means that there is no call interface displayed on the current in-vehicle device. At this time, the newly passed-in valid call information should be displayed on the in-vehicle display screen. If no device currently occupies the in-vehicle audio channel, it is necessary to judge the value of phoneDevice. If phoneDevice is empty or equal to the device address corresponding to this piece of valid call information, then phoneDevice is assigned based on the device address corresponding to this piece of valid call information, and this piece of valid call information is used as the target call information for updating the call interface of the in-vehicle display screen. It should be understood that when the device switches the audio of the device to non-in-vehicle audio during the call, the in-vehicle display screen of the vehicle still shows the call interface related to the device.

[0060] In an embodiment of the present application, when the call information corresponding to the value of phoneDevice received is a hang-up, it is necessary to judge whether there is still other call in the call list of this device. If not, phoneDevice is set to be empty. If the device corresponding to the value of phoneDevice disconnects the phone Bluetooth, phoneDevice also needs to be set to be empty. When phoneDevice is set to be empty, it means that there is no device currently displaying the call interface.

[0061] In an embodiment of the present application, the method for processing call information of in-vehicle multiple Bluetooth devices further includes: if it is detected that the audio transmission state changes, re-obtain the vehicle audio occupancy state and the occupied device address; if the display device variable is empty, assign a value to the display device variable based on the occupied device address, and use the valid call information with the device address the same as the occupied device address as the target call information; if the display device variable is not empty and the display device variable is different from the occupied device address, assign a value to the display device variable based on the occupied device address, and use the valid call information with the device address the same as the occupied device address as the target call information; if the display device variable is not empty and the display device variable is the same as the occupied device address, use the valid call information with the device address the same as the occupied device address as the target call information.

[0062] In an embodiment of the present application, the audio transmission state can monitor the system broadcast to obtain the audio transmission state of the in-vehicle Bluetooth. By monitoring the system broadcast, the state change of the audio transmission can be responded to in a timely manner, so as to achieve accurate monitoring and corresponding processing of the call state.

[0063] Please refer to Figure 5 , Figure 5 is the call interface update flowchart shown in an exemplary embodiment of the present application. The call can switch the sound output device such as a mobile phone or a vehicle head unit, Figure 5 The implementation scenario is that when the first device and the second device are both in a call and the audio transmission is switched. When it is detected that the audio transmission state changes, it is necessary to determine the device currently occupying the vehicle head unit channel. When phoneDevice is empty or phoneDevice is not equal to the device address corresponding to the device currently occupying the vehicle head unit channel, it means that the device currently occupying the vehicle head unit channel has not previously displayed the call interface on the vehicle display screen of the vehicle head unit. Therefore, it is necessary to update the valid call information corresponding to this device as the target call information to the vehicle display screen for call interface display, and assign a value to phoneDevice based on the device address of this device. If phoneDevice is already the device currently occupying the vehicle audio channel, it means that the call information related to this device has already been displayed on the vehicle head unit interface. In this case, only the valid call information corresponding to this device needs to be obtained by monitoring the Bluetooth phone broadcast as the target call information for updating the call interface on the vehicle display screen.

[0064] In an embodiment of the present application, when the audio transmission state changes, it may be actively switched based on a user instruction, or when a call of one device ends, the call audio is switched to another device.

[0065] Please refer to Figure 6 , Figure 6The block diagram of a vehicle-mounted multi-Bluetooth device call information processing device shown in an exemplary embodiment of the present application. This device can be applied to Figure 1 the implementation environment shown, and this device can also be applicable to other exemplary implementation environments and be specifically configured in other devices. This embodiment does not limit the implementation environment applicable to this device.

[0066] As Figure 6 shown, this exemplary vehicle-mounted multi-Bluetooth device call information processing device includes:

[0067] An information pre-screening module 601, configured to determine pre-screened call information according to the call information of the first period and the call information of the second period, and transmit the pre-screened call information into the corresponding device instance based on the device address. The pre-screened call information includes call status, call identifier, and device address;

[0068] A list update module 602, configured to select the valid call information corresponding to the device instance according to the call list, call identifier, and call status in each device instance, and update the call list in the device instance;

[0069] An information display module 603, configured to perform secondary screening on the valid call information in each device instance in sequence based on the receiving time and the device address to obtain target call information, so that the call interface is displayed based on the target call information.

[0070] Figure 7 The structural schematic diagram of a computer system of an electronic device suitable for implementing the embodiments of the present application is shown. It should be noted that Figure 7 the computer system 700 of the electronic device shown is only an example and should not bring any limitations to the functions and usage scopes of the embodiments of the present application.

[0071] As Figure 7 shown, the computer system 700 includes a central processing unit (CPU) 701, which can perform various appropriate actions and processes according to the program stored in the read-only memory (ROM) 702 or the program loaded from the storage part 708 into the random access memory (RAM) 703, such as executing the methods described in the above embodiments. In the RAM 703, various programs and data required for system operation are also stored. The CPU 701, ROM 702, and RAM 703 are connected to each other through a bus 704. The input / output (I / O) interface 705 is also connected to the bus 704.

[0072] The following components are connected to the I / O interface 705: an input section 706 including a keyboard, a mouse, etc.; an output section 707 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc. and a speaker, etc.; a storage section 708 including a hard disk, etc.; and a communication section 709 including a network interface card such as a LAN (Local Area Network) card, a modem, etc. The communication section 709 performs communication processing via a network such as the Internet. A drive 710 is also connected to the I / O interface 705 as needed. A removable medium 711 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc. is mounted on the drive 710 as needed so that a computer program read therefrom is installed into the storage section 708 as needed.

[0073] Specifically, according to an embodiment of the present application, the processes described above with reference to the flowchart can be implemented as a computer software program. For example, an embodiment of the present application includes a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes a computer program for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network via the communication section 709, and / or installed from the removable medium 711. When the computer program is executed by a central processing unit (CPU) 701, various functions defined in the system of the present application are executed.

[0074] It should be noted that the computer-readable medium shown in the embodiments of the present application may be a computer-readable signal medium, a computer-readable storage medium, or any combination of the two. A computer-readable storage medium may be, for example, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the above. More specific examples of the computer-readable storage medium may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM), a flash memory, an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present application, a computer-readable signal medium may include a data signal propagated in a baseband or as a part of a carrier wave, in which a computer-readable computer program is carried. Such a propagated data signal may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. A computer-readable signal medium may also be any computer-readable medium other than a computer-readable storage medium, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The computer program contained on the computer-readable medium may be transmitted by any appropriate medium, including but not limited to: wireless, wired, etc., or any suitable combination of the above.

[0075] The flowcharts and block diagrams in the accompanying drawings illustrate the possible architectures, functions, and operations of systems, methods, and computer program products according to various embodiments of the present application. Among them, each block in the flowchart or block diagram may represent a module, a program segment, or a part of code, and the above module, program segment, or part of code contains one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the blocks may occur in a different order from that marked in the accompanying drawings. For example, two consecutive blocks shown may actually be executed substantially in parallel, and they may sometimes be executed in the reverse order, depending on the functions involved. It should also be noted that each block in the block diagram or flowchart, and the combination of blocks in the block diagram or flowchart, may be implemented by a dedicated hardware-based system for performing the specified functions or operations, or may be implemented by a combination of dedicated hardware and computer instructions.

[0076] The units involved in the embodiments described in this application can be implemented in software or in hardware, and the described units can also be provided in a processor. Among them, the names of these units do not, in some cases, constitute a limitation on the units themselves.

[0077] Another aspect of this application also provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor of a computer, the computer is caused to execute the vehicle-mounted multi-Bluetooth device call information processing method as described above. The computer-readable storage medium may be included in the electronic device described in the above embodiments, or may exist alone without being assembled into the electronic device.

[0078] Another aspect of this application also provides a computer program product or a computer program. The computer program product or the computer program includes computer instructions, and the computer instructions are stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device executes the vehicle-mounted multi-Bluetooth device call information processing method provided in the above various embodiments.

[0079] The above embodiments only exemplarily illustrate the principles and effects of this application, rather than limiting this application. Any person familiar with this technology can modify or change the above embodiments without departing from the spirit and scope of this application. Therefore, all equivalent modifications or changes completed by those with ordinary knowledge in the technical field without departing from the spirit and technical idea disclosed in this application should still be covered by the claims of this application.

Claims

1. A method for processing call information of multiple Bluetooth devices in a vehicle, characterized in that: The vehicle-mounted multi-Bluetooth device call information processing method comprises: Determine preliminary screening call information according to the call information of the first cycle and the call information of the second cycle, and transfer the preliminary screening call information to the corresponding device instance based on the device address, wherein the preliminary screening call information includes the call status, the call identifier and the device address; Selecting valid call information corresponding to the device instance according to the call list in each device instance, the call identifier and the call status, and updating the call list in the device instance; The valid call information in each device instance is secondary screened based on the device address in order of reception time to obtain target call information, so that the call interface is displayed based on the target call information, including: obtaining display device variables, vehicle audio occupancy status and occupied device address. If the vehicle audio occupancy status is occupied and the device address of the valid call information is the same as the occupied device address, the valid call information is used as the target call information, and the display device variable is assigned a value based on the device address of the target call information.

2. The vehicle-mounted multi-Bluetooth device call information processing method according to claim 1, characterized in that: Selecting valid call information corresponding to the device instance according to the call list in the device instance, the call identifier, and the call status, and updating the call list in the device instance includes: If there is no call information record in the call list of the device instance, taking the initially screened call information as the valid call information and adding it to the call list; If there is a call information record in the call list of the device instance and the call identifier is not included in the call information record, taking the preliminarily screened call information as valid call information based on the call status and adding it to the call list; If there is a call information record in the call list of the device instance and the call information record includes the call identifier, the call information record with the same call identifier and the preliminary screening call information are compared for call status. If the call statuses are different, the preliminary screening call information is used as valid call information, and the call list is modified based on the valid call information.

3. The vehicle-mounted multi-Bluetooth device call information processing method according to claim 1, characterized in that: The call status includes calling, waiting and hanging up, selecting valid call information corresponding to the device instance according to the call list in each device instance, the call identifier and the call status, and updating the call list in the device instance includes: If there is a call information record in the call list of the device instance, the call information record does not include the call identifier, and the call status is in call or waiting, the preliminarily screened call information is used as the valid call information and added to the call list; If there is a call information record in the call list of the device instance, the call information record includes the call identifier, and the call status is in call or waiting, the call information record with the same call identifier is compared with the preliminary screening call information for the call status, and if the call statuses are different, the preliminary screening call information is used as the valid call information, and the call status of the call information record in the call list is modified based on the valid call information; If there is a call information record in the call list of the device instance, the call information record includes the call identifier, and the call status of the preliminary screened call information is hung up, the preliminary screened call information is used as valid call information, and the call information record in the call list with the same call identifier as the valid call information is removed from the call list.

4. The vehicle-mounted multi-Bluetooth device call information processing method according to any one of claims 1 to 3, characterized in that: Secondary screening of the valid call information in each device instance based on the device address in order of receiving time, and obtaining the target call information further includes: If the call interface currently does not display call information, the display device variable is empty; If the vehicle audio occupation state is occupied and the device address of the valid call information is different from the occupied device address, determine whether the display device variable is empty. If the display device variable is empty, use the valid call information as the target call information, assign a value to the display device variable based on the device address of the target call information, and update the occupied device address based on the device address of the target call information. If the vehicle audio occupancy state is unoccupied and the display device variable is empty, the valid call information is used as the target call information, and the display device variable is assigned a value based on the device address of the target call information; If the vehicle audio occupancy status is unoccupied and the display device variable is not empty, it is determined whether the device address of the valid call information is equal to the display device variable. If so, the valid call information is used as the target call information.

5. The vehicle-mounted multi-Bluetooth device call information processing method according to claim 4, characterized in that: The call interface is displayed based on the target call information and includes: If the call status of the target call information is in call, displaying an in call interface based on the target call information in the call interface; If the call status of the target call information is waiting, displaying a dialing interface or an incoming call interface based on the target call information in the call interface; If the call status of the target call information is hung up, a hang up interface is displayed in the call interface.

6. The vehicle-mounted multi-Bluetooth device call information processing method according to claim 5, characterized in that: If the call status of the target call information is hung up, after displaying the hang up interface in the call interface, the method further includes: Reading a call list corresponding to the target call information, and if the call list corresponding to the target call information is empty, setting the display device variable to empty; If there are still call information records in the call list corresponding to the target call information, new target call information is selected based on the call information records, and a call interface is displayed based on the new target call information.

7. The vehicle-mounted multi-Bluetooth device call information processing method according to claim 4, characterized in that: The vehicle-mounted multi-Bluetooth device call information processing method further includes: If a change in the audio transmission status is detected, the vehicle audio occupancy status and occupied device address are re-acquired; If the display device variable is empty, assigning a value to the display device variable based on the occupied device address, and using the valid call information having the same device address as the occupied device address as the target call information; If the display device variable is not empty, and the display device variable is different from the occupied device address, assigning a value to the display device variable based on the occupied device address, and using the valid call information with the same device address as the occupied device address as the target call information; If the display device variable is not empty, and the display device variable is the same as the occupied device address, the valid call information with the same device address as the occupied device address is used as the target call information.

8. The vehicle-mounted multi-Bluetooth device call information processing method according to any one of claims 1 to 3, characterized in that: The vehicle-mounted multi-Bluetooth device call information processing method further includes: When adding the valid call information to the call list, the current system time is recorded as the call start time; When the call interface is displayed, the call duration is obtained based on the call start time and the current system time, and the call duration is displayed.

9. The vehicle-mounted multi-Bluetooth device call information processing method according to any one of claims 1 to 3, characterized in that: The initial screening call information determined based on the call information of the first cycle and the call information of the second cycle includes: If at least one of the call status, call identification or device address of the second cycle is different from the call status, call identification or device address of the first cycle, the call information of the second cycle is used as the preliminary screening call information.

10. A vehicle-mounted multi-Bluetooth device call information processing device, characterized in that: The vehicle-mounted multi-Bluetooth device call information processing device comprises: An information preliminary screening module, used to determine preliminary screening call information according to the call information of the first cycle and the call information of the second cycle, and transfer the preliminary screening call information to the corresponding device instance based on the device address, wherein the preliminary screening call information includes the call status, the call identifier and the device address; A list updating module, configured to select valid call information corresponding to each device instance according to the call list in each device instance, the call identifier and the call status, and update the call list in the device instance; An information display module is used to perform secondary screening on the valid call information in each device instance based on the device address in sequence according to the receiving time to obtain target call information so that the call interface is displayed based on the target call information, including: obtaining display device variables, vehicle audio occupancy status and occupied device address. If the vehicle audio occupancy status is occupied and the device address of the valid call information is the same as the occupied device address, the valid call information is used as the target call information, and the display device variable is assigned a value based on the device address of the target call information.

Images