Display device and file presentation method

Abstract

The embodiment of the present application provides a display device and a file display method. The display device provided by the embodiment comprises at least a display and a controller. In the case of connecting an external memory, the display displays a first interface, the first interface comprises at least a first area, the first area is used for displaying a history window of a file playback progress stored in the external memory, and each history window corresponds to a file. In response to a confirmation operation on the history window, the file corresponding to the history window is continuously displayed from the playback progress recorded by the history window. The user does not need to manually adjust the playback progress, and the user experience is better.

Description

Technical Field

[0001] The present disclosure relates to the technical field of smart televisions, and in particular to a display device and a file display method. Background Art

[0002] Display devices have attracted widespread attention due to their ability to provide users with functions such as audio and video data playback. For example, a display device can play media files, which may include, but are not limited to, video and audio files. To enable the display device to play a wider range of media files, a memory device can be connected to the display device (in this application, the memory device connected to the display device may be referred to as an external memory device), and the display device can play media files stored in the external memory device.

[0003] Typically, users store multiple files of different types in an external storage device. After browsing files in a media center, it is difficult for users to remember the files they have browsed and viewed. In particular, video files take a long time to watch, and it is difficult for users to locate the files they have watched, resulting in a poor user experience. Summary of the Invention

[0004] Based on the above technical problems, the object of the present invention is to provide a display device and a file display method to solve the problems existing in existing display devices.

[0005] A first aspect of an embodiment of the present application provides a display device, including:

[0006] monitor;

[0007] The controller is configured as:

[0008] When the external storage device is connected, the display is controlled to display a first interface, wherein the first interface includes at least a first area, wherein the first area is used to display a history window of the playback progress of files stored in the external storage device, each history window corresponding to a file;

[0009] In response to a confirmation operation on the history window, the display is controlled to continue displaying the file corresponding to the history window, starting from the playback progress recorded in the history window.

[0010] In conjunction with a first feasible implementation of the first aspect, the controller is further configured to:

[0011] In response to turning on the external memory, reading an identification bit of a history switch;

[0012] If the state corresponding to the flag is on, controlling the display to display the first interface;

[0013] If the state corresponding to the identification bit is the off state, the display is controlled to display a second interface, and the second interface is used to display all files stored in the external memory.

[0014] In conjunction with the second feasible implementation manner of the first aspect, the controller is further configured to:

[0015] Read the selected file type;

[0016] If the file type is a preset type, read the flag of the history switch;

[0017] If the file type is not a preset type, the display is controlled to display files that meet the file type.

[0018] In combination with the third feasible implementation of the first aspect, the first interface also includes a second area, and the second area is used to display files that meet the preset type.

[0019] In conjunction with the fourth feasible implementation manner of the first aspect, if the state corresponding to the flag bit is an on state, the controller is further configured to:

[0020] Count the number of playback progress;

[0021] If the number of the playback progress is less than or equal to a preset number, the first area is controlled to display the history windows corresponding to all the playback progress.

[0022] In conjunction with a fifth feasible implementation of the first aspect, the controller is further configured to:

[0023] If the number of playback progresses is greater than a preset number, controlling the first area to display history windows and extension controls corresponding to N-1 playback progresses, where N is a preset number;

[0024] In response to a confirmation operation on the extension control, the content displayed on the display is controlled to jump from the first interface to the third interface, and the third interface is used to display the history window corresponding to the entire playback progress.

[0025] In conjunction with a sixth feasible implementation manner of the first aspect, if the display displays a third interface, the controller is further configured to:

[0026] In response to an operation of invoking a delete drop-down box, controlling the display to display the delete drop-down box, wherein the delete drop-down box includes a multi-select control;

[0027] In response to a confirmation operation on the multi-select control, a selected control is added to each of the history windows.

[0028] In conjunction with the seventh feasible implementation manner of the first aspect, the delete drop-down box further includes a delete all control; and the controller is further configured to:

[0029] In response to a confirmation operation on the delete all control, all play progress is deleted.

[0030] In conjunction with an eighth feasible implementation manner of the first aspect, the controller is further configured to:

[0031] In response to closing the file, reading the flag of the history switch;

[0032] If the state corresponding to the flag is open, read the playback progress of the closed file;

[0033] If the state corresponding to the flag is a closed state, the playback progress of the closed file is not read.

[0034] The display device provided in this embodiment includes at least a display and a controller. When connected to an external storage device, the display displays a first interface. The first interface includes at least a first area for displaying a history window of playback progress of files stored in the external storage device, each of which corresponds to a file. In response to a confirmation operation on a history window, the display continues to display the file corresponding to the history window, starting from the playback progress recorded in the history window. This eliminates the need for users to manually adjust the playback progress, resulting in a better user experience.

[0035] A second aspect of the present application provides a file display method, including:

[0036] When an external storage device is connected, a first interface is displayed, wherein the first interface includes at least a first area, wherein the first area is used to display a history window of the playback progress of files stored in the external storage device, each history window corresponding to a file;

[0037] In response to a confirmation operation on a history window, the file corresponding to the history window continues to be displayed, starting from the playback progress recorded in the history window.

[0038] This embodiment provides a file display method applicable to a display device comprising at least a controller and a display. When connected to an external storage device, the display displays a first interface comprising at least a first area for displaying a history window of playback progress of files stored in the external storage device, each of which corresponds to a file. In response to a confirmation operation on a history window, the display continues displaying the file corresponding to the history window, starting from the playback progress recorded in the history window. This eliminates the need for users to manually adjust the playback progress, resulting in a better user experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0039] In order to more clearly illustrate the technical solution of the present application, the following is a brief introduction to the drawings required for use in the embodiments. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0040] Figure 1 An operation scenario between a display device and a control apparatus according to some embodiments is shown;

