Camera control method and terminal equipment

Abstract

The invention belongs to the field of computer system software, and particularly relates to a camera control method and terminal equipment. The camera control method is applied to the terminal equipment, and comprises the following steps: displaying a first user interaction interface; receiving a first trigger operation of a user; displaying a camera control interface on the first user interaction interface in an overlapping manner according to the first triggering operation; receiving a second trigger operation of the user on the camera control interface; performing function setting on the camera according to the second trigger operation; and when it is confirmed that the first application program matched with the camera control interface runs in the terminal equipment, controlling the first application program to follow the camera control interface to perform function setting. By controlling the first application program matched with the camera control interface to follow the interface to perform function setting, unified camera setting is realized, and setting consistency of different applications when the camera is used is ensured.

Description

TECHNICAL FIELD

[0001] The present application belongs to the field of computer system software, and particularly relates to a camera control method and a terminal device. BACKGROUND

[0002] With the development of device-side applications, a series of problems affecting user experience and application development efficiency have gradually become prominent.

[0003] At present, there are many applications on user devices, and the camera control entry of each application is different. This causes the user to have to constantly adapt to and find new camera control entries when using different applications, greatly increasing the learning cost, making it difficult for the user to form a unified operation habit and cognition, and the user needs to re-explore how to enter the camera control interface every time a new application is contacted, reducing the convenience and efficiency of use. SUMMARY

[0004] In order to solve the above technical problems, the embodiments of the present application provide a camera control method and a terminal device, which solve the problem that the user needs to set the camera control one by one when using multiple applications, so as to improve the consistency of the camera control of multiple applications.

[0005] In a first aspect, the embodiments of the present application provide a camera control method applied to a terminal device, which comprises: displaying a first user interaction interface, the first user interaction interface being a running interface of the terminal device; receiving a first trigger operation of a user; according to the first trigger operation, superimposing and displaying a camera control interface on the first user interaction interface, the camera control interface being used for function setting of a camera connected to the terminal device; receiving a second trigger operation of the user on the camera control interface; according to the second trigger operation, performing function setting on the camera; when it is confirmed that the terminal device runs a first application program matched with the camera control interface, controlling the first application program to follow the camera control interface to perform function setting. The embodiments of the present application directly respond to the first trigger operation and superimpose and display the camera control interface on the running interface of the terminal device, so that the user can quickly perform camera function setting without interrupting the current task, greatly improving the convenience and fluency of operation. Moreover, the application program can be controlled to follow the camera control interface to perform function setting, which means that the user can adjust the parameters of the camera and the related application through a centralized control interface, realize unified camera setting, and ensure the setting consistency of different applications when using the camera.

[0006] In some embodiments, the first user interaction interface displays a camera setting interface of the first application, and the controlling the first application to follow the camera control interface for function setting includes: controlling the camera setting interface of the first application to follow the camera control interface for synchronous change, so that the first application follows the camera control interface for function setting. The embodiments of the present application realize that the user does not need to switch back and forth between different interfaces to find the camera setting options, and all setting functions are concentrated on a unified interaction interface, so that the user can more quickly and intuitively set the functions of the camera. Whether it is adjusting the parameters of the camera, selecting the working mode or setting the preset position, it can be easily completed on the first user interaction interface, which greatly saves the time and effort of the user. On the other hand, the synchronous change mechanism ensures the consistency of different applications and the camera control. When the user operates in the camera control interface, the camera setting interface of the first application can follow the change in real time, which means that the camera parameters set by the user in one application can be automatically synchronized to other related applications. For example, the user adjusts the resolution of the camera in the video conference application, and when switching to the live application, the resolution of the camera will also be automatically adjusted to the same value, without the user needing to set again. This consistency not only improves the user experience, but also reduces the problems that may be caused by inconsistent settings of different applications.

[0007] In some embodiments, the control method of the camera further includes: when the first application is running, receiving a support control instruction of the first application; receiving a preview operation of the user on the camera control interface; according to the support control instruction and the preview operation, sending a preview instruction to the first application; and according to the preview instruction, controlling the first application to enter a preview interface, the preview interface being used to display a camera image. In the embodiments of the present application, the user does not need to frequently switch between different applications to view the camera image, but can quickly enter the preview interface through the operation on the camera control interface. This greatly saves time and improves work efficiency, especially for scenes that need to quickly capture instant pictures.

[0008] In some embodiments, after the step of performing the function setting of the camera according to the second trigger operation, the control method of the camera further comprises: opening a second application program in the first user interaction interface, the second application program being matched with the camera control interface; and controlling the second application program to follow the function setting of the camera control interface. The embodiments of the present application can open a second application program matched with the camera control interface in the first user interaction interface after completing the function setting of the camera, and realize the function setting of the application program following the camera control interface, thereby greatly improving the convenience and consistency of the user in using the camera in different application scenarios. When the user completes a specific function setting using the camera control interface, if the camera needs to be used in another application program, the user does not need to perform a cumbersome setting operation again. The system can automatically identify the matching relationship between the second application program and the camera control interface, and apply the previous setting to the second application program, so that the user can seamlessly switch between different applications without affecting the use experience due to the difference in camera settings of different applications.

[0009] In some embodiments, the camera control interface is an application interface of a camera control program, and the control method of the camera further comprises: confirming that an instruction of opening a camera setting interface of a first application program is received, calling the camera control program, and performing camera control through the camera control interface. The embodiments of the present application realize seamless switching and cooperative work between different application programs, and the user can complete the control of the camera without switching between multiple interfaces. For example, when the user uses a specific photography application program and needs to adjust the camera parameters, the system can quickly call the camera control program, set through the unified camera control interface without interrupting the use of the current application program, thereby improving the smoothness and continuity of the operation.

