CN115767482A - Interaction method, vehicle-mounted terminal, wearable device and storage medium - Google Patents

Abstract

The disclosure provides an interaction method, a vehicle-mounted terminal, a wearable device and a storage medium. The method is used for the vehicle-mounted terminal and the wearable device which are in communication connection, and comprises the following steps: the vehicle-mounted terminal sends a command to the wearable device, wherein the command is used for indicating the wearable device to run a corresponding current application in at least one adjustable application; the method comprises the steps that a vehicle-mounted terminal receives a resource obtaining request sent by wearable equipment, and the resource obtaining request is determined by the wearable equipment based on current application; and the vehicle-mounted terminal sends the resource to the wearable equipment based on the resource acquisition request. The wearable equipment can be used as a physical screen in the vehicle-mounted terminal, the resource occupation burden of the vehicle-mounted terminal can be effectively reduced, the number of applications which can be operated by multiple screens can be effectively increased, the problem of limitation of the number of instances of simultaneous operation of the same application can be solved, and the problems of poor privacy of the multiple screens and high mutual interference can be effectively solved.

Description

Interaction method, vehicle-mounted terminal, wearable device and storage medium

Technical Field

Embodiments of the present disclosure relate to an interaction method, a vehicle-mounted terminal, a wearable device, and a storage medium.

Background

With the continuous upgrading of the vehicle-mounted terminal technology, various application programs can be installed in the vehicle-mounted terminal, and after the vehicle-mounted terminal starts the application programs, interfaces of the application programs can be displayed on the corresponding display screens. For example, the vehicle-mounted entertainment system starts to develop towards digitization and networking, and nowadays, functions such as bluetooth, navigation, music playing and the like become vehicle-mounted general functions. In order to facilitate a driver to quickly grasp various types of application information such as navigation information and communication information, a plurality of display screens controlled by a vehicle-mounted terminal usually display contents at the same time.

Disclosure of Invention

At least one embodiment of the present disclosure provides an interaction method, where a vehicle-mounted terminal and a wearable device establish a communication connection, and the interaction method includes: the vehicle-mounted terminal sends a command to the wearable device, wherein the command is used for indicating the wearable device to run a corresponding current application in at least one adjustable application; the vehicle-mounted terminal receives a resource acquisition request sent by the wearable device, wherein the resource acquisition request is determined by the wearable device based on the current application; and the vehicle-mounted terminal sends resources to the wearable equipment based on the resource acquisition request.

For example, an interaction method provided by at least one embodiment of the present disclosure further includes: the vehicle-mounted terminal receives a device registration request sent by the wearable device, and adds the wearable device to a current available device list of the vehicle-mounted terminal based on the device registration request.

For example, an interaction method provided by at least one embodiment of the present disclosure further includes: the vehicle-mounted terminal receives a service registration request sent by the wearable device, and adds a corresponding service to a current available device service list based on the service registration request.

For example, in an interaction method provided in at least one embodiment of the present disclosure, the list of currently available devices includes: at least one of equipment identity identification code, equipment type, equipment name, equipment user name and equipment version information; and/or, the list of currently available device services includes: at least one of service identification code, service type, service name, service version information, service details and service support interface list.

For example, in an interaction method provided by at least one embodiment of the present disclosure, the vehicle-mounted terminal receives a service registration request sent by the wearable device, and adds a corresponding service to a currently available device service list based on the service registration request, including: the vehicle-mounted terminal receives the service registration request sent by the wearable device, and stores entry information of the service in a target format to the current available device service list based on the service registration request, wherein at least one application interface corresponding to the adjustable application is configured to be registered in the form of the service to local service management of the wearable device, the service is indexed by at least two keywords, the at least two keywords comprise an application package name and an interface name, and the entry information in the target format comprises a device name and a service name.

For example, in an interaction method provided by at least one embodiment of the present disclosure, the sending, by the in-vehicle terminal, a command to the wearable device includes: the vehicle-mounted terminal provides the command to the wearable device based on the current available device list and the current available device service list.

For example, in an interaction method provided by at least one embodiment of the present disclosure, the sending, by the in-vehicle terminal, a command to the wearable device includes: and the vehicle-mounted terminal sends the command capable of obtaining the service calling parameter through analysis to the wearable equipment, wherein the service calling parameter is used for indicating the wearable equipment to start the current application interface of the current application.

For example, in an interaction method provided by at least one embodiment of the present disclosure, the command includes a device name, a service name, and a launch parameter, and the service invocation parameter includes an application package name, an interface name, and a launch parameter.

At least one embodiment of the present disclosure further provides an interaction method, where a vehicle-mounted terminal and a wearable device establish a communication connection, and the interaction method includes: the wearable device receives a command sent by the vehicle-mounted terminal, and the wearable device runs a corresponding current application in at least one adjustable application in the wearable device based on the command; the wearable device sends a resource acquisition request to the vehicle-mounted terminal, wherein the resource acquisition request is determined by the wearable device based on the current application; and the wearable equipment receives the resource sent by the vehicle-mounted terminal based on the resource acquisition request.

For example, in an interaction method provided by at least one embodiment of the present disclosure, the wearable device receives a command sent by the in-vehicle terminal, and the wearable device runs a corresponding current application of at least one adjustable application based on the command, including: the wearable device receives a command sent by the vehicle-mounted terminal, starts a corresponding current application interface of a corresponding current application in at least one adjustable application in the wearable device based on the command, and displays the current application interface of the current application on the wearable device.

For example, an interaction method provided in at least one embodiment of the present disclosure further includes: the wearable device sends a device registration request to the vehicle-mounted terminal, wherein the device registration request is used for instructing the vehicle-mounted terminal to add the wearable device to a current available device list of the vehicle-mounted terminal.

For example, an interaction method provided by at least one embodiment of the present disclosure further includes: the wearable device sends a service registration request to the vehicle-mounted terminal, wherein the service registration request is used for indicating the vehicle-mounted terminal to add a corresponding service to a current available device service list.

For example, in an interaction method provided by at least one embodiment of the present disclosure, the currently available device list includes: at least one of equipment identity identification code, equipment type, equipment name, equipment user name and equipment version information; and/or, the list of currently available device services includes: at least one of a service identification code, a service type, a service name, service version information, service details, and a service support interface list.

For example, in an interaction method provided by at least one embodiment of the present disclosure, the wearable device receives a command sent by the in-vehicle terminal, and the wearable device starts a corresponding current application interface of a corresponding current application in at least one adjustable application in the wearable device based on the command, including: the wearable device receives the command, analyzes the command and acquires a service calling parameter; the wearable device starts the current application interface of the current application based on the service calling parameter.

For example, in an interaction method provided by at least one embodiment of the present disclosure, the command includes a device name, a service name, and launch parameters, and the service invocation parameters include an application package name, an interface name, and launch parameters.

For example, an interaction method provided by at least one embodiment of the present disclosure further includes: in response to the wearable devices being a plurality of wearable devices, communicatively connecting the plurality of wearable devices to each other to enable inter-modulation services with each other such that a current application interface displayed on one of the plurality of wearable devices is shared for display on the other wearable devices.

At least one embodiment of the present disclosure further provides a vehicle-mounted terminal, including a first processor and a first memory, where the first memory is coupled to the first processor, and the first memory is used to store computer program codes, where the computer program codes include computer instructions, and when the first processor reads the computer instructions from the first memory, the vehicle-mounted terminal performs the following operations: sending a command to a wearable device, wherein the command is used for instructing the wearable device to run a corresponding current application in at least one adjustable application; receiving a resource acquisition request sent by the wearable device, wherein the resource acquisition request is determined by the wearable device based on the current application; sending a resource to the wearable device based on the resource acquisition request.

For example, in a vehicle-mounted terminal provided in at least one embodiment of the present disclosure, the vehicle-mounted terminal further performs: receiving a device registration request sent by the wearable device, and adding the wearable device to a current available device list of the vehicle-mounted terminal based on the device registration request.

For example, in a vehicle-mounted terminal provided in at least one embodiment of the present disclosure, the vehicle-mounted terminal further performs: receiving a service registration request sent by a service registration module of the wearable device, and adding a corresponding service to a current available device service list based on the service registration request.

For example, in a vehicle-mounted terminal provided in at least one embodiment of the present disclosure, the list of currently available devices includes: at least one of equipment identity identification code, equipment type, equipment name, equipment user name and equipment version information; and/or, the list of currently available device services includes: at least one of service identification code, service type, service name, service version information, service details and service support interface list.

For example, in a vehicle terminal provided in at least one embodiment of the present disclosure, the receiving, by the vehicle terminal, a service registration request sent by a service registration module of the wearable device, and adding a corresponding service to a currently available device service list based on the service registration request includes: the vehicle-mounted terminal receives a service registration request sent by the wearable device, and stores entry information of the service in a target format to the current available device service list based on the service registration request, wherein at least one application interface corresponding to the adjustable application is configured to be registered in the form of the service to local service management of the wearable device, the service is indexed by at least two keywords, the at least two keywords comprise an application package name and an interface name, and the entry information in the target format comprises a device name and a service name.

