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

Abstract

The present disclosure provides an interaction method, a vehicle terminal, a wearable device and a storage medium. The method is used for a vehicle terminal and a wearable device in communication connection, and comprises: the vehicle terminal sending a command to the wearable device, the command being used to instruct the wearable device to run a corresponding current application in at least one adjustable application; the vehicle terminal receiving a resource acquisition request sent by the wearable device, the resource acquisition request being determined by the wearable device based on the current application; and the vehicle terminal sending a resource to the wearable device based on the resource acquisition request. The present disclosure can use the wearable device as a physical screen in the vehicle terminal, effectively reduce the resource occupation burden of the vehicle terminal, effectively increase the number of applications that can run on multiple screens, solve the problem of limiting the number of simultaneous running instances of the same application, and effectively solve the problems of poor privacy and large mutual interference of multiple screens.

Description

TECHNICAL FIELD

[0001] Embodiments of the present disclosure relate to an interaction method, a vehicle terminal, a wearable device and a storage medium. BACKGROUND

[0002] With the continuous upgrading of vehicle terminal technology, a variety of application programs can be installed in the vehicle terminal. After the vehicle terminal starts the application program, the interface of the application program can be displayed on the corresponding display screen. For example, the vehicle entertainment system starts to develop in the direction of digitization and networking. Today, functions such as Bluetooth, navigation, music playing, etc. have become common functions of vehicles. In order to facilitate the driving personnel to quickly master the navigation information and communication information and other types of application information, the multiple display screens controlled by the vehicle terminal often display content at the same time. SUMMARY

[0003] At least one embodiment of the present disclosure provides an interaction method, in which a vehicle terminal and a wearable device establish a communication connection. The interaction method comprises: the vehicle terminal sends a command to the wearable device, wherein the command is used to instruct the wearable device to run a corresponding current application in at least one adjustable application; the vehicle terminal receives a resource acquisition request sent by the wearable device, the resource acquisition request being determined by the wearable device based on the current application; and the vehicle terminal sends a resource to the wearable device based on the resource acquisition request.

[0004] For example, the interaction method provided by at least one embodiment of the present disclosure further comprises: the vehicle 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 terminal based on the device registration request.

[0005] For example, the interaction method provided by at least one embodiment of the present disclosure further comprises: the vehicle 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.

[0006] For example, in the interaction method provided by at least one embodiment of the present disclosure, the current available device list comprises at least one of a device identity code, a device type, a device name, a device user name, and device version information; and / or the current available device service list comprises at least one of a service identity code, a service type, a service name, service version information, service details, and a service support interface list.

[0007] For example, in the interaction method provided in at least one embodiment of the present disclosure, the vehicle-mounted terminal receives the service registration request sent by the wearable device, and adds the corresponding service to the current 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 the service in the form of entry information of a target format to the current available device service list based on the service registration request, wherein the at least one application interface corresponding to the adjustable application is configured to be registered in the form of the service to the local service management of the wearable device, the service is indexed by at least two keywords, and the at least two keywords include an application package name and an interface name, and the entry information of the target format includes a device name and a service name.

[0008] For example, in the interaction method provided in at least one embodiment of the present disclosure, the vehicle-mounted terminal sends a command to the wearable device, including: 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.

[0009] For example, in the interaction method provided in at least one embodiment of the present disclosure, the vehicle-mounted terminal sends a command to the wearable device, including: the vehicle-mounted terminal sends the command by analyzing the service call parameters that can be obtained to the wearable device, wherein the service call parameters are used to instruct the wearable device to start the current application interface of the current application.

[0010] For example, in the interaction method provided in at least one embodiment of the present disclosure, the command includes a device name, a service name, and a start parameter, and the service call parameter includes an application package name, an interface name, and a start parameter.

[0011] In addition, at least one embodiment of the present disclosure also provides an interaction method, in which 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 device receives resources sent by the vehicle-mounted terminal based on the resource acquisition request.

[0012] For example, in the interaction method provided in at least one of the embodiments of the present disclosure, the wearable device receives the command sent by the vehicle-mounted terminal, and the wearable device runs a corresponding current application in at least one adjustable application based on the command, including: the wearable device receives the command sent by the vehicle-mounted terminal, and the wearable device starts a corresponding current application interface of the 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.

[0013] For example, the interaction method provided in at least one of the embodiments of the present disclosure further includes: the wearable device sends a device registration request to the vehicle-mounted terminal, where the device registration request is used to instruct the vehicle-mounted terminal to add the wearable device to a current available device list of the vehicle-mounted terminal.

[0014] For example, the interaction method provided in at least one of the embodiments of the present disclosure further includes: the wearable device sends a service registration request to the vehicle-mounted terminal, where the service registration request is used to instruct the vehicle-mounted terminal to add a corresponding service to a current available device service list.

[0015] For example, in the interaction method provided in at least one of the embodiments of the present disclosure, the current available device list includes at least one of a device identity code, a device type, a device name, a device user name, and device version information; and / or the current available device service list includes at least one of a service identity code, a service type, a service name, service version information, service details, and a service support interface list.

[0016] For example, in the interaction method provided in at least one of the embodiments of the present disclosure, the wearable device receives the command sent by the vehicle-mounted terminal, and the wearable device starts a corresponding current application interface of the corresponding current application in at least one adjustable application in the wearable device based on the command, including: the wearable device receives the command and parses the command to obtain a service calling parameter; and the wearable device starts the current application interface of the current application based on the service calling parameter.

[0017] For example, in the interaction method provided in at least one of the embodiments of the present disclosure, the command includes a device name, a service name, and a start parameter, and the service calling parameter includes an application package name, an interface name, and a start parameter.

[0018] For example, the interaction method provided in at least one embodiment of the present disclosure further includes: in response to the wearable device being one of a plurality of wearable devices, connecting the plurality of wearable devices to each other to realize mutual adjustment services, so that a current application interface displayed on one of the plurality of wearable devices is shared and displayed on the other wearable devices.

[0019] At least one embodiment of the present disclosure further provides a vehicle terminal, including a first processor and a first memory, wherein the first memory is coupled with the first processor, and the first memory is configured to store computer program codes including computer instructions, when the first processor reads the computer instructions from the first memory, so that the vehicle terminal performs the following operations: sending a command to a wearable device, wherein the command is used to instruct 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; and sending a resource to the wearable device based on the resource acquisition request.

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

[0021] For example, in the vehicle terminal provided in at least one embodiment of the present disclosure, the vehicle terminal further performs the following operations: 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.

[0022] For example, in the vehicle terminal provided in at least one embodiment of the present disclosure, the current available device list includes at least one of a device identity code, a device type, a device name, a device user name, and device version information; and / or, the current available device service list includes at least one of a service identity code, a service type, a service name, service version information, service details, and a service support interface list.

[0023] For example, in the vehicle terminal provided in at least one of the embodiments of the present disclosure, the vehicle terminal 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, which includes: the vehicle 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 local service management of the wearable device in the form of the service, the service is indexed by at least two keywords, and 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.

[0024] For example, in the vehicle terminal provided in at least one of the embodiments of the present disclosure, the vehicle terminal performs sending a command to the wearable device, which includes: the vehicle terminal provides the command based on the current available device list and the current available device service list, and sends the command to the wearable device, wherein the command is configured to be acquired by analyzing a service call parameter, and the service call parameter is used to instruct the wearable device to start the current application interface of the current application.

[0025] For example, in the vehicle terminal provided in at least one of the embodiments of the present disclosure, the command includes a device name, a service name and a start parameter, and the service call parameter includes an application package name, an interface name and a start parameter.

[0026] For example, in the vehicle terminal provided in at least one of the embodiments of the present disclosure, the vehicle terminal performs sending a resource to the wearable device based on the resource acquisition request, which includes: the vehicle terminal provides the resource required by the adjustable application, and establishes a data channel between the vehicle terminal and the current application, so that the vehicle terminal sends the resource to the wearable device.

[0027] At least one of the embodiments of the present disclosure also provides a vehicle, which includes the vehicle terminal in any of the above embodiments.

