CN110087012B

CN110087012B - Camera control method and electronic equipment

Info

Publication number: CN110087012B
Application number: CN201910310356.8A
Authority: CN
Inventors: 黎晶; 郭东平
Original assignee: Huawei Technologies Co Ltd
Current assignee: Honor Device Co Ltd
Priority date: 2019-04-17
Filing date: 2019-04-17
Publication date: 2020-10-23
Anticipated expiration: 2039-04-17
Also published as: CN112422874B; CN110087012A; CN112422874A

Abstract

The embodiment of the application provides a control method of a camera and electronic equipment, relates to the technical field of terminals, and can avoid lifting the camera when a video call is not connected, so that the use experience of a user is improved, and the service life of the camera is prolonged. The method comprises the following steps: the electronic equipment receives a video call request from a first contact; responding to the video call request, the electronic equipment presents a first user interface, wherein a camera is contained in the shell when the first user interface is presented; the electronic equipment detects an event that the user accepts the video call request; in response to the event, the electronic device extends the camera from within the housing to outside the housing.

Description

Camera control method and electronic equipment

Technical Field

The present application relates to the field of terminal technologies, and in particular, to a camera control method and an electronic device.

Background

With the development of mobile internet technology, large-screen terminals have gradually become accepted by users and become a trend. Taking a mobile phone as an example of the electronic device, the screen occupation ratio of the mobile phone refers to a relative ratio of an area of a display screen of the mobile phone to an area of a front panel of the mobile phone. When the screen occupation ratio is higher, the display area of the mobile phone is larger, and the display effect obtained by the user is better.

In order to increase the screen occupation ratio of the terminal as much as possible, some manufacturers set up a lifting camera in the mobile phone. As shown in fig. 1, a mobile phone 11 is provided with a panel 12 that can be lifted and lowered, and the panel 12 is provided with a device such as a camera 13. In a scene where the camera is needed, the mobile phone can automatically lift the panel 12 for shooting. In a scene without using a camera, the mobile phone can retract the panel 12 into the mobile phone, so that a display screen with a larger area can be arranged on the front panel of the mobile phone.

When the mobile phone 11 runs the application with the video chat function, if a video call request sent by a contact is received, the application will call an interface for opening a camera in response to the video call request, and trigger the mobile phone 11 to automatically raise the camera 13 on the panel 12. However, at this time, the user has not accepted the video call request, and the use experience of the user is affected by the automatic rising of the camera 13. In addition, if the user rejects the video call request, or does not answer the video call request, the mobile phone 11 will automatically retract the camera 13, and the back-and-forth expansion of the camera 13 will reduce the service life of the camera 13 and the related components.

Disclosure of Invention

The application aims to provide a control method of a camera and electronic equipment, which can avoid lifting the camera when a video call is not connected, so that the use experience of a user is improved, and the service life of the camera is prolonged.

The above and other objects are achieved by the features of the independent claims. Further implementations are presented in the dependent claims, the description and the drawings.

In a first aspect, a method for controlling a camera is provided, which may be implemented in an electronic device having a camera, wherein the camera may be housed in a housing of the electronic device or extend out of the housing. The control method specifically comprises the following steps: the electronic device may receive a video call request from a first contact. For example, an electronic device may receive a video call request sent by a first contact using another electronic device. For another example, the electronic device may receive a video call request from a first contact forwarded by an application server. In response to the video call request, the electronic device may present a first user interface. For example, the first user interface may be interface 801 shown in FIG. 8. At this time, the camera of the electronic device is accommodated in the housing without extending out. When the electronic device detects an event that the user accepts the video call request, the electronic device may extend the camera from the housing to the outside of the housing in response to the event.

It can be seen that, after the electronic device receives the video call request, the electronic device does not extend the camera housed in the housing until it is not detected that the user accepts the video call request. The electronic device will raise the camera only when the electronic device detects that the user has accepted the video call request. Therefore, when the video call is not connected, the electronic equipment cannot pop up the camera to interfere the use experience of the user, and meanwhile, if the user does not answer the video call request, the electronic equipment can reduce the pop-up of the camera once, so that the service life of the lifting camera is prolonged.

In a possible implementation manner, the first user interface may include a first control (e.g., control 802 in fig. 8) for accepting the video call request, and a second control (e.g., control 803 in fig. 8) for rejecting the video call request; then, the event that the electronic device detects that the user accepts the video call request is: the electronic equipment detects the operation of selecting the first control by the user. That is to say, after the electronic device detects that the user selects the first control, it indicates that the user has accepted the video call request, and then the electronic device may extend the camera out of the housing from the housing.

In one possible implementation, after the electronic device receives the video call request from the first contact, the method may further include: the electronic equipment calls an audio manager to inquire a current audio mode; then, the event that the electronic device detects that the user accepts the video call request is: the electronic equipment inquires about the event that the audio mode is the call mode. That is, after the electronic device queries that the current audio mode is the call mode, it indicates that the user has accepted the video call request, and then the electronic device may extend the camera out of the housing from the housing.

For example, the electronic device invoking the audio manager to query the current audio mode may specifically include: the electronic equipment calls a getMode () function provided by an audio manager, wherein the return value of the getMode () function is the current audio mode; the audio MODE may be one of a CALL MODE _ IN _ COMMUNICATION, a ring MODE _ ringing, a phone MODE _ IN _ CALL, and a NORMAL MODE _ NORMAL.

In one possible implementation, after the electronic device receives the video call request from the first contact, the method may further include: the electronic equipment acquires a communication signaling sent to the server; then, the event that the electronic device detects that the user accepts the video call request is: the electronic device queries an event that the first field in the communication signaling is the first value. That is to say, after the electronic device queries that the first field in the communication signaling sent to the server is the first value, it indicates that the user has accepted the video call request, and then the electronic device can extend the camera from the inside of the housing to the outside of the housing.

In a possible implementation manner, the video call request may be sent by a first contact in the first application; then, before the electronic device detects that the user accepts the event of the video call request, the method may further include: the electronic device determines that the first application is a preset video call application. When the first application is a preset video call application, the electronic equipment can continuously detect whether the user accepts the video call request; otherwise, it is stated that the first application does not have the application permission to use the camera, and the electronic device does not need to continue to detect whether the user accepts the video call request.

In one possible implementation, after the electronic device protrudes the camera from the inside of the housing to the outside of the housing, the electronic device may further present a second user interface, where the second user interface includes an image captured by the electronic device using the camera. For example, after the electronic device extends out of the camera, an interface 1201 as shown in fig. 12 may be displayed. Of course, the electronic device may also display the image sent by the first contact in the third user interface in real time, so as to implement the video call process.

In one possible implementation, the electronic device may also present a third user interface during the process of extending the camera from inside the housing to outside the housing, for example, when the electronic device extends the camera, an interface 1101 as shown in fig. 11 (a) or (b) may be displayed. The third user interface may include a prompt for prompting the user that the camera is being turned on. For example, the prompt message may be a prompt 1102 shown in fig. 11 (a).

In a possible implementation manner, the second user interface may further include a first user image, where the first user image is a user image captured in a last capturing process. For example, the first user image may be the user image 1103 illustrated in fig. 11 (b). Alternatively, the electronic device may also perform blurring processing such as blurring on the first user image. In this way, the first user image may provide a more realistic visual presentation to the user during the period of time the user waits for the camera to be raised. Meanwhile, the first user image can be more softly transited to the user image acquired after the camera is lifted at the time, and user experience of the user is improved.

In addition, the method is also applicable to electronic equipment provided with a non-lifting camera, and the embodiment of the application does not limit the method.

In a second aspect, a method for controlling a camera is provided, which may be implemented in an electronic device having a camera, wherein the camera may be housed in a housing of the electronic device or extend out of the housing. The control method specifically comprises the following steps: the electronic equipment can receive a video call request sent by a first contact in a video call application (such as an application supporting a video call function, e.g. WeChat, contact, etc.); in response to the video call request, the electronic device may present a first user interface. For example, the first user interface may be interface 801 shown in FIG. 8. At this time, the camera of the electronic device is accommodated in the housing without extending out. And after receiving the video call request sent by the first contact, the electronic device may call the getMode () function provided by the audio manager to obtain a return value of the getMode () function, where the return value is the current audio mode. The audio MODE is one of a CALL MODE _ IN _ COMMUNICATION, a ring MODE _ ringing, a phone MODE _ IN _ CALL, or a NORMAL MODE _ NORMAL. If the return value of the getMode () function is a talk mode, indicating that the user has accepted the video call request, the electronic device may extend the camera from the inside of the housing to the outside of the housing. Meanwhile, in the process of extending the camera out of the shell, the electronic equipment can present a second user interface, and the electronic equipment can prompt the user that the camera is extending out in the second user interface. After the camera completely extends out of the shell, the electronic equipment can start the camera to start to collect images, and the collected images are displayed in a third user interface in real time, so that video communication with the first contact person is realized.