For example, in a vehicle terminal provided in at least one embodiment of the present disclosure, the vehicle terminal performs sending of a command to the wearable device, including: the vehicle-mounted terminal provides the command based on the current available equipment list and the current available equipment service list and sends the command to the wearable equipment, wherein the command is configured to obtain a service calling parameter through analysis, and the service calling parameter is used for indicating the wearable equipment to start the current application interface of the current application.

For example, in a vehicle-mounted terminal provided by at least one embodiment of the present disclosure, the command includes a device name, a service name, and a start parameter, and the service invocation parameter includes an application package name, an interface name, and a start parameter.

For example, in a vehicle-mounted terminal provided in at least one embodiment of the present disclosure, the performing, by the vehicle-mounted terminal, sending a resource to the wearable device based on the resource acquisition request includes: the vehicle-mounted terminal provides resources required by the adjustable application, and a data channel is established between the vehicle-mounted terminal and the current application, so that the vehicle-mounted terminal sends the resources to the wearable device.

At least one embodiment of the present disclosure also provides a vehicle including the in-vehicle terminal as in any one of the above embodiments.

At least one embodiment of the present disclosure further provides a wearable device, including a second processor and a second memory, where the second memory is coupled to the second processor, and the second memory is configured to store computer program code, which includes computer instructions, when the second processor reads the computer instructions from the second memory, to cause the wearable device to perform the following operations: receiving a command sent by the vehicle-mounted terminal, and running a corresponding current application in at least one adjustable application based on the command; sending a resource acquisition request to the vehicle-mounted terminal, wherein the resource acquisition request is determined by the wearable device based on the current application; and receiving the resource sent by the vehicle-mounted terminal based on the resource acquisition request.

For example, in a wearable device provided in at least one embodiment of the present disclosure, the wearable device includes a display configured to display a corresponding current application interface of a corresponding current application of at least one adjustable application of the wearable device that is initiated based on the command.

For example, in a wearable device provided in at least one embodiment of the present disclosure, the wearable device further performs at least one of the following: input audio, output audio, get control input events.

For example, in a wearable device provided in at least one embodiment of the present disclosure, the wearable device further performs: providing a device registration request to the vehicle-mounted terminal, wherein the device registration request is used for instructing the vehicle-mounted terminal to add the wearable device to a current available device list of the vehicle-mounted terminal.

For example, in a wearable device provided in at least one embodiment of the present disclosure, the wearable device further performs: and sending a service registration request to the vehicle-mounted terminal, wherein the service registration request is used for indicating the vehicle-mounted terminal to add the corresponding service to the current available equipment service list.

For example, in a wearable device provided in at least one embodiment of the present disclosure, the list of currently available devices includes: at least one of equipment identity identification code, equipment type, equipment name, equipment user name and equipment version information; and/or, the list of currently available device services includes: at least one of a service identification code, a service type, a service name, service version information, service details, and a service support interface list.

For example, in a wearable device provided in at least one embodiment of the present disclosure, the wearable device executes a command received from the in-vehicle terminal and runs a corresponding current application of at least one adjustable application based on the command, including: the wearable device receives the command, analyzes the command and acquires a service calling parameter; the wearable device starts the current application interface of the current application based on the service call parameter.

For example, in a wearable device provided by at least one embodiment of the present disclosure, the command includes a device name, a service name, and an initiation parameter, and the service invocation parameter includes an application package name, an interface name, and an initiation parameter.

For example, in a wearable device provided in at least one embodiment of the present disclosure, the wearable device is a plurality of wearable devices, and the plurality of wearable devices are communicatively connected to each other to implement inter-modulation service with each other, so that a current application interface displayed on one of the plurality of wearable devices is shared and displayed on the other wearable devices.

For example, in a wearable device provided in at least one embodiment of the present disclosure, the plurality of wearable devices further perform: the plurality of wearable devices are configured to communicate with a coordination module to cause the coordination module to coordinate services with the plurality of wearable devices.

At least one embodiment of the present disclosure provides a computer-readable storage medium, wherein the storage medium stores a computer program, and the computer program, when executed by a processor, implements the interaction method as described in any of the above examples.

Drawings

In order to more clearly illustrate the embodiments of the present disclosure or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present disclosure, and other drawings can be obtained by those skilled in the art without creative efforts.

Fig. 1 is a schematic structural diagram of an interactive system according to some embodiments of the present disclosure;

FIG. 2 is a flow chart of an interaction method set forth in some embodiments of the present disclosure;

FIG. 3 is a schematic diagram of an interactive system according to further embodiments of the present disclosure;

FIG. 4 is a flow chart of an interaction method according to further embodiments of the present disclosure;

fig. 5 is a schematic diagram of a device registration provided by some embodiments of the present disclosure;

fig. 6 is a schematic diagram of a service registration provided by some embodiments of the present disclosure;

FIG. 7 is a schematic diagram of a service invocation provided by some embodiments of the present disclosure;

FIG. 8 is a flow chart of an interaction method set forth in further embodiments of the present disclosure;

FIG. 9 is a flowchart of one implementation of step T11 of the interaction method of FIG. 8;

FIG. 10 is a flow chart of one implementation of step T111 of the interaction method of FIG. 9;

FIG. 11 is a flow chart of an interaction method provided by further embodiments of the present disclosure;

fig. 12 is a schematic structural diagram of a vehicle-mounted terminal according to some embodiments of the present disclosure;

fig. 13 is a schematic structural diagram of a wearable device according to some embodiments of the present disclosure;

fig. 14 is a block diagram of a vehicle-mounted terminal and a wearable device provided by some embodiments of the present disclosure;

fig. 15 is a partial module schematic diagram of a vehicle-mounted terminal and a wearable device provided in some embodiments of the present disclosure.

Detailed Description

The technical solutions in the embodiments of the present disclosure will be clearly and completely described below with reference to the drawings in the embodiments of the present disclosure, and it is obvious that the described embodiments are only a part of the embodiments of the present disclosure, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments disclosed herein without making any creative effort, shall fall within the protection scope of the present disclosure.

Unless otherwise defined, all terms (including technical and scientific terms) used in the embodiments of the present disclosure have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs. It will be further understood that terms, such as those defined in commonly used dictionaries, should be interpreted as having a meaning that is consistent with their meaning in the context of the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.

The use of "first," "second," and similar terms in the embodiments of the disclosure is not intended to indicate any order, quantity, or importance, but rather to distinguish one element from another. The use of the terms "a" and "an" or "the" and similar referents do not denote a limitation of quantity, but rather denote the presence of at least one. Similarly, the word "comprising" or "comprises", and the like, means that the element or item preceding the word comprises the element or item listed after the word and its equivalent, but does not exclude other elements or items. The terms "connected" or "coupled" and the like are not restricted to physical or mechanical connections, but may include electrical connections, whether direct or indirect. Flowcharts are used in the disclosed embodiments to illustrate the steps of the methods according to the disclosed embodiments. It should be understood that the preceding and following steps are not necessarily performed in the exact order in which they are performed. Rather, various steps may be processed in reverse order or simultaneously. Meanwhile, other operations may be added to the processes, or a certain step or steps may be removed from the processes. The inventor of the present disclosure finds that a plurality of screens are generally set in a vehicle-mounted terminal (e.g., a car-mounted intelligent cabin) for outputting different display pictures, so as to implement physical multi-screen interaction, and respond to an interactive operation of a user on a target application program on multiple screens. Therefore, the bottom layer is realized by that an operating system of the intelligent cabin generates corresponding virtual screens for a plurality of physical screens in a software layer, simultaneously binds the target application program with the corresponding virtual screens, and finally transmits the display data of the target application program on the virtual screens to the corresponding physical screens for display.

The inventor of the present disclosure finds, through research, that some current technical solutions have the following problems: firstly, a plurality of physical screens are required to be arranged in the intelligent cabin, and the number and the size of the screens are fixed and cannot be changed, so that the cost is high and the expansibility is poor; secondly, the application programs running on the multiple screens and the user input processing are all run on the operating system of the intelligent cockpit, which causes a large pressure on the operating system of the intelligent cockpit, for example, when running heavy applications (such as multiple screens playing high-definition movies or executing 3D games at the same time), all the computing tasks are burdened by the operating system of the intelligent cockpit, so that the operating system of the intelligent cockpit becomes a single point of performance in the whole cockpit system, often one or more applications are not responded in time due to excessive operating pressure, and even the stability of the whole intelligent cockpit system is affected; thirdly, because all program applications are installed on the operating system of the smart cockpit, the number of applications that can be run on the multi-screen is also limited by the number of applications installed on the operating system of the smart cockpit, and the number of instances that the same application can run on multiple screens at the same time is also limited; fourthly, because the application program is displayed on a plurality of physical screens in the intelligent cabin, the privacy is weak, and the mutual interference among the screens in the intelligent cabin is large, so that the multi-screen use scene of the intelligent cabin is seriously limited.

To this end, at least one embodiment of the present disclosure provides an interaction method, where the interaction method is used for a vehicle-mounted terminal and a wearable device, and the vehicle-mounted terminal and the wearable device establish a communication connection, where the interaction method includes: the method comprises the steps that a vehicle-mounted terminal sends a command to wearable equipment, wherein the command is used for indicating the wearable equipment to run a corresponding current application in at least one adjustable application; the method comprises the steps that a vehicle-mounted terminal receives a resource obtaining request sent by wearable equipment, and the resource obtaining request is determined by the wearable equipment based on current application; and the vehicle-mounted terminal sends the resource to the wearable equipment based on the resource acquisition request.

