Method for playing interaction between multiple screens and related device

Abstract

The application provides a playing interaction method between multiple screens and related equipment, which obtains screen registration information, and then determines whether a current player is a focus player in response to obtaining sound source information synchronized by the current player, determines a target screen displaying the current player according to the screen registration information, and determines a target controller controlling playing content in the target screen according to the screen registration information, and then displays the sound source information in the target controller, so that a user can control the current player to play according to the target controller, realizes interaction between the player and the controller, and in the case that the player and the controller are located in different screens of a cabin media system, the player content can be displayed in the controller bound to the corresponding screen, so as to realize cross-screen interaction and improve the user experience.

Description

Technical Field

[0001] This application relates to the field of automotive technology, specifically to a method and related equipment for playback interaction between multiple screens. Background Technology

[0002] In current smart cockpits, there is typically only one main screen in the front row as the human-computer interaction device. On the main screen, the player can connect to middleware to distribute the playback content to desktop windows, bottom navigation bar controls, etc., so that users can browse the playback content without opening the player and perform playback control operations such as pausing, previous track, or next track.

[0003] However, with the development of smart cockpits, multi-screen cockpit systems have emerged on the market, and interaction on a single screen can no longer meet user needs. Summary of the Invention

[0004] In view of the above-mentioned defects or deficiencies in the prior art, this application aims to provide a multi-screen playback interaction method and related device to solve the problem of low interactivity of a single screen in the prior art.

[0005] This application provides a method for playback interaction between multiple screens, the method including:

[0006] Obtain screen registration information, wherein the screen registration information includes the player displayed on each screen and the controller capable of controlling the content played on each screen;

[0007] In response to obtaining the audio source information synchronized with the current player, it is determined whether the current player is the focused player, wherein the focused player is the player that is playing the most recently on the screen;

[0008] If so, the target screen for displaying the current player is determined based on the screen registration information, and the target controller for controlling the content played on the target screen is determined based on the screen registration information.

[0009] The audio source information is displayed in the target controller so that the user can control the playback of the current player based on the target controller.

[0010] Optionally, obtaining screen registration information includes:

[0011] Obtain the display screen identifiers bound to all players under the operating system, and the control screen identifiers bound to all controllers, and generate the registration information corresponding to the operating system based on the display screen identifiers and the control screen identifiers;

[0012] Receive corresponding registration information from other operating systems besides the aforementioned operating system, and send the registration information corresponding to the aforementioned operating system to the other operating system;

[0013] The screen registration information is determined based on the registration information corresponding to the operating system and the registration information corresponding to other operating systems.

[0014] The method further includes:

[0015] In response to the detection of a focus request from the current player, the target screen for displaying the current player is located based on the screen registration information, and the token information of the current player is written into the focus stack of the target screen;

[0016] Determining whether the current player is the focused player includes:

[0017] Determine whether the token information of the current player is at the top of the focus stack. If so, then determine the current player as the focus player.

[0018] Optionally, displaying the sound source information in the target controller includes:

[0019] The target controller displays the audio source information in association with the identifier of the current player;

[0020] The method further includes:

[0021] In response to detecting a playback control command from the current controller, the player to be controlled is determined based on the identifier carried in the playback control command;

[0022] The playback control command is executed by the player to be controlled.

[0023] Optionally, the method further includes:

[0024] In response to detecting a playback control command from the current controller, the screen to be controlled is determined based on the screen registration information.

[0025] The player located at the top of the focus stack of the screen to be controlled is identified as the player to be controlled;

[0026] The playback control command is executed by the player to be controlled.

[0027] Optionally, the method further includes:

[0028] In response to detecting that a headphone device is connected to the current screen, the associated screen of the current screen is determined, and the focused player of the associated screen is determined;

[0029] From all the audio source information displayed by the controller in the current screen, remove the audio source information of players other than the focused player of the associated screen.

[0030] Optionally, after writing the token information of the current player into the focus stack of the target screen, the method further includes:

[0031] Determine whether an earphone device is connected to the target screen;

[0032] If not, the corresponding audio will be played through the in-vehicle audio device controlled by the current player.

[0033] This application embodiment also provides a cockpit media system, the cockpit media system including at least one operating system, the operating system including a media center and at least one screen, the screen having a display player and / or controller, and the media centers being able to communicate across systems;

[0034] The player is used to play and control the audio source;

