Address generation system for wireless communication networks

Abstract

The present application relates to an address generation system (100) for a wireless communication network (102) including at least one sink device (104, 104a, 104b) and at least one wireless node device (108, 108a, 108b). Each wireless node device (108, 108a, 108b) is configured to communicate with at least one sink device or other wireless node devices (108) belonging to the at least one wireless node device. Each wireless node device is configured to generate its internet address (IA), the internet address (IA) including a sink identifier (ID) of the sink device (104, 104a, 104b) belonging to the at least one sink device and a wireless communication network address (NA) of the wireless node device, such that the wireless node device is accessible via the sink device.

Description

[Technical Field]

[0001] This application relates generally to address generation systems for wireless communication networks. [Background technology]

[0002] A single large-scale Internet Protocol version 6 (IPv6)-related wireless mesh network including multiple wireless node devices may include multiple border routers and multiple sinks for reasons of robustness, capacity, and scalability. For example, if the backhaul links are Ethernet links and the border routers are connected to the same links, the border routers may be connected to the same links and reside in the same IPv6 subnet in the physical topology. The border routers may also be logically, rather than physically, connected to the same links and reside in the same IPv6 subnet, for example, via a bridged Layer 2 (L2) virtual private network (VPN).

[0003] The IPv6 Neighbor Discovery (ND) mechanism allows node devices on a particular link to perform an autoconfiguration mechanism. The discovery mechanism allows routers to advertise their presence on a link through Router Advertisement (RA) messages, and allows routers and other IPv6 node devices to resolve the link-layer (LL) addresses of on-link neighbors using Neighbor Solicitation (NS) and Neighbor Advertisement (NA) messages.

[0004] The IPv6 Stateless Address Autoconfiguration (SLAAC) mechanism allows a node device to automatically generate an IPv6 address using an IPv6 prefix, obtained, for example, from an RA message or some other message, in combination with an Interface Identifier (IID) generated, for example, from an LL address or some other address or information.

[0005] The basic IPv6 subnetting model specifies that an IPv6 subnet may not span multiple links. Different links using the same or different LL technologies are in different IPv6 subnets and should communicate with each other using Internet Protocol (IP) routing.

[0006] The IPv6 ND proxy mechanism specifies how to bridge multiple links into a single IPv6 subnet by allowing a proxy device, e.g., a border router, to answer NS messages with NA messages on behalf of other devices, e.g., node devices. This proxying is done according to an ND proxy cache that resides on the proxy device and contains the IPv6 addresses to be proxied. An ND proxy mechanism may reside, for example, on a border router, and a corresponding ND proxy cache that also resides on the border router may contain the IPv6 addresses of node devices connected to the border router.

[0007] Compared to traditional IP routing, the use of the ND proxy mechanism allows a single subnet prefix to support multiple physical links, eliminating the need to assign subnet numbers to different networks, thereby simplifying administration. Furthermore, its use allows for easy connection of at least one leaf link to an existing network without requiring any coordination with Internet Service Providers (ISPs) or upstream routers, as well as suppressing broadcast-intensive IPv6 ND messaging in downstream networks when the downstream network offers more efficient technology-specific alternatives.

[0008] With the ND proxy mechanism, when a node device changes from one sink and border router to another, the ND proxy caches of these border routers contain the same IPv6 address of the node device, so both ND proxies will reply to the NS / NA messages to the same IPv6 address, which will cause undefined operation. Summary of the Invention

[0009] One object of the present invention is to overcome the drawbacks of known solutions and to provide an address generation method for generating unique unicast internet addresses for wireless node devices in all ND proxies and updating ND proxies and external devices outside the wireless communication network, so that downlink information from external devices is sent via the correct border router and the correct sink device.

[0010] One object of the present invention is achieved by providing an address generation system, a wireless node device, an address generation method, a computer program, and a computer-readable medium according to the independent claims.

[0011] Embodiments of the invention are disclosed in the independent and dependent claims.

