A two-wheeled vehicle multi-device collaboration method and apparatus

Abstract

The specification provides a two-wheeled vehicle multi-device cooperation method and device. Scene information of a target two-wheeled vehicle, service requirement information of a target service, and device capability information and device state information of multiple target devices are acquired; according to the service requirement information, multiple target tasks corresponding to the target service are determined, and according to the scene information, the device capability information, and the device state information, a task allocation result corresponding to the multiple target tasks is determined; according to the task allocation result, the multiple target devices are controlled to execute corresponding target tasks, and the service state of the target service is synchronized among the multiple target devices; in response to a change in the device state of any target device, the task allocation result is updated according to the changed device state information and the service state, and the multiple target devices are controlled to execute corresponding target tasks according to the updated task allocation result. Thus, the situation of manually switching between different devices to execute tasks by the user is reduced, and the continuity of the target service is improved.

Description

Technical Field

[0001] This specification relates to the fields of intelligent mobility, Internet of Things and distributed operating system collaboration technology, and in particular to a method and device for multi-device collaboration in two-wheeled vehicles. Background Technology

[0002] As two-wheeled vehicles become increasingly intelligent, various devices such as vehicle-mounted systems, mobile phones, and smart helmets are gradually being used together in riding scenarios. Currently, these devices typically operate independently, with a lack of correlation between business status and device status. This results in users needing to manually switch devices to perform business tasks, and it is difficult to adjust and continue related tasks in a timely manner when device status changes.

[0003] There is currently no effective solution to the above problems. Summary of the Invention

[0004] This specification provides a method and apparatus for multi-device collaboration in two-wheeled vehicles, which solves the problem that business tasks need to be manually switched when multiple devices in a two-wheeled vehicle operate independently, and that related tasks are difficult to continue in a timely manner when the device status changes.

[0005] This specification provides a method for multi-device collaboration in a two-wheeled vehicle, including: Acquire scenario information of the target two-wheeled vehicle, business requirement information of the target business, and equipment capability and status information of multiple target devices; wherein, the multiple target devices include vehicle-mounted units and at least one collaborative device; Based on the business requirement information, multiple target tasks corresponding to the target business are determined, and based on the scenario information, the device capability information, and the device status information, the task allocation results corresponding to the multiple target tasks are determined. Based on the task allocation results, control the multiple target devices to execute corresponding target tasks, and synchronize the service status of the target services among the multiple target devices; In response to a change in the device status of any of the target devices, the task allocation result is updated based on the changed device status information and the service status, and the multiple target devices are controlled to execute the corresponding target tasks based on the updated task allocation result.

[0006] In one embodiment, the collaborative device includes at least one of a mobile phone, a smart helmet, a Bluetooth headset, an action camera, and a cycling sensor; The device capability information includes general capability information and cycling scenario capability information; wherein, the general capability information includes at least one of display capability, audio capability, camera capability, network capability and data processing capability, and the cycling scenario capability information includes at least one of cycling safety level, wearing status, vehicle control permissions, power supply method and head-up display capability; The device status information includes at least one of online status, power status, and abnormal status.

[0007] In one embodiment, obtaining the device capability information and device status information of the plurality of target devices includes: The vehicle-mounted system sends a network request to the collaborative device via a distributed soft bus. Receive the device identifier, capability description information, and device status information returned by the collaborative device according to the networking request; Based on the device identifier, the collaborative device is authenticated and bound, and the collaborative device that has passed the authentication and binding verification is connected to the vehicle system to build the target super terminal; Based on the capability description information and device status information of each target device, a unified device capability pool and device status view corresponding to the target super terminal are determined, and the device capability information of each target device is determined based on the unified device capability pool.

[0008] In one embodiment, obtaining the scene information of the target two-wheeled vehicle includes: Obtain the vehicle status information and user behavior information of the target two-wheeled vehicle; The target scenario type of the target two-wheeled vehicle is determined based on the vehicle status information, the device status view, the wearing status, and the user behavior information. The scene information is determined based on the target scene type; The target scenario type includes at least one of the following: cycling scenario, parking scenario, incoming call scenario, navigation scenario, shooting scenario, music playback scenario, and abnormal alarm scenario.

[0009] In one embodiment, determining multiple target tasks corresponding to the target business based on the business requirement information, and determining the task allocation result based on the scenario information, the device capability information, and the device status information, includes: Based on the business requirement information, determine the multiple target capabilities required for the target business; Based on the multiple target capabilities, the target service is divided into multiple target tasks corresponding to each of the target capabilities; Based on the target capabilities corresponding to each target task, the unified device capability pool, and the device status view, candidate devices corresponding to each target task are determined; Based on the scenario information, a target carrier device is determined from the candidate devices corresponding to each target task, and the task allocation result is determined based on the target carrier device corresponding to each target task.

[0010] In one embodiment, determining the target bearer device from the candidate devices corresponding to each target task based on the scenario information includes: For any of the target tasks, the capability matching degree of each candidate device is determined based on the target capability corresponding to the target task and the device capability information of each candidate device. Based on the device capability information and device status information of each candidate device, determine the riding safety level, battery adequacy, power supply stability and online reliability of each candidate device; Based on the scenario information, determine the target weights corresponding to the capability matching degree, the riding safety level, the battery adequacy, the power supply stability, and the online reliability, respectively. Using the target weights, the capability matching degree, riding safety level, battery adequacy, power supply stability and online reliability of each candidate device are weighted and processed to determine the task adaptation score of each candidate device for the target task; Based on the task adaptation score of each candidate device, the target bearer device corresponding to the target task is determined from each candidate device.

[0011] In one embodiment, synchronizing the service status of the target service among the plurality of target devices includes: Based on the task allocation results, the participating devices and the service data to be synchronized are determined to execute the target service. Using a distributed data management mechanism, the business data to be synchronized and the business status are synchronized to each of the participating devices; Acquire user operation events generated by any of the participating devices; The service status is updated based on the user operation event, and the updated service status is sent to each of the participating devices.

[0012] In one embodiment, determining the target weights corresponding to the capability matching degree, the riding safety level, the battery adequacy, the power supply stability, and the online reliability based on the scenario information includes: When the scene information represents a cycling scene, the target weight corresponding to the cycling safety level is determined as the maximum value among the target weights. Based on the task adaptation score of each candidate device, the display task is assigned to the vehicle system or the smart helmet, and the audio task is assigned to the smart helmet. When the scene information represents a parking scene, the target weight corresponding to the capability matching degree is determined as the maximum value among the target weights, and the interaction task is assigned to the mobile phone according to the task adaptation score of each candidate device.

[0013] In one embodiment, updating the task allocation result in response to a change in the device state of any of the target devices includes: If any of the target devices is detected to be offline, the affected target tasks corresponding to the offline target devices are determined according to the task allocation results; Based on the equipment capability information and equipment status information of the remaining target equipment, determine the target replacement equipment corresponding to the affected target task; The affected target tasks are assigned to the target alternative devices, and the current business status is synchronized to the target alternative devices to obtain updated task assignment results; The vehicle-mounted system caches the service status changes of the offline target device during the offline period.

[0014] In one embodiment, the method further includes: In response to the offline target device coming back online, obtain the current device capability information and current device status information corresponding to the re-online target device; Based on the task allocation result, determine the original target task corresponding to the target device that is re-connected, and determine the task recovery result based on the current device capability information, the current device status information, and the original target task; If the task recovery result indicates that the re-connected target device can execute the original target task, the recovery service status is determined based on the service status change and the current service status. The restored service status is synchronized to the target device that has been brought back online, the original target task is reassigned to the target device that has been brought back online, and the original target task continues to be executed according to the restored service status.

[0015] In one embodiment, the method further includes: The vehicle-mounted system periodically sends heartbeat detection information to each of the target devices. Based on the heartbeat response information returned by each of the target devices, determine the current online status and capability changes of each of the target devices; Update the unified device capability pool and the device status view based on the current online status and the capability change information; Based on the updated unified device capability pool and device status view, the task allocation results are updated, and the multiple target devices are controlled to execute corresponding target tasks according to the updated task allocation results.

[0016] This specification provides a multi-device coordination device for a two-wheeled vehicle, including: The information acquisition module is used to acquire scene information of the target two-wheeled vehicle, business requirement information of the target business, and equipment capability information and equipment status information of multiple target devices; wherein, the multiple target devices include a vehicle-mounted unit and at least one collaborative device; The task allocation module is used to determine multiple target tasks corresponding to the target business based on the business requirement information, and to determine the task allocation results corresponding to the multiple target tasks based on the scenario information, the device capability information and the device status information. The status synchronization module is used to control the multiple target devices to execute corresponding target tasks according to the task allocation results, and to synchronize the service status of the target service among the multiple target devices; The task execution module is used to respond to a change in the device status of any of the target devices, update the task allocation result according to the changed device status information and the service status, and control the multiple target devices to execute the corresponding target tasks according to the updated task allocation result.

[0017] This specification also provides an electronic device including a processor and a memory for storing processor-executable instructions, wherein the processor, when executing the instructions, implements a two-wheeled vehicle multi-device collaborative method.

[0018] This specification also provides a computer-readable storage medium having computer instructions stored thereon, which, when executed, implement a method for multi-device collaboration in a two-wheeled vehicle.

[0019] This specification also provides a computer program product comprising a computer program that, when executed by a processor, implements a method for multi-device collaboration in a two-wheeled vehicle.

[0020] Based on the multi-device collaboration method for two-wheeled vehicles provided in this specification, the method acquires scene information of the target two-wheeled vehicle, business requirement information of the target service, and device capability and status information of multiple target devices. The multiple target devices include a vehicle-mounted system and at least one collaborative device. Based on the business requirement information, multiple target tasks corresponding to the target service are determined, and based on the scene information, device capability information, and device status information, task allocation results corresponding to the multiple target tasks are determined. Based on the task allocation results, the multiple target devices are controlled to execute the corresponding target tasks, and the business status of the target service is synchronized among the multiple target devices. In response to a change in the device status of any target device, the task allocation results are updated based on the changed device status information and the business status, and the multiple target devices are controlled to execute the corresponding target tasks based on the updated task allocation results. Thus, compared to existing methods where each device operates independently and the user needs to manually switch devices to execute business tasks, this application can control multiple target devices to execute corresponding target tasks according to the task allocation results, reducing the need for manual switching between different devices. On the one hand, the task allocation results are determined based on scenario information, business requirement information, equipment capability information, and equipment status information, and the business status is synchronized among multiple target devices. On the other hand, when the equipment status of any target device changes, the task allocation results are updated based on the changed equipment status information and business status, so that the relevant target tasks can be adjusted and continued in a timely manner, thereby improving the continuity of target services. Attached Figure Description

[0021] To more clearly illustrate the embodiments of this specification, the accompanying drawings used in the embodiments will be briefly introduced below. The drawings described below are only some embodiments recorded in this specification. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0022] Figure 1 This is a flowchart illustrating a multi-device collaboration method for two-wheeled vehicles, provided in one embodiment of this specification. Figure 2 This is a schematic diagram of the electronic device structure provided in one embodiment of this specification; Figure 3 This is a schematic diagram of the structural composition of a multi-device collaborative device for a two-wheeled vehicle, provided in one embodiment of this specification. Figure 4 This is a schematic diagram of the overall architecture of a two-wheeled vehicle multi-device collaborative system provided in one embodiment of this specification; Figure 5 This is a schematic diagram of a super terminal logic structure provided in one embodiment of this specification; Figure 6 This is a schematic diagram of task scheduling in a cycling scenario provided by one embodiment of this specification; Figure 7 This is a schematic diagram of an offline device downgrade process provided in one embodiment of this specification. Detailed Implementation

[0023] To enable those skilled in the art to better understand the technical solutions in this specification, the technical solutions in the embodiments of this specification will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this specification, and not all embodiments. Based on the embodiments in this specification, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of this specification.

[0024] See Figure 1 As shown in the embodiments of this specification, a method for multi-device collaboration in two-wheeled vehicles is provided, wherein the method is specifically applied to the server side. In specific implementation, the method may include the following: S101: Obtain the scene information of the target two-wheeled vehicle, the business requirement information of the target business, and the equipment capability information and equipment status information of multiple target devices; wherein, the multiple target devices include the vehicle-mounted unit and at least one collaborative device; S102: Based on the business requirement information, determine multiple target tasks corresponding to the target business, and based on the scenario information, the device capability information, and the device status information, determine the task allocation results corresponding to the multiple target tasks; S103: Based on the task allocation result, control the multiple target devices to execute the corresponding target tasks, and synchronize the service status of the target service among the multiple target devices; S104: In response to a change in the device status of any of the target devices, update the task allocation result according to the changed device status information and the service status, and control the multiple target devices to execute the corresponding target tasks according to the updated task allocation result.

[0025] The scenario information of the target two-wheeled vehicle is used to characterize the current usage scenario of the target two-wheeled vehicle, and can be determined based on the vehicle status of the target two-wheeled vehicle, the device status of each target device, and user behavior. The scenario information may include at least one of the following: riding scenario, parking scenario, incoming call scenario, navigation scenario, shooting scenario, music playback scenario, and abnormal alarm scenario.

[0026] The aforementioned business requirement information for the target service is used to characterize the equipment capabilities and business functions required to execute the target service. The target service may include any one of the following: navigation service, call service, music playback service, photography service, and anomaly alarm service. Different target services correspond to different business requirement information.

[0027] The aforementioned device capability information is used to characterize the functions that each target device can provide. This device capability information may include at least one of the following: display capability, audio output capability, audio acquisition capability, camera capability, input capability, voice interaction capability, network communication capability, data processing capability, storage capability, riding safety level, wearing status perception capability, vehicle control permissions, and head-up display capability.

