Method and apparatus for centralized tunnel communication based on mcdata

Abstract

This application provides a centralized tunnel communication method and apparatus based on MCData. The method includes: starting an MCData terminal and accessing the MCData service; obtaining a user configuration containing tunnel service configuration from the MCData service through the MCData terminal, sending a tunnel establishment request to the MCData service according to the tunnel service configuration, and establishing a tunnel link upon response, wherein the tunnel link distinguishes different service types and corresponding priorities; periodically detecting changes in the network address of the MCData terminal and automatically updating the tunnel link; performing cross-terminal service routing based on existing tunnel links and resolution protocols, obtaining data packets from the sending address through the sending MCData terminal, forwarding them to the receiving MCData terminal through the service-corresponding tunnel link, and receiving the data packets through the receiving MCData terminal and forwarding them to the destination address. This application introduces centralized tunnel control and forwarding on the MCData server side, improving scalability and reliability under large-scale concurrency.

Description

Technical Field

[0001] This invention relates to the field of communication technology, and in particular to a centralized tunnel communication method and apparatus based on MCData. Background Technology

[0002] With the increasing demand for highly reliable, low-latency, and secure data communication and service scheduling capabilities from industries such as public security, emergency response, railways, subways, and low-altitude air traffic control, the MCX system based on the 3GPP standard has been gradually applied and promoted in various industry scenarios.

[0003] In related technologies, MCData, as an important component of the MCX system, supports diverse data communication functions such as SMS and file distribution. It can also provide IP data carrying capacity through the MCData IP Connectivity mechanism. This mechanism allows MCData terminal devices to act as gateways, combining the carrying control capabilities of MC services to achieve point-to-point IP sessions with QoS guarantees, and can transparently interconnect with external networks. Tunneling technology achieves transparent transmission across networks and protocols by encapsulating data packets of one network protocol outside of data packets of another network protocol. Its core idea is to encapsulate data streams that cannot be directly routed through tunnels, transmit them in the carrying network, and finally decapsulate them at the destination to restore the original data, thus achieving network interoperability and isolation. The MCData IP Connectivity adopts the GRE-in-UDP tunneling protocol, which adds a layer of UDP encapsulation to the GRE tunnel packets on the basis of the classic GRE tunnel, and has high compatibility, flexibility, low deployment cost, and end-to-end QoS support.

[0004] However, the existing MCData IP Connectivity combined with GRE-in-UDP has the following drawbacks: each pair of devices needs to maintain its own tunnel for data interaction, and the number of tunnels grows exponentially under large-scale multi-terminal concurrent creation, resulting in complex session relationships and a heavy management burden; it cannot perform fine-grained priority differentiation and scheduling for different types of data applications, making it difficult to meet the strict requirements of mission-critical services for bandwidth, latency, and reliability; it lacks link keep-alive and adaptive update mechanisms for scenarios such as terminal IP address changes and multi-network switching; and it lacks centralized management and configuration capabilities, making it difficult to uniformly configure and schedule the service type, number, and priority of tunnels.

[0005] Based on the above analysis of the development status of this technology field, existing technologies lack solutions that introduce centralized tunnel management and forwarding mechanisms, support priority scheduling and resource allocation for service types on the central side, introduce link keep-alive mechanisms and automatic tunnel update mechanisms, and provide unified network address allocation and tunnel configuration capabilities on the central service side. Summary of the Invention

[0006] The purpose of this invention is to provide a centralized tunnel communication method and apparatus based on MCData, aiming to solve the above-mentioned problems in the prior art.

[0007] According to a first aspect of the present invention, a centralized tunnel communication method based on MCData is provided, comprising: Start the MCData terminal and connect to the MCData service; The user configuration, which includes tunnel service configuration, is obtained from the MCData service through the MCData terminal. A tunnel establishment request is sent to the MCData service according to the tunnel service configuration. After the response, a tunnel link is established. The tunnel link distinguishes different service types and their corresponding priorities. Periodically detect changes in the network address of the MCData terminal and automatically update the tunnel link; Cross-terminal service routing is performed based on existing tunnel links and resolution protocols. The sending MCData terminal obtains data packets from the sending address, which are then forwarded to the receiving MCData terminal by the service-corresponding tunnel link. The receiving MCData terminal receives the data packets and forwards them to the destination address.

[0008] According to a second aspect of the present invention, a centralized tunnel communication device based on MCData is provided, comprising: The startup module is used to start the MCData terminal and connect to the MCData service. The link establishment module is used to obtain the user configuration containing the tunnel service configuration from the MCData service through the MCData terminal, send a tunnel establishment request to the MCData service according to the tunnel service configuration, and establish a tunnel link after the response. The tunnel link distinguishes different service types and corresponding priorities. The keep-alive detection module is used to periodically detect changes in the network address of the MCData terminal and automatically update the tunnel link. The application transmission module is used to perform cross-terminal service routing based on existing tunnel links and resolution protocols. It obtains data packets from the sending address through the sending MCData terminal, forwards them to the receiving MCData terminal through the tunnel link corresponding to the service, and then receives the data packets through the receiving MCData terminal and forwards them to the destination address.