[0010] In some embodiments, the control method of the camera further comprises: receiving a preview operation of the user on the camera setting interface of the first application program; opening a preview interface of the first application program according to the preview operation; and calling the camera control program to control the preview interface. The embodiments of the present application realize that the user can directly perform a preview operation on the camera setting interface of the first application program without switching to other interfaces or performing a complex operation process. This greatly improves the convenience of the user operation, and enables the user to more quickly view the shooting picture of the camera and understand the shooting effect in time. Moreover, the camera control program is called to control the preview interface, thereby realizing a unified control mode. Whether the user is performing a camera parameter setting or viewing a preview picture, the user can perform the operation through the same camera control program, thereby avoiding the trouble caused by the difference in control modes between different interfaces.

[0011] In some embodiments, the camera control method further includes: when a third application is running, receiving a user's preview operation on the camera settings interface of the third application, wherein the third application and the camera control interface are not compatible; according to the preview operation, overlaying the displayed camera control interface on the camera settings interface of the third application; and entering the preview interface on the camera control interface. In this embodiment, after a user performs a preview operation on the camera settings interface of the third application, the camera control interface can be directly overlaid on that interface and the user can enter the preview interface, which provides the user with an extremely convenient way to view the camera footage.

[0012] In some embodiments, receiving the user's first trigger operation includes: receiving the user's operation to open the sidebar; opening the sidebar interface according to the operation; and receiving the user's first trigger operation on the sidebar interface. This embodiment of the application avoids placing too many operation buttons on the main interface by receiving the first trigger operation on the sidebar interface after the user has opened it, thus maintaining the simplicity of the main interface. This prevents the main interface from appearing too cluttered and allows for convenient access to camera control functions when needed. The sidebar can be expanded and collapsed according to the user's needs, and can be hidden when the camera control function is not in use, thus not occupying screen space and improving screen space utilization.

[0013] In some embodiments, the function settings include at least one of the following: selecting a camera, setting the camera's working mode, and setting the camera's preset position.

[0014] Secondly, embodiments of this application provide a terminal device, including: at least one processor and at least one memory, wherein the memory stores a computer program, and when the program is executed by the processor, the processor performs the steps of the camera control method described above.

[0015] This application provides a camera control method and a terminal device. The camera control method is applied to the terminal device and includes: displaying a first user interface, which is the operating interface of the terminal device; receiving a first trigger operation from a user; overlaying a camera control interface onto the first user interface based on the first trigger operation, the camera control interface being used to configure the functions of the camera connected to the terminal device; receiving a second trigger operation from the user on the camera control interface; configuring the functions of the camera based on the second trigger operation; and controlling the first application to follow the camera control interface in configuring its functions when it is confirmed that the terminal device is running a first application matching the camera control interface. The camera control method and terminal device provided in this application, by directly responding to the first trigger operation and overlaying the camera control interface onto the operating interface of the terminal device, allow users to quickly configure camera functions without interrupting the current task, greatly improving the convenience and smoothness of operation. Furthermore, it enables the application to be controlled to follow the camera control interface in configuring its functions, meaning that users can adjust the parameters of both the camera and related applications simultaneously through a centralized control interface, achieving unified camera settings and ensuring consistency in settings across different applications using the camera. Attached Figure Description

[0016] One or more embodiments are illustrated by way of example with reference to the accompanying drawings. These illustrations do not constitute a limitation on the embodiments. Elements having the same reference numerals in the drawings are denoted as similar elements. Unless otherwise stated, the figures in the drawings are not to be limited by scale.

[0017] Figure 1 This is a schematic diagram of a camera control system provided in an embodiment of this application;

[0018] Figure 2 This is a schematic diagram of the structure of a terminal device provided in an embodiment of this application;

[0019] Figure 3 This is a schematic flowchart of a camera control method provided in an embodiment of this application;

[0020] Figure 4 This is a flowchart illustrating the first triggering operation of receiving a user, as provided in an embodiment of this application.

[0021] Figure 5 This is a flowchart illustrating the control of the second application provided in an embodiment of this application;

[0022] Figure 6This is a flowchart illustrating the process of receiving a user's preview command on the camera control interface and entering the preview interface, as provided in an embodiment of this application.

[0023] Figure 7 This is a flowchart illustrating the process of receiving a user's preview operation and entering the preview interface on the camera settings interface of the first application, as provided in an embodiment of this application.

[0024] Figure 8 This is a flowchart illustrating the process of receiving a user's preview operation and entering the preview interface on the camera settings interface of a third application, as provided in an embodiment of this application.

[0025] Explanation of icon numbers:

[0026] Reference Name Reference Name 1000 Control system of a camera 101 Processor 100 Terminal device 102 Memory 200 Camera Detailed Implementation

[0027] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and thoroughly described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. It should be understood that the specific embodiments described herein are only used to explain this application and are not intended to limit this application.

[0028] The technical features involved in the various embodiments of this application described below do not conflict with each other and can be combined with each other.

[0029] Although the functional modules are divided in the device schematic diagram and the logical sequence is shown in the flowchart, in some cases, the steps may be performed in a different order than those shown in the flowchart.

[0030] When an element is described as "connected" to another element, it can be directly connected to the other element, or there may be one or more intervening elements between them.

[0031] The terms "first," "second," etc., used in the specification and claims of this application are used to distinguish similar objects and are not used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first," "second," etc., are generally of the same class and are not limited in number; for example, a first object can be one or more.

[0032] As device applications continue to evolve and expand, a series of issues worthy of in-depth analysis have gradually emerged. On the one hand, rapid technological development drives the continuous emergence of new applications, bringing users an extremely rich array of functional options and fully demonstrating the remarkable achievements of technological progress. However, from another perspective, the number of applications installed on user devices has increased dramatically, which undoubtedly makes application management and use more complex and challenging.