[0028] The aforementioned device status information is used to characterize the current operating status of each target device. This device status information may include at least one of the following: online status, battery status, power supply status, operating status, and abnormal status, to determine whether the corresponding target device is currently capable of performing the target task.

[0029] The aforementioned collaborative device can refer to any device other than the vehicle-mounted system that can connect to the vehicle-mounted system and participate in the execution of the target service. The collaborative device may include at least one of a mobile phone, smart helmet, Bluetooth headset, action camera, navigation device, and cycling sensor.

[0030] The aforementioned target task can refer to a business execution task obtained by dividing the target service based on the business requirement information of the target service. The target task may include at least one of the following: computing task, display task, audio output task, audio acquisition task, camera task, data transmission task, and control task. Different target tasks can be executed by different target devices.

[0031] The task allocation results described above are used to characterize the correspondence between each target task and the target device executing that task. These task allocation results are determined based on the scenario information, the device capability information, and the device status information of each target device, and can be updated when the device status of a target device changes.

[0032] The service status of the aforementioned target service is used to characterize the current execution status of the target service. The service status may include at least one of the following: navigation route and real-time location, music playback track and playback progress, call status and call duration, video capture status, and user operation status, and is synchronized among multiple target devices participating in the execution of the target service.

[0033] In some embodiments, the step of determining multiple target tasks corresponding to the target business based on the business requirement information, and determining the task allocation result corresponding to the multiple target tasks based on the scenario information, the device capability information, and the device status information, may further include: Based on the business requirement information, multiple target capabilities required for the target business are determined, and the target business is divided into multiple target tasks based on the multiple target capabilities; wherein each target task corresponds to at least one of the target capabilities. For any of the target tasks, based on the target capabilities corresponding to the target task and the device capability information, a capability matching device corresponding to the target task is determined, and an available device is determined from the capability matching devices based on the device status information; Based on the available devices corresponding to each of the target tasks, multiple candidate device combinations are determined; wherein the available devices in each of the candidate device combinations are capable of jointly executing the multiple target tasks; Based on the scenario information, the device capability information and device status information corresponding to each candidate device combination, the scenario adaptation result of each candidate device combination is determined, and based on the scenario adaptation result, the target device combination is determined from the multiple candidate device combinations. The task allocation result is determined based on the correspondence between each available device in the target device combination and each target task.

[0034] By dividing multiple target tasks according to the multiple target capabilities required by the target business, and combining equipment capability information and equipment status information to determine available devices and candidate device combinations, multiple available devices can jointly execute the target business when a single target device cannot meet all target capabilities. At the same time, the scenario adaptation results of each candidate device combination are determined according to scenario information, and the task allocation results are determined accordingly, which helps to improve the matching degree between target tasks and target devices and the synergy of multiple target devices in executing target businesses.

[0035] In some embodiments, the collaborative device includes a smart helmet, and the device status information includes the wearing status of the smart helmet; in response to a change in the device status of any of the target devices, the task allocation result is updated according to the changed device status information and the business status, and the multiple target devices are controlled to execute corresponding target tasks according to the updated task allocation result. In specific implementations, this may further include: In response to the smart helmet changing from a worn state to an unworn state, the next target task to be executed by the smart helmet is determined based on the task allocation result. Based on the device capability information and device status information of the vehicle-mounted system, the target succession task that the vehicle-mounted system can execute is determined from the target succession task to be continued. Based on the business status, determine the current execution status corresponding to the target follow-up task; The task allocation result is updated according to the target succession task, and the vehicle system is controlled to continue executing the target succession task according to the updated task allocation result and the current execution status. In response to the smart helmet changing from an unworn state to a worn state, the target task to be restored and the corresponding restoration execution state are determined based on the smart helmet's device capability information, device status information, and the business status. The task allocation result is updated according to the target task to be restored, and the smart helmet is controlled to execute the target task to be restored according to the updated task allocation result and the recovery execution status; The target task to be continued and the target task to be restored include at least one of audio output task and display task.

[0036] When the wearing status of the smart helmet changes, the target task to be continued is determined based on the task allocation result. The corresponding task is then continued to be executed by the vehicle-mounted system by combining the device capability information, device status information and current business status. This reduces the need for users to manually switch devices or restart services. After the smart helmet returns to the wearing status, the corresponding target task is restored according to the current business status, so that the target business can continue to run according to the current execution status, improving the continuity of target tasks during device status changes.

[0037] In some embodiments, the collaborative device includes a smart helmet; the acquisition of scene information of the target two-wheeled vehicle, business requirement information of the target service, and device capability information and device status information of multiple target devices may, in specific implementations, further include: The vehicle driving status, vehicle locking status, and smart helmet wearing status of the target two-wheeled vehicle are obtained. If the vehicle's driving state indicates that the vehicle speed is greater than zero, or the vehicle's locked state indicates that the target two-wheeled vehicle has been unlocked and the wearing state indicates that the smart helmet has been worn, then the scene information is determined to be riding scene information. When the vehicle driving state indicates that the vehicle speed is zero and the vehicle locking state indicates that the target two-wheeled vehicle is locked, the scene information is determined to be parking scene information; Obtain the service startup information of the target service, determine the service type of the target service based on the service startup information, and determine the target capability set required by the target service based on the service type; Based on the target capability set, the business requirement information is determined; Obtain the capability description information and current operating status of each target device; determine the device capability information from the capability description information of each target device according to the target capability set; and determine the device status information according to the current operating status of the target device corresponding to the device capability information. The service types include at least one of navigation service, call service, music playback service, shooting service, and abnormal alarm service.

[0038] By combining the vehicle's driving status, vehicle locking status, and smart helmet wearing status to determine the scene information, the scene information can be made to correspond with the actual usage status of the target two-wheeled vehicle. At the same time, the target capability set is determined according to the business type of the target business, and relevant equipment capability information and equipment status information are obtained based on the target capability set, so that the business requirement information and equipment information correspond to each other, providing a clear data basis for subsequently determining multiple target tasks and their task allocation results.

[0039] In some embodiments, the collaborative device includes at least one of a mobile phone, a smart helmet, a Bluetooth headset, an action camera, and a cycling sensor; The device capability information includes general capability information and cycling scenario capability information; wherein, the general capability information includes at least one of display capability, audio capability, camera capability, network capability and data processing capability, and the cycling scenario capability information includes at least one of cycling safety level, wearing status, vehicle control permissions, power supply method and head-up display capability; The device status information includes at least one of online status, power status, and abnormal status.

[0040] In practice, the vehicle-mounted system sends a device discovery request via a distributed soft bus. Upon receiving the request, the mobile phone, smart helmet, Bluetooth headset, action camera, and cycling sensor send their device identifier, capability description information, and current operating status to the vehicle-mounted system, respectively. The vehicle-mounted system performs identity authentication and binding verification based on each device identifier and establishes a communication connection with devices that pass the authentication and binding verification. Based on the capability description information and current operating status returned by each device, the vehicle-mounted system creates device capability entries and device status entries corresponding to each device identifier.

[0041] The device capability entries include general capability information and cycling scenario capability information. For in-vehicle systems, general capability information includes display capabilities, audio capabilities, and data processing capabilities; cycling scenario capability information includes vehicle control permissions, vehicle power supply methods, and a high level of cycling safety. For mobile phones, general capability information includes display capabilities, network capabilities, and data processing capabilities; cycling scenario capability information includes independent battery power supply methods and a lower level of cycling safety. For smart helmets, general capability information includes audio capabilities and camera capabilities; cycling scenario capability information includes wearing status and head-up display capabilities. For Bluetooth headsets, general capability information includes audio capabilities. For action cameras, general capability information includes camera capabilities. For cycling sensors, general capability information includes cycling status perception capabilities.

[0042] The vehicle-mounted system updates the corresponding device status entries based on the periodic operational status reports sent by each target device. These device status entries record the online status, battery status, and abnormal status of the target device. When a target device can maintain communication with the vehicle-mounted system, its corresponding online status is determined as online; when the target device does not return to operational status or the communication connection is lost, its corresponding online status is determined as offline. The vehicle-mounted system also determines the battery status based on the remaining battery power reported by the target device and determines the abnormal status based on the operational anomaly information reported by the target device.

[0043] When a target service is initiated, the vehicle's infotainment system determines the required display, audio, camera, network, or data processing capabilities based on the service's requirements. It then identifies candidate devices that meet these requirements. The system further removes offline, low-battery, or abnormal devices based on their online, battery, and faulty states. For display or interactive tasks requiring user attention, the system determines the target device based on the riding safety level of the remaining candidate devices. For candidate devices with similar capability matching, the system determines the target device based on the power supply method and battery status.

[0044] In the cycling navigation service, the vehicle-mounted system determines its route calculation and display capabilities based on the device's capabilities, assigning route calculation and full map display tasks to the system. When the smart helmet is worn, online, and not in an abnormal state, the system assigns voice broadcasting and simplified navigation prompts to the helmet based on its audio and head-up display capabilities. When the mobile phone is online and not in an abnormal state, the system assigns real-time traffic information retrieval tasks to the phone based on its network capabilities. When the smart helmet becomes unworn, offline, or in an abnormal state, the vehicle-mounted system resumes the voice broadcasting and simplified navigation prompt tasks based on its own audio and display capabilities.

[0045] By recording the general capability information, cycling scenario capability information, and device status information of each collaborative device in relation to device identifiers, candidate devices can be determined based on the capability requirements of the target business. Furthermore, the target device for executing the target task can be determined by combining online status, battery status, abnormal status, and cycling safety level, thus avoiding assigning the target task to a device that is currently not functioning properly. At the same time, when the wearing status, online status, or abnormal status of the target device changes, other target devices with corresponding capabilities can take over the relevant target task, improving the matching degree and continuity of multiple target devices in executing the target business.

[0046] In some embodiments, the method for obtaining the device capability information and device status information of the plurality of target devices may further include the following: S1: The vehicle's infotainment system sends a network request to the collaborative device via a distributed soft bus. S2: Receive the device identifier, capability description information, and device status information returned by the cooperating device according to the networking request; S3: Based on the device identifier, perform identity authentication and binding verification on the collaborative device, and connect the collaborative device that has passed the identity authentication and binding verification to the vehicle system to build the target super terminal; S4: Based on the capability description information and device status information of each target device, determine the unified device capability pool and device status view corresponding to the target super terminal, and determine the device capability information of each target device based on the unified device capability pool.

[0047] In practice, the vehicle's infotainment system broadcasts a network request via a distributed soft bus carried by StarMesh, Bluetooth, or Wi-Fi. This network request instructs discoverable collaborative devices to apply to join the target superterminal. Upon receiving the network request, the collaborative device returns its device identifier, capability description information, and device status information to the vehicle's infotainment system. The capability description information indicates the functional capabilities of the collaborative device, and the device status information indicates whether the collaborative device is currently able to provide the corresponding functional capabilities.

[0048] The vehicle-mounted system (V2X) queries the device binding relationship corresponding to the target two-wheeled vehicle based on the received device identifier, and performs identity authentication and binding verification on the collaborative device based on the query results. When the device identifier passes authentication and matches the device binding relationship, the V2X establishes a communication connection with the corresponding collaborative device and adds the collaborative device to the target device list; when the device identifier fails authentication or does not match the device binding relationship, the V2X refuses to add the corresponding collaborative device. The V2X constructs a target super terminal based on itself and the collaborative devices in the target device list, such that the target super terminal includes the V2X and at least one collaborative device that has passed identity authentication and binding verification.

[0049] The vehicle-mounted system determines the capability type and parameters of each target device based on its capability description information, and establishes a correspondence between device identifiers, capability types, and capability parameters. The capability types include at least one of display capabilities, audio capabilities, camera capabilities, network capabilities, and data processing capabilities, and may also include at least one of riding safety levels, wearer status awareness capabilities, vehicle control permissions, power supply methods, and head-up display capabilities. The capability parameters represent the available scope or execution conditions of the corresponding capability.

[0050] The vehicle-mounted system (V2X) groups target devices with the same capability type into the same candidate device set based on their capability types, and constructs a unified device capability pool based on each candidate device set and its corresponding capability parameters. Each device capability entry in the unified device capability pool includes at least a device identifier, capability type, and capability parameters, enabling the V2X to determine the target device with the corresponding capability from the unified device capability pool based on the capability type required for the target task. The V2X then determines the device capability information of the corresponding target device based on each device capability entry.

[0051] The vehicle-mounted system establishes a correspondence between device identifiers and online status, battery status, and abnormal status based on the device status information returned by each target device, and constructs a device status view based on this correspondence. The system receives device status information periodically sent by each cooperating device and updates the status record of the corresponding device identifier in the device status view using newly received device status information. When the vehicle-mounted system does not receive device status information from any cooperating device or the communication connection with that cooperating device is lost, the system updates the online status of that cooperating device to offline status.

[0052] The device capability entries in the unified device capability pool are associated with the status records in the device status view through device identifiers. When any target device is offline or in an abnormal state, the vehicle-mounted system determines the device capability corresponding to that device identifier in the unified device capability pool as unavailable based on the device identifier of the target device; when the target device returns to online and the abnormal state is eliminated, the vehicle-mounted system restores the corresponding device capability to available status based on the newly received device status information.

[0053] Taking cycling navigation as an example, the vehicle-mounted system queries a unified device capability pool based on the route calculation, display, network, audio, and head-up display capabilities required for navigation. This determines that the vehicle-mounted system possesses route calculation and display capabilities, the mobile phone has network capabilities, and the smart helmet has audio and head-up display capabilities. The vehicle-mounted system then uses the device status view to determine the online status, battery status, and abnormal status of the mobile phone and smart helmet. Target devices in an available state are identified as candidate devices for the corresponding navigation tasks, thus providing device capability and status information for task allocation and task reallocation after changes in device status.

