A method and system for multi-link redundant transmission of vehicle-mounted remote communication terminal

CN122994942APending Publication Date: 2026-10-27GOSUNCNWELINK TECH
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202611291200.6
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2026-08-24
Publication Date
2026-10-27

AI Technical Summary

Technical Problem

[0007]本发明实施例旨在提供一种车载远程通信终端多链路冗余传输方法及传输系统,旨在解决现有车载远程通信终端因采用单卡单待或双卡冗余架构,普遍存在网络覆盖盲区、切换时延超阈值导致业务中断、关键业务缺乏优先级保障的问题

Benefits of technology

[0018]与现有技术相比较,本发明实施例提供的一种车载远程通信终端多链路冗余传输方法及传输系统,该车载终端多链路冗余传输方法通过车载远程通信终端的车端SDK通过双卡双通架构同时建立与云端SDK虚拟网关集群的两条蜂窝网络连接链路,在车云两端SDK发送业务数据时,车端SDK根据业务类型创建不同的RTT隧道,将业务数据智能分发至对应的RTT隧道,并基于差异化QoS资源保障策略进行智能化QoS调度,通过两条蜂窝网络连接链路同时将RTT隧道待发送的业务数据发送至云端;云端SDK虚拟网关集群接收两路业务数据包,基于预设报文优选机制对两路业务数据包进行解析,获得最优报文,丢弃冗余报文,并对最优报文按序重组,得到重组后的业务数据包。从而通过两条蜂窝网络连接链路同时发送相同业务数据,云端SDK基于预设报文优选机制选取最优报文,形成多发选收冗余传输机制,该机制实现了网络故障情况下的零丢包切换,提升弱网环境下数据传输成功率,性能优于传统的双卡“1+1”主备冗余保护切换机制,且任意单路随机故障均不影响关键业务质量,实现关键业务零感知切换,显著提升车联网服务可靠性;通过车端SDK根据业务类型创建不同的RTT隧道,将业务数据智能分发至对应的RTT隧道,并基于差异化QoS资源保障策略进行智能化QoS调度转发,从而针对不同业务类型创建独立的RTT隧道,并为每条隧道配置差异化QoS资源保障策略,实现智能化QoS调度,支持业务差异化QoS保障,实现关键业务优先转发,满足多样化车联网应用场景。

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN122994942A_ABST
    Figure CN122994942A_ABST
Patent Text Reader

Abstract

This invention discloses a multi-link redundant transmission method and system for vehicle-mounted remote communication terminals. The method includes: the vehicle-side SDK of the vehicle-mounted remote communication terminal simultaneously establishes two cellular network connection links with a cloud-based SDK virtual gateway cluster via a dual-SIM dual-pass architecture; when the SDKs at both ends of the vehicle and cloud send service data, the vehicle-side SDK creates different RTT tunnels according to the service type, intelligently distributes the service data to the corresponding RTT tunnel, and performs intelligent QoS scheduling based on a differentiated QoS resource guarantee strategy, simultaneously sending the service data to be sent through the RTT tunnels to the cloud via the two cellular network connection links; the cloud-based SDK virtual gateway cluster simultaneously receives two service data packets, parses the two service data packets based on a preset message optimization mechanism, obtains the optimal message, discards redundant messages, and reassembles the optimal message in sequence to obtain the reassembled service data packet. This improves the data transmission success rate in weak network environments and meets the needs of vehicle-to-everything (V2X) application scenarios.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This invention relates to the field of vehicle networking technology, and in particular to a multi-link redundant transmission method and transmission system for an in-vehicle remote communication terminal. Background Technology

[0002] With the evolution of Internet of Vehicles (IoV) technology, the in-vehicle telematics box (TBOX), as a key connected device for data interaction between the vehicle and the cloud service platform, undertakes core business functions such as remote vehicle control, over-the-air (OTA) firmware upgrades, and vehicle security monitoring. The reliability and real-time performance of its communication link directly affect the Quality of Service (QoS) of these services. Currently, in-vehicle telematics boxes adopt a single-SIM single-standby architecture, accessing only a single operator's network, which presents the following problems: (1) A single network has coverage blind spots, and the SIM card may be physically damaged or suspended due to non-payment, resulting in single point of failure, causing vehicle control failure or upgrade interruption.

[0003] (2) Some products use dual-card redundancy, but the protocol stack needs to be rebuilt when switching between primary and backup, and the delay usually exceeds 5 seconds, which exceeds the TCP retransmission timeout threshold, causing the connection to be disconnected and making it impossible to achieve seamless business connection.

[0004] (3) Lack of business priority differentiation means that critical vehicle control signaling and security data are easily squeezed out by non-critical traffic such as entertainment systems, affecting the quality of core services.

[0005] (4) In order to shorten the switching delay, the simultaneous registration of dual cards on the network keeps the radio frequency module active for a long time, which significantly increases the static power consumption and is not conducive to the life of vehicle battery and energy efficiency.

[0006] Therefore, there is an urgent need for an in-vehicle communication solution that can simultaneously ensure communication reliability, real-time switching, service priority scheduling, and power consumption optimization. Summary of the Invention

[0007] This invention aims to provide a multi-link redundant transmission method and system for vehicle-mounted remote communication terminals, addressing the common problems of network coverage blind spots, service interruptions due to handover latency exceeding thresholds, and lack of priority guarantees for critical services in existing vehicle-mounted remote communication terminals that employ single-SIM single-standby or dual-SIM redundant architectures.

[0008] To address the aforementioned technical problems, a first aspect of this invention provides a method for multi-link redundant transmission in a vehicle-mounted terminal, the method comprising: The vehicle-side SDK of the in-vehicle remote communication terminal establishes two cellular network connection links with the cloud SDK virtual gateway cluster simultaneously through a dual-SIM dual-pass architecture. When the vehicle-side SDK sends service data to both ends of the cloud, the vehicle-side SDK creates different RTT tunnels according to the service type, intelligently distributes the service data to the corresponding RTT tunnel, and performs intelligent QoS scheduling based on differentiated QoS resource guarantee strategies. The service data to be sent in the RTT tunnel is sent to the cloud simultaneously through two cellular network connection links. The cloud SDK virtual gateway cluster simultaneously receives two service data packets sent through two cellular network connection links. Based on a preset message optimization mechanism, it parses the two service data packets, obtains the optimal message, discards redundant messages, and reassembles the optimal message in order to obtain the reassembled service data packet.

[0009] In some embodiments, when the vehicle-side SDK sends service data to both the vehicle and cloud SDKs, the vehicle-side SDK creates different RTT tunnels according to the service type, intelligently distributes the service data to the corresponding RTT tunnel, and performs intelligent QoS scheduling based on a differentiated QoS resource guarantee strategy. The service data to be sent in the RTT tunnel is simultaneously sent to the cloud through two cellular network connection links, including: When the SDKs on both the vehicle and cloud sides send business data, the vehicle-side SDK will copy the same business data frame to form two identical business data packets. The vehicle-side SDK creates different RTT tunnels based on the business type; The vehicle-side SDK intelligently distributes business data from different tunnels to the corresponding RTT tunnels; The vehicle-side SDK performs intelligent QoS scheduling based on differentiated QoS resource guarantee strategies, and simultaneously sends the service data to be sent through the RTT tunnel to the cloud through two cellular network connection links.

[0010] In some embodiments, the differentiated QoS resource guarantee strategy includes: creating independent RTT tunnels that respectively carry signaling services, video services, and Internet services; configuring the highest QoS priority for the RTT tunnel where signaling services reside to ensure priority forwarding of critical services.