[0012] An address generation system for a wireless communication network includes at least one sink device and at least one wireless node device, each configured to communicate with the at least one sink device or other wireless node devices belonging to the at least one wireless node device, and each wireless node device further configured to generate an internet address for the wireless node device including a sink identifier of the sink device belonging to the at least one sink device and a network address of the wireless node device, such that the wireless node device is accessible via the sink device.

[0013] A wireless node device for address generation in a wireless communication network includes a controller and a wireless communication device, the controller and the wireless communication device are configured to perform wireless communication with at least one sink device or other wireless node devices belonging to the wireless communication network, and the controller is further configured to generate an internet address including a sink identifier of the sink device and a network address of the wireless node device belonging to the at least one sink device, so that the wireless node device is accessible via the sink device.

[0014] One address generation method for a wireless communication network is performed by a previous address generation system or a previous wireless node device. The method includes the following steps: communicating with a sink device or another wireless node device belonging to the wireless communication network by the wireless node device; and generating, by the wireless node device, an internet address for the wireless node device, the internet address including a sink identifier of the sink device and a network address of the wireless node device, so that the wireless node device is accessible via the sink device.

[0015] One computer program includes instructions that, when executed (run, performed, operated) by a processor, cause a wireless node device to perform at least the steps of a previous address generation method according to a previous wireless node device.

[0016] A tangible, non-volatile computer readable medium containing the predecessor computer program related to the predecessor computer program.

[0017] Exemplary embodiments of address generation will now be described with reference to the accompanying drawings. [Brief explanation of the drawings]

[0018] [Figure 1]1 shows an address generation system. [Figure 2] 1 shows a flowchart of an address generation method. [Figure 3] This shows the internet address format. [Figure 4] 1 illustrates the operational parts of a wireless radio node device. DETAILED DESCRIPTION OF THE INVENTION

[0019] Detailed Description of the Drawings FIG. 1 illustrates an address generation system 100 operating in a communication environment, where communication is wireless over at least a wireless wireless communication network (communication network system) 102 that includes multiple wireless wireless communication devices (communication devices) 104, 108.

[0020] The plurality of devices 104, 108 includes at least one sink device (sink) 104, e.g., one, two, three, four, or more sink devices 104, and at least one node device (node) 108, e.g., one, two, three, four, or more node devices 108. The devices 104, 108 are configured, for example, in the presented environment, to operate in the same spectrum in the same geographic region. Use of the same spectrum enables bidirectional wireless communication between the devices 104, 108 in the network 102, where a wireless communication (transmission) transmitted by one device 104, 108 may be received by another device 104, 108, and vice versa. Alternatively, some or all of the devices 104, 108 may be configured to operate in different spectrums in the same geographic region.

[0021] The system 100 is configured in a wireless radio communication network 102 that uses packet transmission for communication. The system 100 may be applied to a wireless communication network 102 that complies with the Digital European Cordless Telecommunications (DECT-2020) standard.

[0022] The DECT-2020 standard is a radio access technology developed by ETSI. DECT-2020 supports massive machine-based communications (mMTC) and ultra-reliable low-latency communications (URLLC). At the physical (PHY) layer, the key technology components of DECT-2020 are orthogonal frequency-division multiplexing (OFDM), adaptive modulation and coding schemes (MCS), modern channel coding methods (Turbo, LDPC, and convolutional coding), hybrid automatic repeat request (HARQ) for both scheduled and contention-based transmissions, and support for multi-antenna communication using different multiple-input multiple-output (MIMO) streams. At the medium access (MAC) layer and from the system aspect, the key technology components of DECT-2020 are support for numerous Internet of Things (IoT) sensors, actuators, and other industrial applications; support for mesh network topologies; support for URLLC communication with very low latency (a typical application would be wireless microphones); and support for license-exempt frequency operation and multiple overlapping uncoordinated networks with cognitive radio capabilities to share spectrum resources among multiple networks.

