WO2023226744A9

WO2023226744A9 - Communication method and related device

Info

Publication number: WO2023226744A9
Application number: PCT/CN2023/092908
Authority: WO
Inventors: 孙少忠
Original assignee: 荣耀终端有限公司
Priority date: 2022-05-27
Filing date: 2023-05-09
Publication date: 2024-01-04
Also published as: CN117112251B; WO2023226744A1; CN115033396A; CN115033396B; CN117112251A

Abstract

The present application provides a communication method and a related device. According to the communication method, a JS application framework in a wearable device can register a communication interface, and an AMS can be bound to the communication interface. A local application in the wearable device may communicate with a third-party application by means of the communication interface. In this way, the local application in the wearable device and the third-party application can realize data sharing, more application scenes can be expanded, and the user experience is improved.

Description

A communication method and related equipment

This application claims priority to the Chinese patent application filed with the China Patent Office on May 27, 2022, with the application number 202210588160.7 and the application title "A communication method and related equipment", the entire content of which is incorporated into this application by reference. .

Technical field

The present application relates to the field of terminal technology, and in particular, to a communication method and related equipment.

Background technique

Currently, some third-party applications in wearable devices are developed using JavaScript (JS for short) language, while local applications are developed based on the operating system (Operating System, OS). Third-party applications in wearable devices cannot communicate with local applications, so the data between the two cannot be shared and cannot be integrated and used.

Therefore, how to realize communication between third-party applications and local applications in wearable devices is an issue that needs to be solved urgently.

Contents of the invention

This application provides a communication method and related equipment. According to this communication method, the JS application framework in the wearable device can register the communication interface, and AMS can bind the communication interface. Local applications in wearable devices can communicate with third-party applications through this communication interface. In this way, local applications and third-party applications in wearable devices can share data, expand more application scenarios, and improve user experience.

In a first aspect, this application provides a communication method. This method can be applied to electronic devices. The method may include: the local application in the electronic device sends a first message to the capability management service AMS in the electronic device; the AMS sends the first message to a third-party application in the electronic device through the first communication interface; or, the AMS receives the third-party The application sends the second message through the first communication interface; the AMS sends the second message to the local application. The first communication interface is a communication interface between the AMS and the JS application framework in the electronic device. The first message includes the package name of the local application, the package name of the third-party application, and the first target transmission data. The second message includes the package name of the third-party application, the package name of the local application, and the second target transmission data.

In the solution provided by this application, the local application in the electronic device can send the first message to the AMS, and the AMS sends the first message to the third-party application through the first communication interface. That is to say, the local application in the electronic device can send data to the third-party application in the electronic device through the first communication interface. The AMS in the electronic device may also receive a second message sent by the third-party application through the first communication interface, and send the second message to the local application. That is to say, the third-party application in the electronic device can send data to the local application in the electronic device through the first communication interface. In this way, the electronic device can realize the interaction between the local application and the third-party application through the first communication interface, thereby realizing data sharing, realizing more application scenarios and improving the user experience.

In some embodiments of the present application, the first communication interface may be the interface M in the embodiments described below.

It should be noted that any local application and any third-party application in the electronic device can communicate based on the first communication interface. In some embodiments of the present application, the local application may include relevant instructions for calling the first communication interface. Similarly, the third-party application may include relevant instructions for calling the first communication interface.

In some embodiments of the present application, the first message may be message X11 in the embodiments described later.

In some embodiments of the present application, the second message may be message X12 in the embodiments described below.

It can be understood that for the specific meaning of the first target transmission data and the second target transmission data, please refer to the relevant description of the target transmission data in the embodiments to be described later, and the description will not be further elaborated here.

It should be noted that the local application mentioned in the claims can be any local application in the electronic device. In some embodiments of this application, the local application mentioned in the claims may be the local application N in the embodiments described below.

Similarly, it should be noted that the third-party application mentioned in the claims can be any third-party application in the electronic device. In some embodiments of this application, the third-party application mentioned in the claims may be the third-party application T in the embodiments described below.

It should also be noted that the electronic device mentioned in the claims may be a wearable device mentioned in the embodiments described below.

In connection with the first aspect, in a possible implementation manner, before the local application in the electronic device sends the first message to the capability management service AMS in the electronic device, or the AMS receives the third message sent by the third-party application through the first communication interface. Before sending the second message, the method may also include: the electronic device starts a third-party application; the JS application framework registers the first communication interface; and the AMS binds the first communication interface.

In the solution provided by this application, between realizing communication between the local application and the third-party application based on the first communication interface, the electronic device can register the first communication interface. Specifically, after the electronic device starts the third-party application, the JS application framework in the electronic device can register the first communication interface, and accordingly, the AMS can bind the first communication interface.

In some embodiments of the present application, the user operation triggers the electronic device to start a third-party application, and the electronic device can start a registration process to register the first communication interface. In this way, the electronic device can register the first communication interface before the local application communicates with the third-party application, and does not need to wait until the local application sends a message to the third-party application to register, or the third-party application sends a message to the local application. Registration saves communication time between local applications and third-party applications.

For example, the user clicks the application icon of the third-party application, and in response to the click operation, the electronic device launches the third-party application and starts the registration process. The registration process may include: the JS application framework registers the first communication interface and notifies the AMS to bind the first communication interface.

For example, the user triggers the launch of a third-party application while browsing another application, and the electronic device can also initiate the registration process.

It should be noted that in some embodiments of the present application, after the electronic device is turned on and the third-party application is started for the first time, the registration process can be triggered to register the first communication interface.

In some embodiments of the present application, the local application sends a message to the third-party application through the AMS. During this process, the third-party application will be started. After the third-party application is started, the electronic device can start the registration process. Further, the JS application framework registers the first communication interface and notifies AMS to bind the first communication interface.

Combined with the first aspect, in one possible implementation, before the electronic device starts the third-party application, the method may also include: the local application sends a third message to the AMS; the AMS determines whether there is a running application in the electronic device, and In the case where there is a running application in the electronic device, compare the running application with the third-party application priority. The electronic device starts a third-party application, which may specifically include: when there is no running application in the electronic device, or the priority of the running application is not higher than the priority of the third-party application, the electronic device starts the third-party application. . After the AMS binds the first communication interface, the method may further include: the AMS sends the third target transmission data to the third-party application through the first communication interface. The third message includes the package name of the local application, the package name of the third-party application, and the third target transmission data.

In the solution provided by this application, the local application sends a message to the third-party application through the AMS. During this process, the third-party application will be started. After the third-party application is started, the electronic device can start the registration process. It is worth noting that the electronic device will start a third-party application only when there is no running application, or the priority of the running application is not higher than the priority of the third-party application. This means that the electronic device will only launch third-party applications and then start the registration process if it does not affect the running status of higher-priority applications, fully considering user needs and experience.

In some embodiments of the present application, the third message may be message X1 in the embodiments described below.

It can be understood that for the specific meaning of the third target transmission data, please refer to the relevant description of the target transmission data in the embodiments to be described later, and will not be described here.

Combined with the first aspect, in a possible implementation manner, before the JS application framework registers the first communication interface, the method may further include: the JS application framework sends a fourth message to the third-party application. After the JS application framework registers the first communication interface, the method may further include: the JS application framework sends a fifth message to the AMS. Among them, the fourth message is used to notify the third-party application to start the registration process. The fifth message is used to notify AMS that the first communication interface has been registered.

In some embodiments of the present application, the fourth message may be message X8 in the embodiments described below.

In some embodiments of the present application, the fifth message may be message X9 in the embodiments described below.

