Screen projection method and device for cockpit ktv multi-screen interaction

Abstract

The application relates to a cockpit KTV multi-screen interaction screen projection method and device, wherein the method comprises the following steps: starting a screen projection mode of a target vehicle to newly create and display an activity interface in the rear row of the target vehicle; every preset time, a current video frame picture bitmap is acquired from a KTV main interface playing TextureView of a front row main driver screen of the target vehicle, a bitmap object corresponding to the current video frame picture bitmap is drawn into a canvas of a playing control of the rear row interface, and the bitmap object is drawn into a TextureView of the rear row for rendering to obtain corresponding rendering data; and based on the rendering data and the activity interface, the rear row interface is synchronized with the KTV main interface of the front row main driver screen for playing a video source. According to the application, only video content is projected onto other screens, so that a menu interface can be specially customized and differentiated according to the position of the screen.

Description

Technical Field

[0001] This application relates to the field of smart cockpit technology, and in particular to a projection method and device for multi-screen interaction in a cockpit KTV. Background Technology

[0002] Currently, most screen mirroring solutions used for both front and rear rows rely on projection technology, such as Android's Mirror framework, which mirrors the screen one-to-one. However, this also projects all elements from the front screen, such as the menu interface, significantly reducing the user experience for rear passengers. Since front passengers' menu operations block the view of rear passengers who don't need to interact with the screen, and rear passengers lack independent menu access, they are entirely dependent on front-seat controls. For example, during karaoke or entertainment, rear passengers cannot independently select songs, change tracks, or perform other actions. Conversely, when rear passengers operate the projected screen, the front screen is also affected, resulting in very low interactivity and only a synchronized display.

[0003] In summary, the existing in-vehicle KTV multi-screen interaction technology can only project screens and cannot perform independent menu operations, which urgently needs to be addressed. Summary of the Invention

[0004] This application provides a screen projection method and device for multi-screen interaction in a cabin KTV, to solve the problems in the prior art where multi-screen interaction in in-vehicle KTV can only project screens and cannot perform independent menu operations.

[0005] The first aspect of this application provides a screen projection method for multi-screen interaction in a cockpit KTV, comprising the following steps: activating the screen projection mode of the target vehicle to create and display an activity interface in the rear row of the target vehicle; at preset intervals, obtaining a bitmap of the current video frame from the playback TextureView of the KTV main interface on the front driver's screen of the target vehicle, drawing the bitmap object corresponding to the current video frame bitmap onto the canvas of the playback control on the rear interface, and rendering the canvas onto the TextureView of the rear interface to obtain corresponding rendering data; based on the rendering data and the activity interface, enabling the rear interface and the KTV main interface on the front driver's screen to play video sources synchronously.

[0006] Optionally, in one embodiment of this application, the step of synchronizing the video source playback of the rear-seat interface with the KTV main interface on the front driver's screen based on the rendering data and the activity interface includes: overlaying the activity interface and the rendering data to construct an independent rear-seat interface so that the video in the rear-seat interface is synchronized with the video in the KTV main interface on the front driver's screen.

[0007] Optionally, in one embodiment of this application, before obtaining the current video frame bitmap from the playback TextureView of the KTV main interface on the front driver's side screen of the target vehicle at preset intervals, the method further includes: obtaining a SurfaceTexture object from the TextureView of the rear interface based on a preset getSurfaceTexture() calling strategy; locking the canvas of the TextureView using a preset lockCanvas() strategy and the SurfaceTexture object, and obtaining the canvas object; determining the width and height of the TextureView, and constructing a blank bitmap object based on the width and height.

[0008] Optionally, in one embodiment of this application, the step of obtaining the current video frame bitmap from the playback TextureView of the KTV main interface on the front driver's screen of the target vehicle at preset time intervals, drawing the bitmap object corresponding to the current video frame bitmap onto the canvas of the playback control on the rear interface, and drawing the canvas onto the TextureView in the rear for rendering to obtain the corresponding rendering data includes: using the canvas object to draw the content of the playback TextureView of the KTV main interface on the front driver's screen onto the bitmap object; and unlocking the canvas of the TextureView based on a preset unlockCanvasAndPost(canvas) strategy to render the TextureView in the TextureView in the rear to obtain the rendering data.