[0041] Figure 2 shows a block diagram of a hardware configuration of a control device 100 according to some embodiments;

[0042] Figure 3 shows a hardware configuration block diagram of a display device 200 according to some embodiments;

[0043] Figure 4 shows a software configuration diagram in the display device 200 according to some embodiments;

[0044] Figure 5 A flowchart of the interaction between a display device and a user provided in a feasible embodiment;

[0045] Figure 6 A schematic diagram of a memory interface provided in a feasible embodiment;

[0046] Figure 7 A schematic diagram of a memory interface provided in a feasible embodiment;

[0047] Figure 8 A schematic diagram of a memory interface provided in a feasible embodiment;

[0048] Figure 9 A flowchart of a method for invoking a first interface provided in a feasible embodiment;

[0049] Figure 10 A schematic diagram showing changes in a display interface provided for a feasible implementation method;

[0050] Figure 11 A schematic diagram showing changes in a display interface provided for a feasible implementation method;

[0051] Figure 12 A flowchart of a method for invoking a first interface provided in a feasible embodiment;

[0052] Figure 13 A flowchart of a method for invoking a first interface provided in a feasible embodiment;

[0053] Figure 14A schematic diagram showing changes in a display interface provided for a feasible implementation method;

[0054] Figure 15 A schematic diagram showing changes in a display interface provided for a feasible implementation method;

[0055] Figure 16 A schematic diagram showing changes in a display interface provided for a feasible implementation method;

[0056] Figure 17 A schematic diagram showing changes in a display interface provided for a feasible implementation method;

[0057] Figure 18 A schematic diagram of a first interface provided in a feasible embodiment;

[0058] Figure 19 A schematic diagram of a history window display method provided in a feasible embodiment;

[0059] Figure 20 A schematic diagram showing changes in a display interface provided for a feasible implementation method;

[0060] Figure 21 A schematic diagram showing changes in a display interface provided for a feasible implementation method;

[0061] Figure 22 A schematic diagram of a method for deleting a history window provided in a feasible embodiment;

[0062] Figure 23 A feasible embodiment provides an interface showing a delete drop-down box;

[0063] Figure 24 A feasible embodiment provides an interface showing a selected control;

[0064] Figure 25 A schematic diagram showing changes in a display interface provided for a feasible implementation method;

[0065] Figure 26 A schematic diagram showing changes in a display interface provided for a feasible implementation method;

[0066] Figure 27 A schematic diagram of changes in a display interface provided in a feasible implementation manner. DETAILED DESCRIPTION

[0067] In order to make the purpose and implementation of this application clearer, the exemplary implementation of this application will be clearly and completely described below in conjunction with the drawings in the exemplary embodiments of this application. Obviously, the described exemplary embodiments are only part of the embodiments of this application, not all of the embodiments.

[0068] It should be noted that the brief descriptions of terms in this application are only for the purpose of facilitating the understanding of the embodiments described below, and are not intended to limit the embodiments of this application. Unless otherwise specified, these terms should be understood according to their ordinary and usual meanings.

[0069] In the specification and claims of this application and the accompanying drawings, the terms "first," "second," "third," etc. are used to distinguish similar or similar objects or entities, and are not necessarily intended to limit a particular order or sequence, unless otherwise noted. It should be understood that the terms used in this manner are interchangeable under appropriate circumstances.

[0070] The terms "comprise," "include," and "have," and any variations thereof, are intended to cover but not exclude inclusion; for example, a product or device comprising a list of components is not necessarily limited to all the components expressly listed but may include other components not expressly listed or inherent to such product or device.

[0071] The term "module" refers to any known or later developed hardware, software, firmware, artificial intelligence, fuzzy logic, or combination of hardware and / or software code that is capable of performing the functionality associated with that element.

[0072] Figure 1 Schematic diagram of an operation scenario between a display device and a control device according to an embodiment. Figure 1 As shown, the user can operate the display device 200 through the smart device 300 or the control apparatus 100 .

[0073] In some embodiments, the control device 100 may be a remote controller. Communication between the remote controller and the display device may include infrared protocol communication, Bluetooth protocol communication, or other short-range communication methods, and the display device 200 may be controlled wirelessly or wired. The user may control the display device 200 by inputting user commands through buttons on the remote controller, voice input, control panel input, and the like.

[0074] In some embodiments, a smart device 300 (such as a mobile terminal, tablet computer, computer, laptop computer, etc.) can also be used to control the display device 200. For example, the display device 200 can be controlled using an application running on the smart device.

[0075] In some embodiments, the display device 200 can also be controlled in a manner other than the control device 100 and the smart device 300. For example, the user's voice command control can be directly received through a module for obtaining voice commands configured inside the display device 200, or the user's voice command control can be received through a voice control device set outside the display device 200.

[0076] In some embodiments, the display device 200 also communicates data with the server 400. The display device 200 may be connected to a local area network (LAN), a wireless local area network (WLAN), or other networks. The server 400 may provide various content and interactions to the display device 200. The server 400 may be a single cluster or multiple clusters, and may include one or more types of servers.

[0077] Figure 2 Schematically shows a block diagram of the configuration of the control device 100 according to an exemplary embodiment. Figure 2 As shown, the control device 100 includes a controller 110, a communication interface 130, a user input / output interface 140, a memory, and a power supply. The control device 100 can receive user input operation commands and convert the operation commands into commands that the display device 200 can recognize and respond to, acting as an interaction medium between the user and the display device 200.

[0078] Figure 3 FIG. 2 is a block diagram showing a hardware configuration of the display device 200 according to an exemplary embodiment.

[0079] In some embodiments, the display apparatus 200 includes at least one of a tuner 210 , a communicator 220 , a detector 230 , an external device interface 240 , a controller 250 , a display 260 , an audio output interface 270 , a memory, a power supply, and a user interface.

