Method and devices for running push-button configuration sessions

• US 9,906,409 B2
• Filed: 12/12/2012
• Issued: 02/27/2018
• Est. Priority Date: 12/12/2011
• Status: Active Grant

• Current Assignee: Siemens AG
• Original Assignee: Siemens AG
• Inventors: Bahr, Michael, Falk, Rainer, Mogre, Parag
• Primary Examiner(s): BROWN, CHRISTOPHER J
• Application Number:
  US14/364,939
• Publication Number:
  US 20140337952A1
• Time in Patent Office: 1,903 Days
• Field of Search: 726 6
• CPC Class Codes: H04B 3/544 Setting up communications; Call and signalling arrangements
• CPC Class Codes: H04L 12/282 based on user interaction within the home receiver circuitry for displaying additional information being controlled by a remote control apparatus H04N21/42204
• CPC Class Codes: H04L 41/0806 for initial configuration or provisioning, e.g. plug-and-play
• CPC Class Codes: H04L 41/28 Restricting access to network management systems or functions, e.g. using authorisation function to access network configuration
• CPC Class Codes: H04L 63/065 for group communications cryptographic mechanisms or cryptographic arrangements for key management involving conference or group key H04L9/0833
• CPC Class Codes: H04L 63/083 using passwords cryptographic mechanisms or cryptographic arrangements for entity authentication using a predetermined code H04L9/3226
• CPC Class Codes: H04L 63/0876 based on the identity of the terminal or configuration, e.g. MAC address, hardware or software configuration or device fingerprint
• CPC Class Codes: H04L 63/162 at the data link layer
• CPC Class Codes: H04W 12/50 Secure pairing of devices

Abstract

A method and a network node device run Push-Button Configuration sessions within a heterogeneous network, IEEE 1905.1, using a push button configuration mechanism that ensures that only one single new network node device is registered for a single push button key press event and thus overlapping Push-Button Configuration sessions within a heterogeneous network are prevented. After finishing the push button configuration mode, the number of new nodes is checked. If more than one node has been added, a configuration roll-back is performed. Preferably, the push button configuration roll-back is performed as soon as the authentication of more than one distinct node has been detected. The roll-back includes the deletion or deactivation of credentials established by the push-button configuration.

Claims

1. A method for running Push-Button Configuration sessions within a heterogeneous network with a plurality of network node devices interconnected to each other over multiple hops via at least one interface, comprising:

sending a notification message about a first Push-Button Event from a first network node device to at least two second network node devices,

wherein the first and the at least two second network node devices are authenticated for the network,

wherein the first Push-Button-Event is assigned to the first network node device,

wherein the sending of the notification message is triggered by the first Push-Button Event, whereby the at least two second network node devices become authenticating second network node devices;

authenticating at least two third network node devices each by a second Push-Button-Event, wherein the at least two third network node devices are not yet authenticated for the network,

wherein the second Push-Button-Event is assigned to each of the third network node devices to run a Push-Button Configuration Protocol,

wherein the at least two third network node devices are authenticated for the network either with (1) the first network node device and one of the two authenticating second network node device or (2) the at least two authenticating second network node devices; and

after authenticating the at least two third network node devices, performing a Push-Button Configuration Roll-Back procedure using either (1) the first network node device and the authenticating second network node device or (2) the at least two authenticating second network node devices,

wherein the Push Button Configuration Roll Back procedure discredits credentials established when authenticating the at least two third network node devices;

running the first Push-Button Configuration Roll-Back procedure and a second Push-Button Configuration Roll-Back procedure both via at least one method selected from;

internally within the first network node device and directly with the first network node device;

indirectly via a non-authenticating second network node between the authenticating second network node device and the first network node device by handshaking messages;

both each directly with the first network node device; and

indirectly via a non-authenticating second network node device between the authenticating second network node device and the first network node device by handshaking messages.

2. The method according to claim 1, further comprising:

initiating the Push-Button Configuration Roll-Back procedure by initiating network node devices,

running the Push-Button Configuration Protocol in Push-Button Configuration Protocol runs,

transmitting a first Push-Button Configuration result message by broadcast or by relayed multicast from the initiating network node devices to all network node devices in the heterogeneous network, wherein the first Push-Button Configuration result message includes a message identifier and a message source identifier in a message header field,

comparing with each initiating network node device Push-Button Configuration result messages, to count a number of different first Push-Button Configuration result messages, wherein the comparison is based on the message identifier and message source identifier, and

if the number of different first Push-Button Configuration result messages is greater than 1, performing at least one process selected from;