[0023] Some other non-limiting examples to which system 100 may also be applied may include, but are not limited to, a Bluetooth Low Energy (BLE) mesh network, a ZigBee network, a Thread network, a public land mobile network (PLMN), a wireless local area network (WLAN), a low power wide area network (LPWAN), a cellular-based local area network, a cellular network, a wireless multi-hop network, or a wireless mesh network, e.g., the wireless sensor network of patent application US 2021 / 0282004, and / or any other wireless network.

[0024] The devices 104, 108 are configured to receive packet communications with one wireless technology, e.g., BLE communications or WLAN communications, where all communications are from the same network 102. However, at least one of the devices 104, 108, e.g., one, two, three, four, or more devices, may be configured to receive communications with at least two wireless technologies, e.g., BLE communications and WLAN communications, where all communications are from the same network 102.

[0025] The system 100 will be described primarily using four devices 104a, 104b, 108a, and 108b belonging to the system 100, which are configured to operate in the network 102 and to perform single-hop and multi-hop communications within the network 102. The sink devices 104a and 104b correspond to the sink device 104, and the node devices 108a and 108b correspond to the node device 108. The network 102 may also include multiple other devices 104, 108, in which case the network 102 includes the devices 104, 104a, 104b, 108, 108a, and 108b.

[0026] As explained above, each device 104, 108 is configured by its wireless communication apparatus (communication apparatus, data transmitter) 436 to provide bidirectional single-hop and multi-hop wireless communication with at least one other device 104, 108. This means that each device 104, 108 may be configured to operate as a transmitter, as a receiver, or as a transceiver, where each device 104, 108 is configured to send at least one data communication (transmission, message) UL, DL to other device(s) 104, 108 in the network 102 and to receive at least one data communication UL, DL from other device(s) 104, 108.

[0027] The system 100 also includes at least one Internet router device (Internet router, customer edge (CE) router) 105, e.g., one, two, three, four, or more Internet routers 105. Each Internet router 105 is configured to operate as a router that routes (distributes, forwards) data from other external communication network(s) 106, e.g., the Internet, towards the network 102, vice versa, outside the network 102 alone, or together with other existing Internet router(s) 105, if present.

[0028] Each Internet router 105 is configured to communicate with at least one external communication device 107, e.g., one, two, three, four, or more external devices 107, and with other Internet routers 105, if present, in the external network(s) 106. An Internet router 105 is also configured to communicate with at least one border router device (border router) 103 outside the network 102, e.g., one, two, three, four, or more border routers 103, via a connection WC that is part of the external network(s) 106. The connection WC may be a wired connection, e.g., an Ethernet connection, as shown, or a wireless connection WC, e.g., a WLAN or cellular connection.

[0029] Alternatively, the Internet router 105 may be configured to communicate with at least one sink device 104, for example, one, two, three, four, or more sink devices 104, if the Internet router 105 includes a border router 103, in which case the border router 103 acts as the Internet router 105.

[0030] The system 100 also includes at least one border router 103, e.g., one, two, three, four, or more border routers 103. Each border router 103 is connected to an Internet router 105 via a connection WC, as shown in the figure. Alternatively, at least one border router 103, e.g., one, two, three, four, or more border routers 103, may operate as an Internet router 105, in which case each existing border router(s) 103, if any, that does not operate as an Internet router 105 is connected via a connection WC to one border router 103 that operates as an Internet router 105. Alternatively, each border router 103 may operate as an Internet router 105.

[0031] If at least one border router 103 acts as an Internet router 105 in the system 100, the external device(s) 107 may communicate directly with the border router(s) 103 acting as the Internet router 105.

[0032] Each border router 103 is configured to act as a wireless communication network entry between network 102 and other external network(s) 106, e.g., the Internet, and to deliver data from other external network(s) 106 to network 102 and vice versa via sink device(s) 104. Each border router 103 includes or has connections to at least one sink device 104, e.g., one, two, three, four, or more sink devices 104.