[0009] A second aspect of this application provides a screen projection device for multi-screen interaction in a cockpit KTV, comprising: a startup module for starting the screen projection mode of a target vehicle to create and display an activity interface in the rear row of the target vehicle; a screen projection module for obtaining a bitmap of the current video frame from the playback TextureView of the KTV main interface on the front driver's screen of the target vehicle at preset intervals, drawing the bitmap object corresponding to the current video frame bitmap onto the canvas of the playback control on the rear row interface, and rendering the canvas onto the TextureView of the rear row to obtain corresponding rendering data; and a playback module for synchronizing video source playback between the rear row interface and the KTV main interface on the front driver's screen based on the rendering data and the activity interface.

[0010] Optionally, in one embodiment of this application, the playback module includes: an overlay unit, used to overlay the activity interface and the rendering data to construct an independent rear-seat interface, so that the rear-seat interface can be played synchronously with the video in the KTV main interface of the driver's screen in the front row.

[0011] Optionally, in one embodiment of this application, it further includes: an acquisition module, configured to acquire a SurfaceTexture object from the TextureView of the rear interface based on a preset getSurfaceTexture() call strategy before acquiring the current video frame bitmap from the playback TextureView of the KTV main interface on the front driver's side screen of the target vehicle at preset intervals; a locking module, configured to lock the canvas of the TextureView using a preset lockCanvas() strategy and the SurfaceTexture object, and acquire a canvas object; and a construction module, configured to determine the width and height of the TextureView, and construct a blank bitmap object based on the width and height.

[0012] Optionally, in one embodiment of this application, the screen projection module includes: a drawing unit, used to draw the content of the playback TextureView of the KTV main interface on the front driver's screen into a bitmap object using a canvas object; and an unlocking unit, used to unlock the canvas of the TextureView based on a preset unlockCanvasAndPost(canvas) strategy, so as to render the TextureView in the rear row through the canvas of the TextureView to obtain rendering data.

[0013] A third aspect of this application provides a vehicle, including: a memory, a processor, and a computer program stored in the memory and executable on the processor. The processor executes the program to implement the screen projection method for multi-screen interaction in a cabin KTV as described in the above embodiments.

[0014] A fourth aspect of this application provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the above-described method for multi-screen interaction in a cockpit KTV.

[0015] A fifth aspect of this application provides a computer program product, including a computer program that is executed to implement the above-described screen projection method for multi-screen interaction in a cabin KTV.

[0016] Therefore, the embodiments of this application have the following beneficial effects:

[0017] This application's embodiments can initiate the screen projection mode of the target vehicle to create and display an activity interface in the rear seats of the vehicle. At preset intervals, the current video frame bitmap is obtained from the playback TextureView of the KTV main interface on the driver's side screen of the target vehicle. The bitmap object corresponding to the current video frame bitmap is drawn onto the canvas of the playback control on the rear-seat interface, and the canvas is then rendered in the TextureView of the rear-seat interface to obtain corresponding rendering data. Based on the rendering data and the activity interface, the rear-seat interface and the KTV main interface on the driver's side screen can synchronously play video sources. This application, by projecting only the video content onto other screens, enables the video content to be displayed on other screens, allowing the menu interface to be customized and differentiated according to its location on the screen, greatly enriching the user interaction content of multi-screen hardware. This solves the problem in existing technologies where in-vehicle KTV multi-screen interaction can only project the video and cannot perform independent menu operations.

[0018] Additional aspects and advantages of this application will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of this application. Attached Figure Description

[0019] The above and / or additional aspects and advantages of this application will become apparent and readily understood from the following description of the embodiments taken in conjunction with the accompanying drawings, wherein:

[0020] Figure 1 This is a flowchart of a screen projection method for multi-screen interaction in a cabin KTV according to an embodiment of this application;

[0021] Figure 2 A schematic diagram of a video stream copying process provided for one embodiment of this application;

[0022] Figure 3 A video rendering diagram of a screen casting initiator is provided as an embodiment of this application;

[0023] Figure 4 A schematic diagram of video rendering on the screen-projected device is provided as an embodiment of this application;

[0024] Figure 5 This is an example diagram of a screen projection device for multi-screen interaction in a cabin KTV according to an embodiment of this application;

[0025] Figure 6 This is a schematic diagram of the vehicle structure provided in an embodiment of this application.

