Service connection methods, devices, storage media, software products and vehicles

By identifying relative movement trends between devices and currently running services, combined with user intent and historical habits, the problem of service continuity when switching between mobile phones and in-vehicle systems is solved, achieving seamless service switching and a consistent experience across different devices.

CN123124034APending Publication Date: 2026-11-17CHERY AUTOMOBILE CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202611478242.0
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2026-09-21
Publication Date
2026-11-17

AI Technical Summary

Technical Problem

When switching services between mobile phones and in-vehicle systems, it is difficult to maintain the continuity of service operation, which requires users to perform repeated operations inside or outside the vehicle, affecting the continuity and consistency of service experience in travel scenarios.

Method used

By identifying relative movement trends between devices and currently running services, the target service is determined and transferred from the first device to the second device through a service flow channel. Combined with the user's travel intentions and historical habits, the service is ensured to switch seamlessly between different devices.

Benefits of technology

It enables seamless service switching between devices, reduces repetitive user operations, and improves the continuity and consistency of services in travel scenarios.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123124034A_ABST
    Figure CN123124034A_ABST
Patent Text Reader

Abstract

This disclosure provides a service continuity method, apparatus, storage medium, program product, and vehicle, relating to the field of information processing technology. It addresses the problem of maintaining operational continuity after service switching in related technologies, improving the continuity and consistency of service continuity in travel scenarios. The method includes: determining a target service to be transferred in the first device based on the relative movement trend between a first device and a second device, and the current operating service of the first device; wherein the relative movement trend includes a moving away trend or an approaching trend; determining the service operation status of the target service; wherein the service operation status characterizes the operating progress and / or operating content of the target service on the first device; and transferring the target service and service operation status from the first device to the second device through a service transfer channel between the first and second devices, so that the second device can continue the target service on the second device based on the service operation status.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This disclosure relates to the field of information processing technology, and in particular to service connection methods, apparatus, storage media, program products, and vehicles. Background Technology

[0002] With the development of smart cockpit and vehicle networking technologies, interconnectivity between mobile phones and vehicle systems has become an important function of vehicle cabins. Users expect services such as audio playback, navigation, schedule reminders, and ticketing information on their mobile phones to continue seamlessly after entering the vehicle and remain available after exiting. Related technologies have enabled mobile phones and vehicle systems to establish communication connections and provide access to some services within the mobile phone ecosystem on the vehicle's side to meet in-vehicle information and entertainment needs.

[0003] However, when related technologies connect services between mobile phones and in-vehicle systems, the continuity of service operation after switching between different devices is often difficult to maintain. Users need to perform repetitive operations inside or outside the vehicle, resulting in service interruptions and affecting the continuity and consistency of the travel experience. Summary of the Invention

[0004] The embodiments disclosed herein provide a service continuity method, apparatus, storage medium, program product, and vehicle, which can solve the problem of difficulty in maintaining the continuity of operation after service switching in related technologies, and improve the continuity and consistency of service continuity in travel scenarios.

[0005] In a first aspect, this application provides a service continuity method, comprising: determining a target service to be transferred in the first device based on the relative movement trend between a first device and a second device, and the current operating service of the first device; wherein the relative movement trend includes a moving away trend or a moving towards trend; determining the service operation status of the target service; wherein the service operation status is used to characterize the operation progress and / or operation content of the target service on the first device; and transferring the target service and service operation status from the first device to the second device through a service transfer channel between the first device and the second device, so that the second device can continue the target service on the second device through the service operation status.

[0006] The service continuity method provided in this application can accurately identify the service object and timing that needs to be transferred based on the user's movement state as the first device approaches or moves away from the second device, combined with the service currently running on the first device. This avoids false triggering or omissions caused by relying solely on a single connection state. On this basis, the target service and service running state are transferred from the first device to the second device through the service transfer channel between the first and second devices. This allows the second device to continue the target service on the second device based on the service running state. This ensures that the service can continue execution from the original running progress and / or original running content after switching between different devices, without requiring the user to re-initiate or repeat operations. This solves the problem of maintaining the continuity of the running state after service switching in related technologies and improves the continuity and consistency of service continuity in travel scenarios.

[0007] In some possible implementations, where the first device is a user's mobile device and the second device is an in-vehicle device, the target service to be transferred in the first device is determined based on the relative movement trend between the first and second devices and the current operating service of the first device. This includes: if the relative movement trend is determined to be a proximity trend, determining the user's service continuation intention based on the current operating service, the user's travel intention, location information, and / or the user's set schedule information; and determining the target service from the transferable services of the first device based on the service continuation intention.

[0008] The service continuation method provided in this application can determine the service continuation intention by combining the currently running service, the user's travel intention, location information and / or the user's set schedule information when the mobile device approaches the vehicle device, and determine the target service from the transferable services of the mobile device based on the service continuation intention. This makes the determination of the target service more consistent with the user's actual travel intention and the current scenario, thereby improving the accuracy of service transfer between the mobile device and the vehicle device and reducing erroneous transfers.

[0009] In some possible implementations, the target service and service operation status are transferred from the first device to the second device through a service transfer channel between the first device and the second device, so that the second device can continue the target service on the second device based on the service operation status. This includes: determining the confidence level for continuing the target service based on target information; wherein the target information includes: the user's service transfer habits; and transferring the target service, service operation status, and confidence level from the first device to the second device, so that the second device can continue the target service based on the confidence level.

[0010] The service continuation method provided in this application can determine the confidence level of the target service based on target information including the user's service flow habits, and transfer the target service, service operation status and confidence level to the second device, so that the second device can continue the target service based on the confidence level. This introduces consideration of the user's historical habits into the service continuation process, reduces the risk of incorrect continuation, and improves the accuracy and reliability of service continuation.

[0011] In some possible implementations, the target information may further include at least one of the following: the usage status of the first device, the relative moving speed between the first device and the second device, and the trajectory stability between the first device and the second device; the usage status includes at least one of the following: whether the first device is in a call state, whether the first device is connected to other devices; the confidence level when the first device is in a call state is lower than the confidence level when the first device is in a call state; the confidence level when the first device is connected to other devices is lower than the confidence level when the first device is not connected to other devices; other devices are devices other than the second device.

[0012] The service connection method provided in this application can determine the confidence level by combining at least one of the usage status of the first device, relative movement speed, and trajectory stability. The confidence level is reduced when the first device is in a call or connected to another device, ensuring that the confidence level reflects whether the user is currently in a convenient position to connect and the authenticity of the approach behavior. Simultaneously, by considering relative movement speed, it can be determined whether the user is approaching the second device at a stable speed. The confidence level is reduced accordingly when the speed is too fast, too slow, or fluctuates significantly, thus ruling out situations where the user is merely passing by or has an unstable movement status. Furthermore, by considering trajectory stability, it can be determined whether the movement trajectory of the first device continuously points towards the second device. The confidence level is reduced accordingly when the trajectory frequently changes direction, stops, or deviates, thus ruling out situations where the user's intention is unclear. This avoids erroneous service connection triggering when the user is in a call, using other devices, has an unstable movement status, or an unclear trajectory, further reducing the risk of erroneous connection and improving the accuracy of service connection.

[0013] In some possible implementations, continuing the target service based on confidence level includes: continuing the target service on the second device based on the service running status when the confidence level is not lower than a first confidence level threshold; outputting confirmation information to the user when the confidence level is lower than the first confidence level threshold; and continuing the target service on the second device based on the service running status in response to the user's service continuation command.

[0014] The service continuation method provided in this application can execute different continuation strategies based on the comparison result between the confidence level and a first confidence threshold. When the confidence level is not lower than the first confidence threshold, it automatically continues the target service on the second device based on the service running status, ensuring continuity and a seamless experience in high-confidence scenarios. When the confidence level is lower than the first confidence threshold, it outputs confirmation information to the user and responds to the user's service continuation command before resuming the connection. This allows the user to confirm whether to continue the connection in low-confidence scenarios, thereby ensuring service continuity while avoiding erroneous connections in low-confidence scenarios. It balances automation and user control, improving the accuracy of service continuation and the user experience.

