Address prefix allocation methods and devices, storage media and electronic devices
By automatically assigning network address prefixes to boundary nodes in a wireless mesh network, the poor applicability caused by manual assignment is solved, achieving highly adaptable network address prefix assignment suitable for smart home whole-house networks.
Patent Information
- Application Number
- CN202211356176.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2022-11-01
- Publication Date
- 2025-12-02
- Estimated Expiration
- 2042-11-01
AI Technical Summary
In existing technologies, manually assigning network address prefixes is not suitable for smart home whole-house networks, resulting in poor applicability of network address prefix assignment, especially in scenarios where network topology changes frequently, making management inconvenient.
The network address prefix is automatically assigned by the boundary nodes in the wireless mesh network. The boundary nodes that have established communication connections with the router are used to assign network address prefixes to the unconnected boundary nodes. The network address prefix is split in an automated manner to ensure that the address prefixes of each node are different.
It enables automated and adaptable network address prefix allocation in smart home whole-house networks, improving the applicability of network address prefix allocation and making it suitable for environments with frequent network topology changes.
Smart Images

Figure CN115733820B_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of smart home technology, and more specifically, to a method and apparatus for allocating address prefixes, a storage medium, and an electronic device. Background Technology
[0002] A smart home whole-house network is a mesh network (wireless mesh network) composed of routers and other device nodes. This network is heterogeneous and can support multiple connection technologies, providing interconnectivity for different devices. To facilitate interaction between devices, network address prefixes can be manually assigned, allowing for the allocation of non-overlapping network address prefixes.
[0003] However, manually assigning network address prefixes requires extensive expertise and is unsuitable for mesh networks such as smart home whole-house networks. Furthermore, this manual method is not suitable for scenarios where network topology frequently changes. Therefore, the address prefix assignment methods in related technologies suffer from poor applicability due to the need for manual allocation. Summary of the Invention
[0004] The purpose of this application is to provide a method, apparatus, storage medium, and electronic device for allocating address prefixes, so as to at least solve the problem that the address prefix allocation methods in the related art have poor applicability due to the need for manual allocation of network address prefixes.
[0005] According to one aspect of the embodiments of this application, a method for allocating an address prefix is provided, comprising: receiving a first address prefix request sent by a first boundary node, wherein the first boundary node is a boundary node in a wireless mesh network that has not established a communication connection with a router of the wireless mesh network, and the first address prefix request is used to request the allocation of a network address prefix for the first boundary node; in response to the first address prefix request, if there is an unallocated sub-network address prefix in a set of sub-network address prefixes that match the first network address prefix of a second boundary node, selecting a first sub-network address prefix from the unallocated sub-network address prefixes, wherein the second boundary node is a boundary node corresponding to the first boundary node that has established a communication connection with a router of the wireless mesh network, and the sub-network address prefixes in the set of sub-network address prefixes are identical in all address bits except for a set of preset address bits, and the set of preset address bits are all different from each other; and sending a first address prefix allocation message to the first boundary node, wherein the first address prefix allocation message is used to instruct the allocation of the first sub-network address prefix to the first boundary node.
[0006] According to another aspect of the embodiments of this application, an address prefix allocation apparatus is also provided, comprising: a receiving unit, configured to receive a first address prefix request sent by a first boundary node, wherein the first boundary node is a boundary node in a wireless mesh network that has not established a communication connection with a router of the wireless mesh network, and the first address prefix request is used to request the allocation of a network address prefix for the first boundary node; a first selection unit, configured to, in response to the first address prefix request, select a first sub-network address prefix from a set of unallocated sub-network address prefixes that match the first network address prefix of a second boundary node, wherein the second boundary node is a boundary node corresponding to the first boundary node that has established a communication connection with a router of the wireless mesh network, and the sub-network address prefixes in the set of sub-network address prefixes are identical in all address bits except for a set of preset address bits, and the set of preset address bits are all different from each other; and a first sending unit, configured to send a first address prefix allocation message to the first boundary node, wherein the first address prefix allocation message is used to indicate that the first sub-network address prefix is allocated to the first boundary node.
[0007] According to another aspect of the embodiments of this application, a computer-readable storage medium is also provided, wherein a computer program is stored in the computer program, and the computer program is configured to execute the above-described address prefix allocation method at runtime.
[0008] According to another aspect of the embodiments of this application, an electronic device is also provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the address prefix allocation method described above through the computer program.
[0009] In this embodiment, a method is adopted whereby a border node in a wireless mesh network that has established a communication connection with a router in the wireless mesh network allocates an address prefix to a border node that has not established a communication connection with a router in the wireless mesh network. This is achieved by receiving a first address prefix request from a first border node, where the first border node is a border node in the wireless mesh network that has not established a communication connection with a router in the wireless mesh network, and the first address prefix request is used to request the allocation of a network address prefix for the first border node. In response to the first address prefix request, if there is an unallocated sub-network address prefix in a set of sub-network address prefixes that match the first network address prefix of a second border node, a first sub-network address prefix is selected from the unallocated sub-network address prefixes. The second border node is a border node corresponding to the first border node that has established a communication connection with a router in the wireless mesh network. All address bits in the set of sub-network address prefixes are identical except for a set of preset address bits. The preset address bits are all different; a first address prefix allocation message is sent to the first boundary node, wherein the first address prefix allocation message is used to instruct the first sub-network address prefix to be allocated to the first boundary node. Since the boundary node that has established a communication connection with the router of the wireless mesh network allocates the address prefix to the boundary node that has not established a communication connection with the router of the wireless mesh network when allocating the network address prefix, the purpose of automatically allocating the network address prefix to the boundary node in the wireless mesh network can be achieved. At the same time, splitting the network address prefix into sub-network address prefixes in which all address bits except a set of preset address bits are the same and the set of preset address bits are all different can achieve the purpose of allocating different network address prefixes to different boundary nodes, thereby achieving the technical effect of improving the adaptability of network address prefix allocation, and thus solving the problem of poor applicability of network address prefix allocation caused by the need for manual allocation of network address prefixes in related technologies. Attached Figure Description
[0010] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.
[0011] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, for those skilled in the art, other drawings can be obtained based on these drawings without creative effort.
[0012] Figure 1 This is a schematic diagram of a hardware environment for an optional address prefix allocation method according to an embodiment of this application;
[0013] Figure 2 This is a flowchart illustrating an optional address prefix allocation method according to an embodiment of this application;
[0014] Figure 3 This is a schematic diagram of an optional wireless mesh network according to an embodiment of this application;
[0015] Figure 4 This is a schematic diagram of an optional network address according to an embodiment of this application;
[0016] Figure 5 This is a schematic diagram of another optional wireless mesh network according to an embodiment of this application;
[0017] Figure 6 This is a flowchart illustrating another optional address prefix allocation method according to an embodiment of this application;
[0018] Figure 7 This is a schematic diagram of an optional network address prefix according to an embodiment of this application;
[0019] Figure 8 This is a flowchart illustrating another optional address prefix allocation method according to an embodiment of this application;
[0020] Figure 9 This is a structural block diagram of an optional address prefix allocation device according to an embodiment of this application;
[0021] Figure 10 This is a structural block diagram of an optional electronic device according to an embodiment of this application. Detailed Implementation
[0022] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present application, and not all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative effort should fall within the scope of protection of the present application.
[0023] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.
[0024] According to one aspect of the embodiments of this application, a method for allocating address prefixes is provided. This address prefix allocation method is widely applicable to whole-house intelligent digital control application scenarios such as smart homes, smart home ecosystems, and intelligence house ecosystems. Optionally, in this embodiment, the above-mentioned address prefix allocation method can be applied to, for example... Figure 1 The hardware environment shown consists of terminal device 102 and server 104. For example... Figure 1 As shown, server 104 is connected to terminal device 102 via a network and can be used to provide services (such as application services) to the terminal or clients installed on the terminal. A database can be set up on the server or independently of the server to provide data storage services for server 104. Cloud computing and / or edge computing services can be configured on the server or independently of the server to provide data processing services for server 104.
[0025] The aforementioned network may include, but is not limited to, at least one of the following: wired network, wireless network. The aforementioned wired network may include, but is not limited to, at least one of the following: wide area network, metropolitan area network, local area network. The aforementioned wireless network may include, but is not limited to, at least one of the following: Wi-Fi (Wireless Fidelity), Bluetooth. The terminal device 102 may not be limited to PC, mobile phone, tablet computer, smart air conditioner, smart range hood, smart refrigerator, smart oven, smart stove, smart washing machine, smart water heater, smart washing equipment, smart dishwasher, smart projector, smart TV, smart clothes rack, smart curtains, smart audio-visual equipment, smart socket, smart speaker, smart speaker box, smart fresh air equipment, smart kitchen and bathroom equipment, smart bathroom equipment, smart robot vacuum cleaner, smart window cleaning robot, smart mopping robot, smart air purifier, smart steam oven, smart microwave oven, smart water heater, smart air purifier, smart water dispenser, smart door lock, etc.
[0026] The address prefix allocation method of this application embodiment can be executed by server 104, terminal device 102, or jointly by server 104 and terminal device 102. The testing method of the interface of this application embodiment executed by terminal device 102 can also be executed by a client installed on it.
[0027] Taking the address prefix allocation method in this embodiment as an example, which is executed by terminal device 102, Figure 2 This is a flowchart illustrating an optional address prefix allocation method according to an embodiment of this application, as shown below. Figure 2 As shown, the process of this method may include the following steps:
[0028] Step S202: Receive a first address prefix request sent by a first boundary node, wherein the first boundary node is a boundary node in the wireless mesh network that has not established a communication connection with the router of the wireless mesh network, and the first address prefix request is used to request the allocation of a network address prefix for the first boundary node.
[0029] The address prefix allocation method in this embodiment can be applied to scenarios where address prefixes are allocated to edge nodes in a wireless mesh network (i.e., a mesh network). The aforementioned wireless mesh network is based on a multi-hop interconnection network structure, meaning that each node in the wireless mesh network can send and receive signals, and can communicate directly with one or more peer nodes. Furthermore, the wireless mesh network supports various connection technologies, such as Wi-Fi, Ethernet, BLE, Zigbee, and Wi-Fi Mesh. Since the functions of each node in a wireless mesh network are not entirely identical, it is a heterogeneous network. A heterogeneous network can be a network that divides nodes into two or more categories according to function and utility, while a homogeneous network is a network where all nodes have the same function and utility.
[0030] In this embodiment, a border node (which may be called a border router) can be a border device in a wireless mesh network, typically a device with at least two connections simultaneously, for example, one connection to the router via Wi-Fi and the other connection to a BLE device via BLE. The wireless mesh network can be a smart home whole-house network, where a smart home whole-house network is a mesh network composed of multiple devices. Based on whether it is connected to a router in the wireless mesh network, border nodes can be divided into: border nodes that have established communication connections with routers in the wireless mesh network are called Top border nodes; border nodes that have not established communication connections with routers in the wireless mesh network are called Non-Top border nodes. Routers can belong to the basic network, which can be routers within the home and extended access points (APs).
[0031] For example, Figure 3 This is a schematic diagram of the network topology of a smart home whole-house network. The network topology uses the basic network as the core router in the mesh network, and the lines represent the communication connection status between each node. Figure 3 As shown, the smart home whole-house network includes: N Top Border Routers: Top Border Router 1, Top Border Router 2, Top Border Router 3, and Top Border Router N; one Node 1 connected to the basic network; Nodes 11 and 12 belonging to Top Border Router 1; Nodes 21 and 22 belonging to Top Border Router 2 and non-Top Border Router 1; Nodes 31 and 32 belonging to Top Border Router 3; and Nodes 211 and 212 belonging to non-Top Border Router 1. The network topology under other Top Border Routers (e.g., Top Border Router N) may be the same as, similar to, or different from Top Border Router 1, Top Border Router 2, or Top Border Router 3, and will not be listed here.
[0032] When facilitating communication between different devices, network devices can be IP-based (Internet Protocol). The same connectivity technology can form a specific mesh network. This mesh network can use the same network address prefix and is a network rooted at a border router. Mesh networks rooted at different border routers can use different network address prefixes. Related technologies allow manually assigning non-overlapping network address prefixes to different border routers.
[0033] For example, a network using IPv6 (Internet Protocol Version 6) as its network layer can provide broad interconnectivity, and devices connected to the underlying network typically share the same IPv6 address prefix. The same connectivity technology can form a specific mesh network, which can use the same IPv6 address prefix. This mesh network is rooted at the border router. Ultimately, the entire smart home network forms a multi-rooted, multi-layered network topology with the underlying network at its core. Here, the two connections of the border router usually require different IPv6 address prefixes. However, due to heterogeneity and the existence of IPv6, how to plan IPv6 address prefixes effectively and minimize IPv6 routing resources is a crucial problem that mesh network management must solve. Currently, manually assigning these IPv6 address prefixes ensures that they do not overlap and that the number of IPv6 address prefixes is not excessive.
[0034] However, manually assigning network address prefixes is suitable for networks that don't change frequently and have professional network administrators, but it's not suitable for wireless networks aimed at ordinary users, such as smart home whole-house networks, leading to inconvenience in network address prefix allocation and management. This embodiment provides a scheme for automatically assigning network address prefixes (IP address prefixes) in a wireless mesh network. The top boundary node automatically assigns mutually exclusive network address prefixes to non-top boundary nodes, ensuring that network address prefixes do not overlap and improving the applicability of network address prefix allocation.
[0035] For a first boundary node, which may be a non-top boundary node, when it needs to obtain a network address prefix for use in a network rooted at that first boundary node, it can send a first address prefix request to its corresponding top boundary node (i.e., the second boundary node) to request the allocation of a network address prefix for the first boundary node; correspondingly, the second boundary node can receive the aforementioned first address prefix request sent by the first boundary node. Here, the first boundary node and the second boundary node can establish communication connections with at least two nodes through at least two of the following wireless connection methods: Wi-Fi, Ethernet, BLE, Zigbee, Wi-Fi Mesh, etc.
[0036] Step S204: In response to the first address prefix request, if there is an unallocated sub-network address prefix in a set of sub-network address prefixes that match the first network address prefix of the second boundary node, select the first sub-network address prefix from the unallocated sub-network address prefixes.
[0037] In response to the first address prefix request, the second border node can assign a network address prefix. Assigning a network address prefix to the second border node can be selected from a set of sub-network address prefixes that match the first network address prefix. The first network address prefix can be a network address prefix that matches the second border node, and it can be a different network address prefix than those matched by other Top border nodes connected to the same router as the second border node. For Top border nodes connected to different routers, their corresponding network address prefixes can be the same or different.
[0038] If there is an unallocated sub-network address prefix among the set of sub-network address prefixes that match the first network address prefix of the second boundary node, then any one of these sub-network address prefixes can be selected as the first sub-network address prefix allocated to the first boundary node. If there is no unallocated sub-network address prefix among the set of sub-network address prefixes that match the first network address prefix of the second boundary node, then a new network address prefix that matches the second boundary node can be requested, split into sub-network address prefixes, and then one of the split sub-network address prefixes can be selected as the first sub-network address prefix allocated to the first boundary node.
[0039] The aforementioned first network address prefix can be one or more network address prefixes used by the second boundary node after it recognizes that it has established a direct communication connection with the router in the wireless mesh network. Except for a set of preset address bits, all other address bits in the aforementioned set of sub-network address prefixes are the same, and the set of preset address bits are all different. The aforementioned set of sub-network address prefixes can be generated by adding a set of preset address bits with different values after the first network address prefix, or by replacing the values in the set of preset address bits in the first network address prefix with different values, or by other methods. This embodiment does not limit this method.
[0040] Here, a sub-network address prefix can be called a network address prefix unit. For example, the network address prefix matching the Top boundary node can be called the Top IPv6 address prefix. All devices in the base network use a default Top IPv6 address prefix. Boundary routers (i.e., Top boundary nodes) in the base network can occupy one or more Top IPv6 address prefixes. The sub-network address prefixes split from the Top IPv6 address prefix can be called IPv6 address prefix units. An IPv6 address prefix unit is a minimum address prefix. A Top IPv6 address prefix can be divided into several IPv6 address prefix units. If multiple IPv6 address prefix units are consecutive, they can be merged into a larger IPv6 address prefix. Non-Top boundary nodes can occupy one or more IPv6 address prefix units, obtained from the Top boundary node. Leaf node devices obtain IPv6 address prefixes from the base network or boundary nodes at each layer to construct their own IPv6 addresses.
[0041] For example, such as Figure 4 As shown, the network address prefix matched with the Top border router is a 56-bit network address prefix. By adding 8 different bits after the network address prefix matched with the Top border router, a set of sub-network address prefixes can be formed and allocated to non-Top border routers that have requested network address prefixes from the Top border router.
[0042] Step S206: Send a first address prefix allocation message to the first boundary node, wherein the first address prefix allocation message is used to indicate that the first sub-network address prefix is allocated to the first boundary node.
[0043] After selecting the first sub-network address prefix, the second border node can send a first address prefix allocation message to the first border node. This first address prefix allocation message may carry the aforementioned first sub-network address prefix to indicate that the first sub-network address prefix is allocated to the first border node. The second border node can send the first address prefix allocation message to the first border node in various ways, including but not limited to at least one of the following: unicast, multicast, broadcast, or other methods capable of information transmission between different border nodes. This embodiment does not limit this method.
[0044] It should be noted that in a wireless mesh network, each boundary node in each layer that does not have a direct communication connection with the router can find a corresponding boundary node that has a direct communication connection with the router, i.e., the Top boundary node to which it belongs, and can directly request a network address prefix from that boundary node.
[0045] Upon receiving the first address prefix allocation message, the first border node can determine the first sub-network address prefix and use it for the network rooted at itself. For example, a non-top border router, upon receiving the allocated IPv6 address prefix unit, can use the IPv6 address prefix unit for the network rooted at itself.
[0046] It should be noted that, based on different network topologies, non-Top boundary nodes can be categorized into Level 1 non-Top boundary nodes, Level 2 non-Top boundary nodes, and so on up to Level N (where N is a positive integer greater than or equal to 1). Level 1 non-Top boundary nodes are boundary nodes in a homogeneous network rooted at a Top boundary node; Level 2 non-Top boundary nodes are boundary nodes in a homogeneous network rooted at a Level 1 non-Top boundary node, and so on. Regardless of the level, every non-Top boundary node requests a network address prefix from its corresponding Top boundary node. For example, ... Figure 5 As shown, non-Top border router 1 is a first-level non-Top border node, and non-Top border router 11 is a second-level non-Top border node. Both of them request network address prefixes from Top border router 2.
[0047] In a homogeneous network rooted at a boundary node, both the boundary node and other nodes (e.g., leaf nodes) can communicate using their requested network address prefixes. For example, ... Figure 5As shown, within the homogeneous network rooted at Top border router 1, there are nodes 11 and 12. Both can use the network address prefix unit reserved by Top border router 1 plus their own host address as the network address for communication. Within the homogeneous network rooted at Top border router 2, there are nodes 21, 22, and non-Top border router 1. All three can use the network address prefix unit reserved by Top border router 2 plus their own host address as the network address for communication. Within the homogeneous network rooted at non-Top border router 1, there are nodes 211 and non-Top border router 11. Non-Top border router 1 requests a network address prefix unit from Top border router 2 for use within the homogeneous network rooted at non-Top border router 1. Both node 211 and non-Top border router 11 can use the requested network address prefix unit from non-Top border router 1 plus their own host address as the network address for communication. Within a homogeneous network rooted at non-Top border router 11, there is node 2111. The non-Top border router requests a network address prefix unit from Top border router 2 as the network address prefix unit used within the homogeneous network rooted at non-Top border router 11. Node 2111 can use the network address prefix unit requested by non-Top border router 11 plus its own host address as the network address for communication.
[0048] Through steps S202 to S206 above, a first address prefix request sent by a first boundary node is received. The first boundary node is a boundary node in the wireless mesh network that has not established a communication connection with a router in the wireless mesh network. The first address prefix request is used to request the allocation of a network address prefix for the first boundary node. In response to the first address prefix request, if there is an unallocated sub-network address prefix in a set of sub-network address prefixes matching the first network address prefix of a second boundary node, a first sub-network address prefix is selected from the unallocated sub-network address prefixes. The second boundary node is a boundary node corresponding to the first boundary node that has established a communication connection with a router in the wireless mesh network. The sub-network address prefixes in the set of sub-network address prefixes are identical in all address bits except for a set of preset address bits, and the preset address bits are all different. A first address prefix allocation message is sent to the first boundary node. The first address prefix allocation message is used to instruct the allocation of the first sub-network address prefix to the first boundary node. This solves the problem of poor applicability of network address prefix allocation methods in related technologies due to the need for manual allocation, and improves the applicability of network address prefix allocation.
[0049] In one exemplary embodiment, sending a first address prefix allocation message to a first boundary node includes:
[0050] S11, within the first time period, repeatedly send the first address prefix allocation message to the first boundary node at a preset frequency until a response message is received from the first boundary node in response to the first address prefix allocation message.
[0051] In this embodiment, in order to ensure that the first boundary node can receive the first address prefix allocation message, the second boundary node can repeatedly send the first address prefix allocation message to the first boundary node at a preset frequency until it receives a response message from the first boundary node in response to the first address prefix allocation message.
[0052] Optionally, to avoid prolonged delays in receiving response messages from the first border node due to reasons such as the first border node being offline, a preset waiting time for receiving response messages can be established, i.e., a first time period, the duration of which can be a preset duration. The second border node can repeatedly send the first address prefix allocation message to the first border node at a preset frequency within the first time period until it receives a response message from the first border node in response to the first address prefix allocation message, or until the current time exceeds the time range of the first time period.
[0053] For example, a top border router can find an unassigned IPv6 address prefix unit, send it to a non-top border router in the form of a unicast, and repeat the transmission at a certain frequency within a limited time, stopping when it receives a response.
[0054] In this embodiment, by continuously sending the allocated network address prefix to the network address prefix requester within a certain period of time, the probability of the requester receiving the allocated network address prefix can be increased, thereby improving the success rate of network address prefix allocation.
[0055] In one exemplary embodiment, after sending the first address prefix allocation message to the first boundary node, the above method further includes:
[0056] S21, if a response message is received from the first boundary node in response to the first address prefix allocation message within the first time period, the first sub-network address prefix is marked as allocated.
[0057] S22, if no response message is received from the first boundary node in response to the first address prefix allocation message within the first time period, the first sub-network address prefix is remarked as unallocated.
[0058] In this embodiment, the status of each sub-network address prefix can be marked, such as allocated status (i.e., occupied status), unallocated status (i.e., unoccupied status), and pre-allocated status (i.e., pre-occupied status). By marking and updating the current status of different sub-network addresses, it is convenient to know the available sub-network address prefixes, and at the same time, it is convenient to reclaim the allocated sub-network address prefixes, thereby improving the rationality of network address prefix utilization.
[0059] Before the first sub-network address prefix is selected, it is in an unallocated state and can be selected as a sub-network address prefix to be allocated to the first boundary node. After the first sub-network address prefix is selected, it can be marked as a pre-allocated state. Sub-network address prefixes in the pre-allocated state cannot be allocated to other boundary nodes that have applied for network address prefixes.
[0060] When sending a first address prefix allocation message to the first border node, if a response message is received from the first border node in response to the first address prefix allocation message within the first time period, it can be determined that the first sub-network address prefix has been successfully allocated to the first border node, and the first sub-network address prefix is marked as allocated. A sub-network address prefix in the allocated state cannot be allocated to other border nodes that have requested a network address prefix. If no response message is received from the first border node in response to the first address prefix allocation message within the first time period, it can be determined that the first sub-network address prefix has not been successfully allocated to the first border node, and the first sub-network address prefix is remarked as unallocated.
[0061] For example, combining Figure 3 As shown, non-Top border router 1 requests a network address prefix from Top border router 2. Top border router 2 selects an unallocated IPv6 address prefix, marks it as pre-allocated, and sends an allocation message for the IPv6 address prefix to non-Top border router 1. If Top border router 2 receives a response to the allocation message from non-Top border router 1 within a preset time, it marks the pre-allocated IPv6 address prefix as allocated. If Top border router 3 does not receive a response to the allocation message from non-Top border router 1 within a preset time, it remarkes the pre-allocated IPv6 address prefix as unallocated.
[0062] This embodiment facilitates the management of network address prefixes by setting the status of sub-network address prefixes to unallocated, pre-allocated, or allocated, and by updating the status of sub-network address prefixes in a timely manner. This prevents network address prefixes from being repeatedly occupied and improves the efficiency of network address prefix allocation.
[0063] In one exemplary embodiment, after sending the first address prefix allocation message to the first boundary node, the above method further includes:
[0064] S31, upon receiving the response message returned by the first boundary node in response to the first address prefix allocation message, the first sub-network address prefix is marked as allocated, and the allocation time of the first sub-network address prefix is timed.
[0065] S32, if an indication message is received from the first boundary node before the allocated time of the first sub-network address prefix reaches a preset time threshold, indicating that the first boundary node is to use the first sub-network address prefix, the allocated time of the first sub-network address prefix is re-timed;
[0066] S33, if no indication message sent by the first boundary node instructing the first boundary node to use the first sub-network address prefix is received before the allocation time of the first sub-network address reaches a preset time threshold, the first sub-network address prefix is marked as unallocated.
[0067] After sub-network address prefixes are allocated to border nodes, due to reasons such as border node offline status or network topology changes, the allocated sub-network address prefixes may not be used by the border nodes, resulting in a waste of network address prefix resources. In this embodiment, the non-Top border nodes to which the sub-network address prefixes were allocated can periodically send indication messages to the Top border nodes to indicate the usage status of the sub-network address prefixes. Based on the usage status of the sub-network address prefixes, the Top border nodes can update the status of the sub-network address prefixes, thereby reclaiming unused sub-network address prefixes and allocating them to other non-Top border nodes that have requested sub-network address prefixes. This ensures that the sub-network address prefixes are fully utilized and reduces the number of sub-network address prefixes required.
[0068] Upon receiving the first address prefix allocation message, the first border node can respond to the acknowledgment message returned by the first border node to the second border node, and periodically send indication messages to the second border node to instruct the first border node to use the first sub-network address prefix. After receiving the acknowledgment message returned by the first border node in response to the first address prefix allocation message, the second border node can mark the first sub-network address prefix as allocated, and simultaneously start a timer to record the allocation time of the first sub-network address prefix. It also presets a time threshold for receiving the indication message sent by the first border node instructing the first border node to use the first sub-network address prefix. If the first border node sends the aforementioned indication information, then the second border node can receive the aforementioned indication information sent by the first border node before the allocated time reaches the set time threshold.
[0069] If the second boundary node receives an indication message from the first boundary node instructing the first boundary node to use the first sub-network address prefix before the allocated time of the first sub-network address prefix reaches a preset time threshold, the allocated time of the first sub-network address prefix can be reset. Optionally, to facilitate the first boundary node's awareness of the reception status of its indicated information, the second boundary node can send a response message to the first boundary node acknowledging receipt of the indicated message.
[0070] If the second boundary node does not receive an indication message from the first boundary node indicating that the first boundary node is using the first sub-network address prefix before the allocated time of the first sub-network address prefix reaches a preset time threshold, the sub-network address prefix can be considered unused and marked as unallocated. Sub-network address prefixes marked as unallocated can be reassigned to other non-Top boundary nodes for use.
[0071] In this embodiment, non-Top boundary nodes that are assigned sub-network address prefixes periodically report the usage of the sub-network address prefixes. Top boundary nodes can update the status of the sub-network address prefixes in a timely manner based on the usage of the sub-network address prefixes and reclaim unused sub-network address prefixes, thereby improving the utilization rate of network address prefixes and reducing the number of sub-network address prefixes.
[0072] The address prefix allocation method in this embodiment will be explained below with reference to an optional example. In this optional example, the first border node is a non-Top border router, the second border node is a Top border router, and the first sub-network address prefix is an IPv6 address prefix unit.
[0073] This optional example provides a scheme for a non-Top border router to request a network address prefix, combined with... Figure 6 The process by which a top border router assigns network address prefixes to non-top border routers may include the following steps:
[0074] Step S601: The non-Top border router requests an IPv6 address prefix unit from the Top border router. The request can be made via unicast, multicast, broadcast, or other methods.
[0075] Despite the multi-layered network topology, regardless of the layer, every non-Top border router can find its corresponding Top border router and directly request IPv6 address prefix units from the Top border router. The request can be made via unicast, multicast, broadcast, or other methods.
[0076] In step S602, the Top border router selects an unassigned IPv6 address prefix unit and marks it as pre-assigned.
[0077] Top-level border routers can assign one or more IPv6 address prefix units to their subordinate (one or more) non-top-level border routers. If multiple IPv6 address prefix units are contiguous, they can be merged into a larger IPv6 address prefix. In this case, contiguous IPv6 address prefix units can be assigned to the non-top-level border router and its subordinate non-top-level border routers. When the assigned IPv6 address prefix units can be merged, the merged IPv6 address prefix unit can be used to communicate with the non-top-level border router.
[0078] In step S603, within a preset time period, the Top border router sends the selected IPv6 network address prefix unit to the non-Top border router in a unicast manner at a certain frequency.
[0079] In step S604, after receiving the allocated IPv6 address prefix unit, the non-Top border router immediately sends a response to the Top border router.
[0080] Step S605: If the Top border router does not receive a response from a non-Top border router after a preset time, the IPv6 address prefix unit is marked as unassigned.
[0081] In step S606, the non-Top border router periodically sends the requested IPv6 address prefix unit to the Top border router, indicating that the IPv6 address prefix unit is in use.
[0082] In step S607, after the Top border router receives the IPv6 address prefix unit sent by the non-Top border router, it refreshes the occupancy flag of the IPv6 address prefix unit.
[0083] Step S608: If the occupancy flag of the IPv6 address prefix unit is not refreshed within a certain period of time, mark the IPv6 address prefix unit as unallocated.
[0084] This optional example demonstrates how non-Top border routers periodically send requested IPv6 address prefix units to the Top border router. This allows for the determination of whether IPv6 address prefix units are currently in use and updates to their occupancy status. This facilitates the reallocation of unoccupied IPv6 address prefix units, improving their utilization rate and ultimately reducing their number.
[0085] In one exemplary embodiment, before receiving the first address prefix request sent by the first boundary node, the above method further includes:
[0086] S41, Select a network address prefix marked as unoccupied from a preset set of network address prefixes to obtain the first address prefix to be occupied;
[0087] S42, if it is determined that the first address prefix to be occupied is not occupied, the first address prefix to be occupied is marked as a network address prefix occupied by the second boundary node, wherein the first address prefix to be occupied is the first network address prefix.
[0088] A set of sub-network address prefixes can be obtained based on a first network address prefix, while the first sub-network address prefix can be selected from a set of network address prefixes. To improve the rationality of network address prefix utilization, different top boundary nodes connected to the same router can share a set of network address prefixes. When a network address prefix needs to be used, it can be selected from a set of network address prefixes, and whether the selected network address prefix is occupied is determined based on whether it is already in use (by this top boundary node or other top boundary nodes).
[0089] The above set of network address prefixes can be called a network address prefix pool, for example, an IPv6 address prefix pool. An IPv6 address prefix pool can be like... Figure 7 As shown, this IPv6 address prefix pool is pre-planned for smart home whole-house networks and contains multiple Top IPv6 address prefixes. A Top IPv6 address prefix is the first 56 bits of a 128-bit IPv6 network address. Top border routers can apply to obtain one or more Top IPv6 address prefixes from the IPv6 address prefix pool.
[0090] In this embodiment, when a second boundary node detects that it has established a direct communication connection with a router in the wireless mesh network, it selects a network address prefix from the network address prefix pool. The selected network address prefix can be directly marked as a network address prefix occupied by the second boundary node. If a set of network address prefixes is shared by multiple top boundary nodes, in order to avoid network address prefix occupation conflicts, the second boundary node can first determine that the network address prefix is not occupied, including not occupied by the second boundary node itself and not occupied by other boundary nodes. The second boundary node can select a network address prefix marked as unoccupied from the network address prefix pool as the first address prefix to be occupied (at this time, it can be determined that the network address prefix is not occupied by itself), and confirm whether the network address prefix is occupied by other boundary nodes by sending a first address prefix allocation message to other boundary nodes.
[0091] If it is determined that the first network address prefix to be occupied is not occupied, the second boundary node marks the first network address prefix to be occupied as a network address prefix occupied by the second boundary node, that is, it has successfully occupied the first network address prefix. If it cannot be determined that the first network address prefix to be occupied is not occupied, the second boundary node may stop trying to occupy the network address prefix and instead try to occupy other network address prefixes to obtain a network address prefix.
[0092] It should be noted that if a second boundary node goes offline due to a power outage or reboot, the network address prefix allocated before it went offline will be unusable upon restarting. It will need to reapply for a network address prefix, and the process is similar to that described above, so it will not be repeated here. Simultaneously, the sub-network address prefixes applied for by non-Top boundary nodes belonging to the second boundary node (e.g., the first boundary node) will also become unusable. The second boundary node can send notification messages to its included non-Top boundary nodes via broadcast, multicast, or other means to notify them to reapply for sub-network address prefixes.
[0093] This embodiment obtains network address prefixes by confirming that the requested network address prefix is not already in use, thus avoiding duplicate use of network address prefixes and improving the accuracy of network address prefix allocation.
[0094] In an exemplary embodiment, after selecting a network address prefix marked as unoccupied from a preset set of network address prefixes to obtain a first address prefix to be occupied, the above method further includes:
[0095] S51, during the second time period, continuously send the first address prefix occupancy request to other boundary nodes, wherein the other boundary nodes are the boundary nodes that have established communication connections with the router of the wireless mesh network, excluding the second boundary node, and the first address prefix occupancy request is used to request the occupancy of the first address prefix to be occupied;
[0096] S52, if no indication message indicating that the first pending network address has been occupied is received from other boundary nodes during the second time period, it is determined that the first pending address prefix has not been occupied;
[0097] S53, if an indication message is received from a third boundary node among other boundary nodes during the second time period, indicating that the first address prefix to be occupied has been occupied, it is determined that the first address prefix to be occupied has been occupied.
[0098] If a set of network address prefixes is used only by the second boundary node, then the network address prefixes marked as unoccupied are actually unoccupied and can be used directly. If a set of network address prefixes is shared by other top boundary nodes (e.g., different top boundary nodes connected to the same router), then the same network address prefix may be selected by multiple top boundary nodes simultaneously, leading to network address prefix usage conflicts. To ensure the rationality of network address prefix usage, after selecting the first unoccupied address prefix, the second boundary node can continuously send first address prefix occupancy requests to other boundary nodes within a second time period to request the occupancy of the first unoccupied address prefix. Here, other boundary nodes are those boundary nodes that have established communication connections with the routers of the wireless mesh network, excluding the second boundary node.
[0099] Upon receiving a request to reserve a first address prefix, other border nodes can determine whether the first address prefix to be reserved has already been reserved, either by their own border node or by another border node. If they determine that the first address prefix to be reserved is not reserved, they can ignore the request. If they determine that the first address prefix to be reserved is reserved, they can return an indication message to the second border node indicating that the first network address to be reserved has been reserved.
[0100] The second boundary node can wait during the second time period to receive indication information returned by other boundary nodes in response to the first address prefix occupancy request. If it receives indication information returned by a boundary node (e.g., a third boundary node) in response to the first address prefix occupancy request, it can be determined that the first address prefix to be occupied has been occupied; otherwise, it can be determined that the first address prefix to be occupied has not been occupied.
[0101] Optionally, to synchronize the occupancy status of network address prefixes among different boundary nodes, if no indication information is received from any other boundary node in response to the first address prefix occupancy request within the second time period, the second boundary node may mark the first pending network address as occupied, and may also send indication information to other boundary nodes indicating that the first pending address prefix has been occupied (e.g., occupied by the second boundary node). Furthermore, to reduce network resource consumption, the indication information returned to the second boundary node by the boundary node occupying the first pending address prefix in response to the first address prefix occupancy request may be limited to that node.
[0102] Optionally, if it is determined that the first address prefix to be occupied has already been occupied, the second boundary node can reselect the network address prefix and send an address prefix occupancy request to re-apply for the network address prefix. The method for re-applying for the network address prefix is similar to that described above and will not be repeated here.
[0103] For example, combining Figure 3 In the wireless mesh network shown, after Top Border Router 1 selects a Top IPv6 address prefix from the Top IPv6 address prefix pool, it can send a request to other Top Border Routers in the basic network to claim the Top IPv6 address prefix via broadcast or multicast. If Top Border Router 2 receives this request and finds that the Top IPv6 address prefix is already in use, it immediately sends a response message to Top Border Router 1 indicating that the Top IPv6 address prefix is already in use. Upon receiving the response message, Top Border Router 1 marks the Top IPv6 address prefix as in use and re-requests a Top IPv6 address prefix. If no response indicating that the Top IPv6 address prefix is already in use is received from other Top Border Routers within a certain period of time, Top Border Router 1 can claim the Top IPv6 address prefix.
[0104] This embodiment improves the effectiveness of network address prefix allocation by determining whether a network address prefix is occupied by other border nodes within a preset time period based on whether an indication message indicating that the currently available network address prefix has been occupied is received from other border nodes.
[0105] In one exemplary embodiment, the above method further includes:
[0106] S61, if a second address prefix occupancy request is received from the fourth boundary node among other boundary nodes during the second time period, the second unoccupied address prefix requested by the fourth boundary node is extracted from the second address prefix occupancy request.
[0107] S62, if the second address prefix to be occupied is the same as the first address prefix to be occupied, and the network address of the fourth boundary node is greater than the network address of the second boundary node, stop sending the first address prefix occupation request, and mark the first address prefix to be occupied as occupied.
[0108] While the second boundary node is sending a first address prefix occupancy request to other boundary nodes, when other boundary nodes need to use a network address prefix, they can select a network address prefix to be occupied from a set of network address prefixes in the same or similar manner, and send a network address prefix occupancy request to the top boundary nodes other than themselves. For example, the fourth boundary node among the other boundary nodes can send a second address prefix occupancy request to the top boundary nodes other than itself to request the occupation of the second unoccupied address prefix. The second unoccupied address prefix can be the same as or different from the first unoccupied address prefix.
[0109] During the second time period, the second boundary node can receive the aforementioned second address prefix occupancy request sent by the fourth boundary node and determine that the network address prefix to be occupied by the fourth boundary node is the second address prefix to be occupied. The second boundary node can determine whether the second address prefix to be occupied has already been occupied in a similar manner as described above. If it has, it returns a response message indicating that the second address prefix to be occupied has been occupied; otherwise, it ignores the second address prefix occupancy request.
[0110] If the second pending address prefix is the same as the first pending address prefix, to avoid network address prefix conflicts, the allocation of the first pending network address can be determined based on preset rules. These preset rules could be: allocation based on selection time, meaning the Top boundary node with the earliest selection time from a set of network address prefixes is allowed to occupy that network address prefix; or allocation based on priority, meaning a Top boundary node with higher priority is allowed to occupy that network address prefix.
[0111] To simplify the network address prefix allocation process, in this embodiment, network address prefix allocation can be based on the size of the network address of the Top boundary node. For example, a network address prefix can be assigned to a Top boundary node with a larger network address. Here, Top boundary nodes connected to the same router have the same network address prefix, and the comparison of network address sizes refers to the host addresses of different Top boundary nodes. If the network address of the fourth boundary node is greater than the network address of the second boundary node, the second boundary node relinquishes its claim to that network address prefix, stops sending first address prefix allocation requests to other boundary nodes, and marks the address prefix as occupied. If the network address of the fourth boundary node is less than the network address of the second boundary node, the second boundary node can continue to attempt to occupy that network address prefix and continue sending first address prefix allocation requests to other boundary nodes.
[0112] For example, in such Figure 3 In the wireless mesh network shown, automatic conflict detection of IPv6 address prefixes in the underlying network is possible. After obtaining a Top IPv6 address prefix, Top Border Router 1 sends a request to other Top Border Routers in the underlying network to claim the Top IPv6 address prefix via broadcast or multicast. If Top Border Router 3 is also sending the same request, Top Border Router 1 can compare the IPv6 address sizes of Top Border Router 1 and Top Border Router 3. If the IPv6 address of Top Border Router 3 is larger than that of Top Border Router 1, Top Border Router 1 stops sending the request to claim the Top IPv6 address prefix, marks the Top IPv6 address prefix as occupied, and re-executes the step of randomly selecting a Top IPv6 address prefix from the IPv6 address prefix pool and sending a claim request to other Top Border Routers.
[0113] In this embodiment, by comparing the network address sizes of boundary nodes requesting to occupy the same network address prefix, the boundary node with the larger network address continues to occupy the network address prefix, which simplifies the network address prefix occupation process and improves the efficiency of network address prefix allocation.
[0114] The address prefix allocation method in this embodiment will be explained below with reference to an optional example. In this optional example, the second boundary node is Top Border Router 1, the third boundary node is Top Border Router 2, the fourth boundary node is Top Border Router 3, and the preset set of network address prefixes is the IPv6 address prefix pool, and the network address prefix is the Top IPv6 address prefix.
[0115] To address the IP address management issues in mesh networks, this optional example provides a scheme for automatically assigning IP address prefixes. It eliminates the need for manual IPv6 prefix allocation, automatically assigning non-contiguous IPv6 prefixes while minimizing the number of IPv6 prefixes required. Combined with... Figure 3 and Figure 8 The process by which a top border router requests a network address prefix may include the following steps:
[0116] S801, Top Border Router 1 randomly selects a Top IPv6 address prefix from the IPv6 address prefix pool.
[0117] When a device in the underlying network identifies itself as a Top Border Router, it can automatically request one or more Top IPv6 address prefixes for connections outside the underlying network. For example, when Top Border Router 1 identifies itself as a Top Border Router, it can randomly select a Top IPv6 address prefix from the IPv6 address prefix pool.
[0118] S802, determine whether the prefix of the Top IPv6 address is already in use. If so, repeat step S801; otherwise, proceed to step S803.
[0119] S803 sends a request to claim a Top IPv6 address prefix in the underlying network in the form of broadcast or multicast.
[0120] S804, Top Border Router 2 sends a response to Top Border Router 1 indicating that the Top IPv6 address prefix has been occupied.
[0121] S805, mark the Top IPv6 address prefix as occupied, and re-execute step S801.
[0122] S806, Top Border Router 3 sends the same Top IPv6 address prefix claim request to Top Border Router 1.
[0123] S807, Top Border Router 1 compares its own network address with that of Top Border Router 3. If its own network address is larger, it continues to send a request to occupy the current network address prefix. If its own network address is smaller, it stops sending the request to occupy the current network address prefix and re-executes step S801.
[0124] This optional example demonstrates how selecting a Top IPv6 address prefix by a Top border router and sending a claim request to other Top border routers can prevent Top IPv6 address prefix claims between Top border routers and improve the rationality of Top IPv6 address prefix allocation.
[0125] In one exemplary embodiment, before receiving the first address prefix request sent by the first boundary node, the above method further includes:
[0126] S71, by adding a set of preset address bits after the first network address prefix, the first network address prefix is split into a set of sub-network address prefixes, wherein the set of preset address bits added to the sub-network address prefixes in the set of sub-network address prefixes are different from each other;
[0127] S72, set the second sub-network address prefix in a set of sub-network address prefixes as the sub-network address prefix used by devices in a homogeneous network rooted at the second boundary node, and mark the other sub-network address prefixes in the set of sub-network address prefixes other than the second sub-network address prefix as unassigned.
[0128] In this embodiment, a set of sub-network address prefixes can be obtained by splitting the first network address prefix. The first network address prefix can be split into a set of sub-network address prefixes by adding a preset address bit after the first network address prefix. The resulting set of sub-network address prefixes can be assigned to the non-Top boundary nodes contained in the second boundary node for the allocation and management of the sub-network address prefixes.
[0129] A set of preset address bits added after the first network address prefix are all different. The resulting set of sub-network address prefixes also have all preset address bits, while all other address bits are identical. For example, ... Figure 4 As shown, by adding different preset bits after the network address prefix, different sub-network address prefixes can be obtained.
[0130] For a homogeneous network rooted at the second boundary node, one sub-network address prefix can be selected from a set of sub-network address prefixes, such as the second sub-network address prefix, as the sub-network address prefix used by devices in the homogeneous network rooted at the second boundary node. Other sub-network address prefixes besides the second sub-network address prefix can be marked as unassigned so that they can be assigned to non-Top boundary nodes that require sub-network address prefixes.
[0131] For example, after a Top border router obtains a Top IPv6 address prefix, it subdivides the Top IPv6 address prefix into an IPv6 address prefix unit for its own network and other IPv6 address prefix units. The IPv6 address prefix unit for its own network is the IPv6 address prefix unit used in the network rooted at this Top border router, while the other IPv6 address prefix units are IPv6 address prefix units that can be assigned to subordinate non-Top border routers.
[0132] In this embodiment, by adding a set of different preset bits after the network address prefix, a set of sub-network address prefixes can be obtained, which can improve the utilization rate of the network address prefix.
[0133] In one exemplary embodiment, after receiving the first address prefix request sent by the first boundary node, the above method further includes:
[0134] S81, if there is no unallocated sub-network address prefix in a set of sub-network address prefixes, select a network address prefix marked as unoccupied from a preset set of network address prefixes to obtain the second network address prefix;
[0135] S82, if it is determined that the second network address prefix is not occupied, mark the second network address prefix as a network address prefix occupied by the second boundary node;
[0136] S83, by adding a set of preset address bits after the second network address prefix, the second network address prefix is split into multiple sub-network address prefixes, wherein the set of preset address bits added to the sub-network address prefixes of the multiple sub-network address prefixes are different from each other;
[0137] S84, selects the third sub-network address prefix from multiple sub-network address prefixes;
[0138] S85, send a second address prefix allocation message to the first boundary node, wherein the second address prefix allocation message is used to indicate that the third sub-network address prefix is allocated to the first boundary node.
[0139] As the number of devices in a Mesh network increases, IPv6 address prefixes can be automatically expanded and allocated. If all sub-network address prefixes in a set of sub-network address prefixes are marked as occupied, and the second boundary node has no sub-network address prefixes available for allocation to the first boundary node, it needs to re-apply for network address prefixes. The re-applied network address prefix is then split into sub-network address prefixes, which can be allocated to the first boundary node. When re-applying for network address prefixes, the second boundary node can select one marked as unoccupied from a preset set of network address prefixes to obtain a second network address prefix. If it is determined that no other boundary node occupies this network address prefix, it marks this second network address prefix as occupied by the second boundary node. The process of re-applying for network address prefixes is similar to that in the previous embodiments and will not be described in detail here.
[0140] After obtaining the second network address prefix, the second boundary node can add a set of different preset address bits after the second network address prefix, thereby splitting the second network address prefix into multiple sub-network address prefixes. The preset address bits of the sub-network address prefixes are different from each other, and the other address bits are completely the same. A third sub-network address prefix is selected from the multiple sub-network address prefixes, and the selected third sub-network address prefix is allocated to the first boundary node through the second address prefix allocation message. The method of splitting the second network address prefix and the method of allocating the third sub-network address prefix are similar to those in the previous embodiments, and will not be described again here.
[0141] This embodiment reduces the waste of network address prefix resources by determining whether there are any allocatable sub-network address prefixes after receiving an address prefix request, and then applying for and splitting a network address prefix when there are no allocatable sub-network address prefixes. This is because if there is no subsequent demand for sub-network address prefixes, the applied network address prefixes and the split sub-network address prefixes will be wasted, thus improving the rationality of network address prefix resource utilization.
[0142] In one exemplary embodiment, after sending the first address prefix allocation message to the first boundary node, the above method further includes:
[0143] S91, upon receiving a first address prefix allocation message, the first sub-network address prefix carried in the first address prefix allocation message is saved, wherein the saved first sub-network address prefix is used by devices in a homogeneous network rooted at the first boundary node;
[0144] S92, if the boundary node corresponding to the first boundary node changes among the boundary nodes that establish a communication connection with the router of the wireless mesh network, the saved first sub-network address prefix is revoked, wherein the revoked first sub-network address prefix is in an unavailable state.
[0145] Upon receiving a first address prefix allocation message, the first boundary node can store the first sub-network address prefix carried within it. This sub-network address prefix can be used in homogeneous networks rooted at the first boundary node. For example, in a network such as... Figure 3 In the wireless mesh network shown, non-Top border router 1, node 211 and node 212 are devices in a homogeneous network rooted at non-Top border router 1. The IPv6 address prefix unit assigned to non-Top border router 1 can be used in the homogeneous network rooted at non-Top border router 1.
[0146] In this embodiment, if the Top boundary node to which the first boundary node belongs changes, for example, due to a change in network topology, the already allocated first sub-network address prefix needs to be revoked and placed in an unavailable state to avoid conflicts with the new network topology. Furthermore, the first boundary node can request a sub-network address prefix from its new Top boundary node, in a manner similar to that described in the previous embodiments, and will not be repeated here.
[0147] In this embodiment, when the Top boundary node changes, the application of the sub-network address prefix is revoked and placed in an unavailable state. This avoids conflicts between the application of the sub-network address prefix and the changed network topology, and improves the accuracy of communication between devices in a homogeneous network rooted at a non-Top boundary node.
[0148] It should be noted that, for the sake of simplicity, the foregoing method embodiments are all described as a series of actions. However, those skilled in the art should understand that this application is not limited to the described order of actions, as some steps may be performed in other orders or simultaneously according to this application. Furthermore, those skilled in the art should also understand that the embodiments described in the specification are preferred embodiments, and the actions and modules involved are not necessarily essential to this application.
[0149] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods according to the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM (Read-Only Memory) / RAM (Random Access Memory), magnetic disk, optical disk), and includes several instructions to cause a terminal device (which may be a mobile phone, computer, server, or network device, etc.) to execute the methods described in the various embodiments of this application.
[0150] According to another aspect of the embodiments of this application, an address prefix allocation apparatus for implementing the above-described address prefix allocation method is also provided. Figure 9 This is a structural block diagram of an optional address prefix allocation device according to an embodiment of this application, such as... Figure 9 As shown, the device may include:
[0151] The receiving unit 902 is used to receive a first address prefix request sent by a first boundary node, wherein the first boundary node is a boundary node in the wireless mesh network that has not established a communication connection with the router of the wireless mesh network, and the first address prefix request is used to request the allocation of a network address prefix for the first boundary node;
[0152] The first selection unit 904, connected to the receiving unit 902, is used to respond to the first address prefix request and select the first sub-network address prefix from the unallocated sub-network address prefixes if there is an unallocated sub-network address prefix in a set of sub-network address prefixes that match the first network address prefix of the second boundary node. The second boundary node is the boundary node that establishes a communication connection with the router of the wireless mesh network corresponding to the first boundary node. The sub-network address prefixes in the set of sub-network address prefixes are the same except for a set of preset address bits, and the set of preset address bits are different from each other.
[0153] The first sending unit 906, connected to the first selection unit 904, is used to send a first address prefix allocation message to the first boundary node, wherein the first address prefix allocation message is used to indicate that the first sub-network address prefix is allocated to the first boundary node.
[0154] It should be noted that the receiving unit 902 in this embodiment can be used to perform the above step S202, the first selection unit 904 in this embodiment can be used to perform the above step S204, and the first sending unit 906 in this embodiment can be used to perform the above step S206.
[0155] Through the above module, a first address prefix request is received from a first boundary node, wherein the first boundary node is a boundary node in the wireless mesh network that has not established a communication connection with a router in the wireless mesh network, and the first address prefix request is used to request the allocation of a network address prefix for the first boundary node; in response to the first address prefix request, if there is an unallocated sub-network address prefix in a set of sub-network address prefixes that match the first network address prefix of a second boundary node, a first sub-network address prefix is selected from the unallocated sub-network address prefixes, wherein the second boundary node is a boundary node corresponding to the first boundary node that has established a communication connection with a router in the wireless mesh network, and the sub-network address prefixes in the set of sub-network address prefixes are identical in all address bits except for a set of preset address bits, and the set of preset address bits are all different from each other; a first address prefix allocation message is sent to the first boundary node, wherein the first address prefix allocation message is used to instruct the allocation of the first sub-network address prefix to the first boundary node, thereby solving the problem of poor applicability of network address prefix allocation methods in related technologies due to the need for manual allocation of network address prefixes, and improving the applicability of network address prefix allocation.
[0156] In one exemplary embodiment, the first transmitting unit includes:
[0157] The sending module is used to repeatedly send the first address prefix allocation message to the first boundary node at a preset frequency within a first time period until it receives a response message from the first boundary node in response to the first address prefix allocation message.
[0158] In one exemplary embodiment, the above-described apparatus further includes:
[0159] The first marking unit is used to mark the first sub-network address prefix as allocated when, after sending the first address prefix allocation message to the first boundary node, it receives a response message from the first boundary node in response to the first address prefix allocation message within a first time period.
[0160] The second marking unit is used to remark the first sub-network address prefix as unassigned if no response message is received from the first boundary node in response to the first address prefix allocation message within the first time period.
[0161] In one exemplary embodiment, the above-described apparatus further includes:
[0162] The first execution unit is configured to, after sending the first address prefix allocation message to the first boundary node, mark the first sub-network address prefix as allocated and count the allocation time of the first sub-network address prefix upon receiving the response message returned by the first boundary node in response to the first address prefix allocation message.
[0163] The timing unit is used to re-time the allocated time of the first sub-network address prefix when it receives an indication message from the first boundary node instructing the first boundary node to use the first sub-network address prefix before the allocated time of the first sub-network address prefix reaches a preset time threshold.
[0164] The third marking unit is used to mark the first sub-network address prefix as unassigned if it does not receive an indication message from the first boundary node indicating that the first boundary node should use the first sub-network address prefix before the allocation time of the first sub-network address reaches a preset time threshold.
[0165] In one exemplary embodiment, the above-described apparatus further includes:
[0166] The second selection unit is used to select a network address prefix marked as unoccupied from a preset set of network address prefixes before receiving the first address prefix request sent by the first boundary node, so as to obtain the first address prefix to be occupied;
[0167] The fourth marking unit is used to mark the first address prefix to be occupied as a network address prefix occupied by the second boundary node when it is determined that the first address prefix to be occupied is not occupied, wherein the first address prefix to be occupied is the first network address prefix.
[0168] In one exemplary embodiment, the above-described apparatus further includes:
[0169] The second sending unit is used to select a network address prefix marked as unoccupied from a preset set of network address prefixes to obtain the first address prefix to be occupied, and then continuously send the first address prefix occupation request to other boundary nodes during the second time period. The other boundary nodes are the boundary nodes that have established communication connections with the router of the wireless mesh network, except for the second boundary node. The first address prefix occupation request is used to request to occupy the first address prefix to be occupied.
[0170] The first determining unit is configured to determine that the first address prefix is not occupied if no indication message indicating that the first address to be occupied has been occupied is received from other boundary nodes within the second time period.
[0171] The second determining unit is configured to determine that the first address prefix to be occupied has been occupied when it receives an indication message from a third boundary node among other boundary nodes during the second time period, indicating that the first address prefix to be occupied has been occupied.
[0172] In one exemplary embodiment, the above-described apparatus further includes:
[0173] The extraction unit is used to extract the second address prefix to be occupied by the fourth boundary node from the second address prefix occupancy request when a second address prefix occupancy request is received from the fourth boundary node among other boundary nodes during the second time period.
[0174] The second execution unit is used to stop sending the first address prefix occupancy request and mark the first address prefix as occupied when the second address prefix to be occupied is the same as the first address prefix to be occupied and the network address of the fourth boundary node is greater than the network address of the second boundary node.
[0175] In one exemplary embodiment, the above-described apparatus further includes:
[0176] The first splitting unit is used to split the first network address prefix into a group of sub-network address prefixes by adding a set of preset address bits after the first network address prefix before receiving the first address prefix request sent by the first boundary node. The set of preset address bits added to the sub-network address prefixes in the group of sub-network address prefixes are different from each other.
[0177] The third execution unit is used to set the second sub-network address prefix in a set of sub-network address prefixes as the sub-network address prefix used by devices in the homogeneous network rooted at the second boundary node, and to mark the other sub-network address prefixes in the set of sub-network address prefixes other than the second sub-network address prefix as unassigned.
[0178] In one exemplary embodiment, the above-described apparatus further includes:
[0179] The third selection unit is used to select a network address prefix marked as unoccupied from a preset set of network address prefixes after receiving the first address prefix request sent by the first boundary node, in the case that there is no unallocated sub-network address prefix in a set of sub-network address prefixes, to obtain the second network address prefix.
[0180] The fifth marking unit is used to mark the second network address prefix as a network address prefix occupied by the second boundary node when it is determined that the second network address prefix is not occupied; the second splitting unit is used to split the second network address prefix into multiple sub-network address prefixes by adding a set of preset address bits after the second network address prefix, wherein the set of preset address bits added to the sub-network address prefixes of the multiple sub-network address prefixes are different from each other.
[0181] The fourth selection unit is used to select a third sub-network address prefix from multiple sub-network address prefixes; the third sending unit is used to send a second address prefix allocation message to the first boundary node, wherein the second address prefix allocation message is used to indicate that the third sub-network address prefix is allocated to the first boundary node.
[0182] In one exemplary embodiment, the above-described apparatus further includes:
[0183] The storage unit is used to, after sending the first address prefix allocation message to the first boundary node, and upon receiving the first address prefix allocation message, store the first sub-network address prefix carried in the first address prefix allocation message, wherein the stored first sub-network address prefix is used by devices in the homogeneous network rooted at the first boundary node.
[0184] The cancellation unit is used to cancel the saved first sub-network address prefix when the boundary node corresponding to the first boundary node changes among the boundary nodes that have established a communication connection with the router of the wireless mesh network. The first sub-network address prefix is in an unavailable state after cancellation.
[0185] According to another aspect of the embodiments of this application, a storage medium is also provided. Optionally, in this embodiment, the storage medium can be used to execute program code for any of the address prefix allocation methods described above in the embodiments of this application.
[0186] Optionally, in this embodiment, the storage medium may be located on at least one of the network devices in the network shown in the above embodiment.
[0187] Optionally, in this embodiment, the storage medium is configured to store program code for performing the following steps:
[0188] S1, receive a first address prefix request sent by a first boundary node, wherein the first boundary node is a boundary node in the wireless mesh network that has not established a communication connection with the router of the wireless mesh network, and the first address prefix request is used to request the allocation of a network address prefix for the first boundary node;
[0189] S2, in response to the first address prefix request, if there is an unallocated sub-network address prefix in a set of sub-network address prefixes that match the first network address prefix of the second boundary node, the first sub-network address prefix is selected from the unallocated sub-network address prefixes. The second boundary node is the boundary node that establishes a communication connection with the router of the wireless mesh network corresponding to the first boundary node. The sub-network address prefixes in the set of sub-network address prefixes are the same except for a set of preset address bits, and the set of preset address bits are different from each other.
[0190] S3, send a first address prefix allocation message to the first boundary node, wherein the first address prefix allocation message is used to indicate that the first sub-network address prefix is allocated to the first boundary node.
[0191] Optionally, specific examples in this embodiment can refer to the examples described in the above embodiments, and will not be repeated in this embodiment.
[0192] Optionally, in this embodiment, the storage medium may include, but is not limited to, various media capable of storing program code, such as USB flash drives, ROMs, RAMs, portable hard drives, magnetic disks, or optical disks.
[0193] According to another aspect of the embodiments of this application, an electronic device for implementing the above-described address prefix allocation method is also provided, the electronic device being a server, a terminal, or a combination thereof.
[0194] Figure 10 This is a structural block diagram of an optional electronic device according to an embodiment of this application, such as... Figure 10 As shown, it includes a processor 1002, a communication interface 1004, a memory 1006, and a communication bus 1008. The processor 1002, communication interface 1004, and memory 1006 communicate with each other via the communication bus 1008.
[0195] Memory 1006 is used to store computer programs;
[0196] When processor 1002 executes a computer program stored in memory 1006, it performs the following steps:
[0197] S1, receive a first address prefix request sent by a first boundary node, wherein the first boundary node is a boundary node in the wireless mesh network that has not established a communication connection with the router of the wireless mesh network, and the first address prefix request is used to request the allocation of a network address prefix for the first boundary node;
[0198] S2, in response to the first address prefix request, if there is an unallocated sub-network address prefix in a set of sub-network address prefixes that match the first network address prefix of the second boundary node, the first sub-network address prefix is selected from the unallocated sub-network address prefixes. The second boundary node is the boundary node that establishes a communication connection with the router of the wireless mesh network corresponding to the first boundary node. The sub-network address prefixes in the set of sub-network address prefixes are the same except for a set of preset address bits, and the set of preset address bits are different from each other.
[0199] S3, send a first address prefix allocation message to the first boundary node, wherein the first address prefix allocation message is used to indicate that the first sub-network address prefix is allocated to the first boundary node.
[0200] Optionally, the communication bus can be a PCI (Peripheral Component Interconnect) bus or an EISA (Extended Industry Standard Architecture) bus, etc. This communication bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 10 The symbol is represented by a single thick line, but this does not indicate that there is only one bus or one type of bus. The communication interface is used for communication between the aforementioned electronic device and other devices.
[0201] The memory may include RAM, or non-volatile memory, such as at least one disk storage device. Optionally, the memory may also be at least one storage device located remotely from the aforementioned processor.
[0202] As an example, the memory 1006 described above may include, but is not limited to, the receiving unit 902, the first selection unit 904, and the first sending unit 906 in the address prefix allocation device. Furthermore, it may include, but is not limited to, other module units in the address prefix allocation device, which will not be elaborated upon in this example.
[0203] The processors mentioned above can be general-purpose processors, including but not limited to: CPU (Central Processing Unit), NP (Network Processor), etc.; they can also be DSP (Digital Signal Processor), ASIC (Application Specific Integrated Circuit), FPGA (Field-Programmable Gate Array), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components.
[0204] Optionally, specific examples in this embodiment can refer to the examples described in the above embodiments, and will not be repeated here.
[0205] Those skilled in the art will understand that Figure 10 The structure shown is for illustrative purposes only. The device implementing the above address prefix allocation method can be a terminal device, such as a smartphone (e.g., Android phone, iOS phone), tablet computer, PDA, mobile Internet Devices (MID), PAD, etc. Figure 10 This does not limit the structure of the aforementioned electronic device. For example, the electronic device may also include components that are more... Figure 10 The more or fewer components shown (such as network interfaces, display devices, etc.), or having the same Figure 10 The different configurations shown.
[0206] Those skilled in the art will understand that all or part of the steps in the various methods of the above embodiments can be implemented by a program instructing the hardware related to the terminal device. The program can be stored in a computer-readable storage medium, which may include: flash drive, ROM, RAM, disk or optical disk, etc.
[0207] The sequence numbers of the embodiments in this application are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.
[0208] If the integrated units in the above embodiments are implemented as software functional units and sold or used as independent products, they can be stored in the aforementioned computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause one or more computer devices (which may be personal computers, servers, or network devices, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application.
[0209] In the above embodiments of this application, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions of other embodiments.
[0210] In the several embodiments provided in this application, it should be understood that the disclosed client can be implemented in other ways. The device embodiments described above are merely illustrative; for example, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces, indirect coupling or communication connection between units or modules, and may be electrical or other forms.
[0211] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of the solution provided in this embodiment, depending on actual needs.
[0212] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or at least two units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.
[0213] The above description is only a preferred embodiment of this application. It should be noted that for those skilled in the art, several improvements and modifications can be made without departing from the principle of this application, and these improvements and modifications should also be considered within the scope of protection of this application.
Claims
1. A method for allocating address prefixes, characterized in that, include: Receive a first address prefix request sent by a first boundary node, wherein the first boundary node is a boundary node in the wireless mesh network that has not established a communication connection with the router of the wireless mesh network, and the first address prefix request is used to request the allocation of a network address prefix for the first boundary node; In response to the first address prefix request, if there is an unallocated sub-network address prefix in a set of sub-network address prefixes matching the first network address prefix of the second boundary node, a first sub-network address prefix is selected from the unallocated sub-network address prefixes; if there is no unallocated sub-network address prefix in a set of sub-network address prefixes matching the first network address prefix of the second boundary node, a new network address prefix matching the second boundary node is requested, and the network address prefix matching the second boundary node is split into sub-network address prefixes, and one sub-network address prefix is selected from the split sub-network address prefixes as the first sub-network address prefix allocated to the first boundary node; wherein, the second boundary node is a boundary node corresponding to the first boundary node that establishes a communication connection with the router of the wireless mesh network, and the sub-network address prefixes in the set of sub-network address prefixes are identical in all address bits except for a set of preset address bits, and the set of preset address bits are all different from each other; Send a first address prefix allocation message to the first border node, wherein the first address prefix allocation message is used to indicate that the first sub-network address prefix is allocated to the first border node.
2. The method according to claim 1, characterized in that, Sending the first address prefix allocation message to the first boundary node includes: Within a first time period, the first address prefix allocation message is repeatedly sent to the first border node at a preset frequency until a response message is received from the first border node in response to the first address prefix allocation message.
3. The method according to claim 2, characterized in that, After sending the first address prefix allocation message to the first boundary node, the method further includes: If, during the first time period, a response message is received from the first boundary node in response to the first address prefix allocation message, the first sub-network address prefix is marked as allocated. If no response message is received from the first boundary node in response to the first address prefix allocation message within the first time period, the first sub-network address prefix is remarked as unallocated.
4. The method according to claim 1, characterized in that, After sending the first address prefix allocation message to the first boundary node, the method further includes: Upon receiving a response message from the first boundary node in response to the first address prefix allocation message, the first sub-network address prefix is marked as allocated, and the allocation time of the first sub-network address prefix is timed. If an indication message is received from the first boundary node before the allocated time of the first sub-network address prefix reaches a preset time threshold, indicating that the first boundary node is using the first sub-network address prefix, the allocated time of the first sub-network address prefix shall be re-timed. If no indication message from the first border node instructing the first border node to use the first sub-network address prefix is received before the allocated time of the first sub-network address reaches a preset time threshold, the first sub-network address prefix is marked as unallocated.
5. The method according to claim 1, characterized in that, Before receiving the first address prefix request sent by the first boundary node, the method further includes: Select a network address prefix marked as unoccupied from a preset set of network address prefixes to obtain the first address prefix to be occupied; If it is determined that the first address prefix to be occupied is not occupied, the first address prefix to be occupied is marked as a network address prefix occupied by the second boundary node, wherein the first address prefix to be occupied is the first network address prefix.
6. The method according to claim 5, characterized in that, After selecting a network address prefix marked as unoccupied from a preset set of network address prefixes to obtain the first address prefix to be occupied, the method further includes: During the second time period, a first address prefix occupancy request is continuously sent to other boundary nodes, wherein the other boundary nodes are boundary nodes other than the second boundary node among the boundary nodes that have established communication connections with the router of the wireless mesh network, and the first address prefix occupancy request is used to request the occupancy of the first address prefix to be occupied; If no indication message indicating that the first pending network address prefix has been occupied is received from the other boundary nodes during the second time period, it is determined that the first pending address prefix has not been occupied. If, during the second time period, an indication message is received from the third boundary node among the other boundary nodes, indicating that the first address prefix to be occupied has been occupied, it is determined that the first address prefix to be occupied has been occupied.
7. The method according to claim 6, characterized in that, The method further includes: If a second address prefix occupancy request is received from the fourth boundary node among the other boundary nodes during the second time period, the second unoccupied address prefix requested by the fourth boundary node is extracted from the second address prefix occupancy request. If the second address prefix to be occupied is the same as the first address prefix to be occupied, and the network address of the fourth boundary node is greater than the network address of the second boundary node, the sending of the first address prefix occupancy request is stopped, and the first address prefix to be occupied is marked as occupied.
8. The method according to claim 1, characterized in that, Before receiving the first address prefix request sent by the first boundary node, the method further includes: By adding the set of preset address bits after the first network address prefix, the first network address prefix is split into the set of sub-network address prefixes, wherein the set of preset address bits added to the sub-network address prefixes in the set of sub-network address prefixes are all different. The second sub-network address prefix in the set of sub-network address prefixes is set as the sub-network address prefix used by devices in the homogeneous network rooted at the second boundary node, and the other sub-network address prefixes in the set of sub-network address prefixes other than the second sub-network address prefix are marked as unassigned.
9. The method according to claim 1, characterized in that, After receiving the first address prefix request sent by the first boundary node, the method further includes: If there is no unallocated sub-network address prefix in the set of sub-network address prefixes, select a network address prefix marked as unoccupied from a preset set of network address prefixes to obtain the second network address prefix; If it is determined that the second network address prefix is not occupied, the second network address prefix is marked as a network address prefix occupied by the second boundary node; By adding the set of preset address bits after the second network address prefix, the second network address prefix is split into multiple sub-network address prefixes, wherein the set of preset address bits added to the sub-network address prefixes of the multiple sub-network address prefixes are different from each other; Select a third sub-network address prefix from the plurality of sub-network address prefixes; A second address prefix allocation message is sent to the first boundary node, wherein the second address prefix allocation message is used to indicate that the third sub-network address prefix is allocated to the first boundary node.
10. The method according to any one of claims 1 to 9, characterized in that, After sending the first address prefix allocation message to the first boundary node, the method further includes: Upon receiving the first address prefix allocation message, the first sub-network address prefix carried in the first address prefix allocation message is saved, wherein the saved first sub-network address prefix is used in devices within a homogeneous network rooted at the first boundary node; If the boundary node corresponding to the first boundary node changes among the boundary nodes that have established a communication connection with the router of the wireless mesh network, the saved first sub-network address prefix is revoked, wherein the revoked first sub-network address prefix is in an unavailable state.
11. An address prefix allocation device, characterized in that, include: A receiving unit is configured to receive a first address prefix request sent by a first boundary node, wherein the first boundary node is a boundary node in the wireless mesh network that has not established a communication connection with a router of the wireless mesh network, and the first address prefix request is used to request the allocation of a network address prefix for the first boundary node. A first selection unit is configured to, in response to the first address prefix request, select a first sub-network address prefix from a set of unallocated sub-network address prefixes that match the first network address prefix of the second boundary node; and, if no unallocated sub-network address prefix is found in the set of sub-network address prefixes that match the first network address prefix of the second boundary node, re-apply for a network address prefix that matches the second boundary node, split the network address prefix that matches the second boundary node into sub-network address prefixes, and select one sub-network address prefix from the split sub-network address prefixes as the first sub-network address prefix allocated to the first boundary node; wherein the second boundary node is a boundary node corresponding to the first boundary node that establishes a communication connection with the router of the wireless mesh network, and the sub-network address prefixes in the set of sub-network address prefixes are identical in all address bits except for a set of preset address bits, and the set of preset address bits are all different from each other; The first sending unit is configured to send a first address prefix allocation message to the first border node, wherein the first address prefix allocation message is used to indicate that the first sub-network address prefix is allocated to the first border node.
12. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes a stored program, wherein the program, when executed, performs the method of any one of claims 1 to 10.
13. An electronic device comprising a memory and a processor, characterized in that, The memory stores a computer program, and the processor is configured to execute the method of any one of claims 1 to 10 through the computer program.
Citation Information
Patent Citations
Method and system for establishing IPv6 (Internet Protocol Version 6) address pool
CN102340551A
Method and device for redistributing address prefixes
CN111586197A