Display device and camera detection prompting method

Abstract

The invention provides a display device and a camera detection prompting method, the method can respond to a change notice of a device directory, a removed device node and a running state of a camera corresponding to the removed device node are detected, the device directory is used for recording the device node corresponding to the camera currently connected with the display device, and the device node is used for recording the device node corresponding to the camera currently connected with the display device. The removed device node is a deleted device node in the device directory, the running state is an open state or a closed state, and the running state is a running state recorded before receiving a change notification of the device directory. And when the operation state is an on state, controlling the display to display first prompt information which is used for representing that the currently used camera is removed. According to the method, corresponding control and processing logic can be executed on the camera based on the plugging state change information and the operation state of the camera, and accurate prompting of the abnormal state of the camera is achieved.

Description

Technical Field

[0001] The present application relates to the technical field of display devices, and in particular to a display device and a camera detection prompt method. Background Art

[0002] Display devices refer to terminal devices that can output specific display images, which can be terminal devices such as smart TVs, communication terminals, smart advertising screens, projectors, etc. Taking smart TVs as an example, smart TVs are based on Internet application technology, have open operating systems and chips, have open application platforms, can realize two-way human-computer interaction functions, and are TV products that integrate multiple functions such as audio and video, entertainment, and data to meet the diverse and personalized needs of users.

[0003] In order to meet the personalized needs of users, a built-in or external camera can be installed on the display device to collect image data of the external environment scene, and process and display it, so as to realize functions such as video chatting, taking pictures, and recording videos on the display device.

[0004] However, due to the plug-in and unplug characteristics of external cameras, there is uncertainty in the virtual node corresponding to the mounted camera. In the application scenario of multiple cameras, it is impossible to accurately prompt the abnormal status of the camera. Summary of the invention

[0005] The present application provides a display device and a camera detection prompt method to solve the problem that in the application scenario of multiple cameras, it is impossible to accurately prompt the abnormal status of the camera.

[0006] In a first aspect, the present application provides a display device, including a display, a device interface, and a controller. The display is configured to display a user interface; the device interface is used to connect a camera; and the controller is configured to execute the following program steps:

[0007] In response to a notification of a change in a device directory, detecting a removed device node, wherein the device directory is used to record device nodes corresponding to cameras currently connected to the display device, and the removed device node is a device node deleted from the device directory;

[0008] Detecting the operating state of the camera corresponding to the removed device node, where the operating state is an on state or an off state, and the operating state is the operating state recorded before receiving the change notification of the device directory;

[0009] When the operating state is the on state, the display is controlled to display a first prompt message, where the first prompt message is used to indicate that the currently used camera has been removed.

[0010] In a second aspect, the present application further provides a camera detection prompt method, which is applied to the above-mentioned display device, and the method comprises:

[0011] In response to a notification of a change in a device directory, detecting a removed device node, wherein the device directory is used to record device nodes corresponding to cameras currently connected to the display device, and the removed device node is a device node deleted from the device directory;

[0012] Detecting the operating state of the camera corresponding to the removed device node, where the operating state is an on state or an off state, and the operating state is the operating state recorded before receiving the change notification of the device directory;

[0013] When the operating state is the on state, the display is controlled to display a first prompt message, where the first prompt message is used to indicate that the currently used camera has been removed.

[0014] It can be seen from the above technical solutions that the present application provides a display device and camera detection prompt method, the method can detect the operation status of the removed device node and the camera corresponding to the removed device node in response to the change notification of the device directory, the device directory is used to record the device node corresponding to the camera currently connected to the display device, the removed device node is the device node deleted in the device directory, the operation status is the on state or the off state, and the operation status is the operation status recorded before receiving the change notification of the device directory. When the operation status is the on state, the display is controlled to display the first prompt information, and the first prompt information is used to indicate that the currently used camera has been removed. The method executes corresponding control and processing logic on the camera based on the plug-in status change information and the operation status of the camera, so as to realize accurate prompting of abnormal camera status. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0016] Figure 1 A schematic diagram of an operation scenario between a display device and a control device provided in some embodiments of the present application;

[0017] Figure 2 A schematic diagram of the hardware configuration of a display device provided in some embodiments of the present application;

[0018] Figure 3 A schematic diagram of the hardware configuration of a control device provided in some embodiments of the present application;

[0019] Figure 4 A schematic diagram of software configuration of a display device provided in some embodiments of the present application;

[0020] Figure 5 A schematic diagram of a configuration of a camera provided in some embodiments of the present application;

[0021] Figure 6 Another configuration diagram of a camera provided in some embodiments of the present application;

[0022] Figure 7 A schematic diagram of a multi-camera management architecture provided for some embodiments of the present application;

[0023] Figure 8 A schematic diagram of a control flow when a camera is removed provided in some embodiments of the present application;

[0024] Fig. 9 A schematic diagram of a control flow of starting a camera provided in some embodiments of the present application;

[0025] Fig.10 A schematic diagram of a control flow corresponding to scenario 1 provided in some embodiments of the present application;

[0026] Fig.11 A schematic diagram of a control flow corresponding to scenario 2 provided in some embodiments of the present application;

[0027] Fig.12 A schematic diagram of a prompt interface for displaying second prompt information provided in some embodiments of the present application;

[0028] Fig.13 A schematic diagram of a prompt interface for displaying a jump option for jumping to a camera purchase interface provided in some embodiments of the present application;

[0029] Fig.14 A schematic diagram of the control flow corresponding to scenario three provided in some embodiments of the present application;

[0030] Fig.15 A schematic diagram of a control flow corresponding to scenario 5 provided in some embodiments of the present application;

[0031] Fig.16 A schematic diagram of a prompt interface for displaying first prompt information provided in some embodiments of the present application;

[0032] Fig.17 A schematic diagram of a control flow corresponding to scenario nine provided in some embodiments of the present application;

[0033] Fig.18 A schematic diagram of a prompt interface corresponding to scenario 10 provided in some embodiments of the present application;

[0034] Fig.19 A schematic diagram of a prompt interface for displaying third prompt information provided in some embodiments of the present application. DETAILED DESCRIPTION

[0035] The following embodiments are described in detail, and examples thereof are shown in the accompanying drawings. When the following description refers to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The implementations described in the following embodiments do not represent all implementations consistent with the present application. They are only examples of systems and methods consistent with some aspects of the present application as detailed in the claims.