[0028] The at least one embodiment of the present disclosure further provides a wearable device, comprising a second processor and a second memory, wherein the second memory is coupled with the second processor, and the second memory is configured to store computer program codes, the computer program codes comprising computer instructions, when the second processor reads the computer instructions from the second memory, so that the wearable device performs the following operations: receiving a command sent by the vehicle 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 terminal, wherein the resource acquisition request is determined by the wearable device based on the current application; and receiving resources sent by the vehicle terminal based on the resource acquisition request.

[0029] For example, in the wearable device provided by at least one embodiment of the present disclosure, the wearable device comprises a display configured to display a corresponding current application interface of the corresponding current application in at least one adjustable application in the wearable device which is started based on the command.

[0030] For example, in the wearable device provided by at least one embodiment of the present disclosure, the wearable device further performs at least one of the following: inputting audio, outputting audio, and acquiring a control input event.

[0031] For example, in the wearable device provided by at least one embodiment of the present disclosure, the wearable device further performs the following operation: providing a device registration request to the vehicle terminal, wherein the device registration request is used to instruct the vehicle terminal to add the wearable device to a current available device list of the vehicle terminal.

[0032] For example, in the wearable device provided by at least one embodiment of the present disclosure, the wearable device further performs the following operation: sending a service registration request to the vehicle terminal, wherein the service registration request is used to instruct the vehicle terminal to add a corresponding service to a current available device service list.

[0033] For example, in the wearable device provided by at least one embodiment of the present disclosure, the current available device list comprises at least one of the following: a device identity code, a device type, a device name, a device user name, and device version information; and / or, the current available device service list comprises at least one of the following: a service identity code, a service type, a service name, service version information, service details, and a service support interface list.

[0034] For example, in the wearable device provided in at least one embodiment of the present disclosure, the wearable device receives the command sent by the vehicle terminal and runs a corresponding current application in at least one adjustable application based on the command, including: the wearable device receives the command and parses the command to obtain service call parameters; and the wearable device starts the current application interface of the current application based on the service call parameters.

[0035] For example, in the wearable device provided in at least one embodiment of the present disclosure, the command includes a device name, a service name and a start parameter, and the service call parameters include an application package name, an interface name and a start parameter.

[0036] For example, in the 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 realize mutual adjustment services, so that a current application interface displayed on one of the plurality of wearable devices is shared and displayed on other wearable devices.

[0037] For example, in the 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 collaboration module, so that the collaboration module performs service collaboration on the plurality of wearable devices.

[0038] 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 is executed by a processor to implement the interaction method described in any of the above examples. BRIEF DESCRIPTION OF DRAWINGS

[0039] In order to more clearly illustrate the technical solutions of the embodiments of the present disclosure or the prior art, the drawings needed in the embodiment or prior art description will be briefly introduced below. Obviously, 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 labor.

[0040] Figure 1 is a structural schematic diagram of an interaction system according to some embodiments of the present disclosure;

[0041] Figure 2 is a flowchart of an interaction method according to some embodiments of the present disclosure;

[0042] Figure 3 is a structural schematic diagram of an interaction system according to some embodiments of the present disclosure;

[0043] Figure 4is a flowchart of an interaction method according to some embodiments of the present disclosure;

[0044] Figure 5 is a principle diagram of device registration according to some embodiments of the present disclosure;

[0045] Figure 6 is a principle diagram of service registration according to some embodiments of the present disclosure;

[0046] Figure 7 is a principle diagram of service invocation according to some embodiments of the present disclosure;

[0047] Figure 8 is a flowchart of an interaction method according to some embodiments of the present disclosure;

[0048] Figure 9 is Figure 8 is a flowchart of an execution process of step T11 of the interaction method in

[0049] Figure 10 is Figure 9 is a flowchart of an execution process of step T111 of the interaction method in

[0050] Figure 11 is a flowchart of an interaction method according to some embodiments of the present disclosure;

[0051] Figure 12 is a structural diagram of a vehicle terminal according to some embodiments of the present disclosure;

[0052] Figure 13 is a structural diagram of a wearable device according to some embodiments of the present disclosure;

[0053] Figure 14 is a block diagram of a vehicle terminal and a wearable device according to some embodiments of the present disclosure;

[0054] Figure 15 is a partial module diagram of a vehicle terminal and a wearable device according to some embodiments of the present disclosure. DETAILED DESCRIPTION

[0055] 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. Obviously, the described embodiments are only some of the embodiments of the present disclosure, but not all the embodiments. Based on the embodiments in the present disclosure, all other embodiments obtained by those of ordinary skill in the art without creative work fall within the scope of protection of the present disclosure.

[0056] Unless otherwise defined, all terms (including technical and scientific terms) used in 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.

[0057] The terms "first", "second", and similar terms used in the present disclosure do not denote any order, quantity, or importance, but are used to distinguish different constituent elements. The terms "one", "a", or "the" and similar terms do not denote a quantity of particular mentioned items, but denote the presence of at least one of the items. Similarly, the terms "include", "comprise", and the like are intended to mean that the elements or objects listed after the terms encompass the elements or objects recited after the terms and equivalents thereof, without excluding other elements or objects. The terms "connected" or "coupled" and the like are not limited to physical or mechanical connections or couplings, but can include electrical connections or couplings, whether direct or indirect. Flowcharts are used in the present disclosure to illustrate steps of methods according to the present disclosure. It should be understood that the preceding or following steps do not necessarily proceed in order. Instead, various steps can be processed in reverse order or simultaneously. Other operations can also be added to or removed from the processes, or one or more steps can be removed from the processes. The inventors of the present disclosure have found that a plurality of screens are usually arranged in a vehicle terminal (for example, a vehicle machine intelligent cockpit) to output different display pictures, so as to realize physical multi-screen interaction and respond to the interaction operation of a user acting on a target application program on the multi-screens. In this way, the underlying implementation usually generates corresponding virtual screens for the plurality of physical screens by the operating system of the intelligent cockpit in a software layer, binds the target application program to 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.

[0058] The inventors of the present disclosure find through research that the prior art has the following problems: first, a plurality of physical screens need to be arranged in the intelligent cockpit, and the number and size of the screens are fixed and cannot be changed, resulting in high cost and poor scalability; second, 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 the operating system of the intelligent cockpit to have a large pressure, for example, when running heavy applications (such as playing high-definition movies or executing 3D games on multiple screens at the same time), all computing tasks are borne by the operating system of the intelligent cockpit, which makes the operating system of the intelligent cockpit a performance single point in the entire cockpit system, and often causes one or more applications to respond in a timely manner due to excessive computing pressure, and even affects the stability of the entire intelligent cockpit system; third, since all program applications are installed on the operating system of the intelligent cockpit, the number of applications that can run on the multiple screens is also limited by the number of applications installed on the operating system of the intelligent cockpit, and the number of instances of the same application that can run on the multiple screens at the same time is also limited; fourth, since the application programs are displayed on the plurality of physical screens in the intelligent cockpit, the privacy is weak, and the screens in the intelligent cockpit interfere with each other, which seriously limits the use scenarios of the multiple screens of the intelligent cockpit.

[0059] To solve the above problems, at least one embodiment of the present disclosure provides an interaction method for a vehicle terminal and a wearable device, the vehicle terminal and the wearable device establishing a communication connection, the interaction method comprising: the vehicle terminal sending a command to the wearable device, the command being used to instruct the wearable device to run a corresponding current application in at least one adjustable application; the vehicle terminal receiving a resource acquisition request sent by the wearable device, the resource acquisition request being determined by the wearable device based on the current application; and the vehicle terminal sending a resource to the wearable device based on the resource acquisition request.

[0060] To solve the above problems, at least one embodiment of the present disclosure provides an interaction method for a vehicle terminal and a wearable device, the vehicle terminal and the wearable device establishing a communication connection, the interaction method comprising: the vehicle terminal sending a command to the wearable device, the command being used to instruct the wearable device to run a corresponding current application in at least one adjustable application; the vehicle terminal receiving a resource acquisition request sent by the wearable device, the resource acquisition request being determined by the wearable device based on the current application; and the vehicle terminal sending a resource to the wearable device based on the resource acquisition request.

[0061] The interaction method of the embodiments of the present disclosure can make the wearable device act as a physical screen in the vehicle terminal, and can dynamically join or leave, greatly enhancing the expansibility and flexibility of the multi-screen processing of the vehicle terminal. The interaction method of the embodiments of the present disclosure can implement running an application on the wearable device, effectively reducing the resource occupation burden of the vehicle terminal, and because the application can be decomposed into being installed on the operating system of the vehicle terminal and the operating system of the wearable device respectively, the number of applications that can run on multiple screens is effectively increased, and the problem of limiting the number of simultaneous running instances of the same application can also be solved.