[0009] According to a third aspect of the present invention, an electronic device is provided, comprising: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program, when executed by the processor, implements the steps of the centralized tunneling communication method based on MCData as provided in the first aspect of the present disclosure.

[0010] According to a fourth aspect of the present invention, a computer-readable storage medium is provided, on which an implementation program for information transmission is stored, which, when executed by a processor, implements the steps of the centralized tunnel communication method based on MCData provided in the first aspect of the present disclosure.

[0011] The technical solution provided by this invention includes the following beneficial effects: Centralized tunnel control and forwarding are introduced at the MCData server, significantly reducing the number of tunnels, lowering system complexity, and improving scalability and reliability under large-scale concurrency; tunnel links differentiate between different service types and corresponding priorities to meet critical service requirements; network address changes of MCData terminals are periodically detected, and tunnel links are automatically updated to ensure communication continuity and stability in multiple network environments such as public networks, private networks, Wi-Fi, and satellite; and service configuration and virtual address allocation are uniformly provided at the MCData server to avoid conflicts.

[0012] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit this disclosure. Attached Figure Description

[0013] To more clearly illustrate the technical solutions in one or more embodiments of this specification or in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in this specification. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0014] Figure 1 This is a flowchart of a centralized tunnel communication method based on MCData according to an embodiment of the present invention; Figure 2 This is a schematic diagram of MCData configuration download according to an embodiment of the present invention; Figure 3 This is a schematic diagram illustrating the MCData IP Connectivity tunnel negotiation and establishment according to an embodiment of the present invention; Figure 4 This is a schematic diagram of tunnel link keep-alive and automatic tunnel update according to an embodiment of the present invention; Figure 5 This is a schematic diagram of the end-to-end flow according to an embodiment of the present invention; Figure 6 This is a schematic diagram of the centralized tunnel networking framework according to an embodiment of the present invention; Figure 7 This is a schematic diagram of the centralized tunnel communication implementation framework according to an embodiment of the present invention; Figure 8This is a schematic diagram of a centralized tunnel communication device based on MCData according to an embodiment of the present invention; Figure 9 This is a schematic diagram of an electronic device according to an embodiment of the present invention. Detailed Implementation

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

[0016] Method Example 1 According to an embodiment of the present invention, a centralized tunnel communication method based on MCData is provided. Figure 1 This is a flowchart of a centralized tunnel communication method based on MCData according to an embodiment of the present invention, such as... Figure 1 As shown, the centralized tunnel communication method based on MCData according to an embodiment of the present invention specifically includes: In step S110, the MCData terminal is started and the MCData service is accessed, specifically including: Once the MCData terminal starts up, it will connect to the MCData service according to the 3GPP MCData standard process. The connection process may include authentication, registration, service authorization, and configuration subscription to complete the initial interaction with MCData.

[0017] In step S120, the user configuration containing the tunnel service configuration is obtained from the MCData service through the MCData terminal. A tunnel establishment request is sent to the MCData service according to the tunnel service configuration. Upon response, a tunnel link is established. The tunnel link distinguishes different service types and corresponding priorities, specifically including: The tunnel service configuration is described by a predefined list of tunnel services; The tunnel service configuration fields include a tunnel service identifier to distinguish different service types, a global service application virtual network segment to identify the service address space, and a terminal service application virtual network segment allocated to the MCData terminal in the address space. To achieve centralized management and configuration of tunnel links, in this embodiment of the invention, the MCData user configuration... <mcdata-user-profile>Element <onnetwork>Under element, through <anyext>Extended element import <tunnelservices>The `<tunnel>` element is used to define the list of tunnel services available to each terminal. <tunnelservices>An element can contain several <tunnel>The format of a child element is shown below: <tunnelservices> <tunnel id="sip:tunnel-cmd@mnc000.mcc460.3gppnetwork.org" ue-net="10.0.0.0 / 24" service-net="10.0.0.0 / 16" / > <tunnel id="sip:tunnel-video@mnc000.mcc460.3gppnetwork.org" ue-net="10.1.0.0 / 24" service-net="10.1.0.0 / 16" / > < / tunnelservices> id: Tunnel service identifier, used to distinguish different service types. Tunnels with the same service identifier between MCData terminals and MCData services can form a centralized communication network to realize cross-terminal data interaction; cmd represents control services, and video represents audio and video services. service-net: A global business application virtual network segment used to identify the virtual address space used by business applications under the tunnel network; ue-net: Terminal business application virtual network segment, which is a subnet of the global business application virtual network segment. Each terminal is assigned a different subnet segment for virtual address mapping of terminal-side business applications to avoid address conflicts between different terminals.

[0018] By adding the above service configuration information to the MCData user configuration, the terminal can obtain the definition of available tunnels during the registration phase, thereby realizing unified tunnel configuration and centralized management, and providing a configuration basis for service isolation and cross-terminal interoperability based on virtual network segment division.

[0019] Figure 2 This is a schematic diagram of MCData configuration download according to an embodiment of the present invention, as shown below. Figure 2 The image shows the MCData configuration download process.

