Communication method and system between devices, and storage medium

Abstract

The invention provides an inter-device communication method and system and a storage medium. The first electronic equipment sends a first request to a first server, wherein the first request carries an account ID of a first user account; and the first server determines a second electronic device logged in with a second user account based on the account ID of the first user account, the second user account is the same as or associated with the first user account, and a network call establishment request is sent to the second electronic device. The second electronic equipment receives the operation of the user on the first answering control and sends a second request to the second server; and the second server generates an account ID and an account password of the first network call and sends the account ID and the account password of the first network call to the first electronic device and the second electronic device, and the first electronic device and the second electronic device establish the first network call. According to the invention, the watch can actively initiate the network call connection to other devices under the condition that the watch does not store the device information of other devices.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a method, system and storage medium for communication between devices. Background Art

[0002] With the popularity of smart watches in recent years, communication between watches and mobile phones has become an indispensable feature. If watches and mobile phones can communicate, it will be convenient for users to use.

[0003] Currently, the operator's calling plan can be used. The watch needs to be designed with a subscriber identity module (SIM) card slot or support the embedded subscriber identity module (ESIM) function, integrate the phone card into the watch, and make calls with mobile phones or other operator devices by dialing / answering calls. However, if the watch does not support a SIM card slot or does not support the ESIM function, it cannot communicate with other devices. Summary of the invention

[0004] The present application provides a method, system and storage medium for communication between devices, which enable a watch to actively initiate a network call connection to other devices even when the watch does not store device information of other devices.

[0005] In a first aspect, the present application provides a device-to-device communication system, the system comprising a first electronic device, a second electronic device, a first server, and a second server, a first long connection is established between the second electronic device and the first server, a first user account is logged in to the first electronic device, a second user account is logged in to the second electronic device, and the first user account and the second user account are the same or related to each other; wherein the first electronic device is used to receive and respond to a first user operation, and send a first request to the first server, the first request carrying an account ID of the first user account; the first server is used to respond to the first request and determine, based on the account ID of the first user account, a second electronic device logged in to the second user account; the first The server is also used to send a request to establish a network call to the second electronic device; the second electronic device is used to display a first user interface in response to the request to establish a network call, and the first user interface displays a first answering control and a first hang-up control; the second electronic device is also used to receive a user's operation on the first answering control and send a second request to the second server; the second server is used to generate an account ID and an account password for the first network call in response to the second request; the second server is also used to send the account ID and account password of the first network call to the first electronic device and the second electronic device, and the account ID and account password of the first network call are used by the first electronic device and the second electronic device to establish the first network call.

[0006] In the embodiment of the present application, the first electronic device may be a device that supports a SIM card slot or supports an ESIM, or the first electronic device may be a device that does not support a SIM card slot or supports an ESIM. In other words, devices that support a SIM card slot or support an ESIM may be applicable to the present application.

[0007] In some embodiments, the first electronic device may be a children's watch, the second electronic device may be a family member of the user of the first electronic device, the first electronic device and the second electronic device may log in to the same user account, or log in to different user accounts but establish a binding relationship.

[0008] In other embodiments, the account ID and account password of the first network call can also be obtained by the first electronic device from the second server. Then the second server sends it to the second electronic device, and the second electronic device can display the first user interface, in which the first answering control and the first hang-up control are displayed. The second electronic device can receive the user's operation on the first answering control, and connect to the second server based on the account ID and account password of the first network call. After the first electronic device and the second electronic device are both connected to the second server based on the account ID and account password of the first network call, the first electronic device and the second electronic device establish the first network call, and the first electronic device and the second electronic device can send audio messages or send audio messages and images to each other through the first network call.

[0009] Through this method, when the first electronic device does not store the device information of other devices inside, the first electronic device can also actively initiate a network call connection to other electronic devices. After receiving the user's request to play the network call, the first electronic device can send a request to establish a network call to other devices through the first server. The other device then applies for the account ID and account password of the first network call, thereby realizing the first network call between the first electronic device and the second electronic device. The first electronic device and the second electronic device can send audio messages or send audio messages and images to each other through the first network call.

[0010] In combination with the first aspect, in a possible implementation, the second electronic device is further used to: establish a first session connection with the first electronic device; in response to receiving the account ID and account password of the first network call sent by the second server, send a first message to the first electronic device through the first session connection; the first electronic device is further used to display a second user interface in response to the first message, and the second user interface includes a second hang-up control and call duration.

[0011] In combination with the first aspect, in a possible implementation manner, the first session connection is initiated by the second electronic device to the first electronic device based on the device information of the first electronic device stored in the second electronic device.

[0012] The device information of the first electronic device includes one or more of the following: a unique identifier of the first electronic device, a device type of the first electronic device, a cloud device ID of the first electronic device, a node ID of the first electronic device, an IP address of the first electronic device, and a MAC address of the first electronic device.

[0013] The second server cannot send messages to the first electronic device. Then the second electronic device needs to establish a first session connection with the first electronic device. After the second electronic device connects to the second server based on the account ID and account password of the first network call, the second electronic device needs to send a first message to the first electronic device through the first session connection. The first message is used to inform the first electronic device that the second electronic device has been connected to the second server and the first electronic device needs to switch to display the second user interface. In this way, when the first electronic device cannot actively establish a session connection with the second electronic device, the first electronic device can actively establish a session connection through the second electronic device.

[0014] In combination with the first aspect, in one possible implementation, the second electronic device is also used to stop displaying the first user interface and start displaying a third user interface in response to receiving the account ID and account password of the first network call sent by the second server, and the third user interface includes a third hang-up control and call duration.

[0015] In combination with the first aspect, in a possible implementation, the system also includes a third electronic device, on which a third user account is logged in, and the third user account is the same as or related to the first user account; the first server is specifically used to: respond to the first request, determine the second electronic device on which the second user account is logged in and the third electronic device on which the third user account is logged in based on the account ID of the first user account; send a request to establish a network call to the second electronic device and the third electronic device; the third electronic device is used to display a fourth user interface in response to the request to establish a network call, and the fourth user interface displays a second answering control and a fourth hang up control; the second electronic device is also used to send a second message to the first server; the first server is also used to send a second message to the third electronic device; the third electronic device is also used to stop displaying the fourth user interface in response to the second message.

[0016] In other embodiments, the second message may also be sent by the first electronic device to the third electronic device through the first server.

[0017] In this way, when the first electronic device initiates an Internet call connection, the first electronic device cannot select a specific device to initiate the Internet call connection to, and the first electronic device can send the Internet call establishment request to one or more devices logged in with the same account, and to one or more devices logged in with different accounts but associated with each other through the second server. After one of the electronic devices agrees to establish an Internet call connection with the first electronic device, the other electronic devices that receive the Internet call connection will stop prompting the user to answer the Internet call.

[0018] In combination with the first aspect, in a possible implementation, the second electronic device is further used to: receive an operation of the user on the first hang-up control to establish a first session connection with the first electronic device; send a third message to the first electronic device through the first session connection; the first electronic device is further used to display a fifth user interface in response to the third message, the fifth user interface including first indication information, and the first indication information is used to prompt the user that the user has refused to establish a network call.

[0019] The second server cannot send a message to the first electronic device. After the second electronic device refuses to establish a network call connection with the first electronic device, the second electronic device needs to establish a first session connection with the first electronic device and send a call rejection message to the first electronic device, so that the first electronic device can prompt the user that the second electronic device has rejected the network call.

[0020] In combination with the first aspect, in a possible implementation, the system also includes a third electronic device, on which a third user account is logged in, and the third user account is the same as or related to the first user account; the second electronic device is also used to: send a fourth message to the first server; the first server is also used to send a fourth message to the third electronic device; the third electronic device is also used to stop displaying a fourth user interface in response to the fourth message, the fourth interface is displayed after the third electronic device receives the network call request sent by the first server, and the fourth user interface displays a second answer control and a fourth hang up control.

[0021] The third electronic device also establishes a long connection with the second server.

[0022] Optionally, the first message may also be sent by the first electronic device to the third electronic device through the first server.

[0023] After the second electronic device refuses to establish an Internet call connection with the first electronic device, it is necessary to send a message to the third electronic device to inform the third electronic device to stop displaying the Internet call request interface (ie, the fourth user interface).

[0024] In combination with the first aspect, in one possible implementation, the second electronic device is further used to receive and send a third request to the second server in response to a second user operation; the second server is further used to generate an account ID and account password for a second network call in response to the third request; the second server is further used to send the account ID and account password for the second network call to the first electronic device and the second electronic device, and the account ID and account password for the second network call are used by the first electronic device and the second electronic device to establish a second network call.

[0025] The second user operation may be that the user operates on the second electronic device to actively initiate a network call connection to the first electronic device. When the second electronic device actively initiates a network call connection, the second electronic device may select a target for the network call connection (for example, the user selects the first electronic device).

[0026] In combination with the first aspect, in a possible implementation, the second electronic device is further used to establish a second session connection with the first electronic device; the second electronic device is further used to display a sixth user interface in response to a second user operation, and the sixth user interface includes a fifth hang-up control; the first electronic device is further used to: in response to the account ID and account password of the second network call sent by the second server, display a seventh user interface, and the seventh user interface includes a third answering control and a sixth hang-up control; receive and respond to the user's operation on the third answering control, and send a fifth message to the second electronic device through the second session connection; the second electronic device is further used to display an eighth user interface in response to the fifth message, and the eighth user interface includes call duration and the seventh hang-up control.

[0027] When the second electronic device actively initiates the network call connection, the second electronic device also needs to actively establish a second session connection with the first electronic device. After the first electronic device confirms to answer the network call request sent by the second electronic device, the first electronic device can send a fifth message to the second electronic device through the second session connection, so that the second electronic device can start to display the call in progress interface (i.e., the eighth user interface).

[0028] In combination with the first aspect, in one possible implementation, the first electronic device is further used to receive and respond to the user's operation on the sixth hang-up control, and send a sixth message to the second electronic device through the second session connection; the second electronic device is further used to respond to the sixth message and display a ninth user interface, the ninth user interface including second indication information, and the second indication information is used to prompt the user that the user has refused to establish a network call.

[0029] When the second electronic device actively initiates the network call connection, the second electronic device also needs to actively establish a second session connection with the first electronic device. After the first electronic device refuses to answer the network call request sent by the second electronic device, the first electronic device can send a sixth message to the second electronic device through the second session connection, so that the second electronic device can prompt the second electronic device that the first electronic device has refused the network call.

[0030] In combination with the first aspect, in a possible implementation manner, the first electronic device is a watch, and the second electronic device is a mobile phone.

[0031] In a second aspect, the present application provides a method for communication between devices, the method comprising: the second electronic device displays a first user interface, and the first user interface displays a first answering control and a first hang-up control; wherein the first user interface is displayed after the second electronic device receives a network call request sent by the first server, and the network call request is sent to the second electronic device after the first server receives the first request sent by the first electronic device and determines the second electronic device logged in with the second user account based on the account ID of the first user account carried in the first request, the first user account is the user account logged in on the first electronic device, and the second user account is the same as or associated with the first user account; the second electronic device receives the user's operation on the first answering control, and sends a second request to the second server, the second request is used to instruct the second server to generate an account ID and account password for the first network call and send the account ID and account password for the first network call to the first electronic device and the second electronic device, and the account ID and account password of the first network call are used for the first electronic device and the second electronic device to establish the first network call.

[0032] In combination with the second aspect, in a possible implementation, after the second electronic device displays the first user interface, the method also includes: the second electronic device establishes a first session connection with the first electronic device; in response to receiving the account ID and account password of the first network call sent by the second server, the second electronic device sends a first message to the first electronic device based on the first session connection, and the first message is used to instruct the first electronic device to display a second user interface, and the second user interface includes a second hang-up control and call duration.

[0033] In conjunction with the second aspect, in a possible implementation manner, the first session connection is initiated by the second electronic device to the first electronic device based on device information of the first electronic device stored in the second electronic device.

[0034] In combination with the second aspect, in one possible implementation, the device information of the first electronic device includes one or more of the following: a unique identifier of the first electronic device, a device type of the first electronic device, a cloud device ID of the first electronic device, a node ID of the first electronic device, an IP address of the first electronic device, and a MAC address of the first electronic device.

[0035] In combination with the second aspect, in one possible implementation, after the second electronic device receives the account ID and account password of the first network call sent by the second server, the method also includes: the second electronic device stops displaying the first user interface and starts displaying a third user interface, and the third user interface includes a third hang-up control and call duration.

[0036] In combination with the second aspect, in a possible implementation, after the second electronic device displays the first user interface, the method also includes: the second electronic device receives the user's operation on the first hang-up control; in response to the operation on the first hang-up control, establishes a first session connection with the first electronic device; the second electronic device sends a third message to the first electronic device through the first session, and the third message is used to instruct the first electronic device to display a fifth user interface, and the fifth user interface includes first indication information, and the first indication information is used to prompt the user that the user has refused to establish a network call.

[0037] In combination with the second aspect, in a possible implementation, after the second electronic device receives the user's operation on the first hang-up control, the method also includes: the second electronic device sends a fourth message to the first server, the fourth message is used to instruct the first server to send a fourth message to the third electronic device, the fourth message is used to instruct the third electronic device to stop displaying a fourth user interface, the fourth interface is displayed after the third electronic device receives the network call request sent by the first server, the fourth user interface displays the second answering control and the fourth hang-up control, a third user account is logged in to the third electronic device, and the third user account is the same as or related to the first user account.

[0038] In combination with the second aspect, in a possible implementation, the method also includes: the second electronic device receives and responds to the second user operation, sends a third request to the second server, the third request is used to instruct the second server to generate an account ID and account password for the second network call, and sends the account ID and account password of the second network call to the first electronic device and the second electronic device, and the account ID and account password of the second network call are used by the first electronic device and the second electronic device to establish the second network call.

[0039] In combination with the second aspect, in a possible implementation, the method also includes: after the second electronic device receives and responds to the second user operation, the method also includes: the second electronic device establishes a second session connection with the first electronic device; in response to the second user operation, displays a sixth user interface, the sixth user interface includes a fifth hang-up control; receives a fifth message sent by the first electronic device through the second session connection, wherein the fifth message is sent by the first electronic device after receiving the user's operation on the third answering control in the seventh user interface, and the seventh user interface is displayed by the first electronic device in response to the account ID and account password of the second network call sent by the second server; in response to the fifth message, the second electronic device displays an eighth user interface, the eighth user interface includes call duration and the seventh hang-up control.

[0040] In combination with the second aspect, in a possible implementation, after the second electronic device displays the sixth user interface, the method also includes: the second electronic device receives the sixth message sent by the first electronic device, wherein the sixth message is sent by the first electronic device after receiving the user's operation on the sixth hang-up control; in response to the sixth message, the second electronic device displays a ninth user interface, the ninth user interface includes second indication information, and the second indication information is used to prompt the user that the network call has been rejected.

[0041] In conjunction with the second aspect, in a possible implementation manner, the first electronic device is a watch, and the second electronic device is a mobile phone.

[0042] In a third aspect, the present application provides an electronic device, which is a second electronic device, and the second electronic device includes one or more processors and one or more memories; wherein the one or more memories are coupled to the one or more processors, and the one or more memories are used to store computer program codes, and the computer program codes include computer instructions. When the one or more processors execute the computer instructions, the second electronic device executes a device-to-device communication method provided in any possible implementation of the above-mentioned second aspect.

[0043] In a fourth aspect, the present application provides a chip system, which is applied to a second electronic device. The chip system includes one or more processors, and the processor is used to call computer instructions to enable the second electronic device to execute a device-to-device communication method provided in any possible implementation of the above-mentioned second aspect.

[0044] In a fifth aspect, the present application provides a computer-readable storage medium, comprising instructions, which, when executed on a second electronic device, enable the second electronic device to execute a method for inter-device communication provided in any possible implementation of the second aspect.

[0045] For the description of the beneficial effects of the second to fifth aspects, reference may be made to the description of the beneficial effects in the first aspect, and this application will not repeat them here. BRIEF DESCRIPTION OF THE DRAWINGS

[0046] Figure 1A A system architecture diagram provided for this application;

[0047] Figure 1B An interactive schematic diagram provided for this application;

[0048] Figure 2A-2L A UI schematic diagram showing the electronic device 100 calling the smart watch 200;

[0049] Figure 3 A schematic diagram showing a method for establishing a trusted relationship between an electronic device 100 and a smart watch 200 is shown;

[0050] Figure 4 A schematic diagram showing a method for establishing a session connection between the electronic device 100 and the smart watch 200 is shown;

[0051] Figure 5 A schematic diagram showing a method for successfully establishing an RTC call connection between the electronic device 100 and the smart watch 200 is shown;

[0052] Figure 6 A schematic diagram of a method in which an electronic device 100 and a smart watch 200 fail to establish an RTC call connection is shown;

[0053] Figure 7 Another schematic diagram of a method in which an electronic device 100 and a smart watch 200 do not establish an RTC call connection is shown;

[0054] Figure 8 A schematic diagram showing another method in which the electronic device 100 and the smart watch 200 do not establish an RTC call connection;

[0055] Figure 9A-9K A UI schematic diagram showing a smart watch 200 calling an electronic device 100;

[0056] Fig.10 A schematic diagram showing a method in which the smart watch 200 sends an RTC call establishment request to a device with the same account or a different account and an associated relationship through a push server;

[0057] Fig.11 A schematic diagram showing a method for establishing an RTC call between a smart watch 200 and an electronic device 100 is shown;

[0058] Fig.12 A schematic diagram of a method in which a smart watch 200 and an electronic device 100 do not establish an RTC call connection is shown;

[0059] Fig.13 Another schematic diagram of a method in which a smart watch 200 and an electronic device 100 do not establish an RTC call connection is shown;

[0060] Fig.14 A schematic diagram showing another method in which the smart watch 200 and the electronic device 100 do not establish an RTC call connection;

[0061] Fig.15 A schematic diagram of a method flow for inter-device communication provided in this application;

[0062] Fig.16 A schematic diagram of the structure of an electronic device is shown;

[0063] Fig.17 1 is a software structure block diagram of the electronic device 100 according to an embodiment of the present invention. DETAILED DESCRIPTION

[0064] The technical solutions in the embodiments of the present application will be described clearly and in detail below in conjunction with the accompanying drawings. In the description of the embodiments of the present application, unless otherwise specified, " / " means or, for example, A / B can mean A or B; "and / or" in the text is only a description of the association relationship of associated objects, indicating that there can be three relationships, for example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. In addition, in the description of the embodiments of the present application, "multiple" means two or more than two.

