Linkage control method and device between wearable equipment and vehicle

Abstract

The invention discloses a linkage control method and device between wearable equipment and a vehicle. The method comprises the steps that the wearable device and the vehicle are connected through wireless communication; based on the attribute information of the wearable device and the option information of the vehicle, constructing an application for wearable device optimization; obtaining position information of the wearable device; and transmitting an application deactivation command or an application deletion command to the wearable device based on the location information of the wearable device.

Description

Technical Field

[0001] This disclosure relates to a method and apparatus for controlling the linkage between a wearable device and a vehicle. More specifically, this disclosure relates to a method and apparatus for controlling the linkage between a wearable device and a vehicle, wherein the vehicle has control over the linkage with the wearable device. Background Technology

[0002] The statements in this section are provided only as background information in relation to this disclosure and are not required to constitute prior art.

[0003] Wearable device technology is rapidly developing and being widely adopted. Wearable devices, including smartwatches, smart glasses, and smart rings, can provide users with a wide range of information in their daily lives. One function of wearable devices is to control or monitor various functions within a vehicle by connecting to it.

[0004] Traditionally, smartphones and vehicles connect via Bluetooth or Wi-Fi. However, bugs or security issues in smartphones can affect vehicle systems, leading to navigation malfunctions or leaks of personal information. Furthermore, vehicle control via smartphone is limited to a few functions, which does not fully satisfy the user experience.

[0005] Currently, there are no clearly defined specifications or standards for the connection between wearable devices and vehicles. Furthermore, if external devices control critical vehicle functions, the risk of safety vulnerabilities or accidents due to incorrect operation may increase. Therefore, vehicles should have primary control over the connection with wearable devices and be able to directly manage and control the use of wearable devices. Summary of the Invention

[0006] The purpose of this disclosure is to provide a method and apparatus for controlling wearable devices from a vehicle, wherein the vehicle has control over the wearable device.

[0007] The technical objectives of this disclosure are not limited to those described above. Other technical objectives not mentioned above will be clearly understood by those skilled in the art from the description given below.

[0008] This disclosure provides a method for controlling the linkage between a wearable device and a vehicle. The method includes: wirelessly connecting the wearable device and the vehicle; constructing a software program or application (i.e., an app) optimized for the wearable device based on attribute information of the wearable device and option information of the vehicle; obtaining location information of the wearable device; and sending an application deactivation command or an application deletion command to the wearable device based on the location information of the wearable device.

[0009] Another embodiment of this disclosure provides a control device for linking a wearable device with a vehicle. The device includes: at least one memory for storing commands; and at least one processor. The at least one processor is configured to perform: using a wireless communication connection between the wearable device and the vehicle; constructing an application optimized for the wearable device based on attribute information of the wearable device and option information of the vehicle; obtaining location information of the wearable device; and sending an application deactivation command or an application deletion command to the wearable device based on the location information of the wearable device.

[0010] According to one embodiment of this disclosure, the vehicle has control over the wearable device, thereby enabling the vehicle to directly manage the use of the wearable device.

[0011] The technical effects of this disclosure are not limited to those described above. Those skilled in the art to which this disclosure pertains may understand other technical effects not mentioned herein from the following description. Attached Figure Description

[0012] Figure 1 A block diagram of a wearable device control device according to an embodiment of the present disclosure is shown.

[0013] Figure 2 This is a flowchart illustrating the process of registering a wearable device according to an embodiment of the present disclosure.

[0014] Figure 3 This is a flowchart illustrating a process of pushing a software program or application (i.e., an app) to a wearable device according to an embodiment of the present disclosure.

[0015] Figure 4 This is a flowchart illustrating a process for deactivating an application based on location indication of a monitored wearable device, according to an embodiment of the present disclosure.

[0016] Figure 5 This is a flowchart illustrating the process of instructing the removal of an application based on the application's activation time, according to the present disclosure.

[0017] Figure 6 It is a block diagram of a computing device that can be used to implement the method or apparatus according to the present disclosure. Detailed Implementation

[0018] In the following description, some embodiments of this disclosure are described in detail with reference to the accompanying drawings. In the following description, the same reference numerals denote the same elements, although these elements are shown in different drawings. Furthermore, in the following description of some embodiments, detailed descriptions of known functions and configurations incorporated herein are omitted for clarity and brevity.

