Video playback method, device, terminal, and program

Abstract

A video playback method, device, terminal, storage medium, and program product, which relate to the field of human-computer interaction technology, includes the steps of: displaying a windowed playback control in a non-battle scene interface when a video playback resource of a first video exists in a non-battle scene interface, the non-battle scene interface being a scene interface other than a battle (101); displaying a video playback window in a higher layer of the non-battle scene interface in response to a trigger operation on the windowed playback control in the non-battle scene interface, the first video being played in the video playback window (102); and closing the video playback window when switching from the non-battle scene interface to the battle interface (103).

Description

Technical Field

[0001] (Cross-reference to related applications) This application claims the priority of a Chinese patent application with the application number 202111204151.5 and the invention title of "Video Playback Method, Apparatus, Terminal, Storage Medium and Program Product", which was filed with the China National Intellectual Property Administration on October 15, 2021, and all of its content is incorporated herein by reference.

[0002] This application relates to the technical field of human-computer interaction, and particularly relates to a video playback method, apparatus, terminal and program.

Background Art

[0003] In a multiplayer online battle arena (MOBA) game, the out-of-battle scene refers to the game environment outside the rounds of battles in the MOBA game. Players can learn game knowledge, obtain various benefits such as hero skins, prepare for battles, or communicate with other players to become friends outside the battle. The in-battle scene refers to the enclosed world where the battle game is played, and players aim to engage in heroic battles, release skills, and achieve game victories therein.

[0004] In the related art, in the out-of-battle environment, a playback interface for game-related videos is provided to users. When a user needs to watch game-related videos, the user can access the video playback interface through this interface and play this game-related video.

[0005] Obviously, in order to watch game-related videos during the game, it is necessary to always stay on the video playback interface and cannot switch to other out-of-battle scene interfaces.

Summary of the Invention

Problems to be Solved by the Invention

[0006] This application provides a video playback method, apparatus, terminal, storage medium, and program product. The technical solution is as follows. [Means for solving the problem]

[0007] According to one aspect of the present invention, a video playback method is provided which is performed by a terminal, and the method is If a video playback resource for a first video exists in the non-battle scene interface, the step is to display a windowed playback control in the non-battle scene interface, wherein the non-battle scene interface is a scene interface outside of the game. A step of displaying a video playback window on a higher layer of the out-of-battle scene interface in response to a trigger operation on the windowed playback control in the out-of-battle scene interface, wherein the first video is played in the video playback window; The process includes the step of closing the video playback window when switching from the non-battle scene interface to the battle interface.

[0008] According to another aspect of the present application, a video playback device is provided, the device is If a video playback resource for a first video exists in the non-battle scene interface, a first display module configured to display a windowed playback control in the non-battle scene interface, wherein the non-battle scene interface is a scene interface outside of a match, and the first display module, A second display module configured to display a video playback window on a higher layer of the out-of-battle scene interface in response to a trigger operation on the windowed playback control in the out-of-battle scene interface, wherein the first video is played back in the video playback window, and the second display module The system includes a first control module configured to close the video playback window when switching from the non-battle scene interface to the battle interface.

[0009] According to another aspect of the present invention, a terminal is provided, the terminal comprising a processor and a memory storing at least one program, the at least one program being loaded and executed by the processor to realize the video playback method described in the above aspect.

[0010] According to another aspect of the present application, a computer-readable storage medium is provided, the storage medium storing at least one instruction, at least one program, a code set or instruction set, and the one instruction, the at least one program, the code set or instruction set is loaded and executed by a processor to realize the video playback method described in the above aspect.

[0011] According to another aspect of the present application, a computer program product is provided, the computer program product includes computer instructions, the computer instructions are stored in a computer-readable storage medium. The terminal's processor reads the computer instructions from the computer-readable storage medium and executes them, thereby causing the terminal to execute the video playback method provided in the alternative embodiment described above. [Effects of the Invention]

[0012] In game scenes, by providing a windowed video playback function to the video playback resource within the non-battle scene interface, the first video can be played through a video playback window. This provides a feasible way for users to play videos during gameplay, eliminating the need to always maintain a full-screen video playback interface. Playing videos through a video playback window reduces the impact on user-related operations in the non-battle scene interface during video playback. Furthermore, by closing the video playback window after entering the battle interface, the impact of video playback on the game battle process can be avoided. [Brief explanation of the drawing]

[0013] [Figure 1] This is a flowchart of a video playback method according to one exemplary embodiment of the present invention. [Figure 2] This is a schematic diagram of the video playback process according to one exemplary embodiment of the present invention. [Figure 3] This is a flowchart of a video playback method according to another exemplary embodiment of the present invention. [Figure 4] This is a schematic diagram showing the display of the first video according to another exemplary embodiment of the present application. [Figure 5] This is a schematic diagram of the video playback process according to another exemplary embodiment of the present application. [Figure 6] This is a schematic diagram illustrating the closing process of a video playback window according to one exemplary embodiment of the present invention. [Figure 7] This is a flowchart of a video playback method according to another exemplary embodiment of the present invention. [Figure 8] A schematic diagram of a video switching process according to one exemplary embodiment of the present invention. [Figure 9] This is a flowchart of a video playback method according to another exemplary embodiment of the present invention. [Figure 10] This is a schematic diagram of the video playback window display position according to one exemplary embodiment of the present invention. [Figure 11]It is a schematic diagram of the process of enlarging a video playback window according to an exemplary embodiment of the present application. [Figure 12] It is a schematic diagram of the process of reducing a video playback window according to an exemplary embodiment of the present application. [Figure 13] It is a schematic diagram of the process of updating the control size corresponding to a function control according to an exemplary embodiment of the present application. [Figure 14] It is a flowchart of a video playback method according to another exemplary embodiment of the present application. [Figure 15] It is a schematic diagram of the process of updating the window position of a video playback window according to an exemplary embodiment of the present application. [Figure 16] It is a schematic diagram of the process of updating the window position of a video playback window according to another exemplary embodiment of the present application. [Figure 17] It is a schematic diagram of a video full-screen mode according to an exemplary embodiment of the present application. [Figure 18] It is a schematic diagram of a video playback module related to a video playback process according to an exemplary embodiment of the present application. [Figure 19] It is a schematic diagram of the window scaling process in the window interaction mode. [Figure 20] It is a schematic diagram showing the configuration of a video playback device according to an exemplary embodiment of the present application. [Figure 21] It is a schematic diagram showing the configuration of a terminal according to an exemplary embodiment of the present application.

Embodiments for Carrying Out the Invention

[0014] To more clearly explain the object, technical solution and advantages of the present application, hereinafter, the embodiments of the present application will be described in more detail with reference to the drawings.

[0015] First, the nouns related to the embodiments of the present application will be briefly introduced.

[0016] Out-of-battle (also called "out-of-game" or "out-of-match"): This is the environment outside of the in-game battle combat. Users can learn game knowledge, acquire hero skins, prepare for battle, and interact with other users to make friends. Out-of-battle is support and assistance for the game. In the embodiments of the present invention, the out-of-battle scene interface is an interface for displaying out-of-game scenes. Exemplary examples of out-of-battle scene interfaces may include a hero skin viewing interface, a game video viewing interface, a game live viewing interface, a friend communication interface, a lineup matching interface, and the like.

[0017] In-Battle (also called "In-Game" or "In-Match"): This is the gateway world where the battle combat game is played. Users can engage in heroic battles, unlock skills, and aim for game victory, which constitute the core experience of the in-battle game. Optionally, in the embodiments of the present invention, the battle interface is an interface that displays the battle scene, such as a battle participation interface, and may include a battle matching interface, a character selection interface (an interface for choosing to participate in a battle), a battle display interface (which displays the process of a user participating in a battle), or a battle spectator interface, an interface for a user to observe friends or other users participating in a battle.

[0018] Referring to Figure 1, Figure 1 is a flowchart of a video playback method according to one exemplary embodiment of the present invention. As an example, if the implementing entity of the method is a terminal, the method includes the following steps.

