A multi-operator dual-domain private network access method and system based on DNS directional resolution
By working together with DNS directed resolution and line policy control modules, the complexity of enterprise terminal configuration and uncontrollable access paths in multi-carrier 5G dual-domain private network scenarios are solved, realizing unified access and intelligent path selection for multi-carrier access, and improving access reliability and continuity.
Patent Information
- Application Number
- CN202611091629.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-07-22
- Publication Date
- 2026-11-17
AI Technical Summary
In multi-carrier 5G dual-domain private network scenarios, enterprise terminal configurations are complex, access paths are uncontrollable, policy adjustment costs are high, and security boundaries are dispersed. Existing technologies have failed to achieve a coordinated process for unified access, DNS directed resolution, proxy forwarding, line policy control, line isolation, and secure access control across multiple carriers.
By using DNS directed resolution, domain name resolution requests from enterprise terminals are directed to proxy forwarding nodes. Combined with the line policy control module, path selection is coordinated to achieve unified access and intelligent path selection for multi-carrier dual-domain private networks. This includes the collaborative work of DNS resolution scheduling nodes, proxy forwarding nodes, and line policy control modules.
It enables unified access to 5G dual-domain private networks from multiple operators, reduces the cost of differentiated terminal configuration and multi-point maintenance, improves the reliability and continuity of access paths, and ensures controlled access paths for enterprise business requests and automated fault switching.
Smart Images