In a third aspect, an electronic device is provided, including: the camera can be accommodated in the shell of the electronic equipment or extends out of the shell; a touch screen; one or more processors; a memory; wherein one or more computer programs are stored in the memory; the processor is coupled with the camera, the touch screen and the memory, and when the electronic device runs, the processor executes one or more computer programs stored in the memory, so that the electronic device executes the control method of the camera.

In a fourth aspect, there is provided a computer storage medium comprising computer instructions which, when run on an electronic device, cause the electronic device to perform the method of controlling a camera according to any one of the first aspect.

In a fifth aspect, a computer program product is provided, which, when run on an electronic device, causes the electronic device to execute the method of controlling a camera according to any one of the first aspect.

It is to be understood that the electronic device according to the third aspect, the computer storage medium according to the fourth aspect, and the computer program product according to the fifth aspect are all configured to execute the corresponding method provided above, and therefore, the beneficial effects achieved by the electronic device can refer to the beneficial effects in the corresponding method provided above, and are not described herein again.

Drawings

Fig. 1 is a schematic view of an electronic device provided with a lift-type camera in the prior art;

fig. 2 is a schematic architecture diagram of a communication system according to an embodiment of the present application;

fig. 3 is a first schematic structural diagram of an electronic device according to an embodiment of the present disclosure;

fig. 4 is a schematic structural diagram of an electronic device according to an embodiment of the present application;

fig. 5 is a schematic diagram illustrating an architecture of an operating system in an electronic device according to an embodiment of the present disclosure;

fig. 6 is a first scene schematic diagram of a camera control method according to an embodiment of the present application;

fig. 7 is a scene schematic diagram ii of a camera control method according to an embodiment of the present application;

fig. 8 is a third scene schematic diagram of a camera control method according to an embodiment of the present application;

fig. 9 is a fourth scene schematic diagram of a camera control method according to an embodiment of the present application;

fig. 10 is a scene schematic diagram five of a camera control method provided in the embodiment of the present application;

fig. 11 is a scene schematic diagram six of a camera control method provided in the embodiment of the present application;

fig. 12 is a scene schematic diagram seven of a camera control method according to an embodiment of the present application.

Detailed Description

The terminology used in the following examples is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used in the specification of this application and the appended claims, the singular forms "a", "an", "the" and "the" are intended to include the plural forms as well, such as "one or more", unless the context clearly indicates otherwise. It should also be understood that in the following embodiments of the present application, "at least one", "one or more" means one, two or more. The term "and/or" is used to describe an association relationship that associates objects, meaning that three relationships may exist; for example, a and/or B, may represent: a alone, both A and B, and B alone, where A, B may be singular or plural. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship.

Reference throughout this specification to "one embodiment" or "some embodiments," or the like, means that a particular feature, structure, or characteristic described in connection with the embodiment is included in one or more embodiments of the present application. Thus, appearances of the phrases "in one embodiment," "in some embodiments," "in other embodiments," or the like, in various places throughout this specification are not necessarily all referring to the same embodiment, but rather "one or more but not all embodiments" unless specifically stated otherwise. The terms "comprising," "including," "having," and variations thereof mean "including, but not limited to," unless expressly specified otherwise.

As shown in fig. 2, a communication system 100 is provided, which communication system 100 may include a first electronic device (e.g., electronic device 101) and a second electronic device (e.g., electronic device 102).

Illustratively, the electronic device 101 may be connected (e.g., wired or wireless) with the electronic device 102 via one or more communication networks 104. The communication network 104 may be a Local Area Network (LAN) or a Wide Area Network (WAN), such as the internet. The communication network 104 may be implemented using any known network communication protocol, which may be any of a variety of wired or wireless communication protocols, such as Ethernet, Universal Serial Bus (USB), FIREWIRE (FIREWIRE), Global System for Mobile communications (GSM), General Packet Radio Service (GPRS), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), time division multiple Access (TD-SCDMA), long Term Evolution (LTE), bluetooth, Wi-Fi, NFC, voice over internet protocol (VoIP), a communication protocol supporting a network slice architecture, or any other suitable communication protocol. Illustratively, in some embodiments, the electronic device 101 may establish a Wi-Fi connection with the electronic device 102 via a Wi-Fi protocol.

In some embodiments, the communication system 100 may also include an application server 105. There may be one or more application servers 105. The application server 105 is configured to communicate with the electronic device 101 and Applications (APPs) installed on the electronic device 102 through one or more communication networks 104.

Taking a video call APP with a video call function as an example, the user a may use the video call APP in the electronic device 101 to perform a video call with the user B. For example, user a may invite user B to make a video call in a video call APP of electronic device 101, and in turn, electronic device 101 may send a video call request to application server 105 inviting user B. The video call request may carry parameters such as an identifier (e.g., a nickname and an account number of the user B) of the user B in the video call APP. Then, after receiving the video call request, the application server 105 may determine, according to the identifier of the user B in the video call APP in the video call request, that the receiving party of the call request is the user B, and query the electronic device associated with the user B as the electronic device 102. Further, the application server 105 may forward the video call request sent by the electronic device 101 to the electronic device 102 of the user B.

If the electronic device 102 detects that the user B accepts the video call request sent by the user a this time, the electronic device 102 may continue to send the captured voice and image to the electronic device 101 in real time through the application server 105. Meanwhile, the electronic device 101 may also send the collected voice and image to the electronic device 102 in real time through the application server 105, so that the user a may perform a video call with the user B.

Of course, the application server 105 may also perform operations such as identity authentication and security encryption on instructions or data sent by the electronic device 101 or the electronic device 102, which is not limited in this embodiment of the application.

In still other embodiments, the system 100 may further include an electronic device 103 (e.g., a wearable device). Illustratively, the electronic device 101 may be connected (e.g., wired or wireless) with the electronic device 103 via the communication network 104 described above.

For example, a video call APP with a video call function may be installed in the wearable device. Then, the wearable device may receive video call requests sent by the respective contacts in the video call APP. For another example, the user may also invite one or more contacts in the video call APP to perform a video call in the wearable device, which is not limited in this embodiment of the application.

In some embodiments, the specific structures of the electronic device 101, the electronic device 102, and the wearable device 103 may be the same or different.

Embodiments of an electronic device with video call functionality, a user interface for such an electronic device, and for using such an electronic device are described below. In some embodiments, the electronic device may be a portable electronic device, such as a cell phone, a tablet, a wearable electronic device with wireless communication capabilities (e.g., a smart watch), and the like, that also includes other functionality, such as personal digital assistant and/or music player functionality. Exemplary embodiments of the portable electronic device include, but are not limited to, a mount

Or other operating system. The portable electronic device may also be other portable electronic devices such as a Laptop computer (Laptop) or the like. It should also be understood that in other embodiments, the electronic device may not be a portable electronic device, but may be a desktop computer.

For example, fig. 3 shows a schematic structural diagram of the electronic device 101.

The electronic device 101 may include a processor 110, an external memory interface 120, an internal memory 121, a Universal Serial Bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, an earphone interface 170D, a sensor module 180, a key 190, a motor 191, an indicator 192, a camera 193, a display screen 194, a Subscriber Identification Module (SIM) card interface 195, and the like. The sensor module 180 may include a pressure sensor 180A, a gyroscope sensor 180B, an air pressure sensor 180C, a magnetic sensor 180D, an acceleration sensor 180E, a distance sensor 180F, a proximity light sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, an ambient light sensor 180L, a bone conduction sensor 180M, and the like.

It is to be understood that the illustrated structure of the embodiment of the present invention does not specifically limit the electronic device 101. In other embodiments of the present application, the electronic device 101 may include more or fewer components than illustrated, or combine certain components, or split certain components, or a different arrangement of components. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

Processor 110 may include one or more processing units, such as: the processor 110 may include an Application Processor (AP), a modem processor, a Graphics Processor (GPU), an Image Signal Processor (ISP), a controller, a video codec, a Digital Signal Processor (DSP), a baseband processor, and/or a neural-Network Processing Unit (NPU), etc. The different processing units may be separate devices or may be integrated into one or more processors.

The controller can generate an operation control signal according to the instruction operation code and the timing signal to complete the control of instruction fetching and instruction execution.