At least one embodiment of the present disclosure further provides an interaction method, where the interaction method is used for a vehicle-mounted terminal and a wearable device, and the vehicle-mounted terminal and the wearable device establish a communication connection, and the interaction method includes: the wearable device receives a command sent by the vehicle-mounted terminal, and the wearable device runs a corresponding current application in at least one adjustable application in the wearable device based on the command; the wearable device sends a resource acquisition request to the vehicle-mounted terminal, and the resource acquisition request is determined by the wearable device based on the current application; and the wearable equipment receives the resource sent by the vehicle-mounted terminal based on the resource acquisition request.

According to the interaction method, the vehicle-mounted terminal and the wearable device are matched, so that the wearable device can be used as a physical screen in the vehicle-mounted terminal and can be dynamically added or separated, and the expansibility and flexibility of multi-screen processing of the vehicle-mounted terminal are greatly enhanced. The interaction method of the embodiment of the disclosure can realize that the application runs on the wearable device, effectively reduces the resource occupation burden of the vehicle-mounted terminal, and effectively increases the number of applications that can be run by multiple screens because the application can be decomposed from the operating system that is centrally installed on the vehicle-mounted terminal to the operating system that is respectively installed on the operating system of the vehicle-mounted terminal and the operating system of the wearable device, and also can solve the problem of limitation of the number of instances that the same application runs simultaneously.

At least one embodiment of the present disclosure further provides a vehicle-mounted terminal, including a first processor and a first memory, the first memory being coupled to the first processor, the first memory being configured to store computer program codes, the computer program codes including computer instructions, when the first processor reads the computer instructions from the first memory, the vehicle-mounted terminal performs the following operations: sending a command to the wearable device, wherein the command is used for instructing the wearable device to run a corresponding current application in the at least one adjustable application; receiving a resource acquisition request sent by wearable equipment, wherein the resource acquisition request is determined by the wearable equipment based on the current application; and sending the resource to the wearable device based on the resource acquisition request.

According to the vehicle-mounted terminal and the wearable device, the operating system which is installed on the vehicle-mounted terminal in a centralized manner can be decomposed into the operating system which is installed on the vehicle-mounted terminal and the operating system which is installed on the wearable device, so that the resource occupation burden of the vehicle-mounted terminal is effectively reduced, the number of applications which can be run by multiple screens can be effectively increased, and the problem of limitation of the number of instances which can be run by the same application at the same time can be solved.

Yet another embodiment of the present disclosure provides a wearable device, including a second processor and a second memory, the second memory coupled to the second processor, the second memory configured to store computer program code, the computer program code including computer instructions, when the second processor reads the computer instructions from the second memory, the wearable device performs the following operations: receiving a command sent by the vehicle-mounted terminal, and running a corresponding current application in at least one adjustable application based on the command; sending a resource acquisition request to the vehicle-mounted terminal, wherein the resource acquisition request is determined by the wearable device based on the current application; and receiving the resource sent by the vehicle-mounted terminal based on the resource acquisition request.

The wearable device of the embodiment of the disclosure can be used as a physical screen in the vehicle-mounted terminal through the cooperation with the vehicle-mounted terminal, and can be dynamically added or separated, so that the expansibility and flexibility of multi-screen processing of the vehicle-mounted terminal are greatly enhanced. The wearable device can run the application, so that the resource occupation burden of the vehicle-mounted terminal is effectively reduced, and the application is decomposed into the operating system which is installed on the vehicle-mounted terminal and the operating system of the wearable device from the operating system which is installed on the vehicle-mounted terminal in a centralized manner, so that the number of applications which can be run by multiple screens is effectively increased, and the problem of limitation of the number of instances which are run by the same application at the same time can be solved. The wearable equipment of this disclosed above-mentioned embodiment has stronger privacy, can only supply the wearing person oneself to watch, listen and control, can effectively solve the problem that the privacy of shielding is poor, mutual interference is big.

Fig. 1 is a schematic structural diagram of an interactive system according to some embodiments of the present disclosure. Fig. 2 is a flowchart of an interaction method according to some embodiments of the present disclosure.

For example, as shown in fig. 1, an interactive system 1000 of some embodiments of the present disclosure includes a vehicle-mounted terminal 100 and a wearable device 200. The in-vehicle terminal 100 and the wearable device 200 establish a communication connection. For example, the in-vehicle terminal 100 and the wearable device 200 may establish a communication connection through a wireless communication module, such as Wi-Fi communication, bluetooth communication, and the like. For example, after establishing communication connections across each other, the wearable device 200 may enable communication of information related to, for example, services in the vehicle-mounted terminal 100 through the vehicle-mounted service bus 110 arranged within the vehicle-mounted terminal 100.

For example, as shown in fig. 1 and fig. 2, the interaction method (for example, denoted as interaction method one) of some embodiments of the present disclosure includes at least steps S11 to S13.

Step S11, the vehicle-mounted terminal 100 sends a command A1 to the wearable device 200, where the command A1 is used to instruct the wearable device 200 to run a corresponding current application of the at least one adjustable application.

Step S12, the in-vehicle terminal 100 receives a resource acquisition request B1 sent by the wearable device 200, where the resource acquisition request B1 is determined by the wearable device 200 based on the current application.

Step S13, the in-vehicle terminal 100 transmits the resource C1 to the wearable device 200 based on the resource acquisition request B1.

For example, step S12 of the above embodiment may be executed before step S11, or may be executed after step S11, and step S12 and step S11 may also be executed simultaneously, which is not limited in this embodiment of the present disclosure.

In some examples, command A1 may be a service invocation command that may be used to instruct wearable device 200 to run an adjustable application, i.e., embodiments of the present disclosure may run an adjustable application in wearable device 200 based on the service invocation command.

In some examples, the first interaction method further comprises the following processes or steps: the in-vehicle terminal 100 receives the device registration request transmitted by the wearable device 200, and adds the wearable device 200 to the currently available device list of the in-vehicle terminal 100 based on the device registration request, so that device registration of the wearable device 200 can be achieved. In this way, the in-vehicle terminal 100 may maintain a list of devices within the in-vehicle terminal 100 that may be invoked. For example, the list of currently available devices includes: at least one of equipment identity identification code, equipment type, equipment name, equipment user name and equipment version information. For example, the device registration request is a data protocol packet that corresponds to the above-described currently available device list and is in a certain format.

According to the embodiment of the invention, the wearable equipment can be added to the available equipment list of the vehicle-mounted terminal through equipment registration, and the cooperation between the wearable equipment and the vehicle-mounted terminal is realized, so that the wearable equipment can be used as a physical screen in the vehicle-mounted terminal and can be dynamically added or separated, and the expansibility and flexibility of multi-screen processing of the vehicle-mounted terminal are greatly enhanced.

In some examples, the first interaction method further comprises the following processes or steps: the in-vehicle terminal 100 receives the service registration request transmitted by the wearable device 200, and adds a corresponding service to the currently available device service list based on the service registration request, so that registration of the service of the wearable device 200 can be achieved. In this way, the in-vehicle terminal 100 may maintain a list of device services that may be invoked within the in-vehicle terminal 100. For example, the list of currently available device services includes: at least one of service identification code, service type, service name, service version information, service details and service support interface list. For example, the service registration request is formed of a data protocol packet corresponding to the currently available device service list described above and in a certain format.

According to the embodiment of the disclosure, the corresponding service can be added to the device service list of the vehicle-mounted terminal through registration of the service of the device, so that the integration of the application capability, the hardware capability and the like of the vehicle-mounted terminal and the wearable device can be effectively realized.

For example, in step S11, the command A1 includes a device name, a service name, and a startup parameter. For example, command A1 takes the form of a (device name, service name, startup parameters) triplet. Of course, this is merely exemplary and not a limitation of the present disclosure.

In some examples, wearable device 200 includes augmented reality glasses (also referred to as AR glasses). The embodiment of the present disclosure adopts the AR glasses to cooperate with the vehicle-mounted terminal 100, so that the embodiment of the present disclosure has better experience and fewer limitations on the operation convenience of the video display and input mode, and can relatively have more available resources on system resources. Of course, this is merely an example, and is not a limitation of the present disclosure, for example, the wearable device 200 of the embodiment of the present disclosure may also adopt other wearable devices that are intelligently designed and developed by applying wearable technology to daily wear, such as wearable devices of smart watches, smart gloves, and the like configured with a communication module, and is not exhaustive and repeated here. It should be noted that, the wearable device adopted in some embodiments of the present disclosure is not only a hardware device, but also can realize powerful functions through software support, data interaction, and cloud interaction.

Fig. 3 is a schematic structural diagram of an interactive system according to further embodiments of the present disclosure. Fig. 4 is a flowchart of an interaction method according to further embodiments of the present disclosure.

For example, as shown in fig. 3 and 4, the interaction method of some embodiments of the present disclosure includes at least step S21 to step S25.

In step S21, the in-vehicle terminal 100 receives the device registration request D1 transmitted by the wearable device 200, and adds the wearable device 200 to the currently available device list of the in-vehicle terminal 100 based on the device registration request D1.

Step S22, the in-vehicle terminal 100 receives the service registration request E1 sent by the wearable device 200, and adds the corresponding service to the currently available device service list based on the service registration request E1.