[0011] In some embodiments, the preset message selection mechanism includes: the cloud SDK virtual gateway cluster performs timestamp comparison, sequence number verification, and integrity verification on the received service data packet messages; and selects the message that passes the verification and has the earliest timestamp as the optimal message to achieve zero packet loss switching in the event of network failure.

[0012] In some embodiments, the method further includes: establishing an end-to-end encrypted secure tunnel between the vehicle-side SDK of the vehicle-mounted remote communication terminal and the cloud SDK virtual gateway cluster, and using a preset encryption algorithm to encrypt the transmitted data across the entire link.

[0013] In some embodiments, the method further includes: real-time monitoring of link performance indicators of two cellular network connection links, and dynamically adjusting transmission strategies and coding rates based on the link performance indicators using an AI algorithm.

[0014] Accordingly, a second aspect of the present invention provides a multi-link redundant transmission system for a vehicle-mounted remote communication terminal, applied to the multi-link redundant transmission method for a vehicle-mounted remote communication terminal described in the first aspect of the present invention. The system includes: a vehicle-mounted remote communication terminal integrating an embedded vehicle-side SDK, a cloud-based operation management platform deploying a cloud-based SDK virtual gateway cluster, and a unified management platform, wherein: The vehicle-mounted remote communication terminal supports dual-SIM dual-pass. Its vehicle-side SDK establishes two cellular network connection links with the cloud SDK virtual gateway cluster simultaneously through the dual-SIM dual-pass architecture. When the vehicle and cloud SDKs send service data, the vehicle-side SDK creates different RTT tunnels according to the service type, intelligently distributes the service data to the corresponding RTT tunnel, and performs intelligent QoS scheduling based on differentiated QoS resource guarantee strategies. The service data to be sent in the RTT tunnel is sent to the cloud operation and management platform simultaneously through the two cellular network connection links. The cloud-based operation and management platform is used to simultaneously receive two service data packets sent through two cellular network connection links via a cloud SDK virtual gateway cluster. Based on a preset message optimization mechanism, it parses the two service data packets to obtain the optimal message, discards redundant messages, and reassembles the optimal message in order to obtain the reassembled service data packets. The unified management platform is used to distribute differentiated QoS resource guarantee policies to vehicle-mounted remote communication terminals, status monitoring, and intelligent operation and maintenance, thereby achieving separation of control and transfer.

[0015] In some embodiments, the vehicle-side SDK has kernel-level network capabilities, including: establishing a secure data channel between user space and kernel space through the TUN virtual network card driver; implementing real-time packet capture, filtering, and labeling based on the Netfilter framework; and implementing intelligent distribution of policy routing based on source IP, application UID, or destination address using Iptables four-table five-chain operations.

[0016] In some embodiments, the cloud SDK virtual gateway cluster has the following processing capabilities: unified management of the vehicle-mounted dual-link encrypted tunnel, completion of decryption and protocol conversion; intelligent identification of redundant data packets and sequential reassembly of messages.

[0017] In some embodiments, the unified management platform adopts a control-transfer separation architecture, including: a control plane for formulating differentiated QoS resource guarantee policies, issuing security configurations, and monitoring status; and a data plane for encryption encapsulation, intelligent routing, and high-speed forwarding.

[0018] Compared with existing technologies, the present invention provides a multi-link redundant transmission method and system for vehicle-mounted remote communication terminals. This method establishes two cellular network connection links between the vehicle-side SDK of the vehicle-mounted remote communication terminal and the cloud SDK virtual gateway cluster simultaneously via a dual-SIM dual-pass architecture. When the SDKs at both ends of the vehicle and cloud send service data, the vehicle-side SDK creates different RTT tunnels according to the service type, intelligently distributes the service data to the corresponding RTT tunnel, and performs intelligent QoS scheduling based on a differentiated QoS resource guarantee strategy. The service data to be sent through the RTT tunnels is simultaneously sent to the cloud via the two cellular network connection links. The cloud SDK virtual gateway cluster receives the two service data packets, parses them based on a preset message optimization mechanism, obtains the optimal message, discards redundant messages, and reassembles the optimal message in sequence to obtain the reassembled service data packets. This allows for the simultaneous transmission of the same service data through two cellular network links. The cloud SDK selects the optimal packet based on a preset packet optimization mechanism, forming a multi-transmission and selective reception redundant transmission mechanism. This mechanism achieves zero-packet loss switching in the event of network failure, improving the data transmission success rate in weak network environments. Its performance is superior to the traditional dual-SIM "1+1" primary / backup redundant protection switching mechanism, and any random failure on a single path does not affect the quality of critical services, achieving zero-perception switching of critical services and significantly improving the reliability of vehicle-to-everything (V2X) services. The vehicle-side SDK creates different RTT tunnels based on service types, intelligently distributing service data to the corresponding RTT tunnels. It also performs intelligent QoS scheduling and forwarding based on differentiated QoS resource guarantee policies. This creates independent RTT tunnels for different service types and configures differentiated QoS resource guarantee policies for each tunnel, achieving intelligent QoS scheduling, supporting differentiated QoS guarantees for services, prioritizing the forwarding of critical services, and meeting diverse V2X application scenarios.

[0019] This invention, while ensuring high reliability and low handover latency in communication links, also considers service priority scheduling strategies and terminal power consumption optimization. It achieves seamless service transmission, differentiated bandwidth scheduling, and low power consumption, reducing dual-SIM standby power consumption and optimizing energy efficiency. This meets the core requirements of current intelligent connected vehicles for high reliability, low latency, high security, and low power consumption in-vehicle communication. Therefore, it solves the problems commonly found in existing in-vehicle remote communication terminals, which use single-SIM single-standby or dual-SIM redundant architectures, such as network coverage blind spots, service interruptions due to handover latency exceeding thresholds, and lack of priority guarantees for critical services. Attached Figure Description

[0020] One or more embodiments are illustrated by way of example with reference numerals in the accompanying drawings. These illustrations do not constitute a limitation on the embodiments. Elements with the same reference numerals in the drawings are denoted as similar elements. Unless otherwise stated, the figures in the drawings are not to be limited by scale.

[0021] Figure 1 This is a schematic diagram of the architecture of a multi-link redundant transmission system for a vehicle-mounted remote communication terminal provided by the present invention; Figure 2 This is a flowchart illustrating a multi-link redundant transmission method for a vehicle-mounted remote communication terminal provided by the present invention. Figure 3 This is a schematic diagram of a multi-link redundant transmission method for a vehicle-mounted remote communication terminal and an encrypted cellular network connection link in the system provided by the present invention; Figure 4 This is a transmission timing diagram of a multi-link redundant transmission method and system for a vehicle-mounted remote communication terminal provided by the present invention, based on a multi-transmission selective reception redundant transmission mechanism; Figure 5 This is a schematic diagram of a multi-link redundant transmission method and system for vehicle-mounted remote communication terminals provided by the present invention, which performs intelligent QoS scheduling based on a differentiated QoS resource guarantee strategy. Detailed Implementation

[0022] To facilitate understanding of the present invention, a more detailed description is provided below with reference to the accompanying drawings and specific embodiments. It should be noted that when an element is described as being "fixed to" another element, it can be directly on the other element, or one or more intermediate elements may exist between them. When an element is described as being "connected" to another element, it can be directly connected to the other element, or one or more intermediate elements may exist between them. The terms "upper," "lower," "inner," "outer," "bottom," etc., used in this specification indicate the orientation or positional relationship based on the orientation or positional relationship shown in the accompanying drawings, and are only for the convenience of describing the present invention and simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, or be constructed and operated in a specific orientation, and therefore should not be construed as a limitation of the present invention. Furthermore, the terms "first," "second," "third," etc., are used for descriptive purposes only and should not be construed as indicating or implying relative importance.