[0062] The vehicle terminal of at least one embodiment of the present disclosure further comprises a first processor and a first memory, the first memory is coupled with the first processor, the first memory is configured to store computer program code, the computer program code comprises computer instructions, when the first processor reads the computer instructions from the first memory, the vehicle terminal is caused to perform the following operations: sending a command to the wearable device, the command is used to instruct 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, the resource acquisition request is determined by the wearable device based on the current application; and sending a resource to the wearable device based on the resource acquisition request.

[0063] The vehicle terminal of the embodiments of the present disclosure can implement decomposing an application from being centrally installed on the operating system of the vehicle terminal to being installed on the operating system of the vehicle terminal and the operating system of the wearable device respectively, effectively reducing the resource occupation burden of the vehicle terminal, and effectively increasing the number of applications that can run on multiple screens, and also solving the problem of limiting the number of simultaneous running instances of the same application.

[0064] The vehicle terminal of the embodiments of the present disclosure can implement decomposing an application from being centrally installed on the operating system of the vehicle terminal to being installed on the operating system of the vehicle terminal and the operating system of the wearable device respectively, effectively reducing the resource occupation burden of the vehicle terminal, and effectively increasing the number of applications that can run on multiple screens, and also solving the problem of limiting the number of simultaneous running instances of the same application.

[0065] The wearable device of the above-mentioned embodiments of the present disclosure can be used as a physical screen in the vehicle terminal by cooperating with the vehicle terminal, and can dynamically join or leave, greatly enhancing the expansibility and flexibility of the multi-screen processing of the vehicle terminal. The wearable device of the above-mentioned embodiments of the present disclosure can run applications, thereby effectively reducing the resource occupation burden of the vehicle terminal, and because the applications are decomposed into the operating system of the vehicle terminal and the operating system of the wearable device, the number of applications that can run on the multi-screen is effectively increased, and the problem of limiting the number of simultaneous running instances of the same application can also be solved. The wearable device of the above-mentioned embodiments of the present disclosure has strong privacy, and can only be watched, listened to, and controlled by the wearer, which can effectively solve the problems of poor multi-screen privacy and large mutual interference.

[0066] Figure 1 is a structural schematic diagram of an interaction system according to some embodiments of the present disclosure. Figure 2 is a flowchart of an interaction method according to some embodiments of the present disclosure.

[0067] For example, as shown in Figure 1 , the interaction system 1000 according to some embodiments of the present disclosure includes a vehicle terminal 100 and a wearable device 200. The vehicle terminal 100 and the wearable device 200 establish a communication connection. For example, the vehicle terminal 100 and the wearable device 200 can establish a communication connection through a wireless communication module, such as Wi-Fi communication and Bluetooth communication. For example, after establishing a cross-terminal communication connection with each other, the wearable device 200 can communicate with the vehicle terminal 100, for example, with service-related information, through the vehicle service bus 110 arranged in the vehicle terminal 100.

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

[0069] Step S11, the vehicle terminal 100 sends a command A1 to the wearable device 200, wherein the command A1 is used to instruct the wearable device 200 to run a corresponding current application in at least one adjustable application.

[0070] Step S12, the vehicle terminal 100 receives 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.

[0071] Step S13, the vehicle terminal 100 sends a resource C1 to the wearable device 200 based on the resource acquisition request B1.

[0072] For example, step S12 of the above embodiment can be performed before step S11, or after step S11, or simultaneously with step S11, and the embodiments of the present disclosure do not limit this.

[0073] In some examples, the command A1 can be a service invocation command, which can be used to instruct the wearable device 200 to run the adjustable application, i.e., the embodiments of the present disclosure can run the adjustable application in the wearable device 200 based on the service invocation command.

[0074] In some examples, the interaction method one further includes the following process or step: the vehicle-mounted terminal 100 receives the device registration request sent by the wearable device 200, and adds the wearable device 200 to the current available device list of the vehicle-mounted terminal 100 based on the device registration request, so that the device registration of the wearable device 200 can be realized. In this way, the vehicle-mounted terminal 100 can maintain a list of devices that can be invoked in the vehicle-mounted terminal 100. For example, the current available device list includes at least one of a device identity code, a device type, a device name, a device user name, and device version information. For example, the device registration request is a data protocol packet corresponding to the above-mentioned current available device list and in a certain format.

[0075] The embodiments of the present disclosure can add the wearable device to the available device list of the vehicle-mounted terminal through device registration, realize the cooperation of the wearable device and the vehicle-mounted terminal, so that the wearable device can serve as a physical screen in the vehicle-mounted terminal and can dynamically join or leave, greatly enhancing the expansibility and flexibility of the multi-screen processing of the vehicle-mounted terminal.

[0076] In some examples, the interaction method one further includes the following process or step: the vehicle-mounted terminal 100 receives the service registration request sent by the wearable device 200, and adds the corresponding service to the current available device service list based on the service registration request, so that the registration of the service of the wearable device 200 can be realized. In this way, the vehicle-mounted terminal 100 can maintain a list of device services that can be invoked in the vehicle-mounted terminal 100. For example, the current available device service list includes at least one of a service identity code, a service type, a service name, service version information, service details, and a service support interface list. For example, the service registration request is a data protocol packet corresponding to the above-mentioned current available device service list and in a certain format.

[0077] The embodiments of the present disclosure can add the corresponding service to the device service list of the vehicle-mounted terminal through the registration of the service of the device, so that the application capabilities and hardware capabilities of the vehicle-mounted terminal and the wearable device can be effectively integrated.

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

[0079] In some examples, the wearable device 200 includes an augmented reality glasses (may also be referred to as AR glasses). The embodiments of the present disclosure cooperate with the vehicle terminal 100 by using the AR glasses, so that the embodiments of the present disclosure have a better experience and less limitation in video display and input method operation convenience, and can also have more available resources in system resources. Of course, this is merely exemplary and not a limitation of the present disclosure, for example, the wearable device 200 of the embodiments of the present disclosure can also be other devices developed by applying wearable technology to the intelligent design of daily wear, such as smart watches, smart gloves and other wearable devices configured with a communication module, which are not listed here. It should be noted that the wearable device used by some embodiments of the present disclosure is not only a hardware device, but also can realize powerful functions through software support and data interaction and cloud interaction.

[0080] Figure 3 is a structural schematic diagram of an interaction system proposed by another embodiment of the present disclosure. Figure 4 is a flowchart of an interaction method proposed by another embodiment of the present disclosure.

[0081] For example, as shown in Figure 3 and Figure 4 , the interaction method of some embodiments of the present disclosure at least includes steps S21-S25.

[0082] Step S21, the vehicle terminal 100 receives the device registration request D1 sent by the wearable device 200, and adds the wearable device 200 to the current available device list of the vehicle terminal 100 based on the device registration request D1.

[0083] Step S22, the vehicle terminal 100 receives the service registration request E1 sent by the wearable device 200, and adds the corresponding service to the current available device service list based on the service registration request E1.

[0084] Step S23, the vehicle terminal 100 sends a command A1 to the wearable device 200, wherein the command A1 is used to instruct the wearable device 200 to run a corresponding current application in at least one adjustable application.

[0085] Step S24, the vehicle terminal 100 receives the 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.

[0086] Step S25, the vehicle-mounted terminal 100 sends the resource C1 to the wearable device 200 based on the resource acquisition request B1.

[0087] For example, the step S24 of the above embodiment can be performed before the step S23, or can be performed after the step S23, or the step S24 and the step S23 can be performed simultaneously, and the embodiments of the present disclosure do not limit this.

[0088] In some examples, in the step S21, when the user wears the wearable device 200 into the vehicle-mounted terminal domain, the wearable device 200 is caused to negotiate and register the local device to the vehicle-mounted terminal 100 through the vehicle-mounted service bus 100, so that the device registration of the wearable device 200 can be realized.