[0033] In the crucial area of ​​camera control access, the current situation suffers from numerous drawbacks. Firstly, the camera control access methods vary significantly across different applications, placing a heavy burden on users. For ordinary users unfamiliar with technical operations, switching applications means adapting to entirely new operating methods each time. For example, some applications may cleverly hide the camera control access under multiple menus, requiring users to click repeatedly to find it; while other applications may place the access in an easily overlooked, inconspicuous corner of the interface. This frequent adaptation process undoubtedly consumes a significant amount of users' time and energy.

[0034] Furthermore, because different applications have different camera control entry points, it's difficult for users to accurately remember the exact location of each application. This means that when users need to use the camera function of a specific application, they often have to spend a lot of time recalling or painstakingly searching for the entry point again. Moreover, as the number of applications continues to increase, this memory burden grows exponentially, causing significant confusion and inconvenience for users. For new users, facing numerous applications with different camera control entry points, the learning curve becomes extremely steep. They need to explore and learn how to access the camera control interface for each application, which not only wastes valuable time but can also frustrate and discourage them, thus greatly reducing their acceptance of new applications.

[0035] From the perspective of operational habits and cognition, the differences in camera control access points across different applications make it difficult for users to develop consistent operating habits. For example, in one application, a user might habitually access the camera control interface by clicking a specific icon on the screen; while in another application, it might require swiping the screen, long-pressing a button, or using specific gestures. This confusing operational habit forces users to constantly adjust their thinking and action patterns when using different applications, easily leading to operational errors. Simultaneously, users' perception of camera control also varies depending on the application. In some applications, the camera control interface is designed to be simple and clear, easy for users to understand and operate; while in others, the interface may be complex and cluttered, leaving users confused. This inconsistency in perception seriously affects users' confidence and satisfaction with the camera function. Furthermore, the inconsistent camera control access points disrupt the continuity of the user experience. Users expect a consistent experience when using different applications, but due to the lack of a unified camera control access point, they cannot easily switch between and use the camera function in different applications, which is undoubtedly a significant challenge for users who frequently use the camera function.

[0036] In conclusion, the inconsistent camera control interfaces on user devices have already severely impacted user experience and application development efficiency. This problem will become even more pronounced as the number of applications continues to increase.

[0037] Based on this, embodiments of this application provide a camera control method and terminal device. By overlaying the camera control interface on the terminal device's operating interface, users can quickly find the camera control entry point through a unified trigger operation, regardless of the application scenario. This eliminates the need to adapt to different camera control entry points for different applications, greatly reducing the user's learning cost.

[0038] Please see Figure 1 , Figure 1 This is a schematic diagram of a camera control system provided in an embodiment of this application.

[0039] This application provides a camera control system 1000, which includes a terminal device 100 and at least one camera 200. The camera 200 is communicatively connected to the terminal device 100.

[0040] The camera 200 and the terminal device 100 can be connected via a wired interface or a wireless network. It is understood that the camera 200 includes cameras, webcams, and other video recording devices, while the terminal device 100 includes network-enabled devices such as mobile phones, tablets, and computer terminals. Wired interfaces include USB, HDMI, VGA, DVI, and DisplayPort interfaces, and wireless networks include Bluetooth and Wi-Fi.

[0041] In this embodiment, the camera 200 used includes devices capable of taking or recording images, such as cameras and webcams. These cameras include cameras of different brands, types, and models. The camera provides a communication interface to the terminal device 100, allowing the terminal device 100 to acquire and identify the camera's parameter information, thereby enabling the terminal device 100 to control the camera.

[0042] Please see Figure 2 , Figure 2 This is a schematic diagram of the structure of a terminal device provided in an embodiment of this application.

[0043] This application provides a terminal device 100, which includes at least one processor 101 and at least one memory 102. The memory 102 stores a computer program that, when executed by the processor 101, causes the processor 101 to perform the steps of the camera control method in any of the following method embodiments.

[0044] Processor 101 and memory 102 can be connected via a bus or other means. Figure 2 Taking the example of a connection between China and Israel via a bus.

[0045] The processor 101 provides computing and control capabilities to control the terminal device 100 to perform corresponding tasks, such as controlling the terminal device 100 to perform a camera control method as described in any of the following method embodiments, including: displaying a first user interface, the first user interface being the operating interface of the terminal device; receiving a first trigger operation from a user; displaying a camera control interface superimposed on the first user interface according to the first trigger operation, the camera control interface being used to configure the functions of the camera connected to the terminal device; receiving a second trigger operation from a user on the camera control interface; configuring the functions of the camera according to the second trigger operation; and when it is confirmed that the terminal device is running a first application program that matches the camera control interface, controlling the first application program to follow the camera control interface in configuring its functions.

[0046] By overlaying the camera control interface onto the terminal device's operating interface, users can quickly find the camera control entry point through a unified trigger operation, regardless of the application scenario. This eliminates the need to adapt to different camera control entry points for different applications, greatly reducing the user's learning cost.

[0047] Processor 101 can be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), a hardware chip, or any combination thereof; it can also be a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a programmable logic device (PLD), or a combination thereof. The aforementioned PLD can be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL), or any combination thereof.

[0048] The memory 102, as a non-volatile computer-readable storage medium, can be used to store non-volatile software programs, non-volatile computer-executable programs, and modules, such as the program instructions / modules corresponding to the camera control method in the embodiments of the present invention. The processor 101 executes various functional applications and data processing of the terminal device by running the non-volatile software programs, instructions, and modules stored in the memory 102, thereby implementing the camera control method of the above-described method embodiments.

[0049] Memory 102 may include volatile memory (VM), such as random access memory (RAM); memory 102 may also include non-volatile memory (NVM), such as read-only memory (ROM), flash memory, hard disk drive (HDD), solid-state drive (SSD), or other non-transitory solid-state storage devices; memory 102 may also include combinations of the above types of memory.

[0050] Memory 102 may include high-speed random access memory, and may also include non-volatile memory, such as at least one disk storage device, flash memory device, or other non-volatile solid-state storage device. In some embodiments, memory 102 may optionally include memory remotely located relative to processor 101. Examples of the above-described networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.