(a) each of the initiating network node devices rolls back running of the Push-Button Configuration Protocol with the authenticated third network node device and deletes or deactivates the credentials established with the authenticated third network node device or

(b) each of the initiating network node devices rolls back running of the Push-Button Configuration Protocol with the authenticated third network node device, deletes or deactivates the credentials established with the authenticated third network node device and sends a Push-Button Configuration roll-back message to all other network node devices in the network in order to trigger rolling back of the Push-Button Configuration Protocol runs with the authenticated third network node device at other network node devices.

3. The method according to claim 1, further comprising:

initiating the Push-Button Configuration Roll-Back procedure by initiating network node devices,

running the Push-Button Configuration Protocol in Push-Button Configuration Protocol runs,

transmitting a first Push-Button Configuration result message by broadcast or by relayed multicast from the initiating network node devices to all network node devices in the heterogeneous network, wherein the first Push-Button Configuration result message includes a message identifier and a message source identifier in a message header field,

comparing with each network node device in the network, whether it has initiated a Push-Button Configuration Roll-Back procedure or not, Push-Button Configuration result messages, to count a number of different first Push-Button Configuration result messages, wherein the comparison is based on the message identifier and message source identifier, and

if the number of different first Push-Button Configuration result messages is greater than 1, each network node device in the network, whether it has initiated a Push-Button Configuration Roll-Back procedure or not, sends a Push-Button Configuration roll-back message to all other network node devices in the network in order to trigger rolling back of the Push-Button Configuration Protocol runs with the authenticated third network node device at other network node devices.

4. The method according to claim 1, further comprising:

initiating the Push-Button Configuration Roll-Back procedure by initiating network node devices,

running the Push-Button Configuration Protocol n Push-Button Configuration Protocol runs,

transmitting a first Push-Button Configuration result message by broadcast or by relayed multicast from the initiating network node devices to all network node devices in the heterogeneous network, wherein the first Push-Button Configuration result message includes, in a TLV-part or an information element or in header field of the message, at least one of a first identifier indicating sender or originator of the Push-Button Configuration result message, a second identifier indicating an address of the first network node device as originator of the first Push-Button-Event, and a third identifier indicating an event ID of the first Push-Button-Event;

comparing with each initiating network node devices Push-Button Configuration result messages, to count a number of different first Push-Button Configuration result messages, wherein the comparison is performed based on at least one of the first identifier, the second identifier and the third identifier, and

if the number of different first Push-Button Configuration result messages is greater than 1 performing at least one process selected from;

(a) each of the initiating network node devices rolls back running of the Push-Button Configuration Protocol with the authenticated third network node device and deletes or deactivates the credentials established with the authenticated third network node device or

(b) each of the initiating network node devices rolls back running of the Push-Button Configuration Protocol with the authenticated third network node device, deletes or deactivates the credentials established with the authenticated third network node device and sends a Push-Button Configuration roll-back message to all other network node devices in the network in order to trigger rolling back of the Push-Button Configuration Protocol runs with the authenticated third network node device at other network node devices.

5. The method according to claim 1, further comprising:

initiating the Push-Button Configuration Roll-Back procedure by initiating network node devices,

running the Push-Button Configuration Protocol in Push-Button Configuration Protocol runs,

transmitting a first Push-Button Configuration result message by broadcast or by relayed multicast from the initiating network node devices to all network node devices in the heterogeneous network, wherein a first Push-Button Configuration result message includes, in a TLV-part or an information element or a header field of the message, at least one of a first identifier indicating sender or originator of the Push-Button Configuration result message, a second identifier indicating an address of the first network node device as originator of the first Push-Button-Event, and a third identifier indicating an event ID of the first Push-Button-Event,

comparing with each network node device in the network, whether it has initiated a Push-Button Configuration Roll-Back procedure or not, Push-Button Configuration result messages, to count a number of different first Push-Button Configuration result messages, wherein the comparison is performed based on at least one of the first identifier, the second identifier, and the third identifier, and

if the number of different first Push-Button Configuration result messages is greater than 1, each network node device in the network, whether it has initiated a Push-Button Configuration Roll-Back procedure or not, sends a Push-Button Configuration roll-back message to all other network node devices in the network in order to trigger rolling back of the Push-Button Configuration Protocol runs with the authenticated third network node device at other network node devices.

6. The method according to claim 1, further comprising:

initiating the Push-Button Configuration Roll-Back procedure by initiating network node devices,

running the Push-Button Configuration Protocol in Push-Button Configuration Protocol runs,

