Addressing system for wireless communication networks

Abstract

The present application relates to an addressing system (100) for a wireless communication network (102). The system includes a first communication device (104a) and a second communication device (104b). The first and second communication devices (104a, 104b) belong to a group of a plurality of communication devices (104, 104a, 104b) of the network. Each communication device (104, 104a, 104b) is configured to provide bidirectional wireless communication with at least one of the plurality of communication devices. Each communication device performs a step (322) of addressing the communication device (104, 104a, 104b) and generating a long node identifier (L-ID) used for at least one security procedure of communications in the network. Each communication device is configured to perform a step (328) of generating a short node identifier (S-ID) that identifies the communication device in dedicated communications between itself and other communication devices (104, 104a, 104b) belonging to the plurality of communication devices. Each communication device is configured to perform steps (330, 338, 342, 344) of including at least a generated short node identifier of the communication device as a transmitter address in a control portion (214) of the communication packet (208) to inform its receiver of the transmitter of the communication packet, and including at least a long node identifier of the communication device in another portion (216) of the communication packet to ensure security of communications between the communication devices.

Description

[Technical Field]

[0001] TECHNICAL FIELD This application relates generally to addressing systems for wireless communication networks. [Background technology]

[0002] Node identity (ID) is used to identify the sender of data and the receiver of data in any wireless technology that requires node identity to be frequently signaled in packet transmissions. The node ID set as the receiver ID of a data packet is used to separate transmissions at the receiver from each other, i.e., the receiver only acts on messages intended for that receiver. The node ID set as the transmitter ID of a data packet is used to identify the transmitter so that the receiver can perform the correct action for the transmitter.

[0003] In wireless communication systems where different devices can independently access the channel and transmit packets, such as Bluetooth Low Energy (BLE)® networks and wireless local area networks (WLANs) such as Wi-Fi® networks, each packet transmission must include both a receiver ID and a transmitter ID.

[0004] The node ID must be long, i.e., number of bits, sufficient to provide at least local uniqueness of the sender and receiver, and is transmitted in every packet transmission. It may be, for example, 32 bits or 48 bits, where 48 bits is already 2 48 It is possible to provide global uniqueness with addresses.

[0005] The BLE system uses 48-bit receiver and transmitter IDs (addresses) in the Medium Access Control (MAC) header of a packet after the physical layer (PHY) header of the packet. In a WLAN (Wi-Fi) system, as an example, each packet includes a Basic Service Set (BSS) ID and 48-bit transmitter and receiver IDs in its MAC header. This results in a very strictly enforced packet resolution, where each transmission in a WLAN system includes a 48-bit BSS ID, a 48-bit receiver MAC address, and a 48-bit transmitter MAC address.

[0006] Such bit sequences of receiver ID and transmitter ID in each packet transmission are a significant amount of overhead, especially when the data transmission is sufficiently small, which may occur in the case of Internet of Things (IoT) operations. For example, if the amount of data transmitted as one data burst by an IoT device is 32 bytes, and the receiver ID and transmitter ID in each packet transmission are both 32 to 48 bits, the overhead will be 25% to 37.5% due to these IDs. Summary of the Invention

[0007] One object of the present invention is to overcome the drawbacks of known solutions and to provide an addressing system for wireless communication networks, in which communication devices assign short node identifiers using a distributed scheme and minimal signaling, avoiding centralized assignment and coordination, while still supporting Hybrid Automatic Repeat Request (HARQ) operation.

[0008] One object of the present invention is achieved by providing an addressing system, a communication device, a method, a computer program and a computer readable medium according to the independent claims.

[0009] Embodiments of the invention are disclosed in the independent claims.