Step S23, the vehicle-mounted terminal 100 sends a command A1 to the wearable device 200, where the command A1 is used to instruct the wearable device 200 to run a corresponding current application of the at least one adjustable application.

Step S24, the in-vehicle terminal 100 receives a resource acquisition request B1 sent by the wearable device 200, where the resource acquisition request B1 is determined by the wearable device 200 based on the current application.

In step S25, the in-vehicle terminal 100 transmits the resource C1 to the wearable device 200 based on the resource acquisition request B1.

For example, step S24 of the above embodiment may be performed before step S23, or may be performed after step S23, and step S24 and step S23 may also be performed simultaneously, which is not limited in this embodiment of the present disclosure.

In some examples, in step S21, after the user wears the wearable device 200 and enters the vehicle-mounted terminal domain, the wearable device 200 negotiates and registers the local device with the vehicle-mounted terminal 100 through the vehicle-mounted service bus 100, so that device registration of the wearable device 200 may be achieved.

In some examples, the in-vehicle terminal domain refers to a range of areas in which the wearable device 200 and the in-vehicle terminal 100 can discover each other. For example, the vehicle terminal domain refers to a broadcast discovery area of bluetooth low energy (i.e. bluetooth BLE) by using a discovery mode of bluetooth low energy. For example, if an ultra-wideband (i.e., UWB) discovery method is used, the in-vehicle terminal domain refers to an ultra-wideband broadcast discovery area. Of course, this is merely exemplary and not a limitation of the present disclosure.

Fig. 5 is a schematic diagram of a device registration according to some embodiments of the present disclosure. Fig. 6 is a schematic diagram of a service registration according to some embodiments of the present disclosure. Fig. 7 is a schematic diagram of a service invocation according to some embodiments of the present disclosure.

In some examples, the wearable device 200 and the in-vehicle terminal 100 discover each other. For example, as shown in fig. 5, the wearable device 200 may complete mutual discovery between devices with the vehicle-mounted terminal 100 in various ways, for example, by means of bluetooth BLE, USB cable, UWB, and the like. Of course, this is merely exemplary and not a limitation of the present disclosure. Thus, after mutual discovery among the devices is realized, the embodiments of the present disclosure proceed to the next step of device interconnection and access to the in-vehicle service bus 110.

In some examples, authentication between the wearable device 200 and the in-vehicle terminal 100 may be performed again after the wearable device 200 and the in-vehicle terminal 100 achieve mutual discovery with each other. For example, as shown in fig. 5, the wearable device 200 may perform authentication between devices with the vehicle-mounted terminal 100 in various ways, for example, an account number, a personal identification number (i.e., a PIN code), a two-dimensional code, and the like. Of course, this is merely exemplary and not a limitation of the present disclosure.

For example, as shown in fig. 5, in the case that the wearable device 200 passes authentication, the wearable device 200 and the vehicle-mounted terminal 100 establish a private protocol channel for data encryption, exchange device information of each other, for example, the wearable device 200 sends its own device information to the vehicle-mounted terminal 100, and the vehicle-mounted terminal 100 adds the wearable device 200 to a currently available device list to implement device registration of the wearable device 200. In this way, the wearable device 200 can be added as an available external device to the available device list of the vehicle-mounted terminal 100, while the wearable device 200 and the vehicle-mounted terminal 100 may have a timed heartbeat policy, such that the available device list in the vehicle-mounted terminal 100 is updated in time when the wearable device 200 goes offline. For example, the timing heartbeat strategy can ensure that the services of the wearable device and the wearable device are really invokable, and prevent other terminals from invoking the offline device service after the wearable device is offline. For example, when a wearable device 200 comes back on-line again after going off-line, the device registration and the registration of the service described above will be performed again.

For example, as shown in fig. 6, at least one application interface corresponding to an adjustable application of an embodiment of the present disclosure is configured to be registered in the local service management of the wearable device 200 in the form of a service, which may be indexed by at least two keywords and the at least two keywords include an application package name and an interface name.

For example, for one navigation application software, a plurality of services such as a riding navigation service, a driving navigation service, a walking navigation service and the like can be corresponded according to different interfaces. Of course, this is merely exemplary and not a limitation of the present disclosure.

For example, as shown in fig. 3 and 6, step S22 may further include the following processes or steps: the in-vehicle terminal 100 receives the service registration request E1 transmitted by the wearable device 200, and stores entry information of the service in the target format to a currently available device service list based on the service registration request E1, so that registration of the service of the wearable device 200 can be achieved. For example, the entry information in the object format may include a device name and a service name. In some examples of the present disclosure, any trusted device may query the in-vehicle terminal 100 for currently invokable service information.

In some embodiments of the present disclosure, the tunable application can register the service in a service manner, so that the application package name corresponding to the service name can be found in the registered information according to the service name, thereby implementing service scheduling and application running.

In some examples, step S23 may further include the following process or step: in response to registration of the service of the wearable device 200, the in-vehicle terminal 100 provides the command A1 to the wearable device 200 based on the currently available device list and the currently available device service list.

In some examples, as shown in fig. 7, step S23 may further include the following process or step: the vehicle-mounted terminal 100 sends a command A1 for acquiring the service invocation parameter by parsing to the wearable device 200 (for example, the service invocation parameter may be acquired by parsing the service scheduling command to the command A1 shown in fig. 7), where the service invocation parameter is used to instruct the wearable device 200 to start a current application interface of a current application. For example, the service invocation parameters include an application package name, an interface name, and a launch parameter.

The embodiment of the disclosure can run the application on the wearable device, effectively reduces the resource occupation burden of the vehicle-mounted terminal, and effectively increases the number of applications which can be run by multiple screens because the application is set to be respectively installed on the operating system of the vehicle-mounted terminal and the operating system of the wearable device, and also can solve the problem of limitation of the number of instances which can be run by the same application at the same time.

In some examples of the disclosure, the tunable application may have multiple modes of operation: such as a native application running on glasses, or an application running on the in-vehicle terminal 100 and projected to the display on the wearable device 200, or a light application like a small program, so that the resource occupation burden of the in-vehicle terminal 100 can be effectively reduced.

Fig. 8 is a flowchart of an interaction method according to still other embodiments of the disclosure.

For example, as shown in fig. 1 and 8, the interaction method (for example, denoted as interaction method two) of some embodiments of the present disclosure includes at least step T11 to step T13.

Step T11, the wearable device 200 receives the command A1 sent by the in-vehicle terminal 100, and the wearable device 200 runs a corresponding current application in at least one adjustable application in the wearable device 200 based on the command A1.

Step T12, the wearable device 200 sends a resource acquisition request B1 to the vehicle-mounted terminal 100, where the resource acquisition request B1 is determined by the wearable device 200 based on the current application.

In step T13, the wearable device 200 receives the resource C1 transmitted by the in-vehicle terminal 100 based on the resource acquisition request B1.

For example, step T12 of the above embodiment may be performed before step T11, or may be performed after step T11, and step T12 and step T11 may also be performed simultaneously, which is not limited in this embodiment of the disclosure.

Fig. 9 is a flow chart of one implementation of step T11 of the interaction method of fig. 8. For example, as shown in fig. 9, one example of step T11 includes at least step T111 and step T112.

Step T111, the wearable device 200 receives the command A1 sent by the in-vehicle terminal 100, and the wearable device 200 starts a corresponding current application interface of a corresponding current application in at least one adjustable application in the wearable device 200 based on the command A1.

And step T112, displaying the current application interface of the current application on the wearable device 200.

This above-mentioned embodiment of this disclosure can regard as the physics screen in the vehicle mounted terminal with wearable equipment, can operate the application on the wearable equipment to reduce vehicle mounted terminal's resource effectively and occupy the burden, wearable equipment has stronger privacy moreover, can only supply the wearing person oneself to watch, listen and control like this, thereby can effectively solve the problem that the privacy of shielding is poor, mutual interference is big.

In some examples, the second interaction method further includes the following processes or steps: the wearable device 200 transmits a device registration request to the in-vehicle terminal 100, wherein the device registration request is for instructing the in-vehicle terminal 100 to add the wearable device 200 to a currently available device list of the in-vehicle terminal 100. For example, the list of currently available devices includes: at least one of the equipment identity identification code, the equipment type, the equipment name, the equipment user name and the equipment version information.

In some examples, the second interaction method further comprises the following processes or steps: the wearable device 200 transmits a service registration request to the vehicle-mounted terminal 100, wherein the service registration request is used for instructing the vehicle-mounted terminal 100 to add a corresponding service to a current available device service list. For example, the list of currently available device services includes: at least one of service identification code, service type, service name, service version information, service details and service support interface list.

Fig. 10 is a flow chart of one implementation of step T111 of the interaction method of fig. 9. For example, as shown in fig. 10, one example of step T111 includes at least step T1111 and step T1112.

Step T1111, the wearable device 200 receives the command A1, and parses the command A1 to obtain the service invocation parameter.

Step T1112, the wearable device 200 starts the current application interface of the current application based on the service invocation parameter.

For example, in step T1111, the command A1 includes a device name, a service name, and an activation parameter. For example, command A1 takes the form of a (device name, service name, startup parameters) triplet. Of course, this is merely exemplary and not a limitation of the present disclosure. For example, in step T1111, the service invocation parameter includes an application package name, an interface name, and a start parameter.