[0026] Among them, 10-screen projection device for multi-screen interaction in cabin KTV; 100-start-up module, 200-screen projection module, 300-playback module; 601-memory, 602-processor, 603-communication interface. Detailed Implementation

[0027] The embodiments of this application are described in detail below. Examples of these embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals denote the same or similar elements or elements having the same or similar functions throughout. The embodiments described below with reference to the accompanying drawings are exemplary and intended to explain this application, and should not be construed as limiting this application.

[0028] The following describes a screen projection method and apparatus for multi-screen interaction in a cabin KTV according to embodiments of this application, with reference to the accompanying drawings. Addressing the problems mentioned in the background art, this application provides a screen projection method for multi-screen interaction in a cabin KTV. In this method, the screen projection mode of the target vehicle is activated to create and display an activity interface in the rear row of the target vehicle. At preset intervals, the current video frame bitmap is obtained from the playback TextureView of the KTV main interface on the front driver's screen of the target vehicle. The bitmap object corresponding to the current video frame bitmap is drawn onto the canvas of the playback control on the rear row interface, and the canvas is drawn onto the TextureView of the rear row for rendering to obtain corresponding rendering data. Based on the rendering data and the activity interface, the rear row interface and the KTV main interface on the front driver's screen are synchronized for video source playback. This application, by projecting only the video content onto other screens, enables the display of video content on other screens, allowing the menu interface to be customized and differentiated according to its location on the screen, greatly enriching the user interaction content of the multi-screen hardware. This solves the problem in existing technologies where in-vehicle KTV multi-screen interaction can only project screens and cannot perform independent menu operations.

[0029] Specifically, Figure 1 A flowchart illustrating a screen projection method for multi-screen interaction in a cabin KTV, provided as an embodiment of this application.

[0030] like Figure 1 As shown, the screen projection method for multi-screen interaction in this cabin KTV includes the following steps:

[0031] In step S101, the screen projection mode of the target vehicle is activated to create and display the activity interface in the back seat of the target vehicle.

[0032] In step S102, at preset intervals, the current video frame bitmap is obtained from the playback TextureView of the KTV main interface on the front driver's screen of the target vehicle, and the bitmap object corresponding to the current video frame bitmap is drawn onto the canvas of the playback control on the rear interface. The canvas is then drawn onto the TextureView in the rear for rendering to obtain the corresponding rendering data.

[0033] In the embodiments of this application, the main interface of the KTV on the front driver's screen uses a combination of TextureView and Android Media Player for video playback, and the menu operation interface is on this playback layout.

[0034] First, in the embodiments of this application, the screen mirroring button can be clicked to create a new activity interface in the back row and display it there; second, as... Figure 2 As shown, in this embodiment of the application, the playback frame can be obtained from the playback TextureView in the front row through a timed operation per second (such as a timed task operation of more than 30 times per second), and the copied bitmap is drawn onto the canvas of the playback control in the current back row interface, so as to render the canvas onto the back row TextureView, thereby obtaining the video data of the back row.

[0035] Optionally, in one embodiment of this application, before obtaining the current video frame bitmap from the playback TextureView of the KTV main interface on the front driver's side screen of the target vehicle at preset intervals, the method further includes: obtaining a SurfaceTexture object from the TextureView of the rear interface based on a preset getSurfaceTexture() calling strategy; locking the canvas of the TextureView using a preset lockCanvas() strategy and the SurfaceTexture object, and obtaining the canvas object; determining the width and height of the TextureView, and constructing a blank bitmap object based on the width and height.

[0036] It should be noted that, in this embodiment of the application, the SurfaceTexture object can be obtained from the TextureView in the back row by calling the getSurfaceTexture() method; secondly, in this embodiment of the application, the lockCanvas() method can be used to lock the canvas of the TextureView and obtain a canvas object for subsequent drawing operations.

[0037] Subsequently, embodiments of this application can create a blank Bitmap object based on the width and height of the TextureView to store the copied content.

[0038] Therefore, the embodiments of this application provide reliable data support and basis for obtaining rear-row video data by constructing a blank bitmap object.

