Configuration method of IPv6 address stored in DNS (Domain Name Server) corresponding to power grid equipment and related equipment

Abstract

The invention provides a configuration method of an IPv6 address stored in a DNS (Domain Name Server) corresponding to power grid equipment and related equipment. The method comprises the following steps: acquiring geographical location information and identification information corresponding to the power grid equipment; based on the geographical location information, determining a routable prefix of an IPv6 address corresponding to the power grid equipment; determining a settable suffix of an IPv6 address corresponding to the power grid equipment based on the geographical location information and the identification information; and combining the routable prefix and the settable suffix to obtain the IPv6 address of the power grid equipment, thereby solving the technical problem that each power grid enterprise lacks a unified configuration rule for configuring the IPv6 address of the power grid equipment in the prior art, and improving the configuration efficiency of the IPv6 address of the power grid equipment.

Description

Technical Field

[0001] This application relates to the technical field of data processing, and in particular, to a method for configuring an IPv6 address stored in DNS corresponding to a power grid device and related devices. Background Art

[0002] With the rapid development of the Industrial Internet of Things (IIoT), power grid companies have deployed a large number of power grid device nodes in scenarios such as substations, transmission lines, and power supply facilities. These power grid devices are used to monitor the operating status of power equipment and environmental parameters (such as temperature, gas concentration, security information, etc.), forming a huge power grid device network. Allocating IPv6 addresses to power grid devices is an inevitable requirement for the development of the industrial Internet of Things.

[0003] In the prior art, there are many power grid enterprises under the power grid. During the IPv6 address planning process of power grid devices, each power grid enterprise independently plans the last 64 bits of the IPv6 address of the power grid device. However, there are relatively many power grid enterprises and relatively many power grid devices in each power grid enterprise. If each power grid enterprise independently plans the IPv6 address of the power grid device, it will be time-consuming and laborious for each power grid enterprise, and the management of the IPv6 address of the power grid device will be chaotic. Therefore, it is necessary to formulate a unified rule for configuring the IPv6 address of the power grid device to improve the configuration efficiency of the IPv6 address of the power grid device by each power grid enterprise. Summary of the Invention

[0004] In view of this, the purpose of this application is to propose a method for configuring an IPv6 address stored in DNS corresponding to a power grid device and related devices to overcome all or part of the deficiencies in the prior art.

[0005] Based on the above purpose, this application provides a method for configuring an IPv6 address stored in DNS corresponding to a power grid device, including: obtaining the geographical location information and identification information corresponding to the power grid device; determining the routable prefix of the IPv6 address corresponding to the power grid device based on the geographical location information; determining the settable suffix of the IPv6 address corresponding to the power grid device based on the geographical location information and the identification information; and combining the routable prefix and the settable suffix to obtain the IPv6 address of the power grid device.

[0006] Optionally, the geographical location information includes the district information, the location information, and the production line information where the power grid device is located; determining the settable suffix of the IPv6 address corresponding to the power grid device based on the geographical location information and the identification information includes: determining a first data corresponding to the district information according to a pre-constructed correspondence between district information and data; determining a second data corresponding to the location information according to a pre-constructed correspondence between location information and data; determining a third data corresponding to the production line information according to a pre-constructed correspondence between production line information and data; determining a fourth data corresponding to the identification information according to a pre-constructed correspondence between identification information and data; and sequentially combining the first data, the second data, the third data, and the fourth data to obtain the settable suffix.

[0007] Optionally, the geographical location information includes the urban area where the power grid device is located; determining the routable prefix of the IPv6 address corresponding to the power grid device based on the geographical location information includes: determining the routable prefix corresponding to the urban area according to a pre-constructed correspondence between urban areas and routable prefixes.

[0008] Optionally, the geographical location information includes the urban area where the power grid device is located; after combining the routable prefix and the settable suffix to obtain the IPv6 address of the power grid device, the method includes: storing the IPv6 address in a pre-constructed domain name table corresponding to the urban area where the power grid device is located, and storing the domain name table in a server corresponding to the urban area.

[0009] Optionally, after storing the domain name table in the server corresponding to the urban area, the method includes: in response to receiving a query instruction for the IPv6 address of the power grid device, determining the urban area where the query instruction is issued; and querying the IPv6 address of the power grid device based on the urban area where the power grid device is located, the urban area where the query instruction is issued, the geographical location information, and the identification information.

[0010] Optionally, querying the IPv6 address of the power grid device based on the urban area where the power grid device is located, the sending urban area, the geographical location information, and the identification information includes: in response to determining that the urban area where the power grid device is located is the same as the sending urban area, querying a first domain name table corresponding to the sending urban area, and querying the IPv6 address of the power grid device in the first domain name table based on the urban area where the power grid device is located, the geographical location information, and the identification information; in response to determining that the urban area where the power grid device is located is different from the sending urban area, sending an access request to a server corresponding to the urban area where the power grid device is located; in response to determining that the server passes the access request, querying a second domain name table corresponding to the urban area where the power grid device is located, and querying the IPv6 address of the power grid device in the second domain name table based on the urban area where the power grid device is located, the geographical location information, and the identification information.

[0011] Optionally, after combining the routable prefix and the configurable suffix to obtain the IPv6 address of the power grid device, the method further includes: verifying whether the number of data bits of the IPv6 address is equal to a predetermined number of data bits; in response to determining that the number of data bits is equal to the predetermined number of data bits, determining that the IPv6 address passes the verification.

[0012] Based on the same inventive concept, the present application also provides a configuration device for the IPv6 address stored in DNS corresponding to a power grid device, including: an acquisition module configured to acquire the geographical location information and identification information corresponding to the power grid device; a first determination module configured to determine a routable prefix of the IPv6 address corresponding to the power grid device based on the geographical location information; a second determination module configured to determine a configurable suffix of the IPv6 address corresponding to the power grid device based on the geographical location information and the identification information; and a combination module configured to combine the routable prefix and the configurable suffix to obtain the IPv6 address of the power grid device.

[0013] Based on the same inventive concept, the present application also provides an electronic device, including a memory, a processor, and a computer program stored on the memory and executable by the processor, where the processor implements the method as described above when executing the computer program.

[0014] Based on the same inventive concept, the present application also provides a non-transitory computer-readable storage medium storing computer instructions for causing a computer to execute the method as described above.

[0015] As can be seen from the above, the present application provides a method for configuring an IPv6 address stored in DNS corresponding to a power grid device and related devices. The method includes obtaining geographical location information and identification information corresponding to the power grid device. Based on the geographical location information, a routable prefix of the IPv6 address corresponding to the power grid device is determined. The routable prefix of the IPv6 address corresponding to the power grid device determined based on the geographical location information is accurate. Based on the geographical location information and the identification information, a settable suffix of the IPv6 address corresponding to the power grid device is determined, improving the efficiency of setting the settable suffix. The routable prefix and the settable suffix are combined to obtain the IPv6 address of the power grid device. Configuring the IPv6 address of the power grid device using a unified rule not only improves the configuration efficiency of the IPv6 address of the power grid device but also facilitates the management of the IPv6 addresses of numerous power grid devices. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] To more clearly illustrate the technical solutions in the present application or related technologies, the following will briefly introduce the drawings required for use in the embodiments or related technology descriptions. Obviously, the drawings in the following description are only embodiments of the present application. For those of ordinary skill in the art, without creative efforts, other drawings can be obtained based on these drawings.