[0089] In some examples, the vehicle-mounted terminal domain refers to the area range in which the wearable device 200 and the vehicle-mounted terminal 100 can discover each other. For example, using a discovery mode of low-power Bluetooth (i.e., Bluetooth BLE), the vehicle-mounted terminal domain refers to the broadcast discovery area of the low-power Bluetooth. For example, using a discovery mode of ultra-wideband (i.e., UWB), the vehicle-mounted terminal domain refers to the broadcast discovery area of the ultra-wideband. Of course, this is merely exemplary and is not a limitation of the present disclosure.

[0090] Figure 5 A principle diagram of device registration provided by some embodiments of the present disclosure. Figure 6 A principle diagram of service registration provided by some embodiments of the present disclosure. Figure 7 A principle diagram of service calling provided by some embodiments of the present disclosure.

[0091] In some examples, the wearable device 200 and the vehicle-mounted terminal 100 discover each other. For example, as shown in Figure 5 The wearable device 200 can complete the mutual discovery between devices with the vehicle-mounted terminal 100 in multiple ways, such as through Bluetooth BLE, USB cable, UWB, etc. Of course, this is merely exemplary and is not a limitation of the present disclosure. In this way, the embodiments of the present disclosure enter the next step of device interconnection and access to the vehicle-mounted service bus 110 after realizing the mutual discovery between devices.

[0092] In some examples, after the wearable device 200 and the vehicle-mounted terminal 100 realize the mutual discovery between each other, the authentication and authorization between the wearable device 200 and the vehicle-mounted terminal 100 can be performed. For example, as shown in Figure 5 The wearable device 200 can perform the authentication and authorization between devices with the vehicle-mounted terminal 100 in multiple ways, such as using an account, a personal identification code (i.e., PIN code), a two-dimensional code, etc. Of course, this is merely exemplary and is not a limitation of the present disclosure.

[0093] For example, such as Figure 5 As shown, after successful authentication of the wearable device 200, the wearable device 200 and the vehicle terminal 100 establish a private encrypted protocol channel to exchange device information. For example, the wearable device 200 sends its own device information to the vehicle terminal 100, and the vehicle terminal 100 adds the wearable device 200 to the list of currently available devices, thus registering the wearable device 200. In this way, the wearable device 200 can be added as an available external device to the list of available devices of the vehicle terminal 100. Simultaneously, the wearable device 200 and the vehicle terminal 100 can have a timed heartbeat strategy, ensuring that the list of available devices in the vehicle terminal 100 is updated promptly when the wearable device 200 goes offline. For example, the timed heartbeat strategy ensures that the wearable device and its services are truly callable, preventing other devices from calling the offline device's services after the wearable device has gone offline. For example, when a wearable device 200 goes offline and then comes back online, the aforementioned device registration and service registration will be performed again.

[0094] For example, such as Figure 6 As shown, in embodiments of this disclosure, at least one application interface corresponding to the adjustable application is configured to be registered as a service in the local service management of the wearable device 200. The service can be indexed by at least two keywords, and the at least two keywords include the application package name and the interface name.

[0095] For example, a navigation application may offer multiple services, such as cycling navigation, driving navigation, and walking navigation, depending on the interface. This is merely an example and is not intended to limit the scope of this disclosure.

[0096] For example, such as Figure 3 and Figure 6 As shown, step S22 may further include the following process or steps: the vehicle terminal 100 receives a service registration request E1 sent by the wearable device 200, and stores the service in a target format entry information to the currently available device service list based on the service registration request E1, thereby enabling the service registration of the wearable device 200. For example, the target format entry information may include the device name and service name. In some examples of this disclosure, any trusted device can query the vehicle terminal 100 for currently callable service information.

[0097] In some embodiments of this disclosure, the tunable application can register services as services, so that the application package name corresponding to the service name can be found in the registered information according to the service name, thereby realizing service scheduling and application operation.

[0098] In some examples, step S23 can further include the following process or step: in response to the registration of the service of the wearable device 200, the vehicle-mounted terminal 100 provides the wearable device 200 with the command A1 based on the current available device list and the current available device service list.

[0099] In some examples, as shown in Figure 7 , step S23 can further include the following process or step: the vehicle-mounted terminal 100 sends the wearable device 200 with the command A1 (e.g. Figure 7 , the service scheduling command analysis of the command A1 can obtain the service calling parameter), which is used to instruct the wearable device 200 to start the current application interface of the current application. For example, the service calling parameter includes the application package name, the interface name and the start parameter.

[0100] The above embodiments of the present disclosure can run the application on the wearable device, effectively reducing the resource occupation burden of the vehicle-mounted terminal, and because the application is installed on the operating system of the vehicle-mounted terminal and the operating system of the wearable device respectively, the number of multi-screen runable applications is effectively increased, and the limitation of the number of simultaneous running instances of the same application can also be solved.

[0101] In some examples of the present disclosure, the adjustable application can have multiple running modes: for example, a native application running on glasses, or an application running on the vehicle-mounted terminal 100 and displayed on the wearable device 200, or a light application similar to a small program, so as to effectively reduce the resource occupation burden of the vehicle-mounted terminal 100.

[0102] Figure 8 is a flowchart of an interaction method according to another embodiment of the present disclosure.

[0103] For example, as shown in Figure 1 and Figure 8 , the interaction method (e.g. denoted as interaction method two) of some embodiments of the present disclosure at least includes steps T11-T13.

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

[0105] Step T12, the wearable device 200 sends 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.

[0106] Step T13, the wearable device 200 receives the resource C1 sent by the vehicle-mounted terminal 100 based on the resource acquisition request B1.

[0107] For example, step T12 of the above embodiment can be performed before step T11, or after step T11, or simultaneously with step T11, and the embodiments of the present disclosure do not limit this.

[0108] Figure 9 is Figure 8 The flow chart of an execution process of step T11 of the interaction method in the second embodiment. For example, as shown in FIG. 11, one example of step T11 at least includes step T111 and step T112. Figure 9

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

[0110] Step T112, the current application interface of the current application is displayed on the wearable device 200.

[0111] The above embodiments of the present disclosure can use the wearable device as a physical screen in the vehicle terminal, and the wearable device can run applications, thereby effectively reducing the resource occupation burden of the vehicle terminal, and the wearable device has strong privacy, so that only the wearer can watch, listen and control, thereby effectively solving the problems of poor privacy and large mutual interference of multiple screens.

[0112] In some examples, the interaction method two further includes the following process or step: the wearable device 200 sends a device registration request to the vehicle terminal 100, wherein the device registration request is used to instruct the vehicle terminal 100 to add the wearable device 200 to the current available device list of the vehicle terminal 100. For example, the current available device list includes at least one of the device identity code, the device type, the device name, the device user name, and the device version information.

[0113] In some examples, the interaction method two further includes the following process or step: the wearable device 200 sends a service registration request to the vehicle terminal 100, wherein the service registration request is used to instruct the vehicle terminal 100 to add the corresponding service to the current available device service list. For example, the current available device service list includes at least one of the service identity code, the service type, the service name, the service version information, the service details, and the service support interface list.

[0114] Figure 10 is Figure 9 The flow chart of an execution process of step T111 of the interaction method in the second embodiment. For example, as shown in FIG. 11, one example of step T11 at least includes step T111 and step T112. Figure 10 ​As shown, one example of step T111 includes at least step T1111 and step T1112.

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

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

[0117] For example, in step T1111, the command A1 includes the device name, the service name and the start parameter. For example, the command A1 takes the form of a (device name, service name, start parameter) 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 the application package name, the interface name and the start parameter.

[0118] In some examples, the interaction method two further includes the following process or step: 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 realize mutual service adjustment, so that the current application interface displayed on one of the plurality of wearable devices 200 is shared and displayed on the other wearable devices 200.

[0119] For example, for the schedule on the wearable device 200 worn by user A in the vehicle terminal 100, under the condition of trust, the user A's own schedule can be shared in the form of a service to other users (e.g. user B) in the vehicle terminal 100, i.e. the wearable device 200 worn by user A and the wearable device 200 worn by user B can discover and connect each other and discover and call each other's services through the vehicle service bus, so that the wearable device 200 of user B in the vehicle terminal 100 can display the schedule of user A. In this way, not only can the service be scheduled through the vehicle terminal 100, but also all wearable devices 200 in the vehicle terminal 100 can call each other's services under the condition of sufficient trust, increasing the flexibility of service invocation.

[0120] Figure 11 A flowchart of an interaction method provided by some embodiments of the present disclosure.