[0051] One or more modules are stored in memory 102 and, when executed by one or more processors 101, perform the camera control method in any of the following method embodiments, for example, perform the following described... Figure 3 , Figure 4 , Figure 5 The steps shown can also be implemented. Figure 6 The functions of each module.

[0052] In this embodiment, the terminal device 100 further includes a display for displaying an interface, or the terminal device 100 is externally connected to a display for displaying an interface. The terminal device 100 may also have wired or wireless network interfaces, a keyboard, and input / output interfaces for input and output. The terminal device 100 may also include other components for implementing device functions, which will not be described in detail here.

[0053] Please see Figure 3 , Figure 3 This is a schematic flowchart of a camera control method provided in an embodiment of this application.

[0054] The camera control method is applied to a terminal device; specifically, the processor of the terminal device is the main body that executes the camera control method.

[0055] like Figure 3 As shown, the camera control method includes:

[0056] Step S1: Display the first user interaction interface, which is the operating interface of the terminal device.

[0057] The user interface (UI) of a terminal device refers to the interface displayed to the user during normal operation. Elements within the UI can include application icons and shortcuts, status information, notification bars, taskbars, or navigation bars. The UI is the primary interface for user interaction with the device. Users can perform various operations on this interface, such as opening applications, adjusting settings, and viewing information. As the device is used and different applications are running, the UI will continuously change. For example, when a new notification arrives, the notification bar will display a corresponding prompt; when a user opens an application, the UI may switch to that application's interface. Users can personalize the UI to some extent according to their preferences, such as changing wallpapers, adjusting icon layouts, and setting themes. In short, the UI is a crucial window for user interaction with the device.

[0058] Step S2: Receive the user's first trigger operation.

[0059] The first trigger operation is used to trigger the overlay display of the camera control interface on the first user interaction interface.

[0060] The user's first trigger action is typically received through at least one of the following methods: touch sensing, physical button, sensor detection, voice recognition, etc.

[0061] In touch sensing, devices with touchscreens, such as smartphones and tablets, receive trigger operations by detecting the user's touch actions on the screen. For example, when a user taps a specific area on the screen, swipes, or performs a long press, the device's touch sensor detects these actions and converts them into electrical signals, which are then transmitted to the device's operating system for processing. Touchscreens can accurately detect information such as the user's touch location, touch pressure, and touch duration, thereby enabling various different trigger operation methods.

[0062] Among these, some terminal devices are equipped with physical buttons, which users can press to trigger specific operations. Examples include the power button and volume buttons on a mobile phone. When a user presses a physical button, the device's internal circuitry detects the pressed state and triggers the corresponding action. Physical buttons typically offer clear tactile feedback, allowing users to operate more accurately.

[0063] In terms of sensor detection, some terminal devices can also receive user-triggered actions through built-in sensors. For example, some devices can detect user shaking movements using an accelerometer or device rotation movements using a gyroscope. When the device detects a specific sensor signal, it can interpret it as a user-triggered action. Sensor detection enables more natural and intuitive operation methods, such as waking up the screen or switching applications by shaking the device.

[0064] For voice recognition, some smart terminal devices support this function, allowing users to trigger operations via voice commands. When a user speaks specific keywords or phrases, the device's microphone captures the sound signal and converts it into text commands using a voice recognition algorithm. The device's operating system then executes the corresponding operations based on these commands. Voice recognition enables a more convenient and natural way of operating, especially when the user's hands are occupied or touch operation is inconvenient.

[0065] In some embodiments, please refer to Figure 4 The above step S2: receiving the user's first trigger operation includes:

[0066] Step S21: Receive the user's action to open the sidebar.

[0067] Step S22: Open the sidebar interface according to the sidebar opening operation.

[0068] Step S22: Receive the user's first trigger operation on the sidebar interface.

[0069] The "Open Sidebar" option is used to open the sidebar interface.

[0070] The sidebar interface includes multiple icons. Among these icons is an icon for the camera control interface, which may include the word "Camera" or other icons.

[0071] The user's action of opening the sidebar is typically received through at least one of the following methods: touch sensing, physical button, sensor detection, voice recognition, etc.

[0072] Specifically, when a user clicks the camera control interface icon on the sidebar interface, the first trigger operation is received.

[0073] In this embodiment, by receiving the first trigger operation on the sidebar interface after the user opens it, the presence of too many operation buttons on the main interface can be avoided, maintaining its simplicity. This prevents the main interface from appearing overly cluttered while allowing convenient access to camera control functions when needed. The sidebar can be expanded and collapsed according to the user's needs, and can be hidden when the camera control function is not in use, thus not occupying screen space and improving screen space utilization.

[0074] Step S3: Based on the first trigger operation, the camera control interface is overlaid on the first user interaction interface. The camera control interface is used to configure the functions of the camera connected to the terminal device.

[0075] Specifically, the methods for overlaying the camera control interface on the first user interface may include layer overlay, pop-up window, transparent overlay, etc.

[0076] In the case of layer overlay, the operating system of the terminal device typically supports the display of multiple layers. Upon receiving the first trigger operation, the system creates a new layer on top of the current user interface layer to display the camera control interface. This new layer partially or completely overlays the original interface, thus achieving the overlay display effect. For example, on a smartphone, when a user swipes up from the bottom of the screen to bring up the control center, the control center interface is overlaid on the currently running application interface using a layer overlay method.

[0077] In the pop-up window method, the camera control interface can be displayed as a pop-up window. When the first trigger operation occurs, the system will pop up a window at a specific location on the screen; this window is the camera control interface. The pop-up window can have different sizes and shapes and can be adjusted and moved as needed. For example, in some computer software, when a user clicks a function button, a settings window will pop up for configuring relevant parameters.