[0065] In the following, the terms "first" and "second" are used for descriptive purposes only and are not to be understood as suggesting or implying relative importance or implicitly indicating the number of the indicated technical features. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of the features, and in the description of the embodiments of the present application, unless otherwise specified, "plurality" means two or more.

[0066] The term "user interface (UI)" in the following embodiments of the present application refers to a medium interface for interaction and information exchange between an application or operating system and a user, which realizes the conversion between the internal form of information and the form acceptable to the user. A common form of user interface is a graphical user interface (GUI), which refers to a user interface related to computer operation displayed in a graphical manner. It can be a visual interface element such as text, icons, buttons, menus, tabs, text boxes, dialog boxes, status bars, navigation bars, widgets, etc. displayed on the display screen of an electronic device.

[0067] Figure 1A A system architecture diagram provided for this application.

[0068] like Figure 1A As shown, the system may include a real time communication (RTC) server, an electronic device 100 and a smart watch 200.

[0069] Among them, the electronic device 100 and the smart watch 200 can establish a network call connection.

[0070] The network call connection may be an RTC call connection. The following embodiments of the present application are described by taking the network call connection as an RTC call connection as an example. The network call connection may also be other call connections, not limited to the RTC call connection, and the present application does not limit this.

[0071] The electronic device 100 may initiate an RTC call establishment request to the smart watch 200. After the smart watch 200 receives the RTC call establishment request sent by the electronic device 100, the smart watch 200 may establish an RTC call connection with the electronic device 100 after obtaining the user's consent. Specifically, the electronic device 100 may send an RTC call establishment request to the RTC server. After the RTC server receives the RTC call establishment request sent by the electronic device 100, the RTC server may generate a conference ID and a conference password for the RTC call, and send the conference ID and the conference password for the RTC call to the electronic device 100. Afterwards, the RTC server may also send the conference ID and the conference password for the RTC call to the smart watch 200. After receiving the conference ID and the conference password for the RTC call, the electronic device 100 and the smart watch 200 may establish an RTC call connection based on the conference ID and the conference password for the RTC call.

[0072] Optionally, the smart watch 200 may also initiate an RTC call establishment request to the electronic device 100. After the electronic device 100 receives the RTC call establishment request sent by the smart watch 200, the electronic device 100 may establish an RTC call connection with the smart watch 200 after obtaining the user's consent. Specifically, the smart watch 200 may send an RTC call establishment request to the RTC server. After the RTC server receives the RTC call establishment request sent by the smart watch 200, the RTC server may generate a conference ID and conference password for the RTC call, and send the conference ID and conference password for the RTC call to the smart watch 200. Afterwards, the RTC server may also send the conference ID and conference password for the RTC call to the electronic device 100. After receiving the conference ID and conference password for the RTC call, the electronic device 100 and the smart watch 200 may establish an RTC call connection based on the conference ID and conference password for the RTC call.

[0073] Next, a method for inter-device communication provided in the present application is explained in combination with a scenario in which the electronic device 100 calls the smart watch 200 and a scenario in which the smart watch 200 calls the electronic device 100.

[0074] Figure 1B An interactive schematic diagram provided for this application.

[0075] like Figure 1B As shown, the present application includes a device server, a business server, an RTC server, an electronic device 100 and a smart watch 200.

[0076] Among them, the RTC server can establish an RTC call between the electronic device 100 and the smart watch 200.

[0077] A session connection and an RTC call can be established between the electronic device 100 and the smart watch 200 .

[0078] The smart watch 200 can establish a long connection with the device server. The device server and the service server can communicate with each other.

[0079] The device server can provide identity authentication and remote control services for the smart watch 200 .

[0080] The device server may also provide authentication equipment and remote control services for the electronic device 100 .

[0081] The service server may provide watch service for the smart watch 200 and the electronic device 100 .

[0082] For the responsibilities of each server, please refer to the description in the subsequent embodiments, and this application will not go into details here.

[0083] The electronic device 100 calls the smart watch 200 .

[0084] First, the UI implementation of the electronic device 100 calling the smart watch 200 is introduced.

[0085] Figure 2A-2L A UI schematic diagram showing the electronic device 100 calling the smart watch 200 is shown.

[0086] Optionally, the electronic device 100 can call the smart watch 200 in the first application.

[0087] Figure 2A The main interface 210 of the electronic device 100 is shown. The main interface 210 includes icons of multiple applications, such as an icon of a weather application, an icon of a Huawei store application, an icon of a smart home application, an icon of a sports and health application, an icon of a memo application, an icon of a calendar application, an icon of a life service application, an icon of a first application, an icon of a camera application, an icon of an address book application, an icon of a phone application, and an icon of a message application, etc. The main interface 210 also shows a battery indicator, a weather indicator, a date indicator, a network signal indicator, a page indicator, etc.

[0088] like Figure 2A As shown, the electronic device 100 may receive an input operation (eg, a single click) from a user on an icon of a first application, and in response to the input operation from the user, the electronic device 100 may display Figure 2B The user interface 220 is shown. The user interface 220 is the main interface of the first application.

[0089] like Figure 2B The electronic device 100 (such as a mobile phone) can display the user interface 220 of the first application. The user interface 220 may include one or more smart devices and the online or offline status of the smart devices. For example, the number of smart devices may be 8. For example, a smart speaker in the living room, a smart large screen in the living room, a smart table lamp in bedroom one, a smart air purifier in the bedroom, a smart camera in the living room, a smart air conditioner in the living room, a tablet, smart curtains in the living room, and a smart air conditioner in bedroom one. The user interface 220 exemplarily shows that the smart speaker in the living room is offline, the smart large screen in the living room is offline, the smart table lamp in the bedroom is offline, the smart air purifier in the bedroom is offline, the smart camera in the living room is offline, the smart air conditioner in the living room is offline, the tablet is offline, the smart curtains in the living room are offline, and the Honor children's watch is online, wherein the Honor children's watch can be a smart watch 200.

[0090] Optionally, one or more smart devices and smart devices shown in the user interface 220 may be associated with the same user account, or may be associated with different user accounts, but associations are established between the different user accounts.

[0091] like Figure 2B The electronic device 100 may receive an input operation (such as a single click) from a user on a device icon of a Honor children's watch, and in response to the user's input operation, the electronic device 100 may display Figure 2C User interface 230 is shown. User interface 230 is a detailed interface of the Honor children's watch.

[0092] Multiple options are shown in the user interface 230, such as micro chat option, video call option, phone option, watch management option, watch address book option, call record option, alarm option, album option, pedometer option and application management option.

[0093] Among them, the user can send messages to the smart watch 200 through the WeChat chat option.

[0094] The user can make a voice network call or a video network call with the smart watch 200 through the video call option.

[0095] The user can make a call with the smart watch 200 through the operator's phone through the phone option.

[0096] The user can manage the smart watch 200 through watch management.

[0097] The user can view the address book information added in the smart watch 200 through the watch address book option.

[0098] The user can view the call records of the smart watch 200 in the recent period through the call record option.

[0099] The user can view the alarms set by the smart watch 200 through the alarm option.

[0100] The user can view one or more pictures taken by the smart watch 200 through the album option.

[0101] The user can view the exercise details of the smart watch 200, such as the number of steps, calorie consumption, etc., through the pedometer option.

[0102] The user can view one or more applications downloaded by the smart watch 200 through the application management option.

[0103] The electronic device 100 may receive an input operation (eg, a single click) from the user for a video call option in the user interface 230 , and in response to the input operation from the user, the electronic device 100 may send a video call request to the smart watch 200 .

[0104] After the smart watch 200 receives the video call request, the electronic device 100 can establish a network video call with the smart watch 200 .

[0105] Optionally, the electronic device 100 may also establish an Internet voice call with the smart watch 200. Specifically, after the electronic device 100 receives the user's input operation for the video call option, the electronic device 100 may prompt the user to initiate an Internet video call or an Internet voice call. After selecting an Internet voice call, the user may send a request to establish an Internet voice call to the smart watch 200. The user may also send a request to establish an Internet voice call to the smart watch 200 after selecting an Internet voice call. In other possible implementations, after the smart watch 200 receives the video call request, the electronic device 100 may establish an Internet video call with the smart watch 200. After the electronic device 100 and the smart watch 200 establish an Internet video call, the electronic device 100 may receive a user operation to switch the Internet video call to an Internet voice call.

[0106] For example, Figure 2C As shown, the electronic device 100 may receive a user input operation (eg, a single click) for a video call option in the user interface 230, and in response to the user input operation, the electronic device 100 may display Figure 2D The user interface 2310 shown. The user interface 2310 may include a switch to voice call control and a hang-up control, and the user interface 2310 may be a network call request interface. Among them, the user can switch the video call to the voice call by switching to the voice call control. The user can also stop sending the video call request to the smart watch 200 by hanging up the control.

[0107] Likewise, after the electronic device 100 receives the user's input operation for the video call option in the user interface 230 , the electronic device 100 may send a video call request to the smart watch 200 .

[0108] In some embodiments, if the smart watch 200 is online, the smart watch 200 can receive a video call request sent by the electronic device 100 .

[0109] Optionally, after receiving the video call request sent by the electronic device 100, the smart watch 200 may display Figure 2EThe user interface 240 shown. The user interface 240 is a network call waiting interface. The user interface 240 may include a hang-up control and an answer control. Among them, the user can refuse to establish a network video call with the electronic device 100 through the hang-up control. The user can also establish a network video call with the electronic device 100 through the answer control.

[0110] For example, Figure 2E As shown, the smart watch 200 can receive the user's input operation (such as a single click) for the answering control in the user interface 240, and in response to the user's input operation, the electronic device 100 can display Figure 2F The user interface 250 is shown. The user interface 250 is an interface indicating that the network call has been answered. The user interface 250 may include a hang-up control, and the user can end the network video call with the electronic device 100 through the hang-up control.

[0111] Similarly, after the smart watch 200 receives the user's input operation on the answer control in the user interface 240, that is, after the smart watch 200 agrees to establish a network video call with the electronic device 100, the smart watch 200 can send a message to the electronic device 100, so that the electronic device 100 can switch from the network call request interface to the network call answered interface.

[0112] For example, Figure 2G As shown, after the electronic device 100 receives the message sent by the smart watch 200, the electronic device 100 can display Figure 2GThe user interface 260 shown is an interface for answering a network call. The user interface 260 may include a hang-up option, a switch to a network voice call option, a switch to the front and rear cameras option, an option to turn off the camera of the electronic device 100, a mute option, a speaker option, and an option to reduce the user interface 260. Among them, the user can actively end the network video call with the smart watch 200 through the hang-up option. The user can also switch the network video call to the network voice call option by switching to the network voice call option, and the network voice call option cannot display the images captured by the cameras of both parties. The user can also switch the electronic device 100 from the front camera to the rear camera by switching the front and rear camera options, and display the image captured by the rear camera of the electronic device 100, and send the image captured by the rear camera of the electronic device 100 to the smart watch 200. The user can also stop the electronic device 100 from capturing images through the front camera by turning off the camera option of the electronic device 100, and stop displaying the image captured by the electronic device 100 through the front camera in the user interface 260, and also stop sending the image captured by the electronic device 100 through the front camera to the smart watch 200. The user can also use the mute option to turn off the microphone of the electronic device 100 and stop collecting audio through the microphone, and also stop sending the audio collected by the electronic device 100 through the microphone to the smart watch 200. The user can also use the speaker option to make the electronic device 100 play the audio sent by the smart watch 200 through the speaker. The user can also use the shrink user interface 260 option to shrink the user interface 260. After exiting the first application, the electronic device 100 can also suspend and display the shrunken user interface 260.

[0113] Optionally, after receiving the video call request sent by the electronic device 100, the smart watch 200 may display Figure 2E The user interface 240 is shown. The user of the smart watch 200 can refuse to establish a network voice call with the electronic device 100.

[0114] For example, Figure 2H As shown, the smart watch 200 may receive an input operation (e.g., a single click) from the user for a hang-up control in the user interface 240, and in response to the user's input operation, the smart watch 200 may stop displaying the user interface 240. After the smart watch 200 receives the input operation from the user for the hang-up control in the user interface 240, the smart watch 200 may send a message to the electronic device 100 to inform the electronic device 100 that the smart watch 200 has rejected the network video call with the electronic device 100.

[0115] After receiving the message sent by the smart watch 200, the electronic device 100 can display Fig.2I The user interface 270 shown in the figure shows a prompt message “The watch has rejected your video call request” in the user interface 270. The prompt message is used to prompt the user of the electronic device 100 that the user of the smart watch 200 rejects the establishment of a network video call.

[0116] After the electronic device 100 displays the user interface 270, the electronic device 100 may continue to display Figure 2C User interface 230 is shown.

[0117] Optionally, after receiving the video call request sent by the electronic device 100, if the smart watch 200 is making an Internet video call or an Internet voice call with another electronic device, the smart watch 200 may send a message to the electronic device 100, the message being used to indicate to the electronic device 100 that the smart watch 200 is making an Internet video call or an Internet voice call with another device, and please try again later.

[0118] After receiving the message sent by the smart watch 200, the electronic device 100 can display Figure 2J The user interface 280 is shown, and the user interface 280 shows the prompt information "Watch is busy". The prompt information is used to prompt the user of the electronic device 100 and the user of the smart watch 200 that the smart watch 200 is making an Internet video call or an Internet voice call with other devices.

[0119] After the electronic device 100 displays the user interface 280, the electronic device 100 may continue to display Figure 2C User interface 230 is shown.

[0120] Optionally, after the electronic device 100 sends the network video call request to the smart watch 200, if the electronic device 100 does not receive a feedback message sent by the smart watch 200 within a certain period of time, such as a message of receiving the network video call request or a message of rejecting the network video call request or a busy line message, the electronic device 100 may stop sending the network video call request to the smart watch 200 and display a Figure 2K The user interface 290 shown. The user interface 290 shows a prompt message "No one answered the watch, please try again later." The prompt message is used to prompt the user of the electronic device 100 that the smart watch 200 has no response.

[0121] After the electronic device 100 displays the user interface 290, the electronic device 100 may continue to display Figure 2C User interface 230 is shown.

[0122] In other embodiments, if the smart watch 200 is in an offline state, the smart watch 200 cannot receive the video call request sent by the electronic device 100 .

[0123] In the case where the electronic device 100 cannot send the video call request to the smart watch 200, the electronic device 100 may display Figure 2L User interface 2910 is shown. User interface 2910 shows a prompt message “Watch is not online, please try again later”. This prompt message is used to remind the user of electronic device 100 that smart watch 200 is offline and it is impossible to establish a network video call or network audio call with the offline smart watch 200.

[0124] After the electronic device 100 displays the user interface 2910, the electronic device 100 may continue to display Figure 2C User interface 230 is shown.

[0125] Next, the specific implementation of the electronic device 100 calling the smart watch 200 is introduced.

[0126] The electronic device 100 calling the smart watch 200 includes the following stages: the electronic device 100 and the smart watch 200 establish a trusted relationship, the electronic device 100 and the smart watch 200 establish a session connection, and the electronic device 100 and the smart watch 200 establish an RTC call connection.

[0127] 1. The electronic device 100 and the smart watch 200 establish a trusted relationship.

[0128] Figure 3 A schematic diagram of a method for establishing a trusted relationship between the electronic device 100 and the smart watch 200 is shown.

[0129] S301 : The smart watch 200 establishes a connection with a device server.

[0130] Optionally, the smart watch 200 can establish a long connection with the device server.

[0131] The device server may be a server that authenticates and authorizes the device. The device server may also send a control message to the smart watch 200.

[0132] Optionally, after the smart watch 200 is turned on for the first time, the smart watch 200 can send an authentication and certification request to the device server. After the device server authentication and certification are passed, the device server marks the smart watch 200 as a legitimate device, and the smart watch 200 and the device server can establish a long connection.

[0133] Exemplarily, the long connection between the smart watch 200 and the device server can be a message queuing telemetry transport (MQTT) connection. After the device server is authenticated and certified, the smart watch 200 can send a request to establish an MQTT connection to the device server. After the device server receives the request to establish an MQTT connection sent by the smart watch 200, the device server can send a request to confirm the establishment of the connection to the smart watch 200. After the smart watch 200 receives the request to confirm the establishment of the connection sent by the device server, the smart watch 200 can establish an MQTT connection with the device server.

[0134] Optionally, after the smart watch 200 establishes a long connection with the device server, the user can add the smart watch 200 to the Figure 2B The user interface 220 is shown. The online state or offline state of the smart watch 200 is displayed in the user interface 220.

[0135] Optionally, the smart watch 200 also needs to send the device information of the smart watch 200 to the device server, and the device server can save the device information of the smart watch 200. The device information of the smart watch 200 includes but is not limited to one or more of the following: the device unique identifier of the smart watch 200, the Internet protocol (IP) address of the smart watch 200, the media access control address (MAC) address of the smart watch 200, the public key of the smart watch 200, the device type of the smart watch 200, etc. Among them, the device unique identifiers of different devices are different.

[0136] The smart watch 200 stores a pair of public and private keys internally. The smart watch 200 can also send the public key of the smart watch 200 to the device server so that the electronic device 100 can obtain the public key of the smart watch 200 from the device server and complete the trusted authentication process between the electronic device 100 and the smart watch 200.

[0137] The device server may store device information of multiple devices, such as device information of the electronic device 100, which includes but is not limited to one or more of the following: a unique device identifier of the electronic device 100, an Internet Protocol IP address of the electronic device 100, a MAC address of the electronic device 100, a public key of the electronic device 100, a device type of the electronic device 100, and other information.

[0138] S302: The electronic device 100 establishes a connection with a device server.

[0139] Optionally, the electronic device 100 and the device server may establish a long connection.

[0140] Optionally, the long connection between the electronic device 100 and the device server may be an MQTT connection. The electronic device 100 may send an MQTT connection establishment request to the device server. After receiving the MQTT connection establishment request sent by the electronic device 100, the device server may send a confirmation connection establishment request to the electronic device 100 after confirmation. After receiving the confirmation connection establishment request sent by the device server, the electronic device 100 may establish an MQTT connection with the device server.