[0020] For each piece of information in the tunnel service configuration, a tunnel establishment request, namely a SIP INVITE request, is initiated to the MCData service through the MCData terminal. The session type of the tunnel establishment request is to establish a data channel one-to-one-ipconn. The target ID in the message body is set to the tunnel service identifier, and the terminal-side tunnel IP address and port information are carried. After confirming the session type and target ID through the MCData service, if the session type is confirmed to be one-to-one-ipconn and the target ID is a valid tunnel service identifier, the centralized tunnel negotiation process is initiated, and a tunnel establishment response is sent to the MCData terminal. The tunnel establishment response message body carries the service-side tunnel IP address and port information. Based on the tunnel service identifier, the service type and corresponding priority are obtained, and a dedicated bearer establishment request with the corresponding priority is sent to the 3GPP core network through the MCData service. After the parameters are negotiated between the two parties, a GRE-in-UDP tunnel link is established based on the tunnel IP address and port information of the terminal side and the service side respectively. After the virtual tunnel device is initialized, IP data packets can be encapsulated and decapsulated through the tunnel.

[0021] Through configuration and link establishment, the MCData system establishes a centralized tunnel negotiation mechanism based on SIP / SDP, and completes dedicated carrier establishment by interacting with the core 3GPP network in conjunction with tunnel priority configuration, thereby achieving differentiated priority protection and improving transmission reliability and service quality in multi-service concurrent scenarios.

[0022] Figure 3 This is a schematic diagram of MCData IP Connectivity tunnel negotiation and establishment according to an embodiment of the present invention, as shown below. Figure 3 As shown, the MCData IP Connectivity tunnel negotiation and establishment process is illustrated.

[0023] In step S130, the network address changes of the MCData terminal are periodically detected, and the tunnel link is automatically updated, specifically including: The GRE-in-UDP tunnel link itself does not have the ability to adapt to changes in NAT port mapping and network address changes, making it difficult to directly adapt to complex network environments with multiple standards such as emergency response, low-altitude, railway, and public networks. In order to ensure the continuity and reliability of tunnel communication based on MCData IPConnectivity, this embodiment of the invention defines a link keep-alive and tunnel automatic update mechanism.

[0024] After the tunnel is established, the MCData terminal periodically sends heartbeat keep-alive requests to the MCData service listening side using the tunnel IP address and port information it is listening to on its own side. It uses a preset field as the magic header (MCKP, MC Keepalive Protocol) of the heartbeat keep-alive message. In this embodiment of the invention, the magic header is 0x4D434B50, so as to distinguish it from GRE-in-UDP data packets. The magic header is followed by comma-separated text parameters. The heartbeat keep-alive request message includes the message sequence number, tunnel service identifier, and MCData terminal user ID. When the MCData service receives a heartbeat keep-alive request, it confirms that the tunnel link is active and returns a heartbeat keep-alive response message. The heartbeat keep-alive response message includes a message sequence number that matches the request, a tunnel service identifier, and the source IP and source port of the heartbeat packet observed by the service side. When the MCData terminal receives the heartbeat keep-alive response message, it compares it with the source IP and source port obtained from the previous feedback. If they are inconsistent, it is determined that the network address has changed, that is, NAT port drift or network switching, and a tunnel establishment request is resent to the MCData service to update the tunnel link.

[0025] In this embodiment of the invention, the tunnel information update request is made by sending a SIP re-INVITE request in the existing tunnel negotiation INVITE session after the MCData terminal detects a change in the network address, and carrying the updated local tunnel IP and port information in the SDP. When the MCData service receives the re-INVITE tunnel information update request, it returns a 200 OK update response to the MCData terminal. At the same time, it extracts the terminal tunnel IP and port information from the requested SDP message body and updates the GRE-in-UDP tunnel peer parameter configuration in real time, so that the new external tunnel mapping takes effect immediately.

[0026] By using a custom lightweight MCKP keep-alive mechanism and SIP re-INVITE-based in-session parameter updates, we can quickly detect and repair NAT mapping changes and multi-network switching, keeping the tunnel continuously available without rebuilding the session, thereby significantly improving communication continuity and reliability in complex mobile scenarios.

[0027] Figure 4 This is a schematic diagram of tunnel link keep-alive and automatic tunnel update according to an embodiment of the present invention, as shown below. Figure 4 As shown, the tunnel link keep-alive and tunnel automatic update process are illustrated.

[0028] In step S140, cross-terminal service routing is performed based on the existing tunnel link and resolution protocol. The sending MCData terminal obtains the data packet from the sending address, which is then forwarded to the receiving MCData terminal by the service-corresponding tunnel link. The receiving MCData terminal receives the data packet and forwards it to the destination address. Specifically, this includes: Once the tunnel is established, the MCData terminal and MCData service enable IP forwarding functionality, acting as intermediate routing devices for IP packets between cross-terminal business applications. They configure data packet routing and address translation rules to facilitate data traffic between various business applications under the same tunnel service through the established tunnel. In practical applications of forwarding, the roles of the MCData terminal and the MCData service are as follows: MCData terminal: Based on the global service application virtual network segment service-net in the user configuration, it routes traffic destined for this network segment to the corresponding tunnel, and establishes address translation rules based on the terminal's service application virtual network segment ue-net, specifically including: Configure the identification information of the business application, including IP, protocol (UDP / TCP) or port, specify its tunnel service identifier, and allocate a virtual IP address for the business application from the business application virtual network segment; when receiving an IP packet from the terminal network, identify the corresponding business application based on the source IP, protocol or port of the packet, determine its matching tunnel, route the IP packet to the tunnel, and perform SNAT on the source IP address to convert it to the allocated virtual IP address of the business application; when receiving an IP packet after the tunnel is deblocked, use the destination IP of the packet as the virtual IP address of the business application, find the corresponding business application, perform DNAT on the destination IP address to convert it to the actual address of the business application, and forward it to the target business application.

