Cockpit multi-sound-zone management method, related apparatus and communication system

Abstract

A cockpit multi-sound-zone management method, a related apparatus and a communication system. A cockpit system can divide a plurality of screens into a plurality of driver-passenger zones on the basis of a configuration file. Each driver-passenger zone can be associated with one sound zone. The cockpit system can dynamically create and delete a sound zone on the basis of the connection and removal of a sound production device. The cockpit system can perform unified management on the audio focus, volume, audio routing and media session in a sound zone. An application corresponding to a driver-passenger zone can apply for the audio focus in a sound zone associated with the driver-passenger zone, and a sound production device in the sound zone is used to play audio. The audio playing in different sound zones can be independent of each other and not affect each other. In this way, different users in a vehicle can conveniently listen to audio using different sound zones, thereby improving the audio listening experience of the users in the vehicle.

Description

Cockpit multi-sound zone management method, related device and communication system

[0001] This application claims priority to the Chinese patent application with application number 202311669639.4 filed with the State Intellectual Property Office of China on December 5, 2023, and priority to the Chinese patent application entitled "Cockpit multi-tone zone management method, related devices and communication system", all contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of intelligent automobile technology, and in particular to a cockpit multi-sound zone management method, related devices, and communication systems. Background Art

[0003] With the development of electronic products, vehicles are increasingly equipped with more and more electronic devices. Vehicles are also becoming increasingly intelligent. The cockpit system of a smart vehicle can be equipped with intelligent and connected in-vehicle products, enabling intelligent interaction with people, the road, and the vehicle itself. Today's cockpit systems can support an increasing number of screens and audio devices. Based on these screens and audio devices, the cockpit system can be divided into one or more audio zones. The cockpit system needs to manage these audio zones to provide users in different positions in the vehicle with a better driving experience. Summary of the Invention

[0004] This application provides a cockpit multi-zone management method, related devices, and communication system that can dynamically create or delete audio zones based on changes in external sound devices in the cockpit system. The cockpit system can centrally manage the audio focus, volume, audio routing, and media sessions within a zone. Furthermore, audio playback in each zone can be independent and independent of each other. This allows different users in the vehicle to listen to audio in different zones, improving the user's in-vehicle audio listening experience.

[0005] In the first aspect, the present application provides a cockpit multi-zone management method, which is applied to a vehicle, wherein the vehicle includes an in-vehicle speaker and multiple screens, wherein the multiple screens include a first screen and a second screen, and the first screen and the second screen are both associated with the first sound zone corresponding to the in-vehicle speaker. The vehicle can detect that the first application on the second screen requests to play the first audio, and plays the first audio through the in-vehicle speaker; the vehicle detects that the second application on the first screen requests to play the second audio, plays the second audio through the in-vehicle speaker, and pauses the first audio or reduces the volume of the first audio; the vehicle detects an input operation on the second screen to access the first sound device, the vehicle connects to the first sound device, and creates a second sound zone corresponding to the first sound device; the sound zone associated with the second screen changes from the first sound zone to the second sound zone; the vehicle again detects that the first application requests to play the first audio, and plays the first audio through the first sound device.

[0006] It can be seen that when the vehicle has no external sound device, the vehicle can include a first sound zone associated with the in-vehicle speakers. All screens in the vehicle can be associated with the first sound zone. When the vehicle is connected to an external sound device, the vehicle can create a new sound zone and associate the corresponding screen with the newly created sound zone. In this way, the sound zone associated with the screen can be dynamically adjusted to separate the audio applied on different screens to different sound devices for playback. In this way, different users can connect different sound devices to different screens, and then use different sound devices to listen to the audio they want to listen to without affecting each other. This can improve the audio listening experience of users sitting in different positions in the vehicle.

[0007] In combination with the first aspect, in some embodiments, a first configuration file is stored in the vehicle, and the first configuration file is used to indicate the correspondence between multiple screens and driving areas, wherein any one of the multiple screens corresponds to a driving area, the sound zone associated with the screen corresponding to the same driving area remains consistent, and the sound zones associated with the screens corresponding to different driving areas are the same or different.

[0008] Different models of vehicles may have different screens in their cockpit systems. The above embodiment allows configuration of the driving and passenger areas of different models simply by modifying the configuration files for each model. Different models of vehicle cockpit systems can create driving and passenger areas based on their corresponding configuration files.

[0009] In combination with the first aspect, in some embodiments, the vehicle includes a first audio focus stack corresponding to the first sound zone, and the first audio focus stack includes audio focus information of an application running in the foreground or background on the screen associated with the first sound zone; after the vehicle detects an input operation acting on the second screen connected to the first sound device, it can create a second audio focus stack corresponding to the second sound zone, and migrate the audio focus information of the application running in the foreground or background on the second screen from the first audio focus stack to the second audio focus stack.

[0010] In combination with the first aspect, in some embodiments, the vehicle includes a first audio routing table corresponding to a first sound zone, the first audio routing table includes application information of an application running in the foreground or background on a screen associated with the first sound zone, and the first audio routing table is configured with a first audio channel of an in-vehicle speaker, which is used to indicate that the audio of the application corresponding to the application information in the first audio routing table is routed to the first audio channel; after the vehicle detects an input operation acting on the second screen to access the first sound device, it can create a second audio routing table corresponding to the second sound zone, and migrate the application information of the application running in the foreground or background on the second screen from the first audio routing table to the second audio routing table; and create a second audio channel for the first sound device, and configure the second audio channel in the second audio routing table, the second audio channel configured in the second audio routing table is used to indicate that the audio of the application corresponding to the application information in the second audio routing table is routed to the second audio channel.

[0011] In combination with the first aspect, in some embodiments, the vehicle includes a first media session stack corresponding to a first audio zone, and the first media session stack includes a media session of an application running in the foreground or background on a screen associated with the first audio zone; after the vehicle detects an input operation acting on the second screen accessing the first sound device, it can create a second media session stack corresponding to a second audio zone, and migrate the media session of the application running in the foreground or background on the second screen from the first media session stack to the second media session stack.

[0012] In combination with the first aspect, in some embodiments, before the vehicle detects an input operation on the second screen for accessing the first sound device, when an input operation on the first screen for viewing audio playback information is detected, the vehicle can display a first list on the first screen according to the first media session stack, and the first list includes the audio playback information indicated by the first media session stack; when an input operation on the second screen for viewing audio playback information is detected, the vehicle displays the first list on the second screen according to the first media session stack.

[0013] In combination with the first aspect, in some embodiments, the first list includes audio playback information of the first audio; when the second audio is played by the in-car speaker and the first audio is paused, the vehicle detects an input operation on the audio playback information of the first audio in the first list on the first screen, and the input operation on the audio playback information of the first audio in the first list is used to play the first audio; in combination with the first aspect, in some embodiments, the first audio is played through the in-car speaker, and the second audio is paused.

[0014] In combination with the first aspect, in some embodiments, after the vehicle detects an input operation on the second screen for accessing the first sound device, it can detect an input operation on the first screen for viewing audio playback information, and display a second list on the first screen according to the first media session stack, the second list includes the audio playback information indicated by the first media session stack, and the second list does not include the audio playback information of the first audio; after detecting an input operation on the second screen for viewing audio playback information, a third list is displayed on the second screen according to the second media session stack, the third list includes the audio playback information indicated by the second media session stack, and the second list includes the audio playback information of the first audio.

[0015] In combination with the first aspect, in some embodiments, after the vehicle is connected to the first sound-emitting device, an input operation for adjusting the volume to the first volume is detected on the second screen, and the volume of the audio played by the first sound-emitting device is adjusted to the first volume.

[0016] In combination with the first aspect, in some embodiments, after the vehicle is connected to the first sound device, an input operation on the first screen for adjusting the volume to a second volume is detected, and the volume of the audio played by the in-vehicle speakers is adjusted to the second volume.

[0017] It can be seen that the volume in different sound zones can be adjusted independently without affecting each other.

[0018] In combination with the first aspect, in some embodiments, the first interface of the second application is displayed on the first screen, and the first interface is the playback interface of the second audio. After the vehicle is connected to the first sound device, when an input operation to migrate the first interface from the first screen to the second screen is detected, the vehicle can display the first interface on the second screen, cancel the display of the first interface on the first screen, and switch the second audio from the in-vehicle speaker to the first sound device to continue playing.

[0019] In combination with the first aspect, in some embodiments, after the vehicle switches the second audio from the in-car speaker to the first sound device to continue playing, when it detects that the third application on the first screen requests to play the third audio, the vehicle plays the third audio through the in-car speaker.

[0020] In combination with the first aspect, in some embodiments, after the vehicle switches the second audio from the in-vehicle speaker to the first sound device to continue playing, when it detects that the first application on the second screen requests to play the first audio, the vehicle plays the first audio through the first sound device and pauses the second audio or lowers the playback volume of the second audio.

[0021] In combination with the first aspect, in some embodiments, the vehicle includes a first audio focus stack, a first audio routing table, and a first media session stack corresponding to the first audio zone, and a second audio focus stack, a second audio routing table, and a second media session stack corresponding to the second audio zone, the first audio focus stack including audio focus information of the second application, the first audio routing table including application information of the second application, and the first media session stack including the media session stack of the first application; after the vehicle detects the input operation of migrating the first interface from the first screen to the second screen, the audio focus information of the second application can be migrated from the first audio focus stack to the second audio focus stack, the application information of the second application can be migrated from the first audio routing table to the second audio routing table, and the media session of the second application can be migrated from the first media session stack to the second media session stack.

[0022] It can be seen that during the screen migration process, the migrated application does not need to adapt the multimedia display interface and audio stream according to the screen after the screen migration. Since the application information of the above-mentioned second application is migrated to the audio routing table associated with the second sound zone, the second application can find itself in the audio routing table associated with the second sound zone, and then transmit the audio of the second application to the audio channel of the first sound device according to the audio routing table corresponding to the second sound zone. This can achieve the seamless switching of the audio of the second application from the in-car speakers to the first sound device, maintaining the continuity of the audio playback. The above-mentioned seamless switching of the audio of the second application from the in-car speakers to the first sound device can mean that when the audio of the second application is switched to the first sound device, the first sound device can continue to play the audio from the position where the in-car speakers stopped playing the audio.

[0023] In combination with the first aspect, in some embodiments, the second interface of the first application is displayed on the second screen, and the second interface is the playback interface of the first audio; the vehicle again detects that the first application requests to play the first audio, and after playing the first audio through the first sound device, when the input operation of sharing the second interface from the second screen to the first screen is detected, the vehicle displays the second interface on the first screen and switches the first audio from the first sound device to the in-car speakers to continue playing.

[0024] In combination with the first aspect, in some embodiments, the vehicle also includes a third screen, the third screen is associated with the third sound zone of the second sound device, the second sound device is connected to the vehicle, the vehicle detects the input operation of sharing the second interface from the second screen to the third screen, and displays the second interface on the third screen.

[0025] In combination with the first aspect, in some embodiments, after the vehicle switches the first audio from the first sound-emitting device to the in-vehicle speaker to continue playing, when it detects that the fourth application on the second screen requests to play the fourth audio, the vehicle plays the fourth audio through the first sound-emitting device.

[0026] In combination with the first aspect, in some embodiments, the vehicle detects that the fifth application on the third screen requests to play the fifth audio, and plays the fifth audio through the second sound device.

[0027] In combination with the first aspect, in some embodiments, after the vehicle switches the first audio from the first sound-emitting device to the in-car speaker to continue playing, when it detects that the sixth application on the first screen requests to play the sixth audio, the vehicle plays the sixth audio through the in-car speaker and pauses playing the first audio.

[0028] In combination with the first aspect, in some embodiments, the vehicle includes a first audio focus stack and a first audio routing table corresponding to the first audio zone, and a second audio focus stack and a second audio routing table corresponding to the second audio zone, the second audio focus stack includes audio focus information of the first application, and the second audio routing table includes application information of the first application; after the vehicle detects the input operation of sharing the second interface from the second screen to the first screen, the audio focus information of the first application is migrated from the second audio focus stack to the first audio focus stack, and the application information of the first application is migrated from the second audio routing table to the first audio routing table.

[0029] It can be seen that during the screen sharing process, the shared application does not need to adapt the multimedia display interface and audio stream according to the screen receiving the screen sharing. Since the audio routing strategy of the first application mentioned above is migrated to the audio routing table associated with the first audio zone, the audio track of the first application can find itself in the audio routing table associated with the first audio zone, and then the audio of the first application is transmitted to the audio channel of the in-car speaker according to the audio routing table associated with the first audio zone. This can achieve seamless switching of the audio of the first application from the first sound device to the in-car speaker, maintaining the continuity of audio playback.

[0030] In combination with the first aspect, in some embodiments, after the vehicle is connected to the first sound-emitting device, when it is detected that the first sound-emitting device is disconnected, the vehicle changes the sound zone associated with the second screen from the second sound zone to the first sound zone; when the second audio is played by the in-vehicle speaker, it is detected that the first application on the second screen requests to play the first audio, the first audio is played through the in-vehicle speaker, and the second audio is paused or the volume of the second audio is lowered.

[0031] In combination with the first aspect, in some embodiments, the vehicle includes a first audio focus stack corresponding to the first sound zone and a second audio focus stack corresponding to the second sound zone. After the vehicle detects that the first sound device is disconnected, the audio focus information in the second audio focus stack is migrated to the first audio focus stack, and the second audio focus stack is deleted.

[0032] In combination with the first aspect, in some embodiments, the vehicle includes a first audio routing table corresponding to the first audio zone and a second audio routing table corresponding to the second audio zone. After the vehicle detects that the first sound device is disconnected, the application information in the second audio routing table is migrated to the first audio routing table and the second audio routing table is deleted.

[0033] In combination with the first aspect, in some embodiments, the vehicle includes a first media session stack corresponding to the first audio zone and a second media session stack corresponding to the second audio zone. After the vehicle detects that the first sound device is disconnected, the media session in the second media session stack is migrated to the first media session stack and the second media session stack is deleted.

[0034] In conjunction with the first aspect, in some embodiments, the vehicle further includes a fourth screen, and the fourth screen maintains the same audio zone associated with the second screen. Upon detecting a request from the first application to play the first audio, the vehicle plays the first audio through the first sound device. Then, upon detecting a request from a seventh application on the fourth screen to play a seventh audio, the vehicle plays the seventh audio through the first sound device, and pauses the first audio or reduces the volume of the seventh audio. The fourth screen and the second screen may correspond to the same driving zone.

[0035] In a second aspect, the present application provides a vehicle that may include a screen, in-vehicle speakers, a memory, and a processor. The screen may be used to display a user interface. The in-vehicle speakers may be used to play audio. The memory may be used to store a computer program. The processor may be used to invoke the computer program, causing the vehicle to execute any possible implementation method described in the first aspect.

[0036] In a third aspect, the present application provides a computer-readable storage medium comprising instructions, which, when executed on a vehicle, causes the vehicle to execute any possible implementation method as in the first aspect.

[0037] In a fourth aspect, the present application provides a computer program product, which may include computer instructions. When the computer instructions are run on a vehicle, the vehicle executes any possible implementation method as in the first aspect.

[0038] In a fifth aspect, the present application provides a chip, which is applied to a vehicle, and the chip includes one or more processors, which are used to call computer instructions to enable the vehicle to execute any possible implementation method as in the first aspect.

[0039] It is understood that the vehicle provided in the second aspect, the computer-readable storage medium provided in the third aspect, the computer program product provided in the fourth aspect, and the chip provided in the fifth aspect are all used to execute the methods provided in the embodiments of the present application. Therefore, the beneficial effects that can be achieved can be referenced to the beneficial effects of the corresponding methods and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0040] FIG1 is a schematic diagram of the relationship between a driving area and a screen provided in an embodiment of the present application;

[0041] FIG2 is a schematic structural diagram of a vehicle 100 provided in an embodiment of the present application;

[0042] FIG3 is a schematic diagram of a cockpit audio partition architecture provided by an embodiment of the present application;

[0043] FIG4 is a schematic diagram of the architecture of a cockpit system provided in an embodiment of the present application;

[0044] FIG5 is a schematic diagram of a cabin audio partition architecture when no external sound device is connected, provided by an embodiment of the present application;

[0045] FIG6 is a schematic diagram of a cockpit audio partition architecture when external earphones 1 and 2 are connected, provided by an embodiment of the present application;

[0046] FIG7 is a flow chart of a method for creating a sound zone according to an embodiment of the present application;

[0047] FIG8 is a schematic diagram of an external sound device for a cockpit system provided by an embodiment of the present application;

[0048] FIG9 is a flow chart of a method for creating an audio channel provided in an embodiment of the present application;

[0049] 10 and 11 are schematic diagrams showing a specific process of creating a sound zone in a cockpit system according to an embodiment of the present application;

[0050] FIG12 is a flow chart of a method for deleting an audio channel when a sound device is removed, provided in an embodiment of the present application;

[0051] 13 and 14 are schematic diagrams showing a specific process of deleting a sound zone in a cockpit system according to an embodiment of the present application;

[0052] 15A to 15D are schematic diagrams of audio playback scenarios where some sound-emitting devices are removed, provided in embodiments of the present application;

[0053] FIG16 is a schematic diagram of audio stream transmission in different audio zones provided by an embodiment of the present application;

[0054] FIG17 is a schematic diagram of applying for audio focus according to an embodiment of the present application;

[0055] FIG18 is a schematic diagram of adjusting the volume of a multimedia playback application provided in an embodiment of the present application;

[0056] FIG19 is a schematic diagram of a system application for adjusting volume according to an embodiment of the present application;

[0057] 20A to 20D are schematic diagrams of some volume adjustment scenarios provided by embodiments of the present application;

[0058] FIG21 is a schematic diagram of a media session management provided in an embodiment of the present application;

[0059] FIG22 is a schematic diagram of a screen migration method provided by an embodiment of the present application;

[0060] 23 and 24 are schematic diagrams of screen migration scenarios provided by embodiments of the present application;

[0061] FIG25 is a schematic diagram of a screen sharing method provided in an embodiment of the present application;

[0062] Figures 26 and 27 are schematic diagrams of screen sharing scenarios provided by embodiments of the present application;

[0063] Figures 28A to 28F are other screen sharing scene diagrams provided in embodiments of the present application. DETAILED DESCRIPTION

[0064] The technical solutions in the embodiments of the present application are described below in conjunction with the drawings in the embodiments of the present application. Among them, in the description of the embodiments of the present application, the terms used in the following embodiments are only for the purpose of describing specific embodiments, and are not intended to be used as limitations on the present application. As used in the specification and claims of the present application, the singular expressions "a", "said", "above", "the" and "this" are intended to also include expressions such as "one or more", unless there is a clear contrary indication in the context. It should also be understood that in the following embodiments of the present application, "at least one", "one or more" refer to one or more (including two). The term "and / or" is used to describe the association relationship of associated objects, indicating that three relationships can exist; for example, A and / or B can represent: the existence of A alone, the existence of A and B at the same time, and the existence of B alone, where A and B can be singular or plural. The character " / " generally indicates that the associated objects before and after are in an "or" relationship.

[0065] References to "one embodiment" or "some embodiments" etc. described in this specification mean that the specific features, structures or characteristics described in conjunction with the embodiment are included in one or more embodiments of the present application. Therefore, the statements "in one embodiment", "in some embodiments", "in some other embodiments", "in some other embodiments", etc. appearing in different places in this specification do not necessarily refer to the same embodiment, but mean "one or more but not all embodiments", unless otherwise specifically emphasized in another way. The terms "including", "comprising", "having" and their variations all mean "including but not limited to", unless otherwise specifically emphasized in another way. The term "connected" includes direct and indirect connections, unless otherwise stated. "First" and "second" are used for descriptive purposes only and are not to be understood as indicating or implying relative importance or implicitly indicating the number of technical features indicated.

[0066] In the embodiments of this application, words such as "exemplarily" or "for example" are used to indicate examples, illustrations, or explanations. Any embodiment or design described as "exemplarily" or "for example" in the embodiments of this application should not be interpreted as being preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplarily" or "for example" is intended to present the relevant concepts in a concrete manner.

[0067] The term "user interface (UI)" in the following embodiments of this application refers to the medium interface for interaction and information exchange between an application (APP) or an operating system (OS) and a user, which realizes the conversion between the internal form of information and the form acceptable to the user. The user interface is a source code written in a specific computer language such as Java and extensible markup language (XML). The interface source code is parsed and rendered on an electronic device and finally presented as content that the user can recognize. The commonly used form of user interface is graphical user interface (GUI), which refers to a user interface related to computer operation that is displayed in a graphical manner. It can be a visual interface element such as text, icons, buttons, menus, tabs, text boxes, dialog boxes, status bars, navigation bars, widgets, etc. displayed on the screen of an electronic device.

[0068] The cockpit system may include multiple screens and multiple sound devices. There may be multiple applications on these multiple screens that apply for audio focus in order to obtain permission to use the sound device for audio playback. The cockpit system needs to manage the application for audio focus, determine which applications can obtain audio focus, and route the audio of the application that obtains audio focus to the appropriate sound device. When a user operation to adjust the volume is received, the cockpit system needs to determine which sound device's volume to adjust. It can be seen that the audio zone management in the cockpit system involves audio routing, volume management, audio focus management and other contents.

[0069] The cockpit system can also include the vehicle's onboard operating system (OS). This OS manages and controls onboard software and hardware resources, supporting the development of higher-level software, data connectivity, and the operation of higher-level software. It also controls application execution and provides a variety of human-computer interaction interfaces.

[0070] The cockpit system can also be called cockpit, smart cockpit, etc.

[0071] In some embodiments, a cockpit system based on the Android Open Source Project (AOSP) includes an audio routing-related management module, a volume-related management module, and an audio focus-related management module. Among them, the audio routing-related management module can match the audio content (context) and the playback address (address) according to car_audio_configuration.xml, and then generate an audio routing strategy. The volume-related management module can be used to manage the volume in each audio zone, and classify different contexts into different volume groups (VolumeGroup) for management. The audio focus-related management module manages the audio focus according to the focus strategy of one audio corresponding to one audio focus. These management modules work independently, which is not conducive to the unified management of the audio zones by the cockpit system. The above-mentioned cockpit system based on AOSP lacks unified management of media sessions applied in multiple audio zones.

[0072] Furthermore, when audio is transferred from one audio zone to another within the cockpit system, the AOSP-based cockpit system requires the audio playback application to adapt (for example, adapting the audio to the different audio zones, adapting the audio playback interface to the screens corresponding to the different audio zones, etc.). Different audio and video applications have different adaptation methods, which not only increases the workload for audio and video application developers but also affects the user's audio listening experience.

[0073] This application provides a cockpit multi-zone management method, which can manage each audio zone independently. Among them, the cockpit system can uniformly manage the audio focus, volume, audio routing, and media sessions in a sound zone. The cockpit system can divide the vehicle's own sound devices (such as in-car speakers) into a sound zone, and divide the sound devices connected to the cockpit system (such as headphones) into one or more sound zones. The cockpit system can dynamically create and delete sound zones based on the access and removal of sound devices.