[0078] In the transparent overlay method, the camera control interface can be superimposed on the first user interface in a semi-transparent form. This allows users to see part of the underlying operating interface through the semi-transparent camera control interface, enabling them to configure camera functions without completely obscuring the original interface content. This method is frequently used in some graphic design software, allowing users to adjust parameters through a semi-transparent toolbar while performing drawing operations.

[0079] In some embodiments, the method of overlaying the camera control interface on the first user interface may include a floating window approach. A floating window is typically a small, independent, movable window that appears on the terminal device's screen and can be freely adjusted in position and size to a certain extent. This floating window represents the camera control interface and is displayed simultaneously on the screen with the first user interface, presenting an overlay effect. The floating window approach can make full use of limited screen space. Users can quickly access the camera control interface through the floating window while performing other operations, conveniently adjusting shooting parameters.

[0080] In this embodiment, the camera control interface is a user interface used to configure the functions of the camera connected to the terminal device. In some embodiments, the function settings include at least one of the following: selecting a camera, setting the camera's working mode, setting the camera's preset camera position, etc.

[0081] Regarding the camera selection function, when multiple cameras are connected to the terminal device, the camera control interface can provide an option list, allowing users to select the specific camera they wish to use. For example, in a video conferencing system, a user may have connected multiple external cameras; this function allows for easy switching between different cameras to obtain the optimal shooting angle and image quality. This function can be implemented through drop-down menus, icon selection, or list display, making it convenient for users to quickly find and switch to the desired camera.

[0082] Among the features, the camera's operating mode settings allow users to adjust the camera's operation according to different shooting needs. Specifically, camera operating modes include: portrait tracking, sound source tracking, and fixed panorama. Portrait tracking is a camera function that uses image recognition technology to automatically identify people in the frame and continuously track their movement. The camera analyzes feature points in the image, such as the person's outline, skin tone, and facial features, to determine the person's position and continuously adjusts the lens direction and focus to ensure the person remains centered or in a specific area of ​​the frame. For example, in a video conference, when a speaker moves around the room, a camera equipped with portrait tracking can automatically follow the speaker, ensuring they are always clearly visible in the frame. Sound source tracking uses microphone arrays or other audio sensors to detect the direction of sound and automatically adjusts the camera's direction to align with the sound source. Cameras typically combine audio signal processing technology and motor drive systems to achieve fast and accurate sound source tracking. For example, in a conference room, when someone speaks, a camera with sound source tracking can automatically turn towards the speaker, capturing the sound and ensuring a clear image. In fixed panoramic mode, the camera remains in a fixed position and angle, capturing a wide panoramic view. Typically, the camera uses a wide-angle or fisheye lens to capture as much of the surrounding environment as possible. For example, in a monitoring room, a fixed panoramic camera can cover the entire room, providing comprehensive surveillance footage. Users can switch the camera's operating mode via buttons, menus, or quick settings.

[0083] The feature for setting preset camera positions allows users to pre-select specific camera locations and angles, enabling quick switching to these preset positions when needed. For example, in a video surveillance system, users can set multiple different preset camera positions, such as panoramic views or close-up views of specific areas. When viewing footage from different locations, simply selecting the corresponding preset camera position allows for quick switching of camera positions and angles. This function can be implemented through parameter adjustments in the settings interface, virtual joystick operation, or selection from the preset camera position list.

[0084] Step S4: Receive the user's second trigger operation on the camera control interface.

[0085] Specifically, the second triggering action is usually a specific interactive behavior performed by the user on the camera control interface, which may include: clicking a specific button, swiping, selecting options, etc.

[0086] Clicking a specific button, such as a button on the camera control interface for switching working modes (e.g., switching from human tracking to sound source tracking), triggers a second action.

[0087] A sliding operation is when a user adjusts a parameter value on the camera control interface using a slider, such as adjusting brightness or contrast. This sliding action can be considered a secondary trigger operation.

[0088] The camera control interface has a drop-down menu or option list. Users can select one of the options, such as selecting a different camera, selecting the camera's working mode, or selecting the camera's preset position. This also constitutes a second trigger operation.

[0089] Step S5: Configure the camera's functions according to the second trigger operation.

[0090] The function settings include at least one of the following: selecting a camera, setting the camera's working mode, and setting the camera's preset position.

[0091] Specifically, after the user performs the second trigger operation, the terminal device will make corresponding adjustments to the camera based on the second trigger operation.

[0092] For example, if the second triggering action is clicking the "Select Camera" button on the camera control interface, the terminal device will pop up a list displaying all currently connected cameras, from which the user can select and switch to the desired camera. If the second triggering action is clicking the "Set Camera Working Mode" button, a drop-down menu will appear, containing mode options such as human tracking, sound source tracking, and fixed panorama. After the user selects a mode, the terminal device will send a command to the camera to switch to the corresponding working mode. When the second triggering action is selecting "Set Camera Preset Position," a series of preset position options may be displayed, such as a conference room panorama or a speaker close-up. After the user selects a mode, the terminal device will adjust the camera's position and angle parameters to achieve the preset position effect.

[0093] Furthermore, if the second trigger operation involves adjusting parameters via a slider, such as adjusting the focal length, the terminal device will send a specific focal length adjustment command to the camera based on the slider's position, causing the camera's focal length to change accordingly. Adjustments to parameters such as exposure and contrast follow a similar principle; the terminal device sends corresponding commands to the camera based on the user's actions, thus enabling the camera's function settings.

[0094] In the user's second trigger operation, the camera can be configured with one or more functions.

[0095] Step S6: When it is confirmed that the terminal device is running a first application that matches the camera control interface, control the first application to follow the camera control interface to perform function settings.

[0096] The first application is an application that is compatible with the camera control interface. An application compatible with the camera control interface refers to an application that establishes a matching relationship with the camera control interface through specific protocols or specific commands.