A memory may also be provided in processor 110 for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. The memory may hold instructions or data that have just been used or recycled by the processor 110. If the processor 110 needs to reuse the instruction or data, it can be called directly from the memory. Avoiding repeated accesses reduces the latency of the processor 110, thereby increasing the efficiency of the system.

In some embodiments, processor 110 may include one or more interfaces. The interface may include an integrated circuit (I2C) interface, an integrated circuit built-in audio (I2S) interface, a Pulse Code Modulation (PCM) interface, a universal asynchronous receiver/transmitter (UART) interface, a Mobile Industry Processor Interface (MIPI), a general-purpose input/output (GPIO) interface, a Subscriber Identity Module (SIM) interface, and/or a Universal Serial Bus (USB) interface, etc.

The I2C interface is a bi-directional synchronous serial bus that includes a serial data line (SDA) and a Serial Clock Line (SCL). In some embodiments, processor 110 may include multiple sets of I2C buses. The processor 110 may be coupled to the touch sensor 180K, the charger, the flash, the camera 193, etc. through different I2C bus interfaces, respectively. For example: the processor 110 may be coupled to the touch sensor 180K via an I2C interface, such that the processor 110 and the touch sensor 180K communicate via an I2C bus interface to implement the touch functionality of the electronic device 101.

The I2S interface may be used for audio communication. In some embodiments, processor 110 may include multiple sets of I2S buses. The processor 110 may be coupled to the audio module 170 via an I2S bus to enable communication between the processor 110 and the audio module 170. In some embodiments, the audio module 170 may communicate audio signals to the wireless communication module 160 via the I2S interface, enabling answering of calls via a bluetooth headset.

The PCM interface may also be used for audio communication, sampling, quantizing and encoding analog signals. In some embodiments, the audio module 170 and the wireless communication module 160 may be coupled by a PCM bus interface. In some embodiments, the audio module 170 may also transmit audio signals to the wireless communication module 160 through the PCM interface, so as to implement a function of answering a call through a bluetooth headset. Both the I2S interface and the PCM interface may be used for audio communication.

The UART interface is a universal serial data bus used for asynchronous communications. The bus may be a bidirectional communication bus. It converts the data to be transmitted between serial communication and parallel communication. In some embodiments, a UART interface is generally used to connect the processor 110 with the wireless communication module 160. For example: the processor 110 communicates with a bluetooth module in the wireless communication module 160 through a UART interface to implement a bluetooth function. In some embodiments, the audio module 170 may transmit the audio signal to the wireless communication module 160 through a UART interface, so as to realize the function of playing music through a bluetooth headset.

MIPI interfaces may be used to connect processor 110 with peripheral devices such as display screen 194, camera 193, and the like. The MIPI interface includes a Camera Serial Interface (CSI), a display screen serial interface (DSI), and the like. In some embodiments, the processor 110 and the camera 193 communicate through a CSI interface to implement the capture functionality of the electronic device 101. The processor 110 and the display screen 194 communicate through the DSI interface to implement the display function of the electronic device 101.

The GPIO interface may be configured by software. The GPIO interface may be configured as a control signal and may also be configured as a data signal. In some embodiments, a GPIO interface may be used to connect the processor 110 with the camera 193, the display 194, the wireless communication module 160, the audio module 170, the sensor module 180, and the like. The GPIO interface may also be configured as an I2C interface, an I2S interface, a UART interface, a MIPI interface, and the like.

It should be understood that the connection relationship between the modules according to the embodiment of the present invention is only illustrative, and does not limit the structure of the electronic device 101. In other embodiments of the present application, the electronic device 101 may also adopt different interface connection manners or a combination of multiple interface connection manners in the above embodiments.

The charging management module 140 is configured to receive charging input from a charger. The charger may be a wireless charger or a wired charger. In some wired charging embodiments, the charging management module 140 may receive charging input from a wired charger via the USB interface 130. In some wireless charging embodiments, the charging management module 140 may receive a wireless charging input through a wireless charging coil of the electronic device 101. The charging management module 140 may also supply power to the electronic device through the power management module 141 while charging the battery 142.

The power management module 141 is used to connect the battery 142, the charging management module 140 and the processor 110. The power management module 141 receives input from the battery 142 and/or the charge management module 140, and supplies power to the processor 110, the internal memory 121, the display 194, the camera 193, the wireless communication module 160, and the like. The power management module 141 may also be used to monitor parameters such as battery capacity, battery cycle count, battery state of health (leakage, impedance), etc. In some other embodiments, the power management module 141 may also be disposed in the processor 110. In other embodiments, the power management module 141 and the charging management module 140 may be disposed in the same device.

The wireless communication function of the electronic device 101 may be implemented by the antenna 1, the antenna 2, the mobile communication module 150, the wireless communication module 160, the modem processor, the baseband processor, and the like.

The antennas 1 and 2 are used for transmitting and receiving electromagnetic wave signals. Each antenna in the electronic device 101 may be used to cover a single or multiple communication bands. Different antennas can also be multiplexed to improve the utilization of the antennas. For example: the antenna 1 may be multiplexed as a diversity antenna of a wireless local area network. In other embodiments, the antenna may be used in conjunction with a tuning switch.

The mobile communication module 150 may provide a solution including 2G/3G/4G/5G wireless communication applied on the electronic device 101. The mobile communication module 150 may include one or more filters, switches, power amplifiers, Low Noise Amplifiers (LNAs), and the like. The mobile communication module 150 may receive the electromagnetic wave from the antenna 1, filter, amplify, etc. the received electromagnetic wave, and transmit the electromagnetic wave to the modem processor for demodulation. The mobile communication module 150 may also amplify the signal modulated by the modem processor, and convert the signal into electromagnetic wave through the antenna 1 to radiate the electromagnetic wave. In some embodiments, at least some of the functional modules of the mobile communication module 150 may be disposed in the processor 110. In some embodiments, at least some of the functional modules of the mobile communication module 150 may be disposed in the same device as at least some of the modules of the processor 110.

The modem processor may include a modulator and a demodulator. The modulator is used for modulating a low-frequency baseband signal to be transmitted into a medium-high frequency signal. The demodulator is used for demodulating the received electromagnetic wave signal into a low-frequency baseband signal. The demodulator then passes the demodulated low frequency baseband signal to a baseband processor for processing. The low frequency baseband signal is processed by the baseband processor and then transferred to the application processor. The application processor outputs a sound signal through an audio device (not limited to the speaker 170A, the receiver 170B, etc.) or displays an image or video through the display screen 194. In some embodiments, the modem processor may be a stand-alone device. In other embodiments, the modem processor may be provided in the same device as the mobile communication module 150 or other functional modules, independent of the processor 110.

The wireless communication module 160 may provide a solution for wireless communication applied to the electronic device 101, including Wireless Local Area Networks (WLANs) (e.g., wireless fidelity (Wi-Fi) networks), Bluetooth (BT), Global Navigation Satellite System (GNSS), Frequency Modulation (FM), Near Field Communication (NFC), Infrared (IR), and the like. The wireless communication module 160 may be one or more devices that integrate one or more communication processing modules. The wireless communication module 160 receives electromagnetic waves via the antenna 2, performs frequency modulation and filtering processing on electromagnetic wave signals, and transmits the processed signals to the processor 110. The wireless communication module 160 may also receive a signal to be transmitted from the processor 110, perform frequency modulation and amplification on the signal, and convert the signal into electromagnetic waves through the antenna 2 to radiate the electromagnetic waves.

In some embodiments, antenna 1 of electronic device 101 is coupled to mobile communication module 150 and antenna 2 is coupled to wireless communication module 160 so that electronic device 101 can communicate with networks and other devices through wireless communication techniques. The wireless communication technology may include global system for mobile communications (GSM), General Packet Radio Service (GPRS), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), time-division code division multiple access (time-division code division multiple access, TD-SCDMA), Long Term Evolution (LTE), LTE, BT, GNSS, WLAN, NFC, FM, and/or IR technologies, etc. The GNSS may include a Global Positioning System (GPS), a global navigation satellite system (GLONASS), a beidou satellite navigation system (BDS), a quasi-zenith satellite system (QZSS), and/or a Satellite Based Augmentation System (SBAS).

The electronic device 101 implements display functions via the GPU, the display screen 194, and the application processor, etc. The GPU is a microprocessor for image processing, and is connected to the display screen 194 and an application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. The processor 110 may include one or more GPUs that execute program instructions to generate or alter display information.