[0019] In step 101, if a video playback resource for the first video exists in the non-battle scene interface, a windowed playback control is displayed in the non-battle scene interface, and the non-battle scene interface is a scene interface outside of the battle.

[0020] During gameplay, users can participate in battles, learn game knowledge outside of battles, acquire hero skins, prepare for combat, and interact with other users to make friends. Outside of battles, game-related video resources are also provided, such as game live streams, battle lineup recommendation videos, and hero skin showcase videos. If a user needs to watch the above game-related videos within the game, they must remain in the full-screen video playback interface until the video playback is complete, and other game-related operations cannot be performed during video playback, resulting in a high time cost for video playback during gameplay.

[0021] To improve the ease of use and viewing efficiency of in-game video playback, an embodiment of the present invention provides a function to play game videos using a video playback window during gameplay. Since the video playback window does not affect the display of the game's own out-of-battle scene interface during video playback, the user can perform game-related operations on the out-of-battle scene interface while watching game-related videos, and the video played in the video playback window is not affected even when a different out-of-battle scene interface is switched.

[0022] Because the game involves various types of videos, such as online videos and local videos, in one possible embodiment, windowed playback controls are provided for different types of video playback resources to meet the needs of users who want to view different types of videos in the out-of-battle scene interface. The windowed playback controls are used to trigger the playback of the video using a video playback window. That is, when the terminal detects that a video playback resource for a first video exists in the out-of-battle scene interface, the windowed playback controls are displayed in the out-of-battle scene interface, allowing the user to trigger the windowed playback function of the video using the windowed playback controls.

[0023] For example, taking a MOBA game as an example, the out-of-battle scene interface for video playback resources could be the in-game preparation center interface, and correspondingly, the first video could be a lineup recommendation video. The out-of-battle scene interface could also be an event TV interface, and correspondingly, the first video could be various event live videos. The out-of-battle scene interface could also be a micro-community interface, and correspondingly, the first video could be gameplay strategy videos for various heroes, etc. The out-of-battle scene interface could also be a short video interface, and correspondingly, the first video could be gameplay instruction videos from different game streamers, etc. The embodiments of this application do not limit the out-of-battle scene interface or the specific videos displayed in the out-of-battle scene interface.

[0024] Optionally, the display position of the windowed playback control can be made clear that it is related to the first video, that is, that after the user taps the windowed playback control, the device is used to play the first video in the video playback window. Exemplaryly, the windowed playback control can be displayed in positions such as the lower right corner, upper left corner, lower left corner, or upper right corner of the first video, and the embodiments of the present application do not limit the display position of the windowed playback control.

[0025] As shown in Figure 2, Figure 2 is a schematic diagram of the video playback process according to one exemplary embodiment of the present invention. Taking the case where the out-of-battle scene interface is a virtual character recommendation interface as an example, the out-of-battle scene interface 201 contains a video playback resource for the first video 202, and a windowed playback control 203 is displayed in the lower right corner of the first video 202. Optionally, a full-screen control 206 is displayed in the lower left corner of the first video 202, and the full-screen control 206 is used to trigger full-screen display of the first video 202.

[0026] In step 102, in response to a trigger operation on the windowed playback control in the out-of-battle scene interface, a video playback window is displayed on a higher layer of the out-of-battle scene interface, and the first video is played in the video playback window.

[0027] In one possible embodiment, if a user needs to play a first video via a video playback window, they can tap a windowed playback control. In response, the terminal receives the trigger operation of the windowed playback control in the out-of-battle scene interface, displays a video playback window on a higher layer of the out-of-battle scene interface, and plays the first video in the video playback window.

[0028] As shown in Figure 2, if a user needs to play the first video 202 using the video playback window, they can tap the windowed playback control 203 corresponding to the first video 202. In response, the terminal receives a trigger operation on the windowed playback control 203 and displays a video playback window 204 in the lower left corner of the out-of-battle scene interface 201, with the first video 202 displayed in the video playback window 204.

[0029] Optionally, when playing the first video in the video playback window, you can close the video playback resource for the first video displayed in the out-of-battle scene interface.

[0030] When playing the first video in the video playback window, the user can optionally switch between different out-of-battle scene interfaces. During the out-of-battle scene interface switching process, the video playback window will appear on a higher level of the different out-of-battle scene interface, allowing the user to play the first video. This also allows the user to perform game-related operations in other out-of-battle scene interfaces, such as contacting others, making friends, matching in the lineup, and viewing other game-related information, while watching the first video.

[0031] Optionally, to avoid the video playback window blocking the out-of-battle scene interface and affecting user operation, the video playback window may be displayed in the corner of the out-of-battle scene interface interface, or in the corner of the terminal display screen, for example, the upper left corner, upper right corner, lower right corner, lower left corner, etc. Embodiments of the present application do not limit the display position of the video playback window.

[0032] The optional adoption of a video playback window is essentially intended to allow users to perform other out-of-battle operations while watching a video; therefore, to avoid completely blocking the out-of-battle scene interface, the display size of the video playback window should be smaller than the display size of the terminal's display screen.

[0033] Furthermore, since the display of a video playback window in the embodiment of this application does not depend on the video windowing function provided by the terminal system, but is provided by the target application (the application to which the battle-out-of-battle scene interface belongs), the video playback window provided in the embodiment of this application can provide more additional functions, such as video switching, volume control, display of video-related information, and video favorites, as described in the following embodiment.

[0034] In one possible embodiment, the target application implements video playback functionality for a video playback window (bound to the image display component) by calling the FFmpeg library to decode the first video, update the resulting image frames, and display them in the image display component (e.g., RawImage component) of the game engine (e.g., Unity engine). Furthermore, since the video displayed by calling the game engine can be naturally integrated into the hierarchical management system of the game GUI, additional screen alignment is unnecessary, improving development efficiency.

[0035] In step 103, if the user switches from the non-battle scene interface to the battle interface, the video playback window is closed.

[0036] Since employing a video playback window to play videos is intended to improve the efficiency of users watching videos in non-battle scenes, in order to avoid the video playback window interfering with the game battle (the main game process), in one possible embodiment, when entering the battle interface, i.e., when switching from the non-battle scene interface to the battle interface, the terminal closes the video playback window and stops playing the first video through the video playback window.

[0037] As shown in Figure 2, after switching from the non-battle scene interface 201 to the battle interface 205, the terminal does not display the video playback window 204 on the battle interface 205.

[0038] Furthermore, in the embodiment of this invention, the video playback window is a video playback component provided by the game itself, rather than calling a video playback window installed in the terminal system itself. Therefore, in the embodiment of this invention, the video playback window is automatically closed when the game battle process is entered, thereby avoiding any impact on the main game process.

[0039] As described above, in the embodiment of the present invention, by providing a windowed video playback function to the video playback resource in the out-of-battle scene interface, the first video can be played through a video playback window, providing a viable method for the user to play videos during gameplay, and eliminating the need to always maintain a full-screen video playback interface. Furthermore, by playing videos through a video playback window, the impact on the user's related operations in the out-of-battle scene interface during video playback can be reduced, and after entering the battle interface, the video playback window can be closed, simultaneously avoiding any impact of video playback on the game battle process.

[0040] To prevent the video playback window process from interfering with the game's main process (battle process), the terminal implements hierarchical control over the video playback window and sets closing rules. In other words, when a battle access command is received, the video playback window is closed beforehand to prevent any changes in the game's battle process.

[0041] As an exemplary example, Figure 3 shows a flowchart of a video playback method according to another exemplary embodiment of the present application. Using the example where the implementing entity of the method is a terminal, the method includes the following steps.

[0042] In step 301, if a video playback resource for the first video exists in the non-battle scene interface, a windowed playback control is displayed in the non-battle scene interface, and the non-battle scene interface is a scene interface outside of the battle.

[0043] The embodiment of step 301 can be found by referring to step 101, which will not be described again in this embodiment.

[0044] In step 302, in response to a trigger operation on the windowed playback control in the non-battle scene interface, the first video stream and first video-related information corresponding to the first video are received via the video call interface.