[0019] Furthermore, terms such as first, second, A, B, (a), (b), etc., are used only to distinguish one component from another and do not imply or suggest the nature, order, or sequence of the components. In this specification, when a component “comprises,” “has,” or “contains” a component, that component is intended to further include other components without excluding them, unless expressly stated to the contrary. Terms such as “unit,” “module,” etc., refer to one or more units for performing at least one function or operation, which may be implemented by hardware, software, or a combination thereof.

[0020] The following detailed description and appendix Figure 1 This disclosure is intended to describe embodiments of the invention and is not intended to represent the only embodiments that may be practiced. When components, controllers, systems, modules, units, devices, elements, etc. (i.e., elements) of this disclosure are described as having a purpose or performing an operation, function, etc., the components, controllers, systems, modules, units, devices, elements, etc., herein should be considered as "configured" to satisfy that purpose or perform that operation or function. Each component, controller, system, module, unit, device, element, etc., may be implemented individually or included as part of an element in a processor and memory (such as a non-transitory computer-readable medium).

[0021] Figure 1 A block diagram of a wearable device control device 100 according to an embodiment of the present disclosure is shown.

[0022] like Figure 1 As shown, a wearable device control device 100 according to an embodiment of the present disclosure includes all or part of an external device registration unit 110, a vehicle application (i.e., software program or application) setting unit 120, a remote application manager 130, a wearable device monitoring unit 140, and a voice recognition processor 150. Figure 1 The modules shown are not all necessary components. In other embodiments, some modules included in the wearable device control device 100 may be added, modified, or deleted. Figure 1 The constituent elements shown represent functionally different components, and at least one constituent element can be implemented in a physical environment by being integrated with another component.

[0023] Users can enter the vehicle and register wearable devices to the external device registration unit 110. Users can register wearable devices directly inside the vehicle. Users can also register wearable devices using a mobile application or service website.

[0024] The external device registration unit 110 can use short-range wireless communication (e.g., Wi-Fi or Bluetooth) to search for wearable devices. The external device registration unit can connect the wearable device to the vehicle via wireless communication.

[0025] Users can use a mobile phone application to input information from the wearable device into their mobile phone. The external device registration unit 110 can use the input wearable device information to search for wearable devices and automatically connect them to the vehicle. If the vehicle and wearable device are automatically connected, the user must approve the connection request from the vehicle.

[0026] When a wearable device is connected to a vehicle, the user can select an application and its temporary options, wherein the application can be used by an application on the wearable device. In this disclosure, temporary options refer to options that allow the user to decide whether to use the application continuously or temporarily.

[0027] Users can use a mobile application to pre-enter information about the applications they want to use and their temporary options.

[0028] When registering a wearable device, users can use the device to set the apps they want to use and select temporary options. Users can decide whether to use all apps or specific apps. Users can select temporary options for each app.

[0029] Users are free to change the information of registered wearable devices, the applications available for registered wearable devices, and the temporary options for those applications.

[0030] The process of registering a wearable device with a vehicle includes a process where the user approves the vehicle's control over the wearable device. Vehicle control may include the vehicle's permission to force the installation of necessary applications on the wearable device, the vehicle's permission to restrict the use of applications on the wearable device, and the vehicle's permission to remove applications from the wearable device.

[0031] The vehicle provides access to all apps installed on the wearable device. The vehicle has the right to restrict app usage and delete them. Therefore, user approval is required for control of the vehicle. Thus, the vehicle can maintain dominant control over the wearable device.

[0032] When a wearable device is registered, the external device registration unit 110 can check the linkage control options supported by the wearable device and store the wearable device's attribute information in the wearable device attribute database. The linkage control options may include supported feature options and hardware support options. Supported feature options may include whether the wearable device supports voice recognition, whether the wearable device has a touchpad function, and whether the wearable device provides haptic feedback. Hardware support options may include information about the display size and its availability, resolution, microphone availability, hardware key availability, and single-button jog availability. Wearable device attribute information may include attribute information about the wearable device regarding the supported feature options and hardware support options.

[0033] The external device registration unit 110 can use the registration information of the wearable device to search for registered wearable devices. If a registered wearable device is detected around the vehicle, the external device registration unit 110 can automatically connect the registered wearable device to the vehicle. The external device registration unit 110 can use wireless communication to search for wearable devices.