[0097] In some embodiments, the first user interface displays the camera settings interface of the first application. Step S6: Controlling the first application to perform function settings in accordance with the camera control interface specifically includes: controlling the camera settings interface of the first application to change synchronously with the camera control interface, so that the first application performs function settings in accordance with the camera control interface.

[0098] Specifically, first, the terminal device needs to identify the primary application running that matches the camera's control interface. This can be determined by examining the application's specific identifier, registration information, or camera-related interfaces. For example, some video conferencing applications may register their camera usage requests with the system upon startup.

[0099] Next, after confirming the existence of the first application, a communication channel is established between the terminal device and that application. This can be achieved through inter-process communication mechanisms provided by the operating system, such as message passing, shared memory, or specific communication protocols.

[0100] Then, any changes on the camera control interface are continuously monitored, including changes to function settings caused by user-triggered actions. For example, when the user switches the camera's operating mode, selects a different preset camera position, or adjusts other parameters, the camera control interface records these changes. Once a change is detected on the camera control interface, this change information is immediately transmitted to the first application via an established communication channel. The transmitted information may include the new operating mode, preset camera position parameters, adjusted camera parameters, etc.

[0101] Then, after receiving the change information from the camera control interface, the first application makes corresponding adjustments to achieve synchronization. For example, if the camera control interface switches to human tracking mode, the first application may need to adjust its video display layout or image processing algorithm to adapt to the human tracking output. If the preset camera position changes, the application may need to adjust the window size or viewing angle to match the new camera angle.

[0102] In this embodiment, the camera settings interface of the first application is displayed on the first user interface, and the settings interface and the camera control interface are synchronized. Users no longer need to switch between different interfaces to find camera settings options; all settings are centralized on a unified interface, allowing users to quickly and intuitively configure the camera. Adjusting camera parameters, selecting working modes, or setting preset camera positions can all be easily done on the first user interface, greatly saving users' time and effort. Furthermore, the synchronized mechanism ensures consistency between different applications and camera control. When the user operates on the camera control interface, the camera settings interface of the first application changes in real time. This means that camera parameters set in one application can be automatically synchronized to other related applications. For example, if a user adjusts the camera resolution in a video conferencing application, the camera resolution will automatically adjust to the same value when switching to a live streaming application, without requiring the user to set it again. This consistency not only improves the user experience but also reduces problems that may arise from inconsistencies in settings between different applications.

[0103] In some embodiments, after performing synchronization adjustments, the first application can send feedback information to the terminal device to confirm that it has successfully followed the function settings made by the camera control interface. The feedback information may include the current status of the application, whether the new settings were successfully applied, etc. The terminal device can verify whether the synchronization was successful by comparing the status information of the camera control interface and the first application. For example, it can check whether their operating modes are consistent, whether the preset camera position parameters are the same, etc. If inconsistencies are found, further adjustments can be made or error messages can be displayed.

[0104] In this embodiment, by directly responding to the first trigger operation and overlaying the camera control interface on the terminal device's running interface, the user can quickly configure camera functions without interrupting the current task, greatly improving the convenience and smoothness of operation. Furthermore, it enables the application to follow the camera control interface in function settings, meaning that users can adjust camera and related application parameters simultaneously through a centralized control interface, achieving unified camera settings and ensuring consistency in settings across different applications using the camera.

[0105] Please see Figure 5 , Figure 5 This is a flowchart illustrating the control of the second application provided in an embodiment of this application.

[0106] In some embodiments, after performing step S5: setting the camera's functions according to the second trigger operation, the camera control method further includes:

[0107] Step S7: Open the second application in the first user interface. The second application is matched with the camera control interface.

[0108] The second application is another application, besides the first application, that is compatible with the camera control interface. An application compatible with the camera control interface refers to an application that establishes a matching relationship with the camera control interface through specific protocols or specific commands.

[0109] Specifically, the method for matching the second application with the camera control interface can be as follows: the camera control interface sends a matching protocol to the second application, and then the second application returns a matching instruction according to the matching protocol, thereby establishing a matching relationship between the second application and the camera control interface.

[0110] It should be noted that the first application and the second application can be any application running on the terminal device.

[0111] Step S8: Control the second application to follow the camera control interface to set functions.

[0112] Specifically, the terminal device controls the second application to make corresponding adjustments to follow the camera control interface to achieve synchronization. For example, if the camera control interface switches to human tracking mode, the second application may need to adjust its video display layout or image processing algorithm to adapt to the human tracking output. If the preset camera position changes, the second application may need to adjust the window size or viewing angle to match the new camera angle.

[0113] This application embodiment allows users to open a second application matching the camera control interface on the first user interface after completing the camera's functional settings. This application then follows the camera control interface in its functional settings, significantly improving the convenience and consistency of camera use across different application scenarios. When a user completes specific functional settings using the camera control interface, they no longer need to perform cumbersome setup procedures again if they need to use the camera in another application. The system automatically identifies the matching relationship between the second application and the camera control interface and synchronously applies the previous settings to the second application. This allows users to seamlessly switch between different applications without being affected by differences in camera settings between applications.

[0114] Please see Figure 6 , Figure 6 This is a schematic diagram illustrating the process of receiving a user's preview command on the camera control interface and entering the preview interface, as provided in an embodiment of this application.

[0115] In some embodiments, the camera control method further includes:

[0116] Step S9: When the first application is running, receive the support control instructions of the first application.

[0117] Among them, the support for control commands can be the commands sent by the first application after the first application and the camera control interface have established a preview match.

[0118] Specifically, the method for establishing a preview match between the first application and the camera control interface can be as follows: the camera control interface sends a preview match protocol to the first application, and then the first application returns a support control command according to the match protocol, thereby establishing a preview match relationship between the first application and the camera control interface.

[0119] Step S10: Receive the user's preview operation on the camera control interface.

[0120] In this context, previewing typically involves specific user interactions on the camera control interface, such as clicking a button or issuing a voice command. For example, the camera control interface might have a "Preview" button; clicking this button initiates a preview.