[0045] The differences between the video playback window in the embodiment of this application and the mini-window playback window (picture-in-picture) installed in the terminal system itself are as follows: The video playback window is the video playback component of the game application itself, has the function of acquiring game-related videos from the game application, and developers can add customization functions to the video playback component (since developers cannot customize the mini-window playback window installed in the terminal system itself, the playback effect achieved by different applications through the mini-window playback function provided by the terminal system is exactly the same).

[0046] In one possible embodiment, when a terminal receives a trigger operation for windowed playback control in an out-of-battle scene interface, it can obtain a first video stream corresponding to a first video and first video-related information corresponding to the first video via a video call interface corresponding to a video playback window, thereby enabling playback of the first video in the video playback window and display of information related to the first video in the video playback window.

[0047] The optional display of video-related information may be a customization feature added by the developer to the video playback component. If the video-related information display feature is not added, the video playback window can only retrieve the first video stream corresponding to the first video.

[0048] The first video-related information may optionally include the video title, video creator, and avatar corresponding to the video creator, and the embodiments of this application do not limit the first video-related information.

[0049] Optionally, if the first video is a local video of the game application, the first video stream corresponding to the first video and first video-related information are obtained from the local game video database via the video invocation interface. If the first video is an online video such as a live video, the background server of the game application pulls the first video stream from the game live platform and feeds it back to the terminal, and in response, the terminal receives the first video stream and first video-related information via the video invocation interface.

[0050] In step 303, the first video is played in the video playback window based on the first video stream and the first video-related information.

[0051] In one possible embodiment, the terminal plays the first video in a video playback window based on the first video stream and displays first video-related information of the first video in the video playback window.

[0052] Optionally, in the process of playing the first video in the video playback window, the first video-related information does not have to be displayed by default. If the user needs to view the first video-related information for the first video, they can tap the first video in the video playback window. Thus, the terminal receives a trigger operation on the first video in the video playback window and displays the first video-related information in the video playback window.

[0053] As shown in Figure 4, Figure 4 is a schematic diagram showing the display of the first video according to another exemplary embodiment of the present invention. The out-of-battle scene interface 401 displays a video playback window 402, and in addition to the first video, the video playback window 402 displays video-related information 403 associated with the video.

[0054] As shown in Figure 5, Figure 5 is a schematic diagram of the video playback process according to another exemplary embodiment of the present invention. Taking live video as an example, if a video resource related to live video exists in the first out-of-battle scene interface 501, and a windowed playback control 502 is displayed in the lower right corner of the video resource, the user can tap the windowed playback control 502 to return to the second out-of-battle scene interface 504 and at the same time display a video playback window 505 in the second out-of-battle scene interface 504, and the video playback window 505 will display the live video. Optionally, the live video may also be further provided with a small window spectator control 503, and the user can tap the small window spectator control 503 to similarly return to the second out-of-battle scene interface 504 and display the video playback window 505.

[0055] In step 304, if a battle command is received, the battle participation interface is displayed and the video playback window is closed.

[0056] Optionally, during gameplay, the battle interface includes at least a battle participation interface and a battle spectator interface, where the battle participation interface is an interface related to the process by which a user controls the participation of virtual objects in battle, and the battle spectator interface is an interface related to the process by which a user watches other users participate in battle.

[0057] In one possible embodiment, the terminal enters the battle participation interface shortly after receiving a battle command, and therefore, the video playback window needs to be closed in a timely manner to avoid its influence on the main battle process.

[0058] Optionally, taking a MOBA game as an example, a battle command could be a battle matchmaking completion instruction sent from the server to the terminal after battle matchmaking is complete. For example, in a 5v5 battle mode, after entering the matchmaking page and matchmaking is complete, the video playback window closes automatically. A battle command could also be a virtual character selection operation, indicating that the user needs to select a virtual character to participate in the battle, and in response, the terminal receives a battle command. For example, in a 1v1 battle mode, if the user directly selects a virtual character to participate in the battle, the video playback window closes automatically.

[0059] As shown in Figure 6, Figure 6 is a schematic diagram of the closing process of a video playback window according to one exemplary embodiment of the present invention. Taking the case where the out-of-battle scene interface 601 is a battle matching interface as an example, the battle matching interface is the interface before matching is completed. In this case, the out-of-battle scene interface 601 displays the video playback window 602, which allows the user to watch game-related videos during matching, thereby improving time utilization. After successful matching, indicating that a battle will soon begin, the out-of-battle scene interface 601 is switched to the battle loading interface 603, and at the same time, the video playback window 602 is closed.

[0060] In step 305, if a battle command is received, the playback progress of the first video in the video playback window is obtained.

[0061] While waiting for a successful battle match, the user can play a first video of interest via the video playback window. After a successful match, the video playback window is immediately closed, meaning that even if a match is successful, the user may not be able to finish playing the first video of interest. Therefore, in order to allow the user to continue watching the first video after the battle ends and to avoid having to re-search for the first video and adjust its playback progress, in one possible embodiment, the terminal can retrieve the playback progress of the first video in the video playback window after receiving a battle command, thereby allowing the playback process of the first video to resume after the battle ends.

[0062] For example, if the terminal receives a battle command and the first video has played up to 1 minute 30 seconds, the playback progress is 00:01:30.

[0063] Furthermore, the step of recording the playback progress of the first video after the terminal receives a battle command may be performed simultaneously with the step of closing the video playback window.

[0064] In step 306, if a battle end command is received, the video playback window is opened, and the first video is played in the video playback window based on the playback progress.

[0065] To improve the efficiency of the user's continued viewing of the first video, in one possible embodiment, when the terminal receives a battle end command, it opens a video playback window and plays the first video again in the first video playback window, avoiding a situation where the user needs to switch to an out-of-battle scene interface where a video playback resource corresponding to the first video exists. Here, the battle end command may be triggered by the server at the end of the battle, or it may be manually triggered by the user during the battle (i.e., by ending the battle midway), and the embodiments of the present application are not limited thereto.

[0066] Optionally, before entering battle, the terminal has already recorded the playback progress of the first video, so in one possible embodiment, to avoid the user needing to further adjust the video playback progress in the video playback window or to repeatedly watch a portion of the video clip in the first video, the video playback progress of the first video is resumed in the video playback window.

[0067] In step 307, if a spectator order is received, the battle observation interface is displayed and the video playback window is closed.

[0068] Optionally, a battle interface can also be a battle observation interface, which refers to an interface for watching other users battle.

[0069] In one possible embodiment, if a user needs to watch a friend's battle process, they can tap the spectator control. In response, after receiving the spectator command, the device enters the battle observation interface and simultaneously closes the video playback window.

[0070] In step 308, if a spectator order is received, the playback progress of the first video in the video playback window is obtained.

[0071] To allow users to continue watching the first video after they have finished watching, and to avoid the need to re-search for the first video and adjust its playback progress, in one possible embodiment, after the terminal receives a viewing command, it may also obtain the playback progress of the first video in the video playback window, thereby allowing the playback process of the first video to be resumed after viewing has finished.

[0072] Furthermore, the step of recording the playback progress of the first video after the terminal receives the viewing order may be performed simultaneously with the step of closing the video playback window.

[0073] In step 309, if a command to end viewing is received, the video playback window is opened, and the first video is played in the video playback window based on the playback progress.

[0074] To improve the efficiency of users re-viewing the first video, in one possible embodiment, after the terminal receives a battle end command, it opens a video playback window and plays the first video again in the first video playback window, thereby avoiding a situation where the user needs to switch to an out-of-battle scene interface where a video playback resource corresponding to the first video exists. Here, the spectator end command may be triggered by the server at the end of the battle, or it may be manually triggered by the user during the battle (i.e., by ending spectating midway), and the embodiments of the present application are not limited thereto.

[0075] Optionally, since the terminal has already recorded the playback progress of the first video before viewing, in one possible embodiment, to avoid the user needing to further adjust the video playback progress in the video playback window or to repeatedly view a portion of a partial video clip in the first video, the video playback progress of the first video is resumed in the video playback window.

[0076] In this embodiment, since the video playback window is a playback component provided within the game application itself, the video playback window can obtain video resources from the game application, and at the same time, in order to avoid the video playback window affecting the game application itself, the video playback window can be closed autonomously when the game enters the main process (battle process).