[0023] Unless otherwise defined, all technical and scientific terms used in this specification have the same meaning as commonly understood by one of ordinary skill in the art to which this invention pertains. The terminology used in this specification is for the purpose of describing particular embodiments only and is not intended to limit the invention. The term "and / or" as used in this specification includes any and all combinations of one or more of the associated listed items.

[0024] Furthermore, the technical features involved in the different embodiments of the present invention described below can be combined with each other as long as they do not conflict with each other.

[0025] With the evolution of Internet of Vehicles (IoV) technology, the in-vehicle telematics box (TBOX) is a key connected device for data interaction between the vehicle and the cloud service platform. It undertakes core business functions such as remote vehicle control, over-the-air (OTA) firmware upgrades, and vehicle security monitoring. The reliability and real-time performance of its communication link directly affect the quality of service (QoS) of the above services.

[0026] Currently, most commercially available vehicle-mounted remote communication terminal products adopt a "single SIM card, single standby" communication architecture, which uses a single user identification card (SIM) and a single operator's network. This architecture presents the following technical problems in actual operating environments: First, there are risks of network coverage blind spots and single points of failure. The existing single-SIM single-standby architecture relies on a single operator's network for data transmission. Limited by the deployment density and geographical coverage of a single operator's base stations, vehicles are prone to communication blind spots in typical weak coverage scenarios such as remote areas, underground parking lots, or tunnels. At the same time, the SIM card itself is susceptible to single points of failure at the hardware and service levels, such as physical interface oxidation, contact failure, or account suspension by the operator due to unpaid fees. These factors may lead to failures such as remote vehicle control command issuance failure, unexpected interruption of OTA upgrade process, or failure to upload vehicle security data normally, which seriously affects the normal use of vehicle network services.

[0027] Second, the high latency of primary / backup network switching makes seamless service continuity impossible. Some existing solutions employ a dual-SIM "1+1" primary / backup redundancy protection switching mechanism to improve availability, but their primary / backup switching process typically relies on network layer signal strength scanning and full protocol stack reconstruction, resulting in an overall switching latency generally exceeding 5 seconds. For long-connection services based on Transmission Control Protocol (TCP), this latency exceeds the standard TCP Retransmission Timeout (RTO) threshold, easily causing connection link breaks. Continuous services such as remote vehicle control and real-time security monitoring are forced to interrupt, making seamless service continuity during network switching impossible and resulting in extremely poor user experience and service stability.

[0028] Third, the lack of a service priority scheduling mechanism makes core service bandwidth easily squeezed out. Existing vehicle-mounted remote communication terminal communication systems adopt a unified traffic transmission strategy, lacking a differentiated quality of service (QoS) guarantee mechanism based on service type at the service scheduling level. It fails to prioritize and allocate bandwidth between critical services such as remote vehicle control signaling and security alarm data and non-critical Internet traffic generated by the vehicle infotainment system, making core service data susceptible to background traffic impacts, and making it difficult to guarantee the real-time performance and reliability of transmission.

[0029] Fourth, the high static power consumption of the terminal is detrimental to vehicle energy consumption management. To maintain dual-SIM simultaneous network connectivity and shorten potential handover latency, some solutions require both RF and baseband modules to remain active for extended periods, resulting in a significant increase in the static power consumption of the TBOX unit. This additional power consumption shortens the battery life during static parking for vehicles powered by batteries and accelerates battery aging, negatively impacting the overall vehicle energy management efficiency.

[0030] In summary, how to balance service priority scheduling strategies and terminal power consumption optimization while ensuring high reliability and low handover latency of communication links is a technical challenge that urgently needs to be addressed in this field.

[0031] For this purpose, please refer to Figure 1 This invention provides a multi-link redundant transmission system 100 for an in-vehicle remote communication terminal based on a dual SIM dual active (DSDA) architecture, applicable to the multi-link redundant transmission method for an in-vehicle remote communication terminal based on a DSDA architecture described in any of the following embodiments. The system includes: an in-vehicle remote communication terminal 10 integrating an embedded vehicle-side SDK, a cloud-based operation management platform 20 deploying a cloud-based SDK virtual gateway cluster, and a unified management platform 30, wherein: The vehicle-mounted remote communication terminal 10 supports dual-SIM dual-pass. Its vehicle-side SDK establishes two cellular network connection links with the cloud SDK virtual gateway cluster simultaneously through the dual-SIM dual-pass architecture. When the vehicle and cloud SDKs send service data, the vehicle-side SDK creates different RTT tunnels according to the service type, intelligently distributes the service data to the corresponding RTT tunnel, and performs intelligent QoS scheduling based on differentiated QoS resource guarantee strategies. The service data to be sent in the RTT tunnel is sent to the cloud operation management platform 20 simultaneously through the two cellular network connection links. The cloud-based operation and management platform 20 is used to simultaneously receive two service data packets sent through two cellular network connection links via the cloud SDK virtual gateway cluster. Based on a preset message optimization mechanism, it parses the two service data packets, obtains the optimal message, discards redundant messages, and reassembles the optimal message in order to obtain the reassembled service data packets. The unified management platform 30, belonging to the control layer, is used to distribute differentiated QoS resource guarantee policies to the vehicle-mounted remote communication terminal 10, monitor status, and perform intelligent operation and maintenance, thereby achieving separation of control and transfer.

[0032] In this embodiment, a multi-link redundant transmission system for vehicle-mounted remote communication terminals based on a dual-SIM dual-pass architecture is provided. The vehicle-mounted remote communication terminal establishes two cellular network connection links with the cloud SDK virtual gateway cluster simultaneously based on the dual-SIM dual-pass architecture using the vehicle-side SDK (Software Development Kit). When the SDKs at both ends of the vehicle and cloud send service data, the vehicle-side SDK creates different RTT tunnels according to the service type, intelligently distributes the service data to the corresponding RTT tunnel, and performs intelligent QoS scheduling based on the differentiated QoS resource guarantee policy issued by the unified management platform. The service data to be sent in the RTT tunnels is simultaneously sent to the cloud operation management platform through the two cellular network connection links. The cloud operation management platform, which deploys the cloud SDK virtual gateway cluster, simultaneously receives the two service data packets sent through the two cellular network connection links through the cloud SDK virtual gateway cluster. Based on a preset message optimization mechanism, the two service data packets are parsed to obtain the optimal message, discard redundant messages, and reassemble the optimal message in order to obtain the reassembled service data packet. This allows for the simultaneous transmission of the same service data through two cellular network links. The cloud SDK selects the optimal packet based on a preset packet optimization mechanism, forming a multi-transmission and selective reception redundant transmission mechanism. This mechanism achieves zero-packet loss switching in the event of network failure, improving the data transmission success rate in weak network environments. Its performance is superior to the traditional dual-SIM "1+1" primary / backup redundant protection switching mechanism, and any random failure on a single path does not affect the quality of critical services, achieving zero-perception switching of critical services and significantly improving the reliability of vehicle-to-everything (V2X) services. The vehicle-side SDK creates different RTT tunnels based on service types, intelligently distributing service data to the corresponding RTT tunnels. It also performs intelligent QoS scheduling and forwarding based on differentiated QoS resource guarantee policies. This creates independent RTT tunnels for different service types and configures differentiated QoS resource guarantee policies for each tunnel, achieving intelligent QoS scheduling, supporting differentiated QoS guarantees for services, prioritizing the forwarding of critical services, and meeting diverse V2X application scenarios.

[0033] This invention, while ensuring high reliability and low handover latency in communication links, also considers service priority scheduling strategies and terminal power consumption optimization. It achieves seamless service transmission, differentiated bandwidth scheduling, and low power consumption, reducing dual-SIM standby power consumption and optimizing energy efficiency. This meets the core requirements of current intelligent connected vehicles for high reliability, low latency, high security, and low power consumption in-vehicle communication. Therefore, it solves the problems commonly found in existing in-vehicle remote communication terminals, which use single-SIM single-standby or dual-SIM redundant architectures, such as network coverage blind spots, service interruptions due to handover latency exceeding thresholds, and lack of priority guarantees for critical services.