[0074] This application constructs a hierarchical cabin audio partitioning architecture, dividing the audio system portion of the cabin system into multiple levels to support flexible configuration of the screen and audio in the cabin. Specifically, the audio system portion of the cabin system can be divided into four levels: screen, driving zone, sound zone, and sound device. The screen in the cabin system can be divided into multiple driving zones. Each driving zone can be associated with a sound zone. An application on a screen can request audio focus in the sound zone associated with the driving zone to which the screen belongs. In other words, the audio of an application on a screen can be played by the sound device corresponding to the sound zone associated with the driving zone to which the screen belongs. The relationship between the screen and the driving zone can be determined based on a configuration file. The association between the driving zone and the sound zone can be determined based on the correspondence between the sound device corresponding to the sound zone and the screen. The correspondence between the sound device and the screen can be dynamically changeable. Therefore, the association between the driving zone and the sound zone is also dynamically changeable. Based on this hierarchical cabin audio partitioning architecture, different vehicle models can implement the multi-sound zone management method of this application through configuration.

[0075] In scenarios where audio streaming is required, the cockpit system can uniformly migrate the audio focus, audio routing, and media session of the audio playback application in one audio zone to another audio zone, so that the sound device playing the audio can be seamlessly switched from the sound device corresponding to one audio zone to the sound device corresponding to another audio zone. The sound device corresponding to the other audio zone can continue to play the above audio. In this way, the audio is transferred from one sound device to another without causing the audio to be interrupted or played from the beginning, which can bring a good audio listening experience to the user. In addition, the audio playback application is unaware of the above audio streaming scenario and does not need to adapt to the audio playback application.

[0076] To facilitate understanding, some concepts involved in this application are introduced below.

[0077] 1. Audio Focus

[0078] Audio focus can refer to the permission to use the sound device to play audio. When an APP obtains audio focus, this APP can use the sound device to play audio. When an APP loses audio focus, this APP will pause or stop playing audio, or lower the volume of the playing audio. It is understandable that when multiple APPs use the same sound device to play audio at the same time, the audio of these multiple APPs will be mixed together. After mixing, the user may not be able to hear the content being played clearly. In order to avoid all applications using a sound device to play audio at the same time, usually only one application can obtain audio focus in the same time period. When an application holds audio focus, other applications can still apply for audio focus or preempt audio focus.

[0079] Audio focus types include: long focus, short focus, ducking focus, and exclusive focus. Applications can apply for any of the above types of audio focus as needed.

[0080] Long focus (AUDIOFOCUS_GAIN) can indicate an audio focus that needs to be occupied for a long time. When the audio focus of an application is long focus, the application will stop playing audio after losing long focus. In some embodiments, after the application holding the long focus stops playing audio, other applications that were previously playing audio will not resume playing. For example, when music APP1 holds the audio focus and plays music, in response to the operation of opening music APP2 to play music, music APP2 will apply for long focus. Music APP2 can seize the audio focus of music APP1 and start playing music. When music APP2 pauses playing music, music APP1 will not actively resume playing. Among them, when music APP2 seizes the audio focus of music APP1, the cockpit system can delete the audio focus information of music APP1 in the audio focus stack. At this time, if music APP1 wants to play music, it needs to reapply for audio focus. In other words, when an application applies for long focus, the cockpit system can clear the audio focus stack. The application corresponding to the audio focus information at the top of the audio focus stack can be the application that currently holds the audio focus and uses the sound device to play audio.

[0081] Short focus (AUDIOFOCUS_TRANSIENT) can indicate audio focus that is occupied for a short period of time. Short focus can cause the application that loses audio focus to pause playback, and the application that loses audio focus can resume playback after the short focus is abandoned. For example, when music APP1 holds audio focus and plays music, the phone application receives an incoming call. The phone application can apply for short focus. The phone application can seize the audio focus of music APP1 and start playing the incoming call prompt tone. When the call ends, the phone application can actively give up the short focus, and music APP1 can regain audio focus and resume playing music. Among them, when the phone application seizes the audio focus of music APP1, the cockpit system can place the audio focus information of the phone application at the top of the stack in the audio focus stack, and place the audio focus information of music APP1 below the top of the stack (that is, the last digit of the audio focus information of the phone application). When the call ends, the cockpit system can delete the audio focus information of the phone application in the audio focus stack. In this way, the audio focus information of music APP1 in the audio focus stack is back to the top of the stack. Music APP1 can actively resume playback after the phone application's call ends.

[0082] Ducking focus (AUDIOFOCUS_TRANSIENT_MAY_DUCK) can indicate audio focus that is occupied for a short time. Unlike short focus, ducking focus allows the application that previously obtained audio focus to lower the volume and play simultaneously with the application that newly obtained ducking focus. For example, in a scenario where you are listening to music and navigating at the same time, when music APP1 holds the audio focus and plays music, the navigation application needs to play the navigation prompt sound. The navigation application can apply for ducking focus. The navigation application can seize the audio focus of music APP1 and start playing the navigation prompt sound. When the navigation application plays the navigation prompt sound, music APP1 can lower the volume while playing music to ensure that the user can hear the navigation prompt sound more clearly. When the navigation prompt sound is finished, the navigation application can actively give up the ducking focus, and music APP1 can restore the volume of the music. Among them, when the navigation application seizes the audio focus of music APP1, the cockpit system can place the audio focus information of the navigation application at the top of the stack in the audio focus stack, and place the audio focus information of music APP1 below the top of the stack. When the navigation prompt ends, the cockpit system can delete the navigation app's audio focus information from the audio focus stack. This way, the audio focus information for music app 1 is back at the top of the stack. Music app 1 can then proactively restore the volume of the music playback.

[0083] Exclusive focus (AUDIOFOCUS_TRANSIENT_EXCLUSIVE) can indicate audio focus that is occupied for a short time. Unlike short focus and dodging focus, exclusive focus has the highest priority. It allows applications that apply for exclusive focus to seize the audio focus of other applications, but does not allow other applications to seize exclusive focus when applying for audio focus.

[0084] The cockpit system can have one or more audio zones. Each zone has an audio focus. Different applications can hold audio focus in different zones. Therefore, each zone can have an audio focus stack. The cockpit system manages the audio focus stacks for each zone based on the type of focus requested by the application. Multiple applications corresponding to a single zone can compete for audio focus in the zone associated with that zone.

[0085] 2. Audio Routing

[0086] Each sound device in the cockpit system has its own corresponding audio channel, which can be used to transmit audio playback data.

[0087] Audio routing refers to the relationship between an app and the audio channel it uses when playing audio. The cockpit system uses this routing to determine which audio channel an app's audio should be transmitted through, and therefore which sound device should play the app's audio.

[0088] 3. Media Session

[0089] A media session can be a bridge between the cockpit system and multimedia playback applications. Multimedia playback applications can include apps for playing audio and / or video. When playing audio and / or video, multimedia playback applications can create a media session. The media session can inform the cockpit system that the multimedia playback application is playing multimedia content (such as audio and / or video), and can also inform the cockpit system what multimedia content is being played and how to control the multimedia content being played (such as pause / play / fast forward / fast rewind).

[0090] In some embodiments, the cockpit system can display controls for controlling multimedia content playback in the user interface of the audio center based on the media session. This makes it easier for users to control multimedia content outside of the multimedia playback application.

[0091] 4. Occupant Zone

[0092] The driving zone can be divided based on the screens in the cockpit system. The cockpit system can include one or more driving zones. A driving zone can correspond to one or more screens.

[0093] Please refer to FIG1 , which exemplarily shows a schematic diagram of the relationship between the driving area and the screen.

[0094] For example, a cockpit system may include driving zone 0, driving zone 1, driving zone 2, and driving zone 3. The screens corresponding to driving zone 0 may include the central control screen, instrument panel, and heads-up display (HUD). The screens corresponding to driving zone 1 may include the passenger screen. The passenger screen may refer to the screen located in the passenger seat area, conveniently viewing for the passenger seated user. The screens corresponding to driving zone 2 may include rear screen 1, rear screen 2, armrest screen, and rear curtain. Rear screen 1 and rear screen 2 may refer to screens located in the rear seat area, conveniently viewing for the rear seated user. The screens corresponding to driving zone 3 may include virtual screens. Virtual screens may be designed to use external speakers configured on the vehicle's exterior as an independent audio zone. Virtual screens may be non-physical or physically present. Driving zone 3 may be associated with the audio zone corresponding to the external speakers. This allows users to play audio using the external speakers by streaming the audio to the virtual screen.

[0095] Occupancy zone 0 can be called OccupantZone0. Occupancy zone 1 can be called OccupantZone1. Occupancy zone 2 can be called OccupantZone2. Occupancy zone 3 can be called OccupantZone3. The screen corresponding to an occupancy zone can be called the screen in that occupancy zone or the screen bound to that occupancy zone. The correspondence between occupancy zones and screens can also be called the binding relationship between occupancy zones and screens.

[0096] As can be seen, the screen bound to driving zone 0 primarily serves the driver. The screen bound to driving zone 1 primarily serves the user in the front passenger seat. The screen bound to driving zone 2 primarily serves users in the back seat. The screen bound to driving zone 3 can be used to serve users outside the vehicle. The above-mentioned driving zone division can be divided into multiple areas based on the location of the screens on the vehicle: driver area, front passenger area, back seat area, and exterior area.

[0097] This application does not limit the division of the driving and passenger areas in the cockpit system. The cockpit system is not limited to driving and passenger areas 0 to 3, and may include more or fewer driving and passenger areas. The binding relationship between the driving and passenger areas and screens is not limited to the binding relationship shown in Figure 1. The driving and passenger areas in the cockpit system can be bound to more or fewer screens.

[0098] Each screen in the cockpit system can be configured with one or more applications. Two different screens can be configured with different applications or the same application. Take the central control screen and the co-pilot screen as an example. Both the central control screen and the co-pilot screen can be configured with an application market APP for installing APPs. In response to the operation of installing one or more applications in the application market APP on the central control screen, the cockpit system can configure these one or more applications on the central control screen. In response to the operation of installing another one or more applications in the application market APP on the co-pilot screen, the cockpit system can configure these other one or more applications on the central and co-pilot screens. In other words, the cockpit system can configure the application on the screen where the user operation for installing this application is performed. The embodiment of the present application does not limit the source of the applications in each screen.

[0099] The applications in the screen corresponding to the driving area can be called the applications corresponding to the driving area. When a driving area is bound to multiple screens, the applications corresponding to the driving area can include the applications in these multiple screens.

[0100] In some embodiments, a configuration file for the driving zone may be stored in the cockpit system. This configuration file may include rules for binding screens to the driving zone. The cockpit system may create the driving zone based on this configuration file and determine the screens corresponding to the driving zone. This configuration file may be referred to as a first configuration file.

[0101] Different models of vehicles may have different screens in their cockpit systems. The above embodiment allows configuration of the driving and passenger areas of different models simply by modifying the configuration files for each model. Different models of vehicle cockpit systems can create driving and passenger areas based on their corresponding configuration files.

[0102] 5. Audio Zone

[0103] Audio zones can be divided based on the sound devices in the cockpit system. The cockpit system can include one or more audio zones. A audio zone can be associated with one or more sound devices.

[0104] For example, the cockpit system can divide all the in-vehicle speakers configured in the vehicle into an audio zone and create AudioZone 0. The sound-emitting device associated with AudioZone 0 is the in-vehicle speaker. Optionally, the cockpit system can also divide the in-vehicle speakers into multiple audio zones. This embodiment of the present application is not limited to this.

[0105] In some embodiments, when an exterior speaker is configured on the outside of the vehicle, the cockpit system may divide the exterior speaker into a sound zone and create a sound zone associated with the exterior speaker.

[0106] In some embodiments, the cockpit system can be connected to one or more external sound-emitting devices, such as headphones. Headphones can include wired headphones, wireless headphones (such as Bluetooth headphones, etc.). When an external sound-emitting device, such as headphone 1, is detected, the cockpit system can divide headphone 1 into another audio zone and create audio zone 1 (AudioZone1). The sound-emitting device associated with audio zone 1 can include headphone 1. When it is detected that headphone 1 is disconnected, the cockpit system can delete audio zone 1.

[0107] In some embodiments, the cockpit system can associate audio zone 0 with the driving zone 0 shown in Figure 1. In this way, the application corresponding to the driving zone 0 can compete for audio focus in audio zone 0 and play audio using the in-car speakers after obtaining the audio focus.

[0108] If there is only one audio zone in the cockpit system, namely audio zone 0, the cockpit system can associate all driving and passenger zones with audio zone 0. In this way, applications corresponding to all driving and passenger zones in the cockpit system compete for audio focus in audio zone 0 and play through the car speakers after obtaining audio focus.

[0109] When the aforementioned headphones 1 are connected to an external cockpit system, the cockpit system can determine which screen the headphones 1 are bound to. Specifically, in response to an operation on a screen connecting an external sound device to the cockpit system, the cockpit system can bind the sound device to that screen. The sound device is bound to the screen through which it is connected to the cockpit system. The cockpit system can then associate the sound zone corresponding to the sound device with the driving zone associated with the screen to which the sound device is bound.

[0110] For example, if earphones 1 are connected to the cockpit system via the passenger screen, the cockpit system can bind earphones 1 to the passenger screen. The cockpit system can then associate audio zone 1 corresponding to earphones 1 with the passenger screen's bound driving zone 1, as shown in Figure 1. This allows apps corresponding to passenger zone 1 to compete for audio focus in audio zone 1 and, after gaining audio focus, use earphones 1 to play audio.

[0111] Equipment hardware and software structure

[0112] The structure of the vehicle 100 involved in this application and the software architecture of the cockpit system in the vehicle 100 are introduced below.

[0113] FIG. 2 exemplarily shows a schematic structural diagram of a vehicle 100 .

[0114] As shown in FIG2 , a vehicle 100 may include a controller area network (CAN) bus 11, multiple electronic control units (ECUs), an engine 13, a telematics box (T-box) 14, a transmission 15, a driving recorder 16, an anti-lock brake system (ABS) 17, a sensor system 18, a camera system 19, a microphone 20, a speaker 21, and the like.

[0115] The CAN bus 11 is a serial communication network that supports distributed or real-time control and is used to connect the various components of the vehicle 100. Any component on the CAN bus 11 can monitor all data transmitted on the CAN bus 11. Frames transmitted by the CAN bus 11 can include data frames, remote frames, error frames, and overload frames, with different frames transmitting different types of data. In the embodiments of the present application, the CAN bus 11 can be used to transmit data involved in the multi-zone management method between various components. The specific implementation of this method can be found in the detailed description of the method embodiments below.

[0116] The various components of the vehicle 100 may be connected and communicated via other methods, not limited to the CAN bus 11. In other embodiments, the various components of the vehicle 100 may also communicate via other methods. For example, the various components may communicate via an in-vehicle Ethernet (Ethernet), a local interconnect network (LIN) bus, FlexRay, or a common in-vehicle media-oriented system (MOST) bus, etc., although this is not a limitation in the present embodiment. The following embodiments are described using the assumption that the various components communicate via the CAN bus 11.

[0117] The ECU is the processor or brain of vehicle 100, instructing components to perform actions based on instructions received from the CAN bus 11 or user input. The ECU may consist of a security chip, a microprocessor (MCU), random access memory (RAM), read-only memory (ROM), input / output (I / O) interfaces, an analog / digital converter (A / D converter), and large-scale integrated circuits for input, output, shaping, and driver functions.

[0118] There are many types of ECUs, and different types of ECUs can be used to achieve different functions.

[0119] The multiple ECUs in the vehicle 100 may include, for example, an engine ECU 121 , a telematics box (T-box) ECU 122 , a transmission ECU 123 , a driving recorder ECU 124 , an anti-lock brake system (ABS) ECU 125 , and the like.

[0120] The engine ECU 121 is used to manage the engine and coordinate its various functions, such as starting and shutting down the engine. The engine is a device that provides power to the vehicle 100. An engine is a machine that converts a certain form of energy into mechanical energy. The vehicle 100 can be used to convert the chemical energy of liquid or gas combustion, or electrical energy into mechanical energy and output power externally. The engine components can include two major mechanisms: the crankshaft and the valve mechanism, as well as five major systems: cooling, lubrication, ignition, energy supply, and starting system. The main components of the engine include the cylinder block, cylinder head, piston, piston pin, connecting rod, crankshaft, flywheel, etc.

[0121] The T-box ECU 122 is used to manage the T-box 14 .

[0122] T-box 14 is mainly responsible for communicating with the Internet, providing a remote communication interface for vehicle 100, and providing services including navigation, entertainment, driving data collection, driving trajectory recording, vehicle fault monitoring, vehicle remote query and control (such as unlocking and closing, air conditioning control, window control, engine torque limit, engine start and stop, seat adjustment, query of battery power, fuel level, door status, etc.), driving behavior analysis, wireless hotspot sharing, roadside assistance, abnormal reminders, etc.

[0123] T-box 14 can be used to communicate with a telematics service provider (TSP) and user (e.g., driver) side electronic devices to display and control the vehicle status on the electronic devices. When the user sends a control command through the vehicle management application on the electronic device, the TSP will issue a request instruction to the T-box 14. After obtaining the control command, the T-box 14 sends a control message through the CAN bus and controls the vehicle 100, and finally feeds back the operation results to the vehicle management application on the user side electronic device. In other words, the data read by the T-box 14 through the CAN bus 11, such as vehicle condition reports, driving reports, fuel consumption statistics, violation inquiries, location trajectories, driving behavior and other data, can be transmitted to the TSP background system via the network, and forwarded by the TSP background system to the user side electronic device for the user to view.

[0124] The T-box 14 may specifically include a communication module and a screen.

[0125] Among them, the communication module can be used to provide wireless communication functions, supporting the vehicle 100 to communicate with other devices through wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) networks), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), infrared technology (IR), ultra-wideband (UWB) and other wireless communication technologies. The communication module can also be used to provide mobile communication functions, supporting the vehicle 100 to communicate with other devices through communication technologies such as global system for mobile communications (GSM), universal mobile telecommunications system (UMTS), wideband code division multiple access (WCDMA), time-division code division multiple access (TD-SCDMA), long term evolution (LTE), 5G and the future 6G.

[0126] The communication module can establish connections and communicate with other devices such as servers and user-side electronic devices through cellular V2X (vehicle to everything) communication technology (C-V2X) based on cellular networks. C-V2X can include, for example, long-term evolution (LTE)-based V2X (LTE-V2X) and 5G-V2X.

[0127] The screen can be used to provide a visual interface. The vehicle 100 may include one or more screens, for example, an instrument screen arranged in front of the driver's seat, a screen arranged above the seat for displaying the surrounding situation, a HUD that projects information onto the windshield, and so on. The screens in the vehicle 100 may also include: a central control screen, a co-pilot screen, a rear screen, an armrest screen, a rear curtain, and so on. Among them, the rear seat area of ​​the vehicle 100 may be configured with one or more rear screens. For example, the area of ​​the left rear seat is configured with a screen. The area of ​​the right rear seat is configured with another screen. This application does not limit the number and position of the screens included in the vehicle 100.

[0128] T-box 14 may also be referred to as a vehicle system, a telematics processor, a vehicle gateway, etc., which is not limited in the embodiments of the present application.

[0129] The transmission ECU 123 is used to manage the transmission.

[0130] The transmission 15 is a mechanism used to change the engine's speed and torque. It can change the output-to-input ratio in a fixed or step-by-step manner. Transmission 15 components may include a transmission mechanism, an operating mechanism, and a power take-off mechanism. The transmission mechanism primarily changes the magnitude and direction of torque and speed; the operating mechanism primarily controls the transmission mechanism to achieve gear shifting, thereby changing the transmission ratio and achieving speed and torque variations.

[0131] The drive recorder ECU 124 is used to manage the drive recorder 16 .

[0132] The components of the driving recorder 16 may include a host computer, a vehicle speed sensor, and data analysis software. The driving recorder 16 is a device that records images and sounds of a vehicle while it is in motion, including relevant information such as driving time, speed, and location. In this embodiment of the present application, while the vehicle is in motion, the vehicle speed sensor collects wheel speed information and transmits it to the driving recorder 16 via the CAN bus.

[0133] The ABS ECU 125 is used to manage the ABS 17 .

[0134] ABS17 automatically controls the braking force during vehicle braking to prevent the wheels from locking and maintain a rolling and sliding state, thereby ensuring maximum adhesion between the wheels and the ground. During braking, if the electronic control unit determines that a wheel is approaching locking based on the wheel speed signal input by the wheel speed sensor, the ABS will enter the anti-lock brake pressure adjustment process.

[0135] The sensor system 18 may include: an acceleration sensor, a vehicle speed sensor, a vibration sensor, a gyroscope sensor, a radar sensor, a signal transmitter, a signal receiver, and the like. The acceleration sensor and the vehicle speed sensor are used to detect the speed of the vehicle 100. The vibration sensor may be installed under the seat, on the seat belt, on the backrest of the seat, on the operating panel, on the airbag, or in other locations to detect whether the vehicle 100 has been hit and the location of the user. The gyroscope sensor may be used to determine the motion posture of the vehicle 100. The radar sensor may include a laser radar, an ultrasonic radar, a millimeter wave radar, and the like. The radar sensor is used to transmit electromagnetic waves to illuminate a target and receive its echo, thereby obtaining information such as the distance from the target to the electromagnetic wave emission point, the rate of change of distance (radial velocity), the direction, and the altitude, thereby identifying other vehicles, pedestrians, or roadblocks near the vehicle 100. The signal transmitter and the signal receiver are used to send and receive signals, which can be used to detect the location of the user. The signal may be, for example, ultrasonic waves, millimeter waves, lasers, and the like.

[0136] The camera system 19 may include multiple cameras for capturing still images or videos. The cameras in the camera system 19 may be located in front of, behind, on the sides of, or inside the vehicle, to facilitate functions such as assisted driving, driving recording, panoramic surround view, and in-vehicle monitoring.

[0137] The sensor system 18 and the camera system 19 can be used to detect the surrounding environment, so that the vehicle 100 can make corresponding decisions to cope with environmental changes. For example, they can be used to complete the task of paying attention to the surrounding environment during the autonomous driving stage.

[0138] The microphone 20, also known as a "microphone" or "microphone", is used to convert sound signals into electrical signals. When making a call or outputting a voice command, the user can speak by putting their mouth close to the microphone 20 to input the sound signal into the microphone 20. The vehicle 100 can be provided with at least one microphone 20. In other embodiments, the vehicle 100 can be provided with two microphones 20, which can not only collect sound signals but also realize noise reduction. In other embodiments, the vehicle 100 can also be provided with three, four or more microphones 20 to form a microphone array to collect sound signals, reduce noise, identify the sound source, realize directional recording functions, etc.

[0139] In addition, the vehicle 100 may also include multiple interfaces, such as a USB interface, an RS-232 interface, an RS485 interface, etc., which can be connected to external electronic devices such as cameras, microphones, and headphones.

[0140] In this embodiment of the present application, microphone 20 can be used to detect voice commands input by the user. Sensor system 18, camera system 19, T-box 14, etc. can be used to recognize the user's voice commands. When the voice command is recognized, T-box ECU 122 can execute the voice command.

[0141] The speaker 21, which may also be referred to as a "speaker" or a "horn", may be used to convert electrical signals into sound signals. The speaker 21 may be used for audio playback. The vehicle 100 may be provided with at least one speaker 21. For example, the vehicle 100 may include a plurality of in-vehicle speakers. These multiple in-vehicle speakers may be distributed in different locations in the vehicle so that users sitting in various locations in the vehicle can have a good audio listening experience. In some embodiments, the vehicle 100 may also include an external speaker. In some embodiments, the vehicle 100 may also be connected to an external sound-emitting device (such as a Bluetooth headset, etc.) and play audio through the external sound-emitting device.