[0017] Figure 1 Schematic flowchart of a method for configuring an IPv6 address stored in DNS corresponding to a power grid device according to an embodiment of the present application;

[0018] Figure 2 Schematic diagram of the composition of the IPv6 address of a power grid device according to an embodiment of the present application;

[0019] Figure 3 Schematic flowchart of a method for configuring an IPv6 address stored in DNS corresponding to a power grid device according to another embodiment of the present application;

[0020] Figure 4 Schematic structural diagram of a device for configuring an IPv6 address stored in DNS corresponding to a power grid device according to an embodiment of the present application;

[0021] Figure 5 Schematic diagram of the hardware structure of an electronic device according to an embodiment of the present application. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0022] To make the objectives, technical solutions, and advantages of the present application clearer and more understandable, the following further details the present application in combination with specific embodiments and with reference to the accompanying drawings.

[0023] It should be noted that, unless otherwise defined, the technical terms or scientific terms used in the embodiments of this application should have the ordinary meanings understood by those with ordinary skills in the field to which this application belongs. The "first", "second" and similar words used in the embodiments of this application do not indicate any order, quantity or importance, but are only used to distinguish different components. Words such as "including" or "comprising" mean that the elements or objects appearing before this word cover the elements or objects listed after this word and their equivalents, without excluding other elements or objects. Words such as "connected" or "linked" are not limited to physical or mechanical connections, but may include electrical connections, whether direct or indirect. "Upper", "lower", "left", "right", etc. are only used to represent relative position relationships. When the absolute position of the object being described changes, the relative position relationship may also change accordingly.

[0024] As described in the background art section, with the rapid development of the Internet of Things for power grids, power grid companies have deployed a large number of power grid device nodes in scenarios such as substations, transmission lines, and power supply facilities. These power grid devices are used to monitor the operating status of power equipment and environmental parameters (such as temperature, gas concentration, security information, etc.), forming a huge power grid device network. Allocating IPv6 addresses to power grid devices is an inevitable requirement for the development of the industrial Internet of Things. An IPv6 address is a 128-bit address used to identify devices or interfaces on the network in the Internet Protocol Version 6. The huge address space of IPv6 can meet the access requirements of a large number of power terminals (such as smart meters, sensors, and relay protection devices) and solve the problem of IPv4 address exhaustion.

[0025] In the prior art, there are many power grid enterprises under the power grid. During the process of IPv6 address planning for power grid devices, each power grid enterprise independently plans the last 64 bits of the IPv6 addresses of power grid devices. However, there are relatively many power grid enterprises and relatively many power grid devices in each power grid enterprise. If each power grid enterprise independently plans the IPv6 addresses of power grid devices, it will be time-consuming and laborious for each power grid enterprise. Therefore, it is necessary to formulate a unified rule for configuring the IPv6 addresses of power grid devices to improve the configuration efficiency of the IPv6 addresses of power grid devices by each power grid enterprise.

[0026] In addition to the above problems, after the IPv6 address of the power grid device is configured using the existing technology, there is still a problem of finding the IPv6 address of the power grid device. The existing DNS (Domain Name System) resolution method needs to query one by one, parsing the human-readable semantic information into machine-readable IP addresses, resulting in a huge DNS table entry scale and low query efficiency, which is difficult to meet the requirements of high concurrency and ultra-large-scale networks in the power grid Internet of Things. Among them, the DNS table entry is a record stored in the DNS for resolving the mapping relationship between domain names and IP addresses. In the traditional network architecture, accessing sensor nodes usually relies on a naming service similar to DNS, called Object Name Service (ONS), which parses human-readable semantic information into machine-readable IP addresses. For the sake of simplicity of narration, DNS and ONS will be uniformly described as DNS hereinafter. However, with the expansion of the network scale and the rapid increase in the number of nodes, many problems have emerged in the traditional DNS resolution method. First, the DNS table entry scale is huge. Each sensor node requires a DNS table entry, resulting in a rapid expansion of the DNS table entry scale as the number of nodes increases. Second, the query efficiency is low. The visitor needs to parse the semantic information into an IP address by querying one by one. This method will generate huge network overhead in the scenario of a large number of nodes. Especially when real-time monitoring or big data analysis is required, frequent parsing requests will seriously affect the system performance. In addition, the centralized architecture of the traditional DNS resolution method is prone to single-point overload and is difficult to meet the requirements of high concurrency and ultra-large-scale networks in the power grid Internet of Things.

[0027] In view of this, an embodiment of the present application proposes a method for configuring the IPv6 address corresponding to a power grid device stored in DNS, referring to Figure 1 , including the following steps:

[0028] Step 101, obtain the geographical location information and identification information corresponding to the power grid device.

[0029] In this step, with the rapid development of the Internet of Things for power grids, more and more power grid devices have the need to be connected to the network, and it is necessary to assign IPv6 addresses to power grid devices. Since there are relatively many power grid companies and power grid devices in power grid companies, if each power grid company configures the IPv6 addresses of power grid devices without a unified rule, it will not only cause each power grid enterprise to spend a lot of time and effort, but also lead to chaos in the management of the IPv6 addresses of power grid devices. Therefore, it is necessary to configure IPv6 addresses for the power grid devices of each power grid company using a unified configuration rule. First, obtain the geographical location information of the power grid device. Among them, the power grid device is a device with networking function in the power grid. For example, the power grid device is a smart meter, a sensor or a controller, etc. The geographical location information can indicate the location where the power grid device is located. Since there may be other power grid devices at the location where the power grid device is located, in order to accurately distinguish each power grid device, it is also necessary to obtain the identification information of the power grid device. Among them, the identification information is the unique identifier of the power grid device.

[0030] Step 102: Based on the geographical location information, determine the routable prefix of the IPv6 address corresponding to the power grid device.

[0031] In this step, the first 64 bits of the IPv6 address corresponding to the power grid device are the routable prefix of the IPv6 address. The routable prefix of the IPv6 address is the core part in the global unicast address that is used to identify the network topology and support routing decisions, and it is composed of two parts: the network prefix and the interface identifier. The routable prefix is assigned by the operator according to the geographical location information. Therefore, it is possible to determine the routable prefix of the IPv6 address corresponding to the power grid device based on the geographical location information. Since the geographical location information of the power grid device can accurately reflect the geographical location of the power grid device, the routable prefix of the IPv6 address corresponding to the power grid device determined based on the geographical location information is accurate.

[0032] Step 103: Based on the geographical location information and the identification information, determine the configurable suffix of the IPv6 address corresponding to the power grid device.