transmitting a first Push-Button Configuration result message by broadcast or by relayed multicast from the initiating network node devices to all network node devices in the heterogeneous network, wherein a first Push-Button Configuration result message includes in a TLV-part or an information element an address or abstraction layer identifier of the third network node device,

comparing with each initiating network node devices Push-Button Configuration result messages, to count a number of different first Push-Button Configuration result messages, wherein the comparison is performed based on the address or abstraction layer identifier of the third network node devices, and

if the number of different first Push-Button Configuration result messages is greater than 1 performing at least one process selected from;

(a) each of the initiating network node devices rolls back running of the Push-Button Configuration Protocol with the authenticated third network node device and deletes or deactivates the credentials established with the authenticated third network node device or

(b) each of the initiating network node devices rolls back running of the Push-Button Configuration Protocol with the authenticated third network node device, deletes or deactivates the credentials established with the authenticated third network node device and sends a Push-Button Configuration roll-back message to all other network node devices in the network in order to trigger rolling back of the Push-Button Configuration Protocol runs with the authenticated third network node device at other network node devices.

7. The method according to claim 1, further comprising:

initiating the Push-Button Configuration Roll-Back procedure by initiating network node devices,

running the Push-Button Configuration Protocol in a Push-Button Configuration Protocol runs,

transmitting a first Push-Button Configuration result message by broadcast or by relayed multicast from the initiating network node devices to all network node devices in the heterogeneous network, wherein a first Push-Button Configuration result message includes in a TLV-part or an information element an address or abstraction layer identifier of the third network node device,

comparing with each initiating network node device-Push-Button Configuration result messages, to count a number of different first Push-Button Configuration result messages, wherein the comparison is performed based on the address or abstraction layer identifier of the third network node device, and

if the number of different first Push-Button Configuration result messages is greater than 1, each network node device in the network whether it has initiated a Push-Button Configuration Roll-Back procedure or not sends a Push-Button Configuration roll-back message to all other network node devices in the network in order to trigger rolling back of the Push-Button Configuration Protocol runs with the authenticated third network node device at other network node devices.

8. The method according to claim 1, further comprising:

initiating with an initiating second network node device the Push-Button Configuration Roll-Back procedure, wherein a non-initiating second network node device does not initiate the Push-Button Configuration Roll-Back procedure,

running the Push-Button Configuration Protocol in Push-Button Configuration Protocol runs,

sending a second Push-Button Configuration result message from each initiating second network node device directly or indirectly via at least one non-initiating second network node device to the first network node device, wherein the second Push-Button Configuration result message as one handshake message includes a message identifier and a message source identifier in a message header field, and

the first network node device;

(a) initiates itself the Push-Button Configuration Roll-Back procedure and rolls back running of the Push-Button Configuration Protocol with the authenticated third network node device, deletes or deactivates the credentials established with the authenticated third network node device and sends a Push-Button Configuration roll-back message as another handshaking message directly or indirectly via at least one non-initiating second network node device to the initiating second network node device in order to trigger rolling back of the Push-Button Configuration Protocol run with the authenticated third network node device at the initiating second network node device or respectively

(b) does not initiate itself the Push-Button Configuration Roll-Back procedure, but performs a comparison of the second Push-Button Configuration result messages received to count a number of different second Push-Button Configuration result messages, the comparison being performed based on the message identifiers and message source identifiers, and if the number of different second Push-Button Configuration result messages is greater than 1, the first network node device sends a Push-Button Configuration roll-back message as another handshaking message directly or indirectly via the at least one non-initiating second network node device to the at least two initiating second network node devices in order to trigger rolling back of the Push-Button Configuration Protocol runs with the authenticated third network node device at the at least two initiating second network node devices.

9. The method according to claim 1, further comprising:

initiating with an initiating second network node device the Push-Button Configuration Roll-Back procedure, wherein a non-initiating second network node device does not initiate the Push-Button Configuration Roll-Back procedure,

running the Push-Button Configuration Protocol in Push-Button Configuration Protocol runs,

sending a second Push-Button Configuration result message from each initiating second network node device directly or indirectly via at least one non-initiating second network node device to the first network node device, wherein the second Push-Button Configuration result message as one handshake message includes, in a TLV-part or an information element or a header field of the message, at least one of a first identifier indicating sender or originator of the Push-Button Configuration result message, a second identifier indicating an address of the first network node device as originator of the first Push-Button-Event and as receiver of the second Push-Button Configuration result message (PBR), and a third identifier indicating an event ID of the first Push-Button-Event,