Combined with the first aspect, in a possible implementation manner, the electronic device starts a third-party application, which may specifically include: AMS sending a sixth message to the JS application framework; the JS application framework loads relevant components of the third-party application and sends them to the AMS. Seventh news. Among them, the sixth message is used to notify the JS application framework to start the third-party application; the seventh message is used to notify the AMS that the third-party application has been started.

In some embodiments of the present application, the sixth message may be message X6 in the embodiments described below.

In some embodiments of the present application, the seventh message may be message X7 in the embodiments described below.

It can be understood that the specific manner in which the JS application framework loads relevant components of third-party applications can be found in the embodiments described later, and will not be described here.

Combined with the first aspect, in a possible implementation manner, before the electronic device starts the third-party application, the method may also include: AMS establishing a communication connection with the UI component in the electronic device; AMS requesting the UI component to place the original display interface in Backstage.

In the solution provided by this application, before starting a third-party application, the electronic device can first request the UI component to increase the interface resources so as to display the relevant interface of the third-party application.

It can be understood that the specific method for establishing a communication connection between the AMS and the UI component in the electronic device can be referred to the embodiments described later, and will not be described here.

In conjunction with the first aspect, in one possible implementation, after the AMS sends the first message to the third-party application in the electronic device through the first communication interface, the method may further include: the AMS receives the third-party application through the first communication interface. The eighth message sent; AMS sends the eighth message to the third-party application. Among them, the eighth message includes the package name of the third-party application, the package name of the local application, and the fourth target transmission data.

In the solution provided by this application, the local application in the electronic device can communicate with the third-party application as the sender of the message, and can also communicate with the third-party application as the receiver of the message. In other words, after registering the communication interface, the electronic device does not limit the message sender and message receiver when communicating between local applications and third-party applications, and can maximize data sharing, thereby expanding more application scenarios and improving user experience. experience.

In some embodiments of the present application, the eighth message may be message X12 in the embodiments described below.

It can be understood that for the specific meaning of the fourth target transmission data, please refer to the relevant description of the target transmission data in the embodiments to be described later, and will not be described here.

In conjunction with the first aspect, in a possible implementation manner, after the AMS receives the second message sent by the third-party application through the first communication interface, the method may further include: the local application sends a ninth message to the AMS; the AMS through the first communication interface The communication interface sends a ninth message to the third-party application. Among them, the ninth message includes the package name of the local application, the package name of the third-party application, and the fifth target transmission data.

In some embodiments of the present application, the ninth message may be message X11 in the embodiments described below.

It can be understood that for the specific meaning of the fifth target transmission data, please refer to the relevant description of the target transmission data in the embodiments to be described later, and will not be described here.

In a second aspect, the present application provides an electronic device. The electronic device may include a display, memory, and one or more processors. Wherein, the memory may be coupled with one or more processors. Memory is used to store computer programs. The processor is used to call the computer program to perform any method of the first aspect. Specifically, the processor may be configured to: the local application sends a first message to the capability management service AMS in the electronic device; the AMS sends the first message to the third-party application through the first communication interface; or the AMS receives the third-party application through the first communication interface. The second message sent by the communication interface; the AMS sends the second message to the local application. The first communication interface is a communication interface between the AMS and the JS application framework in the electronic device. The first message includes the package name of the local application, the package name of the third-party application, and the first target transmission data. The second message includes the package name of the third-party application, the package name of the local application, and the second target transmission data.

Combined with the second aspect, in a possible implementation manner, the processor is configured to: before the local application sends a first message to the capability management service AMS in the electronic device, or the AMS receives a message sent by a third-party application through the first communication interface Before the second message, it can also be used to: start a third-party application; JS application framework registers the first communication interface; AMS binds the first communication interface.

Combined with the second aspect, in a possible implementation, before being used to launch a third-party application, the processor can also be used to: the local application sends a third message to the AMS; the AMS determines whether there is a running application in the electronic device , and when there is a running application in the electronic device, compare the priorities of the running application and the third-party application. The processor is used to launch third-party applications. Specifically, it can be used to: launch third-party applications when there is no running application in the electronic device, or the priority of the running application is not higher than the priority of the third-party application. . After the AMS binds the first communication interface, the processor may also be configured to: the AMS sends the third target transmission data to the third-party application through the first communication interface. The third message includes the package name of the local application, the package name of the third-party application, and the third target transmission data.

Combined with the second aspect, in a possible implementation manner, before the processor is used for the JS application framework to register the first communication interface, the processor may also be used for the JS application framework to send a fourth message to the third-party application. After the processor is used by the JS application framework to register the first communication interface, the processor can also be used by the JS application framework to send the fifth message to the AMS. Among them, the fourth message is used to notify the third-party application to start the registration process. The fifth message is used to notify AMS that the first communication interface has been registered.

Combined with the second aspect, in one possible implementation, when the processor is used to launch a third-party application, it can be specifically used to: AMS send the sixth message to the JS application framework; the JS application framework loads relevant components of the third-party application , and sends the seventh message to AMS. Among them, the sixth message is used to notify the JS application framework to start the third-party application; the seventh message is used to notify the AMS that the third-party application has been started.

Combined with the second aspect, in one possible implementation, before being used to launch a third-party application, the processor can also be used to: establish a communication connection between the AMS and the UI component in the electronic device; the AMS requests the UI component to display the original interface. Put in the background.

In conjunction with the second aspect, in a possible implementation manner, after the processor is configured for: the AMS to send the first message to the third-party application in the electronic device through the first communication interface, the processor may also be configured for: the AMS to receive the third-party application. The eighth message is sent through the first communication interface; the AMS sends the eighth message to the third-party application. Among them, the eighth message includes the package name of the third-party application, the package name of the local application, and the fourth target transmission data.

Combined with the second aspect, in a possible implementation manner, after the processor is used for: the AMS to receive the second message sent by the third-party application through the first communication interface, the processor can also be used for: the local application to send the ninth message to the AMS. ; The AMS sends the ninth message to the third-party application through the first communication interface. Among them, the ninth message includes the package name of the local application, the package name of the third-party application, and the fifth target transmission data.

In a third aspect, the present application provides a computer storage medium that includes computer instructions. When the computer instructions are run on an electronic device, the electronic device causes the electronic device to execute any of the possible implementations of the first aspect.

In a fourth aspect, embodiments of the present application provide a chip that can be applied to electronic equipment. The chip includes one or more processors, and the processor is used to call computer instructions to cause the electronic equipment to execute any of the above-mentioned first aspects. One possible implementation.

In a fifth aspect, embodiments of the present application provide a computer program product containing instructions, which when the computer program product is run on an electronic device, causes the electronic device to execute any of the possible implementations of the first aspect.

It can be understood that the electronic device provided by the second aspect, the computer storage medium provided by the third aspect, the chip provided by the fourth aspect, and the computer program product provided by the fifth aspect are all used to execute any possibility of the first aspect. way of implementation. Therefore, the beneficial effects that can be achieved can be referred to the beneficial effects of any possible implementation method in the first aspect, and will not be described again here.

Description of drawings

Figure 1 is a schematic diagram of a communication scenario provided by an embodiment of the present application;

Figure 2 is a schematic structural diagram of a wearable device 100 provided by an embodiment of the present application;

Figure 3 is a schematic diagram of the hardware structure of a wearable device 100 provided by an embodiment of the present application;

Figure 4 is a schematic software structure diagram of a wearable device 100 provided by an embodiment of the present application;

Figure 5 is a schematic diagram of a communication process between wearable device applications provided by an embodiment of the present application;