[0010] One embodiment of the present invention is an addressing system for a wireless communication network. The system includes a first communication device and a second communication device. The first and second communication devices belong to a group of a plurality of communication devices in the network. Each communication device is configured to provide bidirectional wireless communication with at least one of the plurality of communication devices. Each communication device has a long node identifier that addresses the communication device and is used for at least one security procedure for communications in the network. Each communication device is configured to generate a short node identifier that identifies the communication device in dedicated communications between itself and other communication devices in the plurality of communication devices. Each communication device is configured to include at least the short node identifier generated by the communication device as a transmitter address in a control portion of a communication packet to inform a receiver of the transmitter of the communication packet, and to include at least the long node identifier in another portion of the communication packet to ensure security of communications between the communication devices.

[0011] One embodiment of the present invention is a method for addressing a wireless communication network, the method comprising the steps of indicating at least first and second communication devices belonging to a group of a plurality of communication devices in the network, the method further comprising the step of indicating, by each communication device, a long node identifier for addressing the communication devices and for using the long node identifier in at least one security procedure for communications in the network, the step of generating, by each communication device, a short node identifier for identifying the communication device in dedicated communications between the communication device and other communication devices belonging to the plurality of communication devices, the step of including, by each communication device, at least the short node identifier generated by the communication device as a transmitter address in a control portion of the communication packet to inform a receiver of the transmitter of the communication packet, and including at least the long node identifier of the communication device in another portion of the communication packet to ensure security of bidirectional wireless communications between the communication devices.

[0012] One embodiment of the present invention is a wireless communication device for a wireless communication network. The device includes a controller unit and a data transfer unit. The data transfer unit is configured to provide bidirectional wireless communication with at least one other wireless communication device. The controller unit is configured to address the communication device and indicate a long node identifier used for at least one security procedure for communications in the wireless communication network. The controller unit is configured to generate a short node identifier that identifies the communication device in dedicated communications between the communication device and other communication devices in the network. The controller unit is configured to include at least the short node identifier generated by the communication device as a transmitter address in a control portion of the communication packet to inform a receiver of the transmitter of the communication packet, and to include at least the long node identifier of the communication device in another portion of the communication packet to ensure communication security.

[0013] One embodiment of the present invention is a method for addressing a wireless communication device. The method includes providing, by a data transfer unit of the communication device, bidirectional wireless communication with at least one other wireless communication device. The method further includes indicating, by a controller unit of the communication device, a long node identifier for addressing the communication device and for using the long node identifier in at least one security procedure for communications in a wireless communication network. The method further includes generating, by the controller unit, a short node identifier for identifying the communication device in dedicated communications between the communication device and other communication devices in the network. The method further includes including, by the controller unit, at least the short node identifier generated by the communication device as a transmitter address in a control portion of the communication packet to inform a receiver of the transmitter of the communication packet, and including at least the long node identifier of the communication device in another portion of the communication packet to ensure communication security.

[0014] An embodiment of the present invention is a computer program comprising instructions that, when executed by a computer according to the apparatus embodiments described above, cause said computer to perform at least the steps of the method embodiments described above.

[0015] One embodiment of the present invention is a tangible, non-volatile computer readable storage medium containing a computer program according to the computer program embodiment described above.

[0016] Further embodiments of the invention are disclosed in the dependent claims.

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

[0018] [Figure 1] 1 illustrates a wireless communication environment for an addressing system. [Figure 2a] 1 illustrates an exemplary format of a packet. [Figure 2b] 1 shows an example of a MAC PDU structure. [Figure 3] 1 shows a flowchart of an addressing method. [Figure 4] 1 shows the components of a wireless communication device. DETAILED DESCRIPTION OF THE INVENTION

[0019] FIG. 1 illustrates an environment in which an addressing system 100 may be applied.

[0020] The environment includes a wireless communication network (system) 102 that includes multiple wireless communication devices (nodes) 104, 104a, 104b. The devices 104, 104a, 104b, for example, operate in the same spectrum in the same geographic region within the exemplary environment. Use of the same spectrum enables bidirectional communication between the devices 104, 104a, 104b, i.e., a wireless transmission transmitted by one device 104, 104a, 104b of the network 102 can be received by another device 104, 104a, 104b of the network 102, and vice versa.