[0080] In some embodiments, the controller includes a processor, a video processor, an audio processor, a graphics processor, RAM, ROM, and first to nth interfaces for input / output.

[0081] In some embodiments, the display 260 includes a display screen component for presenting images, and a driving component for driving image display, a component for receiving image signals output from a controller, and a component for displaying video content, image content, and a menu control interface and a user control UI interface.

[0082] In some embodiments, the display 260 may be a liquid crystal display, an OLED display, a projection display, or a projection device and a projection screen.

[0083] In some embodiments, the communicator 220 is a component used to communicate with external devices or servers using various communication protocols. For example, the communicator may include at least one of a Wi-Fi module, a Bluetooth module, a wired Ethernet module, or other network communication protocol chip or a near-field communication protocol chip, as well as an infrared receiver. The display device 200 can use the communicator 220 to send and receive control signals and data signals with the external control device 100 or the server 400.

[0084] In some embodiments, the user interface may be configured to receive a control signal from the control device 100 (eg, an infrared remote controller, etc.).

[0085] In some embodiments, detector 230 is used to collect signals from the external environment or external interactions. For example, detector 230 may include a light receiver, such as a sensor for collecting ambient light intensity; or an image collector, such as a camera, for collecting external environmental scenes, user attributes, or user interaction gestures; or a sound collector, such as a microphone, for receiving external sounds.

[0086] In some embodiments, the external device interface 240 may include, but is not limited to, any one or more of the following: a high-definition multimedia interface (HDMI), an analog or digital high-definition component input interface (component), a composite video input interface (CVBS), a USB input interface (USB), an RGB port, etc. It may also be a composite input / output interface formed by multiple of the above interfaces.

[0087] In some embodiments, the tuner-demodulator 210 receives broadcast television signals via wired or wireless reception, and demodulates audio and video signals, such as EPG data signals, from a plurality of wireless or wired broadcast television signals.

[0088] In some embodiments, the controller 250 and the tuner 210 may be located in different separate devices, that is, the tuner 210 may also be located in an external device of the main device where the controller 250 is located, such as an external set-top box.

[0089] In some embodiments, controller 250 controls the operation of the display device and responds to user operations via various software control programs stored in memory. Controller 250 controls the overall operation of display device 200. For example, in response to receiving a user command to select a UI object for display on display 260, controller 250 may perform operations related to the object selected by the user command.

[0090] In some embodiments, the object may be any selectable object, such as a hyperlink, an icon, or other operable control. Operations associated with the selected object include: displaying a page, document, or image connected to the hyperlink, or executing a program corresponding to the icon.

[0091] In some embodiments, the controller includes at least one of a central processing unit (CPU), a video processor, an audio processor, a graphics processing unit (GPU), RAM Random Access Memory (RAM), ROM (Read-Only Memory, ROM), a first interface to an nth interface for input / output, a communication bus (Bus), etc.

[0092] The CPU is used to execute operating system and application instructions stored in memory, as well as various interactive instructions received from external input, to execute various applications, data, and content, ultimately displaying and playing various audio and video content. The CPU can include multiple processors, such as a main processor and one or more sub-processors.

[0093] In some embodiments, a graphics processor is used to generate various graphical objects, such as icons, operation menus, and graphics displayed in response to user input commands. The graphics processor includes an arithmetic unit, which performs operations based on various user interaction commands and displays various objects according to display attributes; and a renderer, which renders the various objects generated by the arithmetic unit. These rendered objects are then displayed on the display.

[0094] In some embodiments, the video processor is used to receive an external video signal and perform video processing such as decompression, decoding, scaling, noise reduction, frame rate conversion, resolution conversion, and image synthesis according to the standard codec protocol of the input signal to obtain a signal that can be directly displayed or played on the display device 200.

[0095] In some embodiments, the video processor includes a demultiplexing module, a video decoding module, an image synthesis module, a frame rate conversion module, a display formatting module, and the like. The demultiplexing module is used to demultiplex the input audio and video data stream. The video decoding module is used to process the demultiplexed video signal, including decoding and scaling processing. The image synthesis module, such as an image synthesizer, is used to superimpose and mix the GUI signal generated by the graphics generator according to user input or itself with the scaled video image to generate an image signal for display. The frame rate conversion module is used to convert the input video frame rate. The display formatting module is used to receive the frame rate converted video output signal and change the signal to conform to the display format signal, such as outputting an RGB data signal.

[0096] In some embodiments, the audio processor is used to receive an external audio signal, perform decompression and decoding according to the standard codec protocol of the input signal, as well as noise reduction, digital-to-analog conversion, and amplification processing to obtain a sound signal that can be played in a speaker.

[0097] In some embodiments, the user may input a user command through a graphical user interface (GUI) displayed on the display 260, and the user input interface receives the user input command through the graphical user interface (GUI). Alternatively, the user may input a user command through a specific sound or gesture, and the user input interface may recognize the sound or gesture through a sensor to receive the user input command.

[0098] In some embodiments, a "user interface" is a medium interface for interaction and information exchange between an application or operating system and a user, which realizes the conversion between the internal form of information and the form acceptable to the user. A common form of user interface is a graphical user interface (GUI), which refers to a user interface related to computer operations that is displayed in a graphical manner. It can be an interface element such as an icon, window, or control displayed on the display screen of an electronic device, where a control can include visual interface elements such as icons, buttons, menus, tabs, text boxes, dialog boxes, status bars, navigation bars, and widgets.

[0099] In some embodiments, the system of the display device may include a kernel, a command parser (shell), a file system, and applications. The kernel, shell, and file system together form the basic operating system structure, which allows users to manage files, run programs, and use the system. After power is turned on, the kernel starts, activates kernel space, abstracts hardware, initializes hardware parameters, runs and maintains virtual memory, schedulers, signals, and inter-process communication (IPC). After the kernel starts, the shell and user applications are loaded. After startup, the application is compiled into machine code to form a process.