[0033] The system 100 also includes at least one sink device 104 configured to communicate with at least one border router 103, as previously described. Each sink device 104 is configured to operate as a wireless interface for a border router 103 in the network 102. Each sink device 104 may be located in physical connection with the border router 103 or may be located separately in a different portion of the network 102. If a border router 103 includes several sink devices 104, at least one, e.g., one, two, three, four, or more sink devices 104 may be located in connection with the border router 103, and the rest may be located separately in a different portion of the network 102.

[0034] Each sink device 104 is a fixed router device (mesh router), but the node devices 108 are configured to operate in different fixed or non-fixed roles in the network 102. The node devices 108 in the system 100 are router devices and non-router devices depending on whether the node devices 108 need to participate in data routing (distribution, forwarding) or not. One method for selecting the role of router or non-router in the network 102 can follow, for example, the method described in patent application US 10,499,264.

[0035] Each mesh router 104, 108 is configured to maintain connectivity for the system 100 and route data for other devices 104, 108 as needed. Each non-router device 108 is configured to provide bidirectional communication to transmit its own data and receive data directed to it as well as sink and router devices 104, 108, but the non-router devices 108 do not route data for other devices 104, 108. Each of the devices 108 is configured to operate at least as a router device or a non-router device.

[0036] The system 100 includes node devices 108, whereby due to wide distances and limited wireless ranges between the node devices 108, some of the node devices 108 may not be able to communicate directly with the sink device(s) 104 (border router 103), in which case multi-link (multi-hop) communication between each device 108 and the sink device 104 must be used.

[0037] System 100 also includes a back-end system (not shown) that may be an external control system, a monitoring system, or both, and may be implemented on a high-performance computer. Alternatively, the back-end system may simply be implemented on a mobile device (phone) that communicates with Internet router(s) 105, border router(s) 103, or directly with one of devices 104, 108, using the wireless interface of network 102 or another wireless interface, such as a BLE or radio frequency identification (RFID) interface, for example, to deliver configuration information to network 102. In such a configuration, the mobile device also has a connection to a high-performance computer, which in this case may act as Internet router 105.

[0038] The system 100 is configured to generate an internet address IA for each node device 108 and use the generated address IA so that external devices 107 and internet routers 105 outside the network 102 can communicate downlink packet communications DL with the associated node device 108 via the correct border router 103 and the correct sink device 104 with which the associated node device 108 is currently in the routing topology.

[0039] The internet address IA of the node device 108 may be a unicast IPv6 address or a unicast IPv4 address.

[0040] 2 illustrates an address generation method 210 for generating an internet address IA for a node device 108. The method 210 is performed in the system 100 described above.

[0041] In step 212, one of the node devices 108, i.e., node device 108a corresponding to node device 108, is directly associated by its controller 430 and communication unit 436 with sink node 104a corresponding to the other sink device 104 as shown in the figure in a single-hop communication. When node device 108a sends an uplink internet packet (IP) communication (message) UL, e.g., an uplink IPv4 or IPv6 communication, to sink device 104a or outside network 102, it communicates directly with sink device 104 and further via sink device 104a if the destination (recipient) of the packet communication UL is outside network 102. Correspondingly, when an external device 107, internet router 105 or border router 103 outside of network 102 or sink device 104a sends downlink IP communication DL, e.g., downlink IPv4 or IPv6 communication, to node device 108a, the packet communication DL is routed through sink device 104a if the source (sender) of the packet communication DL is outside of network 102 and also communicates directly with node device 108a.

[0042] Alternatively, node device 108a may be associated by its controller 430 and communication unit 436 with an intermediate node device 108 that acts as a mesh router between node device 108a and sink device 104a in a multi-hop communication. Node device 108a is then part of the routing topology of sink device 104a, meaning that an uplink packet communication UL sent by node device 108a to sink device 104a or outside network 102 is routed via at least one intermediate node device 108, e.g., one, two, three, four, or more intermediate node devices 108, if the destination (recipient) of the packet communication UL is sink device 104a. The packet communication UL is further routed via sink device 104a if the destination of the packet communication UL is outside network 102. When an external device 107, internet router 105, or border router 103 outside the network 102 or sink device 104a sends a downlink packet communication DL to node device 108a, the packet communication DL is routed through sink device 104a if the source (sender) of the packet communication DL is outside the network 102. The packet communication DL may be further routed to node device 108a via at least one intermediate node device 108, e.g., one, two, three, four, or more intermediate node devices 108, or may communicate directly with node device 108a, e.g., when an association change occurs.

