Service discovery and flow arrangement method and system based on cooperation of DHCP (dynamic host configuration protocol) and DNS (domain name system)

Abstract

The embodiment of the invention discloses a DHCP (Dynamic Host Configuration Protocol) and DNS (Domain Name Server) collaboration-based service discovery and flow arrangement method and system, which enable a network administrator to more conveniently manage and discover equipment and services in a network through collaborative planning of an IP (Internet Protocol) address and a domain name, enable a user to identify information such as a department, a position and a function to which the equipment belongs through the domain name, and improve the efficiency of service discovery and flow arrangement. Human errors and query cost in network management are reduced, and efficiency and accuracy of domain name transformation of network management are improved; through the dynamic domain name arrangement, the DHCP server can adjust the domain name and the record value in real time according to the state change of the client, so that the network service can better adapt to different application scenes and user requirements, and the flexibility and expandability of the Internet of Things service are improved; the analysis is arranged and the static configuration is issued at the DHCP server, so that the requirement on the capability of the DNS server is reduced, and the stability of the DNS server is also improved.

Description

Technical Field

[0001] The embodiments of the present invention relate to the field of network interaction technology, and more particularly to a method and system for service discovery and traffic orchestration based on DHCP and DNS collaboration. Background Art

[0002] In today's network environment, DHCP and DNS, as fundamental Internet services, play a vital role. DHCP automatically assigns IP addresses to devices connected to the network, greatly simplifying network management and improving network deployment efficiency. DNS, on the other hand, performs the critical task of translating domain names into IP addresses, enabling users to access various network resources using easy-to-remember domain names, thus achieving convenient access to network resources.

[0003] During normal network interactions, DHCP automatically sends dynamic update messages to a DNS server when assigning an IP address to a client. The DNS server records the mapping between domain names and IP addresses, allowing other devices to communicate with newly connected devices by querying the domain name to obtain the corresponding IP address, thus successfully completing the communication connection. When a terminal device releases its occupied IP address or the IP address lease expires, the DHCP server also sends a corresponding message to the DNS server, requesting that the DNS server delete the corresponding domain name and IP address mapping, ensuring the accuracy and timeliness of domain name resolution information.

[0004] The DHCP server can also send various record types to the DNS server, such as TXT, NAPTR, and SRV. This allows other terminals to obtain not only the IP address but also more information related to the domain name, such as the service description, service priority, and service location rules, further enriching the ability to discover and access network services.

[0005] To better adapt to dynamic changes in the network environment, some DNS servers are equipped with a dynamic detection module. This module monitors the operating status of registered IP addresses in real time and dynamically adjusts the resolution strategy based on the acquired status information. For example, if the server corresponding to a certain IP address is found to be overloaded, the DNS server can redirect subsequent resolution requests to other servers with lower loads, thereby optimizing network traffic distribution and improving overall network service performance and user experience.

[0006] However, the current prior art has the following defects:

[0007] 1) Insufficient ability to dynamically adjust domain names

[0008] Currently, the domain name associated with the IP address assigned by DHCP to a client is relatively fixed. It's either statically configured by the server or proactively provided by the client during the request process. Once the IP address is assigned, the server struggles to dynamically adjust the corresponding domain name based on subsequent changes in the client's status, such as changes in device type, service requirements upgrades, or network location relocation. This limits the flexibility and adaptability of network services, making them unable to meet the demands of today's complex and ever-changing network application scenarios.

[0009] 2) Lack of coordination between IP address and domain name planning

[0010] In many network environments, DHCP servers often lack comprehensive planning when assigning IP addresses. Even when IP address planning exists, corresponding domain name planning is often missing. This results in users being unable to intuitively associate or infer the specific information of the terminal device or service they want to access simply by using the domain name when accessing network services. For example, in a large enterprise network, devices in different departments may use similar IP address segments. However, due to the lack of a reasonable domain name planning, users in other departments cannot quickly determine the device's department or functional purpose from the domain name when accessing these devices, which increases the difficulty of network management and service access.

[0011] 3) Performance and stability issues caused by dynamic detection