[0021] The system 100 may be applied to any wireless communication network 102 that uses frequent signaling of node identifiers (identities, IDs) in packet transmissions. Preferably, the system 100 may be applied to a wireless communication network 102 that complies with the DECT (Digital European Cordless Telephone)-2020 standard. Some non-limiting examples to which the system 100 may be applied include, but are not limited to, wireless mesh networks and / or other wireless networks, such as a BLE mesh network, a Thread network, a Zigbee network, a public land mobile network (PLMN), a WLAN network, a cellular network, or a wireless sensor network.

[0022] Typically, devices 104, 104a, 104b of network 102 can receive transmissions using one wireless technology, e.g., BLE transmissions or WLAN transmissions, all from the same network 102. However, at least one of devices 104, 104a, 104b of network 102 can receive transmissions using at least two wireless technologies, e.g., BLE transmissions and WLAN transmissions, all from the same network 102.

[0023] DECT-2020 is a radio access technology developed by ETSI. DECT-2020 supports massive machine-type communications (mMTC) and ultra-reliable low-latency communications (URLLC). At the physical (PHY) layer, the key technical components of DECT-2020 are orthogonal frequency-division multiplexing (OFDM), adaptive modulation and coding (MCS), modern channel coding methods (Turbo, LDPC, and convolutional coding), HARQ for both scheduled and contention-based transmissions, and support for multi-antenna transmission with different multiple-input multiple-output (MIMO) streams. At the medium access (MAC) layer, according to system aspects, the key technical components of DECT-2020 are support for a large number of IoT sensors, actuators, and other industrial applications, support for mesh network topologies, support for URLLC communications with very low latency (a typical application might be wireless microphones), operation in license-exempt frequencies, and support for multiple overlapping uncoordinated networks with cognitive radio capabilities for sharing spectrum resources among multiple networks.

[0024] 2a shows an exemplary format of a packet 208 used in the system 100. The system 100 is not limited to this packet format and may, of course, use any other format.

[0025] Packet 208 may be, but is not limited to, a PHY layer packet 208 as shown.

[0026] The format of the packet 208 includes a Synchronization Training Field Symbol (STFS) field 210, a Channel Training Field (CTF) 212, a PHY header field, i.e., a PHY control field (portion) 214, and a Data field 216. The STFS field 210 is used to provide time and frequency synchronization to the receiving device 104, 104a, 104b and may also be used for other purposes, such as adjusting the gain of the receiving device 104, 104a, 104b. The CTF field 212 is used for channel estimation purposes in the receiving device 104, 104a, 104b. The header field 214 is used to transmit necessary information about how the Data field 216 will be transmitted. The header field 214 includes, but is not limited to, information used for the modulation and coding scheme (MCS), the network address (identity, identifier, ID), the receiver address (identity, identifier, ID), the transmitter address (identity, identifier, ID), the transmit power used to transmit the packet 208, the HARQ process number, a new data indicator, a redundancy version for the packet 208, and / or HARQ feedback information. The data field 216 includes at least one MAC protocol data unit (PDU) and is the field that is retransmitted in a HARQ operation.

[0027] The header field 214 includes identification information representing (identifying) the sender (transmitting device) 104, 104a, 104b, i.e., a transmitter identifier. Alternatively or additionally, the header field 214 may further include identification information representing (identifying) the receiver (receiving device) 104, 104a, 104b, i.e., a receiver identifier. The header field 214 may be protected by a cyclic redundancy check (CRC) so that the receiving device 104, 104a, 104b can be assured that it has received the header field 214 correctly. The length of the CRC in the header field 214 may be, for example, 8 or 16 bits.

[0028] The length of the header field 214 may be between 26 and 120 bits, although other lengths of the header field 214 are possible. Preferably, the length of the header field 214 may be between approximately 50 and 80 bits, and may be determined by the format of the packet 208. Alternatively or additionally, the length of the header field 214 may be determined by whether a CTF field may be used to transfer control channel bits. While the length of the header field 214 has been described above, the same applies to the header field 214 of the packet 208 if the packet 208 is a packet of any other layer.