[0121] For example, as shown in Figure 1 and Figure 11 The interaction method (e.g. denoted as interaction method three) of some embodiments of the present disclosure includes at least steps P11-P13.

[0122] 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 in at least one adjustable application.

[0123] 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.

[0124] Step P13, the vehicle-mounted terminal 100 sends a resource C1 to the wearable device 200 based on the resource acquisition request B1, and the wearable device 200 receives the resource C1 sent by the vehicle-mounted terminal 100.

[0125] For example, the step P12 of the above-mentioned embodiment can be executed before the step T11, or can be executed after the step P11, and the step P12 and the step P11 can also be performed simultaneously, and the embodiments of the present disclosure do not limit this.

[0126] In some examples, the interaction method three further includes the following process or step: the wearable device 200 sends a device registration request to the vehicle-mounted terminal 100, the vehicle-mounted terminal 100 receives the device registration request sent by the wearable device 200, and the vehicle-mounted terminal 100 adds the wearable device 200 to a current available device list of the vehicle-mounted terminal 100 based on the device registration request, so as to realize the device registration of the wearable device 200.

[0127] In some examples, the interaction method three further includes the following process or step: the wearable device 200 sends a service registration request to the vehicle-mounted terminal 100, the vehicle-mounted terminal 100 receives the service registration request sent by the wearable device 200, and the vehicle-mounted terminal 100 adds a corresponding service to a current available device service list based on the service registration request, so as to realize the registration of the service of the wearable device 200.

[0128] In some examples, the current available device list includes at least one of a device identity code, a device type, a device name, a device user name, and device version information. In some examples, the current available device service list includes at least one of a service identity code, a service type, a service name, service version information, service details, and a service support interface list.

[0129] Figure 12 is a structural schematic diagram of a vehicle-mounted terminal 100 according to some embodiments of the present disclosure.

[0130] For example, as Figure 1 and Figure 12As shown, the vehicle terminal 100 provided by some embodiments of the present disclosure includes a first processor 101 and a first memory 102. The first memory 102 is coupled to the first processor 101, and the first memory 102 is configured to store computer program codes including computer instructions. When the first processor 101 reads the computer instructions from the first memory 102, the vehicle terminal 100 is caused to perform the following operations: sending a command A1 to the wearable device 200, where the command A1 is configured to instruct the wearable device 200 to run a corresponding current application in at least one adjustable application; receiving 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; and sending a resource C1 to the wearable device 200 based on the resource acquisition request B1.

[0131] In some examples, the vehicle terminal 100 further performs the following operations: receiving a device registration request D1 sent by the wearable device 200, and adding the wearable device 200 to a current available device list of the vehicle terminal 100 based on the device registration request D1, so that the device registration of the wearable device 200 can be implemented.

[0132] In some examples, the 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 a current available device service list based on the service registration request E1, so that the registration of the service of the wearable device 200 can be implemented.

[0133] In some examples, the current available device list includes at least one of a device identity code, a device type, a device name, a device user name, and device version information. In some examples, the current available device service list includes at least one of a service identity code, a service type, a service name, service version information, service details, and a service support interface list.

[0134] In some examples, the vehicle terminal 100 performs the following operations: receiving a service registration request E1 sent by the wearable device 200, and adding a corresponding service to a current available device service list based on the service registration request E1, which further includes the following: the vehicle terminal 100 receives the service registration request E1 sent by the wearable device 200, and stores entry information of the service in a target format to the current available device service list based on the service registration request E1, where at least one application interface corresponding to the adjustable application is configured to be registered in a local service management of the wearable device 200 in the form of a service, the service is indexed by at least two keywords, and the at least two keywords include an application package name and an interface name, and the entry information of the service in the target format includes a device name and a service name.

[0135] In some examples, the vehicle terminal 100 performing sending the command A1 to the wearable device 200 further comprises the following: the vehicle terminal 100 provides the 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 the service call parameter by parsing the service call parameter, i.e., the service scheduling command of the command A1 is parsed to obtain the service call parameter, and the service call parameter is used to instruct the wearable device 200 to start the current application interface of the current application.

[0136] In some examples, the command A1 includes a device name, a service name, and a start parameter. In some examples, the service call parameter includes an application package name, an interface name, and a start parameter. For example, the service call parameter takes the form of a (application package name, interface name, start parameter) three-tuple. Of course, this is merely exemplary and not a limitation of the present disclosure.

[0137] In some examples, the vehicle terminal 100 performs sending the resource C1 to the wearable device 200 based on the resource acquisition request B1, comprising the following: the vehicle terminal 100 provides the resource required by the adjustable application, and establishes a data channel with the current application, so that the vehicle terminal 100 sends the resource to the wearable device 200.

[0138] In some examples, the vehicle terminal 100 is arranged on a vehicle and is composed of a vehicle gateway, a telematics box (T-Box), a human machine interface (HMI), a processor, a chassis control system, and an automated driving system (ADS), etc. In addition, the system for assisting the vehicle terminal 100 of the vehicle also includes a server, which can provide various functions such as program upgrading and driving data storage. The T-Box is used to establish communication with the server to realize the interaction between the vehicle terminal 100 and the server. The vehicle gateway can have a wireless communication function, specifically a Wi-Fi communication function, a Bluetooth communication function, etc., and is used to establish a communication connection with the wearable device 200 to realize the interaction between the vehicle terminal 100 and the wearable device 200. The chassis control system is used to realize the control of the chassis, specifically the brake, acceleration, steering, etc. The automated driving system is used to realize the positioning, driving navigation, driving strategy calculation, etc. of the vehicle. The HMI is used to display the user operation interface, and the processor is used to obtain and execute the instructions sent by the user through the HMI. Of course, this is merely exemplary and not a limitation of the present disclosure.

[0139] It should be noted that the specific implementation and technical effects of the vehicle terminal 100 can refer to the related content of the interaction method of the wearable device and the vehicle terminal provided in the above embodiments of the present disclosure, which will not be repeated here. It should also be noted that the vehicle terminal 100 can include more or fewer components, and the connection relationship between the components is not limited, and can be determined according to actual needs, and the embodiments of the present disclosure do not limit and repeat this.

[0140] For example, some embodiments of the present disclosure also provide a vehicle, which can include the vehicle terminal 100 in any of the above embodiments. It should be noted that, for the sake of clarity and simplicity, the embodiments of the present disclosure do not give all the constituent units of the vehicle. In order to achieve some necessary functions of the vehicle, those skilled in the art can provide, set up other constituent units not shown according to specific needs, and the embodiments of the present disclosure do not limit this, since this is not the focus of the present disclosure, which will not be repeated here. It should also be noted that the specific implementation and technical effects of the vehicle can refer to the related content of the vehicle terminal provided in the above embodiments of the present disclosure, which will not be repeated here.

[0141] Figure 13 is a structural schematic diagram of a wearable device 200 provided by some embodiments of the present disclosure.

[0142] For example, as shown in Figure 1 and Figure 13 some embodiments of the present disclosure provide a wearable device 200, which includes a second processor 201 and a second memory 202. The second memory 202 is coupled to the second processor 201, and the second memory 202 is configured to store computer program code, which includes computer instructions. When the second processor 201 reads the computer instructions from the second memory 202, the wearable device 200 executes the following operations: receiving a command A1 sent by the vehicle 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 terminal 100, the resource acquisition request B1 being determined by the wearable device 200 based on the current application; and receiving a resource C1 sent by the vehicle terminal 100 based on the resource acquisition request B1.

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

[0144] In some examples, the wearable device 200 further performs at least one of the following: inputting audio, outputting audio, and acquiring a control input event.

[0145] In some examples, the wearable device 200 further performs the following operation: providing a device registration request to the vehicle terminal 100, the device registration request being used to instruct the vehicle terminal 100 to add the wearable device 200 to a current available device list of the vehicle terminal 100. For example, the current available device list includes at least one of a device identity code, a device type, a device name, a device user name, and device version information.

[0146] In some examples, the wearable device 200 further performs the following operation: sending a service registration request to the vehicle terminal 100, the service registration request being used to instruct the vehicle terminal 100 to add a corresponding service to a current available device service list. For example, the current available device service list includes at least one of a service identity code, a service type, a service name, service version information, service details, and a service support interface list.