[0034] In one embodiment, the vehicle-mounted remote communication terminal 10 integrates an embedded vehicle-side SDK, which has kernel-level network capabilities, including: establishing a secure data channel between user space and kernel space through the TUN virtual network card driver; implementing real-time packet capture, filtering, and labeling based on the Netfilter framework; and implementing intelligent distribution of policy routing based on source IP, application UID, or destination address through Iptables four-table five-chain operations.

[0035] In one embodiment, the cloud-based operation management platform 20 deploys a cloud-based SDK virtual gateway cluster, which has the following processing capabilities: unified management of the vehicle-mounted dual-link encrypted tunnel, completing decryption and protocol conversion; intelligent identification of redundant data packets and sequential reassembly of messages; and fully transparent connection to the vehicle manufacturer's Telematics Service Provider (TSP) platform.

[0036] In one embodiment, the unified management platform 30 adopts a control-transfer separation architecture, including: a control plane for formulating differentiated QoS resource guarantee policies, issuing security configurations, and monitoring status; and a data plane for encryption encapsulation, intelligent routing, and high-speed forwarding.

[0037] The differentiated QoS resource guarantee strategy includes: creating independent RTT tunnels to carry signaling services, video services, and Internet services respectively; configuring the highest QoS priority for the RTT tunnels where signaling services are located to ensure that critical services are forwarded first.

[0038] In addition, the unified management platform 30 also has AI-driven intelligent operation and maintenance functions, which can analyze traffic and equipment status through machine learning to achieve fault location and self-healing in seconds.

[0039] This invention utilizes a unified management platform with a control-transfer separation architecture. The control plane issues the latest differentiated QoS resource protection policies and security configurations, while the data plane performs high-speed encryption encapsulation and intelligent routing. Combined with AI-driven second-level fault location and self-healing capabilities, it achieves intelligent operation and maintenance across the entire chain.

[0040] Based on the same inventive concept, in one embodiment, please refer to Figure 2 This invention provides a multi-link redundant transmission method for vehicle-mounted terminals based on DSDA architecture, applied to the multi-link redundant transmission system 100 for vehicle-mounted remote communication terminals based on DSDA architecture described in any of the above embodiments. The method includes: S1. The vehicle-side SDK of the vehicle-mounted remote communication terminal establishes two cellular network connection links with the cloud SDK virtual gateway cluster simultaneously through a dual-SIM dual-pass architecture. S2. When the vehicle-side SDK sends service data to both ends of the cloud, the vehicle-side SDK creates different RTT tunnels according to the service type, intelligently distributes the service data to the corresponding RTT tunnel, and performs intelligent QoS scheduling based on the differentiated QoS resource guarantee strategy. The service data to be sent in the RTT tunnel is sent to the cloud simultaneously through two cellular network connection links. The S3 cloud SDK virtual gateway cluster simultaneously receives two service data packets sent through two cellular network connection links. Based on a preset message optimization mechanism, it parses the two service data packets, obtains the optimal message, discards redundant messages, and reassembles the optimal message in order to obtain the reassembled service data packet.

[0041] In this embodiment, a multi-link redundant transmission method for vehicle-mounted terminals with a DSDA architecture is provided. The vehicle-side SDK of the vehicle-mounted remote communication terminal establishes two cellular network connection links with the cloud SDK virtual gateway cluster simultaneously through a dual-SIM dual-pass architecture. When the SDKs at both ends of the vehicle and cloud send service data, the vehicle-side SDK creates different RTT tunnels according to the service type, intelligently distributes the service data to the corresponding RTT tunnel, and performs intelligent QoS scheduling based on a differentiated QoS resource guarantee strategy. The service data to be sent through the RTT tunnels is simultaneously sent to the cloud through the two cellular network connection links. The cloud SDK virtual gateway cluster receives the two service data packets, parses them based on a preset message optimization mechanism, obtains the optimal message, discards redundant messages, and reassembles the optimal message in sequence to obtain the reassembled service data packets. This allows for the simultaneous transmission of the same service data through two cellular network links. The cloud SDK selects the optimal packet based on a preset packet optimization mechanism, forming a multi-transmission and selective reception redundant transmission mechanism. This mechanism achieves zero-packet loss switching in the event of network failure, improving the data transmission success rate in weak network environments. Its performance is superior to the traditional dual-SIM "1+1" primary / backup redundant protection switching mechanism, and any random failure on a single path does not affect the quality of critical services, achieving zero-perception switching of critical services and significantly improving the reliability of vehicle-to-everything (V2X) services. The vehicle-side SDK creates different RTT tunnels based on service types, intelligently distributing service data to the corresponding RTT tunnels. It also performs intelligent QoS scheduling and forwarding based on differentiated QoS resource guarantee policies. This creates independent RTT tunnels for different service types and configures differentiated QoS resource guarantee policies for each tunnel, achieving intelligent QoS scheduling, supporting differentiated QoS guarantees for services, prioritizing the forwarding of critical services, and meeting diverse V2X application scenarios.

[0042] This invention, while ensuring high reliability and low handover latency in communication links, also considers service priority scheduling strategies and terminal power consumption optimization. It achieves seamless service transmission, differentiated bandwidth scheduling, and low power consumption, reducing dual-SIM standby power consumption and optimizing energy efficiency. This meets the core requirements of current intelligent connected vehicles for high reliability, low latency, high security, and low power consumption in-vehicle communication. Therefore, it solves the problems commonly found in existing in-vehicle remote communication terminals, which use single-SIM single-standby or dual-SIM redundant architectures, such as network coverage blind spots, service interruptions due to handover latency exceeding thresholds, and lack of priority guarantees for critical services.

[0043] In one embodiment, in step S1, the vehicle-side SDK of the vehicle-mounted remote communication terminal establishes two cellular network connection links with the cloud SDK virtual gateway cluster simultaneously through a dual-SIM dual-pass architecture.

[0044] Specifically, please refer to Figure 3The vehicle-mounted remote communication terminal is configured with two data communication modules based on the DSDA architecture. These two modules establish two independent data channels using a dual-SIM dual-standby (DSDA) architecture. Each data communication module can accommodate one primary SIM card and one secondary SIM card. Through the DSDA architecture, both the primary SIM card data channel and the secondary SIM card data channel are activated simultaneously, forming two cellular network connection links (e.g., ...). Figure 3 The encrypted cellular network connection link 1 and encrypted cellular network connection link 2 shown (i.e., dual links) enable the vehicle-mounted remote communication terminal to achieve dual-SIM dual-pass functionality.

[0045] Among them, the vehicle-side SDK of the vehicle-mounted remote communication terminal establishes two independent cellular network connection links with the cloud SDK virtual gateway cluster through a dual-SIM dual-pass architecture, which can simultaneously send the same service data to be sent to the cloud through the two cellular network connection links.

[0046] In one embodiment, in step S2, when the vehicle-side SDK sends service data to both the vehicle and cloud SDKs, the vehicle-side SDK creates different RTT tunnels according to the service type, intelligently distributes the service data to the corresponding RTT tunnel, and performs intelligent QoS scheduling based on a differentiated QoS resource guarantee strategy, simultaneously sending the service data to be sent in the RTT tunnel to the cloud through two cellular network connection links; specifically including steps S21-S24: S21. When the SDK on both the vehicle and cloud ends sends business data, the vehicle SDK copies the same business data frame to form two identical business data packets.