[0029] Figure 2b shows an example of a MAC PDU structure 218 that may be used in the system 100. The system 100 is not limited to this structure and may use any structure.

[0030] The MAC PDU structure 218 includes a MAC header field and at least a portion of the MAC PDU data.

[0031] The MAC header field is used to convey the necessary parameters of MAC-level security (if used) as well as indicate the contents of the MAC PDU data to the receiving device 104, 104a, 104b. MAC-level security is expected to encrypt all other fields in the MAC PDU except the MAC header field, and integrity protection is provided by a Message Integrity Code (MIC) from the complete MAC PDU and appended to the end of the MAC PDU.

[0032] FIG. 3 illustrates how an addressing method 320 is used in the transmission of the packets 208 described above, and how the devices 104, 104a, 104b operate in the systems and networks 100, 102 described above.

[0033] The method 320 is primarily described using two devices 104a, 104b, namely a first device 104a and a second device 104b, both of which belong to the same network 102, which may also include multiple other devices 104.

[0034] In step 322, each device 104, 104a, 104b of the network 102 indicates, by its controller unit 424, a long node identifier (long ID, long address) L-ID, which may be, for example, an identifier having a length of 32 to 48 bits, such as a 48-bit Ethernet MAC address used in Wi-Fi networks. The indicated L-ID is globally unique, or at least unique within the network 102 in which the device 104, 104a, 104b operates or prefers to operate.

[0035] As described above, each device 104, 104a, 104b can provide bidirectional wireless communication with at least one other device 104, 104a, 104b in the network 102 via its data transfer unit 426, i.e., can transmit at least one data packet 208 to the other device 104, 104a, 104b and receive at least one data packet 208 from the other device 104, 104a, 104b. In other words, each device 104, 104a, 104b can function as a transmitter and / or a receiver.

[0036] In the method 320, at the start, the device 104a functions as a transmitter and the device 104b functions as a receiver, and these roles change between the devices 104a, 104b during communication with each other. Preferably, the transmitter and receiver devices 104, 104a, 104b may be identical to each other, although the invention is not limited thereto.

[0037] The L-ID of each of the illustrated devices 104, 104a, 104b is used to identify (address) the device 104, 104a, 104b from other devices 104, 104a, 104b operating in the network 102 and is also used for at least one security procedure, for example, encryption and / or integrity protection of data communicated in the network 102.

[0038] In step 328, when each device 104, 104a, 104b attempts to associate with another device 104, 104a, 104b in the network 102 to communicate with the other devices 104, 104a, 104b, or to associate with the network 102 to join the network 102, the controller 424 of each device generates (assigns) a random short node identifier (S-ID), which may be, for example, an identifier having a length of 8 to 32 bits. The S-ID is generated to be shorter than the L-ID, meaning that it contains fewer bits than the L-ID. The S-ID may be, for example, 8, 16, 24, or 32 bits long, but is preferably 16 or 24 bits long in DECT-2020.

[0039] The S-ID generated by each of 104, 104a, 104b identifies and distinguishes the device 104, 104a, 104b from other devices 104, 104a, 104b in a dedicated communication (association), e.g., unique packet transmission, between the two devices 104, 104a, 104b in the network 102.

[0040] Each device 104, 104a, 104b has its L-ID, and when one of the devices 104, 104a, 104b (in this example, device 104a) initiates an association with at least one other device 104, 104b in the network 102 and attempts to communicate with at least one other device 104, 104b, device 104a generates a random S-ID for itself.

[0041] In step 330, device 104a determines a beacon packet 208. Device 104a, via its controller unit 424, includes the generated S-ID as a transmitter address in a control portion (field) 214 of the beacon packet 208 to be broadcast, e.g., a PHY control field, and includes device 104a's L-ID as plain text in another portion (field) of the beacon packet 208, e.g., a data field 216, to secure the packet 208. The beacon packet 208 is broadcast to all devices 104, 104b in the network 102 or to a specific group of devices 104, 104b, where the S-ID is indicated in the control portion 214 (as a "receiver address"). The remainder of the packet 208 is either encrypted, integrity protected, or transmitted as plain text. Device 104a then begins broadcasting, via its data forwarding portion 426, the generated beacon packet 208 that includes both the S-ID and L-ID as an attempt to associate with other devices 104, 104b.