[0029] MCData service: When establishing a terminal tunnel, it adds routing rules based on the terminal service application virtual network segment in the tunnel configuration, and routes data packets destined for that network segment to the corresponding terminal tunnel.

[0030] The specific application process is as follows: The address translation rules are obtained as the resolution protocol, which includes SNAT mapping and DNAT mapping. Based on the virtual network segment of the terminal business application, the MCData terminal allocates the application virtual address to the corresponding business application in advance. The MCData terminal receives IP packets sent from the IP address of the sending service. The current IP packet includes the IP address of the sending service and the destination virtual address. Based on the IP packet, the service type is identified, and SNAT mapping is performed on the IP address of the sending service to obtain the corresponding sending virtual address. The IP packet is then re-encapsulated and forwarded to the MCData service by the tunnel link between the MCData terminal and the MCData service corresponding to the service type. The MCData service parses IP packets, obtains the destination virtual address, determines the tunnel link corresponding to the service type, re-encapsulates the IP packets, and forwards them to the receiving MCData terminal via the tunnel link corresponding to the service type between the MCData service and the receiving MCData terminal. The receiving MCData terminal performs DNAT mapping on the destination virtual address to obtain the corresponding receiving service terminal IP address, and then forwards the final IP data packet to the receiving service terminal IP address, where the receiving service terminal IP address serves as the destination address.

[0031] In this embodiment of the invention, the sending service application 1 on the MCData terminal 1 side and the receiving service application 2 on the MCData terminal 2 side complete IP data interaction. The network IP addresses of the MCData service, MCData terminal 1, and MCData terminal 2 are 50.114.129.100, 50.114.129, 101, and 50.114.129.102, respectively. The tunnel information received by MCData terminal 1 is as follows: the global service application virtual network segment is 10.0.0.0 / 8, and the terminal service application virtual network segment is 10.0.0.0 / 24; The tunnel information received by MCData terminal 2 is as follows: the global service application virtual network segment is 10.0.0.0 / 8, and the terminal service application virtual network segment is 10.0.1.0 / 24; The global service application virtual network segment of tunnels of the same service type is the same, but they belong to different terminals. Therefore, the terminal service application virtual network segment is set differently. In the embodiment of the present invention, the first octet distinguishes the service type, and the second and third octets distinguish different terminals. The two can jointly determine a unique tunnel link. The sending service terminal IP address is 192.168.1.2, and the virtual address assigned to it by MCData terminal 1 is 10.0.0.2. The receiving service terminal IP address is 192.168.1.3, and the virtual address assigned to it by MCData terminal 2 is 10.0.1.3. The fourth octet represents the service terminal managed by the MCData terminal. The specific transmission process is as follows: Application 1 learns in advance that the virtual address of Application 2 is 10.0.1.3, sends IP packets to this address, and sets the default gateway to MCData terminal 1; MCData terminal 1 receives an IP data packet and identifies the service application. It performs SNAT mapping on the source address to the virtual address 10.0.0.2 of service application 1 and routes the data packet to the corresponding tunnel. The GRE-in-UDP tunnel encapsulates the service data packet with GRE+UDP and transmits it to the MCData service in the wireless network. After receiving the tunnel data packet, the MCData service decapsulates it to obtain the original data packet. Based on the destination address 10.0.1.3, it matches the virtual network segment of the terminal service application of MCData terminal 2 and forwards the data packet to the corresponding tunnel of terminal 2, where it is encapsulated with GRE+UDP again for transmission. After receiving the tunnel data packet, MCData terminal 2 decapsulates it to obtain the original data packet with a destination address of 10.0.1.3. It matches the information of service application 2, performs DNAT to convert the destination address to 192.168.1.3, and forwards it to service application 2.

[0032] Figure 5 This is a schematic diagram of the end-to-end flow according to an embodiment of the present invention, as shown below. Figure 5 As shown, this illustrates the data transmission process between business application 1 and application business 2.

[0033] The above technical solutions of the embodiments of the present invention will be illustrated with reference to the following accompanying drawings.

[0034] Figure 6 This is a schematic diagram of the centralized tunnel networking framework according to an embodiment of the present invention, as shown below. Figure 6 As shown, in the centralized tunnel communication network based on MCDataIP Connectivity, the MCData terminal acts as the IP communication gateway, and the MCData service acts as the central tunnel management and forwarding node. The overall network framework is as follows: (1) MCData terminal Access and Configuration Acquisition: When the MCData terminal device starts up, it accesses the MCData service through a wireless network (such as public network, 5G private network, Wi-Fi, satellite network, etc.) according to the MCData standard, and obtains the tunnel service configuration information of MCData IPConnectivity from the MCData service; Tunnel establishment: Based on the obtained tunnel service configuration information, the terminal initiates several tunnel negotiation and establishment requests through the MCData IP Connectivity process and completes the tunnel establishment. Different tunnels can be used to carry different types of business application traffic. Gateway function: As an IP communication gateway for business applications, the MCData terminal can distinguish the service type based on the IP address or port information of the data packet and introduce it into the corresponding tunnel; when a data packet is received from the tunnel, the terminal completes the decapsulation and forwards the original IP data packet to the corresponding local business application.