[0141] Optionally, after the electronic device 100 receives the user's input operation (such as a single click) for the first application, the electronic device 100 displays Figure 2B After the user interface 220 is shown, the electronic device 100 may send a request to establish a persistent connection to the device server and establish a persistent connection with the device server.

[0142] Optionally, the electronic device 100 may not establish a persistent connection with the device server. For example, when the electronic device 100 does not start the first application, the electronic device 100 may not establish a persistent connection with the device server.

[0143] It should be noted that the above-mentioned long connection is not limited to MQTT connection, but can also be other connection methods, which is not limited in this application.

[0144] S303: The electronic device 100 obtains the device information of the smart watch 200 from the device server.

[0145] Optionally, when receiving device information of different devices, the device server can store the device information of different devices. When maintaining the device information of different devices, the device server generates a cloud device ID for each device. The cloud device IDs of different devices are different. The device server can uniquely determine the target device based on the cloud device ID.

[0146] The device information maintained by the device server may include but is not limited to one or more of the following: the device's unique device identifier, the device's IP address, the device's MAC address, the device's cloud device ID, the device's public key, etc.

[0147] For example, the device information of the smart watch 200 maintained by the device server may include but is not limited to one or more of the following: the device unique identifier of the smart watch 200, the IP address of the smart watch 200, the MAC address of the smart watch 200, the cloud device ID of the smart watch 200, the public key of the smart watch 200, the device type of the smart watch 200, etc.

[0148] After the electronic device 100 establishes a connection with the device server, the electronic device 100 can obtain the device information of the smart watch 200 from the device server and save the device information of the smart watch 200.

[0149] Optionally, the electronic device 100 adds a smart watch 200 to Figure 2B After the user interface 220 is shown, the electronic device 100 can obtain the device information of the smart watch 200 from the device server and save the device information of the smart watch 200.

[0150] The electronic device 100 can obtain the device information of other more devices from the device server and save the device information of other more devices.

[0151] Optionally, the electronic device 100 also stores device information of the electronic device 100, and the device information of the electronic device 100 includes but is not limited to one or more of the following: a unique device identifier of the electronic device 100, an Internet Protocol IP address of the electronic device 100, a MAC address of the electronic device 100, a public key of the electronic device 100, a device type of the electronic device 100, and other information.

[0152] S304 : The electronic device 100 obtains the public key of the smart watch 200 from the device information of the smart watch 200 .

[0153] Optionally, when receiving device information of different devices, the device server can store the device information of different devices. When maintaining the device information of different devices, the device server generates a node ID for each device. The device server can uniquely determine the target device based on the node ID.

[0154] Optionally, the electronic device 100 adds a smart watch 200 to Figure 2B After the user interface 220 is shown, the electronic device 100 can generate a node ID for the smart watch 200 .

[0155] The device information maintained by the device server may include but is not limited to one or more of the following: the device's unique device identifier, the device's IP address, the device's MAC address, the device's cloud device ID, the device's public key, the device's node ID, the device's type, etc.

[0156] For example, the device information of the smart watch 200 maintained by the device server may include but is not limited to one or more of the following: the device unique identifier of the smart watch 200, the IP address of the smart watch 200, the MAC address of the smart watch 200, the cloud device ID of the smart watch 200, the public key of the smart watch 200, the node ID of the smart watch 200, the device type of the smart watch 200, etc.

[0157] The electronic device 100 and the smart watch 200 need to complete a trusted authentication process so that the electronic device 100 and the smart watch 200 can communicate with each other.

[0158] If the electronic device 100 and the smart watch 200 have not completed the trusted authentication process, the electronic device 100 and the smart watch 200 cannot communicate with each other.

[0159] The trusted authentication process between the electronic device 100 and the smart watch 200 may include the process shown in S304 to S309 .

[0160] In some embodiments, the device information of the device may also include other information, such as the manufacturer of the device, the production date of the device, etc. This application does not limit this.

[0161] The electronic device 100 may obtain the public key of the smart watch 200 from the device information of the smart watch 200 being maintained.

[0162] S305 : The electronic device 100 encrypts the first parameter based on the public key of the smart watch 200 to obtain a first encrypted parameter.

[0163] S306. The electronic device 100 sends the first encryption parameter to the device server.

[0164] S307 . The device server sends the first encryption parameter to the smart watch 200 .

[0165] The electronic device 100 may randomly generate a first parameter, and encrypt the first parameter based on a public key of the smart watch 200 to obtain a first encrypted parameter.

[0166] The electronic device 100 may send the first encryption parameter to the smart watch 200 through the device server. Specifically, the electronic device 100 sends the first encryption parameter to the device server, and then the device server sends the first encryption parameter to the smart watch 200.

[0167] S308. The smart watch 200 decrypts the first encryption parameter based on the private key of the smart watch 200 to obtain the first parameter.

[0168] After the smart watch 200 receives the first encryption parameter sent by the electronic device 100 through the device server, the smart watch 200 can obtain the private key of the smart watch 200 and decrypt the first encryption parameter based on the private key of the smart watch 200.

[0169] If the smart watch 200 can successfully encrypt the first encryption parameter using the private key of the smart watch 200 to obtain the first parameter, it can be proved that the electronic device 100 and the smart watch 200 are trusted devices.

[0170] If the smart watch 200 cannot successfully encrypt the first encryption parameter using the private key of the smart watch 200 to obtain the first parameter, it means that the electronic device 100 and the smart watch 200 are not trusted devices.

[0171] Optionally, the smart watch 200 may also actively initiate a trusted authentication process to the electronic device 100 .

[0172] Specifically, the smart watch 200 can randomly generate a second parameter, encrypt the second parameter based on the private key of the smart watch 200, obtain a second encrypted parameter, and send the second encrypted parameter to the electronic device 100 through the device server. After receiving the second encrypted parameter sent by the device server, if the electronic device 100 can decrypt the second encrypted parameter through the public key of the smart watch 200 to obtain the second parameter, it means that the electronic device 100 and the smart watch 200 are trusted devices. If the second encrypted parameter cannot be decrypted through the public key of the smart watch 200 to obtain the second parameter, it means that the electronic device 100 is not a trusted device between the smart watch 200.

[0173] Optionally, the electronic device 100 may initiate a trusted authentication process to the smart watch 200 and the smart watch 200 may initiate a trusted authentication process to the electronic device 100. If both processes are authenticated, it indicates that the electronic device 100 and the smart watch 200 are trusted devices.

[0174] S309: Trusted Device The electronic device 100 and the smart watch 200 are trusted devices.

[0175] Based on the description in S308, when it is determined that the electronic device 100 and the smart watch 200 are trusted devices, the electronic device 100 can communicate with the smart watch 200, for example, the electronic device 100 can establish a network video call or a network voice call with the smart watch 200.

[0176] When it is determined that the electronic device 100 and the smart watch 200 are not trusted devices, the electronic device 100 cannot communicate with the smart watch 200, for example, the electronic device 100 cannot establish a network video call with the smart watch 200 or the electronic device 100 cannot establish a network voice call with the smart watch 200.

[0177] Optionally, when it is determined that the electronic device 100 and the smart watch 200 are trusted devices, in order to ensure the security of subsequent communication between the electronic device 100 and the smart watch 200, the electronic device 100 and the smart watch 200 can each generate a secret key based on the first parameter and / or the second parameter, and encrypt the communication message between the electronic device 100 and the smart watch 200 based on the secret key before sending it to the peer device, thereby ensuring the security of communication between the electronic device 100 and the smart watch 200.

[0178] In a possible implementation, the electronic device 100 may generate a first key using a first parameter, and the smart watch 200 may generate a second key based on the first parameter, and the first key and the second key may be the same or different.

[0179] In other possible implementations, the electronic device 100 may generate the first key using the second parameter. The smart watch 200 may generate the second key based on the second parameter, and the first key and the second key may be the same or different.

[0180] In other possible implementations, the electronic device 100 may generate a first key using a first parameter and a second parameter. The smart watch 200 may generate a second key based on the first parameter and the second parameter, and the first key and the second key may be the same or different.

[0181] The first key and the second key can encrypt and decrypt each other. For example, the second key can decrypt data encrypted by the first key, and the first key can decrypt data encrypted by the second key.

[0182] Optional, Figure 3 In the embodiment, the electronic device 100 may include a connection networking server, and the smart watch 200 may include a connection networking client. Figure 3 In the embodiment, the interaction between the electronic device 100 and the device server may be performed through the connection networking service end on the electronic device 100 and the device server. Figure 3 In the embodiment, the interaction between the smart watch 200 and the device server may be performed through the connection networking client on the smart watch 200 and the device server. Figure 3 In the embodiment, the interaction between the electronic device 100 and the smart watch 200 may be performed through a connection networking server on the electronic device 100 and a connection networking client on the smart watch 200. Figure 3 The connection networking server and the connection networking client are not shown.

[0183] 2. The electronic device 100 and the smart watch 200 establish a session connection.

[0184] After the electronic device 100 and the smart watch 200 mutually recognize each other as trusted devices, the electronic device 100 can establish a second session connection with the smart watch 200. This facilitates communication between the electronic device 100 and the smart watch 200 through the second session connection.

[0185] Figure 4 A schematic diagram of a method for establishing a session connection between the electronic device 100 and the smart watch 200 is shown.

[0186] The electronic device 100 may include a first application and a connection networking service end, and the smart watch 200 may include a connection networking client end and a second application.

[0187] In some embodiments, the connection networking service end may be a functional module in the first application, or the connection networking service end may not be a functional module in the first application.

[0188] In some embodiments, the connection networking client may be a functional module in the second application, or the connection networking client may not be a functional module in the second application.

[0189] In some embodiments, the connection networking service end may be referred to as a magiclink svc module.

[0190] In some embodiments, the connection networking client can be called a magiclink sdk module.

[0191] The first application and the second application may be the same or similar, and both may implement a network video call or a network audio call between devices.

[0192] S401. A first application stores device information of multiple devices.

[0193] Depend on Figure 3 As can be seen from the embodiment, the first application stores device information of multiple devices, for example, device information of the smart watch 200 is stored.

[0194] In other embodiments, the device information of the smart watch 200 may also be referred to as the networking information of the smart watch 200 .

[0195] The device information of the smart watch 200 includes but is not limited to the unique device identifier of the smart watch 200, the IP address of the smart watch 200, the MAC address of the smart watch 200, the cloud device ID of the smart watch 200, the public key of the smart watch 200, the node ID of the smart watch 200, etc.

[0196] S402: The first application displays a first user interface, in which device icons of multiple devices are displayed, and an association relationship is established between the multiple devices.

[0197] The first user interface may be a main interface of the first application.

[0198] The first application can be Figure 2A The first application shown. In other embodiments, the first application may also be referred to as a smart space application.

[0199] The first user interface may be Figure 2B The user interface 220 is shown. The device icons of the multiple devices may include a device icon for a smart speaker, a device icon for a smart TV, a device icon for a smart desk lamp, a device icon for an air purifier, a device icon for a camera, a device icon for an air conditioner, a device icon for a tablet, a device icon for curtains, a device icon for a smart watch 200, and the like.

[0200] The multiple devices shown in the user interface 220 may establish an association relationship, for example, associated with the same user account, or associated with different user accounts, but different user accounts have established an association relationship.

[0201] S403: The first application receives an operation by the user on the device icon of the smart watch 200 in the first user interface, and displays a control interface of the smart watch 200.

[0202] For example, the smart watch 200 may be Figure 2B The Honor children's watch shown.

[0203] Exemplary, reference Figure 2B In the description of the embodiment, the first application can receive and respond to the user's input operation on the device icon of the Honor children's watch in the user interface 220, and the first application can display Figure 2C The user interface 230 shown in the figure may be referred to as a control interface of the smart watch 200. The control interface of the smart watch 200 includes a plurality of options, such as a micro chat option, a video call option, a phone option, a watch management option, a watch address book option, a call log option, an alarm option, an album option, a pedometer option, and an application management option.

[0204] S404: The first application sends a request to establish a session connection to the connection networking server.

[0205] S405: The connection networking service end sends a session connection establishment request to the device server.

[0206] S406: The device server sends a session connection establishment request to the connection networking client.

[0207] S407: The connection networking client sends a confirmation to the second application to establish a session connection.

[0208] In response to the first application displaying the control interface of the smart watch 200, for example, the first application displays Figure 2C As shown in the user interface 230 , the electronic device 100 may actively send a request to establish a session connection to the smart watch 200 .

[0209] Optionally, as long as the first application displays the control interface of the smart watch 200, the first application will actively send a request to establish a session connection to the second application, so that the first application can send a message to the second application through the established session connection.

[0210] Optionally, after the first application stops displaying the control interface of the smart watch 200, for example, stops displaying Figure 2C After the user interface 230 is displayed, the session connection between the first application and the second application is disconnected.

[0211] Specifically, the first application needs to determine the cloud device ID of the smart watch 200 from the locally stored device information of the smart watch 200, for example. The first application can send a session connection establishment request to the connection networking server.

[0212] In one possible implementation, the cloud device ID of the smart watch 200 may be carried in the session connection request and sent to the connection network server. In other possible implementations, the cloud device ID of the smart watch 200 may also be sent to the connection network server independently of the session connection request. This application does not limit this.

[0213] Optionally, the first application also needs to confirm the cloud device ID of the electronic device 100 and send the cloud device ID of the electronic device 100 to the connection networking server. In one possible implementation, the cloud device ID of the electronic device 100 can be carried in the request to establish a session connection and sent to the connection networking server. In other possible implementations, the cloud device ID of the electronic device 100 can also be sent to the connection networking server independently of the request to establish a session connection. This application does not limit this.

[0214] In the embodiment of the present application, the cloud device ID of the smart watch 200 and the cloud device ID of the electronic device 100 are sent out independently of the request to establish a session connection.

[0215] The connection networking service end may send a session connection establishment request to the device server. After receiving the session connection establishment request, the device server may obtain the cloud device ID of the smart watch 200 and the cloud device ID of the electronic device 100. The device server may obtain the IP address or MAC address of the smart watch 200 based on the cloud device ID of the smart watch 200, and the device server may then send the session connection establishment request to the connection networking client in the smart watch 200 based on the IP address or MAC address of the smart watch 200.

[0216] After receiving the session connection establishment request sent by the connection networking service end in the electronic device 100, the device server then sends the session connection establishment request to the connection networking client in the smart watch 200. The connection networking client confirms the establishment of the session connection and sends the confirmation of the session connection establishment to the second application to inform the second application that the session connection has been established.

[0217] Optionally, in addition to sending a session connection establishment request to the connection networking client in the smart watch 200 , the device server also needs to send the cloud device ID of the electronic device 100 to the connection networking client in the smart watch 200 .

[0218] In one possible implementation, the cloud device ID of the electronic device 100 may be carried in the session connection request and sent to the connection networking client. In other possible implementations, the cloud device ID of the electronic device 100 may also be sent to the connection networking client independently of the session connection request. This application does not limit this.

[0219] S408: The connection networking client sends a confirmation to the device server to establish a session connection.

[0220] S409: The device server sends a confirmation to the connection networking server to establish a session connection.

[0221] S410: The connection networking server sends a confirmation to the first application to establish a session connection.

[0222] After the second application confirms to establish a session connection with the first application, the connection networking client may send a confirmation of establishing the session connection to the device server.

[0223] Optionally, in addition to sending confirmation of establishing the session connection to the device server, the connection networking client also needs to send the cloud device ID of the electronic device 100 to the device server.

[0224] In one possible implementation, the cloud device ID of the electronic device 100 may be carried in the confirmation of establishing a session connection and sent to the device server. In other possible implementations, the cloud device ID of the electronic device 100 may also be sent to the device server independently of the confirmation of establishing a session connection. This application does not limit this.

[0225] After receiving the session connection establishment message sent by the connection networking client, the device server can obtain the cloud device ID of the electronic device 100. After obtaining the cloud device ID of the electronic device 100, the device server can send a confirmation message to the connection networking service end in the electronic device 100 based on the IP address or MAC address of the electronic device 100.

[0226] The connection networking service end in the electronic device 100 then sends a confirmation of establishing the session connection to the first application in the electronic device 100 .

[0227] Optionally, the device server only needs to send confirmation of establishing a session connection to the connection networking server in the electronic device 100. The cloud device ID of the electronic device 100 may not be sent to the connection networking server in the electronic device 100. The cloud device ID of the electronic device 100 may also be sent to the connection networking server in the electronic device 100. This application does not limit this.

[0228] S411: The electronic device 100 and the smart watch 200 establish a session connection.

[0229] In some embodiments, the session between the electronic device 100 and the smart watch 200 may be referred to as a second session connection.

[0230] The second session connection is a data transmission channel between the electronic device 100 and the smart watch 200.

[0231] After the first application in the electronic device 100 receives the confirmation of establishing a session connection sent by the connection networking service end in the electronic device 100 , the electronic device 100 can establish a first session connection with the smart watch 200 .

[0232] After the electronic device 100 and the smart watch 200 establish the first session connection, the electronic device 100 and the smart watch 200 may send messages through the first session connection.

[0233] Optionally, as can be seen from S309, the electronic device 100 and the smart watch 200 have also negotiated to obtain a first key and a second key. When the electronic device 100 and the smart watch 200 send a message through a session connection, the electronic device 100 and the smart watch 200 can encrypt the data using the negotiated first key and second key and then send the data to the peer application through the session connection, thereby ensuring the reliability of data transmission.

[0234] 3. The electronic device 100 and the smart watch 200 establish an RTC call connection.

[0235] Figure 5 A schematic diagram of a method for the electronic device 100 and the smart watch 200 to successfully establish an RTC call connection is shown.

[0236] S501: The control interface of the smart watch 200 includes a first option, and a first application receives an input operation of a user for the first option.

[0237] The control interface of the smart watch 200 can be Figure 2C The user interface 230 shown. The first option may be a video call option in the user interface 230. The first application may receive an input operation of the user for the video call option in the user interface 230.

[0238] S502: In response to a user input operation, the first application displays a network call request interface.

[0239] In response to the user input operation for the video call option in the user interface 230, the first application displays a network call request interface. The network call request interface may be Figure 2D User interface 2310 is shown.

[0240] In response to the user's input operation on the video call option in the user interface 230 , the electronic device 100 may send a video call request to the smart watch 200 .

[0241] After the smart watch 200 receives the video call request, the electronic device 100 can establish a network video call with the smart watch 200 .