[0012] While DNS servers that incorporate dynamic detection modules can, to a certain extent, achieve real-time monitoring of IP address status and dynamic adjustment of resolution strategies, frequent detection operations inevitably increase the burden on the network and server. On the one hand, a large number of detection requests consumes valuable network bandwidth resources, leading to increased network congestion. On the other hand, the DNS server needs to process a large amount of detection data, which significantly increases its own load and maintenance costs, thereby affecting the stability of the DNS service node. In a network environment with high concurrent access, this situation may lead to increased DNS resolution delays and even resolution failures, seriously affecting the normal operation of network services. Summary of the Invention

[0013] To this end, an embodiment of the present invention provides a method and system for service discovery and traffic orchestration based on DHCP and DNS collaboration to solve the problems in the prior art of domain name inability to dynamically adjust and service discovery rigidity caused by the lack of collaboration between DHCP and DNS.

[0014] In order to achieve the above objectives, the embodiments of the present invention provide the following technical solutions:

[0015] According to a first aspect of an embodiment of the present invention, a method for service discovery and traffic orchestration based on DHCP and DNS collaboration is provided, the method comprising:

[0016] Continuously collect status information of all perceptible terminals, including fingerprint, device type, network location, service type and load indicators;

[0017] During the network deployment phase, semantic domain name rules are predefined through the IP address and domain name collaborative planning strategy. These semantic domain name rules associate domain name fields with terminal attributes. When the DHCP server assigns an IP address, a domain name is dynamically generated based on these semantic domain name rules.

[0018] Obtain the status information of the corresponding terminal, organize multiple DNS record values ​​associated with the same domain name, and send static configuration instructions to the DNS server. The DNS server responds to the instructions and updates the records to achieve dynamic service discovery and traffic guidance.

[0019] Furthermore, continuously collecting status information of all perceptible terminals also includes indirectly obtaining terminal information by sending instructions.

[0020] Furthermore, when the terminal status information changes, a dynamic update of the domain name is triggered, including automatic reorganization of the location identification field when the device location migrates.

[0021] Furthermore, the semantic domain name rule includes a location identification field and a service type field. The location identification field is generated according to the binary segment mapping of the IP address, and the location hierarchy includes a building number, a floor, and an area number.

[0022] Furthermore, multiple DNS record values ​​associated with the same domain name are arranged, including:

[0023] Dynamically adjust the order of DNS return records based on terminal load, with records for terminals with lower loads being ranked higher.

[0024] Based on the terminal's geographic location and network status, ACL policies are issued to the DNS server to achieve local access.

[0025] When the terminal is offline or the load exceeds the threshold, an instruction is sent to the DNS server to delete the corresponding record.

[0026] Furthermore, the static configuration instructions sent to the DNS server include but are not limited to: A record, AAAA record, PTR record, SRV record, TXT record, and NAPTR record.

[0027] According to a second aspect of an embodiment of the present invention, a system for service discovery and traffic orchestration based on DHCP and DNS collaboration is provided, the system comprising:

[0028] The terminal automatic monitoring module is used to continuously collect status information of all perceived terminals, including fingerprints, device types, network locations, service types, and load indicators;

[0029] An IP address and domain name collaborative planning module is used to predefine semantic domain name rules using the IP address and domain name collaborative planning strategy during the network deployment phase. The semantic domain name rules associate domain name fields with terminal attributes. When the DHCP server assigns an IP address, a domain name is dynamically generated according to the semantic domain name rules.

[0030] The dynamic domain name orchestration module is used to obtain the status information of the corresponding terminal, orchestrate multiple DNS record values ​​associated with the same domain name, and send static configuration instructions to the DNS server. The DNS server responds to the instructions and updates the records to achieve dynamic service discovery and traffic guidance.

[0031] Furthermore, the terminal automatic monitoring module is implemented through the IPAM function of the DHCP server, and the monitoring data includes device fingerprint and service port information.

[0032] The embodiments of the present invention have the following advantages:

[0033] The embodiments of the present invention establish a collaborative planning system for IP addresses and domain names, allowing network administrators to more conveniently manage and discover devices and services on the network. Through a unified planning strategy, users can identify a device's department, location, and function by domain name, reducing human error and query costs in network management and improving the efficiency and accuracy of domain name-based network management.