[0100] like Figure 4 As shown in the figure, the display device system can include a kernel, a command parser (shell), a file system, and application programs. The kernel, shell, and file system together form the basic operating system structure, allowing users to manage files, run programs, and use the system. After power is applied, the kernel boots up, activates kernel space, abstracts hardware, initializes hardware parameters, and runs and maintains virtual memory, a scheduler, signals, and inter-process communication (IPC). After the kernel boots up, the shell and user applications are loaded. After booting up, the application is compiled into machine code, forming a process.

[0101] like Figure 4 As shown, the system of the display device is divided into three layers, namely the application layer, the middleware layer and the hardware layer from top to bottom.

[0102] The application layer mainly includes commonly used applications on the TV and the application framework. Common applications are mainly browser-based applications, such as HTML5 apps, and native apps.

[0103] The Application Framework is a complete programming model that provides all the basic functions required by standard application software, such as file access, data exchange, etc., as well as the user interfaces for these functions (toolbars, status bars, menus, and dialog boxes).

[0104] Native apps can support online or offline, message push or local resource access.

[0105] The middleware layer includes various TV protocols, multimedia protocols, and system components. Middleware uses the basic services (functions) provided by system software to connect various parts of the application system or different applications on the network, enabling resource and function sharing.

[0106] The hardware layer mainly includes the HAL interface, hardware, and drivers. The HAL interface is a unified interface for all TV chips, and the specific logic is implemented by each chip. Drivers mainly include: audio driver, display driver, Bluetooth driver, camera driver, WiFi driver, USB driver, HDMI driver, sensor driver (such as fingerprint sensor, temperature sensor, pressure sensor, etc.), and power driver.

[0107] To allow the display device to play more media files, it is possible to connect a storage device to the display device, allowing the display device to play media files stored in the external storage device. Typically, users store multiple different types of files in the external storage device. When users browse files in the media center, it is difficult for them to remember which files they have viewed, especially when watching long videos. This makes it difficult for users to locate the files they have viewed, resulting in a poor user experience.

[0108] In order to solve the above technical problems, the present application provides a display device. The structure and functions of each part of the display device can refer to the above embodiments. In addition, based on the display device shown in the above embodiments, this embodiment further optimizes some functions of the display device. For details, please refer to Figure 5 , Figure 5 A flowchart of the interaction between a display device and a user provided in a feasible embodiment;

[0109] The user executes step S51 to insert the external memory;

[0110] The display shows a prompt window. The display method of the prompt window can refer to the conventional prompt window displayed on the display when the external memory is inserted into the display device in this field. The applicant does not make too many restrictions here.

[0111] As an implementation method, when the user clicks on the prompt window, the display can show the memory interface, which is used to show all the files stored in the external memory. At this time, the display interface of the display can refer to Figure 6 . Figure 6 This is a schematic diagram of a memory interface provided in a feasible embodiment. It can be seen that all files stored in the external memory can be displayed. Figure 6 In the illustrated embodiment, the files stored in the external memory include video files 61 , audio files 62 and PDF files 63 .

[0112] As an implementation method, the memory interface is provided with a type control, and the user can control the display content of the memory interface by touching the type control. For an example, please continue to refer to Figure 6 The memory interface includes a type control 64. When the user selects the type control as video, the display interface of the display can refer to Figure 7 , Figure 7 This is a schematic diagram of a memory interface provided in a feasible embodiment. It can be seen that the memory interface can display video files stored in an external memory.

[0113] As an implementation method, the memory interface is provided with a sequence control, and the user can control the display content of the memory interface by touching the sequence control. For an example, please continue to refer to Figure 6 The memory interface includes a sequence control 65. When the user selects the sequence control as a name, the display interface of the display can refer to Figure 8 , Figure 8 This is a schematic diagram of a storage interface provided in a feasible embodiment. It can be seen that the storage interface can display files in a sequence of names (AZ).

[0114] It is worth noting that this embodiment only exemplarily shows the controls included in several memory interfaces. The above controls do not constitute a limitation. In actual application, the controls included in the memory interface can be configured according to needs. The applicant does not make too many limitations here.

[0115] In the case of connecting to an external memory, the controller is configured to execute S52 to control the display to display a first interface, where the first interface at least includes a first area.

[0116] In this embodiment, when the display device is first plugged into an external storage device, the display does not display the first interface. Only when the external storage device is connected again will the controller control the display to display the first interface. The following describes the display process of the first interface in different situations.

[0117] As a feasible implementation, in response to the re-insertion of the external memory, the controller controls the display to display the first interface (the first interface will be described in detail later).

[0118] In order to ensure that the user can independently choose whether to display the first interface, this embodiment also proposes a method for calling the first interface. Figure 9 , Figure 9 This is a flowchart of a method for invoking a first interface according to a feasible embodiment, wherein the controller is configured to execute steps S91-S93;

[0119] The controller is configured to execute step S91 to read the identification bit of the history switch;

[0120] In this embodiment, a history switch can be configured for the display device. The user can control whether the display displays the first interface by turning the history switch on or off. There are many ways for the user to call the history switch. As a feasible implementation method, the user can touch the menu key of the remote control, and the display will display the menu interface, and a history switch control is set on the menu interface. The user can control whether the display displays the first interface by touching the history switch control. For example, if the user turns on the history switch control, the corresponding display displays the first interface; if the user turns off the history switch control, the corresponding display does not display the first interface. As a feasible implementation method, a physical history switch can be configured for the display device. For example, if the user turns on the history switch control, the corresponding display displays the first interface; if the user turns off the history switch control, the corresponding display does not display the first interface. This embodiment only exemplifies two implementation methods of calling the history switch. The above implementation methods do not constitute a limitation. In actual application, the implementation methods of calling the history switch can be, but are not limited to, the above-mentioned methods. The applicant does not make too many limitations here.