[0043] The node device 108a has a network address (node ​​address) NA, for example, a 32-bit DECT-2020 NR RD-ID identifier, and when the node device 108a associates with the sink device 104a or the intermediate node device 108, it obtains the network address of the current sink device 104a from a known association mechanism by its controller 430 and communication unit 436.

[0044] In step 214, the node device 108a, by its controller 430, generates its internet (IP) address IA that identifies and locates the node device 108a in the network 102. The node device 108a generates the internet address IA from the sink identifier ID for the current sink device 104a and from the network address NA of said wireless node device 108a by at least partially processing the sink identifier ID and the network address NA, for example, by using at least one of concatenation, hashing, and other processing of the sink identifier ID and the network address NA. The sink identifier ID includes the network address of the sink device 104a, for example, a 32-bit long DECT-2020 NR RD-ID identifier, a generated random value, or any identifier that allows for identifying the sink device 104a. Alternatively, the sink identifier ID may include any identifier, for example, the identifier of the border router 103a to which the sink device 104a is connected, that enables the system 100 to communicate data from the external network(s) 106 through the sink device 104a to the node device 108a.

[0045] The node device 108a includes the processed sink identifier ID and network address NA in the interface identifier (IID) field of the Internet (IP) address format AF shown in Figure 3. The address format AF also includes an Internet Subnet Prefix field for an Internet Subnet Prefix (Network Prefix) PR, which consists of a subnet address of the network 102 that is the same for all devices 104, 108 in the network 102. Thus, the generated Internet address IA of the node device 108a consists of the subnet prefix PR in the Subnet Prefix field and the processed sink identifier ID and network address NA in the IID field, which greatly improves the accessibility of the node device 108a from outside the network 102 when the exact sink device 104, 104a, 104b is known.

[0046] In step 216, node device 108a communicates with sink device 104a via controller 430 and communication unit 436 by sending an uplink packet communication UL to inform at least one of sink device 104a, border router 103a to which sink device 104a is connected, and external device 107, e.g., sink device 104a only, border router 103a only, sink device 104a and border router 103a, sink device 104a and external device 107 if relevant, border router 103a and external device 107 if relevant, or all of devices 103a, 104a, 107 if relevant, of its current Internet address IA. After receiving the packet communication UL, its receiver(s), including at least one of border router 103a and sink device 104a, are configured to update their ND proxy caches with node device 108a's current address IA.

[0047] The packet communication UL includes the address of the node device 108a (source, sender), the address of the receiver (destination) 103a, 104a, 107, e.g., the address of the border router 103a, the sink device 104a, or the external device 107, and within the payload of the packet communication UL, a unique identifier UID that enables the external device 107 to send the downlink packet communication DL to the correct node device 108a from outside the network 102. Furthermore, the payload of the packet communication UL may include a previous Internet address IA that includes a sink identifier ID of the previous sink device 104. Additionally or alternatively, with regard to the previous identifier option, the payload of the packet communication packet UL may include its generated current Internet address IA. In addition to the previous option, the payload of the packet communication UL may include other information, e.g., application-related data, if the node device 108a has to send such information.

[0048] In step 218, when node device 108a changes the routing of its packet communication UL, DL such that sink device 104a is changed to another sink device 104 according to the figure, it associates with the new sink device 104b directly or with another intermediate node device 108 configured to route the packet communication UL to the new sink device 104b or via at least one other intermediate node device 108, e.g., one, two, three, four, or more intermediate node devices 108, by means of controller 430 and communication unit 436.