[0033] In this step, the last 64 bits of the IPv6 address corresponding to the power grid device are the settable suffix of the IPv6 address, and the settable suffix can be set by the user. Since there are many power grid devices, in order to facilitate the management of the IPv6 addresses of the power grid devices, based on the geographical location information and identification information of the power grid devices, the settable suffix of the IPv6 address corresponding to the power grid device is determined. Only using the geographical location information cannot accurately distinguish many power grid devices. Therefore, in this application, many power grid devices are distinguished by using the geographical location information and identification information together, so that the power grid devices are unique. Therefore, using the geographical location information and identification information to determine the settable suffix of the IPv6 address corresponding to the power grid device is also unique. Embedding the identity semantic information of the power grid device in the settable suffix of the IPv6 address and using a unified rule to set the settable suffix of the IPv6 address corresponding to many power grid devices improves the efficiency of setting the settable suffix.

[0034] Step 104, combine the routable prefix and the settable suffix to obtain the IPv6 address of the power grid device.

[0035] In this step, the routable prefix is the first 64 bits of the IPv6 address, the settable suffix is the last 64 bits of the IPv6 address, and the IPv6 address includes a total of 128 bits. Therefore, combine the routable prefix and the settable suffix to obtain the IPv6 address of the power grid device. Since the last 64 bits of the IPv6 address are settable, the geographical location information and identification information that can accurately distinguish many power grid devices are used together to determine the last 64 bits of the IPv6 address, which not only improves the setting efficiency but also facilitates the management of the settable suffix. Furthermore, as Figure 2 shown, by combining the routable prefix and the settable suffix to obtain the IPv6 address of the power grid device and configuring the IPv6 address of the power grid device using a unified rule, it also improves the configuration efficiency of the IPv6 address of the power grid device and facilitates the management of the IPv6 addresses of many power grid devices.

[0036] Through the above solution, the geographical location information and identification information corresponding to the power grid device are obtained. Based on the geographical location information, the routable prefix of the IPv6 address corresponding to the power grid device is determined, and the routable prefix of the IPv6 address corresponding to the power grid device determined based on the geographical location information is accurate. Based on the geographical location information and the identification information, the settable suffix of the IPv6 address corresponding to the power grid device is determined, which improves the efficiency of setting the settable suffix. The routable prefix and the settable suffix are combined to obtain the IPv6 address of the power grid device, and the IPv6 address of the power grid device is configured using a unified rule, which not only improves the configuration efficiency of the IPv6 address of the power grid device but also facilitates the management of the IPv6 addresses of numerous power grid devices.

[0037] In some embodiments, the geographical location information includes the district / county information, the location information, and the production line information where the power grid device is located; the determining the settable suffix of the IPv6 address corresponding to the power grid device based on the geographical location information and the identification information includes: determining the first data corresponding to the district / county information according to the pre-constructed correspondence between the district / county information and the data; determining the second data corresponding to the location information according to the pre-constructed correspondence between the location information and the data; determining the third data corresponding to the production line information according to the pre-constructed correspondence between the production line information and the data; determining the fourth data corresponding to the identification information according to the pre-constructed correspondence between the identification information and the data; and sequentially combining the first data, the second data, the third data, and the fourth data to obtain the settable suffix.

[0038] In this embodiment, in the industrial Internet of Things of the power grid company, there are a large number of power grid devices that need to be efficiently addressed and managed. These power grid devices are distributed in different cities, districts / counties, substations, locations, and production lines. The geographical location information can indicate the geographical location of the power grid device, where the geographical location information includes the district / county information, the location information, and the production line information where the power grid device is located. The identification information can uniquely identify the power grid device. The identification information can be the identification of the power grid device in the production line where it is located, and the identification information can be composed of the power grid device and a symbol. Exemplarily, Sensor 1 and Sensor 2 in Production Line A.

[0039] Pre-build the correspondence between district / county information and data, and establish the data corresponding to the district / county information. Among them, the data corresponding to different district / county information is different. Determine the first data corresponding to the district / county information according to the correspondence between the district / county information and the data. Exemplarily, the relationship between the district / county information and the data can exist in the form of a first data table. When the district / county information is determined, search for the first data corresponding to the district / county information in the first data table. Among them, the first data is hexadecimal data, and the number of data bits of the first data is eight. The district / county information includes the district / county name, or the district / county information includes the ID corresponding to the district / county name. To improve the search efficiency, the correspondence between the district / county information and the data includes multiple corresponding sub-relations between the district / county information and the data, and the district / county information in each corresponding sub-relation between the district / county information and the data belongs to the same urban area. To reduce the storage pressure on the server, each corresponding sub-relation between the district / county information and the data can be stored in the server of its corresponding urban area. If cross-server queries are required, that is, the urban area where the query instruction is issued is different from the storage urban area, a query request needs to be sent to the server in the storage urban area. After the server in the storage urban area passes the query request, the relationship stored in the server in the storage urban area can be queried. Multiple corresponding sub-relations between the district / county information and the data correspond to the same urban area.

[0040] Pre-build the correspondence between venue information and data, and establish the data corresponding to the venue information. Among them, in the same district / county, the data corresponding to different venue information is different. Determine the second data corresponding to the venue information according to the correspondence between the venue information and the data. Exemplarily, the correspondence between the venue information and the data can exist in the form of a second data table. When the venue information is determined, search for the second data corresponding to the venue information in the second data table. Among them, the second data is hexadecimal data, and the number of data bits of the second data is sixteen. The venue information includes the venue name, or the venue information includes the ID corresponding to the venue name. To improve the search efficiency, the correspondence between the venue information and the data includes multiple sub-correspondences between the venue information and the data, and the venue information in each corresponding sub-relation between the venue information and the data belongs to the same district / county. To reduce the storage pressure on the server, each corresponding sub-relation between the venue information and the data can be stored in the server of its corresponding urban area according to the district / county information. Multiple corresponding sub-relations between the venue information and the data correspond to the same district / county.

[0041] Pre-construct the correspondence between production line information and data, and establish the data corresponding to the production line information. Among them, in the same location, the data corresponding to different production line information is different. Determine the third data corresponding to the production line information according to the correspondence between the production line information and the data. Exemplarily, the correspondence between the production line information and the data can exist in the form of a third data table. When the production line information is determined, search for the third data corresponding to the production line information in the third data table. Among them, the third data is hexadecimal data, and the number of data bits of the third data is eight. The production line information includes the production line name, or the production line information includes the ID corresponding to the production line name. To improve the search efficiency, the correspondence between the production line information and the data includes multiple sub-correspondences between the production line information and the data, and the location information in each sub-correspondence between the production line information and the data belongs to the same location. To reduce the storage pressure on the server, each sub-correspondence between the production line information and the data can be stored in the server of its corresponding urban area according to the location information. Multiple sub-correspondences between the production line information and the data correspond to the same location information.