[0015] In some possible implementations, when the first device is an in-vehicle device and the second device is a user's mobile device, the target service to be transferred in the first device is determined based on the relative movement trend between the first device and the second device and the current running service of the first device. This includes: if the relative movement trend is determined to be a moving away trend, determining the user's service continuation intention based on the current running service; and determining the target service from the transferable services of the first device based on the service continuation intention.

[0016] The service continuation method provided in this application can determine the user's service continuation intention based on the current running service of the vehicle-mounted device when the first device is an in-vehicle device, the second device is a mobile device, and the relative movement trend is a moving away trend. Based on the service continuation intention, the target service is determined from the transferable services of the vehicle-mounted device. This allows unfinished services on the vehicle-mounted device to be accurately identified and transferred to the mobile device for continued execution after the user gets off the vehicle and moves away from the vehicle. This achieves reverse service continuation from the vehicle-mounted device to the mobile device, avoids service interruption due to the user leaving the vehicle, and improves the bidirectional continuity and consistency of service continuation in travel scenarios.

[0017] In some possible implementations, the service flow channel is a service synchronization channel that is independent of the media projection channel between the first device and the second device.

[0018] The service continuity method provided in this application can set the service flow channel as a service synchronization channel independent of the media projection channel, so that the transmission of the target service and the service operation status does not depend on the media projection channel. Thus, service flow can still be carried out when the media projection channel is not established, interrupted, or has limited resources, avoiding the restriction of service continuity on the media projection status and improving the independence and reliability of service continuity.

[0019] In some possible implementations, when the first device is a user's mobile device, the first device is determined as follows: at least one candidate mobile device connected to the second device is identified; for each candidate mobile device, a service flow priority is determined based on the vehicle cabin location corresponding to each mobile device; and the candidate mobile device with the highest service flow priority among the at least one candidate mobile devices is identified as the first device.

[0020] The service continuity method provided in this application can determine the service flow priority based on the vehicle cabin location corresponding to each candidate mobile device when multiple candidate mobile devices are connected to the second device, and determine the candidate mobile device with the highest priority as the first device. This allows the service flow to be initiated by the mobile device in the appropriate cabin location first, thereby avoiding service error flow when multiple mobile devices are online at the same time. It realizes accurate distribution of services in multi-device scenarios, improves the accuracy of service continuity and the travel experience of multiple passengers.

[0021] In some possible implementations, the method further includes: saving a copy of the target service's service operation state on the first device before transferring the target service and service operation state from the first device to the second device; and maintaining the target service's service operation state on the first device based on the copy of the service operation state if the connection between the first device and the second device is broken or the transfer of the target service and service operation state fails.

[0022] The service continuity method provided in this application enables the first device to save a copy of the service running state of the target service before service transfer, and to maintain the service running state of the target service on the first device based on the copy of the service running state when the connection is broken or the transfer fails. This allows the first device to retain the original service running state and continue execution even if the service transfer fails, avoiding loss of service running state, service interruption, or user reoperation due to connection breakage or transfer failure, thereby improving the reliability and continuity of service continuity.

[0023] Secondly, this application provides a service connection device, including: a determining module and a processing module; The determining module is used to determine the target service to be transferred in the first device based on the relative movement trend between the first device and the second device and the current running service of the first device; wherein the relative movement trend includes a moving away trend or a moving towards trend; the determining module is also used to determine the service running status of the target service; the processing module is used to transfer the target service and service running status from the first device to the second device through the service transfer channel between the first device and the second device, so that the second device can continue the target service on the second device through the service running status.

[0024] In some possible implementations, where the first device is a user's mobile device and the second device is an in-vehicle device, the determining module is specifically used to: determine the user's service continuation intention based on the currently running service, the user's travel intention, location information, and / or the user's set schedule information when the relative movement trend is determined to be a proximity trend; and determine the target service from the available services of the first device based on the service continuation intention.

[0025] In some possible implementations, the determining module is specifically used to: determine the confidence level of continuing the target service based on target information; wherein the target information includes: the user's service flow habits; and transfer the target service, service running status and confidence level from the first device to the second device, so that the second device continues the target service based on the confidence level.

[0026] In some possible implementations, the target information may further include at least one of the following: the usage status of the first device, the relative moving speed between the first device and the second device, and the trajectory stability between the first device and the second device; the usage status includes at least one of the following: whether the first device is in a call state, whether the first device is connected to other devices; the confidence level when the first device is in a call state is lower than the confidence level when the first device is in a call state; the confidence level when the first device is connected to other devices is lower than the confidence level when the first device is not connected to other devices; other devices are devices other than the second device.

[0027] In some possible implementations, the determining module is specifically configured to: continue the target service on the second device based on the service running status if the confidence level is not lower than a first confidence level threshold; output confirmation information to the user if the confidence level is lower than the first confidence level threshold; and continue the target service on the second device based on the service running status in response to the user's service continuation command.

[0028] In some possible implementations, where the first device is an in-vehicle device and the second device is a user's mobile device, the determining module is specifically used to: determine the user's service continuation intention based on the currently running service when the relative movement trend is determined to be a moving away trend; and determine the target service from the available services of the first device based on the service continuation intention.

[0029] In some possible implementations, the service flow channel is a service synchronization channel that is independent of the media projection channel between the first device and the second device.

[0030] In some possible implementations, when the first device is a user's mobile device, the determining module is further configured to: determine at least one candidate mobile device connected to the second device; for each candidate mobile device, determine the service flow priority of each candidate mobile device based on the vehicle cabin location corresponding to each mobile device; and determine the candidate mobile device with the highest service flow priority among the at least one candidate mobile devices as the first device.

[0031] In some possible implementations, the processing module is further configured to: save a copy of the target service's service running state on the first device before transferring the target service and service running state from the first device to the second device; and maintain the target service's service running state on the first device based on the copy of the service running state if the connection between the first device and the second device is broken or the transfer of the target service and service running state fails.

[0032] Thirdly, this application provides a control device, including: a memory and a processor; the memory and the processor are coupled; the memory is used to store a computer program; the processor executes the computer program to implement the service continuation method of any of the above embodiments.

[0033] Fourthly, this application provides a computer-readable storage medium storing computer program instructions that, when executed by a processor, implement the service continuation method of any of the above embodiments.

[0034] Fifthly, this application provides a computer program product including computer program instructions that, when executed by a processor, implement the service continuation method of any of the above embodiments.

[0035] Sixthly, this application provides a vehicle including the control device of any of the preceding embodiments; or the computer-readable storage medium of any of the preceding embodiments; or the computer program product of any of the preceding embodiments. Attached Figure Description

[0036] To more clearly illustrate the technical solutions in this disclosure, the accompanying drawings used in some embodiments of this disclosure will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this disclosure. For those skilled in the art, other drawings can be obtained based on these drawings.

[0037] Figure 1 A schematic diagram of the architecture of a service continuity system provided for some embodiments of this disclosure; Figure 2 A flowchart illustrating a service continuity method provided for some embodiments of this disclosure; Figure 3 A schematic diagram of the architecture of yet another service continuity system provided in some embodiments of this disclosure; Figure 4 A schematic diagram of the structure of a service connection device provided in some embodiments of this disclosure; Figure 5 This is a schematic diagram of the structure of a control device provided in some embodiments of this disclosure. Detailed Implementation

[0038] The technical solutions of this disclosure will now be clearly and completely described with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this disclosure, and not all embodiments. Based on the embodiments of this disclosure, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this disclosure.

[0039] It should be noted that, in this disclosure, the terms "exemplary" or "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design described as "exemplary" or "for example" in this disclosure should not be construed as being more preferred or advantageous than other embodiments or designs. Specifically, the use of terms such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner.

[0040] Hereinafter, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature.

[0041] In the description of this disclosure, unless otherwise stated, " / " means "or," for example, A / B can mean A or B. "And / or" in this document is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, and B alone. Furthermore, "at least one" means one or more, and "more than one" means two or more.