[0034] In this disclosure, the process of sending the application required for smooth communication between the vehicle and the wearable device and installing the application on the wearable device can be referred to as application push.

[0035] The vehicle application setting unit 120 can generate an application that includes available application functions based on the current vehicle options. The current vehicle options may include information about the vehicle options applied during vehicle manufacturing. This information about the current vehicle options can be stored in a vehicle option database.

[0036] The vehicle application setting unit 120 can check wearable device attribute information stored in the wearable device attribute database. The vehicle application setting unit 120 can use the wearable device attribute information to check control options that can be linked to the vehicle. Control options that can be linked to the vehicle may include supported feature options and hardware support options.

[0037] The vehicle application setting unit 120 can construct an application that supports wearable devices by considering vehicle option information and wearable device attribute information. The vehicle application setting unit 120 can check the attribute information of the wearable device and select an application optimized for the wearable device.

[0038] The vehicle application setting unit 120 can send application files optimized for connected wearable devices. The vehicle application setting unit 120 can instruct the wearable device to install the sent application.

[0039] Through the app push process, users can achieve different results compared to downloading apps from app stores. Users can efficiently utilize the storage space of their wearable devices because they don't have to download resource-intensive software containing unnecessary features. Because only essential and usable functions are installed on the wearable device based on vehicle options, the file size and functionality of downloaded apps can vary depending on the vehicle type, even for the same vehicle.

[0040] When a registered wearable device is connected to a vehicle, the vehicle application setting unit 120 can check whether any additional applications have been allowed to be installed due to changes in the wearable device's settings. The vehicle application setting unit 120 can check whether any additional applications have been installed due to changes in the wearable device's settings.

[0041] If the application is allowed to be installed but has not yet been installed, the vehicle application setting unit 120 can send an application file optimized for the connected wearable device and instruct the wearable device to install the application.

[0042] If a registered wearable device is connected to the vehicle, the vehicle application setting unit 120 can check whether the application can be deleted due to a change in settings. If the application can be deleted due to a change in settings, the vehicle application setting unit 120 can delete the application installed on the wearable device.

[0043] The remote application manager 130 can receive the location information of the wearable device from the wearable device monitoring unit 140.

[0044] The remote application manager 130 can disable or delete applications on the wearable device based on its location and temporary options. Applications installed on the wearable device can include temporary and permanent applications.

[0045] In this disclosure, a temporary application refers to an application that is downloaded and used when a wearable device is connected to a vehicle, and automatically deleted from the wearable device when the vehicle is turned off. When the vehicle and the wearable device are connected, the vehicle can automatically install the necessary temporary applications on the wearable device. When the vehicle is turned off, the wearable device can automatically delete the temporary applications. Temporary applications do not require separate user control. Temporary applications may include, for example, digital key applications related to vehicle ignition safety.

[0046] In this disclosure, a permanent application refers to an application that is automatically downloaded when the wearable device registers with the vehicle, activated when the vehicle and the wearable device are connected, and deactivated when the wearable device is removed from the vehicle. When the wearable device is connected to the vehicle, the vehicle may automatically activate the permanent application. When the wearable device is moved away from the vehicle, the vehicle may deactivate the permanent application. Permanent applications may include, for example, applications for controlling the vehicle's infotainment, navigation, and HVAC (heating, ventilation, and air conditioning) systems.

[0047] In one embodiment of this disclosure, a car rental operator can set all application attributes of wearable devices to be connected to the vehicle as temporary applications. When a registered wearable device is detected in the vehicle, and the car rental operator has set all application attributes of the wearable device in the vehicle as temporary applications, the vehicle can only offer the applications subscribed to by the wearable device. When the vehicle rental period ends, the wearable device control device 100 can send an application deletion command to the connected wearable device.

[0048] When using a wearable device to control a vehicle, the user may need to receive a linkage signal from the vehicle to control it. If no linkage signal is received from the vehicle, the application controlling the vehicle will not be activated. Inactive applications are not visible on the wearable device.