[0042] Using an S-ID having a length of 8 to 32 bits reduces the transmission overhead in the control portion 214 of the packet 208. In particular, in packets 208 that use substantially short slots, the overhead in the control portion 214 can be minimized to efficiently use the short slots for application layer data. For example, DECT-2020 supports a 1.728 MHz channel bandwidth with a subcarrier spacing of 27 kHz, where the slot length is only 10 ms / 24 = 0.41666 ms, i.e., the packet (frame) time is 10 ms, the packet is divided into 24 time slots.

[0043] When the device 104a broadcasts its beacon packet 208, the device 104a can simultaneously detect the environment by the data transfer unit 426 of the device 104a in order to listen to the wireless communications of the other devices 104, 104b and receive the beacon packet 208 from the other devices 104, 104b operating similarly to the devices 104, 104a. During these operations, the device 104a detects the S-ID included in the control portion 214 of the detected communication packet 208 by the controller unit 424 of the device 104a, and records (stores) the detected S-ID in the memory unit 432 of the device 104a by the controller unit 424 of the device 104a.

[0044] Each of the other devices 104, 104b operates in a similar manner, i.e., they listen to the wireless communications of the other devices 104, 104a in the network 102 and check, via the controller section 424, whether any of the detected S-IDs of the other devices 104, 104a are similar to the S-IDs of the other devices 104, 104b themselves.

[0045] In step 334, when one of the other devices 104, 104b (in this example, device 104b) receives the broadcasted beacon packet 208 from device 104a, its data forwarding section 426 detects the S-ID of device 104a from the control section 214 of the received beacon packet 208, and the controller section 424 of device 104b checks whether the included S-ID of device 104a is similar to device 104b's own S-ID or any other recorded S-ID already known to device 104b.

[0046] In step 336, if such a match exists, i.e., if device 104b detects that the received S-ID of device 104a is similar to the S-ID of device 104b, device 104b regenerates (reassigns) a new S-ID for itself, similar to that described in step 328, and returns to listening to its environment.

[0047] In step 338, if no such match exists, device 104b, which has already detected device 104a's L-ID from the data portion 216 of the beacon packet 208 and wishes to associate with device 104a, determines an association request packet 208 via its controller unit 424. Device 104b includes its S-ID as the sender address and device 104a's S-ID as the receiver address in the control portion 214 of the association request packet 208. Device 104b also includes at least its L-ID as plaintext in another portion, e.g., the data portion 216 of the association request packet 208. The remainder of the packet 208 is encrypted and integrity protected. Device 104b may also include device 104a's L-ID in the data portion 216. After determining the association request packet 208, device 104b transmits (unicasts) the association request packet 208 to device 104a via its data forwarding unit 426.

[0048] In step 340, when device 104a receives an association request packet 208 from device 104b via its data transfer section 426, it detects the S-ID of device 104b from the control section 214 of the received association request packet 208 via its controller section 424, and checks whether the included S-ID of device 104b is similar to device 104a's own S-ID or any other recorded S-ID already known to device 104a.

[0049] In step 342, if such a match exists, i.e., if device 104a detects that the received S-ID of device 104b is similar to the S-ID of device 104a or some other recorded S-ID, device 104a determines, via its controller portion 424, a No Association (NACK) response packet 208. Device 104a includes its S-ID as the sender address and the S-ID of device 104b as the receiver address in the control portion 214 of the NACK response packet 208, and then transmits the NACK response packet 208 to device 104b via its data forwarding portion 426.