comparing second Push-Button Configuration result messages, to count a number of different second Push-Button Configuration result messages, wherein the comparison is performed based on at least one of the first identifier, the second identifier and the third identifier, and

the first network node device;

(a) initiates itself the Push-Button Configuration Roll-Back procedure, if the comparison is an internal comparison in the first network node device and the comparison shows the number of different second Push-Button Configuration result messages is greater than 1, the first network node device itself rolls running of the Push-Button Configuration Protocol with the authenticated third network node device, deletes or deactivates the credentials established with the authenticated third network node device and sends a Push-Button Configuration roll-back message as another handshaking message via at least one non-initiating second network node device to the initiating second network node device in order to trigger rolling back of the Push-Button Configuration Protocol run with the authenticated third network node device at the initiating second network node device or respectively,

(b) does not itself initiate the Push-Button Configuration Roll-Back procedure, but performs the comparison on the second Push-Button Configuration result messages received and if the number of different second Push-Button Configuration result messages is greater than 1, sends a Push-Button Configuration roll-back message as another handshaking message directly or indirectly via the at least one non-initiating second network node device to the at least two initiating second network node devices in order to trigger rolling back of the Push-Button Configuration Protocol runs with the authenticated third network node device at the at least two initiating second network node devices.

10. The method according to claim 1, further comprising:

initiating with an initiating second network node device the Push-Button Configuration Roll-Back procedure, wherein a non-initiating second network node device does not initiate the Push-Button Configuration Roll-Back procedure,

running the Push-Button Configuration Protocol in Push-Button Configuration Protocol runs,

sending a second Push-Button Configuration result message from each initiating second network node device directly or indirectly via at least one non-initiating second network node device to the first network node device, wherein the second Push-Button Configuration result message as one handshake message includes in a TLV-part or an information element an address or abstraction layer identifier of the third network node devices,

comparing second Push-Button Configuration result messages received, to count a number of different second Push-Button Configuration result messages, wherein the comparison is performed based on the address or abstraction layer identifier of the third network node devices, and

the first network node device;

(a) initiates itself the Push-Button Configuration Roll-Back procedure, if, based on the address or abstraction layer identifier, the number of different third network node devices is greater than 1, the first network node device itself rolls back running of the Push-Button Configuration Protocol with the authenticated third network node device, deletes or deactivates the credentials established with the authenticated third network node device and sends a Push-Button Configuration roll-back message as another handshaking message directly or indirectly via at least one non-initiating second network node device to the initiating second network node device in order to trigger rolling back of the Push-Button Configuration Protocol run with the authenticated third network node device at the initiating second network node device or respectively

(b) does not itself initiate the Push-Button Configuration Roll-Back procedure, but performs the comparison, and if the number of different second Push-Button Configuration result messages is greater than 1, the first network node device sends a Push-Button Configuration roll-back message as another handshaking message directly or indirectly via the at least one non-initiating second network node device to the at least two initiating second network node devices in order to trigger rolling back of the Push-Button Configuration Protocol runs with the authenticated third network node device at the at least two initiating second network node devices.

11. The method according to claim 2, wherein the Push-Button Configuration roll-back message includes a message identifier and a message source identifier in a message header field, or in a TLV-part, or an information element, a first identifier indicating the address of the first network node device as the originator of the first Push-Button-Event and as the sender of the second Push-Button Configuration roll-back message, a second identifier indicating an event ID of the first Push-Button-Event, or a third identifier indicating an address or abstraction layer identifier of the at least one network node device as registrar.

12. The method according to claim 2, further comprising sending a first Push-Button status message to all network node devices in the heterogeneous network and before the first Push-Button Configuration result message in order to announce the first Push-Button Configuration result message.

13. The method according to claim 8, further comprising sending a second Push-Button status message to the first network node device and before the second Push-Button Configuration result message in order to announce the second Push-Button Configuration result message.

14. The method according to claim 2, further comprising counting, with each of the at least two network node devices initiating the Push-Button Configuration Roll-Back procedure, the number of the first Push-Button Configuration result messages only within a time period, starting from the first Push-Button-Event or the reception of the notification message.

15. The method according to claim 8, further comprising counting, with the first network node device, the number of the second Push-Button Configuration result messages only within a time period, starting from the first Push-Button-Event.

16. The method according to claim 4, wherein the first Push-Button Configuration result messages sent and received or received are different to each other if the first identifier is different and the second identifier and the third identifier are equal or the same.

17. A method for running Push-Button Configuration sessions within a heterogeneous network with a plurality of network node devices interconnected to each other over multiple hops via at least one interface, the method comprising:

sending a notification message about a first Push-Button Event from a first network node device to at least two second network node devices,

wherein the first and second network node devices are authenticated for the network,

wherein the first Push-Button-Event is assigned to the first network node device,

wherein the sending of the notification message is triggered by the first Push-Button Event, whereby the at least two second network node devices become authenticating second network node devices;

authenticating a third network node device by a second Push-Button-Event,

wherein the third network node device is not yet authenticated for the network,

wherein the second Push-Button-Event is assigned to the third network node device to run a Push-Button Configuration Protocol with the first network node device or with an authenticating second network node device; and

after finishing authentication, transmitting a third Push-Button Configuration result message from the first network node device or the authenticating second network node device,

the third Push-Button Configuration result message including at least one of;

(i) in a TLV-part or an information element or in header field of the message a first identifier indicating a sender or originator of the Push-Button Configuration result message, a second identifier indicating an address of the first network node device as originator of the first Push-Button-Event or a third identifier indicating an event ID of the first Push-Button-Event and (ii) in a TLV-part or an information element an address or abstraction layer identifier of each third network node device, the third Push-Button Configuration result message being transmitted to all network node devices in the heterogeneous network.

18. A method for running Push-Button Configuration sessions within a heterogeneous network with a plurality of network node devices interconnected to each other over multiple hops via at least one interface, the method comprising:

triggering a first network node device by a first Push-Button-Event assigned to the first network node device;

sending a notification message about a first Push-Button-Event to second network node devices, wherein the first and second network devices are previously authenticated for the network;

triggering a single third network node device by a second Push-Button-Event assigned to the third network device, wherein the single third network node device is not yet authenticated;

authenticating the single third network node device for the network by running a Push-Button Configuration Protocol with the first network node device or with an authenticating second network node device; and

after authenticating the third network node device and terminating a Push-Button Configuration session, sending a fourth Push-Button Configuration result message including in a TLV-part or an information element or in the message header field, at least one of a first identifier indicating the sender or originator of the Push-Button Configuration result message, a second identifier indicating the address of the first network node device as originator of the first Push-Button-Event and as the receiver of the fourth Push-Button Configuration result message, and a third identifier indicating an event ID of the first Push-Button-Event or in a TLV-part or an information element an address or abstraction layer identifier of the third network node devices, wherein the fourth Push-Button Configuration result message is sent from the authenticating second network node device via at least one non-authentication second network node device to the first network node device.

19. A network node device for running Push-Button Configuration sessions within a heterogeneous network with a plurality of other network node devices, interconnected to each other over multiple hops via at least one interface, wherein the first network node device is previously authenticated for the network, the device comprising:

(a) Means for performing a first Push-Button-Event,

(b) Means for sending/receiving a notification message notifying second authenticated network node devices of the first Push Button Event, wherein the second network node devices are each previously authenticated for the network,

(c) Means for running a Push-Button Configuration protocol and a means for initiating a Push-Button Configuration Roll-Back procedure, which are connected with the sending/receiving means and designed such that they;

(c1) run a Push-Button Configuration Protocol with a third network node device not yet authenticated for the network, which is triggered by a second Push-Button-Event assigned to the third network node device to authenticate the third network node device for the network,

(c2) after finishing the authentication, in response to transmission of a first Push-Button Configuration result message to all network node devices in the heterogeneous network and receiving a first Push-Button Configuration result message from at least one of the other network node devices, initiate a Push-Button Configuration Roll-Back procedure in order to delete or deactivate credentials established with the authenticated third network node device, if due to a comparison, whether the first Push-Button Configuration result messages being sent and received are different to each other, a number of the first Push-Button Configuration result messages by counting is greater than 1;

wherein the means for running a Push-Button Configuration protocol and the means for initiating a Push-Button Configuration Roll-Back procedure are connected with the sending/receiving means and within the Push-Button Configuration Roll-Back procedure the run of the Push-Button Configuration Protocol with the authenticated third network node device is rolled back and the credentials established with the authenticated third network node device are deleted or deactivated.

20. A network node device according to claim 19, wherein the means for running a Push-Button Configuration protocol and the means for initiating a Push-Button Configuration Roll-Back procedure are connected with the sending/receiving means and designed such that within the Push-Button Configuration Roll-Back procedure the run of the Push-Button Configuration Protocol with the authenticated third network node device is rolled back, the credentials established with the authenticated third network node device are deleted or deactivated and a Push-Button Configuration roll-back message to all other network node devices in the network in order to trigger rolling back of the Push-Button Configuration Protocol runs with the authenticated third network node device at other network node devices is sent.