[0077] Furthermore, by recording the current playback progress of the video before entering a battle, it becomes possible to continue generating any videos that could not be completed before entering the battle based on the recorded playback progress at the end of the subsequent battle. This eliminates the need to re-search for videos or manually adjust the playback progress after the battle ends, thus improving the convenience of video playback.

[0078] Since the video playback window is a playback component provided within the game application itself, the video playback window has the authority to retrieve video resources from the game application. Therefore, in one possible embodiment, the user can switch between different videos directly through the video playback window, thereby eliminating the need to return to the original out-of-battle scene interface and re-select video resources, thus improving video switching efficiency.

[0079] Referring to Figure 7, which is a flowchart of a video playback method according to another exemplary embodiment of the present invention, the method, as an example, describes a case where the implementing entity of the method is a terminal, and includes the following steps.

[0080] In step 701, if a video playback resource for the first video exists in the non-battle scene interface, a windowed playback control is displayed in the non-battle scene interface, and the non-battle scene interface is a scene interface outside of the battle.

[0081] In step 702, in response to a trigger operation on the windowed playback control in the non-battle scene interface, the first video stream and first video-related information corresponding to the first video are obtained via the video call interface.

[0082] In step 703, the first video is played in the video playback window based on the first video stream and the first video-related information.

[0083] Embodiments of steps 701 to 703 can be found in the above embodiment and will not be described again in this embodiment.

[0084] In step 704, the video switching control is displayed in response to a trigger operation within the video playback window.

[0085] In the process of optionally playing the first video in the video playback window, by default, only the video screen of the first video is displayed in the video playback window, and video-related information such as function controls or video titles is not displayed. In other words, the UI is not displayed in the video playback window by default.

[0086] In one possible embodiment, if a user needs to switch videos, they can tap a video area within the video playback window. In response, the terminal receives a trigger operation within the video playback window and displays video switching controls within the video playback window. Optionally, the terminal can determine whether or not a trigger operation has been received within the video playback window by detecting the position of the operation focus.

[0087] The trigger operation within the video playback window may optionally be a tap, double tap, swipe, or long press, and the embodiments of this application are not limited to such trigger operations.

[0088] Optionally, the video switching control can be used to switch to the next video or to switch to the previous video.

[0089] In one possible embodiment, the first video-related information may include a video list, and in response to a trigger operation in the video playback window, the terminal displays a video switching control based on the video list. Here, if the video list indicates that there is a video preceding the video corresponding to the first video, the first video switching control (used to switch to the previous video) is set to a triggerable state; if the video list indicates that there is no video preceding the video corresponding to the first video, the first video switching control is set to a non-triggerable state; if the video list indicates that there is a video following the video corresponding to the first video, the second video switching control (used to switch to the next video) is set to a triggerable state; and if the video list indicates that there is no video following the video corresponding to the first video, the second video switching control is set to a non-triggerable state. As shown in Figure 8, Figure 8 is a schematic diagram of the video switching process according to one exemplary embodiment of the present invention. The out-of-battle scene interface 801 displays a video playback window 802, and the video playback window 802 displays a video switching control 803. When the user taps the video switching control 803, the device receives the trigger operation of the video switching control 803 and decides to switch to the next video, thus allowing the playback of video 804 directly in the video playback window 802.

[0090] Optionally, the video playback window may also display video switching controls, as well as video title, author information, and other information related to the first video. Furthermore, it may also display controls such as a windowed playback end control, a window close control, a pause / play control, and a playback adjustment control. The embodiments of this application do not limit the functional controls displayed in the video playback window.

[0091] In step 705, in response to a trigger operation on the video switching control, the video playback window switches to playing the second video.

[0092] The difference from the picture-in-picture mode built into the terminal system itself is that the video playback window in the embodiment of the present invention is provided with a video switching function. In one possible embodiment, if the user needs to switch to the next or previous video, they can directly tap the video switching control in the video playback window, and in response, the terminal can receive the trigger operation of the video switching control and switch to playback of the second video in the video playback window.

[0093] The video playback window in this application has the authority to obtain video resources from the game application, and therefore the video playback window can obtain video resources after they have been switched by a video switching command. In one exemplary example, step 705 may further include steps 705A to 705C.

[0094] In step 705A, in response to a trigger operation on the video switching control, a video switching command is sent via the video calling interface, and the video switching command is used to obtain the second video stream and second video-related information corresponding to the second video.

[0095] In one possible embodiment, when a terminal receives a trigger operation for a video switching control, it determines the video information to be switched and further sends a video switching command via a video calling interface. The video switching command is used to obtain video resources corresponding to the video to be switched, i.e., a second video stream and second video-related information corresponding to the second video.

[0096] Optionally, when playing an online video, a video switching command is sent to the server via the target application video call interface; when playing a local video, a video switching command is sent to the local video management server via the target application video call interface.

[0097] In step 705B, the second video stream and second video-related information are obtained via the video calling interface.

[0098] In one possible embodiment, the terminal transmits the acquired second video stream and second video-related information to the playback component corresponding to the video playback window via the video call interface, so that the video playback window can directly display the switched second video.

[0099] In step 705C, the second video is played in the video playback window based on the second video stream and the second video-related information.

[0100] In one possible embodiment, the second video is played in the video playback window based on the second video stream, and second video-related information corresponding to the second video is displayed.

[0101] Optionally, if the video playback window has not received the second video-related information, it will not display the second video-related information accordingly.

[0102] In step 706, if the user switches from the non-battle scene interface to the battle interface, the video playback window is closed.

[0103] Embodiments of step 706 can be found in the embodiments described above, and will not be repeated in these embodiments.

[0104] In this embodiment, the video playback window has the authority to acquire video resources within the game. Accordingly, the video playback window is equipped with a video switching control. This eliminates the need for the user to close the video playback window, re-select another video, and play it in the video playback window. Instead, the user can directly switch to playing another video in the video playback window, improving the efficiency of video switching and further enhancing the efficiency of video playback in the game.

[0105] To prevent the video playback window from blocking the out-of-battle scene interface, when a terminal invokes the video playback window, it defaults to appearing in the corner area of ​​the screen, and to accommodate different terminals, the window size of the video playback window is determined by the display screen size corresponding to the current terminal.

[0106] Referring to Figure 9, Figure 9 is a flowchart of a video playback method according to another exemplary embodiment of the present application. As an example, if the implementing entity of the method is a terminal, the method includes the following steps:

[0107] In step 901, if a video playback resource for the first video exists in the non-battle scene interface, a windowed playback control is displayed in the non-battle scene interface, and the non-battle scene interface is a scene interface outside of the match.

[0108] Embodiments of step 901 can be found in the embodiments described above, and will not be repeated in these embodiments.

[0109] In step 902, in response to a trigger operation on the windowed playback control in the non-battle scene interface, the first window size and first window position of the video playback window are determined, with different display screen sizes corresponding to different first window sizes, and the first window size being smaller than the display screen size.

[0110] In one possible embodiment, when a terminal receives a trigger operation for a windowed playback control in an out-of-battle scene interface, it can determine a first window size and a first window position of the video playback window, thereby displaying the video playback window based on the window size and window position.

[0111] To minimize the video playback window's obstruction of the out-of-battle scene interface and further reduce the impact on user actions within the out-of-battle scene interface during video playback, the first window size of the video playback window must match the terminal's current display screen size, resulting in the first window size being smaller than the display screen size. Therefore, when the terminal displays the out-of-battle scene interface in full screen, the video playback window can reduce the obstruction of the out-of-battle scene interface.

[0112] Optionally, when a user invokes a video playback window, the video playback window may default to adopting the minimum window size. Optionally, the minimum window size may be set by the developer, and different first window sizes may be set for devices with different display screen sizes to accommodate different devices. Optionally, the device may adjust the first window size based on its own display screen size.

[0113] For example, the first window size can be set to 1 / 8 of the display screen size.