[0147] In some examples, the wearable device 200 performing the receiving of the command sent by the vehicle terminal 100 and the running of the corresponding current application in the at least one adjustable application based on the command further includes the following: the wearable device 200 receives the command and parses the command to obtain service call parameters; and the wearable device 200 starts a current application interface of the current application based on the service call parameters. For example, the command includes a device name, a service name, and a start parameter. For example, the service call parameters include an application package name, an interface name, and a start parameter.

[0148] In some examples, the interaction system of the embodiments of the present disclosure includes a plurality of wearable devices 200, which are communicatively connected to each other to realize mutual adjustment services so that a current application interface displayed on one of the plurality of wearable devices 200 is shared and displayed on the other wearable devices 200.

[0149] In some examples, the plurality of wearable devices 200 further perform the following operation: the plurality of wearable devices 200 are configured to communicate with a collaboration module so that the collaboration module performs service collaboration on the plurality of wearable devices 200. For example, the embodiments of the present disclosure can realize the ordering of input events of each wearable device 200 through the collaboration module and redraw in a unified order on each end to achieve consistent collaboration content on each end. For example, the functions that join the service collaboration can include multi-person creative drawing, multi-person collaborative office work, or multi-person games, etc. Of course, this is merely exemplary and is not a limitation of the present disclosure.

[0150] It should be noted that the specific implementation and technical effects of the wearable device 200 can refer to the related content of the above-mentioned embodiments of the interaction method between the wearable device and the vehicle terminal, which will not be repeated here.

[0151] Figure 14A block diagram of a vehicle terminal 100 and a wearable device 200 is provided for some embodiments of the present disclosure.

[0152] For example, as shown in Figure 14 The vehicle 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 of the terminal side) and a backend resource service module 130. The first service scheduling module 120 is configured to be communicatively connected with the wearable device 200 through a vehicle service bus 110.

[0153] For example, as shown in Figure 1 , Figure 3 , Figure 7 and Figure 14 The first service scheduling module 120 is configured to send a command to the wearable device 200, which instructs the wearable device 200 to run a corresponding current application in 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 resources are sent to the wearable device 200 based on a resource acquisition request sent by the wearable device 200, wherein the resource acquisition request is determined by the wearable device 200 based on the current application.

[0154] In some examples, the backend resource service module 130 can provide the wearable device 200 with necessary resources, such as movie files for a vehicle cinema, applet downloads, vehicle sensor information acquisition, etc. Of course, this is only exemplary and is not a limitation of the present disclosure.

[0155] In some examples, the vehicle terminal 100 further includes a first device discovery module 160, which is configured to be communicatively connected with the wearable device 200 (e.g., a second device discovery module of the wearable device 200, which can be seen below) to achieve mutual discovery between the vehicle terminal 100 and the wearable device 200.

[0156] In some examples, the vehicle terminal 100 further includes a first authentication module 170, which is configured to be communicatively connected with the wearable device 200 (e.g., a second authentication module of the wearable device 200, which can be seen below) to achieve mutual authentication between the vehicle terminal 100 and the wearable device 200.

[0157] In some examples, the vehicle terminal 100 also includes a device management module 140, which is configured to receive a device registration request sent by the wearable device 200 (e.g., the device registration module of the wearable device 200, as detailed below), and add the wearable device 200 to the currently available device list of the vehicle terminal 100 based on the device registration request, thereby enabling device registration of the wearable device 200. For example, the currently available device list includes at least one of the following: device identification code, device type, device name, device username, and device version information.

[0158] In some examples, the vehicle terminal 100 also includes a service management module 150. This service management module is configured to receive service registration requests from the wearable device 200 (e.g., the device registration module of the wearable device 200, as detailed below), and add the corresponding service to the currently available device service list based on the service registration request, thereby enabling the registration of services by the wearable device 200. For example, the currently available device service list may include at least one of the following: service identification code, service type, service name, service version information, service details, and a service support interface list.

[0159] For example, such as Figure 14 As shown, at least one embodiment of the wearable device 200 provided in this disclosure includes a second service scheduling module 210 (i.e., the service scheduling module on the wearable device side), which is configured to communicate with the vehicle terminal 100 (e.g., the first service scheduling module 120 of the vehicle terminal 100) via the vehicle service bus 110.

[0160] For example, such as Figure 1 , Figure 3 , Figure 7 and Figure 14 As shown, the second service scheduling module 210 is configured to receive commands sent by the vehicle terminal 100 and run the corresponding current application in at least one of the callable applications based on the commands. For example, the current application may have a data channel established with the vehicle terminal 100 (e.g., the backend resource service module 130 of the vehicle terminal 100) so that the vehicle terminal 100 can provide resources to the current application.

[0161] For example, such as Figure 14 As shown, the wearable device 200 also includes a display 220, which is configured to display the current application interface of the corresponding current application in at least one adjustable application of the wearable device that is launched based on a command, so that the user can operate the application normally.

[0162] In some examples, the wearable device 200 further comprises 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 obtain a control input event. For example, the audio input module 230 comprises a headset, the audio output module 240 comprises a microphone, and the control input module 250 comprises a touchpad. Of course, this is merely exemplary and not a limitation of the present disclosure.

[0163] In some examples, the wearable device 200 further comprises a second device discovery module 280 configured to be communicatively connected with the in-vehicle terminal 100 (e.g., the first device discovery module 160 of the in-vehicle terminal 100) to enable mutual discovery between the wearable device 200 and the in-vehicle terminal 100.

[0164] In some examples, the wearable device 200 further comprises a second authentication module 290 configured to be communicatively connected with the in-vehicle terminal 100 (e.g., the first authentication module 170 of the in-vehicle terminal 100) to enable mutual authentication between the wearable device 200 and the in-vehicle terminal 100.

[0165] In some examples, the wearable device 200 further comprises a device registration module 260 configured to provide a device registration request to the in-vehicle terminal 100, the device registration request being used to instruct the in-vehicle terminal 100 to add the wearable device 200 to a current available device list of the in-vehicle terminal 100. In this way, the wearable device 200 can register itself to the in-vehicle terminal 100 via the device registration module and the in-vehicle service bus 110. For example, the current available device list comprises at least one of a device identity code, a device type, a device name, a device user name, and device version information.

[0166] In some examples, the wearable device 200 further comprises a service registration module 270 configured to send a service registration request to the in-vehicle terminal 100, the service registration request being used to instruct the in-vehicle terminal 100 to add a corresponding service to a current available device service list. In this way, the wearable device 200 can register available services on itself to the in-vehicle terminal 100 via the service registration module and the in-vehicle service bus 110. For example, the current available device service list comprises at least one of a service identity code, a service type, a service name, a service version information, a service detail, and a service support interface list.

[0167] Figure 15 A partial module schematic diagram of the in-vehicle terminal 100 and the wearable device 200 according to some embodiments of the present disclosure.

[0168] For example, as shown in Figure 15 The service management module 150 of the 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.

[0169] For example, as shown in Figure 3 , Figure 5 , Figure 6 , Figure 7 and Figure 15 The first local service management unit 271 is configured to register services corresponding to at least one application interface of the adjustable application in the wearable device 200, i.e., to register the application interface of the 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 send a service registration request based on the service registered by the first local service management unit 271, which is indexed by at least two keywords and includes an application package name and an interface name.

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

[0171] For example, for a navigation application software, according to different interfaces, a plurality of services such as a riding navigation service, a driving navigation service, and a walking navigation service can be corresponded. Of course, this is only an example and is not a limitation of the present disclosure.

[0172] In some examples, the application package name corresponding to one service name can be different. For example, the service name to be called is a map application, and on different wearable devices, it can correspond to Baidu Map or Gaode Map. These corresponding relationships can be maintained by a corresponding service scheduling module. In some examples, the interface name corresponding to one service name can be different. For example, for a navigation interface, the actual interface name corresponding to Baidu Map and Gaode Map is also different. These corresponding relationships are also maintained by a corresponding service scheduling module.

