Information display method and device, vehicle terminal

Abstract

This application provides an information display method and apparatus, and an in-vehicle terminal; wherein, the information display method is applied to an in-vehicle system, and the method includes: establishing a connection with a target audio source, and receiving a first media session token sent by the target audio source through the connection; wherein, the target audio source includes an audio source to which the user wishes to switch or an audio source that was playing before a power outage and restart; constructing a first media controller through the first media session token, and sending a first command to the target audio source through the first media controller; wherein, the first command is used to control the playback state of the target audio source; obtaining the execution result of the first command by the target audio source through the callback mechanism of the first media controller, and displaying the execution result in an interactive window.

Description

Technical Field

[0001] This application relates to electronic technology, including but not limited to information display methods and devices, and vehicle-mounted terminals. Background Technology

[0002] AndroidAutomotiveOS is a powerful, open, and highly customizable in-vehicle operating system. It not only seamlessly supports a large number of Android applications but also provides a wealth of in-vehicle services and development toolchains, bringing great convenience to automakers and developers.

[0003] However, in the solutions of AndroidAutomotiveOS or AndroidCarOS, when restoring the target audio source after a power failure or restarting, or when switching the target audio source, the final execution result of the target audio source is not clear, and AndroidAutomotiveOS or AndroidCarOS does not provide a corresponding solution. Summary of the Invention

[0004] In a first aspect, embodiments of this application provide an information display method applied to an in-vehicle system. The method includes: establishing a connection with a target audio source and receiving a first media session token sent by the target audio source through the connection; wherein the target audio source includes an audio source to which the user wishes to switch or an audio source that was playing before a power outage and restart; constructing a first media controller through the first media session token and sending a first command to the target audio source through the first media controller; wherein the first command is used to control the playback state of the target audio source; obtaining the execution result of the first command by the target audio source through a callback mechanism of the first media controller and displaying the execution result in an interactive window.

[0005] It is understood that, in this embodiment of the application, a solution is provided in the vehicle system where the final execution result of the target audio source cannot be known. Specifically, after establishing a connection with the desired audio source, or after a power outage and restart, and after establishing a connection with the audio source that was playing before the power outage and restart, the vehicle system receives a first media session token sent by the audio source through the connection, and constructs a first media controller based on this token. The media controller then sends a command to the audio source to control its playback state (i.e., a first command), and uses the callback mechanism of the first media controller to obtain the audio source's execution result for the command, finally displaying the execution result on the interactive window.

[0006] In this way, in in-vehicle applications, the driver or other people in the car can intuitively see on the screen of the in-vehicle terminal whether the desired audio source has been switched successfully, or whether the audio source that was playing before the power outage has been restored after a power outage and restart. This solves the user pain point that the driver or other people in the car have no way of knowing the execution results in these two scenarios in in-vehicle applications, and the driver or other people in the car do not need to go through cumbersome operations to find the execution results in these two scenarios, thus making it more in line with the characteristics of in-vehicle applications.

[0007] Secondly, embodiments of this application provide an information display device applied to an in-vehicle system. The device includes: a connection module configured to establish a connection with a target audio source; wherein the target audio source includes an audio source to which the user wishes to switch or an audio source that was playing before a power outage and restart; a receiving module configured to receive a first media session token sent by the target audio source through the connection; a construction module configured to construct a first media controller using the first media session token; a sending module configured to send a first command to the target audio source through the first media controller; wherein the first command is used to control the playback state of the target audio source; an acquisition module configured to acquire the execution result of the first command from the target audio source through a callback mechanism of the first media controller; and a display module configured to display the execution result in an interactive window.

[0008] Thirdly, embodiments of this application provide an in-vehicle terminal, including a memory and a processor. The memory stores a computer program that can run on the processor, and the processor executes the program to implement the method described in the first aspect.

[0009] Fourthly, embodiments of this application provide a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor or an in-vehicle terminal, implements the method described in the first aspect.

[0010] Fifthly, embodiments of this application provide a computer program product, including a computer program or instructions, which, when executed by a processor or vehicle terminal, implement the method described in the first aspect of this application.