[0042] Pre-construct the correspondence between identification information and data, and establish the data corresponding to the identification information. Among them, in the same production line, the data corresponding to different identification information is different. Determine the fourth data corresponding to the identification information according to the correspondence between the identification information and the data. Exemplarily, the correspondence between the identification information and the data can exist in the form of a fourth data table. When the identification information is determined, search for the fourth data corresponding to the identification information in the fourth data table. Among them, the fourth data is hexadecimal data, and the number of data bits of the fourth data is thirty-two. The identification information includes the identifier. Combine the first data, the second data, the third data, and the fourth data in sequence to embed the identity semantic information of the node for identifying a specific node, and obtain a suffix that can be set. By pre-constructing various correspondences to respectively determine the data corresponding to the geographical location information and the identification information, and combining all the determined data into a suffix that can be set, the suffix that can be set has distinguishability, achieving the purpose of accurately determining the suffix that can be set. To improve the search efficiency, the correspondence between the identification information and the data includes multiple sub-correspondences between the identification information and the data, and the location information in each sub-correspondence between the identification information and the data belongs to the same production line. To reduce the storage pressure on the server, each sub-correspondence between the identification information and the data can be stored in the server of its corresponding urban area according to the production line information. Multiple sub-correspondences between the identification information and the data correspond to the same production line information.

[0043] It should be noted that there are bit numbers, that is, the number of data bits, in the first data, the second data, the third data, and the fourth data, and the bit numbers can be set by the user. Exemplarily, the bit number of the first data is 8, the bit number of the second data is 16, the bit number of the third data is 8, and the bit number of the fourth data is 32. The data on each bit number is hexadecimal data.

[0044] In some embodiments, the geographical location information includes the urban area where the power grid device is located; based on the geographical location information, determining the routable prefix of the IPv6 address corresponding to the power grid device includes: determining the routable prefix corresponding to the urban area according to the pre-constructed correspondence between the urban area and the routable prefix.

[0045] In this embodiment, there is a correspondence between the urban area and the routable prefix. This correspondence is constructed by the operator and can be directly obtained for use. Through the geographical location information, the urban area where the power grid device is located can be quickly located, and the corresponding routable prefix can be determined according to the urban area. Exemplarily, the correspondence between the urban area and the routable prefix can exist in the form of a data table. When the urban area is determined, the routable prefix corresponding to the urban area is searched in the data table. Since the urban area in the geographical location information is accurate and unique, the routable prefix of the IPv6 address can be accurately determined through the geographical location information.

[0046] In some embodiments, the geographical location information includes the urban area where the power grid device is located; after combining the routable prefix and the configurable suffix to obtain the IPv6 address of the power grid device, the method includes: storing the IPv6 address in the pre-constructed domain name table corresponding to the urban area where the power grid device is located, and storing the domain name table in the server corresponding to the urban area.

[0047] In this embodiment, in order to facilitate the unified management of the IPv6 addresses of power grid devices, the IPv6 addresses are stored in the pre-constructed domain name table corresponding to the urban area where the power grid devices are located, and the domain name table is stored in the server corresponding to the urban area, where the domain name table is stored in the DNS. Since there are relatively many power grid devices, there are relatively many corresponding IPv6 addresses. Storing and managing the IPv6 addresses of power grid devices according to the urban areas where the power grid devices are located achieves the purpose of reasonably managing the IPv6 addresses.

[0048] It should be noted that the power grid devices are stored according to the urban areas where they are located. Since the routable prefixes of the power grid devices in the same urban area are the same, only the configurable suffixes of the power grid devices can be stored in the domain name table. When the user has a query requirement for the IPv6 address of the power grid device, the routable prefix where the power grid device is located is obtained, and the routable prefix is combined with the found configurable suffix to obtain the IPv6 address of the power grid device, saving storage space. Through the aggregated design of the routable prefix, the routable prefix can be determined only by the urban area where the power grid device is located, greatly reducing the number of DNS entries and the complexity of resolution.

[0049] In some embodiments, after storing the domain name table to the server corresponding to the urban area, the method includes: in response to receiving a query instruction for the IPv6 address of the power grid device, determining the urban area where the query instruction is issued; querying the IPv6 address of the power grid device based on the urban area where the power grid device is located, the urban area where the query instruction is issued, the geographical location information, and the identification information.

[0050] In this embodiment, the user has a query requirement for the IPv6 address of the power grid device and issues a query instruction. When receiving the query instruction for the IPv6 address of the power grid device, the urban area where the query instruction is issued is determined. Since the IPv6 address of the power grid device is stored according to the urban area where it is located and the IPv6 address of the power grid device is determined based on the geographical location information and the identification information, therefore, based on the urban area where the power grid device is located, the urban area where the query instruction is issued, the geographical location, and the identification information, the IPv6 address of the power grid device is queried. Querying the IPv6 address of the power grid device using the known information of the power grid device improves the query efficiency of the IPv6 address. By embedding the identity semantics, the IPv6 address itself has the semantic expression ability, and the visitor can directly obtain the routable prefix and the settable suffix of the IPv6 address through the relevant information of the power grid device, simplifying the DNS table entry query process.

[0051] In some embodiments, the querying the IPv6 address of the power grid device based on the urban area where the power grid device is located, the urban area where the query instruction is issued, the geographical location information, and the identification information includes: in response to determining that the urban area where the power grid device is located is the same as the urban area where the query instruction is issued, querying the first domain name table corresponding to the urban area where the query instruction is issued, and querying the IPv6 address of the power grid device in the first domain name table based on the urban area where the power grid device is located, the geographical location information, and the identification information; in response to determining that the urban area where the power grid device is located is different from the urban area where the query instruction is issued, sending an access request to the server corresponding to the urban area where the power grid device is located; in response to determining that the server passes the access request, querying the second domain name table corresponding to the urban area where the power grid device is located, and querying the IPv6 address of the power grid device in the second domain name table based on the urban area where the power grid device is located, the geographical location information, and the identification information.

[0052] In this embodiment, when the urban area where the power grid device is located is the same as the urban area where the query instruction is issued, the server corresponding to this urban area performs the query processing, directly queries the first domain name table corresponding to the issuing urban area, and the IPv6 address of the power grid device can be queried based on the urban area where the power grid device is located, the geographical location information, and the identification information. Based on the above information, the IPv6 address of the power grid device is queried in the first domain name table, which improves the query efficiency of the IPv6 address of the power grid device. When the urban area where the power grid device is located is different from the issuing urban area, it means that cross-server query is required. First, an access request needs to be sent to the urban area where the power grid device is located. When the server passes the access request, query the second domain name table corresponding to the urban area where the power grid device is located. The IPv6 address of the power grid device can be queried from multiple corresponding relationships based on the urban area where the power grid device is located, the geographical location information, and the identification information. Based on the IPv6 address queried from multiple relationship tables, query the IPv6 address of the power grid device in the second domain name table. If the IPv6 addresses queried twice are the same, it indicates that the queried IPv6 address is accurate, which improves the query accuracy of the IPv6 address of the power grid device.