[0036] It should be noted that the brief description of terms in this application is only for the convenience of understanding the embodiments described below, and is not intended to limit the embodiments of this application. Unless otherwise specified, these terms should be understood according to their common and usual meanings.

[0037] The terms "first", "second", "third", etc. in the specification and claims of this application and the above drawings are used to distinguish similar or similar objects or entities, and do not necessarily mean to limit a specific order or sequence, unless otherwise noted. It should be understood that the terms used in this way can be interchangeable under appropriate circumstances.

[0038] The terms "comprises," "comprising," and "having," 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.

[0039] 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 functions associated with that element.

[0040] In the embodiment of the present application, the display device 200 generally refers to a device with image display and data processing capabilities. For example, the display device 200 includes but is not limited to a smart TV, a mobile terminal, a computer, a monitor, an advertising screen, a wearable device, a virtual reality device, an augmented reality device, etc.

[0041] Figure 1 This is a schematic diagram of an operation scenario between a display device and a control device provided in some embodiments of the present application. Figure 1 As shown in FIG. 1 , the user can operate the display device 200 through touch operation, the mobile terminal 300 and the control device 100. For example, the control device 100 can be a remote controller, a stylus pen, a handle, etc.

[0042] The mobile terminal 300 can be used as a control device for performing human-computer interaction between the user and the display device 200. The mobile terminal 300 can also be used as a communication device for establishing a communication connection with the display device 200 and performing data interaction. In some embodiments, the mobile terminal 300 can install software applications with the display device 200, and achieve connection and communication through a network communication protocol to achieve the purpose of one-to-one control operation and data communication. The audio and video content displayed on the mobile terminal 300 can also be transmitted to the display device 200 to achieve a synchronous display function.

[0043] like Figure 1 As also shown in FIG. 4 , the display device 200 also communicates data with the server 400 through various communication methods. The display device 200 may be allowed to communicate and connect through a local area network (LAN), a wireless local area network (WLAN), and other networks.

[0044] The display device 200 may provide a broadcast receiving television function, and may also additionally provide an intelligent network television function with a computer support function, including but not limited to network television, smart television, Internet Protocol television (IPTV), and the like.

[0045] Figure 2 Some embodiments of the present application provide Figure 1 2 is a block diagram of the hardware configuration of the display device 200.

[0046] In some embodiments, the display device 200 may include at least one of a tuner 210, a communication device 220, a detector 230, a device interface 240, a controller 250, a display 260, an audio output device 270, a memory, a power supply, and a user input interface.

[0047] In some embodiments, the detector 230 is used to collect signals of the external environment or external interaction. For example, the detector 230 includes a light receiver, a sensor for collecting the intensity of ambient light; or, the detector 230 includes an image collector, such as a camera, which can be used to collect external environment scenes, user attributes or user interaction gestures; or, the detector 230 includes a sound collector, such as a microphone, etc., for receiving external sounds.

[0048] In some embodiments, the device interface 240 is used to connect an external device. It includes but is not limited to any one or more interfaces such as the high-definition multimedia interface (HDMI), analog or digital high-definition component input interface (component), composite video input interface (CVBS), USB input interface (USB), RGB port, etc. It can also be a composite input / output interface formed by the above multiple interfaces. For example, the display device 200 can be connected to an external camera through a USB interface, collect image data of the external environment scene through the camera, and display it through the display 260.

[0049] In some embodiments, the display 260 includes a display function component for presenting a picture, and a driving component for driving an image display. The display 260 is used to receive an image signal output from the controller 250 for display. For example, the display 260 can be used to display video content, image content, and components of a menu control interface and a user control UI interface.

[0050] In some embodiments, the communication device 220 is a component for communicating with an external device or server 400 according to various communication protocol types. The display device 200 may be provided with a plurality of communication devices 220 according to different supported communication modes. For example, when the display device 200 supports wireless network communication, the display device 200 may be provided with a communication device 220 including a WiFi function. When the display device 200 supports Bluetooth connection communication, the display device 200 needs to be provided with a communication device 220 including a Bluetooth function.

[0052] The communication device 220 can enable the display device 200 to communicate with the external device or server 400 by wireless or wired connection. Among them, the wired connection can connect the display device 200 with the external device through components such as data cables and interfaces. The wireless connection can connect the display device 200 with the external device through wireless signals or wireless networks. The display device 200 can establish a connection relationship with the external device directly, or indirectly establish a connection relationship through a gateway, a router, a connection device, etc.

[0053] In some embodiments, the controller 250 may include at least one of a central processing unit, a video processor, an audio processor, a graphics processor, and a power processor, and a first interface to an nth interface for input / output. The controller 250 controls the operation of the display device and responds to the user's operation through various software control programs stored in the memory. The controller 250 controls the overall operation of the display device 200.

[0054] In some embodiments, the controller 250 and the tuner-demodulator 210 may be located in different separate devices, that is, the tuner-demodulator 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.

[0055] 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).

[0056] In some embodiments, the audio output device 270 may be a local speaker of the display device 200, or may be an external audio output device of the display device 200. In particular, for the external audio output device of the display device 200, the display device 200 may also be provided with an external audio output terminal, and the audio output device may be connected to the display device 200 through the external audio output terminal to output the sound of the display device 200.

[0057] In some embodiments, the user input interface 280 may be used to receive instructions from a user.

[0058] Figure 3 Some embodiments of the present application provide Figure 1 The hardware configuration diagram of the control device in the figure. Figure 3 As shown, the control device 100 may include: a controller 110, a communication interface 130, a user input / output interface, a memory, and a power supply.

[0059] The control device 100 is configured to control the display device 200 , and can receive user input operation instructions, and convert the operation instructions into instructions that the display device 200 can recognize and respond to, playing the role of an interactive intermediary between the user and the display device 200 .

[0060] In some embodiments, the control device 100 may be a smart device, for example, the control device 100 may be installed with various applications for controlling the display device 200 according to user needs.

[0061] In some embodiments, Figure 1 As shown, the mobile terminal 300 or other intelligent electronic devices can play a similar function as the control device 100 after installing the application for controlling the display device 200 .