In some examples, the second interaction method further comprises the following processes or steps: in response to the wearable device 200 being a plurality of wearable devices 200, the plurality of wearable devices 200 are communicatively connected to each other to enable inter-modulation services with each other such that a current application interface displayed on one of the plurality of wearable devices 200 is shared for display on the other wearable devices 200.

For example, for the schedule on the wearable device 200 worn by the user a in the vehicle-mounted terminal 100, the schedule of the user a can be shared to other users (for example, the user b) in the vehicle-mounted terminal 100 in the form of service in the case of trust, that is, the wearable device 200 worn by the user a and the wearable device 200 worn by the user b can discover each other and can invoke each other service through the vehicle-mounted service bus, so that the wearable device 200 of the user b in the vehicle-mounted terminal 100 can display the schedule of the user a. Therefore, service scheduling can be performed through the vehicle-mounted terminal 100, and all wearable devices 200 in the vehicle-mounted terminal 100 can perform intermodulation service under the condition of sufficient trust, so that the flexibility of service calling is increased.

Fig. 11 is a flowchart of an interaction method according to still other embodiments of the present disclosure.

For example, as shown in fig. 1 and fig. 11, the interaction method (for example, denoted as interaction method three) of some embodiments of the present disclosure includes at least steps P11 to P13.

Step P11, the vehicle-mounted terminal 100 sends a command A1 to the wearable device 200, and the wearable device 200 receives the command A1 sent by the vehicle-mounted terminal 100, where the command A1 is used to instruct the wearable device 200 to run a corresponding current application of the at least one adjustable application.

Step P12, the wearable device 200 sends a resource acquisition request B1 to the vehicle-mounted terminal 100, and the vehicle-mounted terminal 100 receives the resource acquisition request B1 sent by the wearable device 200, where the resource acquisition request B1 is determined by the wearable device 200 based on the current application.

In step P13, the in-vehicle terminal 100 transmits the resource C1 to the wearable device 200 based on the resource acquisition request B1, and the wearable device 200 receives the resource C1 transmitted by the in-vehicle terminal 100.

For example, step P12 of the above embodiment may be performed before step T11, or may be performed after step P11, and step P12 and step P11 may also be performed simultaneously, which is not limited in this embodiment of the disclosure.

In some examples, the interaction method three further comprises the following process or steps: the wearable device 200 transmits a device registration request to the in-vehicle terminal 100, the in-vehicle terminal 100 receives the device registration request transmitted by the wearable device 200, and the in-vehicle terminal 100 adds the wearable device 200 to the currently available device list of the in-vehicle terminal 100 based on the device registration request, so that device registration of the wearable device 200 can be achieved.

In some examples, the third interaction method further includes the following process or steps: the wearable device 200 transmits a service registration request to the in-vehicle terminal 100, the in-vehicle terminal 100 receives the service registration request transmitted by the wearable device 200, and the in-vehicle terminal 100 adds a corresponding service to the currently available device service list based on the service registration request, so that registration of the service of the wearable device 200 can be achieved.

In some examples, the list of currently available devices includes: at least one of equipment identity identification code, equipment type, equipment name, equipment user name and equipment version information. In some examples, the list of currently available device services includes: at least one of a service identification code, a service type, a service name, service version information, service details, and a service support interface list.

Fig. 12 is a schematic structural diagram of an in-vehicle terminal 100 according to some embodiments of the present disclosure.

For example, as shown in fig. 1 and 12, some embodiments of the present disclosure provide a vehicle-mounted terminal 100 including a first processor 101 and a first memory 102. The first memory 102 is coupled to the first processor 101, the first memory 102 is used for storing computer program codes, the computer program codes comprise computer instructions, when the first processor 101 reads the computer instructions from the first memory 102, the vehicle-mounted terminal 100 is caused to execute the following operations: sending a command A1 to the wearable device 200, where the command A1 is used to instruct the wearable device 200 to run a corresponding current application of the at least one adjustable application; receiving a resource acquisition request B1 sent by the wearable device 200, wherein the resource acquisition request B1 is determined by the wearable device 200 based on the current application; and transmitting the resource C1 to the wearable device 200 based on the resource acquisition request B1.

In some examples, the in-vehicle terminal 100 further performs the following operations: receiving the device registration request D1 transmitted by the wearable device 200, and adding the wearable device 200 to the currently available device list of the in-vehicle terminal 100 based on the device registration request D1, thereby enabling device registration of the wearable device 200.

In some examples, the in-vehicle terminal 100 further performs the following operations: receiving a service registration request E1 sent by the wearable device 200, and adding a corresponding service to the currently available device service list based on the service registration request E1, thereby enabling registration of the service of the wearable device 200.

In some examples, the list of currently available devices includes: at least one of the equipment identity identification code, the equipment type, the equipment name, the equipment user name and the equipment version information. In some examples, the list of currently available device services includes: at least one of service identification code, service type, service name, service version information, service details and service support interface list.

In some examples, the in-vehicle terminal 100 performing receiving the service registration request E1 transmitted by the wearable device 200, and adding the corresponding service to the currently available device service list based on the service registration request E1 further includes the following: the vehicle-mounted terminal 100 receives a service registration request E1 sent by the wearable device 200, and stores entry information of a service in a target format to a current available device service list based on the service registration request E1, wherein at least one application interface corresponding to an adjustable application is configured to be registered in a local service management of the wearable device 200 in the form of the service, the service is indexed by at least two keywords, the at least two keywords comprise an application package name and an interface name, and the entry information in the target format comprises the device name and the service name.

In some examples, the execution of the command A1 by the in-vehicle terminal 100 to the wearable device 200 further includes the following: the vehicle-mounted terminal 100 provides a command A1 based on the current available device list and the current available device service list and sends the command A1 to the wearable device 200, wherein the command A1 is configured to obtain a service invocation parameter by parsing, that is, the command A1 is parsed to obtain the service invocation parameter by performing a service scheduling command, and the service invocation parameter is used for instructing the wearable device 200 to start a current application interface of a current application.

In some examples, command A1 includes a device name, a service name, and startup parameters. In some examples, the service invocation parameters include an application package name, an interface name, and a launch parameter. For example, the service invocation parameters take the form of (application package name, interface name, launch parameters) triplets. Of course, this is merely exemplary and not a limitation of the present disclosure.

In some examples, the in-vehicle terminal 100 performs the transmission of the resource C1 to the wearable device 200 based on the resource acquisition request B1, including the following: the vehicle-mounted terminal 100 provides resources required by the adjustable application and establishes a data channel with the current application so that the vehicle-mounted terminal 100 sends the resources to the wearable device 200.

In some examples, the in-vehicle terminal 100 is disposed on a vehicle, and is composed of an in-vehicle gateway, a Telematics BOX (T-BOX), a Human Machine Interface (HMI), a processor, a chassis control System, and an Automatic Driving System (ADS), and the like. In addition, the system for assisting the in-vehicle terminal 100 of the vehicle further includes a server that can provide various functions such as program upgrade, driving data storage, and the like. The T-Box is used for establishing communication contact with the server so as to realize interaction between the vehicle-mounted terminal 100 and the server. The vehicle-mounted gateway may have a wireless communication function, specifically, a Wi-Fi communication function, a bluetooth communication function, and the like, and is configured to establish a communication connection with the wearable device 200 to enable interaction between the vehicle-mounted terminal 100 and the wearable device 200. The chassis control system is used for realizing control over the chassis, and specifically can be used for braking, accelerating, steering and the like. The automatic driving system is used for realizing positioning, driving navigation, driving strategy calculation and the like of the vehicle. The HMI is used for displaying a user operation interface, and the processor is used for acquiring and executing instructions sent by a user through the HMI. Of course, this is merely exemplary and not a limitation of the present disclosure.

It should be noted that, for specific implementation, technical effects, and the like of the vehicle-mounted terminal 100, reference may be made to relevant contents of the interaction method for the wearable device and the vehicle-mounted terminal provided in the foregoing embodiments of the present disclosure, and details are not repeated here. It should be further noted that the vehicle-mounted terminal 100 may include more or fewer components, and the connection relationship between the components is not limited, which may be determined according to actual requirements, and the embodiment of the present disclosure is not limited or described herein.

For example, some embodiments of the present disclosure also provide a vehicle, which may include the vehicle-mounted terminal 100 in any of the above embodiments. It should be noted that, for clarity and conciseness of representation, not all the constituent elements of the vehicle are given in the embodiments of the present disclosure. In order to implement some necessary functions of the vehicle, those skilled in the art may provide and set other components not shown according to specific needs, and the embodiments of the present disclosure are not limited thereto, and are not repeated herein since they are not the important points of the present disclosure that need to be described. It should be further noted that, for specific implementation, technical effects, and the like of the vehicle, reference may be made to relevant contents of the vehicle-mounted terminal provided in the foregoing embodiments of the present disclosure, and details are not described herein.

Fig. 13 is a schematic structural diagram of a wearable device 200 according to some embodiments of the present disclosure.