[0053] In addition, since the geographical location information and identification information of the power grid device have been obtained, the IPv6 address of the power grid device can be found, which provides effective information for finding the IPv6 address in the domain name table and improves the query efficiency. Through this load sharing design, query requests are distributed to each regional DNS server, avoiding single-point overload, improving the stability and query efficiency of the system, enhancing the addressing efficiency and real-time performance, while reducing the DNS table entry scale and network load, providing important technical support for the efficient operation of the power grid Internet of Things, and is particularly suitable for the efficient addressing and management of a large number of nodes in the power grid Internet of Things. The lightweight DNS resolution method based on load sharing not only solves the performance bottleneck problem of the traditional DNS resolution method, but also provides reliable technical guarantee for the efficient operation of the power grid Internet of Things, and can meet the actual needs of the ultra-large-scale network in the industrial Internet of Things of power grid companies. It should be noted that the correctness of the DNS table entries also needs to be verified periodically, and the mapping relationship between the DNS table entries and the local identity semantic mapping table needs to be checked regularly to ensure data consistency.

[0054] In another embodiment provided by the present application, in response to receiving a query instruction for the IPv6 address of a power grid device, the IPv6 address of the power grid device is queried based on the geographical location information and identification information corresponding to the power grid device, including: determining the routable prefix of the IPv6 address corresponding to the power grid device based on the geographical location information; determining the settable suffix of the IPv6 address corresponding to the power grid device based on the geographical location information and the identification information; combining the routable prefix and the settable suffix to obtain the IPv6 address of the power grid device. After receiving the query instruction, the IPv6 address of the power grid device can be directly queried without passing through DNS, improving the query efficiency.

[0055] In some embodiments, after combining the routable prefix and the settable suffix to obtain the IPv6 address of the power grid device, the method further includes: verifying whether the number of data bits of the IPv6 address is equal to a predetermined number of data bits; in response to determining that the number of data bits is equal to the predetermined number of data bits, determining that the IPv6 address passes the verification.

[0056] In this embodiment, since the IPv6 address should be a 128-bit address, based on this, verify whether the number of data bits of the IPv6 address is equal to the predetermined number of data bits, where the predetermined number of data bits is 128. When the number of data bits of the IPv6 address is equal to the predetermined number of data bits, it indicates that the IPv6 address is correct, and it is determined that the IPv6 address passes the verification. When the number of data bits of the IPv6 address is not equal to the predetermined number of data bits, it indicates that the IPv6 address is incorrect, and it is determined that the IPv6 address fails the verification, and a prompt message is sent to the user to re-determine the IPv6 address. By comparing the number of data bits of the IPv6 address with the predetermined number of data bits, the purpose of accurately verifying whether the IPv6 address passes the verification is achieved.

[0057] In another embodiment provided by the present application, as Figure 3 shown, assume that a certain power grid company has deployed five devices, namely Sensor 1 on Production Line 1 of Substation A in the First District and First County of the First Urban Area, Sensor 1 on Production Line 2 of Substation A in the First District and First County of the First Urban Area, Circuit Breaker 1 on Production Line 1 of Substation A in the First District and First County of the First Urban Area, Circuit Breaker 1 on Production Line 2 of Substation B in the First District and Second County of the First Urban Area, and Sensor 1 on Production Line 1 of Substation C in the Third County of the Second Urban Area. Now, it is necessary to perform IPv6 address allocation and DNS service optimization for the devices in its industrial Internet of Things. The specific implementation is based on the following steps (illustrated with examples):

[0058] Step 1, divide the IPv6 address structure. The first 64 bits are used as the routable prefix, and the range of the routable prefix is specific to the municipal information for quickly locating the target area; the last 64 bits embed the identity semantic information of the node for identifying the specific node;

[0059] Step 2, define the identity semantic information of the last 64 bits of the IPv6 address: District / County information: identifying administrative regions; Site information: identifying substations; Production line information: identifying production lines; Identification information: identifying specific devices.

[0060] Steps 3 - 5 are the processes of constructing multiple corresponding relationships. After construction, the constructed corresponding relationships can be directly used for searching.

[0061] Step 3, the user configures parameters indicating the number of bits required for each semantic information, which are: 8 bits for district / county information; 16 bits for site information; 8 bits for production line information; 32 bits for identification information.

[0062] Step 4, verify the legality of the parameter configuration. Calculate the total length of the last 64 bits to be 64, ensuring that it does not exceed 64 bits, which is legal;

[0063] Step 5, generate an identity semantic mapping table;

[0064] Table 1 Corresponding relationship between district / county information and data

[0065]

[0066]

[0067] Table 2 Corresponding relationship between site information and data

[0068] Location Information Data (Hexadecimal Representation) Substation A 0001 Substation B 0002 Substation C 0003

[0069] Table 3 Corresponding relationship between production line information and data

[0070] Production Line Information Data (Hexadecimal Representation) Production Line 1 01 Production Line 2 02

[0071] Table 4 Corresponding relationship between identification information and data

[0072] Identification Information Data (Hexadecimal Representation) Sensor 1 00000001 Circuit Breaker 1 00000002

[0073] Step 6, perform IPv6 addressing based on the identity semantic information:

[0074] Step 6.1, it is known that the device routing prefix for the first urban area is 2001:0db8:0001:: / 64, and the device routing prefix for the second urban area is 2001:0db8:0002:: / 64. Therefore, the IPv6 addresses are assigned as follows:

[0075] The IPv6 address of Sensor 1 on Production Line 1 of Substation A in the first district / county of the first urban area is: 2001:0db8:0001:0000:0100:0101:0000:0001

[0076] The IPv6 address of Circuit Breaker 1 on Production Line 1 of Substation A in the First District of the First Urban Area is: 2001:0db8:0001:0000:0100:0101:0000:0002

[0077] The IPv6 address of Sensor 1 on Production Line 2 of Substation A in the First District of the First Urban Area is: 2001:0db8:0001:0000:0100:0102:0000:0001

[0078] The IPv6 address of Circuit Breaker 1 on Production Line 2 of Substation B in the Second District of the First Urban Area is: 2001:0db8:0001:0000:0200:0202:0000:0002

[0079] The IPv6 address of Sensor 1 on Production Line 1 of Substation C in the Third District of the Second Urban Area is: 2001:0db8:0002:0000:0300:0301:0000:0001

[0080] Step 6.2, verify the uniqueness of the address. In response to determining that the IPv6 address of the power grid device is unique, it is determined that the IPv6 address passes the address uniqueness verification.

[0081] Step 7, optimize the DNS entry structure, aggregate DNS entries, and convert the individual records in the traditional DNS entries into aggregated records based on the first 64-bit routable prefix.

[0082] Each power grid device in the traditional DNS entry requires a separate entry to be recorded, as shown in Table 5.

[0083] Table 5 IPv6 address table of each power grid device recorded in the traditional DNS entry

[0084]

[0085] By aggregating the first 64-bit routable prefix, the entries are merged, and the optimized DNS entry content is shown in Table 6.

[0086] Table 6 IPv6 address table of each power grid device recorded in the optimized DNS entry

[0087] City where Power Grid Equipment is Located IPv6 Routable Prefix (Hexadecimal Representation) First Urban District 2001:0db8:0001:: / 64 Second Urban District 2001:0db8:0002:: / 64