Figure 6 is a flow chart of a communication method provided by an embodiment of the present application;

Figure 7 is a flow chart of yet another communication method provided by an embodiment of the present application;

Figure 8 is a schematic diagram of another communication scenario provided by an embodiment of the present application;

Figures 9a-9c are a set of user interface schematic diagrams provided by embodiments of the present application;

Figure 10 is a flow chart of yet another communication method provided by an embodiment of the present application;

Figure 11 is a schematic diagram of another communication scenario provided by an embodiment of the present application;

Figure 12 is a schematic diagram of another communication scenario provided by an embodiment of the present application;

Figure 13 is a schematic diagram of a user interface provided by an embodiment of the present application;

Figure 14 is a flow chart of yet another communication method provided by an embodiment of the present application.

Detailed ways

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present application. Among them, in the description of the embodiments of this application, unless otherwise stated, "/" means or, for example, A/B can mean A or B; "and/or" in the text is only a way to describe related objects. The association relationship means that there can be three relationships. For example, A and/or B can mean: A exists alone, A and B exist simultaneously, and B exists alone. In addition, in the description of the embodiment of the present application , "plurality" means two or more than two.

It should be understood that the terms "first", "second", etc. in the description, claims and drawings of this application are used to distinguish different objects, rather than describing a specific sequence. Furthermore, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusion. For example, a process, method, system, product or device that includes a series of steps or units is not limited to the listed steps or units, but optionally also includes steps or units that are not listed, or optionally also includes Other steps or units inherent to such processes, methods, products or devices.

Reference in this application to "an embodiment" means that a particular feature, structure or characteristic described in connection with the embodiment may be included in at least one embodiment of the application. The appearances of this phrase in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. It will be explicitly and implicitly understood by those skilled in the art that the embodiments described herein may be combined with other embodiments.

Currently, third-party applications in wearable devices are developed using JS language, and the underlying layer calls C++ interfaces through Jerryscript. It is understandable that the JS language is a lightweight, interpreted or just-in-time compiled programming language with function priority. C++ is a statically typed, compiled, general-purpose, case-sensitive, irregular programming language that supports procedural programming, object-oriented programming and generic programming. Understandably, Jerryscript is a lightweight JS engine.

As shown in FIG. 1 , the wearable device 100 can establish a communication connection with the terminal device 200 to realize information interaction with the terminal device 200 . It is understood that the communication connection may be a Bluetooth connection. In some embodiments of this application, third-party applications in wearable devices can implement information interaction with terminal devices such as mobile phones through the wearable device service wearkit service. It can be understood that wearkit service is a communication protocol between mobile phones and watches. Its specific description Please refer to relevant technical documents.

However, the native applications in the wearable device 100 are developed based on the underlying framework of the OS. This means that the third-party application and the local application in the wearable device 100 cannot communicate, and the two cannot share data.

It can be understood that an operating system (OS) is a computer program that manages computer hardware and software resources. The operating system needs to handle basic tasks such as managing and configuring memory, determining the priority of system resource supply and demand, controlling input and output devices, operating the network, and managing the file system. The operating system also provides an interface for users to interact with the system.

It can be understood that the wearable device 100 can be a smart watch, a smart bracelet, or other devices, and this application does not limit the specific type of the wearable device 100 .

This application provides a communication method and related equipment. According to this communication method, the JS application framework in the wearable device 100 can register a communication interface, and the AMS can bind the communication interface. Local applications in the wearable device 100 can communicate with third-party applications through the communication interface. In this way, local applications and third-party applications in the wearable device 100 can share data, expand more application scenarios, and improve user experience.

The device involved in this application is first introduced below.

Please refer to FIG. 2 , which is a schematic structural diagram of a wearable device 100 provided by an embodiment of the present application.

As shown in FIG. 2 , the wearable device 100 may include a main body part 110 and a wearable part 120 .

Among them, the main body component 110 may be provided with sensors, a display screen, etc. The wearable device 100 can determine the user's motion status through sensors and collect the user's motion data (eg, running trajectory, number of rope skipping, exercise time, etc.) and health data (eg, heart rate, blood oxygen, pressure, etc.). The wearable device 100 can also display the collected health data and exercise data through the display screen. Of course, the display screen of the wearable device 100 can also display time, power, Bluetooth connection status, etc. The main body part 110 may also include buttons 111 and 112 . Body component 110 may also include magnetic contacts. The wearable device 100 can be charged through the magnetic contacts.

Wearing component 120 may be used to mount body component 110 . As shown in FIG. 2 , the wearing component 120 may be a bracelet, a watch strap, or other component, which allows the main component 110 to be attached to the user's body (eg, wrist).

The following is a detailed introduction to the hardware structure of a wearable device 100 provided by an embodiment of the present application with reference to FIG. 3 .

The wearable device 100 may include a processor 101, a wireless communication module 102, a sensor module 103, a charging management module 104, a power management module 1041, a battery 1042, a magnetic contact 105, an audio module 106, a speaker 106A, a receiver 106B, and a microphone 106C. , display screen 107, buttons 108 and memory 109.

It can be understood that the structure illustrated in the embodiment of the present invention does not constitute a specific limitation on the wearable device 100 . In other embodiments of the present application, the wearable device 100 may include more or less components than shown in the figures, or combine some components, or split some components, or arrange different components. The components illustrated may be implemented in hardware, software, or a combination of software and hardware.

The processor 101 may include one or more processing units. For example, the processor 101 may include an application processor (Application Processor, AP), a modem processor, a graphics processor (Graphics Processing unit, GPU), and an image signal processor. (Image Signal Processor, ISP), controller, memory, video codec, digital signal processor (Digital Signal Processor, DSP), baseband processor, and/or neural network processor (Neural-network Processing Unit, NPU), etc. Among them, different processing units can be independent devices or integrated in one or more processors.

The controller may be the nerve center and command center of the wearable device 100 . The controller can generate operation control signals based on the instruction operation code and timing signals to complete the control of fetching and executing instructions.

In the embodiment provided in this application, the wearable device 100 can execute the communication method through the processor 101.

The processor 101 may also be provided with a memory for storing instructions and data. In some embodiments, the memory in processor 101 is a cache memory. This memory may hold instructions or data that have been recently used or recycled by the processor 101 . If the processor 101 needs to use the instructions or data again, it can be called directly from the memory. Repeated access is avoided and the waiting time of the processor 101 is reduced, thus improving the efficiency of the system.

In some embodiments of the present application, processor 101 may include one or more interfaces. This interface can be used to connect the wearable device 100 and peripheral devices. This interface can also be used to connect other electronic devices. For example, AR equipment, etc.

The wireless communication module 102 can provide applications on the wearable device 100 including Wireless Local Area Networks (WLAN) (such as Wireless Fidelity (Wi-Fi) network), Bluetooth (Bluetooth, BT), and global navigation. Wireless communication solutions such as Global Navigation Satellite System (GNSS), Frequency Modulation (FM), Near Field Communication (NFC), Infrared (IR) and other wireless communications. The wireless communication module 102 may be one or more devices integrating at least one communication processing module. The wireless communication module 102 can receive electromagnetic waves via an antenna, frequency modulate and filter the electromagnetic wave signals, and send the processed signals to the processor 101 . The wireless communication module 102 can also receive the signal to be sent from the processor 101, frequency modulate it, amplify it, and convert it into electromagnetic waves through the antenna for radiation.

In some embodiments of the present application, the wireless communication module 102 may include at least a Bluetooth module. The wearable device 100 can establish a communication connection with the terminal device 200 through the Bluetooth module in the wireless communication module 102 (as shown in FIG. 1 ).