[0062] The controller 110 includes a processor 112, a RAM 113, a ROM 114, a communication interface 130, and a communication bus. The controller 110 is used to control the operation and operation of the control device 100, as well as the communication and cooperation between the internal components and the external and internal data processing functions.

[0063] The communication interface 130 implements communication of control signals and data signals with the display device 200 under the control of the controller 110. The communication interface 130 may include at least one of other near field communication modules such as a WiFi chip 131, a Bluetooth module 132, and an NFC module 133.

[0064] The user input / output interface 140 , wherein the input interface includes at least one of other input interfaces such as a microphone 141 , a touch panel 142 , a sensor 143 , and a button 144 .

[0065] In some embodiments, the control device 100 includes at least one of a communication interface 130 and an input / output interface 140. The control device 100 is configured with a communication interface 130, such as a WiFi, Bluetooth, NFC or other module, and can encode the user input command through the WiFi protocol, Bluetooth protocol, or NFC protocol and send it to the display device 200.

[0066] The memory 190 is used to store various operating programs, data and applications for driving and controlling the control device 100 under the control of the controller. The memory 190 can store various control signal instructions input by the user.

[0067] The power supply 180 is used to provide operating power support for each component of the control device 100 under the control of the controller.

[0068] In order to perform user interaction, in some embodiments, the display device 200 may run an operating system. The operating system is a computer program for managing and controlling hardware resources and software resources in the display device 200. The operating system can control the display device to provide a user interface, for example, the operating system can directly control the display device to provide a user interface, or can provide a user interface by running an application program. The operating system also allows the user to interact with the display device 200.

[0069] It should be noted that the operating system may be a native operating system based on a specific operating platform, or a third-party operating system deeply customized based on a specific operating platform, or an independent operating system specially developed for the display device.

[0070] The operating system can be divided into different modules or layers according to the functions implemented, for example Figure 4 As shown, in some embodiments, the system is divided into four layers, from top to bottom, namely, the application layer (Applications) layer (referred to as "application layer"), the application framework layer (Application Framework) layer (referred to as "framework layer"), the system library layer and the kernel layer.

[0071] In some embodiments, the application layer is used to provide services and interfaces for applications so that the display device 200 can run applications and interact with users based on the applications. At least one application can be run in the application layer, and these applications can be window programs, system settings programs, clock programs, etc. that come with the operating system; they can also be applications developed by third-party developers. In specific implementations, the application packages in the application layer are not limited to the above examples.

[0072] The framework layer provides application programming interfaces (APIs) and programming frameworks for applications. The application framework layer includes some predefined functions. The application framework layer is equivalent to a processing center that determines the actions that applications in the application layer take. Through the API interface, applications can access system resources and obtain system services during execution.

[0073] like Figure 4 As shown, in the embodiment of the present application, the application framework layer includes a view system, managers, content providers, etc., wherein the view system can design and implement the interface and interaction of the application, and the view system includes lists, grids, text boxes, buttons, etc. The manager includes at least one of the following modules: an activity manager for interacting with all activities running in the system; a location manager for providing system services or applications with access to system location services; a package manager for retrieving various information related to the application package currently installed on the device; a notification manager for controlling the display and clearing of notification messages; and a window manager for managing icons, windows, toolbars, wallpapers, and desktop widgets on the user interface.

[0074] In some embodiments, the activity manager is used to manage the life cycle of each application and the usual navigation back function, such as controlling the exit, opening, and back of the application. The window manager is used to manage all window programs, such as obtaining the display screen size, determining whether there is a status bar, locking the screen, capturing the screen, and controlling the display window changes, for example, reducing the display window, shaking the display, distorting the display, etc.

[0075] In some embodiments, the system runtime layer can provide support for the framework layer. When the framework layer is used, the operating system will run the instruction library contained in the system runtime layer, such as the C / C++ instruction library, to implement the functions to be implemented by the framework layer.

[0076] In some embodiments, the kernel layer is a functional layer between the hardware and software of the display device 200. The kernel layer can implement functions such as hardware abstraction, multitasking, and memory management. Figure 4As shown, the kernel layer may be configured with hardware drivers, and the drivers included in the kernel layer may be at least one of the following drivers: 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, etc.

[0077] It should be noted that the above example is only a simple division of the operating system functions and does not constitute a limitation on the specific operating system form of the display device 200 in the embodiment of the present application. Depending on factors such as the function of the display device and the type of operating system, the number of levels and specific level types contained in the operating system may be expressed in other forms.

[0078] Based on the above display device 200, a specific screen can be presented. For example, a playback screen, a control interface, and other application interfaces. According to the developer or operator of the application, the application installed on the display device 200 can include various forms, such as system applications, third-party applications, etc. The applications installed on the display device can also be divided into multiple types according to the functions that the application can achieve, such as video applications, reading applications, game applications, etc.

[0079] In some embodiments, the application installed on the display device 200 includes a camera application, which is an application that can call a camera, such as a photo taking application, a magic mirror application, etc. The camera application can be a system application or a third-party application developed based on a specific display device type and user needs. The camera application can be installed in the display device 200 and started and run under user control.

[0080] When the display device 200 runs a camera application, the camera 500 may be called and controlled to collect image data of the external environment scene through the camera and display it through the display 260. For example, the camera application may use the camera to capture the user's facial image for skin analysis or virtual makeup trial. The camera application may also use the camera for real-time video calls or conferences.

[0081] In some embodiments, the camera 500 may be a built-in camera on the display device 200, may be uniformly controlled by the controller 250 in the display device 200, and may directly send the collected image data to the controller 250. Obviously, in order to facilitate the collection of user images, the camera should be set at a specific position on the display device 200. For example, Figure 5 As shown, for a display device 200 such as a smart TV, a camera can be set on the top of the smart TV, and the shooting direction of the camera is the same as the screen light emission direction of the smart TV, so that image data located in front of the screen can be captured.

[0082] In some embodiments, the camera 500 may also be a camera externally connected to the display device 200 via the device interface 240. Figure 6 As shown, after the camera is connected to the device interface 240 , it can send the collected image data to the display device 200 through a specific data transmission method supported by the device interface 240 .

[0083] In some embodiments, in order to improve the user experience, when the display device 200 runs the camera application, it can execute corresponding processing logic based on the insertion or removal status of the camera. For example, when the display device 200 detects that the camera is removed, it can display a prompt message indicating that the camera is not currently inserted or the camera has been removed through a pop-up window, a status bar notification, etc. For another example, when a new camera is detected to be inserted, the camera reconnection process is executed.