[0121] This embodiment does not impose any restrictions on the time when the controller reads the history switch flag. For example, in some feasible implementations, each time a user turns on an external storage device, the controller is triggered to read the history switch flag. For another example, in some feasible implementations, each time the history switch flag changes, the controller is triggered to read the history switch flag.

[0122] The implementation method of the controller reading the historical switch identification bit can refer to the identification bit reading method commonly used in this field, and the applicant does not make too many restrictions here.

[0123] If the state corresponding to the flag is the on state, the controller is configured to execute step S92 to control the display to display the first interface;

[0124] If the state corresponding to the flag is the off state, the controller is configured to execute step S93 to control the display to display a second interface for displaying all files stored in the external memory.

[0125] The following describes the method of accessing the first interface with reference to the accompanying drawings:

[0126] Figure 10 A schematic diagram of changes in the display interface provided by a feasible implementation method. In this embodiment, the history switch is in the on state. The user connects the external storage device to the display device, and a prompt window is displayed on the display. At this time, the display can refer to effect 10-1; the user clicks the prompt window to turn on the external storage device. In response to the activation of the external storage device, the controller reads the identification bit of the history switch. In this embodiment, the state corresponding to the identification bit is the on state, and the controller controls the display to display the first interface; at this time, the display can refer to effect 10-2. It can be seen that the first interface includes: history window 101, history window 102, history window 103, and history window 104.

[0127] Figure 11 A schematic diagram of a display interface change provided for a feasible implementation. In this embodiment, the history switch is in the off state. The user connects the external storage device to the display device, and a prompt window is displayed on the display. At this time, the display can refer to effect 11-1; the user clicks the prompt window to turn on the external storage device. In response to the activation of the external storage device, the controller reads the flag of the history switch. In this embodiment, the flag corresponds to the off state, and the controller controls the display to display the second interface; at this time, the display can refer to effect 11-2. It can be seen that the second interface includes: file 111, file 112, file 113, file 114, file 115, file 116...

[0128] In order to ensure that the user can independently choose whether to display the first interface, this embodiment also proposes a method for calling the first interface. Figure 12 and 13 , Figure 12 This is a flowchart of a method for invoking a first interface provided in a feasible embodiment, wherein the controller is configured to execute steps S121-S123;

[0129] Typically, different types of files can be stored in an external memory. The file types can be, but are not limited to, PDF, video, picture, audio, etc. In this embodiment, the files stored in the external memory are divided into files that conform to preset types and files that do not conform to preset types. Files that conform to preset types include files that can be displayed in segments. As a feasible embodiment, the segmented display can be files that are displayed in segments in time. For example, video type files are files that are displayed in segments in time. As a feasible embodiment, the segmented display can be files that are displayed in segments in space. For example, text type files are files that are displayed in segments in space. Files that do not conform to preset types can be picture type files.

[0130] The controller is configured to execute step 121 to read the selected file type;

[0131] This embodiment does not limit the time when the controller reads the file type. For example, in some feasible implementations, each time the user opens the external storage device, the controller is triggered to read the file type; in another example, in some feasible implementations, the controller is triggered to read the file type when the file type set by the user changes.

[0132] The implementation method of the controller reading the identification bit of the history switch can refer to the conventional file type reading method in this field, and the applicant does not make too many restrictions here.

[0133] If the file type is a preset type, the controller is configured to execute step S122 to read the identification bit of the history switch;

[0134] If the file type is not a preset type, the controller is configured to execute step S123 to control the display to display files that match the file type.

[0135] The following describes the method of accessing the first interface with reference to the accompanying drawings:

[0136] Figure 14 A schematic diagram of changes in the display interface provided for a feasible implementation method. In this embodiment, the history switch is in the on state. The user connects the external storage to the display device, and a prompt window is displayed on the display. At this time, the display can refer to effect 14-1; the user clicks the prompt window to turn on the external storage. In response to the activation of the external storage, the user sets the file type to video, and at this time the display can refer to effect 14-2. (Video is a preset type). The controller continues to read the identification bit of the history switch. The state corresponding to the identification bit in this embodiment is the on state. The controller controls the display to display the first interface. At this time, the display can refer to effect 14-3.

[0137] Figure 15A schematic diagram of changes in the display interface provided for a feasible implementation method. In this embodiment, the history switch is in the off state. The user connects the external memory to the display device, and a prompt window is displayed on the display. At this time, the display can refer to effect 15-1; the user clicks the prompt window to turn on the external memory. In response to the turning on of the external memory, the user sets the file type to picture, and at this time the display can refer to effect 15-2. (Video is a preset type). The controller continues to read the identification bit of the history switch. The state corresponding to the identification bit in this embodiment is the off state. The controller controls the display to display the picture file stored in the external memory; at this time, the display can refer to effect 15-3.

[0138] Figure 13 This is a flowchart of a method for invoking a first interface according to a feasible embodiment, wherein the controller is configured to execute steps S131-S135;

[0139] The controller is configured to execute step 131 to read the identification bit of the history switch;

[0140] This embodiment does not impose any restrictions on the time when the controller reads the file type. For example, in some feasible implementations, each time a user turns on an external storage device, the controller is triggered to read the flag of the history switch. For another example, in some feasible implementations, any change in the history switch set by the user triggers the controller to read the flag of the history switch.

[0141] The implementation method of the controller reading the identification bit of the history switch can refer to the conventional file type reading method in this field, and the applicant does not make too many restrictions here.

[0142] If the state corresponding to the flag is on, the controller is configured to execute step S132 to read the selected file type;

[0143] If the file type is a preset type, the controller is configured to execute step S133 to control the display to display the first interface;