[0121] Step S11: Send a preview command to the first application according to the support control command and preview operation.

[0122] Specifically, when the terminal device receives a support control command from the first application and a preview operation from the user on the camera control interface, it determines that the first user needs to preview, and at this time the terminal device sends a preview command to the first application.

[0123] This preview command is used to trigger the first application to enter the preview interface.

[0124] Step S12: According to the preview instruction, control the first application to enter the preview interface, which is used to display the camera's video feed.

[0125] Specifically, the preview interface displays the image content captured by the camera in real time. This means that users can see the scene in front of the camera lens on this interface, just like looking through the camera's viewfinder. The image update speed is usually fast to ensure that users have a smooth visual experience. For example, in video conferencing applications, the preview interface displays the image captured by the user's own camera, allowing users to check their appearance and background environment before starting the meeting.

[0126] In this embodiment, users do not need to frequently switch between different applications to view the camera footage; they can quickly enter the preview interface through operations on the camera control interface. This greatly saves time and improves work efficiency, especially helpful for scenarios that require quickly capturing fleeting moments.

[0127] In some embodiments, the camera control interface is the application interface of the camera control program, and the camera control method further includes: confirming receipt of an instruction to open the camera settings interface of the first application, calling the camera control program, and controlling the camera through the camera control interface.

[0128] The camera control interface is the application interface of the camera control program. The camera control program can control the camera's functions and can establish compatibility with other applications such as the first application and the second application.

[0129] Specifically, the instruction to open the camera settings interface of the first application can be triggered by user actions or system events. Users can trigger the instruction in various ways, such as clicking specific icons, buttons, or menu options within the first application—elements explicitly associated with camera settings. For example, in a video conferencing application, there might be a "Camera Settings" button; clicking this button will trigger the instruction to open the camera settings interface. Specific gestures can also trigger the instruction, such as swiping or long-pressing on the screen. The terminal device recognizes these gestures and associates them with opening the camera settings interface. Additionally, certain system events can also trigger the instruction. For instance, when the first application launches for the first time, if the application needs to use a camera, it might automatically trigger the instruction to open the camera settings interface for initial setup. Or, when the terminal device connects to a new camera, the system can detect this event and prompt the user to open the camera settings interface for configuration.

[0130] Terminal devices can invoke the camera control program through predefined application programming interfaces (APIs). Once the instruction to open the camera settings interface of the first application is received, the first application can communicate with the camera control program by calling these APIs. For example, the first application can send a specific request to the operating system, which then forwards the request to the camera control program to activate its corresponding function. Alternatively, the inter-process communication mechanisms provided by the operating system can be used to invoke the camera control program. For instance, through message passing, shared memory, etc., the first application can send a start signal to the camera control program, triggering its execution.

[0131] Specifically, the camera control interface can also be used to configure the functions of the cameras connected to the aforementioned terminal devices. Furthermore, when the terminal device is in the first interactive interface, the functions displayed in the overlaid camera control interface are set to all the camera function settings available on the terminal device.

[0132] This application embodiment achieves more efficient and convenient camera control by tightly integrating the camera settings interface with the camera control program. Upon receiving a command to open the camera settings interface of the first application, the system can quickly invoke the camera control program, providing the user with a direct and dedicated channel to manage the camera. This design eliminates the need for users to navigate through complex system settings; instead, they can quickly access the camera control interface relevant to the current task in specific application scenarios.

[0133] Please see Figure 7 , Figure 7 This is a flowchart illustrating the process of receiving a user's preview operation and entering the preview interface on the camera settings interface of the first application, as provided in an embodiment of this application.

[0134] In some embodiments, such as Figure 7 As shown, the camera control method also includes:

[0135] Step S14: Receive the user's preview operation on the camera settings interface of the first application.

[0136] Previewing typically involves specific user interactions on the camera settings interface, such as clicking a button or using voice commands. For example, a "Preview" button on the camera settings interface triggers a preview when clicked.

[0137] Step S15: Open the preview interface of the first application according to the preview operation.

[0138] Specifically, when a user's preview operation is received on the camera settings interface of the first application, the preview interface is opened in the first application.

[0139] Step S16: Call the camera control program and control the preview interface through the camera control program.

[0140] Specifically, since the first application is compatible with the camera control interface (camera control program), the preview interface can be controlled through the camera control program. This includes controlling the scaling of the preview interface, controlling the rotation of the camera corresponding to the preview interface, and controlling the selection of the camera corresponding to the preview interface (e.g., switching from capturing images from camera A to capturing images from camera B), etc.

[0141] This application embodiment allows users to directly preview the camera settings interface within the first application, without switching to other interfaces or performing complex procedures. This significantly improves user convenience, enabling users to quickly view the camera's footage and understand the shooting results promptly. Furthermore, by invoking the camera control program to control the preview interface, a unified control method is achieved. Whether the user is setting camera parameters or viewing the preview, they can operate through the same camera control program, avoiding the confusion caused by differences in control methods between different interfaces.

[0142] Please see Figure 8 , Figure 8 This is a flowchart illustrating the process of receiving a user's preview operation and entering the preview interface on the camera settings interface of a third application, as provided in an embodiment of this application.

[0143] In some embodiments, such as Figure 8 As shown, the camera control methods also include:

[0144] Step S17: When a third application is running, the user's preview operation is received on the camera settings interface of the third application. The third application and the camera control interface are not compatible.

[0145] The third application is incompatible with the camera control interface. This refers to any application on the terminal device that is incompatible with the camera control interface, other than the one compatible with it.

[0146] Previewing typically involves specific user interactions on the camera settings interface, such as clicking a button or using voice commands. For example, a "Preview" button on the camera settings interface triggers a preview when clicked.

[0147] Step S18: Based on the preview operation, overlay the camera control interface on the camera settings interface of the third application.