[0039] Optionally, in one embodiment of this application, at preset time intervals, the current video frame bitmap is obtained from the playback TextureView of the KTV main interface on the front driver's screen of the target vehicle, and the bitmap object corresponding to the current video frame bitmap is drawn onto the canvas of the playback control on the rear interface. The canvas is then drawn onto the TextureView in the rear for rendering to obtain the corresponding rendering data. This includes: using the canvas object to draw the content of the playback TextureView of the KTV main interface on the front driver's screen onto the bitmap object; and unlocking the canvas of the TextureView based on the preset unlockCanvasAndPost(canvas) strategy to render the TextureView in the TextureView in the rear to obtain the rendering data.

[0040] In actual execution, embodiments of this application can use the obtained canvas object to draw the content of the front TextureView onto the created Bitmap object; after drawing is completed, embodiments of this application can call the unlockCanvasAndPost(canvas) method to unlock the canvas of the TextureView and submit the drawing operation to the back TextureView so that the back TextureView can be rendered through the canvas of the TextureView to obtain the rendering data.

[0041] In step S103, based on the rendering data and activity interface, the rear-seat interface and the KTV main interface on the driver's screen in the front row are synchronized to play video sources.

[0042] Subsequently, embodiments of this application can overlay a rear-row operation menu interface on top of the video playback space in the rear row, thereby allowing for the customization of an independent rear-row operation interface.

[0043] Therefore, under the premise of single-host hardware, the embodiments of this application do not excessively rely on host hardware resources, realize the sharing and synchronization of front and back row video streams, and the independent menu operation interface, which meets the scenario of users watching video streams simultaneously and using them individually.

[0044] Optionally, in one embodiment of this application, based on rendering data and an activity interface, the rear-seat interface and the KTV main interface on the front driver's screen are synchronized for video source playback. This includes: overlaying the activity interface and rendering data to construct an independent rear-seat interface so that the rear-seat interface can synchronize with the video in the KTV main interface on the front driver's screen.

[0045] It should be noted that, as Figure 3 As shown in the embodiments of this application, in the front-row video playback activity interface, the video stream playback carrier is a textureview control, the video playback decoding and loading is done by the native Android MediaPlayer, and the decoded video stream is played on the textureview control; a playback control component is overlaid on the textureview control, including a play / pause, previous / next track control, playlist, screen casting and other operation menu control interface, for front-row users to operate and control.

[0046] like Figure 4 As shown, the layout of the playback interface on the rear screen is similar to the layout described above. That is, the textureview control in an activity was previously overlaid with the operation layout interface of the rear screen. The layout interface is different from that of the front screen. The rear screen does not have a media player to load and decode the video source.

[0047] Therefore, while the video in the front row is playing, clicking the screen mirroring button in the front row will allow the video in the rear row and the video in the front row to be displayed synchronously through the above process. The screens are displayed synchronously, and the menus can be operated independently, enabling various multi-screen interaction scenarios. For example, while the front row is selecting songs or singing, the back row can continue to select songs and like the atmosphere of the karaoke room. The menus on multiple screens are independent of each other and do not interfere with each other.

[0048] In summary, the embodiments of this application greatly enrich the user interaction content of multi-screen hardware by projecting only video content onto other screens, such as projecting from the front row to the back row, and vice versa. This allows video content to be displayed on other screens, and the menu interface to be customized and differentiated according to the location of the screen. In the embodiment of this application, the projection behavior initiated by the front screen of the in-vehicle KTV can project the music video to the back row, with lyrics and video synchronized. While the users in the front row are operating their song selection menus, the passengers in the back row are not affected and can continue to see the playback and lyrics and sing normally. The passengers in the back row can also select / skip songs according to their needs, and even add some atmosphere for the users in the front row to sing.

[0049] According to the screen projection method for multi-screen interaction in a cabin KTV proposed in this application, the screen projection mode of the target vehicle is activated to create and display an activity interface in the rear row of the target vehicle. At preset intervals, the current video frame bitmap is obtained from the playback TextureView of the KTV main interface on the front driver's screen of the target vehicle, and the bitmap object corresponding to the current video frame bitmap is drawn onto the canvas of the playback control on the rear interface. The canvas is then drawn onto the TextureView in the rear for rendering to obtain the corresponding rendering data. Based on the rendering data and the activity interface, the rear interface and the KTV main interface on the front driver's screen are synchronized for video source playback. This application, by projecting only the video content onto other screens, enables the video content to be displayed on other screens, allowing the menu interface to be customized and differentiated according to its location on the screen, greatly enriching the user interaction content of the multi-screen hardware.