[0142] In some embodiments, the memory in the vehicle 100 may be used to store the binding relationship between the vehicle and the user.

[0143] It should be understood that the illustrated structures of the embodiments of this application do not constitute specific limitations on the vehicle system. Vehicle 100 may include more or fewer components than shown, or may combine or separate certain components, or have different component arrangements. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0144] For example, the vehicle 100 may also include a separate memory, a battery, lights, wipers, an instrument panel, a transmission control unit (TCU), an auxiliary control unit (ACU), a passive entry and start system (PEPS), an on-board unit (OBU), a body control module (BCM), a charging port, and the like.

[0145] In the present application, the memory of the vehicle 100 can be used to store a configuration file of the driving zone. The configuration file can be used to determine the binding relationship between the screen of the vehicle 100 and the driving zone.

[0146] FIG3 exemplarily shows a schematic diagram of a cockpit audio partition architecture provided by the present application.

[0147] As shown in Figure 3, the audio system in the cockpit system can be logically divided into four levels: cockpit screen, driving area, sound area, and sound equipment.

[0148] The cockpit screens may include screens in the vehicle 100. For example, screen 0, screen 1, screen 2, screen 3, and so on. Screen 0 may be the center console screen. Screen 2 may be the instrument panel screen. Screen 3 may be the passenger screen. Screen 4 may be the rear screen.

[0149] The driving and audio zones can refer to the description of the previous embodiment. For example, the driving zones may include driving zone 0, driving zone 1, driving zone 2, and so on. Driving zone 0 can be bound to the central control screen and instrument screen (i.e., screen 0 and screen 1). Driving zone 1 can be bound to the passenger screen (i.e., screen 2). Driving zone 2 can be bound to the rear screen (i.e., screen 3). Audio zones may include audio zone 0, audio zone 1, audio zone 2, and so on.

[0150] Driving zone 0 can be associated with audio zone 0. Driving zone 1 can be associated with audio zone 1. Driving zone 2 can be associated with audio zone 2. The embodiment of the present application does not limit the association relationship between the above-mentioned driving zones and audio zones.

[0151] The sound-emitting devices may include the vehicle 100's built-in sound-emitting devices and external sound-emitting devices. For example, there are sound-emitting devices 0, 1, 2, and so on. Sound-emitting device 0 may be a speaker inside the vehicle 100. Sound-emitting device 1 may be an external headphone 1. Sound-emitting device 2 may be an external headphone 2.

[0152] The above-mentioned sound zone 1 may be created when sound device 1 is connected. Therefore, sound device 1 can be associated with sound zone 1. The above-mentioned sound zone 2 may be created when sound device 2 is connected. Therefore, sound device 2 can be associated with sound zone 2.

[0153] In some embodiments, sound device 1 is connected via screen 2. The cockpit system can associate audio zone 1 associated with sound device 1 with driving zone 1 bound to screen 2. Sound device 2 is connected via screen 3. The cockpit system can associate audio zone 2 associated with sound device 2 with driving zone 2 bound to screen 3.

[0154] When an app on screen 0 needs to play audio, the cockpit system can complete the application's audio focus request through driving zone 0 and audio zone 0, and determine that the application's audio should be routed to the audio channel of sound device 0. In this way, the app on screen 0 can play audio through sound device 0. Similarly, when an app on screen 2 needs to play audio, the cockpit system can complete the application's audio focus request through driving zone 1 and audio zone 1, and determine that the application's audio should be routed to the audio channel of sound device 1. In this way, the app on screen 2 can play audio through sound device 1.

[0155] In the aforementioned cabin audio zoning architecture, the cabin screen and the passenger zone can be bound via a configuration file. The association between the passenger zone and the audio zone, and the association between the audio zone and the sound device, can be dynamically determined based on the connection or removal of the sound device.

[0156] The above-mentioned cockpit audio partition architecture can support the flexible configuration of the driving and passenger area to which the screen belongs and the routing of audio to the sound devices, support the dynamic creation and deletion of audio zones, and also support the seamless switching of audio between sound devices in screen migration and screen sharing scenarios without the need for multimedia playback applications to adapt.

[0157] FIG4 exemplarily shows a schematic diagram of the architecture of a cockpit system provided by the present application.

[0158] As shown in FIG4 , the cockpit system may include an application layer, a driving area management layer, an audio framework layer, a hardware abstraction layer (HAL), and a sound device.

[0159] 1. Application layer

[0160] The application layer may include one or more APPs. For example, multimedia playback applications, audio centers, cockpit voice assistants, Bluetooth, desktop services, and so on. Multimedia playback applications may be APPs used to play multimedia content (such as audio and / or video). Multimedia playback applications may include but are not limited to: music APPs, phone APPs, video APPs, audio book APPs, radio APPs, navigation APPs, and so on. Multimedia playback applications may belong to third-party applications. Audio centers, cockpit voice assistants, Bluetooth, and desktop services may belong to system applications. The difference between third-party applications and system applications lies in whether they can globally manage and control other applications. Third-party applications cannot globally manage and control other applications. System applications can globally manage and control other applications.

[0161] In some embodiments, the above-mentioned system applications are configured on multiple screens in the cockpit system. The system application on one screen can globally manage and control other applications on the same screen. The third-party applications on different screens can be different.

[0162] For example, multiple screens such as the central control screen, co-pilot screen, and rear screen can all include an audio center, cabin voice assistant, Bluetooth, and desktop services.

[0163] The desktop service can be used to display the desktop. The desktop can include application icons for the on-screen applications, controls for adjusting volume and brightness, and so on. It is understood that the central control screen, passenger screen, rear screen, and other screens can all display the desktop through the desktop service to facilitate user interaction with the screen.

[0164] Bluetooth can be used to connect Bluetooth devices, such as Bluetooth headsets. Bluetooth can provide a user interface for Bluetooth connection to facilitate users to select Bluetooth devices and complete the connection and removal of Bluetooth devices. It is understandable that if a screen receives a user operation to connect a Bluetooth headset, the Bluetooth headset can be bound to this screen after it is connected to the cockpit system. The central control screen, co-pilot screen, rear screen and other screens can all provide Bluetooth connection services via Bluetooth. In this way, the central control screen, co-pilot screen, rear screen and other screens can all be bound to Bluetooth headsets.

[0165] The cockpit voice assistant can be used to interact with the user through voice, recognizing and executing the user's voice commands. For example, the user can use the cockpit voice assistant to open a music app to play music, or open a navigation app for navigation, etc. In some embodiments, the cockpit voice assistant can display the text content of its voice interaction with the user on the screen.

[0166] The audio center can be used to display the multimedia playlist on the screen. The multimedia playlist may include information about the multimedia content currently being played on the screen, and / or information about multimedia content that has been played. In some embodiments, the multimedia playlist may also include controls for controlling the playback of multimedia content. In this way, the user can control the multimedia content on a screen through the audio center on the screen (such as pausing playback, switching playback content, etc.). The central control screen, co-pilot screen, rear screen and other screens can all display the multimedia playlists on their respective screens through the audio center.

[0167] In some embodiments, the audio center of a screen can obtain the media session of the application on this screen, and then determine the content in the multimedia playlist based on the media session. The audio center can also be called a media center or other name.

[0168] In some embodiments, the audio center of a screen may further obtain a media session in a media session stack associated with the driving zone where the screen is located, and then determine the content in the multimedia playlist based on the media session.

[0169] The cockpit system may also include more or fewer applications, which is not limited in the present embodiment.

[0170] 2. Driving area management

[0171] The driving area management layer may include: media session management API (MediaSessionManager API), media session service (MediaSessionService), audio management API (AudioManager API), audio service (AudioService), cockpit audio management API (CarAudioManager API), cockpit audio service (CarAudioService). Among them, the media session management API, media session service, audio management API, and audio service can be native modules in the existing cockpit system (such as the cockpit system based on AOSP). The cockpit audio management API and cockpit audio service can be modules added to the cockpit system by this application for unified management of audio focus, volume, audio routing, and media sessions. Among them, both the media session service and the audio service can communicate with the cockpit audio service.

[0172] In the cockpit system of the present application, the multimedia playback application can still manage the media session by calling the media session service through the media session management API according to the original calling logic, and manage one or more of the audio focus, volume, and audio routing by calling the audio service through the audio management API. When the media session service receives information that the multimedia playback application is performing media session management, the media session service can instruct the cockpit audio service to manage the media session of the multimedia playback application based on the information. For example, the above-mentioned media session management information may include but is not limited to: information on creating a media session, information on deleting a media session, information on the multimedia content being played, and so on. When the audio service receives information that the multimedia playback application is performing audio management, the audio service can instruct the cockpit audio service to manage the audio focus, and / or volume, and / or audio routing in the multimedia playback application based on the information. The above-mentioned audio management information may include but is not limited to: information on applying for audio focus, information on giving up audio focus, information on adjusting volume, information on adjusting audio routing, and so on.

[0173] System applications in each screen (such as audio center, cockpit voice assistant, Bluetooth, desktop services, etc.) can call cockpit audio services through the cockpit audio management API to achieve unified management of audio focus, volume, and audio routing.

[0174] The cockpit audio service can include the in-vehicle audio feature part, the APP and screen association module, the screen and driving area association module, the driving area audio management module, and the cockpit media session management module.

[0175] The in-vehicle audio feature part may include audio-related logic for screen sharing features and audio-related logic for screen migration features. The screen sharing feature may refer to sharing multimedia content played on one screen to one or more other screens. For example, the co-pilot screen is playing video A of a video APP. In response to the operation of sharing video A to the central control screen and the rear screen, the cockpit system may also play video A on the central control screen and the rear screen. In this way, the co-pilot screen, the central control screen and the rear screen all play video A. Among them, the audio-related logic for the screen sharing feature may be used to indicate the logic for audio to flow between sound-emitting devices in a screen sharing scenario. For example, the audio-related logic for the screen sharing feature may include but is not limited to: when the multimedia content played on one screen is shared to all screens bound to the driving area, the audio in the multimedia content is migrated to the in-car speakers and played by the in-car speakers. The above-mentioned audio-related logic for the screen sharing feature is only an exemplary description of this application and should not constitute a limitation on this application.

[0176] The screen migration feature may refer to migrating multimedia content played on one screen to another screen. For example, the central control screen is playing video A of a video APP. In response to the operation of migrating video A to the co-pilot screen, the cockpit system may turn off video A in the central control screen and play video A in the co-pilot screen. In this way, the playback window of video A is migrated from the central control screen to the co-pilot screen. Among them, the audio-related logic of the screen migration feature can be used to indicate the logic of audio flow between sound devices in the screen migration scenario. For example, the audio-related logic of the screen migration feature may include but is not limited to: when the multimedia content played on one screen is migrated to another screen, the audio in the multimedia content is migrated from the sound device corresponding to the audio associated with the driving and passenger area bound to this screen to the sound device corresponding to the audio associated with the driving and passenger area bound to this other screen. The above-mentioned audio-related logic of the screen migration feature is only an exemplary description of the present application and should not constitute a limitation to the present application.

[0177] The APP and screen association module includes a screen APP list. The screen APP list can record the information of the APP configured in each screen in the cockpit system. The APP configured in each screen in the cockpit system can be independent. Each screen can install APP independently. In response to the operation for installing an APP on a screen, the cockpit system can configure this APP in this screen after downloading and installing this APP. The application icon of this APP can be displayed on the desktop of this screen so that the user can use this APP. This APP can be called the APP installed on this screen. The desktop of other screens that do not have this APP installed may not contain the application icon of this APP. The APP and screen association module can manage the above-mentioned screen APP list according to the changes of the APP in the screen. The cockpit audio service can determine which APPs are contained in each screen based on the screen APP list.

[0178] The module for associating screens with the passenger area may include a passenger area configuration file. This configuration file may record the binding relationship between the screens and the passenger area. The cabin audio service can read this configuration file, create a passenger area based on it, and bind the screens to the passenger area.

[0179] The passenger zone audio management module manages audio for applications in the passenger zone. It retrieves the passenger zone configuration file from the aforementioned screen and passenger zone association module to determine the number of passenger zones in the cabin system and the association between these zones and screens. The passenger zone audio management module can also create passenger zones and bind screens to them.

[0180] In some embodiments, the passenger zone audio management module may include a passenger zone audio management module corresponding to each passenger zone. The passenger zone audio management module corresponding to a passenger zone may be used to manage the audio of the application corresponding to the passenger zone.

[0181] Exemplarily, the driving area audio management module may include a driving area 0 audio management module and a driving area 1 audio management module. The driving area 0 audio management module can be used to manage the audio of the application corresponding to the driving area 0. The driving area 1 audio management module can be used to manage the audio of the application corresponding to the driving area 1. For example, the driving area 0 may be the driving area bound to the central control screen, instrument screen, and HUD. The driving area 1 may be the driving area bound to the co-pilot screen. The driving area audio management module is not limited to the driving area audio management modules corresponding to the driving area 0 and the driving area 1. The driving area audio management module may also include driving area audio management modules corresponding to more or fewer driving areas.

[0182] The audio management module for riding zone 0 includes: a historically connected device list (historicalDeviceList), an application list (applicationList), active sound zone information (activeZone), and active device information (activeDevice). The historically connected device list in the audio management module for riding zone 0 may include information about sound devices previously bound to the screen in riding zone 0. The audio management module for riding zone 0 may update the historically connected device list based on changes in the sound devices bound to the screen in riding zone 0. The sound device information in the historically connected device list may include, but is not limited to, identification information of the sound device, volume configuration information of the sound device, and the like. The volume configuration information of the sound device may be used to indicate the volume level set for the sound device. The application list in the audio management module for riding zone 0 may include information about applications currently running in the foreground or background on the screen bound to riding zone 0. Applications in the application list in the audio management module for riding zone 0 may include applications installed by the screen in riding zone 0 and currently running on the screen in riding zone 0, as well as applications installed by screens in other riding zones and transferred to the screen in riding zone 0 for running. The applications in the application list in the audio management module for riding zone 0 may be applications corresponding to riding zone 0. The audio management module for riding zone 0 may update its application list based on changes in applications running on the screen in riding zone 0. In some embodiments, the audio management module for riding zone 0 may obtain application activity information from the activity manager service (AMS) to determine the application running on the screen in riding zone 0. An activity is an application component that provides an interactive window for users to perform certain operations, such as playing audio, taking photos, making calls, etc. The active sound zone information in the audio management module for riding zone 0 may be used to indicate the sound zone currently associated with riding zone 0. The audio management module for riding zone 0 may update its active sound zone information based on changes in the associated sound zones of riding zone 0. The active device information in riding zone 0 may be used to indicate the sound device currently bound to the screen in riding zone 0. Riding zone 0 may update its active sound zone information based on changes in the sound device bound to the screen in riding zone 0.

[0183] The Driving Zone 1 Audio Management Module also includes: a list of historically connected devices, a list of applications, active audio zone information, and active device information. For details, please refer to the above description of the Driving Zone 0 Audio Management Module. This will not be repeated here.

[0184] The cabin media session management module can be used to manage media sessions for applications corresponding to each passenger zone. The cabin media session management module can synchronize information about applications corresponding to each passenger zone from the aforementioned passenger zone audio management module to determine which media sessions are included in each passenger zone. In some embodiments, the cabin media session management module can include a media session management module corresponding to each passenger zone. The media session management module corresponding to a passenger zone can be used to manage media sessions in that passenger zone (i.e., the media sessions for the applications corresponding to that passenger zone).

[0185] For example, the cabin media session management module may include a zone 0 media session management module and a zone 1 media session management module. The zone 0 media session management module may be used to manage media sessions in zone 0. The zone 1 media session management module may be used to manage media sessions in zone 1. The cabin media session management module is not limited to media session management modules corresponding to zone 0 and zone 1, and may include media session management modules corresponding to more or fewer zones.

[0186] The Riding Zone 0 media session management module may include an active media session stack. The active media session stack in the Riding Zone 0 media session management module may be used to indicate the media session stack in which the media session for the application corresponding to Riding Zone 0 is currently located. The media session stack in which the media session for the application corresponding to Riding Zone 0 is located may change as the audio zone associated with Riding Zone 0 changes.

[0187] The media session management module for driving zone 1 may also include an active media session stack. For details, please refer to the above introduction to the media session management module for driving zone 0. This will not be repeated here.

[0188] For example, if the audio zone associated with driving zone 1 is the same as that associated with driving zone 0, the media session of the application corresponding to driving zone 1 may be in the same media session stack as the media session of the application corresponding to driving zone 0.

[0189] The media session stack containing the media session of an application corresponding to a particular riding zone may be referred to as the media session stack associated with that particular riding zone. In some embodiments, a media session stack associated with a particular riding zone may include not only the media session of the application corresponding to that particular riding zone but also media sessions of applications corresponding to other riding zones. For example, if riding zone 1 and riding zone 0 are associated with the same audio zone, media session stack 0 may include both the media session of the application corresponding to riding zone 0 and the media session of the application corresponding to riding zone 1.

[0190] In some embodiments, the driving area management layer may further include a driving area video management module. The driving area video management module may be used to manage the video playback content of the corresponding application in the driving area. Similar to the above-mentioned driving area audio management module, the driving area video management module may include video management modules corresponding to each driving area. For example, the driving area 0 video management module, the driving area 1 video management module, and so on. The driving area 0 video management module may be used to manage the video playback content corresponding to the driving area 0. The driving area 1 video management module may be used to manage the video playback content corresponding to the driving area 1. In the scenario of screen migration or screen sharing, the above-mentioned driving area video management module may be responsible for transferring the video playback interface of the application from one screen to other screens.

[0191] 3. Audio framework layer

[0192] The audio framework layer may include: media session management instantiation API (MediaSessionManagerEx API), media session service instantiation (MediaSessionServiceEx), audio zone management API, audio zone management module (AudioZoneService), audio policy management module (AudioPolicyManager), and audio channel management module (AudioFlinger).

[0193] The audio zone management API can be used by various modules and services in the driving zone audio management module layer to call the audio zone management module to manage the audio zone.

[0194] The audio zone management module can be used to manage audio zones, for example, creating new audio zones and their corresponding audio zone management modules, deleting audio zones and their corresponding audio zone management modules, and managing and controlling the audio focus, audio routing, and volume within the audio zones. In some embodiments, the audio zone management module may include a corresponding audio zone management module for each audio zone. The audio zone management module corresponding to a audio zone can be used to manage that audio zone. The audio zone management module may include at least one audio zone management module corresponding to the audio zone associated with the in-vehicle speakers.

[0195] For example, the audio zone management module may include a audio zone 0 management module and a audio zone 1 management module. The audio zone 0 management module may be used to manage the audio focus, audio routing, and volume in audio zone 0. The audio zone 1 management module may be used to manage the audio focus, audio routing, and volume in audio zone 1. For example, audio zone 0 may be associated with driving zone 0, and the associated sound device may be an in-vehicle speaker. Audio zone 1 may be associated with driving zone 1, and the associated sound device may be external headphones 1. The audio zone management module is not limited to corresponding audio zone 0 and audio zone 1, and may also include audio zone management modules corresponding to more or fewer audio zones.

[0196] The audio zone 0 management module may include: an audio routing module, a focus management module, and a volume management module. The audio routing module in the audio zone 0 management module can be used to manage the audio routing in audio zone 0. The audio routing module can determine the audio routing strategy for the audio of the application corresponding to the driving zone associated with audio zone 0. Among them, the audio of the application corresponding to the driving zone associated with audio zone 0 can be routed to the audio channel corresponding to audio zone 0. The focus management module in the audio zone 0 management module can be used to manage the audio focus of audio zone 0. The application corresponding to the driving zone associated with audio zone 0 can compete for the audio focus in audio zone 0. The audio zone 0 management module may include an audio focus stack and update the audio focus stack based on the information of the application corresponding to the driving zone associated with audio zone 0 requesting audio focus. The volume management module in the audio zone 0 management module can be used to manage the volume of audio zone 0. The audio zone 0 management module can adjust the volume of the sound device associated with audio zone 0 according to the instruction to adjust the volume.

[0197] The audio zone 1 management module may also include an audio routing module, a focus management module, and a volume management module. For details, please refer to the above introduction to the audio zone 0 management module. This will not be repeated here.

[0198] The Media Session Management Instantiation API allows modules and services within the cockpit audio management module layer to call the Media Session Service Instantiation API. For example, the cockpit Media Session Management module can use the Media Session Management Instantiation API to call the Media Session Service Instantiation API to create, delete, or update a media session stack.

[0199] A media session service instantiation may include one or more media session stacks. The number of media session stacks may be consistent with the number of audio zones.

[0200] Exemplarily, the riding zone 0 media session management module may call the media session service instantiation to create a media session stack 0. Media session stack 0 may include the media session of the application corresponding to riding zone 0. In the case that the audio zone associated with riding zone 1 is different from that of riding zone 0, the riding zone 1 media session management module may call the media session service instantiation to create a media session stack 1. Media session stack 1 may include the media session of the application corresponding to riding zone 1. In some embodiments, when the audio zone associated with riding zone 1 changes to the audio zone associated with riding zone 0, the riding zone 1 media session management module may call the media session service instantiation to migrate the media session in media session stack 1 to media session stack 0, and delete media session stack 0.

[0201] Not limited to media session stack 0 and media session stack 1, the media session service instantiation may also include more or fewer media session stacks.

[0202] The audio policy management module manages audio routing policies. It can create, delete, and update audio routing tables. Each audio zone can be associated with an audio routing table. An audio routing table associated with a zone can record the audio routing policies for the applications associated with that zone's driving and riding zones. An audio routing table can be called an AudioPolicyMix.

[0203] For example, the audio zone 0 management module can instruct the audio policy management module to create audio routing table 0. The audio zone 1 management module can instruct the audio policy management module to create audio routing table 1. Among them, audio routing table 0 may include information about the application corresponding to the driving zone associated with audio zone 0. All audios applied in audio routing table 0 can be routed to the audio channel corresponding to audio zone 0, that is, played by the sound device associated with audio zone 0. Similarly, audio routing table 1 may include information about the application corresponding to the driving zone associated with audio zone 1. All audios applied in audio routing table 1 can be routed to the audio channel corresponding to audio zone 1, that is, played by the sound device associated with audio zone 1.

[0204] When the driving zone associated with a sound zone changes, the sound zone management module corresponding to the sound zone may instruct the audio policy management module to update the audio routing table associated with the sound zone.

[0205] In some embodiments, the audio policy management module may further include a Bluetooth protocol module. The Bluetooth protocol module may be used to indicate the parameters and processes required for the Bluetooth-based audio channel to transmit the audio channel. For example, the Bluetooth protocol module may include the Bluetooth audio transmission model agreement (Advanced Audio Distribution Profile, A2DP). A2DP specifies the protocol stack software and usage methods for transmitting high-quality audio file data using Bluetooth asynchronous transmission channels. Based on A2DP, high-quality audio can be transmitted through Bluetooth sound, enabling the use of Bluetooth headphones to listen to audio in the cockpit system.

[0206] The audio channel management module can be used to manage the audio channels in the cockpit system. The audio channel management module may include audio channels for the in-car speakers. There can be multiple audio channels for the in-car speakers, for example, audio channel 0 (Mix0), audio channel 1 (Mix1), audio channel 2 (Mix2), and so on. Among them, there can be multiple in-car speakers in the cockpit, and different types of audio can be processed differently to produce different playback sound effects. For example, the audio types may include media audio, call audio, alarm audio, and so on. Different types of audio can be transmitted and played through different audio channels of the in-car speakers.