[0035] The media center is used to obtain screen registration information; in response to obtaining the audio source information synchronized with the current player, it determines whether the current player is the focus player. If so, it determines the target screen to display the current player based on the screen registration information, and determines the target controller to control the playback content in the target screen based on the screen registration information, and sends the audio source information to the target controller.

[0036] The controller is used to display the received audio source information and to control the playback of the current player;

[0037] The screen registration information includes the players displayed on each screen and the controllers that can control the content played on each screen; the focus player is the most recently played player on the screen.

[0038] This application also provides a vehicle, which includes the cockpit media system provided in any embodiment of this application.

[0039] This application embodiment also provides an electronic device, the electronic device comprising:

[0040] Processor and memory;

[0041] The processor executes the steps of the multi-screen playback interaction method provided in any embodiment of this application by calling the program or instructions stored in the memory.

[0042] This application also provides a computer-readable storage medium storing a program or instructions that cause a computer to perform the steps of the multi-screen playback interaction method provided in any embodiment of this application.

[0043] In summary, this application proposes a multi-screen playback interaction method. This method obtains screen registration information, and then, in response to obtaining the audio source information synchronized with the current player, determines whether the current player is the focused player. If so, it determines the target screen for displaying the current player based on the screen registration information, and also determines the target controller for controlling the playback content on the target screen based on the screen registration information. The audio source information is then displayed on the target controller, allowing the user to control the playback of the current player using the target controller. This achieves interaction between the player and the controller. For multi-screen cockpit media systems, when the player and controller are located on different screens, the player content can be directionally displayed on the controller bound to the corresponding screen. This allows the user to control playback of a player not on this screen through the controller, achieving cross-screen interaction. Furthermore, this method enables one-to-one or one-to-many audio source information display and playback control between the controller and the player, improving the user experience. Attached Figure Description

[0044] To more clearly illustrate the technical solutions in the specific embodiments of this application or the prior art, the drawings used in the description of the specific embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of this application. For those skilled in the art, other drawings can be obtained from these drawings without creative effort.

[0045] Figure 1 This is a flowchart illustrating a playback interaction method between multiple screens provided in an embodiment of this application;

[0046] Figure 2 This is a schematic diagram of the binding of various screens in a cockpit media system provided in an embodiment of this application;

[0047] Figure 3 This is a flowchart illustrating a synchronized display and playback control method provided in an embodiment of this application;

[0048] Figure 4 This is a schematic diagram of the structure of a cockpit media system provided in an embodiment of this application;

[0049] Figure 5 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0050] The present application will now be described in further detail with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and not intended to limit it. Furthermore, it should be noted that, for ease of description, only the parts relevant to the invention are shown in the accompanying drawings.

[0051] It should be noted that, unless otherwise specified, the embodiments and features described in this application can be combined with each other. This application will now be described in detail with reference to the accompanying drawings and embodiments.

[0052] As mentioned in the background section, in order to address the problems in the prior art, this application proposes a multi-screen playback interaction method that can be executed by the operating system in the cockpit media system. Figure 1 This is a flowchart illustrating a playback interaction method between multiple screens provided in an embodiment of this application. See also... Figure 1 The specific methods for playback interaction between multiple screens include:

[0053] S110, Obtain screen registration information.

[0054] The screen registration information includes the player displayed on each screen and the controller that can control the content played on each screen. The player can be software used to play and control audio playback, including but not limited to music players and video players such as QQ Music and Kugou Music. The controller can be a control used to control audio playback; for example, the controller can be located at the bottom, top, or side edge of the screen.

[0055] Specifically, the screen registration information describes all screen-bound players and / or controllers in the entire cockpit media system. A screen-bound player refers to the player displayed on the screen; a player can be bound to only one screen, meaning it is displayed on only one screen. A screen-bound controller refers to a controller that can control the content played on the screen; a controller can be bound to one or more screens, meaning it can control the content played on one or more screens.

[0056] In this embodiment, all players and controllers in the cockpit media system can access the media center framework in the operating system and register with the media center and bind screens during application initialization. A player can bind to a screen ID representing its assigned screen, and a controller can bind to one or more screen IDs, representing the screens from which it can control the playback content.

[0057] Considering that the cockpit media system may have multiple operating systems, the media centers of each operating system can communicate with each other, enabling cross-platform communication capabilities. The media center can send the registration and binding information of the player and controller on the current end to the other end to maintain information synchronization, allowing each operating system to generate screen registration information containing all screen-related information.

[0058] In one specific implementation, obtaining screen registration information includes the following steps:

[0059] Step 11: Obtain the display screen identifiers bound to all players and the control screen identifiers bound to all controllers under the operating system, and generate the registration information corresponding to the operating system based on the display screen identifiers and control screen identifiers;

[0060] Step 12: Receive the corresponding registration information sent by other operating systems besides the operating system, and send the registration information corresponding to the operating system to the other operating systems;

[0061] Step 13: Determine the screen registration information based on the registration information corresponding to the operating system and the registration information corresponding to other operating systems.

[0062] In step 11, the media center in the operating system can receive the display screen identifiers bound to all players under the operating system, as well as the control screen identifiers bound to all controllers.

[0063] Specifically, the media center can use the screen identifier as the key and the registration information of the player and controller as the value to declare key-value pairs of player registration information and key-value pairs of controller registration information, thus forming the registration information corresponding to the operating system.

[0064] Furthermore, in step 12, the media center can receive corresponding registration information sent by other operating systems besides the operating system, and send the registration information obtained in step 11 to other operating systems to maintain information synchronization between the various operating systems.

[0065] Furthermore, in step 13, the media center in the operating system can generate screen registration information containing all screen-related information based on the registration information corresponding to the operating system and the registration information corresponding to other operating systems, namely the player displayed on each screen and the controller that can control the playback content on each screen.

[0066] Through steps 11-13 above, the relevant binding information of all screens in the entire cockpit media system is determined. In the case of multiple operating systems and multiple screens, complete screen registration information can be obtained, which facilitates subsequent cross-system and cross-screen interaction.

[0067] For example, Figure 2 This is a schematic diagram illustrating the binding of various screens in a cockpit media system provided in an embodiment of this application. For example... Figure 2 As shown, taking the entire cockpit media system, which includes five screens, as an example, the central control screen, the rear left direct-view screen (located on the front seat back of the rear left side), the rear left armrest screen (located on the rear left armrest), the rear right direct-view screen (located on the front seat back of the rear right side), and the rear right armrest screen (located on the rear right armrest).

[0068] The central control screen, the rear left direct-view screen, and the rear left armrest screen all belong to the same operating system and can be regarded as the Slave end. The rear right direct-view screen and the rear right armrest screen all belong to the same operating system and can be regarded as the Master end.

[0069] from Figure 2 As can be seen, the display screens bound to players 1 through 4 are labeled as the central control screen, and the control screens bound to controllers 1 and 2 are labeled as the central control screen; the display screens bound to players 5 and 6 are labeled as the rear left direct-view screen, and the control screen bound to controller 3 is labeled as the rear left direct-view screen; the control screens bound to controller 4 are labeled as the central control screen, the rear left direct-view screen, and the rear left armrest screen. The display screens bound to players 7 and 8 are labeled as the rear right direct-view screen, and the control screen bound to controller 4 is labeled as the rear right direct-view screen; the control screens bound to controller 5 are labeled as the central control screen, the rear left direct-view screen, and the rear right direct-view screen.

[0070] S120. In response to obtaining the audio source information synchronized with the current player, determine whether the current player is the focus player, where the focus player is the player that is playing the latest one on the screen.

[0071] In this embodiment, each player can call an interface to synchronize audio source information with the operating system's media center. The audio source information can describe the content being played, such as the name of the content and its author.

[0072] Specifically, when the operating system's media center receives audio source information, it first determines whether the current player that sent the audio source information is the focused player, i.e., whether it is the most recently playing player on the screen. For example, a focus stack can be used to record players that have requested focus, and then the focus stack can be used to determine whether the current player is the focused player.

[0073] In one specific implementation, the method provided in this application further includes:

[0074] In response to the detection of a focus request from the current player, the target screen for displaying the current player is located based on the screen registration information, and the token information of the current player is written into the focus stack of the target screen;

[0075] Determining whether the current player is the focused player includes:

[0076] Determine if the token information of the current player is at the top of the focus stack. If so, then designate the current player as the focus player.

[0077] The focus request can be a request to the media center to request playback focus (which can be understood as playback permission). For example, the player can send a focus request to the media center when it detects that the playback content needs to be changed, such as automatically switching to the next track, the user clicking to switch to the next track on the player, or the user clicking to switch to the previous track on the controller.

[0078] Specifically, if the media center receives a focus request, it can allocate focus to the current player, locate the target screen for displaying the current player using the screen registration information, and then write the current player's token information to the top of the target screen's focus stack. The token information can be an identifier used by the player for communication authentication or authorization, such as a token.