[0050] Secondly, the screen projection device for multi-screen interaction in a cabin KTV according to an embodiment of this application is described with reference to the accompanying drawings.

[0051] Figure 5 This is a block diagram of a projection device for multi-screen interaction in a cabin KTV, according to an embodiment of this application.

[0052] like Figure 5 As shown, the multi-screen interactive projection device 10 of the cabin KTV includes: a start-up module 100, a projection module 200, and a playback module 300.

[0053] The startup module 100 is used to start the screen projection mode of the target vehicle to create and display the activity interface in the back seat of the target vehicle.

[0054] The projection module 200 is used to obtain the current video frame bitmap from the playback TextureView of the KTV main interface on the front driver's screen of the target vehicle at preset intervals, draw the bitmap object corresponding to the current video frame bitmap onto the canvas of the playback control on the rear interface, and draw the canvas onto the TextureView of the rear for rendering to obtain the corresponding rendering data.

[0055] The playback module 300 is used to synchronize the video source playback between the rear-seat interface and the KTV main interface on the driver's screen in the front row, based on rendering data and the activity interface.

[0056] Optionally, in one embodiment of this application, the playback module 300 includes: an overlay unit for overlaying the activity interface and rendering data to construct an independent rear-seat interface so that the rear-seat interface can be played synchronously with the video in the KTV main interface on the driver's screen in the front row.

[0057] Optionally, in one embodiment of this application, the projection device 10 for multi-screen interaction in the cabin KTV of this application embodiment further includes: an acquisition module, a locking module, and a construction module.

[0058] The acquisition module is used to obtain SurfaceTexture objects from the TextureView of the rear-seat interface before obtaining the current video frame bitmap from the playback TextureView of the KTV main interface on the front driver's screen of the target vehicle at preset intervals, based on a preset getSurfaceTexture() call strategy.

[0059] The locking module is used to lock the canvas of the TextureView using a preset lockCanvas() strategy and a SurfaceTexture object, and to obtain the canvas object.

[0060] The building block is used to determine the width and height of the TextureView and to construct a blank bitmap object based on the width and height.

[0061] Optionally, in one embodiment of this application, the projection module 200 includes a drawing unit and an unlocking unit.

[0062] The drawing unit is used to draw the content of the playback TextureView of the KTV main interface on the driver's side screen into a bitmap object using a canvas object.

[0063] The unlocking unit is used to unlock the canvas of the TextureView based on the preset unlockCanvasAndPost(canvas) strategy, so that the TextureView can be rendered in the subsequent TextureView to obtain the rendering data.

[0064] It should be noted that the explanation of the above-mentioned screen projection method embodiment for multi-screen interaction in cabin KTV also applies to the screen projection device for multi-screen interaction in cabin KTV in this embodiment, and will not be repeated here.

[0065] The screen projection device for multi-screen interaction in a cabin KTV according to the embodiments of this application includes a startup module 100, used to start the screen projection mode of the target vehicle to create and display an activity interface in the rear row of the target vehicle; a screen projection module 200, used to obtain the current video frame bitmap from the playback TextureView of the KTV main interface on the front driver's screen of the target vehicle at preset intervals, draw the bitmap object corresponding to the current video frame bitmap onto the canvas of the playback control on the rear interface, and draw the canvas onto the TextureView of the rear interface for rendering to obtain the corresponding rendering data; and a playback module 300, used to synchronize the video source playback between the rear interface and the KTV main interface on the front driver's screen based on the rendering data and the activity interface. This application, by projecting only the video content onto other screens, enables the video content to be displayed on other screens, and allows the menu interface to be customized and differentiated according to the position of the screen, greatly enriching the user interaction content of the multi-screen hardware.

[0066] Figure 6 A schematic diagram of the structure of a vehicle provided in an embodiment of this application. The vehicle may include:

[0067] The memory 601, the processor 602, and the computer program stored on the memory 601 and capable of running on the processor 602.

[0068] When the processor 602 executes the program, it implements the screen projection method for multi-screen interaction in the cabin KTV provided in the above embodiments.

[0069] Furthermore, the vehicle also includes:

[0070] Communication interface 603 is used for communication between memory 601 and processor 602.