[0144] If the file type is not a preset type, the controller is configured to execute step S134 to control the display to display a second interface for displaying all files stored in the external memory.

[0145] If the state corresponding to the flag is an off state, the controller is configured to execute step S135 without reading the file type.

[0146] The following describes the method of accessing the first interface with reference to the accompanying drawings:

[0147] Figure 16A schematic diagram of changes in the display interface provided for a feasible implementation method. In this embodiment, the history switch is in the on state. The user connects the external memory to the display device, and a prompt window is displayed on the display. At this time, the display can refer to effect 16-1; the user clicks the prompt window to turn on the external memory. In response to the activation of the external memory, the controller continues to read the identification bit of the history switch. The state corresponding to the identification bit in this embodiment is the on state. The controller reads the file type. In this embodiment, the user sets the file type to audio. At this time, the display can refer to effect 16-2. (Audio is a preset type). The controller controls the display to display the first interface; at this time, the display can refer to effect 16-3.

[0148] Figure 17 This is a schematic diagram of the changes in the display interface provided by a feasible implementation method. In this embodiment, the history switch is in the on state. The user connects the external storage device to the display device, and a prompt window is displayed on the display. At this time, the display can refer to effect 17-1; the user clicks the prompt window to turn on the external storage device. In response to the activation of the external storage device, the controller continues to read the identification bit of the history switch. In this embodiment, the state corresponding to the identification bit is the on state. The controller reads the file type. In this embodiment, the user sets the file type to picture. At this time, the display can refer to effect 17-2. The display then displays all the picture files. For details, please refer to effect 17-3.

[0149] In this embodiment, the first area is used to display a history window of the playback progress of files stored in the external memory, and each history window corresponds to a file;

[0150] In this embodiment, the controller can record the playback progress of some preset types of files. The playback progress is used to record the nodes at which the user has watched the file. For example, for a video file, wherein the video file includes 20 episodes of a TV series, and the user has watched 2 episodes of the TV series, then 2 episodes are the playback progress for the video file. For another example, for a video file, wherein the video file is 60 minutes long, and the user has watched 30 minutes, then 30 minutes is the playback progress for the video file. For another example, for a PDF file, wherein the PDF file includes 60 pages, and the user has watched 20 pages, then 20 pages is the playback progress for the PDF file. This embodiment is only an illustrative introduction to several ways of representing the playback progress, and the above-mentioned representation does not constitute a limitation. In actual application, the playback progress can also be represented in other ways.

[0151] This embodiment does not limit the time point at which the controller records the playback progress. For example, as a feasible implementation method, when playing a preset type file, the controller can record a playback progress at intervals, and each time the playback progress record is completed, the newly recorded playback progress replaces the previously recorded playback progress to ensure that for a file, the controller always records a playback progress. As a feasible implementation method, the controller can record the playback record of the preset type file each time it closes the file. In order to reduce the data processing capacity of the controller, as a feasible implementation method, in response to closing a file, the controller can read the identification bit of the history switch; if the state corresponding to the identification bit is the on state, the playback progress of the closed file is read; if the state corresponding to the identification bit is the off state, the playback progress of the closed file is not read.

[0152] The first interface is described below with reference to specific drawings. Figure 18 This is a schematic diagram of a first interface provided in a feasible embodiment. It can be seen that the first interface includes a first area 181, wherein the first area includes 5 history windows.

[0153] As a feasible implementation method, the first interface further includes a second area, and the second area is used to display files that meet the preset type. Figure 18 The first interface also includes a second area 182, which displays 6 video files.

[0154] This embodiment also provides a display method of a history window. The display method of the history window is described below with reference to specific drawings. Figure 19 A schematic diagram of a history window display method provided in a feasible embodiment. If the state corresponding to the flag is on, the controller is further configured to execute steps S191 to S192;

[0155] S191 counts the number of playback progress;

[0156] If the number of the playback progress is less than or equal to the preset number, S192 controls the first area to display the history windows corresponding to all the playback progress.

[0157] This embodiment does not limit the preset number. As a feasible embodiment, the preset number may be N, where N is an integer greater than or equal to 1. As a feasible implementation, the preset number may be determined by the number of history windows that can be displayed in the first area. For example, in a feasible embodiment, if five history windows can be displayed in the first area, the preset number may be equal to 5.

[0158] The following is an explanation of how the history window is displayed with reference to specific figures:

[0159] Figure 20 A schematic diagram of changes in the display interface provided by a feasible implementation method. In this embodiment, the history switch is on. The user connects the external storage device to the display device, and a prompt window is displayed on the display. At this time, the display can refer to effect 20-1; the controller counts the number of playback progress to 5 (the preset number in this embodiment is 5, and the number of playback progress is less than or equal to the preset number); the controller controls the first area to display the history window corresponding to all playback progress. At this time, the display can refer to effect 20-2.

[0160] This embodiment also provides a display method for a history window. The following is an explanation of the display method for the history window with reference to the specific figures. Figure 19 If the number of playback progress is greater than a preset number, the controller is further configured to execute steps S193 to S194;

[0161] S193 controls the first area to display history windows and extension controls corresponding to N-1 playback progresses, where N is a preset number;

[0162] S194 controls the content displayed on the display to jump from the first interface to the third interface in response to the confirmation operation on the extension control, and the third interface is used to display the history window corresponding to the entire playback progress.

[0163] The following is an explanation of how the history window is displayed with reference to specific figures:

[0164] Figure 21 A schematic diagram of the display interface changes provided for a feasible implementation method. In this embodiment, the history switch is in the on state. The user connects the external storage to the display device, and a prompt window is displayed on the display. At this time, the display can refer to the schematic diagram. Figure 21-1 The controller counts the number of playback progress as 12 (the preset number in this embodiment is 5, and the number of playback progress is greater than the preset number); the controller controls the first area to display (5-1) the history window and extension control 211 corresponding to the playback progress. At this time, the display can refer to the schematic diagram. Figure 21-2 The user touches the extended control 211, and the content displayed on the display jumps to the third interface. In this embodiment, the third interface includes 12 history windows. At this time, the display can refer to the schematic diagram. Figure 21-3 .