Figure CN123124046A_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of communication network technology, specifically to a method and system for accessing multi-carrier dual-domain private networks based on DNS directed resolution. Background Technology
[0002] As 5G private networks are increasingly used in government, healthcare, campuses, industrial parks, and enterprise branch access scenarios, enterprise users typically have two types of access needs: one is accessing ordinary internet resources, and the other is accessing the enterprise intranet or target business systems through controlled paths. 5G dual-domain private networks, through service offloading and access isolation, enable enterprise terminals to obtain relatively stable and secure enterprise business access capabilities in a mobile network environment.
[0003] In actual deployment, enterprises may simultaneously utilize 5G dual-domain private network capabilities provided by different operators. The access boundaries, routing policies, resolution policies, address planning, and fault handling methods differ between operators' links. If enterprises maintain multiple sets of access points, DNS policies, proxy rules, and routing configurations, it will lead to problems such as complex terminal configurations, uncontrollable access paths, high policy adjustment costs, and fragmented security boundaries.
[0004] In the field of 5G private networks, relevant technical solutions have been proposed. For example, CN116193456A discloses an access management and control system for 5G campus private networks, which mainly realizes campus service offloading, DNS management, and private network access control through user plane functions and edge computing environments. However, it only targets a single campus 5G private network environment and fails to solve the coordination problem of multi-operator access. CN116112984B discloses a 5G wireless network converged management and control scheme, which uses offloading devices, access gateways, and controllers to offload and control service subscription information and authorized application lists, thereby enabling terminal access requests to... While existing solutions utilize dedicated or default service channels, their focus is primarily on traffic distribution at the user service subscription level, neglecting unified access and proxy forwarding coordination across multi-carrier scenarios. CN118449899A discloses an automatic switching method for establishing primary / backup access paths between 5G commercial private networks and traditional MPLS networks. This method achieves fault switching through routing policies and link monitoring logic configured on the customer-side equipment. However, it only addresses the dual-link primary / backup switching issue, failing to cover unified access across multi-carrier 5G dual-domain private networks or establish a closed loop between DNS directed resolution, proxy forwarding, line isolation, and secure access control. Therefore, existing solutions revolve around a single carrier, a single campus, or a single private network channel, failing to treat unified access, DNS directed resolution, proxy forwarding, line policy control, line isolation, fault switching, and secure access control across multi-carrier 5G dual-domain private networks as an integrated collaborative process. This results in fragmented multi-carrier access, high enterprise-side configuration costs, disconnect between DNS resolution and service access paths, lack of coordination between proxy forwarding and line policies, and fragmented secure access control. Summary of the Invention
[0005] To address the aforementioned issues, this invention proposes a method and system for accessing multi-carrier dual-domain private networks based on DNS directed resolution. By using DNS directed resolution, private network service requests are directed to a proxy forwarding node. The proxy forwarding node and the line policy control module collaboratively select the path, thereby achieving unified access and intelligent path selection for multi-carrier dual-domain private networks.
[0006] On the one hand, a multi-carrier dual-domain private network access method based on DNS directed resolution includes:
[0007] S1, the enterprise terminal initiates a domain name resolution request to the enterprise-side access node, the domain name resolution request carrying the target domain name to be resolved and the target business system identifier;
[0008] S2, the enterprise-side access node sends the resolution request to the DNS resolution scheduling node. The DNS resolution scheduling node determines whether the resolution request belongs to the enterprise private network controlled business based on the target business system identifier and the preset business domain name policy set, and obtains the enterprise terminal source information and business type corresponding to the resolution request.
[0009] S3, if the resolution request belongs to the enterprise private network controlled service, the DNS resolution scheduling node returns the abstract access entry of the proxy forwarding node, so that the enterprise terminal can subsequently initiate a service request to the abstract access entry and enter S4; if it does not belong to the enterprise private network controlled service, the domain name resolution request enters the normal resolution path.
[0010] S4, the enterprise terminal initiates a business request to the proxy forwarding node based on the abstract access entry, and the proxy forwarding node establishes a forwarding relationship based on the target business system identifier, access policy and connection status;
[0011] S5, the line policy control module selects the multi-carrier private network access path based on the enterprise terminal source information, target business system identifier, business type, operator link status, isolation policy and priority;
[0012] S6, the proxy forwarding node forwards the service request to the corresponding multi-carrier private line access node according to the forwarding relationship and the multi-carrier private network access path, and the private line access node sends the service traffic to the target service system.
[0013] Furthermore, the preset set of business domain name policies includes domain name, subdomain name, business system identifier, enterprise terminal source information, time window or policy priority; when matching policies, the domain name or subdomain name is a mandatory matching condition, and the business system identifier, enterprise terminal source information, and time window are optional matching conditions for filtering. The time window is used to limit the policy to be effective only within a specified time range; when multiple policies meet the matching conditions at the same time, the final hit policy is determined according to the policy priority, enterprise terminal source information, and policy start / stop status.
[0014] Furthermore, if the resolution request belongs to a controlled service of the enterprise private network, the DNS resolution scheduling node also returns the cache time corresponding to the abstract access entry, so that the enterprise terminal can directly initiate a service request to the abstract access entry within the cache time; if the resolution request does not belong to a controlled service of the enterprise private network, the DNS resolution scheduling node will send the resolution request to a public DNS server for normal resolution.
[0015] Furthermore, the abstract access entry is a Uniform Resource Locator (URL) or a combination of IP address and port of the proxy forwarding node; the abstract access entry does not directly point to the target business system, but serves as a unified access address for the proxy forwarding node, so that requests from different target business systems enter the proxy forwarding node through the same abstract access entry, and are then further distinguished and forwarded by the proxy forwarding node based on the target business system identifier.
[0016] Furthermore, when the DNS resolution scheduling node detects that the proxy forwarding node is unavailable, it returns a preset backup proxy entry or a normal resolution path; during the period when the proxy forwarding node is unavailable, newly arriving service requests are directed to the backup proxy forwarding node or directly enter the normal resolution path to ensure service continuity.
[0017] Furthermore, before establishing a forwarding relationship based on the target business system identifier, access policy, and connection status, the proxy forwarding node also includes:
[0018] The service request is validated according to the access policy. If the validation fails, the request is rejected. If the validation passes, the proxy forwarding node writes the target service system identifier, abstract access entry identifier, connection 5-tuple and session state into the forwarding context and establishes a forwarding relationship based on the forwarding context.
[0019] Furthermore, the proxy forwarding node adopts an application layer proxy approach, and performs target acceptance based on the target business system identifier and access policy.
[0020] Furthermore, the line policy control module matches the corresponding isolation policy and access priority based on the enterprise terminal source information and the target business system;
[0021] Based on the service type and the status of the operator's links, a set of candidate links that meet the service requirements is selected from the currently available operator links;
[0022] Based on access priority and isolation policy, sort the links of each operator in the candidate link set;
[0023] The highest-ranked carrier link is selected as the multi-carrier private network access path.
[0024] Furthermore, when selecting a multi-carrier private network access path, the line policy control module also includes: determining the primary access path and alternative access paths, and sending the path selection results to the proxy forwarding node and the multi-carrier private line access node.
[0025] On the other hand, a multi-carrier dual-domain private network access system based on DNS directed resolution includes:
[0026] The request module is used to initiate a domain name resolution request to the enterprise-side access node through the enterprise terminal. The domain name resolution request carries the target domain name to be resolved and the target business system identifier.
[0027] The scheduling module is used to send the resolution request to the DNS resolution scheduling node through the enterprise-side access node. The DNS resolution scheduling node determines whether the resolution request belongs to the enterprise private network controlled business based on the target business system identifier and the preset business domain name policy set, and obtains the enterprise terminal source information and business type corresponding to the resolution request.
[0028] The DNS resolution module is used to determine whether the resolution request belongs to the enterprise private network controlled service. If so, it returns the abstract access entry of the proxy forwarding node through the DNS resolution scheduling node so that the enterprise terminal can subsequently initiate service requests to the abstract access entry; otherwise, the domain name resolution request enters the normal resolution path.
[0029] The forwarding relationship establishment module is used to initiate business requests to the proxy forwarding node through the enterprise terminal based on the abstract access entry. The proxy forwarding node establishes forwarding relationships based on the target business system identifier, access policy and connection status.
[0030] The path selection module is used to select a multi-carrier private network access path based on the enterprise terminal source information, target business system, business type, operator link status, isolation policy and priority, through the line policy control module.
[0031] The forwarding module is used to forward service requests to the corresponding multi-carrier private line access node through the proxy forwarding node according to the forwarding relationship and the access path of the multi-carrier private network. The private line access node then sends the service traffic to the target service system.
[0032] The present invention adopts the above technical solution and has the following beneficial effects:
[0033] (1) This invention receives domain name resolution requests and service access requests from enterprise terminals through a unified access node on the enterprise side. The line policy control module dynamically selects the optimal access path among multiple operator 5G dual-domain private network links based on multi-dimensional parameters such as enterprise terminal source information, target business system, service type, operator link status, isolation policy and priority. This eliminates the need for enterprise terminals to perceive the access differences of each operator's link separately, thus solving the problems of fragmented access among multiple operators and high configuration and change costs on the enterprise side.
[0034] (2) This invention maintains a set of business domain name policies through DNS resolution scheduling nodes. For resolution requests that match the enterprise private network controlled business, it returns an abstract access entry point to the proxy forwarding node, so that the enterprise business request automatically enters the controlled access path; if the request does not match, it enters the normal resolution path, which does not affect the normal access of non-private network business; at the same time, the abstract access entry does not directly point to the target business system, but serves as a unified access address for the proxy forwarding node. This enables different target business systems to enter through the same entry point and then be distinguished and forwarded by the proxy forwarding node. This allows the enterprise terminal to be unaware of the access details of the target business system, forming a complete closed loop from domain name recognition to business forwarding, reducing the cost of differentiated configuration and multi-point maintenance on the terminal side;
[0035] (3) This invention ensures that only authorized requests can establish forwarding relationships through permission verification; it performs health checks on DNS resolution scheduling nodes and proxy forwarding nodes through a fault switching module, and automatically switches to alternative links or backup nodes according to preset strategies when the primary path is unavailable, avoiding service interruption caused by single point of failure, and improving the reliability and continuity of multi-operator private network access. Attached Figure Description
[0036] Figure 1 This is a flowchart of a multi-carrier dual-domain private network access method based on DNS directed resolution, according to an embodiment of the present invention.
[0037] Figure 2 This is a schematic diagram of the multi-carrier 5G dual-domain private network converged access method and system architecture according to an embodiment of the present invention;
[0038] Figure 3 This is a flowchart illustrating the DNS directed resolution and proxy forwarding process according to an embodiment of the present invention.
[0039] Figure 4 This is a flowchart illustrating the multi-carrier line policy control and fault switching process according to an embodiment of the present invention.
[0040] Figure 5 This is a diagram of a multi-carrier dual-domain private network access system based on DNS directed resolution, according to an embodiment of the present invention. Detailed Implementation
[0041] The present invention will be further described in detail below with reference to the embodiments and accompanying drawings, but the embodiments of the present invention are not limited thereto.
[0042] like Figure 1 As shown, the present invention provides a method for accessing a multi-carrier dual-domain private network based on DNS directed resolution, comprising:
[0043] S1, the enterprise terminal initiates a domain name resolution request to the enterprise-side access node, the domain name resolution request carrying the target domain name to be resolved and the target business system identifier.
[0044] S2, the enterprise-side access node sends the resolution request to the DNS resolution scheduling node. The DNS resolution scheduling node determines whether the resolution request belongs to the enterprise private network controlled business based on the target business system identifier and the preset business domain name policy set, and obtains the enterprise terminal source information and business type corresponding to the resolution request.
[0045] Specifically, the preset set of business domain name policies includes domain name, subdomain name, business system identifier, enterprise terminal source information, time window or policy priority; when matching policies, the domain name or subdomain name is a mandatory matching condition, and the business system identifier, enterprise terminal source information, and time window are optional matching conditions for filtering. The time window is used to limit the policy to be effective only within a specified time range; when multiple policies meet the matching conditions at the same time, the final hit policy is determined according to the policy priority, enterprise terminal source information, and policy start / stop status.
[0046] Specifically, such as Figure 2 As shown in this embodiment, the enterprise-side access node is located between the enterprise terminal, enterprise branches, and platform-side functional modules, uniformly receiving resolution requests and service access requests. The DNS resolution scheduling node is responsible for determining the entry point of the resolution flow, the proxy forwarding node is responsible for accepting the service flow, and the multi-carrier private line access node is responsible for sending controlled service traffic into the corresponding carrier private network link. The line policy control module, the security access control module, and the fault switching module together constitute the control plane, which coordinates and constrains the request flow, resolution flow, service flow, and policy control flow. Figure 1 The multi-carrier links in the system are represented by independent leased line access boundaries. Logical and policy isolation are maintained between different links, and the target business system is not directly exposed to the enterprise-side terminal. The platform uses a unified policy control relationship to associate the enterprise-side source, target business system identifier, access permissions, line selection, and fault handling results, so that the same enterprise access entry can enter different carrier links according to the policy, while avoiding the mixing of forwarding status and isolation boundaries of different links.
[0047] S3. If the resolution request belongs to the enterprise private network controlled service, the DNS resolution scheduling node returns the abstract access entry of the proxy forwarding node so that the enterprise terminal can subsequently initiate service requests to the abstract access entry; if it does not belong to the enterprise private network controlled service, the domain name resolution request enters the normal resolution path.
[0048] Specifically, after entering the normal parsing path, there is no need to execute S4~S6.
[0049] Specifically, if the resolution request belongs to a controlled service of the enterprise private network, the DNS resolution scheduling node also returns the cache time corresponding to the abstract access entry, so that the enterprise terminal can directly initiate a service request to the abstract access entry within the cache time; if the resolution request does not belong to a controlled service of the enterprise private network, the DNS resolution scheduling node will send the resolution request to the public DNS server for normal resolution.
[0050] Specifically, the abstract access entry is a Uniform Resource Locator (URL) or a combination of IP address and port of the proxy forwarding node; the abstract access entry does not directly point to the target business system, but serves as the unified access address of the proxy forwarding node, so that requests from different target business systems enter the proxy forwarding node through the same abstract access entry, and are then further distinguished and forwarded by the proxy forwarding node according to the target business system identifier.
[0051] Specifically, when the DNS resolution scheduling node detects that the proxy forwarding node is unavailable, it returns a preset backup proxy entry or a normal resolution path; during the period when the proxy forwarding node is unavailable, newly arriving service requests are directed to the backup proxy forwarding node or directly enter the normal resolution path to ensure service continuity.
[0052] Specifically, the DNS directed resolution mechanism works as follows: The DNS resolution scheduling node uses a set of business domain name policies as its core to perform policy matching on enterprise-side resolution requests. Policy hit conditions can include domain name, subdomain, business system identifier, enterprise-side origin, time window, or policy priority. Upon a hit, the system returns an abstract entry point to the proxy forwarding node, allowing subsequent business requests to enter the controlled access path; requests that do not hit continue along the normal resolution path, avoiding impact on uncontrolled business access. During resolution processing, the DNS resolution scheduling node can first normalize the business domain name in the resolution request before performing matching according to the policy rule set. When the matching result is for a controlled business, the resolution response returns the abstract access entry point of the proxy forwarding node and the corresponding cache time; when the matching result is for an uncontrolled business, the resolution response enters the normal resolution path. This approach prevents the target business system from being directly exposed as an enterprise-side resolution result. When multiple policies meet the conditions simultaneously, the DNS resolution scheduling node can determine the final policy based on priority, enterprise-side source, target business system identifier, and policy start / stop status. When a policy is missing, disabled, or the proxy forwarding node is unavailable, it can return a normal resolution path, a backup proxy entry, or a preset downgrade result, with the specific choice determined by the deployment policy.
[0053] S4, the enterprise terminal initiates a business request to the proxy forwarding node based on the abstract access entry point, and the proxy forwarding node establishes a forwarding relationship based on the target business system identifier, access policy and connection status.
[0054] Specifically, before establishing a forwarding relationship based on the target business system identifier, access policy, and connection status, the proxy forwarding node also includes:
[0055] The service request is validated according to the access policy. If the validation fails, the request is rejected. If the validation passes, the proxy forwarding node writes the target service system identifier, abstract access entry identifier, connection 5-tuple and session state into the forwarding context and establishes a forwarding relationship based on the forwarding context.
[0056] Specifically, the proxy forwarding node adopts an application layer proxy approach, and undertakes the target based on the business host identifier and access policy.
[0057] Specifically, the proxy forwarding mechanism:
[0058] As the receiving point of the controlled access path, the proxy forwarding node performs target identification, policy verification, and forwarding processing on business requests from the enterprise side. The proxy forwarding node shields the access details of the target business system and works in conjunction with the line policy control module to select multi-carrier private network links according to the target business system identifier, access policy, and link status.
[0059] When a proxy forwarding node establishes a forwarding relationship, it can write the target business system identifier, proxy entry identifier, connection 5-tuple, session state, and line selection result from the business request into the forwarding context. For application-layer proxies, target acceptance can be based on the business host identifier and access policy; for transport-layer proxies, forwarding can be based on connection state and line policy. A transport-layer proxy is similar to IP / port mapping, does not parse application-layer business content, and forwards directly based on TCP / UDP connections.
[0060] The proxy forwarding node and the line policy control module can work together via policy query, rule distribution, or local rule caching. After the policy is updated, new sessions will select a line according to the new policy, while existing sessions can continue to maintain the original path based on connection maintenance requirements or switch to an alternative path when the failover module is triggered.
[0061] Specifically, such as Figure 3 As shown, enterprise-side DNS resolution requests first enter the DNS resolution scheduling node via the enterprise-side access node. The DNS resolution scheduling node then performs a hit determination on the set of business domain name policies. When a policy is hit, the resolution result does not directly point to the target business system, but instead returns to the abstract entry point of the proxy forwarding node, allowing subsequent business requests to naturally enter the controlled access path. When a policy is not hit, the request enters the normal resolution path, preventing uncontrolled services from being forcibly included in the private network forwarding process. After receiving a hit business request, the proxy forwarding node establishes a forwarding relationship according to the target business system identifier, access policy, and line policy control results, and then hands over the business traffic to the multi-carrier private line access node for processing. This process centralizes the target entry point, line selection, and proxy rules that need to be statically maintained on the terminal side to the platform side. Enterprise terminals can complete business access simply by accessing the abstract entry point based on the resolution result, thereby reducing the risk of multi-point configuration and policy inconsistency on the terminal side.
[0062] S5, the line policy control module selects a multi-carrier private network access path based on the enterprise terminal source information, target business system, business type, operator link status, isolation policy and priority.
[0063] Specifically, S4 is responsible for determining whether the DNS resolution request matches the controlled business policy, and S5 selects the specific access path after the request has entered the controlled access path.
[0064] Specifically, the operator link status is dynamically obtained during operation through link health detection and connection status, and is a result determined based on whether the current operator link is available.
[0065] Isolation strategy: This mainly refers to the control rules preset during the policy configuration phase, which are used to limit policy isolation between different operator links, different enterprise sources, and different target business systems.
[0066] Priority: This mainly refers to preset strategy items, including primary / backup order, line priority, and strategy hit priority.
[0067] Specifically, the line policy control module matches the corresponding isolation policy and access priority based on the enterprise terminal source information and the target business system;
[0068] Based on the service type and the status of the operator's links, a set of candidate links that meet the service requirements is selected from the currently available operator links;
[0069] Based on access priority and isolation policy, sort the links of each operator in the candidate link set;
[0070] The highest-ranked carrier link is selected as the multi-carrier private network access path.
[0071] Specifically, when selecting access paths for multi-carrier private networks, the line policy control module also includes: determining the primary access path and alternative access paths, and sending the path selection results to the proxy forwarding node and the multi-carrier private line access node.
[0072] Specifically, the line policy control module maintains the mapping relationship between the enterprise-side source, target business system, business type, operator link, access priority, and isolation requirements. When a business request enters the proxy forwarding node, the line policy control module selects an access path based on the current link availability and policy priority. For scenarios with address planning differences, path control can be achieved through address translation, policy routing, or equivalent methods. The path selection results output by the line policy control module may include the primary operator link, alternative operator links, execution actions, policy hit reasons, and isolation boundary identifiers. Multi-operator leased line access nodes generate or reference forwarding rules, policy routing, or address translation rules accordingly, ensuring that different operator links remain separate in terms of control logic and forwarding status. When there are differences in address planning or business access boundaries, the proxy forwarding node can act as a unified interface to mask these differences. The line policy control module only outputs abstract link identifiers and policy actions to the multi-operator leased line access nodes, without requiring the enterprise-side terminal to be aware of the underlying link details.
[0073] Specifically, such as Figure 4 As shown, the input conditions for the line policy control module include the enterprise-side source, target business system, service type, link status, isolation policy, and priority. The policy control results are used to select a primary path, alternative path, or preset degraded path among multiple carrier dual-domain private network links, and forwarding is performed through multi-carrier private line access nodes. Link isolation boundaries remain in effect throughout the routing process to prevent unauthorized path sharing between links from different carriers.
[0074] Health checks can be triggered by link status detection, node status detection, connection persistence, or forwarding failure events. When the primary path is unavailable, the failover module selects an alternative link, alternative node, or degraded path based on preset priorities and isolation requirements. After fault recovery, the platform can decide whether to maintain the current link or switch back according to the policy based on recovery confirmation, stability observation, and policy priorities to avoid frequent switching caused by short-term state fluctuations. The relevant detection cycle and threshold parameters remain abstract and are determined by the actual deployment strategy.
[0075] The failover process can be abstracted into four states: Normal, Degraded, Failover, and Failback Observation. The failover module updates the state based on health checks, forwarding failure events, and changes in link status. Path adjustments are only triggered when state changes meet preset conditions to reduce frequent failovers caused by short-term fluctuations.
[0076] The secure access control module is in Figure 4 The process records policy hits, forwarding paths, link anomalies, handover actions, recovery judgments, and processing results, and associates them with the access subject and the target business system identifier. These records support access auditing, anomaly tracing, and policy review, but do not require exposing internal line details on the terminal side, nor do they alter the controlled access paths already established by DNS redirection and proxy forwarding.
[0077] S6, the proxy forwarding node forwards the service request to the corresponding multi-carrier private line access node according to the forwarding relationship and the multi-carrier private network access path, and the private line access node sends the service traffic to the target service system.
[0078] Specifically, this embodiment also includes a fault switching module that can determine anomalies through link status detection, node status detection, connection persistence status, or forwarding failure events. When the primary path is unavailable, the fault switching module selects an alternative operator link, an alternative node, or a degraded path according to a preset strategy. The detection period, switching threshold, priority order, and recovery strategy are retained as deployment parameters.
[0079] Specifically, this embodiment also includes a secure access control module, which provides unified control over enterprise-side access subjects, business domain name policies, proxy forwarding permissions, line isolation policies, and access logs. This module works in conjunction with the DNS resolution scheduling node, proxy forwarding node, and line policy control module to ensure that access control, policy hits, path selection, abnormal events, and processing results are continuously recorded, facilitating subsequent auditing, tracing, and policy review.
[0080] The security access control module can record processing results in three dimensions: authentication, authorization, and audit log. Record fields may include access subject identifier, enterprise-side source, target business system identifier, policy rule identifier, proxy entry identifier, carrier link identifier, processing result, exception category, and time information. Field content should be represented using de-identified or abstract identifiers.
[0081] Specifically, the present invention addresses the following issues:
[0082] Unified access problem: This invention aims to address the issue of dispersed entry points and significant configuration differences among enterprise terminals, enterprise branches, or enterprise gateways in multi-carrier 5G dual-domain private network scenarios. It solves this problem by having enterprise-side access nodes uniformly receive parsing requests and service access requests, and incorporate these requests into subsequent parsing, proxying, and routing processes.
[0083] Business identification and targeted resolution issues: This invention aims to address the problem that ordinary resolution cannot identify controlled enterprise businesses and cannot stably guide access paths. It maintains a set of business domain name policies through DNS resolution scheduling nodes, returns an abstract access entry point to the proxy forwarding node for matching resolution requests, and maintains the ordinary resolution path for unmatched requests.
[0084] Target business system access handling issue: This invention aims to address the problem that enterprise-side terminals should not directly maintain the access details of the target business system. It uses a proxy forwarding node to handle business requests guided by DNS redirection and forwards them according to the target business system identifier, access policy, and connection status.
[0085] Multi-carrier line convergence and isolation issues: This invention aims to solve the problem of inconsistent link entry points, isolation boundaries, and routing strategies among multiple carriers. It connects 5G dual-domain private network links of different carriers through multi-carrier dedicated line access nodes, and the line policy control module selects the access path based on the enterprise-side source, target business system, business type, link status, and isolation requirements.
[0086] Access path closed-loop control problem: This invention needs to solve the problems that controlled business traffic may mistakenly enter uncontrolled paths and address planning differences affect reachability. It aims to form a closed loop of linkage between DNS resolution scheduling nodes, proxy forwarding nodes, line policy control modules and multi-carrier leased line access nodes, and to shield the planning differences between the enterprise-side network and the target business system through proxy forwarding, policy routing or equivalent mechanisms.
[0087] Fault switching issue: This invention addresses the problem of service interruption caused by abnormalities in links, parsing scheduling nodes, or proxy forwarding nodes. It uses a fault switching module to detect availability and select alternative operator links, alternative nodes, or preset degraded paths when the current path becomes unavailable. Specific detection cycles, switching thresholds, and recovery strategies can be determined based on actual deployment.
[0088] Security access issues: This invention aims to address the problems of decentralized access control, access isolation, and auditing. It uses a security access control module to implement policy control and behavior recording for enterprise-side requests, access to target business systems, proxy forwarding processes, and line selection results.
[0089] Specifically, in this embodiment, enterprise-side access entry, DNS redirection, proxy forwarding, multi-carrier leased line access, line policy control, fault switching, and secure access control are integrated into a unified collaborative process. The platform includes enterprise-side access nodes, DNS resolution scheduling nodes, proxy forwarding nodes, multi-carrier leased line access nodes, line policy control modules, fault switching modules, secure access control modules, and target business system connection modules. Each node can be deployed in a centralized or distributed manner depending on the enterprise scale, or it can be deployed on independent devices, virtualized environments, or containerized environments.
[0090] (1) Enterprise-side access layer: The enterprise-side access node receives parsing requests and service access requests initiated by enterprise terminals, enterprise branches or enterprise gateways, and incorporates access from different enterprise-side sources into a unified entry point. This node does not require the enterprise side to be aware of the access differences of each operator's link. After the parsing requests and service requests enter the platform, subsequent modules will complete the identification, acceptance and routing.
[0091] (2) DNS resolution scheduling layer: The DNS resolution scheduling node maintains a set of business domain name policies. The policy set includes at least the controlled business domain name, the target business system identifier, the proxy forwarding entry identifier, the policy priority, and optional cache parameters. When the resolution request hits a controlled business policy, the DNS resolution scheduling node returns the abstract access entry of the proxy forwarding node; when the policy is not hit, the request is processed according to the normal resolution path.
[0092] (3) Proxy forwarding layer: Proxy forwarding nodes receive business requests guided by DNS directed resolution and establish forwarding relationships based on the target business system identifier, access policy, and connection status. Proxy forwarding nodes can be implemented using application layer proxy, layer 4 connection proxy, or a combination of both, so that enterprise-side access requests do not need to directly maintain the details of the target business system.
[0093] (4) Multi-carrier leased line convergence layer: Multi-carrier leased line access nodes connect to the 5G dual-domain private network links of the three types of operators, and maintain logical and policy isolation between links of different operators. The line policy control module selects the access path according to the enterprise-side source, target business system, business type, link status, isolation requirements and policy priority. The selection result can be executed through policy routing, forwarding rules, link identification or equivalent policy mechanism.
[0094] (5) Security and Continuity Control Layer: The security access control module provides unified control over enterprise-side access, business access isolation, proxy forwarding authorization, and behavior logging. The failover module detects the availability status of operator links, proxy forwarding nodes, or parsing scheduling nodes, and selects alternative links, alternative nodes, or preset degradation paths when the current path is unavailable.
[0095] Specifically, in an enterprise networking embodiment, when an enterprise terminal accesses a target business system, the resolution request first enters the DNS resolution scheduling node. After determining that the domain name belongs to the controlled enterprise business, the DNS resolution scheduling node returns the abstract entry point to the proxy forwarding node. The enterprise terminal then initiates a business request to the proxy forwarding node. Based on the target business system identifier and the selection result of the line policy control module, the proxy forwarding node sends the request to the corresponding operator's private network link. After the target business system responds, the response traffic returns to the enterprise side via the corresponding link and proxy forwarding relationship. Thus, the enterprise side obtains a unified entry point, unified resolution policy, unified proxy handling, and unified line scheduling capabilities.
[0096] In this embodiment, during platform deployment, the service domain name policy set, proxy forwarding entry point, operator link identifier, line priority, and fault switching rules can be configured first. During runtime, the DNS resolution scheduling node, proxy forwarding node, line policy control module, and fault switching module will gradually coordinate according to the request status. The above configuration items are all abstract policy items and are not limited to specific vendor equipment, specific link parameters, or fixed values.
[0097] Specifically, this invention does not rely on a specific deployment method or implementation details, and can be flexibly adjusted during implementation: DNS resolution scheduling nodes can be centrally deployed in a unified control location, or distributed according to enterprise regions, access points, or business systems; policy sets can be configured locally, issued by a centralized controller, or generated synchronously by interfaces; proxy forwarding nodes can be implemented using application layer proxy, layer 4 connection proxy, transparent proxy, reverse proxy, or a combination of the above methods, or deployed on the same node or different nodes as the line policy control module; multi-carrier leased line access nodes can access three types of carrier links, or in some embodiments, access two types or configure more similar backup links; link selection can adopt strategies such as primary / backup, priority, weight, load balancing, service type binding, or manual specification; service identification conditions can adopt domain name, address range, port, protocol type, enterprise-side source, user identity, terminal type, time window, or... Multiple conditions can be combined, not limited to single domain name matching; fault switching can be triggered by link detection, node status monitoring, connection failure detection, proxy return status, or service reachability detection. The switching target can be a backup operator link, backup proxy node, backup DNS node, or a preset degraded access policy; secure access control can adopt identity authentication, certificate authentication, dynamic authentication, device fingerprinting, enterprise-side whitelist, business authorization table, or multi-factor collaborative authentication, etc., which can be selected according to the enterprise's security requirements; the platform as a whole can be deployed on physical devices, virtual machines, containers, or cloud-edge collaborative environments, and the modules can synchronize policies through local calls, message queues, configuration centers, databases, or interface calls; the target business system can be an internal enterprise application, an industry private network application, a park business system, or other business systems that need to be accessed through the enterprise private network. It can be described as an abstract business system in the formal application document, without limiting it to a specific industry.
[0098] like Figure 5 As shown, this embodiment also discloses a multi-carrier dual-domain private network access system based on DNS directed resolution, including:
[0099] Request module 51 is used to initiate a domain name resolution request to the enterprise-side access node through the enterprise terminal. The domain name resolution request carries the target domain name to be resolved and the target business system identifier.
[0100] The scheduling module 52 is used to send the resolution request to the DNS resolution scheduling node through the enterprise-side access node. The DNS resolution scheduling node determines whether the resolution request belongs to the enterprise private network controlled business based on the target business system identifier and the preset business domain name policy set, and obtains the enterprise terminal source information and business type corresponding to the resolution request.
[0101] The resolution module 53 is used to determine whether the resolution request belongs to the enterprise private network controlled service. If so, it returns the abstract access entry of the proxy forwarding node through the DNS resolution scheduling node so that the enterprise terminal can subsequently initiate a service request to the abstract access entry; otherwise, the domain name resolution request enters the normal resolution path.
[0102] The forwarding relationship establishment module 54 is used to initiate a business request to the proxy forwarding node through the enterprise terminal based on the abstract access entry. The proxy forwarding node establishes a forwarding relationship based on the target business system identifier, access policy and connection status.
[0103] The path selection module 55 is used to select a multi-carrier private network access path based on the enterprise terminal source information, target business system, business type, operator link status, isolation policy and priority through the line policy control module;
[0104] The forwarding module 56 is used to forward service requests to the corresponding multi-carrier private line access node through the proxy forwarding node according to the forwarding relationship and the multi-carrier private network access path, and the private line access node then sends the service traffic to the target service system.
[0105] A specific implementation of a multi-carrier dual-domain private network access system based on DNS directed resolution is described in this embodiment, which is the same as the multi-carrier dual-domain private network access method based on DNS directed resolution.
[0106] Although the invention has been specifically shown and described in conjunction with preferred embodiments, those skilled in the art should understand that various changes in form and detail may be made to the invention without departing from the spirit and scope of the invention as defined in the appended claims, all of which shall be within the scope of protection of the invention.
Claims
1. A method for accessing a multi-carrier dual-domain private network based on DNS directed resolution, characterized in that, Includes the following steps: S1, the enterprise terminal initiates a domain name resolution request to the enterprise-side access node, the domain name resolution request carrying the target domain name to be resolved and the target business system identifier; S2, the enterprise-side access node sends the resolution request to the DNS resolution scheduling node. The DNS resolution scheduling node determines whether the resolution request belongs to the enterprise private network controlled business based on the target business system identifier and the preset business domain name policy set, and obtains the enterprise terminal source information and business type corresponding to the resolution request. S3, if the resolution request belongs to the enterprise private network controlled service, the DNS resolution scheduling node returns the abstract access entry of the proxy forwarding node, so that the enterprise terminal can subsequently initiate a service request to the abstract access entry and enter S4; if it does not belong to the enterprise private network controlled service, the domain name resolution request enters the normal resolution path. S4, the enterprise terminal initiates a business request to the proxy forwarding node based on the abstract access entry, and the proxy forwarding node establishes a forwarding relationship based on the target business system identifier, access policy and connection status; S5, the line policy control module selects the multi-carrier private network access path based on the enterprise terminal source information, target business system identifier, business type, operator link status, isolation policy and priority; S6, the proxy forwarding node forwards the service request to the corresponding multi-carrier private line access node according to the forwarding relationship and the multi-carrier private network access path, and the private line access node sends the service traffic to the target service system.
2. The multi-carrier dual-domain private network access method based on DNS directed resolution according to claim 1, characterized in that, In S2, the preset set of business domain name policies includes domain name, subdomain name, business system identifier, enterprise terminal source information, time window or policy priority. When matching policies, the domain name or subdomain name is a mandatory matching condition, and the business system identifier, enterprise terminal source information, and time window are optional matching conditions for filtering. The time window is used to limit the policy to be effective only within a specified time range. When multiple policies meet the matching conditions at the same time, the final hit policy is determined according to the policy priority, enterprise terminal source information, and policy start / stop status.
3. The multi-carrier dual-domain private network access method based on DNS directed resolution according to claim 1, characterized in that, In S3, if the resolution request belongs to the enterprise private network controlled service, the DNS resolution scheduling node also returns the cache time corresponding to the abstract access entry, so that the enterprise terminal can directly initiate a service request to the abstract access entry within the cache time. If the resolution request does not belong to the enterprise's private network controlled services, the DNS resolution scheduling node will send the resolution request to the public DNS server for normal resolution.
4. The multi-carrier dual-domain private network access method based on DNS directed resolution according to claim 3, characterized in that, In S3, the abstract access entry is the Uniform Resource Locator or a combination of IP address and port of the proxy forwarding node; the abstract access entry does not directly point to the target business system, but serves as the unified access address of the proxy forwarding node, so that requests from different target business systems enter the proxy forwarding node through the same abstract access entry, and the proxy forwarding node performs secondary differentiation and forwarding based on the target business system identifier.
5. The multi-carrier dual-domain private network access method based on DNS directed resolution according to claim 1, characterized in that, S3 also includes: when the DNS resolution scheduling node detects that the proxy forwarding node is unavailable, it returns a preset backup proxy entry or a normal resolution path; during the period when the proxy forwarding node is unavailable, newly arriving service requests are directed to the backup proxy forwarding node or directly enter the normal resolution path.
6. The multi-carrier dual-domain private network access method based on DNS directed resolution according to claim 1, characterized in that, In S4, before the proxy forwarding node establishes a forwarding relationship based on the target business system identifier, access policy, and connection status, it also includes: The service request is validated according to the access policy. If the validation fails, the request is rejected. If the validation passes, the proxy forwarding node writes the target service system identifier, abstract access entry identifier, connection 5-tuple and session state into the forwarding context and establishes a forwarding relationship based on the forwarding context.
7. The multi-carrier dual-domain private network access method based on DNS directed resolution according to claim 1, characterized in that, In S4, the proxy forwarding node adopts the application layer proxy method, and performs target reception based on the target business system identifier and access policy.
8. The multi-carrier dual-domain private network access method based on DNS directed resolution according to claim 1, characterized in that, S5 specifically includes: The line policy control module matches the corresponding isolation policy and access priority based on the enterprise terminal source information and the target business system; Based on the service type and the status of the operator's links, a set of candidate links that meet the service requirements is selected from the currently available operator links; Based on access priority and isolation policy, sort the links of each operator in the candidate link set; The highest-ranked carrier link is selected as the multi-carrier private network access path.
9. The multi-carrier dual-domain private network access method based on DNS directed resolution according to claim 1, characterized in that, In S5, when selecting a multi-carrier private network access path, the line policy control module also includes: determining the primary access path and alternative access paths, and sending the path selection results to the proxy forwarding node and the multi-carrier private line access node.
10. A multi-carrier dual-domain private network access system based on DNS directed resolution, characterized in that, include: The request module is used to initiate a domain name resolution request to the enterprise-side access node through the enterprise terminal. The domain name resolution request carries the target domain name to be resolved and the target business system identifier. The scheduling module is used to send the resolution request to the DNS resolution scheduling node through the enterprise-side access node. The DNS resolution scheduling node determines whether the resolution request belongs to the enterprise private network controlled business based on the target business system identifier and the preset business domain name policy set, and obtains the enterprise terminal source information and business type corresponding to the resolution request. The DNS resolution module is used to determine whether the resolution request belongs to the enterprise private network controlled service. If so, it returns the abstract access entry of the proxy forwarding node through the DNS resolution scheduling node so that the enterprise terminal can subsequently initiate service requests to the abstract access entry; otherwise, the domain name resolution request enters the normal resolution path. The forwarding relationship establishment module is used to initiate business requests to the proxy forwarding node through the enterprise terminal based on the abstract access entry. The proxy forwarding node establishes forwarding relationships based on the target business system identifier, access policy and connection status. The path selection module is used to select a multi-carrier private network access path based on the enterprise terminal source information, target business system, business type, operator link status, isolation policy and priority, through the line policy control module. The forwarding module is used to forward service requests to the corresponding multi-carrier private line access node through the proxy forwarding node according to the forwarding relationship and the access path of the multi-carrier private network. The private line access node then sends the service traffic to the target service system.
Citation Information
Patent Citations
A method, system, device and storage medium for the converged management and control of 5G wireless networks
CN116112984B
Method for constructing automatic switching based on 5G private network and traditional MPLS side network
CN118449899A