[0084] However, due to the plug-in and unplug characteristics of external cameras, there will be uncertainty in the virtual node corresponding to the mounted camera. In the application scenario of multiple cameras, it is impossible to accurately prompt the abnormal status of the camera and reconnect the camera control.

[0085] In order to realize the control and processing logic of multiple cameras. In some embodiments, Figure 7 As shown, the display device 200 provides a multi-camera management architecture, including an application layer, a camera platform and a hardware abstraction layer (HardwareAbstraction Layer, HAL).

[0086] The application layer includes camera applications and camera reminder applications. The camera application can directly use the camera functions provided by the camera platform. Based on different camera usage scenarios, the camera can be called to realize functions such as video calls, photos, and videos. The camera reminder application is a global camera abnormality reminder application, which is used to realize camera abnormality reminders.

[0087] The camera platform can provide camera functions for the application layer, such as camera opening and closing functions, and connect to the camera device management status of the HAL layer, so that the camera device can be properly managed and controlled. The camera platform can call the HAL layer through the interface, monitor the plug-in and unplug-out status changes of the camera called back by the HAL layer, and monitor the changes of the device nodes (device files) under the device directory (such as the / dev / video / directory) through the registration file method. The device node contains the general interface of the camera platform or the virtual device node adapted to the camera platform. After detecting the plug-in and unplug-out status changes of the camera, the camera platform can synchronize the plug-in and unplug-out status change information to the camera reminder application through broadcasting, callback and other mechanisms.

[0088] The HAL layer is the layer for connecting to specific camera hardware devices. The HAL layer configures basic camera interfaces, which are abstracted into specific hardware details and provide interfaces for upper-layer applications to interact with the underlying camera hardware. For example, when a camera application starts a camera, it can call the basic camera interface in the HAL layer to start the camera based on the camera functions provided by the camera platform.

[0089] The HAL layer can also send the plug-in status change information of the plug-in attribute camera to the camera platform to implement the plug-in attribute camera management. For example, when the camera is plugged into the USB interface, the HAL layer will detect the first plug-in signal generated when the camera is connected to the USB interface, and notify the camera platform to increase the camera count; conversely, when the camera is removed from the USB interface, the HAL layer will detect the second plug-in signal generated when the camera is disconnected from the USB interface, and notify the camera platform to reduce the corresponding camera count.

[0090] In the above multi-camera management architecture, the application layer can call camera functions, the camera platform can provide a unified camera device management and monitoring mechanism, the HAL layer can connect with specific camera hardware devices, and an efficient collaboration mechanism can be formed through the application layer, camera platform and HAL layer.

[0091] Based on the above management architecture, in the application scenario of multiple cameras, the display device 200 can respond to the change notification of the device directory, detect the plug-in status change information of the camera, and execute the control and processing logic of multiple cameras based on the plug-in status change information to realize abnormal prompts in different camera usage scenarios.

[0092] Among them, the device directory is used to record the device node corresponding to the camera currently connected to the display device 200, and the plug-in status change information includes the insertion status information of the newly added device node and / or the removal status information of the removed device node. The newly added device node is the newly created device node in the device directory, that is, the newly inserted camera, and the removed device node is the deleted device node in the device directory, that is, the removed camera.

[0093] In the display device 200, the hardware device can be represented as a file or directory in the file system, thereby allowing the user space program to interact with the device driver in the kernel through a standard file operation interface to implement various operations on the hardware device. The device directory is a virtual file system directory in the display device 200, and each device node (device file) under the device directory represents a camera.

[0094] In the display device 200, when a camera device is plugged into the device interface 240, a first plug-in signal generated when the camera is connected to the device interface 240 can be detected, and in response to the first plug-in signal, a device node of the camera can be created in the device directory. Similarly, when a camera device is removed from the device interface 240, a second plug-in signal generated when the camera is disconnected from the device interface 240 can be detected, and in response to the second plug-in signal, the device node of the camera can be deleted in the device directory.

[0095] For example, the kernel of the display device 200 can dynamically create a device node in the / dev / video / directory, and its identification field can be / dev / videoX, where X is an increasing number used to distinguish different camera devices. For example, the / dev / video / directory includes / dev / video0, / dev / video1, / dev / video2, etc., which correspond to device nodes of different cameras.

[0096] When a camera is plugged into the USB interface, the kernel will create a device node / dev / videoX in the / dev / video / directory. When the camera is removed from the USB interface, the kernel will delete the device node / dev / videoX in the / dev / video / directory. Therefore, by detecting the creation and deletion changes of the device nodes in the / dev / video / directory, it is possible to determine whether a camera has been inserted or removed, thereby obtaining the camera's plug-in and unplug status change information.

[0097] In some embodiments, the display device 200 can register for monitoring of the device directory, monitor the creation events of the device directory for creating device nodes and the deletion events for deleting device nodes. When a creation event or a deletion event is monitored, it indicates that the device node in the device directory has changed, and a device directory change notification is generated to trigger the step of detecting the plug-in and unplug status change information of the detection camera.

[0098] In some embodiments, the display device 200 can periodically obtain a device directory and detect whether a device node in the device directory has changed. That is, obtain the current device directory and read the identification field corresponding to the device node in the current device directory. Then obtain the historical device directory and read the identification field corresponding to the device node in the historical device directory. The historical device directory is the device directory obtained in the previous detection cycle. If the identification field corresponding to the device node in the current device directory is different from the identification field corresponding to the device node in the historical device directory, it means that the device node in the device directory has changed, and then a device directory change notification is generated to trigger the step of detecting the plug-in status change information of the detection camera.

[0099] In some embodiments, the display device 200 can traverse the current device directory and the historical device directory in response to the notification of the change of the device directory, and mark the device nodes that exist in the current device directory but not in the historical device directory as newly added device nodes, that is, newly inserted cameras. The device nodes that do not exist in the current device directory but exist in the historical device directory are marked as removed device nodes, that is, removed cameras. In this way, it can be determined whether a camera is inserted or removed, thereby obtaining the plug-in and unplug status change information of the camera.

