CN117376469A - Information processing method and electronic equipment - Google Patents

Abstract

The embodiment of the application discloses an information processing method and electronic equipment, which relate to the technical field of electronic equipment and can realize callback processing of missed calls through the electronic equipment. The specific scheme is as follows: the first number is stored in the first history when the first call is not connected. A first missed call indication is received, the first missed call indication indicating that the first call is not connected. And under the condition that the first missed call indication is transmitted through the preset service, after the first missed call indication is received, the first history record is not updated. The first missed call indication does not include the first number. And receiving the operation of the user on the first control. The first control is a control indicating that the first incoming call is not connected. And responding to the first operation, and sending a first callback instruction to the second equipment, wherein the first callback instruction comprises a first number acquired from the first history record, and the first callback instruction is used for instructing the second equipment to make telephone callback according to the first number.

Description

Information processing method and electronic equipment

Technical Field

The embodiment of the application relates to the technical field of electronic equipment, in particular to an information processing method and electronic equipment.

Background

Currently, a mobile phone can establish a communication connection with a smart watch (hereinafter referred to as a watch) to perform data transmission.

For example, the communication connection may be a Bluetooth connection based on the Bluetooth (r) protocol. The Bluetooth connection service type in the mobile phone is apple notification center service (Apple Notification Center Service, ANCS).

Illustratively, based on the bluetooth connection, the watch may handle phone-based conversations. The call may include an incoming call and an outgoing call. For example, the watch may answer or reject a phone-based call at the direction of the user.

In some implementations, the watch may also callback incoming calls received by the handset. The incoming call which is not connected is the incoming call which is received and refused. The callback processing corresponds to calling out the telephone number of the missed call based on the mobile phone. In this implementation, the contact information (such as the contact name) and the phone number of the missed call are pre-stored in the mobile phone. In this case, the wristwatch cannot dial back the missed call based on the mobile phone.

Disclosure of Invention

The embodiment of the application provides an information processing method and electronic equipment, wherein the electronic equipment is first equipment. So that the first device always stores the telephone number of the missed call. And when the first device instructs other electronic devices (such as the second device) to dial back the missed call, the phone number of the missed call can be obtained.

In order to achieve the above purpose, the embodiments of the present application adopt the following technical solutions:

in a first aspect, an information processing method is provided, which is applied to a first device, and a communication connection is established between the first device and a second device. The first device is provided with a display screen. The method comprises the following steps: a first call request message is received, the first call request message being for indicating a first incoming call, the first call request message including a first number of the first incoming call. The first number is stored in a first history when the first call is not connected. A first missed call indication is received, the first missed call indication indicating that the first call is not connected. And under the condition that the first missed call indication is transmitted through a preset service, after the first missed call indication is received, the first history record is not updated. The first missed call indication does not include the first number. A first operation of a user is received, the first operation being an operation on a first control. The first control is a control displayed on the display screen and used for indicating that the first incoming call is not connected. And responding to the first operation, and sending a first callback instruction to the second equipment, wherein the first callback instruction comprises the first number acquired from the first history record, and the first callback instruction is used for instructing the second equipment to callback a telephone according to the first number.

Based on the above scheme, when the second device receives the first incoming call, the second device may send a first call request to the first device to indicate the first incoming call. The first device may store the phone number of the first incoming call in the first history when the first incoming call is missed. When the service type of the Bluetooth connection used in the second device is a preset service type, the first device does not update the first history record after receiving the first missed call indication. That is, after the first missed call indication is received, the first number is still stored in the first history record. In this way, the subsequent first device may obtain the first number from the first history and send the first number to the second device. The second device can dial back the first incoming call according to the first number.

Optionally, the second device stores a first number of the first incoming call and first contact information corresponding to the first incoming call. In the application, the second device stores the phone number of the first incoming call and the first contact information corresponding to the first incoming call. The first contact information may be a name of the first contact, etc. In this case, the first missed call indication received by the first device through the preset service does not include the phone number of the first call, i.e., the first number.

Optionally, the storing the first number in the first history record includes: a second missed call indication is received, the second missed call indication indicating that the first call was missed. The first number is stored in the first history in response to the second missed call indication. Based on the above scheme, the first device may store the first number in the first history when receiving the second missed call indication. So that a subsequent first device can obtain a first number of a first incoming call from the first history.

Optionally, after receiving the first call request message, the method further includes: and storing the first number of the first incoming call indicated by the first call request message in an incoming call variable, wherein the incoming call variable is used for storing the number of the current incoming call. Storing the first number in the first history in response to the second missed call indication, including: the first number is stored from the incoming call variable into the first history variable, the first history variable being one of one or more variables included in the first history record, each variable in the first history record being for storing a telephone number of an incoming call.

Based on the above scheme, when the first device receives the first call request message, the first device may save the first number included in the first call request message in the incoming call variable. The first device stores a first number in the future call variable in the first history variable, enabling the first number to be stored in the first history.

Optionally, before the storing the first number from the incoming call variable into the first history variable, the method further comprises: the first number is stored from the incoming variable to a first missed variable. The first missed variable is for storing a telephone number of a missed call. The storing the first number from the incoming call variable to the first history variable includes: the first number is stored from the first missed variable to the first historical variable. In the above arrangement, the first device stores the first number from the incoming variable into the first missed variable. The first number stored in the first history variable may be obtained from a first missed variable.

Optionally, after the receiving the first missed call indication, before the updating of the first history record is not performed, the method further includes: and determining that the service type used by the second equipment is the preset service when the first missed call indication is received.

Optionally, the preset service is ANCS.

In the present application, when the first missed call indication is transmitted through the ANCS, the first number is not included in the first missed call indication.

Optionally, before the sending, in response to the first operation, a first callback indication to the second device, the method further includes: and responding to the first operation, and acquiring the first number from the first historical variable.

Optionally, the storing the first number in the first history record includes: the first number and a first identification of the first incoming call are stored in the first history. Before the obtaining the first number from the first history variable, the method further includes: and determining callback information according to the first operation. The callback information includes the first identification. The obtaining the first number from the first history variable includes: and acquiring the first number from the first historical variable according to the first identifier indicated by the callback information.

In the above scheme, the first incoming call is correspondingly configured with a first identifier, and the first identifier and the first number are stored in the first historical variable. The first device may determine, according to the first operation, a first identification of a first incoming call indicated by the user. The first device may index from the first history variable to a first number corresponding to the first identification according to the first identification. Thereby obtaining the first number from the first history variable.