For example, as shown in fig. 1 and 13, some embodiments of the present disclosure provide a wearable device 200 including a second processor 201 and a second memory 202. A second memory 202 is coupled to the second processor 201, the second memory 202 being adapted to store computer program code, the computer program code comprising computer instructions. When the second processor 201 reads the computer instructions from the second memory 202, the wearable device 200 performs the following operations: receiving a command A1 sent by the vehicle-mounted terminal 100, and running a corresponding current application in at least one adjustable application based on the command A1; sending a resource acquisition request B1 to the vehicle-mounted terminal 100, wherein the resource acquisition request B1 is determined by the wearable device 200 based on the current application; and receiving the resource C1 transmitted by the in-vehicle terminal 100 based on the resource acquisition request B1.

In some examples, wearable device 200 includes a display 203, display 203 configured to display a corresponding current application interface of a corresponding current application of at least one adjustable application of wearable device 200 that is launched based on the command.

In some examples, the wearable device 200 also performs at least one of: input audio, output audio, get control input events.

In some examples, wearable device 200 also performs the following operations: the vehicle-mounted terminal 100 is provided with a device registration request for instructing the vehicle-mounted terminal 100 to add the wearable device 200 to a currently available device list of the vehicle-mounted terminal 100. For example, the list of currently available devices includes: at least one of equipment identity identification code, equipment type, equipment name, equipment user name and equipment version information.

In some examples, the wearable device 200 further performs: a service registration request for instructing the in-vehicle terminal 100 to add a corresponding service to the currently available device service list is transmitted to the in-vehicle terminal 100. For example, the list of currently available device services includes: at least one of service identification code, service type, service name, service version information, service details and service support interface list.

In some examples, the wearable device 200 executing the receiving of the command sent by the in-vehicle terminal 100 and the running of the corresponding current application of the at least one tunable application based on the command further includes the following: the wearable device 200 receives the command and parses the command to obtain the service invocation parameters; and the wearable device 200 starts the current application interface of the current application based on the service invocation parameter. For example, the command includes a device name, a service name, and a startup parameter. For example, the service invocation parameters include an application package name, an interface name, and launch parameters.

In some examples, the interaction system of embodiments of the present disclosure includes a plurality of wearable devices 200, the plurality of wearable devices 200 being communicatively connected to each other to enable inter-modulation services with each other, such that a current application interface displayed on one of the plurality of wearable devices 200 is shared for display on the other wearable devices 200.

In some examples, the plurality of wearable devices 200 also perform the following operations: the plurality of wearable devices 200 are configured to communicate with the collaboration module such that the collaboration module collaborates services of the plurality of wearable devices 200. For example, the embodiments of the present disclosure may implement, through the collaboration module, sequencing the input events of the wearable devices 200, and redrawing the input events at each end in a uniform order, so as to achieve consistency of collaboration content at each end. For example, the function of joining a service collaboration may include multi-person authoring drawings, multi-person collaboration office or multi-person games, or the like. Of course, this is merely exemplary and not a limitation of the present disclosure.

It should be noted that, for specific implementation, technical effects, and the like of the wearable device 200, reference may be made to relevant contents of the interaction method for the wearable device and the vehicle-mounted terminal provided in the foregoing embodiments of the present disclosure, and details are not repeated here.

Fig. 14 is a block diagram of a vehicle-mounted terminal 100 and a wearable device 200 according to some embodiments of the present disclosure.

For example, as shown in fig. 14, a vehicle-mounted terminal 100 provided by at least one embodiment of the present disclosure includes a first service scheduling module 120 (i.e., a service scheduling module at a terminal where the vehicle-mounted terminal is located) and a backend resource service module 130. The first service scheduling module 120 is configured to communicatively couple with the wearable device 200 via the in-vehicle service bus 110.

For example, as shown in fig. 1, 3, 7 and 14, the first service scheduling module 120 is configured to transmit a command to the wearable device 200, the command being used to instruct the wearable device 200 to run a corresponding current application of the at least one adjustable application. The backend resource service module 130 is configured to provide resources required by the adjustable application, and a data channel is established between the backend resource service module 130 and the current application, so that the resources are sent to the wearable device 200 based on a resource acquisition request sent by the wearable device 200, where the resource acquisition request is determined by the wearable device 200 based on the current application.

In some examples, the back-end resource service module 130 can provide the wearable device 200 with necessary resources, such as movie files for an in-vehicle theater, applet downloads, in-vehicle sensor information acquisition, and so on. Of course, this is merely exemplary and not a limitation of the present disclosure.

In some examples, the vehicle terminal 100 further comprises a first device discovery module 160, the first device discovery module 160 being configured to communicatively connect with the wearable device 200 (e.g. a second device discovery module of the wearable device 200, see below in particular) to enable mutual discovery of the vehicle terminal 100 and the wearable device 200 with each other.

In some examples, the vehicle-mounted terminal 100 further includes a first authentication module 170, and the first authentication module 170 is configured to be communicatively connected with the wearable device 200 (e.g., a second authentication module of the wearable device 200, see below in particular) to enable authentication between the vehicle-mounted terminal 100 and the wearable device 200.

In some examples, the in-vehicle terminal 100 further includes a device management module 140, and the device management module 140 is configured to receive a device registration request sent by the wearable device 200 (e.g., a device registration module of the wearable device 200, see below in particular), and add the wearable device 200 to a list of currently available devices of the in-vehicle terminal 100 based on the device registration request, so that device registration of the wearable device 200 may be achieved. For example, the list of currently available devices includes: at least one of equipment identity identification code, equipment type, equipment name, equipment user name and equipment version information.

In some examples, the in-vehicle terminal 100 further includes a service management module 150 configured to receive a service registration request sent by the wearable device 200 (e.g., a device registration module of the wearable device 200, see below in particular), and add a corresponding service to a currently available device service list based on the service registration request, so that registration of the service of the wearable device 200 may be achieved. For example, the list of currently available device services includes: at least one of service identification code, service type, service name, service version information, service details and service support interface list.

For example, as shown in fig. 14, the wearable device 200 provided by at least one embodiment of the present disclosure includes a second service scheduling module 210 (i.e., a service scheduling module of a wearable device side), and the second service scheduling module 210 is configured to be communicatively connected with the vehicle-mounted terminal 100 (e.g., the first service scheduling module 120 of the vehicle-mounted terminal 100) through the vehicle-mounted service bus 110.

For example, as shown in fig. 1, 3, 7 and 14, the second service scheduling module 210 is configured to receive a command transmitted by the in-vehicle terminal 100 and run a corresponding current application of the at least one tunable application based on the command. For example, a data channel may be established between the current application and the in-vehicle terminal 100 (e.g., the back-end resource service module 130 of the in-vehicle terminal 100) so that the in-vehicle terminal 100 provides a resource to the current application.

For example, as shown in fig. 14, the wearable device 200 further includes a display 220, the display 220 configured to display a corresponding current application interface of a corresponding current application of at least one adjustable application in the wearable device that is initiated based on the command, such that the user may operate the application normally.

In some examples, the wearable device 200 further includes at least one of an audio input module 230, an audio output module 240, and a control input module 250. The audio input module 230 is configured to input audio, the audio output module 240 is configured to output audio, and the control input module 250 is configured to acquire control input events. For example, the audio input module 230 includes a headphone, the audio output module 240 includes a microphone, and the control input module 250 includes a touch pad. Of course, this is merely exemplary and not a limitation of the present disclosure.

In some examples, the wearable device 200 further includes a second device discovery module 280, the second device discovery module 280 configured to communicatively couple with the in-vehicle terminal 100 (e.g., the first device discovery module 160 of the in-vehicle terminal 100) to enable mutual discovery of the wearable device 200 and the in-vehicle terminal 100 with each other.

In some examples, the wearable device 200 further includes a second authentication and authentication module 290, and the second authentication and authentication module 290 is configured to be in communication connection with the vehicle-mounted terminal 100 (e.g., the first authentication and authentication module 170 of the vehicle-mounted terminal 100) to realize authentication and authentication between the wearable device 200 and the vehicle-mounted terminal 100.

In some examples, the wearable device 200 further comprises a device registration module 260, the device registration module 260 being configured to provide the vehicle terminal 100 with a device registration request for instructing the vehicle terminal 100 to add the wearable device 200 to a current available device list of the vehicle terminal 100. In this way, the wearable device 200 can register the present device with the in-vehicle terminal 100 through the device registration module and the in-vehicle service bus 110. For example, the list of currently available devices includes: at least one of equipment identity identification code, equipment type, equipment name, equipment user name and equipment version information.

In some examples, the wearable device 200 further includes a service registration module 270, the service registration module 270 configured to: a service registration request for instructing the in-vehicle terminal 100 to add a corresponding service to the currently available device service list is transmitted to the in-vehicle terminal 100. In this way, the wearable device 200 can register the available services on the device with the in-vehicle terminal 100 through the service registration module and the in-vehicle service bus 110. For example, the list of currently available device services includes: at least one of a service identification code, a service type, a service name, service version information, service details, and a service support interface list.

Fig. 15 is a partial module schematic diagram of a vehicle-mounted terminal 100 and a wearable device 200 according to some embodiments of the present disclosure.

For example, as shown in fig. 15, the service management module 150 of the in-vehicle terminal 100 includes a remote service registration unit 151 and a remote service management unit 152, and the service registration module 270 of the wearable device 200 includes a first local service management unit 271 and a service publishing unit 272.