[0034] The dynamic domain name orchestration module allows the DHCP server to adjust domain names and record values ​​in real time based on client status changes, allowing network services to better adapt to different application scenarios and user needs. For example, in an IoT environment, where the location and function of devices may change frequently, dynamic domain name adjustment ensures that devices can be accessed using the appropriate domain name regardless of their status, improving the flexibility and scalability of IoT services.

[0035] The DNS server is one of the most critical core services in the network. By leveraging the existing capabilities of the DHCP server and orchestrating the resolution and issuing static configurations on the DHCP server, the requirements for the DNS server's own capabilities are reduced and its stability is improved. BRIEF DESCRIPTION OF THE DRAWINGS

[0036] To more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the following briefly introduces the drawings required for the embodiments or the description of the prior art. Obviously, the drawings described below are merely exemplary, and those skilled in the art can derive other implementation drawings based on the provided drawings without inventive effort.

[0037] The structures, proportions, sizes, etc. illustrated in this specification are intended only to complement the contents disclosed herein and to facilitate understanding and reading by persons familiar with the art. They are not intended to limit the conditions under which the present invention may be implemented and therefore have no substantive technical significance. Any structural modifications, changes in proportions, or adjustments in sizes, without affecting the efficacy and objectives of the present invention, shall still fall within the scope of the technical contents disclosed herein.

[0038] Figure 1 A schematic diagram of the logical structure of a system for service discovery and traffic orchestration based on DHCP and DNS collaboration provided by an embodiment of the present invention;

[0039] Figure 2 A flow chart of a method for service discovery and traffic orchestration based on DHCP and DNS collaboration provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0040] The following describes the implementation of the present invention using specific embodiments. Those skilled in the art will readily understand the other advantages and benefits of the present invention from the disclosure herein. Obviously, the embodiments described are only a portion of the present invention, not all of it. All other embodiments derived by persons of ordinary skill in the art based on the embodiments of the present invention without inventive effort are intended to fall within the scope of protection of the present invention.

[0041] In order to solve the problem that the domain name cannot be dynamically adjusted and the service discovery is rigid due to the lack of coordination between DHCP and DNS in the above-mentioned existing technology.

[0042] refer to Figure 1 The embodiment of the present invention discloses a service discovery and traffic orchestration system based on DHCP and DNS collaboration, which includes: a terminal automatic monitoring module 1; an IP address and domain name collaborative planning module 2; and a dynamic domain name orchestration module 3.

[0043] Furthermore, the terminal automatic monitoring module is implemented through the IPAM function of the DHCP server, and the monitoring data includes device fingerprint and service port information.

[0044] The terminal automatic monitoring module 1 can continuously monitor and scan the status information of all perceived terminals, and can also send instructions to indirectly obtain terminal information from other devices (including but not limited to fingerprints, device type and specifications, connected network location, services provided, device load conditions, etc.).

[0045] Construct IP address and domain name collaborative planning module 2. During the network deployment phase, network administrators can pre-formulate corresponding planning strategies for IP addresses and domain names based on the network's organizational structure, business function division, and equipment management requirements (IP addresses are expanded in binary from front to back to divide into multiple specific semantic spaces, and semantic spaces are assigned identifiers and domain names are specified).

[0046] For example, "dns.2building.1room.zdns.cn" represents the DNS server located in Unit 1, Building 2. When the DHCP server assigns an IP address, it automatically assigns the corresponding domain name to the client based on pre-defined planning policies, achieving a close association and collaborative management of IP addresses and domain names. A designated domain name segment is reserved to identify the services provided (the first domain name field is recommended). This allows for automatic matching with specific services based on the results returned by the terminal's automatic monitoring module, dynamically assigning the domain name associated with the service, and facilitating service discovery by other devices through the domain name.

[0047] The dynamic domain name orchestration module 3 is introduced into the DHCP server. It indirectly influences the direction of network traffic by adjusting the domain name resolution results and orchestrates the traffic interactions between devices.