[0035] (2) MCData service User and Tunnel Configuration Service: The MCData service includes user configuration functionality, which can add tunnel service configuration information to each device. This information includes parameters such as tunnel service identifier, terminal service application virtual network segment, global service application virtual network segment, and tunnel link priority, which can be configured through a centralized management page. Tunnel establishment and QoS guarantee: The MCData service receives tunnel establishment requests from each terminal and establishes a tunnel communication link with them. Each MCData terminal and the MCData service establish different virtual tunnels according to different service types. At the same time, it can interact with the core network through the 5G N5 or LTE Rx interface to apply for radio bearer resources according to the tunnel priority, thereby ensuring the quality of service of service traffic in the tunnel. Traffic routing and forwarding: As the central node of the tunnel, the MCData service undertakes the function of cross-tunnel traffic forwarding; based on the virtual network segment information of each terminal's business application, it identifies and schedules the received tunnel traffic and forwards it to the corresponding tunnel of the target terminal, so as to realize the interoperability of services between different terminals.

[0036] Figure 7 This is a schematic diagram of the centralized tunnel communication implementation framework according to an embodiment of the present invention, as shown below. Figure 7 The diagram illustrates the complete process of implementing centralized tunnel communication based on MCData IP Connectivity: (1) Start MCData terminal When the MCData terminal device starts up, it accesses the MCData service according to the 3GPP MCData standard process. The access process may include authentication, registration, service authorization, and configuration subscription to complete the initial interaction with the MCData service.

[0037] (2) MCData configuration download After completing the access process, the MCData terminal obtains the user configuration from the MCData service, which includes tunnel service configuration information. The tunnel service configuration information may include the tunnel service identifier, the virtual network segment of the terminal business application, the virtual network segment of the global business application, and the tunnel link priority.

[0038] (3) Initiate the IP Connectivity tunnel negotiation and establishment process After parsing the tunnel service configuration information, the MCData terminal initiates the tunnel establishment process, which includes: the MCData terminal uses the IP Connectivity protocol to send a tunnel negotiation request to the MCData service, and the request carries the tunnel service identifier and the terminal tunnel network information; After receiving the request, the MCData service performs authentication and configuration matching based on the tunnel service identifier and returns the corresponding service tunnel network information; the terminal and the service complete the tunnel establishment based on the network parameters in the negotiation result.

[0039] (4) Initiate tunnel link keep-alive and tunnel automatic update process After the tunnel is established, the MCData terminal initiates the tunnel link keep-alive process to monitor the tunnel status and network environment in real time. In scenarios such as changes in the network NAT environment or switching of access networks, the MCData terminal can automatically trigger the tunnel update process and complete the tunnel parameter update through an automatic negotiation mechanism, thereby ensuring the continuity and stability of services.

[0040] (5) IP packet routing and network address translation After the tunnel is established, the MCData terminal and MCData service match the corresponding tunnel configuration information according to the tunnel service identifier and establish data packet routing and address translation rules. MCData Terminal: Based on the global business application virtual network segment, it routes traffic destined for that network segment to the corresponding tunnel; based on the terminal's business application virtual network segment, it establishes address translation rules to map data traffic from different business applications to the corresponding tunnels, thereby achieving the binding between virtual addresses and business applications; MCData service: Establishes routing rules based on the virtual network segment of the terminal business application, and forwards data packets destined for that network segment to the corresponding terminal tunnel.

[0041] (6) Access the service After the tunnel is established and the routing rules are configured, business applications under each MCData terminal network can achieve IP data communication across terminal networks through the centralized tunnel.

[0042] Method Example 2 In low-altitude aircraft, the communication network environment is complex, often requiring simultaneous access to multiple standards such as public networks, private low-altitude networks, and satellite networks. This invention addresses this by installing MCData terminals on the aircraft and deploying MCData services in the backend, combined with the centralized tunneling communication method based on MCData IP Connectivity proposed in this paper.

[0043] It can be achieved: It supports data interoperability between airborne equipment such as flight control devices and cameras and backend low-altitude management services, and can be extended to direct data interaction between aircraft. As the flight altitude changes, the terminal can dynamically switch between public networks, private networks, and satellite links. Combined with heartbeat keep-alive and automatic tunnel update mechanisms, it ensures link continuity and stability. For different services such as control commands, video transmission, and status reporting, the system can allocate differentiated service priorities and establish dedicated tunnels with different QoS levels to ensure priority protection for critical services.

[0044] Method Example 3 With the advancement of MCX and FRMCS systems, MCX-based vehicle radios will be gradually deployed and popularized in rail transit fields such as railways and subways. In addition to providing traditional voice, video, and SMS functions, vehicle radios can also expand MCData capabilities, employing the centralized tunneling communication method based on MCData IP Connectivity as described in this invention.