[0100] For example, following the above example, when the camera is inserted into the USB interface, the kernel will create a device node / dev / videoX in the / dev / video / directory. The camera platform will register a listener for the / dev / video / directory. When the newly created device node / dev / videoX in the / dev / video / directory is listened, the insertion status information representing the device node / dev / videoX (newly added device node) will be synchronized to the camera reminder application in the application layer through broadcast, callback and other mechanisms, so that the camera reminder application can execute the corresponding processing logic. Similarly, when the camera is removed from the USB interface, the kernel will delete the device node / dev / videoX in the / dev / video / directory. The camera platform will listen to the deletion of the device node / dev / videoX in the / dev / video / directory, and synchronize the removal status information representing the device node / dev / videoX (removed device node) to the camera reminder application in the application layer through broadcast, callback and other mechanisms, so that the camera reminder application can execute the corresponding processing logic.

[0101] In some embodiments, the display device 200 can obtain a device directory in response to a startup instruction for starting a camera, and determine whether the display device 200 is currently connected to a camera based on the device node recorded in the device directory. If there is a device node in the device directory, a startup instruction is sent to the camera corresponding to the device node to start the camera. If there is no device node in the device directory, it means that the display device 200 is not currently connected to a camera, and the display 260 is controlled to display a second prompt message, and the second prompt message is used to indicate that the camera is not currently connected.

[0102] It is understandable that the startup instruction for starting the camera can be triggered when the camera application is started. For example, when the user starts an independent camera application through the application interface of the display device 200, the startup instruction for starting the camera will be triggered, thereby realizing the camera function. For another example, when the display device 200 runs a video call application, it receives a video call request initiated by the user in the video call application, and generates a startup instruction for starting the camera, thereby realizing the video call function.

[0103] In some embodiments, the display device 200 can detect the operating state of the camera. The control and processing logic of multiple cameras is executed based on the plug-in state change information and the operating state of the camera. Among them, the operating state includes an on state and an off state, the on state indicates that the camera is currently on, and the off state indicates that the camera is currently off.

[0104] In some embodiments, the operating status of the camera can be represented based on an operating parameter. When the operating status of the camera is on, the operating parameter can be a first parameter value; when the operating status of the camera is off, the operating parameter can be a second parameter value, which is used to characterize various logic and display processing during the camera's operating status switching process.

[0105] For example, the operating status of the camera is indicated by record[i].status=0 / 1. Here, i is an increasing number used to distinguish different camera devices. When record[i].status=0, it indicates that the operating status of the camera is off, and when record[i].status=1, it indicates that the operating status of the camera is on.

[0106] In some embodiments, the display device 200 may register a monitoring function, and monitor the start-up event and the shutdown event of the camera through the monitoring function. When the start-up event of the camera is monitored, the running state of the camera is marked as the start-up state. When the shutdown event of the camera is monitored, the running state of the camera is marked as the shutdown state.

[0107] For example, the camera reminder application (registration end) registers the camera's running status monitoring function. When the camera application starts the camera, the monitoring function will monitor the camera's startup event, and synchronize the camera's startup event to the registration end through the monitoring function, so that the camera reminder application updates the recorded camera's running status. For example, when the device node / dev / video0 in the / dev / video / directory corresponds to the camera camera0 and is turned on by the camera application, record[0].status=1 is recorded, indicating that the camera camera0 is turned on. Otherwise, record[0].status=0 is recorded, indicating that the camera camera0 is turned off.

[0108] In some embodiments, Figure 8As shown, the display device 200 can execute the control and processing logic when the camera is removed based on the plug-in status change information and the operating status of the camera. In response to the change notification of the device directory, the display device 200 can detect the plug-in status change information to determine the removal of the device node (S801), and detect the operating status of the camera corresponding to the removed device node recorded before receiving the change notification of the device directory (S802). If the operating status is closed, it means that the unused camera is removed, and no processing is performed (S803). If the operating status is on, it means that the currently used camera is removed, then the display 260 is controlled to display the first prompt information (S804), and the first prompt information is used to indicate that the currently used camera has been removed.

[0109] In some embodiments, the display device 200 can also respond to the device directory change notification, detect the plug-in status change information to determine the newly added device node, and detect the operating status of the connected camera recorded before receiving the device directory change notification. If the operating status of the connected camera is on, it means that the camera is currently in use, and no logical processing is performed for this camera insertion.

[0110] In some embodiments, in order to facilitate the control and management of multiple cameras, the display device 200 can create and maintain a camera list, which is used to record the operating status of the camera currently connected to the display device 200, and the list length is used to represent the number of cameras currently connected to the display device. That is, the display device 200 can create a device node of the camera in the device directory in response to the first plug-in signal generated when the camera is connected to the device interface 240, and add the operating status of the camera to the camera list. In response to the second plug-in signal generated when the camera is disconnected from the device interface, the device node of the camera is deleted in the device directory, and the operating status of the camera is deleted in the camera list. In this way, the camera list is updated according to the insertion and removal of the camera.

[0111] For example, the / dev / video / directory includes device nodes for three cameras, namely / dev / video0 (corresponding to camera camera0), / dev / video1 (corresponding to camera camera1), and / dev / video2 (corresponding to camera camera2). Correspondingly, the camera list is record[0].status=0 / 1, record[1].status=0 / 1, and record[2].status=0 / 1. This indicates that the current display device 200 is connected to three cameras, and the corresponding list length is 3. When camera camera0 is removed, the / dev / video / directory is updated to / dev / video1 (corresponding to camera camera1) and / dev / video2 (corresponding to camera camera2). Correspondingly, the camera list is updated to record[1].status=0 / 1 and record[2].status=0 / 1. This indicates that the current display device 200 is connected to two cameras, and the corresponding list length is 2.

[0112] In some embodiments, Fig. 9 As shown, the display device 200 can respond to a startup instruction for starting the camera and detect the list length of the camera list (S901). When the list length is 0, it means that the display device 200 is not currently connected to the camera, and then controls the display 260 to display a second prompt message (S902), and the second prompt message is used to indicate that the camera is not currently connected.

[0113] When the list length is not 0, it means that the display device 200 is currently connected to a camera, and then the target camera is queried in the camera list (S903), and the target camera is a camera whose operating state is closed in the camera list. If the target camera is found in the camera list, a start command is sent to the target camera to start the target camera (S904). When a receipt signal is received from the target camera in response to the start command, the operating state of the target camera in the camera list is changed to the open state in response to the receipt signal (S905).