[0071] The memory 601 is used to store computer programs that can run on the processor 602.

[0072] The memory 601 may include high-speed RAM memory, and may also include non-volatile memory, such as at least one disk storage device.

[0073] If the memory 601, processor 602, and communication interface 603 are implemented independently, then the communication interface 603, memory 601, and processor 602 can be interconnected via a bus to complete communication between them. The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. Buses can be categorized as address buses, data buses, control buses, etc. For ease of representation, Figure 6 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.

[0074] Optionally, in a specific implementation, if the memory 601, processor 602, and communication interface 603 are integrated on a single chip, then the memory 601, processor 602, and communication interface 603 can communicate with each other through an internal interface.

[0075] The processor 602 may be a central processing unit (CPU), an application specific integrated circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of this application.

[0076] This application also provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the above-described method for multi-screen interaction in a cockpit KTV.

[0077] This application also provides a computer program product, including a computer program, which, when executed, is used to implement the above-described cockpit KTV multi-screen interactive projection method.

[0078] In the description of this specification, the references to terms such as "one embodiment," "some embodiments," "example," "specific example," or "some examples," etc., indicate that a specific feature, structure, material, or characteristic described in connection with that embodiment or example is included in at least one embodiment or example of this application. In this specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples. Moreover, without contradiction, those skilled in the art can combine and integrate the different embodiments or examples described in this specification, as well as the features of different embodiments or examples.

[0079] Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one of that feature. In the description of this application, "N" means at least two, such as two, three, etc., unless otherwise explicitly specified.

[0080] Any process or method described in the flowchart or otherwise herein can be understood as representing a module, segment, or portion of code comprising one or N executable instructions for implementing custom logic functions or processes, and the scope of the preferred embodiments of this application includes additional implementations in which functions may be performed not in the order shown or discussed, including substantially simultaneously or in reverse order depending on the functions involved, as should be understood by those skilled in the art to which embodiments of this application pertain.

[0081] The logic and / or steps represented in the flowchart or otherwise described herein, for example, can be considered as a sequenced list of executable instructions for implementing logical functions, and can be embodied in any computer-readable medium for use by, or in conjunction with, an instruction execution system, apparatus, or device (such as a computer-based system, a processor-included system, or other system that can fetch and execute instructions from, an instruction execution system, apparatus, or device). For the purposes of this specification, "computer-readable medium" can be any means that can contain, store, communicate, propagate, or transmit programs for use by, or in conjunction with, an instruction execution system, apparatus, or device. More specific examples (a non-exhaustive list) of computer-readable media include: an electrical connection having one or more wires (electronic device), a portable computer disk drive (magnetic device), random access memory (RAM), read-only memory (ROM), erasable and editable read-only memory (EPROM or flash memory), fiber optic devices, and portable optical disc read-only memory (CDROM). Alternatively, the computer-readable medium may be paper or other suitable media on which the program can be printed, since the program can be obtained electronically by optically scanning the paper or other medium, followed by editing, interpreting, or otherwise processing as necessary, and then stored in a computer memory.

[0082] It should be understood that the various parts of this application can be implemented using hardware, software, firmware, or a combination thereof. In the above embodiments, the N steps or methods can be implemented using software or firmware stored in memory and executed by a suitable instruction execution system. If implemented in hardware, as in another embodiment, it can be implemented using any one or a combination of the following techniques known in the art: discrete logic circuits having logic gates for implementing logical functions on data signals, application-specific integrated circuits (ASICs) having suitable combinational logic gates, programmable gate arrays (PGAs), field-programmable gate arrays (FPGAs), etc.

[0083] Those skilled in the art will understand that all or part of the steps of the methods in the above embodiments can be implemented by a program instructing related hardware. The program can be stored in a computer-readable storage medium, and when executed, the program includes one or a combination of the steps of the method embodiments.

[0084] Furthermore, the functional units in the various embodiments of this application can be integrated into a processing module, or each unit can exist physically separately, or two or more units can be integrated into a module. The integrated module can be implemented in hardware or as a software functional module. If the integrated module is implemented as a software functional module and sold or used as an independent product, it can also be stored in a computer-readable storage medium.

[0085] The storage medium mentioned above can be a read-only memory, a disk, or an optical disk, etc. Although embodiments of this application have been shown and described above, it is understood that the above embodiments are exemplary and should not be construed as limiting this application. Those skilled in the art can make changes, modifications, substitutions, and variations to the above embodiments within the scope of this application.