Sensor module 103 may include one or more sensors, which may be of the same type or different types. As shown in FIG. 3 , the sensor module 103 may include a pressure sensor 103A, a gyroscope sensor 103B, an acceleration sensor 103C, a touch sensor 103D, a bone conduction sensor 103E, a light sensor 103F, and the like.

The pressure sensor 103A is used to sense pressure signals and can convert the pressure signals into electrical signals. In some embodiments, the pressure sensor 103A may be disposed on the display screen 107 . When a touch operation is performed on the display screen 107, the wearable device 100 detects the strength of the touch operation according to the pressure sensor 103A. The wearable device 100 may also calculate the touched position based on the detection signal of the pressure sensor 103A. In some embodiments, touch operations acting on the same touch location but with different touch operation intensities may correspond to different operation instructions.

The gyro sensor 103B may be used to determine the motion posture of the wearable device 100 . In some embodiments, the angular velocity of wearable device 100 about three axes (ie, x, y, and z axes) may be determined by gyro sensor 103B.

The acceleration sensor 103C can detect the acceleration of the wearable device 100 in various directions (generally three axes). When the wearable device 100 is stationary, the magnitude and direction of gravity can be detected. The acceleration sensor 103C can also be used to identify the posture of the wearable device 100 and be used in horizontal and vertical screen switching, pedometer and other applications.

Touch sensor 103D is also called a "touch panel". The touch sensor 103D can be disposed on the display screen 107. The touch sensor 103D and the display screen 107 form a touch screen, which is also called a "touch screen". Touch sensor 103D is used to detect the for touch operations on or near it. The touch sensor can pass the detected touch operation to the application processor to determine the touch event type. Visual output related to the touch operation may be provided through the display screen 107 . In other embodiments, the touch sensor 103D may also be disposed on the surface of the wearable device 100 in a position different from that of the display screen 107 .

The bone conduction sensor 103E can acquire vibration signals. In some embodiments of the present application, the bone conduction sensor 103E can also contact the human body's pulse and receive blood pressure beating signals. In some embodiments, the application processor can analyze the heart rate information based on the blood pressure beating signal acquired by the bone conduction sensor 103E to implement the heart rate detection function.

Light sensor 103F may include a light emitting diode and a photoreceiver. The wearable device 100 can irradiate a beam of light into the skin tissue of the human body through the light-emitting diode in the light sensor 103F, and then convert the received light signal into an electrical signal through the photoelectric receiver. Since the blood flow of the human body changes periodically with the pulse, and the proportion of oxygenated red blood cells in the blood also changes with the pulse, their absorption of incident light also changes periodically with the pulse. The change is reflected in the receiving end that the received electrical signal also changes with the pulse. The light sensor 103F can obtain the heart rate in the above manner. The wearable device 100 can also irradiate the finger with infrared light and red light simultaneously through the light-emitting diode, and then measure the absorption spectrum of the reflected light through the light sensor 103F. Since oxyhemoglobin in the blood absorbs more red light and less infrared light, and hemoglobin absorbs more infrared light and less red light, the wearable device 100 can measure blood oxygen content in the above manner. .

It can be understood that the sensor module 103 shown in FIG. 3 is only an exemplary division method, and other division methods are possible, and this application does not limit this.

The charging management module 104 is used to receive charging input from the charger. Among them, the charger can be a wireless charger or a wired charger. In some wired charging embodiments, the charging management module 104 may receive charging input from the wired charger through the magnetic contacts 105 . In some wireless charging embodiments, the charging management module 104 may receive wireless charging input through the wireless charging coil of the wearable device 100 . While the charging management module 104 charges the battery 1042, it can also provide power to the wearable device 100 through the power management module 1041. Among them, the magnetic contact 105 can also be understood as a magnetic sensor.

The audio module 106 is used to convert digital audio information into analog audio signal output, and is also used to convert analog audio input into digital audio signals. Speaker 106A is used to convert audio electrical signals into sound signals. The receiver 106B is used to convert audio electrical signals into sound signals. Microphone 106C is used to convert sound signals into electrical signals.

The display screen 107 is used to display pictures and the like. Display screen 107 may include a display panel. The display panel can use a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode or an active-matrix organic light-emitting diode (Active-Matrix Organic Light). Emitting Diode (AMOLED), Flex Light-Emitting Diode (FLED), Mini LED, Micro LED, Micro-OLED, Quantum Dot Light Emitting Diode (QLED), etc.

The key 108 may be a mechanical key or a touch key. The wearable device 100 may receive key inputs and generate key signal inputs related to user settings and function control of the wearable device 100 . In some embodiments of the present application, the wearable device 100 may include buttons 111 and 112 as shown in FIG. 2 .

Memory 109 may be used to store computer executable program code. The executable program code includes instructions. deal with The processor 101 executes instructions stored in the memory 109 to execute various functional applications and data processing of the wearable device 100 . The memory 109 may include a program storage area and a data storage area. Among them, the stored program area can store an operating system, at least one application program required for a function (such as a sound playback function, an image video playback function, etc.), etc. The storage data area may store data created during use of the wearable device 100 (such as audio data, phone book, etc.).

In some embodiments of the present application, the wearable device 100 can store the collected user's health data, exercise data, etc. in the memory 109 .

It is understood that in some embodiments of the present application, the wearable device 100 may include a motor. The motor can produce vibration cues. For example, the motor can be used to vibrate for incoming calls or for touch vibration feedback. For example, touch operations for different applications (such as taking pictures, audio playback, etc.) can correspond to different vibration feedback effects. The motor can also respond to different vibration feedback effects for touch operations in different areas of the display screen 107 . Different application scenarios (such as time reminders, receiving information, alarm clocks, games, etc.) can also correspond to different vibration feedback effects. The touch vibration feedback effect can also be customized. Wearable device 100 may also include an indicator. The indicator can be an indicator light, which can be used to indicate charging status, power changes, messages, missed calls, notifications, etc.

The software structure of the wearable device 100 provided by the embodiment of the present application will be introduced in detail below with reference to FIG. 4 .

The wearable device 100 may include native applications, third-party applications (ie, JS applications), JS application frameworks, OS framework layers, and OS kernel layers.

Local applications can be understood as applications installed in the wearable device 100 when the operating system is installed before the wearable device 100 leaves the factory. Native applications can include health applications. Users can record health data and exercise data through this health application. Of course, local applications can also include applications such as gallery, Bluetooth, and music. According to the above, the local application in the wearable device 100 is developed in C++ language.

Third-party applications can be understood as applications downloaded through the app store. For example, third-party applications may include navigation applications, search engines, etc. downloaded from an application store. It is understandable that the third-party application in the wearable device 100 is developed using JS language and belongs to JS application.

The JS application framework is used to support the development of third-party applications. JS application framework can include JS data binding (data binding), JS runtime (runtime) and JS framework (framework).

Among them, JS data binding can include binding relationships. View model instance, publisher (subject) and observer (observer). In the wearable device 100, the compiler compiles html and CSS into JS code and JSON objects, and uses the engine to call the JS interface to the C++ implementation. The calling process requires the participation of JS data binding.

JS runtime includes core libraries and virtual machines. The runtime is responsible for the scheduling and management of the system. The core library contains two parts: one part is the functional functions that the programming language (for example, JS language) needs to call, and the other part is the core library of the system. JS applications and JS frameworks run in virtual machines. The virtual machine executes programming files (eg, JS files) of JS applications and JS frameworks as binary files. The virtual machine is used to perform object life cycle management, stack management, thread management, security and exception management, and garbage collection and other functions.