[0114] Since function controls within the out-of-battle scene interface are generally displayed closer to the center of the interface, in one possible embodiment, to avoid the video playback window blocking the function controls within the out-of-battle scene interface and thus influencing the user's ability to perform related operations within the out-of-battle scene interface, the video playback window is displayed by default in the corner area of ​​the terminal display screen, and the first window position of the video playback window may be in the upper left corner area, upper right corner area, lower left corner area, and lower right corner area of ​​the display screen, etc.

[0115] Since the video playback window and the out-of-battle scene interface are both optionally controlled by the target application, the target application can intelligently determine the main control position within the current out-of-battle scene interface and also display the video playback window in a display area that does not block the main control position.

[0116] In step 903, the video playback window is displayed on a higher layer of the non-battle scene interface based on the size and position of the first window.

[0117] In one possible embodiment, after the terminal determines the first window size and first window position of the video playback window, the video playback window can be displayed on a higher layer of the out-of-battle scene interface. For example, if the terminal determines that the first window size is 300px x 600px and the first window position is the lower left corner of the display screen, it displays a video playback window of size 300px x 500px in the lower left corner area of ​​the display screen and plays the first video in the video playback window.

[0118] As shown in Figure 10, Figure 10 is a schematic diagram of the display position of the video playback window according to one exemplary embodiment of the present invention. The terminal may display the video playback window 1001 in the upper left corner of the non-battle scene interface 1000 (upper left corner of the terminal display screen), the video playback window 1002 in the upper right corner of the non-battle scene interface 1000 (upper right corner of the terminal display screen), the video playback window 1003 in the lower left corner of the non-battle scene interface 1000 (lower left corner of the terminal display screen), or the video playback window 1004 in the lower right corner of the non-battle scene interface 1000 (lower right corner of the terminal display screen).

[0119] In step 904, in response to a gesture operation on the video playback window, the window scaling ratio is determined based on the gesture operation.

[0120] To meet the viewing needs of users with different video playback window sizes, in one possible embodiment, the user is allowed to manually scale the video playback window, and in response, the terminal can receive gesture operations on the video playback window, determine the window scaling ratio based on the gesture operations, and further change the window size of the video playback window.

[0121] Here, the gesture operation can be a double-contact gesture operation, where the video playback window is enlarged by moving two fingers apart, and the video playback window is reduced by moving two fingers together.

[0122] Regarding the process of determining the window scaling ratio based on gesture operations, in one possible embodiment, if multiple touch signals are detected within the video playback window, the terminal monitors the ratio of the change in distance between the contact points corresponding to the touch signals in real time, and further determines the current window scaling ratio based on the relationship between the ratio of the change in distance and the scaling ratio.

[0123] Optionally, the relationship between the distance change ratio and the window scaling ratio is pre-configured for each terminal.

[0124] In step 905, the second window size is determined based on the first window size and the window scaling ratio.

[0125] In one possible embodiment, after determining the window scaling ratio, the second window size of the video playback window can be updated in real time based on the first window size.

[0126] For example, if the window scaling ratio is "20% enlargement" and the first window size is 300px x 500px, the corresponding second window size will be 360px x 600px.

[0127] In the process of selectively scaling the video playback window, in order to avoid the video playback window becoming too large to exceed the area of ​​the display screen or blocking a large portion of the non-battle scene interface, and to avoid the video playback window becoming too small to affect the user's video viewing experience or to avoid user interaction with the video playback window, in one possible embodiment, a first window size threshold and a second window size threshold are set, and the second window size must be greater than or equal to the first window size threshold and less than or equal to the second window size threshold.

[0128] Here, the first and second window size thresholds are set by the developer. Optionally, different first and second window size thresholds can be set for different types of devices. For example, the first window size threshold could be 210px, indicating that the minimum width of the video playback window is 210px or greater, and the second window size threshold could be 670px, indicating that the maximum width of the video playback window is 670px or less.

[0129] In step 906, the video playback window is displayed on a higher layer of the non-battle scene interface based on the second window size and the first window position.

[0130] In one possible embodiment, the size of the video playback window is scaled in response to a target gesture operation, and when the target gesture operation is completed, the terminal displays the video playback window at the first window position with the updated second window size.

[0131] As shown in Figure 11, Figure 11 is a schematic diagram of the video playback window enlargement process according to one exemplary embodiment of the present invention. A video playback window 1102 is displayed in the lower left corner of the out-of-battle scene interface 1101, and when the terminal receives an enlarge gesture operation (two fingers separated from each other along the direction of the arrow) on the video playback window, the video playback window 1102 is enlarged by the enlarge gesture until it is updated to a video playback window 1103.

[0132] As shown in Figure 12, Figure 12 is a schematic diagram of the process of shrinking a video playback window according to one exemplary embodiment of the present invention. A video playback window 1202 is displayed in the lower left corner of the out-of-battle scene interface 1201, and when the terminal receives a shrink gesture operation (two fingers moving closer to each other along the direction of the arrow) for the video playback window, the video playback window 1202 is shrunk by the shrink gesture operation until it is updated to the video playback window 1203.

[0133] In step 907, if the user switches from the non-battle scene interface to the battle interface, the video playback window is closed.

[0134] Embodiments of step 907 can be found by referring to the embodiments described above, and will not be repeated in these embodiments.

[0135] In this embodiment, the user can customize the window size of the video playback window. By enlarging and shrinking the window size using target gestures, the video playback window can be adapted to different devices while simultaneously meeting the different user needs regarding the window size of the video playback window, thus fulfilling personalized needs for video playback during games.

[0136] In some possible application scenarios, the video playback window displays video-related function controls, such as video switching controls, pause / play controls, replay controls, and playback progress adjustment controls. Therefore, when adjusting the window size of the video playback window, the usability of each function control must also be considered.

[0137] Optionally, after the terminal determines the window size of the video playback window after scaling, it can further determine the control size of each function control based on the second window size, thereby adjusting the control size of the function controls to match the current window size of the video playback window.

[0138] Here, the control size has a positive correlation with the second window size. That is, when the video playback window is enlarged, the control size of the function controls also increases, and when the video playback window is reduced, the control size of the function controls also decreases.

[0139] Optionally, different functional controls may support different control sizes or the same control size.

[0140] Optionally, a control size threshold can be set to avoid situations where the control size is too small and therefore unhelpful to the user in the video playback window. That is, the control size must be greater than the control size threshold. For example, the control size threshold is 20px, and the minimum control width of a display function control must be greater than 20px.

[0141] In one possible embodiment, after the video playback window size is updated to the second window size, the video playback window does not display function controls by default. After the terminal receives a trigger operation on the video playback window, each function control can be displayed in the video playback window based on the target control size.

[0142] Optionally, the video playback window may also display video-related information, such as the video title. Therefore, during the window resizing process of the video playback window, the number of words in the displayed video title also adjusts to the window size. Here, the larger the window size, the more words are displayed, and conversely, the smaller the window size, the fewer words are displayed.

[0143] As shown in Figure 13, Figure 13 is a schematic diagram of the process for updating the control size corresponding to a function control according to one exemplary embodiment of the present invention. The out-of-battle scene interface 1301 displays a video playback window 1302, and the video playback window 1302 displays a video title 1303 and a function control 1304. After an enlargement operation is performed on the video playback window 1302, the number of title words in the video title 1303 displayed in the video playback window 1302 increases, and the control size of the function control 1304 increases.

[0144] To prevent the video playback window from blocking the out-of-battle scene interface, allow users to manually drag and change the display position of the video playback window.

[0145] Referring to Figure 14, Figure 14 is a flowchart of a video playback method according to another exemplary embodiment of the present application. As an example, if the implementing entity of the method is a terminal, the method includes the following steps:

[0146] In step 1401, if a video playback resource for the first video exists in the non-battle scene interface, a windowed playback control is displayed in the non-battle scene interface, and the non-battle scene interface is a scene interface outside of the match.

[0147] In step 1402, in response to a trigger operation on the windowed playback control in the non-battle scene interface, the first window size and first window position of the video playback window are determined, with different display screen sizes corresponding to different first window sizes, and the first window size being smaller than the display screen size.