21. A network node device according to claim 19, wherein the means for running a Push-Button Configuration protocol and the means for initiating a Push-Button Configuration Roll-Back procedure are connected with the sending/receiving means and designed such that within the Push-Button Configuration Roll-Back procedure a Push-Button Configuration roll-back message to all other network node devices in the network in order to trigger rolling back of the Push-Button Configuration Protocol runs with the authenticated third network node device at other network node devices is sent.

22. A network node device according to claim 19, wherein the means for running a Push-Button Configuration protocol and the means for initiating a Push-Button Configuration Roll-Back procedure are designed such that the comparison, whether the first Push-Button Configuration result messages being sent and received are different is based on a message identifier and a message source identifier, a first identifier indicating the sender or originator of the Push-Button Configuration result message, a second identifier indicating the address of the first network node device as the originator of the first Push-Button-Event and/or a third identifier indicating an event ID of the first Push-Button-Event each included in a TLV-part or an information element or in header field of the first Push-Button Configuration result message or an address or abstraction layer identifier of the third network node device included in a TLV-part or an information element of the first Push-Button Configuration result message.

23. A First network node device according to claim 20, wherein the Push-Button Configuration roll-back message includes a message identifier and a message source identifier in a message header field, and/or in a TLV-part or an information element a first identifier indicating the address of the first network node device as the originator of the first Push-Button-Event and as the sender of the second Push-Button Configuration roll-back message, a second identifier indicating an event ID of the first Push-Button-Event and/or a third identifier indicating an address or abstraction layer identifier of the at least one network node device as registrar.

24. A network node device according to one of the claim 19, wherein the means for running a Push-Button Configuration protocol and the means for initiating a Push-Button Configuration Roll-Back procedure are connected with the sending/receiving means and designed such that a first Push-Button status message is sent to all network node devices in the heterogeneous network with or without the third network node devices and before the first Push-Button Configuration result message in order to announce the first Push-Button Configuration result message.

25. A network node device according to claim 19, wherein the means for running a Push-Button Configuration protocol and the means for initiating a Push-Button Configuration Roll-Back procedure are designed such that they count the number of the first Push-Button Configuration result messages only within a time period, starting from the first virtual or physical Push-Button-Event.

26. A network node device according to claim 22, wherein the first Push-Button Configuration result messages being sent and received are different to each other if the first identifier is different and the second identifier and the third identifier are equal or the same.

27. A computer program product for product for running Push-Button Configuration sessions within a heterogeneous network, the computer program product comprising a non-transitory computer-readable storage device having computer-readable program instructions stored therein, wherein the computer readable program instructions when executed by a processor:

sends a notification message about a first Push-Button Event from the first network node device to at least two second network node devices, wherein the first and second network node devices are previously authenticated for the network,

wherein the first Push-Button-Event is assigned to the first network node device,

wherein the sending of the notification message is triggered by the first Push-Button Event

whereby the at least two second network node devices become authenticating second network node devices;

authenticates at least two third network node devices each by a second Push-Button-Event, wherein the at least two third network node devices are not yet authenticated for the network,

wherein the second Push-Button-Event is assigned to each of the third network node devices to run a Push-Button Configuration Protocol,

wherein the at least two third network node devices are authenticated for the network with devices selected from (1) the first network node device and an authenticating second network node device and (2) at least two authenticating second network node devices; and

after authenticating the at least two third network node devices, performs a Push-Button Configuration Roll-Back procedure by either (1) the first network node device and the authenticating second network node device or and (2) the at least two authenticating second network node devices,

wherein the Push Button Configuration Roll Back procedure discredits credentials established when authenticating the at least two third network node devices; and

further comprising means for running a Push-Button Configuration protocol and means for initiating a Push-Button Configuration Roll-Back procedure connected with sending/receiving means and within the Push-Button Configuration Roll-Back procedure the run of the Push-Button Configuration Protocol with the authenticated third network node device is rolled back and the credentials established with the authenticated third network node device are deleted or deactivated.

28. A computer program product for product for running Push-Button Configuration sessions within a heterogeneous network, the computer program product comprising a non-transitory computer-readable storage device having computer-readable program instructions stored therein, wherein the computer readable program instructions when executed by a processor:

sends a notification message about a first Push-Button Event from a first network node device to at least two second network node devices,

wherein the first and second network node devices are previously authenticated for the network,

wherein the first Push-Button-Event is assigned to the first network node device,

wherein the sending of the notification message is triggered by the first Push-Button Event