[0050] In step 343, after receiving the NACK response packet 208, device 104b regenerates a new S-ID for itself, as described in steps 328 and 336, and then returns to determine and retransmit a new association request packet 208 with device 104b's new S-ID, as described in step 338.

[0051] In step 344, if no such match exists, device 104a, which has already detected device 104b's L-ID from the data portion 216 of the association request packet 208 and wishes to associate with device 104b, determines an association acknowledgement (ACK) response packet 208 via its controller portion 424. Device 104a includes its S-ID as the transmitter address and device 104b's S-ID as the receiver address in the control portion 214 of the ACK response packet 208, and then transmits the ACK response packet 208 to device 104b via its data forwarding portion 426 to complete the association. Device 104a may also include at least one of device 104a, 104b's L-IDs in another portion of the ACK response packet 208, e.g., the data portion 216.

[0052] The aforementioned association signaling between devices 104a, 104b is used to exchange the relationship between L-ID and S-ID, whereby the S-ID is used to enable HARQ operations at the link layer and the L-ID is used to enable encryption and integrity protection.

[0053] In step 346, after completing the association and before device 104a receives the data packet 208 from device 104b, device 104b includes its S-ID as the sender address and device 104a's S-ID as the receiver address in the control portion 214 of the data packet 208. The security procedure for the data packet 208 is performed by using the L-ID of device 104b or the L-IDs of both devices 104a and 104b. Device 104b performs the security procedure by using the L-ID of device 104b in the encryption mask and integrity protection calculation (MIC calculation), which may not include the L-ID of device 104b or device 104a.

[0054] When device 104a receives data packet 208, it uses the S-ID of device 104b obtained from the control portion 214 of data packet 208 to obtain the correct L-ID for device 104b, and performs decryption and integrity protection checks using the L-ID of device 104b or the L-IDs of both devices 104a and 104b. Device 104b obtains the correct S-ID and L-ID relationship information in association completion step 344, as described above.

[0055] The roles of the devices 104a, 104b may of course be reversed.

[0056] Without the correct S-ID and L-ID relationship information, integrity protection fails and data packet 208 is discarded. Therefore, transmission of the L-ID over the air interface is avoided. Even if another communication pair of device 104 uses the same S-ID as device 104a and 104b, and 104b receives such a data packet, the data will not be erroneously forwarded to upper layers.

[0057] Communication between devices 104a, 104b exists via packet transmissions unless the association is terminated, which may be performed by a termination packet 208 that terminates the association, or may occur when communication between devices 104a, 104b is interrupted for any reason, such as a lack of communication within a predetermined period of time.

[0058] The generation of the S-ID provides the system 100 in which each device 104, 104a, 104b has two independent identifiers, where the L-ID provides network-wide uniqueness and the S-ID provides local link-level uniqueness in each device's wireless neighborhood. The L-ID is used as the basis for link-layer security procedures, such as encryption and integrity protection, and is used in mesh network operation for packet routing.

[0059] FIG. 4 illustrates devices 104, 104a, 104b communicating in the network 102 and capable of implementing the addressing method 320.

[0060] The device 104, 104a, 104b includes a controller portion 424 that controls the operation of its respective portions 426, 432, 448, 450, 452 so that the device 104, 104a, 104b operates as described in the context of the previous figures.

[0061] Controller portion 424 includes a processor portion 448 that executes operator-initiated and / or computer program-initiated instructions and processes data to run applications. Processor portion 448 may include at least one processor, for example, one, two, three, or more processors.

[0062] The controller unit 424 also includes a memory unit 432 for storing and maintaining data, which may be instructions, computer programs, and data files. The memory unit 432 may include at least one memory, such as one, two, three, or more memories.

[0063] The devices 104, 104a, 104b also include a data transfer unit 426 and an antenna unit 450 that are used by the controller unit 424 to transmit commands, requests, and data to at least one of the entities in the system 100, e.g., the devices 104, 104a, 104b, via the antenna unit 450. The data transfer unit 426 also receives commands, requests, and data from at least one of the entities in the system 100, e.g., the devices 104, 104a, 104b, via the antenna unit 450. Communication between the data transfer unit 426 of the devices 104, 104a, 104b and other entities in the system 100 is provided wirelessly via the antenna unit 450.