[0148] In step 1403, the video playback window is displayed on a higher layer of the non-battle scene interface based on the size and position of the first window.

[0149] Embodiments of steps 1401 to 1403 can be found in the above embodiment and will not be described again in this embodiment.

[0150] In step 1404, in response to a drag operation on the video playback window, the second window position of the video playback window is determined based on the drag operation.

[0151] In one possible embodiment, the video playback window is displayed by default in the corner area of ​​the screen, and when the video playback window blocks a function control in the out-of-battle scene interface, the user can drag the video playback window to update its display position, and in response, the terminal receives the drag operation on the video playback window and determines a second window position for the video playback window based on the drag operation.

[0152] Optionally, the video playback window displays the position it will be at when the drag operation is stopped during dragging, or determines the screen corner area that the video playback window should currently display based on the request that the video playback window be displayed in the screen corner area. In one exemplary example, step 1404 may further include steps 1404A and 1404B.

[0153] In step 1404A, in response to a drag operation on the video playback window, the coordinates of the center position of the video playback window when the drag operation is stopped are determined, and the video playback window moves according to the drag operation.

[0154] In one possible embodiment, after the terminal receives a drag operation on the video playback window, it is necessary to determine the touch position of the drag operation in real time and update the position of the video playback window based on the touch position; that is, the video playback window moves in response to the drag operation. When the drag operation stops, it is necessary to determine which screen corner area the video playback window will be displayed in, obtain the center position coordinates of the video playback window at the time the drag operation stops, and then determine which screen corner area the video playback window will be snapped to based on the quadrant in which the center position coordinates are located.

[0155] In step 1404B, the position of the second window corresponding to the video playback window is determined based on the display area where the center position coordinates are located, and the second window position is located at the screen corner position corresponding to the display area.

[0156] Here, the terminal's central position is used as the coordinate origin, and the terminal's display screen area is divided into four quadrants, i.e., four candidate display areas.

[0157] In one possible embodiment, after determining the center coordinates of the video playback window, the target quadrant (display area) where the center coordinates are located is determined, and the video playback window is displayed at the screen corner position corresponding to the target display area.

[0158] As shown in Figure 15, Figure 15 is a schematic diagram of the window position update process of a video playback window according to one exemplary embodiment of the present invention. The out-of-battle scene interface 1501 displays a video playback window 1502, and when the user drags the video playback window 1502 along the direction of the arrow, the center position 1503 of the video playback window is located in the upper right display area 1504 of the terminal display screen, and correspondingly, the video playback window 1505 is displayed in the corner area of ​​the upper right corner of the screen.

[0159] As shown in Figure 16, Figure 16 is a schematic diagram of the window position update process of a video playback window according to another exemplary embodiment of the present invention. The out-of-battle scene interface 1601 displays a video playback window 1602, and when the user drags the video playback window 1602 along the direction of the arrow, the center position 1603 of the video playback window is located in the lower left display area 1604 of the terminal display screen, and accordingly the video playback window 1605 is displayed in the corner area of ​​the lower left corner of the screen. Therefore, even if the video playback window is dragged outside the display screen, as long as the center position coordinates are located within the aforementioned quadrant, the video playback window is determined to have been dragged to the lower left display area, and accordingly it is displayed in the lower left corner of the screen.

[0160] In step 1405, the video playback window is displayed on a higher layer of the non-battle scene interface based on the second window position and the first window size.

[0161] In one possible embodiment, after the terminal determines the second window position, a video playback window the size of the first window is displayed at the display position indicated by the second window position.

[0162] In step 1406, if the user switches from the non-battle scene interface to the battle interface, the video playback window is closed.

[0163] The embodiment of step 1406 can be found in the embodiments described above, and will not be repeated in this embodiment.

[0164] In this embodiment, a function is provided that allows the user to change the display position of the video playback window, thereby preventing the video playback window from blocking function controls within the out-of-battle scene interface, as the video playback window changes in response to user drag operations.

[0165] Unlike conventional video windows that depend on the terminal system, the video window continues to be displayed even when the application to which the video within the video window belongs is switched from a foreground execution state to a background execution state. In the embodiment of the present invention, since the video playback window depends on the game application, that is, the video playback window is not independent of the game application, when the game application (target application) is switched to background execution, the video playback window also stops displaying accordingly. In one possible embodiment, when the target application is switched from a foreground execution state to a background execution state, the display of the video playback window stops. Here, the target application is a game program that displays an out-of-battle scene interface.

[0166] Optionally, if the target application is switched from background execution to foreground execution, it can continue to play the first video via the video playback window.

[0167] In addition to playing game-related videos via a video playback window during gameplay, in another possible embodiment, game-related videos can also be played in full-screen mode. To meet the needs of users viewing game videos, the full-screen video playback window displays video-related information (video title), pause controls, playback timing controls, countdown controls, a playback progress bar (a draggable progress bar), dotting indicators, and video playback controls (used to switch from full-screen mode to video playback window display mode).

[0168] As shown in Figure 17, Figure 17 is a schematic diagram of a video fullscreen mode according to one exemplary embodiment of the present invention. The video fullscreen display interface 1701 displays video content introducing a new hero, and the progress bar displays a dotting display control 1706, which, when tapped, allows the user to jump directly to the display of the new hero appearance and skill introduction chapter. Optionally, the video fullscreen display interface 1701 further displays a windowed playback control 1702, and the user can display the video playback window 1704 of the video in the out-of-battle scene interface 1703 via the windowed playback control 1702. Optionally, the video playback window 1704 may further display an exit window control 1705, allowing the user to exit the playback mode of playing the video in the video playback window. Optionally, the video playback window 1704 further displays a progress bar and a dotting display control 1706 (scaling).

[0169] Based on the video playback process shown in the above embodiment, Figure 18 shows the video playback module involved in the video playback process. The video playback module comprises a video playback logic module 1801, an interface interaction module 1802, a video decoding module 1803, and a video rendering module 1804. Here, the interface interaction module 1802 includes a full-screen interaction 1805 and a window interaction 1806.

[0170] The video playback logic module 1801 is configured to maintain the video playback interface, manage the interface display level and lifecycle, organize video playback data such as video links, the type of interaction used, and dotting information, and to process related logic such as pause, replay, and video switching.

[0171] The interface interaction module 1802 is configured to complete the display of interaction interfaces such as playback progress, title, and current playback status, and is also configured to complete the reception and response of user interaction information such as controlling playback progress, switching playback status, and switching fullscreen / window interaction modes.

[0172] In one illustrative example, the window scaling process in window interaction mode can be performed as shown in Figure 19. In small window playback mode, when two-finger input is detected on the screen, the current input position is recorded, then the distance change ratio is determined according to the change in distance between the two fingers, and the size of the playback window is updated based on the distance change ratio. If no two-finger input is detected, the cache data is cleared.

[0173] The video decoding module 1803 is configured to decode video streams and can flexibly control switching between hard and soft decoding via a cloud-controlled switch, enabling compatibility with different terminal devices and ensuring decoding efficiency.

[0174] The video rendering module 1804 is configured to update the decoded image frames and display them in the video playback window.

[0175] The following are embodiments of the apparatus of the present application. For details not described in detail in the embodiments of the apparatus, refer to the embodiments of the method described above.

[0176] Figure 20 is a schematic diagram showing the configuration of a video playback device according to one exemplary embodiment of the present invention. The device is If a video playback resource for a first video exists in the non-battle scene interface, a first display module 2001 is configured to display a windowed playback control in the non-battle scene interface, wherein the non-battle scene interface is a scene interface outside of a match, and the first display module 2001 A second display module 2002 is configured to display a video playback window on a higher layer of the out-of-battle scene interface in response to a trigger operation on the windowed playback control in the out-of-battle scene interface, wherein the first video is played back in the video playback window, and the second display module 2002 is configured to display a video playback window on a higher layer of the out-of-battle scene interface, and the first video is played back in the video playback window, The system includes a first control module 2003 configured to close the video playback window when switching from the non-battle scene interface to the battle interface.

[0177] Optionally, the first control module 2003 is: The system includes a first control unit configured to display a battle participation interface and close the video playback window upon receiving a battle command.