[0242] Optionally, the electronic device 100 may also establish an Internet voice call with the smart watch 200. Specifically, after the electronic device 100 receives the user's input operation for the video call option, the first application may prompt the user to initiate an Internet video call or an Internet voice call. After selecting an Internet voice call, the user may send a request to establish an Internet voice call to the smart watch 200. The user may also send a request to establish an Internet voice call to the smart watch 200 after selecting an Internet voice call. In other possible implementations, after the smart watch 200 receives the video call request, the electronic device 100 may establish an Internet video call with the smart watch 200. After the electronic device 100 and the smart watch 200 establish an Internet video call, the electronic device 100 may receive a user operation to switch the Internet video call to an Internet voice call.

[0243] S503: The first application sends a request to establish an RTC call to the RTC server.

[0244] In response to the first application receiving the user's input operation for the first option, the first application may send a request to establish an RTC call to the RTC server.

[0245] The RTC server is a server that establishes RTC calls between devices.

[0246] S504: The RTC server generates an account ID and an account password for the second RTC call.

[0247] In response to the RTC call request sent by the first application, the RTC call request can generate an account ID and an account password for the second RTC call.

[0248] The account ID and password for different RTC calls are different.

[0249] S505. The RTC server sends the account ID and account password of the second RTC call to the first application.

[0250] S506: The first application connects to the RTC server based on the account ID and account password of the second RTC call.

[0251] After the RTC server generates the account ID and account password of the second RTC call, the RTC server may send the account ID and account password of the second RTC call to the first application.

[0252] After the first application receives the account ID and account password of the second RTC call sent by the RTC server, the first application can connect to the RTC server based on the account ID and account password of the second RTC call. The first application can communicate with the RTC server.

[0253] S507 . The first application sends the account ID and password of the second RTC call, the device information of the electronic device 100 , and the device information of the smart watch 200 to the service server.

[0254] In some embodiments, the device server and the service server may communicate with each other. The device server and the service server may be the same server or different servers, which is not limited in this application.

[0255] The device information of the electronic device 100 may include but is not limited to information such as the device type of the electronic device 100 and the manufacturer of the electronic device 100.

[0256] The device information of the smart watch 200 may include but is not limited to the device type of the smart watch 200 , the manufacturer of the smart watch 200 , and other information.

[0257] S508. The business server needs to confirm whether the device information of the electronic device 100 and the smart watch 200 has been verified.

[0258] Optionally, the service server needs to confirm whether the manufacturers of the PTC calls supported by the service server include the manufacturer of the electronic device 100 and the manufacturer of the smart watch 200 .

[0259] Optionally, the service server also needs to confirm whether the device types of the PTC calls supported by the service server include the device type of the electronic device 100 and the device type of the smart watch 200 .

[0260] The business server can also confirm whether other device information of the electronic device 100 and other device information of the smart watch 200 have been verified, which is not limited in this application.

[0261] When the device information of the electronic device 100 and the smart watch 200 is successfully verified, S509 is executed.

[0262] If the device information verification of the electronic device 100 and the smart watch 200 fails, the process ends.

[0263] S509: The service server sends a request to establish an RTC call (account ID and account password for the second RTC call) to the device server.

[0264] S510: The device server may send a request to establish an RTC call (account ID and account password for the second RTC call) to the connection networking client.

[0265] S511. The connection networking client then sends a request to establish an RTC call (account ID and account password for the second RTC call) to the second application.

[0266] Optionally, when the business server confirms that the device information verification of the electronic device 100 and the smart watch 200 is passed, a request to establish an RTC call is sent to the business server device server. At the same time, the business server also needs to send the account ID and account password of the second RTC call to the device server.

[0267] The device server sends the RTC call establishment request, the account ID and account password of the second RTC call to the connection networking client.

[0268] The connection networking client then sends the RTC call establishment request, the account ID and account password of the second RTC call to the second application.

[0269] In one possible implementation, the account ID and account password of the second RTC call may be carried in the request to establish the RTC call and sent to the second application. In other possible implementations, the account ID and account password of the second RTC call may be sent to the second application independently of the request to establish the RTC call. This application does not limit this.

[0270] In other possible implementations, the first application only needs to send the device information of the electronic device 100 and the device information of the smart watch 200 to the business server, and the business server only needs to send the request to establish an RTC call to the second application. When the business server determines that the device information of the electronic device 100 and the smart watch 200 has been verified, the business server can send a verification pass notification to the electronic device 100. In response to the verification pass notification sent by the business server, the first application can send the account ID and account password of the second RTC call to the second application through the second session connection.

[0271] In other possible implementations, the first application only needs to send the device information of the electronic device 100 and the device information of the smart watch 200 to the business server, and the business server does not need to send the request to establish an RTC call to the second application. When the business server determines that the device information of the electronic device 100 and the smart watch 200 has been verified, the business server can send a verification pass notification to the electronic device 100. In response to the verification pass notification sent by the business server, the first application can send the request to establish an RTC call, the account ID and account password of the second RTC call to the second application through the second session connection.

[0272] Optionally, after receiving the request to establish an RTC call, the second application may send a successful reception message to the device server and the service server through the connection networking client to feedback to the service server that the second application has received the request to establish an RTC call.

[0273] S512: The second application prompts the user to answer the call.

[0274] After receiving the request to establish an RTC call, the account ID and the account password of the second RTC call, the second application can prompt the user to answer the call in response to the request to establish an RTC call.

[0275] Exemplarily, after receiving the request to establish an RTC call, the second application may display Figure 2E The user interface 240 shown. The user interface 240 is a network call waiting interface. The user interface 240 may include a hang-up control and an answer control. Among them, the user can refuse to establish a network video call with the electronic device 100 through the hang-up control. The user can also establish a network video call with the electronic device 100 through the answer control.

[0276] S513: The second application receives the user's call answering operation.

[0277] After the second application prompts the user to answer the call, the second application can receive the user's operation of answering the call.

[0278] For example, Figure 2E As shown, the smart watch 200 can receive the user's input operation (such as a single click) for the answering control in the user interface 240, and in response to the user's input operation, the electronic device 100 can display Figure 2F The user interface 250 is shown. The user interface 250 is an interface indicating that the network call has been answered. The user interface 250 may include a hang-up control, and the user can end the network video call with the electronic device 100 through the hang-up control.

[0279] S514: The second application connects to the RTC server based on the account ID and account password of the second RTC call.

[0280] In response to the operation of answering the call, the second application can connect to the RTC server based on the account ID and account password of the second RTC call. The first application can communicate with the RTC server.

[0281] S515. The second application sends a successful answer message to the first application through the second session connection.

[0282] After the second application is connected to the RTC server, the second application may notify the first application that the second application has been successfully connected to the RTC server.

[0283] The second application can send a successful answer message to the first application through the second session to inform the first application that the second application has successfully connected to the RTC server. The first application can switch to the network call answered interface to avoid the first application staying in the network call waiting interface.

[0284] In other embodiments, if both the second application and the first application are connected to the RTC server, the second application may also send a successful answer message to the first application through the RTC server, which is not limited in this application.

[0285] S516. In response to the successful answering message, the first application switches from the network call waiting interface to the network call answered interface.

[0286] In response to a successful answering message sent by the second application through the second session connection, the first application may switch from the network call waiting interface to the network call answered interface.

[0287] The network call answered interface can be Figure 2G User interface 260 is shown.

[0288] For example, the first application may display Figure 2GThe user interface 260 shown is an interface for answering a network call. The user interface 260 may include a hang-up option, a switch to a network voice call option, a switch to the front and rear cameras option, an option to turn off the camera of the electronic device 100, a mute option, a speaker option, and an option to reduce the user interface 260. Among them, the user can actively end the network video call with the smart watch 200 through the hang-up option. The user can also switch the network video call to the network voice call option by switching to the network voice call option, and the network voice call option cannot display the images captured by the cameras of both parties. The user can also switch the electronic device 100 from the front camera to the rear camera by switching the front and rear camera options, and display the image captured by the rear camera of the electronic device 100, and send the image captured by the rear camera of the electronic device 100 to the smart watch 200. The user can also stop the electronic device 100 from capturing images through the front camera by turning off the camera option of the electronic device 100, and stop displaying the image captured by the electronic device 100 through the front camera in the user interface 260, and also stop sending the image captured by the electronic device 100 through the front camera to the smart watch 200. The user can also use the mute option to turn off the microphone of the electronic device 100 and stop collecting audio through the microphone, and also stop sending the audio collected by the electronic device 100 through the microphone to the smart watch 200. The user can also use the speaker option to make the electronic device 100 play the audio sent by the smart watch 200 through the speaker. The user can also use the shrink user interface 260 option to shrink the user interface 260. After exiting the first application, the electronic device 100 can also suspend and display the shrunken user interface 260.

[0289] S517: The first application and the second application establish a second RTC call connection.

[0290] After the first application and the second application are connected to the RTC server based on the account ID and account password of the second RTC call, respectively, the first application and the second application can establish a second RTC call connection. The first application and the second application can transmit data to each other through the second RTC call connection. For example, the first application can send the audio or audio and image of the user of the electronic device 100 to the second application through the second RTC call connection, and the second application can display the audio or audio and image of the user of the electronic device 100. The second application can send the audio or audio and image of the user of the smart watch 200 to the first application through the second RTC call connection, and the first application can display the audio or audio and image of the user of the smart watch 200.

[0291] In some embodiments, if the smart watch 200 receives the request to establish the RTC call, but refuses to establish the RTC call, the smart watch 200 may send a message to the electronic device 100 through the second session connection to inform the electronic device 100 that the smart watch 200 has refused to establish the RTC call.

[0292] Figure 6 A schematic diagram of a method in which an electronic device 100 and a smart watch 200 fail to establish an RTC call connection is shown.

[0293] for Figure 6 For the description of S601-S612 in the embodiment, please refer to Figure 5 The description of S501-S512 in the embodiment will not be repeated in this application.

[0294] S613: The second application receives an operation from the user to reject the call.

[0295] like Figure 2H As shown, after the smart watch 200 receives the request to establish an RTC call, the smart watch 200 can display Figure 2E User interface 240 is shown.

[0296] When the user of the smart watch 200 refuses to establish the RTC call, the smart watch 200 may receive an input operation (eg, a single click) from the user for the hang-up control in the user interface 240 , and in response to the input operation from the user, the smart watch 200 may stop displaying the user interface 240 .

[0297] S614: The second application sends a call rejection message to the first application through the second session connection.

[0298] S615. In response to the call rejection message, the first application switches from the network call request interface to the call rejection interface.

[0299] After the smart watch 200 receives the user's input operation on the hang-up control in the user interface 240 , the smart watch 200 may send a call rejection message to the electronic device 100 to inform the electronic device 100 that the smart watch 200 has rejected the network video call with the electronic device 100 .

[0300] The reject call interface can be Fig.2I User interface 270 is shown.

[0301] After receiving the message sent by the smart watch 200, the electronic device 100 can display Fig.2IThe user interface 270 shown in the figure shows a prompt message “The watch has rejected your video call request” in the user interface 270. The prompt message is used to prompt the user of the electronic device 100 that the user of the smart watch 200 rejects the establishment of a network video call.

[0302] After the electronic device 100 displays the reject call interface, the electronic device 100 may continue to display Figure 2C User interface 230 is shown.

[0303] In some embodiments, if the user of the smart watch 200 does not see the RTC call request in time after the smart watch 200 receives the RTC call establishment request, and the electronic device 100 does not receive a response message (such as a call rejection message, a call answering message, or a busy line message, etc.) sent by the smart watch 200 within the first time period, the electronic device 100 may prompt the user that the other party has paused and cannot answer the call.

[0304] Figure 7 Another schematic diagram of a method in which an RTC call connection is not established between the electronic device 100 and the smart watch 200 is shown.

[0305] for Figure 7 For the description of S701-S712 in the embodiment, please refer to Figure 5 The description of S501-S512 in the embodiment will not be repeated in this application.

[0306] S713: If no response message is received within the first time period, the first application switches from the network call request interface to the no answer interface.

[0307] Optionally, the no answer interface can be Figure 2K User interface 290 is shown.

[0308] After the electronic device 100 sends the network video call request to the smart watch 200, if the electronic device 100 does not receive a feedback message sent by the smart watch 200 within the first time period, such as a message accepting the network video call request or a message rejecting the network video call request or a busy line message, the electronic device 100 may stop sending the network video call request to the smart watch 200 and display a Figure 2K The user interface 290 shown. The user interface 290 shows a prompt message "No one answered the watch, please try again later." The prompt message is used to prompt the user of the electronic device 100 that the smart watch 200 has no response.

[0309] The electronic device 100 displays Figure 2K After the user interface 290 shown, the electronic device 100 may continue to display Figure 2C User interface 230 is shown.

[0310] S714: If no one answers the call after the first time period, the second application stops prompting the user to answer the call.

[0311] Similarly, if the smart watch 200 does not receive any user operation within the first time period, the second application in the smart watch 200 may stop prompting the user to answer the call. For example, the second application may stop displaying Figure 2E User interface 240 is shown.

[0312] Optionally, S713 and S714 may be executed simultaneously, or S714 may be executed before S713, or S714 may be executed after S713, which is not limited in the present application.

[0313] In some embodiments, if the smart watch 200 is establishing an RTC call request with another device after receiving the request to establish an RTC call, if the smart watch 200 can only establish an RTC call connection with one device at the same time, the smart watch 200 can send a message to the electronic device 100, which is used to indicate to the electronic device 100 that the smart watch 200 is conducting an RTC call with other devices.

[0314] In other embodiments, the smart watch 200 may also establish RTC calls with multiple devices at the same time, which is not limited in this application.

[0315] Figure 8 A schematic diagram of another method in which the electronic device 100 and the smart watch 200 do not establish an RTC call connection is shown.

[0316] for Figure 8 For the description of S801-S811 in the embodiment, please refer to Figure 5 The description of S501-S511 in the embodiment will not be repeated in this application.

[0317] S812: The second application sends a busy message to the first application through the second session connection.

[0318] When the second application in the smart watch 200 is conducting an RTC call with another device, the second application in the smart watch 200 receives a request to establish an RTC call sent by the other device. In the case that the smart watch 200 can only establish an RTC call connection with one device at the same time, the smart watch 200 can send a message to the electronic device 100, which is used to indicate to the electronic device 100 that the smart watch 200 is conducting an RTC call with another device.

[0319] S813. In response to the busy line message, the first application switches from the network call request interface to the busy line interface.

[0320] Optionally, the busy line interface can be Figure 2J The user interface 280 is shown.

[0321] After the first application in the electronic device 100 receives the busy line message sent by the second application in the smart watch 200 through the second session connection, the electronic device 100 can display Figure 2J The user interface 280 is shown, and the user interface 280 shows the prompt information "Watch is busy". The prompt information is used to prompt the user of the electronic device 100 and the user of the smart watch 200 that the smart watch 200 is making an Internet video call or an Internet voice call with other devices.

[0322] The smart watch 200 calls the electronic device 100 .

[0323] First, the UI implementation of the electronic device 100 calling the smart watch 200 is introduced.

[0324] Figure 9A-9K A UI schematic diagram of the smart watch 200 calling the electronic device 100 is shown.

[0325] Optionally, the smart watch 200 can call the electronic device 100 in the second application.

[0326] Fig. 9A The user interface 910 of the second application in the smart watch 200 is shown. The user interface 910 includes a WeChat chat option and a call option. Among them, the user can send information to other devices through the WeChat chat option. The user can also make an Internet call to other devices through the call option.

[0327] For example, Fig. 9A As shown, the smart watch 200 can receive an input operation (such as a single click) from a user for a call option in the user interface 910. In response to the input operation from the user, the smart watch 200 can display Fig. 9B The user interface 920 shown in FIG. 9 may include a hang-up control, and the user interface 920 may also be a network call request interface. The user may stop sending a network call request through the hang-up control.

[0328] The network call request may be a network video call, or a network voice call.

[0329] Optionally, after the smart watch 200 receives the user's input operation for the call option in the user interface 910, the second application can prompt the user to select whether to establish an Internet video call or an Internet voice call.

[0330] It should be noted that, due to the limited memory control of the smart watch 200, the device information of other devices (or the networking information of other devices) will not be stored in the smart watch 200. Therefore, the smart watch 200 cannot choose which device to send the network call request to. Therefore, after the smart watch 200 sends the request to establish a network call, other devices associated with the same account as the smart watch 200, or other devices that are not associated with the same account as the smart watch 200 but have established an association relationship between different user accounts, can all receive the request to establish a network call sent by the smart watch 200.

[0331] The smart watch 200 receives a user operation to initiate a request to establish a network call.

[0332] Exemplarily, if the electronic device 100 and the electronic device 300 are both logged into the same user account as the smart watch 200, the electronic device 100 and the electronic device 300 can both receive the network call establishment request sent by the smart watch 200.

[0333] For example, if the user accounts logged in to electronic device 100 and electronic device 300 are different from those of smart watch 200, but the user accounts logged in to electronic device 100 and electronic device 300 have established an association with the user account logged in to smart watch 200, then electronic device 100 and electronic device 300 can both receive the request to establish a network call sent by smart watch 200.

[0334] For example, Fig. 9C As shown, after receiving the network call establishment request sent by the smart watch 200, the electronic device 100 can display Fig. 9C The user interface 930 shown may be a network call waiting interface. The user interface 930 includes a hang-up option and an answer option. The user may refuse to establish a network call connection with the smart watch 200 through the hang-up option. The user may also establish a network call connection with the smart watch 200 through the answer option.

[0335] For example, similarly, Fig.9D As shown, after the electronic device 300 receives the network call establishment request sent by the smart watch 200, the electronic device 100 can display Fig.9D The user interface 940 shown is similar to the user interface 930 and will not be described in detail in this application.

[0336] If the user of the electronic device 100 agrees to establish a network call connection with the smart watch 200, the electronic device 300 cannot establish a network call connection with the smart watch 200. If the user of the electronic device 300 agrees to establish a network call connection with the smart watch 200, the electronic device 100 cannot establish a network call connection with the smart watch 200.

[0337] The following embodiments of the present application are described by taking the establishment of a network call connection between the electronic device 100 and the smart watch 200 as an example.

[0338] Optionally, after the electronic device 100 receives the request to establish a network call connection sent by the smart watch 200, if the electronic device 100 does not open the first application, or the first application is opened but running in the background, then the electronic device 100 can display the incoming call notification in the drop-down notification bar.