[0114] If the target camera is not found in the camera list, it means that there is no idle camera among the cameras currently connected to the display device 200, and the display 260 is controlled to display the third prompt information (S906), where the third prompt information is used to indicate that there is no available camera at present.

[0115] After controlling the display 260 to display the third prompt information, the display device 200 can enter a waiting state. When a new camera is connected to the display device 200, the display device 200 can receive a notification of a change in the device directory. In response to the notification of the change, the display device 200 detects the plug-in status change information to determine the newly added device node (S907), and sends a startup instruction to the newly added camera corresponding to the newly added device node to start the newly added camera (S908). When receiving a receipt signal from the newly added camera for the startup instruction, in response to the receipt signal, the operating status of the newly added camera is added to the camera list (S909), and the operating status of the newly added camera in the camera list is set to the on state (S910).

[0116] In some embodiments, while the display device 200 displays the prompt information, a jump option for jumping to a specified interface can also be added to the user interface, for example, Fig.13 As shown, a jump option for a camera purchase interface can be set in the prompt interface, and in response to a user inputting a click instruction for the jump option, the display 260 can be controlled to display a preset camera purchase interface.

[0117] In this embodiment, for the scenario that supports plugging and unplugging cameras, in the scenario of multiple cameras being used, the control and processing logic for removing and inserting multiple cameras is implemented based on the plug-in and unplugging status change information and operating status of the cameras, and reminders of abnormal states of the cameras currently in use are realized, such as accurate reminders when the camera is removed; when inserting the camera, the normal display of the camera in use is guaranteed, so that the interaction error state will not be caused by inserting or removing the camera that is not in use, and accurate prompts of abnormal camera states and reconnection of camera control are realized.

[0118] The following describes the control and processing logic of the camera in combination with specific camera usage scenarios.

[0119] Scenario 1: When the display device 200 is connected to a camera, the camera is started.

[0120] like Fig.10 As shown, when the display device 200 runs a camera application, the camera application can send a startup instruction for starting the camera to the camera platform, so that the camera platform can detect the device nodes recorded in the device directory and determine the currently connected camera information. The camera basic interface in the HAL layer can be directly called to start the camera, thereby collecting and displaying image data through the camera.

[0121] In order to improve the user experience, when the display device 200 runs the camera application, the camera application can also request the camera platform to obtain a device list, which includes the device identification (camera id), device attributes, configuration information, etc. of all connected cameras. Based on the device list input by the camera platform, a device selection interface is generated and displayed, and the device selection interface includes multiple camera selection items for the user to select.

[0122] In response to a click instruction of a device option input by the user, the camera application can obtain the device identification corresponding to the device option, and send a start instruction carrying the device identification to the camera platform to start the camera corresponding to the device identification.

[0123] Scenario 2: When the display device 200 is not connected to a camera, the camera is started.

[0124] like Fig.11 As shown, in the scenario where the camera is not connected, the camera application is started. When the camera application is started, a startup instruction for starting the camera is sent to the camera platform, so that the camera platform can detect the device node recorded in the device directory. Since the camera is not inserted, the camera platform can detect that the camera is not currently connected, and then synchronize the status information representing the unconnected camera to the camera reminder application, so that the camera reminder application displays the second prompt information representing that the camera is not currently connected, as shown in the figure. Fig.12 The prompt interface shown.

[0125] In addition, if Fig.13 As shown, according to business scenario requirements, a jump option for jumping to the camera purchase interface can be added in the prompt interface. When the user inputs a click instruction for the jump option, the display 260 can be controlled to display the preset camera purchase interface.

[0126] Scenario 3: Continuing from Scenario 2, the display device 200 is connected to a camera.

[0127] like Fig.14As shown, in the second scenario, after the camera reminder application displays the second prompt information indicating that the camera is not currently connected, it can enter the waiting state and wait for the camera to be connected. When the camera camera0 is inserted into the device interface 240, the kernel of the display device 200 will create a device node / dev / video0 (corresponding to the camera camera0) in the / dev / video / directory, and the camera platform will monitor the changes of the device nodes in the / dev / video / directory, and synchronize the insertion status information of the device node / dev / video0 to the camera reminder application through broadcast. The camera reminder application cancels the display of the second prompt information according to the insertion status information transmitted by the camera platform, and updates the camera list, and adds the running status of the camera corresponding to the device node / dev / video0 in the camera list, that is, the camera list includes: record[0].status=0.

[0128] At the same time, the camera reminder application or camera platform can synchronize the insertion status information to the camera application by broadcasting, so that the camera application can execute the specific startup process of camera 0. When the camera reminder application monitors the running status of the registered camera, when it monitors that the camera 0 corresponding to the device node / dev / video0 is turned on by the camera application, the camera list is updated to record[0].status=1, indicating that the camera 0 is turned on.

[0129] In order to implement abnormal reminders during the process of starting the camera, when starting camera 0, the camera platform or camera application can send an abnormal detection notification carrying the device identifier (camera id) to the camera reminder application, such as action = setup, Extra = Camera id of camera 0, indicating whether camera 0 is abnormal when starting camera 0. The camera reminder application will perform corresponding detection operations based on the abnormal detection notification, such as whether there is a device node / dev / video0 in the / dev / video / directory, whether the driver required by camera 0 has been loaded and works normally, etc. When an abnormality is detected, an abnormal reminder message can be displayed.

[0130] Scenario 4: Following Scenario 3, when the camera of the display device 200 is already started, the camera is connected again.

[0131] Continuing with scenario three, after the camera application starts camera0, in the scenario where the camera has been started, the camera camera is inserted into the device interface 240, and the kernel of the display device 200 will create a device node / dev / video1 (corresponding to camera camera1) in the / dev / video / directory. The camera platform will monitor the changes of the device nodes in the / dev / video / directory, and synchronize the insertion status information of the device node / dev / video1 to the camera reminder application through broadcast. The camera reminder application adds the operating status of the camera corresponding to the device node / dev / video1 to the camera list according to the insertion status information transmitted by the camera platform, that is, the camera list includes: record[0].status=1, record[1].status=0.

[0132] Since the camera list records the camera 0 whose running status is turned on, it means that the camera 0 is in use, so no logical processing is performed for the insertion of the camera 1 this time.