Optionally, the first missed variable is missedPhoneNumberInfo. The first history variable is callhistoryinfo.

Optionally, after receiving the first call request message, the method further includes: the first call request message also comprises first contact information corresponding to the first incoming call. And rendering a first interface according to the first number and the first contact information in the first call request message. The first interface is the processing interface that receives the first call. The first interface includes call information corresponding to the first call.

Optionally, after the receiving the first missed call indication, the method further includes: the first missed call indication includes the first contact information. And rendering a second interface according to the first contact information in the first missed call indication. The second interface includes a first notification. The first notification is used for indicating that the first incoming call is not connected.

Optionally, after the sending the first callback indication to the second device, the method further includes: and displaying a third interface. The third interface is a processing interface for dialing the first number.

In a second aspect, a communication system is provided that includes a first device and a second device that establish a communication connection. The second device is configured to send a first call request message to the first device when the first call is received, where the first call request message is used to indicate a first call, and the first call request message includes a first number of the first call. The first device is configured to store the first number in a first history when the first call is not connected. The second device is further configured to send a first missed call indication to the first device through a preset service, where the first missed call indication is used to indicate that the first call is not connected. The first missed call indication does not include the first number. The first device is further configured to not update the first history record if the first missed call indication is received. The first device is also configured to receive a first operation of a user, the first operation being an operation of a first control. The first control is a control displayed on a display screen and indicating that the first incoming call is not connected. The first device is further configured to send, in response to the first operation, a first callback indication to the second device, the first callback indication including the first number obtained from the first history. The second device is further configured to dial back a call using the first number according to the first callback indication.

Optionally, the first device storing the first number in a first history record includes: the first device receives a second missed call indication indicating that the first call was not completed. The first device stores the first number in the first history in response to the second missed call indication.

Optionally, after the first device receives the first call request message, the method further includes: the first device stores the first number of the first incoming call indicated by the first call request message in an incoming call variable, where the incoming call variable is used to store the number of the current incoming call. The first device storing the first number in the first history in response to the second missed call indication, comprising: the first device stores the first number from the incoming call variable into the first history variable, the first history variable being one of one or more variables included in the first history record, each variable in the first history record being for storing a telephone number of an incoming call.

In a third aspect, a chip system is provided, the chip system being applied to a first device. The system-on-chip includes one or more interface circuits and one or more processors. The interface circuit and the processor are interconnected by a wire. The interface circuit is to receive a signal from a memory of the first device and to send the signal to the processor, the signal including computer instructions stored in the memory. When the processor executes the computer instructions, the first device performs the information processing method provided in the first aspect and any one of its possible implementations.

In a fourth aspect, a computer-readable storage medium is provided, the computer-readable storage medium being applied to a first device. Comprising computer instructions which, when run on the first device, cause the first device to perform the information processing method provided in the first aspect and any one of its possible implementations.

In a fifth aspect, there is provided a computer program product for, when run on a computer, causing the computer to perform the information processing method performed by the first electronic device in the first aspect and any one of its possible implementations.

It will be appreciated that the solutions provided in the second aspect to the fifth aspect provided in the present application may correspond to the first aspect and any possible design thereof, so that the beneficial effects that can be achieved are similar, and are not repeated here.

Drawings

FIG. 1 is a schematic diagram of a handset interacting with a wristwatch;

FIG. 2 is a schematic diagram of another handset and watch interaction;

FIG. 3 is a schematic illustration of an interface;

FIG. 4 is another interface schematic;

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

fig. 6 is an interaction schematic diagram of an information processing method according to an embodiment of the present application;

FIG. 7 is a schematic diagram of an interface according to an embodiment of the present disclosure;

FIG. 8 is an interaction diagram of another information processing method according to an embodiment of the present application;

FIG. 9 is a schematic illustration of yet another interface provided by an embodiment of the present application;

fig. 10 is a schematic diagram of another electronic device according to an embodiment of the present disclosure;

fig. 11 is a schematic diagram of a system on chip according to an embodiment of the present application.

Detailed Description

The terms "first" and "second" are used below for descriptive purposes only and are not to be construed as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defining "a first" or "a second" may explicitly or implicitly include one or more such feature. In the description of the present embodiment, unless otherwise specified, the meaning of "plurality" is two or more.

Currently, a user may use multiple electronic devices simultaneously in order to obtain different intelligent service experiences through different electronic devices.

By way of example, the plurality of electronic devices may include a cell phone, a smart watch, and the like.

Reference is made to fig. 1. In some embodiments, the mobile phone may establish a communication connection with a smart watch (hereinafter simply referred to as a watch) for data transmission. For example, the communication connection may be a Bluetooth connection based on the Bluetooth (r) protocol.

Based on the bluetooth connection, the watch can process call requests based on the handset. The call request may include an incoming call request and an outgoing call request. The incoming call request corresponds to a call request of a calling user received by the mobile phone. The call request corresponds to a call request sent by the mobile phone to the called user.

In this embodiment, the call made by the mobile phone is a call made based on a subscriber identity module (subscriber identity module, SIM) card or an embedded subscriber identity module (embedded subscriber identity module, ESIM) card.

For example, taking an example that the mobile phone receives an incoming call request, referring to fig. 2, the phone number of the contact a, such as the number a, is pre-stored in the mobile phone. When the mobile phone receives the call request of the contact a, the interface 201 may be correspondingly displayed. The interface 201 may include a name of a contact (contact a), and the like. The incoming call of contact a will be referred to hereinafter simply as incoming call 1.

Based on the Bluetooth connection, when receiving the call request of the incoming call 1, the mobile phone can synchronize the contact information corresponding to the incoming call 1 with the watch. The contact information may include, among other things, a contact name (contact a), a phone number (number a), and the like.

After receiving the information of the call request, the watch corresponds to the display interface 202. Among other things, contact name (contact A), control 1, control 2, and the like may be included in interface 202. The control 1 is used for providing the function of refusing the current incoming call to the user, and the control 2 is used for providing the function of answering the current incoming call to the user.

It will be appreciated that in some implementations, the handset does not detect that the user has entered operations 1 and 2 in the interface 201 for a preset time. The operation 1 is used for indicating the mobile phone to answer the current incoming call. This operation 2 is used to instruct the mobile phone to reject the current incoming call. At the same time, the watch also does not detect that the user entered operations 3 and 4 in the interface 202. This operation 3 instructs the wristwatch to answer the incoming call currently being made based on the mobile phone. This operation 4 instructs the wristwatch to reject the incoming call currently being made based on the mobile phone. Wherein operation 3 may be a click operation on control 2 and operation 4 may be a click operation on control 1.