[0339] For example, Fig.9E As shown, after receiving the network call connection request sent by the smart watch 200, the electronic device 100 can display a prompt message 990 in the pull-down notification bar, and the prompt message 990 is used to remind the user that there is a new incoming call reminder. The electronic device 100 can receive the user's input operation (such as a single click) for the prompt message 990, and in response to the user's input operation, the electronic device 100 can display Fig. 9C User interface 930 is shown.

[0340] For example, Fig.9F As shown, the electronic device 100 may receive an input operation (eg, a single click) from a user for an answering option in the user interface 930. In response to the input operation from the user, the electronic device 100 may display Figure 9G The user interface 950 shown may be a network call answering interface. The user interface 950 is similar to the user interface 260 , and reference may be made to the description of the user interface 260 , which will not be repeated herein.

[0341] For example, Figure 9H As shown, after the electronic device 100 establishes a network call connection with the smart watch 200, the smart watch 200 may also switch to display Figure 9H The user interface 960 shown is similar to the user interface 250 , and reference may be made to the description of the user interface 250 , which will not be repeated herein.

[0342] After the smart watch 200 establishes a network call connection with the electronic device 100, the smart watch 200 may send a message to the electronic device 300, where the message is used to inform the electronic device 300 that the smart watch 200 has established a network call connection with the electronic device 100 and instruct the electronic device 300 to stop displaying the user interface 940.

[0343] In some embodiments, after the smart watch 200 sends a message to the electronic device 100 and the electronic device 300 to establish a network call connection, if the smart watch 200 does not receive a feedback message (such as a call answering message or a call rejection message) sent by the electronic device 100 and the electronic device 300 within a first time period, the smart watch 200 may display Fig.9I The prompt message displayed is “The other party is not online, please try again later”, which reminds the user that a network call connection cannot be established with other devices at present.

[0344] In some embodiments, after the smart watch 200 sends a message to the electronic device 100 and the electronic device 300 to establish a network call connection, if both the electronic device 100 and the electronic device 300 reject the call, the smart watch 200 may display Figure 9J The prompt message "The other party has rejected your video call request" is shown to prompt the user that the electronic device 100 and the electronic device 300 have rejected the network call connection. Optionally, if the electronic device 100 rejects the call but the electronic device 300 has not rejected the call, or the electronic device 300 rejects the call but the electronic device 100 has not rejected the call, the smart watch 200 may not display Figure 9J Only after both the electronic device 100 and the electronic device 300 reject the call, the smart watch 200 will display the prompt message. Figure 9J The prompt information shown.

[0345] In some embodiments, after the smart watch 200 sends a message to establish a network call connection to the electronic device 100 and the electronic device 300, if both the electronic device 100 and the electronic device 300 have established a network call connection with other devices, the smart watch 200 may display Figure 9K The prompt message “The other party is busy” is shown to remind the user that the electronic device 100 and the electronic device 300 have established a network call connection with other devices.

[0346] Next, the specific implementation of the smart watch 200 calling the electronic device 100 is introduced.

[0347] The storage space of the smart watch 200 is limited and cannot store the networking information of other devices. Therefore, the smart watch 200 cannot actively initiate a session connection with other devices. However, the smart watch 200 can request the electronic device 100 to actively establish a session connection.

[0348] In the scenario where the smart watch 200 calls the electronic device 100, a long connection can be established with the electronic device 100 through the push server. When the smart watch 200 needs to call the electronic device 100, the smart watch 200 can send an RTC call establishment request to the electronic device 100 through the push server, so that the electronic device 100 can receive the RTC call establishment request sent by the smart watch 200.

[0349] The smart watch 200 calling the electronic device 100 includes the following stages: the smart watch 200 sends an RTC call establishment request to a device with the same account or a different account and an associated relationship through a push server, the smart watch 200 and the electronic device 100 establish a trusted relationship and establish a first session connection, and the smart watch 200 and the electronic device 100 establish an RTC call connection.

[0350] Fig.10 The diagram shows a method in which the smart watch 200 sends an RTC call establishment request to a device with the same account or a different account and an associated relationship through a push server.

[0351] like Fig.10 As shown, a first user account is logged in to the smart watch 200, a second user account is logged in to the electronic device 100, and a third user account is logged in to the electronic device 300. The first user account, the second user account and the third user account are the same. Alternatively, the first user account, the second user account and the third user account are different, but an association relationship is established between the first user account, the second user account and the third user account, for example, the user accounts of different family members in a family are associated with each other.

[0352] S1001. The push server and the electronic device 100 establish a long connection.

[0353] S1002. The push server and the electronic device 300 establish a long connection.

[0354] The push server can establish a long connection with the electronic device 100 and the electronic device 300 respectively, so that the electronic device 100 and the electronic device 300 can receive the RTC call establishment request sent by the smart watch 200 through the push server.

[0355] S1003: The second application in the smart watch 200 receives a user operation of initiating an RTC call.

[0356] For example, the smart watch 200 may display Fig. 9AThe user interface 910 of the second application shown. The user interface 910 includes a WeChat chat option and a call option. Among them, the user can send a message to other devices through the WeChat chat option. The user can also make an Internet call to other devices through the call option.

[0357] For example, Fig. 9A As shown, the smart watch 200 can receive an input operation (such as a single click) from a user for a call option in the user interface 910. In response to the input operation from the user, the smart watch 200 can display Fig. 9B The user interface 920 shown in FIG. 9 may include a hang-up control, and the user interface 920 may also be a network call request interface. The user may stop sending a network call request through the hang-up control.

[0358] The user operation to initiate an RTC call can be Fig. 9A The user input operation for the call making option in the user interface 910 is shown.

[0359] S1004. The second application in the smart watch 200 sends a request to establish an RTC call to the service server.

[0360] S1005: The service server sends a request to establish an RTC call to the push server.

[0361] After the second application in the smart watch 200 receives the user operation of initiating an RTC call, the second application can send a request to establish an RTC call to the service server, and the service server then sends the request to establish an RTC call to the push server.

[0362] Optionally, the second application also needs to send the account information of the first user account logged in on the smart watch 200 to the push server through the business server.

[0363] In one possible implementation, the account information of the first user account may be carried in the RTC call establishment request and sent to the push server. In other possible implementations, the account information of the first user account may also be sent to the push server independently, which is not limited in this application.

[0364] S1006 . The push server sends a request to establish an RTC call to the first application in the electronic device 100 .

[0365] S1007 . The push server sends a request to establish an RTC call to the third application in the electronic device 300 .

[0366] After the push server receives the RTC call establishment request sent by the second application in the smart watch 200 through the service server, the push server can also obtain the account information of the first user account.

[0367] Exemplarily, the account information of the first user account may be an account ID of the first user account.

[0368] The push server stores the association relationship between user accounts. The push server can determine other user accounts associated with the first user account based on the account ID of the first user account. The push server can also determine other devices logged in with the first user account based on the account ID of the first user account.

[0369] For example, the push server determines, based on the account ID of the first user account, that the other devices logged in with the first user account may be the electronic device 100 and the electronic device 300 .

[0370] For another example, the push server determines based on the account ID of the first user account that other user accounts associated with the first user account may be the second user account and the third user account, the device logged in with the second user account may be the electronic device 100, and the device logged in with the third user account may be the electronic device 300.

[0371] After determining the electronic device 100 and the electronic device 300, the push server can send a request to establish an RTC call to the electronic device 100 and the electronic device 300 respectively. Specifically, the push server can send a request to establish an RTC call to the connection networking service end in the electronic device 100 through a long connection, and the connection networking service end in the electronic device 100 then sends the request to establish an RTC call to the first application in the electronic device 100. The push server can send a request to establish an RTC call to the connection networking service end in the electronic device 300 through a long connection, and the connection networking service end in the electronic device 300 then sends the request to establish an RTC call to the third application in the electronic device 300.

[0372] The third application may be an application that is the same as or similar to the first application.

[0373] S1008. In response to establishing the RTC call request, the first application displays a network call request interface.

[0374] S1009. In response to establishing the RTC call request, the third application displays a network call request interface.

[0375] After receiving the request to establish an RTC call, the first application in the electronic device 100 can display a network call request interface in response to the request to establish an RTC call, thereby prompting the user of the electronic device 100 that the electronic device 100 has received the request to establish an RTC call sent by the smart watch 200.

[0376] Exemplarily, the network call request interface displayed by the first application may be Fig. 9C The user interface 930 shown. The user interface 930 includes a hang-up option and an answering option. The user can refuse to establish a network call connection with the smart watch 200 through the hang-up option. The user can also establish a network call connection with the smart watch 200 through the answering option.

[0377] Similarly, after receiving the request to establish an RTC call, the third application in the electronic device 300 can display a network call request interface in response to the request to establish an RTC call, thereby prompting the user of the electronic device 300 that the electronic device 300 has received the request to establish an RTC call sent by the smart watch 200.

[0378] Exemplarily, the network call request interface displayed by the third application may be Fig.9D User interface 940 is shown. User interface 940 is similar to user interface 930.

[0379] After the first application in the electronic device 100 displays the network call request interface, and the third application in the electronic device 300 displays the network call request interface, the electronic device 100 or the electronic device 300 can establish a network call with the smart watch 200.

[0380] The following embodiments of the present application are described by taking the electronic device 100 and the smart watch 200 establishing a network call as an example.

[0381] S1010: The first application receives an operation of a user answering a call.

[0382] S1011. The first application sends a message indicating that the electronic device 100 has answered the call to the push server through a long connection.

[0383] S1012. The push server sends a message to stop displaying the network call request interface to the third application in the electronic device 300 through a long connection.

[0384] S1013. The third application stops displaying the network call request interface.

[0385] After receiving the request to establish an RTC call, the first application in the electronic device 100 can display a network call request interface in response to the request to establish an RTC call, and the first application can receive a user's call.

[0386] Exemplarily, the electronic device 100 may receive a user input operation (eg, a single click) for an answer option in the user interface 930. In response to the user input operation, the first application may send a message through the push server indicating that the electronic device 100 has answered the call.

[0387] After receiving the message from electronic device 100 indicating that electronic device 100 has answered the call, the push server may send a message to stop displaying the network call request interface to the third application in electronic device 300 through a persistent connection to instruct electronic device 300 to stop displaying the network call request interface.

[0388] After the third application in the electronic device 300 receives the message of stopping displaying the network call request interface sent by the push server, the third application can stop displaying the network call request interface, that is, the third application can stop displaying the network call request interface. Fig.9D User interface 940 is shown.

[0389] Fig.11 A schematic diagram of a method for establishing an RTC call between a smart watch 200 and an electronic device 100 is shown.

[0390] S1101 : The electronic device 100 and the smart watch 200 establish a trusted relationship.

[0391] For the specific implementation of establishing a trusted relationship between the electronic device 100 and the smart watch 200, please refer to Figure 3 The description in the embodiments will not be repeated in this application.

[0392] S1102: The electronic device 100 and the smart watch 200 establish a first session connection.

[0393] Since the smart watch 200 does not store the networking information of other devices, the smart watch 200 cannot actively initiate the establishment of a session connection to the electronic device 100. The smart watch 200 can instruct the electronic device 100 to actively initiate the establishment of a session connection through the push server. The electronic device 100 can actively request the smart watch 200 to establish a session connection and establish a first session connection.

[0394] The specific implementation of the electronic device 100 and the smart watch 200 establishing the first session connection can be referred to Figure 4 The description in the embodiments will not be repeated in this application.

[0395] S1103. The first application in the electronic device 100 sends a request to establish an RTC call to the RTC server.

[0396] S1104. The RTC server generates an account ID and an account password for the first RTC call.

[0397] S1105. The RTC server sends the account ID and account password of the first RTC call to the first application.

[0398] S1106. The first application in the electronic device 100 connects to the RTC server based on the account ID and account password of the first RTC call.

[0399] S1107 . The first application in the electronic device 100 sends the account ID and password of the first RTC call, the device information of the electronic device 100 , and the device information of the smart watch 200 to the service server.

[0400] S1108. The business server needs to confirm whether the device information of the electronic device 100 and the smart watch 200 has been verified.

[0401] When the device information of the electronic device 100 and the smart watch 200 is successfully verified, S1109 is executed.

[0402] If the device information verification of the electronic device 100 and the smart watch 200 fails, the process ends.

[0403] S1109. The service server sends a request to establish an RTC call (account ID and account password for the first RTC call) to the device server.

[0404] S1110. The device server may send a request to establish an RTC call (account ID and account password of the first RTC call) to the connection networking client.

[0405] S1111. The connection networking client then sends a request to establish an RTC call (account ID and account password for the first RTC call) to the second application in the smart watch 200.

[0406] For the description of S1103-S1111, please refer to Figure 5 The description of S503-S511 in the embodiment will not be repeated in this application.

[0407] S1112. The second application connects to the RTC server based on the account ID and account password of the first RTC call.

[0408] After the second application receives the account ID and account password of the first RTC call, the second application can connect to the RTC server based on the account ID and account password of the first RTC call.

[0409] The first application also connects to the RTC server based on the account ID and account password of the first RTC call.

[0410] The electronic device 100 and the smart watch 200 have established a first RTC call connection. The electronic device 100 and the smart watch 200 can send messages to each other through the first RTC call.

[0411] S1113. In response to connecting to the RTC server, the second application switches from the network call request interface to the call in progress interface.

[0412] After the electronic device 100 and the smart watch 200 establish the first RTC call connection, the second application can switch to the call in progress interface to prompt the user that the network call between the smart watch 200 and the electronic device 100 has been connected.

[0413] For example, the call in progress interface can be Figure 9H User interface 960 is shown.

[0414] S1114. The connection networking client in the smart watch 200 sends a message to the push server indicating that the smart watch 200 has been connected to the RTC server.

[0415] S1115. The push server sends a message to the connection networking service end in the electronic device 100 that the smart watch 200 has been connected to the RTC server.

[0416] S1116. The connection networking service end in the electronic device 100 sends a message to the first application in the electronic device 100 indicating that the smart watch 200 has been connected to the RTC server.

[0417] S1117 . In response to the message that the smart watch 200 has been connected to the RTC server, the call waiting interface is switched to the call in progress interface.

[0418] After the second application is connected to the RTC server, the connection networking client in the smart watch 200 can send a message to the push server through a long connection, indicating that the smart watch 200 has been connected to the RTC server.

[0419] The push server then sends a message to the connection networking service end in the electronic device 100 that the smart watch 200 has been connected to the RTC server.

[0420] The connection networking service end in the electronic device 100 then sends the message that the smart watch 200 has been connected to the RTC server to the first application in the electronic device 100 through a long connection.

[0421] After the first application in the electronic device 100 receives the message that the smart watch 200 has connected to the RTC server, the electronic device 100 can switch from the call waiting interface to the call in progress interface to prompt the user that the network call between the smart watch 200 and the electronic device 100 has been connected.

[0422] For example, the call in progress interface can be Figure 9G User interface 950 is shown.

[0423] In other embodiments, the electronic device 100 and the smart watch 200 have established a first session connection. The smart watch 200 may also send a message to the electronic device 100 through the first session connection indicating that the smart watch 200 has been connected to the RTC server.

[0424] Optionally, after the smart watch 200 and the electronic device 100 establish an RTC call, the smart watch 200 or the electronic device 100 needs to inform the electronic device 300 so that the electronic device 300 can stop displaying the network call request interface. Specifically, the smart watch 200 can instruct the electronic device 300 to stop displaying the network call request interface through the first session connection or the push server, or the electronic device 300 can instruct the electronic device 300 to stop displaying the network call request interface through the push server.

[0425] In some embodiments, if the electronic device 100 receives the request to establish the RTC call, but the electronic device 100 refuses to establish the RTC call, the electronic device 100 may send a message to the smart watch 200 through the first session connection to inform the smart watch 200 that the electronic device 100 has refused to establish the RTC call.

[0426] Fig.12 A schematic diagram of a method in which a smart watch 200 and an electronic device 100 fail to establish an RTC call connection is shown.

[0427] S1201. In response to establishing an RTC call request, the first application displays a network call request interface.

[0428] S1202: In response to establishing the RTC call request, the third application displays a network call request interface.

[0429] refer to Fig.10 In the description of S1008 and S1009 in the embodiment, after the electronic device 100 receives the RTC call establishment request sent by the smart watch 200, the first application can display the network call request interface. Similarly, after the electronic device 300 receives the RTC call establishment request sent by the smart watch 200, the third application can display the network call request interface.

[0430] S1203: The first application receives an operation from the user to reject the call.

[0431] After the first application displays the network call request interface, for example, the first application can display Fig. 9C User interface 930 is shown.

[0432] When the user of the electronic device 100 refuses to establish the RTC call, the smart watch 200 can receive the user's input operation (such as a single click) for the hang-up control in the user interface 930, and in response to the user's input operation, the electronic device 100 can stop displaying the user interface 930.

[0433] Optionally, after the first application receives the user's operation of rejecting the call, the first application can stop displaying the network call request interface.

[0434] S1204: The electronic device 100 establishes a first session connection with the smart watch 200.

[0435] The electronic device 100 stores the device information of the smart watch 200 (or the networking information of the smart watch 200). The electronic device 100 can initiate a session connection to the smart watch 200 based on the networking information of the electronic device 100. After the smart watch 200 agrees, the electronic device 100 can establish a first session connection with the smart watch 200. For the specific implementation of establishing the first session connection between the electronic device 100 and the smart watch 200, please refer to Figure 4 The description in the embodiments will not be repeated in this application.

[0436] In some embodiments, the push server cannot send the message to the smart watch 200, and a first session connection can be established between the electronic device 100 and the smart watch 200. The electronic device 100 can send a message to the smart watch 200 through the first session connection, for example, sending a call rejection message to the smart watch 200 through the first session connection to inform the smart watch 200 that the electronic device 100 has rejected the call.

[0437] S1205. The connection networking server in the electronic device 100 sends a call rejection notification to the connection networking client on the smart watch 200 through the first session connection.

[0438] S1206 . The connection networking client on the smart watch 200 sends a call rejection notification to the second application on the smart watch 200 .

[0439] S1207. In response to the call rejection notification, the second application switches from the network call request interface to the call rejection interface.

[0440] After receiving the call rejection notification, the second application may switch from the network call request interface to the call rejection interface.