[0049] When the wearable device moves out of the vehicle, the remote application manager 130 can detect the wearable device's location and send an application deactivation command. The remote application manager 130 can send the application deactivation command to the wearable device wirelessly. Even if the wearable device moves away from the vehicle at high speed, the remote application manager 130 can still send commands to the wearable device via Bluetooth or Wi-Fi. The remote application manager 130 can deactivate the wearable device's applications based on the vehicle's speed.

[0050] The remote application manager 130 may have permission to delete temporary applications. When the wearable device is detached from the vehicle and the vehicle engine is off, the remote application manager 130 may send a command to delete the temporary applications.

[0051] The remote application manager 130 can send temporary application deletion commands to the wearable device as needed and revoke permissions held by the wearable device. After sending the temporary application deletion command to the wearable device, the remote application manager 130 removes the connection between the application and the wearable device. To reuse an application deleted from the wearable device, the user must re-register the application.

[0052] The remote application manager 130 may have the authority to disable applications on the wearable device. The remote application manager 130 can use the wearable device location monitoring unit to obtain the wearable device's location information. The remote application manager 130 can detect whether the wearable device has moved out of the vehicle and disable the applications installed on the wearable device. To prevent the user of the wearable device from controlling the vehicle from outside, the remote application manager 130 disables the applications on the wearable device.

[0053] The remote application manager 130 can restrict the use of individual applications based on driving speed. The vehicle sends its current driving speed to the wearable device, and the wearable device determines whether to activate or deactivate individual applications based on the received speed.

[0054] The remote application manager 130 can distinguish whether each wearable device belongs to a driver or a passenger. The remote application manager 130 can control certain functions of the applications based on the location of the wearable devices and the vehicle speed. The control settings for vehicle speed and passenger location are determined when each application is installed on the wearable device. When the vehicle sends its current speed to the wearable device, the wearable device can restrict the use of the applications.

[0055] For example, the remote application manager 130 can disable applications on the wearable device when the driving speed exceeds 30 kilometers per hour (km / h), especially applications that include video content. In another example, when the driving speed exceeds 100 km / h, the remote application manager 130 can control the wearable device to perform only voice-based operations. If a passenger is using the wearable device, the remote application manager 130 can allow the passenger to use all application functions regardless of the driving speed.

[0056] The wearable device monitoring unit 140 can check the location of the wearable device. The wearable device monitoring unit 140 can send the location information of the wearable device to the remote application manager 130.

[0057] The wearable device monitoring unit 140 can determine whether the wearable device is separated from the vehicle by using wireless communication between the vehicle and the wearable device. The wearable device monitoring unit 140 can use the signal strength of the wireless connection and the ping signal between the vehicle and the wearable device to check the distance between them. The ping signal is used to check the connection status and response time between two devices in a network or wireless communication system. The wearable device monitoring unit 140 can determine the distance or connection status between the vehicle and the wearable device by sending a ping signal to the wearable device and measuring the response time of the wearable device.

[0058] The wearable device monitoring unit 140 can use the vehicle's wireless antenna to detect the presence of wearable devices inside the vehicle.

[0059] The method of using signal strength and ping signals to determine whether a wearable device is separated from a vehicle is susceptible to interference from surrounding radio waves and may be inaccurate if the wearable device is very close to the vehicle. Therefore, this disclosure proposes a method that complements the method of using wireless communication to determine the separation of a wearable device from a vehicle.

[0060] If the wearable device is near the vehicle, the vehicle can wirelessly identify the wearable device and establish a connection with it. The application controlling the vehicle is not immediately activated.

[0061] The remote application manager 130 only sends an application activation message to the wearable device after confirming the wireless signal strength, wireless location, and that the vehicle doors are closed. For example, the remote application manager 130 may only send an application activation message to the wearable device after confirming that the signal strength between the vehicle and the wearable device is strong enough, that the wearable device is inside the vehicle, and that the vehicle doors are closed.

[0062] When the car door is opened, the remote application manager 130 can send an application deactivation command to the wearable device. By deactivating the application after confirming that the door is open, the user is prevented from controlling the vehicle using the wearable device from outside the vehicle.

[0063] The wearable device monitoring unit 140 can determine the location of the wearable device within the vehicle. For example, the wearable device monitoring unit 140 can determine whether the driver is wearing the wearable device. In another example, the wearable device monitoring unit 140 can determine whether the passenger is wearing the wearable device.