[0165] As a feasible implementation method, the third interface may only display the first M files of preset types that the user has recently viewed, where M is a positive integer greater than N.

[0166] In order to enhance the user experience and ensure that the user can delete the historical playback window according to his / her will, this embodiment further provides a method for deleting the historical window. The method for deleting the historical window is described below with reference to specific figures. Figure 22 A schematic diagram of a method for deleting a history window provided in a feasible embodiment. If the display shows the third interface, the controller is further configured to execute steps S221 to S222;

[0167] S221: In response to the operation of invoking the delete drop-down box, controlling the display to display the delete drop-down box, wherein the delete drop-down box includes a multi-select control;

[0168] There are multiple ways for a user to call up the delete drop-down box. As a feasible embodiment, in an application scenario where the display shows the third interface, the user can call up the delete drop-down box by touching the menu button of the remote control. As a feasible embodiment, in an application scenario where the display shows the third interface, the user can call up the delete drop-down box by voice. This embodiment only exemplifies two ways of calling up the delete drop-down box. The above two ways do not constitute a limitation. In actual application, the way of calling up the delete drop-down box can be, but is not limited to, the above two ways.

[0169] The following is an explanation of the delete drop-down box with reference to the accompanying drawings. Figure 23 A feasible embodiment provides an interface showing a delete drop-down box. As can be seen from the figure, the delete drop-down box 231 includes a multiple-selection control 2311, a delete all control 2312, and an exit multiple-selection control 2313. This example is only an exemplary description of a delete drop-down box, and the above drop-down box does not constitute a limitation.

[0170] by Figure 23 Taking the delete drop-down box as an example, as a feasible implementation, in response to the user touching the exit multi-select control 2313, the display does not display the delete drop-down box 231. As a feasible implementation, in response to the user touching the delete all control 2312, the display does not display the history window. As a feasible implementation, in response to the user touching the delete all control 2312, the display displays a prompt window, which is used to prompt the user that the display device is about to delete the history window or playback progress.

[0171] S222: In response to the confirmation operation on the multi-select control, a selected control is added to each of the history windows.

[0172] The following is an explanation of the selected control with reference to the specific drawings. Figure 24 A feasible embodiment provides an interface showing a selected control. As can be seen from the figure, each history window is configured with a selected control.

[0173] The following is an explanation of the deletion process of the history window with reference to the accompanying drawings:

[0174] Figure 25 A schematic diagram of the changes in the display interface provided for a feasible implementation method. In this embodiment, the display displays the third interface. For details, please refer to effect 25-1. In this embodiment, the third interface includes 10 historical windows. The user calls up the delete drop-down box by touching the menu button of the remote control. At this time, the interface displayed on the display can refer to effect 25-2. The user clicks the multi-select control, and the controller adds a selection control for each of the historical windows. At this time, the interface displayed on the display can refer to effect 25-3. In this embodiment, the user selects historical window 1, historical window 2, and historical window 3. In response to the user's confirmation operation, the controller deletes historical window 1, historical window 2, historical window 3 and the playback progress corresponding to historical window 1, historical window 2, and historical window 3. At this time, the interface displayed on the display can refer to effect 25-4.

[0175] Figure 26 A schematic diagram of the changes in the display interface provided by a feasible implementation method. In this embodiment, the display displays the third interface. For details, please refer to effect 26-1. In this embodiment, the third interface includes 10 historical windows. The user calls the delete drop-down box by touching the menu button of the remote control. At this time, the interface displayed on the display can refer to effect 26-2. The user clicks the delete all control, and the display displays a prompt window. The prompt window is used to prompt the user that all playback progress will be deleted. At this time, the interface displayed on the display can refer to effect 26-3. In response to the user's confirmation operation, the controller deletes historical window 1, historical window 2, historical window 3, historical window 4, historical window 5, historical window 6, historical window 7, historical window 8, historical window 9, historical window 10 and the playback progress corresponding to historical window 1, historical window 2, historical window 3, historical window 4, historical window 5, historical window 6, historical window 7, historical window 8, historical window 9, and historical window 10. At this time, the interface displayed on the display can refer to effect 26-4.

[0176] Figure 27 This is a schematic diagram of the display interface changes provided in a feasible implementation. In this embodiment, the display displays the third interface. For details, see Effect 27-1. In this embodiment, the third interface includes 10 history windows. When the user uses the menu button on the touch remote control to access the delete drop-down box, the display interface is shown in Effect 27-2. When the user clicks to exit the multi-select control, the display interface disappears. See Effect 27-3 for the display interface.

[0177] In response to the confirmation operation on the history window, the controller is configured to execute S53 to control the display to continue displaying the file corresponding to the history window, starting from the playback progress recorded in the history window.

[0178] The user's confirmation operation on the history window may be, but is not limited to, when the user controls the cursor to move to the history window via the remote control, the user touches the confirmation button of the remote control.

[0179] The display device provided in this embodiment includes at least a display and a controller. When connected to an external storage device, the display displays a first interface. The first interface includes at least a first area for displaying a history window of playback progress of files stored in the external storage device, each of which corresponds to a file. In response to a confirmation operation on a history window, the display continues to display the file corresponding to the history window, starting from the playback progress recorded in the history window. This eliminates the need for the user to manually adjust the playback progress, resulting in a better user experience.

[0180] A second aspect of the present application embodiment provides a file display method, including:

[0181] When an external storage device is connected, a first interface is displayed, wherein the first interface includes at least a first area, wherein the first area is used to display a history window of the playback progress of files stored in the external storage device, each history window corresponding to a file;