[0042] The technical solutions in the embodiments of this application will now be described with reference to the accompanying drawings.

[0043] See Figure 1 This is a schematic diagram of a service continuity system provided in an embodiment of this disclosure. Figure 1 As shown, the service continuity system includes: a service continuity device 101, a first device 102, and a second device 103. The service continuity device 101 is communicatively connected to the first device 102 and the second device 103, respectively.

[0044] It should be understood that the specific deployment method of the service connection device 101 is not limited in the embodiments of this application. The service connection device 101 may be an independent device or independent functional module deployed independently of the first device 102 and the second device 103, or it may be deployed inside the first device 102, inside the second device 103, or deployed in a distributed manner on both sides of the first device 102 and the second device 103. For ease of description, the following embodiments of this application use the deployment of the service connection device 101 independently of the first device 102 and the second device 103 as an example, but this does not constitute a limitation on the scope of protection of this application.

[0045] In this embodiment, the service connection device 101 and the first device 102 can communicate through various means, including but not limited to: Bluetooth (BT), Wireless Local Area Networks (WLAN), Near Field Communication (NFC), Universal Serial Bus (USB), and in-vehicle Ethernet, etc., wired or wireless connection methods. This embodiment does not limit the scope of these methods. The service connection device 101 and the second device 103 can communicate through various means, including but not limited to: Bluetooth, WLAN, Near Field Communication, cellular networks (such as 4G, 5G), and in-vehicle Ethernet, etc., this embodiment does not limit the scope of these methods. The first device 102 and the second device 103 can also establish a communication connection through the aforementioned wired or wireless methods, this embodiment does not limit the scope of these methods.

[0046] In some embodiments, the first device 102 may be a mobile device, such as a smartphone, tablet, wearable device, etc.; or it may be an in-vehicle device, such as an in-vehicle infotainment system, cockpit domain controller, etc. The second device 103 may be a different device from the first device 102. For example, when the first device 102 is a mobile device, the second device 103 may be an in-vehicle device; when the first device 102 is an in-vehicle device, the second device 103 may be a mobile device. This application embodiment does not limit the specific device form of the first device 102 and the second device 103.

[0047] In one possible implementation, in a service continuity scenario, the service continuity device 101 is configured to: determine the target service to be transferred in the first device 102 based on the relative movement trend between the first device 102 and the second device 103, and the currently running service of the first device 102; wherein the relative movement trend includes a moving away trend or a moving towards trend. Then, the service operation status of the target service is determined; wherein the service operation status characterizes the running progress and / or running content of the target service on the first device 102. Subsequently, through the service flow channel between the first device 102 and the second device 103, the target service and its service operation status are transferred from the first device 102 to the second device 103, so that the second device 103 can continue the target service on the second device 103 based on the service operation status.

[0048] The relative movement trend can be determined based on the change in the relative distance between the first device 102 and the second device 103. For example, a decreasing distance between them indicates a trend of approaching each other, while an increasing distance indicates a trend of moving away from each other. The currently running service can be a service that is running or active on the first device 102, such as an audio playback service, a navigation service, or a ticketing information service. The service transfer channel can be a communication channel between the first device 102 and the second device 103 used to transmit the target service and its operational status. This channel can reuse an existing connection between the first device 102 and the second device 103 or be established independently. The service operational status can include, but is not limited to, at least one of the following: audio playback progress, media identifier, remaining navigation route, estimated arrival time, and ticketing information, so that the second device 103 can locally resume and continue executing the same target service based on the service operational status.

[0049] It should be pointed out that, Figure 1 The structure shown does not constitute a limitation on the service continuity system, which may include fewer or more components than shown, or combine certain components, or have different component arrangements. This application embodiment does not impose any limitations in this regard.

[0050] The service continuation method provided in this application embodiment can be applied to... Figure 1 In the service connection device 101 shown, such as in the controller of the service connection device 101; it can also be applied to Figure 1 In the first device 102 shown, such as the controller of the first device 102; some functions may be deployed in the first device 102 and some functions may be deployed in the second device 103, and this application embodiment does not limit this. In this application embodiment, for ease of description, the service continuity method is applied to Figure 1 The service connection device 101 shown is used as an example for illustration, but this does not constitute a limitation on the scope of protection of this application.

[0051] It is understood that the application scenarios of the embodiments of this disclosure are not limited. The system architecture and business scenarios described in the embodiments of this disclosure are for the purpose of more clearly illustrating the technical solutions of the embodiments of this disclosure, and do not constitute a limitation on the technical solutions provided by the embodiments of this disclosure. As those skilled in the art will know, with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided by the embodiments of this disclosure are also applicable to similar technical problems.

[0052] The service continuation method provided in the embodiments of this disclosure will be described in detail below.

[0053] This disclosure provides a service continuity method, such as Figure 2 As shown, the method includes the following steps: S201. Based on the relative movement trend between the first device and the second device, and the current operating service of the first device, determine the target service to be transferred in the first device.

[0054] Relative movement trends include those that move away from or near the trend.

[0055] In one possible implementation, the first device and the second device can establish a communication connection via Bluetooth, Wi-Fi, NFC, SATA, or vehicular Ethernet. The relative movement trend between the first and second devices can be determined based on changes in their relative distance. For example, if the distance between the first and second devices gradually decreases, the relative movement trend is determined to be an approaching trend, indicating that the user carrying the first device is approaching the second device, or vice versa. If the distance between the first and second devices gradually increases, the relative movement trend is determined to be a moving away trend, indicating that the user carrying the first device is moving away from the second device.

[0056] Optionally, the relative distance change can be determined based on at least one of the following methods: Bluetooth signal strength, Ultra Wideband (UWB) ranging, Global Navigation Satellite System (GNSS) location information, etc. This application embodiment does not limit this.

[0057] S202. Determine the service operation status of the target service.

[0058] Among them, the service operation status is used to characterize the running progress and / or running content of the target service on the first device.

[0059] For example, for an audio playback service, the service running status may include playback progress, playlist, volume, loop mode, etc.; for a navigation service, the service running status may include waypoint sequence, current remaining path, estimated arrival time, real-time traffic information, etc.; for a ticketing information card service, the service running status may include ticket type (movie / restaurant), order number, QR code information, venue information, time, etc. This allows the second device to locally resume and continue executing the same target service based on the service running status.

[0060] S203. The target service and service operation status are transferred from the first device to the second device through the service transfer channel between the first device and the second device, so that the second device can continue the target service on the second device through the service operation status.

[0061] The service transfer channel can be a communication channel between the first device and the second device used to transmit the target service and the service operation status.

[0062] In one possible implementation, the service transfer channel is a service synchronization channel independent of the media projection channel between the first and second devices. The service transfer channel can reuse existing connections between the first and second devices, such as Bluetooth or Wi-Fi connections, or it can be established independently. This application does not limit the specific form of the service transfer channel.

[0063] For example, to enable service transfer between the first device and the second device, a deep service fusion framework can be pre-established between them. This deep service fusion framework differs from simple audio / video streaming; it defines a unified service description protocol and service transfer channel to support cross-device state synchronization and task takeover at the "service" level.

[0064] Specifically, the service description protocol is defined based on a lightweight structured data format, such as JSON Schema (JavaScript Object Notation Schema) or Protocol Buffers (protobuf). Each flowable service is abstracted as a service descriptor, and the data structure of the service descriptor contains at least the following fields: (1) A globally unique identifier for a service (service_id), for example, “audio_playback” represents the audio playback service and “navigation_task” represents the navigation task; (2) Service running status (service_state), for example, for an audio playback service, its status can be {"playback_status": "playing", "current_position_ms": 45000, "media_id": "song_123"}, where "playback_status" indicates the playback status, "playing" indicates that it is playing, "current_position_ms" indicates the current playback position in milliseconds, and "media_id" indicates the media identifier; (3) A list of device capabilities required to perform the service, such as {"high_quality_audio_output", "large_screen_display"}, where "high_quality_audio_output" represents high-quality audio output capability and "large_screen_display" represents large screen display capability; (4) The ownership context to which the service belongs, such as the associated user account and device identifier.