[0148] Specifically, since the third application is incompatible with the camera control interface, the camera control interface needs to be overlaid on the camera settings interface of the third application.

[0149] Step S19: Enter the preview interface on the camera control interface.

[0150] Specifically, users enter the preview interface from the camera control interface and control the preview interface from there.

[0151] Specifically, since the third application is incompatible with the camera control interface (camera control program), the camera control interface can be overlaid on the camera settings interface of the third application. Users can then control the preview interface from the camera control interface. This includes controlling the scaling of the preview interface, rotating the camera corresponding to the preview interface, and selecting the camera corresponding to the preview interface (e.g., switching from capturing footage from camera A to capturing footage from camera B).

[0152] In this embodiment, after a user performs a preview operation on the camera settings interface of the third application, the camera control interface can be directly overlaid on the interface and the user can enter the preview interface, which provides the user with an extremely convenient way to view the camera footage.

[0153] It should be noted that, in this embodiment, the camera settings options in the camera settings interfaces of the first application, the second application, and the third application may be different. For example, the "Select Camera" option in the camera settings interface of the first application may include selecting camera A and selecting camera B. The "Select Camera" option in the camera settings interface of the second application may include selecting camera A, selecting camera B, and selecting camera C. The "Select Camera" option in the camera settings interface of the third application may include selecting camera B, selecting camera C, and selecting camera D.

[0154] It should also be noted that in this embodiment, the first application and the second application are both compatible with the camera control interface, while the third application is not compatible with the camera control interface. The terminal device may also include multiple other applications compatible with the camera control interface, as well as multiple other applications not compatible with the camera control interface.

[0155] The camera control method provided in this application allows users to quickly configure camera functions without interrupting their current task by directly responding to a first trigger operation and overlaying the camera control interface on the terminal device's operating interface. This significantly improves the convenience and smoothness of operation. Furthermore, it enables the application to follow the camera control interface in function settings. This means users can adjust camera and related application parameters simultaneously through a centralized control interface, achieving unified camera settings and ensuring consistency in settings across different applications using the camera.

[0156] This application also provides a non-volatile computer-readable storage medium, such as a memory including program code, which can be executed by a processor to complete the camera control method in the above embodiments. For example, the non-volatile computer-readable storage medium may be a read-only memory (ROM), a random access memory (RAM), a compact disc read-only memory (CDROM), magnetic tape, floppy disk, and optical data storage device, etc.

[0157] This application also provides a computer program product, which includes one or more lines of program code. The program code is stored in a non-volatile computer-readable storage medium. The processor of an electronic device reads the program code from the non-volatile computer-readable storage medium and executes the program code to complete the method steps of the camera control method provided in the above embodiments.

[0158] It should be noted that the device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs.

[0159] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal (which may be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0160] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, and not to limit them; under the concept of the present invention, the technical features of the above embodiments or different embodiments can also be combined, the steps can be implemented in any order, and there are many other variations of different aspects of the present invention as described above, which are not provided in detail for the sake of brevity; although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features; and these modifications or substitutions 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 invention.

Claims

1. A method for controlling a camera, characterized in that, The camera control method, applied to terminal devices, includes: Display a first user interface, which is the operating interface of the terminal device; Receive the user's first trigger action; According to the first trigger operation, a camera control interface is overlaid on the first user interface. The camera control interface is used to set the functions of the camera connected to the terminal device. Receives a second trigger operation from the user on the camera control interface; Based on the second trigger operation, the camera's functions are configured; When it is confirmed that the terminal device is running a first application that matches the camera control interface, the first application is controlled to follow the camera control interface in setting functions.

2. The camera control method according to claim 1, characterized in that, The first user interface displays the camera settings interface of the first application, and controlling the first application to follow the camera control interface to perform function settings includes: The camera settings interface of the first application is controlled to change synchronously with the camera control interface, so that the first application can perform function settings in accordance with the camera control interface.

3. The camera control method according to claim 1, characterized in that, The camera control method also includes: When the first application is running, receive the support control instructions of the first application; The camera control interface receives user preview operations. Based on the support control command and the preview operation, send a preview command to the first application; According to the preview instruction, the first application is controlled to enter the preview interface, which is used to display the camera's video feed.

4. The camera control method according to claim 1, characterized in that, After performing the step of setting the camera's functions according to the second trigger operation, the camera control method further includes: Open the second application in the first user interface, and the second application is matched with the camera control interface; The second application is controlled to perform function settings following the camera control interface.

5. The camera control method according to claim 1, characterized in that, The camera control interface is the application interface of the camera control program, and the camera control method further includes: Upon receiving the instruction to open the camera settings interface of the first application, the camera control program is invoked, and the camera is controlled through the camera control interface.

6. The camera control method according to claim 5, characterized in that, The camera control method also includes: Receive the user's preview operation on the camera settings interface of the first application; According to the preview operation, open the preview interface of the first application; The camera control program is invoked, and the preview interface is controlled through the camera control program.

7. The camera control method according to claim 1, characterized in that, The camera control method also includes: When a third application is running, the user's preview operation is received on the camera settings interface of the third application, and the third application is not compatible with the camera control interface; Based on the preview operation, the camera control interface is overlaid on the camera settings interface of the third application; Enter the preview interface on the camera control interface.

8. The camera control method according to claim 1, characterized in that, The first trigger operation for receiving the user includes: Receive user requests to open the sidebar; Open the sidebar interface according to the described sidebar opening operation; The first trigger operation from the user is received on the sidebar interface.

9. The camera control method according to any one of claims 1-8, characterized in that, The functional settings include at least one of the following: Select the camera, set the camera's working mode, and set the camera's preset position.

10. A terminal device, characterized in that, include: At least one processor and at least one memory, wherein the memory stores a computer program that, when executed by the processor, causes the processor to perform the steps of the camera control method according to any one of claims 1-9.

Images