[0045] It can be achieved: The system enables simultaneous transmission of multiple services, such as vehicle control, dispatching commands, and video surveillance, on a unified wireless bearer. Through a centralized tunnel negotiation mechanism, different services are mapped to tunnel links with priority distinctions, ensuring the real-time performance and reliability of critical services such as dispatching and control. By leveraging the system's centralized scheduling and tunnel management capabilities, the system achieves unified access and differentiated QoS guarantees for a large number of vehicle-mounted terminals, thereby improving overall operational security and communication efficiency.

[0046] In summary, to address the existing problems, this invention proposes a centralized tunnel communication method based on MCData. This method introduces centralized tunnel control and forwarding at the MCData server, significantly reducing the number of tunnels, lowering system complexity, and improving scalability and reliability under large-scale concurrency. Tunnel links differentiate between different service types and their corresponding priorities, and are linked with core network dedicated bearer policies to achieve differentiated QoS guarantees for control, status, and video services, meeting critical business requirements. Periodic detection of network address changes at MCData terminals, through extended heartbeat and session refresh mechanisms, automatically updates tunnel links to ensure communication continuity and stability in multiple network environments such as public networks, private networks, Wi-Fi, and satellite. Unified service configuration and virtual address allocation are provided at the MCData server to avoid conflicts and support centralized policies and operation and maintenance management, improving system controllability.

[0047] Device Examples According to an embodiment of the present invention, a centralized tunnel communication device based on MCData is provided. Figure 8 This is a schematic diagram of a centralized tunnel communication device based on MCData according to an embodiment of the present invention, as shown below. Figure 8 As shown, the centralized tunnel communication device based on MCData according to an embodiment of the present invention specifically includes: Startup module 80 is used to start the MCData terminal and access the MCData service, specifically for: Once the MCData terminal is started, it will be connected to the MCData service according to the 3GPP MCData standard procedure.

[0048] Link establishment module 82 is used to obtain user configuration containing tunnel service configuration from MCData service through MCData terminal, send tunnel establishment request to MCData service according to tunnel service configuration, and establish tunnel link after response. The tunnel link distinguishes different service types and corresponding priorities, and is specifically used for: The tunnel service configuration is described by a predefined list of tunnel services; The tunnel service configuration fields include a tunnel service identifier to distinguish different service types, a global service application virtual network segment to identify the service address space, and a terminal service application virtual network segment allocated to the MCData terminal in the address space.

[0049] For each piece of information in the tunnel service configuration, a tunnel establishment request is initiated to the MCData service through the MCData terminal. The session type of the tunnel establishment request is to establish a data channel. The target ID in the message body is set to the tunnel service identifier, and the terminal-side tunnel IP address and port information are carried. After confirming the session type and target ID through the MCData service, a tunnel establishment response is sent to the MCData terminal. The tunnel establishment response message body carries the service-side tunnel IP address and port information. Based on the tunnel service identifier, the service type and corresponding priority are obtained, and a dedicated carrier establishment request with the corresponding priority is sent to the 3GPP core network through the MCData service. A GRE-in-UDP tunnel link is established based on the tunnel IP address and port information of the terminal and the server respectively.

[0050] Keep-alive detection module 84 is used to periodically detect changes in the network address of the MCData terminal and automatically update the tunnel link. Specifically, it is used for: Using the tunnel IP address and port information monitored on this side by the MCData terminal, a heartbeat keep-alive request is periodically sent to the MCData service monitoring side. Preset fields are used as the magic header of the heartbeat keep-alive message. The heartbeat keep-alive request message includes the message sequence number, tunnel service identifier and MCData terminal user ID. When the MCData service receives a heartbeat keep-alive request, it confirms that the tunnel link is active and returns a heartbeat keep-alive response message. The heartbeat keep-alive response message includes a message sequence number that matches the request, a tunnel service identifier, and the source IP and source port of the heartbeat packet observed by the service side. When the MCData terminal receives the heartbeat keep-alive response message, it compares it with the source IP and source port obtained from the previous feedback. If they are inconsistent, it is determined that the network address has changed, and a tunnel establishment request is resent to the MCData service to update the tunnel link.

[0051] Application transmission module 86 is used for cross-terminal service routing based on existing tunnel links and resolution protocols. It obtains data packets from the sending address through the sending MCData terminal, forwards them to the receiving MCData terminal via the service-corresponding tunnel link, and then receives and forwards the data packets to the destination address. Specifically, it is used for: The address translation rules are obtained as the resolution protocol, which includes SNAT mapping and DNAT mapping. Based on the virtual network segment of the terminal business application, the MCData terminal allocates the application virtual address to the corresponding business application in advance. The MCData terminal receives IP packets sent from the IP address of the sending service. The current IP packet includes the IP address of the sending service and the destination virtual address. Based on the IP packet, the service type is identified, and SNAT mapping is performed on the IP address of the sending service to obtain the corresponding sending virtual address. The IP packet is then re-encapsulated and forwarded to the MCData service by the tunnel link between the MCData terminal and the MCData service corresponding to the service type. The MCData service parses IP packets, obtains the destination virtual address, determines the tunnel link corresponding to the service type, re-encapsulates the IP packets, and forwards them to the receiving MCData terminal via the tunnel link corresponding to the service type between the MCData service and the receiving MCData terminal. The receiving MCData terminal performs DNAT mapping on the destination virtual address to obtain the corresponding receiving service IP address, and then forwards the final IP data packet to the receiving service IP address as the destination address.