[0088] Step 8, store the last 64-bit semantic information in the identity semantic mapping table for quickly completing the IPv6 address and cache the identity semantic mapping table on the local device.

[0089] Step 8.1, taking the urban area where the power grid device is located as a unit, the identity semantic mapping tables in different cities only store the last 64-bit semantic information within their respective regions;

[0090] The identity semantic mapping tables stored in the first urban area are shown in Tables 7 - 10:

[0091] Table 7 Correspondence between district / county information and data stored in the first urban area

[0092]

[0093]

[0094] Table 8 Correspondence between venue information and data stored in the first urban area

[0095] Location Information Data (Hexadecimal Representation) Substation A 0001 Substation B 0002

[0096] Table 9 Correspondence between production line information and data stored in the first urban area

[0097] Production Line Information Data (Hexadecimal Representation) Production Line 1 01 Production Line 2 02

[0098] Table 10 Correspondence between identification information and data stored in the first urban area

[0099] Identification Information Data (Hexadecimal Representation) Sensor 1 00000001 Circuit Breaker 1 00000002

[0100] The identity semantic mapping tables stored in the second urban area are shown in Tables 11 - 14:

[0101] Table 11 Correspondence between district / county information and data stored in the second urban area

[0102] District Information Data (Hexadecimal Representation) Third District 03

[0103] Table 12 Correspondence between venue information and data stored in the second urban area

[0104] Location Data (Hexadecimal Representation) Substation C 0003

[0105] Table 13 Correspondence between production line information and data stored in the second urban area

[0106] Production Line Information Data (Hexadecimal Representation) Production Line 1 01

[0107] Table 14 Correspondence between identification information and data stored in the second urban area

[0108] Identification Data (Hexadecimal Representation) Sensor 1 00000001

[0109] It should be noted that the correspondence in the above tables is only an example and does not represent all correspondences.

[0110] Step 8.2, Store the identity semantic mapping table in the corresponding area DNS server;

[0111] Step 8.3, Store the identity semantic mapping table in each node of the corresponding area;

[0112] Step 9, the visitor uses the DNS sharing query resolution method with embedded identity semantics to access the local node "Sensor 1, Production Line 1, Substation A, First District, First City".

[0113] Step 9.1, the visitor inputs the target node information "Sensor 1, Production Line 1, Substation A, First District, First City" and sends a query request to the local DNS server;

[0114] Step 9.2, the local DNS server resolves that the city where the node is located is the First City, and returns the first 64 bits of the IPv6 address "2001:0db8:0001:0000";

[0115] Step 9.3, since the target node accessed by the visitor is a local node, query the local identity semantics mapping table:

[0116] Query the corresponding relationship between district information and data, and obtain the first data corresponding to the district information: 01 (First District).

[0117] Query the corresponding relationship between venue information and data, and the second data corresponding to the venue information: 0001 (Substation A).

[0118] Query the corresponding relationship between production line information and data, and obtain the third data corresponding to the production line information: 01 (Production Line 1).

[0119] Query the corresponding relationship between identification information and data, and obtain the fourth data corresponding to the identification information: 00000001 (Sensor 1).

[0120] Step 9.4, combine the first data, second data, third data, and fourth data queried, and complete the IPv6 address as: 2001:0db8:0001:0000:0100:0101:0000:0001;

[0121] Step 9.5, the visitor uses the complete IPv6 address to establish a connection with the target node to complete the access;

[0122] Step 10, the visitor uses the DNS sharing query resolution method with embedded identity semantics to access the non-local node "Sensor 1, Production Line 1, Substation C, Third District, Second City".

[0123] Step 10.1, the visitor inputs the target node information "Sensor 1, Production Line 1, Substation C, Third District, Second City" and sends a query request to the local DNS server;

[0124] Step 10.2, the local DNS server resolves that the city where the node is located is the Second City, and returns the first 64 bits of the IPv6 address "2001:0db8:0002:0000";

[0125] Step 10.3, since the target node accessed by the visitor is not a node in this area, a query is initiated to the DNS server in the second urban area;

[0126] Step 10.4, query the identity semantic mapping table in the second urban area and the local identity semantic mapping table:

[0127] Query the corresponding relationship between the district / county information and the data, and obtain the first data corresponding to the district / county information: 03 (the third district / county).

[0128] Query the corresponding relationship between the location information and the data, and the second data corresponding to the location information: 0003 (substation C).

[0129] Query the corresponding relationship between the production line information and the data, and obtain the third data corresponding to the production line information: 01 (production line 1).

[0130] Query the corresponding relationship between the identification information and the data, and obtain the fourth data corresponding to the identification information: 00000001 (sensor).

[0131] Step 10.4, combine the first data, the second data, the third data and the fourth data queried, and complete the IPv6 address as: 2001:0db8:0002:0000:0300:0301:0000:0001;

[0132] Step 10.5, the visitor uses the complete IPv6 address to establish a connection with the target node and completes the access;

[0133] Step 11, regularly check the mapping relationship between the DNS entries and the local identity semantic mapping table. If there are device changes, update the table content in time to ensure data consistency;

[0134] Step 12, end.

[0135] It should be noted that the method of this embodiment of the present application can be executed by a single device, such as a computer or a server, etc. The method of this embodiment can also be applied to a distributed scenario and completed by multiple devices cooperating with each other. In this case of a distributed scenario, one of the multiple devices can only execute one or more steps in the method of this embodiment of the present application, and these multiple devices will interact with each other to complete the described method.

[0136] It should be noted that some embodiments of the present application have been described above. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims may be performed in a different order than in the above embodiments and still achieve the desired results. Additionally, the processes depicted in the drawings do not necessarily require the specific order or sequential order shown to achieve the desired results. In certain embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0137] Based on the same inventive concept, corresponding to any of the above method embodiments, the present application further provides a configuration device for the IPv6 address stored in the DNS corresponding to the power grid device.

[0138] Referring to Figure 4 , the configuration device for the IPv6 address stored in the DNS corresponding to the power grid device includes:

[0139] An acquisition module 10, configured to acquire the geographical location information and identification information corresponding to the power grid device.

[0140] A first determination module 20, configured to determine the routable prefix of the IPv6 address corresponding to the power grid device based on the geographical location information.

[0141] A second determination module 30, configured to determine the settable suffix of the IPv6 address corresponding to the power grid device based on the geographical location information and the identification information.

[0142] A combination module 40, configured to combine the routable prefix and the settable suffix to obtain the IPv6 address of the power grid device.

[0143] Through the above device, the geographical location information and identification information corresponding to the power grid device are acquired. Based on the geographical location information, the routable prefix of the IPv6 address corresponding to the power grid device is determined, and the routable prefix of the IPv6 address corresponding to the power grid device determined based on the geographical location information has accuracy. Based on the geographical location information and the identification information, the settable suffix of the IPv6 address corresponding to the power grid device is determined, improving the efficiency of setting the settable suffix. The routable prefix and the settable suffix are combined to obtain the IPv6 address of the power grid device, and the IPv6 address of the power grid device is configured using a unified rule, which not only improves the configuration efficiency of the IPv6 address of the power grid device but also facilitates the management of the IPv6 addresses of numerous power grid devices.