[0079] Each screen corresponds to a focus stack, which records the token information of players that have requested focus. The player at the top of the focus stack is the player that most recently requested focus, i.e., the focus player, and can respond to the controller's playback control commands first.

[0080] Furthermore, after receiving the synchronized audio source information, the media center can determine whether the current player that sent the audio source information is at the top of the focus stack. If so, the current player can be identified as the focus player.

[0081] The above implementation method enables the focus player to be determined based on the focus stack, ensuring the accuracy of the determination. Furthermore, by recording each player requesting focus through the focus stack, the player at the top of the stack can respond to the controller's playback control commands first, allowing the user to control the latest playing player through the controller and avoiding control errors.

[0082] S130. If so, then determine the target screen for displaying the current player based on the screen registration information, and determine the target controller for controlling the content played on the target screen based on the screen registration information.

[0083] Specifically, if the media center determines that the received audio source information is sent by the focused player, it can use the screen registration information to find the target screen that displays the current player, that is, the screen where the current player is located.

[0084] After locating the target screen, the next step is to locate the target controller that controls the content played on that target screen based on the screen registration information. It should be noted that there can be one or more target controllers controlling the target screen, and these controllers can be located either within the target screen or on other screens.

[0085] For example, such as Figure 2 As shown, assuming Figure 2 After player 1 synchronizes the audio source information to the media center, the media center determines that it is the player at the top of the stack. At this time, it can query that the screen where player 1 is located is the central control screen, and then query the controllers that can control the central control screen, including: controller 1, controller 2, controller 4, and controller 5. Among them, controller 4 and controller 5 are located on other screens. Subsequently, the media center can synchronize the audio source information to each of the queried controllers for display. Users can use the controllers to control the playback content corresponding to the displayed audio source information.

[0086] S140. Display the audio source information in the target controller so that the user can control the playback of the current player based on the target controller.

[0087] Specifically, after the media center locates the target controller based on the screen registration information, it can synchronize the audio source information to the target controller. The target controller can then display the audio source information. After displaying the audio source information, the user can control the playback of the current player through the target controller, that is, control the playback content of the current player.

[0088] It should be noted that if the target controller is located on another operating system, the media center can synchronize the audio source information to the media center under the operating system of the target controller, and then the media center under the operating system of the target controller can synchronize the audio source information to the target controller.

[0089] In this embodiment of the application, after the target controller receives and displays the audio source information, it can control the current player, such as controlling the current player to pause playback, switch to the next song, switch to the previous song, etc.

[0090] In this embodiment of the application, considering that a controller can control multiple screens, there may be a situation where multiple audio source information is displayed in a controller at the same time. However, if the screen where the controller is located is connected to a headphone device, then the number of players that the controller can control is limited. The audio source information displayed in the controller can be reduced to display only the players that can be controlled in the controller.

[0091] In one example, the method provided in this application embodiment further includes the following steps:

[0092] Step 21: In response to detecting that a headphone device is connected to the current screen, determine the associated screen of the current screen and determine the focused player of the associated screen;

[0093] Step 22: Remove the audio source information of other players, except for the focused player on the associated screen, from all the audio source information displayed by the controller on the current screen.

[0094] In step 21, if a headphone device is detected connected to the current screen, the screen associated with the current screen can be determined first. The associated screen is the screen that the controller in the current screen can still control when a headphone device is connected.

[0095] For example, if the current screen is the rear left direct-view screen, the associated screen can be the rear left armrest screen; if the current screen is the rear right direct-view screen, the associated screen can be the rear right armrest screen; if the current screen is the central control screen, the associated screen can be the central control screen.

[0096] Furthermore, after identifying the associated screens, the focus player of the associated screen can be determined by combining the focus stack of the associated screens and the token information at the top of the stack. Then, from all the audio source information displayed by the controller in the current screen, the audio source information of the focus player is retained, and other audio source information is removed.

[0097] By using steps 21-22 above, when a headphone device is connected to the screen, the screen's controller can still display the focused player that can be controlled even after headphones are connected. This prevents the user from controlling other unrelated players on the screen using the on-screen controller, further improving the user experience. For example, after a user plugs headphones into the rear right-side screen, the controller on the rear right-side screen only displays the audio source information of the player on the rear right armrest screen.

[0098] In this embodiment, the controller controls the playback of the player corresponding to the displayed audio source information, which can be achieved by relying on a media center. For example, the controller sends playback control commands to the media center, and the media center then synchronizes the playback control commands to the player.