The display screen 194 is used to display images, video, and the like. The display screen 194 includes a display panel. The display panel may be a Liquid Crystal Display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (active-matrix organic light-emitting diode, AMOLED), a flexible light-emitting diode (FLED), a miniature, a Micro-oeld, a quantum dot light-emitting diode (QLED), or the like. In some embodiments, the electronic device 101 may include 1 or more display screens 194.

The electronic device 101 may implement a shooting function through the ISP, the camera 193, the video codec, the GPU, the display screen 194, the application processor, and the like.

The ISP is used to process the data fed back by the camera 193. For example, when a photo is taken, the shutter is opened, light is transmitted to the camera photosensitive element through the lens, the optical signal is converted into an electrical signal, and the camera photosensitive element transmits the electrical signal to the ISP for processing and converting into an image visible to naked eyes. The ISP can also carry out algorithm optimization on the noise, brightness and skin color of the image. The ISP can also optimize parameters such as exposure, color temperature and the like of a shooting scene. In some embodiments, the ISP may be provided in camera 193.

The camera 193 is used to capture still images or video. The object generates an optical image through the lens and projects the optical image to the photosensitive element. The photosensitive element may be a Charge Coupled Device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The light sensing element converts the optical signal into an electrical signal, which is then passed to the ISP where it is converted into a digital image signal. And the ISP outputs the digital image signal to the DSP for processing. The DSP converts the digital image signal into image signal in standard RGB, YUV and other formats. In some embodiments, the electronic device 101 may include 1 or more cameras 193.

For example, one or more cameras 193 in the electronic device 101 may be configured as a liftable camera. Taking a mobile phone as an example of the electronic device 101, as shown in fig. 4, the mobile phone may include components such as a display 194, a housing 30, and an image capturing device 50. The camera device 50 is provided with one or more cameras 193.

As shown in fig. 4, the housing 30 is provided with an opening 31, and the housing 30 forms an accommodating chamber (not shown in fig. 4) for accommodating the image pickup device 50. The housing chamber communicates with the opening 31. The camera device 50 can be movably accommodated in the accommodating cavity and can extend out of or retract into the housing 30 through the opening 31.

The image pickup device 50 includes a driving assembly (not shown in fig. 4) and a camera 193. The driving assembly is used to drive the camera 193 to extend or retract into the receiving cavity through the opening 31. Illustratively, the camera device 50 may be used to capture a scene or a portrait of the front side of the mobile phone, i.e. the camera 193 of the camera device 50 may be used as a front camera device. For another example, the camera 193 on the imaging device 50 may also be used as a rear-mounted imaging device, or the camera 193 on the imaging device 50 may also be provided as a rotary-type imaging device, which is not limited in this embodiment of the present application.

The digital signal processor is used for processing digital signals, and can process digital image signals and other digital signals. For example, when the electronic device 101 selects a frequency bin, the digital signal processor is used to perform fourier transform or the like on the frequency bin energy.

Video codecs are used to compress or decompress digital video. The electronic device 101 may support one or more video codecs. In this way, the electronic device 101 may play or record video in a variety of encoding formats, such as: moving Picture Experts Group (MPEG) 1, MPEG2, MPEG3, MPEG4, and the like.

The NPU is a neural-network (NN) computing processor that processes input information quickly by using a biological neural network structure, for example, by using a transfer mode between neurons of a human brain, and can also learn by itself continuously. The NPU can implement applications such as intelligent recognition of the electronic device 101, for example: image recognition, face recognition, speech recognition, text understanding, and the like.

The external memory interface 120 may be used to connect an external memory card, such as a Micro SD card, to extend the storage capability of the electronic device 101. The external memory card communicates with the processor 110 through the external memory interface 120 to implement a data storage function. For example, files such as music, video, etc. are saved in an external memory card.

Internal memory 121 may be used to store one or more computer programs, including instructions. The processor 110 may execute the above-mentioned instructions stored in the internal memory 121, so as to enable the electronic device 101 to execute the method for intelligently recommending contacts, as well as various functional applications and data processing, etc. provided in some embodiments of the present application. The internal memory 121 may include a program storage area and a data storage area. Wherein, the storage program area can store an operating system; the storage area may also store one or more application programs (e.g., gallery, contacts, etc.), etc. The storage data area may store data (such as photos, contacts, etc.) created during use of the electronic device 101, and the like. In addition, the internal memory 121 may include a high-speed random access memory, and may also include a nonvolatile memory, such as one or more magnetic disk storage devices, flash memory devices, Universal Flash Storage (UFS), and the like. In other embodiments, the processor 110 causes the electronic device 101 to execute the control method of the camera provided in the embodiments of the present application, and various functional applications and data processing by executing instructions stored in the internal memory 121 and/or instructions stored in a memory provided in the processor.

The electronic device 101 may implement audio functions via the audio module 170, the speaker 170A, the receiver 170B, the microphone 170C, the headphone interface 170D, and the application processor. Such as music playing, recording, etc.

The audio module 170 is used to convert digital audio information into an analog audio signal output and also to convert an analog audio input into a digital audio signal. The audio module 170 may also be used to encode and decode audio signals. In some embodiments, the audio module 170 may be disposed in the processor 110, or some functional modules of the audio module 170 may be disposed in the processor 110.

The speaker 170A, also called a "horn", is used to convert the audio electrical signal into an acoustic signal. The electronic apparatus 101 can listen to music through the speaker 170A or listen to a handsfree call.

The receiver 170B, also called "earpiece", is used to convert the electrical audio signal into an acoustic signal. When the electronic device 101 answers a call or voice information, the voice can be answered by placing the receiver 170B close to the ear of the person.

The microphone 170C, also referred to as a "microphone," is used to convert sound signals into electrical signals. When making a call or transmitting voice information, the user can input a voice signal to the microphone 170C by speaking the user's mouth near the microphone 170C. The electronic device 101 may be provided with one or more microphones 170C. In other embodiments, the electronic device 101 may be provided with two microphones 170C to achieve a noise reduction function in addition to collecting sound signals. In other embodiments, the electronic device 101 may further include three, four, or more microphones 170C to collect sound signals, reduce noise, identify sound sources, and implement directional recording functions.

The headphone interface 170D is used to connect a wired headphone. The headset interface 170D may be the USB interface 130, or may be a 3.5mm open mobile electronic device platform (OMTP) standard interface, a cellular telecommunications industry association (cellular telecommunications industry association of the USA, CTIA) standard interface.

The sensors 180 may include a pressure sensor 180A, a gyroscope sensor 180B, an air pressure sensor 180C, a magnetic sensor 180D, an acceleration sensor 180E, a distance sensor 180F, a proximity light sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, an ambient light sensor 180L, a bone conduction sensor 180M, and the like.

The keys 190 include a power-on key, a volume key, and the like. The keys 190 may be mechanical keys. Or may be touch keys. The electronic device 101 may receive a key input, and generate a key signal input related to user settings and function control of the electronic device 101.

The motor 191 may generate a vibration cue. The motor 191 may be used for incoming call vibration cues, as well as for touch vibration feedback. For example, touch operations applied to different applications (e.g., photographing, audio playing, etc.) may correspond to different vibration feedback effects. The motor 191 may also respond to different vibration feedback effects for touch operations applied to different areas of the display screen 194. Different application scenes (such as time reminding, receiving information, alarm clock, game and the like) can also correspond to different vibration feedback effects. The touch vibration feedback effect may also support customization.

Indicator 192 may be an indicator light that may be used to indicate a state of charge, a change in charge, or a message, missed call, notification, etc.

The SIM card interface 195 is used to connect a SIM card. The SIM card can be brought into and out of contact with the electronic device 101 by being inserted into the SIM card interface 195 or by being pulled out of the SIM card interface 195. The electronic device 101 may support 1 or more SIM card interfaces, N being a positive integer greater than 1. The SIM card interface 195 may support a Nano SIM card, a Micro SIM card, a SIM card, etc. The same SIM card interface 195 can be inserted with multiple cards at the same time. The types of the plurality of cards may be the same or different. The SIM card interface 195 may also be compatible with different types of SIM cards. The SIM card interface 195 may also be compatible with external memory cards. The electronic device 101 interacts with the network through the SIM card to implement functions such as communication and data communication. In some embodiments, the electronic device 101 employs esims, namely: an embedded SIM card. The eSIM card can be embedded in the electronic device 101 and cannot be separated from the electronic device 101.

The software system of the electronic device 101 may adopt a layered architecture, an event-driven architecture, a micro-core architecture, a micro-service architecture, or a cloud architecture. The embodiment of the application takes an Android system with a layered architecture as an example, and exemplarily illustrates a software structure of the electronic device 101.