[0054] By authenticating and binding collaborative devices through the vehicle-mounted system, and connecting verified collaborative devices to the target super terminal, the target devices participating in business collaboration can be limited. By establishing the correspondence between device identifiers, device capability information, and device status information, a unified device capability pool and device status view are formed. The system can determine the target devices that have the corresponding capabilities and are in an available state according to the capabilities required by the target task, and synchronously update the availability status of the corresponding device capabilities when the device status changes. This provides an accurate basis for the allocation and reallocation of target tasks and improves the continuity of business collaboration among multiple target devices.

[0055] In some embodiments, the method for obtaining scene information of the target two-wheeled vehicle may further include the following: S1: Obtain the vehicle status information and user behavior information of the target two-wheeled vehicle; S2: Determine the target scenario type of the target two-wheeled vehicle based on the vehicle status information, the device status view, the wearing status, and the user behavior information; S3: Determine the scene information based on the target scene type; The target scenario type includes at least one of the following: cycling scenario, parking scenario, incoming call scenario, navigation scenario, shooting scenario, music playback scenario, and abnormal alarm scenario.

[0056] In practice, the vehicle-mounted system acquires the vehicle status information of the target two-wheeled vehicle, including at least one of the following: vehicle driving status, vehicle speed, power-on status, and locked status. The system also acquires user behavior information triggered by the user through the vehicle-mounted system, mobile phone, smart helmet, or other collaborative devices, including at least one of the following: navigation initiation, call answering, camera initiation, music playback, and service closure.

[0057] The vehicle-mounted system determines the online and abnormal states of each target device based on the device status view, and obtains the wearing status of the smart helmet from the capability description information or current operating status reported by the smart helmet. The wearing status includes both worn and unworn states. The vehicle-mounted system associates vehicle status information, device status view, wearing status, and user behavior information according to the corresponding collection time to determine the vehicle status, device status, and user operation at the same time.

[0058] When the vehicle speed is greater than zero, the vehicle system determines that the target two-wheeled vehicle is in a riding scenario based on the vehicle's driving status; when the target two-wheeled vehicle is unlocked, the smart helmet is worn, and the vehicle speed is zero, the vehicle system determines that the target two-wheeled vehicle is in a riding preparation state based on the power-on status and user behavior information, and classifies the riding preparation state into a riding scenario; when the vehicle speed is zero and the target two-wheeled vehicle is locked, the vehicle system determines that the target two-wheeled vehicle is in a parking scenario.

[0059] When a mobile phone is online in the device status view and sends an incoming call event to the vehicle's infotainment system, the system determines the incoming call scenario based on the event. When a user triggers a navigation start operation through any target device, the system determines the navigation scenario based on the navigation start operation; when a user triggers a shooting start operation through the infotainment system, mobile phone, or smart helmet, the system determines the shooting scenario based on the shooting start operation; when a user triggers a music playback operation, the system determines the music playback scenario based on the music playback operation.

[0060] When an abnormal status of any target device in the device status view indicates that the corresponding target device has malfunctioned, or when the vehicle-mounted system obtains an abnormal alarm message from the target two-wheeled vehicle, the vehicle-mounted system determines the abnormal alarm scenario based on the abnormal target device, the abnormal type, and the abnormal alarm message. The abnormal type may include at least one of the following: device offline, insufficient power, communication abnormality, and function execution abnormality.

[0061] When multiple scenario conditions are met simultaneously, the vehicle's infotainment system will collectively identify these scenario types as the target scenario type. For example, if the target two-wheeled vehicle is in motion and the user has activated the navigation service, the target scenario type includes both riding and navigation scenarios; if the target two-wheeled vehicle is in motion and the phone receives an incoming call event, the target scenario type includes both riding and incoming call scenarios. When an abnormal alarm occurs, the vehicle's infotainment system will prioritize the abnormal alarm scenario as the target scenario type for processing.

[0062] The vehicle's infotainment system determines the corresponding scene constraint information based on the target scene type, and then determines the scene information based on the target scene type and the scene constraint information. Scene constraint information for cycling scenarios restricts target tasks requiring continuous user operation; scene constraint information for parking scenarios allows the phone to perform interactive operations; scene constraint information for incoming call scenarios indicates audio tasks and call control tasks; scene constraint information for navigation scenarios indicates route calculation tasks, navigation display tasks, and voice broadcast tasks; scene constraint information for shooting scenarios indicates image acquisition tasks, preview tasks, and data transmission tasks; scene constraint information for music playback scenarios indicates audio playback tasks and playback control tasks; and scene constraint information for abnormal alarm scenarios increases the execution priority of abnormal alarm tasks.

[0063] By combining vehicle status information, device status view, smart helmet wearing status, and user behavior information to determine the target scenario type, it is possible to distinguish between cycling, parking, and different business scenarios. When multiple scenarios coexist, corresponding scenario information is generated, providing a clear basis for allocating target tasks based on scenario information. At the same time, abnormal alarm scenarios can be identified based on abnormal device status and abnormal alarm information, enabling abnormal alarm tasks to be prioritized, reducing the need for users to manually switch business scenarios, and improving the matching degree between multi-device collaborative tasks and the current cycling scenario.

[0064] In some embodiments, the method involves determining multiple target tasks corresponding to the target business based on the business requirement information, and determining the task allocation result based on the scenario information, the device capability information, and the device status information. In specific implementations, the method may further include the following: S1: Based on the business requirement information, determine the multiple target capabilities required by the target business; S2: Based on the multiple target capabilities, the target service is divided into multiple target tasks corresponding to each of the target capabilities; S3: Determine the candidate devices corresponding to each target task based on the target capabilities corresponding to each target task, the unified device capability pool, and the device status view; S4: Based on the scenario information, determine the target carrier device from the candidate devices corresponding to each target task, and determine the task allocation result based on the target carrier device corresponding to each target task.

[0065] In practice, the vehicle's infotainment system acquires the service requirement information of the target service and parses the functions that the target service needs to invoke from the service requirement information. Based on the capability types corresponding to each function, the infotainment system determines multiple target capabilities required by the target service. Taking navigation as an example, the multiple target capabilities may include data processing capabilities, display capabilities, audio capabilities, and network capabilities; taking incoming call services as an example, the multiple target capabilities may include network capabilities, display capabilities, and audio capabilities.

[0066] The vehicle-mounted infotainment system breaks down target services into multiple target tasks that can be executed by different target devices based on multiple target capabilities, and establishes a correspondence between target tasks and target capabilities. For example, the system breaks down navigation services into route calculation tasks, map display tasks, voice broadcast tasks, and real-time traffic information acquisition tasks, and maps route calculation tasks to data processing capabilities, map display tasks to display capabilities, voice broadcast tasks to audio capabilities, and real-time traffic information acquisition tasks to network capabilities.

[0067] For any given target task, the vehicle's infotainment system queries the unified device capability pool based on the target capability corresponding to that task, obtains device capability entries with the corresponding capability type, and determines initial candidate devices based on the device identifiers in the device capability entries. The vehicle's infotainment system uses the device identifiers to query the device status view, determines the online status, battery status, and abnormal status of each initial candidate device, and removes target devices that are offline, have insufficient battery, or are in an abnormal state from the initial candidate devices, thus obtaining the candidate devices corresponding to that target task.

[0068] The vehicle's infotainment system determines the scene weights for each evaluation factor based on scene information, and calculates the task adaptation score for each candidate device for the corresponding target task based on the candidate device's capability matching degree, riding safety level, battery status, power supply stability, and online reliability. The task adaptation score can be expressed as: Task compatibility score = capability matching degree × first weight + riding safety level × second weight + battery status × third weight + power supply stability × fourth weight + online reliability × fifth weight.

[0069] Among them, the capability matching degree is determined based on the target capability corresponding to the target task and the capability parameters of the candidate devices; the riding safety level and power supply stability are determined based on the riding scenario capability information of the candidate devices; and the battery status and online reliability are determined based on the device status view. The first to fifth weights are adjusted according to the scenario information.

[0070] In cycling scenarios, the vehicle's infotainment system assigns a higher weight to the second weight corresponding to cycling safety level to prioritize candidate devices that do not require handheld operation or continuous head-down operation. In parking scenarios, the system assigns a higher weight to the first weight corresponding to capability matching to prioritize candidate devices with more complete interactive capabilities. In incoming call scenarios, the system increases the impact of audio capability matching and cycling safety level on task adaptation scores. In abnormal alarm scenarios, the system sets the execution priority of abnormal alarm tasks higher than the execution priority of other target tasks.

[0071] For each target task, the vehicle's infotainment system (VIS) identifies the candidate device with the highest task adaptation score as the target device. When multiple candidate devices have the same task adaptation score, the VIS determines the candidate device with higher vehicle power supply or higher battery status as the target device based on the candidate devices' power supply method and battery status. The VIS establishes a mapping relationship between target tasks and target devices based on the task identifier, the target capability corresponding to each target task, and the device identifier of each target device, and determines the task allocation result based on the mapping relationship.

[0072] Taking a two-wheeled vehicle in a riding scenario and performing navigation services as an example, the vehicle's infotainment system determines, based on a unified device capability pool, that both the vehicle's infotainment system and the mobile phone have data processing capabilities, both have display capabilities, the vehicle's infotainment system, smart helmet, and Bluetooth headset all have audio capabilities, and the mobile phone has network capabilities. The vehicle's infotainment system deletes devices in offline or abnormal states based on the device status view, and based on the task adaptation score, assigns route calculation and map display tasks to the vehicle's infotainment system with stable power supply, assigns voice broadcasting tasks to the smart helmet that is being worn and online, and assigns real-time traffic information acquisition tasks to the mobile phone that is online. This forms the task allocation result corresponding to the navigation service.

[0073] By converting multiple target capabilities required for a target business into multiple corresponding target tasks, different target devices can undertake target tasks that match their own capabilities. By filtering out target devices that do not have the corresponding capabilities or are currently unavailable through a unified device capability pool and device status view, and by evaluating candidate devices in conjunction with scenario information, it is possible to determine the target carrying device that is suitable for the target task and the current scenario. This reduces the user's manual selection and switching of devices, improves the utilization of multiple device capabilities, and enhances the matching degree between task allocation results and cycling scenarios.

[0074] In some embodiments, the method for determining the target bearer device from the candidate devices corresponding to each target task based on the scenario information may further include the following: S1: For any of the target tasks, determine the capability matching degree of each candidate device based on the target capability corresponding to the target task and the device capability information of each candidate device; S2: Based on the device capability information and device status information of each candidate device, determine the riding safety level, battery adequacy, power supply stability and online reliability of each candidate device; S3: Based on the scenario information, determine the target weights corresponding to the capability matching degree, the riding safety level, the battery adequacy, the power supply stability, and the online reliability, respectively; S4: Using the target weights, the capability matching degree, riding safety level, battery adequacy, power supply stability and online reliability of each candidate device are weighted and processed to determine the task adaptation score of each candidate device for the target task; S5: Based on the task adaptation score of each candidate device, determine the target bearer device corresponding to the target task from among the candidate devices.

[0075] In practice, for any given target task, the vehicle-mounted system reads the device capability information from each candidate device, comparing the target capability with the device capability information of each candidate device. Based on the capability type and requirements corresponding to the target capability, the system determines whether the capability types provided by the candidate devices are consistent and whether the capability parameters meet the requirements, and determines the capability matching degree of each candidate device based on the comparison results. A higher capability matching degree is determined when the candidate devices provide consistent capability types and meet all capability requirements; a lower capability matching degree is determined when the candidate devices provide consistent capability types but only meet some capability requirements.

[0076] The vehicle's infotainment system determines the riding safety level of each candidate device based on its riding scenario capabilities. For infotainment systems, smart helmets, or Bluetooth headsets that can perform the target task without requiring additional handheld operation from the user, a higher riding safety level is assigned; for mobile phones that require continuous touch or handheld operation, a lower riding safety level is assigned. When a smart helmet is not worn, the system lowers the riding safety level of the smart helmet or removes it from the candidate devices based on the wearing status.

[0077] The vehicle's infotainment system determines the battery status of each candidate device based on the remaining battery level recorded in the device status view, and determines the corresponding battery adequacy based on the battery range in which the remaining battery level falls. The higher the remaining battery level, the higher the determined battery adequacy; if the remaining battery level is lower than the minimum execution battery level corresponding to the target task, the corresponding candidate device will be removed from the candidate device list.

[0078] The vehicle-mounted infotainment system determines power supply stability based on the power supply method of each candidate device. Specifically, it assigns higher power supply stability to systems powered continuously by the vehicle, while for devices powered by independent batteries, such as mobile phones, smart helmets, Bluetooth headsets, or action cameras, power supply stability is determined based on the respective device's battery status. The system also determines online reliability based on the online status recorded in the device status view and the continuous reception of periodic device status information. Higher online reliability is assigned when a candidate device remains online and periodic device status information arrives continuously; lower online reliability is assigned when a candidate device experiences communication interruptions or missing periodic device status information.

[0079] Based on the target scenario type and scenario constraints in the scenario information, the vehicle's system determines the target weights for capability matching, riding safety level, battery adequacy, power supply stability, and online reliability. In riding scenarios, the target weight corresponding to riding safety level is set as the highest among all target weights; in parking scenarios, the target weight corresponding to capability matching is set as the highest; in incoming call scenarios, the target weights for capability matching and riding safety level corresponding to audio capabilities are increased; in abnormal alarm scenarios, the target weights for capability matching and online reliability are increased, and the execution priority of abnormal alarm tasks is set higher than the execution priority of other target tasks.