[0065] The service flow channel is independent of the media projection channel between the first and second devices. After the first and second devices establish a connection, such as via Bluetooth, Wi-Fi Direct, or cellular network, an additional low-latency, highly reliable bidirectional control channel, namely the service flow channel, is established in addition to the traditional media projection channel. This service flow channel can be established based on network sockets or a custom Transmission Control Protocol / User Datagram Protocol (TCP / UDP) for real-time synchronization of service descriptors between the two parties; transmission of context data required by the context-aware engine, such as the service running status on the first device, signal commands on the second device, and control commands for sending service flow (e.g., "takeover request" or "state synchronization").

[0066] Additionally, a service fusion proxy can be implemented at the operating system level of both the first and second devices. The service fusion proxy provides standardized Application Programming Interfaces (APIs) for upper-layer applications to call. Key interfaces include: `registerService(descriptor)`, used by an application to register its transferable services with the framework; `updateServiceState(service_id, new_state)`, used to update the state of the local service and automatically notify the peer via a bidirectional state synchronization channel; and `requestHandover(target_device, service_id)`, used to actively request the transfer of a specified service to the target device. Through the service fusion proxy, the first and second devices can perform state synchronization, task takeover, and resource coordination on a service-by-service basis.

[0067] In one possible implementation, after receiving the target service and its operational status through the service flow channel, the second device can continue the target service on the second device based on the operational status. For example, if the target service is an audio playback service, the second device can resume playback from the exact position where it stopped on the first device, based on the audio playback progress and media identifier; if the target service is a navigation service, the second device can continue performing the navigation task on the second device based on the remaining part of the navigation route and the estimated arrival time. This achieves seamless service continuity from the first device to the second device.

[0068] In one possible implementation, before transferring the target service and its service state from the first device to the second device, the service connection device can save a copy of the target service's service state on the first device; if the connection between the first device and the second device is broken, or if the transfer of the target service and its service state fails, the service state of the target service on the first device is maintained based on the copy of the service state.

[0069] For example, in response to potential anomalies such as connection drops or service failures during service transitions, the service continuity device can perform corresponding exception handling based on different anomaly types. For instance, in the event of a network interruption, the first device, acting as the source device, can retain a copy of the service's running state and attempt to retransmit the target service and its running state. If retransmission fails after three attempts, the local playback or navigation state on the first device remains unchanged. In the event of a second device crash and restart, the second device can proactively request the most recent service_state from the mobile phone after recovery to attempt service restoration. In the event of a disconnection by the first device, the second device can take over and operate independently. If the first and second devices reconnect subsequently, the latest state will be synchronized back to the first device. This ensures that services are not lost, achieving a truly seamless transition experience.

[0070] Based on the above technical solution, this application can accurately identify the service object and timing that needs to be transferred based on the user's movement state as the first device approaches or moves away from the second device, combined with the service currently running on the first device, thus avoiding false triggering or omissions caused by relying solely on a single connection state. On this basis, through the service transfer channel between the first and second devices, the target service and service operation state are transferred from the first device to the second device, so that the second device can continue the target service on the second device through the service operation state. This allows the service to continue execution from the original running progress and / or original running content after switching between different devices, without requiring the user to re-initiate or repeat the operation, thereby solving the problem of difficulty in maintaining the continuity of the running state after service switching in related technologies, and improving the continuity and consistency of service connection in travel scenarios.

[0071] In some embodiments, where the first device is a user's mobile device and the second device is an in-vehicle infotainment system, in order to determine the target service to be transferred in the first device, the embodiments of this application provide the following steps: S301. If the relative movement trend is determined to be a convergence trend, the user's service continuity intention is determined based on the currently running service, the user's travel intention, location information and / or the user's set schedule information.

[0072] The user's travel intent reflects their desired destination or purpose of travel, such as going to work, shopping mall, or home. The service continuation device can determine the travel intent based on information such as navigation destination, calendar events, and historical travel patterns on the first device. Location information reflects the current location of the first device. User-set schedule information reflects events pre-set by the user in applications such as calendars and memos, including event time, location, and type (e.g., meeting, dinner, movie). With user authorization, the service continuation device can access calendar, memos, and other applications on the first device to obtain schedule information. Service continuation intent indicates the user's intention to continue using services running or pending on the first device on the second device, such as continuing to listen to audio, continuing navigation, or checking tickets.

[0073] In one possible implementation, the service connection device can store a rule mapping library of scenarios, intents, and actions. The service connection device can match the currently running service, travel intent, location information, and schedule information with the scenarios in the rule mapping library to obtain the corresponding service connection intent.

[0074] In another possible implementation, the service connection device can be deployed with a lightweight machine learning model. The service connection device can input the currently running service, the user's travel intention, location information, and / or the user's set schedule information into the lightweight machine learning model for feature extraction and probabilistic prediction to obtain the service connection intention. This application does not limit the specific method for determining the service connection intention.

[0075] For example, if the relative movement trend is approaching, the currently running service is an audio playback service, the travel intention is to go to the company, and the schedule information shows a meeting at 9:00 AM, the service continuity device determines that the service continuity intention is to continue playing audio on the second device and continue navigation to the company. As another example, if the relative movement trend is approaching, the currently running service is a navigation service, the location information shows the user is near a shopping mall, and the schedule information shows a dinner appointment, the service continuity device determines that the service continuity intention is to continue navigation on the second device and check the restaurant's waiting list information upon arrival.

[0076] S302 determines the target service from the available services of the first device based on the service continuation intent.

[0077] Among them, transferable services can be used to represent services that have been registered with the service connection device and the second device has connection capabilities.

[0078] In one possible implementation, the service connection device can match the service connection intent with the service identifier of a service that can be transferred on the first device.

[0079] For example, if the service continuation intent is "continue listening to audio", the service with the service identifier "audio_playback" will be matched; if the service continuation intent is "continue navigation", the service with the service identifier "navigation_task" will be matched; if the service continuation intent is "view queue numbers", the service with the service identifier "ticket_info" will be matched. The successfully matched and transferable service is determined as the target service.

[0080] Based on the above technical solution, this application can determine the service continuation intention by combining the currently running service, the user's travel intention, location information and / or the user's set schedule information when the mobile device approaches the vehicle-mounted device, and determine the target service from the transferable services of the mobile device based on the service continuation intention. This makes the determination of the target service more consistent with the user's actual travel intention and the current scenario, thereby improving the accuracy of service transfer between the mobile device and the vehicle-mounted device and reducing erroneous transfers.

[0081] In some embodiments, where the first device is a user's mobile device and the second device is an in-vehicle infotainment system, in order to enable the second device to continue the target service on the second device based on the service running state, the service continuation method provided in this application includes the following steps: S401. Based on the target information, determine the confidence level of the target service to be continued.

[0082] The target information includes users' service flow habits. These habits can include whether users historically transfer services such as audio and navigation from their phones to the vehicle's infotainment system when approaching a vehicle, and what types of services they typically use. The service connection device can learn these service flow habits by studying historical data.

[0083] In one possible implementation, the service connection device can count the number of historical transfers and the total number of triggers of the target service from the first device to the second device under the same or similar circumstances within a historical time period, and use the ratio of the two as the confidence level. This application does not impose specific limitations on this.

[0084] For example, if in the historical records, a user's phone was playing audio 10 times when they approached the vehicle, and the audio was transferred to the vehicle's infotainment system 8 times, then the confidence level of the service connection device in determining the audio playback service is 0.8; if the historical transfer count is 2 times and the total number of triggers is 10 times, then the confidence level is 0.2.

[0085] Optionally, the service connection device can also weight historical records according to their time proximity, with historical records more recent than the current time having a higher weight. This application embodiment does not limit the statistical window, the source of historical data, or the specific calculation method.

