An inter-device communication method, system and storage medium

Abstract

The application provides an inter-device communication method, system and storage medium. A first electronic device sends a first request to a first server, and the first request carries an account ID of a first user account; 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 being the same as or associated with the first user account, and sends a network call request to the second electronic device. The second electronic device receives an operation of a user on a first listening control, and sends a second request to a second server. The second server generates an account ID and an account password of a 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, so that the first electronic device and the second electronic device establish the first network call. In the case that the watch does not store device information of other devices, the watch can actively initiate a network call connection to other devices.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of communication, and in particular to an inter-device communication method, system and storage medium. BACKGROUND

[0002] In recent years, with the popularity of smart watches, the call between the watch and the mobile phone has become an indispensable feature. If the watch and the mobile phone can communicate, it can be convenient for users to use.

[0003] Currently, the operator call scheme can be used, and a subscriber identity module (SIM) card slot or embedded subscriber identity module (ESIM) function needs to be designed on the watch to integrate the phone card into the watch, and the call can be realized by dialing to call or listen to the call to the mobile phone or other operator devices. However, if the watch does not support the SIM card slot or does not support the ESIM function, the watch cannot communicate with other devices. SUMMARY

[0004] The present application provides an inter-device communication method, system and storage medium, which realizes that the watch can also actively initiate a network call connection to other devices without storing the device information of other devices.

[0005] In a first aspect, the present application provides an inter-device communication system, which comprises a first electronic device, a second electronic device, a first server and a second server, the second electronic device and the first server have a first long connection, the first electronic device has a first user account logged in, the second electronic device has a second user account logged in, the first user account and the second user account are the same or are associated with each other; wherein the first electronic device is configured to receive and respond to a first user operation, send a first request to the first server, the first request carries an account ID of the first user account; the first server is configured to determine the second electronic device with the second user account logged in based on the account ID of the first user account in response to the first request; the first server is further configured to send a network call establishment request to the second electronic device; the second electronic device is configured to display a first user interface in response to the network call establishment request, the first user interface displays a first call control and a first hang-up control; the second electronic device is further configured to receive a user operation on the first call control and send a second request to the second server; the second server is configured to generate an account ID and an account password of a first network call in response to the second request; the second server is further configured to send the account ID and the account password of the first network call to the first electronic device and the second electronic device, and the account ID and the 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.

[0006] In the embodiments of the present application, the first electronic device can be a device supporting a SIM card slot or supporting an ESIM, or can be a device not supporting a SIM card slot or supporting an ESIM. That is, both the device supporting the SIM card slot or supporting the ESIM can be applied to the present application.

[0007] In some embodiments, the first electronic device can be a children watch, and the second electronic device can be a family member of a user of the first electronic device. The first electronic device and the second electronic device can 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 the account password of the first network call can also be obtained by the first electronic device from the second server. The second server can send the account ID and the account password to the second electronic device. The second electronic device can display a first user interface, and the first user interface can display a first answer control and a first hang-up control. The second electronic device can receive a user operation on the first answer control, and connect to the second server based on the account ID and the 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 the account password of the first network call, the first electronic device and the second electronic device establish the first network call, and can transmit audio messages or transmit audio messages and images to each other through the first network call.

[0009] Through the method, the first electronic device can initiate a network call connection to other electronic devices without storing device information of the other electronic devices. After receiving a user request to play a network call, the first electronic device can send a request to establish a network call to the other electronic devices through the first server. The other electronic devices can apply for an account ID and an account password of the first network call, so as to realize the first network call between the first electronic device and the second electronic device. The first electronic device and the second electronic device can transmit audio messages or transmit audio messages and images to each other through the first network call.

[0010] In combination with the first aspect, in a possible implementation manner, the second electronic device is further configured to: establish a first session connection with the first electronic device; in response to receiving the account ID and the 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; and the first electronic device is further configured to: in response to the first message, display a second user interface, and the second user interface includes a second hang-up control and a call duration.

[0011] With reference to the first aspect, in a possible implementation manner, the first session connection is initiated by the second electronic device based on 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 a message to the first electronic device. Then, the second electronic device needs to establish the first session connection with the first electronic device. After the second electronic device connects to the second server based on the account ID and the 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, and the first message is used to inform the first electronic device that the second electronic device has connected to the second server, and the first electronic device needs to switch to display the second user interface. In this way, in the case that 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] With reference to the first aspect, in a possible implementation manner, the second electronic device is further configured to stop displaying the first user interface and start displaying a third user interface in response to receiving the account ID and the account password of the first network call sent by the second server, and the third user interface includes a third hang-up control and a call duration.

[0015] With reference to the first aspect, in a possible implementation manner, the system further includes a third electronic device, the third electronic device is logged in with a third user account, and the third user account is the same as or associated with the first user account; the first server is specifically configured to: in response to the first request, determine 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; and send a network call establishment request to the second electronic device and the third electronic device; the third electronic device is configured to display a fourth user interface in response to the network call establishment request, and the fourth user interface displays a second answer control and a fourth hang-up control; the second electronic device is further configured 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; and the third electronic device is further configured to stop displaying the fourth user interface in response to the second message.

[0016] In other embodiments, the second message can 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 the network call connection, the first electronic device cannot select a specific device to which the network call connection is initiated, and the first electronic device can send the network call establishment request to one or more devices logged in with the same account and 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 the network call connection with the first electronic device, the other electronic devices receiving the network call connection will stop prompting the user to answer the network call.

[0018] With reference to the first aspect, in a possible implementation manner, the second electronic device further includes: receiving the operation of the first hang-up control by the user, establishing a first session connection with the first electronic device; and sending a third message to the first electronic device through the first session connection. The first electronic device further includes: in response to the third message, displaying a fifth user interface, and the fifth user interface includes first indication information, and the first indication information is used to prompt that the user has refused to establish the network call.

[0019] The second server cannot send a message to the first electronic device, and after the second electronic device refuses to establish the 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 the message of refusing the call to the first electronic device, so that the first electronic device can prompt the user that the second electronic device has refused the network call.

[0020] With reference to the first aspect, in a possible implementation manner, the system further includes a third electronic device, and the third electronic device is logged in with a third user account, and the third user account is the same as or associated with the first user account. The second electronic device further includes: sending a fourth message to the first server. The first server further includes: sending the fourth message to the third electronic device. The third electronic device further includes: in response to the fourth message, stopping 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 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 can 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 the network call connection with the first electronic device, a message needs to be sent to the third electronic device to inform the third electronic device to stop displaying the network call request interface (that is, the fourth user interface).

[0024] With reference to the first aspect, in a possible implementation manner, the second electronic device further receives and responds to a second user operation to send a third request to the second server; the second server further generates an account ID and an account password of the second network call in response to the third request; and the second server further sends the account ID and the account password of the second network call to the first electronic device and the second electronic device, and the account ID and the 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.

[0025] The second user operation can be that the user initiates the network call connection to the first electronic device on the second electronic device. When the second electronic device initiates the network call connection, the second electronic device can select an object of the network call connection (for example, the user selects the first electronic device).

[0026] With reference to the first aspect, in a possible implementation manner, the second electronic device further establishes a second session connection with the first electronic device; the second electronic device further displays a sixth user interface in response to the second user operation, and the sixth user interface includes a fifth hang-up control; the first electronic device further displays a seventh user interface in response to the account ID and the account password of the second network call sent by the second server, and the seventh user interface includes a third answer control and a sixth hang-up control; the first electronic device further receives and responds to a user operation on the third answer control to send a fifth message to the second electronic device through the second session connection; and the second electronic device further displays an eighth user interface in response to the fifth message, and the eighth user interface includes a call duration and a seventh hang-up control.

[0027] When the second electronic device initiates the network call connection, the second electronic device further 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 a call-in-progress interface (that is, an eighth user interface).

[0028] With reference to the first aspect, in a possible implementation manner, the first electronic device further receives and responds to a user operation on the sixth hang-up control to send a sixth message to the second electronic device through the second session connection; and the second electronic device further displays a ninth user interface in response to the sixth message, and the ninth user interface includes second indication information for prompting that the user has refused to establish the network call.

[0029] When the second electronic device initiatively initiates the network call connection, the second electronic device also needs to initiatively establish a second session connection with the first electronic device. After the first electronic device rejects 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 rejected the network call.

[0030] With reference to 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 inter-device communication, the method comprising: displaying, by a second electronic device, a first user interface, the first user interface displaying 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 a first server, the network call request being sent by the first server after the first server receives a first request sent by a first electronic device and determines, based on an account ID of a first user account carried in the first request, that a second electronic device logs in a second user account, the first user account being a user account logged in on the first electronic device, the second user account being the same as or associated with the first user account; receiving, by the second electronic device, an operation of a user on the first answer control, and sending, by the second electronic device, a second request to a second server, the second request being used to instruct the second server to generate an account ID and an account password of a first network call and send the account ID and the account password of the first network call to the first electronic device and the second electronic device, the account ID and the account password of the first network call being used for the first electronic device and the second electronic device to establish the first network call.

[0032] With reference to the second aspect, in a possible implementation manner, after the second electronic device displays the first user interface, the method further comprises: establishing, by the second electronic device, a first session connection with the first electronic device; and in response to receiving the account ID and the account password of the first network call sent by the second server, sending, by the second electronic device, a first message to the first electronic device based on the first session connection, the first message being used to instruct the first electronic device to display a second user interface, the second user interface including a second hang-up control and a call duration.

[0033] With reference to the second aspect, in a possible implementation manner, the first session connection is established by the second electronic device initiatively connecting to the first electronic device based on device information of the first electronic device stored in the second electronic device.

[0034] In a possible implementation manner of the second aspect, the device information of the first electronic device comprises 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 a possible implementation manner of the second aspect, after the second electronic device receives the account ID and the account password of the first network call sent by the second server, the method further comprises: the second electronic device stops displaying the first user interface and starts displaying a third user interface, the third user interface comprising a third hang-up control and a call duration.

[0036] In a possible implementation manner of the second aspect, after the second electronic device displays the first user interface, the method further comprises: the second electronic device receives an operation of the user on the first hang-up control; in response to the operation on the first hang-up control, the second electronic device establishes a first session connection with the first electronic device; and the second electronic device sends a third message to the first electronic device through the first session, the third message being used to instruct the first electronic device to display a fifth user interface, the fifth user interface comprising first indication information, the first indication information being used to prompt the user that the network call has been rejected.

[0037] In a possible implementation manner of the second aspect, after the second electronic device receives the operation of the user on the first hang-up control, the method further comprises: the second electronic device sends a fourth message to the first server, the fourth message being used to instruct the first server to send a fourth message to the third electronic device, the fourth message being used to instruct the third electronic device to stop displaying a fourth user interface, the fourth interface being displayed by the third electronic device after receiving the network call request sent by the first server, the fourth user interface comprising a second answer control and a fourth hang-up control, the third electronic device being logged in with a third user account, the third user account being the same as or associated with the first user account.

[0038] In a possible implementation manner of the second aspect, the method further comprises: the second electronic device receives and responds to a second user operation, and sends a third request to the second server, the third request being used to instruct the second server to generate an account ID and an account password of a second network call, and send the account ID and the account password of the second network call to the first electronic device and the second electronic device, the account ID and the account password of the second network call being used for the first electronic device and the second electronic device to establish the second network call.

[0039] With reference to the second aspect, in a possible implementation manner, the method further includes: after the second electronic device receives and responds to the second user operation, the method further includes: the second electronic device establishing a second session connection with the first electronic device; displaying a sixth user interface in response to the second user operation, the sixth user interface including 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 the first electronic device receives a user operation on a third answer control in a seventh user interface, and the seventh user interface is displayed by the first electronic device in response to the second server sending an account ID and an account password of the second network call; in response to the fifth message, the second electronic device displays an eighth user interface, and the eighth user interface includes a call duration and a seventh hang-up control.

[0040] With reference to the second aspect, in a possible implementation manner, after the second electronic device displays the sixth user interface, the method further includes: the second electronic device receiving a sixth message sent by the first electronic device, wherein the sixth message is sent by the first electronic device after the first electronic device receives a user operation on the sixth hang-up control; in response to the sixth message, the second electronic device displays 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 network call has been rejected.

[0041] With reference to 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, and when the one or more processors execute the computer instructions, the second electronic device performs the device-to-device communication method provided in any possible implementation manner of the second aspect.

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

[0044] In a fifth aspect, the present application provides a computer readable storage medium, which includes instructions, and when the instructions run on a second electronic device, the second electronic device performs the device-to-device communication method provided in any possible implementation manner of the second aspect.

[0045] The beneficial effects of the second aspect to the fifth aspect can refer to the beneficial effects of the first aspect, which will not be repeated here. BRIEF DESCRIPTION OF DRAWINGS

[0046] FIG. 1A A system architecture diagram is provided for the present application;

[0047] FIG. 1B An interaction schematic diagram is provided for the present application;

[0048] FIGS. 2A-2L A UI schematic diagram showing that the electronic device 100 calls the smart watch 200 is shown;