[0182] In response to a confirmation operation on a history window, the file corresponding to the history window continues to be displayed, starting from the playback progress recorded in the history window.

[0183] This embodiment provides a file display method applicable to a display device comprising at least a controller and a display. When connected to an external storage device, the display displays a first interface comprising at least a first area for displaying a history window of playback progress of files stored in the external storage device, each of which corresponds to a file. In response to a confirmation operation on a history window, the display continues displaying the file corresponding to the history window, starting from the playback progress recorded in the history window. This eliminates the need for users to manually adjust the playback progress, resulting in a better user experience.

[0184] In a specific implementation, the present invention further provides a computer storage medium, wherein the computer storage medium may store a program that, when executed, may include some or all of the steps of each embodiment of the control key customization method and activation method provided by the present invention. The storage medium may be a magnetic disk, an optical disk, a read-only memory (ROM), or a random access memory (RAM).

[0185] Those skilled in the art will clearly understand that the techniques in the embodiments of the present invention can be implemented using software plus a necessary general-purpose hardware platform. Based on this understanding, the technical solutions in the embodiments of the present invention, or the portion that contributes to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a storage medium such as ROM / RAM, a magnetic disk, or an optical disk, and includes a number of instructions for enabling a computer device (which can be a personal computer, server, or network device, etc.) to execute the methods of various embodiments of the present invention or certain portions of the embodiments.

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

[0187] For ease of explanation, the above description has been presented in conjunction with specific embodiments. However, the above exemplary discussion is not intended to be exhaustive or to limit the embodiments to the specific forms disclosed above. Based on the above teachings, various modifications and variations are possible. The above embodiments have been selected and described to better explain the principles and practical applications, thereby enabling those skilled in the art to better utilize the embodiments and various variations of the embodiments suitable for specific use considerations.

Claims

1. A display device, characterized in that: include: monitor; The controller is configured as: When an external memory device is detected to be connected, a prompt window is displayed, wherein the prompt window is used to prompt the user that the external memory device has been inserted; In response to an opening operation on the prompt window, controlling the display to display a memory interface, the memory interface including a type control and files stored in the external memory; When the type control is selected as the first file type, if it is detected that it is not the first time to connect the external storage device, reading the first file type; If the first file type is a preset type, reading a history switch flag, wherein the preset type of file includes a file that can be displayed in segments in time or space, and the history switch flag is set by the user selecting a history switch control in a menu interface or by using a physical switch; If the state corresponding to the flag bit of the history switch is on, controlling the display to display a first interface, the first interface including at least a first area and a second area, the first area being used to display a history window of the playback progress of files stored in the external memory, each history window corresponding to a file, and the second area being used to display a target file that matches the first file type; When a confirmation operation on the history window is received, controlling the display to continue displaying the file corresponding to the history window, starting from the playback progress recorded in the history window; When a confirmation operation on the target file is received, controlling the display to display the target file from the beginning; If the first file type is not a preset type, or the state corresponding to the flag bit of the history switch is off, controlling the display to display a target file that meets the first file type; If it is detected that the external storage device is connected for the first time, the first file type is not read.

2. The display device according to claim 1, wherein If the state corresponding to the flag bit of the history switch is on, the controller is further configured to: Count the number of playback progress; If the number of the playback progress is less than or equal to a preset number, the first area is controlled to display the history windows corresponding to all the playback progress.

3. The display device according to claim 2, wherein The controller is further configured to: If the number of playback progresses is greater than a preset number, controlling the first area to display history windows and extension controls corresponding to N-1 playback progresses, where N is a preset number; In response to a confirmation operation on the extension control, the content displayed on the display is controlled to jump from the first interface to the third interface, and the third interface is used to display the history window corresponding to the entire playback progress.

4. The display device according to claim 2 or 3, characterized in that If the display shows the third interface, the controller is further configured to: In response to an operation of invoking a delete drop-down box, controlling the display to display the delete drop-down box, wherein the delete drop-down box includes a multi-select control; In response to a confirmation operation on the multi-select control, a selected control is added to each of the history windows.

5. The display device according to claim 4, wherein: The delete drop-down box also includes a delete all control; the controller is further configured to: In response to a confirmation operation on the delete all control, all play progress is deleted.

6. The display device according to claim 1, wherein The controller is further configured to: In response to the closed file, reading the flag of the history switch; If the state corresponding to the flag bit of the history switch is on, reading the playback progress of the closed file; If the state corresponding to the flag of the history switch is closed, the playback progress of the closed file is not read.

7. A file display method, characterized in that: include: When an external memory device is detected to be connected, a prompt window is displayed, wherein the prompt window is used to prompt the user that the external memory device has been inserted; In response to an opening operation on the prompt window, a storage interface is displayed, wherein the storage interface includes a type control and files stored in the external storage; When the type control is selected as the first file type, if it is detected that it is not the first time to connect the external storage device, reading the first file type; If the first file type is a preset type, reading a history switch flag, wherein the preset type of file includes a file that can be displayed in segments in time or space, and the history switch flag is set by the user selecting a history switch control in a menu interface or by using a physical switch; If the state corresponding to the flag bit of the history switch is on, a first interface is displayed, the first interface including at least a first area and a second area, the first area being used to display a history window of the playback progress of files stored in the external memory, each history window corresponding to a file, and the second area being used to display target files that conform to the first file type; When a confirmation operation on a history window is received, the file corresponding to the history window is continued to be displayed starting from the playback progress recorded in the history window; In case of receiving a confirmation operation on the target file, controlling the display to display the target file from the beginning; If the first file type is not a preset type, or the state corresponding to the flag bit of the history switch is off, displaying target files that match the first file type; If it is detected that the external storage device is connected for the first time, the first file type is not read.

Images