Claims

1. A screen projection method for multi-screen interaction in a cockpit KTV, characterized in that, Includes the following steps: Activate the screen mirroring mode of the target vehicle to create and display an activity interface in the back seat of the target vehicle; Every preset time interval, the current video frame bitmap is obtained from the playback TextureView of the KTV main interface on the front driver's screen of the target vehicle, and the bitmap object corresponding to the current video frame bitmap is drawn onto the canvas of the playback control on the rear interface. The canvas is then drawn onto the TextureView in the rear for rendering to obtain the corresponding rendering data. Based on the rendering data and the activity interface, the rear-seat interface and the KTV main interface on the front driver's screen are synchronized to play video sources. The step of synchronizing video source playback between the rear-seat interface and the KTV main interface on the driver's side screen based on the rendering data and the activity interface includes: The activity interface and the rendering data are superimposed to construct an independent rear-seat interface so that the rear-seat interface can play the video synchronously with the KTV main interface on the driver's screen in the front row. Before retrieving the current video frame bitmap from the playback TextureView of the KTV main interface on the front driver's side screen of the target vehicle at preset intervals, the method further includes: Based on the preset getSurfaceTexture() call strategy, the SurfaceTexture object is obtained from the TextureView of the back-end interface; The canvas of the TextureView is locked using the preset lockCanvas() strategy and the SurfaceTexture object, and the canvas object is obtained. Determine the width and height of the TextureView, and construct a blank bitmap object based on the width and height.

2. The method according to claim 1, characterized in that, At preset time intervals, the current video frame bitmap is obtained from the playback TextureView of the KTV main interface on the front driver's screen of the target vehicle. The bitmap object corresponding to the current video frame bitmap is drawn onto the canvas of the playback control on the rear interface, and the canvas is drawn onto the TextureView of the rear interface for rendering to obtain the corresponding rendering data, including: Using the canvas object, the content of the playback TextureView of the KTV main interface on the front driver's screen is drawn onto the bitmap object; Based on the preset unlockCanvasAndPost(canvas) strategy, the canvas of the TextureView is unlocked so that the rendering can be performed in the TextureView in the back row through the canvas of the TextureView to obtain the rendering data.

3. A projection device for multi-screen interaction in a cabin KTV, characterized in that, include: The startup module is used to start the screen projection mode of the target vehicle to create and display the activity interface in the back seat of the target vehicle; The screen projection module is used to obtain the current video frame bitmap from the playback TextureView of the KTV main interface on the front driver's screen of the target vehicle at preset intervals, draw the bitmap object corresponding to the current video frame bitmap onto the canvas of the playback control on the rear interface, and draw the canvas onto the TextureView of the rear for rendering to obtain the corresponding rendering data. The playback module is used to synchronize the video source playback between the rear-seat interface and the KTV main interface on the driver's screen in the front row, based on the rendering data and the activity interface. The playback module includes: The overlay unit is used to overlay the activity interface and the rendering data to construct an independent rear-seat interface so that the rear-seat interface can play the video synchronously with the KTV main interface on the front driver's screen. The projection device for the multi-screen interaction in the cabin KTV also includes: The acquisition module is used to acquire a SurfaceTexture object from the TextureView of the rear interface based on a preset getSurfaceTexture() call strategy before acquiring the current video frame bitmap from the playback TextureView of the KTV main interface on the front driver's screen of the target vehicle at preset intervals. The locking module is used to lock the canvas of the TextureView using a preset lockCanvas() strategy and the SurfaceTexture object, and to obtain the canvas object. A construction module is used to determine the width and height of the TextureView and construct a blank bitmap object based on the width and height.

4. A vehicle, characterized in that, include: The system includes a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the screen projection method for multi-screen interaction in a cabin KTV as described in any one of claims 1-2.

5. A computer-readable storage medium having a computer program stored thereon, characterized in that, The program is executed by the processor to implement the screen projection method for multi-screen interaction in a cabin KTV as described in any one of claims 1-2.

6. A computer program product, comprising a computer program, characterized in that, The computer program is executed to implement the screen projection method for multi-screen interaction in a cabin KTV as described in any one of claims 1-2.

Images