[0086] In one possible implementation, the target information further includes at least one of the following: the usage status of the first device, the relative moving speed between the first device and the second device, and the trajectory stability between the first device and the second device. The usage status includes at least one of the following: whether the first device is in a call state, and whether the first device is connected to other devices. The confidence level when the first device is in a call state is lower than the confidence level when the first device is connected to other devices is lower than the confidence level when the first device is not connected to other devices; other devices refer to devices other than the second device.

[0087] Understandably, the usage status of the first device reflects whether it is convenient for the user to continue the target service. For example, if the user is on a call or wearing headphones, automatically continuing audio playback may interrupt the user's current activity or cause audio output conflicts. Relative movement speed reflects the authenticity and urgency of the user's approach to the second device. For example, a user approaching a vehicle at a steady pace usually indicates that they are about to board, while excessively fast, slow, or frequently fluctuating speeds may indicate that the user is merely passing by or has unclear intentions. Trajectory stability reflects whether the user's movement direction is clearly directed towards the second device; a stable trajectory usually indicates a clearer user intention, while frequent changes in trajectory or deviations increase the risk of false triggering. Therefore, by comprehensively considering the above information to determine the confidence level, the service connection device can reduce the probability of false triggering and improve the accuracy of service connection.

[0088] In one possible implementation, the service connection device can determine the confidence components corresponding to the above information items separately, and then perform weighted fusion of the confidence components to obtain the final confidence level.

[0089] In another possible implementation, the target information may also include at least one of the following: vehicle status, such as speed, gear, door open / closed status, whether the vehicle is powered on, and whether the driver's door is open; the urgency of the user-set schedule information, such as the time remaining until the meeting starts; the destination type corresponding to the target service, such as a company, shopping mall, or restaurant; whether the second device has the necessary equipment capabilities to execute the target service; user confirmation or cancellation records for previous service connections; the network quality between the first and second devices; and whether the first device is a driver's seat device.

[0090] Therefore, it is possible to further determine whether the user actually needs to continue the target service, thereby improving the success rate of connection while reducing the probability of false triggering. For example, if the second device is not currently in park or the speed is high, it indicates that the user may not be ready to get in the car, and the service connection device can reduce the confidence level; if the user has canceled audio connection multiple times in the past, the service connection device can reduce the confidence level of the audio playback service; if the target service is navigation service and the schedule shows that the user will be late, the service connection device can increase the confidence level of the navigation service. This application embodiment does not impose any limitations on this.

[0091] S402, Transfer the target service, service operation status and confidence level from the first device to the second device, so that the second device can continue the target service based on the confidence level.

[0092] In one possible implementation, in order to continue the target service based on confidence level, the service continuation device can continue the target service on the second device based on the service running state if the confidence level is not lower than a first confidence level threshold; or, if the confidence level is lower than the first confidence level threshold, it can output confirmation information to the user, thereby responding to the user's service continuation command and continuing the target service on the second device based on the service running state.

[0093] In another possible implementation, the service connection device can output a confirmation message to the user and, in response to the user's service connection command, connect the target service on the second device based on the service running status if the confidence level is below a first confidence threshold but above a second confidence threshold. If no service connection command is received or a cancellation command is received, the target service is not connected. If the confidence level is not higher than the second confidence threshold, the service connection device does not trigger service transition, but only records the current context for subsequent analysis.

[0094] Optionally, the first confidence threshold and the second confidence threshold can be set according to actual needs. For example, when the confidence level is between 0 and 1, the first confidence threshold can be 0.8 and the second confidence threshold can be 0.5. This application does not impose specific limitations on this.

[0095] For example, when the confidence level is between 0.5 and 0.8, the service continuation device can push a notification to the first or second device: "We have detected that you are about to board the vehicle. Do you wish to continue playing the music?", allowing users to confirm or cancel with one click. When the confidence level is below 0.5, no transition is triggered; only the context is recorded for subsequent analysis. This application does not impose specific restrictions on this.

[0096] Based on the above technical solution, this application can determine the confidence level of the target service based on target information containing the user's service flow habits, and transfer the target service, service operation status and confidence level to the second device, so that the second device can continue the target service based on the confidence level. This introduces consideration of the user's historical habits in the service continuation process, reduces the risk of incorrect continuation, and improves the accuracy and reliability of service continuation.

[0097] In some embodiments, where the first device is an in-vehicle infotainment system and the second device is a user's mobile device, in order to determine the target service to be transferred in the first device, the service continuation method provided in this application embodiment further includes the following steps: S501. If the relative movement trend is determined to be a moving away trend, determine the user's service continuation intention based on the currently running service.

[0098] The currently running services are those that are running or active on the vehicle's infotainment system, such as audio playback and navigation services.

[0099] In one possible implementation, when the relative movement trend is a moving-away trend, it indicates that the user is moving away from the vehicle's infotainment system with their mobile device, meaning the user may be getting out of the vehicle or has already gotten out. In this case, the service continuity device can determine the user's intention to continue using the service on their mobile device based on the service currently running on the vehicle's infotainment system.

[0100] For example, if the vehicle's infotainment system is currently playing audio and the user gets out of the vehicle with a mobile device, the service continuity device determines that the service continuity intention is to continue playing the audio on the mobile device; or, if the vehicle's infotainment system is currently performing a navigation task and the vehicle has reached the vicinity of the destination, and the user may continue walking after getting out of the vehicle, the service continuity device determines that the service continuity intention is to continue navigating the remaining route on the mobile device.

[0101] S502. Based on the service continuation intent, determine the target service from the transferable services of the first device.

[0102] For example, the service connection device matches the service connection intent with the service identifier of the transferable service on the vehicle's infotainment system, and determines the successfully matched transferable service as the target service. For instance, when the service connection intent is "continue playing audio", the audio playback service with the service identifier "audio_playback" is matched; when the service connection intent is "continue navigation", the navigation service with the service identifier "navigation_task" is matched.

[0103] Based on the above technical solution, this application can determine the user's service continuation intention based on the current running service of the vehicle-mounted device when the first device is an in-vehicle device, the second device is a mobile device, and the relative movement trend is a moving away trend. Based on the service continuation intention, the target service is determined from the transferable services of the vehicle-mounted device. This allows the unfinished services on the vehicle-mounted device to be accurately identified and transferred to the mobile device for continued execution after the user gets off the vehicle and moves away from the vehicle. This achieves reverse service continuation from the vehicle-mounted device to the mobile device, avoids service interruption due to the user leaving the vehicle, and improves the bidirectional continuity and consistency of service continuation in travel scenarios.

[0104] In some embodiments, where the first device is a user's mobile device, multiple candidate mobile devices may simultaneously connect to the second device. To determine the first device from among the multiple candidate mobile devices, the service connection method provided in this application embodiment further includes the following steps: S601, Determine at least one candidate mobile device connected to the second device.

[0105] In one possible implementation, when one or more users bring one or more mobile devices into the vicinity of a vehicle, a second device (e.g., an in-vehicle infotainment system) can discover and connect to one or more candidate mobile devices via Bluetooth, Wi-Fi, NFC, or UPS. The service connection device obtains a list of candidate mobile devices currently connected to the second device, thus identifying at least one candidate mobile device.

[0106] For example, there may be multiple candidate mobile devices in the car at the same time, such as the driver's mobile phone, the front passenger's mobile phone, and the rear passenger's tablet computer.

[0107] S602. For each of the at least one candidate mobile devices, the service connection device determines the service flow priority of each candidate mobile device based on the vehicle cabin location corresponding to each candidate mobile device.

[0108] For example, the service connection device can determine the vehicle cabin location corresponding to each candidate mobile device through methods such as UWB precise positioning, login account matching, manual selection of preferences, or Bluetooth signal strength gradient analysis.

[0109] For example, the service connection device can determine whether a candidate mobile device is located in the driver's seat, passenger seat, or rear seat using UWB anchor points; it can match the user ID bound to the driver's seat with the login account of the candidate mobile device; it can prompt the user to select "Who owns this phone?" during the initial connection and remember the user's selection; it can also analyze the approximate location of the candidate mobile device by the difference in Bluetooth signal strength of multiple antennas. After determining the location in the vehicle cabin, the service connection device determines the service flow priority for each candidate mobile device according to the preset device role priority.