For example, as shown in fig. 3, 5, 6, 7 and 15, the first local service management unit 271 is configured to register a service corresponding to at least one application interface corresponding to an adjustable application in the wearable device 200, that is, register an application interface corresponding to an adjustable application in the wearable device 200 in the form of a service in the first local service management unit 271. The service publishing unit 272 is configured to transmit a service registration request based on a service registered by the first local service managing unit 271, the service being indexed by at least two keywords including an application package name and an interface name.

For example, as shown in fig. 3, 5, 6, 7, and 15, the remote service registration unit 151 is configured to receive a service registration request through the in-vehicle service bus 110, and the remote service management unit 152 is configured to store entry information of a service in a target format including a device name and a service name to a currently available device service list based on the service registration request, so that registration of the service of the wearable device 200 may be achieved.

For example, for one navigation application software, a plurality of services such as a riding navigation service, a driving navigation service, a walking navigation service and the like can be corresponded according to different interfaces. Of course, this is merely exemplary and not a limitation of the present disclosure.

In some examples, the application package names corresponding to one service name may be different. For example, the service name to be invoked is a map application, and on different wearable devices, the service name can correspond to a Baidu map or a Gauss map. These correspondences may be maintained by the corresponding service scheduling modules. In some examples, the interface names corresponding to one service name may be different, for example, for a navigation interface, the actual interface names corresponding to a Baidu map and a Gade map may also be different. These correspondences are also maintained by the corresponding service scheduling modules.