JS framework can include UI component adapter layer and application programming interface adapter layer. It is understandable that the application programming interface can be referred to as API. UI component adapter layer can include basic components, animation components, page switching components, styles Manager and text editor etc. The API adapter layer can include basic components, rendering models, style managers, etc. It is understandable that the meaning of the above components can be referred to relevant technical documents. JS framework can include some predefined functions.

Of course, the JS framework can also include other components, and this application does not limit this.

The OS framework layer (framework) can include UI components (kit), OS API, capability management service (Ability Management Service, AMS), and package management service (Bundle Management Service, BMS). Among them, the UI component is used to start local applications. In addition, UI components are also responsible for drawing and displaying on the screen, and drawing different applications by managing the context of different scenes. For example, the buttons, marquee display boxes, font colors and lines displayed on the watch all require the support of UI components. OS API is the application programming interface provided by OS framework for local applications. AMS is used to manage the life cycle of third-party applications. For example, starting, switching, closing, etc. of third-party applications.

The OS kernel layer (kernel) is the foundation of the operating system. The final functions of the operating system are completed through the kernel layer. The kernel layer can include audio drivers, Bluetooth drivers, sensor drivers, display drivers, touch screen drivers, button drivers, etc. It is understandable that the OS kernel can include task management, memory management, interrupt management, exception management, system clock, semaphore, mutex lock, queue management, event management and software timer, etc. Furthermore, the OS kernel can also include C++ support, debugging components, etc.

It should be noted that the schematic software structure diagram of the wearable device 100 shown in FIG. 4 provided by the embodiment of the present application is only an example and should not be regarded as a limitation of the present application. It can be understood that the software structure of the wearable device 100 may also include more layers (for example, a hardware abstraction layer), and this application does not limit the specific module divisions in different layers of the operating system. For details, please refer to the conventional technology. An introduction to operating system software architecture.

Please refer to FIG. 5 , which is a schematic diagram of a communication process between wearable device applications according to an embodiment of the present application.

As shown in Figure 5, the local application N of the wearable device can send messages to the AMS. The message may include the package name of the local application N, the package name of the third-party application T, and the data that the local application N needs to send to the third-party application T. After receiving the message sent by the local application N, the AMS can determine the priority of the third-party application T. When there is no running application, or the running application has a lower priority than the third-party application T, AMS can establish a communication connection with the UI component and request the UI component to put the original display interface in the background to start Third-party applications T. Then, AMS can request the JS application framework to start the third-party application T. The JS framework can load related components of third-party applications T. Further, the JS application framework can send a message to AMS to notify AMS that the third-party application T has been started. After the message is sent successfully, the JS application framework can register the interface M. The interface M is the communication interface between the JS application framework and AMS. After the interface M is successfully registered, AMS can send data to the third-party application T.

It should be noted that in some embodiments of the present application, the transmission of messages between local applications and JS applications needs to go through the kernel layer.

Based on the communication process between wearable device applications shown in Figure 5, a communication method provided by the embodiment of the present application is concretely combined with Figure 6.

S601: Local application N sends message X1 to AMS. The message X1 includes the package name of the local application N and the package name of the third-party application T, as well as the target transmission data.

The local application N in the wearable device 100 may send a message X1 to the AMS in the wearable device 100 . Reasonable Solution: The message X1 may include the package name of the local application N, the package name of the third-party application T, and the target transmission data. Among them, the target transmission data refers to the data that the local application N needs to transmit to the third-party application T. Understandably, the package name is used to uniquely identify the application.

In some embodiments of the present application, the target transmission data may be the user's motion data or the user's health data. Of course, the target transmission data can also be other types of data, and this application does not limit this.

In some embodiments of the present application, the message X1 may include Bundlename/APP_index, message, messageLength and Type. It can be understood that Bundlename/APP_index, message, messageLength and Type are all fields of message X1. Among them, Bundlename/APP_index represents the package name. message transmits data to the target. That is, the data that local application N needs to transmit to third-party application T. messageLength represents the length of the message. Its unit can be bytes. Type represents the message type.

For example, when Type is music, the message type of message X1 is music information. When Type is healthdata, the message type of message X1 is health data. When Type is navigation, the message type of message X1 is navigation information. When Type is touchinfo, the message type of message X1 is touch information.

It can be understood that the local application N can be any application among local applications. Similarly, the third-party application T can be any of the third-party applications.

S602: The AMS determines whether there is a running application in the wearable device 100, and if there is a running application in the wearable device 100, compares the priorities of the running application and the third-party application T.

After receiving the message X1, the AMS can check whether there is a running application in the wearable device 100. If there is no running application in the wearable device 100, the wearable device 100 can continue to perform subsequent steps. If there is a running application in the wearable device 100, the AMS can compare the priorities of the running application and the third-party application T. If the priority of the running application is not higher than the priority of the third-party application T, the wearable device 100 continues to perform subsequent steps. In the case where the priority of the running application is higher than the priority of the third-party application T, the wearable device 100 will no longer perform subsequent steps until there is no longer a priority higher than the third-party application T in the wearable device 100 and the application is running before performing subsequent steps.

It can be understood that the priority list may be stored in the wearable device 100 . The priority list includes priorities corresponding to each application in the wearable device 100 .

It can be understood that the application running in the wearable device 100 may be a local application or a third-party application.

S603: When there is no running application in the wearable device 100, or the priority of the running application is not higher than the priority of the third-party application T, the AMS sends the message X2 to the UI component. Message X2 is used to establish the communication connection between the UI component and AMS.

It can be understood that if the AMS determines that there is no running application in the wearable device 100, or the priority of the running application is not higher than the priority of the third-party application T, the AMS can send the message X2 to the UI component, thereby communicating with the UI. The component establishes a communication connection.

In some embodiments of the present application, message X2 may be: AMS_START_CHECK_REQUEST.

Correspondingly, the UI component can receive message X2 sent by AMS. The UI component can determine whether to establish a communication connection with the AMS based on the current task processing situation. If the UI component is executing other processes, the UI component may temporarily not establish a communication connection with the AMS until the UI component is no longer executing other processes and then establish a communication connection with the AMS. If UI group If there is no process being executed by the software, that is, the UI component is capable of handling other tasks, the wearable device 100 can continue to perform subsequent steps.

S604: The UI component sends message X3 to AMS. Message X3 is used to indicate that the UI component agrees to establish a communication connection with AMS.

It is understandable that after receiving the message X2 sent by the AMS, the UI component can send the message X3 to the AMS. Message X3 may indicate that the UI component agrees to establish a communication connection with the AMS.

In some embodiments of the present application, the message X3 may be: AMS_START_CHECK_RESPONSE.

Correspondingly, AMS can receive the message X3 sent by the UI component. This means that AMS has established a communication connection with the UI component.

S605: AMS sends message X4 to the UI component. Message X4 is used to request the UI component to put the original display interface in the background.

It is understandable that after the AMS and the UI component establish a communication connection, the AMS can send the message X4 to the UI component to request the UI component to place the interface originally displayed on the display screen in the background.

In some embodiments of the present application, message X4 may be: LAUNCHER_BACKGROUND.

Correspondingly, the UI component can receive message X4 sent by AMS.

S606: The UI component sends message X5 to AMS. Message X5 is used to notify AMS that the original display interface has been placed in the background.

It is understandable that after the UI component receives the message X4 sent by AMS and determines that AMS is about to launch the third-party application T, it can put the original display interface in the background and send message X5 to AMS so that AMS can launch the third-party application T in time.