[0110] Optionally, the service flow priority of candidate mobile devices located in the driver's seat is the highest, while the service flow priority of candidate mobile devices located in the front passenger seat or rear seat is lower; the current driver's seat phone has the highest permissions, while the front passenger seat or rear seat devices have medium permissions. If only one candidate mobile device is connected to the second device, the service connection device can directly identify that candidate mobile device as the first device. This application does not impose specific restrictions in this regard.

[0111] S603, the service continuity device determines the candidate mobile device with the highest service flow priority among at least one candidate mobile device as the first device.

[0112] In one possible implementation, the service continuity device can compare the service flow priorities of multiple candidate mobile devices and determine the candidate mobile device with the highest service flow priority as the first device. Therefore, when multiple mobile devices are online simultaneously, only the first device with the highest priority triggers automatic service flow, while the other candidate mobile devices need to manually request service flow, thus avoiding incorrect service flow between multiple mobile devices and achieving accurate service distribution.

[0113] For example, when both the driver's and passenger's mobile phones are connected to the vehicle's infotainment system, the service continuity device will identify the driver's phone as the primary device, and only the driver's phone will trigger automatic service flow. The passenger's phone can push service information to the passenger's screen via a "recommendation stream," but it cannot forcibly interrupt the driver's service.

[0114] In some embodiments, such as Figure 3 As shown, Figure 3 The service continuity system in the system includes a user and device layer, a core service layer, and a hardware resource layer.

[0115] The user and device layer includes a first device, a second device, and a user identity and account center. In this embodiment, the first device can be a mobile terminal, and the second device can be an in-vehicle terminal. In other embodiments, the first device can also be an in-vehicle terminal, and the second device can be a mobile terminal; this application does not impose any restrictions on this.

[0116] In one possible implementation, the user identity and account center can be used to identify the user's identity and thereby determine the first device and / or the second device. For example, the user identity and account center can identify the driver user through account login, thereby identifying the driver user's mobile terminal as the first device and the vehicle terminal as the second device.

[0117] The core service layer includes a context-aware engine, a unified service runtime status management module, a service flow scheduling module, and a service flow channel. The context-aware engine determines the target service to be flowed from the first device based on the relative movement trend between the first and second devices and the currently running service on the first device. The service flow scheduling module transfers the target service and its runtime status from the first device to the second device via the service flow channel between the first and second devices, allowing the second device to continue the target service based on its runtime status. The service flow channel provides encrypted, low-latency transmission and is independent of the media projection channel between the first and second devices.

[0118] The hardware resource layer includes vehicle sensors, mobile device hardware, and in-vehicle infotainment hardware. Vehicle sensors provide the context perception engine with vehicle status information, such as speed, gear position, and door opening / closing status, to help determine the relative movement trend between the first and second devices and the current services being provided by the first device. In-vehicle infotainment hardware may include a large in-vehicle screen, audio system, computing unit, and Global Positioning System (GPS), providing hardware support for the in-vehicle infotainment device to connect to target services. Mobile device hardware may include a positioning module, storage module, and microphone, providing positioning, storage, and voice input support for the first device, and transmitting encrypted, low-latency data to the core service layer via a service flow channel.

[0119] It should be pointed out that, Figure 3 The structure shown does not constitute a limitation on the service continuity system, which may include fewer or more components than shown, or combine certain components, or have different component arrangements. This application embodiment does not impose any limitations in this regard.

[0120] For example, the service flow is illustrated by taking a mobile device as the first device and an in-vehicle device as the second device.

[0121] At time T1, the audio playback service and / or navigation service is running on the mobile device (the first device).

[0122] At time T2, the user approaches the vehicle (second device) with their mobile device. At this time, the relative movement trend between the first device and the second device is a convergence trend.

[0123] At time T3, the context-aware engine detects the user's intention to board the vehicle and triggers preloading. Specifically, based on the relative movement trend (proximity trend) between the first and second devices and the currently running services of the first device (audio playback service and / or navigation service), the context-aware engine determines the target service to be transferred in the first device and determines the service running status of the target service. The service running status is used to characterize the running progress and / or running content of the target service on the first device, such as audio playback progress, media identifier, remaining part of the navigation route, etc.

[0124] At time T4, the service transfer module synchronizes the service running status of the target service to the second device through the service transfer channel between the first and second devices, making the resources of the second device ready. Specifically, the service transfer module transfers the target service and its running status from the first device to the second device, and the second device performs resource preloading and status preparation based on the service running status.

[0125] At time T5, after the user boards the vehicle, the second device automatically resumes the target service based on the service's running status. For example, the in-vehicle system automatically resumes audio playback from the exact location where the mobile device stopped, or automatically displays a prepared navigation route. No manual operation from the user is required throughout the entire process.

[0126] At time T6, while the vehicle is in motion, the service flow module can push scenario-based services to the second device through the service flow channel, such as traffic information, schedule reminders, and nearby services. These pushes can be determined based on the service operation status and scenario information synchronized between the first and second devices.

[0127] At time T7, the user arrives at their destination, gets off the vehicle, and moves away from it. At this point, the relative movement trend between the first and second devices changes to a moving-away trend.

[0128] At time T8, the context-aware engine detects the intention to disembark and triggers the disembarkation and rerouting strategy. Specifically, based on the relative movement trend (movement away trend) between the first and second devices and the current running services of the second device, the context-aware engine determines the target service to be transferred in the second device and determines its service running status.

[0129] At time T9, the service transfer module transfers the target service and its running status from the second device back to the mobile device (first device) through the service transfer channel, enabling the first device to seamlessly take over unfinished services. For example, the mobile device can take over unfinished audio or continue navigating the remaining walking path.

[0130] In some embodiments, the service transfer is illustrated using a mobile device as the first device and an in-vehicle device as the second device. The service continuity method provided in this application includes the following steps: S701, Service continuity device acquires scenario information.

[0131] S702, The service continuity device determines the user's service continuity intention based on contextual information and through a user intention prediction algorithm.

[0132] In one possible implementation, the service continuity device can align and extract features from multiple collected contextual information sets within a time window, forming a unified contextual feature vector. Then, the service continuity device categorizes the current moment into a predefined scenario (e.g., "the user walks towards a parked vehicle with their phone," "the vehicle speeds towards a shopping district-type destination," "the vehicle has stopped and the driver's side door is open"), and based on the scenario and historical habits, infers the user's most likely service continuity intention (e.g., continuing audio playback, continuing navigation, checking tickets, etc.).

[0133] S703, The service continuity device performs rule matching based on the service continuity intent to determine the current stage.

[0134] In one possible implementation, the service connection device matches the current scenario against a preset rule base and performs the following judgments in sequence: Determine whether the relative movement trend between the first device and the second device is a convergence trend. If so, the service continuity device determines the target service to be transferred in the first device based on the current operating service of the first device, and determines the service operation status of the target service, so that the second device can prepare resources.

[0135] Determine if the user has boarded the vehicle. The service connection device can determine whether the user has boarded the vehicle based on the vehicle status (such as door opening, seat sensors, etc.). If so, the service connection device transfers the target service and service operation status from the first device to the second device through the service transfer channel between the first and second devices, so that the second device can continue the target service on the second device based on the service operation status.

[0136] Determine if the vehicle is in motion. The service connection device can determine whether the vehicle is in motion based on its status (such as speed greater than zero). If so, the service connection device can push scene services to the second device, such as traffic information, schedule reminders, and nearby services.

[0137] Determine whether the relative movement trend between the first device and the second device is a moving away trend. If so, the service continuity device determines the target service to be transferred in the second device and its service operation status based on the current operating service of the second device, and transfers it back to the first device (mobile device) through the service transfer channel, so that the first device can continue the target service through the service operation status.

[0138] If none of the above conditions are met, the service connection device continues to acquire scenario information and makes the next round of decisions.