In some examples, the service invoker initiates an invocation of a map navigation service with the following parameters: (DeviceID = xxx, serviceName = navigator, startParams { "start _ pos" = "Shanghai", "end _ pos" = "Shandong", "traffic _ tool" = "car", "method" = "naviwthpath"), where the command represents: invoking a navigation service on a wearable device with device name "xxx" and using a separate path navigation interface of the navigation service to initiate a self-driving navigation from Shanghai to Shandong. Thus, after being translated by the service scheduling module, the following commands are formed: (AppPkgName = "baidu mapnavi", activityName = "navi pathactivity", params = { "start _ from" = "sharghai", "end _ to" = "Shandong", "traffic _ tool" = "car" }.

For example, as shown in fig. 3, fig. 5, fig. 6, fig. 7, and fig. 15, the service management module 150 of the vehicle-mounted terminal 100 further includes a second local service management unit 153, and the second local service management unit 153 is configured to manage all services that can be invoked across terminals by a remote device (e.g., the wearable device 200) locally by the vehicle-mounted terminal 100, so that the wearable device 200 can query the service management module 150 of the vehicle-mounted terminal 100 for an available device service list, that is, the available device service list is maintained by the second local service management unit 153.

For example, as shown in fig. 3, 5, 6, 7 and 15, the second service scheduling module 210 of the wearable device 200 includes a local service scheduling unit 211 and a service scheduling command parsing unit 212. The first service scheduling module 120 is configured to provide a command based on the currently available device list and the currently available device service list, and send the command to the service scheduling command parsing unit 212 through the in-vehicle service bus 110, so that the service scheduling command parsing unit 212 parses the command to obtain the service invocation parameter, so that the local service scheduling unit 211 starts the current application interface of the current application based on the service invocation parameter, that is, converts the invocation request of the corresponding service into a local application invocation request, and runs the local application in the foreground with the correct parameter. As such, after the application is invoked, it may be output through the display 220 of the wearable device 200 as a screen, the headset and the microphone of the wearable device 200 as input and output of audio, respectively, and control input may also be implemented through the touchpad of the wearable device 200.

In the examples of fig. 14 to 15 of the present disclosure, the wearable device 200 can be dynamically added/removed to/from the vehicle-mounted terminal domain as a peripheral screen of the vehicle-mounted terminal 100 according to the user's requirement, and thus the expandability and flexibility of the vehicle-mounted terminal multi-screen processing are greatly enhanced. Moreover, the privacy that user's many screens of assurance that it can be very big degree were used prevents the mutual interference between different screens, and the user can only see the application screen of the wearable equipment of oneself wearing.

In some examples of the disclosure, the tunable application may have multiple modes of operation: for example, a native application running on the wearable device 200, or an application running on the in-vehicle terminal 100 and projected on the wearable device 200 for display, or a light application like a small program, so that the resource occupation burden of the in-vehicle terminal 100 can be effectively reduced.

In some examples, their corresponding service invocation parameters may be different for a plurality of different operating modes of the tunable application.

For example, for a native application running on a wearable device, the service invocation parameters may be exemplified as follows:

(DeviceID＝xxx,ServiceName＝Navigate,StartParams＝{“start_pos”＝

“Shanghai”,“end_pos”＝“Shandong”,“traffic_tool”＝“car”,“method”＝

“naviWithPath”)。

therefore, the service scheduling module of the wearable device end is required to find the native application start of the local end providing the navigation service.

For example, for a run mode of a screen-cast application, the service invocation parameters may be exemplified as follows:

(DeviceID＝xxx,ServiceName＝Sink,StartParams＝{“url”＝“192.168.0.1:5000”,“bit_rate”＝“2M”}。

therefore, a service scheduling module of the wearable device side is required to start a local screen projection client side, and the screen projection server side on the vehicle-mounted terminal is connected and screen projection content is played according to the transmitted parameters such as the uniform resource locator, the flow and the like.

For example, for a light application running mode, the service invocation parameters may be exemplified as follows:

(DeviceID＝xxx,ServiceName＝“QuickAppEngine”,StartParams＝{“url”＝“192.168.0.1:9898/sample.rpk”,“width”＝“640”,“height”＝“480”}。

thus, the service scheduling module on the wearable device side is required to start the local light application engine, download the corresponding light application resource package according to the incoming uniform resource locator, and display and run the light application in a window of 640 × 480.

Of course, the above description is only exemplary and not limiting of the present disclosure, and since this is not the focus of the description of the embodiments of the present disclosure, the detailed description is omitted here.

It should be noted that, in the embodiment of the present disclosure, the vehicle-mounted terminal 100 and/or the wearable device 200 may include more or fewer modules, and the connection relationship between the modules is not limited and may be determined according to actual needs. The specific configuration of each module is not limited. For specific implementation and technical effects of the vehicle-mounted terminal 100 and/or the wearable device 200, reference may be made to relevant contents of the interaction method provided in the foregoing embodiments of the disclosure, and details are not described here.

The various modules in the above embodiments may each be configured as software, hardware, firmware, or any combination thereof that performs a particular function. For example, the modules may correspond to an application specific integrated circuit, to pure software code, or to a combination of software and hardware.

It should be noted that, although the vehicle-mounted terminal 100 or the wearable device 200 is described above as being divided into modules for respectively executing corresponding processes, it is clear to those skilled in the art that the processes executed by the respective modules may also be executed without any specific module division by the vehicle-mounted terminal 100 or the wearable device 200 or explicit demarcation between the respective modules.

For example, the processes described above with reference to the flowcharts may be implemented as computer software programs, according to embodiments of the present disclosure. For example, embodiments of the present disclosure include a computer program product comprising a computer program carried on a non-transitory computer readable medium, the computer program containing program code for performing the method illustrated by the flow chart. The computer program, when executed by a processor, performs the interaction method of the disclosed embodiments.

It should be noted that the computer readable medium of the present disclosure may be a computer readable signal medium or a computer readable storage medium or any combination of the two. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples of the computer readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In embodiments of the disclosure, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In embodiments of the present disclosure, however, a computer readable signal medium may comprise a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: electrical wires, optical cables, RF (radio frequency), etc., or any suitable combination of the foregoing.

The computer readable medium may be included in the wearable device and/or the in-vehicle terminal; or may exist separately without being assembled into the wearable device and/or the in-vehicle terminal.

The following points need to be explained:

(1) The drawings of the embodiments of the disclosure only relate to the structures related to the embodiments of the disclosure, and other structures can refer to common designs.

(2) Without conflict, embodiments of the present disclosure and features of the embodiments may be combined with each other to arrive at new embodiments.

The above description is only a specific embodiment of the present disclosure, but the scope of the present disclosure is not limited thereto, and the scope of the present disclosure should be subject to the scope of the claims.

Claims (36)

1. An interaction method is provided, wherein a vehicle-mounted terminal and a wearable device establish communication connection, and the interaction method comprises the following steps:

the vehicle-mounted terminal sends a command to the wearable device, wherein the command is used for indicating the wearable device to run a corresponding current application in at least one adjustable application;

the vehicle-mounted terminal receives a resource acquisition request sent by the wearable device, wherein the resource acquisition request is determined by the wearable device based on the current application;

and the vehicle-mounted terminal sends resources to the wearable equipment based on the resource acquisition request.

2. The interaction method of claim 1, further comprising:

the vehicle-mounted terminal receives a device registration request sent by the wearable device, and adds the wearable device to a current available device list of the vehicle-mounted terminal based on the device registration request.

3. The interaction method of claim 2, further comprising:

the vehicle-mounted terminal receives a service registration request sent by the wearable device, and adds a corresponding service to a current available device service list based on the service registration request.

4. The interaction method of claim 3,

the list of currently available devices includes: at least one of equipment identity identification code, equipment type, equipment name, equipment user name and equipment version information; and/or the presence of a gas in the gas,

the list of currently available device services includes: at least one of a service identification code, a service type, a service name, service version information, service details, and a service support interface list.

5. The interaction method of claim 3,

the vehicle-mounted terminal receives a service registration request sent by the wearable device, and adds a corresponding service to a current available device service list based on the service registration request, wherein the service registration request comprises:

the vehicle-mounted terminal receives the service registration request sent by the wearable device and stores the item information of the service in a target format to the current available device service list based on the service registration request,

the at least one application interface corresponding to the tunable application is configured to be registered in the form of the service in local service management of the wearable device, the service is indexed by at least two keywords, the at least two keywords include an application package name and an interface name, and the entry information in the target format includes a device name and a service name.

6. The interaction method of claim 3, wherein the vehicle-mounted terminal sends a command to the wearable device, comprising:

the vehicle-mounted terminal provides the command to the wearable device based on the current available device list and the current available device service list.

7. The interaction method of claim 6, wherein the vehicle-mounted terminal sends a command to the wearable device, comprising:

and the vehicle-mounted terminal sends the command capable of obtaining the service calling parameter through analysis to the wearable equipment, wherein the service calling parameter is used for indicating the wearable equipment to start the current application interface of the current application.

8. The interaction method of claim 7,

the command comprises a device name, a service name and a starting parameter, and the service calling parameter comprises an application package name, an interface name and a starting parameter.

9. An interaction method is provided, wherein a vehicle-mounted terminal and a wearable device establish communication connection, and the interaction method comprises the following steps:

the wearable device receives a command sent by the vehicle-mounted terminal, and the wearable device runs a corresponding current application in at least one adjustable application in the wearable device based on the command;

the wearable device sends a resource acquisition request to the vehicle-mounted terminal, wherein the resource acquisition request is determined by the wearable device based on the current application;

and the wearable equipment receives the resource sent by the vehicle-mounted terminal based on the resource acquisition request.

10. The interaction method of claim 9, wherein the wearable device receives a command sent by the in-vehicle terminal, and the wearable device runs a corresponding current application of the at least one adjustable application based on the command, and comprises:

the wearable device receives a command sent by the vehicle-mounted terminal, and the wearable device starts a corresponding current application interface of a corresponding current application in at least one adjustable application in the wearable device based on the command, and,

displaying the current application interface of the current application on the wearable device.

11. The interaction method of claim 10, further comprising:

the wearable device sends a device registration request to the vehicle-mounted terminal, wherein the device registration request is used for instructing the vehicle-mounted terminal to add the wearable device to a current available device list of the vehicle-mounted terminal.

12. The interaction method of claim 11, further comprising:

the wearable device sends a service registration request to the vehicle-mounted terminal, wherein the service registration request is used for indicating the vehicle-mounted terminal to add a corresponding service to a current available device service list.

13. The interaction method of claim 12,

the list of currently available devices includes: at least one of equipment identity identification code, equipment type, equipment name, equipment user name and equipment version information; and/or the presence of a gas in the gas,

the list of currently available device services includes: at least one of service identification code, service type, service name, service version information, service details and service support interface list.

14. The interaction method of claim 10, wherein the wearable device receives a command sent by the in-vehicle terminal, and the wearable device starts a corresponding current application interface of a corresponding current application in at least one adjustable application in the wearable device based on the command, comprising:

the wearable device receives the command, analyzes the command and acquires a service calling parameter;

the wearable device starts the current application interface of the current application based on the service calling parameter.

15. The interactive method of claim 14,

the command comprises a device name, a service name and a starting parameter, and the service calling parameter comprises an application package name, an interface name and a starting parameter.

16. The interaction method of claim 9, further comprising:

in response to the wearable devices being a plurality of wearable devices, communicatively connecting the plurality of wearable devices to each other to enable inter-modulation services with each other such that a current application interface displayed on one of the plurality of wearable devices is shared for display on the other wearable devices.

17. An in-vehicle terminal comprising a first processor and a first memory, wherein the first memory is coupled to the first processor, wherein the first memory is configured to store computer program code, wherein the computer program code comprises computer instructions that, when read from the first memory by the first processor, cause the in-vehicle terminal to:

sending a command to a wearable device, wherein the command is used for instructing the wearable device to run a corresponding current application in at least one adjustable application;

receiving a resource acquisition request sent by the wearable device, wherein the resource acquisition request is determined by the wearable device based on the current application;

sending a resource to the wearable device based on the resource acquisition request.

18. The in-vehicle terminal of claim 17, wherein the in-vehicle terminal further performs:

receiving a device registration request sent by the wearable device, and adding the wearable device to a current available device list of the vehicle-mounted terminal based on the device registration request.

19. The in-vehicle terminal of claim 18, wherein the in-vehicle terminal further performs:

receiving a service registration request sent by the wearable device, and adding a corresponding service to a current available device service list based on the service registration request.

20. The in-vehicle terminal according to claim 19,

the list of currently available devices includes: at least one of equipment identity identification code, equipment type, equipment name, equipment user name and equipment version information; and/or the presence of a gas in the gas,

the list of currently available device services includes: at least one of service identification code, service type, service name, service version information, service details and service support interface list.

21. The in-vehicle terminal of claim 19, wherein the in-vehicle terminal performs receiving a service registration request sent by the wearable device and adding a corresponding service to a list of currently available device services based on the service registration request, comprising:

the vehicle-mounted terminal receives a service registration request sent by the wearable device and stores the item information of the service in a target format to the current available device service list based on the service registration request,

the at least one application interface corresponding to the adjustable application is configured to be registered in the local service management of the wearable device in the form of the service, the service is indexed by at least two keywords, the at least two keywords comprise an application package name and an interface name, and the entry information in the target format comprises a device name and a service name.

22. The vehicle terminal of claim 21, wherein the vehicle terminal performing the sending of the command to the wearable device comprises:

the vehicle-mounted terminal provides the command based on the current available equipment list and the current available equipment service list and sends the command to the wearable equipment, wherein the command is configured to obtain a service calling parameter through analysis, and the service calling parameter is used for indicating the wearable equipment to start the current application interface of the current application.

23. The in-vehicle terminal according to claim 22,

the command comprises a device name, a service name and a starting parameter, and the service calling parameter comprises an application package name, an interface name and a starting parameter.

24. The in-vehicle terminal of claim 17, wherein the in-vehicle terminal performs the sending of the resource to the wearable device based on the resource acquisition request, comprising:

the vehicle-mounted terminal provides resources required by the adjustable application, and a data channel is established between the vehicle-mounted terminal and the current application, so that the vehicle-mounted terminal sends the resources to the wearable device.

25. A vehicle, wherein the vehicle comprises the in-vehicle terminal according to any one of claims 17 to 24.

26. A wearable device comprising a second processor and a second memory, wherein the second memory is coupled to the second processor, wherein the second memory is configured to store computer program code comprising computer instructions that, when read from the second memory by the second processor, cause the wearable device to:

receiving a command sent by the vehicle-mounted terminal, and running a corresponding current application in at least one adjustable application based on the command;

sending a resource acquisition request to the vehicle-mounted terminal, wherein the resource acquisition request is determined by the wearable device based on the current application;

and receiving the resource sent by the vehicle-mounted terminal based on the resource acquisition request.

27. The wearable device of claim 26, wherein,

the wearable device includes a display configured to display a corresponding current application interface of a corresponding current application of at least one adjustable application of the wearable device that is launched based on the command.

28. The wearable device of claim 26, wherein,

the wearable device further performs at least one of: input audio, output audio, get control input events.

29. The wearable device of claim 26, wherein the wearable device further performs:

providing a device registration request to the vehicle-mounted terminal, wherein the device registration request is used for instructing the vehicle-mounted terminal to add the wearable device to a current available device list of the vehicle-mounted terminal.

30. The wearable device of claim 29, wherein the wearable device further performs:

and sending a service registration request to the vehicle-mounted terminal, wherein the service registration request is used for indicating the vehicle-mounted terminal to add the corresponding service to the current available equipment service list.

31. The wearable device of claim 30, wherein,

the list of currently available devices includes: at least one of equipment identity identification code, equipment type, equipment name, equipment user name and equipment version information; and/or the presence of a gas in the gas,

the list of currently available device services includes: at least one of service identification code, service type, service name, service version information, service details and service support interface list.

32. The wearable device of claim 31, wherein the wearable device performs receiving a command sent by the in-vehicle terminal and running a corresponding current application of at least one adjustable application based on the command, comprising:

the wearable device receives the command, analyzes the command and acquires a service calling parameter;

the wearable device starts the current application interface of the current application based on the service calling parameter.

33. The wearable device of claim 32, wherein,

the command comprises a device name, a service name and a starting parameter, and the service calling parameter comprises an application package name, an interface name and a starting parameter.

34. The wearable device of claim 26, wherein,

the wearable devices are a plurality of wearable devices which are in communication connection with each other to achieve mutual intermodulation service, so that the current application interface displayed on one of the wearable devices is shared and displayed on other wearable devices.

35. The wearable device of claim 34, wherein the plurality of wearable devices further performs:

the plurality of wearable devices are configured to communicate with a coordination module to cause the coordination module to coordinate services with the plurality of wearable devices.

36. A computer-readable storage medium, wherein a computer program is stored in the storage medium, which computer program, when being executed by a processor, carries out the interaction method according to any one of claims 1 to 16.

Images