[0173] In some examples, the service invoker initiates a call of a map navigation service with the following parameters: (DeviceID=xxx, ServiceName=Navigate, StartParams={“start_pos”=“Shanghai”, “end_pos”=“Shandong”, “traffic_tool”=“car”, “method”=“naviWithPath”}), where the command indicates that the navigation service on the wearable device with the device name “xxx” is called to start the self-driving navigation from Shanghai to Shandong using the independent path navigation interface of the navigation service. In this way, after being translated by the service scheduling module, the following command is formed: (AppPkgName=“baiduMapNavi”, ActivityName=“NaviPathActivity”, Params={“start_from”=“Shagnhai”, “end_to”=“Shandong”, “traffic_tool”=“car”}). The translated instruction indicates that the road navigation interface of the local Baidu map navigation application is invoked, the starting address is Shanghai, the destination address is Shandong, and the driving mode is driving. This is merely exemplary and is not a limitation of the present disclosure.

[0174] For example, as shown in Figure 3 、 Figure 5 、 Figure 6 、 Figure 7 and Figure 15 , the service management module 150 of the vehicle terminal 100 further includes a second local service management unit 153, which is configured to manage all services that can be cross-end called by the remote device (for example, the wearable device 200) in the local vehicle terminal 100, so that the wearable device 200 can query the available device service list from the service management module 150 of the vehicle terminal 100, that is, the available device service list is maintained by the second local service management unit 153.

[0175] For example, as shown in Figure 3 、 Figure 5 、 Figure 6 、 Figure 7 and Figure 15As shown, the second service scheduling module 210 of the wearable device 200 includes a local service scheduling unit 211 and a service scheduling command analysis unit 212. The first service scheduling module 120 is configured to provide a command based on the current available device list and the current available device service list, and send the command to the service scheduling command analysis unit 212 through the vehicle-mounted service bus 110, so that the service scheduling command analysis unit 212 analyzes the command to obtain a service call parameter, so that the local service scheduling unit 211 starts the current application interface of the current application based on the service call parameter, that is, converts the call request of the corresponding service into a local application call request and runs the local application in the foreground with correct parameters. In this way, after the application is started, the display 220 of the wearable device 200 can be used as a screen output, the earphone and microphone of the wearable device 200 can be used as the input and output of audio respectively, and the touchpad of the wearable device 200 can also be used to realize control input.

[0176] In some examples of the present disclosure, Figures 14-15 In some examples of the present disclosure,

[0177] In some examples of the present disclosure, the adjustable application can have multiple running modes: for example, a native application running on the wearable device 200, or an application running on the vehicle-mounted terminal 100 and projected to the wearable device 200 for display, or a light application similar to a small program, so as to effectively reduce the resource occupation burden of the vehicle-mounted terminal 100.

[0178] In some examples, for the multiple different running modes of the adjustable application, their corresponding service call parameters can be different.

[0179] For example, for the native application running on the wearable device, the service call parameter can be shown as follows:

[0180] (DeviceID=xxx,ServiceName=Navigate,StartParams={“start_pos”=

[0181] “Shanghai”,“end_pos”=“Shandong”,“traffic_tool”=“car”,“method”=

[0182] “naviWithPath”)。

[0183] Therefore, the service scheduling module of the wearable device needs to start the native application that provides the navigation service.

[0184] For example, for the running mode of the screen projection application, the service calling parameter can be shown as follows:

[0185] (DeviceID=xxx,ServiceName=Sink,StartParams={“url”=“192.168.0.1:5000”,“bit_rate”=“2M”}).

[0186] Therefore, the service scheduling module of the wearable device needs to start the local screen projection client, and connect the screen projection server on the vehicle terminal and play the screen projection content according to the uniform resource locator and the traffic parameter.

[0187] For example, for the running mode of the light application, the service calling parameter can be shown as follows:

[0188] (DeviceID=xxx,ServiceName=“QuickAppEngine”,StartParams={“url”=“192.168.0.1:9898 / sample.rpk”,“width”=“640”,“height”=“480”}).

[0189] Therefore, the service scheduling module of the wearable device needs to start the local light application engine, and download the corresponding light application resource package according to the uniform resource locator, and display and run the light application in a 640*480 window.

[0190] Of course, the above is only exemplary and is not a limitation of the present disclosure, since this is not the focus of the embodiments of the present disclosure to be described, and thus will not be described here.

[0191] It should be noted that in the embodiments of the present disclosure, the vehicle terminal 100 and / or the wearable device 200 can include more or fewer modules, and the connection relationship between the modules is not limited and can be determined according to actual needs. The specific constituting mode of each module is not limited. The specific implementation and technical effects of the vehicle terminal 100 and / or the wearable device 200 can refer to the related content of the interaction method provided in the above embodiments of the present disclosure, and thus will not be described here.

[0192] Each module in the above embodiments can be respectively configured as software, hardware, firmware or any combination of the above for performing specific functions. For example, these modules can correspond to dedicated integrated circuits, can also correspond to pure software code, and can also correspond to software and hardware combined modules.

[0193] It should be noted that although the vehicle terminal 100 or the wearable device 200 is divided into modules for performing respective processes in the above description, it is clear to those skilled in the art that the processes performed by the modules can also be performed without any specific module division or clear demarcation between the modules.

[0194] For example, according to embodiments of the present disclosure, the processes described above with reference to the flowcharts can be implemented as a computer software program. For example, embodiments of the present disclosure include a computer program product including a computer program carried on a non-transitory computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. When the computer program is executed by a processor, an interactive method of embodiments of the present disclosure is performed.

[0195] It should be noted that the computer-readable medium described above in the present disclosure can be a computer-readable signal medium or a computer-readable storage medium or any combination of the two. The computer-readable storage medium may, for example, but is not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or apparatus, or any combination of the above. More specific examples of the computer-readable storage medium can 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 disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In embodiments of the present disclosure, the computer-readable storage medium can be any tangible medium that contains or stores a program that can be used by or in conjunction with an instruction execution system, device or apparatus. In embodiments of the present disclosure, the computer-readable signal medium can include a data signal carried in a baseband or as a part of a carrier wave, which carries computer-readable program code. Such a propagated data signal can take on many forms, including but not limited to an electromagnetic signal, an optical signal, or any suitable combination of the above. The computer-readable signal medium can also be any computer-readable medium that is not a storage medium and that can communicate, propagate or transport program for use by or in connection with an instruction execution system, device or apparatus. The program code contained on the computer-readable medium can be transmitted using any suitable medium, including but not limited to a wire, an optical fiber, an RF (radio frequency) or the like, or any suitable combination of the above.

[0196] The computer-readable medium described above can be contained in the wearable device and / or the vehicle terminal described above; it can also exist separately without being assembled into the wearable device and / or the vehicle terminal.

[0197] The following needs to be explained:

[0198] (1) The drawings of the embodiments of the present disclosure only relate to the structures involved in the embodiments of the present disclosure, and other structures can be referred to the general design.

[0199] (2) In the case of no conflict, the embodiments of the present disclosure and the features in the embodiments can be combined with each other to obtain new embodiments.

[0200] The above is only a specific implementation of the present disclosure, but the protection scope of the present disclosure is not limited thereto, and the protection scope of the present disclosure should be subject to the protection scope of the claims.

Claims

1. An interaction method, wherein, The in-vehicle terminal and the wearable device establish a communication connection, and the interaction method includes: The vehicle terminal sends a command to the wearable device, wherein the command is used to instruct the wearable device to run the corresponding current application in at least one adjustable application; The vehicle 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; The vehicle-mounted terminal sends resources to the wearable device based on the resource acquisition request; The interaction method further includes: the vehicle terminal receiving a device registration request sent by the wearable device, and adding the wearable device to the currently available device list of the vehicle terminal based on the device registration request; The wearable device serves as the physical screen within the vehicle-mounted terminal. The interaction method further includes: the vehicle terminal receiving a service registration request sent by the wearable device, and adding the corresponding service to the currently available device service list based on the service registration request; The vehicle-mounted terminal receives a service registration request sent by the wearable device, and adds the corresponding service to the 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 the service in the target format as entry information into the currently 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 to the local service management of the wearable device in the form of the service, the service is indexed by at least two keywords and the at least two keywords include the application package name and the interface name, and the target format entry information includes the device name and the service name.

2. The interaction method as described in claim 1, wherein, The list of currently available devices includes at least one of the following: device identification code, device type, device name, device username, and device version information; and / or, The list of currently available device services includes at least one of the following: service identification code, service type, service name, service version information, service details, and service support interface list.

3. The interaction method as described in claim 1, wherein, The vehicle-mounted terminal sends commands to the wearable device, including: The vehicle terminal provides the command to the wearable device based on the list of currently available devices and the list of currently available device services.

4. The interaction method as described in claim 3, wherein, The vehicle-mounted terminal sends commands to the wearable device, including: The vehicle terminal sends a command to the wearable device, which can be parsed to obtain service call parameters, wherein the service call parameters are used to instruct the wearable device to launch the interface of the current application.

5. The interaction method as described in claim 4, wherein, The command includes the device name, service name, and startup parameters. The service call parameters include the application package name, interface name, and startup parameters.

6. An interaction method, wherein, The in-vehicle terminal and the wearable device establish a communication connection, and the interaction method includes: The wearable device receives commands sent by the vehicle terminal, and the wearable device runs the corresponding current application in at least one adjustable application in the wearable device based on the commands; The wearable device sends a resource acquisition request to the vehicle terminal, wherein the resource acquisition request is determined by the wearable device based on the current application; The wearable device receives resources sent by the vehicle terminal based on the resource acquisition request; The interaction method further includes: the wearable device sending a device registration request to the vehicle terminal, wherein the device registration request is used to instruct the vehicle terminal to add the wearable device to the vehicle terminal's currently available device list; The wearable device serves as the physical screen within the vehicle-mounted terminal. The interaction method further includes: the wearable device sending a service registration request to the vehicle terminal, wherein the service registration request is used to instruct the vehicle terminal to add the corresponding service to the currently available device service list in a target format; Wherein, at least one application interface corresponding to the adjustable application is configured to be registered to the local service management of the wearable device in the form of the service, the service is indexed by at least two keywords and the at least two keywords include the application package name and the interface name, and the target format entry information includes the device name and the service name.

7. The interaction method as described in claim 6, wherein, The wearable device receives commands sent by the in-vehicle terminal, and the wearable device runs at least one current application within an adjustable application based on the commands, including: The wearable device receives a command sent by the vehicle terminal, and based on the command, the wearable device launches the interface of the corresponding current application in at least one adjustable application within the wearable device, and... Display the interface of the current application on the wearable device.

8. The interaction method as described in claim 6, wherein, The list of currently available devices includes at least one of the following: device identification code, device type, device name, device username, and device version information; and / or, The list of currently available device services includes at least one of the following: service identification code, service type, service name, service version information, service details, and service support interface list.

9. The interaction method as described in claim 7, wherein, The wearable device receives a command sent by the vehicle terminal, and based on the command, the wearable device launches the interface of the current application corresponding to at least one adjustable application in the wearable device, including: The wearable device receives the command and parses the command to obtain service call parameters; The wearable device launches the interface of the current application based on the service call parameters.

10. The interaction method as described in claim 9, wherein, The command includes the device name, service name, and startup parameters. The service call parameters include the application package name, interface name, and startup parameters.

11. The interaction method as described in claim 6, further comprising: In response to the fact that the wearable device is multiple wearable devices, the multiple wearable devices are connected to each other to enable mutual service interoperability, so that the interface of the current application displayed on one of the multiple wearable devices is shared and displayed on other wearable devices.

12. A vehicle-mounted terminal, comprising a first processor and a first memory, wherein, The first memory is coupled to the first processor. The first memory stores computer program code, which includes computer instructions. When the first processor reads the computer instructions from the first memory, the vehicle terminal performs the following operations: Send a command to a wearable device, wherein the command is used to instruct the wearable device to run the corresponding current application in at least one adjustable application; Receive 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; Send resources to the wearable device based on the resource acquisition request; The vehicle terminal also performs the following actions: receiving a device registration request sent by the wearable device, and adding the wearable device to the current available device list of the vehicle terminal based on the device registration request; The wearable device serves as the physical screen within the vehicle-mounted terminal. The vehicle terminal also performs the following: receiving a service registration request sent by the wearable device, and adding the corresponding service to the currently available device service list based on the service registration request; The vehicle-mounted terminal receives a service registration request sent by the wearable device and adds the corresponding service to the currently available device service list based on the service registration request, including: The vehicle-mounted terminal receives a service registration request sent by the wearable device, and stores the service in a target format as an entry information in the currently 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 to the local service management of the wearable device in the form of the service, the service is indexed by at least two keywords and the at least two keywords include the application package name and the interface name, and the target format entry information includes the device name and the service name.

13. The vehicle-mounted terminal as described in claim 12, wherein, The list of currently available devices includes at least one of the following: device identification code, device type, device name, device username, and device version information; and / or, The list of currently available device services includes at least one of the following: service identification code, service type, service name, service version information, service details, and service support interface list.

14. The vehicle-mounted terminal as described in claim 13, wherein, The vehicle-mounted terminal sends commands to the wearable device, including: The vehicle terminal provides the command based on the list of currently available devices and the list of currently available device services, and sends the command to the wearable device. The command is configured to obtain service call parameters through parsing, and the service call parameters are used to instruct the wearable device to launch the interface of the current application.

15. The vehicle-mounted terminal as described in claim 14, wherein, The command includes the device name, service name, and startup parameters. The service call parameters include the application package name, interface name, and startup parameters.

16. The vehicle-mounted terminal as described in claim 12, wherein, The vehicle-mounted terminal sends resources to the wearable device based on the resource acquisition request, including: The vehicle-mounted terminal provides the resources required by the adjustable application and establishes a data channel with the current application so that the vehicle-mounted terminal can send the resources to the wearable device.

17. A vehicle, wherein, The vehicle includes the vehicle-mounted terminal as described in any one of claims 12-16.

18. A wearable device, comprising a second processor and a second memory, wherein, The second memory is coupled to the second processor. The second memory stores computer program code, which includes computer instructions. When the second processor reads the computer instructions from the second memory, the wearable device performs the following operations: Receive commands sent by the vehicle terminal, and run the corresponding current application in at least one adjustable application based on the commands; Send a resource acquisition request to the vehicle terminal, wherein the resource acquisition request is determined by the wearable device based on the current application; Receive the resources sent by the vehicle terminal based on the resource acquisition request; The wearable device also performs the following: providing a device registration request to the vehicle terminal, wherein the device registration request is used to instruct the vehicle terminal to add the wearable device to the vehicle terminal's list of currently available devices; The wearable device serves as the physical screen within the vehicle-mounted terminal. The wearable device also performs the following: sending a service registration request to the vehicle terminal, wherein the service registration request is used to instruct the vehicle terminal to add the corresponding service to the list of currently available device services in a target format; Wherein, at least one application interface corresponding to the adjustable application is configured to be registered to the local service management of the wearable device in the form of the service, the service is indexed by at least two keywords and the at least two keywords include the application package name and the interface name, and the target format entry information includes the device name and the service name.

19. The wearable device of claim 18, wherein, The wearable device includes a display configured to display the interface of the current application in at least one adjustable application of the wearable device that is launched based on the command.

20. The wearable device of claim 19, wherein, The wearable device also performs at least one of the following: inputting audio, outputting audio, and acquiring control input events.

21. The wearable device of claim 20, wherein, The list of currently available devices includes at least one of the following: device identification code, device type, device name, device username, and device version information; and / or, The list of currently available device services includes at least one of the following: service identification code, service type, service name, service version information, service details, and service support interface list.

22. The wearable device of claim 21, wherein, The wearable device executes commands received from the in-vehicle terminal and runs the corresponding current application in at least one adjustable application based on the commands, including: The wearable device receives the command and parses the command to obtain service call parameters; The wearable device launches the interface of the current application based on the service call parameters.

23. The wearable device of claim 22, wherein, The command includes the device name, service name, and startup parameters. The service call parameters include the application package name, interface name, and startup parameters.

24. The wearable device of claim 18, wherein, The wearable device comprises multiple wearable devices, which communicate with each other to enable mutual service interoperability, so that the interface of the current application displayed on one of the multiple wearable devices can be shared and displayed on other wearable devices.

25. The wearable device of claim 24, wherein, The multiple wearable devices also perform: The plurality of wearable devices are configured to communicate with the collaboration module so that the collaboration module can perform service collaboration on the plurality of wearable devices.

26. A computer-readable storage medium, wherein, The storage medium stores a computer program, which, when executed by a processor, implements the interactive method according to any one of claims 1 to 11.

Images