[0099] In one specific implementation, displaying sound source information in the target controller includes:

[0100] In the target controller, the audio source information is associated with the identifier of the current player;

[0101] The method provided in this application embodiment also includes:

[0102] In response to the detection of a playback control command from the current controller, the player to be controlled is determined based on the identifier carried in the playback control command; the playback control command is then executed through the player to be controlled.

[0103] Specifically, during the process of synchronizing the audio source information to the target controller for display, the identifier of the current player can also be synchronized at the same time, so that the target controller can associate the audio source information with the identifier of the current player, making it easy for users to know from the target controller which player the audio source comes from.

[0104] Furthermore, considering that one controller can control multiple screens, the audio source information at the top of the stack for each screen can be synchronized to the controller for display. As a result, there may be situations where multiple audio source information is displayed in one controller at the same time. In order to facilitate user control of playback, the corresponding player's icon is displayed at the same time as the audio source information, so that users can select the audio source information on the controller and achieve the purpose of accurate playback control.

[0105] Specifically, in response to detecting a user's audio source selection and control operations, the controller can generate a playback control command containing the player's identifier and the control operation, and send it to the media center. Furthermore, after receiving the playback control command, the media center can identify the player to be controlled by the player's identifier carried in the playback control command, and then synchronize the playback control command to the player to be controlled, so that the player to be controlled can execute the control operation in the playback control command.

[0106] It should be noted that if the player to be controlled is located on another operating system, the media center can first send the playback control command to the media center under the operating system of the player to be controlled, and then the media center under the operating system of that player will synchronize the playback control command to the player to be controlled.

[0107] Through the above implementation method, the player to be controlled can be determined according to the identifier carried in the playback control command, and then the playback control command can be sent to the player to be controlled for execution, which can improve the efficiency of playback control.

[0108] In another specific implementation, the method provided in this application further includes the following steps:

[0109] Step 31: In response to detecting a playback control command from the current controller, determine the screen to be controlled corresponding to the playback control command based on the screen registration information;

[0110] Step 32: Determine the player at the top of the focus stack of the screen to be controlled;

[0111] Step 33: Execute playback control commands through the player to be controlled.

[0112] The controller can respond to the detection of playback control voice initiated by the user, recognize the playback control voice, generate playback control instructions containing control operations, such as next track, previous track, etc., and then send the playback control instructions to the media center.

[0113] Specifically, in step 31, after the media center receives the playback control command, it can first find the screen controlled by the current player that sent the playback control command through the screen registration information, and use it as the screen to be controlled.

[0114] Furthermore, in step 32, the media center can query the token information located at the top of the focus stack of the screen to be controlled, and use the player corresponding to the token information as the player to be controlled.

[0115] Furthermore, in step 33, the media center can synchronize playback control commands to the player to be controlled, so that the player to be controlled can execute the control operations in the playback control commands. If the player to be controlled is located under another operating system, the media center can first send the playback control commands to the media center under the operating system of the player to be controlled, and then the media center under its operating system will synchronize the playback control commands to the player to be controlled.

[0116] Through the above implementation method, the screen corresponding to the playback control command can be queried first according to the screen registration information, and then the focus stack of that screen can be queried. The playback control command can be synchronized to the player at the top of the stack, which can improve the accuracy of playback control and ensure that the controller's playback control is always aimed at the player at the top of the stack, that is, at the player that is playing the latest, thus avoiding control errors.

[0117] For example, Figure 3 This is a flowchart of a synchronous display and playback control provided in an embodiment of this application, such as... Figure 3As shown, firstly, the player can register with the media center by sending its display screen identifier (displayID), and the controller can register with the media center by sending its control screen identifier (displayID). Furthermore, if the player needs to update playback information, it can request focus and thus synchronize audio source information. After detecting that it is the player at the top of the stack, the media center can distribute playback information to the controller according to its displayID, and the controller can display the playback information. Further, if the controller needs to perform playback control, it can send control commands to the media center. The media center can then issue control commands to the player according to its displayID, allowing the player to update its playback status (pause, play) or update the playback content.

[0118] In this embodiment of the application, considering that the vehicle's cockpit media system can have multiple screens and multiple operating systems, but usually there is only one in-vehicle audio device in the vehicle, in order to avoid sound confusion caused by multiple players playing content through the in-vehicle audio device at the same time, the player can also be used to control the content played by the in-vehicle audio device when the player requests focus.