[0052] In summary, to address the existing problems, this invention introduces a centralized tunnel communication device based on MCData. This introduces centralized tunnel control and forwarding at the MCData server, significantly reducing the number of tunnels, lowering system complexity, and improving scalability and reliability under large-scale concurrency. The tunnel links differentiate between different service types and their corresponding priorities, and are linked with the core network's dedicated bearer strategy to achieve differentiated QoS guarantees for control, status, and video services, meeting critical business requirements. Periodic detection of network address changes at the MCData terminal, through extended heartbeat and session refresh mechanisms, automatically updates the tunnel links to ensure communication continuity and stability in multiple network environments such as public networks, private networks, Wi-Fi, and satellite. Unified service configuration and virtual address allocation are provided at the MCData server to avoid conflicts and support centralized policies and operation and maintenance management, improving system controllability.

[0053] Electronic device examples Figure 9 This is a schematic diagram of an electronic device according to an embodiment of the present invention. The electronic device 900 may include at least one processor 910 and a memory 920. The processor 910 can execute instructions stored in the memory 920. The processor 910 is communicatively connected to the memory 920 via a data bus. In addition to the memory 920, the processor 910 can also be communicatively connected to an input device 930, an output device 940, and a communication device 950 via the data bus.

[0054] Processor 910 can be any conventional processor, such as a commercially available CPU. Processors may also include graphics processing units (GPUs), field-programmable gate arrays (FPGAs), systems on chips (SOCs), application-specific integrated circuits (ASICs), or combinations thereof.

[0055] The memory 920 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk or optical disk.

[0056] In this embodiment of the present disclosure, the memory 920 stores executable instructions, and the processor 910 can read the executable instructions from the memory 920 and execute the instructions to implement all or part of the steps of any of the MCData-based centralized tunnel communication methods in the exemplary embodiments described above.

[0057] Computer-readable storage medium embodiments In addition to the methods and apparatus described above, exemplary embodiments of this disclosure may also be a computer program product or a computer-readable storage medium storing the computer program product, the computer product including computer program instructions that can be executed by a processor to implement all or part of the steps described in any of the MCData-based centralized tunneling communication methods in the exemplary embodiments described above.

[0058] Computer program products can be written in any combination of one or more programming languages ​​to perform the operations of the embodiments of this application. Programming languages ​​include object-oriented programming languages ​​such as Java and C++, as well as conventional procedural programming languages ​​such as C or similar languages, and scripting languages ​​(e.g., Python). The program code can be executed entirely on the user's computing device, partially on the user's device, as a standalone software package, partially on the user's computing device and partially on a remote computing device, or entirely on a remote computing device or server.

[0059] Computer-readable storage media may be any combination of one or more readable media. A readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may be, for example,, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of readable storage media include: static random access memory (SRAM) having one or more electrically connected wires; electrically erasable programmable read-only memory (EEPROM); erasable programmable read-only memory (EPROM); programmable read-only memory (PROM); read-only memory (ROM); magnetic storage; flash memory; magnetic disk or optical disk; or any suitable combination thereof.

[0060] 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; 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 or all 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.< / tunnel> < / tunnelservices> < / tunnelservices> < / anyext> < / onnetwork>

Claims

1. A centralized tunnel communication method based on MCData, characterized in that, include: Start the MCData terminal and connect to the MCData service; The MCData terminal obtains user configuration containing tunnel service configuration from the MCData service, sends a tunnel establishment request to the MCData service according to the tunnel service configuration, and establishes a tunnel link after responding. The tunnel link distinguishes different service types and corresponding priorities. The network address of the MCData terminal is periodically detected to change, and the tunnel link is automatically updated. Cross-terminal service routing is performed based on existing tunnel links and resolution protocols. The sending MCData terminal obtains data packets from the sending address, which are then forwarded to the receiving MCData terminal by the service-corresponding tunnel link. The receiving MCData terminal receives the data packets and forwards them to the destination address.

2. The method according to claim 1, characterized in that, The specific steps of starting the MCData terminal and accessing the MCData service include: after the MCData terminal is started, accessing the current MCData terminal to the MCData service according to the 3GPP MCData standard procedure.

3. The method according to claim 1, characterized in that, The step of obtaining the user configuration, which includes the tunnel service configuration, from the MCData service via the MCData terminal specifically includes: The tunnel service configuration is described by a predefined list of tunnel services; The tunnel service configuration fields include a tunnel service identifier for distinguishing different service types, a global service application virtual network segment for identifying the service address space, and a terminal service application virtual network segment allocated to the MCData terminal in the address space.