[0207] In some embodiments, when an external sound device is connected to the cockpit system, the audio channel management module can create an audio channel for this sound device. When the external sound device is removed, the audio channel management module can delete the audio channel for this sound device. For example, when a Bluetooth headset 1 is connected to the cockpit system, the audio channel management module can create Bluetooth audio channel 1 (Bluetooth Mix 1) for Bluetooth headset 1. When Bluetooth headset 1 is disconnected from the cockpit system, the audio channel management module can delete Bluetooth audio channel 1.

[0208] In some embodiments, the passenger zone audio management module can assign the audio channel of the vehicle's speakers to audio zone 0. In this way, the audio zone 0 management module can determine that the audio channel corresponding to audio zone 0 is the audio channel of the vehicle's speakers. If the aforementioned Bluetooth headset 1 is connected to the cockpit system via the screen bound to passenger zone 1, the passenger zone audio management module can assign Bluetooth audio channel 1 to audio zone 1. In this way, the audio zone 1 management module can determine that the audio channel corresponding to audio zone 1 is Bluetooth audio channel 1.

[0209] The audio channel management module is not limited to the audio channels of the in-car speakers and the Bluetooth audio channel 1, and may also include more or fewer audio channels.

[0210] 4. Hardware Abstraction Layer and Sound Devices

[0211] The hardware abstraction layer (HAL) can be an interface layer between the cockpit system core and the hardware circuitry, used to abstract the hardware. The HAL can include an in-vehicle speaker HAL and a Bluetooth HAL. The in-vehicle speaker HAL can be the interface between the cockpit system and the in-vehicle speakers. The cockpit system can use the in-vehicle speaker HAL to control audio playback from the in-vehicle speakers. The Bluetooth HAL can be the interface between the cockpit system and Bluetooth headsets. The cockpit system can use the Bluetooth HAL to control audio playback from Bluetooth headsets connected to the cockpit system.

[0212] The cockpit sound device may include an in-vehicle speaker or a Bluetooth headset connected to the cockpit system. This application does not limit the cockpit sound device. For example, the cockpit sound device may also include an external speaker configured on the outside of the vehicle 100, a wired headset connected to the cockpit system, and so on.

[0213] The cockpit system shown in FIG4 is merely an example of the present application. The cockpit system of vehicle 100 is not limited to the cockpit system shown in FIG4 . The cockpit system of vehicle 100 may also include more or fewer modules than those shown in FIG4 , or may combine or separate certain software modules, or arrange the software modules in different locations.

[0214] In some embodiments, the vehicle 100 may include multiple processor chips and multiple cockpit systems. Different audio zones may be in different processor chips and cockpit systems. For example, the central control screen and the co-pilot screen are controlled by one processor chip and a cockpit system. The rear screen is controlled by another processor chip and a cockpit system. The driving area where the central control screen and the co-pilot screen are located and the audio zones associated with the driving area can all be in the cockpit system that controls the central control screen. The driving area where the rear screen is located and the audio zones associated with the driving area can all be in the cockpit system that controls the rear screen. Among them, the cockpit audio services in different cockpit systems can communicate with each other. In scenarios involving audio streaming, such as screen migration and screen sharing, the cockpit audio services in different cockpit systems can communicate with each other to migrate audio focus information, audio routing, and media sessions, thereby achieving seamless switching of audio between sound devices connected to different cockpit systems.

[0215] In order to facilitate understanding of the multi-sound zone management solution of the present application, the subsequent embodiments of the present application are specifically described using an example in which a vehicle 100 is configured with a cockpit system.

[0216] Connect external sound devices to dynamically create sound zones

[0217] In some embodiments, when the cockpit system lacks an external sound device, the system can include audio zones associated with the vehicle's speakers. All driving and passenger zones in the cockpit system can be associated with audio zones associated with the vehicle's speakers. When an external sound device is connected to the cockpit system, the system can create a new audio zone and associate the driving and passenger zone, where the screen associated with the external sound device is located, with this newly created zone. This allows for dynamic adjustment of the audio zones corresponding to applications in the driving and passenger zones, allowing audio from different applications on different screens to be played back on different sound devices.

[0218] FIG5 exemplarily shows a schematic diagram of a cockpit audio partition architecture provided by the present application when no external sound device is connected.

[0219] As shown in Figure 5, the cockpit system includes driving area 0, driving area 1, and driving area 2. The screens in driving area 0 include the central control screen, the instrument screen, and the HUD. The screens in driving area 1 include the co-pilot screen, and the screens in driving area 2 include the rear screen. The applications corresponding to driving area 0 can be determined based on the applications running in the foreground or background on the central control screen, the instrument screen, and the HUD. For example, the applications corresponding to driving area 0 may include application 1, application 2, application 3, and so on. The applications corresponding to driving area 1 can be determined based on the applications running in the foreground or background on the co-pilot screen. For example, the applications corresponding to driving area 1 can include application 4, application 5, and so on. The applications corresponding to driving area 2 can be determined based on the applications running in the foreground or background on the rear screen. For example, the applications corresponding to driving area 2 may include application 6, and so on.

[0220] If the cockpit system lacks an external sound device, the central control screen, instrument panel, HUD, passenger panel, and rear screen can all be linked to the in-car speakers. Therefore, driving zones 0 through 2 can all be associated with the entire vehicle sound zone. The entire vehicle sound zone is the sound zone associated with the in-car speakers.

[0221] As can be seen from Figure 5, all applications corresponding to driving zone 0 to driving zone 2 are set in the whole vehicle sound zone and are played through the in-car speakers. Among them, the applications corresponding to driving zone 0 to driving zone 2 all compete for audio focus in the whole vehicle sound zone. Applications that compete for audio focus in the whole vehicle sound zone can use the in-car speakers to play audio. For example, when application 1 on the central control screen holds the audio focus, the in-car speakers can obtain the audio playback data of application 1 and play the audio of application 1 based on the audio playback data of application 1. When application 4 on the co-pilot screen seizes the audio focus, the in-car speakers can pause playing the audio of application 1, obtain the audio playback data of application 4, and play the audio of application 4. Furthermore, when application 6 on the rear screen seizes the audio focus of application 4, the in-car speakers can pause playing the audio of application 4, obtain the audio playback data of application 6, and play the audio of application 6.

[0222] In addition, the media sessions of the applications corresponding to driving areas 0 to 2 can all be placed in a media session stack. The audio centers of the screens in driving areas 0 to 2 can obtain the information of the media sessions in this media session stack. The audio centers of these screens can display multimedia playlists based on the information of the media sessions. In this way, any screen in driving areas 1 to 2 can obtain the information of the media sessions of the applications corresponding to all driving areas. The multimedia playlists displayed on the screens with audio centers in driving areas 1 to 2 can be the same.

[0223] In some embodiments, the multimedia playlist may include controls for controlling the playback of multimedia content. Since the multimedia playlist displayed in the audio center of all screens is the same, the user can view and control multimedia content playing on other screens (such as the passenger screen and rear screen) on the central control screen, view and control multimedia content playing on other screens (such as the central control screen and rear screen) on the passenger screen, and view and control multimedia content playing on other screens (such as the central control screen and passenger screen) on the rear screen.

[0224] As can be seen from the above examples, when the cockpit system lacks an external sound device, all screens in the cockpit share audio resources. Only one application on any screen can receive audio focus at any given time, thereby using the in-car speakers to play audio. Screens such as the passenger and rear screens can function as extensions of the central control screen.

[0225] FIG6 exemplarily shows a schematic diagram of a cockpit audio partition architecture provided by the present application when external earphones 1 and 2 are connected.

[0226] As shown in Figure 6 , the cockpit system includes driving zone 0, driving zone 1, and driving zone 2. The screens in driving zone 0 to driving zone 2 and the corresponding applications can refer to the description of the embodiment shown in Figure 5 above.

[0227] In some embodiments, headphones 1 are connected to the cockpit system via the passenger screen. The passenger screen receives a user input to connect headphones 1. After headphones 1 are connected to the cockpit system, the cockpit system can bind the passenger screen to headphones 1. Since the passenger screen is located in passenger area 1, the cockpit system can create headphone audio zone 1, associate it with passenger area 1, and assign the audio channels of headphones 1 to it. This means that the sound device associated with audio zone 1 is headphones 1.

[0228] Headphones 2 connect to the cockpit system via the rear screen. The rear screen receives a user input to connect headphones 2. After headphones 2 connect to the cockpit system, the system can bind the rear screen to headphones 2. Because the rear screen is located in passenger zone 2, the cockpit system can create headphone audio zone 2, associate it with passenger zone 2, and assign the audio channel of headphone 2 to it. This means that the sound device associated with audio zone 2 is headphones 2.

[0229] The sound zone associated with driving zone 0 is still the whole vehicle sound zone. The whole vehicle sound zone is the sound zone associated with the speakers in the car.

[0230] As shown in Figure 6, the applications corresponding to driving zone 0 (such as Application 1, Application 2, Application 3, etc.) are set in the vehicle's sound zone and can play audio through the in-vehicle speakers. Applications corresponding to driving zone 1 (such as Application 4, Application 5, etc.) are set in headphone sound zone 1, and the headphones play audio through headphone 1. Applications corresponding to driving zone 2 (such as Application 6, etc.) are set in headphone sound zone 2 and can play audio through headphone 2. Applications corresponding to driving zones 0-2 can compete for audio focus in the sound zone associated with each driving zone. After winning the audio focus in the sound zone, they use the sound device associated with the sound zone to play audio. For example, when Application 1 on the central control screen holds the audio focus in the vehicle's sound zone, the in-vehicle speakers can receive the audio playback data of Application 1 and play its audio. When Application 4 on the passenger screen holds the audio focus in headphone sound zone 1, headphone 1 can receive the audio playback data of Application 4 and play its audio. The audio played by the in-vehicle speakers and the audio played by headphone 1 can be independent and do not interfere with each other. This allows the driver to listen to the audio from Application 1 through the car's speakers and the user in the passenger seat to listen to the audio from Application 4 through headphones 1 without affecting each other. Furthermore, if Application 2 on the central control screen seizes the audio focus of Application 1 within the vehicle's sound zone, the car's speakers can pause the audio from Application 1, obtain the audio playback data from Application 2, and then play the audio from Application 2. These changes in the audio played by the car's speakers do not affect the audio played by headphones 1. Headphones 1 can continue to play the audio from Application 4.

[0231] The volume of the aforementioned in-car speakers, headphones 1, and headphones 2 can also be independently controlled. For example, in response to a volume adjustment on the central control screen, the cockpit system can adjust the volume of the in-car speakers. In response to a volume adjustment on the passenger screen, the cockpit system can adjust the volume of headphones 1. In response to a volume adjustment on the rear screen, the cockpit system can adjust the volume of headphones 2.

[0232] In addition, the media sessions of applications corresponding to driving zones 0 to 2 can be placed in different media session stacks respectively. The media session stack associated with driving zone 0 may only include media sessions for applications corresponding to driving zone 0. The media session stack associated with driving zone 1 may only include media sessions for applications corresponding to driving zone 1. The media session stack associated with driving zone 2 may only include media sessions for applications corresponding to driving zone 2. The audio centers of the screens in different driving zones may display different multimedia playlists based on the media session stacks associated with the corresponding driving zones. For example, the multimedia playlist displayed in the audio center of the central control screen includes multimedia content information for applications corresponding to driving zone 0, but does not include multimedia content information for applications corresponding to driving zones 1 and 2. The multimedia playlist displayed in the audio center of the passenger screen includes multimedia content information for applications corresponding to driving zone 1, but does not include multimedia content information for applications corresponding to driving zones 0 and 2. Users can view and control the multimedia content of applications corresponding to each driving zone on the screens in each driving zone separately.

[0233] As can be seen from the above embodiments, the audio zones in the cockpit system can dynamically change in response to changes in the external audio devices connected to the cockpit system. As the audio zones associated with the driving and passenger areas change, the corresponding applications can also be dynamically assigned to the corresponding audio zones after the change. Users can separate the audio playback of different applications by connecting external audio devices to the cockpit system. This allows different users to connect different external audio devices to screens in different driving and passenger areas, allowing them to listen to their desired audio using different audio devices without interfering with each other.

[0234] The following describes a method for creating a sound zone when an external sound device is connected, as provided in an embodiment of the application.

[0235] FIG7 exemplarily shows a flow chart of a method for creating a sound zone provided by the present application.

[0236] Here, the cockpit system is connected to the headset 1 through the co-pilot screen as an example. The headset 1 can be a Bluetooth headset.

[0237] As shown in FIG. 7 , the method may include steps S711 to S713 .

[0238] S711. The co-pilot screen receives a user operation for connecting earphone 1.

[0239] The user operation of connecting the headset 1 may include selecting the headset 1 on the co-pilot screen to establish a Bluetooth connection. The embodiment of the present application does not limit the user operation of connecting the headset 1.

[0240] S712: After earphone 1 is connected to the cockpit system, the cockpit system creates Bluetooth audio channel 1.

[0241] The headset 1 being connected to the cockpit system may indicate that the headset 1 and the cockpit system have completed Bluetooth pairing connection. The embodiment of the present application does not specifically limit the method of Bluetooth pairing connection.

[0242] The Bluetooth audio channel 1 may be used to transmit the audio stream to be played to the earphone 1 so that the earphone 1 plays the audio. The Bluetooth audio channel 1 may be an audio channel associated with the earphone 1.

[0243] S713. After the cockpit audio service in the cockpit system senses that the audio channel of earphone 1 is successfully created, earphone 1 is bound to the co-pilot screen, audio zone 1 is created, Bluetooth audio channel 1 is assigned to audio zone 1, and audio zone 1 is associated with driving zone 1.

[0244] For details about the cockpit audio service, refer to the description of the embodiment shown in Figure 4 . Since headphones 1 are connected to the cockpit system via the passenger screen, the cockpit audio service can bind headphones 1 to the passenger screen. The cockpit audio service can call the audio zone management module to create audio zone 1, assign Bluetooth audio channel 1 to audio zone 1, and associate audio zone 1 with driving zone 1, where the passenger screen is located. This allows applications associated with audio zone 1 to be routed to the corresponding audio channel.

[0245] In some embodiments, if the headset 1 has previously accessed the cockpit system through the passenger seat screen, the headset 1 can automatically establish a Bluetooth connection with the cockpit system when it is accessed again, without the user having to perform any user operation to connect the headset 1. After the headset 1 is accessed again, the cockpit system can still bind the headset 1 to the passenger seat screen. In other words, if the headset 1 first accesses the cockpit system through the passenger seat screen, subsequent active accesses by the headset 1 can be presumed to be accessed through the passenger seat screen.

[0246] FIG8 exemplarily shows a schematic diagram of an external sound device of a cockpit system.

[0247] Here, we use the example of connecting the cockpit system to earphone 1 through the passenger screen and earphone 2 through the rear screen. Both earphones 1 and 2 can be Bluetooth earphones.

[0248] As shown in Figure 8, when earphone 1 is connected to the cockpit system, the Bluetooth protocol module in the audio policy management module can search for a Bluetooth audio protocol that is compatible with earphone 1 and can transmit audio data to earphone 1. The Bluetooth protocol module can open output port 1 based on the found Bluetooth audio protocol. Output port 1 can be used to send data such as parameters and processes for establishing and transmitting audio streams to the audio channel management module. The audio policy management module can instruct the audio channel management module to create an audio channel. The audio channel management module can call the Bluetooth hardware abstraction module to open the port of Bluetooth audio channel 1 to complete the creation of Bluetooth audio channel 1. In this way, Bluetooth audio channel 1 can be connected to earphone 1 through the Bluetooth hardware abstraction module.

[0249] Similarly, when earphone 2 is connected to the cockpit system, the Bluetooth protocol module searches for a Bluetooth audio protocol compatible with earphone 2 and capable of transmitting audio data to earphone 2. Based on the found Bluetooth audio protocol, the Bluetooth protocol module opens output port 2 and, through output port 2, instructs the audio channel management module to create an audio channel. The audio channel management module calls the Bluetooth hardware abstraction module to open the port for Bluetooth audio channel 2, completing the creation of Bluetooth audio channel 2. This allows Bluetooth audio channel 2 to be connected to earphone 2 via the Bluetooth hardware abstraction module.

[0250] After earphone 1 is bound to the co-pilot screen and the Bluetooth audio channel 1 of earphone 1 is created, the driving zone 1 audio management module corresponding to the co-pilot screen can instruct the audio zone management module to create an audio zone 1 management module corresponding to audio zone 1, and assign Bluetooth audio channel 1 to audio zone 1. Then, the audio zone 1 management module can instruct the audio policy management module to create an audio routing table 1, and store the information of the application corresponding to the driving zone 1 and the information of the Bluetooth audio channel 1 corresponding to audio zone 1 in the audio routing table 1 according to the application corresponding to the driving zone 1. Since Bluetooth audio channel 1 is assigned to audio zone 1, audio routing table 1 can point to Bluetooth audio channel 1. This means that the audio of the application recorded in audio routing table 1 can be routed to Bluetooth application channel 1 and played by earphone 1.

[0251] Similarly, after earphone 2 is bound to the co-pilot screen and the Bluetooth audio channel 2 of earphone 2 is created, the driving zone 2 audio management module corresponding to the co-pilot screen can instruct the sound zone management module to create a sound zone 2 management module corresponding to sound zone 2, and assign Bluetooth audio channel 2 to sound zone 2. Then, the sound zone 2 management module can instruct the audio policy management module to create an audio routing table 2, and store the information of the application corresponding to the driving zone 2 and the information of the Bluetooth audio channel 2 corresponding to sound zone 2 in the audio routing table 2 according to the application corresponding to the driving zone 2. Since Bluetooth audio channel 2 is assigned to sound zone 2, audio routing table 2 can point to Bluetooth audio channel 2. This means that the audio of the application recorded in audio routing table 2 can be routed to Bluetooth application channel 2 and played by earphone 2.

[0252] The process of connecting other sound devices to the cockpit system can refer to the process of connecting external headphones 1 and headphones 2 mentioned above.

[0253] FIG9 exemplarily shows a flow chart of a method for creating an audio channel.

[0254] As shown in FIG. 9 , the method may include steps S911 to S920 .

[0255] S911, the Bluetooth APP in the co-pilot screen can notify the audio service headset 1 to connect.

[0256] In some embodiments, the headset 1 can complete the Bluetooth pairing connection through the Bluetooth app on the co-pilot screen and connect to the cockpit system. When the headset 1 is connected to the cockpit system, the Bluetooth app on the co-pilot screen can send a message to the audio service that the headset 1 has been connected.

[0257] The Bluetooth APP on the co-pilot screen can display a Bluetooth setting interface. The Bluetooth setting interface can display a prompt message that the headset 1 has been connected to the cockpit system.

[0258] S912: The audio service may send a message to the audio policy management module indicating that earphone 1 is connected.

[0259] S913: The audio policy management module may search for an available Bluetooth audio protocol and open the Bluetooth output port 1 through the Bluetooth audio protocol.

[0260] S914. The audio policy management module sends an instruction to create a Bluetooth audio channel to the audio channel management module.

[0261] S915. The audio channel management module sends an instruction to open the Bluetooth audio channel port to the Bluetooth hardware abstraction module.

[0262] S916. The Bluetooth hardware abstraction module opens the port of Bluetooth audio channel 1.

[0263] S917: The audio channel management module completes creation of Bluetooth audio channel 1.

[0264] For steps S912 to S917 , reference may be made to the description of the embodiment shown in FIG8 .

[0265] S918. The audio channel management module sends a message to the audio service indicating that the creation of Bluetooth audio channel 1 is complete.

[0266] S919. The audio service sends a message to the cockpit audio service indicating that creation of the audio channel for earphone 1 is complete.

[0267] The message sent by the audio service to the cockpit audio service may include: information about the audio channel of headset 1 and information about the screen used by headset 1 to access the cockpit system. This information about the audio channel of headset 1 can be used to indicate that the audio channel of headset 1 is a Bluetooth audio channel. This information about the screen used by headset 1 to access the cockpit system can be used to indicate that headset 1 accesses the cockpit system through the passenger seat screen.

[0268] S920. The cockpit audio service binds earphone 1 to the passenger screen, calls the audio zone management module to create audio zone 1, assigns Bluetooth audio channel 1 to audio zone 1, and associates audio zone 1 with driving zone 1.

[0269] Based on the message sent by the audio service in step S919, the cockpit audio service can bind earphone 1 to the co-pilot screen, call the audio zone management module to create audio zone 1, assign Bluetooth audio channel 1 to audio zone 1, and associate audio zone 1 with driving zone 1.

[0270] For the specific implementation of step S920, please refer to the subsequent introduction of Figures 10 and 11.

[0271] The method for creating an audio channel for a sound device when an external sound device is connected to the cockpit system as shown in FIG9 is merely an exemplary description of the present application and should not constitute a limitation to the present application.

[0272] 10 and 11 are schematic diagrams illustrating a specific process of creating a sound zone by the cockpit system.

[0273] As shown in Figure 10, the driving zone 0 audio management module is the driving zone audio management module corresponding to the central control screen, and can be used to manage the audio of the corresponding application of driving zone 0. Driving zone 0 is bound to the central control screen. The driving zone 1 audio management module is the driving zone audio management module corresponding to the passenger screen, and can be used to manage the audio of the corresponding application of driving zone 1. Driving zone 1 is bound to the passenger screen. The sound device bound to the central control screen can be an in-vehicle speaker. The audio zone associated with the in-vehicle speaker can be audio zone 0. Therefore, driving zone 0 is associated with audio zone 0.

[0274] Since the sound device bound to the central control screen is the in-car speaker, the active device information in the driving zone 0 audio management module may include the in-car speaker information. Since the driving zone 0 is associated with the sound zone 0, the active sound zone information in the driving zone 0 audio management module may include the sound zone 0 information, and the active sound zone information may point to the sound zone 0 management module to indicate that the driving zone 0 is associated with the sound zone 0. The sound zone 0 management module may point to the audio routing table 0, which may indicate that the audio routing policy of the corresponding application of the driving zone 0 is stored in the audio routing table 0. The audio routing table 0 points to the audio channel of the in-car speaker, which may indicate that the audio of the corresponding application of the driving zone 0 is played by the in-car speaker. In addition, the active media session stack in the driving zone 0 media session management module points to the media session stack 0, which may indicate that the media session of the corresponding application of the driving zone 0 can be stored in the media session stack 0.

[0275] As can be seen from the aforementioned Figure 5, when the co-pilot screen is not bound to an external sound device, the co-pilot screen is bound to the in-car speakers, and the driving zone 1 is also associated with the audio zone 0. At this time, the driving zone 1 is also associated with the audio zone 0. The active device information in the driving zone 1 audio management module may include the information of the in-car speakers. The active audio zone information in the driving zone 1 audio management module may include the information of the audio zone 0, and the active audio zone information may point to the audio zone 0 management module to indicate that the driving zone 1 is associated with the audio zone 0. The active media session stack in the driving zone 1 media session management module points to the media session stack 0, which may indicate that the media session of the corresponding application of the driving zone 1 can be stored in the media session stack 0.