[0139] S704. The service connection device performs the corresponding operation based on the judgment result.

[0140] Specifically, the service connection device can perform at least one of the following operations: This allows the second device to prepare resources. When the relative movement trend is determined to be a convergence trend, it instructs the second device to preload frequently used service resources, such as frequently listened podcast episodes and high-frequency navigation start points, to reduce waiting time during subsequent transitions.

[0141] This transfers the target service and its operational status from the first device to the second device. It is used to enable the second device to continue providing the target service based on the service's operational status once it is determined that a user has boarded the vehicle.

[0142] Push scene services to the second device. Used to push scene service information such as traffic conditions, schedule, and surroundings to the second device when it is determined that the vehicle is in motion.

[0143] The target service and service operation status are transferred from the second device back to the first device. This is used to enable the first device to continue the target service through the service operation status when the relative movement trend is determined to be a moving away trend.

[0144] After the corresponding operation is completed, the process ends.

[0145] The foregoing primarily describes the solutions of the embodiments of this disclosure from a methodological perspective. It is understood that, in order to achieve the aforementioned functions, the service connection device includes at least one of the hardware structures and software modules corresponding to the execution of each function. Those skilled in the art should readily recognize that, in conjunction with the units and algorithm steps of the various examples described in the embodiments disclosed herein, the embodiments of this disclosure can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of the embodiments of this disclosure.

[0146] This disclosure embodiment can divide the service connection device into functional modules according to the above method embodiment. For example, each function can be divided into a separate functional module, or two or more functions can be integrated into one functional module. The integrated module can be implemented in hardware or software. It should be noted that the module division in this disclosure embodiment is illustrative and only represents one logical functional division. In actual implementation, there may be other division methods. The following description uses the example of dividing each function into a separate functional module.

[0147] Figure 4 This is a schematic diagram of a service connection device provided in an embodiment of this disclosure. This service connection device can execute the service connection method provided in the above-described method embodiments. Figure 4 As shown, the service connection device 800 includes: a determination module 801 and a processing module 802.

[0148] In some possible implementations, the determining module 801 is used to determine the target service to be transferred in the first device based on the relative movement trend between the first device and the second device and the current operating service of the first device; wherein the relative movement trend includes a moving away trend or a moving towards trend; the determining module 801 is also used to determine the service operation status of the target service; the processing module 802 is used to transfer the target service and service operation status from the first device to the second device through the service transfer channel between the first device and the second device, so that the second device can continue the target service on the second device through the service operation status.

[0149] In some possible implementations, where the first device is a user's mobile device and the second device is an in-vehicle device, the determining module 801 is specifically used to: determine the user's service continuation intention based on the currently running service, the user's travel intention, location information and / or the user's set schedule information when the relative movement trend is determined to be a proximity trend; and determine the target service from the available services of the first device based on the service continuation intention.

[0150] In some possible implementations, the determining module 801 is specifically used to: determine the confidence level of continuing the target service based on the target information; wherein the target information includes: the user's service flow habits; and transfer the target service, service running status and confidence level from the first device to the second device, so that the second device continues the target service based on the confidence level.

[0151] In some possible implementations, the target information may further include at least one of the following: the usage status of the first device, the relative moving speed between the first device and the second device, and the trajectory stability between the first device and the second device; the usage status includes at least one of the following: whether the first device is in a call state, whether the first device is connected to other devices; the confidence level when the first device is in a call state is lower than the confidence level when the first device is in a call state; the confidence level when the first device is connected to other devices is lower than the confidence level when the first device is not connected to other devices; other devices are devices other than the second device.

[0152] In some possible implementations, the determining module 801 is specifically configured to: continue the target service on the second device based on the service running status when the confidence level is not lower than the first confidence level threshold; output confirmation information to the user when the confidence level is lower than the first confidence level threshold; and continue the target service on the second device based on the service running status in response to the user's service continuation instruction.

[0153] In some possible implementations, where the first device is an in-vehicle device and the second device is a user's mobile device, the determining module 801 is specifically used to: determine the user's service continuation intention based on the currently running service when the relative movement trend is determined to be a moving away trend; and determine the target service from the available services of the first device based on the service continuation intention.

[0154] In some possible implementations, the service flow channel is a service synchronization channel that is independent of the media projection channel between the first device and the second device.

[0155] In some possible implementations, when the first device is a user's mobile device, the determining module 801 is further configured to: determine at least one candidate mobile device connected to the second device; for each candidate mobile device, determine the service flow priority of each candidate mobile device based on the vehicle cabin location corresponding to each mobile device; and determine the candidate mobile device with the highest service flow priority among the at least one candidate mobile devices as the first device.

[0156] In some possible implementations, the processing module 802 is further configured to: save a copy of the target service's service running state on the first device before transferring the target service and service running state from the first device to the second device; and maintain the target service's service running state on the first device based on the copy of the service running state if the connection between the first device and the second device is broken or the transfer of the target service and service running state fails.

[0157] When implementing the functions of the integrated modules described above in hardware, this disclosure provides a possible structure for the control device involved in the above embodiments. For example... Figure 5 As shown, the control device 900 includes a processor 902 and a bus 904. Optionally, the control device may also include a memory 901; optionally, the control device 900 may also include a communication interface 903.

[0158] Processor 902 may implement or execute various exemplary logic blocks, modules, and circuits described in conjunction with embodiments of this disclosure. Processor 902 may be a central processing unit, a general-purpose processor, a digital signal processor, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It may implement or execute various exemplary logic blocks, modules, and circuits described in conjunction with embodiments of this disclosure. Processor 902 may also be a combination that implements computing functions, such as including one or more microprocessor combinations, a combination of a DSP and a microprocessor, etc.

[0159] The communication interface 903 is used to connect to other devices via a communication network. This communication network can be Ethernet, wireless access network, wireless local area network (WLAN), etc.

[0160] The memory 901 may be a read-only memory (ROM) or other type of static storage device capable of storing static information and instructions, random access memory (RAM) or other type of dynamic storage device capable of storing information and instructions, or electrically erasable programmable read-only memory (EEPROM), disk storage media or other magnetic storage devices, or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer, but is not limited thereto.

[0161] In one possible implementation, the memory 901 can exist independently of the processor 902. The memory 901 can be connected to the processor 902 via a bus 904 and is used to store instructions or program code. When the processor 902 calls and executes the instructions or program code stored in the memory 901, it can implement the service continuation method provided in this embodiment. In another possible implementation, the memory 901 can also be integrated with the processor 902.

[0162] The 904 bus can be an extended industry standard architecture (EISA) bus, etc. The 904 bus can be divided into address bus, data bus, control bus, etc. For ease of representation, Figure 5 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.

[0163] Some embodiments of this disclosure provide a computer-readable storage medium (e.g., a non-transitory computer-readable storage medium) storing computer program instructions that, when executed on a processor, cause the processor to perform a service continuation method as described in any of the above embodiments.

[0164] Exemplary examples of computer-readable storage media may include, but are not limited to: magnetic storage devices (e.g., hard disks, floppy disks, or magnetic tapes), optical discs (e.g., compact disks (CDs), digital versatile disks (DVDs), etc.), smart cards, and flash memory devices (e.g., erasable programmable read-only memory (EPROMs), cards, sticks, or key drives, etc.). The various computer-readable storage media described in this disclosure may represent one or more devices and / or other machine-readable storage media for storing information. The term "machine-readable storage medium" may include, but is not limited to, wireless channels and various other media capable of storing, containing, and / or carrying instructions and / or data.

[0165] This disclosure provides a computer program product containing instructions that, when run on a processor, cause the processor to execute the service continuation method of any of the above embodiments.

[0166] This disclosure provides a vehicle including the control device of any of the preceding embodiments; or the computer-readable storage medium of any of the preceding embodiments; or the computer program product of any of the preceding embodiments.

[0167] The vehicle provided in this application may be a passenger vehicle or a freight vehicle, and may also be an electric vehicle or a hybrid vehicle. This application does not limit the specific purpose or power type of the vehicle, and the choice can be made according to actual needs.