Fig. 5 is a block diagram of the software architecture of electronic device 101 in some embodiments.

The layered architecture divides the software into several layers, each layer having a clear role and division of labor. The layers communicate with each other through a software interface. In some embodiments, the Android system is divided into four layers, an application layer, an application framework layer, an Android runtime (Android runtime) and system library, and a kernel layer from top to bottom.

The application layer may include one or more applications.

As shown in fig. 5, the application programs may include Applications (APP) such as call (also called phone or dial), contact (also called address book or phone book), camera, gallery, calendar, map, navigation, bluetooth, music, video, short message, and so on.

In some embodiments, an APP with video call functionality (which may be referred to as a video call APP) may be installed in the application layer. Such APP may be preset when the electronic device 101 leaves the factory, or may be a third-party application that is provided in an application market and is capable of performing a video call. For example, the video call APP may be the call APP, the short message APP, or the WeChat APP. When the user uses the video call APP to carry out video call with the contact person, the video call APP can send the voice collected by the microphone to the contact person in real time, and meanwhile, the image collected by the camera 193 can be sent to the contact person in real time.

The application framework layer provides an Application Programming Interface (API) and a programming framework for the application programs of the application layer. The application framework layer includes a number of predefined functions.

As shown in fig. 5, the application framework layer may include a camera service (camera service) and an audio manager (audio manager).

The camera service is a system service (system service) provided by the application framework layer to each APP in the application layer. The APP in the application layer may call various interfaces provided by the camera service to implement camera-related functions, such as turning on the camera 193, turning off the camera 193, taking pictures or recording videos, and the like.

In addition, the system service may further include a Power Manager Service (PMS), a Window Manager Service (WMS), a Bluetooth service (Bluetooth service), a Network Management Service (NMS), an input method management service (IMS), and the like. These system services can run in the background of the electronic device 101, and the APP in the application layer can call the relevant system services to implement the corresponding application functions during running.

The audio manager described above may be used to access and control the volume and audio modes of an electronic device, such as a cell phone. For example, the audio manager may adjust the volume of the electronic device 101. For another example, the audio manager may adjust the sound type (streamType) of the electronic device 101. The sound type may include an ALARM (STREAM _ ALARM), MUSIC (STREAM _ MUSIC), a telephone RING (STREAM _ RING), and the like.

As another example, the audio manager may also be used to manage and set audio modes of the electronic device 101. Illustratively, the audio modes may include the following: a ring MODE (MODE _ ringing), a phone MODE (MODE _ IN _ CALL), a NORMAL MODE (MODE _ NORMAL), and a talk MODE (MODE _ IN _ conversation).

Illustratively, when the electronic device 101 receives phone calls from other contacts, the audio manager may set the current audio mode to ring mode while the electronic device 101 is ringing. When the user talks to other contacts using the conversation APP, the audio manager may set the current audio mode to the phone mode. When the electronic device 101 is engaged in a video call (e.g., an IP video call), the audio manager may set the current audio mode to a call mode. When the electronic device 101 is not ringing, talking, or engaged in a video call, the audio manager may set the current audio mode to the normal mode.

In some embodiments, for example, with the video call function in the call APP, after the call APP receives a video call request sent by a certain contact, the call APP may call an OpenCamera interface provided by the camera service to request the camera service to turn on the camera 193 to acquire an image of the user. The camera service may periodically request the audio manager to query the current audio mode before sending an instruction to the camera driver to turn on the camera 193. When the current audio mode is detected to be a call mode, the user already accepts the video call request. In turn, the camera service may send an instruction to the camera driver to turn on the camera 193. In response to the instruction, the camera driver may control the camera 50 shown in fig. 4 to extend out of the housing 30 through the opening 31, expose the camera 193 on the camera 50, and begin capturing images of the user, such as the user's face, using the camera 193.

That is, after the electronic device 101 receives the video call request, the electronic device 101 does not raise the camera 193 in response to the request of the video call APP to turn on the camera 193 before detecting that the user accepts the video call request. Accordingly, upon receiving the video call request, the video call APP may request the electronic device 101 to raise the camera 193. At this time, the electronic device 101 may first determine whether the user accepts the video call request. If the user is detected to accept the video call request, the electronic device 101 may raise the camera 193. In this way, when the video call is not connected, the electronic device 101 does not pop up the camera 193 to interfere with the user experience, and meanwhile, if the user does not receive the video call request, the electronic device 101 can reduce the popping up of the camera 193 once, thereby prolonging the service life of the lift-type camera 193.

It is understood that raising the camera 193 by the electronic device 101 may mean that the electronic device 101 drives the camera 193 through the opening 31 to extend the camera 193 from inside the housing 30 to outside the housing 30 by a driving component in the camera 50. In addition, the electronic device 101 may also turn on the camera 193 to start capturing images when starting to raise the camera 193. In addition, the electronic device 101 may also turn on the camera 193 to start capturing images during the raising of the camera 193. Of course, the electronic device 101 may also turn on the camera 193 to start capturing images after the camera 193 is fully extended out of the housing 30, i.e., when there is no relative movement between the camera 193 and the housing 30. Among other things, the electronic device 101 turning on the camera 193 may refer to powering on the camera 193 to initiate an event in which the camera 193 generates an image signal through a lens, a photosensitive element, and the like.

Of course, if the camera 193 in the electronic device 101 is not the up-down camera 193, but is a common camera disposed on the housing of the electronic device 101, the electronic device 101 may also use the above method to start capturing the image content by turning on the camera after detecting that the user accepts the video call request, instead of turning on the camera to capture the image after receiving the video call request from the contact. Therefore, when the video call is not connected, the electronic equipment 101 does not turn on the camera to acquire the image content related to the user, and the security risk of privacy disclosure of the user can be reduced.

In addition, as also shown in FIG. 5, an activity manager (activitymanager) may also be included in the application framework layer. The campaign manager may be used to manage the lifecycle of each application. Applications typically run in the form of activity in the operating system. For each activity, there is an application record (activity record) in the activity manager corresponding to the activity, and the activity record holds the activity status of the application. The activity manager may schedule the activity process for the application using the activity record as the identification.

Taking the video call APP as an example, when the electronic device 101 runs the video call APP in the application layer, the video call APP may run as activity on the top layer of the application stack. At this point, the video call APP may interact with the user as a foreground application. When the video call APP receives a video call request sent by a contact, the video call APP can request the camera service to open the camera 193 to collect images. After receiving the request of the video call APP, the camera service may first invoke a specific interface (e.g., an activitymanager ex interface) provided by the activity manager, and query whether an application located at the top of the application stack (i.e., the application requesting to open the camera 193 this time) is the preset video call APP. For example, the call APP and the WeChat APP may be set as video call APPs in advance, and the camera APP is not a preset video call APP. Then, if it is queried that the application requesting to open the camera 193 this time is the camera APP, the camera service may send an instruction to open the camera 193 to the camera driver, thereby driving the electronic device 101 to raise the camera 193.

Correspondingly, if the application requesting to open the camera 193 at this time is a call APP or a WeChat APP, the camera service may further query the current audio mode from the audio manager. When it is detected that the current audio mode is a call mode, which indicates that the user has accepted the video call request, the camera service may send an instruction to turn on the camera 193 to the camera driver, so as to drive the electronic device 101 to raise and turn on the camera 193, thereby preventing the camera 193 from being raised to interfere with the normal use experience of the user when the user is not connected to the video call.

Of course, the application framework layer may also include a window manager, content provider, view system, resource manager, notification manager, and the like.

Wherein, the window manager is used for managing the window program. The window manager can obtain the size of the display screen, judge whether a status bar exists, lock the screen, intercept the screen and the like. The content provider is used to store and retrieve data and make it accessible to applications. The data may include video, images, audio, calls made and received, browsing history and bookmarks, phone books, etc. The view system includes visual controls such as controls to display text, controls to display pictures, and the like. The view system may be used to build applications. The display interface may be composed of one or more views. For example, the display interface including the short message notification icon may include a view for displaying text and a view for displaying pictures. The resource manager provides various resources for the application, such as localized strings, icons, pictures, layout files, video files, and the like. The notification manager enables the application to display notification information in the status bar, can be used to convey notification-type messages, can disappear automatically after a short dwell, and does not require user interaction. Such as a notification manager used to inform download completion, message alerts, etc. The notification manager may also be a notification that appears in the form of a chart or scroll bar text at the top status bar of the system, such as a notification of a background running application, or a notification that appears on the screen in the form of a dialog window. For example, prompting text information in the status bar, sounding a prompt tone, vibrating the electronic device, flashing an indicator light, etc.