[0276] Among them, the media sessions of the corresponding applications in driving area 0 and driving area 1 are both stored in media session stack 0, and the active media session stacks in the driving area 0 media session management module and the driving area 1 media session management module both point to media session stack 0. Therefore, the multimedia playlists displayed in the audio center of the central control screen and the co-pilot screen can be the same, both containing the multimedia content of the corresponding applications in driving area 0 and driving area 1.

[0277] When earphone 1 is connected to the cockpit system through the co-pilot screen, the cockpit system can create audio zone 1 according to the method shown in Figure 11, and adjust the audio zone associated with driving zone 1 to associate driving zone 1 with audio zone 1. As shown in Figure 11:

[0278] S1111: When earphone 1 is connected to the cockpit system and bound to the passenger screen, the driving zone 1 audio management module calls the audio zone management module to create audio zone 1 and generates an audio zone 1 management module.

[0279] After earphone 1 is connected to the cockpit system, the audio channel management module can create Bluetooth audio channel 1 for earphone 1. Since the sound device bound to the passenger screen is switched from the in-car speaker to earphone 1, the active device information in the driving zone 1 audio management module can be updated to the information of earphone 1. For example, the above-mentioned earphone 1 information may include the identifier of earphone 1 and the identifier of Bluetooth audio channel 1. Based on the active device information, the driving zone 1 audio management module can assign Bluetooth audio channel 1 to audio zone 1. In some embodiments, the method of assigning Bluetooth audio channel 1 to audio zone 1 may include: the driving zone 1 audio management module sends the identifier of Bluetooth audio channel 1 to the audio zone 1 management module.

[0280] S1112. Create an audio routing table 1 associated with audio zone 1, configure information of Bluetooth audio channel 1 in audio routing table 1, and configure application information of applications corresponding to driving zone 1.

[0281] The driving zone 1 audio management module can send the information of the applications (i.e., the application list) corresponding to the driving zone 1 to the audio zone 1 management module. The audio routing module of the audio zone 1 management module can call the audio policy management module to create an audio routing table 1 associated with the audio zone 1. The audio routing module of the audio zone 1 management module can configure the information of the Bluetooth audio channel 1 (such as the identifier of the Bluetooth audio channel 1) from the driving zone 1 audio management module and the application information of the applications corresponding to the driving zone 1 in the audio routing table 1. This can mean that the audio of the applications included in the audio routing table 1 are all routed to the Bluetooth audio channel 1 and played through the earphone 1.

[0282] S1113 : Filter out the audio focus information requested by the application corresponding to the driving zone 1 from the audio focus stack associated with the audio zone 0 , and migrate the filtered audio focus information to the audio focus stack associated with the audio zone 1 .

[0283] Before audio zone 1 is created, the audio zone associated with driving zone 1 is audio zone 0. The audio focus information requested by the application corresponding to driving zone 1 is stored in the audio focus stack associated with audio zone 0 and is managed by the focus management module in the audio zone 0 management module. When the audio zone associated with driving zone 1 needs to be switched from audio zone 0 to audio zone 1, the focus management module in the audio zone 0 management module can filter out the audio focus information of the application corresponding to driving zone 1 from the audio focus stack associated with audio zone 0, and send the filtered focus information to the focus management module in the audio zone 1 management module. The focus management module in the audio zone 1 management module can store the audio focus information requested by the application corresponding to driving zone 1 in the audio focus stack associated with audio zone 1. Among them, the focus management module in the audio zone 0 management module can delete the audio focus information requested by the application corresponding to driving zone 1 from the audio focus stack associated with audio zone 0.

[0284] In some embodiments, in the scenario described above where the audio focus information requested by an application corresponding to driving zone 1 is migrated from the audio focus stack associated with audio zone 0 to the audio focus stack associated with audio zone 1, if the audio focus information at the top of the audio focus stack associated with audio zone 0 is requested by an application corresponding to driving zone 1, the audio focus information will retain its audio focus status after the migration. In other words, an application corresponding to driving zone 1 holds audio focus in audio zone 0 and is at the top of the audio focus stack associated with audio zone 0. After the audio focus information is migrated, the application corresponding to driving zone 1 still holds audio focus, and its audio focus changes from the audio focus in audio zone 0 to the audio focus in audio zone 1. This application is at the top of the audio focus stack associated with audio zone 1. For example, when both driving zone 0 and driving zone 1 are associated with audio zone 0, a music app on the passenger screen requests audio focus in audio zone 0 and plays music through the in-car speakers associated with audio zone 0. While the car's speakers are playing the music app, if earphone 1 is connected to the cockpit system through the passenger screen, the music from the music app can be switched to earphone 1. The car's speakers can stop playing the music from the music app. Earphone 1 can resume playing the music from the music app from the point where the car's speakers stopped playing. The seamless switching of the above audio between sound-emitting devices can be achieved with the dynamic changes (such as creation or deletion) of the sound zones in the cockpit system, without the need for multimedia playback applications to perceive and adapt.

[0285] S1114 . The volume management module in the audio zone 1 management module sets the volume data of earphone 1 .

[0286] In some embodiments, earphone 1 is a sound-emitting device that has been connected to the cockpit system through the co-pilot screen. The information of earphone 1 may be included in the list of historically connected devices in the audio management module of the driving area 1. The information of earphone 1 in the list of historically connected devices may include, but is not limited to: the identification of earphone 1, the volume of earphone 1 when it was last connected to the cockpit system, and so on. The audio management module of the driving area 1 may send the volume of the above-mentioned earphone 1 when it was last connected to the cockpit system to the audio zone 1 management module. The volume management module in the audio zone 1 management module may set the volume data of earphone 1 according to the volume of earphone 1 when it was last connected to the cockpit system. In this way, the volume of the audio played when earphone 1 is connected again can be kept consistent with the volume of the audio played when it was last connected to the cockpit system, reducing the user's operation of readjusting the volume to the user's personal volume, thereby improving the user's audio listening experience.

[0287] In some embodiments, the volume management module in the audio zone 1 management module can also set the volume data of the earphone 1 to the default volume data. The embodiment of the present application does not limit the method of setting the volume data of the earphone 1.

[0288] S1115 : Update the active audio zone information in the audio management module of driving zone 1 to the audio zone 1 associated with driving zone 1.

[0289] The active audio zone information in the audio management module of driving zone 1 can be changed from pointing to the audio zone 0 management module to pointing to the audio zone 1 management module as shown in Figure 10. This can indicate that the audio zone associated with driving zone 1 is changed to audio zone 1.

[0290] S1116: Adjust the audio playback route of the application corresponding to driving zone 1, and adjust the sound device for playing the audio of the application corresponding to driving zone 1 from the in-vehicle speaker to earphone 1.

[0291] In some embodiments, when the audio zone associated with driving zone 1 is switched from audio zone 0 to audio zone 1, the audio zone 0 management module can instruct the audio policy management module to delete the information of the application corresponding to driving zone 1 in audio routing table 0. As shown in Figure 10, audio routing table 0 can still point to the audio channel of the in-car speaker. The audio routing table 1 created with the creation of audio zone 1 can point to Bluetooth audio channel 1. This means that the audio of the application recorded in audio routing table 1 (i.e., the application corresponding to driving zone 1) can be routed to Bluetooth application channel 1 and played by earphone 1.

[0292] S1117 : Create media session stack 1 , filter out media sessions of applications corresponding to driving zone 1 from media session stack 0 , and migrate the filtered media sessions to media session stack 1 .

[0293] In some embodiments, the Ride Zone 1 audio management module can synchronize audio zone changes associated with Ride Zone 1 with the Ride Zone 1 media session management module. Upon determining that the audio zone associated with Ride Zone 1 has changed from audio zone 0 to audio zone 1, the Ride Zone 1 media session management module can call a media session service instantiation to create media session stack 1 and migrate the media session of the application corresponding to Ride Zone 1 in media session stack 0 to media session stack 1. The media session service instantiation can also delete the media session of the application corresponding to Ride Zone 1 from media session stack 0.

[0294] S1118 : Adjust the active media session stack in the media session management module of driving area 1 from pointing to media session stack 0 to pointing to media session stack 1 .

[0295] As shown in FIG10 , the active media session stack in the media session management module of driving zone 1 points to media session stack 1 , which may indicate that the media session of the application corresponding to driving zone 1 may be stored in media session stack 1 .

[0296] S1119 . The driving zone 0 media session management module and the driving zone 1 media session management module report the changes of the media session stack to one or more applications in the audio center, Bluetooth, and desktop service.

[0297] The driving area 0 media session management module can report changes in the media session stack 0 to system applications such as the audio center, Bluetooth, and desktop services on the screen bound to the driving area 0 (such as the central control screen).

[0298] The media session stack of driving zone 1 can report changes in the media session stack associated with driving zone 1 to system applications such as the audio center, Bluetooth, and desktop services on the screen bound to driving zone 1 (such as the co-pilot screen).

[0299] S1120: The audio management module of driving zone 1 reports to one or more applications in the audio center, Bluetooth, and desktop service that the audio zone switching associated with driving zone 1 is completed.

[0300] The audio management module of driving zone 1 can report the completion of audio zone switching associated with driving zone 1 to system applications such as the audio center, Bluetooth, and desktop services on the screen bound to the driving zone.

[0301] In some embodiments, system applications such as the audio center, Bluetooth, and desktop services can provide corresponding feedback to the user based on changes in the above-mentioned media session stack and changes in the audio zones associated with the driving area, so that the user can better use each audio zone to listen to audio.

[0302] For example, when the audio center of the central control screen receives the message indicating a change in media session stack 0, it can update the multimedia playlist based on the changed media session stack 0. Because the changed media session stack 0 does not contain the media session for the application corresponding to driving zone 1, the multimedia playlist displayed by the audio center of the central control screen does not include the multimedia content for the application corresponding to driving zone 1.

[0303] When the passenger screen's audio center receives the message that the media session stack associated with driving zone 1 has changed from media session stack 0 to media session stack 1, the passenger screen's audio center updates the multimedia playlist based on media session stack 1. Because media session stack 1 doesn't contain the media session for the app corresponding to driving zone 0, the multimedia playlist displayed in the passenger screen's audio center doesn't include multimedia content from the app corresponding to driving zone 0.

[0304] In some embodiments, a sound zone may be associated with multiple sound devices. Multiple sound devices associated with a sound zone may share the same audio channel and play the same audio. For example, the central control screen and the passenger screen are in the same driving area. The central control screen may be bound to an in-car speaker. The passenger screen may be bound to earphone 1. The in-car speaker and earphone 1 are then associated with the same sound zone. The audio used in the central control screen may be played simultaneously in the in-car speaker and earphone 1. The audio used in the passenger screen may also be played simultaneously in the in-car speaker and earphone 1.

[0305] The order of the steps in the method shown in Figure 11 does not limit the order in which they must be performed. For example, steps S1112, S1113, S1114, and S1117 can be performed simultaneously. That is, when the audio zone associated with driving zone 1 changes from zone 0 to zone 1, the cockpit system can simultaneously shift audio focus, audio routing, volume, and media session. For another example, step S1120 can be performed before step S1119, or steps S1120 and S1119 can be performed simultaneously.

[0306] In some embodiments, the vehicle 100 includes a first screen and a second screen. The first screen and the second screen may correspond to different driving zones. For example, the first screen may be a central control screen. The second screen may be a passenger screen. The first screen may correspond to driving zone 0. The second screen may correspond to driving zone 1. In the case where the cockpit system does not have an external sound device connected to the second screen, both the first screen and the second screen may be associated with the first sound zone corresponding to the in-car speaker. The first sound zone may be sound zone 0 in this application. The fact that both the first screen and the second screen are associated with the first sound zone may mean that the driving zone 0 corresponding to the first screen is associated with the first sound zone, and the driving zone 1 corresponding to the second screen is also associated with the first sound zone.

[0307] In the case where both the first screen and the second screen are associated with the first audio zone, if the cockpit system detects that the first application corresponding to the second screen requests to play the first audio, the cockpit system can play the first audio through the in-car speakers. Then, when it is detected that the second application in the first screen requests to play the second audio, the cockpit system can play the second audio through the in-car speakers and pause the first audio or reduce the playback volume of the first audio. The above-mentioned first application and second application can both be multimedia playback applications. It can be seen that the application in the second screen and the application in the first screen both apply for audio focus in the first audio zone. When the first application in the second screen holds the audio focus in the first audio zone, the second application in the first screen can seize the audio focus of the first application.

[0308] When an input operation is detected on the second screen to connect to the first sound device, the cockpit system can connect to the first sound device and create a second sound zone corresponding to the first sound device. For example, the first sound device can be earphone 1. The second sound zone can be the sound zone 1 of the present application. The cockpit system can change the sound zone associated with the second screen from the above-mentioned first sound zone to the second sound zone. When the above-mentioned in-car speakers play the second audio and lower the playback volume of the first audio to play the first audio at a lower volume, the in-car speakers can stop playing the first audio after the sound zone associated with the second screen changes. When the cockpit system detects again that the first application requests to play the first audio, the cockpit system can play the first audio through the first sound device.

[0309] The above-mentioned first sound zone may correspond to a first audio focus stack. The first audio focus stack may include the audio focus information of the application running in the foreground or background on the screen associated with the first sound zone. That is, the first audio focus stack may include the audio focus information of the application corresponding to the driving zone (such as driving zone 0, driving zone) associated with the first sound zone. When a second sound zone is created, the cockpit system can create a second audio focus stack corresponding to the second sound zone, and migrate the audio focus information of the application running in the foreground or background on the second screen from the first audio focus stack to the second audio focus stack. In addition to the audio focus information of the application running in the foreground or background on the second screen, the cockpit system can also migrate the audio focus information of the application running in the foreground or background on other screens in the same driving zone as the second screen from the first audio focus stack to the second audio focus stack. For example, the second screen corresponds to driving zone 1. When a second sound zone is created, the cockpit system can migrate the audio focus information of the application corresponding to driving zone 1 from the first audio focus stack to the second audio focus stack.

[0310] The first audio zone may correspond to a first audio routing table. The first audio routing table contains application information for applications running in the foreground or background on the screen associated with the first audio zone. The first audio routing table is configured with a first audio channel for the in-vehicle speakers, indicating that audio from applications corresponding to the application information in the first audio routing table is routed to the first audio channel. For example, the first audio routing table may be Audio Routing Table 0 in this application. When a second audio zone is created, the cockpit system may create a second audio routing table corresponding to the second audio zone and migrate application information for applications running in the foreground or background on the second screen from the first audio routing table to the second audio routing table. In addition to application information for applications running in the foreground or background on the second screen, the cockpit system may also migrate application information for applications running in the foreground or background on other screens in the same driving zone as the second screen from the first audio routing table to the second audio routing table. For example, the second screen corresponds to Driving Zone 1. When a second audio zone is created, the cockpit system may migrate application information for applications corresponding to Driving Zone 1 from the first audio routing table to the second audio routing table. The second audio routing table may be Audio Routing Table 1 in this application. The second audio routing table may be configured with a second audio channel. The second audio channel may be Bluetooth audio channel 1. That is, the second audio routing table may point to Bluetooth audio channel 1.

[0311] The above-mentioned first audio zone may correspond to a first media session stack. The first media session stack may be the media session stack 0 of the present application. When creating a second audio zone, the cockpit system may create a second media session stack corresponding to the second audio zone. The second media session stack may be the media session stack 1 of the present application. The cockpit system may migrate the media session of the application corresponding to the driving area (such as the driving area) associated with the second audio zone from the first media session stack to the second media session stack. For details, please refer to the introduction of migrating the media session from the media session stack 0 to the media session stack 1 as described in Figure 10 above.

[0312] Move the sound device out and delete the sound zone dynamically

[0313] In some embodiments, when an external audio device is disconnected from the cockpit system, the cockpit system can delete the audio zone associated with the audio device and re-associate the driver's zone with the audio zone associated with the in-vehicle speakers. This allows the cockpit system to dynamically adjust the audio zone associated with the driver's zone when the external audio device is removed, enabling seamless audio switching between audio devices.

[0314] FIG12 exemplarily shows a flowchart of a method provided in the present application for deleting an audio channel when a sound-emitting device is removed.

[0315] As shown in FIG. 12 , the method may include steps S1211 to S1222 .

[0316] S1211. The Bluetooth APP on the passenger screen can notify the audio service that earphone 1 is disconnected.

[0317] In some embodiments, the Bluetooth APP in the co-pilot screen can display a Bluetooth setting interface. The Bluetooth setting interface can display a prompt message that the headset 1 has been disconnected from the cockpit system.

[0318] S1212: The audio service may indicate to the cockpit audio service that earphone 1 is disconnected.

[0319] S1213. The cockpit audio service searches for the audio zone associated with earphone 1 and pauses the audio currently playing in the audio zone associated with earphone 1.

[0320] In some embodiments, upon receiving the aforementioned message indicating that earphone 1 is disconnected, the cockpit audio service's driver zone 1 management module can search for the audio zone associated with earphone 1. In one possible implementation, the driver zone 1 audio management module can determine, based on the active device information, that earphone 1 is bound to the passenger screen in driver zone 1, and further determine, based on the active audio zone information, that the audio zone associated with earphone 1 is audio zone 1. The driver zone 1 audio management module can instruct the driver zone 1 media session management module to control the media session of the application to which the audio currently playing in audio zone 1 belongs, causing earphone 1 to pause audio playback.

[0321] Step S1213 is optional. It is understandable that if the headset 1 was not playing audio before disconnection, the cockpit audio service may not need to perform step S1213.

[0322] S1214: The audio service may send a message to the audio policy management module to instruct the deletion of the audio channel of earphone 1.

[0323] S1215: The audio policy management module may close the Bluetooth output port 1.

[0324] 8 , it can be seen that the Bluetooth protocol module in the audio policy management module can close the output port 1 .

[0325] S1216: The audio policy management module may send a message to the audio channel management module instructing to delete the Bluetooth audio channel 1.

[0326] S1217: The audio channel management module may send an instruction to the Bluetooth hardware abstraction module to close the port of Bluetooth channel 1.

[0327] S1218. The Bluetooth hardware abstraction module closes the port of Bluetooth audio channel 1.

[0328] S1219: The audio channel management module completes deletion of Bluetooth audio channel 1.

[0329] S1220: The audio channel management module may send a message to the audio service indicating that deletion of Bluetooth audio channel 1 is complete.

[0330] S1221: The audio service may indicate to the cockpit audio service that deletion of the audio channel of earphone 1 is complete.

[0331] S1222. The cockpit audio service may call the audio zone management module to delete audio zone 1, bind the passenger screen to the in-car speakers, and associate the driving zone 1 with audio zone 0 of the in-car speakers.

[0332] For the specific implementation of step S1222, please refer to the subsequent introduction of Figures 13 and 14.

[0333] The above method of deleting the audio channel of the sound device when the sound device connected to the cockpit system is removed is only an exemplary description of the present application and should not constitute a limitation to the present application.

[0334] 13 and 14 are schematic diagrams showing a specific process of deleting a sound zone in the cockpit system.

[0335] When earphones 1 are connected to the cockpit system and bound to the passenger screen, the relationship between driving zone 1 and audio zone 1 can be seen in the cockpit system architecture diagram shown in Figure 10. When earphones 1 are disconnected from the cockpit system, the cockpit system can delete audio zone 1 and adjust the audio zones associated with driving zone 1, re-associating driving zone 1 with audio zone 0. As shown in Figure 14:

[0336] S1411. When earphone 1 bound to the co-pilot screen is disconnected, the driving area 1 audio management module instructs the audio policy management module to delete audio routing table 1 and configure the application information of the application corresponding to the driving area 1 in audio routing table 0.

[0337] As can be seen from step S1212 shown in the aforementioned Figure 12, when earphone 1 is disconnected, the cockpit audio service may receive a message from the audio service indicating that earphone 1 is disconnected. Based on the message that earphone 1 is disconnected, the cockpit audio service may determine that earphone 1 is bound to the screen in the driving zone 1 based on the active device information in the driving zone audio management module. Therefore, the driving zone 1 audio management module instructs the audio policy management module to delete the audio routing table 1 and configure the application information of the application corresponding to the driving zone 1 in the audio routing table 0. Specifically, the driving zone 1 audio management module may instruct the audio zone 1 management module to migrate the audio routing policy of the application corresponding to the driving zone 1. The audio zone 1 management module may call the audio policy management module to migrate the application information of the application recorded in the audio routing table 1 to the audio routing table 0 and delete the audio routing table 1. In this application, migrating the audio routing policy of an application from one audio routing table to another audio routing table may include migrating the application information (such as the application identifier) ​​of the application in this audio routing table to another audio routing table.

[0338] Because earphone 1 is disconnected, the screen in driving area 1 needs to be re-bound to the in-car speaker. Therefore, the active device information in the audio management module of driving area 1 can be updated with the in-car speaker information. For example, the in-car speaker information can include the identifier of the in-car speaker and the identifier of the audio channel of the in-car speaker.

[0339] S1412: Migrate the audio focus information in the audio focus stack associated with audio zone 1 to the audio focus stack associated with audio zone 0, and send an audio focus preemption event to the applicant of the migrated audio focus information.

[0340] The sound device bound to the screen in driving zone 0 is changed to the in-car speaker, and the audio zone associated with driving zone 0 also needs to be changed to the audio zone 0 associated with the in-car speaker. The driving zone 1 audio management module can instruct the audio zone 1 management module to migrate the audio focus information in the audio focus stack associated with audio zone 1 to the audio focus stack associated with audio zone 0. The audio focus information in the above-mentioned audio focus stack associated with audio zone 1 is the audio focus information applied for by the corresponding application of driving zone 1. Among them, the focus management module in the audio zone 1 management module can send the audio focus information in the audio focus stack associated with audio zone 1 to the audio zone 0 management module. The audio zone 0 management module can save the audio focus information in the above-mentioned audio focus stack associated with audio zone 1 to the audio focus stack associated with audio zone 0.

[0341] In some embodiments, in the scenario where the audio focus information requested by the application corresponding to the driving zone 1 is migrated from the audio focus stack associated with the audio zone 1 to the audio focus stack associated with the audio zone 0, if the application holding the audio focus in the audio zone 1 is currently playing audio, and the application holding the audio focus in the audio zone 0 is also currently playing audio, then after the audio focus information is migrated, the focus management module in the audio zone 0 management module may send an audio focus preempted event to the application holding the audio focus in the audio zone 1. Therefore, after the audio focus information requested by the application corresponding to the driving zone 1 is migrated to the audio focus stack associated with the audio zone 0, the application originally holding the audio focus in the audio zone 0 may continue to play audio, while the application originally holding the audio focus in the audio zone 1 loses the audio focus and pauses playing audio.

[0342] S1413: The driving zone 1 audio management module calls the audio zone management module to delete audio zone 1, and deletes the audio zone 1 management module.

[0343] S1414: Update the active audio zone information in the audio management module of driving zone 1 to audio zone 0 associated with driving zone 1.

[0344] The active audio zone information in the driving zone 1 audio management module can be changed from pointing to the audio zone 1 management module as shown in Figure 10 to pointing to the audio zone 0 management module as shown in Figure 13. This can indicate that the audio zone associated with driving zone 1 has changed to audio zone 0.

[0345] S1415: Adjust the audio playback route of the application corresponding to driving zone 1, and adjust the sound device for playing the audio of the application corresponding to driving zone 1 from earphone 1 to the in-car speaker.

[0346] S1416: Migrate the media session in media session stack 1 to media session stack 0, and delete media session stack 1.