In some embodiments of the present application, message X5 may be: AMS_ONBACKGROUND.

Correspondingly, AMS can receive the message X5 sent by the UI component.

S607: AMS sends message X6 to the JS application framework. Message X6 is used to launch third-party application T.

It is understandable that after AMS receives the message X5 sent by the UI component, the AMS can send the message X6 to the JS application framework to notify the JS application framework to start the third-party application T.

In some embodiments of the present application, message X6 is used to notify the JS application framework to launch a third-party application.

In some embodiments of the present application, message X6 may be: ACTIVE.

Correspondingly, the JS application framework can receive message X6 sent by AMS.

S608: The JS application framework loads the relevant components of the third-party application T.

It is understandable that after the JS application framework receives the message X6 sent by the AMS, it can load the relevant components of the third-party application T. It can be understood that the relevant components of T of the third-party application may include interface display components, animation components, etc. Among them, the interface display component may include the position of the control, the shape of the control, and the text corresponding to the control. The animation component can be used to generate startup animations for third-party applications T, as well as animation effects during interface display. It can be understood that the relevant components of the third-party application T may include but are not limited to: general components, container components, basic components, media components, canvas components, grid components, svg components, etc. Among them, the full English name of svg is Scalable Vector Graphics, which means scalable vector graphics. svg is an open standard vector graphics language and a scalable vector graphics format.

In some embodiments of this application, the JS application framework can load: jsability_launch, jsability_show.

Correspondingly, after the JS application framework loads the relevant components of the third-party application T, the third-party application T starts to start.

S609: The JS application framework sends message X7 to AMS. Message X7 is used to notify AMS that third-party application T has been started.

In some embodiments of the present application, message X7 may be: AMS_ONACTIVE.

Correspondingly, AMS can receive message X7 sent by the JS application framework.

S610: The JS application framework sends message X8 to the third-party application T. Message X8 is used to notify the third-party application T to start the registration process.

It is understandable that after the JS application framework sends message X7 to AMS, it can send message X8 to third-party application T to notify third-party application T to start the registration process. Among them, the registration process refers to the process of registering the communication interface.

In some embodiments of the present application, message X8 may be: sunscribemessage.

Correspondingly, the third-party application T can receive the message X8 sent by the JS application framework.

S611: JS application framework registration interface M. The interface M is the communication interface between the JS application framework and AMS.

It is understandable that after the JS application framework sends the message X8 to the third-party application T, the interface M can be registered. The interface M is the communication interface between the JS application framework and AMS. The interface M can also be understood as the communication interface between JS applications and local applications.

In some embodiments of this application, the interface M may be: TriggerSuccessCallback.

S612: The JS application framework sends message X9 to AMS. Message X9 is used to notify AMS that interface X has been registered.

It is understandable that after the JS application framework registers the interface M, it can send message X9 to AMS to notify AMS that the interface M has been registered.

In some embodiments of the present application, message X9 may be: AMS_REGISTER.

S613: AMS binds interface M.

It is understandable that after the JS application framework registers the interface M, AMS can bind the interface M to facilitate subsequent communication through the interface M.

In some embodiments of this application, AMS can bind TriggerSuccessCallback.

S614: AMS sends message X10 to third-party application T. Message X10 contains target transmission data.

It can be understood that after AMS binds interface M, it can send message X10 to third-party application T through interface M. Among them, message X10 may include target transmission data. For relevant description of the target transmission data, please refer to step S601, which will not be described again here.

It should be noted that the communication method shown in Figure 6 may include more or fewer steps, which is not limited by this application.

Based on the communication process between wearable device applications shown in Figure 5, another communication method provided by the embodiment of the present application is concretely combined with Figure 7.

S701: Local application N sends message X11 to AMS. The message X11 includes the package name of the local application N and the package name of the third-party application T, as well as the target transmission data.

It can be understood that the relevant description of step S701 may refer to step S601, which will not be described again here.

It should be noted that the specific content of the target transmission data included in the message X11 may be different from the specific content of the target transmission data included in the message X1.

In some embodiments of the present application, the message X11 may be: AMS_SENDMESSAGE.

It can be understood that after the local application N sends the message X11 to the AMS, the AMS can interact with the UI component and request UI resources. For details, please refer to steps S602 to S606, which will not be described again here.

Correspondingly, AMS can receive message X11 sent by local application N.

S702: AMS sends message X11 to third-party application T through interface M.

It can be understood that after receiving the message X11 sent by the local application N, the AMS can send the message X11 to the third-party application T through the interface M. For the description of interface M, please refer to the above and will not be repeated here.

S703: The third-party application T sends the message X12 to the AMS through the interface M. Message X12 includes the package name of the third-party application T and the package name of the local application N, as well as the target transmission data.

It can be understood that the specific content of the target transmission data included in the message X12 may be different from the specific content of the target transmission data included in the message X1 and the message X11. The relevant description of the target transmission data can be referred to above and will not be repeated here.

Correspondingly, AMS can receive the message X12 sent by the third-party application T.

It can be understood that after the third-party application T sends the message X12 to the AMS, the AMS can interact with the UI component and request UI resources. For details, please refer to steps S602 to S606, which will not be described again here.

S704: AMS sends message X12 to local application N.

It can be understood that after AMS receives the message X12 sent by the third-party application T through the interface M, the AMS can send the message X12 to the local application N.

In some embodiments of the present application, the wearable device 100 may only perform step S701 and step S702.

In some embodiments of the present application, the wearable device 100 may only perform step S703 and step S704.

In some embodiments of the present application, the time at which the wearable device 100 performs step S703 and step S704 may be earlier than the time at which step S701 and step S702 are performed.

It should be noted that the communication method shown in Figure 7 may include more or fewer steps, which is not limited by this application.

Some communication scenarios provided by this application are introduced below.

Scenario 1: During running, once the heart rate exceeds the heart rate threshold, the local application in the wearable device 100 sends the heart rate data to a third-party application, and the third-party application starts a corresponding training course.

As shown in FIG. 8 , the user is running while wearing the wearable device 100 . Wearable device 100 may display user interface 300 as shown in Figure 9a. User interface 300 may include the user's heart rate profile. As shown in Figure 9a, the user's highest heart rate is 165 beats/min, the lowest heart rate is 49 beats/min, and the user's current heart rate is 165 beats/min. The wearable device 100 may determine that the user's current heart rate exceeds the heart rate threshold of 160 beats/minute. The health application in the wearable device 100 can send the user's heart rate data to the sports application, and the sports application can start a heart rate training course. As shown in Figure 9b, wearable device 100 may display user interface 400. User interface 400 is the startup interface of the sports application. Then, the wearable device 100 may also display the user interface 500 as shown in Figure 9c. User interface 500 is the startup interface for the heart rate training course.

It can be understood that the health application is a native application of the wearable device 100 , and the sports application is a third-party application of the wearable device 100 .

The following is a detailed introduction to the application of a communication method provided by the embodiment of the present application in scenario one with reference to Figure 10.

S1001: The wearable device 100 detects whether the user is in motion.

The wearable device 100 can detect whether the user is in motion through a gyroscope sensor and an acceleration sensor. The gyro sensor may be the gyro sensor 103B shown in FIG. 3 , and the acceleration sensor may be the acceleration sensor 103C shown in FIG. 3 .

It should be noted that the wearable device 100 can detect the user's exercise type (for example, running, cycling, etc.). In some embodiments of the present application, users can choose the type of exercise themselves.

S1002: The wearable device 100 detects whether the user's heart rate exceeds the heart rate threshold.

The wearable device 100 can detect the user's heart rate in real time and determine whether the user's heart rate exceeds the heart rate threshold.