[0168] A vehicle consists of a body and wheels. The body is used for passengers and for carrying goods, while the wheels are mounted underneath the body to support it and allow it to roll on the road, thus enabling the vehicle to move.

[0169] In some possible examples, the vehicle is equipped with a control system, which typically adopts a layered distributed architecture. From the bottom layer to the top layer, it can be roughly divided into a perception layer, a control layer, a coordination layer, and an interaction layer. The layers communicate with each other through an in-vehicle network.

[0170] The perception layer mainly consists of various sensors distributed inside and outside the vehicle, including but not limited to external environment cameras, millimeter-wave radar, lidar, ultrasonic sensors, in-vehicle driver monitoring cameras, microphone arrays, and various vehicle status sensors (such as wheel speed sensors, inertial measurement units, temperature sensors, etc.). The perception layer is responsible for collecting multi-dimensional data such as the vehicle's own operating status, driver behavior, and external driving environment in real time.

[0171] The control layer consists of dozens to hundreds of electronic control units (ECUs), distributed across multiple functional domains including powertrain, chassis, body, intelligent driving, and infotainment. Each ECU embeds real-time control software that performs closed-loop control of the vehicle's actuators based on preset control strategies or upper-level commands, and generates corresponding alarm signals when abnormal conditions are detected. Typical ECUs include the engine control unit, transmission control unit, brake control unit, steering control unit, vehicle stability control unit, airbag control unit, intelligent driving domain controller, and in-vehicle infotainment unit.

[0172] The coordination layer typically exists in the form of a domain controller or a central computing platform, responsible for cross-domain data fusion, global state management, and collaborative decision-making. The coordination layer centrally processes and schedules the sensing data and control commands that were originally scattered across various functional domains, connecting downwards to various electronic control units and supporting human-machine interaction functions upwards.

[0173] The interaction layer mainly includes in-cabin display devices (such as instrument panel, central control screen, head-up display), voice interaction system, haptic feedback device, etc., which are responsible for presenting vehicle status, warning information and driving suggestions to the driver in the form of visual, auditory or tactile, while receiving the driver's touch, voice and other input commands.

[0174] Data transmission and interaction between different layers are achieved through the vehicle bus network. Common vehicle bus protocols include CAN (Controller Area Network), CAN FD (CAN with Flexible Data-Rate), LIN (Local Interconnect Network), FlexRay, and vehicle Ethernet, which supports high-bandwidth data transmission. Among these, CAN and CAN FD buses are widely used for communication in real-time control domains such as powertrain and chassis, while vehicle Ethernet is gradually being applied to high-bandwidth sensor data transmission in the intelligent driving domain and multimedia interaction scenarios in the cockpit domain.

[0175] In some possible examples, the vehicle terminal, as the core of the vehicle computing platform, is equipped with a processor and memory to execute the service connection method provided in the embodiments of this application.

[0176] For example, the control device of this application is arranged in an in-vehicle terminal.

[0177] For example, the vehicle terminal is equipped with multiple functional modules for performing the various method steps.

[0178] The above are merely specific embodiments of this disclosure, but the scope of protection of this disclosure is not limited thereto. Any changes or substitutions within the technical scope disclosed in this disclosure should be included within the scope of protection of this disclosure. Therefore, the scope of protection of this disclosure should be determined by the scope of the claims.

Claims

1. A service continuity method, characterized in that, The method includes: Based on the relative movement trend between the first device and the second device, and the current operating service of the first device, the target service to be transferred in the first device is determined; wherein, the relative movement trend includes a moving away trend or a moving towards trend; Determine the service operation status of the target service; wherein, the service operation status is used to characterize the operation progress and / or operation content of the target service on the first device; Through the service transfer channel between the first device and the second device, the target service and the service running status are transferred from the first device to the second device, so that the second device can continue the target service on the second device through the service running status.

2. The service continuation method according to claim 1, characterized in that, When the first device is a user's mobile device and the second device is an in-vehicle infotainment system, determining the target service to be transferred in the first device based on the relative movement trend between the first and second devices and the current operating service of the first device includes: If the relative movement trend is determined to be a convergence trend, the user's service continuation intention is determined based on the currently running service, the user's travel intention, location information, and / or the user's set schedule information; Based on the service continuation intent, the target service is determined from the available services of the first device.

3. The service continuation method according to claim 2, characterized in that, The step of transferring the target service and the service running status from the first device to the second device through the service transfer channel between the first device and the second device, so that the second device can continue the target service on the second device through the service running status, includes: Based on the target information, the confidence level for continuing the target service is determined; wherein, the target information includes: the user's service flow habits; The target service, the service running status, and the confidence level are transferred from the first device to the second device, so that the second device can continue the target service based on the confidence level.

4. The service continuation method according to claim 3, characterized in that, The target information further includes at least one of the following: the usage status of the first device, the relative moving speed between the first device and the second device, and the trajectory stability between the first device and the second device; the usage status includes at least one of the following: whether the first device is in a call state, and whether the first device is connected to other devices; The confidence level when the first device is in a call state is lower than the confidence level when the first device is in a call state; the confidence level when the first device is connected to the other device is lower than the confidence level when the first device is not connected to the other device; the other device is a device other than the second device.

5. The service continuity method according to claim 3, characterized in that, The step of continuing the target service based on the confidence level includes: If the confidence level is not lower than the first confidence threshold, the target service is continued on the second device based on the service running status; If the confidence level is lower than the first confidence threshold, a confirmation message is output to the user; In response to the user's service connection instruction, the target service is connected on the second device based on the service running status.

6. The service continuity method according to claim 1 or 2, characterized in that, When the first device is an in-vehicle infotainment system and the second device is the user's mobile device, determining the target service to be transferred in the first device based on the relative movement trend between the first and second devices and the current operating service of the first device includes: If the relative movement trend is determined to be the moving away trend, the user's service continuation intention is determined based on the currently running service; Based on the service continuation intent, the target service is determined from the available services of the first device.

7. The service continuity method according to claim 1, characterized in that, The service flow channel is a service synchronization channel that is independent of the media projection channel between the first device and the second device.

8. The service continuation method according to claim 1, characterized in that, When the first device is the user's mobile device, the first device is determined in the following manner: Identify at least one candidate mobile device connected to the second device; For each of the at least one candidate mobile devices, the service flow priority of each candidate mobile device is determined based on the vehicle cabin location corresponding to each mobile device; The candidate mobile device with the highest service flow priority among the at least one candidate mobile devices is determined as the first device.

9. The service continuation method according to claim 1, characterized in that, The method further includes: Before transferring the target service and its running state from the first device to the second device, a copy of the target service's running state is saved through the first device. If the connection between the first device and the second device is lost, or if the transfer of the target service and the service operation status fails, the service operation status of the target service on the first device is maintained based on the service operation status copy.

10. A service connection device, characterized in that, The device includes: a determining module and a processing module; Based on the relative movement trend between the first device and the second device, and the current operating service of the first device, the target service to be transferred in the first device is determined; wherein, the relative movement trend includes a moving away trend or a moving towards trend; Determine the service operation status of the target service; Through the service transfer channel between the first device and the second device, the target service and the service running status are transferred from the first device to the second device, so that the second device can continue the target service on the second device through the service running status.

11. A control device, characterized in that, The control device includes: a memory and a processor; the memory and the processor are coupled; the memory is used to store instructions executable by the processor; when the processor executes the instructions, it performs the service continuation method as described in any one of claims 1 to 9.

12. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer instructions that, when executed on a processor, cause the processor to perform the service continuation method as described in any one of claims 1 to 9.

13. A computer program product, characterized in that, Includes a computer program; when the computer program is executed, it is capable of implementing the service continuation method as described in any one of claims 1 to 9.

14. A vehicle, characterized in that, It includes the control device as claimed in claim 11; or the computer-readable storage medium as claimed in claim 12; or the computer program product as claimed in claim 13.