[0119] In one example, after writing the current player's token information into the focus stack of the target screen, the process also includes:

[0120] Determine if a headphone device is connected to the target screen; if not, control the in-vehicle audio device to play the corresponding audio through the current player.

[0121] Specifically, after receiving a focus request, retrieving the corresponding target screen, and writing the current player's token information into the target screen's focus stack (i.e., after focus allocation is completed), it can first determine whether the target screen is connected to a headphone device. If so, the current player can control the headphone device to play the corresponding audio.

[0122] If no headphones are connected, it means that the only device playing audio in the vehicle is the in-vehicle audio system. In this case, the current player can be controlled to output audio data to the in-vehicle audio system, and the in-vehicle audio system will then play the audio data.

[0123] For example, when player 1 on the central control screen needs to change the playback content, it can send a focus request, which can then apply for focus and record it in the focus stack. Furthermore, it can control other players to pause playback and control player 1 to play the corresponding audio to the vehicle audio device.

[0124] The above example demonstrates how, when the current player requests focus, it can first determine whether the target screen is connected to a headphone device. If not, the current player can control the in-vehicle audio device to play the corresponding audio, avoiding sound chaos caused by multiple players simultaneously controlling the in-vehicle audio device and further improving the user experience.

[0125] The multi-screen playback interaction method provided in this application obtains screen registration information, and then, in response to obtaining the audio source information synchronized with the current player, determines whether the current player is the focused player. If so, it determines the target screen for displaying the current player based on the screen registration information, and determines the target controller for controlling the playback content on the target screen based on the screen registration information. The audio source information is then displayed on the target controller, allowing the user to control the playback of the current player according to the target controller. This achieves interaction between the player and the controller. For multi-screen cockpit media systems, when the player and controller are on different screens, the player content can be directionally displayed on the controller bound to the corresponding screen. Thus, the user can control the playback of a player not on this screen through the controller, achieving cross-screen interaction. Furthermore, this method can perform one-to-one or one-to-many audio source information display and playback control based on the screen, improving the user experience.

[0126] For the same purpose, this application also provides a cockpit media system, which includes at least one operating system, the operating system including a media center and at least one screen, the screen having a display player and / or controller, and the media centers being able to communicate across systems.

[0127] The player is used to play and control the audio source;

[0128] The media center is used to obtain screen registration information; in response to obtaining the audio source information synchronized with the current player, it determines whether the current player is the focus player. If so, it determines the target screen to display the current player based on the screen registration information, and determines the target controller to control the playback content in the target screen based on the screen registration information, and sends the audio source information to the target controller.

[0129] The controller is used to display the received audio source information and to control the playback of the current player;

[0130] The screen registration information includes the players displayed on each screen and the controllers that can control the content played on each screen; the focus player is the most recently played player on the screen.

[0131] In some implementations, the media center is further used for:

[0132] Obtain the display screen identifiers bound to all players under the operating system, and the control screen identifiers bound to all controllers, and generate the registration information corresponding to the operating system based on the display screen identifiers and the control screen identifiers;

[0133] Receive corresponding registration information from other operating systems besides the aforementioned operating system, and send the registration information corresponding to the aforementioned operating system to the other operating system;

[0134] The screen registration information is determined based on the registration information corresponding to the operating system and the registration information corresponding to other operating systems.

[0135] In some implementations, the media center is further used for:

[0136] In response to the detection of a focus request from the current player, the target screen for displaying the current player is located based on the screen registration information, and the token information of the current player is written into the focus stack of the target screen;

[0137] Additionally, it determines whether the token information of the current player is located at the top of the focus stack; if so, the current player is identified as the focus player.

[0138] In some implementations, the media center is further used for:

[0139] The target controller displays the audio source information in association with the identifier of the current player;

[0140] In addition, in response to detecting a playback control command from the current controller, the player to be controlled is determined based on the identifier carried in the playback control command; and the playback control command is executed through the player to be controlled.

[0141] In some implementations, the media center is further used for:

[0142] In response to detecting a playback control command from the current controller, the screen to be controlled is determined based on the screen registration information.

[0143] The player located at the top of the focus stack of the screen to be controlled is identified as the player to be controlled;

[0144] The playback control command is executed by the player to be controlled.

[0145] In some embodiments, the operating system is further configured to:

[0146] In response to detecting that a headphone device is connected to the current screen, the associated screen of the current screen is determined, and the focused player of the associated screen is determined;