It can be understood that the heart rate threshold can be set according to actual needs, and this application does not limit this. For example, the wearable device 100 may set a heart rate threshold based on the user's historical heart rate data. As another example, the wearable device 100 may set a heart rate threshold according to the type of exercise. In some embodiments of the present application, the heart rate threshold may be 160 beats/minute.

In some embodiments of the present application, the wearable device 100 may store the corresponding relationship between the heart rate threshold and the exercise type. For example, the heart rate threshold corresponding to running is 160 beats/minute. For another example, the heart rate threshold corresponding to yoga is 130 beats/minute. For another example, the heart rate threshold corresponding to cycling is 165 beats/minute.

S1003: The health application in the wearable device 100 sends a message to the AMS in the wearable device 100. The message includes the package name of the health application, the package name of the exercise application, and heart rate data.

Health apps can send messages to AMS. The message can include the package name of the health application, the package name of the exercise application, and the user's heart rate data. It can be understood that the user's heart rate data may include the user's current heart rate. The heart rate data is the target transmission data in the above embodiment.

S1004: AMS detects whether the sports application is started.

It is understandable that AMS can detect whether the sports application is started. That is, AMS can detect whether the application is running or placed in the background.

In some embodiments of the present application, the AMS can also detect whether the sports application has been launched before.

If the sports application has been started or has been started before, the wearable device 100 continues to execute step S1009 and step S1010. If the sports application has not been started and has not been started before, the wearable device 100 continues to perform subsequent steps.

S1005: AMS determines whether the priority of the sports application is not lower than the priority of the currently running application.

It can be understood that the relevant description of step S1005 may refer to step S602, which will not be described again here.

S1006: AMS notifies the JS application framework to start the motion application.

It can be understood that the relevant description of step S1006 may refer to steps S607 to step S610.

It is understandable that before AMS notifies the JS application framework to start the sports application, it can establish a communication connection with the UI component and request the UI component to put the original display interface in the background. For details, please refer to steps S603 to S606, which will not be described again here. .

S1007: JS application framework registration interface M.

It can be understood that the relevant description of step S1006 may refer to step S611.

It is understandable that after the JS application framework registers the interface M, it can also send a message to AMS to notify AMS that the interface M has been registered.

S1008: AMS is bound to interface M.

It can be understood that the relevant description of step S1006 may refer to step S613.

S1009: AMS sends heart rate data to the sports application through interface M.

It can be understood that after the AMS is bound to the interface M, the heart rate data can be sent to the sports application through the interface M.

S1010: The sports application determines a target training course based on heart rate data and starts the target training course.

After the sports application receives the heart rate data, it can determine the target training course based on the user's exercise status and exercise type, and start the target training course. Correspondingly, the wearable device 100 can display the relevant interface of the target training course.

For example, when the user is running, the target training course may be a running heart rate training course. For another example, when the user is cycling, the target training course may be a cycling heart rate training course. For another example, when the user is doing yoga, the target training course may be a yoga heart rate training course.

S1011: When the heart rate is lower than the heart rate threshold or the user stops exercising, the sports application ends the target training session.

It can be understood that the health application of the wearable device 100 can obtain the user's heart rate data in real time and send the heart rate data to the exercise application. Once the user's heart rate is lower than the heart rate threshold or the user stops exercising, the exercise application can end the target training course. The wearable device 100 can close the exercise application.

In some embodiments of the present application, when the user's heart rate is lower than the heart rate threshold, the exercise application can end the target training session regardless of whether the user ends the exercise.

In some embodiments of the present application, in the event that the user stops exercising, the exercise application may end the target training session.

In some embodiments of the present application, when the user's heart rate is lower than the heart rate threshold and the user stops exercising, the exercise application may end the target training session.

In some embodiments of the present application, the JS framework in the wearable device 100 has already registered the interface M. Therefore, the wearable device 100 may not perform steps S1007 and S1008.

It should be noted that the wearable device 100 can also trigger corresponding training courses based on other types of health data of the user (for example, pressure, blood oxygen, etc.). For details, please refer to the above embodiments.

Scenario 2: There is a running application in the wearable device 100 . The wearable device 100 can detect user operations on keys. In response to the user operation, the local application in the wearable device 100 may send a message to the third-party application to launch the third-party application. At the same time, the wearable device 100 can also put running applications in the background.

As shown in FIG. 11 , the user exercises while wearing the wearable device 100 . A sports application is running in the wearable device 100 . As shown in Figure 12, wearable device 100 may display user interface 600. User interface 600 may be an interface for a training session in a sports application. User interface 600 may include the movements the user is training, the user's heart rate, and calories burned. At this time, the wearable device 100 can remind the user that a new message has been received through vibration or voice. As shown in Figure 12, the user can press and hold the button 112 on the wearable device 100. The local application in the wearable device 100 can recognize the user's long press operation. Specifically, the local application can recognize the user's long press operation as a high-level signal for more than 2 seconds. Then, the local application in the wearable device 100 can send a message to the communication application to launch the communication application and display the communication interface including the new message in the communication application. As shown in Figure 13, wearable device 100 may display user interface 700. User interface 700 includes new messages from friends in the messaging application. At the same time, the wearable device 100 can also put the sports application in the background. The sports application in the wearable device 100 can prompt the user for the next training action through voice broadcast or other methods.

It can be understood that the local application in the above embodiment is an application set up to recognize the user's operation on the keys. Sports applications can be local applications or third-party applications. Communication applications are third-party applications.

The application of a communication method provided by the embodiment of the present application in scenario two will be introduced in detail below with reference to Figure 14.

S1401: The wearable device 100 detects a user operation on a key.

The user can press and hold the key, and the wearable device 100 can detect the long press operation on the key. It can be understood that the user operation may also include pressing a button twice, sliding to the right on the display screen, sliding upward on the display screen, etc. This application does not limit the specific form of the user operation.

S1402: The local application in the wearable device 100 identifies the user operation on the button and sends a signal to the AMS in the wearable device 100. This signal is used to notify the communication application to start interface J.

In some embodiments of the present application, the signal sent by the local application to the AMS may be a continuous high-level signal. The signal sent by the local application to the AMS can also be multiple high-level signals within a preset time. For example, two high-level signals within 3 seconds. Of course, the signals sent by the local application to the AMS can also be other types of signals, and this application does not limit this.

In some embodiments of the present application, the signal sent by the local application to the AMS can also be understood as a message.

It is understandable that interface J can be a communication interface including new messages in the communication application (as shown in Figure 13).

S1403: AMS notifies the JS application framework to start the communication application.

S1404: JS application framework registration interface M.

S1405: AMS binds interface M.

S1406: AMS sends the signal to the communication application through interface M.

It can be understood that the relevant description of steps S1403 to S1406 may refer to steps S1006 to S1009, which will not be described again here.

S1407: Communication application display interface J.

It is understandable that after the communication application receives the signal sent by the AMS, the interface J can be displayed.

It should be noted that the third-party application in scenario two can also be other applications other than communication applications, and this application does not limit this.

Scenario 3: The wearable device 100 can detect user operations acting on the corresponding interface of the local application. Local applications can send messages to third-party applications, and third-party applications have been started to implement music playback, generate QR codes, etc.

For example, the user can click the corresponding control on the local music application. This control is used to trigger the playback of the user's favorite song. The wearable device 100 can detect the click operation. Correspondingly, the local music application can send messages to the third-party music application through the interface M. This message is used to notify third-party applications to play the user's favorite songs. After receiving the message, the third-party music application can launch the corresponding interface to realize music playback.