[0011] Sixthly, embodiments of this application provide a computer program that causes a processor or vehicle terminal to perform the method described in the first aspect.

[0012] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and do not limit this application. Attached Figure Description

[0013] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the specification, serve to explain the technical solutions of this application. Obviously, the drawings described below are merely some embodiments of this application, and those skilled in the art can obtain other drawings based on these drawings without any inventive effort.

[0014] The flowcharts shown in the accompanying drawings are merely illustrative and do not necessarily include all content and operations / steps, nor do they necessarily have to be performed in the described order. For example, some operations / steps can be broken down, while others can be combined or partially combined; therefore, the actual execution order may change depending on the specific circumstances.

[0015] Figure 1 A schematic diagram illustrating the implementation flow of the information display method provided in this application embodiment;

[0016] Figure 2 A schematic diagram illustrating a further implementation of step 101 provided in an embodiment of this application;

[0017] Figure 3 A further implementation flow diagram of step 201 provided in the embodiments of this application. Figure 1 ;

[0018] Figure 4 A schematic diagram of the in-vehicle interactive window provided in the embodiments of this application. Figure 1 ;

[0019] Figure 5 A schematic diagram of the in-vehicle interactive window provided in the embodiments of this application. Figure 2 ;

[0020] Figure 6 This is a schematic diagram of the steering wheel control buttons on a vehicle provided in an embodiment of this application;

[0021] Figure 7 A schematic diagram of the in-vehicle interactive window provided in the embodiments of this application. Figure 1 ;

[0022] Figure 8 A further implementation flow diagram of step 201 provided in the embodiments of this application. Figure 2 ;

[0023] Figure 9 This is a schematic diagram of the structure of the information display device provided in the embodiments of this application;

[0024] Figure 10 This is a schematic diagram of the structure of the vehicle-mounted terminal provided in an embodiment of this application. Detailed Implementation

[0025] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the specific technical solutions of this application will be further described in detail below with reference to the accompanying drawings of the embodiments of this application. The following embodiments are used to illustrate this application, but are not intended to limit the scope of this application.

[0026] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used herein is for the purpose of describing embodiments of this application only and is not intended to limit this application.

[0027] In the following description, references to "some embodiments," "this embodiment," "this application embodiment," and examples, etc., describe a subset of all possible embodiments. However, it is understood that "some embodiments" may be the same subset or different subset of all possible embodiments and may be combined with each other without conflict.

[0028] The descriptions such as "first," "second," and "third" appearing in the embodiments of this application are for illustrative purposes and to distinguish the objects being described. They do not indicate any order and do not represent a special limitation on the number of devices in the embodiments of this application. They cannot constitute any limitation on the embodiments of this application.

[0029] Before providing a further detailed description of the embodiments of this application, the nouns and terms that may be involved in the embodiments of this application will be explained first. The nouns and terms involved in the embodiments of this application are subject to the following interpretations.

[0030] AndroidAutomotive: Android in-vehicle operating system; "AndroidAutomotive" can also be described as "AndroidAutomotiveOS" or "AndroidCarOS", etc.

[0031] CarMediaService: In-vehicle media services;

[0032] startService: Starts the service;

[0033] MediaBrowserService: Media browser service;

[0034] MediaSession: Media session;

[0035] MediaController: Media controller;

[0036] MediaSession.Token: Media session token;

[0037] MediaBrowser: Media browser;

[0038] Bundle: A class in Android used to save and transfer data, supporting cross-process communication;

[0039] PackageManager: A class in the Android system that manages application packages;

[0040] PackageName: The application package name, which is unique for each application;

[0041] appName: Application name;

[0042] AM: Amplitude Modulation Broadcasting, is a broadcasting method that uses amplitude modulation to transmit broadcast signals;

[0043] FM: Frequency Modulation Broadcasting is a broadcasting method that uses frequency modulation to transmit broadcast signals.

[0044] In AndroidAutomotiveOS, media playback information is recorded through CarMediaService. The logic for automatic recovery is to start the target media service (i.e., the target audio source application / target media application) through startService. However, there is no standard solution for switching audio sources.

[0045] Furthermore, the inventors of this application discovered the following technical problems and user pain points during their research and analysis:

[0046] (1) When the AndroidCarOS (Android Car System) solution is executed to restore playback, it is not clear about the final result of the target audio source, such as whether playback has been restored or whether there is a problem that prevents playback from being restored; for example, a music application was playing before the power was turned off, and after the power was turned off and then turned on again, the music application is the target audio source.

[0047] (2) There is currently no recommended solution for switching audio sources.

[0048] In view of this, embodiments of this application provide the following information display method, which is applied to an in-vehicle system. In these embodiments, the type of in-vehicle system is not limited; the in-vehicle system may be Android Automotive OS or other types of operating systems.

[0049] Figure 1 This is a schematic diagram illustrating the implementation flow of the information display method provided in the embodiments of this application; as follows: Figure 1 As shown, the method may include the following steps 101 to 106:

[0050] Step 101: Establish a connection with the target audio source; wherein, the target audio source includes the audio source to which you wish to switch or the audio source that was playing before the power outage and restart.

[0051] Step 102: Receive the first media session token sent by the target audio source through the connection;

[0052] Step 103: Construct the first media controller using the first media session token;

[0053] Step 104: Send a first command to the target audio source through the first media controller; wherein the first command is used to control the playback status of the target audio source;

[0054] Step 105: Obtain the execution result of the target audio source for the first command through the callback mechanism of the first media controller;

[0055] Step 106: Display the execution result in the interactive window.

[0056] It is understood that, in this embodiment of the application, a solution is provided in the vehicle system where the final execution result of the target audio source cannot be known. Specifically, after establishing a connection with the desired audio source, or after a power outage and restart, and after establishing a connection with the audio source that was playing before the power outage and restart, the vehicle system receives a first media session token sent by the audio source through the connection, and constructs a first media controller based on this token. The media controller then sends a command to the audio source to control its playback state (i.e., a first command), and uses the callback mechanism of the first media controller to obtain the audio source's execution result for the command, finally displaying the execution result on the interactive window.

[0057] In this way, in in-vehicle applications, the driver or other people in the car can intuitively see on the screen of the in-vehicle terminal whether the desired audio source has been switched successfully, or whether the audio source that was playing before the power outage has been restored after a power outage and restart. This solves the user pain point that the driver or other people in the car have no way of knowing the execution results in these two scenarios in in-vehicle applications, and the driver or other people in the car do not need to go through cumbersome operations to find the execution results in these two scenarios, thus making it more in line with the characteristics of in-vehicle applications.

[0058] The following sections will describe further optional implementation methods for each of the above steps, as well as related terms.

[0059] Step 101: Establish a connection with the target audio source; wherein, the target audio source includes the audio source to which you wish to switch or the audio source that was playing before the power outage and restart.

[0060] It should be noted that, for scenarios where the target audio source is the audio source that was playing before the power outage and restart, the steps of the information display method provided in this application embodiment are operations performed by the vehicle system after the power outage and restart.

[0061] In some embodiments, such as Figure 2 As shown, step 101 may further include the following steps 201 and 202:

[0062] Step 201: Obtain the audio source information of the target audio source; wherein the audio source information of the target audio source includes at least one of the following: application package name, media application service class name, and application name.

[0063] In the embodiments of this application, the methods for obtaining the sound source information of the target sound source may be different for different scenarios.

[0064] In scenarios where the target audio source includes the audio source to which the user wishes to switch, furthermore, in some embodiments, such as... Figure 3 As shown, step 201 may include the following steps 301 and 302:

[0065] Step 301: Receive a switching instruction, which is used to instruct the currently playing audio source to be switched to the target audio source.

[0066] There are no restrictions on how users input switching commands. Users can switch audio sources by touching the application icon or application name of the audio source on the in-vehicle interactive window, or by pressing a specific control button on the vehicle.

[0067] For example, Figure 4 A schematic diagram of the in-vehicle interactive window provided in the embodiments of this application. Figure 1 ;like Figure 4 As shown, the in-vehicle interaction window 400 displays application icons for multiple different audio sources, i.e., an audio source list. Users can select any audio source's application icon to indicate the audio source they want to play. When the in-vehicle system detects that an application icon for an audio source on the in-vehicle interaction window 400 has been selected, it confirms that a switching command has been received; the audio source corresponding to the selected application icon can be understood as the target audio source.