[0064] The wearable device monitoring unit 140 can determine which seat in the vehicle the wearable device is located on. For example, the wearable device monitoring unit 140 can determine the specific seat where the wearable device is located, such as the driver's seat, the front passenger seat, the left seat in the second row, or the right seat in the second row.

[0065] The wearable device monitoring unit 140 can send confirmed location information to the wearable device. Based on the confirmed location information, the wearable device may be subject to application usage restrictions. The confirmed location information of the wearable device can be stored in a wearable device location determination result database. The stored location information can be used by the remote application manager 130.

[0066] The voice recognition processor 150 can choose to use either the vehicle's voice recognition or the voice recognition of a wearable device.

[0067] If a wearable device with a voice recognition microphone located near the user's mouth is registered with the vehicle, the voice recognition processor 150 can use the wearable device's voice recognition. The wearable device can receive the user's voice commands and preprocess them. The preprocessing process may include, for example, processes for removing voice noise and removing echo signals. The wearable device can then send the preprocessed voice to the voice recognition processor 150. When a wearable device with a voice recognition microphone located near the user's mouth is registered with the vehicle, the voice recognition processor 150 uses only the voice information sent by the wearable device and ignores the voice information collected by the vehicle.

[0068] If a wearable device without a voice recognition microphone or with the microphone located far from the user's mouth is registered with the vehicle, the voice recognition processor 150 can set an option to enable voice recognition for the vehicle. The voice recognition processor 150 uses voice data collected from the vehicle.

[0069] Figure 2 This is a flowchart illustrating the process of registering a wearable device according to an embodiment of the present disclosure.

[0070] The wearable device controller 100 can use short-range wireless communication such as Wi-Fi or Bluetooth to search for wearable devices and establish a connection with the wearable devices (S200).

[0071] Users can use a mobile phone application to input information about the wearable device into their mobile phone. The external device registration unit 110 can use the input wearable device information to search for wearable devices and automatically connect them to the vehicle. If the vehicle and the wearable device connect automatically, the user must approve the connection request from the vehicle.

[0072] After entering the vehicle, the user can register the wearable device with the vehicle (S210). The user can register the wearable device directly inside the vehicle or outside the vehicle via a mobile application or service webpage. When the wearable device is connected to the vehicle, the user can select applications that can be used by the wearable device's application and their temporary options. In this disclosure, temporary options refer to options that allow the user to decide whether to use the application continuously or temporarily.

[0073] When a wearable device is registered, the wearable device control unit 100 can check the linkage control options supported by the wearable device and store the wearable device's attribute information in the wearable device attribute database (S220). The linkage control options may include supported feature options and hardware support options. Supported feature options may include whether the wearable device supports voice recognition, whether the wearable device has a touchpad function, and whether the wearable device provides haptic feedback. Hardware support options may include information about the display size and whether it is supported, resolution, the presence or absence of a microphone, the availability of hard keys, and the availability of a single-button jog. The wearable device attribute information may include attribute information about the wearable device regarding the supported feature options and hardware support options.

[0074] Figure 3 This is a flowchart illustrating a process of pushing an application to a wearable device according to an embodiment of the present disclosure.

[0075] The wearable device controller 100 can check whether the wearable device is connected to the vehicle (S300). If it is not connected (no at S300), the wearable device controller 100 will check for a connection or connect the wearable device and the vehicle.

[0076] When the wearable device is connected to the vehicle (yes at S300), the wearable device control unit 100 can set up a linkage application for using the functions provided by the vehicle via the wearable device (S310). Based on the assumption that the vehicle is equipped with all available options, all default settings of the linkage application have the same size. The vehicle application setting unit 120 can set up the linkage application considering the functions that vary depending on the options provided by the vehicle. For example, the vehicle application setting unit 120 can rebuild the application to perform functions that vary depending on the options for each vehicle. The process of rebuilding the application may include an application optimization process.

[0077] The wearable device control unit 100 can check the current vehicle options (S320). The current vehicle options may include information about the vehicle options applied during vehicle manufacturing. The information about the current vehicle options can be stored in a vehicle option database.

[0078] The wearable device control unit 100 can check wearable device attribute information stored in the wearable device attribute database (S330). The vehicle application setting unit 120 can use the wearable device attribute information to check control options that can be linked to the vehicle. Control options that can be linked to the vehicle may include supported feature options and hardware support options.