[0064] The device 104, 104a, 104b also includes a power supply 452. The power supply 452 includes components, such as a battery and a regulator, for providing power to the device 104, 104a, 104b.

[0065] The memory unit 432 stores at least a data transfer application 454 that operates (controls) the data transfer unit 426, an antenna application 456 that operates the antenna unit 450, and a power supply application 458 that operates the power supply unit 452.

[0066] The memory portion 432 also stores a computer program 460 (software, application) that, when executed by the controller portion 424 in a computer, e.g., device 104, 104a, 104b, uses at least one of the portions 426, 448, 450, 452 to perform at least the operations of device 104, 104a, 104b previously described in this description and in the figures.

[0067] The computer program 460 may be stored on a tangible, non-volatile computer readable storage medium, such as a compact disc (CD) or universal serial bus (USB) type storage device.

[0068] The present invention has been described above with reference to the exemplary embodiments mentioned above, and some of its advantages have been explained. It is clear that the present invention is not limited to these embodiments, but also includes all possible embodiments within the scope of the claims.

Claims

1. An addressing system (100) for a wireless communication network (102), comprising: a first communication device (104a); a second communication device (104b); the first and second communication devices (104a, 104b) belong to a group of a plurality of communication devices (104, 104a, 104b) of the network, each communication device (104, 104a, 104b) configured to provide bidirectional wireless communication with at least one of the plurality of communication devices; Each communication device has a long node identifier (L-ID) (322) that addresses the communication device (104, 104a, 104b) and is used for at least one communication security procedure in the network; each communication device is configured to generate (328) a short node identifier (S-ID) that is not centrally assigned or distributed in the network to identify the communication device in dedicated communications between itself and another communication device (104, 104a, 104b) belonging to the plurality of communication devices, the short node identifier having fewer bits than the long node identifier; Each communication device is further configured (330, 338, 342, 344) to include at least its generated short node identifier as a transmitter address in a control portion (214) of the communication packet (208) to inform the receiver of the transmitter of the communication packet, and to include at least its long node identifier in another portion (216) of the communication packet to ensure the security of those communications.

2. 2. The system of claim 1, wherein the first communication device is configured to use a short node identifier of the first communication device as a transmitter address in a control portion of the first packet and a long node identifier of the first communication device in another portion of the first packet when determining the first packet as a beacon to be broadcast to at least the second communication device.

3. 3. The system of claim 2, wherein the second communication device is configured to use the short node identifier of the second communication device as a transmitter address and the short node identifier of the first communication device as a receiver address in a control portion of the second packet, and the long node identifier of the second communication device in another portion sent to the first communication device as an association request.

4. 4. The system of claim 3, wherein the first communication device is configured to use the short node identifier of the first communication device as a transmitter address and the short node identifier of the second communication device as a receiver address in a control portion of the third packet, and the long node identifier of the first communication device and the long node identifier of the second communication device in another portion of the third packet when determining a third packet as an association acknowledgment to be sent to the second communication device to complete the association of the first and second communication devices.

5. 5. The system of claim 3, wherein the first communication device is configured to check a control portion of the second packet to detect (340) whether the short node identifier matches a short node identifier (S-ID) of another communication device known to the first communication device, and if such a match exists, to determine (342) a fourth packet as an association negation response to be sent to the second communication device, and to use the short node identifier of the first communication device as a transmitter address and the short node identifier of the second communication device as a receiver address in the control portion (214) of the fourth packet (208).

6. 6. The system of claim 5, wherein the second communication device is configured, upon receiving the fourth packet, to regenerate (343) a short node identifier (S-ID) of the second communication device and re-determine (338) a second packet with the regenerated short node identifier of the second communication device for retransmission as a new response to the first communication device.

