Method, device and vehicle-mounted system for vehicle-mounted system communication
By determining the application package name of the third-party application and generating a virtual call status, the suspension problem of third-party applications in the vehicle system when the communication interface is occupied is solved, ensuring the normal operation of the application and improving the user experience.
Patent Information
- Application Number
- CN202111143747.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2021-09-28
- Publication Date
- 2025-09-09
- Estimated Expiration
- 2041-09-28
AI Technical Summary
When the communication interface of the vehicle system is occupied, third-party applications, especially navigation applications, are prone to pause or stop running, affecting the user's normal use.
By judging the application package name of the third-party application, it is determined whether it is on the blacklist, and a virtual call status is generated based on the blacklist. The virtual call status is sent to the third-party application to adjust its working status to avoid the impact of the actual status of the communication interface.
This ensures that the working status of third-party applications is not affected by the actual call status of the communication interface, meets the actual needs of users, and improves the user experience.
Smart Images

Figure CN115883592B_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of information interaction technology, and more specifically to a method, device and vehicle-mounted system for vehicle-mounted system communication. Background Art
[0002] With the development of the modern automotive industry and electronic technology, electronic systems such as vehicle navigation, communications, and multimedia audio and video entertainment can be connected through network technology to form a powerful, comprehensive in-vehicle system. In-vehicle systems can be equipped with Bluetooth communication modules and / or 4G modules for communicating with mobile terminals and making incoming and outgoing calls. They also feature multimedia audio and video entertainment functions, including satellite digital broadcast reception, in-vehicle digital television reception, and CD / DVD playback, providing users with a rich audio-visual experience. Users can also install their favorite third-party applications in the in-vehicle system to access a variety of entertainment information.
[0003] In-vehicle Bluetooth devices mainly include: Bluetooth headsets, in-vehicle Bluetooth hands-free devices, etc. When users use third-party applications installed on the in-vehicle system, in order to ensure that the normal use of the mobile terminal is not affected when the user uses the third-party application, for example, in order to not affect the user's ability to use the in-vehicle Bluetooth device to connect to the mobile terminal for calls through the in-vehicle system, when developing third-party applications, in addition to basic functions, the application developer also has the function of monitoring the usage status of the in-vehicle Bluetooth device in the in-vehicle system. When the in-vehicle Bluetooth device is detected to be occupied, it indicates that the user is using the in-vehicle Bluetooth device for a call, and the current third-party application can be controlled to be paused. When the call is determined to be over, the working status of the third-party application can be restored.
[0004] However, in addition to third-party entertainment applications, in-vehicle systems can also install third-party applications with special functions, such as in-vehicle navigation applications. If the communication interface is suddenly occupied while the user is using the in-vehicle navigation application, causing the in-vehicle navigation application to pause or stop running, this will affect the user's normal use of the navigation function and fail to meet user needs. Summary of the Invention
[0005] In order to solve the above problems, the present application is proposed. According to one aspect of the present application, a method for communication between an in-vehicle system and a mobile terminal is provided, wherein the in-vehicle system includes a communication interface, and the communication interface is used for communication between the in-vehicle system and a mobile terminal. The method includes:
[0006] When a preset trigger condition is met, determine whether the third-party application is on the blacklist based on the application package name of the third-party application;
[0007] If the third-party application is on the blacklist, issuing or not issuing the first virtual call state of the communication interface to the third-party application, so that the third-party application adjusts its working state according to the first virtual call state;
[0008] Otherwise, the second virtual call state of the communication interface is sent to the third-party application, so that the third-party application adjusts its working state according to the virtual call state.
[0009] In one embodiment of the present application, the preset trigger condition includes: the third-party application requests the in-vehicle system to monitor the call status of the communication interface.
[0010] In one embodiment of the present application, the preset trigger condition includes: the communication interface is occupied.
[0011] In one embodiment of the present application, determining whether a third-party application belongs to a blacklist according to the application package name of the third-party application includes:
[0012] The application package name of the third-party application is compared one by one with the application package names in the blacklist to determine whether the third-party application belongs to the blacklist.
[0013] In one embodiment of the present application, before determining whether the third-party application belongs to the blacklist according to the application package name of the third-party application, the method further includes:
[0014] Determine whether a communication connection can be established with the server;
[0015] If a communication connection can be established with the server, a request for calling the blacklist is sent to the server;
[0016] Otherwise, the local blacklist is called.
[0017] In one embodiment of the present application, if the third-party application is on a blacklist, after sending the first virtual call state of the communication interface to the third-party application, the method further includes:
[0018] When the vehicle-mounted system is able to establish a communication connection with the server, a request for updating and obtaining the blacklist is sent to the server to update the local blacklist of the vehicle-mounted system.
[0019] In one embodiment of the present application, the virtual call state is used to represent that the communication interface is not occupied.
[0020] In one embodiment of the present application, the communication interface is a Bluetooth interface.
[0021] According to another aspect of the present application, a device for communication of an in-vehicle system is provided, wherein the in-vehicle system includes a communication interface, and the communication interface is used for communication between the in-vehicle system and a mobile terminal, wherein the device includes:
[0022] A judgment module, configured to judge whether a third-party application belongs to a blacklist according to the application package name of the third-party application when a preset trigger condition is met;
[0023] A sending module is used to send or not send the first virtual call status of the communication interface to the third-party application when the third-party application is on the blacklist, so that the third-party application communicates with the vehicle system according to the first virtual call status; and when the third-party application is not on the blacklist, send the second virtual call status of the communication interface to the third-party application, so that the third-party application performs a second preset action according to the second virtual call status.
[0024] In one embodiment of the present application, the preset trigger condition includes: the third-party application requests the in-vehicle system to monitor the call status of the communication interface.
[0025] In one embodiment of the present application, the preset trigger condition includes: the communication interface is occupied.
[0026] In one embodiment of the present application, the judgment module is further configured to:
[0027] The application package name of the third-party application is compared one by one with the application package names in the blacklist to determine whether the third-party application belongs to the blacklist.
[0028] In one embodiment of the present application, the apparatus further comprises:
[0029] The communication module is used to determine whether a communication connection can be established with the server before determining whether the third-party application belongs to the blacklist based on the application package name of the third-party application; if a communication connection can be established with the server, a request to call the blacklist is sent to the server; otherwise, a local blacklist is called.
[0030] According to another aspect of the present application, there is provided a vehicle-mounted system, the vehicle-mounted system including the apparatus as described above, and further including:
[0031] The Bluetooth communication module is used to establish a communication connection with the mobile terminal.
[0032] According to another aspect of the present application, a storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the processor executes the above-mentioned method for vehicle system communication.
[0033] According to the method, device and vehicle-mounted system of the present application, by sending or not sending the virtual call status of the communication interface to the third-party application in the blacklist when the preset trigger condition is met, the working status of the third-party application in the vehicle-mounted system is not affected by the actual call status of the communication interface.
[0034] In addition, when the vehicle system requests a blacklist from the server, if the vehicle system cannot establish a connection with the server, the third-party application can be judged by calling the local blacklist, which can reduce the waiting time when calling the blacklist and improve the user experience. BRIEF DESCRIPTION OF THE DRAWINGS
[0035] The above and other purposes, features, and advantages of the present application will become more apparent through a more detailed description of the embodiments of the present application in conjunction with the accompanying drawings. The accompanying drawings are intended to provide a further understanding of the embodiments of the present application and constitute a part of the specification. Together with the embodiments of the present application, they are used to explain the present application and do not constitute a limitation of the present application. In the drawings, the same reference numerals generally represent the same components or steps.
[0036] Figure 1 A schematic flow chart showing a method for vehicle system communication according to an embodiment of the present application;
[0037] Figure 2 A schematic diagram showing a specific example of a method for in-vehicle system communication according to an embodiment of the present application;
[0038] Figure 3 A schematic block diagram of an in-vehicle system communication device according to an embodiment of the present application is shown. DETAILED DESCRIPTION
[0039] In order to make the purpose, technical solutions and advantages of the present application more apparent, the following is a detailed description of example embodiments of the present application with reference to the accompanying drawings. Obviously, the described embodiments are only part of the embodiments of the present application, rather than all the embodiments of the present application, and it should be understood that the present application is not limited to the example embodiments described herein. Based on the embodiments of the present application described in this application, all other embodiments obtained by those skilled in the art without creative work should fall within the scope of protection of this application.
[0040] Based on the aforementioned technical problems, the present application provides a method for vehicle-mounted system communication, wherein the vehicle-mounted system includes a communication interface, and the communication interface is used for the vehicle-mounted system to communicate with a mobile terminal. The method includes: when a preset trigger condition is met, judging whether the third-party application belongs to a blacklist based on the application package name of the third-party application; if the third-party application belongs to the blacklist, sending or not sending the first virtual call status of the communication interface to the third-party application, so that the third-party application adjusts its working status according to the first virtual call status; otherwise, sending the second virtual call status of the communication interface to the third-party application, so that the third-party application adjusts its working status according to the virtual call status. The embodiments of the present application can achieve that the working status of the third-party application in the vehicle-mounted system is not affected by the actual call status of the communication interface.
[0041] In addition, when the vehicle system requests a blacklist from the server, if the vehicle system cannot establish a connection with the server, it can call the local blacklist to make a judgment for the third-party application, which can reduce the waiting time when calling the blacklist and improve the user experience.
[0042] The following describes in detail the method for vehicle system communication according to an embodiment of the present application with reference to the accompanying drawings. The features of the various embodiments of the present application can be combined with each other without conflict.
[0043] Figure 1 A schematic flow chart showing a method for vehicle system communication according to an embodiment of the present application is shown; Figure 1 As shown, the vehicle system communication method 100 according to an embodiment of the present application may include the following steps S101, S102, and S103:
[0044] In step S101, when a preset trigger condition is met, it is determined whether the third-party application belongs to a blacklist according to the application package name of the third-party application.
[0045] The third-party application (Application, referred to as APP) in the embodiments of this application mainly refers to an application or program package customized by a third-party developer based on the middleware interface encapsulated by the communication protocol of various applications. With the rapid development of communication technology and the promotion of various third-party applications, users can install the applications of their interest on various terminal devices, such as mobile phones and vehicles, according to their own needs, so as to obtain various information. In this embodiment, the third-party application can be an in-vehicle application or an application installed on a mobile terminal.
[0046] In one example, the preset trigger condition includes a request from the third-party application to the vehicle system to monitor the call status of the communication interface. As a third-party application, it has the function of actively monitoring the vehicle system's communication interface, for example, sending a request to the vehicle system to obtain the call status of the communication interface at preset intervals. If the communication interface is not occupied, the third-party application can continue to run. If the communication interface is occupied, it will execute the corresponding next step.
[0047] In another example, the preset trigger condition includes: the communication interface is occupied. A third-party application can also passively obtain the call status information of the communication interface. For example, when the communication interface is occupied, the vehicle system proactively sends the call status information of the communication interface to the third-party application, so that the third-party application can perform corresponding operations.
[0048] Typically, third-party applications will be suspended or stopped to avoid service conflicts. Because call status information is transmitted through the system's communication interface, third-party applications can obtain call status information normally by simply calling or monitoring the communication interface. This allows third-party applications to implement exclusive logic for call status based on their needs, resulting in many services in the in-vehicle system being unable to function properly during calls. For example, if a mobile phone and the in-vehicle system are logged into the same WeChat account, and the mobile phone is simultaneously connected to the in-vehicle Bluetooth communication module, the WeChat application installed on the in-vehicle system will automatically hang up even if a voice call is received if it detects that the communication interface is occupied. This results in the inability to answer WeChat voice calls, resulting in a poor user experience. Similarly, navigation applications installed on the in-vehicle system will be unable to provide navigation services during calls. However, for special third-party applications, such as in-vehicle navigation applications, pausing or stopping them can cause inconvenience to the driver, potentially leading to the driver taking the wrong route or causing other unexpected situations. Therefore, it is necessary to ensure that these special third-party applications remain running, regardless of whether the communication interface is occupied. Specifically, these special third-party applications can be blacklisted.
[0049] Specifically, judging whether the third-party application belongs to the blacklist according to the application package name of the third-party application includes: comparing the application package name of the third-party application with the application package names in the blacklist one by one to determine whether the third-party application belongs to the blacklist.
[0050] In step S102, if the third-party application belongs to the blacklist, the first virtual call state of the communication interface is sent to the third-party application, so that the third-party application keeps running according to the first virtual call state.
[0051] For vehicles, since there is no SIM card in the vehicle system, when connecting to the mobile terminal through the vehicle Bluetooth device, it is necessary to connect through a communication interface. The communication interface may include a Bluetooth interface, and may also include: a USB interface or a Wi-Fi interface, or a combination of several of them.
[0052] Mobile terminals include but are not limited to mobile phones, laptops, tablets, POS machines and car computers.
[0053] In one example, the first virtual call state is used to indicate that the communication interface is not occupied. When the call state indicates that the call is in progress, it indicates that the communication interface is occupied; when the call state indicates that the call is not in progress, it indicates that the communication interface is not occupied.
[0054] It is worth mentioning that since the Bluetooth interface is not an open interface, when a third-party application wants to monitor the status of the communication interface of the vehicle-mounted system, it cannot monitor it. At this time, the Bluetooth communication module will generate a virtual call state and send it to the third-party application. In traditional technology, the virtual call state is a virtual call state generated based on the real call state. That is to say, the mobile terminal and the third-party application can obtain a virtual call state that is consistent with the real call state through a request. However, in an embodiment of the present application, a first virtual call state will be generated and sent to a third-party application in the blacklist to prevent the third-party application from obtaining the real call state, so that the third-party application believes that the communication interface has not been occupied and the third-party application can always be in working condition.
[0055] For a specific example, see Figure 2 , the mobile terminal is a smart phone, and the smart phone sends a request to the Bluetooth interface of the vehicle system and establishes a Bluetooth connection. When a third-party application installed in the vehicle system requests to monitor the call status of the Bluetooth interface, the vehicle system determines whether the third-party application is on the blacklist. For example, if third-party application 1 is on the blacklist, a first virtual call status can be generated and then sent to third-party application 1 so that third-party application 1 will always be in working state. When third-party application m is not on the blacklist, the vehicle system generates a second virtual call status and then sends it to third-party application m so that third-party application m suspends working state. The above is a case where the third-party application actively obtains the call status of the communication interface. Alternatively, the third-party application can also obtain the call status of the communication interface in a passive manner. For example, after the smart phone establishes a connection with the Bluetooth interface of the vehicle system, the vehicle system immediately generates a first virtual call status and sends it to the third-party application on the blacklist. Here, the first virtual call status can be received without the third-party application sending a monitoring request.
[0056] In other examples, when a third-party application in the blacklist sends a request to obtain the call status of the communication interface, the virtual call status can also be refused to be sent, so that the third-party application in the blacklist cannot know the actual occupancy status of the current communication interface and keep running.
[0057] In step S103, if the third-party application does not belong to the blacklist, the second virtual call state of the communication interface is sent to the third-party application, so that the third-party application adjusts its working state according to the second virtual call state.
[0058] The second virtual call status here can be used to represent the actual occupancy of the communication interface. Specifically, if a third-party application not on the blacklist wants to obtain the call status of the communication interface, the Bluetooth communication module will generate a second virtual call status based on the actual occupancy of the communication interface and send it to the third-party application not on the blacklist. Upon receiving the information that the communication interface is occupied, the third-party application will pause or stop running.
[0059] When it is determined that the communication interface is occupied, the third-party application can also keep monitoring the communication interface, so that when the call ends, the third-party application can immediately resume working.
[0060] Since third-party applications can passively receive the call status of the communication interface sent by the vehicle system, in one possible implementation, the third party that is not in the blacklist may not be in a working state. At this time, the vehicle system does not need to send the phone message to the third-party application.
[0061] In other embodiments of the present application, before determining whether the third-party application belongs to the blacklist based on the application package name of the third-party application, the method also includes: determining whether a communication connection can be established with the server; if a communication connection can be established with the server, sending a request to call the blacklist to the server; otherwise, calling the local blacklist.
[0062] As a means of transportation, a vehicle may be unable to communicate with the server due to poor network signals due to geographical location, environmental factors, and other factors while driving. In this case, a local blacklist can be called. The package name of the third-party application is compared with the package name of the third-party application in the local blacklist to determine whether the third-party application is on the blacklist. In this embodiment, when the vehicle-mounted system requests a blacklist from the server, if a connection cannot be established with the server, the third-party application can be judged by calling the local blacklist, which can reduce the waiting time when calling the blacklist and improve the user experience.
[0063] In another embodiment of the present application, if the third-party application belongs to the blacklist, after sending the first virtual call status of the communication interface to the third-party application, the method also includes: when the vehicle-mounted system is able to establish a communication connection with the server, sending a request for obtaining the blacklist to the server to update the local blacklist of the vehicle-mounted system.
[0064] Here, the blacklist in the server can be updated by backend staff based on actual user usage of third-party applications, or automatically updated based on user feedback. Therefore, the server blacklist is the most up-to-date blacklist. The in-vehicle system can request the blacklist from the server at regular intervals, for example, every month, or immediately request the blacklist each time it disconnects and reconnects to the server.
[0065] The server in the above embodiment may be a cloud server.
[0066] The embodiment of the present application can realize that the working state of the third-party application in the blacklist is not affected by the actual call state of the communication interface. When the communication interface is occupied, the third-party application can still continue to run, which can meet the actual needs of users.
[0067] The following combination Figure 3 The vehicle system communication device of the present application is described, wherein: Figure 3 A schematic block diagram of an in-vehicle system communication device according to an embodiment of the present application is shown.
[0068] like Figure 3 As shown, the vehicle system communication device 300 according to the present application includes: a judgment module 301 and a sending module 302. The modules can respectively execute the above combined Figure 1 The following describes only the main functions of each unit of the vehicle system communication apparatus 300, and omits the details already described above.
[0069] The vehicle-mounted system in the embodiment of the present invention includes a communication interface, which is used for the vehicle-mounted system to communicate with a mobile terminal. The device includes:
[0070] The judgment module 301 is used to judge whether the third-party application belongs to the blacklist according to the application package name of the third-party application when a preset trigger condition is met;
[0071] The sending module 302 is used to send the first virtual call status of the communication interface to the third-party application when the third-party application is on the blacklist, so that the third-party application keeps running according to the first virtual call status; otherwise, send the second virtual call status of the communication interface to the third-party application, so that the third-party application adjusts its working status according to the second virtual call status.
[0072] In one example, the preset trigger condition includes: the third-party application requests the in-vehicle system to monitor the call status of the communication interface.
[0073] In another example, the preset trigger condition includes: the communication interface is occupied.
[0074] Furthermore, the judgment module is further configured to compare the application package name of the third-party application with the application package names in the blacklist one by one to determine whether the third-party application belongs to the blacklist.
[0075] Furthermore, the device further comprises:
[0076] The communication module 303 is used to determine whether a communication connection can be established with the server before determining whether the third-party application belongs to the blacklist based on the application package name of the third-party application; if a communication connection can be established with the server, a request to call the blacklist is sent to the server; otherwise, a local blacklist is called.
[0077] An embodiment of the present application further provides a vehicle-mounted system, the vehicle-mounted system including the vehicle-mounted system communication device described above. The vehicle-mounted system further includes:
[0078] The communication interface is used to establish a communication connection with the mobile terminal.
[0079] In addition, according to an embodiment of the present application, a storage medium is also provided, on which program instructions are stored. When the program instructions are executed by a computer or processor, the computer or processor is used to execute the corresponding steps of the method for vehicle-mounted system communication according to the embodiment of the present application. The storage medium may include, for example, a memory card of a smartphone, a storage component of a tablet computer, a hard disk of a personal computer, a read-only memory (ROM), an erasable programmable read-only memory (EPROM), a portable compact disc read-only memory (CD-ROM), a USB memory, or any combination of the above storage media.
[0080] The in-vehicle system communication device, in-vehicle system, and storage medium of the embodiments of the present application have the same advantages as the aforementioned method because they can implement the aforementioned method.
[0081] Although example embodiments have been described herein with reference to the accompanying drawings, it should be understood that the above example embodiments are merely illustrative and are not intended to limit the scope of the present application. Various changes and modifications may be made therein by those skilled in the art without departing from the scope and spirit of the present application. All such changes and modifications are intended to be included within the scope of the present application as required by the appended claims.
[0082] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.
[0083] In the several embodiments provided in this application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of the units described is merely a logical function division. In actual implementation, other division methods may be used, such as combining or integrating multiple units or components into another device, or ignoring or not performing some features.
[0084] In the description provided herein, a large number of specific details are described. However, it is understood that the embodiments of the present application can be practiced without these specific details. In some instances, well-known methods, structures, and techniques are not shown in detail so as not to obscure the understanding of this description.
[0085] Similarly, it should be understood that in order to streamline the present application and aid in understanding one or more of the various inventive aspects, in the description of the exemplary embodiments of the present application, the various features of the present application are sometimes grouped together into a single embodiment, figure, or description thereof. However, this approach of the present application should not be interpreted as reflecting the intention that the application claimed for protection requires more features than those explicitly recited in each claim. More precisely, as reflected in the corresponding claims, the inventive point is that the corresponding technical problem can be solved with fewer features than all the features of a single disclosed embodiment. Therefore, the claims following the detailed description are hereby expressly incorporated into the detailed description, with each claim itself serving as a separate embodiment of the present application.
[0086] It will be understood by those skilled in the art that, except where mutually exclusive, all features disclosed in this specification (including the accompanying claims, abstract, and drawings) and all processes or units of any method or apparatus disclosed herein may be combined in any combination. Unless expressly stated otherwise, each feature disclosed in this specification (including the accompanying claims, abstract, and drawings) may be replaced by an alternative feature providing the same, equivalent, or similar purpose.
[0087] Furthermore, those skilled in the art will appreciate that although some embodiments described herein include certain features included in other embodiments but not other features, combinations of features from different embodiments are intended to be within the scope of this application and to form different embodiments. For example, in the claims, any of the claimed embodiments may be used in any combination.
[0088] The various component embodiments of the present application can be implemented in hardware, or in a software module running on one or more processors, or in a combination thereof. Those skilled in the art will appreciate that a microprocessor or digital signal processor (DSP) can be used in practice to implement some or all of the functions of some modules according to the embodiments of the present application. The application can also be implemented as a part or all of a device program (e.g., a computer program and a computer program product) for performing the method described herein. Such a program implementing the present application can be stored on a computer-readable medium, or can have the form of one or more signals. Such a signal can be downloaded from an Internet website, or provided on a carrier signal, or provided in any other form.
[0089] It should be noted that the above embodiments illustrate rather than limit the present application, and that a person skilled in the art may devise alternative embodiments without departing from the scope of the appended claims. In the claims, any reference symbols placed between brackets should not be construed as limiting the claims. The word "comprising" does not exclude the presence of elements or steps not listed in the claims. The word "a" or "an" preceding an element does not exclude the presence of a plurality of such elements. The present application may be implemented by means of hardware comprising several different elements and by means of appropriately programmed computers. In a unit claim enumerating several means, several of these means may be embodied by the same item of hardware. The use of the words first, second, and third etc. does not indicate any order. These words may be interpreted as names.
[0090] The above description is merely a specific embodiment or illustration of a specific embodiment of the present application, and the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in the present application should be included in the scope of protection of the present application. The scope of protection of the present application should be based on the scope of protection of the claims.
Claims
1. A method for communication of an in-vehicle system, wherein the in-vehicle system includes a communication interface, wherein the communication interface is used for communication between the in-vehicle system and a mobile terminal, characterized in that: The method comprises: When a preset trigger condition is met, determining whether the third-party application belongs to the blacklist according to the application package name of the third-party application; the preset trigger condition includes: the communication interface is occupied; If the third-party application is on the blacklist, sending a first virtual call state of the communication interface to the third-party application, so that the third-party application keeps running according to the first virtual call state; the first virtual call state is used to indicate that the communication interface is not occupied; Otherwise, the second virtual call status of the communication interface is sent to the third-party application so that the third-party application adjusts its working status according to the second virtual call status, and the adjustment of the working status includes pausing or stopping the operation; the second virtual call status is used to characterize the actual occupancy of the communication interface.
2. The method according to claim 1, wherein Determining whether a third-party application is on the blacklist based on its application package name includes: The application package name of the third-party application is compared one by one with the application package names in the blacklist to determine whether the third-party application belongs to the blacklist.
3. The method according to claim 1, wherein Before determining whether the third-party application belongs to the blacklist according to the application package name of the third-party application, the method further includes: Determine whether a communication connection can be established with the server; If a communication connection can be established with the server, a request for calling the blacklist is sent to the server; Otherwise, the local blacklist is called.
4. The method according to claim 1, wherein If the third-party application is on the blacklist, after sending the first virtual call status of the communication interface to the third-party application, the method further includes: When the vehicle-mounted system is able to establish a communication connection with the server, a request for obtaining a blacklist is sent to the server to update the local blacklist of the vehicle-mounted system.
5. The method according to claim 1, wherein The communication interface is a Bluetooth interface.
6. A device for communication of an in-vehicle system, wherein the in-vehicle system includes a communication interface, and the communication interface is used for communication between the in-vehicle system and a mobile terminal, characterized in that: The device comprises: a judgment module, configured to judge whether the third-party application belongs to the blacklist according to the application package name of the third-party application when a preset trigger condition is met; the preset trigger condition includes: the communication interface is occupied; a sending module, configured to send the first virtual call state of the communication interface to the third-party application when the third-party application is on the blacklist, so that the third-party application keeps running according to the first virtual call state; otherwise, send the second virtual call state of the communication interface to the third-party application, so that the third-party application adjusts its working state according to the second virtual call state, wherein the adjusting of the working state includes pausing or stopping the operation; The first virtual call state is used to represent that the communication interface is not occupied; and the second virtual call state is used to represent the actual occupancy status of the communication interface.
7. The device according to claim 6, characterized in that The judgment module is also used for: The application package name of the third-party application is compared one by one with the application package names in the blacklist to determine whether the third-party application belongs to the blacklist.
8. The device according to claim 6, wherein The device further comprises: The communication module is used to determine whether a communication connection can be established with the server before determining whether the third-party application belongs to the blacklist based on the application package name of the third-party application; if a communication connection can be established with the server, a request to call the blacklist is sent to the server; otherwise, a local blacklist is called.
9. A vehicle-mounted system, characterized in that: The vehicle-mounted system includes the device according to any one of claims 6 to 8, and further includes: The communication interface is used to establish a communication connection with the mobile terminal.
10. A storage medium, characterized in that: The storage medium stores a computer program, which, when executed by a processor, enables the processor to perform the method according to any one of claims 1 to 5.
Citation Information
Patent Citations
Method and apparatus for processing vehicle-mounted bluetooth phone call
CN108134867A
Monitoring method, monitoring device, vehicle and storage medium
CN112565526A