[0080] The vehicle-mounted system converts the capability matching degree, riding safety level, battery adequacy, power supply stability, and online reliability of each candidate device into the same scoring range, and then weights the converted evaluation values ​​using the weights of each objective. The task adaptation score of any candidate device for the target task can be determined by the following relationship: Task compatibility score = Competency matching degree × First target weight + Cycling safety level × Second target weight + Battery adequacy × Third target weight + Power supply stability × Fourth target weight + Online reliability × Fifth target weight.

[0081] The weights for the first to fifth objectives correspond to capability matching, riding safety level, battery adequacy, power supply stability, and online reliability, respectively. All objective weights are non-negative, and the sum of all objective weights is one.

[0082] The vehicle's infotainment system compares the task adaptation scores of each candidate device for the same target task and determines the candidate device with the highest task adaptation score as the target device for the target task. When multiple candidate devices have the same task adaptation score, the vehicle's infotainment system prioritizes the candidate device that uses continuous power from the vehicle as the target device; when multiple candidate devices use independent battery power, the vehicle's infotainment system determines the candidate device with higher battery capacity or higher online reliability as the target device.

[0083] Taking voice broadcasting tasks in a cycling scenario as an example, in-vehicle infotainment systems, smart helmets, and Bluetooth headsets all have audio capabilities and can serve as candidate devices for the task. The in-vehicle infotainment system determines corresponding evaluation values ​​for each candidate device based on its audio capabilities, cycling safety level, battery status, power supply method, and online status. When the smart helmet is worn, online, and has sufficient battery power, it receives a higher evaluation value in terms of cycling safety level and capability matching. The in-vehicle infotainment system calculates the task adaptation score for each candidate device based on the corresponding target weights and determines the smart helmet with the highest task adaptation score as the target device for the voice broadcasting task.

[0084] By combining target capabilities with equipment capabilities information to determine capability matching, and by determining riding safety level, battery adequacy, power supply stability, and online reliability based on equipment capabilities and status information, candidate equipment can be evaluated in terms of capability, riding safety, and equipment availability. By dynamically determining the target weight of each evaluation factor based on scenario information, the task adaptation score can change with riding scenarios, parking scenarios, or business scenarios, thereby selecting the target carrying equipment that is suitable for the target task and the current scenario, improving the accuracy of task allocation, and reducing the need for users to manually select equipment.

[0085] In some embodiments, the method for synchronizing the service status of the target service among the plurality of target devices may further include the following: S1: Based on the task allocation results, determine the participating devices and the service data to be synchronized for executing the target service; S2: Using a distributed data management mechanism, the business data to be synchronized and the business status are synchronized to each of the participating devices; S3: Obtain user operation events generated by any of the participating devices; S4: Update the service status according to the user operation event, and send the updated service status to each of the participating devices.

[0086] In practice, the vehicle-mounted system reads the mapping relationship between target tasks and target carrier devices recorded in the task allocation results. Based on the device identifiers of each target carrier device, it determines the participating devices that will execute the target service. The vehicle-mounted system performs deduplication on the device identifiers in the task allocation results, ensuring that the same target device undertaking one or more target tasks is identified as only one participating device.

[0087] The vehicle's infotainment system determines the business data required to execute the corresponding target task based on the target task undertaken by each participating device, and identifies this business data as the business data to be synchronized for the corresponding participating device. The business data to be synchronized corresponds to the type of the target service. Specifically, the business data to be synchronized for navigation services may include navigation route, current location, navigation prompts, and real-time traffic information; the business data to be synchronized for music playback services may include media identifier, playback progress, and audio control information; the business data to be synchronized for incoming call services may include incoming call status, call status, and call control information; and the business data to be synchronized for photography services may include image preview data, shooting status, and data transmission progress.

[0088] The vehicle-mounted system establishes a correspondence between the target task, participating devices, and the business data to be synchronized, and determines the business data to be synchronized that each participating device needs to receive based on this correspondence. For example, the vehicle-mounted system responsible for map display receives navigation routes and current location; the smart helmet responsible for voice broadcasting receives navigation prompts; and the mobile phone responsible for obtaining real-time traffic information receives its current location and returns real-time traffic information. Thus, the corresponding business data can be synchronized according to the target tasks undertaken by the participating devices.

[0089] The vehicle-mounted system utilizes a distributed data management mechanism to establish corresponding distributed service data for target services, and writes the service data to be synchronized and the current service status into this distributed service data. Each participating device reads the service data to be synchronized and the service status corresponding to its own target task through a distributed soft bus, and executes the corresponding target task based on the read service data to be synchronized. When any participating device updates the distributed service data, the vehicle-mounted system sends the corresponding service data to be synchronized and the service status to other participating devices according to the updated content.

[0090] Participating devices detect user actions performed on target services and generate user operation events based on the detected actions. Each user operation event includes the device identifier that generated it, the operation type, and operation parameters. The operation type includes at least one of start, pause, resume, switch, end, and adjust, and the operation parameters represent the service content corresponding to the user operation. The participating devices send the user operation events to the vehicle's infotainment system via a distributed soft bus.

[0091] The vehicle-mounted system (V2X) determines the participating device that generated the user operation event based on the device identifier in the user operation event, and determines the service status that needs to be updated based on the operation type and operation parameters. When the participating device that generated the user operation event is not the target bearer device for the corresponding target task, the V2X determines the target bearer device corresponding to the target task based on the task allocation result, and forwards the user operation event to the target bearer device. The V2X updates the service status based on the execution result of the user operation event by the target bearer device, and sends the updated service status to each participating device, so that each participating device can continue to execute the corresponding target task according to the updated service status.

[0092] When any participating device is offline, the vehicle's infotainment system saves the business data to be synchronized and the updated business status that need to be sent to that participating device, and controls other online participating devices to continue executing the corresponding target tasks. When an offline participating device comes back online, the vehicle's infotainment system determines the target task corresponding to that participating device based on the device identifier, and sends the current business data to be synchronized and the business status to the online participating device, enabling the online participating device to continue the corresponding target task according to the current business status.

[0093] Taking navigation as an example, the in-vehicle infotainment system handles route calculation and map display, the smart helmet provides voice prompts, and the mobile phone acquires real-time traffic information. When a user triggers a route change operation through the in-vehicle infotainment system, the system generates a user operation event and updates the navigation route and progress accordingly. The system then synchronizes the updated navigation route to the mobile phone and the updated navigation prompts and progress to the smart helmet, enabling the mobile phone to acquire real-time traffic information according to the updated route and the smart helmet to provide voice prompts according to the updated navigation progress.

[0094] By determining the participating devices and the business data to be synchronized for each participating device based on the task allocation results, business data can be synchronized to the corresponding participating devices along with the target task. By converting user operation events generated by any participating device into business status updates and sending the updated business status to each participating device, the business execution progress and operation results of multiple participating devices can be kept consistent, avoiding users from repeatedly performing the same operations on different devices. Synchronizing the current business data and business status when a participating device goes offline and then comes back online also enables the participating device that has come back online to continue the target task from the current business status, improving the continuity of cross-device business execution.

[0095] In some embodiments, the method for determining the target weights corresponding to the capability matching degree, the riding safety level, the battery adequacy, the power supply stability, and the online reliability based on the scenario information may further include the following: S1: When the scene information represents a cycling scene, the target weight corresponding to the cycling safety level is determined as the maximum value among the target weights. Based on the task adaptation score of each candidate device, the display task is assigned to the vehicle system or the smart helmet, and the audio task is assigned to the smart helmet. S2: When the scene information represents a parking scene, the target weight corresponding to the capability matching degree is determined as the maximum value among the target weights, and the interaction task is assigned to the mobile phone according to the task adaptation score of each candidate device.

[0096] In practice, the vehicle-mounted system determines the current target scenario type based on scenario information and reads the corresponding weight configuration relationship based on the target scenario type. The weight configuration relationship specifies the relative magnitudes of the target weights corresponding to capability matching degree, riding safety level, battery adequacy, power supply stability, and online reliability. The vehicle-mounted system determines the weight of each target based on the weight configuration relationship and uses each target weight to calculate the task adaptation score of the candidate device for the target task.

[0097] When the scene information indicates that the target two-wheeled vehicle is in a riding scenario, the vehicle's system determines the target weight corresponding to the riding safety level as the maximum value among all target weights, while retaining the target weights corresponding to capability matching degree, battery adequacy, power supply stability, and online reliability. Therefore, candidate devices only receive the corresponding task adaptation score based on the riding safety level if they possess the capabilities required for the target task and are in an available state.

[0098] For display tasks, the vehicle-mounted system determines the display capability requirements based on the content to be displayed, and then selects the vehicle-mounted system and a smart helmet with head-up display (HUD) capability as candidate devices from a unified device capability pool. For display tasks involving complete navigation maps or vehicle status information, the vehicle-mounted system determines its task compatibility score based on its display capabilities, fixed installation location, and vehicle power supply method. For simplified display tasks such as direction indicators, distance prompts, or abnormal alarms, the vehicle-mounted system determines the smart helmet's task compatibility score based on its HUD capability, wearing status, and online status. The vehicle-mounted system compares the task compatibility scores of the vehicle-mounted system and the smart helmet, assigning the display task to the vehicle-mounted system or smart helmet with the higher task compatibility score.

[0099] For audio tasks, the vehicle's infotainment system selects a smart helmet as a candidate device from a unified device capability pool based on the audio capabilities corresponding to the task. It then determines the smart helmet's wearing status, online status, battery status, and any abnormal status based on the device status view. When the smart helmet is in a worn, online, fully charged, and not in an abnormal state, the system calculates a task compatibility score based on its audio capabilities and riding safety level. It then assigns voice broadcast tasks, incoming call audio tasks, or music playback tasks to the smart helmet, allowing the user to receive the corresponding audio information without manual operation.

[0100] Taking cycling navigation as an example, the vehicle's infotainment system assigns the task of displaying the complete map to itself, while the tasks of providing simplified directional guidance and voice prompts are assigned to the smart helmet that is already being worn. The vehicle's infotainment system displays the navigation route and vehicle status on its own screen, while the smart helmet provides directional guidance via a head-up display and outputs turning distance and road information via audio.

[0101] When the scene information indicates that the target two-wheeled vehicle is in a parking scenario, the vehicle's infotainment system determines the target weight corresponding to the capability matching degree as the maximum value among all target weights, and determines the phone's capability matching degree for the interactive task based on the phone's display capabilities, touch capabilities, network capabilities, and data processing capabilities. The infotainment system also calculates the phone's task adaptation score for the interactive task based on the phone's online status, battery level, power supply stability, and online reliability.

[0102] For interactive tasks such as destination input, navigation route selection, media content selection, viewing captured content, or adjusting service parameters, the vehicle's infotainment system selects the mobile phone with the highest task adaptation score from the corresponding candidate devices as the target device and assigns the interactive task to the mobile phone. The mobile phone displays the corresponding interactive interface based on the synchronized service status and sends the user operation events generated by the user through the interactive interface to the vehicle's infotainment system to update the service status of the target service.

[0103] When the target two-wheeled vehicle changes from a riding scenario to a parking scenario, the vehicle's system redetermines the weights of each target based on the updated scenario information and updates the task adaptation score of each candidate device using the redefined target weights. Based on the updated task adaptation score, the vehicle's system allocates interactive tasks requiring more user interaction to the mobile phone and synchronizes the current business status to the mobile phone, enabling users to continue performing the corresponding interactive tasks based on the business status formed in the riding scenario.

[0104] In some embodiments, the method updates the task allocation result in response to a change in the device state of any of the target devices. In a specific implementation, the method may further include the following: S1: If any of the target devices is detected to be offline, determine the affected target tasks corresponding to the offline target devices based on the task allocation results; S2: Based on the equipment capability information and equipment status information of the remaining target equipment, determine the target replacement equipment corresponding to the affected target task; S3: Assign the affected target tasks to the target replacement devices, and synchronize the current business status to the target replacement devices to obtain the updated task assignment results; S4: Utilize the vehicle-mounted system to cache the service status changes of the offline target device during the offline period.

[0105] In practice, the vehicle's infotainment system receives device status information periodically sent by each collaborative device and updates the device status view based on this information. When the vehicle's infotainment system does not receive device status information from any collaborative device within a preset detection period, or detects that the communication connection between the distributed soft bus and the collaborative device is broken, the vehicle's infotainment system identifies the collaborative device as an offline target device and updates the corresponding online status to offline status in the device status view.

[0106] The vehicle-mounted system, based on the device identifier of the offline target device, queries the mapping relationship between target tasks and target carrier devices recorded in the task allocation results. Target tasks whose target carrier device identifier matches the device identifier of the offline target device are identified as affected target tasks. Based on the target capabilities corresponding to the affected target tasks, the vehicle-mounted system sets the device capabilities in the unified device capability pool corresponding to the offline target device to unavailable.

[0107] For any affected target task, the vehicle's system determines other target devices with the corresponding capabilities from a unified device capability pool based on the target capabilities corresponding to the affected target task. It then removes other target devices that are offline, have insufficient power, or are in an abnormal state based on the device status view, resulting in alternative candidate devices. Based on the current scenario information, the vehicle's system determines the capability matching degree, riding safety level, battery adequacy, power supply stability, and online reliability of each alternative candidate device, and determines the task adaptation score of each alternative candidate device based on the above evaluation parameters.

[0108] The vehicle's infotainment system compares the task compatibility scores of each alternative candidate device and identifies the alternative candidate device with the highest task compatibility score as the target alternative device for the affected target task. When only one other target device is online, the vehicle's infotainment system determines the affected target task that the other target device can execute based on its device capability information and assigns the executable affected target task to the other target device.