[0347] In some embodiments, the ride zone 1 audio management module can synchronize audio zone changes associated with ride zone 1 with the ride zone 1 media session management module. Upon determining that the audio zone associated with ride zone 1 has changed from audio zone 1 to audio zone 0, the ride zone 1 media session management module can invoke a media session service instantiation to migrate the media session in media session stack 1 to media session stack 0 and delete media session stack 1.

[0348] S1417: Adjust the active media session stack in the media session management module of driving area 1 from pointing to media session stack 1 to pointing to media session stack 0.

[0349] As shown in FIG13 , the active media session stack in the media session management module of driving zone 1 points to media session stack 0 , which may indicate that the media session of the corresponding application of driving zone 1 may be stored in media session stack 0 .

[0350] S1418. The driving zone 0 media session management module and the driving zone 1 media session management module report the changes of the media session stack to one or more applications in the audio center, Bluetooth, and desktop service.

[0351] S1419. The audio management module of driving zone 1 reports to one or more applications in the audio center, Bluetooth, and desktop service that the audio zone switching associated with driving zone 1 is completed.

[0352] Step S1418 and step S1419 may refer to step S1119 and step S1120 shown in FIG. 11 , respectively.

[0353] The embodiment of the present application does not limit the execution order of the steps in the method shown in Figure 14 above.

[0354] As shown in Figure 13 , media session stack 1 executing media session stack 0 indicates that the media session in media session stack 1 is migrated to media session stack 0. The focus management module in the audio zone 1 management module pointing to the focus management module in the audio zone 0 management module indicates that the audio focus information in the audio focus stack associated with audio zone 0 is migrated to the audio focus stack associated with audio zone 1. Media session stack 1, audio zone 1 management module, audio routing table 1, and Bluetooth audio channel 1 are represented by dotted lines, indicating that these modules are deleted from the cockpit system when headset 1 is disconnected.

[0355] 15A to 15D exemplarily illustrate schematic diagrams of audio playback scenarios in which some sound-emitting devices are removed.

[0356] As shown in Figure 15A, the central control screen is bound to the speakers in the car. The central control screen can display the navigation interface of the navigation application. The speakers in the car can play the navigation prompt tone of the navigation application. The co-pilot screen is bound to earphones 1, and the co-pilot screen can display the audio playback interface 1510 of the music APP. The audio playback interface 1510 may include a pause control 1511. The pause control 1511 can be used to pause the playback of music, such as music A. Earphones 1 can play music A of the music APP. It can be seen that when different screens are each bound to a sound device, the applications in different screens can play audio through the sound devices bound to the screens. In this way, users using different screens do not interfere with each other and can each listen to the audio they want to listen to.

[0357] As shown in Figure 15B, when earphone 1 is disconnected, the cockpit system can bind the co-pilot screen to the central control screen. Earphone 1 can stop playing music A. The central control screen still displays the navigation interface of the navigation application. The navigation application in the central control screen still holds the audio focus in the sound zone associated with the in-car speakers, and uses the in-car speakers to play the navigation prompt tone. Since the sound device bound to the co-pilot screen has changed, the sound zone associated with the driving area where the co-pilot screen is located has also changed. The music APP in the co-pilot screen receives a message that the audio focus has been preempted. Therefore, the music APP pauses playing music. As shown in Figure 15B, the co-pilot screen displays the audio playback interface 1510 of the music APP. The audio playback interface 1510 may include a playback control 1512. The playback control 1512 may indicate that music A is currently paused and can be used to trigger the music APP to continue playing music A.

[0358] As shown in Figure 15C , the center console can display an audio center user interface 1520 in response to a user opening the audio center. As can be seen from the previous embodiment, if the center console and the passenger screen are bound to the same sound device, the audio zones associated with the center console and passenger screens are the same, and the two passenger screens share a common media session stack. Therefore, the audio center in the center console can access the media session of the passenger screen application, enabling it to display the multimedia content on the passenger screen. As shown in Figure 15C , user interface 1520 may include multimedia content from the music app on the passenger screen, such as play controls 1521. Play controls 1521 can be used to trigger the music app on the passenger screen to play music A.

[0359] In response to the operation of play control 1521 shown in Figure 15C , the in-car speakers can begin playing Music A from the music app on the passenger screen. Play control 1521 shown in Figure 15C in the audio center user interface 1520 can be switched to display as pause control 1522 shown in Figure 15D . Pause control 1522 can be used to pause Music A. Furthermore, play control 1521 shown in Figure 15C in the audio playback interface 1510 on the passenger screen also switches to display as pause control 1511 shown in Figure 15D . The in-car speakers can then continue playing Music A.

[0360] In some embodiments, in response to an operation on playback control 1521 shown in FIG15C , the audio center can send a command to the cockpit audio service to play the audio of a music app. The cockpit audio service can locate the music app's media session from the media session stack instantiated by the media session service and then control the music app's media session to play the music app's audio. Furthermore, the cockpit audio service can call the audio zone management module to manage the audio focus of the audio zones associated with the in-vehicle speakers, allowing the music app to obtain audio focus.

[0361] In some embodiments, the audio focus acquired by the navigation app on the central control screen is ducked. After the music app acquires audio focus, the vehicle's speakers can still play the navigation prompt tone. While the navigation prompt tone is playing, the vehicle's speakers can lower the volume of the music playing in the music app. When the navigation prompt tone finishes playing, the vehicle's speakers can restore the volume of the music playing in the music app.

[0362] In some embodiments, when the music APP in the co-pilot screen holds the audio focus and uses earphone 1 to play music A, if earphone 1 is disconnected, the cockpit system can bind the co-pilot screen to the in-car speaker and assign the audio focus in the sound zone associated with the in-car speaker to the music APP in the co-pilot screen. In this way, the audio of the music APP can continue to play without pausing, and the in-car speaker can continue to play the above-mentioned music A without the user having to perform the operation of playing audio as shown in Figure 15C. In other words, when an application on a screen holds the audio focus in the sound zone associated with the driving area where this screen is located, if the sound device bound to this screen is disconnected, the application on this screen can switch to continue to hold the focus in the sound zone where the in-car speaker is located. The application can seamlessly switch to playing audio using the in-car speaker.

[0363] When the first screen (such as the central control screen) and the second screen (such as the co-pilot screen) are both associated with the first sound zone of the in-car speaker, the cockpit system detects an input operation on the first screen for viewing audio playback information, and can display a first list on the first screen according to the first media session stack. The first list includes the audio playback information indicated by the first media session stack. The above-mentioned input operation for viewing audio playback information can be a user operation to open the audio center in the first screen. The first list can refer to the user interface 1520 shown in Figure 15C above. When the in-car speaker plays the second audio, when an input operation on the first audio playback information in the first list is detected on the first screen, the cockpit system can play the first audio through the in-car speaker and pause the second audio. The above-mentioned input operation on the first audio playback information in the first list can refer to the operation of the playback control 1521 shown in Figure 15C. For example, the second audio can be the navigation prompt sound of the navigation application in the central control screen shown in Figure 15B. The first audio can be music A in the music APP in the co-pilot screen shown in Figure 15D.

[0364] When the first screen (such as the central control screen) is associated with the first sound zone of the car speaker, and the second screen (such as the co-pilot screen) is associated with the first sound device (such as earphone 1), the cockpit system detects an input operation on the first screen for viewing audio playback information, and can display a second list on the first screen according to the first media session stack. The second list includes the audio playback information indicated by the first media session stack. Since the media session of the application corresponding to the driving zone associated with the second sound zone in the first media session stack has been migrated to the second media session stack, the second list does not include the audio playback information of the application corresponding to the driving zone associated with the second sound zone (for example, the audio playback information of music A of the music APP in the co-pilot screen shown in Figure 15C above). The cockpit system detects an input operation on the second screen for viewing audio playback information, and can display a third list on the second screen according to the second media session stack. The third list includes the audio playback information indicated by the second media session stack. The third list can be the user interface of the audio center on the second screen. Since the first media session stack and the second media session stack are different, the second list and the third list are different.

[0365] FIG16 exemplarily shows a schematic diagram of audio stream transmission in different audio zones provided by the present application.

[0366] When there are multiple audio zones in the cockpit system, the audio streams of applications corresponding to the driving and riding areas associated with different audio zones can be transmitted to different sound devices through different channels and played by different sound devices.

[0367] As shown in Figure 16, the driver zone audio management module includes: the driver zone 0 audio management module corresponding to the central control screen, the driver zone 1 audio management module corresponding to the passenger screen, and the driver zone 2 audio management module corresponding to the rear screen. The driver zone 0 audio management module pointing to the audio zone 0 management module indicates that driver zone 0 is associated with audio zone 0. Similarly, driver zone 1 is associated with audio zone 1. Driver zone 2 is associated with audio zone 2. Audio zone 0 can be the audio zone associated with the in-vehicle speakers. Audio zone 1 can be the audio zone associated with headphone 1. Audio zone 2 can be the audio zone associated with headphone 2.

[0368] As can be seen from the above embodiments, the driving zone 0 audio management module can instruct the audio zone 0 management module to manage the audio routing strategy of the corresponding application of the driving zone 0. The audio zone 0 management module can store the audio routing strategy of the corresponding application of the driving zone 0 in the audio routing table 0. The audio routing table 0 points to the audio channel of the in-car speaker, which can indicate that the audio of the application recorded in the audio routing table 0 can be routed to the audio channel of the in-car speaker. Similarly, the driving zone 1 audio management module can instruct the audio zone 1 management module to manage the audio routing strategy of the corresponding application of the driving zone 1. The audio routing table 1 points to the audio channel of the in-car speaker, which can indicate that the audio of the application recorded in the audio routing table 1 can be routed to the Bluetooth audio channel 1. The driving zone 2 audio management module can instruct the audio zone 2 management module to manage the audio routing strategy of the corresponding application of the driving zone 2. The audio routing table 2 points to the audio channel of the in-car speaker, which can indicate that the audio of the application recorded in the audio routing table 2 can be routed to the Bluetooth audio channel 2.

[0369] When an application needs to play audio, it can create a corresponding audio track (AudioTrack). An audio track can be a class used for audio playback and can transmit audio data to the audio channel of the sound device.

[0370] For example, there may be audio track 0 in the central control screen. The audio policy management module can query the application to which audio track 0 belongs in audio routing table 0, and then transmit the audio stream of the application to which audio track 0 belongs to the audio channel of the in-car speaker (for example, audio channel 0, or audio channel 1, or audio channel 2, etc.) according to audio routing table 0. The audio channel management module can transmit the audio stream in the audio channel of the in-car speaker to the in-car speaker through the in-car speaker hardware abstraction module. Then, the in-car speaker can play the above audio stream from audio track 0.

[0371] Audio track 1 can be displayed on the passenger screen. The audio policy management module can query the audio policy management module to find the application to which audio track 1 belongs in audio routing table 1. Then, based on audio routing table 1, the audio stream of the application to which audio track 1 belongs can be transmitted to Bluetooth audio channel 1. The audio channel management module can transmit the audio stream on Bluetooth audio channel 1 to earphone 1 through the Bluetooth hardware abstraction module. Then, earphone 1 can play the audio stream from audio track 1.

[0372] Track 2 can be played on the rear screen. The audio policy management module can query the audio policy management module to find the application to which Track 2 belongs in audio routing table 2. The audio stream of the application to which Track 2 belongs can then be transferred to Bluetooth audio channel 2 according to audio routing table 2. The audio channel management module can transfer the audio stream in Bluetooth audio channel 2 to earphone 2 via the Bluetooth hardware abstraction module. Earphone 2 can then play the audio stream from Track 2.

[0373] In some embodiments, upon detecting that the first sound device is disconnected, the cockpit system may change the audio zone associated with the second screen from the second audio zone to the first audio zone, and adjust the audio focus stack, audio routing table, and media session stack corresponding to the first audio zone and the second audio zone. For details, please refer to Figures 12 to 14 of this application for an introduction to the cockpit system adjusting audio routing table 0, audio routing table 1, media session stack 0, media session stack 1, and the audio focus stacks corresponding to audio zones 0 and 1 after detecting that earphone 1 is disconnected.

[0374] Audio focus management

[0375] The cockpit system provided by this application can manage the audio focus in multiple audio zones separately. The audio focus in different audio zones can be independent of each other and do not affect each other.

[0376] FIG17 exemplarily shows a schematic diagram of applying for audio focus provided by the present application.

[0377] As shown in Figure 17, when multimedia playback application 1 needs to play audio, it can request audio focus from the audio service through the audio management API. Multimedia playback application 1 can be a music APP, or a navigation APP, or a video APP, or a phone APP, etc., which have audio playback requirements. The embodiment of this application does not limit the type of multimedia playback application 1. The scenarios in which multimedia playback application 1 needs to play audio may include but are not limited to: multimedia playback application 1 detects a user operation for triggering audio playback, multimedia playback application 1 receives an incoming call and needs to play an incoming call prompt tone, multimedia playback application 1 plays a navigation prompt tone during navigation, etc.

[0378] The request for the multimedia playback application 1 to apply for the audio focus may include but is not limited to: the application identifier of the multimedia playback application 1 and the type of the audio focus applied for.

[0379] The audio focus management module in the audio service can send a request for audio focus from multimedia player application 1 to the cabin audio service. The cabin audio service can determine which driving zone the multimedia player application corresponds to. Specifically, the cabin audio service can determine which driving zone audio management module's application list multimedia player application 1 is in based on the application identifier of multimedia player application 1. For example, if the application list of the driving zone 0 audio management module includes multimedia player application 1, then multimedia player application 1 is the application corresponding to driving zone 0.

[0380] If multimedia playback application 1 corresponds to driving zone 0, the driving zone 0 audio management module can determine that driving zone 0 is associated with audio zone 0 based on the active audio zone information in the driving zone 0 audio management module, and then transmit a message from multimedia playback application 1 requesting audio focus to the audio zone 0 management module corresponding to audio zone 0. In this way, multimedia playback application 1 can request audio focus in audio zone 0. The focus management module in the audio zone 0 management module determines whether multimedia playback application 1 can obtain focus based on the type of audio focus requested by multimedia playback application 1 and the audio focus stack associated with audio zone 0.

[0381] For example, if the audio focus stack associated with audio zone 0 indicates that the application holding audio focus in audio zone 0 holds exclusive focus, the audio zone 0 management module can deny multimedia player application 1's request for audio focus. This request to deny audio focus can be passed to multimedia player application 1 via the cockpit audio service, the audio service, and the audio management API. In some embodiments, upon receiving this request to deny audio focus, multimedia player application 1 can provide the user with a prompt indicating that audio playback has failed or is temporarily unavailable.

[0382] If the audio focus stack associated with audio zone 0 indicates that the application holding the audio focus in audio zone 0 holds the long focus, the audio zone 0 management module can agree to the request of multimedia playback application 1 to apply for audio focus. Among them, the audio zone 0 management module can delete the audio focus information at the top of the audio focus stack associated with audio zone 0 or move it back one position, and place the audio focus information of multimedia playback application 1 in the audio focus stack associated with audio zone 0. The audio focus information of the above-mentioned multimedia playback application 1 may include information such as the application identifier of the multimedia playback application 1 and the type of audio focus requested. In this way, multimedia playback application 1 can hold the audio focus in audio zone 0 and use the sound device associated with audio zone 0 to play audio.

[0383] Similarly, if multimedia player application 1 corresponds to driving zone 1, the driving zone 1 audio management module can transmit a message from multimedia player application 1 requesting audio focus to the audio zone 1 management module. In this way, multimedia player application 1 can request audio focus in audio zone 1. The focus management module within the audio zone 1 management module can determine whether multimedia player application 1 can obtain focus based on the type of audio focus requested by multimedia player application 1 and the audio focus stack associated with audio zone 1.

[0384] If multimedia player application 1 corresponds to driving zone 2, the driving zone 1 audio management module can transmit a message from multimedia player application 1 requesting audio focus to the audio zone 2 management module. In this way, multimedia player application 1 can request audio focus in audio zone 2. The focus management module in the audio zone 2 management module can determine whether multimedia player application 1 can obtain focus based on the type of audio focus requested by multimedia player application 1 and the audio focus stack associated with audio zone 2.

[0385] In some embodiments, when the audio zone associated with the driving zone changes, the driving zone audio management module can instruct the audio zone management module to update the audio focus stack associated with the corresponding audio zone. For example, driving zone 1 changes from being associated with audio zone 1 to being associated with audio zone 0. The driving zone 1 audio management module can instruct the audio zone 1 management module to migrate the audio focus information in the audio focus stack associated with audio zone 1 to the audio focus stack associated with audio zone 0. If multimedia playback application 1 corresponds to driving zone 1, the audio focus information of multimedia playback application 1 is migrated to the audio focus stack associated with audio zone 0. The audio zone for which multimedia playback application 1 competes for audio focus changes from audio zone 1 to audio zone 0. In the above-mentioned process of audio focus information migration, multimedia playback application 1 does not need to perceive the change in the audio zone for which it competes for audio focus. Multimedia playback application 1 only needs to apply for audio focus or give up audio focus from the audio service through the audio management API.

[0386] As can be seen from the above embodiments, different audio zones can independently support applications requesting audio focus. Applications holding audio focus in different audio zones can use different sound devices to play audio. The cockpit system can manage the audio focus in a single audio zone to ensure that the appropriate application holds audio focus and plays audio using the sound device associated with the audio zone when multiple applications compete for audio focus in the same audio zone.

[0387] Volume Management

[0388] The cockpit system provided by this application can manage the volume in multiple audio zones separately. The volume in different audio zones can be adjusted independently without affecting each other. In other words, adjusting the volume in one audio zone will not affect the volume in other audio zones.

[0389] FIG18 is a schematic diagram of adjusting the volume of a multimedia playback application provided in an embodiment of the present application.

[0390] As shown in Figure 18, the multimedia playback application 1 can request the audio service to adjust the volume through the audio management API. In some embodiments, after detecting a user operation to adjust the volume, the multimedia playback application 1 can request to adjust the volume. For example, the user operation to adjust the volume detected by the multimedia playback application 1 may include: an operation of sliding up or down on a preset area on the video playback interface displayed by the multimedia playback application 1. The embodiments of the present application do not limit the user operation used to trigger the multimedia playback application 1 to adjust the volume.

[0391] The request for the multimedia playback application 1 to adjust the volume may include but is not limited to: the application identifier of the multimedia playback application 1 and the volume level.

[0392] The volume management module in the audio service can send a request for adjusting the volume of the multimedia player application 1 to the cockpit audio service. The cockpit audio service can determine which driving zone the multimedia player application corresponds to.

[0393] If multimedia player application 1 corresponds to driving zone 0, the driving zone 0 audio management module can transmit a message requesting multimedia player application 1 to adjust the volume to the audio zone 0 management module. The audio zone 0 management module can then adjust the volume of the audio played by the in-vehicle speakers through the in-vehicle speaker hardware abstraction module.

[0394] If multimedia playback application 1 corresponds to driving zone 1, the driving zone 1 audio management module can transmit a message from multimedia playback application 1 requesting volume adjustment to the audio zone 1 management module. The audio zone 1 management module can then adjust the volume of the audio played by headphones 1 via the Bluetooth hardware abstraction module. In some embodiments, when adjusting the volume of headphones 1, the Bluetooth hardware abstraction module can select a corresponding volume adjustment method based on whether the headphones 1 support absolute volume. If the headphones 1 support absolute volume, the Bluetooth hardware abstraction module can adjust the volume of the headphones 1 by adjusting absolute volume. If the headphones 1 do not support absolute volume, the Bluetooth hardware abstraction module can adjust the volume of the headphones 1 by adjusting non-absolute volume. Absolute volume can refer to sending the volume adjustment to the headphones, which then perform volume processing on the audio stream to achieve volume adjustment. Non-absolute volume can refer to the Bluetooth hardware abstraction module performing volume processing on the audio stream based on the volume adjustment and then passing the processed audio stream to the headphones for playback. In other words, using the non-absolute volume adjustment method above eliminates the need for volume processing on the headphones. Non-absolute volume can also be referred to as relative volume. The embodiments of this application do not limit the above volume adjustment methods.

[0395] Similarly, if multimedia playback application 1 corresponds to driving zone 2, the driving zone 2 audio management module can transmit a message from multimedia playback application 1 requesting volume adjustment to the audio zone 2 management module. The audio zone 2 management module can then adjust the volume of the audio played by earphone 2 through the Bluetooth hardware abstraction module. When adjusting the volume of earphone 2, the Bluetooth hardware abstraction module can select a corresponding volume adjustment method based on whether earphone 2 supports absolute volume. For details, please refer to the above-mentioned method for adjusting the volume of earphone 1. I will not repeat it here.

[0396] FIG19 is a schematic diagram of a system application for adjusting volume provided in an embodiment of the present application.

[0397] As shown in Figure 19, system application 1 can request the cockpit audio service to adjust the volume through the cockpit audio management API. System application 1 can be a cockpit voice assistant, an audio center, or a desktop service and other system applications. After detecting the user operation of adjusting the volume, system application 1 can request to adjust the volume. For example, if system application 1 is a cockpit voice assistant, the user operation of adjusting the volume detected by system application 1 may include: voice instructions for adjusting the volume. If system application 1 is an audio center, the user operation of adjusting the volume detected by system application 1 may include: user operation of the volume control (such as a volume bar, etc.) in the multimedia playlist displayed in the audio center. If the system application is a desktop service, the user operation of adjusting the volume detected by system application 1 may include: user operation of the volume control (such as a volume bar, etc.) displayed on the desktop, and user operation of the physical button for adjusting the volume on the screen. The embodiment of the present application does not limit the user operation used to trigger the system application 1 to adjust the volume.

[0398] In some embodiments, the system application 1 can determine which screen it belongs to and the driving zone bound to the screen it belongs to. The request for the system application 1 to adjust the volume may include but is not limited to: the driving zone identifier of the driving zone bound to the screen to which the system application 1 belongs and the volume level.

[0399] The cockpit audio service can determine the driving zone according to the driving zone identifier in the request, and use the driving zone audio management module corresponding to the driving zone to adjust the volume.

[0400] If the driving zone identifier indicates driving zone 0, the driving zone 0 audio management module can transmit a message requesting system application 1 to adjust the volume to the audio zone 0 management module. In this way, the volume in audio zone 0, that is, the volume of the speakers in the car, can be adjusted.

[0401] If the driving zone identifier indicates driving zone 1, the driving zone 1 audio management module can transmit a message requesting system application 1 to adjust the volume to the audio zone 1 management module. In this way, the volume in audio zone 1, that is, the volume of earphone 1, can be adjusted.

[0402] If the driving zone identifier indicates driving zone 2, the driving zone 2 audio management module can transmit a message requesting the system application 1 to adjust the volume to the audio zone 2 management module. In this way, the volume in audio zone 2, that is, the volume of earphone 2, can be adjusted.

[0403] The specific method for adjusting the volume of the corresponding sound zone by the driving zone audio management module corresponding to the driving zone 0, driving zone 1 or driving zone 2 can be referred to the description of the embodiment of FIG18 , which will not be repeated here.

[0404] 20A to 20D are schematic diagrams of some volume adjustment scenarios provided in this application.

[0405] As shown in Figure 20A, the central control screen is linked to the in-car speakers. The central control screen can display the navigation app's navigation interface. The in-car speakers can play the navigation app's navigation prompts. The passenger screen is linked to earphones 1, which can display the music app's audio playback interface 2010. Audio playback interface 2010 may include a volume bar 2011. Volume bar 2011 can be used to trigger the music app to adjust the volume. Earphones 1 can play music A from the music app.