[0079] The wearable device control device 100 can construct an application supporting the wearable device by considering vehicle option information and wearable device attribute information (S340). For example, the vehicle application setting unit 120 can construct an application that includes functions supported by the vehicle based on the vehicle option information. In another example, the vehicle application setting unit 120 can construct an application that includes functions supported by the wearable device based on the wearable device attribute information. In this disclosure, the process of selecting an application by considering vehicle option information and wearable device attribute information is referred to as an optimization process.

[0080] The wearable device control device 100 can send an application file optimized for the connected wearable device (S350). The wearable device control device 100 can instruct the wearable device to install the sent application. The wearable device control device 100 can select applications supported by the wearable device and instruct the wearable device to install the selected application.

[0081] Figure 4 This is a flowchart illustrating a process for instructing the deactivation of an application based on the location of a monitored wearable device, according to an embodiment of the present disclosure.

[0082] The wearable device controller 100 can check whether the wearable device is connected to the vehicle (S400). If it is not connected (no at S400), the wearable device controller 100 will check for a connection or connect the wearable device and the vehicle.

[0083] When the wearable device is connected to the vehicle (yes at S400), the wearable device controller 100 can check the location of the wearable device (S410).

[0084] The wearable device monitoring unit 140 can determine whether the wearable device is separated from the vehicle by using wireless communication between the vehicle and the wearable device. The wearable device monitoring unit 140 can use the signal strength of the wireless connection and the ping signal between the vehicle and the wearable device to check the distance between them. The ping signal is used to check the connection status and response time between two devices in a network or wireless communication system. The wearable device monitoring unit 140 can determine the distance or connection status between the vehicle and the wearable device by sending a ping signal to the wearable device and measuring the response time of the wearable device.

[0085] The wearable device control device 100 can use the vehicle's wireless antenna to detect the presence of a wearable device inside the vehicle (S420). If no wearable device is detected in the vehicle (no at S420), the wearable device control device 100 will continue the check. The wearable device control device 100 can supplement the method of determining the presence of a wearable device inside the vehicle by checking the vehicle door information.

[0086] When a wearable device is detected inside the vehicle (Yes at S420), the wearable device monitoring unit 140 can determine the location of the wearable device inside the vehicle. For example, the wearable device monitoring unit 140 can determine whether the driver is wearing a wearable device. In another example, the wearable device monitoring unit 140 can determine whether a passenger is wearing a wearable device.

[0087] The wearable device monitoring unit 140 can determine which seat in the vehicle the wearable device is located in. For example, the wearable device monitoring unit 140 can determine the specific seat in which the wearable device is located, such as the driver's seat, the front passenger seat, the left seat in the second row, or the right seat in the second row.

[0088] The wearable device control device 100 can send an application deactivation command to the wearable device based on the location of the wearable device (S430).

[0089] The wearable device control unit 100 may have the authority to disable applications on the wearable device. The wearable device control unit 100 may use the wearable device monitoring unit 140 to obtain the location information of the wearable device. The remote application manager 130 may detect whether the wearable device has moved out of the vehicle and disable applications installed on the wearable device. To prevent the user of the wearable device from controlling the vehicle from outside the vehicle, the wearable device control unit 100 disables applications on the wearable device.

[0090] Figure 5 This is a flowchart illustrating the process of instructing the removal of an application based on the application's activation time, according to the present disclosure.

[0091] The wearable device controller 100 can check whether the wearable device is connected to the vehicle (S500). If it is not connected (no at S500), the wearable device controller 100 will check for a connection or connect the wearable device and the vehicle.

[0092] When the wearable device is connected to the vehicle (yes at S500), the wearable device control unit 100 can monitor the application activation time of the wearable device (S510). For example, the wearable device control unit 100 can check whether the application installed on the wearable device is a temporary application or a permanent application.

[0093] The wearable device control unit 100 can determine whether the activation time of an application installed on the wearable device has expired (S520). For example, if the installed application is a temporary application, the wearable device control unit 100 can determine whether the application's activation time has expired by checking when the vehicle engine is turned off. Temporary applications may include, for example, digital key applications related to vehicle ignition safety.