[0049] After node device 108a decides to perform a sink change between sink devices 104a, 104b, it does not notify the previous sink 104a of the upcoming sink change. Alternatively, when node device 108a decides to perform a sink change between sink devices 104a, 104b, it may notify the previous sink device 104a, the border router 103a, or both devices 103a, 104a of the sink change by sending an uplink packet communication RE to the previous device(s) 103a, 104a to communicate the sink change, in which case the previous device(s) 103a, 104a may update their ND proxy caches by removing non-existing associations. Alternatively, node device 108a may send a packet communication RE notifying the sink change to new sink device 104b, the border router 103b, or both devices 103b, 104b, notifying the previous device(s) 103a, 104a of the sink change.

[0050] In step 220, node device 108a is associated with intermediate node device 108b, which acts as a mesh router between node device 108a and sink device 104b, depending on the illustration. Node device 108a is then part of the routing topology of sink device 104b, which of course means that an uplink packet communication UL sent by node device 108a to sink device 104b will be routed via at least one intermediate node device 108b, e.g., one, two, three, four, or more intermediate node devices 108b, if the destination of the packet communication UL is outside network 102. The packet communication UL will be further routed via sink device 104b if the destination of the packet communication UL is outside network 102. If the source of the downlink packet communication DL is outside the network 102, e.g., an external device 107, an Internet router 105, a border router 103, or a sink device 104b, the source sends the downlink packet communication DL to the node device 108a, and the packet communication DL is routed via the sink device 104b if the source is outside the network 102. The packet communication DL may be further routed to the node device 108a via at least one intermediate node device 108, e.g., one, two, three, four, or more intermediate node devices 108, or may communicate directly with the node device 108a, e.g., if an association change occurs.

[0051] Since node device 108a still has the same network address NA, when node device 108a now associates with the intermediate node device 108, its controller 430 and communication unit 436 obtain the network address of the new (current) sink device 104a from the known association mechanism.

[0052] In step 222, the node device 108a, by its controller 430, regenerates (generates) its new Internet address IA as routing is now performed between the node device 108a and the new sink device 104b instead of the previous sink device 104a. The node device 108a regenerates the new Internet address IA from the sink identifier ID and from the network address NA for the new sink device 104b by at least partially processing the sink identifier ID and network address NA correspondingly as described above in step 214, e.g., by using at least one of concatenation, hashing, and other processing of the sink identifier ID and network address NA. The sink identifier ID also includes the network address of the sink device 104b, e.g., the 32-bit DECT-2020 NR RD-ID identifier, the generated random value RA, or any identifier that allows for identifying the sink device 104b. Alternatively, the sink identifier ID may include any identifier, for example, the identifier of the border router 103b to which the sink device 104b is connected, that enables the system 100 to communicate data from the external network(s) 106 through the sink device 104b to the node device 108a.

[0053] The node device 108a includes the processed sink identifier ID and the network address NA in the IID field of the address format AF. Thus, the generated new internet address IA consists of the subnet prefix PR in the subnet prefix field and the processed sink identifier ID and the network address NA in the IID field to ensure the accessibility of the node device 108a from outside the network 102.

[0054] In step 224, node device 108a communicates with sink device 104b via controller 430 and communication unit 436 by sending an uplink packet communication UL to inform at least one of sink device 104b, border router 103b to which sink device 104b is connected, and external device 107, e.g., sink device 104b only, border router 103b only, sink device 104b and border router 103b, sink device 104b and external device 107 if relevant, border router 103b and external device 107 if relevant, or all of devices 103b, 104b, 107 if relevant, of its new Internet address IA. After receiving the packet communication UL, its receiver(s), including at least one of border router 103b and sink device 104b, are configured to update their ND proxy caches with node device 108a's current address IA.

[0055] The IP communication UL includes the address of the node device 108a as the source, the address of the receiver 103b, 104b, 107, e.g., the address of the border router 103b, the sink device 104b, or the external device 107, and within the payload of the packet communication UL, a unique identifier UID that enables the external device 107 to send the downlink packet communication DL to the correct node device 108a from outside the network 102. Furthermore, the payload of the packet communication UL may include a previous Internet address IA that includes a sink identifier ID of the previous sink device 104a. Additionally or alternatively, with regard to the previous identifier option, the payload of the packet communication UL may include its new Internet address IA. In addition to the previous option, the payload of the packet communication UL may also include other information, e.g., application-related data.