4. The method according to claim 1, characterized in that, The step of sending a tunnel establishment request to the MCData service according to the tunnel service configuration, and establishing a tunnel link after responding specifically includes: For each piece of information in the tunnel service configuration, a tunnel establishment request is initiated to the MCData service through the MCData terminal. The session type of the tunnel establishment request is to establish a data channel. The target ID in the message body is set to the tunnel service identifier, and the terminal-side tunnel IP address and port information are carried. After confirming the session type and target ID through the MCData service, a tunnel establishment response is sent to the MCData terminal. The tunnel establishment response message body carries the service-side tunnel IP address and port information. Based on the tunnel service identifier, the service type and corresponding priority are obtained, and a dedicated carrier establishment request with the corresponding priority is sent to the 3GPP core network through the MCData service. A GRE-in-UDP tunnel link is established based on the tunnel IP address and port information of the terminal and the server respectively.

5. The method according to claim 1, characterized in that, The periodic detection of network address changes of the MCData terminal and the automatic updating of the tunnel link specifically include: Using the tunnel IP address and port information monitored on this side by the MCData terminal, a heartbeat keep-alive request is periodically sent to the MCData service monitoring side. Preset fields are used as the magic header of the heartbeat keep-alive message. The heartbeat keep-alive request message includes the message sequence number, tunnel service identifier and MCData terminal user ID. When the MCData service receives the heartbeat keep-alive request, it confirms that the tunnel link is active and returns a heartbeat keep-alive response message, wherein the heartbeat keep-alive response message includes a message sequence number matching the request, the tunnel service identifier, and the source IP and source port of the heartbeat packet observed by the service side; When the MCData terminal receives the heartbeat keep-alive response message, it compares it with the source IP and source port obtained from the previous feedback. If they are inconsistent, it is determined that the network address has changed, and the terminal resends the tunnel establishment request to the MCData service to update the tunnel link.

6. The method according to claim 1, characterized in that, The cross-terminal service routing based on existing tunnel links and resolution protocols, which involves the sending MCData terminal obtaining data packets from the sending address, forwarding them to the receiving MCData terminal via the service-corresponding tunnel link, and then the receiving MCData terminal receiving the data packets and forwarding them to the destination address, specifically includes: The address translation rules are obtained as the resolution protocol, wherein the resolution protocol includes SNAT mapping and DNAT mapping, and the application virtual address is pre-assigned to the corresponding service application through the MCData terminal based on the terminal service application virtual network segment; The MCData terminal receives IP packets sent from the IP address of the sending service terminal. The current IP packet includes the IP address of the sending service terminal and the destination virtual address. The service type is identified according to the IP packet. SNAT mapping is performed on the IP address of the sending service terminal to obtain the corresponding sending virtual address and re-encapsulate the IP packet. The packet is then forwarded to the MCData service by the tunnel link between the MCData terminal and the MCData service corresponding to the service type. The MCData service parses IP packets, obtains the destination virtual address, determines the tunnel link corresponding to the service type, re-encapsulates the IP packets, and forwards them to the receiving MCData terminal via the tunnel link corresponding to the service type between the MCData service and the receiving MCData terminal. The receiving MCData terminal performs DNAT mapping on the destination virtual address to obtain the corresponding receiving service terminal IP address, and then forwards the final IP data packet to the receiving service terminal IP address.

7. A centralized tunnel communication device based on MCData, characterized in that, include: The startup module is used to start the MCData terminal and connect to the MCData service. The link establishment module is used to obtain user configuration containing tunnel service configuration from the MCData service through the MCData terminal, send a tunnel establishment request to the MCData service according to the tunnel service configuration, and establish a tunnel link after responding. The tunnel link distinguishes different service types and corresponding priorities. The keep-alive detection module is used to periodically detect changes in the network address of the MCData terminal and automatically update the tunnel link. The application transmission module is used to perform cross-terminal service routing based on existing tunnel links and resolution protocols. It obtains data packets from the sending address through the sending MCData terminal, forwards them to the receiving MCData terminal through the tunnel link corresponding to the service, and then receives the data packets through the receiving MCData terminal and forwards them to the destination address.

8. The apparatus according to claim 7, characterized in that, The application transmission module is specifically used for: The address translation rules are obtained as the resolution protocol, wherein the resolution protocol includes SNAT mapping and DNAT mapping, and the application virtual address is pre-assigned to the corresponding service application through the MCData terminal based on the terminal service application virtual network segment; The MCData terminal receives IP packets sent from the IP address of the sending service terminal. The current IP packet includes the IP address of the sending service terminal and the destination virtual address. The service type is identified according to the IP packet. SNAT mapping is performed on the IP address of the sending service terminal to obtain the corresponding sending virtual address and re-encapsulate the IP packet. The packet is then forwarded to the MCData service by the tunnel link between the MCData terminal and the MCData service corresponding to the service type. The MCData service parses IP packets, obtains the destination virtual address, determines the tunnel link corresponding to the service type, re-encapsulates the IP packets, and forwards them to the receiving MCData terminal via the tunnel link corresponding to the service type between the MCData service and the receiving MCData terminal. The receiving MCData terminal performs DNAT mapping on the destination virtual address to obtain the corresponding receiving service terminal IP address, and then forwards the final IP data packet to the receiving service terminal IP address.

9. An electronic device, characterized in that, include: A memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program, when executed by the processor, implements the steps of the centralized tunneling communication method based on MCData as described in any one of claims 1 to 6.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores an implementation program for information transmission, which, when executed by a processor, implements the steps of the centralized tunnel communication method based on MCData as described in any one of claims 1 to 6.

Images