[0048] This module dynamically generates domain names based on the domain name generation strategy established by the "IP Address and Domain Name Collaborative Planning System." It then uses the information scanned by the "Terminal Automatic Monitoring Module" to orchestrate the domain name and resolution results and send API instructions to the DNS server. This orchestration only applies to multiple record values ​​associated with the same domain name, eliminating the need to orchestrate between different domain names.

[0049] For example, the dynamic domain name orchestration module 3 will issue record sorting instructions to the DNS server based on the performance and business load of the terminal device (record sorting can also support configurable ratios; a higher ratio means a higher probability of returning records at the top), dynamically adjusting the order of the record values ​​returned by the DNS server, thereby affecting the traffic direction of accessing these terminals; the orchestration module will also issue the corresponding relationship between ACLs and views to the DNS server based on network congestion, latency, and geographic location information to achieve local access to different services.

[0050] The embodiment of the present invention innovatively introduces an IP address and domain name collaborative planning module into the DHCP server, realizes the synchronous planning of IP addresses and domain names, and dynamically associates certain domain name fields with the services that the terminal can provide, so that other interacting parties can find devices that provide specific services in specific places based only on the domain name, and the domain name itself is also a convenient memory for semantic planning. The dynamic domain name orchestration technology is introduced into the DHCP server so that it can be deeply linked with the DNS server. By utilizing the terminal information mastered by the DHCP server, the domain name and its associated resolution results are orchestrated, which can realize the ability to access services, adjust the traffic distribution between devices of the same service, and so on.

[0051] Corresponding to the aforementioned system for service discovery and traffic orchestration based on DHCP and DNS collaboration, embodiments of the present invention also disclose a method for service discovery and traffic orchestration based on DHCP and DNS collaboration. The following describes in detail the method for service discovery and traffic orchestration based on DHCP and DNS collaboration disclosed in embodiments of the present invention, in conjunction with the aforementioned system for service discovery and traffic orchestration based on DHCP and DNS collaboration.

[0052] refer to Figure 2 , the present invention discloses a method for service discovery and traffic orchestration based on DHCP and DNS collaboration, the method comprising: continuously collecting status information of all perceptible terminals, the status information including fingerprint, device type, network location, service type and load index; predefining semantic domain name rules through IP address and domain name collaborative planning strategy in the network deployment stage, the semantic domain name rules associate domain name fields with terminal attributes, and when the DHCP server assigns an IP address, dynamically generates a domain name according to the semantic domain name rules; obtaining status information of the corresponding terminal, orchestrating multiple DNS record values ​​associated with the same domain name, and sending static configuration instructions to the DNS server, the DNS server responds to the instructions and updates the records, thereby realizing dynamic service discovery and traffic steering.

[0053] Furthermore, continuously collecting status information of all perceptible terminals also includes indirectly obtaining terminal information by sending instructions.

[0054] Furthermore, when the terminal status information changes, a dynamic update of the domain name is triggered, including automatic reorganization of the location identification field when the device location migrates.

[0055] Furthermore, the semantic domain name rule includes a location identification field and a service type field. The location identification field is generated according to the binary segment mapping of the IP address, and the location hierarchy includes a building number, a floor, and an area number.

[0056] Furthermore, multiple DNS record values ​​associated with the same domain name are arranged, including: dynamically adjusting the order of DNS return records according to the terminal load, where the records corresponding to terminals with low load are sorted higher; issuing ACL policies to the DNS server to achieve local access based on the terminal's geographical location and network status; when the terminal is offline or the load exceeds the threshold, sending instructions to the DNS server to delete the corresponding records.

[0057] Furthermore, the static configuration instructions sent to the DNS server include but are not limited to: A record, AAAA record, PTR record, SRV record, TXT record, and NAPTR record.

[0058] The embodiments of the present invention enable the DHCP server to dynamically adjust the corresponding domain name according to the real-time status changes of the client after allocating an IP address to the client, thereby improving the flexibility and adaptability of network services and meeting the diverse needs for domain name management in different network application scenarios; establish a collaborative planning mechanism between IP addresses and domain names, ensure that through reasonable domain name design, users can quickly associate or infer relevant information about the terminal device or service to be accessed only through the domain name, simplify the network management process, and improve the accessibility and manageability of network services; rely solely on the DHCP server's own service detection and discovery mechanism to arrange domain names and record values ​​and issue static instructions to the DNS server, eliminating the need for the DNS server to have a detection function, thereby reducing the maintenance and use costs of the DNS server.