In another implementation, taking the mobile phone as the mobile phone 1 as an example, the call request of the incoming call 1 received by the mobile phone 1 is sent by other call devices (such as the mobile phone 2). Before the mobile phone 1 performs the refusal/answering process for the incoming call 1, the mobile phone 2 performs the hang-up process for the incoming call 1 under the instruction of the user. The hang-up process is stopped in response to the call request of the incoming call 1 sent from the mobile phone 2 to the mobile phone 1.

In the two implementations, the mobile phone (or the mobile phone 1) can automatically hang up the current incoming call 1. I.e. call 1 is not connected.

In some embodiments, a call logging application is installed in the watch that stores a history of calls made based on the handset. The history may include at least one of incoming call records and outgoing call records.

After the call 1 is not connected, the history 1 is correspondingly stored in the call record application, and the history 1 corresponds to the call 1.

Illustratively, referring to FIG. 3, a control 302 of a call logging application may be included on a main interface 301 of the watch. The user may enter an operation 303 on control 302 instructing the wristwatch to run a call log application. Wherein the operation 303 may be a click operation on the control 302.

Referring to fig. 4, in response to operation 303, the watch may run a call log application. In addition, the watch may also switch the interface 401 for call records.

As shown in fig. 4, on interface 401, the watch may present to the user a call log stored in the call log application. As shown in interface 401, history record 1 is included in the call record. The history 1 may show the name of the contact corresponding to the incoming call 1 (contact a) to the user, the time when the mobile phone receives the incoming call 1, and so on.

In some embodiments, based on the bluetooth connection, the user may enter an operation 403 on control 402, instructing the watch to dial back incoming call 1 based on the handset. The callback processing corresponds to telephone callback according to the number A corresponding to the contact A. Wherein the operation 403 may be a click operation on the control 402.

In some implementations, after receiving the user's operation 403, the watch cannot callback the incoming call 1 based on the phone. I.e. the watch fails to perform callback processing of incoming call 1 based on the handset. In this implementation, the service type of the bluetooth connection in the mobile phone is ANCS. Through ANCS, the mobile phone can transmit and send data with the watch.

In order to solve the above technical problems, an embodiment of the present application provides an information processing method and an electronic device, based on bluetooth connection, for an incoming call that is not connected, a watch stores a phone number of the incoming call that is not connected in a first history variable. When the watch performs callback processing on the incoming call which is not connected based on the mobile phone, the phone number can be obtained from the first historical variable and sent to the mobile phone. The watch finishes callback processing of the missed call based on the phone number called by the mobile phone.

The scheme provided by the embodiment of the application can be applied to the electronic equipment of the user. For example, in some embodiments, the electronic device may include a smart watch, smart bracelet, or the like in a wearable device. In other embodiments, the electronic device may also include portable electronic devices such as augmented reality (augmented reality, AR) devices, virtual Reality (VR) devices, artificial intelligence (artificial intelligence, AI) devices, vehicle devices, smart home devices, and the like.

In a specific implementation process, the electronic equipment can perform information interaction with the communication equipment based on Bluetooth connection, and the communication equipment supports a system communication function. The system call is a call based on a SIM card or an ESIM card.