[0094] The wearable device control unit 100 can send a command to the wearable device to delete an application whose activation time has expired (S530). For example, if the installed application is a temporary application, the wearable device control unit 100 can send a command to the wearable device to delete the application once it confirms that the activation time has expired due to the vehicle engine being turned off (yes at S520). If the activation time has not yet expired (no at S520), the wearable device control unit 100 will not send a command and will continue to check the activation time.

[0095] Figure 6 It is a block diagram of a computing device that can be used to implement the method or apparatus according to the present disclosure.

[0096] Computing device 600 may include all or part of memory 610, processor 620, storage device 630, input / output interface 640, and communication interface 650. Computing device 600 may structurally and / or functionally include at least a portion of wearable device control device 100. Computing device 600 may be a fixed computing device, such as a desktop computer or server, and a mobile computing device, such as a laptop, smartphone, or automotive electronics. Computing device 600 may be implemented as any dedicated hardware accelerator capable of efficiently processing operations designed for artificial intelligence models. For example, computing device 600 may include a graphics processing unit (GPU), tensor processing unit (TPU), or neural processing unit (NPU).

[0097] Memory 610 may store programs that enable processor 620 to perform methods or operations according to various embodiments of the present disclosure. For example, memory 610 may store a wearable device attribute database, a vehicle option database, and a wearable device location determination results database. In another example, the program may include a plurality of instructions executable by processor 620, and the methods or operations described above may be performed by processor 620 executing the plurality of instructions. Memory 610 may consist of a single memory or multiple memories. In this case, information required to perform the methods or operations according to various embodiments of the present disclosure may be stored in a single memory or distributed across multiple memories. When memory 610 consists of multiple memories, the multiple memories may be physically separated. Memory 610 may include at least one of volatile memory and non-volatile memory. Volatile memory includes static random access memory (SRAM) or dynamic random access memory (DRAM), and non-volatile memory includes flash memory.

[0098] Processor 620 may include at least one core capable of executing at least one instruction. Processor 620 may execute instructions stored in memory 610. Processor 620 may consist of a single processor or multiple processors.

[0099] Even if the power supply to the computing device 600 is cut off, the storage device 630 retains the stored data. For example, the storage device 630 may include non-volatile memory, or it may include storage media such as magnetic tape, optical disc, or magnetic disk. Programs stored in the storage device 630 may be loaded into the memory 610 before being executed by the processor 620. The storage device 630 may store files written in a programming language, and programs created from these files by a compiler may be loaded into the memory 610. The storage device 630 may store data to be processed by the processor 620 and / or data that has already been processed by the processor 620.

[0100] Input / output interface 640 can provide an interface with input devices such as a keyboard or mouse and / or output devices such as a display device or printer. Users can trigger processor 620 to execute programs via input devices and / or check the processing results of processor 620 via output devices.

[0101] The communication interface 650 can provide access to external networks. The computing device 600 can communicate with other devices through the communication interface 650.

[0102] Each element of the apparatus or method according to this disclosure can be implemented in hardware or software or a combination of hardware and software. The function of each element can be implemented in software, and a microprocessor can be implemented to execute the software function corresponding to each element.

[0103] Various embodiments of the systems and techniques described herein can be implemented using digital electronic circuits, integrated circuits, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), computer hardware, firmware, software, and / or combinations thereof. Various embodiments may include implementations having one or more computer programs executable on a programmable system. The programmable system includes at least one programmable processor, at least one input device, and at least one output device. The programmable processor may be a dedicated processor or a general-purpose processor, coupled to receive data and instructions from and send data and instructions to a storage system. The computer program (also referred to as a program, software, software application, or code) includes instructions for the programmable processor and is stored in a computer-readable recording medium.

[0104] Computer-readable recording media can include all types of storage devices on which computer-readable data can be stored. Computer-readable recording media can be non-volatile or non-transitory media, such as read-only memory (ROM), random access memory (RAM), optical disc ROM (CD-ROM), magnetic tape, floppy disk, or optical data storage devices. Furthermore, computer-readable recording media can also include transient media such as data transmission media. Moreover, computer-readable recording media can be distributed across computer systems connected via a network, and computer-readable program code can be stored and executed in a distributed manner.