[0109] The vehicle-mounted system obtains the current business status corresponding to the affected target task from distributed business data. The current business status includes at least one of the following: the current execution progress of the target task, current business data, and effective user operation results. The vehicle-mounted system assigns the affected target task to a target alternative device and synchronizes the current business status to the target alternative device, enabling the target alternative device to continue executing the affected target task from its current execution progress. The vehicle-mounted system replaces the offline target device's device identifier in the task assignment result with the device identifier of the target alternative device, obtaining an updated task assignment result.

[0110] The vehicle-mounted system establishes an offline cache record for offline target devices. This offline cache record includes the device identifier of the offline target device, the task identifier of the affected target task, and the service status at the time of offline. During the offline period, if any online participating device generates a user operation event or the target replacement device updates the task execution progress, the vehicle-mounted system updates the current service status based on the user operation event or task execution progress, and writes the corresponding service status change to the offline cache record. The service status change includes at least one of the following: task execution progress change, service data change, and user operation result change.

[0111] Taking the task of providing navigation voice broadcasts and simplified navigation prompts on a smart helmet as an example, when the vehicle's infotainment system detects that the smart helmet is offline, it identifies the navigation voice broadcast and simplified navigation prompt tasks as the affected target tasks based on the task allocation results. The system then determines the vehicle's own audio capabilities, display capabilities, online status, and vehicle power supply method as the target replacement device, and synchronizes the current navigation route, current navigation location, and current navigation progress to the system. The system continues to perform the voice broadcast and simplified navigation prompt tasks based on the current navigation progress, and caches navigation route changes, navigation location changes, and navigation progress changes that occurred during the smart helmet's offline period.

[0112] In some embodiments, the method may further include the following: S1: In response to the offline target device coming back online, obtain the current device capability information and current device status information corresponding to the re-online target device; S2: Based on the task allocation result, determine the original target task corresponding to the target device that is re-connected, and determine the task recovery result based on the current device capability information, the current device status information and the original target task; S3: If the task recovery result indicates that the re-connected target device can execute the original target task, determine the recovery business status based on the business status change and the current business status; S4: Synchronize the restored service status to the target device that has been brought back online, reallocate the original target task to the target device that has been brought back online, and continue to execute the original target task according to the restored service status.

[0113] In some embodiments, the method may further include the following: S1: The vehicle system periodically sends heartbeat detection information to each of the target devices; S2: Based on the heartbeat response information returned by each target device, determine the current online status and capability change information of each target device; S3: Update the unified device capability pool and the device status view based on the current online status and the capability change information; S4: Update the task allocation result based on the updated unified device capability pool and device status view, and control the multiple target devices to execute the corresponding target tasks based on the updated task allocation result.

[0114] In some embodiments, the method of controlling the plurality of target devices to perform corresponding target tasks may further include the following: Obtain the target event generated by any of the participating devices; Based on the target event, determine the linkage operation and the target linkage device for executing the linkage operation, and send the corresponding control command to the target linkage device; Obtain the control switching request for the target service; Based on the control switching request, the task allocation result, and the device status information, the target control device is determined, and the control authority of the target service is switched to the target control device. Obtain the service results generated by any of the participating devices, determine the target sharing device based on the service results, and send the service results to the target sharing device.

[0115] In some embodiments, the target service is a navigation service, and the method of controlling the plurality of target devices to execute the corresponding target task may further include the following: Obtain target location information; Using the vehicle's local navigation capabilities, navigation route information is determined based on the target location information and local map data; Based on the task allocation results, the vehicle's infotainment system performs route calculation and map display tasks, and the smart helmet performs navigation prompts. The navigation route information and real-time location status are synchronized to the smart helmet; When the mobile phone is online, real-time traffic information is obtained through the mobile phone, and the navigation route information is updated based on the real-time traffic information.

[0116] In some embodiments, the target service is a call service, and the method of controlling the plurality of target devices to perform corresponding target tasks may further include the following: The incoming call signal is obtained through the mobile phone and sent to the vehicle's infotainment system. Based on the incoming call command, determine the caller ID task, call control task, and call audio task; Based on the task allocation result, the caller ID task is executed through the vehicle's infotainment system, and the call control task and the call audio task are executed through the smart helmet. In response to a call answering command obtained through the smart helmet, a call connection is established using the mobile phone, and the call status is synchronized between the vehicle system, the mobile phone, and the smart helmet; In response to the termination of the call connection, the service status of the target two-wheeled vehicle is restored according to the service status before the call.

[0117] In some embodiments, the target service is a shooting service, and the method of controlling the plurality of target devices to perform corresponding target tasks may further include the following: Based on the aforementioned business requirements information, determine the video acquisition task, video preview task, shooting control task, and video transmission task; According to the task allocation results, the video acquisition task is executed through the smart helmet, the video preview task and the shooting control task are executed through the vehicle system, and the video transmission task is executed through the mobile phone; The system acquires the shooting control command generated by the vehicle's infotainment system and sends the shooting control command to the smart helmet. A video summary is determined based on the video data collected by the smart helmet, and the video summary is sent to the mobile phone so that the video summary can be uploaded via the mobile phone.

[0118] In some embodiments, the method may further include the following: S1: Build the target super terminal.

[0119] In two-wheeled vehicle usage scenarios, distributed soft bus technology is used to discover, connect, and network vehicle-mounted devices, mobile phones, smart helmets, and other collaborative devices, building multiple target devices into a unified target super terminal.

[0120] In the target super terminal, each target device is no longer considered an independent terminal, but rather a different capability node within the target super terminal. The vehicle-mounted system, as the main controller for collaborative scheduling of the target super terminal, is responsible for maintaining the target device list, the unified device capability pool, and the device status view.

[0121] The construction process of the target super terminal includes: after the vehicle-mounted system starts up, it broadcasts a network request through a distributed soft bus; after detecting the network request, collaborative devices such as mobile phones and smart helmets, after identity authentication and binding verification, connect to the vehicle-mounted system and join the target super terminal; each collaborative device registers its own capability description information with the vehicle-mounted system, and the vehicle-mounted system forms a unified device capability pool based on the capability description information of each target device; the vehicle-mounted system continuously monitors the online status and capability changes of each target device, and dynamically updates the unified device capability pool and device status view.

[0122] S2: Establish equipment capability information and equipment status information for the target equipment.

[0123] The vehicle-mounted system establishes device capability information and device status information for each connected target device, wherein the device capability information and device status information include at least one or more of the following: General capability information: Display capabilities (screen size, resolution, touch support); Audio output capabilities (speaker power, stereo support); Audio acquisition capabilities (number of microphones, noise reduction level); Camera capabilities (resolution, frame rate, viewing angle); Touch input capabilities (touchscreen, physical buttons, knobs); Voice interaction capabilities (speech recognition and speech synthesis support); Network capabilities (4G / 5G cellular, Wi-Fi, Bluetooth, StarFlash); Data processing capabilities (CPU computing power level); Storage capabilities (available storage space); Battery status (current battery percentage, power supply method); Online status (online, offline, or sleep); Device priority (master, auxiliary, or extended).

[0124] Cycling scenario capability information: Cycling safety level (whether the target device is suitable for operation while cycling: high, medium, or low; high for vehicle dashboards and smart helmet heads-up displays, low for mobile phones); Wearing status awareness capability (unique to smart helmets, used to detect whether the user is wearing a smart helmet); Vehicle control permissions (whether the target device has the right to read or control the vehicle's electrical equipment); Waterproof and shockproof rating (the target device's adaptability to outdoor cycling environments); Power supply method (vehicle power supply, independent battery, or passive device); Heads-up display capability (unique to smart helmets, used to indicate whether a heads-up display is supported).

[0125] The vehicle-mounted system registers the aforementioned device capability information and device status information to a unified device capability pool and a device status view, respectively, in order to perform device capability discovery, device capability invocation, and target task allocation.

[0126] S3: Performs cross-device capability discovery and invocation.

[0127] When a target service is launched, the vehicle-mounted system determines multiple target capabilities required by the target service based on the service requirements information, and searches for candidate devices that meet each target capability in the unified device capability pool of the target super terminal.

[0128] For example: navigation services require: route calculation capability (vehicle-mounted local system priority) + map display capability + voice broadcast capability + location data capability; call services require: incoming call signal receiving capability + audio input capability + audio output capability + incoming call interface display capability; video capture services require: camera capability + preview display capability + storage or transmission capability; music playback services require: music content source capability + audio output capability + playback control display capability.

[0129] The vehicle-mounted system breaks down the target service into multiple target tasks corresponding to each target capability, and maps these multiple target tasks to different target devices based on the device capability matching results. If the multiple target capabilities required by the target service are distributed across multiple target devices, a cross-device invocation mechanism is used to combine them into a complete service chain.

[0130] The rules for determining candidate devices include: 1. Prioritize candidate devices with high cycling safety levels to handle target tasks that require user attention, including display and interaction tasks; 2. Prioritize candidate devices that are currently online and have sufficient battery power; 3. Prioritize candidate devices with the highest capability matching, for example, for audio output tasks, prioritize smart helmets rather than car speakers; 4. Under the same conditions, priority should be given to candidate devices with higher power supply stability. Among them, the power supply stability of vehicle power supply is higher than that of independent battery power supply.

[0131] S4: Perform the synchronization and transfer of business data and business status to be synchronized.

[0132] During the operation of the target business, a distributed data management mechanism is used to synchronize and transfer the business data and business status to be synchronized among multiple participating devices.

[0133] The business data and business status to be synchronized include at least: navigation route information and real-time location data; music playback status, including track, playback progress and volume; call status, including caller ID, call duration and mute status; video stream data; device working status; user operation status, used to indicate user operations performed by the user on the corresponding participating device; alarm information; and riding mode information, including riding, stopped and charging.

[0134] The flow of business data and business status to be synchronized follows these principles: 1. The business data to be synchronized follows the task allocation results: When the target task is migrated from one target device to another, the relevant business data to be synchronized is synchronized to the target replacement device to ensure the continuity of the target business; 2. Real-time synchronization of service status: Service status such as playback progress, call status, and navigation location remains consistent across all participating devices; 3. Global broadcast of user operation events: User operations on any participating device, including pausing music, answering a call, and zooming in on the map, are broadcast to all relevant participating devices via the vehicle system to ensure consistent user operation results; 4. Caching and recovery of business status changes during offline periods: When the target device is temporarily offline, the vehicle system caches the corresponding business status changes of the offline target device during the offline period, and synchronizes them after the target device comes back online.

[0135] S5: Execute target task assignment.

[0136] As the main controller for collaborative scheduling, the vehicle-mounted system dynamically allocates target tasks among multiple target devices based on equipment capability information, scenario information, and business priorities using a task scheduling algorithm.

[0137] The allocation of target tasks is based on at least the following criteria: target scenario type, including cycling, parking, incoming call, navigation, shooting, and abnormal alarm scenarios; device online status; device remaining battery power; display size and location, including vehicle dashboard screens, mobile phone screens, and head-up displays of smart helmets; audio quality, including audio quality of smart helmet speakers, vehicle speakers, and Bluetooth headsets; cycling safety level, prioritizing target devices that do not require manual operation in cycling scenarios; user interaction burden, prioritizing operations that require user distraction; data processing capabilities; and network quality.

[0138] Task scheduling algorithm: For each target task, the vehicle's infotainment system calculates the task suitability score for each candidate device. The scoring formula is as follows: Task compatibility score = Ability matching degree × W1 + Cycling safety level × W2 + Battery adequacy × W3 + Power supply stability × W4 + Online reliability × W5.

[0139] Among them, the weights W1-W5 of each objective are dynamically adjusted according to the scenario information: Cycling scenario: The target weight W2 corresponding to the cycling safety level is determined as the maximum value among all target weights. Display tasks are prioritized to the vehicle instrument panel or the head-up display of the smart helmet, audio tasks are assigned to the smart helmet, and the mobile phone is used as the background data source. Parking scenario: The target weight W1 corresponding to the capability matching degree is determined as the maximum value among all target weights, and the interaction task is assigned to the mobile phone, while the vehicle system and smart helmet undertake auxiliary tasks; Incoming call scenario: Increase the target weight corresponding to the matching degree of riding safety level and audio capability, allocate incoming call information to the vehicle display, and allocate call audio tasks to the smart helmet; Anomaly alarm scenario: Set the execution priority of the anomaly alarm task to be higher than that of other target tasks, and synchronize the alarm information to all online target devices.

[0140] Task assignment example: Navigation activated while riding: The vehicle's infotainment system calculates the route locally and displays the map on the instrument panel. The infotainment system has route calculation capabilities, a high level of riding safety, and display capabilities. The smart helmet performs voice broadcast tasks. The smart helmet has a high level of riding safety and audio capabilities. The mobile phone serves as a candidate auxiliary device, providing real-time traffic data or alternative route calculations. The infotainment system can still complete navigation independently even when the mobile phone is offline. Incoming call while riding: The vehicle's dashboard displays the incoming call information, the smart helmet's microphone and speaker handle the call audio, and the phone processes the incoming call message in the background; After parking, browse the riding record: The mobile phone serves as the target device for interactive tasks, the vehicle's system displays auxiliary information, and the smart helmet enters sleep mode.

[0141] S6: Establish a cross-device collaborative working mechanism.

[0142] The vehicle-mounted system generates a cross-device collaborative control link based on the task allocation results, enabling multiple target devices to work together to execute corresponding target tasks around the same target business.