7. 7. The system of claim 1, wherein after association of the first and second communication devices, the first and second communication devices are configured to address the communication packets (208) to each other by their short node identifiers (S-IDs) included as sender and receiver addresses in a control portion (214) of the communication packets (208).

8. 8. The system of claim 1, wherein each communication device is configured to check each short node identifier (S-ID) from the control portion (214) of the communication packet (208) in the network to detect (334) whether a short node identifier (S-ID) of another communication device matches the generated short node identifier, and to regenerate (336) its short node identifier (S-ID) if such a match exists.

9. The system of any one of claims 1 to 8, wherein the network is a Digital European Cordless Telephone DECT-220 based network, a wireless mesh network, a Wireless Bluetooth Low Energy (BLE) based wireless network, a Wireless Local Area Network (WLAN), a Thread network, a Zigbee network, a Public Land Mobile Network (PLMN) or a cellular network.

10. An addressing method (320) for a wireless communication network (102), comprising: indicating at least a first and a second communication device (104, 104a, 104b) belonging to a group of a plurality of communication devices (104, 104a, 104b) of said network; indicating (322) by each communication device (104, 104a, 104b) a long node identifier (L-ID) for addressing said communication device (104, 104a, 104b) and for using said long node identifier (L-ID) for at least one communication security procedure in said network; generating (328) by each communication device a short node identifier (S-ID) that is not centrally assigned or distributed in the network to identify the communication device in dedicated communications between the communication device and another communication device (104, 104a, 104b) belonging to the plurality of communication devices, the short node identifier having fewer bits than the long node identifier; and including (330, 338, 342, 344) by each communication device at least a short node identifier generated by the communication device as a transmitter address in a control portion (214) of the communication packet (208) to inform a receiver of the transmitter of the communication packet, and including (330, 338, 342, 344) at least a long node identifier of the communication device in another portion (216) of the communication packet to ensure security of their two-way wireless communication.

11. A controller unit (424); a data transfer unit (426), the data transfer unit is configured to provide bidirectional wireless communication with at least one other wireless communication device (104, 104a, 104b); the controller unit is configured to address the communication device (104, 104a, 104b) and indicate (322) a long node identifier (L-ID) used for at least one communication security procedure in the wireless communication network (102); the controller unit is configured to generate (328) a short node identifier (S-ID) that is not centrally assigned or distributed in the network to identify the communication device in dedicated communications between the communication device and another communication device (104, 104a, 104b) in the network, the short node identifier having fewer bits than the long node identifier; The controller unit is further configured to include (330, 338, 342, 344) at least a short node identifier generated by the communication device in a control portion (214) of the communication packet (208) as a transmitter address to inform a receiver of the transmitter of the communication packet, and to include (330, 338, 342, 344) at least a long node identifier of the communication device in another portion (216) of the communication packet to ensure security of the communication.

12. An addressing method (100) for a wireless communication device (104, 104a, 104b), comprising: providing, by a data transfer unit (426) of said communication device, two-way wireless communication with at least one other wireless communication device (104, 104a, 104b); indicating (322) a long node identifier (L-ID) by a controller unit (424) of said communication device for addressing said communication device and for using said long node identifier (L-ID) in at least one communication security procedure in a wireless communication network (102); generating (328) by the controller unit a short node identifier (S-ID) that is not centrally assigned or distributed in the network to identify the communication device in dedicated communications between the communication device and another communication device (104, 104a, 104b) in the network, the short node identifier having fewer bits than the long node identifier; and including (330, 338, 342, 344) by the controller unit at least the generated short node identifier as a transmitter address in a control portion (214) of the communication packet (208) to inform a receiver of the transmitter of the communication packet, and including (330, 338, 342, 344) at least the long node identifier in another portion (216) of the communication packet to ensure communication security.

13. A computer program (460) comprising instructions which, when executed by a computer, cause the computer to carry out at least the steps of the addressing method according to claim 12.

14. 14. A tangible, non-volatile computer readable storage medium containing the computer program (460) of claim 13.

Images