[0406] In response to an operation of sliding right on the volume bar 2011 to increase the volume as shown in FIG. 20A , the music APP may request to increase the volume.

[0407] As shown in FIG20B , the cockpit system can adjust the volume of the audio played by earphone 1 based on the music APP's request to increase the volume, so that earphone 1 increases the volume to play music A. The specific method for the cockpit system to adjust the volume of the audio played by earphone 1 can refer to the method described in the embodiment of FIG18 above.

[0408] As shown in Figures 20A and 20B, when an application on the passenger screen requests volume adjustment, the cockpit system can adjust the volume of earphones 1 bound to the passenger screen while keeping the volume of the in-car speakers unchanged. This way, users using the central control screen and listening to audio through the in-car speakers and users using the passenger screen and listening to audio through earphones 1 can listen to audio and adjust volume independently without interfering with each other.

[0409] As shown in Figure 20C, while earphones 1 are playing music (e.g., Music A) from a music app, the passenger screen can display desktop 2020 in response to the user's operation to call up the desktop. In some embodiments, desktop 2020 may include a volume control. In response to the user's operation of increasing the volume on volume control 2021, the desktop service on the passenger screen can request to increase the volume.

[0410] As shown in FIG20D , the cockpit system can adjust the volume of the audio played by earphone 1 based on the volume increase request of the desktop service in the passenger screen, so that earphone 1 increases the volume to play music A. The specific method of adjusting the volume of the audio played by earphone 1 by the desktop service can refer to the method described in the embodiment of FIG19 above.

[0411] In some embodiments, when the first screen (e.g., the central control screen) is associated with the first sound zone (e.g., sound zone 0) of the in-car speaker, and the second screen (e.g., the passenger screen) is associated with the second sound zone (e.g., sound zone 1) of the first sound device (e.g., earphone 1), the user can adjust the volume of the in-car speaker through the first screen and adjust the volume of the first sound device through the second screen. For example, when an input operation for adjusting the volume to a first volume is detected on the second screen, the cockpit system can adjust the playback volume of the first sound device to the first volume. The process of adjusting the volume of the first sound device can refer to the embodiments of Figures 20A to 20D above.

[0412] Media Session Management

[0413] The cockpit system provided in the present application can manage the media sessions of the applications corresponding to each driving zone. Specifically, when the audio zones associated with multiple driving zones are the same, the cockpit system can uniformly manage the media sessions of the applications corresponding to these multiple driving zones. The media sessions of the applications corresponding to these multiple driving zones can be placed in the same media session stack. When the audio zones associated with two driving zones are different, the cockpit system can manage the media sessions of the applications corresponding to these two driving zones separately. The media sessions of the applications corresponding to these two driving zones can be placed in two different media session stacks respectively. In other words, the media session stacks in the cockpit system can correspond to the audio zones one by one. The media session stack corresponding to a audio zone may include the application corresponding to the driving zone associated with this audio zone. The media session stacks corresponding to different audio zones can be independent of each other and do not affect each other.

[0414] FIG21 is a schematic diagram of a media session management provided by the present application.

[0415] Here, an example is used to illustrate that the cockpit system includes driving zone 0, driving zone 1, and driving zone 2, and driving zone 0 and driving zone are associated with the same sound zone, and the sound zone associated with driving zone 2 is different from the sound zones associated with driving zone 0 and driving zone 1.

[0416] As shown in Figure 21, the cockpit media session management module includes the driving zone 0 media session management module, the driving zone 1 media session management module, and the driving zone 2 media session management module. The screen in driving zone 0 is bound to the in-vehicle speakers. Driving zone 0 is associated with the audio zone of the in-vehicle speakers. The driving zone 0 media session management module can instruct the media session service to instantiate and create media session stack 0 and store the media session corresponding to the driving zone 0 application in media session stack 0.

[0417] There are no headphones bound to the screen in passenger zone 1. That is, no external audio device is connected to the cockpit system via the screen in passenger zone 1. Therefore, the screen in passenger zone 1 is bound to the in-car speakers. Passenger zone 1 and passenger zone 0 are associated with the same audio zone. The media session management module in passenger zone 1 can store media sessions for applications corresponding to passenger zone 1 in media session stack 0.

[0418] The screen in driving zone 2 is bound to earphone 2. Therefore, driving zone 2 can be associated with the audio zone of earphone 2. The media session management module in driving zone 2 can instruct the media session service to instantiate and create media session stack 2 and store the media session of the corresponding application in driving zone 2 in media session stack 2.

[0419] The audio center on the screen in the driving zone 0 can call the driving zone 0 media session management module through the cockpit audio management API to obtain the media session. The audio center on the screen in the driving zone 0 can obtain the media session in the media session stack 0.

[0420] The audio center on the screen in passenger zone 1 can call the media session management module in passenger zone 1 through the cockpit audio management API to obtain the media session. The audio center on the screen in passenger zone 1 can obtain the media session in media session stack 0.

[0421] The audio center on the screen in the passenger area 2 can call the media session management module in the passenger area 2 through the cockpit audio management API to obtain the media session. The audio center on the screen in the passenger area 2 can obtain the media session in the media session stack 2.

[0422] Media session stack 0 contains media sessions for the corresponding apps in both Riding Zone 0 and Riding Zone 1. Therefore, the multimedia playlists displayed in the audio center on the screens in Riding Zone 0 and Riding Zone 1 are identical and contain multimedia content information for the apps in Riding Zone 0 and Riding Zone 1. Media session stack 0 contains media sessions for the apps in Riding Zone 2. The multimedia playlist displayed in the audio center on the screen in Riding Zone 2 contains multimedia content information for the apps in Riding Zone 2 and is different from the multimedia playlists displayed in the audio center on the screens in Riding Zone 0 and Riding Zone 1.

[0423] When an external sound device is connected to the cockpit system via the screen in passenger area 1, the sound device bound to the screen in passenger area 1 can be switched from the in-car speakers to the external sound device. The media session management module in passenger area 2 can instruct the media session service to instantiate a new media session stack, for example, media session stack 1, and migrate the media session corresponding to the application in passenger area 1 from media session stack 0 to media session stack 1.

[0424] It can be seen that the media session stack and the media sessions in the media session stack can change dynamically with the connection and removal of external sound devices.

[0425] In some embodiments, a multimedia playback application can request the media session service to create a media session corresponding to the multimedia playback application through the media session management API. The media session service can send a message to the cockpit media session management module requesting the multimedia application to create a media session. Then, the cockpit media session management module can determine which driving zone the multimedia playback application corresponds to, and use the driving zone media session management module corresponding to the corresponding driving zone to create a media session. For example, if the multimedia playback application corresponding to driving zone 0 requests to create a media session, the driving zone 0 media session management module can create a media session corresponding to the multimedia playback application and store the media session in media session stack 0.

[0426] A multimedia player application can request access to its media session from the media session service through the media session management API. Upon receiving a request from a multimedia player application to access a media session, the media session service can instantiate the media session service to obtain information about the multimedia player application's media session and then send the media session information to the multimedia player application.

[0427] It can be seen that the multimedia playback application accesses the media session based on the media session service, and does not need to perceive the changes in the media session stack in the cockpit system.

[0428] Screen Migration

[0429] The cockpit system provided in this application can support screen migration. Screen migration can refer to migrating multimedia content played on one screen to another screen. Among them, the original screen that performs screen migration can cancel the display of the playback interface of the migrated multimedia content, and the sound device bound to the original screen can stop playing the audio in the migrated multimedia content. After the screen migration, the screen that receives the screen migration can display the playback interface of the migrated multimedia content, and the sound device bound to the screen can continue to play the audio from the position where the multimedia content was played when the screen migration was performed. This can ensure the continuity of audio playback in the screen migration scenario.

[0430] FIG22 is a schematic diagram of a screen migration method provided by the present application.

[0431] Here we take the example of migrating the multimedia content currently playing on the central control screen to the passenger screen, and the sound devices bound to the central control screen and the passenger screen are different to illustrate.

[0432] As shown in Figure 22, the desktop service can generate an APP migration event for application 1 to migrate from the central control screen to the co-pilot screen. Application 1 can be the multimedia playback application corresponding to the central control screen. The multimedia playback interface of application 1 can be displayed on the central control screen, and the sound device bound to the central control screen, such as the in-car speaker, is playing the audio of application 1. In response to the user operation of migrating the multimedia playback interface of application 1 from the central control screen to the co-pilot screen, the desktop service in the central control screen can generate the above-mentioned APP migration event of application 1. That is, the APP migration event can refer to the display screen change of the multimedia playback interface of application 1. The APP migration event can also be called a screen migration event.

[0433] In some embodiments, the APP migration event may include but is not limited to: the application identifier of the migrated application (i.e., application 1), the screen identifier of the original screen (i.e., the central control screen), and the screen identifier of the screen receiving the screen migration (i.e., the co-pilot screen). The desktop service can send the above-mentioned APP migration event to the driving area audio management module. Driving area 0 is bound to the central control screen. Driving area 1 is bound to the co-pilot screen. Before the screen migration, the application list in the driving area 0 audio management module may include application 1, and the application list in the driving area 1 audio management module may not include application 1.

[0434] Based on the aforementioned app migration event, the audio management module for driving zone 0 can migrate App 1 from the app list to the audio management module for driving zone 1. Therefore, after the screen migration, the app list in the audio management module for driving zone 0 may no longer include App 1, while the app list in the audio management module for driving zone 1 may include App 1. In other words, App 1 has been changed from the app corresponding to driving zone 0 to the app corresponding to driving zone 1.

[0435] Driving zone 0 is associated with audio zone 0. Driving zone 1 is associated with audio zone 1. Based on the above-mentioned APP migration event, the driving zone 0 audio management module can also instruct the audio zone 0 management module to migrate the audio routing strategy and audio focus information of application 1 to the audio zone 1 management module. The audio zone 1 management module can store the audio routing strategy of the above-mentioned application 1 in the audio routing table associated with audio zone 1, and store the audio focus information of application 1 in the audio focus stack associated with audio zone 1. Based on the migration of the above-mentioned audio routing strategy and audio focus information, the sound device that plays the audio of application 1 can be changed from the in-car speaker to the sound device bound to the co-pilot screen, such as earphone 1.

[0436] In some embodiments, the audio zone 1 management module can place the audio focus information of application 1 at the top of the audio focus stack associated with audio zone 1. Then, after the screen migration, application 1 can continue to hold the audio focus, but the audio focus it holds changes from the audio focus of audio zone 0 to the audio focus of audio zone 1.

[0437] When the ride zone corresponding to application 1 changes, the ride zone 1 audio management module can synchronize the ride zone corresponding to application 1 with the ride zone 1 media session management module. The ride zone 1 media session management module can then instruct the media session service instantiation to migrate the media session of application 1 from media session stack 0 to media session stack 1.

[0438] In some embodiments, when the multimedia playback interface of the above-mentioned application 1 is migrated to the passenger screen, the desktop service of the passenger screen can display the multimedia playback interface of application 1 according to the size of the passenger screen, so that the multimedia playback interface of application 1 is adapted to the passenger screen.

[0439] It should be noted that in the aforementioned screen migration scenario, although Application 1 changes from the application corresponding to Driving Zone 0 to the application corresponding to Driving Zone 1, the storage location of Application 1's application installation package remains unchanged. The application icon for Application 1 can still be displayed on the central control screen. In response to the operation of opening Application 1, the cockpit system can still display the user interface of Application 1 on the central control screen.

[0440] As can be seen from Figure 22 above, during the screen migration process, the migrated application does not need to adapt the multimedia display interface and audio stream according to the screen after the screen migration. The migration of the multimedia playback interface display screen and the migration of the audio sound device can be completed by the driving area management layer and the audio framework layer in the cockpit system. Combined with the embodiment of audio stream transmission in Figure 16 above, it can be seen that since the audio routing strategy of the above-mentioned application 1 is migrated to the audio routing table associated with audio zone 1, the audio track of application 1 can find application 1 in the audio routing table associated with audio zone 1, and then the audio of application 1 is transmitted to the audio channel of earphone 1 according to the audio routing table associated with audio zone 1. This can achieve the seamless switching of the audio of application 1 from the in-car speakers to earphone 1, maintaining the continuity of audio playback. The seamless switching of the audio of application 1 from the in-car speakers to earphone 1 can mean that when the audio of application 1 is switched to earphone 1, earphone 1 can continue to play the audio from the position where the in-car speakers stopped playing the audio.

[0441] Figures 23 and 24 are schematic diagrams of screen migration scenarios provided by this application.

[0442] As shown in Figure 23, the central control screen displays the multimedia playback interface of application 1. The driving zone 0 bound to the central control screen contains application 1. That is, application 1 is currently the application corresponding to driving zone 0. Driving zone 0 is associated with the entire vehicle sound zone. The media session stack corresponding to the entire vehicle sound zone includes the media session of application 1. Application 1 can determine that the audio of application 1 needs to be routed to the audio channel of the in-car speaker based on the audio routing table associated with the entire vehicle sound zone. Therefore, application 1 can transmit the audio playback data to the audio channel of the in-car speaker. The in-car speaker can play the audio of application 1. In response to the operation of migrating the multimedia playback interface of application 1 to the co-pilot screen, the cockpit system can migrate the media session, audio routing strategy, and audio focus of application 1. For the specific process, please refer to the introduction of the embodiment of Figure 22 above. The embodiment of this application does not limit the above-mentioned operation of migrating the multimedia playback interface of application 1 to the co-pilot screen. For example, the operation can be an operation of sliding three fingers in a specified direction on the multimedia playback interface of application 1.

[0443] As shown in Figure 24, after Application 1's multimedia playback interface is migrated from the central control screen to the passenger screen, the passenger screen can display Application 1's multimedia playback interface. The central control screen can then stop displaying Application 1's multimedia playback interface. Application 1 is migrated from driving zone 0 to driving zone 1. This means that Application 1 becomes the application corresponding to driving zone 1. Application 1's media session is migrated to the media session stack corresponding to headphone zone 1. The media session stack corresponding to the vehicle's audio zones no longer contains Application 1's media session. Furthermore, because Application 1's audio routing policy has been migrated from the audio routing table associated with the vehicle's audio zones to the audio routing table associated with headphone zone 1, Application 1 can determine, based on the audio routing table associated with headphone zone 1, that its audio needs to be routed to the audio channel of headphone 1. Therefore, Application 1 can transmit audio playback data to the audio channel of headphone 1. Headphone 1 can then play Application 1's audio. When the vehicle's speakers stop receiving Application 1's audio playback data, they can stop playing Application 1's audio.

[0444] After the above application 1 completes the screen migration, the central control screen can open other multimedia playback applications and play the corresponding audio through the car speakers. At this time, the car speakers and headphones 1 can play audio separately without interfering with each other.

[0445] From the above screen migration scenario, it can be seen that even if application 1 is not installed on the co-pilot screen, the multimedia playback interface of application 1 can be displayed through the above screen migration method, and the audio of application 1 can be played through the earphones 1 bound to the co-pilot screen.

[0446] In some embodiments, in response to the operation of closing application 1 on the co-pilot screen, the cockpit system can delete application 1 from the application list corresponding to driving zone 1, and delete the audio focus information and audio routing strategy of application 1 in audio zone 1.

[0447] In some embodiments, the multimedia playback interface of the above-mentioned application 1 can also be migrated from the co-pilot screen back to the central control screen. For details, please refer to the introduction of the multimedia playback interface of application 1 from the central control screen to the co-pilot screen in the above embodiment.

[0448] In some embodiments, when the first screen (such as the central control screen) is associated with the first sound zone (such as sound zone 0) of the in-car speaker, and the second screen (such as the passenger screen) is associated with the second sound zone (such as sound zone 1) of the first sound device (such as earphone 1), the audio played by the in-car speaker can be migrated from the first screen to the second screen as the multimedia playback interface corresponding to the audio is migrated to the first sound device for playback. For example, the first screen displays the first interface of the second application. The first interface can be the multimedia playback interface of application 1 shown in Figure 23. The first interface is the playback interface of the second audio. The second audio can be the audio of application 1. When an input operation to migrate the first interface from the first screen to the second screen is detected, the cockpit system can display the first interface on the second screen, cancel the display of the first interface on the first screen, and switch the second audio from the in-car speaker to the first sound device to continue playing. The in-car speaker can pause playing the second audio. For details, please refer to the embodiment of the multimedia playback interface of application 1 migrating from the central control screen to the passenger screen shown in Figures 23 and 24.

[0449] In the scenario where the first interface of the second application is migrated from the first screen to the second screen, the cockpit system can migrate the audio focus of the second application in the audio focus stack, migrate the application information of the second application in the audio routing table, and migrate the media session of the second application in the media session stack. For details, please refer to the description of the embodiment of migrating application 1 shown in Figure 22 above.

[0450] Screen Sharing

[0451] The cockpit system provided in this application can support screen sharing. Screen sharing can refer to sharing multimedia content played on one screen to one or more other screens. Among them, the original screen for screen sharing can continue to display the playback interface of the shared multimedia content.

[0452] FIG25 is a schematic diagram of a screen sharing method provided in this application.

[0453] Here we take the example of sharing the multimedia content currently playing on the passenger screen to the central control screen and the rear screen, and the sound devices bound to the central control screen, the passenger screen, and the rear screen are different.

[0454] As shown in Figure 25, in the cockpit system, the cockpit audio service may also include a sharing management module. The sharing management module can be used to manage screen sharing. Among them, the content managed by the sharing management module may include: the driving zone information that receives sharing, the shared application information, the driving zone information that emits sound, and the driving zone information that is shared. The driving zone information that receives sharing can be used to indicate the driving zone to which the screen that receives multimedia content sharing belongs. The shared application information can be used to indicate which application the shared multimedia content belongs to. The driving zone information that emits sound can be used to indicate which driving zone’s screen-bound sound device plays the audio in the shared multimedia content after screen sharing. The shared driving zone information can be used to indicate the driving zone to which the screen that initiates screen sharing belongs, that is, the driving zone to which the original screen that played the shared content before screen sharing belongs.

[0455] As shown in Figure 25, the desktop service can generate an APP sharing event for sharing application 4 from the passenger screen to the central control screen and the rear screen. Application 4 can be the multimedia playback application corresponding to the passenger screen. The multimedia playback interface of application 4 can be displayed on the passenger screen, and the sound device bound to the passenger screen, such as earphones 1, is playing the audio of application 4. In response to the user operation of sharing the multimedia playback interface of application 4 from the passenger screen to the central control screen and the rear screen, the desktop service of the passenger screen can generate the above-mentioned APP sharing event of application 4. That is, the APP sharing event can mean that the multimedia playback interface of application 4 will be displayed on more screens. The APP sharing event can also be called a screen sharing event.

[0456] In some embodiments, the APP sharing event may include but is not limited to: the application identifier of the shared application (i.e., application 4), the screen identifier of the original screen (i.e., the co-pilot screen), and the screen identifier of the screen receiving the sharing (i.e., the central control screen and the rear screen). The desktop service can send the above-mentioned APP sharing event to the sharing management module. The sharing management module can create a sharing area 0 management module based on the APP sharing event. The sharing area 0 management module can be used to manage the APP sharing events of the above-mentioned application 4. Among them, the sharing management module may include one or more sharing area management modules. A sharing area management module can be used to manage an APP sharing event. When other APP sharing events are received, the sharing management module can create a new sharing area management module.

[0457] Based on an app sharing event for application 4, the sharing zone management module can determine the following information from the app sharing event: the receiving zone information, the shared application information, the audible audible audible zone information, and the shared audible zone information. In the app sharing event for application 4, the receiving zone information can be used to indicate zone 0, where the center console is located, and zone 2, where the rear screens are located. The shared application information can be used to indicate application 4. The audible audible audible zone information can be used to indicate zone 0, where the center console is bound to the in-car speakers. The shared zone information can be used to indicate the in-car zone where the passenger seat screen is located. In other words, when the passenger seat screen shares multimedia content from application 4 with the center console and rear screens, the multimedia playback interface of application 4 can be displayed on all three screens, with audio from application 4 switched from headphones 1 to the in-car speakers. This allows the driver to view the multimedia playback interface of application 4 on the center console, while the passenger seat can view the multimedia playback interface of application 4 on the passenger seat screen. Users sitting in the back seat can watch the multimedia playback interface of application 4 through the rear screen. All users in the car can listen to the audio of application 4 through the car speakers.

[0458] The embodiments of the present application do not limit the method of selecting the sound device after screen sharing. In some embodiments, if the screen to be shared includes the central control screen or the original screen for screen sharing is the central control screen, the sound device after screen sharing can be the in-car speaker bound to the central control screen. Other external sound devices in the cockpit system do not need to play the audio of the shared application. If the screen to be shared does not include the central control screen, and the original screen for screen sharing is not the central control screen, the sound device after screen sharing can include the sound device bound to the screen to be shared, and the sound device bound to the original screen for screen sharing. In some embodiments, in any APP sharing event, the sound device after screen sharing can be switched to the in-car speaker. Other external sound devices in the cockpit system do not need to play the audio of the shared application.

[0459] The sharing zone 0 management module can indicate to the driving zone 1 audio management module that driving zone 1 is the shared driving zone and the shared application is application 4 based on the shared driving zone information and the shared application information. The sharing zone 0 management module can instruct the driving zone 0 audio management module and the driving zone 2 audio management module to accept screen sharing based on the received shared driving zone information. The sharing zone 0 management module can indicate that driving zone 0 is the driving zone where the sound device is located after screen sharing based on the sounding driving zone information. Then, the driving zone 1 audio management module can migrate application 4 in the application list to the driving zone 0 audio management module. Therefore, after screen sharing, the application list in the driving zone 1 audio management module may not include application 4, and the application list in the driving zone 0 audio management module may include application 4. In other words, application 4 changes from the application corresponding to driving zone 1 to the application corresponding to driving zone 0.

[0460] Driving zone 0 is associated with audio zone 0. Driving zone 1 is associated with audio zone 1. Based on the instructions of the above-mentioned sharing zone 0 management module, the driving zone 1 audio management module can instruct the audio zone 1 management module to migrate the audio routing strategy and audio focus information of application 4 to the audio zone 0 management module. The audio zone 0 management module can store the audio routing strategy of the above-mentioned application 4 in the audio routing table associated with audio zone 0, and store the audio focus information of application 4 in the audio focus stack associated with audio zone 0. Based on the migration of the above-mentioned audio routing strategy and audio focus information, the sound device for playing the audio of application 4 can be changed from earphone 1 to the in-car speaker bound to the central control screen.

[0461] In some embodiments, the audio zone 0 management module can place the audio focus information of application 4 at the top of the audio focus stack associated with audio zone 0. Then, after the screen migration, application 4 can continue to hold the audio focus, but the audio focus it holds changes from the audio focus of audio zone 1 to the audio focus of audio zone 0.

[0462] In some embodiments, when the ride zone corresponding to application 4 changes, the ride zone 0 audio management module can synchronize the ride zone corresponding to application 4 with the ride zone 0 media session management module. The ride zone 0 media session management module can then instruct the media session service instantiation to migrate the media session of application 4 from media session stack 1 to media session stack 0. Optionally, the media session of application 4 may remain stored in media session stack 1 without being migrated.