[0059] For example, in a smart campus IoT scenario, a large number of sensor devices (such as temperature and humidity sensors, cameras, etc.) are connected via wireless networks, and their IP addresses are dynamically assigned by a DHCP server. Devices may need to dynamically change their service type or location identifier due to movement or functional adjustments.

[0060] 1) Realize coordinated planning and configuration of IP and domain names:

[0061] The network administrator predefines the domain name semantic rules: <service type>.<floor>.<region>.iot.zdns.cn

[0062] For example, the temperature and humidity sensor is located in the east area of ​​the 3rd floor, and the corresponding domain name is sensor.3f.east.iot.zdns.cn;

[0063] The DHCP server binds the IP address to the above domain name template according to the IP address allocation rules (such as IP address segments divided by floor and area).

[0064] 2) Automatic terminal monitoring and domain name generation:

[0065] When the temperature and humidity sensor is first connected to the network, the DHCP server obtains its device type (sensor), location (3F-East), and service type (environmental monitoring) through the terminal automatic monitoring module;

[0066] According to the collaborative planning strategy, the domain name sensor.3f.east.iot.zdns.cn is automatically generated and pushed to the DNS server for registration.

[0067] 3) Dynamic domain name arrangement and traffic adjustment:

[0068] If the sensor is moved to the west area of ​​the 4th floor for maintenance, the terminal monitoring module detects the location change and triggers the dynamic domain name orchestration module to update the domain name to sensor.4f.west.iot.zdns.cn;

[0069] The DNS server updates the records synchronously, and other devices can access the sensor through the new domain name without manual intervention.

[0070] At this time, when the device moves or the service changes, the domain name is automatically updated to ensure real-time service discovery; the administrator can infer the device location and function through the domain name, reducing management complexity; other applications connected to the device can be pre-built with the domain name according to the plan, so that the device can be discovered and used after it goes online.

[0071] Or in a cloud computing scenario:

[0072] A cloud service provider needs to deploy multiple servers for the same application (such as a web service) and implement load balancing through DNS round-robin. Traditional solutions rely on DNS to dynamically detect server status, which incurs performance overhead.

[0073] 1) IP and domain name collaborative planning

[0074] Define the domain name rule: web<cluster number>.<data center>.cloud.zdns.cn, for example, web01.us-east.cloud.zdns.cn.

[0075] The DHCP server allocates consecutive IP address segments to servers in the same cluster and associates them with the domain name cluster ID.

[0076] 2) Terminal status monitoring and record arrangement

[0077] The terminal monitoring module of the DHCP server collects the load indicators of each server (CPU, memory utilization, etc.) in real time

[0078] The dynamic domain name orchestration module sends record sorting instructions to the DNS server based on the load:

[0079] ① The servers with lower loads have corresponding returned records that are closer to the front or are closer to the front more often.

[0080] ② The return records corresponding to servers with excessive load are placed at the end or deleted from the return records.

[0081] 3) Traffic Scheduling Effect

[0082] When users access web01.us-east.cloud.zdns.cn, the IP addresses of low-load servers returned by DNS are higher or higher in the front.

[0083] When a server fails, the DHCP server detects the offline state and notifies the DNS server to remove the corresponding record.

[0084] It can be seen that in the cloud computing scenario, there is no need for active detection by the DNS server. DHCP can directly drive the DNS configuration resolution strategy based on existing capabilities, reducing the requirements for the DNS server. At the same time, it supports the server's automatic expansion and contraction strategy and automatically performs business load balancing.

[0085] The embodiments of the present invention have the following advantages:

[0086] 1) Simplify network management process:

[0087] The establishment of a collaborative planning module for IP addresses and domain names makes it easier for network administrators to manage and discover devices and services on the network. Through a unified planning strategy, users can identify the department, location, and function of devices by domain name, reducing human errors and query costs in network management and improving the efficiency and accuracy of domain name transformation of network management.

[0088] 2) Improve network service flexibility:

[0089] The dynamic domain name orchestration module allows the DHCP server to adjust domain names and record values ​​in real time based on client status changes, allowing network services to better adapt to different application scenarios and user needs. For example, in an IoT environment, where the location and function of devices may change frequently, dynamic domain name adjustment ensures that devices can be accessed using the appropriate domain name regardless of their status, improving the flexibility and scalability of IoT services.

[0090] 3) Reduce service deployment and maintenance costs:

[0091] The DNS server is one of the most critical core services in the network. By leveraging the existing capabilities of the DHCP server and orchestrating the resolution and issuing static configurations on the DHCP server, the requirements for the DNS server's own capabilities are reduced and its stability is improved.

[0092] Although the present invention has been described in detail above using general descriptions and specific embodiments, it will be apparent to those skilled in the art that modifications and improvements may be made thereto. Therefore, such modifications and improvements, without departing from the spirit of the present invention, are intended to be within the scope of protection claimed herein.

Claims

1. A method for service discovery and traffic orchestration based on DHCP and DNS collaboration, characterized in that: The method comprises: Continuously collect status information of all perceptible terminals, including fingerprint, device type, network location, service type and load indicators; During the network deployment phase, semantic domain name rules are predefined through the IP address and domain name collaborative planning strategy. These semantic domain name rules associate domain name fields with terminal attributes. When the DHCP server assigns an IP address, a domain name is dynamically generated based on these semantic domain name rules. Obtain the status information of the corresponding terminal, organize multiple DNS record values ​​associated with the same domain name, and send static configuration instructions to the DNS server. The DNS server responds to the instructions and updates the records to achieve dynamic service discovery and traffic guidance.

2. The method for service discovery and traffic orchestration based on DHCP and DNS collaboration as claimed in claim 1, characterized in that: Continuously collecting status information of all perceptible terminals also includes indirectly obtaining terminal information by sending instructions.

3. The method for service discovery and traffic orchestration based on DHCP and DNS collaboration as claimed in claim 2, characterized in that: When the terminal status information changes, the domain name is dynamically updated, including automatic reorganization of the location identification field when the device moves.

4. The method for service discovery and traffic orchestration based on DHCP and DNS collaboration as claimed in claim 1, characterized in that: The semantic domain name rule includes a location identification field and a service type field. The location identification field is generated according to the binary segment mapping of the IP address, and the location hierarchy includes a building number, a floor, and an area number.

5. The method for service discovery and traffic orchestration based on DHCP and DNS collaboration as claimed in claim 1, characterized in that: Arrange multiple DNS record values ​​associated with the same domain name, including: Dynamically adjust the order of DNS return records based on terminal load, with records for terminals with lower loads being ranked higher. Based on the terminal's geographic location and network status, ACL policies are issued to the DNS server to achieve local access. When the terminal is offline or the load exceeds the threshold, an instruction is sent to the DNS server to delete the corresponding record.

6. The method for service discovery and traffic orchestration based on DHCP and DNS collaboration as claimed in claim 5, characterized in that: Static configuration instructions sent to the DNS server include but are not limited to: A records, AAAA records, PTR records, SRV records, TXT records, and NAPTR records.

7. A service discovery and traffic orchestration system based on DHCP and DNS collaboration, characterized in that: The system comprises: The terminal automatic monitoring module is used to continuously collect status information of all perceived terminals, including fingerprints, device types, network locations, service types, and load indicators; An IP address and domain name collaborative planning module is used to predefine semantic domain name rules using the IP address and domain name collaborative planning strategy during the network deployment phase. The semantic domain name rules associate domain name fields with terminal attributes. When the DHCP server assigns an IP address, a domain name is dynamically generated according to the semantic domain name rules. The dynamic domain name orchestration module is used to obtain the status information of the corresponding terminal, orchestrate multiple DNS record values ​​associated with the same domain name, and send static configuration instructions to the DNS server. The DNS server responds to the instructions and updates the records to achieve dynamic service discovery and traffic guidance.

8. The system for service discovery and traffic orchestration based on DHCP and DNS collaboration as claimed in claim 7, characterized in that: The terminal automatic monitoring module is implemented through the IPAM function of the DHCP server, and the monitoring data includes device fingerprint and service port information.

Images