[0147] From all the audio source information displayed by the controller in the current screen, remove the audio source information of players other than the focused player of the associated screen.

[0148] In some embodiments, the operating system is further configured to:

[0149] Determine whether an earphone device is connected to the target screen;

[0150] If not, the corresponding audio will be played through the in-vehicle audio device controlled by the current player.

[0151] For example, Figure 4 This is a structural schematic diagram of a cockpit media system provided in an embodiment of this application. Figure 4 As shown, taking the entire cockpit media system, which includes five screens, as an example, the central control screen, the rear left direct-view screen (located on the front seat back of the rear left side), the rear left armrest screen (located on the rear left armrest), the rear right direct-view screen (located on the front seat back of the rear right side), and the rear right armrest screen (located on the rear right armrest).

[0152] The rear right-side screen and the rear right-side armrest screen belong to Operating System 1, which can be considered the Master terminal. The central control screen, the rear left-side screen, and the rear left-side armrest screen belong to Operating System 2, which can be considered the Slave terminal. The Slave terminal and the Master terminal each have their own media center, and the two media centers can communicate with each other.

[0153] For example, separate installation packages can be prepared for the Slave and Master ends to enable interaction and communication between them. This mainly includes: accessing EASCoreService, which encapsulates the relevant interfaces of DFS to help the media center achieve cross-platform communication; the media center performs channelization for the Master and Slave ends respectively, and differentiates the access interfaces to adapt to the different environments of the two ends; the media center synchronizes information between the Master and Slave ends, including registration information, playback content information, and control command information.

[0154] The cockpit media system provided in this application embodiment can execute the steps in the multi-screen playback interaction method provided in this application method embodiment, and has the execution steps and beneficial effects, which will not be repeated here.

[0155] Figure 5 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. For example... Figure 5As shown, the electronic device 400 includes one or more processors 401 and memory 402.

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

[0157] The memory 402 may include one or more computer program products, which may include various forms of computer-readable storage media, such as volatile memory and / or non-volatile memory. The volatile memory may include, for example, random access memory (RAM) and / or cache memory. The non-volatile memory may include, for example, read-only memory (ROM), hard disk, flash memory, etc. One or more computer program instructions may be stored on the computer-readable storage medium, and the processor 401 may execute the program instructions to implement the multi-screen playback interaction method and / or other desired functions described above in any embodiment of this application. Various contents such as initial external parameters and thresholds may also be stored in the computer-readable storage medium.

[0158] In one example, the electronic device 400 may further include an input device 403 and an output device 404, these components being interconnected via a bus system and / or other forms of connection mechanisms (not shown). The input device 403 may include, for example, a keyboard, a mouse, etc. The output device 404 may output various information to the outside, including warning messages, braking force, etc. The output device 404 may include, for example, a display, a speaker, a printer, and a communication network and its connected remote output devices, etc.

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

[0160] In addition to the methods and devices described above, embodiments of this application may also be computer program products, which include computer program instructions that, when executed by a processor, cause the processor to perform the steps of the multi-screen playback interaction method provided in any embodiment of this application.

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

[0162] Furthermore, embodiments of this application may also be computer-readable storage media storing computer program instructions thereon, which, when executed by a processor, cause the processor to perform the steps of the multi-screen playback interaction method provided in any embodiment of this application.

[0163] The computer-readable storage medium may be any combination of one or more readable media. A readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may, for example, include, but is not limited to, electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatuses, or devices, or any combination thereof. More specific examples of readable storage media (a non-exhaustive list) include: electrical connections having one or more wires, portable disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0164] It should be noted that the terminology used in this application is for the purpose of describing specific embodiments only and is not intended to limit the scope of this application. As shown in the specification and claims of this application, unless the context clearly indicates otherwise, words such as "a," "an," "an," and / or "the" do not specifically refer to the singular and may also include the plural. The terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, or apparatus. Without further limitations, an element defined by the phrase "comprising an..." does not exclude the presence of other identical elements in the process, method, or apparatus that includes said element.

[0165] It should also be noted that the terms "center," "upper," "lower," "left," "right," "vertical," "horizontal," "inner," and "outer," etc., indicate the orientation or positional relationship based on the orientation or positional relationship shown in the accompanying drawings, and are only for the convenience of describing this application and simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, or be constructed and operated in a specific orientation, and therefore should not be construed as a limitation on this application. Unless otherwise expressly specified and limited, the terms "installed," "connected," "linked," etc., should be interpreted broadly. For example, they can refer to a fixed connection, a detachable connection, or an integral connection; they can refer to a mechanical connection or an electrical connection; they can refer to a direct connection or an indirect connection through an intermediate medium; they can refer to the internal communication between two elements. For those skilled in the art, the specific meaning of the above terms in this application can be understood according to the specific circumstances.