[0463] In some embodiments, when the multimedia playback interface of the above-mentioned application 4 is shared to the central control screen and the rear screen, the desktop service of the central control screen can display the multimedia playback interface of application 4 according to the size of the central control screen, so that the multimedia playback interface of application 4 is adapted to the central control screen; the desktop service of the rear screen can display the multimedia playback interface of application 4 according to the size of the rear screen, so that the multimedia playback interface of application 4 is adapted to the rear screen.

[0464] It should be noted that in the above screen sharing scenario, although Application 4 changes from the application corresponding to Driving Zone 1 to the application corresponding to Driving Zone 0, the storage location of the application installation package of Application 4 can remain unchanged. The application icon of Application 4 can still be displayed on the passenger screen.

[0465] As can be seen from Figure 25 above, during the screen sharing process, the shared application does not need to adapt the multimedia display interface and audio stream according to the screen receiving the screen sharing. The migration of the multimedia playback interface display screen and the migration of the audio sound device can be completed by the driving area management layer and the audio framework layer in the cockpit system. Combined with the embodiment of audio stream transmission in Figure 16 above, it can be seen that since the audio routing strategy of the above-mentioned application 4 is migrated to the audio routing table associated with audio zone 0, the audio track of application 4 can find application 4 in the audio routing table associated with audio zone 0, and then the audio of application 4 is transmitted to the audio channel of the in-car speaker according to the audio routing table associated with audio zone 0. This can achieve seamless switching of the audio of application 4 from earphone 1 to the in-car speaker, maintaining the continuity of audio playback.

[0466] Figures 26 and 27 are schematic diagrams of the screen sharing scenario provided by this application.

[0467] As shown in Figure 26, the co-pilot screen displays the multimedia playback interface of application 4. The driving zone 1 bound to the co-pilot screen contains application 4. That is, application 4 is currently the application corresponding to driving zone 1. Driving zone 1 is associated with headphone audio zone 1. The media session stack corresponding to headphone audio zone 1 includes the media session of application 4. Application 4 can determine that the audio of application 4 needs to be routed to the audio channel of headphone 1 based on the audio routing table associated with headphone audio zone 1. Therefore, application 4 can transmit audio playback data to the audio channel of headphone 1. Headphone 1 can play the audio of application 4. In response to the operation of sharing the multimedia playback interface of application 4 to the central control screen and the rear screen, the cockpit system can migrate the media session, audio routing strategy, and audio focus of application 4. For the specific process, please refer to the introduction of the embodiment of Figure 25 above. The embodiment of this application does not limit the above-mentioned operation of migrating the multimedia playback interface of application 1 to the co-pilot screen.

[0468] As shown in Figure 27, after Application 4's multimedia playback interface is shared from the passenger screen to the center console and rear screens, the passenger screen, center console, and rear screens can all display Application 4's multimedia playback interface. Application 4 is migrated from driver zone 1 to driver zone 0. This means that Application 4 becomes the application corresponding to driver zone 0. Application 4's media session is migrated to the media session stack corresponding to the vehicle audio zone. The media session stack corresponding to headphone zone 1 no longer contains Application 4's media session. Furthermore, because Application 4's audio routing policy has been migrated from the audio routing table associated with headphone zone 1 to the audio routing table associated with the vehicle audio zone, Application 4 can determine from the audio routing table that its audio should be routed to the audio channel of the vehicle's speakers. Therefore, Application 4 can transmit its audio playback data to the audio channel of the vehicle's speakers. The vehicle's speakers can then play Application 4's audio. When Headphone 1 stops receiving Application 4's audio playback data, it can stop playing its audio. Headphone 2 also stops receiving Application 4's audio playback data and therefore does not need to play its audio.

[0469] In some embodiments, after the above-mentioned application 4 completes screen sharing, in response to the operation of closing application 4 on the co-pilot screen, the co-pilot screen can cancel the display of the multimedia playback interface of application 4. The central control screen and the rear screen can still continue to display the multimedia playback interface of application 4, and the speakers in the car can continue to play the audio of application 4. After closing application 4, the co-pilot screen can open other multimedia playback applications and play the corresponding audio through headphones 1. Similarly, after the above-mentioned application 4 completes screen sharing, in response to the operation of closing application 4 on the rear screen, the rear screen can cancel the display of the multimedia playback interface of application 4. The central control screen and the co-pilot screen can still continue to display the multimedia playback interface of application 4, and the speakers in the car can continue to play the audio of application 4. After closing application 4, the rear screen can open other multimedia playback applications and play the corresponding audio through headphones 2.

[0470] In some embodiments, after Application 4 completes screen sharing, in response to an action on the central control screen to close Application 4, the passenger screen can stop displaying the multimedia playback interface of Application 4. The passenger screen and rear screen can still continue to display the multimedia playback interface of Application 4, and the in-vehicle speakers can continue to play the audio of Application 4. Application 4 still holds the audio focus of the entire vehicle audio zone. If another application on the central control screen requests audio focus and preempts the audio focus held by Application 4, the in-vehicle speakers can pause playing the audio of Application 4 and instead play the audio of the application that preempted the audio focus of Application 4.

[0471] In some embodiments, in a screen sharing scenario, if a portion of the screens in a riding area are screens that accept sharing, and another portion of the screens are screens that do not accept sharing, then the screens in this riding area that accept sharing can display the shared multimedia content, and the screens that do not accept sharing do not display the shared multimedia content. Furthermore, in the case where this riding area is a riding area that makes sound after screen sharing, when an application on the screen that does not receive sharing in this riding area seizes the audio focus, the shared multimedia content can be paused, and the sound-emitting device in the associated sound zone in this riding area can play the audio of the application that seizes the audio focus. In the case where this riding area is not a riding area that makes sound after screen sharing, when an application on the screen that does not receive sharing in this riding area applies for audio focus, the sound-emitting device in the associated sound zone in this riding area can play the audio of the application that applies for audio focus, and the audio in the shared multimedia content can continue to be emitted by other riding areas.

[0472] Figures 28A to 28F are other screen sharing scene diagrams provided by this application.

[0473] As shown in Figure 28A, the central control screen is bound to the in-car speakers. The central control screen can display the radio user interface. The in-car speakers can play the radio audio. The passenger screen is bound to earphones 1. The passenger screen can display the video playback interface 2810 and sharing controls 2811 of Video App 1. Sharing controls 2811 can be used to trigger screen sharing. Earphones 1 can play the audio of Video A in Video App 1. The rear screen is bound to earphones 2. The rear screen can display the video playback interface of Video App 2. Earphones 2 can play the audio of Video B in Video App 2.

[0474] As shown in Figure 28B, in response to the operation of the sharing control 2811, the co-pilot screen can display a device option box 2812. The device option box 2812 may include one or more device options for screen sharing. For example, all screen options, central control screen options, co-pilot screen options, and so on. The all screens option can be used to share multimedia content to all screens in the cockpit. The central control screen option can be used to share multimedia content to the central control screen. The rear screen option can be used to share multimedia content to the rear screens. In response to the operation of selecting all screens shown in Figure 28B, the co-pilot screen can share the multimedia content of the video APP1 to all screens in the cockpit, such as the central control screen and the rear screens.

[0475] As shown in Figure 28C, the central control screen can accept screen sharing from the passenger screen and display the video playback interface of Video APP 1. The rear screen can also accept screen sharing from the passenger screen and display the video playback interface of Video APP 1. The passenger screen can still display the video playback interface of Video APP 1. Among them, after the passenger screen is screen shared, the sound device playing the audio of the shared multimedia content can be switched from earphone 1 to the in-car speakers. The in-car speakers can pause the radio audio and continue playing the audio of Video A. Earphone 1 can pause the audio of Video A. Earphone 2 can pause the audio of Video B.

[0476] As shown in Figure 28D , after screen sharing is performed on the passenger screen, the phone app on the central control screen receives an incoming call. The central control screen can cancel the video playback interface of video app 1 and instead display the incoming call prompt interface of the phone app. The phone app can then seize the audio focus of video app 1. The in-car speakers can pause the audio of video A and instead play the incoming call prompt tone of the phone app. Because the audio focus of video app 1 has been seized, the multimedia content in video app 1 can be paused. As shown in Figure 28D , the passenger screen can display video playback interface 2810 of video app 1. Video playback interface 2810 may include play controls 2813. Play controls 2813 may indicate that video A in video playback interface 2810 is currently paused and can be used to trigger playback of video A. Similarly, the video playback interface of video app 1 displayed on the rear screen may also indicate that video A is paused. No audio is playing from earphones 1 or 2.

[0477] As shown in Figure 28E, after the passenger screen shares its screen, it can close Video App 1 and open Music App. The passenger screen can display the Music App and play Music A from the Audio App through Headphones 1, which is bound to the passenger screen. The central control screen and rear screens can continue to display the shared multimedia content, namely the video playback interface of Video App 1. The in-car speakers can continue to play the audio from Video App 1's Video A. No audio is played through Headphones 2.

[0478] As shown in Figure 28F, after the passenger screen shares screen, the rear screen can close Video App 1 and open Music App 1. The rear screen can display Music App 1 and play Music B in Music App 1 through earphones 2 connected to the rear screen. The central control screen and passenger screen can continue to display the shared multimedia content, namely the video playback interface of Video App 1. The in-car speakers can continue to play the audio of Video A in Video App 1. No audio is played through earphones 1.

[0479] In some embodiments, when the first screen (such as the central control screen) is associated with the first sound zone (such as sound zone 0) of the in-car speaker, and the second screen (such as the co-pilot screen) is associated with the second sound zone (such as sound zone 1) of the first sound device (such as earphone 1), the audio played by the first sound device can be shared from the second screen to the first screen along with the multimedia interface corresponding to the audio, and migrated to the in-car speaker for playback. For example, the second interface of the first application is displayed on the second screen. The second interface can be the playback interface of the first audio. The second interface can refer to the multimedia playback interface of application 4 shown in Figure 26 of this application. The first audio can be, for example, the audio of application 4. When an input operation of sharing the second interface from the second screen to the first screen is detected, the cockpit system can display the second interface on the first screen and switch the first audio from the first sound device to the in-car speaker for continued playback. For details, please refer to the embodiment of the multimedia playback interface of application 4 shared from the co-pilot screen to the central control screen shown in Figures 26 and 27.

[0480] In the scenario where the second interface of the first application is migrated from the second screen to the first screen, the cockpit system can migrate the audio focus of the first application in the audio focus stack, migrate the application information of the first application in the audio routing table, and migrate the media session of the first application in the media session stack. For details, please refer to the description of the embodiment of migrating application 4 shown in Figure 25 above.

[0481] In some embodiments, the vehicle further includes a third screen. For example, the third screen may be a rear screen. The third screen is associated with a different sound zone from the first screen, and is also associated with a different sound zone from the second screen. For example, the third screen is associated with the third sound zone of the second sound device. The second sound device may be earphone 2. The third sound zone may be sound zone 2. When an input operation to share the second interface from the second screen to the third screen is detected, the cockpit system may display the second interface on the third screen. For details, please refer to Figures 26 and 27, where the multimedia playback interface of application 4 is shared from the co-pilot screen to the rear screen, and the rear screen displays the multimedia playback interface of application 4.

[0482] The input operation for sharing the second interface from the second screen to the first screen and the input operation for sharing the second interface from the second screen to the third screen can be the same input operation. This input operation can refer to the operation for all screen options shown in Figure 28B. Optionally, the input operation for sharing the second interface from the second screen to the first screen and the input operation for sharing the second interface from the second screen to the third screen can also be two separate operations.

[0483] In some embodiments, after the second screen shares the above-mentioned second interface with the first screen and / or the third screen, when the fourth application on the second screen is detected to request to play the fourth audio, the cockpit system can play the fourth audio through the first sound device. For example, the fourth application can be the music app shown in Figure 28E of this application. The fourth audio can be Music A of the music app. When the fifth application on the third screen is detected to request to play the fifth audio, the cockpit system can play the fifth audio through the second sound device. For example, the fifth application can be Music App 1 shown in Figure 28F of this application. The fifth audio can be Music B of the audio zone App 1. When the sixth application on the first screen is detected to request to play the sixth audio, the cockpit system can play the sixth audio through the in-car speakers and pause the first audio. For example, the sixth application can be the phone app shown in Figure 28D of this application. The sixth audio can be the incoming call prompt tone of the phone app.

[0484] It is understood that the various user interfaces described in the embodiments of this application are merely exemplary interfaces and do not limit the scope of this application. In other embodiments, the user interface may adopt a different interface layout, include more or fewer controls, and add or remove other functional options. As long as they are based on the same inventive concept provided by this application, they are all within the scope of protection of this application.

[0485] It should be noted that, without causing any contradiction or conflict, any feature in any embodiment of the present application, or any part of any feature, can be combined, and the combined technical solution is also within the scope of the embodiments of the present application.

[0486] As described above, the above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the above embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the above embodiments, or make equivalent replacements for some of the technical features therein. However, these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present application.

Claims

1. A cockpit multi-sound zone management method, characterized in that: The method is applied to a vehicle, the vehicle includes an in-vehicle speaker and multiple screens, the multiple screens include a first screen and a second screen, the first screen and the second screen are both associated with a first sound zone corresponding to the in-vehicle speaker, and the method includes: detecting that a first application on the second screen requests to play a first audio, and playing the first audio through the in-vehicle speaker; Detecting that a second application on the first screen requests to play a second audio, playing the second audio through the in-vehicle speaker, and pausing the first audio or reducing the playing volume of the first audio; An input operation of connecting a first sound device to the second screen is detected, the vehicle is connected to the first sound device, and a second sound zone corresponding to the first sound device is created; wherein the sound zone associated with the second screen is changed from the first sound zone to the second sound zone; It is detected again that the first application requests to play the first audio, and the first audio is played through the first sound device.

2. The method according to claim 1, characterized in that A first configuration file is stored in the vehicle, and the first configuration file is used to indicate the correspondence between the multiple screens and the driving area, wherein any one of the multiple screens corresponds to a driving area, the sound zone associated with the screen corresponding to the same driving area remains consistent, and the sound zones associated with the screens corresponding to different driving areas are the same or different.

3. The method according to claim 1 or 2, characterized in that: The vehicle includes a first audio focus stack corresponding to the first audio zone, the first audio focus stack including audio focus information of an application running in the foreground or background on a screen associated with the first audio zone; After detecting the input operation of connecting the first sound-emitting device to the second screen, the method further includes: A second audio focus stack corresponding to the second audio zone is created, and audio focus information of an application running in the foreground or background on the second screen is migrated from the first audio focus stack to the second audio focus stack.

4. The method according to any one of claims 1 to 3, characterized in that The vehicle includes a first audio routing table corresponding to the first audio zone, the first audio routing table includes application information of an application running in the foreground or the background on a screen associated with the first audio zone, and the first audio channel of the in-vehicle speaker is configured in the first audio routing table, for indicating that the audio of the application corresponding to the application information in the first audio routing table is routed to the first audio channel; After detecting the input operation of connecting the first sound-emitting device to the second screen, the method further includes: Creating a second audio routing table corresponding to the second audio zone, and migrating application information of applications running in the foreground or background on the second screen from the first audio routing table to the second audio routing table; A second audio channel of the first sound-emitting device is created, and the second audio channel is configured in the second audio routing table, wherein the second audio channel configured in the second audio routing table is used to indicate that the audio of the application corresponding to the application information in the second audio routing table is routed to the second audio channel.

5. The method according to any one of claims 1 to 4, characterized in that The vehicle includes a first media session stack corresponding to the first audio zone, the first media session stack including a media session of an application running in the foreground or the background on a screen associated with the first audio zone; After detecting the input operation of connecting the first sound-emitting device to the second screen, the method further includes: A second media session stack corresponding to the second audio zone is created, and a media session of an application running in the foreground or the background on the second screen is migrated from the first media session stack to the second media session stack.

6. The method according to claim 5, characterized in that Before detecting an input operation on the second screen connected to the first sound-emitting device, the method further includes: detecting an input operation for viewing audio playback information on the first screen, and displaying a first list on the first screen according to the first media session stack, wherein the first list includes the audio playback information indicated by the first media session stack; An input operation for viewing audio playback information on the second screen is detected, and the first list is displayed on the second screen according to the first media session stack.

7. The method according to claim 6, characterized in that The first list includes audio playback information of the first audio; and the method further includes: When the in-vehicle speaker plays the second audio and the first audio is paused, detecting an input operation on the first screen for the audio playback information of the first audio in the first list, wherein the input operation for the audio playback information of the first audio in the first list is used to play the first audio; The first audio is played through the in-vehicle speaker, and the second audio is paused.

8. The method according to any one of claims 5 to 7, characterized in that: After detecting the input operation of connecting the first sound-emitting device to the second screen, the method further includes: An input operation for viewing audio playback information on the first screen is detected, and a second list is displayed on the first screen according to the first media session stack, wherein the second list includes the audio playback information indicated by the first media session stack, and the second list does not include the audio playback information of the first audio; An input operation for viewing audio playback information on the second screen is detected, and a third list is displayed on the second screen according to the second media session stack, wherein the third list includes the audio playback information indicated by the second media session stack, and the second list includes the audio playback information of the first audio.

9. The method according to any one of claims 1 to 8, characterized in that After the vehicle is connected to the first sound-generating device, the method further includes: An input operation on the second screen for adjusting the volume to a first volume is detected, and the volume of the audio played by the first sound device is adjusted to the first volume.

10. The method according to any one of claims 1 to 9, characterized in that After the vehicle is connected to the first sound-generating device, the method further includes: An input operation on the first screen for adjusting the volume to a second volume is detected, and the volume of the audio played by the in-vehicle speaker is adjusted to the second volume.

11. The method according to any one of claims 1 to 10, characterized in that The first screen displays a first interface of the second application, the first interface being a playback interface of the second audio, and after the vehicle is connected to the first sound device, the method further includes: An input operation of migrating the first interface from the first screen to the second screen is detected, the first interface is displayed on the second screen, the first interface is canceled from the first screen, and the second audio is switched from the in-vehicle speaker to the first sound device for continued playback.

12. The method according to claim 11, characterized in that After switching the second audio from the in-vehicle speaker to the first sound device for continued playback, the method further includes: It is detected that a third application on the first screen requests to play a third audio, and the third audio is played through the in-vehicle speaker.

13. The method according to claim 11 or 12, characterized in that: After switching the second audio from the in-vehicle speaker to the first sound device for continued playback, the method further includes: It is detected that the first application on the second screen requests to play the first audio, plays the first audio through the first sound device, and pauses playing the second audio or reduces the playing volume of the second audio.

14. The method according to any one of claims 11 to 13, characterized in that The vehicle includes a first audio focus stack, a first audio routing table, and a first media session stack corresponding to the first audio zone, and a second audio focus stack, a second audio routing table, and a second media session stack corresponding to the second audio zone, the first audio focus stack including audio focus information of the second application, the first audio routing table including application information of the second application, and the first media session stack including a media session stack of the first application; After detecting the input operation of migrating the first interface from the first screen to the second screen, the method further includes: The audio focus information of the second application is migrated from the first audio focus stack to the second audio focus stack, the application information of the second application is migrated from the first audio routing table to the second audio routing table, and the media session of the second application is migrated from the first media session stack to the second media session stack.

15. The method according to any one of claims 1 to 14, characterized in that A second interface of the first application is displayed on the second screen, where the second interface is a playback interface of the first audio; After the first application is detected again to request to play the first audio, and the first audio is played through the first sound device, the method further includes: An input operation of sharing the second interface from the second screen to the first screen is detected, the second interface is displayed on the first screen, and the first audio is switched from the first sound device to the in-vehicle speaker for continued playback.

16. The method according to claim 15, characterized in that The vehicle further includes a third screen, the third screen is associated with a third sound zone of a second sound device, the second sound device is connected to the vehicle, and the method further includes: An input operation of sharing the second interface from the second screen to the third screen is detected, and the second interface is displayed on the third screen.

17. The method according to claim 15 or 16, characterized in that After switching the first audio from the first sound-emitting device to the in-vehicle speaker for continued playback, the method further includes: It is detected that the fourth application on the second screen requests to play the fourth audio, and the fourth audio is played through the first sound device.

18. The method according to claim 16, characterized in that The method further comprises: It is detected that the fifth application on the third screen requests to play the fifth audio, and the fifth audio is played through the second sound device.

19. The method according to any one of claims 15 to 18, characterized in that After switching the first audio from the first sound-emitting device to the in-vehicle speaker for continued playback, the method further includes: It is detected that the sixth application on the first screen requests to play the sixth audio, the sixth audio is played through the in-vehicle speaker, and the first audio is paused.

20. The method according to any one of claims 15 to 19, characterized in that The vehicle includes a first audio focus stack and a first audio routing table corresponding to the first audio zone, and a second audio focus stack and a second audio routing table corresponding to the second audio zone, wherein the second audio focus stack includes audio focus information of the first application, and the second audio routing table includes application information of the first application; After detecting the input operation of sharing the second interface from the second screen to the first screen, the method further includes: The audio focus information of the first application is migrated from the second audio focus stack to the first audio focus stack, and the application information of the first application is migrated from the second audio routing table to the first audio routing table.

21. The method according to any one of claims 1 to 20, characterized in that After the vehicle is connected to the first sound-generating device, the method further includes: detecting that the first sound device is disconnected, changing the sound zone associated with the second screen from the second sound zone to the first sound zone; When the in-car speaker is playing the second audio, it is detected that the first application on the second screen requests to play the first audio, the first audio is played through the in-car speaker, and the second audio is paused or the volume of the second audio is reduced.

22. The method according to claim 21, characterized in that The vehicle includes a first audio focus stack corresponding to the first sound zone and a second audio focus stack corresponding to the second sound zone. After detecting that the first sound device is disconnected, the method further includes: The audio focus information in the second audio focus stack is migrated to the first audio focus stack, and the second audio focus stack is deleted.

23. The method according to claim 21 or 22, characterized in that The vehicle includes a first audio routing table corresponding to the first audio zone and a second audio routing table corresponding to the second audio zone. After detecting that the first sound device is disconnected, the method further includes: The application information in the second audio routing table is migrated to the first audio routing table, and the second audio routing table is deleted.

24. The method according to any one of claims 21 to 23, characterized in that The vehicle includes a first media session stack corresponding to the first audio zone and a second media session stack corresponding to the second audio zone. After detecting that the first sound device is disconnected, the method further includes: Migrate the media session in the second media session stack to the first media session stack, and delete the second media session stack.

25. The method according to any one of claims 1 to 24, characterized in that The vehicle further includes a fourth screen, the fourth screen being consistent with a sound zone associated with the second screen, and after the first application requesting to play the first audio is detected again and the first audio is played through the first sound device, the method further includes: It is detected that the seventh application on the fourth screen requests to play the seventh audio, the seventh audio is played through the first sound device, and the first audio is paused or the playback volume of the seventh audio is reduced.

26. A vehicle, characterized in that: The vehicle includes multiple screens, in-vehicle speakers, a memory and a processor, wherein the screen is used to display a user interface; the in-vehicle speakers are used to play audio; the processor is used to store a computer program; and the processor is used to call the computer program so that the vehicle executes the method described in any one of claims 1-25.

27. A computer-readable storage medium storing instructions, characterized in that: When the instructions are executed on a vehicle, the vehicle executes the method according to any one of claims 1-25.

28. A computer program product, characterized in that The computer program product comprises computer instructions, and when the computer instructions are run on a vehicle, the vehicle is caused to execute the method according to any one of claims 1 to 25.

Images