[0143] Cross-device collaborative working mechanisms should include at least the following: 1. Service Status Synchronization: Changes in the service status of one participating device are synchronized to other participating devices. For example, if a user pauses music on the vehicle's infotainment system, the smart helmet stops audio output, and the mobile phone updates its playback interface; 2. User Operation Event Linkage: A user operation event generated by one participating device drives other participating devices to perform corresponding actions. For example, if a smart helmet detects that a user has removed the helmet, the vehicle's infotainment system pauses the navigation voice broadcast and assigns the voice broadcast task to the vehicle's speakers; 3. Control handover: Control of the target service is transferred between target devices. For example, while riding, a user issues a voice command to answer a phone call through a smart helmet. After the call is established, the audio task is assigned to the smart helmet, and the display task is assigned to the vehicle's infotainment system. 4. Target Task Migration: When the target device performing the target task is insufficient or offline, the affected target task will be assigned to a target alternative device. For example, when the smart helmet's battery is low, the audio output task will be assigned to the vehicle's speakers; 5. Business Result Sharing: The business results generated by one target device are shared as synchronized business data for use by other target devices. For example, video captured by a smart helmet camera is previewed in real time by the vehicle's infotainment system and uploaded in the background by a mobile phone; 6. Target Task Interruption Recovery: If a target service is interrupted due to an abnormality in the target device, execution will resume from the interrupted point when the target device recovers, based on the current service status. For example, after a smart helmet temporarily disconnects and reconnects, it will continue executing the navigation voice broadcast task based on the current navigation location.

[0144] S7: Switch between scenario-based task allocation strategies.

[0145] The vehicle system determines the target scenario type based on the vehicle status information of the target two-wheeled vehicle, the device status view, the wearing status of the smart helmet, and the user behavior information, and switches the corresponding task allocation strategy according to the target scenario type.

[0146] The target scenario types include at least: Cycling Scenario: The vehicle's infotainment system determines that the target two-wheeled vehicle is being ridden based on vehicle status information, specifically, if the vehicle's speed is greater than zero, or if the target two-wheeled vehicle is unlocked and the smart helmet is being worn. Task Allocation Strategy: Prioritizing cycling safety. Display tasks are prioritized for allocation to the vehicle's instrument panel and the smart helmet's head-up display, audio interaction tasks are prioritized for allocation to the smart helmet, and the phone interface is switched to a low-interference mode, including a locked screen or displaying only a minimalist state. Unnecessary notifications are given lower priority or displayed later. Objective: To minimize the frequency with which users look down at their phones and perform manual operations.

[0147] Parking scenario: The vehicle's infotainment system determines that the target two-wheeled vehicle is parked based on vehicle status information, meaning the vehicle's speed is zero and the target two-wheeled vehicle is locked. Task allocation strategy: Prioritize ease of operation. Allocate more operational permissions and interactive tasks to the mobile phone, the vehicle's infotainment system displays auxiliary information, and the smart helmet switches to low-frequency listening mode or sleep mode. Goal: To provide a complete operating experience by utilizing the display and touch capabilities of the mobile phone.

[0148] Incoming call scenario: The mobile phone receives an incoming call command and sends it to the vehicle's infotainment system via a distributed soft bus. Task allocation strategy: The vehicle's instrument panel displays the caller ID and contact information, the smart helmet's speaker plays the ringtone, and the user answers or rejects the call via buttons or voice commands on the smart helmet. After answering, the smart helmet's microphone and speaker execute the call audio task, and the vehicle's infotainment system displays the call status and duration. After the call ends, the vehicle's infotainment system controls multiple target devices to resume navigation or music playback tasks based on the service status before the call. Objective: To answer calls while riding without touching the phone.

[0149] Navigation Scenario: Users input their destination and initiate navigation on their in-vehicle infotainment system or mobile phone. Task Allocation Strategy: The navigation engine runs locally on the in-vehicle infotainment system and performs route calculations. The in-vehicle instrument cluster serves as the primary map display device, while the head-up display (HUD) on the smart helmet shows simplified turn arrows and distance information. The smart helmet's speaker broadcasts navigation prompts. When the mobile phone is online, it serves as an auxiliary data source, providing real-time traffic information and points of interest (POIs). Offline operation of the mobile phone does not affect the core navigation task. When users zoom in and out on the map on the in-vehicle infotainment system, the updated navigation status is synchronized to all online participating devices. Objective: Core navigation calculations are completed locally on the in-vehicle infotainment system, independent of the mobile phone. Navigation information is displayed hierarchically across different target devices, eliminating the need for users to look down at their phones.

[0150] Shooting Scenario: The user initiates the cycling recording or shooting service; Task Allocation Strategy: The smart helmet's camera captures the video stream, the vehicle's instrument panel provides a real-time preview of the screen and offers control operations such as start, pause, and marking, and the mobile phone receives the video summary in the background and performs cloud upload or social sharing after the ride ends; Target: The capture task, preview task, control task, and sharing task are respectively assigned to the corresponding target devices.

[0151] Music playback scenario: Users select music content via their mobile phones; Task allocation strategy: The mobile phone provides the music content source and account access, the vehicle's dashboard displays the current track and playback control information, including previous track, next track, and pause, and the smart helmet speaker performs audio output tasks. Playback progress, pause status, and track skipping operations are synchronized across the three participating devices. When the smart helmet disconnects, the audio output task is assigned to the vehicle's speaker; when the target two-wheeled vehicle enters a parking scenario, more control tasks are assigned to the mobile phone; Objective: To control music while riding via vehicle shortcut keys or smart helmet voice commands, without needing to operate the mobile phone.

[0152] Anomaly Alarm Scenario: The vehicle's infotainment system detects an anomaly in the target two-wheeled vehicle, including abnormal tire pressure, battery overheating, vibration alarms, or receives a safety alarm from the cloud. Task Allocation Strategy: The alarm information is synchronized to all online target devices. The vehicle's instrument panel displays the alarm content in full screen, the smart helmet speaker plays the alarm audio, and the mobile phone pushes an alarm notification. The execution priority of the anomaly alarm task is higher than other target tasks, and the currently playing music or navigation audio is paused or its volume is reduced. Objective: To enable users to perceive safety alarms through any online target device.

[0153] S8: Perform offline downgrade of the target device and continue the target task.

[0154] The vehicle-mounted system records the device identifier, device status information, device capability information, service status, and abnormal status of each target device. When the device status of any target device changes, the task allocation results are updated to perform target task downgrading and service continuation.

[0155] Downgrade strategy: 1. Smart Helmet Offline: When the smart helmet is offline, including when the user removes it, the helmet's battery is depleted, or it is outside the communication range, the vehicle's infotainment system determines the affected target tasks for the smart helmet based on the task allocation results and assigns these tasks to alternative devices. Voice broadcast tasks are assigned to the vehicle's speakers, head-up display content is fully displayed on the vehicle's instrument panel, and call audio tasks are assigned to the vehicle's speakers and microphone or a hands-free phone. The vehicle's infotainment system marks the smart helmet as offline in the device status view, retains the helmet's device capability information, and restores the corresponding task allocation results once the smart helmet is back online. 2. Offline Phone Response: When the mobile network is abnormal or the phone is offline, the vehicle's infotainment system continues to perform navigation tasks using the local navigation engine and cached map data. The local interface on the instrument cluster, including navigation routes and downloaded music, is retained, with only a delay in synchronizing auxiliary data that relies on external networks, including real-time traffic information and cloud messages. The system maintains a basic connection to the cloud via its own 4G network. Once the phone is back online, the system will synchronize the changes in the phone's service status during the offline period to the phone. 3. In-vehicle infotainment system malfunction: When the in-vehicle infotainment system displays abnormally or restarts, the mobile phone takes over the navigation display and service control tasks, while the smart helmet continues to perform audio output tasks. After the in-vehicle infotainment system recovers, it synchronizes the current service status from the mobile phone and restores the collaborative scheduling master control. 4. Multiple target devices offline simultaneously: When only one target device is online, the target tasks that can be executed will be assigned to the online target device to ensure the continuity of navigation services and anomaly alarm services.

[0156] Business status consistency maintenance: When the device status of any target device changes, the vehicle-mounted system updates the display logic and control logic of other related target devices; when a target device comes back online, the vehicle-mounted system synchronizes the current business status and changes in the unified device capability pool to the re-online target device, so that the re-online target device is restored to the corresponding working state; the vehicle-mounted system periodically sends heartbeat detection information to all online collaborative devices to detect whether the collaborative devices are offline, and executes a degradation strategy when the collaborative devices are offline.

[0157] Based on the above embodiments, compared with the existing solutions where each device operates independently in two-wheeled vehicle scenarios, this specification constructs target devices such as vehicle-mounted systems, mobile phones, and smart helmets into a target super terminal. The vehicle-mounted system maintains a unified device capability pool and device status view, enabling unified access to the display, audio, camera, network, and data processing capabilities of different target devices, reducing idle device capabilities and repetitive operations. By determining task allocation results based on scenario information, device capability information, and device status information, and increasing the target weight corresponding to the riding safety level in the riding scenario, target tasks can be assigned to target devices adapted to the current scenario, reducing the need for users to look down at their phones and manually switch devices. By synchronizing pending business data and business status among multiple participating devices and updating business status based on user operation events, cross-device linkage and continuous flow of target services can be achieved. When a target device is offline or malfunctioning, by updating the task allocation results, synchronizing the current business status, and caching changes in business status during the offline period, other available target devices can continue to execute the affected target tasks, thereby improving the continuity of services such as navigation, calls, music playback, shooting, and abnormal alarms, as well as adaptability to different riding scenarios.

[0158] In some embodiments, this specification also provides a two-wheeled vehicle multi-device collaborative system, which, in specific implementation, may further include the following: The information acquisition module is used to acquire scene information of the target two-wheeled vehicle, business requirement information of the target business, and equipment capability information and equipment status information of multiple target devices; wherein, the multiple target devices include a vehicle-mounted unit and at least one collaborative device; The task allocation module is used to determine multiple target tasks corresponding to the target business based on the business requirement information, and to determine the task allocation results corresponding to the multiple target tasks based on the scenario information, the device capability information and the device status information. The collaborative control module is used to control the multiple target devices to execute corresponding target tasks according to the task allocation results, and to synchronize the service status of the target service among the multiple target devices; The allocation update module is used to update the task allocation result according to the changed device status information and the service status in response to a change in the device status of any of the target devices, and to control the multiple target devices to execute the corresponding target tasks according to the updated task allocation result.

[0159] As can be seen from the above, the embodiments of this specification provide a method for multi-device collaboration in two-wheeled vehicles, which acquires scene information of the target two-wheeled vehicle, business requirement information of the target service, and device capability information and device status information of multiple target devices. The multiple target devices include a vehicle-mounted system and at least one collaborative device. Based on the business requirement information, multiple target tasks corresponding to the target service are determined, and based on the scene information, device capability information, and device status information, task allocation results corresponding to the multiple target tasks are determined. Based on the task allocation results, the multiple target devices are controlled to execute the corresponding target tasks, and the business status of the target service is synchronized among the multiple target devices. In response to a change in the device status of any target device, the task allocation results are updated based on the changed device status information and the business status, and the multiple target devices are controlled to execute the corresponding target tasks based on the updated task allocation results. Thus, compared to the existing method where each device operates independently and the user needs to manually switch devices to execute business tasks, this application can control multiple target devices to execute corresponding target tasks according to the task allocation results, reducing the need for manual switching between different devices. On the one hand, the task allocation results are determined based on scenario information, business requirement information, equipment capability information, and equipment status information, and the business status is synchronized among multiple target devices. On the other hand, when the equipment status of any target device changes, the task allocation results are updated based on the changed equipment status information and business status, so that the relevant target tasks can be adjusted and continued in a timely manner, thereby improving the continuity of target services.

[0160] See Figure 2 As shown in the embodiments of this specification, a specific electronic device is also provided, wherein the electronic device includes a network communication port 201, a processor 202 and a memory 203, and the above structures are connected by internal cables so that the various structures can perform specific data interaction.

[0161] Specifically, the network communication port 201 can be used to acquire scene information of the target two-wheeled vehicle, business requirement information of the target service, and equipment capability information and equipment status information of multiple target devices; wherein, the multiple target devices include vehicle-mounted units and at least one collaborative device.

[0162] The processor 202 can be specifically configured to: determine multiple target tasks corresponding to the target service based on the service requirement information; determine task allocation results corresponding to the multiple target tasks based on the scenario information, the device capability information, and the device status information; control the multiple target devices to execute the corresponding target tasks based on the task allocation results; synchronize the service status of the target service among the multiple target devices; and update the task allocation results based on the changed device status information and the service status in response to a change in the device status of any target device, and control the multiple target devices to execute the corresponding target tasks based on the updated task allocation results.

[0163] The memory 203 can be used to store the corresponding instruction program.

[0164] Based on the above method, the relevant structural performance of electronic devices can be effectively utilized to improve the data processing speed of electronic devices and efficiently realize a collaborative method for multiple devices in a two-wheeled vehicle.

[0165] In this embodiment, the network communication port 201 can be a virtual port bound to different communication protocols, thereby enabling the sending or receiving of different data. For example, the network communication port can be a port responsible for web data communication, a port responsible for FTP data communication, or a port responsible for email data communication. Furthermore, the network communication port can also be a physical communication interface or communication chip. For example, it can be a wireless mobile network communication chip, such as GSM or CDMA; it can also be a Wi-Fi chip; or it can be a Bluetooth chip.

[0166] In this embodiment, the processor 202 can be implemented in any suitable manner. For example, the processor can take the form of a microprocessor or processor and a computer-readable medium storing computer-readable program code (e.g., software or firmware) executable by the (micro)processor, logic gates, switches, application-specific integrated circuits (ASICs), programmable logic controllers, and embedded microcontrollers, etc. This specification is not limiting.

[0167] In this embodiment, the memory 203 may include a hierarchy. In a digital system, anything that can store binary data can be a memory. In an integrated circuit, a circuit with storage function but no physical form is also called a memory, such as RAM, FIFO, etc. In a system, a storage device with a physical form is also called a memory, such as a memory stick, TF card, etc.