The Android Runtime comprises a core library and a virtual machine. The Android runtime is responsible for scheduling and managing an Android system.

The core library comprises two parts: one part is a function which needs to be called by java language, and the other part is a core library of android.

The application layer and the application framework layer run in a virtual machine. And executing java files of the application program layer and the application program framework layer into a binary file by the virtual machine. The virtual machine is used for performing the functions of object life cycle management, stack management, thread management, safety and exception management, garbage collection and the like.

The system library may include a plurality of functional modules. For example: surface managers (surface managers), Media Libraries (Media Libraries), three-dimensional graphics processing Libraries (e.g., OpenGL ES), 2D graphics engines (e.g., SGL), and the like.

The surface manager is used to manage the display subsystem and provide fusion of 2D and 3D layers for multiple applications.

The media library supports a variety of commonly used audio, video format playback and recording, and still image files, among others. The media library may support a variety of audio-video encoding formats, such as MPEG4, h.264, MP3, AAC, AMR, JPG, PNG, and the like.

The three-dimensional graphic processing library is used for realizing three-dimensional graphic drawing, image rendering, synthesis, layer processing and the like.

The 2D graphics engine is a drawing engine for 2D drawing.

The kernel layer is a layer between hardware and software. The kernel layer at least comprises a display driver, a camera driver, an audio driver, a sensor driver and the like, and the embodiment of the application does not limit the display driver, the camera driver, the audio driver, the sensor driver and the like.

A mobile phone provided with a lifting camera will be taken as the above-mentioned electronic device 101 for example, and a control method of the camera provided in some embodiments of the present application will be described in detail with reference to the accompanying drawings.

For example, a user may install a video call APP with video call (also referred to as video phone) functionality in a mobile phone. The user may add one or more contacts (also called friends) when using the video call APP and record basic information of each contact, such as the name, phone, address, mailbox, and group to which the contact belongs.

Taking a contact APP as the video call APP for example, as shown in fig. 6, after detecting an operation of opening the contact APP by a user, the mobile phone may display a contact list interface 601, where the contact list interface 601 includes one or more contacts.

Each contact corresponds to a contact information table 602, and the contact information table 602 may be stored in the internal memory 121 or the external memory 120 of the mobile phone. The contact information table 602 records basic information of the contact, such as the name, one or more phone numbers, address, mailbox, group, social data, etc. of the contact in different fields.

Taking contact Mike as an example, after the user selects contact Mike in the contact list interface 601 shown in fig. 6, as shown in fig. 7, the mobile phone may display a detail interface 701 of contact Mike. One or more items of information that Mike holds in contact information table 602 may be included in details interface 701.

In addition, the mobile phone can also display various communication functions supported by the contact Mike through the contact APP in the detail interface 701. For example, as shown in fig. 7, a call control 702, a short message control 703 and a video control 704 are provided in the detail interface 701. If the user selects the call control 702, the mobile phone can automatically call the Mike telephone number to realize the call function. If the user selects the short message control 703, the mobile phone can automatically jump to a short message editing interface with the contact Mike to realize the short message function. If the video control 704 is detected to be selected by the user, the mobile phone can automatically send a video call request to the contact Mike, so as to realize the video call function.

In other embodiments, the contact Mike may also send a video call request to the user (e.g., Peter) using his/her own mobile phone. Illustratively, the contact Mike may invite Peter to a video call using the electronic device 102 described above. After detecting that the user invites Peter to perform a video call, the electronic device 102 may send a video call request to the application server 105 to invite Peter to perform a video call. In turn, application server 105 may send the video call request to Peter's electronic device (e.g., Peter's cell phone).

For example, before receiving a video call request from the contact Mike, the Peter's mobile phone has a lift camera in an un-lifted state. After receiving the video call request from the contact Mike forwarded by the application server 105, the mobile phone of the user Peter may present a first user interface. For example, as shown in fig. 8, after the mobile phone receives a video call request from the contact Mike, the mobile phone may display a first user interface 801 for performing a video call with the contact Mike. The first user interface 801 may include a first control 802 for accepting the video call request and a second control 803 for rejecting the video call request.

Of course, the first user interface presented by the mobile phone may include, in addition to the GUI visible to the user, a presentation manner such as vibration or ring tone corresponding to the video call request, which is not limited in this embodiment of the application.

Still taking the first user interface 801 shown in fig. 8 as an example, if the mobile phone detects that the user clicks the first control 802 in the first user interface 801, that is, the mobile phone detects that the user accepts the video call request, it indicates that the user is willing to accept the video call request. In response to the event (for example, the above-mentioned clicking operation), the mobile phone may transmit the captured video (voice and image) to the contact Mike in real time, and in addition, the mobile phone may receive and play the video sent by the contact Mike in real time. For example, the mobile phone may receive the voice and the image sent by the electronic device 102 of the contact Mike through the application server 105, and send the voice and the image collected by the mobile phone to the electronic device 102 of the contact Mike through the application server 105. If it is detected that the user clicks the second control 803 in the first user interface 801, which indicates that the user does not wish to accept the video call request, the mobile phone may send a message rejecting the video call to the electronic device 102 of the contact Mike through the application server 105 in response to the event, and cancel the video call with the contact Mike.

In addition, since a camera is required to capture an image during a video call, after the mobile phone receives a video call request from the contact Mike, the contact APP may send a camera call request to a camera service (camera service) in the application framework layer. For example, the contact APP may call an OpenCamera interface provided by the camera service, and send a camera call request to the camera service to request the camera service to raise the up-down camera 193 in the cell phone to start capturing images. Or, after the contact APP detects that the user clicks the first control 802, the contact APP may send a camera call request to the camera service, which is not limited in this embodiment of the present application.

The touch sensor 180K is typically integrated on the display 194 of the handset. Then, after the touch sensor 180K detects a touch operation of the user on the first user interface 801, the touch screen may generate a corresponding touch event and report the touch event to the contact APP running in the foreground. The contact APP may determine what operation is specifically performed by the user according to parameters such as coordinates of a touch point in the touch event, and the camera service in the application framework layer may not know the specific operation of the user in the first user interface 801 in some cases.

That is to say, in some embodiments, when the camera service receives a camera call request sent by the contact APP, it cannot be determined whether the user has accepted the video call request. Then, after receiving the camera call request sent by the contact APP, the camera service may determine whether the user accepts the video call request. When the camera service detects that the user accepts the video call request, the camera service can respond to a camera call request sent by the contact APP and lift the lifting camera 193 of the mobile phone. Correspondingly, if the camera service does not detect that the user accepts the video call request, the camera service does not need to raise the lifting camera 193, and the situation that the user experiences interference caused by raising the camera 193 when the video call is not connected is avoided.

In other embodiments, before determining whether the user accepts the video call request, the camera service may determine whether the APP of the current camera call request is a preset video call APP.

In some embodiments, the mobile phone may store an application white list in advance, and applications in the application white list all have application rights to use the camera. For example, the applications in the application white list may include applications that support video call functions (i.e., preset video call APPs), such as WeChat, call, and contact.

For example, a user may authorize various types of application rights to an APP when installing or using the APP in a mobile phone. If the mobile phone detects that the user authorizes the application permission of using the camera to a certain APP, the mobile phone can automatically add the APP to the application white list. For another example, if it is detected that the user authorizes an APP to use the camera, the mobile phone may obtain, from the application market, whether the type to which the APP belongs is a video call APP. If the APP belongs to the video call APP, the mobile phone can automatically add the APP to the application white list.

Then, after the camera service in the mobile phone receives a camera call request sent by a certain APP, in order to avoid that the mobile phone authorizes the APP to use the camera in a state where the video call is not connected, the camera service may first call an activity manager (activitymanager) to query an application name currently running in a foreground, that is, send the name of the APP of the camera call request this time. Still taking the contact APP as an example, after the camera service queries that the APP sending the camera call request is the contact APP, it may query whether the contact APP is located in the application white list. If the contact APP is located in the application white list, it is indicated that the contact APP (i.e., the APP which comes from the camera call request at this time) is the preset video call APP. If the contact APP is not in the application white list, the contact APP is not a preset video call APP.

Of course, in other embodiments, an application blacklist may also be preset for the mobile phone, and all applications in the application blacklist are applications that prohibit the use of the camera, which is an application right. After the camera service queries that the APP sending the camera call request is the contact APP, whether the contact APP is located in the application blacklist can be continuously queried. If the contact APP is located in the application blacklist, it is indicated that the contact APP which sends the camera call request is not the preset video call APP. If the contact APP is not in the application white list, the contact APP sending the camera call request is a preset video call APP.