[0049] FIG. 3 A method schematic diagram showing that the electronic device 100 and the smart watch 200 establish a trusted relationship is shown;

[0050] FIG. 4 A method schematic diagram showing that the electronic device 100 and the smart watch 200 establish a session connection is shown;

[0051] FIG. 5 A method schematic diagram showing that the electronic device 100 and the smart watch 200 successfully establish an RTC call connection is shown;

[0052] FIG. 6 A method schematic diagram showing that the electronic device 100 and the smart watch 200 do not establish an RTC call connection is shown;

[0053] FIG. 7 A method schematic diagram showing that the electronic device 100 and the smart watch 200 do not establish an RTC call connection is shown;

[0054] FIG. 8 A method schematic diagram showing that the electronic device 100 and the smart watch 200 do not establish an RTC call connection is shown;

[0055] FIGS. 9A-9K A UI schematic diagram showing that the smart watch 200 calls the electronic device 100 is shown;

[0056] FIG. 10 A method schematic diagram showing that the smart watch 200 sends an RTC call request to a device with the same account or a different account and establishes an association relationship through a push server is shown;

[0057] FIG. 11 A method schematic diagram showing that the smart watch 200 and the electronic device 100 establish an RTC call is shown;

[0058] FIG. 12 A method schematic diagram showing that the smart watch 200 and the electronic device 100 do not establish an RTC call connection is shown;

[0059] FIG. 13 Another method diagram for the smart watch 200 and the electronic device 100 not establishing an RTC call connection is shown;

[0060] FIG. 14 Another method diagram for the smart watch 200 and the electronic device 100 not establishing an RTC call connection is shown;

[0061] FIG. 15 A method flow diagram for inter-device communication is provided for the present application;

[0062] FIG. 16 A structural diagram of an electronic device is shown;

[0063] FIG. 17 A software structure block diagram of the electronic device 100 of the embodiment of the present application. DETAILED DESCRIPTION

[0064] The technical solutions in the embodiments of the present application will be described clearly and thoroughly below with reference to the drawings. In the description of the embodiments of the present application, unless otherwise specified, " / " represents the meaning of or, for example, A / B can represent A or B; the "and / or" in the text only describes the association relationship of the associated objects, which means that there can be three relationships, for example, A and / or B, which means that there are three cases of A alone, A and B together, and B alone. In addition, in the description of the embodiments of the present application, "multiple" means two or more than two.

[0065] Hereinafter, the terms "first" and "second" are only for descriptive purposes, and cannot be understood as implying or suggesting relative importance or implicitly indicating the number of indicated technical features. Therefore, the features defined with "first" and "second" can explicitly or implicitly include one or more features, and in the description of the embodiments of the present application, unless otherwise specified, the meaning of "multiple" is two or more than two.

[0066] The term "user interface (UI)" in the following embodiments of the present application is a medium interface for interaction and information exchange between an application program or an operating system and a user, which realizes the conversion between the internal form of information and the form that the user can accept. The commonly used form of user interface is graphic 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, icon, button, menu, tab, text box, dialog box, status bar, navigation bar, Widget, etc. displayed in the display screen of the electronic device.

[0067] FIG. 1A A system architecture diagram is provided for the present application.

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

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

[0070] The network call connection can be an RTC call connection. The following embodiments of the present application take the network call connection as an example of the RTC call connection. The network call connection can 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 can initiate an RTC call request to the smart watch 200. After receiving the RTC call request sent by the electronic device 100, the smart watch 200 can establish an RTC call connection with the electronic device 100 after obtaining the user's consent. Specifically, the electronic device 100 can send an RTC call request to the RTC server. After receiving the RTC call request sent by the electronic device 100, the RTC server can generate a conference ID and a conference password of the RTC call, and send the conference ID and the conference password of the RTC call to the electronic device 100. Then, the RTC server can also send the conference ID and the conference password of the RTC call to the smart watch 200. After receiving the conference ID and the conference password of the RTC call, the electronic device 100 and the smart watch 200 can establish an RTC call connection based on the conference ID and the conference password of the RTC call.

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

[0073] Next, the device-to-device communication method provided by the present application will be explained and described in combination with the scenarios of calling the smart watch 200 by the electronic device 100 and calling the electronic device 100 by the smart watch 200, respectively.

[0074] FIG. 1B An interaction diagram is provided in the present application.

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

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

[0077] The session connection and the 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 can also provide verification device and remote control services for the electronic device 100.

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

[0082] The responsibilities of each server can be referred to the description in the subsequent embodiments, which will not be repeated 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] FIGS. 2A-2L The UI schematic diagram of 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] FIG. 2A The main interface 210 of the electronic device 100 is shown. The main interface 210 includes icons of a plurality of 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 health application, an icon of a memo application, an icon of a calendar application, an icon of a life service application, an icon of the first application, an icon of a camera application, an icon of a contacts application, an icon of a phone application, and an icon of an information application, and the like. The main interface 210 also shows a power indicator, a weather indicator, a date indicator, a network signal indicator, a page indicator, and the like.

[0088] As shown in FIG. 2B, the electronic device 100 can receive an input operation (e.g., a single click) of a user on the icon of the first application, and in response to the input operation of the user, the electronic device 100 can display the user interface 220 shown in FIG. 2C. FIG. 2A FIG. 2B As shown in FIG. 2B, the electronic device 100 can receive an input operation (e.g., a single click) of a user on the icon of the first application, and in response to the input operation of the user, the electronic device 100 can display the user interface 220 shown in FIG. 2C.

[0089] As shown in FIG. 2B, the electronic device 100 can receive an input operation (e.g., a single click) of a user on the icon of the first application, and in response to the input operation of the user, the electronic device 100 can display the user interface 220 shown in FIG. 2C. FIG. 2B As shown in FIG. 2B, the electronic device 100 can receive an input operation (e.g., a single click) of a user on the icon of the first application, and in response to the input operation of the user, the electronic device 100 can display the user interface 220 shown in FIG. 2C.

[0090] ​Optionally, one or more smart devices and smart devices shown in the user interface 220 can be associated with the same user account, or can be associated with different user accounts, but the different user accounts are associated with each other.

[0091] As FIG. 2B described above, the electronic device 100 can receive an input operation (e.g., a single click) of a user for a device icon of the Honor children watch, and in response to the input operation of the user, the electronic device 100 can display the user interface 230 shown in FIG. 23. The user interface 230 is a details interface of the Honor children watch. FIG. 2C

[0092] A plurality of options are shown in the user interface 230, such as a micro-chat option, a video call option, a phone option, a watch management option, a watch address book option, a call record option, an alarm clock option, a photo album option, a step counting option, and an application management option, etc.

[0093] Among them, the user can send a message to the smart watch 200 through the micro-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 phone option.

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