[0144] In some embodiments, the second determination module 30 is further configured such that the geographical location information includes the information of the district or county where the power grid device is located, the information of the location where it is located, and the information of the production line where it is located; determining a first data corresponding to the district or county information according to the pre-constructed corresponding relationship between the district or county information and the data; determining a second data corresponding to the location information according to the pre-constructed corresponding relationship between the location information and the data; determining a third data corresponding to the production line information according to the pre-constructed corresponding relationship between the production line information and the data; determining a fourth data corresponding to the identification information according to the pre-constructed corresponding relationship between the identification information and the data; sequentially combining the first data, the second data, the third data, and the fourth data to obtain the settable suffix.

[0145] In some embodiments, the first determination module 20 is further configured such that the geographical location information includes the urban area where the power grid device is located; determining the routable prefix corresponding to the urban area according to the pre-constructed corresponding relationship between the urban area and the routable prefix.

[0146] In some embodiments, it further includes a storage module, and the storage module is configured such that the geographical location information includes the urban area where the power grid device is located; after combining the routable prefix and the settable suffix to obtain the IPv6 address of the power grid device, storing the IPv6 address into the pre-constructed domain name table corresponding to the urban area where the power grid device is located, and storing the domain name table into the server corresponding to the urban area.

[0147] In some embodiments, it further includes a query module, and the query module is configured to, after storing the domain name table into the server corresponding to the urban area, in response to receiving a query instruction for the IPv6 address of the power grid device, determining the urban area where the query instruction is issued; querying the IPv6 address of the power grid device based on the urban area where the power grid device is located, the urban area where the query instruction is issued, the geographical location information, and the identification information.

[0148] In some embodiments, the query module is further configured to, in response to determining that the urban area where the power grid device is located is the same as the urban area where the query instruction is issued, query the first domain name table corresponding to the urban area where the query instruction is issued, and query the IPv6 address of the power grid device in the first domain name table based on the urban area where the power grid device is located, the geographical location information, and the identification information; in response to determining that the urban area where the power grid device is located is different from the urban area where the query instruction is issued, sending an access request to the server corresponding to the urban area where the power grid device is located; in response to determining that the server passes the access request, querying the second domain name table corresponding to the urban area where the power grid device is located, and querying the IPv6 address of the power grid device in the second domain name table based on the urban area where the power grid device is located, the geographical location information, and the identification information.

[0149] In some embodiments, a verification module is further included, and the verification module is configured to verify whether the number of data bits of the IPv6 address is equal to a predetermined number of data bits after combining the routable prefix and the settable suffix to obtain the IPv6 address of the power grid device; in response to determining that the number of data bits is equal to the predetermined number of data bits, it is determined that the IPv6 address passes the verification.

[0150] For the convenience of description, when describing the above device, various modules are described separately according to their functions. Of course, when implementing the present application, the functions of each module can be implemented in the same or multiple software and / or hardware.

[0151] The device in the above embodiment is used to implement the configuration method of the IPv6 address stored in DNS corresponding to the power grid device in any of the foregoing embodiments, and has the beneficial effects of the corresponding method embodiments, which will not be elaborated here.

[0152] Based on the same inventive concept, corresponding to the method in any of the above embodiments, the present application further provides an electronic device, including a memory, a processor, and a computer program stored on the memory and executable on the processor, and when the processor executes the program, it implements the configuration method of the IPv6 address stored in DNS corresponding to the power grid device in any of the above embodiments.

[0153] Figure 5 FIG. shows a more specific schematic diagram of the hardware structure of the electronic device provided in this embodiment. The device may include: a processor 1010, a memory 1020, an input / output interface 1030, a communication interface 1040, and a bus 1050. Among them, the processor 1010, the memory 1020, the input / output interface 1030, and the communication interface 1040 are communicatively connected to each other inside the device through the bus 1050.

[0154] The processor 1010 may be implemented in a general-purpose CPU (Central Processing Unit), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits, etc., and is used to execute relevant programs to implement the technical solutions provided in the embodiments of this specification.

[0155] The memory 1020 can be implemented in the form of ROM (Read Only Memory), RAM (Random Access Memory), static storage devices, dynamic storage devices, etc. The memory 1020 can store an operating system and other application programs. When implementing the technical solutions provided in the embodiments of this specification through software or firmware, the relevant program codes are stored in the memory 1020 and are called and executed by the processor 1010.

[0156] The input / output interface 1030 is used to connect to an input / output module to implement information input and output. The input / output module can be configured as a component in the device (not shown in the figure) or can be externally connected to the device to provide corresponding functions. Among them, the input device can include a keyboard, a mouse, a touch screen, a microphone, various sensors, etc., and the output device can include a display, a speaker, a vibrator, an indicator light, etc.

[0157] The communication interface 1040 is used to connect to a communication module (not shown in the figure) to implement communication interaction between this device and other devices. Among them, the communication module can implement communication in a wired manner (such as USB, network cable, etc.) or can implement communication in a wireless manner (such as mobile network, WIFI, Bluetooth, etc.).

[0158] The bus 1050 includes a path for transmitting information between various components of the device (such as the processor 1010, the memory 1020, the input / output interface 1030, and the communication interface 1040).

[0159] It should be noted that although the above device only shows the processor 1010, the memory 1020, the input / output interface 1030, the communication interface 1040, and the bus 1050, in the specific implementation process, the device may also include other components necessary for normal operation. In addition, those skilled in the art can understand that the above device may also only include the components necessary for implementing the solution of the embodiments of this specification and does not have to include all the components shown in the figure.

[0160] The electronic device in the above embodiment is used to implement the configuration method of the IPv6 address stored in DNS corresponding to the corresponding power grid device in any of the foregoing embodiments, and has the beneficial effects of the corresponding method embodiments, which will not be elaborated here.

[0161] Based on the same inventive concept, corresponding to the method in any of the above embodiments, the present application also provides a non-transitory computer-readable storage medium storing computer instructions for causing the computer to execute the configuration method of the IPv6 address stored in DNS corresponding to the power grid device as described in any of the foregoing embodiments.

[0162] The computer-readable medium of this embodiment includes permanent and non-permanent, removable and non-removable media, and information storage can be implemented by any method or technology. The information can be computer-readable instructions, data structures, program modules, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassette tapes, magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information accessible by a computing device.

[0163] The computer instructions stored in the storage medium of the above embodiment are used to cause the computer to execute the configuration method of the IPv6 address stored in DNS corresponding to the power grid device described in any of the above embodiments, and have the beneficial effects of the corresponding method embodiments, which will not be elaborated here.

[0164] Based on the same concept, corresponding to the method of any of the above embodiments, the present application also provides a computer program product, including computer program instructions, which when run on a computer, cause the computer to execute the configuration method of the IPv6 address stored in DNS corresponding to the power grid device described in any of the above embodiments, and have the beneficial effects of the corresponding method embodiments, which will not be elaborated here.