whereby the at least two second network node devices become authenticating second network node devices;

authenticates a third network node device by a second Push-Button-Event, wherein the third network node device is not yet authenticated for the network, wherein the second Push-Button-Event is assigned to the third network node device to run a Push-Button Configuration Protocol with the first net node device or with an authenticating second network node device; and

after finishing authentication, transmits a third Push-Button Configuration result message from the first network node device or the authenticating second network node device, the third Push-Button Configuration result message including at least one of (i) a message identifier and a message source identifier in a message header field (ii) in a TLV-part or an information element or in header field of the message a first identifier indicating a sender or originator of the Push-Button Configuration result message, a second identifier indicating an address of the first network node device as originator of the first Push-Button-Event and/or a third identifier indicating an event ID of the first Push-Button-Event and (iii) in a TLV-part or an information element an address or abstraction layer identifier of each third network node device,

the third Push-Button Configuration result message being transmitted by broadcast or by relayed multicast to all network node devices in the heterogeneous network;

further comprising means for running a Push-Button Configuration protocol and means for initiating a Push-Button Configuration Roll-Back procedure connected with sending/receiving means and within the Push-Button Configuration Roll-Back procedure the run of the Push-Button Configuration Protocol with the authenticated third network node device is rolled back and the credentials established with the authenticated third network node device are deleted or deactivated.

29. A network node device for running Push-Button Configuration sessions within a heterogeneous network with a plurality of other network node devices, interconnected to each other network, being authenticated for the network, the network node device comprising:

(a) Means for receiving a notification message triggered by a first Push-Button-Event assigned to a first network node device authenticated for the network, and for sending the notification message to a further second authenticated network node device,

(b) Means for running a Push-Button Configuration protocol and a means for initiating a Push-Button Configuration Roll-Back procedure connected with the means for receiving and for sending and configured to;

(b1) run a Push-Button Configuration Protocol with a third network node device not yet authenticated for the network, which is triggered by a second Push-Button-Event assigned to the third network node device to authenticate the third network node device for the network,

(b2) after finishing the authentication, initiate a Push-Button Configuration Roll-Back procedure to delete or deactivate credentials established with the authenticated third network node device, if the first Push-Button Configuration result messages are different to each other, wherein a first Push-Button Configuration result message is transmitted by broadcast or relayed multicast to all network node devices in the heterogeneous network, and wherein a first Push-Button Configuration result message is received from at least one of the other network node devices or due to at least two first Push-Button Configuration result messages being received from at least one of the other network node devices

wherein the means for running a Push-Button Configuration protocol and initiating a Push-Button Configuration Roll-Back procedure are connected with the means for receiving and for sending configured to, within the Push-Button Configuration Roll-Back procedure, roll back the run of the Push-Button Configuration Protocol with the authenticated third network node device and delete or deactivate the credentials established with the authenticated third network node device.

30. A network node device according to claim 29, wherein the means for running a Push-Button Configuration protocol and initiating a Push-Button Configuration Roll-Back procedure are connected with the sending/receiving means and designed such that within the Push-Button Configuration Roll-Back procedure the run of the Push-Button Configuration Protocol with the authenticated third network node device is rolled back, the credentials established with the authenticated third network node device are deleted or deactivated and a Push-Button Configuration roll-back message to all other network node devices in the network in order to trigger rolling back of the Push-Button Configuration Protocol runs with the authenticated third network node device at other network node devices is sent.

31. A network node device according to claim 29, wherein the means for running a Push-Button Configuration protocol and initiating a Push-Button Configuration Roll-Back procedure are connected with the sending/receiving means and designed such that within the Push-Button Configuration Roll-Back procedure a Push-Button Configuration roll-back message to all other network node devices in the network in order to trigger rolling back of the Push-Button Configuration Protocol runs with the authenticated third network node device at other network node devices is sent.

32. A network node device according to claim 29, wherein the means for running a Push-Button Configuration protocol and initiating a Push-Button Configuration Roll-Back procedure are designed such that the comparison, whether the first Push-Button Configuration result messages being sent and received are different is based on a message identifier and a message source identifier, a first identifier indicating the sender or originator of the Push-Button Configuration result message, a second identifier indicating the address of the first network node device as the originator of the first Push-Button-Event and/or a third identifier indicating an event ID of the first Push-Button-Event each included in a TLV-part or an information element or in header field of the first Push-Button Configuration result message or an address or abstraction layer identifier of the third network node device included in a TLV-part or an information element of the first Push-Button Configuration result message.