[0047] Specifically, please refer to Figure 4 When a vehicle generates business data that needs to be sent between the vehicle and cloud SDKs (i.e., in the virtual gateway cluster between the vehicle SDK and the cloud SDK), the embedded vehicle SDK in the in-vehicle remote communication terminal copies the same business data frame by frame, forming two identical business data packets (e.g., ...). Figure 4 The specific process for the service data packet 1 and service data packet 2 shown is as follows: S211. Before sending service data, the vehicle-mounted remote communication terminal (TBOX) appends a set of key metadata to each service data packet. This key metadata includes a timestamp, a sequence number (SN), and integrity verification information, among which: Timestamp: Records the precise time when business data packets are generated or sent, used by the cloud SDK to determine timeliness; Sequence Number (SN): A unique, incrementing ID assigned to business data packets, used for cloud-based detection of packet loss and out-of-order delivery; Integrity verification information, such as hash values ​​or MAC addresses, is used in the cloud to verify whether business data has been tampered with during transmission.

[0048] S212. The vehicle-side SDK of the vehicle-mounted remote communication terminal uses the Netfilter framework and Iptables four tables and five chains to capture and mark business data packets in real time at the kernel layer.

[0049] Specifically, the vehicle-side SDK of the in-vehicle remote communication terminal utilizes pre-defined hooks in the Linux kernel's network protocol stack. By configuring iptables rules, it captures and marks service data packets as they pass through these hooks, thereby achieving service identification and classification. The specific implementation process includes: 1. The core mechanism is determined to be formed by Netfilter hooks and iptables four tables and five chains.

[0050] The Netfilter framework is a framework in the Linux kernel that provides multiple hook points along the critical path of network packets traversing the protocol stack. Kernel modules or drivers can register callback functions on these hooks to intercept, inspect, and modify packets.

[0051] The iptables tool is a user-space command-line utility used to manage Netfilter rules in the kernel. It organizes rules using a four-table, five-chain structure. The four tables are rule sets divided by function. The mangle table is specifically used to modify the content of service packets or set marks for them, which is crucial for service identification. The five chains are divided by the timing of service packet processing. These correspond to five key hook points through which service packets flow in the protocol stack, such as the PREROUTING chain when the service packet first enters the network interface card, and the POSTROUTING chain when the service packet is about to leave.

[0052] 2. At the kernel layer, business data packets are captured and marked in real time using the Netfilter framework and Iptables four tables and five chains.

[0053] Specifically, based on the above core mechanism, the kernel-level workflow of the vehicle-side SDK for the in-vehicle remote communication terminal is as follows: 1) Registering Hook Functions: The kernel module of the vehicle-side SDK of the in-vehicle remote communication terminal registers processing functions at specific hook points (such as PREROUTING or POSTROUTING) in the Netfilter framework. This way, when service data packets pass through these hook points, the code in the vehicle-side SDK can be triggered and executed.

[0054] 2) Configure iptables rules: The vehicle-side SDK adds rules to the kernel's mangle table through user-space programs or scripts. Rules define matching conditions (such as source IP, destination port, etc.), and the action executed upon successful matching is a "marking" action. For example, service packets from a specific network card, usb0.1, can be marked as 1, and packets from usb0.2 as 2.

[0055] 3) Service packet capture and marking: When a service packet (represented in the kernel as a struct sk_buff structure) arrives at a registered hook point: The kernel will pause the normal processing flow of business data packets; Execute the registered hook function and traverse the rules of the corresponding chain in the mangle table; Once the rule is matched, the MARK target will be executed, setting a mark value (Mark) on the sk_buff structure of the business data packet.

[0056] 4) Subsequent Processing and Decision-Making: Tagged business data packets are returned to the normal processing flow. This tag can be read by upper-layer applications (such as policy routing, traffic shaping tools like tc, or other modules in the SDK) to identify the business type of the data packet and perform corresponding operations, for example: Policy-based routing: Directing service data packets to different routing tables or network exits based on tag values; Flow control: Apply different traffic shaping or priority queuing rules to service data packets based on the tag value; Business statistics: Based on the tag values, perform independent traffic statistics and monitoring for business data packets of different businesses.

[0057] The vehicle-side SDK of the in-vehicle remote communication terminal efficiently labels service data packets by using the iptables mangle table, which is parasitic on the Netfilter framework at the kernel level. The entire process is completed in kernel space, resulting in extremely low performance overhead.

[0058] S22. The vehicle-side SDK creates different RTT tunnels based on different business types.

[0059] Specifically, please refer to Figure 5Different independent RTT tunnels are created for different service types: RTT1 (first RTT tunnel), RTT2 (second RTT tunnel), and RTT3 (third RTT tunnel). Signaling services (such as remote unlocking) are carried in RTT1, video services in RTT2, and internet services in RTT3. Differentiated QoS resource guarantee policies are configured for each RTT tunnel to prioritize critical services and achieve intelligent QoS scheduling. RTT stands for Round-Trip Time.

[0060] S23. The vehicle-side SDK intelligently distributes business data from different tunnels to the corresponding RTT tunnels.

[0061] Specifically, a secure data channel between user space and kernel space is established through the TUN virtual network interface card driver. Combined with policy routing based on source IP, application UID, or destination address, service data packets from different tunnels are intelligently distributed to the primary or secondary SIM card. The specific implementation process is as follows: By combining TUN virtual network interface cards (NICs) with policy-based routing, intelligent distribution of service data between the two NICs is achieved. The specific implementation process includes: S231. Create a secure data channel between user mode and kernel mode.

[0062] This step involves creating a virtual network interface card (NIC) device that connects the operating system's kernel space and user-space applications. Specifically, it includes: 1. Creating a TUN Virtual Network Interface Card: The TBOX system, a vehicle-mounted remote communication terminal, creates a virtual network device (TUN device), such as tun0, in the kernel by manipulating the special file / dev / net / tun and using the ioctl() system call. From the Linux kernel's perspective, this tun0 device has the same status as the real physical network interface card eth0, and can be configured with an IP address and participate in routing.

[0063] 2. Establish a virtual data channel: One end of the TUN device is connected to the kernel's network protocol stack, and the other end is connected to the user-space vehicle-side SDK program. This data channel is implemented by two drivers: Character device driver: responsible for transmitting business data packets between user mode and kernel mode; Network interface card (NIC) driver: Responsible for enabling the virtual NIC to participate in the kernel's network protocol stack processing just like a real NIC.

[0064] 3. Vehicle-side SDK intervention: After the vehicle-side SDK program of the vehicle-mounted remote communication terminal opens the TUN device file in user mode, it can read raw IP data packets from the kernel or write service data packets to be sent to the kernel through the read() and write() system calls.

[0065] S232. Configure policy routing to determine the direction of business data packets.

[0066] After the TUN device is established, a policy-based routing system is needed to determine which service data packets should enter the virtual data channel. Policy-based routing can be based on various conditions for matching, including: Application-based UID: Each application has a unique user ID (UID). The system can be configured with rules to direct traffic generated by applications with specific UIDs (such as navigation and entertainment) through the TUN device; Based on source / destination IP: This allows decisions to be made based on either the source or destination IP address of the service data packets. For example, all traffic destined for a specific network segment can be routed to a TUN device. Netfilter-based tagging: It can be combined with iptables to first mark specific service packets (MARK), and then policy routing makes decisions based on this mark.

[0067] In the TBOX dual-card dual-pass architecture, create two virtual network cards (such as tun0 and tun1) and configure independent policy routing rules for each card. For example, configure a rule: all packets from the map application (UID=1000) should look up route table 100, and the default exit of this route table is tun0.

[0068] S233, Intelligent distribution and transmission of service data packets.