[0178] The video playback device may optionally be: The system further includes a first acquisition module that, upon receiving a battle command, acquires the playback progress of the first video in the video playback window. The aforementioned video playback device is The system further includes a first playback module configured to open the video playback window upon receiving a battle end command, and to play the first video in the video playback window based on the playback progress.

[0179] Optionally, the first control module 2003 is: The system includes a second control unit configured to display a battle observation interface and close the video playback window when a spectator order is received.

[0180] The video playback device may optionally be: The system further includes a second acquisition module configured to acquire the playback progress of the first video in the video playback window when a viewing order is received. The aforementioned video playback device is The system further includes a second playback module configured to open the video playback window upon receiving a command to end viewing, and to play the first video in the video playback window based on the playback progress.

[0181] Optionally, the second display module 2002 is: A first acquisition unit is configured to acquire a first video stream and first video-related information corresponding to the first video via a video call interface in response to a trigger operation on the windowed playback control in the out-of-battle scene interface. The system includes a first playback unit configured to play the first video in the video playback window based on the first video stream and the first video-related information.

[0182] The video playback device may optionally be: A third display module configured to display video switching controls in response to a trigger operation within the video playback window, The system further includes a third playback module configured to switch to playback of a second video in the video playback window in response to a trigger operation on the video switching control.

[0183] Optionally, the second playback module is: A transmitting unit configured to send a video switching command via a video call interface in response to a trigger operation for the video switching control, wherein the video switching command is used to obtain a second video stream and second video-related information corresponding to the second video, and the transmitting unit A second acquisition unit configured to acquire the second video stream and the second video-related information via the video call interface, The system includes a second playback unit configured to play the second video in the video playback window based on the second video stream and the second video-related information.

[0184] Optionally, the second display module 2002 is: A first determination unit configured to determine the first window size and first window position of the video playback window in response to a trigger operation on the windowed playback control in the out-of-battle scene interface, wherein different display screen sizes correspond to different first window sizes, and the first window size is smaller than the display screen size, and the first determination unit The system includes a display unit configured to display the video playback window on a higher layer of the out-of-battle scene interface based on the first window size and the first window position.

[0185] The video playback device may optionally be: A first determination module is configured to determine the window scaling ratio based on a gesture operation performed on the video playback window, A second determination module configured to determine a second window size based on the first window size and the window scaling ratio, The system further comprises a fourth display module configured to display the video playback window on a higher layer of the out-of-battle scene interface based on the second window size and the first window position.

[0186] Optionally, the video playback window may display at least one function control corresponding to the first video. The aforementioned video playback device is A third determination module configured to determine the control size of each of the function controls based on the second window size, further comprising a third determination module wherein the control size has a positive correlation with the second window size. The aforementioned video playback device is The system further includes a fifth display module configured to display each of the function controls in the video playback window based on the control size in response to a trigger operation within the video playback window.

[0187] The video playback device may optionally be: A fourth determination module is configured to determine the second window position of the video playback window based on a drag operation performed on the video playback window, in response to the drag operation performed on the video playback window. The system further comprises a sixth display module configured to display the video playback window on a higher layer of the out-of-battle scene interface based on the second window position and the first window size.

[0188] Optionally, the fourth decision module is: A second determination unit is configured to determine the center position coordinates of the video playback window when the drag operation is stopped, in response to a drag operation on the video playback window, wherein the video playback window moves in response to the drag operation, and the second determination unit A third determination unit configured to determine the second window position corresponding to the video playback window based on the display area where the central position coordinates are located, wherein the second window position is located at a screen corner position corresponding to the display area.

[0189] The video playback device may optionally be: A second control module configured to stop displaying the video playback window when the target application is switched from a foreground execution state to a background execution state, wherein the target application is a program for displaying the out-of-battle scene interface, and the second control module The system further includes a third playback module configured to continue playing the first video via the video playback window when the target application is switched from the background execution state to the foreground execution state.

[0190] As described above, in the embodiments of the present invention, by providing a windowed video playback function to the video playback resource in the out-of-battle scene interface, the first video can be played through a video playback window, providing a viable method for the user to play videos during gameplay, and eliminating the need to always maintain a full-screen video playback interface. Furthermore, by playing videos through a video playback window, the impact on the user's related operations in the out-of-battle scene interface during video playback can be reduced, and after entering the battle interface, the video playback window can be closed, simultaneously avoiding any impact of video playback on the game battle process.

[0191] Figure 21 is a schematic diagram showing the configuration of a terminal 2100 according to one exemplary embodiment of the present invention. The terminal 2100 may be a smartphone, tablet computer, MP3 player (Moving Picture Experts Group Audio Layer III), MP4 player (Moving Picture Experts Group Audio Layer IV), notebook computer, or desktop computer. The terminal 2100 may also be referred to by other names such as user device, mobile terminal, laptop terminal, or desktop terminal.

[0192] Typically, terminal 2100 comprises a processor 2101 and memory 2102.

[0193] The processor 2101 may include one or more processing cores, such as a 4-core processor or an 8-core processor. The processor 2101 can be implemented in at least one hardware form from among a Digital Signal Processor (DSP), a Field Programmable Gate Array (FPGA), and a Programmable Logic Array (PLA). The processor 2101 may also include a main processor and a coprocessor. The main processor is a processor used to process data in an active state and is also called a CPU (Central Processing Unit). The coprocessor is a low-power processor used to process data in a standby state. In some embodiments, the processor 2101 may be integrated with a Graphics Processing Unit (GPU), which is used to render and draw content that needs to be displayed on a screen. In some embodiments, the processor 2101 may further include an Artificial Intelligence (AI) processor, which is used to process computational operations related to machine learning.

[0194] The memory 2102 may include one or more computer-readable storage media, which may be non-temporary. The memory 2102 may also include high-speed random-access memory and non-volatile memory, such as one or more magnetic disk storage devices and flash memory storage devices. In some embodiments, the non-temporary computer-readable storage media in the memory 2102 are used to store at least one instruction, which is executed by the processor 2101 to realize a video playback method according to an embodiment of the method of the present application.

[0195] In some embodiments, the terminal 2100 may optionally further include a peripheral interface 2103 and at least one peripheral device. The processor 2101, memory 2102, and peripheral interface 2103 may be connected by a bus or signal lines. Each peripheral device may be connected to the peripheral interface 2103 via a bus, signal lines, or circuit board. Specifically, the peripheral device may include at least one of an RF circuit, a display, an audio circuit, or a power supply.

[0196] The peripheral interface 2103 may be used to connect at least one I / O (Input / Output) related peripheral to the processor 2101 and the memory 2102. In some embodiments, the processor 2101, memory 2102, and peripheral interface 2103 may be integrated on the same chip or circuit board, while in some other embodiments, one or two of the processor 2101, memory 2102, and peripheral interface 2103 may be mounted on separate chips or circuit boards, and this embodiment is not limited thereto.

[0197] Those skilled in the art will understand that the configuration shown in Figure 21 is not limited to terminal 2100 and may include more or fewer components than those shown, or may combine specific components, or employ a different component arrangement.

[0198] Embodiments of the present application further provide a computer-readable storage medium in which at least one instruction, at least one program, code set, or instruction set is stored, and the one instruction, at least one program, code set, or instruction set is loaded and executed by a processor to realize the video playback method provided by each of the above embodiment of the method.

[0199] Embodiments of the present application provide a computer program product, which includes computer instructions, which are stored in a computer-readable storage medium. The processor of a computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, thereby causing the computer device to perform the video playback method provided in the above-described alternative embodiment.

[0200] Those skilled in the art will understand that all or part of the steps of the above embodiments may be performed by hardware, or by program instructions directing the relevant hardware, and that the program may be stored in a computer-readable storage medium, which may be read-only memory, a magnetic disk, or an optical disk, etc.

[0201] The foregoing description is merely an alternative embodiment of the present application and is not intended to limit it. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present application should be included within the scope of protection.

Claims