In some embodiments, if it is found that the contact APP requesting to call the camera this time is not the preset video call APP, and the user has authorized the application permission of the contact APP to use the camera, the camera service in the mobile phone may respond to the camera call request sent by the contact APP, instruct the camera driver to extend the camera 193 housed in the mobile phone housing, and open the camera 193 to start collecting images.

In other embodiments, if it is found that the contact APP requesting to call the camera at this time is the preset video call APP, then if the camera service responds to the camera call request sent by the contact APP at this time to raise the up-down camera 193, a situation that the user does not yet put through the video call request and the mobile phone pops up the camera 193 to collect the user image may occur. In this embodiment of the present application, before responding to the camera call request sent by the contact APP this time, the camera service may first detect whether the user accepts an event of the video call request this time. When the camera service detects that the user accepts the event of the video call request, the camera service can respond to a camera call request sent by the contact APP and lift the lifting camera 193 of the mobile phone.

In some embodiments, the event that the camera service detects that the user accepts the video call request is: the camera service detects an event that an audio MODE IN an audio manager (audio manager) is a call MODE (MODE _ IN _ COMMUNICATION).

Illustratively, still taking the video call request from the contact Mike shown in fig. 8 as an example, if the user performs a click operation on the first control 802 in the first user interface 801, the touch sensor 180K of the mobile phone may report the detected touch event to the contact APP. The contact APP can determine that the user receives the video call request of the contact Mike according to the information such as the coordinates of the touch point in the touch event. Since voice interaction is required when a video call is performed, the contact APP may call the audio manager to set the current audio MODE to the call MODE (MODE _ IN _ COMMUNICATION). Accordingly, if it is not detected that the user accepts the operation of the video call request, the audio manager may continue to set the current audio MODE to the NORMAL MODE (MODE _ NORMAL).

Of course, if the phone receives a phone call event from another contact (e.g., contact Sam) while the first user interface 801 is displayed, it indicates that contact Sam is calling the phone number of the user at the same time that contact Mike makes a video call request to the user. If the priority of the phone event is preset by the mobile phone to be higher than that of the video call event, after the mobile phone receives the phone call event of the contact Sam, the current audio MODE can be set to the ring MODE (MODE _ ringing) by using the audio manager. Subsequently, if it is detected that the user accepts the current phone CALL event of the contact Sam, the handset may CALL the audio manager to set the current audio MODE to the phone MODE (MODE _ IN _ CALL).

In the embodiment of the present application, as shown in fig. 9, after the mobile phone receives the video call request from the contact Mike, the camera service in the mobile phone may call the audio manager to query the current audio mode. For example, the camera service may poll the audio manager at a 50ms (millisecond) period. That is, the camera service may call the getMode () function provided by the audio manager every 50ms, requesting to query the current audio mode.

As also shown in fig. 9, if the current audio mode is not the above call mode, for example, when the audio mode is the above ring tone mode, ring tone mode or normal mode, it indicates that the user has not accepted the video call request from the contact Mike. Correspondingly, if the current audio mode is the call mode, that is, an event that the user accepts the video call request is detected, it is indicated that the user has accepted the video call request sent by the contact Mike.

In other embodiments, a camera service in the handset may register a listening service with the audio manager. When the audio manager monitors that the current audio mode is switched from the non-call mode to the call mode, which indicates that the user has accepted the video call request, the audio manager can actively send an indication message to the camera service, so that the camera service can detect an event that the user accepts the video call request according to the indication message.

In other embodiments, the event that the camera service detects that the user accepts the video call request is: the camera service detects an event in the communication signaling sent by the modem (modem) to the application server 105 where field a is the first value.

For example, still taking the video call request from the contact Mike shown in fig. 8 as an example, after receiving the video call request, the mobile phone may send the call status of the current video call to the application server 105 through the modem in real time. For example, the mobile phone may send a communication signaling to the server every 30ms, where the communication signaling carries a field a indicating the current call state.

For example, if the mobile phone detects that the user clicks the first control 802 in the first user interface 801, the mobile phone may set the field a in the communication signaling to the first value, and send the communication signaling to the application server 105. After receiving the communication signaling sent by the mobile phone this time, the application server 105 may determine that the user accepts the video call request of the contact Mike this time by analyzing the first value in the field a. Correspondingly, if it is not detected that the user clicks the first control 802 in the first user interface 801, the mobile phone may set the field a in the communication signaling to the second value, and send the communication signaling to the application server 105. After receiving the communication signaling carrying the second value, the application server 105 may determine that the current user has not accepted the video call request.

In some embodiments of the present application, as shown in fig. 10, after the mobile phone receives the video call request from the contact Mike, the mobile phone may periodically obtain the communication signaling sent by the modem to the application server 105, and analyze a specific value of the field a in the communication signaling. If the analyzed field A is the second value, the user does not receive the video call request sent by the contact Mike. Correspondingly, if the analyzed field a is the first value, it is also detected that the user accepts the event of the video call request, which indicates that the user has accepted the video call request sent by the contact Mike.

It can be understood that, a person skilled in the art may also set other ways to detect an event that the user receives the video call request, and the embodiment of the present application does not limit this. For example, after receiving a video call request from a contact, the mobile phone may monitor the operating state of a microphone in the mobile phone. When detecting that the microphone starts to work or the microphone collects the voice of the user, namely detecting that the user accepts the event of the video call request, the mobile phone can determine that the video call request is accepted by the user, otherwise, the mobile phone can determine that the user does not accept the video call request.

Still taking the example of the video call request sent by the contact Mike, if the camera service in the mobile phone determines that the user has not accepted the video call request through the above method, the camera service does not need to respond to the camera call request sent by the contact APP for the moment. At this time, the camera service does not raise the elevation type camera 193 in the handset case by the camera driving. And the camera service can continuously inquire whether the user receives the video call request in the audio manager or the modem.

That is to say, before the user accepts this video call request, the cell-phone can not lift over-and-under type camera 193 in the casing to improve the user and experience in the use of video call scene, and, before the user did not put through this video call request, the cell-phone can not lift this camera 193 and gather the image yet, thereby reduces the risk that user's privacy is revealed.

In addition, when the mobile phone determines that the user has not accepted the video call request, the mobile phone may continue to display the first user interface 801 shown in fig. 8. The user may select to accept or reject the video call request sent by the contact Mike this time in the first user interface 801. If it is detected that the user rejects the video call request sent by the contact Mike this time, or the video call request is detected to be overtime, or the contact Mike cancels the video call request, the contact APP may send a message to the camera service to cancel the camera call this time. Furthermore, the camera service can stop determining whether the user receives the video call request or not, and the telescopic state of the lifting camera in the mobile phone shell does not need to be adjusted.

In other embodiments, the first user interface 801 may also be updated when the camera service determines that the user has not accepted the video call request. For example, the cell phone may update the time, signal strength, power, etc. displayed in the status bar in the first user interface 801. For another example, before the user accepts the video call request, if the mobile phone receives a phone call event of another contact (e.g., Sam), the mobile phone may update the first user interface 801 to an incoming call interface of the contact Sam.

Still taking the example of the video call request sent by the contact Mike, if the camera service in the mobile phone determines that the user has accepted the video call request through the method, the camera service may respond to the camera call request sent by the contact APP and send a pop-up instruction to the camera driver. In response to the pop-up command, the camera driver may drive a driving assembly in the handset housing to raise the camera 193 and begin capturing images using the camera 193.

Therefore, the camera control method provided by the embodiment of the application can control the lifting camera in the mobile phone to lift up after the user receives the video call request. Before the user is detected to answer the video call request, the mobile phone does not respond to the video call APP to open the camera to lift the camera, and therefore the use experience of the user in the video call scene is improved.

Illustratively, the entire process of the handset raising the camera 193 takes time. For example, the entire process of raising the camera 193 takes about 1 second or so. Then, as shown in fig. 11 (a), the cellular phone may display a waiting interface 1101 during the process of lifting up the camera 193 from the housing. A prompt 1102 may be included in the wait interface 1101 to prompt the user that the camera is being turned on for the current video call.

Still alternatively, the mobile phone may store the user image captured by the camera in the last shooting process (or video call process), for example, the last frame of picture of the mobile phone before the camera is turned off. Then, as shown in (b) of fig. 11, when the mobile phone displays the waiting interface 1101, the user image 1103 captured before the mobile phone last closed the camera may also be displayed in the waiting interface 1101. Alternatively, the mobile phone may perform blurring processing such as blurring on the user image 1103 when the user image 1103 is displayed on the standby interface 1101. In this way, the user can provide a more realistic visual presentation to the user while waiting for the camera 193 to rise. Meanwhile, the user image 1103 in the waiting interface 1101 may be more softly transited to the user image acquired after the camera 193 is lifted up, so that the user experience of the user is improved.