[0165] It should be noted that the embodiments of the present application can be further described in the following manner:

[0166] It can be understood that before using the technical solutions of the various embodiments of the present disclosure, the types, usage scopes, usage scenarios, etc. of the personal information involved will be informed to the user in an appropriate manner, and the user's authorization will be obtained.

[0167] For example, in response to receiving an active request from the user, a prompt message is sent to the user to clearly prompt the user that the operation requested by the user will require obtaining and using the user's personal information. Thus, the user can autonomously choose whether to provide personal information to software or hardware such as an electronic device, application program, server, or storage medium that performs the operations of the technical solutions of the present disclosure according to the prompt message.

[0168] As an optional but non-limiting implementation manner, in response to receiving an active request from a user, the manner of sending a prompt message to the user may be, for example, in the form of a pop-up window, and the prompt message may be presented in text in the pop-up window. In addition, the pop-up window may also carry a selection control for the user to select "agree" or "disagree" to provide personal information to the electronic device.

[0169] It can be understood that the above notification and user authorization acquisition process is only illustrative and does not constitute a limitation on the implementation manner of the present disclosure. Other manners that comply with relevant laws and regulations can also be applied to the implementation manner of the present disclosure.

[0170] Those of ordinary skill in the art should understand that: the discussion of any of the above embodiments is only exemplary and is not intended to imply that the scope of the present application is limited to these examples; under the concept of the present application, the technical features in the above embodiments or different embodiments can also be combined, the steps can be implemented in any order, and there are many other variations in different aspects of the embodiments of the present application as described above, and they are not provided in detail for the sake of brevity.

[0171] In addition, for the sake of simplicity of description and discussion, and in order not to make the embodiments of the present application difficult to understand, the well-known power / ground connections to integrated circuit (IC) chips and other components may or may not be shown in the provided drawings. In addition, the device may be shown in the form of a block diagram in order not to make the embodiments of the present application difficult to understand, and this also takes into account the fact that the details of the implementation manner of these block diagram devices are highly dependent on the platform on which the embodiments of the present application will be implemented (that is, these details should be completely within the understanding of those skilled in the art). In the case where specific details (such as circuits) are set forth to describe the exemplary embodiments of the present application, it will be apparent to those skilled in the art that the embodiments of the present application can be implemented without these specific details or with variations of these specific details. Therefore, these descriptions should be considered illustrative rather than restrictive.

[0172] Although the present application has been described in connection with specific embodiments of the present application, many alternatives, modifications, and variations of these embodiments will be apparent to those of ordinary skill in the art based on the foregoing description. For example, other memory architectures (such as dynamic RAM (DRAM)) can be used with the embodiments discussed.

[0173] The embodiments of the present application are intended to cover all such alternatives, modifications, and variations that fall within the broad scope of the present application. Therefore, any omissions, modifications, equivalent substitutions, improvements, etc. made within the spirit and principle of the embodiments of the present application shall be included within the protection scope of the present application.

Claims

1. A configuration method for the IPv6 address stored in DNS corresponding to a power grid device, characterized in that, Including: Obtain the geographical location information and identification information corresponding to the power grid device; Based on the geographical location information, determine the routable prefix of the IPv6 address corresponding to the power grid device; Based on the geographical location information and the identification information, determine the settable suffix of the IPv6 address corresponding to the power grid device; Combine the routable prefix and the settable suffix to obtain the IPv6 address of the power grid device.

2. The method according to claim 1, wherein The geographical location information includes the district / county information, the location information, and the production line information where the power grid device is located; The determining the settable suffix of the IPv6 address corresponding to the power grid device based on the geographical location information and the identification information includes: Determine the first data corresponding to the district / county information according to the pre-constructed correspondence between the district / county information and the data; Determine the second data corresponding to the location information according to the pre-constructed correspondence between the location information and the data; Determine the third data corresponding to the production line information according to the pre-constructed correspondence between the production line information and the data; Determine the fourth data corresponding to the identification information according to the pre-constructed correspondence between the identification information and the data; Sequentially combine the first data, the second data, the third data, and the fourth data to obtain the settable suffix.

3. The method according to claim 1, wherein The geographical location information includes the city where the power grid device is located; The determining the routable prefix of the IPv6 address corresponding to the power grid device based on the geographical location information includes: Determine the routable prefix corresponding to the city according to the pre-constructed correspondence between the city and the routable prefix.

4. The method according to claim 1, characterized in that The geographical location information includes the city where the power grid device is located; After combining the routable prefix and the settable suffix to obtain the IPv6 address of the power grid device, the method includes: Store the IPv6 address in the pre-constructed domain name table corresponding to the city where the power grid device is located, and store the domain name table in the server corresponding to the city.

5. The method according to claim 4, characterized in that After storing the domain name table in the server corresponding to the city, the method includes: In response to receiving a query instruction for the IPv6 address of the power grid device, determine the city where the query instruction is sent; Query the IPv6 address of the power grid device based on the city where the power grid device is located, the city where the query instruction is sent, the geographical location information, and the identification information.

6. The method according to claim 5, characterized in that, The querying the IPv6 address of the power grid device based on the city where the power grid device is located, the city where the query instruction is sent, the geographical location information, and the identification information includes: In response to determining that the city where the power grid device is located is the same as the city where the query instruction is sent, query the first domain name table corresponding to the city where the query instruction is sent, and query the IPv6 address of the power grid device in the first domain name table based on the city where the power grid device is located, the geographical location information, and the identification information; In response to determining that the city where the power grid device is located is different from the city where the query instruction is sent, send an access request to the server corresponding to the city where the power grid device is located; In response to determining that the server passes the access request, query the second domain name table corresponding to the urban area where the power grid device is located, and query the IPv6 address of the power grid device in the second domain name table based on the urban area where the power grid device is located, the geographical location information, and the identification information.

7. The method according to claim 1, characterized in that, After combining the routable prefix and the configurable suffix to obtain the IPv6 address of the power grid device, the method further includes: Verify whether the number of data bits of the IPv6 address is equal to the predetermined number of data bits; In response to determining that the number of data bits is equal to the predetermined number of data bits, determine that the IPv6 address passes the verification.

8. A configuration device for an IPv6 address stored in DNS corresponding to a power grid device, characterized in that, Includes: An acquisition module, configured to acquire the geographical location information and identification information corresponding to the power grid device; A first determination module, configured to determine the routable prefix of the IPv6 address corresponding to the power grid device based on the geographical location information; A second determination module, configured to determine the configurable suffix of the IPv6 address corresponding to the power grid device based on the geographical location information and the identification information; A combination module, configured to combine the routable prefix and the configurable suffix to obtain the IPv6 address of the power grid device.

9. An electronic device, comprising a memory, a processor, and a computer program stored on the memory and running on the processor, characterized in that, When the processor executes the program, it implements the method according to any one of claims 1 to 7.

10. A non-transitory computer-readable storage medium storing computer instructions, characterized in that, The computer instructions are used to cause the computer to execute the method according to any one of claims 1 to 7.

Images