[0133] Scenario 5: When the display device 200 is connected to a camera, the camera is removed while in use.

[0134] like Fig.15 As shown, in the scenario 3, after the camera application starts the camera camera0, in the scenario where the camera has been started, the camera camera0 is removed from the device interface 240, and the kernel of the display device 200 deletes the device node / dev / video0 in the / dev / video / directory. The camera platform monitors the changes of the device nodes in the / dev / video / directory, and synchronizes the removal status information of the device node / dev / video0 to the camera reminder application through broadcast.

[0135] The camera reminder application detects the operation status record[0].status=1 of the camera corresponding to the device node / dev / video0 in the camera list according to the removal status information of the device node / dev / video0 passed by the camera platform, indicating that the camera camera0 device is in use, and then controls the display 260 to display the first prompt information indicating that the currently used camera has been removed, as shown in the following figure: Fig.16 The prompt interface shown.

[0136] At the same time, the camera reminder application deletes the running status of the camera corresponding to the device node / dev / video0 in the camera list.

[0137] Scenario 6: When the display device 200 is connected to a camera, the camera is removed when the camera is not in use.

[0138] When the display device 200 is connected to the camera camera0 but the camera camera0 is not started, the corresponding camera list includes: record[0].status=0. When the camera camera0 is removed from the device interface 240, the kernel of the display device 200 deletes the device node / dev / video0 in the / dev / video / directory. The camera platform monitors the changes of the device nodes in the / dev / video / directory and synchronizes the removal status information of the device node / dev / video0 to the camera reminder application through broadcast.

[0139] The camera reminder application receives the removal status information of the device node / dev / video0 from the camera platform, and detects the running status record[0].status=0 of the camera corresponding to the device node / dev / video0 in the camera list, indicating that the camera 0 device is not in use. Then, the running status of the camera corresponding to the device node / dev / video0 is deleted from the camera list, and no logical processing is performed for the removal of the camera 0.

[0140] Scenario 7: When the display device 200 is connected to multiple cameras, unused cameras are removed during the use of the cameras.

[0141] Continuing with scenario 4, when the display device 200 is currently connected to camera 0 and camera 1, and camera 0 is started, the corresponding camera list includes: record[0].status=1, record[1].status=0.

[0142] When camera camera1 is removed from the device interface 240, the kernel of the display device 200 deletes the device node / dev / video1 in the / dev / video / directory. The camera platform monitors the changes of the device nodes in the / dev / video / directory and synchronizes the removal status information of the device node / dev / video1 to the camera reminder application through broadcast.

[0143] The camera reminder application detects the removal status information of the device node / dev / video1 transmitted by the camera platform, and detects the running status record[1].status=0 of the camera corresponding to the device node / dev / video1 in the camera list, indicating that the camera camera1 device is not in use. Then, the running status of the camera corresponding to the device node / dev / video1 is deleted from the camera list, and no logical processing is performed for the removal of the camera camera1.

[0144] Scenario 8: When the display device 200 is connected to multiple cameras, the camera being used is removed during the process of using the camera.

[0145] Based on the judgment logic of scenario seven, when camera camera0 is removed from the device interface 240, the camera reminder application detects the operation status record[0].status=1 of the camera corresponding to the device node / dev / video0 in the camera list according to the removal status information of the device node / dev / video0 transmitted by the camera platform, indicating that the camera camera0 device is in use, and then controls the display 260 to display the first prompt information indicating that the currently used camera has been removed, that is, Fig.16 The prompt interface shown in the figure will be displayed. At the same time, the device node / dev / video0 corresponding to the camera's running status will be deleted in the camera list.

[0146] Scenario nine: When the display device 200 is connected to multiple cameras, a camera is removed while in use.

[0147] like Fig.17 As shown, in the fourth scenario, when the display device 200 is currently connected to camera 0 and camera 1, and camera 0 is started, the corresponding camera list includes: record[0].status=1, record[1].status=0.

[0148] When camera camera0 is removed from the device interface 240, the camera platform will monitor the changes in the device nodes under the / dev / video / directory, detect the removal status information of the device node / dev / video0, automatically start camera camera1, and send the removal status information of the device node / dev / video0 and the start notification of camera camera1 to the camera reminder application, so that the camera reminder application updates the camera list to: record[1].status=1.

[0149] At the same time, the camera reminder application or the camera platform can send a startup notification of camera 1 to the camera application, so that the camera application obtains the image data collected by camera 1 for display, thereby ensuring the continuity of camera use.

[0150] In some embodiments, the camera platform may also synchronize the removal status information of the device node / dev / video0 to the camera reminder application through broadcast. The camera reminder application deletes the running status of the camera corresponding to the device node / dev / video0 in the camera list according to the removal status information of the device node / dev / video0 transmitted by the camera platform, and queries the camera whose current running status is closed based on the camera list, that is, queries the currently idle camera, that is, camera camera1.

[0151] The camera reminder application can send a startup instruction for starting camera camera1 to the camera platform, so that the camera platform starts camera camera1, or send information indicating that camera camera1 can be turned on to the camera application, so that the camera application sends a startup instruction for starting camera camera1 to the camera platform, so as to start camera camera1.

[0152] Scenario 10: When the display device 200 is connected to multiple cameras, a camera is started while the camera is in use.

[0153] like Fig.18 As shown, following scenario nine, when the display device 200 is currently connected to camera camera1 and camera camera1 is started, the corresponding camera list includes: record[1].status=0.

[0154] The camera application sends a startup instruction for starting the camera to the camera platform. The camera platform sends a query instruction representing a query for currently available cameras to the camera reminder application based on the startup instruction sent by the camera application, so that the camera reminder application queries the available cameras in the camera list, that is, queries the cameras whose running status is closed.

[0155] Since the camera camera1 recorded in the current camera list has been used, the camera reminder application does not query an available camera, so the third prompt information indicating that there is no available camera is displayed, as shown in the following figure: Fig.19 The prompt interface shown.

[0156] Based on the above display device 200, some embodiments of the present application also provide a camera detection prompt method, which is applied to the display device 200 described in the above embodiment. The display device 200 may include a display 260, a device interface 240 and a controller 250. Among them, the display 260 is configured to display a user interface. The device interface 240 is used to connect a camera, and the controller is configured to execute the camera detection prompt method, which includes the following steps:

[0157] In response to a notification of a change in the device directory, a removed device node is detected. The device directory is used to record device nodes corresponding to cameras currently connected to the display device, and the removed device node is a device node deleted from the device directory.

[0158] Detect the operating status of the camera corresponding to the removed device node, the operating status is the on state or the off state, and the operating status is the operating status recorded before receiving the change notification of the device directory.

[0159] When the operating state is the on state, the control display 260 displays a first prompt message, and the first prompt message is used to indicate that the currently used camera has been removed.

[0160] The same and similar parts between the various embodiments in this specification can be referenced to each other and will not be described again here.

[0161] It can be seen from the above technical solutions that the display device and camera detection prompt method provided in the above embodiments can detect the operation status of the removed device node and the camera corresponding to the removed device node in response to the change notification of the device directory. The device directory is used to record the device node corresponding to the camera currently connected to the display device. The removed device node is the device node deleted in the device directory. The operation status is the on state or the off state. The operation status is the operation status recorded before receiving the change notification of the device directory. When the operation status is the on state, the display is controlled to display the first prompt information, and the first prompt information is used to indicate that the currently used camera has been removed. The method executes corresponding control and processing logic on the camera based on the plug-in status change information and the operation status of the camera, so as to realize accurate prompting of abnormal camera status.

[0162] Those skilled in the art can clearly understand that the technology in the embodiments of the present invention can be implemented by means of software plus a necessary general hardware platform. Based on this understanding, the technical solution in the embodiments of the present invention is essentially or the part that contributes to the prior art can be embodied in the form of a software product, which can be stored in a storage medium such as ROM / RAM, a disk, an optical disk, etc., and includes a number of instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to execute the methods of various embodiments of the present invention or certain parts of the embodiments.

[0163] 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 it. 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 replace some or all of the technical features therein with equivalents. However, these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present application.

[0164] For the convenience of explanation, the above description has been made in conjunction with specific embodiments. However, the above exemplary discussion is not intended to be exhaustive or limit the embodiments to the specific forms disclosed above. Based on the above teachings, various modifications and variations can be obtained. The selection and description of the above embodiments are to better explain the principles and practical applications, so that those skilled in the art can better use the embodiments and various different variations of the embodiments suitable for specific use considerations.

Claims

1. A display device, characterized in that: include: a display configured to display a user interface; Device interface, used to connect the camera; The controller is configured as: In response to a notification of a change in a device directory, detecting a removed device node, wherein the device directory is used to record device nodes corresponding to cameras currently connected to the display device, and the removed device node is a device node deleted from the device directory; Detecting the operating state of the camera corresponding to the removed device node, where the operating state is an on state or an off state, and the operating state is the operating state recorded before receiving the change notification of the device directory; When the operating state is the on state, the display is controlled to display a first prompt message, where the first prompt message is used to indicate that the currently used camera has been removed.

2. The display device according to claim 1, characterized in that The controller is also configured to: In response to a first plug-in / plug-out signal generated when the camera is connected to the device interface, creating a device node of the camera in the device directory; In response to a second plug-in / plug-out signal generated when the camera is disconnected from the device interface, the device node of the camera is deleted from the device directory.

3. The display device according to claim 1, characterized in that The controller is also configured to: Get the current device directory; Read the identification field corresponding to the device node in the current device directory; Get the historical device catalog; Read the identification field corresponding to the device node in the historical device directory; If the identification field corresponding to the device node in the current device directory is different from the identification field corresponding to the device node in the historical device directory, a change notification of the device directory is generated.

4. The display device according to claim 3, characterized in that The controller is also configured to: Marking a device node that exists in the current device directory and does not exist in the historical device directory as a newly added device node, wherein the newly added device node is a newly created device node in the device directory; A device node that does not exist in the current device directory but exists in the historical device directory is marked as a removed device node.

5. The display device according to claim 1, characterized in that The controller is also configured to: Register the listening function; Monitor the camera start event and shutdown event through the monitoring function; When a camera startup event is monitored, marking the running state of the camera as the startup state; When a camera closing event is monitored, the operating state of the camera is marked as closed.

6. The display device according to claim 1, characterized in that The controller is also configured to: Create a camera list, where the camera list is used to record the operating status of the cameras currently connected to the display device; In response to a first plug-in / plug-out signal generated when a camera is connected to the device interface, adding the operating status of the camera to the camera list; In response to a second plug-in signal generated when the camera is disconnected from the device interface, the operating status of the camera is deleted from the camera list.

7. The display device according to claim 6, characterized in that The controller is also configured to: In response to a start-up instruction for starting a camera, detecting a list length of the camera list, wherein the list length is used to represent the number of cameras currently connected to the display device; When the list length is 0, the display is controlled to display second prompt information, where the second prompt information is used to indicate that a camera is not currently connected.

8. The display device according to claim 7, characterized in that The controller is also configured to: When the length of the list is not 0, query the target camera in the camera list, and the target camera is a camera in the camera list whose running state is closed; Sending a start instruction to the target camera to start the target camera; In response to a receipt signal fed back by the target camera in response to the start instruction, the operating state of the target camera in the camera list is modified to an on state.

9. The display device according to claim 8, characterized in that The controller is also configured to: When the target camera is not found in the camera list, controlling the display to display a third prompt message, wherein the third prompt message is used to indicate that there is no available camera at present; In response to a notification of a change in the device directory, detecting a newly added device node; Sending a start instruction to a newly added camera corresponding to the newly added device node to start the newly added camera; In response to a receipt signal fed back by the newly added camera in response to the start instruction, the running status of the newly added camera is added to the camera list, and the running status of the newly added camera in the camera list is set to the on state.

10. A camera detection prompt method, characterized in that: Applied to the display device according to any one of claims 1 to 9, the method comprising: In response to a notification of a change in a device directory, detecting a removed device node, wherein the device directory is used to record device nodes corresponding to cameras currently connected to the display device, and the removed device node is a device node deleted from the device directory; Detecting the operating state of the camera corresponding to the removed device node, where the operating state is an on state or an off state, and the operating state is the operating state recorded before receiving the change notification of the device directory; When the operating state is the on state, the display is controlled to display a first prompt message, where the first prompt message is used to indicate that the currently used camera has been removed.

Images