Of course, when the camera 193 is lifted up, the mobile phone may also display other text, pictures, videos or animation contents in the waiting interface 1101, which is not limited in this embodiment of the present application.

Still taking the example of the video call request from the contact Mike, when the mobile phone completely lifts the camera 193 from the mobile phone casing, the mobile phone may open the camera to start capturing images. Alternatively, the mobile phone may also turn on the camera to start capturing images during the process of raising the camera 193. As shown in fig. 12, after the camera 193 is completely lifted from the handset housing, the handset can jump from the wait interface 1101 to the second user interface 1201. The mobile phone can display the image content 1202 acquired by the camera 193 in real time in the second user interface 1201. Also, the mobile phone may display image content 1203 sent by the contact Mike in real time in the second user interface 1201. Meanwhile, after the user receives the video call request, the mobile phone can also send the voice content collected by the microphone to the contact Mike in real time, and the mobile phone can receive and play the voice content sent by the contact Mike in real time, so that the video call process is realized.

In addition, in the above embodiments, the camera control method provided by the present application is described by taking a lifting camera as an example, and it can be understood that the method described in the above embodiments is also applicable to a mobile phone with a non-lifting camera.

For example, the camera may be fixed to the front panel of the mobile phone. Then, after receiving the video call request sent by the contact Mike, the mobile phone may also present the first user interface 801, and determine whether the user accepts the video call request at this time. If the fact that the user does not accept the video call request is determined, the mobile phone can continue to display the first user interface 801, and a camera on the front panel cannot be opened to collect images; when the mobile phone determines that the user accepts the video call request, the mobile phone can open a camera on the front panel to start to collect images. Therefore, when the video call is not connected, the mobile phone cannot open the camera to acquire the image content related to the user, and therefore the safety risk of privacy disclosure of the user can be reduced.

Through the above description of the embodiments, it is clear to those skilled in the art that, for convenience and simplicity of description, the foregoing division of the functional modules is merely used as an example, and in practical applications, the above function distribution may be completed by different functional modules according to needs, that is, the internal structure of the device may be divided into different functional modules to complete all or part of the above described functions. For the specific working processes of the system, the apparatus and the unit described above, reference may be made to the corresponding processes in the foregoing method embodiments, and details are not described here again.

Each functional unit in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.

As used in the above embodiments, the terms "when …" or "after …" may be interpreted to mean "if …" or "after …" or "in response to determination …" or "in response to detection …", depending on the context. Similarly, depending on the context, the phrase "at the time of determination …" or "if (a stated condition or event) is detected" may be interpreted to mean "if the determination …" or "in response to the determination …" or "upon detection (a stated condition or event)" or "in response to detection (a stated condition or event)". In addition, in the above-described embodiments, relational terms such as first and second are used to distinguish one entity from another entity without limiting any actual relationship or order between the entities.

The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solutions of the embodiments of the present application may be essentially implemented or make a contribution to the prior art, or all or part of the technical solutions may be implemented in the form of a software product stored in a storage medium and including several instructions for causing a computer device (which may be a personal computer, a server, or a network device) or a processor to execute all or part of the steps of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: flash memory, removable hard drive, read only memory, random access memory, magnetic or optical disk, and the like.

It is noted that a portion of this patent application contains material which is subject to copyright protection. The copyright owner reserves the copyright rights whatsoever, except for making copies of the patent files or recorded patent document contents of the patent office.

Claims

1. A method for controlling a camera, the method being implemented in an electronic device having a camera that is receivable in or protrudable out of a housing of the electronic device, the method comprising:

the electronic equipment receives a video call request from a first contact;

in response to the video call request, the electronic device presents a first user interface, wherein the camera is housed within the housing while the first user interface is presented;

the electronic equipment detects an event that the user accepts the video call request;

in response to the event, the electronic device extends the camera from within the housing to outside the housing.

2. The method of claim 1, wherein the first user interface comprises a first control and a second control, the first control is configured to accept the video call request, and the second control is configured to reject the video call request;

wherein, the event that the user accepts the video call request is: and the user selects the operation of the first control.

3. The method of claim 1, after the electronic device receives the video call request from the first contact, further comprising:

the electronic equipment calls an audio manager to inquire a current audio mode;

wherein, the event that the user accepts the video call request is: and inquiring the event that the audio mode is a call mode.

4. The method of claim 3, wherein the electronic device invokes an audio manager to query for a current audio mode, comprising:

the electronic equipment calls a getMode () function provided by an audio manager, and the return value of the getMode () function is the current audio mode;

the current audio mode is one of the following four audio modes: a CALL MODE _ IN _ COMMUNICATION, a ring MODE _ ringing, a phone MODE _ IN _ CALL, or a NORMAL MODE _ NORMAL.

5. The method of claim 1, after the electronic device receives the video call request from the first contact, further comprising:

the electronic equipment acquires a communication signaling sent to a server;

wherein, the event that the user accepts the video call request is: and inquiring an event of which the first field is the first value in the communication signaling.

6. The method of any of claims 1-5, wherein the video call request is sent by the first contact in a first application;

before the electronic equipment detects that the user accepts the video call request, the method comprises the following steps:

the electronic equipment determines that the first application is a preset video call application.

7. The method of any of claims 1-5, wherein after the electronic device protrudes the camera from within the housing to outside the housing, the method further comprises:

and the electronic equipment presents a second user interface, wherein the second user interface comprises the image acquired by the camera.

8. The method of any of claims 1-5, further comprising, during the extending of the camera head from within the housing to outside the housing:

the electronic equipment presents a third user interface, the third user interface comprises prompt information, and the prompt information is used for prompting a user that the camera is opened.

9. The method of claim 8, wherein the third user interface further comprises a first user image, wherein the first user image is a user image captured during a last capture.

10. An electronic device, comprising:

the camera can be accommodated in the shell of the electronic equipment or extends out of the shell;

the touch screen comprises a display screen and a touch sensor;

one or more processors;

a memory;

wherein the memory has stored therein one or more computer programs, the one or more computer programs comprising instructions, which when executed by the electronic device, cause the electronic device to perform the steps of:

receiving a video call request from a first contact;

presenting a first user interface in response to the video call request, wherein the camera is housed within the housing while the first user interface is presented;

detecting an event that a user accepts the video call request;

in response to the event, extending the camera from within the housing to outside the housing.

11. The electronic device of claim 10, wherein the first user interface comprises a first control and a second control, the first control is configured to accept the video call request, and the second control is configured to reject the video call request;

12. The electronic device of claim 10, wherein after the electronic device receives a video call request from a first contact, the electronic device is further configured to perform:

calling an audio manager to inquire a current audio mode;

13. The electronic device of claim 12, wherein the electronic device invokes an audio manager to query a current audio mode, comprising:

calling a getMode () function provided by an audio manager, wherein the return value of the getMode () function is the current audio mode;

wherein, the current audio mode is one of the following four audio modes: a CALL MODE _ IN _ COMMUNICATION, a ring MODE _ ringing, a phone MODE _ IN _ CALL, and a NORMAL MODE _ NORMAL.

14. The electronic device of claim 10, wherein after the electronic device receives a video call request from a first contact, the electronic device is further configured to perform:

acquiring a communication signaling sent to a server;

15. The electronic device of any of claims 10-14, wherein the video call request is sent by the first contact in a first application;

wherein, before the electronic device detects an event that the user accepts the video call request, the electronic device is further configured to perform:

determining that the first application is a preset video call application.

16. The electronic device of any of claims 10-14, wherein after the electronic device extends the camera from within the housing to outside the housing, the electronic device is further configured to perform:

and presenting a second user interface, wherein the second user interface comprises the image acquired by the camera.

17. The electronic device of any of claims 10-14, wherein during the process of the camera extending out of the housing, the electronic device is further configured to perform:

and presenting a third user interface, wherein the third user interface comprises prompt information used for prompting a user that the camera is opened.

18. The electronic device of claim 17, further comprising a first user image in the third user interface, wherein the first user image is a user image captured during a last capture.

19. A computer-readable storage medium having instructions stored therein, which when run on an electronic device, cause the electronic device to perform the method of controlling a camera according to any one of claims 1-9.

20. A computer program product comprising instructions for causing an electronic device to perform the method of controlling a camera according to any one of claims 1-9 when the computer program product is run on the electronic device.