[0441] For example, the second application may be Fig. 9B The user interface 920 shown switches to display Figure 9J The user interface shown. Figure 9J The user interface shown shows a prompt message “The other party has rejected your video call request.” The prompt message is used to prompt the user of the smart watch 200 that the user of the electronic device 100 has rejected the establishment of a network video call.

[0442] After the smart watch 200 displays the call rejection interface, the smart watch 200 may continue to display Fig. 9A User interface 910 is shown.

[0443] S1208. The connection networking service end in the electronic device 100 sends a call rejection message to the push server.

[0444] S1209 . The push server sends a call rejection message to the connection networking service end in the electronic device 300 .

[0445] S1210. The connection networking service end in the electronic device 300 sends a call rejection message to the third application in the electronic device 300.

[0446] S1211. In response to the call rejection message, the third application stops displaying the network call request interface.

[0447] Optionally, S1208 - S1211 may be executed after S1203 .

[0448] After the user of the electronic device 100 rejects the call, the electronic device 100 can send a reject call message to the electronic device 300 through the push server, so that the electronic device 300 can stop displaying the network call request interface. Specifically, the connection networking service end in the electronic device 100 can send a reject call message to the push server, and the push server then sends the reject call message to the connection networking service end in the electronic device 300, and the connection networking service end in the electronic device 300 then sends the reject call message to the third application in the electronic device 300. In response to the reject call message, the third application stops displaying the network call request interface, and the third application can stop displaying Fig.9D User interface 940 is shown.

[0449] In some embodiments, if the electronic device 100 receives a request to establish an RTC call, and the smart watch 200 is establishing an RTC call request with another device, if the electronic device 100 can only establish an RTC call connection with one device at the same time, the electronic device 100 can send a message to the smart watch 200, which is used to indicate to the smart watch 200 that the electronic device 100 is conducting an RTC call with another device.

[0450] In other embodiments, the electronic device 100 may also establish RTC calls with multiple devices at the same time, which is not limited in this application.

[0451] Fig.13 Another schematic diagram of a method in which a smart watch 200 and an electronic device 100 do not establish an RTC call connection is shown.

[0452] S1301. The connection networking service end in the electronic device 100 sends a busy message to the push server.

[0453] S1302 . The push server sends a busy message to the connection networking service end in the electronic device 300 .

[0454] S1303: The connection networking service end in the electronic device 300 sends a busy message to the third application in the electronic device 300.

[0455] S1304: In response to the busy message, the third application does not display the network call request interface.

[0456] refer to Fig.10 In the description of S1008 and S1009 in the embodiment, after the electronic device 100 and the electronic device 300 receive the RTC call establishment request sent by the smart watch 200, if the electronic device 100 is busy, for example, the electronic device 100 is making a network call with another electronic device. The electronic device 100 may not display the busy message. At the same time, the electronic device 100 may send a busy message to the third application in the electronic device 300 through the push server, so that the third application does not display the network call request interface.

[0457] S1305: The electronic device 100 and the smart watch 200 establish a first session connection.

[0458] S1306. The connection networking service end in the electronic device 100 sends a busy line message to the connection networking service end in the smart watch 200 through the first session connection.

[0459] S1307. The connection networking service end in the smart watch 200 sends a busy line message to the second application in the smart watch 200.

[0460] S1308. The second application switches from the network call request interface to the busy line interface.

[0461] When the first application in the electronic device 100 is conducting an RTC call with another device, the electronic device 100 receives an RTC call establishment request sent by the smart watch 200. In the case that the electronic device 100 can only establish an RTC call connection with one device at the same time, the electronic device 100 can send a busy message to the smart watch 200, and the busy message is used to indicate to the smart watch 200 that the electronic device 100 is conducting an RTC call with another device.

[0462] In response to the busy line message, the second application may switch from the network call request interface to the busy line interface.

[0463] Optionally, the busy line interface can be Figure 9K The user interface displayed.

[0464] After the second application in the smart watch 200 receives the busy line message sent by the first application in the electronic device 100 through the first session connection, the smart watch 200 can display Figure 9K The user interface shown, Figure 9K The user interface shown shows a prompt message "The other party is busy". The prompt message is used to prompt the user of the smart watch 200 that the electronic device 100 is making an Internet video call or an Internet voice call with another device.

[0465] In some embodiments, if the user of the electronic device 100 does not see the RTC call request in time after the electronic device 100 receives the RTC call establishment request, and the smart watch 200 does not receive a response message (such as a call rejection message, a call answering message, or a busy line message, etc.) sent by the electronic device 100 within the first time period, the smart watch 200 may prompt the user that the other party has paused and cannot answer the call.

[0466] Fig.14 A schematic diagram of another method in which the smart watch 200 and the electronic device 100 do not establish an RTC call connection is shown.

[0467] S1401. In response to establishing an RTC call request, display a network call request interface.

[0468] S1402: In response to establishing the RTC call request, display a network call request interface.

[0469] refer to Fig.10In the description of S1008 and S1009 in the embodiment, after the electronic device 100 receives the RTC call establishment request sent by the smart watch 200, the first application can display the network call request interface. Similarly, after the electronic device 300 receives the RTC call establishment request sent by the smart watch 200, the third application can display the network call request interface.

[0470] S1403: If no one answers the call after a first time period, the first application stops prompting the user to answer the call.

[0471] S1404: If no one answers the call after the first time period, the third application stops prompting the user to answer the call.

[0472] S1405: If no response message is received within the first time period, the second application switches from the network call request interface to the no answer interface.

[0473] After the smart watch 200 sends the network video call request to the electronic device 100 and the electronic device 300, if the smart watch 200 does not receive a feedback message sent by the electronic device 100 and the electronic device 300 within the first time period, such as not receiving a message accepting the network video call request or a message rejecting the network video call request or a busy line message, the smart watch 200 may stop sending the network video call request to the electronic device 100 and the electronic device 300, and display Figure 9K The user interface shown. Figure 9K The user interface shown shows a prompt message "the other party is busy".

[0474] Display on smartwatch 200 Figure 9K After the user interface shown, the smart watch 200 may continue to display Fig. 9A User interface 910 is shown.

[0475] Similarly, if the electronic device 100 does not receive any user operation within the first time period, the first application in the electronic device 100 may stop prompting the user to answer the call. Fig. 9C User interface 930 is shown.

[0476] Similarly, if the electronic device 300 does not receive any user operation within the first time period, the third application in the electronic device 300 may stop prompting the user to answer the call. For example, the third application may stop displaying Fig.9D User interface 940 is shown.

[0477] Optionally, S1403, S1404 and S1405 may be executed simultaneously, and the present application does not limit the execution order of S1403, S1404 and S1405.

[0478] Fig.15A schematic flow chart of a method for communication between devices provided in this application.

[0479] S1501. A first electronic device is configured to receive and respond to a first user operation and send a first request to a first server, wherein the first request carries an account ID of the first user account.

[0480] Exemplarily, the first electronic device may be a smart watch 200, and the first server may be a push server.

[0481] The first user operation may be for Fig. 9A Input operation for the Make a Phone Call option in .

[0482] The first request can be Fig.10 The RTC call request is established in S1004 in the embodiment.

[0483] In the embodiment of the present application, the first electronic device may be a device that supports a SIM card slot or supports an ESIM, or the first electronic device may be a device that does not support a SIM card slot or supports an ESIM. In other words, devices that support a SIM card slot or support an ESIM may be applicable to the present application.

[0484] In some embodiments, the first electronic device may be a children's watch, the second electronic device may be a family member of the user of the first electronic device, the first electronic device and the second electronic device may log in to the same user account, or log in to different user accounts but establish a binding relationship.

[0485] S1502: The first server is configured to determine, in response to the first request, a second electronic device logged in with a second user account based on the account ID of the first user account.

[0486] Exemplarily, the second electronic device may be the electronic device 100 .

[0487] S1503: The first server is further configured to send a request to establish a network call to the second electronic device.

[0488] Exemplarily, a request to establish a network call may be Fig.10 The RTC call request is established in S1006 in the embodiment.

[0489] S1504. The second electronic device is configured to display a first user interface in response to a request to establish a network call, wherein the first user interface displays a first answering control and a first hang-up control.

[0490] Exemplarily, the first user interface may be Fig. 9CThe user interface 930 shown. The first answer control may be the answer option shown in the user interface 930, and the first hang-up control may be the hang-up option shown in the user interface 930.

[0491] S1505. The second electronic device is further configured to receive an operation of the user on the first answering control and send a second request to the second server.

[0492] Exemplarily, the second server may be an RTC server.

[0493] Exemplarily, the user's operation on the first answering control may be an input operation on an answering option in the user interface 930 .

[0494] Exemplarily, the second request may be Fig.11 The RTC call request is established as shown in S1103 in the embodiment.

[0495] S1506. The second server is used to generate an account ID and an account password for the first network call in response to the second request.

[0496] Exemplarily, the second server generates the account ID and account password for the first network call, which can be Fig.11 The account ID and account password of a network call shown in S1104 in the embodiment.

[0497] In other embodiments, the account ID and account password of the first network call can also be obtained by the first electronic device from the second server. Then the second server sends it to the second electronic device, and the second electronic device can display the first user interface, in which the first answering control and the first hang-up control are displayed. The second electronic device can receive the user's operation on the first answering control, and connect to the second server based on the account ID and account password of the first network call. After the first electronic device and the second electronic device are both connected to the second server based on the account ID and account password of the first network call, the first electronic device and the second electronic device establish the first network call, and the first electronic device and the second electronic device can send audio messages or send audio messages and images to each other through the first network call.

[0498] S1507. The second server is further used to send the account ID and account password of the first network call to the first electronic device and the second electronic device. The account ID and account password of the first network call are used by the first electronic device and the second electronic device to establish the first network call.

[0499] Through this method, when the first electronic device does not store the device information of other devices inside, the first electronic device can also actively initiate a network call connection to other electronic devices. After receiving the user's request to play the network call, the first electronic device can send a request to establish a network call to other devices through the first server. The other device then applies for the account ID and account password of the first network call, thereby realizing the first network call between the first electronic device and the second electronic device. The first electronic device and the second electronic device can send audio messages or send audio messages and images to each other through the first network call.

[0500] In one possible implementation, the second electronic device is further used to: establish a first session connection with the first electronic device; in response to receiving the account ID and account password of the first network call sent by the second server, send a first message to the first electronic device through the first session connection; the first electronic device is further used to display a second user interface in response to the first message, and the second user interface includes a second hang-up control and call duration.

[0501] In combination with the first aspect, in a possible implementation manner, the first session connection is initiated by the second electronic device to the first electronic device based on the device information of the first electronic device stored in the second electronic device.

[0502] The device information of the first electronic device includes one or more of the following: a unique identifier of the first electronic device, a device type of the first electronic device, a cloud device ID of the first electronic device, a node ID of the first electronic device, an IP address of the first electronic device, and a MAC address of the first electronic device.

[0503] The second server cannot send messages to the first electronic device. Then the second electronic device needs to establish a first session connection with the first electronic device. After the second electronic device connects to the second server based on the account ID and account password of the first network call, the second electronic device needs to send a first message to the first electronic device through the first session connection. The first message is used to inform the first electronic device that the second electronic device has been connected to the second server and the first electronic device needs to switch to display the second user interface. In this way, when the first electronic device cannot actively establish a session connection with the second electronic device, the first electronic device can actively establish a session connection through the second electronic device.

[0504] For example, the first session connection can be Fig.11 The first session connection shown in embodiment S1102.

[0505] Exemplarily, the second user interface may be Figure 9H In the user interface 960 shown, the second hang-up control may be Figure 9H The hang up option in user interface 960 is shown.

[0506] In one possible implementation, the second electronic device is also used to stop displaying the first user interface and start displaying the third user interface in response to receiving the account ID and account password of the first network call sent by the second server, and the third user interface includes a third hang-up control and call duration.

[0507] Exemplarily, the third user interface may be Figure 9G The user interface 950 is shown. The third hang-up control can be Figure 9G The hang up option in user interface 950 is shown.

[0508] In one possible implementation, the system also includes a third electronic device, on which a third user account is logged in, and the third user account is the same as or related to the first user account; a first server, specifically used to: in response to a first request, determine a second electronic device on which a second user account is logged in and a third electronic device on which a third user account is logged in based on the account ID of the first user account; send a request to establish a network call to the second electronic device and the third electronic device; the third electronic device, used to display a fourth user interface in response to the request to establish a network call, in which a second answering control and a fourth hang-up control are displayed; the second electronic device, also used to send a second message to the first server; the first server, also used to send a second message to the third electronic device; the third electronic device, also used to stop displaying the fourth user interface in response to the second message.

[0509] In other embodiments, the second message may also be sent by the first electronic device to the third electronic device through the first server.

[0510] In this way, when the first electronic device initiates an Internet call connection, the first electronic device cannot select a specific device to initiate the Internet call connection to, and the first electronic device can send the Internet call establishment request to one or more devices logged in with the same account, and to one or more devices logged in with different accounts but associated with each other through the second server. After one of the electronic devices agrees to establish an Internet call connection with the first electronic device, the other electronic devices that receive the Internet call connection will stop prompting the user to answer the Internet call.

[0511] Exemplarily, the third electronic device may be the electronic device 300 .

[0512] Exemplarily, the fourth user interface may be Fig.9D The user interface 940 shown. The second answer control can be Fig.9DIn the answer option of the user interface 940 shown, the fourth hang up control can be Fig.9D The hang up option in user interface 940 is shown.

[0513] Exemplarily, the second message may be Fig.10 The stop displaying network call request interface message shown in S1012 in the embodiment.

[0514] In one possible implementation, the second electronic device is further used to: receive a user operation on a first hang-up control to establish a first session connection with the first electronic device; send a third message to the first electronic device through the first session connection; the first electronic device is further used to display a fifth user interface in response to the third message, the fifth user interface including first indication information, and the first indication information is used to prompt the user that the user has refused to establish a network call.

[0515] The second server cannot send a message to the first electronic device. After the second electronic device refuses to establish a network call connection with the first electronic device, the second electronic device needs to establish a first session connection with the first electronic device and send a call rejection message to the first electronic device, so that the first electronic device can prompt the user that the second electronic device has rejected the network call.

[0516] Exemplarily, the third message may be Fig.12 The rejection call notification shown in embodiment S1205.

[0517] Exemplarily, the five user interfaces may be Figure 9J The user interface shown in the figure, the first indication information may be Figure 9J The prompt message in the user interface shown is "The other party has rejected your video call request."

[0518] In one possible implementation, the system also includes a third electronic device, on which a third user account is logged in, and the third user account is the same as or associated with the first user account; the second electronic device is also used to: send a fourth message to the first server; the first server is also used to send a fourth message to the third electronic device; the third electronic device is also used to stop displaying a fourth user interface in response to the fourth message, the fourth interface is displayed after the third electronic device receives a network call request sent by the first server, and the fourth user interface displays a second answer control and a fourth hang up control.

[0519] The third electronic device also establishes a long connection with the second server.

[0520] Optionally, the first message may also be sent by the first electronic device to the third electronic device through the first server.

[0521] After the second electronic device refuses to establish an Internet call connection with the first electronic device, it is necessary to send a message to the third electronic device to inform the third electronic device to stop displaying the Internet call request interface (ie, the fourth user interface).

[0522] Exemplarily, the fourth message may be Fig.12 The call rejection message shown in S1209 in the embodiment.

[0523] In one possible implementation, the second electronic device is further used to receive and send a third request to the second server in response to a second user operation; the second server is further used to generate an account ID and an account password for a second network call in response to the third request; the second server is further used to send the account ID and the account password for the second network call to the first electronic device and the second electronic device, and the account ID and the account password for the second network call are used by the first electronic device and the second electronic device to establish a second network call.

[0524] The second user operation may be that the user operates on the second electronic device to actively initiate a network call connection to the first electronic device. When the second electronic device actively initiates a network call connection, the second electronic device may select a target for the network call connection (for example, the user selects the first electronic device).

[0525] Exemplarily, the second user operation may be Figure 2C Input operation for the video call option in the embodiment.

[0526] The third request can be Figure 5 The establishment of the RTC call request shown in embodiment S503.

[0527] The account ID and password for the second network call can be Figure 5 The account ID and account password of the second network call generated by the RTC server in embodiment S504.

[0528] In one possible implementation, the second electronic device is further used to establish a second session connection with the first electronic device; the second electronic device is further used to display a sixth user interface in response to a second user operation, and the sixth user interface includes a fifth hang-up control; the first electronic device is further used to: in response to an account ID and an account password of a second network call sent by a second server, display a seventh user interface, and the seventh user interface includes a third answering control and a sixth hang-up control; receive and respond to the user's operation on the third answering control, and send a fifth message to the second electronic device through the second session connection; the second electronic device is further used to display an eighth user interface in response to the fifth message, and the eighth user interface includes call duration and a seventh hang-up control.

[0529] When the second electronic device actively initiates the network call connection, the second electronic device also needs to actively establish a second session connection with the first electronic device. After the first electronic device confirms to answer the network call request sent by the second electronic device, the first electronic device can send a fifth message to the second electronic device through the second session connection, so that the second electronic device can start to display the call in progress interface (i.e., the eighth user interface).

[0530] For example, the second session connection can be Figure 4 The embodiment shows a session connection between the second electronic device and the first electronic device.

[0531] The sixth user interface may be Figure 2D The user interface 2310 shown in the embodiment. The fifth hang-up control can be Figure 2D A hang up option in user interface 2310 is shown in the embodiment.

[0532] The seventh user interface may be Figure 2E The user interface 240 shown in the embodiment. The third answer control can be Figure 2E The answer option in the user interface 240 of the embodiment shown. The sixth hang up control can be Figure 2E A hang up option in user interface 240 is shown in the embodiment.

[0533] The user's operation on the third answering control may be Figure 2E The embodiment shows the user's input operation for the answering option.

[0534] The fifth message can be Figure 5 The answering success message shown in embodiment S515.

[0535] The eighth user interface may be Figure 2G The user interface 260 shown in the embodiment. The seventh hang-up control can be Figure 2G A hang up option in the user interface 260 in the embodiment shown.

[0536] In one possible implementation, the first electronic device is further used to receive and respond to the user's operation on the sixth hang-up control, and send a sixth message to the second electronic device through the second session connection; the second electronic device is further used to respond to the sixth message and display a ninth user interface, and the ninth user interface includes second indication information, and the second indication information is used to prompt the user that the user has refused to establish a network call.