[0168] This specification also provides a computer-readable storage medium based on the above-described method for multi-device collaboration in two-wheeled vehicles. This medium acquires scenario information of the target two-wheeled vehicle, business requirement information of the target service, and device capability and status information of multiple target devices. The multiple target devices include a vehicle-mounted system and at least one collaborative device. Based on the business requirement information, multiple target tasks corresponding to the target service are determined, and based on the scenario information, device capability information, and device status information, task allocation results corresponding to the multiple target tasks are determined. Based on the task allocation results, the multiple target devices are controlled to execute the corresponding target tasks, and the business status of the target service is synchronized among the multiple target devices. In response to a change in the device status of any target device, the task allocation results are updated based on the changed device status information and the business status, and the multiple target devices are controlled to execute the corresponding target tasks based on the updated task allocation results.

[0169] In this embodiment, the storage medium includes, but is not limited to, Random Access Memory (RAM), Read-Only Memory (ROM), Cache, Hard Disk Drive (HDD), or Memory Card. The memory can be used to store computer program instructions. The network communication unit can be an interface configured according to standards specified in the communication protocol for network connection communication.

[0170] In this embodiment, the specific functions and effects implemented by the program instructions stored in the computer-readable storage medium can be explained in comparison with other embodiments, and will not be repeated here.

[0171] See Figure 3 At the software level, embodiments of this specification also provide a multi-device collaborative device for two-wheeled vehicles, which may specifically include the following structural modules: The information acquisition module 301 is used to acquire scene information of the target two-wheeled vehicle, business requirement information of the target business, and equipment capability information and equipment status information of multiple target devices; wherein, the multiple target devices include a vehicle-mounted unit and at least one collaborative device; The task allocation module 302 is used to determine multiple target tasks corresponding to the target business based on the business requirement information, and to determine the task allocation results corresponding to the multiple target tasks based on the scenario information, the device capability information and the device status information. The status synchronization module 303 is used to control the multiple target devices to execute corresponding target tasks according to the task allocation results, and to synchronize the service status of the target service among the multiple target devices; The task execution module 304 is used to respond to a change in the device status of any of the target devices, update the task allocation result according to the changed device status information and the service status, and control the multiple target devices to execute the corresponding target tasks according to the updated task allocation result.

[0172] In some embodiments, the above-described device further includes: the collaborative device includes at least one of a mobile phone, a smart helmet, a Bluetooth headset, an action camera, and a cycling sensor; the device capability information includes general capability information and cycling scenario capability information; wherein, the general capability information includes at least one of display capability, audio capability, camera capability, network capability, and data processing capability, and the cycling scenario capability information includes at least one of cycling safety level, wearing status, vehicle control permissions, power supply method, and head-up display capability; the device status information includes at least one of online status, battery status, and abnormal status.

[0173] In some embodiments, the information acquisition module 301, in specific implementation, sends a network request to the collaborative device via the vehicle-mounted system based on a distributed soft bus; receives the device identifier, capability description information, and device status information returned by the collaborative device according to the network request; performs identity authentication and binding verification on the collaborative device based on the device identifier, and connects the collaborative device that has passed the identity authentication and binding verification to the vehicle-mounted system to construct a target super terminal; determines the unified device capability pool and device status view corresponding to the target super terminal based on the capability description information and device status information of each target device, and determines the device capability information of each target device based on the unified device capability pool. It also acquires the vehicle status information and user behavior information of the target two-wheeled vehicle; determines the target scenario type of the target two-wheeled vehicle based on the vehicle status information, the device status view, the wearing status, and the user behavior information; and determines the scenario information based on the target scenario type; wherein the target scenario type includes at least one of riding scenario, parking scenario, incoming call scenario, navigation scenario, shooting scenario, music playback scenario, and abnormal alarm scenario.

[0174] In some embodiments, the task allocation module 302, in its specific implementation, determines multiple target capabilities required by the target service based on the service requirement information; divides the target service into multiple target tasks corresponding to each of the target capabilities based on the multiple target capabilities; determines candidate devices corresponding to each target task based on the target capabilities corresponding to each target task, the unified device capability pool, and the device status view; and the target bearer device determination module is used to determine the target bearer device from the candidate devices corresponding to each target task based on the scenario information, and determine the task allocation result based on the target bearer device corresponding to each target task.

[0175] In some embodiments, the target carrier device determination module, in specific implementation, for any target task, determines the capability matching degree of each candidate device based on the target capability corresponding to the target task and the device capability information of each candidate device; determines the riding safety level, battery adequacy, power supply stability, and online reliability of each candidate device based on the device capability information and device status information of each candidate device; determines the target weights corresponding to the capability matching degree, riding safety level, battery adequacy, power supply stability, and online reliability of each candidate device based on the scenario information; uses each target weight to perform weighted processing on the capability matching degree, riding safety level, battery adequacy, power supply stability, and online reliability of each candidate device to determine the task adaptation score of each candidate device for the target task; and determines the target carrier device corresponding to the target task from among the candidate devices based on the task adaptation scores of each candidate device.

[0176] In some embodiments, the state synchronization module 303, in its specific implementation, determines the participating devices and the business data to be synchronized based on the task allocation result; uses a distributed data management mechanism to synchronize the business data to be synchronized and the business status to each of the participating devices; acquires user operation events generated by any of the participating devices; updates the business status based on the user operation events, and sends the updated business status to each of the participating devices.

[0177] In some embodiments, the task execution module 304, when detecting that any of the target devices is offline, determines the affected target task corresponding to the offline target device based on the task allocation result; determines the target replacement device corresponding to the affected target task based on the device capability information and device status information of the remaining target devices; allocates the affected target task to the target replacement device and synchronizes the current business status to the target replacement device to obtain an updated task allocation result; and uses the vehicle system to cache the business status changes corresponding to the offline target device during the offline period.

[0178] In some embodiments, the above-described apparatus further includes: in response to the offline target device coming back online, obtaining current device capability information and current device status information corresponding to the re-online target device; determining the original target task corresponding to the re-online target device based on the task allocation result, and determining a task recovery result based on the current device capability information, the current device status information, and the original target task; if the task recovery result indicates that the re-online target device can execute the original target task, determining a restored business status based on the business status change and the current business status; synchronizing the restored business status to the re-online target device, reassigning the original target task to the re-online target device, and continuing to execute the original target task based on the restored business status.

[0179] In some embodiments, the above-described device further includes: periodically sending heartbeat detection information to each of the target devices via the vehicle-mounted system; determining the current online status and capability change information of each target device based on the heartbeat response information returned by each target device; updating the unified device capability pool and the device status view based on the current online status and the capability change information; updating the task allocation result based on the updated unified device capability pool and device status view; and controlling the multiple target devices to execute corresponding target tasks based on the updated task allocation result.

[0180] It should be noted that the units, devices, or modules described in the above embodiments can be implemented by computer chips or physical entities, or by products with certain functions. For ease of description, the above devices are described by dividing them into various modules according to their functions. Of course, in implementing this specification, the functions of each module can be implemented in the same software and / or hardware, or modules that implement the same function can be implemented by a combination of sub-modules or sub-units, etc. The device embodiments described above are merely illustrative. For example, the division of units is only a logical functional division, and there may be other division methods in actual implementation. For example, units or components can be combined or integrated into another system, or some features can be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection between the devices or units shown or discussed can be through some interfaces, and the indirect coupling or communication connection between devices or units can be electrical, mechanical, or other forms.

[0181] As can be seen from the above, based on the embodiments of this specification, a two-wheeled vehicle multi-device collaborative device acquires scene information of the target two-wheeled vehicle, business requirement information of the target service, and device capability information and device status information of multiple target devices; wherein, the multiple target devices include a vehicle-mounted unit and at least one collaborative device; Based on the business requirement information, multiple target tasks corresponding to the target business are determined, and based on the scenario information, the device capability information, and the device status information, the task allocation results corresponding to the multiple target tasks are determined. Based on the task allocation results, control the multiple target devices to execute corresponding target tasks, and synchronize the service status of the target services among the multiple target devices; In response to a change in the device status of any of the target devices, the task allocation result is updated based on the changed device status information and the service status, and the multiple target devices are controlled to execute the corresponding target tasks based on the updated task allocation result.

[0182] In a specific scenario example, the multi-device collaboration method and apparatus for two-wheeled vehicles provided in this specification can be applied to solve the problem that business tasks need to be manually switched when multiple devices on a two-wheeled vehicle operate independently, and that related tasks are difficult to continue in a timely manner when device status changes. The specific implementation process may include the following:

[0183] In navigation collaboration scenarios, users can initiate navigation by inputting their destination via voice input on the vehicle's dashboard or by using a rotary knob, or by inputting the destination on their mobile phone and synchronizing the destination information to the vehicle's infotainment system. The vehicle's infotainment system uses its local navigation engine to calculate the route and, based on the navigation service's requirements, determines the route calculation task, map display task, simplified navigation prompt task, voice broadcast task, and auxiliary data acquisition task. When the target two-wheeled vehicle is in a riding scenario, the vehicle's infotainment system determines the target weight corresponding to the riding safety level as the maximum value among all target weights. Based on the task adaptation scores of each candidate device, it assigns the route calculation and map display tasks to the vehicle's infotainment system, the simplified navigation prompt and voice broadcast tasks to the smart helmet that is being worn, and the auxiliary data acquisition task to the online mobile phone. This allows the vehicle's dashboard to display a complete navigation map, remaining distance, and estimated arrival time, enabling intelligent navigation. The helmet's head-up display shows turn arrows and distance information, the smart helmet's speaker broadcasts voice navigation prompts, and the mobile phone provides real-time traffic information, point-of-interest search, and online map updates. The vehicle's infotainment system synchronizes navigation routes, real-time location, and navigation status to all participating devices through a distributed data management mechanism, and updates the navigation status based on map zooming events generated by the user using the vehicle's control knob. When the smart helmet is offline, the vehicle's infotainment system assigns voice broadcasting and simplified navigation prompts to itself, and continues voice broadcasting through the vehicle's speaker and displays corresponding navigation prompts on the vehicle's instrument panel according to the current service status. When the smart helmet returns to online status and is being worn, the vehicle's infotainment system synchronizes the current navigation location and navigation progress to the smart helmet, allowing the smart helmet to resume simplified navigation prompts and voice broadcasting from the current navigation location, thus maintaining continuous navigation service when the mobile phone is offline or the smart helmet is temporarily offline.

[0184] In the call coordination scenario, when a user receives an incoming call command on their mobile phone while riding, the vehicle's infotainment system determines the tasks for receiving the incoming call command, displaying the incoming call information, answering the call, and audio input / output based on the service requirements of the incoming call service. It then assigns the incoming call command receiving task to the mobile phone, the incoming call information display task to the vehicle's infotainment system, and the answering the call and audio input / output tasks to the smart helmet based on the task adaptation score corresponding to the riding scenario. The mobile phone receives the incoming call command in the background and sends it to the vehicle's infotainment system via a distributed soft bus. The vehicle's dashboard displays the caller ID and contact information in an area that does not completely obscure the navigation map, and the smart helmet's speaker plays the incoming call ringtone. The user answers the call via the buttons on the side of the smart helmet or the "answer" button. The "listen" voice command triggers a call answering event. The vehicle's infotainment system updates the call status based on this event, controls the microphone and speaker of the smart helmet to perform call audio tasks, and the phone processes call signaling in the background while the vehicle's instrument panel displays the call status and duration. The vehicle's infotainment system uses a distributed data management mechanism to synchronize the call status between the phone, the vehicle's infotainment system, and the smart helmet, and records the navigation status and music playback status before the call. After the call ends, the vehicle's infotainment system controls the smart helmet to resume navigation voice broadcasting based on the recorded navigation status and music playback status, and resumes music playback if it was in music playback mode before the call, thereby reducing the user's need to take out the phone, unlock the phone, switch applications, and manually resume the original service while riding.

[0185] In helmet-based camera collaboration scenarios, users initiate recording by issuing a "start recording" voice command through their smart helmet. The vehicle's infotainment system determines video capture, preview display, shooting control, video storage, and video sharing tasks based on the recording requirements. It then allocates tasks according to the helmet's camera capabilities, the infotainment system's display capabilities, and the phone's network capabilities: video capture and storage to the helmet, preview display and shooting control to the infotainment system, and video sharing to the phone. The helmet uses its camera to capture the video stream, stores it locally, and then... A distributed soft bus sends the video stream to the vehicle's instrument panel for real-time preview. Users can initiate, pause, or mark events using knobs or touch controls on the instrument panel. The system updates the recording status based on these events and synchronizes the updated status to the smart helmet. When the user issues a "stop recording" voice command or the target two-wheeled vehicle finishes riding, the system controls the smart helmet to stop video capture and synchronizes the video summary to the user's mobile phone. This allows users to perform video editing, social sharing, or cloud backup in parking scenarios via their mobile phones, enabling collaborative access to video capture, preview display, shooting control, video storage, and video sharing capabilities across multiple target devices.