[0105] Although the operations are described as being executed sequentially in the flowcharts / timing diagrams of this specification, this is merely an illustrative description of the technical concept of one embodiment of this disclosure. In other words, those skilled in the art to which this disclosure pertains will understand that various modifications and changes can be made without departing from the basic characteristics of the embodiments of this disclosure; that is, the order shown in the flowcharts / timing diagrams can be changed, and one or more operations can be executed in parallel. Therefore, the flowcharts / timing diagrams are not limited to a temporal order.

[0106] Although embodiments of this disclosure have been described for illustrative purposes, those skilled in the art will understand that various modifications, additions, and substitutions are possible without departing from the concept and scope of the claimed disclosure. Therefore, embodiments of this disclosure have been described for the sake of brevity and clarity. The scope of the technical concept of these embodiments is not limited by the illustrations. Therefore, those skilled in the art should understand that the scope of the claimed disclosure is not limited to the embodiments explicitly described above, but rather to the claims and their equivalents.

Claims

1. A method for controlling the linkage between a wearable device and a vehicle, the method comprising the following steps: The wearable device and the vehicle are connected using wireless communication. Based on the attribute information of the wearable device and the option information of the vehicle, a software program or application (app) optimized for the wearable device is constructed. Obtain the location information of the wearable device; as well as Based on the location information of the wearable device, an application deactivation command or an application deletion command is sent to the wearable device.

2. The method according to claim 1, wherein, The steps for connecting the wearable device include: Request user approval for the vehicle to control the wearable device; Store the attribute information of the wearable devices supported by the wearable device; and Register the wearable device.

3. The method according to claim 1, wherein, The steps for building an application optimized for the wearable device include: By examining the attribute information of the wearable device, an application optimized for the wearable device can be selected.

4. The method according to claim 1, wherein, The steps for building an application optimized for the wearable device include: Send data for applications optimized for the wearable device; and Instruct the wearable device to install the sent application.

5. The method according to claim 1, wherein, The steps for obtaining the location information of the wearable device include: Based on monitoring the location of the wearable device, check whether the wearable device is located inside the vehicle.

6. The method according to claim 1, wherein, The steps of sending the application deactivation command or the application deletion command to the wearable device include: The application deactivation command is sent to the wearable device by considering at least one of wireless signal strength, wireless positioning, and whether the car door is closed.

7. The method according to claim 1, wherein, The steps of sending the application deactivation command or the application deletion command to the wearable device include: Based on the application's activation time, send an application deletion command.

8. The method according to claim 1, wherein, The steps of sending the application deactivation command or the application deletion command to the wearable device include: Based on the vehicle's speed information, a command to disable the application is sent.

9. An apparatus for controlling the linkage between a wearable device and a vehicle, the apparatus comprising: At least one memory is used to store commands; and At least one processor, The at least one processor is configured to execute: The wearable device and the vehicle are connected using wireless communication. Based on the attribute information of the wearable device and the option information of the vehicle, a software program or application (app) optimized for the wearable device is constructed. Obtain the location information of the wearable device; and Based on the location information of the wearable device, an application deactivation command or an application deletion command is sent to the wearable device.

10. The apparatus according to claim 9, wherein, The steps for connecting the wearable device include: Request user approval for the vehicle to control the wearable device; Stores attribute information of wearable devices supported by the wearable device; and Register the wearable device.

11. The apparatus according to claim 9, wherein, The steps for building an application optimized for the wearable device include: By examining the attribute information of the wearable device, an application optimized for the wearable device can be selected.

12. The apparatus according to claim 9, wherein, The steps for building an application optimized for the wearable device include: Send data for applications optimized for the wearable device; and Instruct the wearable device to install the sent application.

13. The apparatus according to claim 9, wherein, The steps for obtaining the location information of the wearable device include: Based on monitoring the location of the wearable device, check whether the wearable device is located inside the vehicle.

14. The apparatus according to claim 9, wherein, The steps of sending the application deactivation command or the application deletion command to the wearable device include: The application deactivation command is sent to the wearable device by considering at least one of wireless signal strength, wireless positioning, and whether the car door is closed.

15. The apparatus according to claim 9, wherein, The steps of sending the application deactivation command or the application deletion command to the wearable device include: Based on the application's activation time, send an application deletion command.

16. The apparatus according to claim 9, wherein, The steps of sending the application deactivation command or the application deletion command to the wearable device include: Using the vehicle's speed information, a command to disable the application is sent.

Images