[0056] The node device 108a sends the information packet communication UL after generating a new internet address IA or, for example, when it needs to send the next application-related data.

[0057] In step 226, if the node device 108a changes the routing of its packet communications UL, DL again such that the sink device 104b is changed to another sink device 104, the method returns to step 220 so that the next internet address IA of the node device 108a is regenerated.

[0058] Similar to step 218, after node device 108a decides to make a further sink change, it does not notify the previous sink 104b of the upcoming sink change. Alternatively, if node device 108a decides to make a further sink change between sink devices 104b, 104b, it may notify the previous sink device 104b, the border router 103b, or both devices 103b, 104b of the sink change by sending an uplink packet communication RE to the previous device(s) 103b, 104b communicating the sink change, in which case the previous device(s) 103b, 104b may update their ND proxy caches by removing non-existing associations. Alternatively, node device 108a may send a packet communication RE notifying the sink change to the new sink device 104, the border router 103, or both devices 103b, 104, notifying the previous device(s) 103b, 104b of the sink change.

[0059] FIG. 4 illustrates a node device 108 configured to communicate with the sink and other node devices 104, 108 in the network 102 and to perform the relevant features (steps) of the address generation method 210 described above.

[0060] The node device 108 includes a controller 430 configured to control the operation of its portions 432, 434, 436, 438, 440 such that the node device 108 operates as described above.

[0061] The controller 430 includes a processor 432 configured to execute at least one of operator-initiated instructions and computer program-initiated instructions and to process data to execute the necessary applications. The processor 432 may include at least one processor, for example, one, two, three, four, or more processors 432.

[0062] The controller 430 also includes a memory 434 configured to store and maintain data, which may be instructions, computer programs, and data files. The memory 434 may include at least one memory, such as one, two, three, four, or more memories 434.

[0063] The node device 108 also includes a communication unit 436 and an antenna 438 that the controller 430 configures to use to send commands, requests, and data to at least one of the entities in the system 100, e.g., the devices 104, 108, via the antenna 438. The controller 430 is also configured to use the communication unit 436 to receive commands, requests, and data from at least one of the entities in the system 100, e.g., the devices 104, 108, via the antenna 438. Communication between the communication unit 436 and the other entities 104, 108 in the system 100 occurs wirelessly via the antenna 438.

[0064] The node device 108 also includes a power supply 440. The power supply 440 includes components configured to provide power to the node device 108, such as a battery and a regulator.

[0065] The memory 434 is configured to store at least a communication application 442 for operating (controlling) the communication device 436 and a power supply application 444 for operating the power supply device 440. The memory 434 is also configured to store a computer program (computer software, computer application) 446 that, when implemented (runs, performs, operates) by the controller 430 in a computer, for example, in the node device 108, is configured to use at least one of the portions 436, 438, 440 to perform at least the operations of the node device 108 described above in the context of the previous figures.

[0066] The computer program 446 may be stored on a tangible, non-volatile computer readable storage medium, for example a compact disc (CD) or universal serial bus (USB) type storage device.

[0067] Address generation has been described above with reference to the aforementioned exemplary embodiments, and some of its advantages have been demonstrated. It is clear that address generation is not limited to only these embodiments, but includes all possible embodiments within the scope of the following claims.

Claims

1. An address generation system (100) for a wireless communication network (102), comprising: At least one sink device (104, 104a, 104b); At least one wireless node device (108, 108a, 108b); each wireless node device (108, 108a, 108b) is configured to communicate with the at least one sink device or another wireless node device (108) belonging to the at least one wireless node device; and wherein each wireless node device is further configured to generate an internet address (IA) for the wireless node device, the internet address (IA) including a sink identifier (ID) of a sink device (104, 104a, 104b) belonging to the at least one sink device and a wireless communication network address (NA) of the wireless node device, thereby making the wireless node device accessible via the sink device.