1. A video playback method performed by a terminal, If a video playback resource for a first video exists in the non-battle scene interface, the step is to display a windowed playback control in the non-battle scene interface, wherein the non-battle scene interface is a scene interface other than the battle scene interface. A step of displaying a video playback window on a higher layer of the out-of-battle scene interface in response to a trigger operation on the windowed playback control in the out-of-battle scene interface, wherein the first video is played in the video playback window. The step of closing the video playback window when switching from the non-battle scene interface to the battle interface is included, The step of displaying a video playback window on a higher layer of the out-of-battle scene interface in response to a trigger operation on the windowed playback control in the out-of-battle scene interface is: A step of determining a first window size and a first window position of a video playback window in response to a trigger operation on the windowed playback control in the out-of-battle scene interface, wherein different display screen sizes correspond to different first window sizes, the first window size is smaller than the display screen size, and the first window position is located at a screen corner position so as to avoid the video playback window blocking a function control in the out-of-battle scene interface. The step of displaying the video playback window on a higher layer of the out-of-battle scene interface based on the first window size and the first window position, If the user switches from the non-battle scene interface to the battle interface, the step of closing the video playback window is performed. When a battle command is received, the process includes the steps of displaying the battle participation interface and closing the video playback window. The aforementioned video playback method is: If a battle command is received, the process further includes the step of obtaining the playback progress of the first video in the video playback window, After closing the aforementioned video playback window, the video playback method is: If a battle end command is received, the further step includes opening the video playback window and playing the first video in the video playback window based on the playback progress, How to play the video.

2. A video playback method performed by a terminal, If a video playback resource for a first video exists in the non-battle scene interface, the step is to display a windowed playback control in the non-battle scene interface, wherein the non-battle scene interface is a scene interface other than the battle scene interface. A step of displaying a video playback window on a higher layer of the out-of-battle scene interface in response to a trigger operation on the windowed playback control in the out-of-battle scene interface, wherein the first video is played in the video playback window. The step of closing the video playback window when switching from the non-battle scene interface to the battle interface is included, The step of displaying a video playback window on a higher layer of the out-of-battle scene interface in response to a trigger operation on the windowed playback control in the out-of-battle scene interface is: A step of determining a first window size and a first window position of a video playback window in response to a trigger operation on the windowed playback control in the out-of-battle scene interface, wherein different display screen sizes correspond to different first window sizes, the first window size is smaller than the display screen size, and the first window position is located at a screen corner position so as to avoid the video playback window blocking a function control in the out-of-battle scene interface. The step of displaying the video playback window on a higher layer of the out-of-battle scene interface based on the first window size and the first window position, If the user switches from the non-battle scene interface to the battle interface, the step of closing the video playback window is performed. When a spectator order is received, the system includes the steps of displaying the battle observation interface and closing the video playback window. The aforementioned video playback method is: If a viewing order is received, the further step includes obtaining the playback progress of the first video in the video playback window, After closing the aforementioned video playback window, the video playback method is: If a command to end viewing is received, the system further includes the steps of opening the video playback window and playing the first video in the video playback window based on the playback progress, How to play the video.

3. The step of displaying a video playback window on a higher layer of the out-of-battle scene interface in response to a trigger operation on the windowed playback control in the out-of-battle scene interface is: In response to a trigger operation on the windowed playback control in the non-battle scene interface, the steps include obtaining a first video stream and first video-related information corresponding to the first video via the video call interface; The process includes the step of playing the first video in the video playback window based on the first video stream and the first video-related information, The video playback method according to claim 1.

4. The aforementioned video playback method is: The steps include: displaying a video switching control in response to a trigger operation within the video playback window; The further step includes switching to playback of a second video in the video playback window in response to a trigger operation on the video switching control, The video playback method according to claim 1.

5. The step of switching to playback of the second video in the video playback window in response to a trigger operation on the video switching control is: The steps include: sending a video switching command via a video call interface in response to a trigger operation on the video switching control, wherein the video switching command is used to obtain a second video stream and second video-related information corresponding to the second video; The steps include obtaining the second video stream and the second video-related information via the video calling interface, The process includes the step of playing the second video in the video playback window based on the second video stream and the second video-related information, The video playback method according to claim 4.

6. Based on the first window size and the first window position, the video playback window is displayed on a higher layer of the non-battle scene interface, and then the video playback method is: In response to a gesture operation on the video playback window, the steps include determining the window scaling ratio based on the gesture operation, A step of determining a second window size based on the first window size and the window scaling ratio, The further step includes displaying the video playback window on a higher layer of the out-of-battle scene interface based on the second window size and the first window position, The video playback method according to claim 1.

7. The video playback window displays at least one of the function controls corresponding to the first video. After determining the second window size based on the first window size and the window scaling ratio, the video playback method proceeds as follows: A step of determining the control size of each of the function controls based on the second window size, further comprising the step of having the control size positively correlated with the second window size, Based on the second window size and the first window position, the video playback window is displayed on a higher layer of the non-battle scene interface, and then the video playback method is: The further step includes displaying each of the function controls in the video playback window based on the control size in response to a trigger operation in the video playback window, The video playback method according to claim 6.

8. Based on the first window size and the first window position, the video playback window is displayed on a higher layer of the non-battle scene interface, and then the video playback method is: In response to a drag operation on the video playback window, the step of determining the second window position of the video playback window based on the drag operation, The further step includes displaying the video playback window on a higher layer of the out-of-battle scene interface based on the second window position and the first window size, The video playback method according to claim 1.

9. A video playback method performed by a terminal, If a video playback resource for a first video exists in the non-battle scene interface, the step is to display a windowed playback control in the non-battle scene interface, wherein the non-battle scene interface is a scene interface other than the battle scene interface. A step of displaying a video playback window on a higher layer of the out-of-battle scene interface in response to a trigger operation on the windowed playback control in the out-of-battle scene interface, wherein the first video is played in the video playback window. The step of closing the video playback window when switching from the non-battle scene interface to the battle interface is included, The step of displaying a video playback window on a higher layer of the out-of-battle scene interface in response to a trigger operation on the windowed playback control in the out-of-battle scene interface is: A step of determining a first window size and a first window position of a video playback window in response to a trigger operation on the windowed playback control in the out-of-battle scene interface, wherein different display screen sizes correspond to different first window sizes, the first window size is smaller than the display screen size, and the first window position is located at a screen corner position so as to avoid the video playback window blocking a function control in the out-of-battle scene interface. The step of displaying the video playback window on a higher layer of the out-of-battle scene interface based on the first window size and the first window position, Based on the first window size and the first window position, the video playback window is displayed on a higher layer of the non-battle scene interface, and then the video playback method is: In response to a drag operation on the video playback window, the step of determining the second window position of the video playback window based on the drag operation, The further step includes displaying the video playback window on a higher layer of the out-of-battle scene interface based on the second window position and the first window size, The step of determining the second window position of the video playback window based on a drag operation performed on the video playback window is as follows: A step of determining the center position coordinates of the video playback window when the drag operation is stopped, in response to a drag operation on the video playback window, wherein the video playback window moves in response to the drag operation. A step of determining the second window position corresponding to the video playback window based on the display area where the central position coordinates are located, wherein the second window position is located at a second screen corner position corresponding to the display area such that the entire video playback window remains on the display screen even if the video playback window is dragged outside the display screen, How to play the video.

10. In response to a trigger operation on the windowed playback control within the out-of-battle scene interface, the video playback window is displayed on a higher layer of the out-of-battle scene interface, and then the video playback method The steps include: stopping the display of the video playback window when the target application is switched from a foreground execution state to a background execution state, wherein the target application is a program for displaying the out-of-battle scene interface; If the target application is switched from the background execution state to the foreground execution state, the step of continuing to play the first video through the video playback window further includes, The video playback method according to claim 1.

11. A terminal comprising a processor and memory storing at least one program, wherein the at least one program is loaded and executed by the processor to realize the video playback method according to any one of claims 1 to 10.

12. A computer program that includes computer instructions stored in a computer-readable storage medium, wherein a processor reads the computer instructions from the computer-readable storage medium and executes them to realize the video playback method according to any one of claims 1 to 10.

Images