[0537] When the second electronic device actively initiates the network call connection, the second electronic device also needs to actively establish a second session connection with the first electronic device. After the first electronic device refuses to answer the network call request sent by the second electronic device, the first electronic device can send a sixth message to the second electronic device through the second session connection, so that the second electronic device can prompt the second electronic device that the first electronic device has refused the network call.

[0538] Exemplarily, the user's operation on the sixth hang-up control may be: Figure 2H The embodiment shows the user's input operation for the hang-up option.

[0539] The sixth message can be Figure 6 The call rejection message shown in embodiment S614.

[0540] Nine user interfaces can be Fig.2I In the user interface 270 shown, the second indication information may be Fig.2I The prompt message in the user interface 270 shown is “The phone has rejected your video call”.

[0541] refer to Fig.16 , Fig.16 A schematic structural diagram of an electronic device is shown.

[0542] The electronic device 100 may be a mobile phone, a tablet computer, a desktop computer, a laptop computer, a handheld computer, a notebook computer, an ultra-mobile personal computer (UMPC), a netbook, a cellular phone, a personal digital assistant (PDA), an augmented reality (AR) device, a virtual reality (VR) device, an artificial intelligence (AI) device, a wearable device, an in-vehicle device, a smart home device and / or a smart city device. The embodiments of the present application do not impose any special restrictions on the specific type of the electronic device.

[0543] The electronic device 100 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 button 190, a motor 191, an indicator 192, a camera 193, a display screen 194, and a subscriber identification module (SIM) card interface 195, etc. 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, etc.

[0544] It is to be understood that the structure illustrated in the embodiment of the present invention does not constitute a specific limitation on the electronic device 100. In other embodiments of the present application, the electronic device 100 may include more or fewer components than shown in the figure, or combine some components, or separate some components, or arrange the components differently. The components shown in the figure may be implemented in hardware, software, or a combination of software and hardware.

[0545] The processor 110 may include one or more processing units, for example, 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. Different processing units may be independent devices or integrated into one or more processors.

[0546] The controller can generate operation control signals according to the instruction operation code and timing signal to complete the control of instruction fetching and execution.

[0547] The processor 110 may also be provided with a memory for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. The memory may store instructions or data that the processor 110 has just used or cyclically used. If the processor 110 needs to use the instruction or data again, it may be directly called from the memory. This avoids repeated access, reduces the waiting time of the processor 110, and thus improves the efficiency of the system.

[0548] In some embodiments, the processor 110 may include one or more interfaces. The interface may include an inter-integrated circuit (I2C) interface, an inter-integrated circuit sound (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.

[0549] The I2C interface is a bidirectional synchronous serial bus, including a serial data line (SDA) and a serial clock line (SCL). In some embodiments, the processor 110 may include multiple groups 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. For example: the processor 110 may be coupled to the touch sensor 180K through the I2C interface, so that the processor 110 communicates with the touch sensor 180K through the I2C bus interface, thereby realizing the touch function of the electronic device 100.

[0550] The I2S interface can be used for audio communication. In some embodiments, the processor 110 can include multiple I2S buses. The processor 110 can be coupled to the audio module 170 via the I2S bus to achieve communication between the processor 110 and the audio module 170. In some embodiments, the audio module 170 can transmit an audio signal to the wireless communication module 160 via the I2S interface to achieve the function of answering a call through a Bluetooth headset.

[0551] The PCM interface can 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 can be coupled via a PCM bus interface. In some embodiments, the audio module 170 can also transmit audio signals to the wireless communication module 160 via the PCM interface to realize the function of answering calls via a Bluetooth headset. Both the I2S interface and the PCM interface can be used for audio communication.

[0552] The UART interface is a universal serial data bus for asynchronous communication. The bus can be a bidirectional communication bus. It converts the data to be transmitted between serial communication and parallel communication. In some embodiments, the UART interface is generally used to connect the processor 110 and the wireless communication module 160. For example, the processor 110 communicates with the Bluetooth module in the wireless communication module 160 through the UART interface to implement the Bluetooth function. In some embodiments, the audio module 170 can transmit an audio signal to the wireless communication module 160 through the UART interface to implement the function of playing music through a Bluetooth headset.

[0553] The MIPI interface can be used to connect the processor 110 with peripheral devices such as the display screen 194 and the camera 193. The MIPI interface includes a camera serial interface (CSI), a display serial interface (DSI), etc. In some embodiments, the processor 110 and the camera 193 communicate via the CSI interface to implement the shooting function of the electronic device 100. The processor 110 and the display screen 194 communicate via the DSI interface to implement the display function of the electronic device 100.

[0554] The GPIO interface can be configured by software. The GPIO interface can be configured as a control signal or as a data signal. In some embodiments, the GPIO interface can 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, etc. The GPIO interface can also be configured as an I2C interface, an I2S interface, a UART interface, a MIPI interface, etc.

[0555] The USB interface 130 is an interface that complies with the USB standard specification, and specifically can be a Mini USB interface, a Micro USB interface, a USB Type C interface, etc. The USB interface 130 can be used to connect a charger to charge the electronic device 100, and can also be used to transfer data between the electronic device 100 and a peripheral device. It can also be used to connect headphones to play audio through the headphones. The interface can also be used to connect other electronic devices, such as AR devices, etc.

[0556] It is understandable that the interface connection relationship between the modules illustrated in the embodiment of the present invention is only a schematic illustration and does not constitute a structural limitation on the electronic device 100. In other embodiments of the present application, the electronic device 100 may also adopt different interface connection methods in the above embodiments, or a combination of multiple interface connection methods.

[0557] The charging management module 140 is used 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 through the USB interface 130. In some wireless charging embodiments, the charging management module 140 may receive wireless charging input through a wireless charging coil of the electronic device 100. While the charging management module 140 is charging the battery 142, it may also power the electronic device through the power management module 141.

[0558] 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 charging management module 140, and supplies power to the processor 110, the internal memory 121, the display screen 194, the camera 193, and the wireless communication module 160. The power management module 141 can also be used to monitor parameters such as battery capacity, battery cycle number, battery health status (leakage, impedance), etc. In some other embodiments, the power management module 141 can also be set in the processor 110. In other embodiments, the power management module 141 and the charging management module 140 can also be set in the same device.

[0559] The wireless communication function of the electronic device 100 can be implemented through the antenna 1, the antenna 2, the mobile communication module 150, the wireless communication module 160, the modem processor and the baseband processor.

[0560] Antenna 1 and antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in electronic device 100 can be used to cover a single or multiple communication frequency bands. Different antennas can also be reused to improve the utilization of antennas. For example, antenna 1 can be reused as a diversity antenna for a wireless local area network. In some other embodiments, the antenna can be used in combination with a tuning switch.

[0561] The mobile communication module 150 can provide solutions for wireless communications including 2G / 3G / 4G / 5G, etc., applied to the electronic device 100. The mobile communication module 150 may include at least one filter, a switch, a power amplifier, a low noise amplifier (LNA), etc. The mobile communication module 150 can receive electromagnetic waves from the antenna 1, and filter, amplify, and process the received electromagnetic waves, and transmit them to the modulation and demodulation processor for demodulation. The mobile communication module 150 can also amplify the signal modulated by the modulation and demodulation processor, and convert it into electromagnetic waves for radiation through the antenna 1. In some embodiments, at least some of the functional modules of the mobile communication module 150 can be set in the processor 110. In some embodiments, at least some of the functional modules of the mobile communication module 150 can be set in the same device as at least some of the modules of the processor 110.

[0562] The modem processor may include a modulator and a demodulator. Among them, the modulator is used to modulate the low-frequency baseband signal to be sent into a medium-high frequency signal. The demodulator is used to demodulate the received electromagnetic wave signal into a low-frequency baseband signal. The demodulator then transmits the demodulated low-frequency baseband signal to the baseband processor for processing. After the low-frequency baseband signal is processed by the baseband processor, it is passed to the application processor. The application processor outputs a sound signal through an audio device (not limited to a speaker 170A, a receiver 170B, etc.), or displays an image or video through a display screen 194. In some embodiments, the modem processor may be an independent device. In other embodiments, the modem processor may be independent of the processor 110 and be set in the same device as the mobile communication module 150 or other functional modules.

[0563] The wireless communication module 160 can provide wireless communication solutions including wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) networks), bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), infrared (IR), etc., which are applied to the electronic device 100. The wireless communication module 160 can be one or more devices integrating at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via the antenna 2, modulates the frequency of the electromagnetic wave signal and performs filtering, and sends the processed signal to the processor 110. The wireless communication module 160 can also receive the signal to be sent from the processor 110, modulate the frequency of it, amplify it, and convert it into electromagnetic waves for radiation through the antenna 2.

[0564] In some embodiments, the antenna 1 of the electronic device 100 is coupled to the mobile communication module 150, and the antenna 2 is coupled to the wireless communication module 160, so that the electronic device 100 can communicate with the network and other devices through wireless communication technology. 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 (TD-SCDMA), long term evolution (LTE), BT, GNSS, WLAN, NFC, FM, and / or IR technology. The GNSS may include a global positioning system (GPS), a global navigation satellite system (GLONASS), a Beidou navigation satellite system (BDS), a quasi-zenith satellite system (QZSS) and / or a satellite based augmentation system (SBAS).

[0565] The electronic device 100 implements the display function through a GPU, a display screen 194, and an application processor. The GPU is a microprocessor for image processing, which connects the display screen 194 and the 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 change display information.

[0566] The display screen 194 is used to display images, videos, etc. The display screen 194 includes a display panel. The display panel can be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode or an active-matrix organic light-emitting diode (AMOLED), a flexible light-emitting diode (FLED), Miniled, MicroLed, Micro-oLed, a quantum dot light-emitting diode (QLED), etc. In some embodiments, the electronic device 100 may include 1 or N display screens 194, where N is a positive integer greater than 1.

[0567] The electronic device 100 can realize the shooting function through ISP, camera 193, video codec, GPU, display screen 194 and application processor.

[0568] The ISP is used to process the data fed back by the camera 193. For example, when taking a photo, the shutter is opened, and the light is transmitted to the camera photosensitive element through the lens. The light signal is converted into an electrical signal, and the camera photosensitive element transmits the electrical signal to the ISP for processing and converts it into an image visible to the naked eye. The ISP can also perform algorithm optimization on the noise and brightness of the image. The ISP can also optimize the exposure, color temperature and other parameters of the shooting scene. In some embodiments, the ISP can be set in the camera 193.

[0569] The camera 193 is used to capture still images or videos. The object generates an optical image through the lens and projects it onto the photosensitive element. The photosensitive element can be a charge coupled device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The photosensitive element converts the optical signal into an electrical signal, and then passes the electrical signal to the ISP to be converted into a digital image signal. The ISP outputs the digital image signal to the DSP for processing. The DSP converts the digital image signal into an image signal in a standard RGB, YUV or other format. In some embodiments, the electronic device 100 may include 1 or N cameras 193, where N is a positive integer greater than 1.

[0570] The digital signal processor is used to process digital signals, and can process not only digital image signals but also other digital signals. For example, when the electronic device 100 is selecting a frequency point, the digital signal processor is used to perform Fourier transform on the frequency point energy.

[0571] Video codecs are used to compress or decompress digital videos. The electronic device 100 may support one or more video codecs. Thus, the electronic device 100 may play or record videos in a variety of coding formats, such as Moving Picture Experts Group (MPEG) 1, MPEG2, MPEG3, MPEG4, etc.

[0572] NPU is a neural network (NN) computing processor. By drawing on the structure of biological neural networks, such as the transmission mode between neurons in the human brain, it can quickly process input information and can also continuously self-learn. Through NPU, applications such as intelligent cognition of electronic device 100 can be realized, such as image recognition, face recognition, voice recognition, text understanding, etc.

[0573] The internal memory 121 may include one or more random access memories (RAM) and one or more non-volatile memories (NVM).

[0574] Random access memory may include static random-access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM, for example, the fifth generation DDR SDRAM is generally referred to as DDR5 SDRAM), etc.; non-volatile memory may include disk storage devices and flash memory.

[0575] Flash memory can be divided into NOR FLASH, NAND FLASH, 3D NAND FLASH, etc. according to the operating principle; single-level cell (SLC), multi-level cell (MLC), triple-level cell (TLC), quad-level cell (QLC), etc. according to the storage unit potential level; universal flash storage (UFS), embedded multi media card (eMMC), etc. according to the storage specification.

[0576] The random access memory can be directly read and written by the processor 110, and can be used to store executable programs (such as machine instructions) of the operating system or other running programs, and can also be used to store user and application data.

[0577] The non-volatile memory may also store executable programs and user and application data, etc., and may be loaded into the random access memory in advance for direct reading and writing by the processor 110 .

[0578] The external memory interface 120 can be used to connect to an external non-volatile memory to expand the storage capacity of the electronic device 100. The external non-volatile memory communicates with the processor 110 through the external memory interface 120 to implement a data storage function. For example, files such as music and videos are stored in the external non-volatile memory.

[0579] The electronic device 100 can implement audio functions such as music playing and recording through the audio module 170, the speaker 170A, the receiver 170B, the microphone 170C, the headphone jack 170D, and the application processor.

[0580] The audio module 170 is used to convert digital audio information into analog audio signal output, and is also used to convert analog audio input into digital audio signals. The audio module 170 can also be used to encode and decode audio signals. In some embodiments, the audio module 170 can be arranged in the processor 110, or some functional modules of the audio module 170 can be arranged in the processor 110.

[0581] The speaker 170A, also called a "speaker", is used to convert an audio electrical signal into a sound signal. The electronic device 100 can listen to music or listen to a hands-free call through the speaker 170A.

[0582] The receiver 170B, also called a "earpiece", is used to convert audio electrical signals into sound signals. When the electronic device 100 receives a call or voice message, the voice can be received by placing the receiver 170B close to the human ear.

[0583] Microphone 170C, also called "microphone" or "microphone", is used to convert sound signals into electrical signals. When making a call or sending a voice message, the user can speak by putting their mouth close to microphone 170C to input the sound signal into microphone 170C. The electronic device 100 can be provided with at least one microphone 170C. In other embodiments, the electronic device 100 can be provided with two microphones 170C, which can not only collect sound signals but also realize noise reduction function. In other embodiments, the electronic device 100 can also be provided with three, four or more microphones 170C to collect sound signals, reduce noise, identify the sound source, realize directional recording function, etc.

[0584] The earphone interface 170D is used to connect a wired earphone and can be a USB interface 130 or a 3.5 mm open mobile terminal platform (OMTP) standard interface or a cellular telecommunications industry association of the USA (CTIA) standard interface.

[0585] The pressure sensor 180A is used to sense the pressure signal and can convert the pressure signal into an electrical signal. In some embodiments, the pressure sensor 180A can be set on the display screen 194. There are many types of pressure sensors 180A, such as resistive pressure sensors, inductive pressure sensors, capacitive pressure sensors, etc. The capacitive pressure sensor can be a parallel plate including at least two conductive materials. When a force acts on the pressure sensor 180A, the capacitance between the electrodes changes. The electronic device 100 determines the intensity of the pressure according to the change in capacitance. When a touch operation acts on the display screen 194, the electronic device 100 detects the touch operation intensity according to the pressure sensor 180A. The electronic device 100 can also calculate the touch position according to the detection signal of the pressure sensor 180A. In some embodiments, touch operations acting on the same touch position but with different touch operation intensities can correspond to different operation instructions. For example: when a touch operation with a touch operation intensity less than the first pressure threshold acts on the short message application icon, an instruction to view the short message is executed. When a touch operation with a touch operation intensity greater than or equal to the first pressure threshold acts on the short message application icon, an instruction to create a new short message is executed.

[0586] The gyro sensor 180B can be used to determine the motion posture of the electronic device 100. In some embodiments, the angular velocity of the electronic device 100 around three axes (i.e., x, y, and z axes) can be determined by the gyro sensor 180B. The gyro sensor 180B can be used for anti-shake shooting. For example, when the shutter is pressed, the gyro sensor 180B detects the angle of the electronic device 100 shaking, calculates the distance that the lens module needs to compensate based on the angle, and allows the lens to offset the shaking of the electronic device 100 through reverse movement to achieve anti-shake. The gyro sensor 180B can also be used for navigation and somatosensory game scenes.

[0587] The air pressure sensor 180C is used to measure air pressure. In some embodiments, the electronic device 100 calculates the altitude through the air pressure value measured by the air pressure sensor 180C to assist positioning and navigation.

[0588] The magnetic sensor 180D includes a Hall sensor. The electronic device 100 can use the magnetic sensor 180D to detect the opening and closing of the flip leather case. In some embodiments, when the electronic device 100 is a flip phone, the electronic device 100 can detect the opening and closing of the flip cover according to the magnetic sensor 180D. Then, according to the detected opening and closing state of the leather case or the opening and closing state of the flip cover, the flip cover can be automatically unlocked.

[0589] The acceleration sensor 180E can detect the magnitude of the acceleration of the electronic device 100 in all directions (generally three axes). When the electronic device 100 is stationary, the magnitude and direction of gravity can be detected. It can also be used to identify the posture of the electronic device and is applied to applications such as horizontal and vertical screen switching and pedometers.

[0590] The distance sensor 180F is used to measure the distance. The electronic device 100 can measure the distance by infrared or laser. In some embodiments, when shooting a scene, the electronic device 100 can use the distance sensor 180F to measure the distance to achieve fast focusing.

[0591] The proximity light sensor 180G may include, for example, a light emitting diode (LED) and a light detector, such as a photodiode. The light emitting diode may be an infrared light emitting diode. The electronic device 100 emits infrared light outward through the light emitting diode. The electronic device 100 uses a photodiode to detect infrared reflected light from nearby objects. When sufficient reflected light is detected, it can be determined that there is an object near the electronic device 100. When insufficient reflected light is detected, the electronic device 100 can determine that there is no object near the electronic device 100. The electronic device 100 can use the proximity light sensor 180G to detect that the user holds the electronic device 100 close to the ear to talk, so as to automatically turn off the screen to save power. The proximity light sensor 180G can also be used in leather case mode and pocket mode to automatically unlock and lock the screen.

[0592] The ambient light sensor 180L is used to sense the ambient light brightness. The electronic device 100 can adaptively adjust the brightness of the display screen 194 according to the perceived ambient light brightness. The ambient light sensor 180L can also be used to automatically adjust the white balance when taking pictures. The ambient light sensor 180L can also cooperate with the proximity light sensor 180G to detect whether the electronic device 100 is in a pocket to prevent accidental touches.