[0186] In a music-enabled scenario, before riding, the user selects a music playlist and starts the music playback service via their mobile phone. The vehicle's infotainment system determines the tasks for music content acquisition, playback information display, playback control, and audio output based on the service requirements of the music playback service. When the target two-wheeled vehicle is in the riding scenario, the system assigns the music content acquisition task to the mobile phone, the playback information display and playback control tasks to the vehicle's infotainment system, and the audio output task to the smart helmet that is being worn, based on the task adaptation scores of each candidate device. The mobile phone performs music content source access and account authentication in the background, the vehicle's dashboard displays the current track name, artist, and playback progress, and allows users to receive previous, next, and pause operations via physical buttons or knobs. The smart helmet's speaker outputs music audio. The vehicle's infotainment system utilizes a distributed data management mechanism to synchronize track information, playback progress, and pause status between the mobile phone, the vehicle's infotainment system, and the smart helmet. It also updates the music playback status based on any song skipping or pause operation event generated by any participating device. When the smart helmet is offline, the vehicle's infotainment system assigns the audio output task to the vehicle's speakers and continues to output music audio according to the current playback progress. When the smart helmet comes back online and is being worn, the vehicle's infotainment system synchronizes the current track information and playback progress to the smart helmet and reallocates the audio output task to the smart helmet. When the target two-wheeled vehicle changes from a riding scenario to a parking scenario, the vehicle's infotainment system increases the target weight corresponding to the capability matching degree and assigns interactive tasks such as playlist management and song search to the mobile phone, enabling users to perform complete music playback control through their mobile phones.

[0187] In some embodiments, see Figure 4 As shown, the target super terminal includes a vehicle-mounted infotainment system, a mobile phone, a smart helmet, and other collaborative devices. The vehicle-mounted infotainment system serves as the main control and display platform for collaborative scheduling and is equipped with a super terminal construction module, a device capability registration module, a distributed task scheduling module, a scene recognition module, a collaborative control module, and a unified device management module. The vehicle-mounted infotainment system connects to the mobile phone, smart helmet, and other collaborative devices via a distributed soft bus to utilize the network and application capabilities of the mobile phone, the voice interaction, head-up display, camera, and wear detection capabilities of the smart helmet, as well as the extended capabilities of Bluetooth headsets, action cameras, and cycling sensors. The vehicle-mounted infotainment system and the mobile phone also communicate with the cloud service platform via 4G or Wi-Fi to achieve data synchronization, remote control, and content services.

[0188] In some embodiments, see Figure 5As shown, the physical device layer includes a vehicle-mounted infotainment system, a mobile phone, and a smart helmet. The vehicle-mounted infotainment system has display, audio, and data processing capabilities; the mobile phone has network, data processing, and display capabilities; and the smart helmet has audio, camera, head-up display, and wearing status awareness capabilities. Each target device registers its corresponding device capability information to a unified device capability pool maintained by the vehicle-mounted infotainment system. The unified device capability pool includes display, audio, camera, network, data processing, riding safety level, wearing status awareness, and vehicle control permissions. Navigation, call, music, and photography services match and call the corresponding target device's device capabilities from the unified device capability pool according to their respective required target capabilities.

[0189] In some embodiments, see Figure 6 As shown, in a cycling scenario, the vehicle's infotainment system increases the target weight corresponding to the cycling safety level and determines the task allocation results for navigation, music, and incoming call services based on the task adaptation scores of each candidate device. Among them, the mobile phone, as the target device with a low cycling safety level, provides real-time traffic data, music content sources, and incoming call processing in the background; the smart helmet, as the target device with a high cycling safety level, performs tasks such as navigation voice broadcast, simplified turn prompts via head-up display, music audio output, and call audio input / output; and the vehicle's infotainment system, as the target device with a high cycling safety level, performs tasks such as local route calculation and navigation map display, track information and playback control display, and incoming call information display, thereby reducing the user's manual operation of the mobile phone during cycling.

[0190] In some embodiments, see Figure 7 As shown, when the vehicle's infotainment system detects a change in the device status of a target device, it determines the corresponding degradation strategy based on the offline device. When the smart helmet is offline, the voice broadcast task is switched to the vehicle's speakers, the head-up display content is switched to the vehicle's instrument panel, and the call audio task is switched to the mobile phone. When the mobile phone is offline, the vehicle's local business interface is retained, and the cloud connection is maintained using the vehicle's mobile communication network. When the vehicle's infotainment system malfunctions, the mobile phone takes over the navigation display and business control, while the smart helmet continues to output audio. The vehicle's infotainment system updates the device management table and retains the capability configuration information of offline devices. When an offline device comes back online, it synchronizes the current business status with the device, restores the original task allocation, and resumes business execution from the interrupted point. When an offline device does not come back online, it maintains a degraded state to ensure the continuity of core business.

[0191] While this specification provides the steps of operation for the methods described in the embodiments or flowcharts, more or fewer steps may be included based on conventional or non-inventive means. The order of steps listed in the embodiments is merely one possible order of execution among many steps and does not represent the only possible order. In actual device or client product execution, the methods shown in the embodiments or drawings may be executed sequentially or in parallel (e.g., in a parallel processor or multi-threaded processing environment, or even a distributed data processing environment). The terms "comprising," "including," or any other variations thereof are intended to cover a non-exclusive inclusion, such that a process, method, product, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, product, or apparatus. Without further limitations, the presence of other identical or equivalent elements in a process, method, product, or apparatus that includes said elements is not excluded. The terms "first," "second," etc., are used to denote names and do not indicate any particular order.

[0192] Those skilled in the art will also know that, besides implementing the controller using purely computer-readable program code, the same functions can be achieved by logically programming the method steps, making the controller function as logic gates, switches, application-specific integrated circuits (ASICs), programmable logic controllers (PLCs), and embedded microcontrollers. Therefore, such a controller can be considered a hardware component, and the devices within it used to implement various functions can also be considered structures within that hardware component. Alternatively, the devices used to implement various functions can be considered as both software modules implementing the method and structures within a hardware component.

[0193] As can be seen from the above description of the embodiments, those skilled in the art can clearly understand that this specification can be implemented by means of software plus necessary general-purpose hardware platforms. Based on this understanding, the technical solutions of this specification can essentially be embodied in the form of a software product. This computer software product can be stored in a storage medium, such as ROM / RAM, magnetic disk, optical disk, etc., and includes several instructions to cause a computer device (which may be a personal computer, mobile terminal, server, or network device, etc.) to execute the methods described in the various embodiments or some parts of the embodiments of this specification.

[0194] Although this specification has been described by way of examples, those skilled in the art will recognize that many variations and modifications are possible without departing from the spirit of this specification, and it is intended that the appended claims cover such variations and modifications without departing from the spirit of this specification.

Claims

1. A method for multi-device collaboration in a two-wheeled vehicle, characterized in that, include: Acquire scenario information of the target two-wheeled vehicle, business requirement information of the target business, and equipment capability and status information of multiple target devices; wherein, the multiple target devices include vehicle-mounted units and at least one collaborative device; Based on the business requirement information, multiple target tasks corresponding to the target business are determined, and based on the scenario information, the device capability information, and the device status information, the task allocation results corresponding to the multiple target tasks are determined. Based on the task allocation results, control the multiple target devices to execute corresponding target tasks, and synchronize the service status of the target services among the multiple target devices; In response to a change in the device status of any of the target devices, the task allocation result is updated based on the changed device status information and the service status, and the multiple target devices are controlled to execute the corresponding target tasks based on the updated task allocation result.

2. The method according to claim 1, characterized in that, The collaborative device includes at least one of a mobile phone, a smart helmet, a Bluetooth headset, an action camera, and a cycling sensor; The device capability information includes general capability information and cycling scenario capability information; wherein, the general capability information includes at least one of display capability, audio capability, camera capability, network capability and data processing capability, and the cycling scenario capability information includes at least one of cycling safety level, wearing status, vehicle control permissions, power supply method and head-up display capability; The device status information includes at least one of online status, power status, and abnormal status.

3. The method according to claim 2, characterized in that, The step of obtaining the device capability information and device status information of the multiple target devices includes: The vehicle-mounted system sends a network request to the collaborative device via a distributed soft bus. Receive the device identifier, capability description information, and device status information returned by the collaborative device according to the networking request; Based on the device identifier, the collaborative device is authenticated and bound, and the collaborative device that has passed the authentication and binding verification is connected to the vehicle system to build the target super terminal; Based on the capability description information and device status information of each target device, a unified device capability pool and device status view corresponding to the target super terminal are determined, and the device capability information of each target device is determined based on the unified device capability pool.

4. The method according to claim 3, characterized in that, The step of obtaining the scene information of the target two-wheeled vehicle includes: Obtain the vehicle status information and user behavior information of the target two-wheeled vehicle; The target scenario type of the target two-wheeled vehicle is determined based on the vehicle status information, the device status view, the wearing status, and the user behavior information. The scene information is determined based on the target scene type; The target scenario type includes at least one of the following: cycling scenario, parking scenario, incoming call scenario, navigation scenario, shooting scenario, music playback scenario, and abnormal alarm scenario.

5. The method according to claim 4, characterized in that, The step of determining multiple target tasks corresponding to the target business based on the business requirement information, and determining the task allocation result based on the scenario information, the device capability information, and the device status information, includes: Based on the business requirement information, determine the multiple target capabilities required for the target business; Based on the multiple target capabilities, the target service is divided into multiple target tasks corresponding to each of the target capabilities; Based on the target capabilities corresponding to each target task, the unified device capability pool, and the device status view, candidate devices corresponding to each target task are determined; Based on the scenario information, a target carrier device is determined from the candidate devices corresponding to each target task, and the task allocation result is determined based on the target carrier device corresponding to each target task.

6. The method according to claim 5, characterized in that, The step of determining the target carrier device from the candidate devices corresponding to each target task based on the scenario information includes: For any of the target tasks, the capability matching degree of each candidate device is determined based on the target capability corresponding to the target task and the device capability information of each candidate device. Based on the device capability information and device status information of each candidate device, determine the riding safety level, battery adequacy, power supply stability and online reliability of each candidate device; Based on the scenario information, determine the target weights corresponding to the capability matching degree, the riding safety level, the battery adequacy, the power supply stability, and the online reliability, respectively. Using the target weights, the capability matching degree, riding safety level, battery adequacy, power supply stability and online reliability of each candidate device are weighted and processed to determine the task adaptation score of each candidate device for the target task; Based on the task adaptation score of each candidate device, the target bearer device corresponding to the target task is determined from each candidate device.

7. The method according to claim 1, characterized in that, The process of synchronizing the service status of the target service among the multiple target devices includes: Based on the task allocation results, the participating devices and the service data to be synchronized are determined to execute the target service. Using a distributed data management mechanism, the business data to be synchronized and the business status are synchronized to each of the participating devices; Acquire user operation events generated by any of the participating devices; The service status is updated based on the user operation event, and the updated service status is sent to each of the participating devices.

8. The method according to claim 6, characterized in that, The step of determining the target weights corresponding to the capability matching degree, the riding safety level, the battery adequacy, the power supply stability, and the online reliability based on the scenario information includes: When the scene information represents a cycling scene, the target weight corresponding to the cycling safety level is determined as the maximum value among the target weights. Based on the task adaptation score of each candidate device, the display task is assigned to the vehicle system or the smart helmet, and the audio task is assigned to the smart helmet. When the scene information represents a parking scene, the target weight corresponding to the capability matching degree is determined as the maximum value among the target weights, and the interaction task is assigned to the mobile phone according to the task adaptation score of each candidate device.

9. The method according to claim 7, characterized in that, The step of updating the task allocation result in response to a change in the device state of any of the target devices includes: If any of the target devices is detected to be offline, the affected target tasks corresponding to the offline target devices are determined according to the task allocation results; Based on the equipment capability information and equipment status information of the remaining target equipment, determine the target replacement equipment corresponding to the affected target task; The affected target tasks are assigned to the target alternative devices, and the current business status is synchronized to the target alternative devices to obtain updated task assignment results; The vehicle-mounted system caches the service status changes of the offline target device during the offline period.

10. The method according to claim 9, characterized in that, The method further includes: In response to the offline target device coming back online, obtain the current device capability information and current device status information corresponding to the re-online target device; Based on the task allocation result, determine the original target task corresponding to the target device that is re-connected, and determine the task recovery result based on the current device capability information, the current device status information, and the original target task; If the task recovery result indicates that the re-connected target device can execute the original target task, the recovery service status is determined based on the service status change and the current service status. The restored service status is synchronized to the target device that has been brought back online, the original target task is reassigned to the target device that has been brought back online, and the original target task continues to be executed according to the restored service status.

11. The method according to claim 3, characterized in that, The method further includes: The vehicle-mounted system periodically sends heartbeat detection information to each of the target devices. Based on the heartbeat response information returned by each of the target devices, determine the current online status and capability changes of each of the target devices; Update the unified device capability pool and the device status view based on the current online status and the capability change information; Based on the updated unified device capability pool and device status view, the task allocation results are updated, and the multiple target devices are controlled to execute corresponding target tasks according to the updated task allocation results.

12. A multi-device collaborative device for a two-wheeled vehicle, characterized in that, include: The information acquisition module is used to acquire scene information of the target two-wheeled vehicle, business requirement information of the target business, and equipment capability information and equipment status information of multiple target devices; wherein, the multiple target devices include a vehicle-mounted unit and at least one collaborative device; The task allocation module is used to determine multiple target tasks corresponding to the target business based on the business requirement information, and to determine the task allocation results corresponding to the multiple target tasks based on the scenario information, the device capability information and the device status information. The status synchronization module is used to control the multiple target devices to execute corresponding target tasks according to the task allocation results, and to synchronize the service status of the target service among the multiple target devices; The task execution module is used to respond to a change in the device status of any of the target devices, update the task allocation result according to the changed device status information and the service status, and control the multiple target devices to execute the corresponding target tasks according to the updated task allocation result.

13. An electronic device, characterized in that, It includes a processor and a memory for storing processor-executable instructions, wherein the processor, when executing the instructions, implements the steps of the method according to any one of claims 1 to 11.

14. A computer-readable storage medium, characterized in that, It stores computer instructions that, when executed by a processor, implement the steps of the method according to any one of claims 1 to 11.

15. A computer program product, characterized in that, It includes a computer program that, when executed by a processor, implements the steps of the method according to any one of claims 1 to 11.

Images