[0069] Once policy-based routing is configured, the transmission process for business data packets is as follows: 1. Business data packets enter the kernel: An application (such as a map app) generates a business data packet and sends it to the Linux kernel via the socket API; 2. Policy-based routing matching: After receiving a service data packet, the kernel protocol stack checks it according to preset policy-based routing rules. For example, if the service data packet comes from a map application (UID=1000), then the rule "look up route table 100" is matched; 3. Directing to TUN devices: The kernel forwards service data packets to the tun0 virtual network interface card according to the instructions in routing table 100; 4. Vehicle-side SDK takeover: The tun0 device transmits the raw IP data packets to the vehicle-side SDK program of the user-mode vehicle remote communication terminal through the character device channel; 5. Vehicle-side SDK Processing and Forwarding: After receiving the raw IP packet, the vehicle-side SDK program can perform various operations: Select physical link: Based on preset strategies (such as link quality, cost, etc.), decide whether to send this service data packet through the primary SIM card (such as wwan0) or the secondary SIM card (such as wwan1); Data processing: Encrypting and decrypting business data packets, adding extra headers, etc. 6. Service Data Packet Sending: The vehicle-side SDK writes the processed data packet back to the kernel via the write() system call. At this point, the data packet will be sent out via another path (for example, directly routed to the physical network card wwan0) and finally sent out from the corresponding SIM card link.

[0070] Therefore, this invention combines TUN virtual network interface cards (NICs) with policy routing to achieve a mechanism for intelligent distribution of service data between the two NICs, enabling layered collaboration: Policy-based routing performs the first-level traffic splitting at the kernel layer based on source IP, application UID, or destination address; The user-mode vehicle-side SDK gains complete control over service data packets in different tunnels through the TUN device, and completes the second-level decision-making for service data packets in different tunnels in user mode.

[0071] This mechanism enables TBOX to achieve extremely flexible and refined dual-card traffic scheduling with very low performance overhead, ensuring the quality of service for vehicle communication.

[0072] S24. The vehicle-side SDK performs intelligent QoS scheduling based on differentiated QoS resource guarantee strategies, and simultaneously sends the service data to be sent in the RTT tunnel to the cloud through two cellular network connection links.

[0073] Specifically, the differentiated QoS resource guarantee strategy includes: creating independent RTT tunnels that respectively carry signaling services, video services, and Internet services; configuring the highest QoS priority for the RTT tunnels where signaling services are located to ensure that critical services are forwarded first, so as to achieve intelligent QoS scheduling.

[0074] The vehicle-side SDK performs intelligent QoS scheduling based on the differentiated QoS resource guarantee policy issued by the unified management platform, prioritizing the forwarding of key signaling in the first RTT tunnel RTT1, ensuring that core vehicle control services are not squeezed out by entertainment traffic in weak network or bandwidth-limited environments.

[0075] In one embodiment, in step S3, the cloud SDK virtual gateway cluster simultaneously receives two service data packets sent through two cellular network connection links, parses the two service data packets based on a preset message optimization mechanism, obtains the optimal message, discards redundant messages, and reassembles the optimal message in order to obtain the reassembled service data packet.

[0076] Please see Figure 3 and Figure 4 The vehicle-mounted remote communication terminal activates both the primary SIM card data channel and the secondary SIM card data channel simultaneously through the DSDA architecture, forming two cellular network connection links (such as...). Figure 3 (See encrypted cellular network connection link 1 and encrypted cellular network connection link 2). When the vehicle generates service data, the embedded vehicle-side SDK of the vehicle-mounted remote communication terminal copies the same service data frame to form two identical service data packets. The vehicle-side SDK creates different RTT tunnels according to the service type, intelligently distributes the service data to the corresponding RTT tunnel, and performs intelligent QoS scheduling based on differentiated QoS resource guarantee policies. The service data to be sent in the RTT tunnel is sent to the cloud simultaneously through the two cellular network connection links.

[0077] The cloud-based SDK virtual gateway cluster simultaneously receives two service data packets sent through two cellular network connection links and parses the two service data packets using a preset message optimization mechanism.

[0078] The preset message optimization mechanism includes: the cloud SDK virtual gateway cluster performs timestamp comparison, sequence number verification, and integrity verification on the received business data packets; and selects the message that passes the verification and has the earliest timestamp as the optimal message to achieve zero packet loss switching in the event of network failure.

[0079] Specifically, the cloud-based SDK virtual gateway cluster compares the timestamps, sequence numbers, and integrity check codes of two service data packets, selecting the first arriving and verified packet for subsequent processing, automatically discarding duplicate packets and reassembling them in order. This forms a multi-transmission selective redundant transmission mechanism. Under this mechanism, even if the network where the primary SIM card resides experiences sudden congestion or disconnection, causing the primary SIM card's service data packets to fail to reach the cloud-based SDK virtual gateway cluster, the secondary SIM card's service data packets can still reach the cloud-based SDK virtual gateway cluster normally. This achieves seamless switching and zero packet loss at the millisecond level, completely solving the problem of TCP disconnection caused by a switching delay greater than 5 seconds in the traditional dual-SIM "1+1" primary / backup redundant protection switching mechanism.

[0080] In this invention, the multi-transmission and selective redundant transmission mechanism includes the vehicle-mounted remote communication terminal simultaneously sending the same service data through two cellular network connection links, and the cloud SDK selecting the optimal message based on a preset message optimization mechanism (combining timestamp, sequence number, and integrity verification) and discarding redundant messages.

[0081] This multi-transmission selective redundant transmission mechanism consists of two phases: Phase 1: Dual-network concurrent transmission of the vehicle-mounted remote communication terminal (TBOX), which is the specific implementation process of steps S1 and S2 above.

[0082] Phase Two: The message optimization mechanism of the cloud SDK. Its core task is to receive two service data packets and select the optimal service data packet based on the preset message optimization mechanism. This is also the specific implementation process of step S3, including: S31, Reception and Buffering.

[0083] After the cloud SDK virtual gateway cluster receives two service data packets sent through two cellular network connection links, it temporarily stores them in a buffer and waits for all the service data packets belonging to the same service to arrive.

[0084] S32. Multi-dimensional comprehensive evaluation and selection.

[0085] The cloud SDK scores and compares business data packets based on the following dimensions: Integrity verification (first priority): Integrity verification is performed first. Messages that fail verification are immediately discarded and will not participate in subsequent evaluations.

[0086] Timestamp comparison (second priority): Among all complete messages, the message with the earliest timestamp (i.e. the earliest sent) is considered the most timely and is retained with priority.

[0087] Serial number verification (auxiliary judgment): When timestamps are the same or the precision is insufficient, messages with consecutive serial numbers and no skipped numbers are considered more reliable choices.

[0088] Link quality feedback (dynamic factor): The cloud SDK can integrate historical data and prioritize packets from links with better long-term quality (such as low packet loss rate and low latency).

[0089] S33. Reassemble the optimal messages in order to obtain the reassembled service data packets.

[0090] Please see Figure 4 Reassembling the optimal packets in order is a crucial step in ensuring the integrity and orderliness of data transmission across dual links, a key aspect of this invention. This reassembly process relies on the coordinated efforts of four core mechanisms: sorting, caching, deduplication, and packet loss handling. The specific process is as follows: 1. Sequential arrangement: Reorganization is based on sequence numbers.

[0091] This forms the basis for the reorganization. Before sending service data, the vehicle-side SDK of the onboard remote communication terminal (TBOX) attaches a set of key metadata to each service data packet, including assigning a unique, incrementing sequence number to each service data packet. The cloud SDK then uses this SN to place service data packets from two different links into a reordering buffer, waiting for them to be arranged in ascending order.

[0092] 2. Cache waiting: a time window to counteract differences in network latency.