[0068] For example, Figure 5 A schematic diagram of the in-vehicle interactive window provided in the embodiments of this application. Figure 2 ;like Figure 5As shown, the in-vehicle interactive window 500 displays playback-related information and icons for the currently playing audio source. The playback-related information includes the album art 501, the name 502, the author information 503, a third icon 504, a fourth icon 505, a fifth icon 506, and a second icon 507. When the user clicks the second icon 507, an application list of multiple currently playing audio sources (i.e., an audio source list) pops up in the interactive window 500. The user can then select the desired audio source from this list.

[0069] In one possible implementation, users can also select which audio source they want to switch to by pressing the steering wheel control button on the vehicle.

[0070] For example, Figure 6 This is a schematic diagram of the vehicle-mounted steering wheel control buttons provided in an embodiment of this application; as shown. Figure 6 As shown, users can press the "MODE" control button to bring up a list of application icons and / or application names (i.e., a list of audio sources) that display multiple audio sources. For example... Figure 7 As shown, when a user presses the "MODE" control button for the first time, either interaction window 700 or interaction window 400 will appear. Taking interaction window 700 as an example, if the user presses MODE once, the currently playing audio source switches to the first audio source 701 in the audio source list; if the user presses MODE again, the currently playing audio source switches to the second audio source 702 in the audio source list, and so on. That is, the user switches the audio source by pressing MODE. The press operation received by the control button can be understood as the switching command, or the vehicle system generates the switching command based on the press operation received by the control button.

[0071] Step 302: According to the switching instruction, obtain the audio source information of the target audio source from the pre-built media service information; wherein, the pre-built media service information includes the audio source information of multiple audio sources.

[0072] In this embodiment of the application, the pre-built media service information may include media service information of some or all media applications (i.e., audio sources) on the vehicle system, and / or media service information of some or all media applications (i.e., audio sources) on electronic devices (such as mobile phones, tablets, etc.) connected to the vehicle terminal.

[0073] For example, in one possible implementation, the media service information can be pre-constructed as follows:

[0074] When the media center starts, it scans the entire in-vehicle system's applications using Android PackageManager queryIntentServices to obtain the media application dataset. It then parses the obtained dataset and uses ServiceInfo.packageName (application package name), ServiceInfo.name (media application service class name), and ServiceInfo.loadLabel(packageManager).toString() (application name) to construct and maintain information about all media services in the in-vehicle system.

[0075] It is understood that, in the embodiments of this application, an implementation scheme for audio source switching is provided in the vehicle system. Based on this scheme, users can switch audio sources through media audio source interaction windows or steering wheel control buttons, thereby reducing the customization and coupling of various media applications, and appropriately providing users with feedback on the switching results.

[0076] As can be understood, the above describes how to obtain the audio source information of a target audio source, including the audio source to which the user expects to switch. The following will describe how to obtain the audio source information of a target audio source, including the audio source that was playing before the power outage and restart.

[0077] for Figure 2 In step 201 shown, the audio source information of the target audio source is obtained; wherein, the audio source information of the target audio source includes at least one of the following: application package name, media application service class name, and application name.

[0078] In the embodiments of this application, the methods for obtaining the sound source information of the target sound source may be different for different scenarios.

[0079] In scenarios where the target audio source includes the audio source that was playing before the power outage and restart, further, in some embodiments, such as Figure 8 As shown, step 201 may include the following steps 801 to 803:

[0080] Step 801: Before power failure and restart, record the relevant information of the audio source that is playing.

[0081] In some embodiments, step 801 may further include: listening to the second media session token before power failure and restart; constructing a second media controller through the second media session token if a change is detected in the second media session token; obtaining the playback status of the corresponding audio source and related information of the corresponding audio source through the second media controller; and recording the related information of the corresponding audio source if the playback status is "playing".

[0082] For example, in one possible implementation, the recording of information related to the currently playing audio source can be achieved as follows:

[0083] Before a power outage and restart, when a media application (i.e., an audio source) starts playing, the media application starts the MediaBrowserService and creates the corresponding MediaSession. At this time, media information (i.e., playback information, such as one or more of the following, including but not limited to song information, status, album art, lyrics, etc.) is set in the MediaSession and the playback status is updated.

[0084] Additionally, during media center initialization, the MediaSessionManager.addOnMediaKeyEventSessionChangedListener method listens for changes in the vehicle system's MediaSession.Token. When media playback is triggered, the callback (Callback, cb) of the aforementioned method detects a change in MediaSession.Token and constructs a MediaController using MediaSession.token. Based on the constructed MediaController, the application is identified using MediaController.getPackageName() (e.g., the package name of the media application), and the playback status is obtained using MediaController.getPlaybackState(). If playback is in progress, the package name and application name (appName) of the media application are recorded in a file.

[0085] Step 802: After power failure and restart, determine the target audio source that matches the relevant information in the pre-built media service information; wherein, the pre-built media service information includes audio source information of multiple audio sources.

[0086] Step 803: Obtain the audio source information of the target audio source from the pre-built media service information.

[0087] For example, in one possible implementation, after a power outage and power-on (i.e., after a power outage and restart), the media center restarts and, through the pre-built media service information mentioned above, matches the relevant information of the target audio source that was playing before the power outage and restart (such as the package name and application name of the media application that was playing before the power outage and restart, i.e. before the power was turned off), to find the audio source information of the target audio source.

[0088] It is understood that once the audio source information of the target audio source (such as application package name, media application service type and / or application name, etc.) is obtained, a connection can be established with the target audio source based on the audio source information.

[0089] That is, such as Figure 2 As shown, in step 202, a connection is established with the target sound source based on the sound source information of the target sound source.

[0090] In some embodiments, step 202 may further include: constructing a media browser based on the audio source information of the target audio source, and invoking a connection method through the media browser to establish a connection with the target audio source.

[0091] For example, in one possible implementation, a MediaBrowser object is constructed using the audio source information, and then the MediaBrowser object's connect method is executed to connect to the target audio source.

[0092] Step 102: Receive the first media session token sent by the target audio source through the connection;

[0093] Step 103: Construct the first media controller using the first media session token;

[0094] Step 104: Send a first command to the target audio source through the first media controller; wherein the first command is used to control the playback status of the target audio source.

[0095] In this embodiment of the application, there is no limitation on the first command. The first command can be a play command, a pause command, or a stop command, etc.

[0096] Step 105: Obtain the execution result of the first command from the target audio source through the callback mechanism of the first media controller.

[0097] For steps 102 to 105, for example, in one possible implementation, the execution result can be obtained as follows:

[0098] Once a connection to the target audio source is successfully established, the target audio source (i.e., the target media application) sends a media session token, thus obtaining the corresponding MediaSession.Token of the target audio source / target media application. A MediaController is then constructed using the MediaSession.token. The MediaController.sendCommand(String command, Bundle args, ResultReceiver cb) method is used to add relevant scenario descriptions to the args parameter, such as "power-on / off recovery" or "audio source switching" (an example of the first command). The cb parameter (callback parameter) receives the execution result from the target audio source.

[0099] Step 106: Display the execution result in the interactive window.

[0100] In some embodiments, the execution result includes successful execution of the first command. In other embodiments, the execution result includes failure of the first command and the reason for the failure.

[0101] For example, in a scenario involving audio source switching, the execution result might be successful switching or failure switching, with the failure possibly due to a network connection failure. Similarly, in a scenario involving resuming playback after a power outage, the execution result might be successful playback resumption after a power outage and restart, or failure playback resumption after a power outage and restart, with the failure possibly due to a network connection failure.

[0102] It is understandable that the above-mentioned Android standard interface design technology solution realizes the restoration of media playback and audio source switching, reduces the customization and coupling of various media applications, and appropriately provides users with feedback on the execution results of audio source restoration or audio source switching, thereby improving the user's driving experience.

[0103] It should be noted that, in the embodiments of this application, the audio source can also be understood as a media application or media audio source, etc.