For example, the user can click on the flight information card in the local application. The wearable device 100 can detect the click operation. Correspondingly, the local application can send messages to the third-party application through the interface M. This message is used to notify third-party applications to display flight specific information. After receiving the message, the third-party application can launch the corresponding interface. The wearable device 100 may display flight specific information on the display screen.

It can be understood that in the above example, before the local application sends a message to the third-party application through the interface M, the JS application framework in the wearable device 100 needs to register the interface M, and the AMS needs to bind the interface M. For detailed description, please refer to the above. I won’t go into details here.

It should be noted that the local applications and third-party applications in scenario three can also be other applications, and this application does not limit this.

Similarly, the third-party application in the wearable device 100 can also send messages to the local application, and the local application has been started to implement functions such as schedule reminders and flight reminders.

It can be understood that the terms "interface" and "user interface" in the description, claims and drawings of this application are media interfaces for interaction and information exchange between application programs or operating systems and users, which implement the internal Conversion between a form and a form acceptable to users. The commonly used form of user interface is graphical user interface (GUI), which refers to a user interface related to computer operations that is displayed graphically. It can be an icon, window, control and other interface elements displayed on the display screen of an electronic device. Controls can include icons, buttons, menus, tabs, text boxes, dialog boxes, status bars, navigation bars, widgets, etc. Visual interface elements.

The above embodiments are only used to illustrate the technical solutions of the present application, but are not intended to limit them. Although the present application has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that they can still modify the technical solutions described in the foregoing embodiments. Modifications may be made to the recorded technical solutions, or equivalent substitutions may be made to some of the technical features; however, these modifications or substitutions do not cause the essence of the corresponding technical solutions to depart from the scope of the technical solutions of the embodiments of the present application.

Claims

A communication method, characterized in that it is applied to wearable devices, and the method includes:

The wearable device detects an operation acting on a first interface; the first interface is an interface of a local application in the wearable device;

In response to the operation on the first interface, the wearable device sends a first message to the third-party application in the wearable device based on the first communication interface through the local application; the first message includes the The package name of the local application, the package name of the third-party application, and the first target transmission data;

The wearable device displays a second interface based on the first message through the third-party application; the second interface is the interface of the third-party application.
The method of claim 1, wherein the first interface includes a flight information card; the first message is used to notify the third-party application to display specific information about the flight; and the second interface includes the Specific information of the flight; the wearable device detects an operation acting on the first interface, specifically including: the wearable device detects an operation acting on the flight information card.
The method of claim 1, wherein the local application is a local music application; the third-party application is a third-party music application; the method further includes: the third-party music application receives the first After the message, the wearable device plays music based on the first message through the third-party music application.
The method of claim 3, wherein the wearable device detects an operation acting on the first interface, specifically including: the wearable device detects an operation acting on a corresponding control on the first interface. Operation; the corresponding control is used to trigger the wearable device to play the user's favorite song.
The method of claim 1, wherein the wearable device displays the second interface based on the first message through the third-party application, specifically including: the wearable device displays the second interface based on the third-party application through the third-party application. The first message generates a QR code and displays a second interface; the second interface includes the QR code.
The method according to any one of claims 1 to 5, wherein the wearable device sends the first message to the third-party application in the wearable device based on the first communication interface through the local application, Specifically: the wearable device sends the first message to the capability management service AMS in the wearable device through the local application; the wearable device sends the first message to the capability management service AMS through the AMS based on the first communication interface. The third-party application sends the first message; the first communication interface is a communication interface between the AMS and the JS application framework in the wearable device.
The method of claim 6, further comprising: the wearable device receiving, through the AMS, a second message sent by the third-party application through the first communication interface; The second message includes the package name of the third-party application, the package name of the local application, and the second target transmission data;

The wearable device sends the second message to the local application through the AMS.
The method of claim 6 or 7, wherein before the wearable device sends the first message to the capability management service AMS in the wearable device through the local application, the method further includes :

The wearable device launches the third-party application;

The wearable device registers the first communication interface through the JS application framework;

The wearable device is bound to the first communication interface through the AMS.
The method of claim 8, wherein before the wearable device starts the third-party application, The method also includes:

The wearable device sends a third message to the AMS through the local application; the third message includes the package name of the local application, the package name of the third-party application, and the third target transmission data;

The wearable device determines whether there is a running application in the wearable device through the AMS, and if there is a running application in the wearable device, compares the running application with the third party application priority;

The wearable device starts the third-party application, specifically including:

When there is no running application in the wearable device, or the priority of the running application is not higher than the priority of the third-party application, the wearable device starts the third-party application;

After the wearable device binds the first communication interface through the AMS, the method further includes:

The wearable device sends the third target transmission data to the third-party application based on the first communication interface through the AMS.
The method of claim 8, wherein before the wearable device registers the first communication interface through the JS application framework, the method further includes:

The wearable device sends a fourth message to the third-party application through the JS application framework; the fourth message is used to notify the third-party application to start the registration process;

After the wearable device registers the first communication interface through the JS application framework, the method further includes:

The wearable device sends a fifth message to the AMS through the JS application framework; the fifth message is used to notify the AMS that the first communication interface has been registered.
The method according to any one of claims 8-10, wherein the wearable device starts the third-party application, specifically including:

The wearable device sends a sixth message to the JS application framework through the AMS; the sixth message is used to notify the JS application framework to start the third-party application;

The wearable device loads relevant components of the third-party application through the JS application framework, and sends a seventh message to the AMS; the seventh message is used to notify the AMS that the third-party application has been started.
The method of claim 11, wherein before the wearable device starts the third-party application, the method further includes:

The wearable device establishes a communication connection with the UI component in the wearable device through the AMS;

The wearable device requests the UI component to place the original display interface in the background through the AMS.
The method according to any one of claims 6-10 and 12, characterized in that after the wearable device sends the first message to the third-party application based on the first communication interface through the AMS, , the method also includes:

The wearable device receives an eighth message sent by the third-party application through the first communication interface through the AMS; the eighth message includes the package name of the third-party application and the package name of the local application. , and the fourth target transmits data;

The wearable device sends the eighth message to the third-party application through the AMS.
The method of claim 11, wherein after the wearable device sends the first message to the third-party application through the AMS based on the first communication interface, the method further includes:

The wearable device receives an eighth message sent by the third-party application through the first communication interface through the AMS; the eighth message includes the package name of the third-party application and the package name of the local application. , and the fourth target transmits data;

The wearable device sends the eighth message to the third-party application through the AMS.
The method of claim 7, wherein after the wearable device receives the second message sent by the third-party application through the first communication interface through the AMS, the method further includes:

The wearable device sends a ninth message to the AMS through the local application; the ninth message includes the package name of the local application, the package name of the third-party application, and fifth target transmission data;

The wearable device sends the ninth message to the third-party application based on the first communication interface through the AMS.
The method of claim 11, wherein after the wearable device receives the second message sent by the third-party application through the first communication interface through the AMS, the method further includes:

The wearable device sends a ninth message to the AMS through the local application; the ninth message includes the package name of the local application, the package name of the third-party application, and fifth target transmission data;

The wearable device sends the ninth message to the third-party application based on the first communication interface through the AMS.
A wearable device includes a display screen, a memory, and one or more processors, characterized in that the memory is used to store a computer program; the processor is used to call the computer program so that the wearable device Carry out the method of any one of claims 1-16.
A computer storage medium, characterized in that it includes: computer instructions; when the computer instructions are run on a wearable device, the wearable device is caused to execute the method described in any one of claims 1-16.