In an embodiment of the present application, the electronic device may process a call task performed based on a call device (e.g., a user's mobile phone). The call tasks may include incoming calls and outgoing calls. In the incoming call, the call device receives a call request of a calling user as a called user. In the call-out call, the call device sends a call request as a calling user to a called user. The processing operations may include at least one of answering an incoming call, rejecting an incoming call, hanging up a call, and callback a call.

For example, in connection with the description of fig. 2, taking the electronic device as a smart watch, the call task is exemplified as an incoming call. After the call device receives a call request for an incoming call 1 as shown in fig. 2, the user may answer the incoming call through control 2 as in interface 202 or reject the incoming call through control 1 as in interface 202.

In different embodiments, the electronic device may have different compositions.

As an example, referring to fig. 5, a schematic software composition diagram of an electronic device is provided in an embodiment of the present application.

As shown in fig. 5, in this example, the software composition of the electronic device may have a multi-layered structure. The layers communicate with each other through a software interface. One or more functional modules may be included in the different layers. Functional modules in the multiple layers may be used in conjunction to implement one or more functions of the electronic device.

It is understood that an operating system may be running in the electronic device. For example, the operating system may be based on Is suitable for use in portable electronic devices or wearable electronic devices. As another example, the operating system may be a micro-operating system customized for a wearable electronic device or a portable electronic device.

An operating system running in the electronic device can provide the processing power of the kernel. For example, the operating system may provide storage, tasks, transmission of data in a bus (e.g., interprocess communication (Inter Process Communication, IPC)), task interruption, and the like.

The configuration and operation of the software in the various layers as shown in fig. 5 may be implemented based on the operating environment provided by the operating system running in the electronic device.

As shown in fig. 5, in this example, the electronic device may include an application layer, a framework layer, algorithms and internal libraries, a hardware abstraction layer, and a hardware driver layer.

Wherein the application layer may include a series of application packages. Take an electronic device as an example of a wristwatch. As an example, the application layer of the watch may include an application package for performing watch management, such as device management, OTA upgrade, dial management, and the like. The application layer may also include a map application, a music application, a navigation application, and the like, as well as a variety of third party developer-provided functionality applications. The application layer may also include communication type applications such as information, call records, calls, etc. The application layer can also comprise applications supporting interconnection and interworking functions with other devices, such as mobile phone positioning, voice assistants, personal transaction centers and the like. The application layer may also include sports health, wallet applications, manufacturing, and other functional applications.

It is understood that the configuration in the application layer as shown in fig. 5 is only an example. In other implementations, the application layer in the electronic device may include more or fewer applications. So as to support various functions of the electronic device through different application programs.

In the example of fig. 5, the call application and call logging application may implement management of incoming and/or outgoing calls made based on the telephony device.

For example, in connection with the description of fig. 4, at least one of an incoming call record and an outgoing call record based on the call device is stored in the call record application. The electronic device may dial back the phone number in the call record based on the call device through the call record application.

As shown in fig. 5, below the application layer may be a framework layer. The frame layer may also be referred to as a frame layer.

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

In this example, the framework layer may provide meta-capability Cross-platform execution environment (ACE) User Interface (UI) frameworks, system base service capabilities, underlying software service capabilities, sports health service capabilities, hardware service capabilities, and the like. Each framework and capability may correspond to an entity or logic module in the framework layer.

The ACE UI framework may include an ACE application development framework. The ACE application development framework can provide various application development logics so as to facilitate software development and design of development designers in the ACE application development framework. The ACE UI framework may also include UI tools (UI kit). The UI tool may provide image rendering processing capabilities. In some embodiments, the UI tool may be used to execute image rendering instructions indicated by an application in the application layer.

For example, after the dial management analyzes the received data file of the dial, the electronic device may be instructed to render the dial image through the UI kit according to the specific parameters of each element in the dial and the image data of each element obtained by the analysis process.

In other embodiments, a touchGFX framework may also be included in the ACE UI framework. the touchGFX framework, which is a graphical user interface (Graphical User Interface, GUI) framework, can execute image rendering instructions issued by applications, either independently or in conjunction with UI tools.

The system basic service capabilities may include communication services and audio services. The communication services may include, among other things, messaging services, conversation services, interworking services, contact services, and the like. The audio services may include music playing services, audio management services, voice broadcasting services, music control services, and the like.

The underlying software service capabilities may include basic services, manufacturing, and device management, among others. The base service may provide log services, file systems, NV management, exception logging, dual-machine communication, memory management, etc. Manufacturing may include manufacturing-related functions. Such as production services, aging services, etc. Device management may include device control, display management, bluetooth management, and the like.

Sports health service capabilities may include sports services and health services. Among other things, athletic services may include exercise services, daily activity services, data store synchronization services, training state assessment services, and the like. Health services may include heart rate services, sleep services, respiratory services, cardiac health services, and the like.

The hardware service capabilities may include various business support capabilities. For example, hardware service capabilities may include location services, bluetooth/bluetooth low energy (Bluetooth low energy, BLE) services, near field communication (Near Field Communication, NFC) services, and the like.

Algorithms and internal libraries may be included under the framework layer. The algorithm and the internal library can comprise a plurality of functional functions and interfaces, and the framework layer is used for realizing corresponding functions by calling the plurality of functional functions and interfaces.

By way of example, the algorithm and internal library may comprise an algorithm library, a base library. The algorithm library may include, among other things, living body detection related algorithm functions, gesture related algorithm functions, and the like. The base library may include bar code correlation algorithm functions, a base C library, and the like.

In this example, the algorithms and internal libraries may also include a communication protocol stack. Protocol data for supporting the communication capabilities of the device may be included in the communication protocol stack. For example, the communication protocol stack may include a bluetooth protocol stack, a BLE protocol stack, and the like.

The hardware abstraction layer, i.e. Hardware Abstract Layer, or simply HAL layer. An abstraction module of one or more entity components may be included in the HAL layer. The application program can realize the calling and the data acquisition of the corresponding entity component by issuing instructions to the abstract module in the entity component.

For example, in this example, a hardware abstraction layer may include a software abstraction module of a physical component such as a board level support package (Board Support Package, BSP), NFC, motor (motorr), liquid crystal display (Liquid Crystal Display, LCD), bluetooth, flash, touch Panel (TP), and the like. The hardware abstraction layer can also comprise a hardware abstraction module corresponding to a sensor component arranged in the electronic equipment. For example, acceleration sensor, gyroscope sensor, and other corresponding hardware abstraction modules. An interrupt module may also be included in the hardware abstraction layer.

In the example of fig. 5, a hardware driver layer may also be included in the electronic device. The hardware Driver layer may also be referred to as a Driver layer. Drives for one or more hardware components may be included in the hardware driver layer. When an application program needs to call a hardware component arranged in the electronic equipment, an instruction can be issued to a driving module arranged in a corresponding hardware driving layer, so that the driving module can convert the software instruction into an instruction which can be directly transmitted to the hardware component, and control and data transmission of the hardware component are realized.

By way of example, the hardware driver layer may include a BSP driver, LCD driver, TP driver, flash driver, monitor driver, bluetooth driver, sensor driver, and the like.

It should be noted that, the application layer may communicate with the framework layer by calling the framework API. The framework layer may also call a corresponding API implementation when functions that require the calling of algorithms and internal libraries communicate with the kernel layer or hardware abstraction layer. For example, APIs that call the kernel layer may include a CMSIS API, HAI APIs may be used when calling the HAL, and the like.

In connection with the example of fig. 5, taking the electronic device as a watch and the call device as a mobile phone as an example, in the embodiment of the present application, the watch may call the bluetooth/BLE module in the frame layer to establish bluetooth connection with the mobile phone. After the bluetooth connection is established, a call application, a call recording application, and the like in the wristwatch can perform information interaction and data transmission with the call device through the bluetooth connection.

The description and examples of fig. 5 are not intended to limit the electronic device in the present application. In other embodiments, the electronic device may also have more or less hardware or software components. The embodiment of the application does not limit the specific composition of the electronic device.

The scheme provided by the embodiment of the application can be applied to the electronic equipment shown in fig. 5.

In the following description, the electronic device is taken as a watch, and the call device is taken as a mobile phone to describe the scheme provided in the embodiment of the application.

In the embodiment of the application, based on the bluetooth connection between the mobile phone and the watch, when the mobile phone receives an incoming call request, the contact information in the incoming call request can be stored in the watch. Wherein the contact information includes a contact name, and a telephone number. So that the subsequent watch can perform the processing of the current incoming call request under the direction of the user. For example, the watch can perform any one of answering an incoming call, rejecting the incoming call, and callback call under the instruction of the user. The callback call is performed after the incoming call is hung up.

In some embodiments of the present application, the watch may also be referred to as a first device and the cell phone may also be referred to as a second device.

Illustratively, taking an example that the mobile phone receives an incoming call request, a SIM card is configured in the mobile phone. The mobile phone can receive incoming call requests sent by other call devices (such as a fixed phone, the mobile phone 2 and the like) based on the SIM card.

In this example, the handset and watch are connected via bluetooth. When the mobile phone receives an incoming call request, the mobile phone can send the contact information in the call request to the watch based on the Bluetooth connection.

The method provided in the embodiment of the present application will be described in detail below with reference to fig. 6, in which the call request of the incoming call received by the mobile phone is taken as the call request of the incoming call 1, and the phone number of the incoming call 1 and the contact information corresponding to the incoming call 1 are stored in the mobile phone in advance.

In some embodiments of the present application, the incoming call 1 may also be referred to as a first incoming call, and the contact information corresponding to the incoming call 1 may also be referred to as first contact information corresponding to the incoming call 1.

As shown in fig. 6, the scheme may include:

s601, the mobile phone sends a first incoming call message to the watch.

For example, when the mobile phone receives the call request of the incoming call 1, the mobile phone may send a first incoming call message to the watch based on the bluetooth connection with the watch. The first incoming call message includes a telephone number corresponding to incoming call 1, i.e., number a. The first incoming call message is used to indicate incoming call 1.

In some embodiments of the present application, the first incoming message may also be referred to as a first call request message, and the number a may also be referred to as a first number.

For example, a SIM card is configured in the mobile phone, and the call request of the incoming call 1 is received based on the SIM card. The call request of the incoming call 1 may be sent by other call devices. In addition, the mobile phone stores contact information of the incoming call 1 in advance. The contact information includes a contact name (contact a), a telephone number (number a), and the like. The contact A is a name stored in the mobile phone by the contact corresponding to the incoming call 1.

In this example, the watch may establish a connection with the handset via bluetooth. When receiving the call request of the incoming call 1, the mobile phone can send a first incoming call message to the watch based on the Bluetooth connection, so that the watch can acquire the number A from the first incoming call message.

In the embodiment of the present application, the watch may continue to execute S602 and subsequent processes when receiving the first incoming call message.

S602, after the watch receives the first incoming call message, the number A is stored in a first incoming call variable.

Illustratively, the first incoming call variable is used to store a phone number of an incoming call currently being made based on the mobile phone. Wherein the first incoming call variable may be stored in a memory of the watch. After receiving the first incoming call message, the watch can store the number A in the first incoming call message in the first incoming call variable. The number A is stored so that the number A can be acquired when the subsequent watch processes the number A.

For example, the first incoming call variable may be incomingCallNumberFromBt. After receiving the first incoming call message, the watch responds to the first incoming call message and stores the number A in the incomingCallNumberFromBt.

S603, the watch adds the first incoming call message to the message queue.

In some embodiments of the present application, in order to ensure normal operation and processing of other application processes in the watch, the watch may first add the first incoming call message to the message queue, so as to facilitate processing of the first incoming call message by the subsequent watch.

S604, after receiving the first interrupt information, the watch takes out the first incoming message from the message queue.

Illustratively, the first interrupt information is for instructing the wristwatch to perform processing of the first incoming message. After receiving the first interrupt information, the wristwatch may take out the first incoming message from the message queue and perform the processing as S605.

In an embodiment of the present application, the first interrupt information may be sent by an interrupt module as in fig. 5.

S605, the watch reads the first incoming call variable, and stores the number A in the first incoming call variable into the second incoming call variable.

Illustratively, the second incoming call variable is used to identify an incoming call number received by the watch. The watch can obtain the incoming call number, namely the number A, by reading the first incoming call variable, and store the number A into the second incoming call variable.

For example, in connection with the description in S602, the second incoming call variable may be incomingphoneimberinfo. After receiving the interrupt information in S604, the wristwatch can acquire the number a by reading incomingCallNumberFromBt and store the number a in incomingphoneinfo.

Alternatively, in some embodiments of the present application, the watch may directly perform the operation in S605 to store the number a in the second incoming call variable in response to the first incoming call message. So that the subsequent watch can continue to process the number a.

For example, after receiving the first incoming call message, the watch responds to the first incoming call message and stores the number a in the first incoming call message in incomingPhoneNumberInfo.

In some embodiments of the present application, the incoming call variables include a first incoming call variable and a second incoming call variable.

In other embodiments of the present application, after receiving the first incoming call message, the wristwatch may further display a first interface according to information in the first incoming call message. In this embodiment, the information in the first incoming message also includes the contact name (contact A). The first interface may present call information corresponding to the incoming call 1 to the user. The call information may include a contact name, etc.

For example, the watch may display an interface 202 as shown in fig. 2 based on information in the first incoming message. The description of the interface 202 may refer to the description in fig. 2, and will not be repeated here.

It should be noted that, in still other embodiments of the present application, the first incoming call message may further include the home location of the number a. The watch may also present the home location of number a and the contact name to the user in the first interface in response to the first incoming message.

In some embodiments of the present application, taking the first interface as the interface 202 as an example, the watch may receive an operation input by a user through the interface 202. The watch can send the instruction A to the mobile phone through Bluetooth connection according to the operation input by the user, so that the mobile phone can execute the first processing corresponding to the instruction A. Wherein, the instruction A comprises any one of an incoming call answering instruction or an incoming call refusing instruction. When the instruction A comprises an incoming call answering instruction, the first processing corresponds to answering an incoming call. When the instruction a includes a refusal incoming call instruction, the first process corresponds to refusing an incoming call.

For example, the operation input by the user is operation 3, and operation 3 indicates that the watch answers the incoming call 1 currently made based on the mobile phone. The watch may send an answer call instruction to the phone through the bluetooth connection according to operation 3. After receiving the call answering instruction, the mobile phone answers the current call 1 in response to the call answering instruction. Thus, the watch can realize answering the current incoming call based on the mobile phone.

As another example, the operation input by the user is operation 4, and operation 4 indicates that the watch refuses the incoming call 1 currently made based on the mobile phone. The watch may send a refusal incoming call instruction to the handset via the bluetooth connection according to operation 4. After receiving the refused incoming call instruction, the mobile phone responds to the refused incoming call instruction to refuse the current incoming call 1. Thus, the watch can reject the current incoming call based on the mobile phone.

In some embodiments of the present application, the incoming call 1 is not connected, i.e., the incoming call 1 is not answered and rejected. After the incoming call 1 is not connected, the mobile phone and the watch can perform the processing from S606 to S608, so as to store the record corresponding to the incoming call 1 in the call record application in the watch.

S606, the mobile phone sends a first missed message to the watch.

Illustratively, after the incoming call 1 is not turned on, the handset may send a first missed message to the watch. The first missed message is used to indicate that the incoming call 1 is not on.

In some embodiments of the present application, the first missed message may also be referred to as a second missed call indication.

In response to the first missed message, the wristwatch may perform operations as S607 and S608.

S607, after receiving the first missed message, the watch reads the second incoming call variable, and stores the number A in the second incoming call variable into the first missed variable.

In the embodiment of the application, the first missed variable is used for storing the telephone number of the missed call. The first missed variable is stored in the memory of the watch. The missed call corresponds to a call that has not been answered or rejected. After the watch receives the first missed message, the watch can acquire the number A by reading the second incoming call variable, and the number A is stored in the first missed variable.

Illustratively, the first missed variable is missedphoneNumberInfo. After the watch reads the number a in incomingphonium-berInfo, the number a may be stored in missedPhoneNumberInfo.

And S608, the watch reads the first missed variable, and stores the number A in the first missed variable into the first historical variable.

For example, the watch may read number a from the first missed variable and store number a in the first historical variable. The first history variable is stored in a memory of the watch. In this way, when the subsequent watch executes callback processing on the incoming call 1 based on the mobile phone, the phone number corresponding to the incoming call 1 can be obtained from the first history variable.

For example, the first history variable callHistoryInfo.phoneNum, callHistoryInfo.phoneNum has a history buffer. The watch can read the missed cache in the missedphoneNumberInfo, obtain the number A, and store the number A in the history cache of the callHistoryInfo.

It should be noted that, in the embodiment of the present application, the history buffer includes a history buffer 1, a history buffer 2, … …, and a history buffer n, n is greater than 2. The plurality of history caches are used for storing a plurality of telephone numbers. The plurality of telephone numbers are telephone numbers corresponding to the call tasks based on the mobile phone. The call tasks may include incoming calls and outgoing calls, among others. The telephone numbers stored in the history buffer memory have a sequence, namely, the earlier the starting time corresponding to the call task is, the closer the corresponding stored telephone number is to the head of the history buffer memory, the later the starting time corresponding to the call task is, and the closer the corresponding stored telephone number is to the tail of the history buffer memory. The header of the history buffer corresponds to the history buffer 1, and the header of the history buffer corresponds to the history buffer n.

In addition, when the watch stores the telephone numbers into the callhistoryinfo.phone num, the telephone numbers stored in the history buffer 1 to the history buffer n can be sequentially and backwardly progressed, the history buffer 1 is vacated, and then the telephone numbers are stored in the history buffer 1.

For example, in some implementations, a phone number, such as number B, corresponding to another call task (e.g., call 2) is stored in history buffer 1. The telephone numbers are not stored in the history buffer 2 to the history buffer n.

In connection with the foregoing description, in this implementation, the watch may obtain the number a by reading the missedPhoneNumberInfo. Before the watch stores the number a in the history buffer, the number B in the history buffer 1 may be stored in the history buffer 1, the history buffer 1 is emptied, and the number a is stored in the history buffer 1 in the callhistoryinfo phonenum.

In another implementation, no telephone number is stored in any of history buffer 1 through history buffer n. In this implementation, the watch may store the number a directly in the history buffer 1 after it has obtained the number a by reading the missed buffer 1 in the missedPhoneNumberInfo.

In other embodiments of the present application, the incoming call 1 is correspondingly configured with a first identifier. The watch may also store this first identification together with the number a in the history buffer 1 of the callhistoryinfo. So that the subsequent watch can obtain the number a from the callhistoryinfo.

It should be noted that, in the embodiment of the present application, the history record corresponding to the incoming call 1 stored in the call record application corresponds to the first identifier stored in the callhistoryinfo.

For example, the history buffer 1 in the callhistoryin-fo.phonenum stores the phone number (number a) of the incoming call 1 and the first identifier, with the history corresponding to the incoming call 1 being the history 1 shown in the interface 401 in fig. 4. History record 1 shown in interface 401 corresponds to a first identification in history cache 1.

In some embodiments of the present application, history 1 may also be referred to as a first history.

In other embodiments of the present application, after the operations of S606 to S608 are completed, the mobile phone and the wristwatch may further proceed with operations as S609 to S613.

S609, the mobile phone sends a second missed message to the watch.

In an embodiment of the present application, the second missed message is used to indicate that incoming call 1 is not on. After the watch receives the second missed message, the watch may perform operations as S610 to S613 in response to the second missed message.

In some embodiments of the present application, the second missed message may also be referred to as a first missed call indication.

And S610, responding to the second missed message, and judging whether the service type of the Bluetooth connection used by the mobile phone is ANCS by the watch.

In some embodiments of the present application, the watch determines that the type of service of the bluetooth connection used by the handset is ANCS. When the service type of the bluetooth connection used by the mobile phone is ANCS, the second missed message may include the contact name corresponding to the incoming call 1, i.e. the contact a. In this case, the wristwatch may correspondingly perform an operation as in S613 in response to the second missed call message.

It should be noted that, in the embodiment of the present application, when the service type of the bluetooth connection used by the mobile phone is ANCS, the phone number corresponding to the incoming call 1, that is, the number a, is not included in the second missed message.

In other embodiments of the present application, the watch determines that the type of service of the bluetooth connection used by the handset is not ANCS. When the service type of the bluetooth connection used by the mobile phone is not ANCS, the second missed message may include contact a and number a. In this case, the wristwatch may correspondingly perform operations as S611 to S613 in response to the second missed call message.

S611, the watch stores the number A in the first missed variable.

For example, the watch may store the number a in the missedPhoneNumberInfo.

Note that, in the embodiment of the present application, after the number a is stored in the missedPhoneNumberInfo, the number a will cover the data stored before the missedPhoneNumberInfo.

And S612, the watch reads the number A in the first missed variable and stores the number A in the first historical variable.

For example, the watch may read missedphoneNumberInfo and obtain number A. And stores the number a in the history buffer 1 in callhistoryinfo.

Note that, in the embodiment of the present application, after the number a is stored in the history buffer 1, the number a will overwrite the data stored in the history buffer 1.

In the embodiment of the present application, the watch may further perform the operation of S613 in response to the second missed message.

S613, obtaining second interface information according to the second missed message.

Illustratively, the second interface corresponds to a message notification interface that receives incoming call 1. The second interface information may include a contact name corresponding to the incoming call 1.

In conjunction with the description in S610, the contact name of incoming call 1, i.e., contact a, may be included in the second missed message. And when the watch receives the second missed message, responding to the second missed message, and acquiring the name of the contact person of the incoming call 1. The watch may render the second interface based on information in the second missed message. And realizing the display of the second interface.

For example, referring to fig. 7, the second interface may be interface 701. The user may be presented with the contact name of call 1 (contact a) in interface 701.

Through S609 to S613, in response to the second missed message, the wristwatch may perform the operation of S613 when determining that the service type of the bluetooth connection used by the mobile phone is ANCS, and perform the operations of S610 to S613 when determining that the service type of the bluetooth connection used by the mobile phone is not ANCS. After the watch receives the second missed message, the number A is still stored in the first history variable.

In other embodiments of the present application, when the watch receives the second missed message, only the processing in S613 is executed in response to the second missed message, to obtain the contact name of the incoming call 1, so as to implement display of the second interface.

In combination with the foregoing description, the watch may also dial back the incoming call 1 based on the mobile phone under the instruction of the user, that is, based on the phone number corresponding to the incoming call 1 called out by the mobile phone.

For example, according to the illustration in fig. 4, a user may enter an operation 403 in interface 401 for control 402, instructing the watch to callback the incoming call 1 based on the handset. After receiving the operation 403, the watch can implement the phone callback for the incoming call 1 according to the number a in the first history variable according to the processing in fig. 8.

In some embodiments of the present application, operation 403 may also be referred to as a first operation, and control 402 may also be referred to as a first control.

As shown in fig. 8, the scheme may include:

s801, in response to operation 403, the watch stores the number a in the first history variable in the first outgoing variable.

Illustratively, upon receiving the operation 403, the watch obtains the number A from the first history variable in response to the operation 403. For the implementation of storing the number a in the first history variable, reference may be made to the description in fig. 6, which is not repeated here.

For example, in connection with fig. 4, operation 403 is an operation performed on a control (control 402) corresponding to the incoming call 1 record. The incoming call 1 record may be stored in a call log application of the watch.

In connection with the above description, the incoming call 1 is correspondingly configured with a first identifier, and the first identifier and the number a are both stored in the callHistory-info. For example, the first identification and the number a are both stored in the history buffer 1.

In this example, in response to this operation 403, the watch may determine the identity of the incoming call 1 indicated by the user, i.e., the first identity, according to this operation 403. After the watch acquires the first identifier, the number a can be acquired from the callhistoryinfo.ph-oneNum according to the first identifier.

It can be understood that when the watch calls back the incoming call 1 based on the mobile phone, only the phone number corresponding to the incoming call 1 is needed.

Thus, in other embodiments of the present application, when the watch stores the number a in the first history variable in the first expiration variable, the number a stored in the callhistoryinfo.

Illustratively, a plurality of bits of storage space are configured in the history buffer 1. bits may also be referred to as bits. The storage space of the plurality of bits is bit0, bit1, … … and bit m in sequence.

In some implementations, m is greater than 20 and the number a may be stored in bit1 through bit20, respectively. The watch may store the number a stored in the history buffer 1 corresponding to the bits 1 to 20 in the outgoingPhoneNumberInfo, and store the number a stored in the outgoingPh-oneNumberInfo in the first outgoing variable.

For example, the first exhalation variable may be phonecallcmd.szphonenum. The wristwatch stores the number a in the callhistoryinfo, -phoneNum, in the phonecallcmd.szphonenum after storing the number a in the outgoingphonenumbinfo.

S802, the watch sends a call callback instruction to the mobile phone.

Illustratively, the callback telephone instruction includes a first outgoing variable. The callback telephone instruction is used for indicating a first calling variable of calling of the mobile phone. The watch may send a call-back instruction to the mobile phone based on the bluetooth connection after completing the operation of S801.

For example, the callback instruction includes phonecallcmd.szphonenum. The number A is stored in PhoneCallCmd.szPhoneNum. The callback telephone instruction is used for instructing the mobile phone to callback the telephone according to the number A in PhoneCallCmd.szPhoneNum.

In some embodiments of the present application, the callback telephone instruction may also be referred to as a first callback indication.

S803, the mobile phone responds to the call-back instruction, and calls back according to the number A in the first calling variable.

Illustratively, after receiving the callback telephone instruction, the handset may obtain the number a from the phonecallcmd. Thus, after receiving the call-back instruction, the mobile phone realizes call-back according to the number A in PhoneCallCmd.szPhoneNum. And then the callback processing of the incoming call 1 is completed.

In other embodiments of the present application, referring to fig. 9, the handset may also display interface 901 after calling out number a in phonecallcmd. Accordingly, the watch displays interface 902 after calling out phone callcmd.szphonenum based on number a in the phone. Interface 901 and interface 902 correspond to the outgoing call interface of number a. Contact name (contact a) and the like are included in the interface 901 and the interface 902.

In some implementations of the present application, interface 902 may also be referred to as a third interface.

The above description has been made mainly from the perspective of each functional module for the solutions provided in the embodiments of the present application. Those of skill in the art will readily appreciate that the elements and algorithm steps of the examples described in connection with the embodiments disclosed herein may be implemented as hardware or combinations of hardware and computer software. Whether a function is implemented as hardware or computer software driven hardware depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

The integrated modules may be implemented in hardware or in software functional modules. It should be noted that, in the embodiment of the present application, the division of the modules is schematic, which is merely a logic function division, and other division manners may be implemented in actual implementation.

By way of example, fig. 10 shows a schematic diagram of the composition of an electronic device 1000. As shown in fig. 10, the electronic device 1000 may include: a processor 1001 and a memory 1002. The memory 1002 is used to store computer-executable instructions. For example, in some embodiments, the processor 1001, when executing the instructions stored in the memory 1002, may cause the electronic device 1000 to perform the method shown in any of the above embodiments. In the example of fig. 10, a display 1003 may also be included in the electronic device. The display 1003 may read contact information from the memory 1002 for display under the control of the processor 1001.

It should be noted that, all relevant contents of each step related to the above method embodiment may be cited to the functional description of the corresponding functional module, which is not described herein.

Fig. 11 shows a schematic diagram of the components of a chip system 1100. The chip system 1100 may include: a processor 1101 and a communication interface 1102 for supporting the relevant devices to implement the functions referred to in the above embodiments. In one possible design, the chip system further includes a memory to hold the necessary program instructions and data for the electronic device. The chip system can be composed of chips, and can also comprise chips and other discrete devices. It should be noted that, in some implementations of the present application, the communication interface 1102 may also be referred to as an interface circuit.

It should be noted that, all relevant contents of each step related to the above method embodiment may be cited to the functional description of the corresponding functional module, which is not described herein.

The functions or acts or operations or steps and the like in the embodiments described above may be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using a software program, it may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the processes or functions described in accordance with embodiments of the present application are produced in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by a wired (e.g., coaxial cable, fiber optic, digital subscriber line (digital subscriber line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer readable storage medium may be any available medium that can be accessed by a computer or a data storage device including one or more servers, data centers, etc. that can be integrated with the medium. The usable medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a Solid State Disk (SSD)), or the like.

Although the present application has been described in connection with specific features and embodiments thereof, it will be apparent that various modifications and combinations can be made without departing from the spirit and scope of the application. Accordingly, the specification and drawings are merely exemplary illustrations of the present application as defined in the appended claims and are considered to cover any and all modifications, variations, combinations, or equivalents that fall within the scope of the present application. It will be apparent to those skilled in the art that various modifications and variations can be made in the present application without departing from the spirit or scope of the application. Thus, if such modifications and variations of the present application fall within the scope of the claims and the equivalents thereof, the present application is intended to include such modifications and variations as well.

Claims (16)

1. An information processing method, wherein the method is applied to a first device, and a communication connection is established between the first device and a second device; the first device is provided with a display screen; the method comprises the following steps:

receiving a first call request message, wherein the first call request message is used for indicating a first incoming call, and the first call request message comprises a first number of the first incoming call;

Storing the first number in a first history when the first call is not connected;

receiving a first missed call indication, wherein the first missed call indication is used for indicating that the first call is not connected;

under the condition that the first missed call indication is transmitted through a preset service, after the first missed call indication is received, the first history record is not updated; the first missed call indication does not include the first number;

receiving a first operation of a user, wherein the first operation is an operation on a first control; the first control is a control which is displayed on the display screen and indicates that the first incoming call is not connected;

and responding to the first operation, sending a first callback instruction to the second equipment, wherein the first callback instruction comprises the first number acquired from the first history record, and the first callback instruction is used for instructing the second equipment to callback a telephone according to the first number.

2. The method of claim 1, wherein the second device has stored therein a first number of the first incoming call and first contact information corresponding to the first incoming call.

3. A method according to claim 1 or 2, characterized in that,

the storing the first number in a first history record includes:

receiving a second missed call indication, wherein the second missed call indication is used for indicating that the first call is not connected;

and in response to the second missed call indication, storing the first number in the first history.

4. The method of claim 3, wherein after receiving the first call request message, the method further comprises:

storing the first number of the first incoming call indicated by the first call request message in an incoming call variable, wherein the incoming call variable is used for storing the number of the current incoming call;

storing the first number in the first history in response to the second missed call indication, including:

storing the first number from the incoming call variable into a first history variable, the first history variable being one of one or more variables included in the first history record, each variable in the first history record being used to store a telephone number of an incoming call.

5. The method of claim 4, wherein prior to said storing said first number from said incoming call variable into said first history variable, said method further comprises:

Storing the first number from the incoming call variable to a first missed variable; the first missed variable is used for storing telephone numbers of missed calls;

the storing the first number from the incoming call variable to the first history variable includes:

and storing the first number from the first missed variable to the first historical variable.

6. The method of any of claims 1-5, wherein after the receiving the first missed call indication, the method further comprises, prior to not updating the first history record:

and determining that the service type used by the second equipment is the preset service when the first missed call indication is received.

7. The method of claim 6, wherein the preset service is ANCS.

8. The method of any of claims 4-7, wherein prior to the sending a first callback indication to the second device in response to the first operation, the method further comprises:

and responding to the first operation, and acquiring the first number from the first historical variable.

9. The method of claim 8, wherein the storing the first number in a first history comprises:

Storing the first number and a first identification of the first incoming call in the first history;

before the obtaining the first number from the first history variable, the method further includes:

determining callback information according to the first operation; the callback information comprises the first identifier;

the obtaining the first number from the first history variable includes:

and acquiring the first number from the first historical variable according to the first identifier indicated by the callback information.

10. The method according to any one of claims 5 to 9, wherein,

the first missed variable is missedphoneNumberInfo;

the first history variable is callhistoryinfo.

11. The method according to any one of claims 1-10, wherein after receiving the first call request message, the method further comprises:

the first call request message also comprises first contact information corresponding to the first incoming call;

rendering a first interface according to the first number and the first contact information in the first call request message; the first interface is the processing interface for receiving the first call; the first interface includes call information corresponding to the first incoming call.

12. The method of claim 11, wherein after receiving the first missed call indication, the method further comprises:

the first missed call indication comprises the first contact information;

rendering a second interface according to the first contact information in the first missed call indication; the second interface includes a first notification; the first notification is used for indicating that the first incoming call is not connected.

13. The method of claim 11 or 12, wherein after the sending of the first callback indication to the second device, the method further comprises:

displaying a third interface; the third interface is a processing interface for dialing the first number.

14. A communication system comprising a first device and a second device, the first device and the second device establishing a communication connection;

the second device is configured to send a first call request message to the first device when a first incoming call is received, where the first call request message is used to indicate the first incoming call, and the first call request message includes a first number of the first incoming call;

The first device is used for storing the first number in a first history record under the condition that the first call is not connected;

the second device is further configured to send a first missed call indication to the first device through a preset service, where the first missed call indication is used to indicate that the first call is not connected; the first missed call indication does not include the first number;

the first device is further configured to not update the first history record if the first missed call indication is received;

the first device is further configured to receive a first operation of a user, where the first operation is an operation of a first control; the first control is a control displayed on a display screen and used for indicating that the first incoming call is not connected;

the first device is further configured to send, in response to the first operation, a first callback indication to the second device, where the first callback indication includes the first number obtained from the first history;

the second device is further configured to dial back a phone by using the first number according to the first callback instruction.

15. A chip system, wherein the chip system is applied to a first device; the system-on-chip includes one or more interface circuits and one or more processors; the interface circuit and the processor are interconnected through a circuit; the interface circuit is configured to receive a signal from a memory of the first device and to send the signal to the processor, the signal comprising computer instructions stored in the memory; the first device performs the method of any of claims 1-13 when the processor executes the computer instructions.

16. A computer-readable storage medium, wherein the computer-readable storage medium is applied to a first device; comprising computer instructions which, when run on the first device, cause the first device to perform the method of any of claims 1-13.