[0104] It should be noted that although the steps of the method in this application are described in a specific order in the accompanying drawings, this does not require or imply that the steps must be performed in that specific order, or that all the steps shown must be performed to achieve the desired result. Additional or alternative steps may be omitted, multiple steps may be combined into one step, and / or one step may be broken down into multiple steps; or steps from different embodiments may be combined into a new technical solution.

[0105] Based on the foregoing embodiments, this application provides an information display device applied to an in-vehicle system.

[0106] Figure 9 This is a schematic diagram of the structure of the information display device provided in the embodiments of this application; as shown below. Figure 9 As shown, the information display device 900 includes a connection module 901, a receiving module 902, a construction module 903, a sending module 904, an acquisition module 905, and a display module 906; wherein:

[0107] The connection module 901 is configured to establish a connection with a target audio source; wherein, the target audio source includes the audio source to which the user wishes to switch or the audio source that was playing before the power outage and restart.

[0108] The receiving module 902 is configured to receive a first media session token sent by the target audio source via a connection;

[0109] Module 903 is configured to construct a first media controller using a first media session token.

[0110] The sending module 904 is configured to send a first command to the target audio source through the first media controller; wherein the first command is used to control the playback status of the target audio source;

[0111] The acquisition module 905 is configured to obtain the execution result of the target audio source for the first command through the callback mechanism of the first media controller;

[0112] Display module 906 is configured to display the execution results in the interactive window.

[0113] In some embodiments, the execution result includes successful execution of the first command. In other embodiments, the execution result includes failure of the first command and the reason for the failure.

[0114] In some embodiments, the connection module 901 is configured to: obtain audio source information of a target audio source; wherein the audio source information of the target audio source includes at least one of the following: application package name, media application service class name, and application name; and establish a connection with the target audio source based on the audio source information.

[0115] Furthermore, in some embodiments, the connection module 901 is configured to: construct a media browser based on the audio source information, and call a connection method through the media browser to establish a connection with the target audio source.

[0116] Furthermore, in some embodiments, the target audio source includes an audio source to which the user wishes to switch; the connection module 901 is configured to: receive a switching instruction, which instructs the user to switch the currently playing audio source to the target audio source; and, according to the switching instruction, obtain audio source information of the target audio source from pre-built media service information; wherein the pre-built media service information includes audio source information of multiple audio sources.

[0117] Furthermore, in some other embodiments, the target audio source includes the audio source that was playing before the power outage and restart; the connection module 901 is configured to: record relevant information of the audio source that was playing before the power outage and restart; and determine the target audio source that matches the relevant information in the pre-built media service information after the power outage and restart; wherein the pre-built media service information includes audio source information of multiple audio sources; and obtain the audio source information of the target audio source from the pre-built media service information.

[0118] For example, in some embodiments, the connection module 901 is configured to: listen for a second media session token before a power outage and restart; construct a second media controller through the second media session token if a change is detected in the second media session token; obtain the playback status of the corresponding audio source and related information of the corresponding audio source through the second media controller; and record the related information of the corresponding audio source if the playback status is "playing".

[0119] The descriptions of the above device embodiments are similar to those of the above method embodiments, and have similar beneficial effects. For technical details not disclosed in the device embodiments of this application, please refer to the descriptions of the method embodiments of this application for understanding.

[0120] It should be noted that the module division in the embodiments of this application is illustrative and only represents one logical functional division. In actual implementation, there may be other division methods. Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, exist as separate physical units, or have two or more units integrated into one unit. The integrated units can be implemented in hardware, as software functional units, or a combination of software and hardware.

[0121] It should be noted that, in the embodiments of this application, if the above-described methods are implemented as software functional modules and sold or used as independent products, they can also be stored in a computer-readable storage medium. Based on this understanding, the technical solutions of the embodiments of this application, or the parts that contribute to related technologies, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause the vehicle terminal to execute all or part of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), magnetic disks, or optical disks. Thus, the embodiments of this application are not limited to any specific hardware and software combination.

[0122] This application provides a vehicle-mounted terminal.