[0593] The fingerprint sensor 180H is used to collect fingerprints. The electronic device 100 can use the collected fingerprint characteristics to implement fingerprint unlocking, access application locks, fingerprint photography, fingerprint call answering, etc.

[0594] The temperature sensor 180J is used to detect temperature. In some embodiments, the electronic device 100 uses the temperature detected by the temperature sensor 180J to execute a temperature processing strategy. For example, when the temperature reported by the temperature sensor 180J exceeds a threshold, the electronic device 100 reduces the performance of a processor located near the temperature sensor 180J to reduce power consumption and implement thermal protection. In other embodiments, when the temperature is lower than another threshold, the electronic device 100 heats the battery 142 to avoid abnormal shutdown of the electronic device 100 due to low temperature. In other embodiments, when the temperature is lower than another threshold, the electronic device 100 performs a boost on the output voltage of the battery 142 to avoid abnormal shutdown caused by low temperature.

[0595] The touch sensor 180K is also called a "touch control device". The touch sensor 180K can be set on the display screen 194. The touch sensor 180K and the display screen 194 form a touch screen, also called a "touch control screen". The touch sensor 180K is used to detect touch operations acting on or near it. The touch sensor can pass the detected touch operation to the application processor to determine the type of touch event. Visual output related to the touch operation can be provided through the display screen 194. In other embodiments, the touch sensor 180K can also be set on the surface of the electronic device 100, which is different from the position of the display screen 194.

[0596] The bone conduction sensor 180M can obtain a vibration signal. In some embodiments, the bone conduction sensor 180M can obtain a vibration signal of a vibrating bone block of the vocal part of the human body. The bone conduction sensor 180M can also contact the human pulse to receive a blood pressure beat signal. In some embodiments, the bone conduction sensor 180M can also be set in an earphone and combined into a bone conduction earphone. The audio module 170 can parse out a voice signal based on the vibration signal of the vibrating bone block of the vocal part obtained by the bone conduction sensor 180M to realize a voice function. The application processor can parse the heart rate information based on the blood pressure beat signal obtained by the bone conduction sensor 180M to realize a heart rate detection function.

[0597] The key 190 includes a power key, a volume key, etc. The key 190 may be a mechanical key or a touch key. The electronic device 100 may receive key input and generate key signal input related to user settings and function control of the electronic device 100.

[0598] Motor 191 can generate vibration prompts. Motor 191 can be used for incoming call vibration prompts, and can also be used for touch vibration feedback. For example, touch operations acting on different applications (such as taking pictures, audio playback, etc.) can correspond to different vibration feedback effects. For touch operations acting on different areas of the display screen 194, motor 191 can also correspond to different vibration feedback effects. Different application scenarios (for example: time reminders, receiving messages, alarm clocks, games, etc.) can also correspond to different vibration feedback effects. The touch vibration feedback effect can also support customization.

[0599] Indicator 192 may be an indicator light, which may be used to indicate charging status, power changes, messages, missed calls, notifications, etc.

[0600] The software system of the electronic device 100 may adopt a layered architecture, an event-driven architecture, a micro-core architecture, a micro-service architecture, or a cloud architecture. In the embodiment of the present invention, the Android system of the layered architecture is taken as an example to exemplify the software structure of the electronic device 100.

[0601] Fig.17 1 is a software structure block diagram of the electronic device 100 according to an embodiment of the present invention.

[0602] The layered architecture divides the software into several layers, each with clear roles and division of labor. The layers communicate with each other through software interfaces. In some embodiments, the Android system is divided into four layers, from top to bottom: the application layer, the application framework layer, the Android runtime and system library, and the kernel layer.

[0603] The application layer can include a series of application packages.

[0604] like Fig.17 As shown, the application package may include camera, gallery, calendar, call, map, navigation, WLAN, Bluetooth, music, video, short message and other applications.

[0605] The application framework layer provides an application programming interface (API) and a programming framework for the applications in the application layer. The application framework layer includes some predefined functions.

[0606] like Fig.17As shown, the application framework layer may include a window manager, a content provider, a view system, a phone manager, a resource manager, a notification manager, and the like.

[0607] The window manager is used to manage window programs. The window manager can obtain the display screen size, determine whether there is a status bar, lock the screen, capture the screen, etc.

[0608] Content providers are used to store and retrieve data and make it accessible to applications. The data may include videos, images, audio, calls made and received, browsing history and bookmarks, phone books, etc.

[0609] The view system includes visual controls, such as controls for displaying text, controls for displaying images, etc. The view system can be used to build applications. A display interface can be composed of one or more views. For example, a display interface including a text notification icon can include a view for displaying text and a view for displaying images.

[0610] The phone manager is used to provide communication functions of the electronic device 100, such as management of call status (including connecting, hanging up, etc.).

[0611] The resource manager provides various resources for applications, such as localized strings, icons, images, layout files, video files, and so on.

[0612] The notification manager enables applications to display notification information in the status bar. It can be used to convey notification-type messages and can disappear automatically after a short stay without user interaction. For example, the notification manager is used to notify download completion, message reminders, etc. The notification manager can also be a notification that appears in the system top status bar in the form of a chart or scroll bar text, such as notifications of applications running in the background, or a notification that appears on the screen in the form of a dialog window. For example, a text message is displayed in the status bar, a prompt sound is emitted, an electronic device vibrates, an indicator light flashes, etc.

[0613] Android Runtime includes core libraries and virtual machines. Android runtime is responsible for scheduling and management of the Android system.

[0614] The core library consists of two parts: one part is the function that needs to be called by the Java language, and the other part is the Android core library.

[0615] The application layer and the application framework layer run in a virtual machine. The virtual machine executes the Java files of the application layer and the application framework layer as binary files. The virtual machine is used to perform functions such as object life cycle management, stack management, thread management, security and exception management, and garbage collection.

[0616] The system library may include multiple functional modules, such as surface manager, media library, 3D graphics processing library (such as OpenGL ES), 2D graphics engine (such as SGL), etc.

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

[0618] The media library supports playback and recording of a variety of commonly used audio and video formats, as well as static image files, etc. The media library can support a variety of audio and video encoding formats, such as: MPEG4, H.264, MP3, AAC, AMR, JPG, PNG, etc.

[0619] The 3D graphics processing library is used to implement 3D graphics drawing, image rendering, compositing, and layer processing.

[0620] A 2D graphics engine is a drawing engine for 2D drawings.

[0621] The kernel layer is the layer between hardware and software. The kernel layer contains at least display driver, camera driver, audio driver, and sensor driver.

[0622] The following is an illustrative description of the workflow of the software and hardware of the electronic device 100 in conjunction with capturing a photo scene.

[0623] When the touch sensor 180K receives a touch operation, the corresponding hardware interrupt is sent to the kernel layer. The kernel layer processes the touch operation into a raw input event (including touch coordinates, timestamp of the touch operation, and other information). The raw input event is stored in the kernel layer. The application framework layer obtains the raw input event from the kernel layer and identifies the control corresponding to the input event. For example, if the touch operation is a touch single-click operation and the control corresponding to the single-click operation is the control of the camera application icon, the camera application calls the interface of the application framework layer to start the camera application, and then starts the camera driver by calling the kernel layer to capture static images or videos through the camera 193.

[0624] The various implementation modes of the present application can be combined arbitrarily to achieve different technical effects.

[0625] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can 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 process or function described in the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can 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 can be transmitted from a website site, computer, server or data center to another website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line) or wireless (e.g., infrared, wireless, microwave, etc.) mode. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrated. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state disk (SSD)), etc.

[0626] Those skilled in the art can understand that to implement all or part of the processes in the above-mentioned embodiments, the processes can be completed by computer programs to instruct related hardware, and the programs can be stored in computer-readable storage media. When the programs are executed, they can include the processes of the above-mentioned method embodiments. The aforementioned storage media include: ROM or random access memory RAM, magnetic disk or optical disk and other media that can store program codes.

[0627] In short, the above description is only an embodiment of the technical solution of the present invention, and is not intended to limit the protection scope of the present invention. Any modification, equivalent replacement, improvement, etc. made according to the disclosure of the present invention shall be included in the protection scope of the present invention.

Claims

1. A device communication system, characterized in that: The system includes a first electronic device, a second electronic device, a first server and a second server, the second electronic device and the first server establish a first persistent connection, a first user account is logged in to the first electronic device, a second user account is logged in to the second electronic device, and the first user account and the second user account are the same or associated with each other; wherein, The first electronic device is configured to receive and respond to a first user operation, and send a first request to the first server, wherein the first request carries an account ID of the first user account; The first server is configured to determine, in response to the first request, the second electronic device logged in by the second user account based on the account ID of the first user account; The first server is further configured to send a request to establish a network call to the second electronic device; The second electronic device is configured to display a first user interface in response to the request to establish a network call, wherein the first user interface displays a first answer control and a first hang-up control; The second electronic device is further configured to receive an operation of the user on the first answering control and send a second request to the second server; The second server is used to generate an account ID and an account password for the first network call in response to the second request; The second server is further used to send the account ID and account password of the first network call to the first electronic device and the second electronic device, and the account ID and account password of the first network call are used by the first electronic device and the second electronic device to establish the first network call.

2. The system according to claim 1, characterized in that The second electronic device is further used for: Establishing a first session connection with the first electronic device; In response to receiving the account ID and account password of the first network call sent by the second server, sending a first message to the first electronic device through the first session connection; The first electronic device is further used to display a second user interface in response to the first message, wherein the second user interface includes a second hang-up control and call duration.

3. The system according to claim 2, characterized in that The first session connection is initiated by the second electronic device to the first electronic device based on the device information of the first electronic device stored in the second electronic device.

4. The system according to claim 3, characterized in that The device information of the first electronic device includes one or more of the following: a unique identifier of the first electronic device, a device type of the first electronic device, a cloud device ID of the first electronic device, a node ID of the first electronic device, an IP address of the first electronic device, and a MAC address of the first electronic device.

5. The system according to any one of claims 1 to 4, characterized in that: The second electronic device is also used to stop displaying the first user interface and start displaying a third user interface in response to receiving the account ID and account password of the first network call sent by the second server, and the third user interface includes a third hang-up control and call duration.

6. The system according to any one of claims 1 to 4, characterized in that: The system further includes a third electronic device, a third user account is logged into the third electronic device, and the third user account is the same as or associated with the first user account; The first server is specifically used for: In response to the first request, determining the second electronic device logged in with the second user account and the third electronic device logged in with the third user account based on the account ID of the first user account; Sending the network call establishment request to the second electronic device and the third electronic device; The third electronic device is used to display a fourth user interface in response to the request to establish a network call, wherein the fourth user interface displays a second answer control and a fourth hang up control; The second electronic device is further used to send a second message to the first server; The first server is further configured to send the second message to the third electronic device; The third electronic device is further configured to stop displaying the fourth user interface in response to the second message.

7. The system according to any one of claims 1 to 6, characterized in that: The second electronic device is further used for: receiving a user operation on the first hang-up control, and establishing a first session connection with the first electronic device; Sending a third message to the first electronic device through the first session connection; The first electronic device is further used to display the fifth user interface in response to the third message, and the fifth user interface includes first indication information, and the first indication information is used to prompt the user that the network call has been rejected.

8. The system according to claim 7, characterized in that The system further includes a third electronic device, a third user account is logged into the third electronic device, and the third user account is the same as or associated with the first user account; The second electronic device is further used to: send a fourth message to the first server; The first server is further configured to send the fourth message to the third electronic device; The third electronic device is also used to stop displaying the fourth user interface in response to the fourth message, wherein the fourth interface is displayed after the third electronic device receives the network call request sent by the first server, and the fourth user interface displays a second answering control and a fourth hang-up control.

9. The system according to any one of claims 1 to 8, characterized in that: The second electronic device is further configured to receive and, in response to a second user operation, send a third request to the second server; The second server is further configured to generate an account ID and an account password for the second network call in response to the third request; The second server is further used to send the account ID and account password of the second network call to the first electronic device and the second electronic device, and the account ID and account password of the second network call are used by the first electronic device and the second electronic device to establish the second network call.

10. The system according to claim 9, characterized in that The second electronic device is further used to establish a second session connection with the first electronic device; The second electronic device is further configured to display a sixth user interface in response to the second user operation, wherein the sixth user interface includes a fifth hang-up control; The first electronic device is further used for: In response to the account ID and account password of the second network call sent by the second server, displaying a seventh user interface, wherein the seventh user interface includes a third answering control and a sixth hang-up control; receiving and responding to a user's operation on the third answering control, and sending a fifth message to the second electronic device through the second session connection; The second electronic device is further used to display an eighth user interface in response to the fifth message, and the eighth user interface includes call duration and a seventh hang-up control.

11. The system according to claim 10, characterized in that The first electronic device is also used receiving and responding to a user operation on the sixth hang-up control, and sending a sixth message to the second electronic device through the second session connection; The second electronic device is further used to display a ninth user interface in response to the sixth message, wherein the ninth user interface includes second indication information, and the second indication information is used to prompt the user that the user has rejected the establishment of the network call.

12. The system according to any one of claims 1 to 11, characterized in that: The first electronic device is a watch, and the second electronic device is a mobile phone.

13. A method for communication between devices, characterized in that: The method comprises: The second electronic device displays a first user interface, wherein the first user interface displays a first answer control and a first hang-up control; wherein the first user interface is displayed after the second electronic device receives a network call request sent by the first server, wherein the network call request is sent to the second electronic device by the first server after receiving a first request sent by the first electronic device and determining a second electronic device logged in with a second user account based on an account ID of a first user account carried in the first request, wherein the first user account is a user account logged in on the first electronic device, and the second user account is the same as or associated with the first user account; The second electronic device receives the user's operation on the first answering control, and sends a second request to the second server, wherein the second request is used to instruct the second server to generate an account ID and an account password for the first network call and send the account ID and the account password for the first network call to the first electronic device and the second electronic device, and the account ID and the account password for the first network call are used by the first electronic device and the second electronic device to establish the first network call.

14. The method according to claim 13, characterized in that After the second electronic device displays the first user interface, the method further includes: The second electronic device establishes a first session connection with the first electronic device; In response to receiving the account ID and account password of the first network call sent by the second server, the second electronic device sends a first message to the first electronic device based on the first session connection, and the first message is used to instruct the first electronic device to display a second user interface, and the second user interface includes a second hang-up control and call duration.

15. The method according to claim 14, characterized in that The first session connection is initiated by the second electronic device to the first electronic device based on the device information of the first electronic device stored in the second electronic device.

16. The method according to claim 15, characterized in that The device information of the first electronic device includes one or more of the following: The unique identifier of the first electronic device, the device type of the first electronic device, the cloud device ID of the first electronic device, the node ID of the first electronic device, the IP address of the first electronic device, and the MAC address of the first electronic device.

17. The method according to any one of claims 13 to 16, characterized in that: After the second electronic device receives the account ID and account password of the first network call sent by the second server, the method further includes: The second electronic device stops displaying the first user interface and starts displaying a third user interface, wherein the third user interface includes a third hang-up control and a call duration.

18. The method according to any one of claims 13 to 17, characterized in that: After the second electronic device displays the first user interface, the method further includes: The second electronic device receives a user's operation on the first hang-up control; In response to an operation on the first hang-up control, establishing a first session connection with the first electronic device; The second electronic device sends a third message to the first electronic device through the first session, where the third message is used to instruct the first electronic device to display the fifth user interface, where the fifth user interface includes first indication information, and the first indication information is used to prompt the user that the network call has been rejected.

19. The method according to claim 18, characterized in that After the second electronic device receives the user's operation on the first hang-up control, the method further includes: The second electronic device sends a fourth message to the first server, and the fourth message is used to instruct the first server to send a fourth message to a third electronic device, and the fourth message is used to instruct the third electronic device to stop displaying a fourth user interface, and the fourth interface is displayed after the third electronic device receives the network call request sent by the first server, and a second answering control and a fourth hang-up control are displayed in the fourth user interface, and a third user account is logged in to the third electronic device, and the third user account is the same as or associated with the first user account.

20. The method according to any one of claims 13 to 19, characterized in that: The method further comprises: The second electronic device receives and responds to the second user operation, and sends a third request to the second server, where the third request is used to instruct the second server to generate an account ID and an account password for a second network call, and send the account ID and the account password for the second network call to the first electronic device and the second electronic device, where the account ID and the account password for the second network call are used by the first electronic device and the second electronic device to establish the second network call.

21. The method according to claim 20, characterized in that After the second electronic device receives and responds to the second user operation, the method further includes: The second electronic device establishes a second session connection with the first electronic device; In response to the second user operation, displaying a sixth user interface, wherein the sixth user interface includes a fifth hang-up control; receiving a fifth message sent by the first electronic device through the second session connection, wherein the fifth message is sent by the first electronic device after receiving a user's operation on a third answering control in a seventh user interface, and the seventh user interface is displayed by the first electronic device in response to the account ID and account password of the second network call sent by the second server; In response to the fifth message, the second electronic device displays an eighth user interface, where the eighth user interface includes call duration and a seventh hang-up control.

22. The method according to claim 21, characterized in that After the second electronic device displays the sixth user interface, the method further includes: The second electronic device receives a sixth message sent by the first electronic device, wherein the sixth message is sent by the first electronic device after receiving an operation of the user on the sixth hang-up control; In response to the sixth message, the second electronic device displays a ninth user interface, where the ninth user interface includes second indication information, where the second indication information is used to prompt the user that the user has rejected the establishment of the network call.

23. The method according to any one of claims 13 to 22, characterized in that: The first electronic device is a watch, and the second electronic device is a mobile phone.

24. An electronic device, which is a second electronic device, characterized in that: The second electronic device includes one or more processors and one or more memories; wherein the one or more memories are coupled to the one or more processors, and the one or more memories are used to store computer program codes, and the computer program codes include computer instructions, and when the one or more processors execute the computer instructions, the second electronic device executes the method described in any one of claims 13-23.

25. A chip system, the chip system is applied to a second electronic device, the chip system comprises one or more processors, characterized in that: The processor is configured to call computer instructions so that the second electronic device executes the method as claimed in any one of claims 13 to 23.

26. A computer-readable storage medium comprising instructions, characterized in that: When the instruction is executed on the second electronic device, the second electronic device executes the method according to any one of claims 13 to 23.

Images