33. A network node device according to claim 30, wherein the Push-Button Configuration roll-back message includes a message identifier and a message source identifier in a message header field, and/or in a TLV-part or an information element a first identifier indicating the address of the first network node device as the originator of the first Push-Button-Event and as the sender of the second Push-Button Configuration roll-back message, a second identifier indicating an event ID of the first Push-Button-Event and/or a third identifier indicating an address or abstraction layer identifier of the at least one network node device as registrar.

34. A network node device according to claim 29, wherein the means for running a Push-Button Configuration protocol and initiating a Push-Button Configuration Roll-Back procedure are connected with the sending/receiving means and designed such that a first Push-Button status message is sent to all network node devices in the heterogeneous network with or without the third network node devices and before the first Push-Button Configuration result message in order to announce the first Push-Button Configuration result message.

35. A network node device according to claim 29, wherein the means for running a Push-Button Configuration protocol and initiating a Push-Button Configuration Roll-Back procedure are designed such that they count the number of the first Push-Button Configuration result messages only within a time period, starting from the reception of the notification message.

36. A network node device according to claim 32, wherein the first Push-Button Configuration result messages, being sent and received or received, are different to each other if the first identifier is different and the second identifier and the third identifier are equal or the same.

37. A computer program product for product for running Push-Button Configuration sessions within a heterogeneous network with a plurality of network node devices interconnected to each other over multiple hops via at least one interface, the computer program product comprising a non-transitory computer-readable storage device having computer-readable program instructions stored therein, the computer readable program instructions being executable by a processor to:

send a notification message about a first Push-Button Event from a first network node device to at least two second network node devices, wherein the first and second network node devices are previously authenticated for the network,

wherein the first Push-Button-Event is assigned to the first network node device,

wherein the sending of the notification message is triggered by the first Push-Button Event,

whereby the at least two second network node devices become authenticating second network node devices;

authenticating at least two third network node devices each by a second Push-Button-Event,

wherein the at least two third network node devices are not yet authenticated for the network,

wherein the second Push-Button-Event is assigned to each of the third network node devices to run a Push-Button Configuration Protocol,

wherein the at least two third network node devices are authenticated for the network with either (1) the first network node device and an authenticating second network node device or (2) at least two authenticating second network node devices; and

after authenticating the at least two third network node devices, performing a Push-Button Configuration Roll-Back procedure by either (1) the first network node device and the authenticating second network node device or (2) the at least two authenticating second network node devices, wherein the Push Button Configuration Roll Back procedure discredits credentials established when authenticating the at least two third network node devices;

running the first Push-Button Configuration Roll-Back procedure and a second Push-Button Configuration Roll-Back procedure both via at least one method selected from;

internally within the first network node device and directly with the first network node device;

indirectly via a non-authenticating second network node between the authenticating second network node device and the first network node device by handshaking messages;

both each directly with the first network node device; and

indirectly via a non-authenticating second network node device between the authenticating second network node device and the first network node device by handshaking messages.

38. Heterogeneous network with a plurality of network node devices interconnected to each other over multiple hops via at least one interface for running Push-Button Configuration sessions, the network comprising:

a first network node device,

at least one second network node device, and

at least one third network node device, wherein the first network node device comprises;

(a) Means for performing a first Push-Button-Event,

(b) Means for sending/receiving messages triggered by the performing means, to send a notification message about the first Push-Button-Event to the at least one second authenticated network node device authenticated for the network,

(c) Means for running a Push-Button Configuration protocol and initiating a Push-Button Configuration Roll-Back procedure, which are connected with the sending/receiving means and configured to;

(c1) run a Push-Button Configuration Protocol with a third network node device not yet authenticated for the network, which is triggered by a second Push-Button-Event assigned to the third network node device to authenticate the third network node device for the network,

(c2) after finishing the authentication, due to a first Push-Button Configuration result message to be transmitted and due to a first Push-Button Configuration result message received from at least one of the other network node devices initiate a Push-Button Configuration Roll-Back procedure to delete or deactivate credentials established with the authenticated third network node device, if due to a comparison, whether the first Push-Button Configuration result messages being sent and received are different to each other, a number of the first Push-Button Configuration result messages by counting is greater than 1;

wherein the means for running a Push-Button Configuration protocol and initiating a Push-Button Configuration Roll-Back procedure are connected with the means for receiving and for sending configured to, within the Push-Button Configuration Roll-Back procedure, roll back the run of the Push-Button Configuration Protocol with the authenticated third network node device and delete or deactivate the credentials established with the authenticated third network node device.