[0123] Figure 10 This is a schematic diagram of the structure of the vehicle-mounted terminal provided in the embodiments of this application; as shown below. Figure 10 As shown, the vehicle terminal 100 includes a memory 1001 and a processor 1002. The memory 1001 stores a computer program that can run on the processor 1002. When the processor 1002 executes the program, it implements the steps in the method provided in the above embodiments.

[0124] It should be noted that the memory 1001 is configured to store instructions and applications executable by the processor 1002, and can also cache data to be processed or already processed (e.g., image data, audio data, voice communication data and video communication data) in the processor 1002 and the various modules in the vehicle terminal 100. It can be implemented by flash memory or random access memory (RAM).

[0125] This application also provides a computer-readable storage medium for storing computer programs.

[0126] Optionally, the computer-readable storage medium can be applied to the vehicle terminal in the embodiments of this application, and the computer program causes the processor or vehicle terminal to execute the various methods of the embodiments of this application. For the sake of brevity, these will not be described in detail here.

[0127] This application also provides a computer program product, including computer program instructions.

[0128] Optionally, the computer program product can be applied to the vehicle terminal in the embodiments of this application, and the computer program instructions cause the processor or vehicle terminal to execute the various methods of the embodiments of this application. For the sake of brevity, they will not be described in detail here.

[0129] This application also provides a computer program.

[0130] Optionally, the computer program can be applied to the vehicle terminal in the embodiments of this application. When the computer program runs on the processor or the vehicle terminal, it causes the processor or the vehicle terminal to execute the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0131] It should be noted that the descriptions of the vehicle-mounted terminal, storage medium, computer program product, and computer program embodiments above are similar to the descriptions of the method embodiments above, and have similar beneficial effects. For technical details not disclosed in the vehicle-mounted terminal, storage medium, computer program product, and computer program embodiments of this application, please refer to the descriptions of the method embodiments of this application for understanding.

[0132] It should be understood that the phrases "one embodiment," "an embodiment," or "some embodiments" mentioned throughout the specification mean that a specific feature, structure, or characteristic related to an embodiment is included in at least one embodiment of this application. Therefore, "in one embodiment," "in one embodiment," or "in some embodiments" appearing throughout the specification do not necessarily refer to the same embodiment. Furthermore, these specific features, structures, or characteristics can be combined in any suitable manner in one or more embodiments. It should be understood that in the various embodiments of this application, the sequence numbers of the above-described processes do not imply a sequential order of execution; the execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application. The sequence numbers of the above-described embodiments are merely for descriptive purposes and do not represent the superiority or inferiority of the embodiments. The descriptions of the various embodiments above tend to emphasize the differences between the various embodiments; their similarities or commonalities can be referred to mutually, and for the sake of brevity, they will not be repeated here.

[0133] In this article, the term "and / or" is merely a description of the relationship between related objects, indicating that there can be three kinds of relationships. For example, object A and / or object B can represent three situations: object A exists alone, object A and object B exist simultaneously, and object B exists alone.

[0134] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element.

[0135] In the several embodiments provided in this application, it should be understood that the disclosed devices and methods can be implemented in other ways. The embodiments described above are merely illustrative. For example, the division of modules is only a logical functional division, and in actual implementation, there may be other division methods, such as: multiple modules or components can be combined, or integrated into another system, or some features can be ignored or not executed. In addition, the coupling, direct coupling, or communication connection between the various components shown or discussed can be through some interfaces, and the indirect coupling or communication connection between devices or modules can be electrical, mechanical, or other forms.

[0136] The modules described above as separate components may or may not be physically separate. The components shown as modules may or may not be physical modules. They may be located in one place or distributed across multiple network units. Some or all of the modules may be selected to achieve the purpose of this embodiment according to actual needs.

[0137] In addition, each functional module in the various embodiments of this application can be integrated into one processing unit, or each module can be a separate unit, or two or more modules can be integrated into one unit; the integrated modules can be implemented in hardware or in the form of hardware plus software functional units.

[0138] Those skilled in the art will understand that all or part of the steps of the above method embodiments can be implemented by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When the program is executed, it performs the steps of the above method embodiments. The aforementioned storage medium includes various media that can store program code, such as mobile storage devices, read-only memory (ROM), magnetic disks, or optical disks.