[0093] Because different cellular network links have varying latency, data packets may arrive in a different order than they were sent. To address this, the system sets a reassembly wait time (or "jitter time"). Before the timer expires, the cloud SDK continues to wait to receive all data packets, thus mitigating network latency differences and achieving optimal packet loss handling.

[0094] 3. Deduplication and verification: Ensure the uniqueness and correctness of the data.

[0095] Deduplication: In the multi-transmission selective redundant transmission mechanism, the same service data packet may arrive through different links. The cloud SDK will check the serial number (SN) of the service data packets. Service data packets with the same sequence number will only be processed once, and the rest will be discarded as redundant packets.

[0096] Integrity verification: After deduplication, integrity verification (such as hash verification) is performed. This is crucial for determining whether a message is optimal; only messages that pass the verification will be retained for subsequent reassembly.

[0097] 4. Packet loss handling: Intelligent recovery mechanism.

[0098] If a service data packet for a certain SN is not received after the timeout period, the system will determine that packet loss has occurred and trigger the following intelligent recovery mechanism: Request retransmission: The cloud SDK will send a negative acknowledgment (NACK) or similar retransmission request to the vehicle SDK.

[0099] Intelligent retransmission: After receiving a request, the vehicle-side SDK will select one or both of the two cellular network connection links with the best current quality for retransmission.

[0100] Timeout Handling: When retransmission requests fail, the system will initiate a more advanced timeout retransmission mechanism. If recovery is not possible after a prolonged period, the cloud SDK may skip the data packet and report incomplete data to the upper-layer application, which will then decide how to handle the situation.

[0101] After the above steps, once all expected business data packets in the rearrangement buffer have arrived in order and been verified to be correct, the sequential reassembly process is complete. At this point, the cloud SDK will submit this continuous and complete string of business data packets to the upper-layer business application for its use.

[0102] In summary, optimal packet reassembly uses sequence number sorting, buffer deduplication, and intelligent packet loss handling to restore redundant data streams from two cellular network connection links into a high-quality, complete, and orderly set of business data.

[0103] In this invention, an in-vehicle remote communication terminal establishes two cellular network connection links with a cloud SDK virtual gateway cluster simultaneously via a dual-SIM dual-pass architecture. The same service data to be sent is simultaneously transmitted to the cloud via these two cellular network connection links. The cloud SDK virtual gateway cluster receives the two service data packets, selects the optimal packet based on a preset packet selection mechanism for processing, and discards redundant packets. This allows the same service data to be sent simultaneously via the two cellular network connection links. The cloud SDK selects the optimal packet based on the preset packet selection mechanism, forming a multi-transmission and selective-receive redundant transmission mechanism. This mechanism achieves zero-packet-loss switching in the event of network failure, improves the data transmission success rate in weak network environments, and outperforms the traditional dual-SIM "1+1" primary / backup redundant protection switching mechanism. Furthermore, any single random failure does not affect the quality of critical services, achieving zero-perception switching of critical services and significantly improving the reliability of vehicle networking services.

[0104] In one embodiment, the vehicle terminal multi-link redundant transmission method further includes: establishing an end-to-end encrypted secure tunnel between the vehicle-side SDK of the vehicle remote communication terminal and the cloud SDK virtual gateway cluster, and using a preset encryption algorithm to encrypt the transmitted data across the entire link.

[0105] Specifically, the preset encryption algorithms include Chinese national cryptographic algorithms and / or international mainstream encryption algorithms such as DES, 3DES, SHA, and AES.

[0106] An end-to-end encrypted security tunnel is established between the vehicle-side SDK of the vehicle-mounted remote communication terminal and the cloud SDK virtual gateway cluster. The national cryptographic algorithm and / or international mainstream encryption algorithms such as DES, 3DES, SHA, and AES are used to transmit data in encrypted form throughout the entire link from the vehicle-mounted remote communication terminal to the cloud. This achieves end-to-end encryption to ensure data security, thoroughly protects user data security, and complies with the vehicle network security compliance requirements.

[0107] In one embodiment, the vehicle terminal multi-link redundancy transmission method further includes an intelligent dynamic link detection step: real-time monitoring of the link performance indicators of the two cellular network connection links of the vehicle-cloud network, and dynamic adjustment of the transmission strategy and encoding rate based on the link performance indicators using an AI algorithm; wherein, the link performance indicators include bandwidth, latency, packet loss rate and / or jitter.

[0108] Specifically, the vehicle-mounted remote communication terminal has a built-in intelligent dynamic link detection module. This module monitors the link performance indicators of the two cellular network connection links of the vehicle-to-cloud network in real time, and dynamically adjusts the transmission strategy and coding rate based on the link performance indicators using an AI algorithm. When the AI ​​algorithm detects a deterioration in the quality of a certain cellular network connection link, it dynamically adjusts the transmission strategy and coding rate, and schedules more critical service traffic to other cellular network connection links.

[0109] The vehicle-mounted remote communication terminal has a built-in intelligent dynamic link detection module, which forms a closed-loop control system from precise perception and intelligent decision-making to dynamic execution. Its specific working process includes: Step 1: Precise perception to achieve real-time, multi-dimensional link detection.

[0110] The intelligent dynamic link detection module continuously monitors key link performance indicators of dual-cellular network connections in real time. 1. Active Probe: The intelligent dynamic link probe module periodically sends probe packets (or "heartbeat packets") to actively measure the link status. The probed link performance indicators include: Bandwidth: Evaluates the maximum data transmission capacity of the link; Latency: Measures the round-trip time (RTT) from the time a data packet is sent to the time it is received. Packet loss rate: The percentage of data packets lost during transmission; Jitter: Assess the degree of variation in latency.

[0111] 2. Passive perception: In addition to active detection, the intelligent dynamic link detection module also monitors the transmission of actual business data as supplementary information on link status.

[0112] Step 2: Intelligent decision-making, realizing AI algorithm-driven quality assessment.

[0113] After obtaining the key performance indicators (KPIs) of the original dual-cellular network connectivity links, the decision-making process begins. This involves AI-driven quality assessment, including: Overall Quality Index (CQI): The AI ​​algorithm integrates multiple metrics (bandwidth, latency, packet loss rate, jitter, etc.) and generates a CQI for each cellular network connection link through weighted calculations. For example, in a typical configuration, the weights for latency, packet loss rate, jitter, and bandwidth margin might be 40%, 30%, 20%, and 10%, respectively.

[0114] Trend Prediction and Early Warning: The AI ​​algorithm not only assesses the current quality but also predicts future trends in the link quality of dual-cellular network connections based on historical data. When a link quality indicator of a cellular network connection is detected to be continuously deteriorating and exceeding a preset threshold, it will be determined that its "quality has declined".

[0115] Step 3: Dynamic execution to achieve precise adjustment of transmission strategy.

[0116] Based on the decision-making results from the AI ​​algorithm, TBOX immediately triggered a series of adjustments to ensure that critical business operations were not affected, including: 1. Intelligent Traffic Scheduling: Directing more critical business traffic to "high-quality links" identified by AI algorithms; specific scheduling methods include: Priority mode: Switches all or most traffic to the single cellular network connection link with the best current quality; Load balancing mode: Dynamically adjusts the traffic distribution ratio based on link quality scores, allowing high-quality cellular network links to bear more load.

[0117] 2. Dynamic Encoding Bitrate Adjustment: When a degradation in the link quality of a cellular network connection is detected, the encoders for video, audio, and other services are triggered to reduce the bitrate. By reducing the amount of data transmitted per unit time, this adapts to deteriorating network conditions and avoids severe stuttering or interruptions due to insufficient bandwidth.