[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 record of the smart watch 200 in the recent period of time through the call record option.

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

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

[0101] The user can view the motion details of the smart watch 200, such as the number of steps counted and the heat consumed, through the step counting option.

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

[0103] ​Electronic device 100 can receive user input (e.g., click) on the video call option in user interface 230, and in response to the user's input, electronic device 100 can send a video call request to smartwatch 200.

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

[0105] Optionally, electronic device 100 can also establish a network voice call with smartwatch 200. Specifically, after receiving the user's input regarding the video call option, electronic device 100 can prompt the user to initiate either a network video call or a network voice call. The user can select a network voice call and then send a request to establish a network voice call to smartwatch 200. Alternatively, the user can select a network voice call and then send a request to establish a network voice call to smartwatch 200. In other possible implementations, after smartwatch 200 receives a video call request, electronic device 100 can establish a network video call with smartwatch 200. After establishing a network video call, electronic device 100 can then receive user input to switch the network video call to a network voice call.

[0106] For example, such as FIG. 2C As shown, the electronic device 100 can receive user input (e.g., a click) for video call options in the user interface 230, and in response to the user's input, the electronic device 100 can display... FIG. 2D The user interface 2310 is shown. User interface 2310 may include a control for switching to a voice call and a hang-up control. User interface 2310 may be a network call request interface. The user can switch from a video call to a voice call by using the voice call control. The user can also stop sending video call requests to the smartwatch 200 by using the hang-up control.

[0107] Similarly, after the electronic device 100 can receive user input on the video call option in the user interface 230, the electronic device 100 can send a video call request to the smartwatch 200.

[0108] In some embodiments, if the smartwatch 200 is online, the smartwatch 200 can receive video call requests sent by the electronic device 100.

[0109] Optionally, after receiving a video call request from electronic device 100, smartwatch 200 can display... FIG. 2EThe user interface 240 shown is a network call to be answered interface. The user interface 240 can include a hang up control and an answer control. The user can reject the network video call with the electronic device 100 through the hang up control. The user can also establish the network video call with the electronic device 100 through the answer control.

[0110] As shown, the smart watch 200 can receive the user's input operation (e.g., a single click) on the answer control in the user interface 240. In response to the user's input operation, the electronic device 100 can display a user interface 250, as shown. FIG. 2E The user interface 250 shown is a network call answered interface. The user interface 250 can include a hang up control. The user can end the network video call with the electronic device 100 through the hang up control. FIG. 2F The user interface 250 shown is a network call answered interface. The user interface 250 can include a hang up control. The user can end the network video call with the electronic device 100 through the hang up control.

[0111] Likewise, after the smart watch 200 receives the user's input operation on the answer control in the user interface 240, i.e., the smart watch 200 agrees to establish the 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] As shown, the smart watch 200 can receive the user's input operation (e.g., a single click) on the answer control in the user interface 240. In response to the user's input operation, the electronic device 100 can display a user interface 250, as shown. FIG. 2G The user interface 250 shown is a network call answered interface. The user interface 250 can include a hang up control. The user can end the network video call with the electronic device 100 through the hang up control. FIG. 2GThe illustrated user interface 260 is a network call answered interface. The user interface 260 can include a hang-up option, a switch to network voice call option, a switch front and back camera option, a close camera of the electronic device 100 option, a mute option, a speaker option, and a shrink user interface 260 option, etc. 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 through the switch to network voice call option, that is, the network voice call option cannot display the images collected by the cameras of both parties. The user can also switch the electronic device 100 from the front camera to the back camera through the switch front and back camera option, display the image collected by the back camera of the electronic device 100, and send the image collected by the back camera of the electronic device 100 to the smart watch 200. The user can also close the camera of the electronic device 100 through the close camera of the electronic device 100 option, so that the electronic device 100 stops collecting images through the front camera, stops displaying the images collected by the front camera of the electronic device 100 in the user interface 260, and also stops sending the images collected by the front camera of the electronic device 100 to the smart watch 200. The user can also mute through the mute option, so that the electronic device 100 closes the microphone, stops collecting audio through the microphone, and also stops sending the audio collected by the microphone of the electronic device 100 to the smart watch 200. The user can also play the audio received by the smart watch 200 through the speaker of the electronic device 100 through the speaker option. The user can also shrink the display user interface 260 through the shrink user interface 260 option. After the electronic device 100 exits the first application, the electronic device 100 can also display the shrunk user interface 260 in a suspended manner.

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

[0114] For example, as FIG. 2H illustrated, the smart watch 200 can receive the input operation (such as a single click) of the user for the hang-up control in the user interface 240. In response to the input operation of the user, the smart watch 200 can stop displaying the user interface 240. After the smart watch 200 receives the input operation of the user for the hang-up control in the user interface 240, the smart watch 200 can send a message to the electronic device 100 to inform the electronic device 100 that the smart watch 200 has refused the network video call with the electronic device 100.

[0115] After the electronic device 100 receives the message sent by the smart watch 200, the electronic device 100 can displayFIG. 2I The user interface 270 shown in FIG. 2B shows a prompt message "Watch has rejected your video call request". The prompt message is used to prompt the user of the electronic device 100 that the user of the smart watch 200 rejects to establish the network video call.

[0116] After the electronic device 100 displays the user interface 270, the electronic device 100 can continue to display FIG. 2C the user interface 230 shown in FIG. 2A.

[0117] Optionally, after the smart watch 200 receives the video call request sent by the electronic device 100, if the smart watch 200 is in a network video call or a network voice call with another electronic device, the smart watch 200 can send a message to the electronic device 100, the message is used to instruct the electronic device 100 that the smart watch 200 is in a network video call or a network voice call with another electronic device, please try later.

[0118] After the electronic device 100 receives the message sent by the smart watch 200, the electronic device 100 can display FIG. 2J the user interface 280 shown in FIG. 2C, the user interface 280 shows a prompt message "Watch is busy in a call". The prompt message is used to prompt the user of the electronic device 100 that the user of the smart watch 200 is in a network video call or a network voice call with another electronic device.

[0119] After the electronic device 100 displays the user interface 280, the electronic device 100 can continue to display FIG. 2C the user interface 230 shown in FIG. 2A.

[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 the feedback message sent by the smart watch 200 within a certain time, for example, the message of receiving the network video call request or the message of rejecting the network video call request or the busy message, etc., the electronic device 100 can stop sending the network video call request to the smart watch 200, and display FIG. 2K the user interface 290 shown in FIG. 2D. The user interface 290 shows a prompt message "Watch is not answered, please try later". The prompt message is used to prompt the user of the electronic device 100 that the smart watch 200 is not responsive.

[0121] After the electronic device 100 displays the user interface 290, the electronic device 100 can continue to display FIG. 2C the user interface 230 shown in FIG. 2A.

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

[0123] In the case that the electronic device 100 cannot send the video call request to the smart watch 200, the electronic device 100 can display FIG. 2L the user interface 2910 as shown. The user interface 2910 shows the prompt information "watch is offline, please try later". The prompt information is used to prompt the user of the electronic device 100 that the smart watch 200 is offline and cannot establish a network video call or a network audio call with the smart watch 200 in offline state.

[0124] After the electronic device 100 displays the user interface 2910, the electronic device 100 can continue to display FIG. 2C the user interface 230 as 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 establishing a trusted relationship, the electronic device 100 and the smart watch 200 establishing a session connection, and the electronic device 100 and the smart watch 200 establishing an RTC call connection.

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

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

[0129] S301, the smart watch 200 establishes a connection with the device server.

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

[0131] The device server can be a server for authenticating and verifying the device. The device server can also send control messages to the smart watch 200.

[0132] Optionally, after the smart watch 200 is first turned on, the smart watch 200 can send an authentication and verification request to the device server. After the device server authenticates and verifies, the device server marks the smart watch 200 as a legal 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 authentication and certification pass, the smart watch 200 can send a request for establishing an MQTT connection to the device server. After the device server receives the request for establishing an MQTT connection sent by the smart watch 200, the device server can send a confirmation of establishing a connection request to the smart watch 200 after confirmation. After the smart watch 200 receives the confirmation of establishing a connection request 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 in the user interface 220 shown in the drawing. The online or offline state of the smart watch 200 can be displayed in the user interface 220. FIG. 2B

[0135] Optionally, the smart watch 200 also needs to send the device information of the smart watch 200 to the device server. 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 (MAC) address of the smart watch 200, the public key of the smart watch 200, the device type of the smart watch 200, and the like. The device unique identifier of different devices is different.

[0136] The smart watch 200 internally stores a pair of public and private keys. 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 with the electronic device 100.

[0137] The device server can store device information of multiple devices. For example, the device information of the electronic device 100 is stored, which includes but is not limited to one or more of the following: the device unique identifier of the electronic device 100, the IP address of the electronic device 100, the MAC address of the electronic device 100, the public key of the electronic device 100, the device type of the electronic device 100, and the like.

[0138] S302, the electronic device 100 establishes a connection with the device server.

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

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

[0141] Optionally, after the electronic device 100 receives the input operation (for example, a single click) of the user for the first application, the electronic device 100 displays the user interface 220 shown in the figure. FIG. 2B After displaying the user interface 220 shown in the figure, the electronic device 100 can send a request for establishing a long connection to the device server and establish a long connection with the device server.

[0142] Optionally, the electronic device 100 can also not establish a long connection with the device server. For example, when the electronic device 100 does not open the first application, the electronic device 100 can not establish a long connection with the device server.

[0143] It should be noted that the above long connection is not limited to the MQTT connection, but can also be other connection modes, which are not limited in the present application.

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

[0145] Optionally, the device server can store the device information of different devices when receiving the device information of different devices. When maintaining the device information of different devices, the device server can generate 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 can include but is not limited to one or more of the following: a device unique identifier of the device, an IP address of the device, a MAC address of the device, a cloud device ID of the device, a public key of the device, etc.

[0147] For example, the device information of the smart watch 200 maintained by the device server can include but is not limited to one or more of the following: a device unique identifier of the smart watch 200, an IP address of the smart watch 200, a MAC address of the smart watch 200, a cloud device ID of the smart watch 200, a public key of the smart watch 200, a 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, after the electronic device 100 adds the smart watch 200 to the user interface 220 shown in the figure, 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. FIG. 2B

[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 the device information of the electronic device 100 inside, and the device information of the electronic device 100 includes but is not limited to one or more of the following: the device unique identifier of the electronic device 100, the Internet Protocol (IP) address of the electronic device 100, the MAC address of the electronic device 100, the public key of the electronic device 100, the device type of the electronic device 100, and the like.

[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, the device server can store the device information of different devices when receiving the device information of different devices. When maintaining the device information of different devices, the device server generates the node ID of each device. The node ID of different devices. The device server can uniquely determine the target device based on the node ID.

[0154] Optionally, after the electronic device 100 adds the smart watch 200 to the user interface 220 shown in the figure, the electronic device 100 can generate the node ID of the smart watch 200. FIG. 2B

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

[0156] For example, the device information of the smart watch 200 maintained by the device server can 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, and the like.​​

[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] In the case that the electronic device 100 and the smart watch 200 do not complete 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 can be the process shown in S304-S309.

[0160] In some embodiments, the device information of the device can also include other information, such as the manufacturer of the device, the production date of the device, and the like. The present application does not limit this.

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

[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 encrypted parameter to the device server.

[0164] S307, the device server sends the first encrypted parameter to the smart watch 200.

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

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

[0167] S308, the smart watch 200 decrypts the first encrypted 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 encrypted 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 encrypted parameter based on the private key of the smart watch 200.

[0169] If the smart watch 200 can successfully encrypt the first encrypted parameter based on the private key of the smart watch 200 to obtain the first parameter, it can prove that the electronic device 100 and the smart watch 200 are trusted devices.

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

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

[0172] Specifically, the smart watch 200 can randomly generate a second parameter, encrypt the second parameter by using the private key of the smart watch 200 to 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 by using the public key of the smart watch 200 to obtain the second parameter, it indicates that the electronic device 100 and the smart watch 200 are trusted devices. If the electronic device 100 cannot decrypt the second encrypted parameter by using the public key of the smart watch 200 to obtain the second parameter, it indicates that the electronic device 100 and the smart watch 200 are not trusted devices.

[0173] Optionally, the electronic device 100 can also initiate the trusted authentication process to the smart watch 200 at the same time, and the smart watch 200 can also actively initiate the 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, the trusted device electronic device 100 and the smart watch 200 are trusted devices.

[0175] Based on the description in S308, if 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] If 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 or a network voice call with the smart watch 200.

[0177] Optionally, in the case of determining that the electronic device 100 and the smart watch 200 are trusted devices, in order to ensure the security of the subsequent communication between the electronic device 100 and the smart watch 200, the electronic device 100 and the smart watch 200 can respectively 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 and then send it to the opposite device, thereby ensuring the security of the communication between the electronic device 100 and the smart watch 200.

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

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

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

[0181] The first secret key and the second secret key can be mutually encrypted and decrypted. For example, the second secret key can decrypt the data encrypted by the first secret key, and the first secret key can decrypt the data encrypted by the second secret key.

[0182] Optionally, FIG. 3 In the embodiment, the electronic device 100 can include a connection networking server, and the smart watch 200 can include a connection networking client. FIG. 3 In the embodiment, the interaction between the electronic device 100 and the device server can be the interaction between the connection networking server on the electronic device 100 and the device server. FIG. 3 In the embodiment, the interaction between the smart watch 200 and the device server can be the interaction between the connection networking client on the smart watch 200 and the device server. FIG. 3 In the embodiment, the interaction between the electronic device 100 and the smart watch 200 can be the interaction between the connection networking server on the electronic device 100 and the connection networking client on the smart watch 200. FIG. 3 The connection networking server and the connection networking client are not shown in the figure.

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

[0184] After the electronic device 100 and the smartwatch 200 mutually recognize and trust each other, the electronic device 100 can establish a second session connection with the smartwatch 200. This facilitates communication between the electronic device 100 and the smartwatch 200 via the second session connection.

[0185] FIG. 4 A schematic diagram illustrating the method for establishing a session connection between electronic device 100 and smartwatch 200 is shown.

[0186] The electronic device 100 may include a first application and a network connection server, while the smartwatch 200 may include a network connection client and a second application.

[0187] In some embodiments, the connection networking server may be a functional module in the first application, or it 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 it may not be a functional module in the second application.

[0189] In some embodiments, the connection networking server may be referred to as the MagicLink SVC module.

[0190] In some embodiments, the networking client may be referred to as a MagicLink SDK module.

[0191] The first and second applications can be the same or similar, both enabling network video or audio calls between devices.

[0192] S401, The first application stores device information for multiple devices.

[0193] Depend on FIG. 3 As can be seen from the embodiments, the first application stores device information of multiple devices, such as device information of smartwatch 200.

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

[0195] The device information of the smartwatch 200 includes, but is not limited to, the smartwatch 200's unique device identifier, the smartwatch 200's IP address, the smartwatch 200's MAC address, the smartwatch 200's cloud device ID, the smartwatch 200's public key, and the smartwatch 200's node ID.

[0196] S402. The first application displays the first user interface, which displays device icons of multiple devices, and these multiple devices have established a relationship.

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

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

[0199] The first user interface can be FIG. 2B The user interface 220 shown. Device icons for multiple devices may include device icons for smart speakers, smart TVs, smart desk lamps, air purifiers, cameras, air conditioners, tablets, curtains, smartwatches 200, etc.

[0200] Multiple devices shown in user interface 220 can be associated with each other. For example, they can be associated with the same user account, or they can be associated with different user accounts, but the different user accounts are associated with each other.

[0201] S403, The first application receives the user's operation on the device icon of the smartwatch 200 in the first user interface and displays the control interface of the smartwatch 200.

[0202] For example, the smartwatch 200 could be FIG. 2B The Honor children's watch shown.

[0203] For example, refer to FIG. 2B As described in the embodiments, the first application can receive and respond to user input operations on the device icon of the Honor children's watch in the user interface 220, and the first application can display... FIG. 2C The user interface 230 shown can be referred to as the control interface of the smartwatch 200. The control interface of the smartwatch 200 includes multiple options, such as WeChat options, video call options, phone options, watch management options, watch contacts options, call log options, alarm clock options, photo album options, pedometer options, and application management options.

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

[0205] S405. The network server sends a request to the device server to establish a session connection.

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

[0207] S407. The client in the connected network sends an acknowledgment 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, the electronic device 100 can actively send a session connection establishment request to the smart watch 200. FIG. 2C As shown in the user interface 230, the electronic device 100 can actively send a session connection establishment request 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 can actively send a session connection establishment request 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 the user interface 230, the session connection between the first application and the second application is disconnected. FIG. 2C

[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. 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 can be carried in the session connection establishment request sent to the connection networking server. In other possible implementations, the cloud device ID of the smart watch 200 can also be sent to the connection networking server independently of the session connection establishment request. The present application does not limit this.

[0213] Optionally, the first application also needs to determine 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 session connection establishment request 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 session connection establishment request. The present application does not limit this.

[0214] In the embodiments 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 independently of the session connection establishment request.

[0215] ​The connection networking server can send a session connection establishment request to the device server. After receiving the session connection establishment request, the device server can obtain the cloud device ID of the smart watch 200 and the cloud device ID of the electronic device 100. The device server can obtain the IP address or MAC address of the smart watch 200 based on the cloud device ID of the smart watch 200, and 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 server in the electronic device 100, the device server 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 establishment of the session connection to the second application to inform the second application that the session connection has been established.

[0217] Optionally, in addition to sending the 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 a possible implementation, the cloud device ID of the electronic device 100 can be sent to the connection networking client in the session connection establishment request. In other possible implementations, the cloud device ID of the electronic device 100 can also be sent to the connection networking client independently of the session connection establishment request. The present application does not limit this.

[0219] S408, the connection networking client sends a confirmation of the establishment of the session connection to the device server.

[0220] S409, the device server sends a confirmation of the establishment of the session connection to the connection networking server.

[0221] S410, the connection networking server sends a confirmation of the establishment of the session connection to the first application.

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

[0223] Optionally, in addition to sending the confirmation of the establishment of 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 a possible implementation, the cloud device ID of the electronic device 100 can be carried in the confirmation of establishing the session connection sent to the device server. In other possible implementations, the cloud device ID of the electronic device 100 can also be independent of the confirmation of establishing the session connection sent to the device server. The present application does not limit this.

[0225] After the device server receives the session connection established sent by the connection networking client, the device server can obtain the cloud device ID of the electronic device 100. After the device server obtains the cloud device ID of the electronic device 100, the device server can send the confirmation of establishing the session connection 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 sends the confirmation of establishing the session connection to the first application in the electronic device 100.

[0227] Optionally, the device server only needs to send the confirmation of establishing the session connection to the connection networking service end in the electronic device 100, and the cloud device ID of the electronic device 100 can not be sent to the connection networking service end in the electronic device 100. The cloud device ID of the electronic device 100 can also be sent to the connection networking service end in the electronic device 100, and the present 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 can 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 the 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 can send messages through the first session connection.

[0233] Optionally, as known from S309, the electronic device 100 and the smart watch 200 further negotiate the first secret key and the second secret key. When the electronic device 100 and the smart watch 200 send messages through the session connection, the electronic device 100 and the smart watch 200 can encrypt the data through the first secret key and the second secret key obtained through negotiation and send the data to the opposite end application through the session connection, so as to ensure the reliability of data transmission.

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

[0235] FIG. 5 A method schematic diagram for successfully establishing an RTC call connection by the electronic device 100 and the smart watch 200 is shown.

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

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

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

[0239] In response to the input operation of the user for the video call option in the user interface 230, the first application displays a network call request interface. The network call request interface can be the user interface 2310 shown in FIG. 13C. FIG. 2D

[0240] In response to the input operation of the user for the video call option in the user interface 230, the electronic device 100 can 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 can also establish a network voice call with the smart watch 200. Specifically, after receiving the input operation of the user for the video call option, the first application can prompt the user to initiate a network video call or a network voice call. The user can send a request for establishing a network voice call to the smart watch 200 after selecting the network voice call. The user can also send a request for establishing a network voice call to the smart watch 200 after selecting the network voice call. In other possible implementations, 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. After the electronic device 100 and the smart watch 200 establish the network video call, the electronic device 100 can receive the user operation to switch the network video call to a network voice call.

[0243] S503, the first application sends a request for establishing an RTC call to an RTC server.

[0244] In response to the first application receiving the input operation of the user for the first option, the first application can send a request for establishing an RTC call to the RTC server.

[0245] The RTC server is a server for establishing an inter-device RTC call.

[0246] S504, the RTC server generates an account ID and an account password of a second RTC call.

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

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

[0249] S505, the RTC server sends the account ID and the 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 the account password of the second RTC call.

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

[0252] After receiving the account ID and the 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 the 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 account 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 can communicate with each other, and the device server and the service server can be the same server or different servers, which are not limited in the present application.

[0255] The device information of the electronic device 100 can include, but is not limited to, the device type of the electronic device 100, the manufacturer of the electronic device 100, and the like.

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

[0257] S508, the service server needs to confirm whether the device information of the electronic device 100 and the smart watch 200 is verified.

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

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

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

[0261] In the case that the device information of the electronic device 100 and the smart watch 200 is verified, S509 is executed.

[0262] In the case that the device information of the electronic device 100 and the smart watch 200 is not verified, the process ends.

[0263] S509, the service server sends the RTC call request (the account ID and account password of the second RTC call) to the device server.

[0264] S510, the device server can send the RTC call request (the account ID and account password of the second RTC call) to the connection networking client.

[0265] S511, the connection networking client sends the RTC call request (the account ID and account password of the second RTC call) to the second application.

[0266] Optionally, in the case that the business server confirms that the device information of the electronic device 100 and the smart watch 200 is verified, the business server sends an RTC call establishment request to the device server, and the business server also sends the account ID and the 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 the account password of the second RTC call to the connection networking client.

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

[0269] In a possible implementation, the account ID and the account password of the second RTC call can be sent to the second application in the RTC call establishment request. In other possible implementations, the account ID and the account password of the second RTC call can be sent to the second application independently of the RTC call establishment request. The 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 RTC call establishment request to the second application. In the case that the business server determines that the device information of the electronic device 100 and the smart watch 200 is verified, the business server can further send a verification success notification to the electronic device 100. In response to the verification success notification sent by the business server, the first application can send the account ID and the 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 also does not need to send the RTC call establishment request to the second application. In the case that the business server determines that the device information of the electronic device 100 and the smart watch 200 is verified, the business server can further send a verification success notification to the electronic device 100. In response to the verification success notification sent by the business server, the first application can send the RTC call establishment request, the account ID and the account password of the second RTC call to the second application through the second session connection.

[0272] Optionally, after receiving the RTC call establishment request, the second application can send a receiving success message to the device server and the business server through the connection networking client, to feed back to the business server that the second application has received the RTC call establishment request.

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

[0274] After receiving the request to establish the 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 the RTC call.

[0275] For example, after receiving the request to establish the RTC call, the second application can display the user interface 240 as shown in FIG. 2E The user interface 240 is a network call waiting to be answered interface. The user interface 240 can include a hang-up control and an answer control. The user can reject the network video call with the electronic device 100 through the hang-up control. The user can also establish the network video call with the electronic device 100 through the answer control.

[0276] S513, the second application receives the operation of the user to answer the call.

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

[0278] For example, as shown in FIG. 2E The smart watch 200 can receive the input operation (e.g., single click) of the user to the answer control in the user interface 240. In response to the input operation of the user, the electronic device 100 can display the user interface 250 as shown in FIG. 2F The user interface 250 is a network call answered interface. The user interface 250 can include a hang-up control. 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 the 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 the account password of the second RTC call. The first application can communicate with the RTC server.

[0281] S515, the second application sends an answer success message to the first application through the second session connection.

[0282] After connecting to the RTC server, the second application can notify the first application that the second application has successfully connected to the RTC server.

[0283] The second application can send a call-accepted 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, and the first application can switch to the network call call-accepted interface to avoid the first application still staying in the network call call-waiting interface.

[0284] In other embodiments, the second application and the first application have both connected to the RTC server, and the second application can also send the call-accepted message to the first application through the RTC server, which is not limited in the present application.

[0285] S516, in response to the call-accepted message, the first application switches from the network call call-waiting interface to the network call call-accepted interface.

[0286] In response to the call-accepted message sent by the second application through the second session, the first application can switch from the network call call-waiting interface to the network call call-accepted interface.

[0287] The network call call-accepted interface can be FIG. 2G the user interface 260 shown in FIG. 2.

[0288] For example, the first application can display FIG. 2GThe illustrated user interface 260 is a network call answered interface. The user interface 260 can include a hang-up option, a switch to network voice call option, a switch front and back camera option, a close camera of the electronic device 100 option, a mute option, a speaker option, and a shrink user interface 260 option, etc. 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 through the switch to network voice call option, that is, the network voice call option cannot display the images collected by the cameras of both parties. The user can also switch the electronic device 100 from the front camera to the back camera through the switch front and back camera option, display the image collected by the back camera of the electronic device 100, and send the image collected by the back camera of the electronic device 100 to the smart watch 200. The user can also close the camera of the electronic device 100 through the close camera of the electronic device 100 option, so that the electronic device 100 stops collecting images through the front camera, stops displaying the images collected by the front camera of the electronic device 100 in the user interface 260, and also stops sending the images collected by the front camera of the electronic device 100 to the smart watch 200. The user can also mute through the mute option, so that the electronic device 100 closes the microphone, stops collecting audio through the microphone, and also stops sending the audio collected by the microphone of the electronic device 100 to the smart watch 200. The user can also play the audio received by the smart watch 200 through the speaker through the speaker option. The user can also shrink the display user interface 260 through the shrink user interface 260 option. After the first application exits the first application, the electronic device 100 can also display the shrunk user interface 260 in a suspended state.

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

[0290] After the first application and the second application connect to the RTC server based on the account ID and the 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 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 of establishing the RTC call, but the smart watch 200 refuses to establish the RTC call. The smart watch 200 can 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] FIG. 6 A method schematic diagram of the electronic device 100 and the smart watch 200 not establishing the RTC call connection is shown.

[0293] For FIG. 6 The description of S601-S612 in the embodiments can refer to the description of S501-S512 in the embodiments. FIG. 5 The description of S501-S512 in the embodiments, the present application will not repeat here.

[0294] S613, the second application receives the user's operation of refusing the call.

[0295] As FIG. 2H shown, after the smart watch 200 receives the request of establishing the RTC call, the smart watch 200 can display the user interface 240 shown in FIG. 2E .

[0296] When the user of the smart watch 200 refuses to establish the RTC call, the smart watch 200 can receive the user's input operation (such as single click) to the hang-up control in the user interface 240. In response to the user's input operation, the smart watch 200 can stop displaying the user interface 240.

[0297] S614, the second application sends a refuse call message to the first application through the second session connection.

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

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

[0300] The refuse call interface can be the user interface 270 shown in FIG. 2I .

[0301] After the electronic device 100 receives the message sent by the smart watch 200, the electronic device 100 can display the user interface 270 shown in FIG. 2IThe user interface 270 shown displays the message "The watch has rejected your video call request." This message is used to inform the user of electronic device 100 that the user of smartwatch 200 has declined to establish a network video call.

[0302] After the electronic device 100 displays the call rejection interface, the electronic device 100 may continue to display... FIG. 2C The user interface 230 shown.

[0303] In some embodiments, if the user of the smartwatch 200 does not see the RTC call request in a timely manner after receiving it, and the electronic device 100 does not receive a response message (such as a call rejection message, a call answer message, or a busy signal) from the smartwatch 200 within a first time period, the electronic device 100 may prompt the user that the other party has paused the call and cannot be answered.

[0304] FIG. 7 This diagram illustrates another method by which an electronic device 100 and a smartwatch 200 fail to establish an RTC call connection.

[0305] for FIG. 7 The description of S701-S712 in the embodiment can be found in the following reference. FIG. 5 The descriptions of S501-S512 in the embodiments will not be repeated here.

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

[0307] Optionally, the unanswered interface can be... FIG. 2K The user interface shown is 290.

[0308] After electronic device 100 sends a network video call request to smartwatch 200, if electronic device 100 does not receive a feedback message from smartwatch 200 within the first time period, such as a message accepting or rejecting the network video call request, or a busy signal, electronic device 100 can stop sending network video call requests to smartwatch 200 and display... FIG. 2K The user interface 290 is shown. User interface 290 displays the message "Watch not answering, please try again later." This message is used to inform the user of electronic device 100 that the smartwatch 200 is not responding.

[0309] Displayed on electronic device 100 FIG. 2K After the user interface 290 shown, the electronic device 100 can continue to display... FIG. 2C The user interface 230 shown.

[0310] S714, if no one answers the call within 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 a user operation within the first time period, the second application in the smart watch 200 can stop prompting the user to answer the call. For example, the second application can stop displaying FIG. 2E the user interface 240 shown.

[0312] Optionally, S713 and S714 can be executed simultaneously, or S714 is executed before S713, or S714 is 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 establishment of the RTC call request, 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, the message is used to instruct the electronic device 100 that the smart watch 200 is in an RTC call with another device.

[0314] In other embodiments, the smart watch 200 can also establish an RTC call with multiple devices at the same time, which is not limited in the present application.

[0315] FIG. 8 Another method for establishing an RTC call connection between the electronic device 100 and the smart watch 200 is shown.

[0316] For FIG. 8 the description of S801-S811 in the embodiment, please refer to FIG. 5 the description of S501-S511 in the embodiment, which will not be repeated here.

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

[0318] When the second application in the smart watch 200 is in an RTC call with another device, the second application in the smart watch 200 receives an establishment of an RTC call request 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, the message is used to instruct the electronic device 100 that the smart watch 200 is in an RTC call with another device.

[0319] S813, in response to the busy line message, the first application is switched from the network call request interface to the busy line interface.

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

[0321] After the first application in electronic device 100 receives a busy message from the second application in smartwatch 200 via a second session connection, electronic device 100 can display... FIG. 2J The user interface 280 displays the message "Watch busy". This message is used to inform the user of electronic device 100 or smartwatch 200 that smartwatch 200 is making a video or voice call with another device.

[0322] Smartwatch 200 calls electronic device 100.

[0323] First, let's introduce the UI implementation of electronic device 100 calling smartwatch 200.

[0324] FIGS. 9A-9K A UI diagram showing how a smartwatch 200 calls an electronic device 100 is shown.

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

[0326] FIG. 9A The user interface 910 of the second application in the smartwatch 200 is shown. The user interface 910 includes a chat option and a call option. Users can send messages to other devices via the chat option. Users can also make VoIP calls to other devices via the call option.

[0327] For example, such as FIG. 9A As shown, the smartwatch 200 can receive user input (e.g., a click) regarding the dialing option in the user interface 910. In response to the user's input, the smartwatch 200 can display... FIG. 9B The user interface 920 is shown. The user interface 920 may include a hang-up control, or it may be a network call request interface. The user can use the hang-up control to stop sending a network call request.

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

[0329] Optionally, after the smartwatch 200 receives input from the user regarding the dialing option in the user interface 910, the second application can prompt the user to choose between establishing a network video call or a network voice call.

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

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

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

[0333] For example, if the electronic device 100 and the electronic device 300 are logged in different user accounts as the smart watch 200, but the user accounts logged in by the electronic device 100 and the electronic device 300 are associated with the user account logged in by the smart watch 200, the electronic device 100 and the electronic device 300 can both receive the network call request sent by the smart watch 200.

[0334] For example, as shown in FIG. 9C , after receiving the network call request sent by the smart watch 200, the electronic device 100 can display a user interface 930 as shown in FIG. 9C , and the user interface 930 can be a network call waiting interface. The user interface 930 includes a hang-up option and a listen option. The user can reject the 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 listen option.

[0335] For example, as shown in FIG. 9D , after receiving the network call request sent by the smart watch 200, the electronic device 300 can display a user interface 940 as shown in FIG. 9D , and the user interface 940 is similar to the user interface 930, which will not be described herein.

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

[0337] The following embodiments of this application illustrate the establishment of a network call connection between an electronic device 100 and a smartwatch 200.

[0338] Optionally, if after receiving a request from the smartwatch 200 to establish a network call connection, the electronic device 100 has not opened the first application, or the first application has been opened but is running in the background, then the electronic device 100 can display the incoming call notification in the drop-down notification bar.

[0339] For example, such as FIG. 9E As shown, after receiving a network call connection request from the smartwatch 200, the electronic device 100 can display a notification message 990 in the drop-down notification bar. The notification message 990 is used to notify the user of a new incoming call. The electronic device 100 can receive user input (e.g., a click) on the notification message 990, and in response to the user's input, the electronic device 100 can display... FIG. 9C The user interface shown is 930.

[0340] For example, such as FIG. 9F As shown, the electronic device 100 can receive user input (e.g., a click) regarding the answer option in the user interface 930, and in response to the user's input, the electronic device 100 can display... FIG. 9G The user interface 950 shown can be a network call answering interface. The user interface 950 is similar to the user interface 260. For details, please refer to the description of the user interface 260. This application will not repeat it here.

[0341] For example, such as FIG. 9H As shown, after the electronic device 100 establishes a network call connection with the smartwatch 200, the smartwatch 200 can also switch to display... FIG. 9H The user interface 960 shown is similar to user interface 250. For details, please refer to the description of user interface 250. This application will not repeat the description here.

[0342] After the smart watch 200 establishes the network call connection with the electronic device 100, the smart watch 200 can send a message to the electronic device 300, which informs the electronic device 300 that the smart watch 200 has established the network call connection with the electronic device 100 and instructs the electronic device 300 to stop displaying the user interface 940.

[0343] In some embodiments, after the smart watch 200 sends the electronic device 100 and the electronic device 300 the message for establishing the network call connection, if the smart watch 200 does not receive the feedback message (e.g., the answer phone message or the reject phone message, etc.) sent by the electronic device 100 and the electronic device 300 within a first time length, the smart watch 200 can display the prompt information "The other party is not online, please try later" as shown in FIG. 9D, which prompts the user that the smart watch 200 cannot establish the network call connection with the other device at present. FIG. 9I

[0344] In some embodiments, after the smart watch 200 sends the electronic device 100 and the electronic device 300 the message for establishing the network call connection, if the electronic device 100 and the electronic device 300 both reject the call, the smart watch 200 can display the prompt information "The other party has rejected your video call request" as shown in FIG. 9E, which prompts the user that the electronic device 100 and the electronic device 300 have rejected to establish the network call connection with the smart watch 200. 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 can not display the prompt information as shown in FIG. 9E. Only when the electronic device 100 and the electronic device 300 both reject the call, the smart watch 200 displays the prompt information as shown in FIG. 9E. FIG. 9J FIG. 9J FIG. 9J

[0345] In some embodiments, after the smart watch 200 sends the electronic device 100 and the electronic device 300 the message for establishing the network call connection, if the electronic device 100 and the electronic device 300 both establish the network call connection with other devices, the smart watch 200 can display the prompt information "The other party is busy" as shown in FIG. 9F, which prompts the user that the electronic device 100 and the electronic device 300 have established the network call connection with other devices. FIG. 9K

[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 network connection information of other devices. Therefore, the smart watch 200 cannot actively initiate the establishment of the session connection with other devices. However, the smart watch 200 can request the electronic device 100 to actively establish the session connection. ​​​​​

[0348] In the scenario that the smart watch 200 calls the electronic device 100, the long connection can be established between the smart watch 200 and 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 the request for establishing the RTC call to the electronic device 100 through the push server, so that the electronic device 100 can receive the request for establishing the RTC call 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 the request for establishing the RTC call to the devices with the same account or different accounts and the devices with the established association relationship through the push server, the smart watch 200 and the electronic device 100 establish the trusted relationship and the first session connection, and the smart watch 200 and the electronic device 100 establish the RTC call connection.

[0350] FIG. 10 A method schematic diagram in which the smart watch 200 sends the request for establishing the RTC call to the devices with the same account or different accounts and the devices with the established association relationship through the push server is shown.

[0351] As shown in FIG. 10 , the first user account is logged in the smart watch 200, the second user account is logged in the electronic device 100, and the third user account is logged in 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 the first user account, the second user account, and the third user account have the established association relationship, 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 the long connection.

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

[0354] The push server can establish the 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 request for establishing the RTC call sent by the smart watch 200 through the push server.

[0355] S1003, the second application in the smart watch 200 receives the user operation of initiating the RTC call by the user.

[0356] For example, the smart watch 200 can display FIG. 9AThe second application is shown in a user interface 910. The user interface 910 includes a micro-chat option and a call option. In this case, the user can send information to other devices through the micro-chat option. The user can also dial a network call to other devices through the call option.

[0357] As an example, FIG. 9A As shown, the smart watch 200 can receive an input operation (e.g., a single click) of the user on the call option in the user interface 910. In response to the input operation of the user, the smart watch 200 can display FIG. 9B As shown, the smart watch 200 can receive an input operation (e.g., a single click) of the user on the call option in the user interface 910. In response to the input operation of the user, the smart watch 200 can display

[0358] The user operation of initiating the RTC call can be FIG. 9A As shown, the smart watch 200 can receive an input operation (e.g., a single click) of the user on the call option in the user interface 910. In response to the input operation of the user, the smart watch 200 can display

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

[0360] S1005, the service server sends the request for establishing an RTC call to a push server.

[0361] After the second application in the smart watch 200 receives the user operation of initiating the RTC call, the second application can send a request for establishing an RTC call to the service server, and the service server sends the request for establishing 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 the smart watch 200 to the push server through the service server.

[0363] In a possible implementation, the account information of the first user account can be carried in the request for establishing an RTC call and sent to the push server. In other possible implementations, the account information of the first user account can also be sent independently of the request for establishing an RTC call sent to the push server, which is not limited in the present application.

[0364] S1006, the push server sends the request for establishing an RTC call to the first application in the electronic device 100.

[0365] S1007, the push server sends the request for establishing an RTC call to the third application in the electronic device 300.

[0366] The push server can also obtain the account information of the first user account after receiving the request for establishing the RTC call sent by the second application in the smart watch 200 through the service server.

[0367] For example, the account information of the first user account can 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 can determine that the other devices logged in with the first user account are the electronic device 100 and the electronic device 300 based on the account ID of the first user account.

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

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

[0372] The third application can be the same or similar application as the first application.

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

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

[0375] The first application in the electronic device 100, after receiving the request for establishing the RTC call, in response to the request for establishing the RTC call, can display a network call request interface, so as to prompt the user of the electronic device 100 that the electronic device 100 has received the request for establishing the RTC call sent by the smart watch 200.

[0376] For example, the network call request interface displayed by the first application can be the user interface 930 shown in FIG. 9B. The user interface 930 includes a hang-up option and a pick-up option. The user can reject the network call connection with the smart watch 200 through the hang-up option. The user can also establish the network call connection with the smart watch 200 through the pick-up option. FIG. 9C

[0377] Similarly, the third application in the electronic device 300, after receiving the request for establishing the RTC call, in response to the request for establishing the RTC call, can display a network call request interface, so as to prompt the user of the electronic device 300 that the electronic device 300 has received the request for establishing the RTC call sent by the smart watch 200.

[0378] For example, the network call request interface displayed by the third application can be the user interface 940 shown in FIG. 9C. The user interface 940 is similar to the user interface 930. FIG. 9D

[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 the network call with the smart watch 200.

[0380] The following embodiments of the present application take the establishment of the network call between the electronic device 100 and the smart watch 200 as an example for description.

[0381] S1010, the first application receives the operation of the user picking up the call.

[0382] S1011, the first application sends, to the push server, a message that the electronic device 100 has picked up the call through the long connection.

[0383] S1012, the push server sends, to the third application in the electronic device 300, a message that the network call request interface is stopped from being displayed through the long connection.

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

[0385] The first application in the electronic device 100, after receiving the request for establishing the RTC call, in response to the request for establishing the RTC call, can display a network call request interface, and the first application can receive the user picking up the call. ​​

[0386] For example, the electronic device 100 can receive a user input operation (e.g., a single tap) for the answer option in the user interface 930, and in response to the user input operation, the first application can send a message that the electronic device 100 has answered the call to the push server.

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

[0388] After receiving the message to stop displaying the network call request interface sent by the push server, the third application in the electronic device 300 can stop displaying the network call request interface, that is, the third application can stop displaying the user interface 940 shown in the figure. FIG. 9D

[0389] FIG. 11 A method for establishing an RTC call by the smart watch 200 and the electronic device 100 is shown.

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

[0391] The specific implementation of the electronic device 100 and the smart watch 200 establishing a trusted relationship can refer to the description in the FIG. 3 embodiments, and details are not described here.

[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 a first session connection can refer to the description in the FIG. 4 embodiments, and details are not described here.

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

[0396] ​S1104, the RTC server generates an account ID and an account password of the first RTC call.

[0397] S1105, the RTC server sends the account ID and the 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 the account password of the first RTC call.

[0399] S1107, the first application in the electronic device 100 sends the account ID and the account 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 service server needs to confirm whether the device information of the electronic device 100 and the smart watch 200 is verified.

[0401] In the case that the device information of the electronic device 100 and the smart watch 200 is verified, S1109 is performed.

[0402] In the case that the device information of the electronic device 100 and the smart watch 200 is not verified, the process ends.

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

[0404] S1110, the device server can send the request for establishing an RTC call (the account ID and the account password of the first RTC call) to the connection networking client.

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

[0406] The description of S1103-S1111 can refer to the description of S503-S511 in the embodiments, which will not be repeated here. FIG. 5

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

[0408] After receiving the account ID and the account password of the first RTC call, the second application can connect to the RTC server based on the account ID and the 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 establish 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 is switched to the call in progress interface by the network call request interface.

[0412] After the electronic device 100 and the smart watch 200 establish the first RTC call connection, the second application can be switched 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 FIG. 9H The user interface 960 shown.

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

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

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

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

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

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

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

[0421] The first application in 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 after receiving the message that the smart watch 200 has connected to the RTC server.

[0422] For example, the call in progress interface can be FIG. 9G the user interface 950 shown.

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

[0424] Optionally, after the smart watch 200 and the electronic device 100 establish the 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 can 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 method for establishing an RTC call connection between the smart watch 200 and the electronic device 100 is shown.

[0427] S1201, in response to the request to establish the RTC call, the first application displays the network call request interface.

[0428] S1202, in response to the request to establish the RTC call, the third application displays the network call request interface.

[0429] Reference FIG. 10 According to the description of S1008 and S1009 in the embodiments, after the electronic device 100 receives the request to establish the RTC call sent by the smart watch 200, the first application can display the network call request interface. Similarly, after the electronic device 300 receives the request to establish the RTC call sent by the smart watch 200, the third application can display the network call request interface.

[0430] S1203, the first application receives an operation of rejecting the call by the user.

[0431] After the first application displays the network call request interface, the first application can display, for example, a user interface 930 as shown in FIG. 9B. FIG. 9C

[0432] When the user of the electronic device 100 rejects to establish the RTC call, the smart watch 200 can receive an input operation (e.g., a single click) of the user to the hang-up control in the user interface 930. In response to the input operation of the user, the electronic device 100 can stop displaying the user interface 930.

[0433] Optionally, after the first application receives the operation of rejecting the call by the user, 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 device information of the smart watch 200 (or referred to as networking information of the smart watch 200). The electronic device 100 can initiate establishment of the 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 the first session connection with the smart watch 200. The specific implementation of the electronic device 100 and the smart watch 200 establishing the first session connection can refer to the description in the embodiments, which will not be described herein again. FIG. 4

[0436] In some embodiments, the push server cannot send the message to the smart watch 200. The electronic device 100 and the smart watch 200 can establish the first session connection. The electronic device 100 can send the message to the smart watch 200 through the first session connection, for example, send the 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 the 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 the 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 a call rejection interface. ​​

[0440] After receiving the call rejection notification, the second application can be switched to a call rejection interface by the network call request interface.

[0441] For example, the second application can be switched to display the user interface 920 shown in FIG. 9B by the network call request interface. FIG. 9B For example, the second application can be switched to display the user interface 920 shown in FIG. 9B by the network call request interface. FIG. 9J For example, the second application can be switched to display the user interface 920 shown in FIG. 9B by the network call request interface. FIG. 9J The prompt information "The other party has rejected your video call request" is shown in the user interface, which is used to prompt the user of the smart watch 200 that the user of the electronic device 100 rejects to establish the network video call.

[0442] After the smart watch 200 displays the call rejection interface, the smart watch 200 can continue to display the user interface 910 shown in FIG. 9A. FIG. 9A After the smart watch 200 displays the call rejection interface, the smart watch 200 can continue to display the user interface 910 shown in FIG. 9A.

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

[0444] S1209, the push server sends the 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 the 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 can be executed after S1203.

[0448] After the user of the electronic device 100 rejects the call, the electronic device 100 can send the call rejection 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 the call rejection message to the push server, the push server sends the call rejection message to the connection networking service end in the electronic device 300, and the connection networking service end in the electronic device 300 sends the call rejection message to the third application in the electronic device 300. In response to the call rejection message, the third application stops displaying the network call request interface, and the third application can stop displaying the user interface 940 shown in FIG. 9C. FIG. 9D After the user of the electronic device 100 rejects the call, the electronic device 100 can send the call rejection 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 the call rejection message to the push server, the push server sends the call rejection message to the connection networking service end in the electronic device 300, and the connection networking service end in the electronic device 300 sends the call rejection message to the third application in the electronic device 300. In response to the call rejection message, the third application stops displaying the network call request interface, and the third application can stop displaying the user interface 940 shown in FIG. 9C.

[0449] In some embodiments, if the electronic device 100 is establishing an RTC call request with other devices after receiving the RTC call request, 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 the smart watch 200 that the electronic device 100 is establishing an RTC call with other devices.

[0450] In other embodiments, the electronic device 100 can also establish an RTC call with multiple devices at the same time, which is not limited in the present application.

[0451] FIG. 13 Another method for establishing an RTC call connection between the smart watch 200 and the electronic device 100 is shown.

[0452] S1301, the connection networking service 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 in the electronic device 300.

[0454] S1303, the connection networking service 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 a network call request interface.

[0456] Reference FIG. 10 According to the description of S1008 and S1009 in the embodiments, after the electronic device 100 and the electronic device 300 receive the RTC call request sent by the smart watch 200, if the electronic device 100 is busy, for example, the electronic device 100 is establishing a network call with other electronic devices. The electronic device 100 can not display a busy message. At the same time, the electronic device 100 can send a busy message to the third application in the electronic device 300 through the push server, so that the third application also does not display a 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 in the electronic device 100 sends a busy message to the connection networking service in the smart watch 200 through the first session connection.

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

[0460] S1308, the second application is switched from the network call request interface to the busy interface.

[0461] When the first application in the electronic device 100 is in an RTC call with another device, the electronic device 100 receives the request for establishing an RTC call 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, which indicates that the electronic device 100 is in an RTC call with another device.

[0462] In response to the busy message, the second application can be switched from the network call request interface to the busy interface.

[0463] Optionally, the busy interface can be FIG. 9K a user interface as shown in FIG. 13B.

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

[0465] In some embodiments, if the user of the electronic device 100 does not see the request for establishing an RTC call in time after the electronic device 100 receives the request for establishing an RTC call, and the smart watch 200 does not receive a response message (such as a reject call message or an answer call message or a busy message, etc.) sent by the electronic device 100 within a first time length, the smart watch 200 can prompt the user that the other party is temporarily unable to answer the call.

[0466] FIG. 14 FIG. 14 shows another method for the smart watch 200 and the electronic device 100 not to establish an RTC call connection.

[0467] S1401, in response to the request for establishing an RTC call, a network call request interface is displayed.

[0468] S1402, in response to the request for establishing an RTC call, a network call request interface is displayed.

[0469] Reference is made to FIG. 10As described in S1008 and S1009 of the embodiment, after receiving the RTC call establishment request sent by the smartwatch 200, the first application of the electronic device 100 can display a network call request interface. Similarly, after receiving the RTC call establishment request sent by the smartwatch 200, the third application of the electronic device 300 can display a network call request interface.

[0470] S1403, if no one answers the call after the first time period, the first application will stop prompting the user to answer the call.

[0471] S1404. If no one answers the call after the first time limit, the third application will stop prompting the user to answer the call.

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

[0473] After smartwatch 200 sends a video call request to electronic devices 100 and 300, if smartwatch 200 does not receive any feedback message from electronic devices 100 and 300 within a certain time period, such as a message accepting or rejecting the video call request, or a busy signal, smartwatch 200 can stop sending video call requests to electronic devices 100 and 300 and display... FIG. 9K The user interface shown. FIG. 9K The user interface shown displays the message "The other party is busy".

[0474] On the display of smartwatch 200 FIG. 9K After the user interface shown, the smartwatch 200 can continue to display... FIG. 9A The user interface shown is 910.

[0475] Similarly, if the electronic device 100 does not receive user input within a certain time period, the first application within the electronic device 100 can stop prompting the user to answer the call. For example, the first application can stop displaying... FIG. 9C The user interface shown is 930.

[0476] Similarly, if the electronic device 300 does not receive user input within a certain time period, the third application within the electronic device 300 can stop prompting the user to answer the call. For example, the third application can stop displaying... FIG. 9D The user interface shown is 940.

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

[0478] FIG. 15A method flowchart of device-to-device communication is provided in the present application.

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

[0480] For example, the first electronic device can be a smart watch 200, and the first server can be a push server.

[0481] The first user operation can be an input operation for FIG. 9A a phone call option.

[0482] The first request can be FIG. 10 an RTC call request in S1004 of the embodiment.

[0483] In the embodiment of the present application, the first electronic device can be a device supporting a SIM card slot or supporting an ESIM, or a device not supporting a SIM card slot or supporting an ESIM. That is, both the device supporting the SIM card slot or supporting the ESIM can be applied to the present application.

[0484] In some embodiments, the first electronic device can be a child watch, and the second electronic device can be a family member of the user of the first electronic device. The first electronic device and the second electronic device can 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 a second electronic device logging in a second user account based on the account ID of the first user account in response to the first request.

[0486] For example, the second electronic device can be the electronic device 100.

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

[0488] For example, the network call request can be FIG. 10 the RTC call request in S1006 of the embodiment.

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

[0490] For example, the first user interface can be FIG. 9CThe user interface 930 is shown. The first answer control can be an answer option shown in the user interface 930, and the first hangup control can be a hangup option shown in the user interface 930.

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

[0492] The second server can be an RTC server, for example.

[0493] The operation of the first answer control by the user can be an input operation on the answer option in the user interface 930, for example.

[0494] The second request can be FIG. 11 The request for establishing the RTC call shown in S1103.

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

[0496] The second server can generate the account ID and the account password of the first network call, for example. FIG. 11 The account ID and the account password of the network call shown in S1104.

[0497] In other embodiments, the account ID and the account password of the first network call can also be obtained by the first electronic device from the second server. The second server can send the account ID and the account password of the first network call to the second electronic device. The second electronic device can display a first user interface, and the first user interface can display the first answer control and the first hangup control. The second electronic device can receive an operation of the first answer control by the user, and connect to the second server based on the account ID and the account password of the first network call. After the first electronic device and the second electronic device are connected to the second server based on the account ID and the 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 audio messages and images to each other through the first network call.

[0498] S1507. The second server is further configured to send the account ID and the account password of the first network call to the first electronic device and the second electronic device, and the account ID and the 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 the method, the first electronic device can also initiate the network call connection to the other electronic device actively without storing the device information of the other electronic device inside the first electronic device. After receiving the user's request for playing the network call, the first electronic device can send a request for establishing the network call to the other electronic device through the first server. The other electronic device applies for the account ID and the account password of the first network call, so as to realize 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 a possible implementation, the second electronic device is further configured to: establish a first session connection with the first electronic device; and send a first message to the first electronic device through the first session connection in response to receiving the account ID and the account password of the first network call sent by the second server.

[0501] With reference to the first aspect, in a possible implementation, the first session connection is initiated by the second 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 a message to the first electronic device. Therefore, 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 the 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 connected to the second server, and the first electronic device needs to switch to display a second user interface. In this way, the first electronic device can establish a session connection actively through the second electronic device in the case that the first electronic device cannot establish a session connection with the second electronic device actively.

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

[0505] For example, the second user interface can beFIG. 9H The second hang-up control in the user interface 960 shown can be a hang-up option in the user interface 960 shown. FIG. 9H The second hang-up control in the user interface 960 shown can be a hang-up option in the user interface 960 shown.

[0506] In a possible implementation, the second electronic device further has a function of, in response to receiving the account ID and the account password of the first network call sent by the second server, stopping displaying the first user interface and starting displaying a third user interface, the third user interface including a third hang-up control and a call duration.

[0507] The third user interface can be, for example, the user interface 950 shown. FIG. 9G The third hang-up control in the user interface 950 shown can be a hang-up option in the user interface 950 shown. FIG. 9G The third hang-up control in the user interface 950 shown can be a hang-up option in the user interface 950 shown.

[0508] In a possible implementation, the system further includes a third electronic device, the third electronic device being logged in with a third user account, the third user account being the same as or associated with the first user account; a first server, specifically configured to: in response to the first request, determine, based on the account ID of the first user account, the second electronic device logged in with the second user account and the third electronic device logged in with the third user account; and send, to the second electronic device and the third electronic device, a network call establishment request; the third electronic device, configured to display, in response to the network call establishment request, a fourth user interface, the fourth user interface including a second answer control and a fourth hang-up control; the second electronic device, further configured to send, to the first server, a second message; the first server, further configured to send, to the third electronic device, the second message; and the third electronic device, further configured to stop displaying the fourth user interface in response to the second message.

[0509] In other embodiments, the second message can 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 a network call connection, the first electronic device cannot select a specific device to which the network call connection is initiated, and the first electronic device can send, to one or more devices logged in with the same account and one or more devices logged in with different accounts but associated with each other, a network call establishment request through the second server. After one of the electronic devices agrees to establish a network call connection with the first electronic device, other electronic devices receiving the network call connection will stop prompting the user to answer the network call.

[0511] The third electronic device can be, for example, the electronic device 300.

[0512] The fourth user interface can be, for example, the user interface 940 shown. FIG. 9D The second answer control in the user interface 940 shown can be an answer option in the user interface 940 shown. FIG. 9DThe fourth hang-up control in the answer option in the user interface 940 shown can be FIG. 9D The hang-up option in the user interface 940 shown.

[0513] Exemplarily, the second message can be FIG. 10 The message shown in S1012 in the embodiment for stopping displaying the network call request interface.

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

[0515] The second server cannot send a message to the first electronic device, and after the second electronic device refuses to establish the 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 message of refusing the call to the first electronic device, so that the first electronic device can prompt the user that the second electronic device has refused the network call.

[0516] Exemplarily, the third message can be FIG. 12 The call refusing notification shown in S1205 in the embodiment.

[0517] Exemplarily, the fifth user interface can be FIG. 9J The first indication information in the user interface shown can be FIG. 9J The prompt message "the other party has refused your video call request" in the user interface shown.

[0518] In a possible implementation, the system further includes a third electronic device, and a third user account is logged in the third electronic device, and the third user account is the same as or associated with the first user account; and the second electronic device is further configured 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; and the third electronic device is further configured to: in response to the fourth message, 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 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 can also be sent by the first electronic device to the third electronic device through the first server.

[0521] After the second electronic device rejects to establish the network call connection with the first electronic device, a message is further sent to the third electronic device to inform the third electronic device to stop displaying the network call request interface (i.e., the fourth user interface).

[0522] For example, the fourth message can be FIG. 12 The rejection phone message shown in S1209 in the embodiment.

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

[0524] The second user operation can be that the user initiates the network call connection to the first electronic device on the second electronic device. When the second electronic device initiates the network call connection, the second electronic device can select an object of the network call connection (for example, the user selects the first electronic device).

[0525] For example, the second user operation can be FIG. 2C The input operation for the video call option in the embodiment.

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

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

[0528] In a possible implementation, the second electronic device is further configured 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, the sixth user interface including a fifth hang-up control; and the first electronic device is further configured to: display a seventh user interface in response to the account ID and the account password of the second network call sent by the second server, the seventh user interface including a third answer control and a sixth hang-up control; receive and respond to a user operation on the third answer control to send a fifth message to the second electronic device through the second session connection; and the second electronic device is further configured to display an eighth user interface in response to the fifth message, the eighth user interface including a call duration and a seventh hang-up control.

[0529] When the second electronic device initiates the network call connection actively, 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 a call in progress interface (i.e., an eighth user interface).

[0530] For example, the second session connection can be FIG. 4 The session connection between the second electronic device and the first electronic device shown in the embodiments.

[0531] The sixth user interface can be FIG. 2D The user interface 2310 shown in the embodiments. The fifth hang-up control can be FIG. 2D The hang-up option in the user interface 2310 shown in the embodiments.

[0532] The seventh user interface can be FIG. 2E The user interface 240 shown in the embodiments. The third answer control can be FIG. 2E The answer option in the user interface 240 shown in the embodiments. The sixth hang-up control can be FIG. 2E The hang-up option in the user interface 240 shown in the embodiments.

[0533] The operation of the user on the third answer control can be FIG. 2E The input operation of the user on the answer option shown in the embodiments.

[0534] The fifth message can be FIG. 5 The answer success message shown in the embodiment S515.

[0535] The eighth user interface can be FIG. 2G The user interface 260 shown in the embodiments. The seventh hang-up control can be FIG. 2G The hang-up option in the user interface 260 shown in the embodiments.

[0536] In a possible implementation, the first electronic device also receives and responds to the operation of the user on the sixth hang-up control, and sends a sixth message to the second electronic device through the second session connection; and the second electronic device also displays a ninth user interface in response to the sixth message, the ninth user interface including second indication information for prompting the user that the network call has been refused.

[0537] When the second electronic device initiates the network call connection actively, 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] For example, the operation of the user on the sixth hang-up control can be FIG. 2H The input operation of the user on the hang-up option shown in the embodiment.

[0539] The sixth message can be FIG. 6 The refused call message shown in the embodiment S614.

[0540] Nine, the user interface can be FIG. 2I The second indication information can be FIG. 2I The prompt information "the phone has refused your video call" in the user interface 270 shown.

[0541] Reference FIG. 16 , FIG. 16 The structure diagram of the electronic device is shown.

[0542] The electronic device 100 can 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, and the specific type of the electronic device is not specially limited in the embodiment of the present application.

[0543] The electronic device 100 can 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, a headset interface 170D, a sensor module 180, a key 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 can include a pressure sensor 180A, a gyro sensor 180B, a barometric 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 can be understood that the structure shown in the embodiments of the present application does not constitute a specific limitation on the electronic device 100. In other embodiments of the present application, the electronic device 100 can include more or fewer components than shown, or combine certain components, or split certain components, or different arrangement of components. The components shown can be implemented in hardware, software, or a combination of software and hardware.

[0545] The processor 110 can include one or more processing units, for example: the processor 110 can include an application processor (AP), a modem processor, a graphics processing unit (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 can be independent devices, or can be integrated into one or more processors.

[0546] The controller can generate operation control signals according to instruction operation codes and timing signals, and complete the control of fetching and executing instructions.

[0547] The processor 110 can also include a memory that stores instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. The cache memory can hold instructions or data that the processor 110 has recently used or is likely to use again. If the processor 110 needs to use the instructions or data again, it can be retrieved directly from the cache memory. This avoids repeated accesses to the main memory, reducing the latency of the processor 110 and thus improving the efficiency of the system.

[0548] In some embodiments, the processor 110 can include one or more interfaces. The interfaces can 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 that includes a serial data line (SDA) and a serial clock line (SCL). In some embodiments, the processor 110 can include multiple sets of I2C buses. The processor 110 can 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 can be coupled to the touch sensor 180K through an I2C interface, so that the processor 110 and the touch sensor 180K communicate through the I2C bus interface, 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 sets of I2S buses. The processor 110 can be coupled to the audio module 170 through the I2S bus, realizing communication between the processor 110 and the audio module 170. In some embodiments, the audio module 170 can deliver audio signals to the wireless communication module 160 through the I2S interface, realizing the function of answering the phone through the 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 can be coupled with the wireless communication module 160 through a PCM bus interface. In some embodiments, the audio module 170 can also transmit audio signals to the wireless communication module 160 through the PCM interface, realizing the function of answering a phone call through 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 bus for asynchronous communication. The bus can be a bidirectional communication bus. It converts data to be transmitted between serial communication and parallel communication. In some embodiments, the UART interface is usually 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, realizing the Bluetooth function. In some embodiments, the audio module 170 can transmit audio signals to the wireless communication module 160 through the UART interface, realizing the function of playing music through a Bluetooth headset.

[0553] The MIPI interface can be used to connect the processor 110 and peripheral devices such as the display screen 194 and the camera 193. The MIPI interface includes the camera serial interface (CSI), the display serial interface (DSI), etc. In some embodiments, the processor 110 and the camera 193 communicate through the CSI interface, realizing the shooting function of the electronic device 100. The processor 110 and the display screen 194 communicate through the DSI interface, realizing 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 and the camera 193, the display screen 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 meets the USB standard specification, which 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, or to transmit data between the electronic device 100 and a peripheral device. It can also be used to connect a headset to play audio through the headset. The interface can also be used to connect other electronic devices, such as AR devices, etc.

[0556] It can be understood that the interface connection relationship between the modules shown in the embodiments of the present application is only illustrative and does not constitute a limitation on the structure of the electronic device 100. In some other embodiments of the present application, the electronic device 100 can also use different interface connection modes or a combination of multiple interface connection modes in the above embodiments.

[0557] The charging management module 140 is configured to receive charging input from a charger. The charger can be a wireless charger or a wired charger. In some wired charging embodiments, the charging management module 140 can receive charging input from a wired charger through the USB interface 130. In some wireless charging embodiments, the charging management module 140 can receive wireless charging input through a wireless charging coil of the electronic device 100. The charging management module 140 can charge the battery 142 and also supply power to the electronic device through the power management module 141.

[0558] The power management module 141 is configured 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 to supply 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 configured to monitor parameters such as battery capacity, battery cycle count, and battery health status (leakage, impedance). In some other embodiments, the power management module 141 can also be arranged in the processor 110. In some other embodiments, the power management module 141 and the charging management module 140 can also be arranged in the same device.

[0559] The wireless communication function of the electronic device 100 can be realized 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] The antenna 1 and the antenna 2 are configured to transmit and receive electromagnetic wave signals. Each antenna in the electronic device 100 can be used to cover a single or multiple communication frequency bands. Different antennas can also be multiplexed to improve the utilization rate of the antennas. For example, the antenna 1 can be multiplexed as a diversity antenna for a wireless local area network. In some other embodiments, the antennas can be used in combination with a tuning switch.

[0561] The mobile communication module 150 can provide a solution for wireless communication including 2G / 3G / 4G / 5G, etc. applied to the electronic device 100. The mobile communication module 150 can 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 by the antenna 1, and perform filtering, amplification, etc. on the received electromagnetic waves, and transfer the same to the modem processor for demodulation. The mobile communication module 150 can also amplify the signal modulated by the modem processor, and radiate the same as electromagnetic waves through the antenna 1. In some embodiments, at least part of the functional modules of the mobile communication module 150 can be disposed in the processor 110. In some embodiments, at least part of the functional modules of the mobile communication module 150 can be disposed in the same device as at least part of the modules of the processor 110.

[0562] The modem processor can include a modulator and a demodulator. The modulator is configured to modulate a low-frequency baseband signal to be transmitted into a medium-high frequency signal. The demodulator is configured to demodulate a 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. The low-frequency baseband signal processed by the baseband processor is transmitted to the application processor. The application processor outputs a sound signal through an audio device (not limited to the speaker 170A, the microphone 170B, etc.), or displays an image or a video through the display screen 194. In some embodiments, the modem processor can be a separate device. In other embodiments, the modem processor can be independent of the processor 110, and disposed in the same device as the mobile communication module 150 or other functional modules.

[0563] The wireless communication module 160 can provide a solution for wireless communication including wireless local area networks (WLAN) (e.g., wireless fidelity (Wi-Fi) network), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), infrared (IR) technology, etc. applied to the electronic device 100. The wireless communication module 160 can be one or more devices that integrate at least one communication processing module. The wireless communication module 160 receives an electromagnetic wave via the antenna 2, frequency-modulates and filters the electromagnetic wave signal, and transmits the processed signal to the processor 110. The wireless communication module 160 can also receive a signal to be transmitted from the processor 110, frequency-modulate it, amplify it, and radiate it as an electromagnetic wave via the antenna 2.

[0564] In some embodiments, the antenna 1 and the mobile communication module 150 of the electronic device 100 are coupled, and the antenna 2 and the wireless communication module 160 are coupled, so that the electronic device 100 can communicate with a network and other devices through wireless communication technology. The wireless communication technology can 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, etc. The GNSS can include a global positioning system (GPS), a global navigation satellite system (GLONASS), a beidu navigation satellite system (BDS), a quasi-zenith satellite system (QZSS), and / or a satellite based augmentation systems (SBAS).

[0565] The electronic device 100 implements a display function through a GPU, a display screen 194, and an application processor, etc. The GPU is a microprocessor for image processing, which is connected to the display screen 194 and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. The processor 110 can include one or more GPUs, which execute program instructions to generate or change display information.

[0566] The display screen 194 is configured to display images, videos, and the like. 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 (AMOLED), a flex light-emitting diode (FLED), a Miniled, a MicroLed, a Micro-oLed, a quantum dot light emitting diodes (QLED), or the like. In some embodiments, the electronic device 100 can include one or N display screens 194, where N is a positive integer greater than 1.

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

[0568] The ISP is configured to process the data fed back by the camera 193. For example, when taking a photo, the shutter is opened, 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 to convert it into an image visible to the naked eye. The ISP can also algorithmically optimize 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 disposed in the camera 193.

[0569] The camera 193 is configured to capture still images or videos. An object generates an optical image through a lens and projects it onto a 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 light signal into an electrical signal, which is then transmitted to the ISP to convert it 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 the like format. In some embodiments, the electronic device 100 can include one or N cameras 193, where N is a positive integer greater than 1.

[0570] The digital signal processor is used to process digital signals, in addition to being able to process digital image signals, it can also process other digital signals. For example, when the electronic device 100 is in frequency point selection, the digital signal processor is used to perform Fourier transform on the frequency point energy, etc.

[0571] The video codec is used to compress or decompress digital video. The electronic device 100 can support one or more video codecs. In this way, the electronic device 100 can play or record videos in multiple encoding formats, such as: moving picture experts group (MPEG) 1, MPEG 2, MPEG 3, MPEG 4, etc.

[0572] The NPU is a neural-network (NN) computing processor, which processes input information quickly by drawing on the structure of a biological neural network, such as drawing on the transmission mode between human brain neurons, and can also constantly self-learn. Through the NPU, the electronic device 100 can realize intelligent cognitive applications, such as: image recognition, face recognition, voice recognition, text understanding, etc.

[0573] The internal memory 121 can include one or more random access memories (RAMs) and one or more non-volatile memories (NVMs).

[0574] The random access memory can 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, such as the fifth generation DDR SDRAM commonly referred to as DDR5 SDRAM), etc.; the non-volatile memory can include a magnetic disk storage device, a flash memory.

[0575] According to the operation principle, the flash memory can include NOR FLASH, NAND FLASH, 3D NAND FLASH, etc. According to the potential order of the storage unit, the flash memory can include single-level cell (SLC), multi-level cell (MLC), triple-level cell (TLC), quad-level cell (QLC), etc. According to the storage specification, the flash memory can include universal flash storage (UFS), embedded multi media Card (eMMC), etc.

[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 an operating system or other programs running, and can also be used to store data of users and application programs, etc.

[0577] The non-volatile memory can also store executable programs and data of users and application programs, etc., and can 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 an external non-volatile memory, so as 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, so as to realize the data storage function. For example, files such as music and video are saved in the external non-volatile memory.

[0579] The electronic device 100 can realize the audio function through the audio module 170, the speaker 170A, the receiver 170B, the microphone 170C, the earphone interface 170D, and the application processor, etc. For example, music playing, recording, etc.

[0580] The audio module 170 is used to convert digital audio information into analog audio signals, 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 part of the function modules of the audio module 170 can be arranged in the processor 110.

[0581] The speaker 170A, also known as a "loudspeaker", is used to convert audio electrical signals into sound signals. 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 "earpiece", is used to convert audio electrical signals into sound signals. When the electronic device 100 answers a phone call or a voice message, the user can answer the voice by holding the receiver 170B close to the ear.

[0583] The microphone 170C, also called "microphone", "sounder", is used to convert sound signals into electrical signals. When making a phone call or sending a voice message, the user can make a sound by holding the microphone 170C close to the mouth, and input the sound signal into the microphone 170C. The electronic device 100 can be provided with at least one microphone 170C. In some other embodiments, the electronic device 100 can be provided with two microphones 170C, in addition to collecting sound signals, the noise reduction function can also be realized. In some other embodiments, the electronic device 100 can also be provided with three, four or more microphones 170C, in addition to collecting sound signals, noise reduction, the sound source can also be identified, and the directional recording function can also be realized.

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

[0585] The pressure sensor 180A is used to sense pressure signals, and can convert the pressure signals into electrical signals. In some embodiments, the pressure sensor 180A can be provided 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 include at least two parallel plates made of conductive material. 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 of the capacitance. When a touch operation acts on the display screen 194, the electronic device 100 detects the intensity of the touch operation according to the pressure sensor 180A. The electronic device 100 can also calculate the position of the touch according to the detection signal of the pressure sensor 180A. In some embodiments, the touch operation 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 a first pressure threshold value acts on a short message application icon, an instruction of viewing a short message is executed. When a touch operation with a touch operation intensity greater than or equal to the first pressure threshold value acts on the short message application icon, an instruction of creating a new short message is executed.

[0586] The gyroscope 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 gyroscope sensor 180B. The gyroscope sensor 180B can be used for anti-shake photography. For example, when the shutter is pressed, the gyroscope sensor 180B detects the angle of shaking of the electronic device 100, calculates the distance that the lens module needs to compensate according to the angle, and lets the lens offset the shaking of the electronic device 100 by reverse movement to achieve anti-shake. The gyroscope sensor 180B can also be used for navigation and motion sensing game scenarios.

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

[0588] The magnetic sensor 180D includes a Hall sensor. The electronic device 100 can detect the opening and closing of a flip cover with the magnetic sensor 180D. 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. In turn, according to the detected opening and closing state of the cover or the opening and closing state of the flip cover, the electronic device 100 can set features such as automatic unlocking of the flip cover.

[0589] The acceleration sensor 180E can detect the magnitude of acceleration of the electronic device 100 in various directions (typically three axes). When the electronic device 100 is stationary, the acceleration sensor 180E can detect the magnitude and direction of gravity. It can also be used to identify the posture of the electronic device, and applied to landscape / portrait switching, pedometers, and other applications.

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

[0591] The proximity light sensor 180G can include, for example, a light-emitting diode (LED) and a light detector, such as a photodiode. The light-emitting diode can be an infrared light-emitting diode. The electronic device 100 emits infrared light outwardly through the light-emitting diode. The electronic device 100 detects infrared reflected light from nearby objects using the photodiode. 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 a user is holding the electronic device 100 close to the ear for a call, so as to automatically turn off the screen to achieve the purpose of power saving. The proximity light sensor 180G can also be used for automatic unlocking and locking of the cover mode and pocket mode.

[0592] Ambient light sensor 180L is used to sense ambient light brightness. Electronic device 100 can adaptively adjust display screen 194 brightness according to sensed ambient light brightness. Ambient light sensor 180L can also be used to automatically adjust white balance when taking a picture. Ambient light sensor 180L can also cooperate with proximity light sensor 180G to detect whether electronic device 100 is in a pocket to prevent accidental touch.

[0593] Fingerprint sensor 180H is used to collect a fingerprint. Electronic device 100 can use collected fingerprint characteristics to implement fingerprint unlocking, access application lock, take a picture with a fingerprint, answer an incoming call with a fingerprint, and so on.

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

[0595] Touch sensor 180K, also referred to as a "touch device". Touch sensor 180K can be disposed on display screen 194, and touch sensor 180K and display screen 194 together form a touch screen, also referred to as a "touch panel". Touch sensor 180K is used to detect a touch operation acting on or near it. Touch sensor 180K can transmit the detected touch operation to an application processor to determine a touch event type. Visual output related to the touch operation can be provided through display screen 194. In other embodiments, touch sensor 180K can also be disposed on a surface of electronic device 100, which is different from the position of display screen 194.

[0596] Bone conduction sensor 180M can obtain a vibration signal. In some embodiments, bone conduction sensor 180M can obtain a vibration signal of a human body sound part vibration bone block. Bone conduction sensor 180M can also contact a human body pulse to receive a blood pressure pulsation signal. In some embodiments, bone conduction sensor 180M can also be disposed in a headset to form a bone conduction headset. Audio module 170 can analyze a voice signal based on the vibration signal of the sound part vibration bone block obtained by bone conduction sensor 180M to implement a voice function. Application processor can analyze heart rate information based on the blood pressure pulsation signal obtained by bone conduction sensor 180M to implement a heart rate detection function.

[0597] The keys 190 include a power key, a volume key, and the like. The keys 190 can be mechanical keys. The keys 190 can also be touch keys. The electronic device 100 can receive a key input, and generate a key signal input related to a user setting and a function control of the electronic device 100.

[0598] The motor 191 can generate a vibration cue. The motor 191 can be used for a call vibration cue, and can also be used for a touch vibration feedback. For example, a touch operation for different applications (e.g., a photograph, audio playback, and the like) can correspond to different vibration feedback effects. A touch operation for different regions of the display 194 can also correspond to different vibration feedback effects. Different application scenarios (e.g., a time reminder, a received message, an alarm, a game, and the like) can also correspond to different vibration feedback effects. The touch vibration feedback effects can also support customization.

[0599] The indicator 192 can be an indicator light, and can be used to indicate a charging state, a power change, and can also be used to indicate a message, a missed call, a notification, and the like.

[0600] The software system of the electronic device 100 can adopt a layered architecture, an event-driven architecture, a microkernel architecture, a microservice architecture, or a cloud architecture. Embodiments of the present application take an Android system with a layered architecture as an example to exemplarily illustrate the software structure of the electronic device 100.

[0601] FIG. 17 is a software structure block diagram of the electronic device 100 of an embodiment of the present application.

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

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

[0604] As shown in FIG. 17 , the application packages can include camera, gallery, calendar, call, map, navigation, WLAN, Bluetooth, music, video, short message, and the like.

[0605] The application framework layer provides an application programming interface (API) and a programming framework for the applications of the application layer. The application framework layer includes some pre-defined functions.

[0606] As shown in FIG. 17As shown, the application framework layer can include a window manager, a content provider, a view system, a phone manager, a resource manager, a notification manager, etc.

[0607] The window manager is used to manage windows. The window manager can acquire the size of the display screen, determine whether there is a status bar, lock the screen, and take a screenshot, etc.

[0608] The content provider is used to store and acquire data, and make the data accessible to applications. The data can include videos, images, audios, dialed and received calls, browsing history and bookmarks, phonebook, etc.

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

[0610] The phone manager is used to provide the communication function of the electronic device 100. For example, the management of the call state (including call connection, call hang-up, etc.).

[0611] The resource manager provides various resources for applications, such as localized strings, icons, pictures, layout files, video files, etc.

[0612] The notification manager enables applications to display notification information in the status bar, which can be used to convey a type of message that can automatically disappear after a short stay without user interaction. For example, the notification manager is used to inform the completion of downloading, message reminders, etc. The notification manager can also be a notification in the form of a chart or a scroll bar text appearing in the top status bar of the system, such as a notification of an application running in the background, or a notification in the form of a dialog window appearing on the screen. For example, prompting text information in the status bar, issuing a prompt sound, the electronic device vibrating, the indicator light flashing, etc.

[0613] The Android runtime includes a core library and a virtual machine. The Android runtime is responsible for the scheduling and management of the Android system.

[0614] The core library includes two parts: one part is the function function that the java language needs to call, and the other part is the core library of Android.

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

[0616] The system library can include a plurality of functional modules. For example, a surface manager, media libraries, a three-dimensional graphics processing library (e.g., OpenGL ES), a 2D graphics engine (e.g., SGL), etc.

[0617] The surface manager is used to manage the display subsystem and provides a plurality of applications with fusion of 2D and 3D layers.

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

[0619] The three-dimensional graphics processing library is used to implement three-dimensional graphics drawing, image rendering, composition, and layer processing, etc.

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

[0621] The kernel layer is a layer between hardware and software. The kernel layer at least includes display drivers, camera drivers, audio drivers, and sensor drivers.

[0622] The following describes, by way of example, the working flow of the software and hardware of the electronic device 100 in a capture and photographing scenario.

[0623] When the touch sensor 180K receives a touch operation, a corresponding hardware interrupt is sent to the kernel layer. The kernel layer processes the touch operation into a raw input event (including touch coordinates, a timestamp of the touch operation, etc.). 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. Taking the touch operation as a touch single-click operation and the control corresponding to the single-click operation as the control of the camera application icon as an example, the camera application calls an interface of the application framework layer, starts the camera application, and then starts the camera driver through the kernel layer, and captures a still image or a video through the camera 193.

[0624] The embodiments of the present application can be combined in any manner to achieve different technical effects.

[0625] In the above embodiments, all or part of the processes can be implemented by software, hardware, firmware, or any combination thereof. When implemented by software, all or part of the processes can be implemented 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, all or part of the processes described in the present application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions can be transferred from one website, computer, server or data center to another website, computer, server or data center through wired (such as coaxial cable, optical fiber, digital subscriber line) or wireless (such as infrared, wireless, microwave, etc.) manner. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that includes one or more available media sets. The available media can be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, a DVD), or a semiconductor medium (for example, a solid state disk (SSD)), etc.

[0626] Those of ordinary skill in the art can understand that all or part of the processes in the above embodiments can be instructed by a computer program to complete the relevant hardware, and the program can be stored in a computer-readable storage medium. When the program is executed, it can include the processes of the above method embodiments. The aforementioned storage medium includes ROM or random access memory (RAM), magnetic disk or optical disk, and various media that can store program codes.

[0627] In summary, the above only describes the embodiments of the present application, and is not used to limit the protection scope of the present application. Any modification, equivalent replacement, improvement, etc. made according to the disclosure of the present application shall be included in the protection scope of the present application.

Claims

1. A device-to-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 have a first long-lived connection. A first user account is logged in on the first electronic device, and a second user account is logged in on the second electronic device. The first user account and the second user account are the same or related to each other. 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 the account ID of the first user account; The first server is configured to, in response to the first request, determine the second electronic device logged in with the second user account based on the account ID of the first user account; The first server is also used 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 also configured to receive user operations on the first answering control and send a second request to the second server; The second server is used to generate the account ID and account password for the first network call in response to the second request; The second server is further configured to send the account ID and password of the first network call to the first electronic device and the second electronic device, wherein the account ID and 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 also used for: Establish a first session connection with the first electronic device; In response to receiving the account ID and password of the first network call sent by the second server, a first message is sent to the first electronic device through the first session connection; The first electronic device is further configured to display a second user interface in response to the first message, the second user interface including 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 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: 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.

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

6. The system according to any one of claims 1-4, characterized in that, The system also includes a third electronic device, on which a third user account is logged in. 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, the second electronic device logged in with the second user account and the third electronic device logged in with the third user account are determined based on the account ID of the first user account; Send 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 also used to send a second message to the first server; The first server is also configured to send the second message to the third electronic device; The third electronic device is also configured to stop displaying the fourth user interface in response to the second message.

7. The system according to any one of claims 1-4, characterized in that, The second electronic device is also used for: Receive user input to the first hang-up control and 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 configured to display a fifth user interface in response to the third message, the fifth user interface including first indication information, the first indication information being used to prompt the user that a network call has been refused.

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

9. The system according to any one of claims 1-4 or claim 8, characterized in that, The second electronic device is also configured to receive and respond to a second user operation by sending a third request to the second server; The second server is also configured to generate an account ID and account password for the second network call in response to the third request; The second server is further configured to send the account ID and password of the second network call to the first electronic device and the second electronic device, wherein the account ID and 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 also used to establish a second session connection with the first electronic device; The second electronic device is also configured to display a sixth user interface in response to the second user operation, the sixth user interface including a fifth hang-up control; The first electronic device is further configured to: In response to the account ID and password of the second network call sent by the second server, a seventh user interface is displayed, which includes a third answer 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 also configured to display an eighth user interface in response to the fifth message, the eighth user interface including call duration and a seventh hang-up control.

11. The system according to claim 10, characterized in that, The first electronic device also uses Receive and respond to the user's operation on the sixth hang-up control, and send the sixth message to the second electronic device through the second session connection; The second electronic device is also configured to display a ninth user interface in response to the sixth message, the ninth user interface including second indication information for prompting the user that a network call has been refused.

12. The system according to any one of claims 1-4, 8, 10, or 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 includes: The second electronic device displays a first user interface, which includes a first answer control and a first hang-up control. The first user interface is displayed after the second electronic device receives a network call request from the first server. The network call request is sent by the first server to the second electronic device after receiving a first request from the first electronic device and determining that the second electronic device is logged in with a 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 answer control and sends a second request to the second server. The second request is used to instruct the second server to generate the account ID and password of the first network call and send the account ID and password of the first network call to the first electronic device and the second electronic device. The account ID and password of 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 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. The first message is used to instruct the first electronic device to display a second user interface, which 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 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-16, characterized in that, After the second electronic device receives the account ID and 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 begins displaying the third user interface, which includes a third hang-up control and call duration.

18. The method according to any one of claims 13-16, characterized in that, After the second electronic device displays the first user interface, the method further includes: The second electronic device receives the user's operation on the first hang-up control; In response to an operation on the first hang-up control, a first session connection is established with the first electronic device; The second electronic device sends a third message to the first electronic device through the first session. The third message is used to instruct the first electronic device to display a fifth user interface. The fifth user interface includes first indication information, which is used to prompt the user that a 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. The fourth message instructs the first server to send a fourth message to the third electronic device. The fourth message instructs the third electronic device to stop displaying the fourth user interface. The fourth user interface is displayed after the third electronic device receives the network call request sent by the first server. The fourth user interface displays a second answer control and a fourth hang-up control. The third electronic device is logged into a third user account, which is the same as or associated with the first user account.

20. The method according to any one of claims 13-16 or claim 19, characterized in that, The method further includes: The second electronic device receives and responds to the second user's operation by sending a third request to the second server. The third request is used to instruct the second server to generate an account ID and password for the second network call, and to send the account ID and password for the second network call to the first electronic device and the second electronic device. The account ID and 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 action, a sixth user interface is displayed, the sixth user interface including a fifth hang-up control; The device 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 answer 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, which 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 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, which includes second indication information to prompt the user that a network call has been refused.

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

24. An electronic device, 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 code, the computer program code including computer instructions, which, when executed by the one or more processors, cause the second electronic device to perform the method as described in any one of claims 13-23.

25. A chip system applied to a second electronic device, the chip system comprising one or more processors, characterized in that, The processor is used to invoke computer instructions to cause the second electronic device to perform the method as described in any one of claims 13-23.

26. A computer-readable storage medium comprising instructions, characterized in that, When the instructions are executed on the second electronic device, the second electronic device causes the second electronic device to perform the method as described in any one of claims 13-23.

Images