2. The generation system of claim 1 , wherein the sink identifier comprises a network address of the sink device or a random value configured to identify the sink device.

3. 3. The generation system of claim 1, wherein the wireless node device is further configured to include the sink identifier and the network address of the wireless node device in an Interface Identifier (IID) field in an Internet Address Format (AF).

4. 4. The generating system of claim 3, wherein the internet address format further comprises an internet subnet prefix (PR) in an internet subnet prefix field.

5. 5. The generation system of claim 1, wherein the wireless node device is further configured to regenerate the internet address when the wireless node device changes routing from a previous sink device (104, 104a) belonging to the at least one sink device to the sink device in the wireless communication network.

6. The generation system of any one of claims 1 to 5, wherein the wireless node device is further configured to include the generated internet address in uplink packet communications (UL).

7. 7. The generation system of claim 6, wherein the wireless node device is further configured to include a unique identifier (UID) of the wireless node device in the uplink packet communication.

8. 8. The generation system of claim 7, wherein the wireless node device is further configured to include in the uplink packet communication at least a previous internet address (IA) of the wireless node device, the previous internet address including a sink identifier (ID) of a previous sink device (103, 103a) belonging to the at least one sink device.

9. The generation system of any one of claims 1 to 8, wherein the wireless node device is further configured to send an uplink packet communication (UL) including the generated internet address to at least the sink device.

10. The generation system according to any one of claims 6 to 9, wherein the wireless node device is further configured to transmit the uplink packet communication after the generation of the internet address or when a need arises to send a next data communication.

11. 11. The generation system of any one of claims 1 to 10, further comprising at least one Internet router device (103, 103a, 103b) including at least one sink device, said at least one Internet router device configured to operate as a wireless communication network entry between said at least one external communication network and said wireless communication network.

12. 12. The generation system of any one of claims 1 to 11, wherein the wireless communication network is a Digital European Cordless Telecommunications 2020 based network, a wireless multi-hop network, a wireless mesh network, a wireless local area network, a cellular based local area network, a low power wide area network, a cellular network, a wireless Bluetooth Low Energy based radio network, a ZigBee network, a Thread network, or a public land mobile network.

13. An address generation method (210) for a wireless communication network (102), comprising at least: communicating, by a wireless node device (108, 108a, 108b), with a sink device (104, 104a, 104b) or with another wireless node device (108) belonging to the wireless communication network; generating, by the wireless node device (108, 108a), an internet address (IA) for the wireless node device, the internet address including a sink identifier (ID) of the sink device (104, 104a, 104b) and a wireless communication network address (NA) of the wireless node device, whereby the wireless node device is accessible via the sink device.

14. A wireless node device (108, 108a, 108b) for address generation in a wireless communication network (102), comprising: a controller (430); a wireless communication device (436); the controller and the wireless communication device are configured to perform wireless communication with at least one sink device (104, 104a, 104b) or other wireless node devices (108, 108a, 108b) belonging to the wireless communication network; The controller is further configured to generate an Internet Address (IA) including a sink identifier (ID) of a sink device (104, 104a, 104b) belonging to the at least one sink device and a wireless communication network address (NA) of the wireless node device, thereby making the wireless node device accessible via the sink device.

15. An address generation method (210) for a wireless communication network (102), comprising at least: communicating, by a wireless node device (108, 108a, 108b), with a sink device (104, 104a, 104b) or with another wireless node device (108) belonging to the wireless communication network; generating, by the wireless node device (108, 108a), an internet address (IA) for the wireless node device, the internet address including a sink identifier (ID) of the sink device (104, 104a, 104b) and a wireless communication network address (NA) of the wireless node device, whereby the wireless node device is accessible via the sink device.

16. A computer program (446) including instructions:

16. A computer program (446) comprising instructions that, when executed by a processor (432), cause the wireless node device (108, 108a, 108b) to perform at least the steps of the method of claim 15.

17. 17. A tangible, non-volatile computer readable medium containing the computer program (446) of claim 16.

Images