[0166] This document uses specific examples to illustrate the principles and implementation methods of this application. The descriptions of the above embodiments are only for the purpose of helping to understand the methods and core ideas of this application. The above descriptions are only preferred embodiments of this application. It should be noted that due to the limitations of written expression, while there are objectively infinite specific structures, those skilled in the art can make several improvements, modifications, or changes without departing from the principles of this application, and can also combine the above technical features in an appropriate manner. These improvements, modifications, changes, or combinations, or the direct application of the inventive concept and technical solution to other situations without modification, should all be considered within the scope of protection of this application.

Claims

1. A method for play interaction between multiple screens, the method comprising: The method comprises: obtaining screen registration information, wherein the screen registration information comprises a player displayed in each screen and a controller capable of controlling the playing content in each screen; in response to obtaining the sound source information of the current player synchronization, determining whether the current player is a focus player, wherein the focus player is the latest player played in the screen; if yes, determining a target screen displaying the current player based on the screen registration information, and determining a target controller controlling the playing content in the target screen based on the screen registration information; displaying the sound source information in the target controller to facilitate the user to control the playing of the current player based on the target controller.

2. The method of claim 1, wherein, The method further comprises: obtaining the display screen identifier bound to all players under the operating system and the control screen identifier bound to all controllers, and generating the registration information corresponding to the operating system based on the display screen identifier and the control screen identifier; receiving the corresponding registration information sent by other operating systems except the operating system, and sending the registration information corresponding to the operating system to the other operating systems; determining the screen registration information based on the registration information corresponding to the operating system and the registration information corresponding to the other operating systems.

3. The method of claim 1, wherein, The method further comprises: in response to detecting the focus application request of the current player, finding the target screen displaying the current player based on the screen registration information, and writing the token information of the current player into the focus stack of the target screen; determining whether the current player is a focus player comprises: judging whether the token information of the current player is located at the top of the focus stack, and if yes, determining the current player as a focus player.

4. The method of claim 1, wherein, Displaying the sound source information in the target controller comprises: in the target controller, associating the display of the sound source information with the identifier of the current player. The method further comprises: in response to detecting the playing control instruction of the current controller, determining the to-be-controlled player based on the identifier carried in the playing control instruction; executing the playing control instruction through the to-be-controlled player.

5. The method of claim 3, wherein, The method further comprises: in response to detecting the playing control instruction of the current controller, determining the to-be-controlled screen corresponding to the playing control instruction based on the screen registration information; determining the player located at the top of the focus stack of the to-be-controlled screen as the to-be-controlled player; executing the playing control instruction through the to-be-controlled player.

6. The method of claim 1, wherein, The method further comprises: in response to detecting that the current screen accesses the earphone device, determining the associated screen of the current screen and the focus player of the associated screen; from all the sound source information displayed by the controllers in the current screen, eliminating the sound source information of the players other than the focus player of the associated screen.

7. The method of claim 3, wherein, After writing the token information of the current player into the focus stack of the target screen, the method further comprises: judging whether the earphone device accesses the target screen; if no, controlling the vehicle-mounted audio device to play the corresponding audio through the current player.

8. A cockpit media system characterized by, The cockpit media system comprises at least one operating system, the operating system comprising a media center and at least one screen, the screen having a display player and / or controller, and the media centers being capable of cross-system communication, wherein; the player is configured to play and control the audio source; the media center is configured to acquire screen registration information; in response to acquiring the audio source information of the current player synchronization, determining whether the current player is a focus player, if yes, determining a target screen displaying the current player based on the screen registration information, and determining a target controller controlling the playing content in the target screen based on the screen registration information, and sending the audio source information to the target controller; the controller is configured to display the received audio source information and control the playing of the current player; wherein the screen registration information comprises the player displayed in each screen and the controller capable of controlling the playing content in each screen; and the focus player is the latest player playing in the screen.

9. A vehicle characterized by comprising: The vehicle comprises the cockpit media system of claim 8.

10. A computer-readable storage medium, characterized in that, The computer readable storage medium stores programs or instructions, which make the computer execute the steps of the playing interaction method between multiple screens according to any one of claims 1 to 7.

Images