[0139] Alternatively, if the integrated units described above are implemented as software functional modules and sold or used as independent products, they can also be stored in a computer-readable storage medium. Based on this understanding, the technical solutions of the embodiments of this application, or the parts that contribute to related technologies, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause the vehicle terminal to execute all or part of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as mobile storage devices, ROMs, magnetic disks, or optical disks.

[0140] The methods disclosed in the several method embodiments provided in this application can be arbitrarily combined without conflict to obtain new method embodiments.

[0141] The features disclosed in the several product embodiments provided in this application can be arbitrarily combined without conflict to obtain new product embodiments.

[0142] The features disclosed in the several method or device embodiments provided in this application can be arbitrarily combined without conflict to obtain new method or device embodiments.

[0143] The above description is merely an embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. An information display method, characterized in that, The method is applied to an in-vehicle system, and the method includes: Establish a connection with a target audio source and receive a first media session token sent by the target audio source through the connection; wherein, the target audio source includes the audio source to which the user wishes to switch or the audio source that was playing before the power outage and restart. A first media controller is constructed using the first media session token, and a first command is sent to the target audio source through the first media controller; wherein, the first command is used to control the playback state of the target audio source; The execution result of the first command by the target audio source is obtained through the callback mechanism of the first media controller, and the execution result is displayed in the interactive window.

2. The method according to claim 1, characterized in that, The execution result includes the first command being executed successfully; or the execution result includes the first command failing to execute and the reason for the failure.

3. The method according to claim 1 or 2, characterized in that, The establishment of a connection with the target sound source includes: Obtain the audio source information of the target audio source; wherein, the audio source information includes at least one of the following: application package name, media application service class name, and application name; A connection is established with the target audio source based on the audio source information.

4. The method according to claim 3, characterized in that, The target audio source includes the audio source to which the user wishes to switch; obtaining the audio source information of the target audio source includes: Receive a switching instruction, the switching instruction being used to instruct the currently playing audio source to be switched to the target audio source; According to the switching instruction, the audio source information of the target audio source is obtained from the pre-built media service information; wherein, the media service information includes audio source information of multiple audio sources.

5. The method according to claim 3, characterized in that, The target audio source includes the audio source that was playing before the power outage and restart; obtaining the audio source information of the target audio source includes: Record relevant information about the audio source being played before the power is turned off and restarted; After a power outage and restart, the target audio source that matches the relevant information in the pre-built media service information is identified; wherein, the media service information includes audio source information of multiple audio sources; The audio source information of the target audio source is obtained from the pre-built media service information.

6. The method according to claim 5, characterized in that, Before power failure and restart, the system records relevant information about the currently playing audio source, including: Before power failure and restart, listen for the second media session token; if a change is detected in the second media session token, construct a second media controller using the second media session token. The playback status of the corresponding audio source and related information of the corresponding audio source are obtained through the second media controller; When the playback status is "playing", record the relevant information of the corresponding audio source.

7. The method according to claim 3, characterized in that, The step of establishing a connection with the target sound source based on the sound source information includes: A media browser is constructed based on the audio source information, and a connection method is invoked through the media browser to establish a connection with the target audio source.

8. An information display device, characterized in that, The device is used in a vehicle-mounted system, and the device includes: A connection module is configured to establish a connection with a target audio source; wherein, the target audio source includes the audio source to which the user wishes to switch or the audio source that was playing before the power outage and restart. The receiving module is configured to receive a first media session token sent by the target audio source through the connection; The construction module is configured to construct a first media controller using the first media session token; The sending module is configured to send a first command to the target audio source through the first media controller; wherein the first command is used to control the playback state of the target audio source; The acquisition module is configured to acquire the execution result of the target audio source for the first command through the callback mechanism of the first media controller; The display module is configured to display the execution results in the interactive window.

9. A vehicle-mounted terminal, comprising a memory and a processor, wherein the memory stores a computer program executable on the processor, characterized in that, When the processor executes the program, it implements the method of any one of claims 1-7.

10. A computer program product, comprising a computer program or instructions, characterized in that, When the computer program or instructions are executed by a processor or vehicle terminal, they implement the method of any one of claims 1-7.

Images