[0118] 3. Transmission strategy optimization: Other optimizations may also be performed, such as: Adjusting redundancy strategies: When link quality is extremely poor, the amount of redundant data sent may be increased to ensure reliability; when quality is good, redundancy may be reduced to save bandwidth. Adjust protocol parameters: Dynamically adjust parameters such as TCP window size and QUIC protocol PING interval to adapt to network changes.

[0119] Therefore, the working process of the intelligent dynamic link detection module includes a "detection-evaluation-adjustment" cycle, which is continuous and enables the TBOX to dynamically adapt to complex network environments, providing stable and reliable communication guarantees for vehicle services.

[0120] It should be noted that the above method embodiments and the above system embodiments belong to the same concept. For details of their implementation process, please refer to the system embodiments. Furthermore, the technical features in the system embodiments are all applicable to the above method embodiments, and will not be repeated here.

[0121] This invention provides a multi-link redundant transmission method and system for vehicle-mounted terminals based on a dual-SIM dual-standby architecture. Through a multi-transmission selective-receiver redundant transmission mechanism, a differentiated QoS resource guarantee strategy, an end-to-end encrypted secure tunnel, and intelligent dynamic link detection, it achieves the following technical effects: The multi-transmission selective-receiver redundant transmission mechanism, based on the dual-SIM dual-standby architecture, enables zero-perceptive switching of critical services, significantly improving the reliability of vehicle-to-everything (V2X) services, reducing dual-SIM standby power consumption, optimizing energy utilization efficiency, and improving data transmission success rate in weak network environments; the differentiated QoS resource guarantee strategy supports differentiated QoS guarantees for services, meeting diverse V2X application scenarios; the end-to-end encrypted secure tunnel ensures end-to-end encrypted data security, complying with V2X security compliance requirements; and intelligent dynamic link detection uses AI algorithms to dynamically adjust transmission strategies and coding rates, ensuring communication stability in complex mobile network environments. This addresses the common problems of network coverage blind spots, service interruptions due to exceeding threshold switching latency, and lack of priority guarantees for critical services in existing vehicle-mounted remote communication terminals using single-SIM single-standby or dual-SIM redundant architectures, and solves the reliability, real-time performance, and security issues in V2X communication.

[0122] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element.

[0123] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, and not to limit them; under the concept of the present invention, the technical features of the above embodiments or different embodiments can also be combined, the steps can be implemented in any order, and there are many other variations of different aspects of the present invention as described above, which are not provided in detail for the sake of brevity; although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features; and these modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present invention.

Claims

1. A method for multi-link redundant transmission in a vehicle-mounted terminal, characterized in that, The method includes: The vehicle-side SDK of the in-vehicle remote communication terminal establishes two cellular network connection links with the cloud SDK virtual gateway cluster simultaneously through a dual-SIM dual-pass architecture. When the vehicle-side SDK sends service data to both ends of the cloud, the vehicle-side SDK creates different RTT tunnels according to the service type, intelligently distributes the service data to the corresponding RTT tunnel, and performs intelligent QoS scheduling based on differentiated QoS resource guarantee strategies. The service data to be sent in the RTT tunnel is sent to the cloud simultaneously through two cellular network connection links. The cloud SDK virtual gateway cluster simultaneously receives two service data packets sent through two cellular network connection links. Based on a preset message optimization mechanism, it parses the two service data packets, obtains the optimal message, discards redundant messages, and reassembles the optimal message in order to obtain the reassembled service data packet.

2. The method according to claim 1, characterized in that, When sending service data between the vehicle and cloud SDKs, the vehicle SDK creates different RTT tunnels based on the service type, intelligently distributes the service data to the corresponding RTT tunnel, and performs intelligent QoS scheduling based on a differentiated QoS resource guarantee strategy. The service data to be sent through the RTT tunnels is simultaneously sent to the cloud via two cellular network connection links, including: When the SDKs on both the vehicle and cloud sides send business data, the vehicle-side SDK will copy the same business data frame to form two identical business data packets. The vehicle-side SDK creates different RTT tunnels based on the business type; The vehicle-side SDK intelligently distributes business data from different tunnels to the corresponding RTT tunnels; The vehicle-side SDK performs intelligent QoS scheduling based on differentiated QoS resource guarantee strategies, and simultaneously sends the service data to be sent through the RTT tunnel to the cloud through two cellular network connection links.

3. The method according to claim 1, characterized in that, The differentiated QoS resource guarantee strategy includes: creating independent RTT tunnels to carry signaling services, video services, and Internet services respectively; configuring the highest QoS priority for the RTT tunnel where signaling services are located to ensure priority forwarding of critical services.

4. The method according to claim 1, characterized in that, The preset message selection mechanism includes: the cloud SDK virtual gateway cluster performs timestamp comparison, sequence number verification, and integrity verification on the received business data packets; and selects the message that passes the verification and has the earliest timestamp as the optimal message to achieve zero packet loss switching in the event of network failure.

5. The method according to claim 1, characterized in that, The method further includes: establishing an end-to-end encrypted secure tunnel between the vehicle-side SDK of the vehicle-mounted remote communication terminal and the cloud SDK virtual gateway cluster, and using a preset encryption algorithm to encrypt the transmitted data across the entire link.

6. The method according to claim 1, characterized in that, The method further includes: real-time monitoring of the link performance indicators of the two cellular network connection links, and dynamic adjustment of the transmission strategy and coding rate based on the link performance indicators using an AI algorithm.

7. A multi-link redundant transmission system for a vehicle-mounted remote communication terminal, characterized in that, The system applied to the multi-link redundant transmission method for an in-vehicle remote communication terminal according to any one of claims 1 to 6, comprises: an in-vehicle remote communication terminal integrating an embedded vehicle-side SDK, a cloud-based operation management platform deploying a cloud-based SDK virtual gateway cluster, and a unified management platform, wherein: The vehicle-mounted remote communication terminal supports dual-SIM dual-pass. Its vehicle-side SDK establishes two cellular network connection links with the cloud SDK virtual gateway cluster simultaneously through the dual-SIM dual-pass architecture. When the vehicle and cloud SDKs send service data, the vehicle-side SDK creates different RTT tunnels according to the service type, intelligently distributes the service data to the corresponding RTT tunnel, and performs intelligent QoS scheduling based on differentiated QoS resource guarantee strategies. The service data to be sent in the RTT tunnel is sent to the cloud operation and management platform simultaneously through the two cellular network connection links. The cloud-based operation and management platform is used to simultaneously receive two service data packets sent through two cellular network connection links via a cloud SDK virtual gateway cluster. Based on a preset message optimization mechanism, it parses the two service data packets to obtain the optimal message, discards redundant messages, and reassembles the optimal message in order to obtain the reassembled service data packets. The unified management platform is used to distribute differentiated QoS resource guarantee policies to vehicle-mounted remote communication terminals, status monitoring, and intelligent operation and maintenance, thereby achieving separation of control and transfer.

8. The system according to claim 7, characterized in that, The vehicle-side SDK has kernel-level network capabilities, including: establishing a secure data channel between user space and kernel space through the TUN virtual network card driver; implementing real-time packet capture, filtering, and labeling based on the Netfilter framework; and implementing intelligent distribution of policy routing based on source IP, application UID, or destination address using Iptables four-table five-chain operations.

9. The system according to claim 7, characterized in that, The cloud-based SDK virtual gateway cluster has the following processing capabilities: unified management of the vehicle-mounted dual-link encrypted tunnel, completion of decryption and protocol conversion; intelligent identification of redundant data packets and sequential reassembly of messages.

10. The system according to claim 7, characterized in that, The unified management platform adopts a control-transfer separation architecture, including: a control plane, used for formulating differentiated QoS resource guarantee policies, issuing security configurations, and monitoring status; and a data plane, used for encryption encapsulation, intelligent routing, and high-speed forwarding.