Method and Devices for Running Push-Button Configuration Sessions

• US 20170155648A1
• Filed: 02/10/2017
• Published: 06/01/2017
• Est. Priority Date: 12/12/2011
• Status: Active Grant

• Current Assignee: Siemens AG
• Original Assignee: Siemens AG
• Inventors: Mogre, Parag, Falk, Rainer, Bahr, Michael
• Granted Patent: US 10,462,001 B2
• Time in Patent Office: Days
• 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. Method for running Push-Button Configuration sessions within a heterogeneous network with a plurality of network node devices (D1, . . D4, ND, AN) interconnected to each other via at least one interface and/or over multiple hops, whereby a first network node device (D1) being authenticated for the network is triggered by a first virtual or physical Push-Button-Event (PBE-1) being assigned to the first network node device (D1) to send directly or indirectly a notification message (PBN) notifying about the first. Push-Button-Event (PBE-1) to second network node devices (D2 . . . D4) being each authenticated for the network characterized by:

(a) At least two third network node devices (ND, AN) not being yet authenticated for the network are triggered each by a second virtual or physical Push-Button-Event (PBE-2) being assigned to the third network node device (ND, AN) to run a Push-Button Configuration Protocol with the first network node device (D1) and at least one of the second network node devices (D2, . . . D4) or with at least two of the second. network node devices (D2 . . . D4) authenticating the at least two third network node devices (ND, AN) for the network and

(b) after finishing the authentication the first network node device (D1) and the at least one of the second network node device (D2 . . . D4) or the at least two of the second network node devices (D2 . . . D4) are initiating each a Push-Button Configuration Roll-Back procedure in order to delete or deactivate credentials established with the authenticated third network node devices (ND, AN).

2. Method according to claim 1, wherein the two Push-Button Configuration Roll-Back procedures are running

(a) internally within the first network node device (D1) and directly with the first network node device (D1) or indirectly via at least one of all the rest of the second network node devices (D2 . . . D4) between the at least one of the second network node device (D2 . . . D4) and the first network node device (D1) by handshaking messages or

(b) both each directly with the first network node device (D1) or indirectly via at least one of all the rest of the second network node devices (D2 . . . D4) between the at least one of the second network node device (D2 . . . D4) and the first network node device (D1) by handshaking messages.

3. Method according to claim 1, wherein a first Push-Button Configuration result message (PBR) including a message identifier and a message source identifier, especially in a message header field, is transmitted broadcast or by relayed multicast from the network node devices initiating the Push-Button Configuration Roll-Back procedure to all network node devices in the heterogeneous network with or without the third network node devices (ND, AN) so that the at least two network node devices initiating the Push-Button Configuration Roll-Back procedure, if they count due to a comparison whether the first Push-Button Configuration result messages (PBR), being (i) sent and received or (ii) received, are different to each other on the basis of the message identifier and message source identifier, a number of the first Push-Button. Configuration result messages (PBR), which is greater than 1,

(a) roll back the of the Bush-Button Configuration Protocol with the authenticated third network node devices AN) and delete or deactivate the credentials established with the authenticated third network node devices (ND, AN) or

(b) roll back the run of the Push-Button Configuration Protocol with the authenticated third network node devices (ND, AN), delete or deactivate the credentials established with the authenticated third network node devices (ND, AN) and send a Push-Button Configuration roll-back message to all other network node devices in the network in order to trigger the roll back of the Push-Button Configuration Protocol runs with the authenticated third network node devices (ND, AN) at other network node devices.

4. Method according to claim 1, wherein a first Push-Button Configuration result message (PBR) including a message identifier and a message source identifier, especially in a message header field, is transmitted by broadcast or by relayed multicast from the network node devices initiating the Push-Button Configuration Roll-Back procedure to all network node devices in the heterogeneous network with or without the third network node devices (ND, AN) so that each network node device in the network whether it has initiated a Push-Button Configuration Roll-Back procedure or not, if it counts due to a comparison whether the first Push-Button Configuration result messages (PBR), being (i) sent and received or (ii) received, are different to each other on the basis of the message identifier and message source identifier, a number of the first Push-Button Configuration result messages (PBR), which is greater than 1, sends a Push-Button Configuration roll-back message to all other network node devices in the network in order to trigger the roll back of the Push-Button Configuration Protocol runs with the authenticated third network node devices (ND, AN) at other network node devices.

5. Method according to claim 1, wherein a first Push-Button Configuration result message (PBS) including in a TLV-part or an information element or in header field of the message a first identifier indicating the sender or originator of the Push-Button Configuration result message (PBR), a second identifier indicating the address of the first network node device as the originator of the first Push-Button-Event (PBE-1) and/or a third identifier indicating an event ID of the first Push-Button-Event (PBE-1) is transmitted by broadcast or by relayed multicast from the network node devices initiating the Push-Button Configuration Roll-Back procedure to network node devices in the heterogeneous network with or without the third network node devices (ND, AN) so that the at least two network node devices initiating the Push-Button Configuration Roll-Back procedure, if they count due to a comparison whether the first Push-Button Configuration result messages (PBR), being (i) sent and received or (ii) received, are different to each other on the basis of the first identifier, the second identifier and/nor the third identifier, a number of the first Push-Button Configuration result messages (PBS), which is greater than 1,

(a) roll back the run of the Push-Button Configuration Protocol with the authenticated third network node devices (ND, AN) and delete or deactivate the credentials established with the authenticated third network node devices (ND, AN) or

(b) roll back the run the Push-Button Configuration Protocol with the authenticated third network node devices (ND, AN), delete or deactivate the credentials established with the authenticated third network node devices (ND, AN) and send a Push-Button Configuration roll-back message to all other network node devices in the network in order to trigger the roll back of the Push-Button Configuration Protocol runs with the authenticated third network node devices (ND, AN) at other network node devices.

6. Method according to claim 1, wherein a first Push-Button Configuration result message (PBR) including in a TLV-part or an information element or a header field of the message a first identifier indicating the sender or originator of the Push-elution Configuration result message (PBR), a second identifier indicating the address of the first network node device as the originator of the first Push-Button-Event (PBE-1) and/or a third identifier indicating an event ID of the first Push-Button-Event (PBE-1) is transmitted by broadcast or by relayed multicast from the network node devices initiating the Push-Button Configuration Roll-Back procedure to all network node device in the heterogeneous network with or without the third network node devices (ND, AN) so that each network node device in the network whether it has initiated a Push-Button Configuration Roll-Back procedure or not, if it counts due to comparison whether the first Push-Button Configuration result messages (PBR), being (i) sent and received or (ii) received, are different to each other on the basis the first identifier, the second identifier and/or the third identifier, a number of the first Push-Button Configuration result messages (PBR), which is greater than 1, sends a Push-Button Configuration roll-back message to all other network node devices in the network in order to trigger the roll back of the Push-Button Configuration Protocol runs with the authenticated third network node devices (ND, AN) at other network node devices.

7. Method according to claim 1, wherein a first Push-Button Configuration result message (PBR) including in a TLV-part or an information element an address or abstraction layer identifier of the third network node device (ND, AN) is transmitted by broadcast or by relayed multicast from the network node devices initiating the Push-Button Configuration Roll-Back Procedure to network node devices in the heterogeneous network with or without the third network node devices (ND, AN) so that the at least two network node devices initiating the Push-Button Configuration Roll-Back procedure, if they count due to a comparison whether the first Push-Button Configuration result messages (PBR), being (i) sent and received or (ii) received, are different to each other on the basis of the address or abstraction layer identifier of the third network node devices (ND, AN), a number of the first Push-Button Configuration result messages (PBR), which is greater than 1,

(a) roll back the run of the Push-Button Configuration Protocol with the authenticated third network node devices (ND, AN) and delete or deactivate the credentials established with the authenticated third network node devices (ND, AN) or

(b) roll back the run of the Push-Button Configuration Protocol with the authenticated third network node devices (ND, AN), delete or deactivate the credentials established with the authenticated third network node devices (ND, AN) and send a Push-Button Configuration roll-back message to all other network node devices in the network in order to trigger the roll back of the Push-Button Configuration Protocol runs with the authenticated third network node devices (ND, AN) at other network node devices.

8. Method according to claim 1, wherein a first Push-Button Configuration result message (PBR) including in a TLV-part or an information element an address or abstraction layer identifier of the third network node device (ND, AN) is transmitted by broadcast or by relayed multicast from the network node devices initiating the Push-Button Configuration Roll-Back procedure to all network node devices in the heterogeneous network with or without the third network node devices (ND, AN) so that each network node device in the network whether it has initiated a Push-Button Configuration Roll-Back procedure or not, if it counts due to a comparison whether the first Push-Button Configuration result messages (PBR), being (i) sent and received or (ii) received, are different to each other on the basis of the address or abstraction layer identifier of the third network node device (ND, AN), a number of the first Push-Button Configuration result messages (PBR), which is greater than 1, sends a Push-Button Configuration roll-back message to all other network node devices in the network in order to trigger the roll back of the Push-Button Configuration Protocol runs with the authenticated third network node devices (ND, AN) at other network node devices.

9. Method according to claim 2, wherein a second Push-Button Configuration result message (PBR) as one handshake message including a message identifier and a message source identifier, especially in a message header field, is sent each from the at least one second network node device (D2 . . . D4) initiating the Push-Button Configuration Roll-Back procedure directly or indirectly via the at least one of all the rest of the second network node devices (D2 . . . D4) to the first network node device (D1) so that the network node device (D1)

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

(b) not initiating itself the Push-Button Configuration Roll-Back procedure, if it counts due to a comparison whether the second Push-Button Configuration result messages (PBR) being received are different to each other on the basis of the message identifiers and message source identifiers, a number of the second Push-Button Configuration result messages (PBR), which is greater than 1, sends Push-Button Configuration roll-back message as another handshaking message directly or indirectly via the at least one of all the rest of the second network node devices (D2 . . . D4) to the at least two second network node devices (D2 . . . D4) initiating each the Push-Button Configuration Roll-Back procedure in order to trigger the roll back of the Push-Button Configuration Protocol runs with the authenticated third network node devices (ND, AN) at the at least two second network node devices (D2 . . . D4).

10. Method according to claim 2, wherein a second Push-Button Configuration result message (PBR) as one handshake message including in a TLV-part or an information element or a header field of the message a first identifier indicating the sender or originator of the Push-Button Configuration result message (PBR), a second identifier indicating the address of the first network node device as the originator of the first Push-Button-Event (PBE-1) and as the receiver of the second Push-Button Configuration result message (PBR) and/or a third identifier indicating an event ID of the first Push-Button-Event (PBE-1) is sent each from the at least one second network node device (D2 . . . D4) initiating the Push-Button Configuration Roll-Back procedure directly or indirectly via the at least one of all the rest of the second network node devices (D2 . . . D4) to the first network node device (D1) so that the first network node (D1)

(a) initiating itself the Push-Button Configuration Roll-Back procedure, if due to an internal comparison in the first network node device (D1) on the basis of the first identifier, the second identifier and/or the third identifier, rolls back the run of the Push-Button Configuration Protocol with the at least one of the authenticated third network node devices (ND, AN), deletes or deactivates the credentials established with the at least one the authenticated third network node devices (ND, AN) and sends a Push-Button Configuration roll-back message as another handshaking message via the at least one of all the rest of the second network node devices (D2 . . . D4) to the at least one second network node device (D2 . . . D4) initiating the Push-Button Configuration Roll-Back procedure in order to trigger the roll back of the Push-Button Configuration Protocol run with the authenticated third network node devices (ND, AN) at the at least one second network node device (D2 . . . AN) or respectively

(b) not initiating itself the Push-Button Configuration Roll-Back procedure, if it counts due to a comparison whether the second Push-Button Configuration result messages (PBR) being received are different to each other on the basis of the first the second identifier and/or the third identifier, a number of the second Push-Button Configuration result messages (PBR), which is greater than 1, sends a Push-Button Configuration roll-back message as another handshaking message directly or indirectly via the at least one of all the rest of the second network node devices (D2 . . . D4) to the at least two second network node devices (D2 . . . D4) initiating each the Push-Button Configuration Roll-Back procedure in order to trigger the roll back of the Push-Button Configuration Protocol runs with the authenticated third network node devices (ND, AN) at the at least two second network node devices (D2 . . . D4).

11. Method according to claim 2, wherein a second Push-Button Configuration result message (PBR) as one handshake message including a TLV-part or an information element an address or abstraction layer identifier of the third network node devices (ND, AN) s sent each from the at least one second network node device (D2 . . . D4) initiating the Push-Button Configuration Roll-Back procedure directly or indirectly via the at least one of all the rest of the second network node devices (D2 . . . D4) the first network node device (D1) so that the first network node device (D1)

(a) initiating itself the Push-Button Configuration Roll-Back procedure, if due to a comparison the authenticated third network node devices (ND, AN) are different on the basis of the address or abstraction layer identifier of the third network node device (ND, AN), rolls back the run of the Push-Button Configuration Protocol with the at least one of the authenticated third network node devices (ND, AN), deletes or deactivates the credentials established with the at least one of the authenticated third network node devices (ND, AN) and sends a Push-Button Configuration roll-back message as another handshaking massage directly or indirectly via the at least one of all the rest of the second network node devices (D2 . . . D4) to the at least one second network node device (D2 . . . D4) initiating the Push-Button Configuration Roll-Back procedure in order to trigger the roll back of the Push-Button Configuration Protocol run with the authenticated third network node devices (ND, AN) at he at least one second network node device (D2 . . . D4) or respectively

(b) not initiating itself the Push-Button Configuration Roll-Back procedure, if it counts dire to a comparison whether the second Push-Button Configuration result messages (PBR) being received are different to each other on the basis of the address or abstraction layer identifier of the third network node device (ND, AN), a number of the second Push-Button Configuration result messages (PBR), which is greater than 1, sends a Push-Button Configuration roll-back message as another handshaking message directly or indirectly via the at least one of all the rest of the second network node devices (D2 . . . D4) to the at least two second network node devices (D2 . . . D4) initiating each the Push-Button Configuration Roll-Back Procedure in order to trigger the roll back of the Push-Button Configuration Protocol runs with the authenticated third network node devices (ND, AN) at the at least two second network node devices (D2 . . . D4).

12. Method according to claim 3, wherein the Push-Button Configuration roll-back message includes a message identifier and a message source identifier, especially 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 (PBE-1) and as the sender of the Push-Button Configuration roll-back message, second identifier indicating an event ID of the first Push-Button-Event (PBE-1) and/or a third identifier indicating an address or abstraction layer identifier of the at least one network node device (D1, D2 . . . D4) as registrar.

13. Method according to claim 3, wherein a first Push-Button status message (PBS) is sent to all network node devices in the heterogeneous network with or without the third network node devices (ND, AN) and before the first Push-Button Configuration result message (PBR) in order to announce this Push-Button Configuration result message (PBR).

14. Method according to claim 9, wherein a second Push-Button status message (PBS) is sent to the first network node device (D1) and before the second Push-Button Configuration result message (PBR) in order to announce this Push-Button Configuration result message (PBR).

15. Method according to claim 3, wherein each of the at least two network node devices initiating the Push-Button Configuration Roll-Back procedure counts the number of the first Push-Button Configuration result messages (PBR) only within a time period, especially of 120 seconds, starting from the first virtual or physical Push-Button-Event (PBE-1) or the reception of the notification message (PBN).

16. Method according to claim 9, wherein the first network node device (D1) counts the number of the second Push-Button Configuration result messages (PBR) only within a time period, especially or 120 seconds, starting from the first virtual or physical Push-Button-Event (PBE-1).

17. Method according to claim 5, wherein the first Push-Button Configuration result messages (PBR) being (i) sent and received or (ii) 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.

18. Method for running Push-Button Configuration sessions within a heterogeneous network with a plurality of network node devices (D1 . . . D4, ND) interconnected to each other via at least one interface and/or over multiple hops, whereby a first network node device (D1) being authenticated for the network is triggered by a first virtual or physical Push-Button-Event (PBE-1) being assigned to the first network node device (D1) to send directly or indirectly a notification message (PBN) notifying about the first Push-Button-Event (PBE-1) to second network node devices (D2 . . . D4) being each authenticated for the network characterized by:

(a) One third network node device (ND) not being yet authenticated for the network is triggered by a second virtual or physical Push-Button-Event (PBE-2) being assigned to the third network node device (ND) to run a Push-Button Configuration Protocol with the first network node device (D1) or with one of the second network node devices (D2 . . . D4) authenticating the third network node device (ND) for the network and

(b) after finishing the authentication the first network node device (D1) or the second network node device (D2 . . . D4) a third Push-Button Configuration result message (PBR) including (i) a message identifier and a message source identifier, especially in a message header field and/or (ii) in a TLV-part or an information element or in header field of the message a first identifier indicating the sender or originator of the Push-Button Configuration result message (PBR), a second identifier indicating the address of the first network node device as the originator of the first Push-Button-Event (PBE-1) and/or a third identifier indicating an event ID of the first Push-Button-Event (PBE-1) and/or (iii) in a TLV-part or an information element an address or abstraction layer identifier of the third network node device (ND) is transmitted by broadcast or by relayed multicast from the network node devices finishing the authentication to all network node devices in the heterogeneous network with or without the third network node device (ND).

19. Method for running Push-Button Configuration sessions within a heterogeneous network with a plurality of network node devices (D1 . . . D4, ND) interconnected to each other via at least one interface and/or over multiple hops, whereby a first network node device (D1) being authenticated for the network is triggered by a first virtual or physical Push-Button-Event (PBE-1) being assigned to the first network node device (D1) to send directly or indirectly a notification message (PBN) notifying about the first Push-Button-Event (PBE-1) to second network node devices (D2 . . . D4) being each authenticated for the network characterized by:

(a) One third network node device (ND) not being vet authenticated for the network is triggered by a second virtual or physical Push Button Event (PBE-2) being assigned to the third network node device (ND) to run a Push-Button Configuration Protocol with one of the second network node devices (D2 . . . D4) authenticating third network node device (ND) for the network and

(b) after finishing the authentication by the second network node device (D2 . . . D4) a fourth Push-Button Configuration result message (PER) including (i) a message identifier and a message source identifier, especially in a message header field, and/or (ii) in a TLV-part or an information element or in header field of the message a first identifier indicating the sender or originator of the Push-Button Configuration result message (PBR), a second identifier indicating the address of the first network node device as the originator of the first Push-Button-Event (PBE-1) and as the receiver of the fourth Push-Button Configuration result message (PBR) and/or a third identifier indicating an event ID of the first Push-Button-Event (PBE-1) and/or (iii) in a TLV-part or an information element an address or abstraction layer identifier of the third network node device (ND) is sent from the second network node device (D2 . . . D4) finishing the authentication directly or indirectly via at least one of the rest of the second network node devices (D2 . . . D4) to the first network node device (D1).

20. First network node device (D1) for running Push-Button Configuration sessions within a heterogeneous network with a plurality of other network node devices (D2 . . . D4, ND, AN), interconnected to each other via at least one interface and/or over multiple hops and authenticated or unauthenticated for the network, being authenticated for the network, characterized by:

(a) Means (M1) for performing a first virtual or physical Push-Button-Event (PBE-1),

(b) Means for sending/receiving information and/or messages (M3), which are triggered by the performing means, send directly or indirectly a notification message (PBN) notifying about the Push-Button-Event (PBE-1) to second authenticated network node devices (D2 . . . D4) of the other network node devices (D2 . . . D4, ND, AN) being each authenticated for the network,

(c) Means for running a Push-Button Configuration protocol and initiating a Push-Button Configuration Roll-Back procedure (M2) 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 (ND, AN) not being yet authenticated for the network, whereby the Push-Button Configuration Protocol is triggered by receiving Push-Button Configuration Protocol Messages, which indicate a second virtual or physical Push-Button-Event (PBE-2) being assigned to the third network node device (ND, AN) in order to authenticate the third network node device (ND, AN) for the network,

(c2) after finishing the authentication, due to a first Push-Button Configuration result message (PBR) to be transmitted by broadcast or relayed multicast to all network node devices in the heterogeneous network with or without the third network node device (ND, AN) and due to a first Push-Button Configuration result message (PBR) being received from at least one of the other network node devices (D2 . . . D4, ND, AN) directly or indirectly via at least one of the rest of the other network node devices (D2 . . . D4, ND, AN), initiate a Push-Button Configuration Roll-Back procedure in order to delete or deactivate credentials established with the authenticated third network node device (ND, AN), if due to a comparison, whether the first Push-Button Configuration result messages (PBR) being sent and received are different to each other, a number of the first Push-Button Configuration result messages (PBR) by counting is greater than 1.

21. First network node device according to claim 20, wherein the means for running a Push-Button Configuration protocol and initiating a Push-Button Configuration Roll-Back procedure (M2) 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 (ND, AN) is rolled back and the credentials established with the authenticated third network node device (ND, AN) are deleted or deactivated.

22. First network node device according to claim 20, wherein the means for running a Push-Button Configuration protocol and initiating a Push-Button Configuration Roll-Back procedure (M2) 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 (ND, AN) is rolled back, the credentials established with the authenticated third network node device (ND, AN) 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 the roll back of the Push-Button Configuration Protocol runs with the authenticated third network node device (ND, AN) at other network node devices is sent.

23. First network node device according to claim 20, wherein the means for running a Push-Button Configuration protocol and initiating a Push-Button Configuration Roll-Back procedure (M2) 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 the roll back of the Push-Button Configuration Protocol runs with the authenticated third network node device (ND, AN) at other network node devices is sent.

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

25. First network node device according to claim 22, wherein the Push-Button Configuration roll-back message includes a message identifier and a message source identifier, especially 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 (PBE-1) and as the sender of the Push-Button Configuration roll-back message, a second identifier indicating an event ID of the first Push-Button-Event (PBE-1) and/or a third identifier indicating an address or abstraction layer identifier of the at least one network node device (D1, D2 . . . D4) as registrar.

26. First network node device according to claim 20, 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 (PBS) is sent to all network node devices in the heterogeneous network with or without third network node devices (ND, AN) and before the first Push-Button Configuration result message (PBR) in order to announce this Push-Button Configuration result message (PBR).

27. First network node device according to claim 20, wherein the means for running a Push-Button Configuration protocol and initiating a Push-Button Configuration Roll-Back procedure (M2) are designed such that they count the number of the first Push-Button Configuration result messages (PBR) only within a time period, especially of 120 seconds, starting from the first virtual or physical Push-Button-Event (PBE-1).

28. First network node device according to claim 24, wherein the Push-Button Configuration result messages (PBR) 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.

41. Computer readable storage media being executable by a processor to run Push-Button Configuration sessions within a heterogeneous network with a plurality of network node devices interconnected to each other via at least one interface and/or over multiple hops and implemented in a first network node device (D1) according to claim 20 and/or in at least one second network node device (D2 . . . D4) carries out the method for running Push-Button Configuration sessions within a heterogeneous network with a plurality of network node devices interconnected to each other via at least one interface and/or over multiple hops.

42. Heterogeneous network for running Push-Button Configuration sessions comprising a first network node device (D1) according to claim 20, at least one second network node device (D2 . . . D4) and at least one third network node device (ND, AN), which together with the first network node device (D1) and the at least one second network node device (D2 . . . D4) are used for running Push-Button Configuration sessions within a heterogeneous network with a plurality of network node devices interconnected to each other via at least one interface and/or over multiple hops.

29. First network node device (D1) for running Push-Button Configuration sessions within a heterogeneous network with a plurality other network node devices (D2 . . . D4, ND), interconnected to each other via at least one interface and/or over multiple hops and authenticated or unauthenticated for the network, being authenticated for the network, characterized by:

(a) Means (M1) for performing a first virtual or physical Push-Button-Event (PBE-1),

(b) Means for sending/receiving information and/or messages (M3), which are triggered by the performing means, send directly or indirectly a notification message (PBN) notifying about the first Push-Button-Event (PBE-1) to second authenticated network node devices (D2 . . . D4) of the other network node devices (D2 . . . D4, ND) being each authenticated for the network,

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

(c1) run a Push-Button Configuration Protocol with one third network node device (ND) not being yet authenticated for the network, whereby the Push-Button Configuration Protocol is triggered by receiving Push-Button Configuration Protocol Messages, which indicate a second virtual or physical Push-Button-Event (PBE-2) being assigned to the third network node device (ND) in order to authenticate the third network node device (ND) for the network,

(c2) after finishing the authentication transmit a third Push-Button Configuration result message (PBR) including (i) a message identifier and a message source identifier, especially in a message header field and/or (ii) in a TLV-part or an information element or in header field of the message a first identifier indicating the sender or originator of the Push-Button Configuration result message (PBR), a second identifier indicating the address of the first network node device as the originator of the first Push-Button-Event (PBE-1) and/or a third identifier indicating an event ID of the first Push-Button-Event (PBE-1) and/or (iii) in a TLV-part or an information element an address or abstraction layer identifier of the third network node device (ND) by broadcast or by relayed multicast to all network node devices in the heterogeneous network with or without the third network node devices (ND).

30. Second network node device (D2 . . . D4) for running Push-Button Configuration sessions within a heterogeneous network with a plurality of other network node devices (D1, D2 . . . D4, ND, AN), interconnected to each other via at least one interface and/or over multiple hops and authenticated or unauthenticated for the network, being authenticated for the network, characterized by:

(a) Means for sending/receiving information and/or messages (M3) receive a notification message (PBN), which is triggered by a first virtual or physical Push-Button-Event (PBE-1) being assigned to a first network node device (D1) of the other network node devices (D1, D2 . . . D4, ND, AN), being authenticated for the network, and send to further second authenticated network node devices (D2 . . . D4) of the other network node devices (D1, D2 . . . D4, ND, AN),

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

(b1) run a Push-Button Configuration Protocol with a third network node device (ND, AN) not being yet authenticated for the network, whereby the Push-Button Configuration Protocol is triggered by receiving Push-Button Configuration Protocol Messages, which indicate a second virtual or physical Push-Button-Event (PBE-2) being assigned to the third network node device (ND, AN) in order to authenticate the third network node device (ND, AN) for the network,

(b2) after finishing the authentication and (i) due to a first Push-Button Configuration result message (PBR) to be transmitted hr broadcast or relayed multicast to all network node devices in the heterogeneous network with or without the third network node device (ND, AN) and due to a first Push-Button Configuration result message (PBR) being received from at least one of the other network node devices (D1, D2 . . . D4, ND, AN) directly or indirectly via at least one of the rest of the other network node devices (D2 . . . D4, ND, AN) or (ii) due to at least two first Push-Button Configuration result messages (PBR) being received from at least one of the other network node devices (D1, D2 . . . D4, ND, AN) directly or indirectly via at least one of the rest of the other network node devices (D2 . . . D4, ND, AN), initiate a Push-Button Configuration Roll-Back procedure in order to delete or deactivate credentials established with the authenticated third network node device (ND, AN), if due to a comparison, whether the first Push-Button Configuration result messages (PBR), being (i) sent and received or (ii) received, are different to each other, a number of the first Push-Button Configuration result messages (PBR) by counting is greater than 1.

31. Second network node device according to claim 30, wherein the means for running a Push-Button Configuration protocol and initiating a Push-Button Configuration Roll-Back procedure (M2) 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 (ND, AN) is rolled back and the credentials established with the authenticated third network node device (ND, AN) are deleted or deactivated.

32. Second network node device according to claim 30, wherein the means for running a Push-Button Configuration protocol and initiating a Push-Button Configuration Roll-Back procedure (M2) are connected with the sending/receiving means and designed such that with the Push-Button Configuration Roll-Back procedure the run of the Push-Button Configuration Protocol with the authenticated third network node device (ND, AN) is rolled back, the credentials established with the authenticated third network node device (ND, AN) 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 the roll back of the Push-Button Configuration Protocol runs with the authenticated third network node device (ND, AN) at other network node devices is sent.

33. Second network node device according to claim 30, wherein the means for running a Push-Button Configuration protocol and initiating a Push-Button Configuration Roll-Back procedure (M2) 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 the roll back of the Push-Button Configuration Protocol runs with the authentic third network node device (ND, AN) at other network node devices is sent.

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

35. Second network node device according to claim 32, wherein the Push-Button Configuration roll-back message includes a message identifier and a message source identifier, especially 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 (PBE-1), a second identifier indicating an event ID of the first Push-Button-Event (PBE-1) and/or a third identifier indicating an address or abstraction layer identifier of the at least one network node device (D1, D2 . . . D4) as registrar.

36. Second network node device according to 30, wherein the means for running a Push-Button Configuration protocol and initiating a Push-Button Configuration Roll-Back procedure (M2) are connected with the sending/receiving means and designed such that a first Push-Button status message (PBS) is sent to all network node devices in the heterogeneous network with or without the third network node devices (ND, AN) and before the first Push-Button Configuration result message (PBR) in order to announce this Push-Button Configuration result message (PBR).

37. Second network node device according to claim 30, wherein the means for running a Push-Button Configuration protocol and initiating a Push-Button Configuration Roll-Back procedure (M2) are designed such that they count the number of the first Push-Button Configuration result messages (PBR) only within a time period, especially of 120 seconds, starting from the reception of the notification message (PBN).

38. Second network node device according to claim 34, wherein the first Push-Button Configuration result messages (PBR), being (i) sent and received or (ii) 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.

39. Second network node device (D2 . . . D4) for running Push-Button Configuration sessions within a heterogeneous network with a plurality of other network node devices (D1, D2 . . . D4, ND), interconnected to each other via at least one interface and/or over multiple hops and authenticated or unauthenticated for the network, being authenticated for the network, characterized by:

(a) Means for sending/receiving information and/or messages (M3) receive a notification message (PBN), which is triggered by first virtual physical Push-Button-Event (PBE-1) being assigned to a first network node device (D1) of the other network node devices (D1, D2 . . . D4, ND), being authenticated for the network, and send to further second authenticated network node devices (D2 . . . D4) or the other network node devices (D1, D2 . . . D4, ND),

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

(b1) run a Push-Button Configuration Protocol with one third network node device (ND) not being yet authenticated for the network, whereby the Push-Button Configuration Protocol is triggered by receiving Push-Button Configuration Protocol Messages, which indicate a second virtual or physical Push-Button-Event (PBE-2) being assigned to the third network node device (ND) in order to authenticate the third network node device (ND) for the network,

(b2) after finishing the authentication transmit a third Push-Button Configuration result message (PBR) including (i) a message identifier and a message source identifier, especially in a message header field and/or (ii) in a TLV-part or an information element or header field of the message a first identifier indicating the sender or originator of the Push-Button Configuration result message (PBR), a second identifier indicating the address of the first network node device as the originator of the first Push-Button-Event (PBE-1) and/or a third identifier indicating an event ID of the first Push-Button-Event (PBE-1) and/or (iii) in a TLV-part or an information element an address or abstraction layer identifier of the third network node device (ND) by broadcast or by relayed multicast to all network node devices in the heterogeneous network with or without the third network node devices (ND).

40. Second network node device (D2 . . . D4) for running Push-Button Configuration sessions within a heterogeneous network with a plurality of other network node devices (D1, D2 . . . D4, ND), interconnected to each other via at least one interface and/or over multiple hops and authenticated or unauthenticated for the network, being authenticated for the network, characterized by:

(a) Means for sending/receiving information and/or messages (M3) receive a notification message (PBN), which is triggered by a first virtual or physical Push-Button-Event (PBE-1) being assigned to a first network node device (D1) of the other network node devices (D1, D2 . . . D4, ND), being authenticated for the network and send to further second authenticated network node devices (D2 . . . D4) of the other network node devices (D1, D2 . . . D4, ND),

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

(b1) run a Push-Button Configuration Protocol with one third network node device (ND) not being yet authenticated for the network, whereby the Push-Button Configuration Protocol is triggered by receiving Push-Button Configuration Protocol Messages, which indicate a second virtual or physical Push-Button-Event (PBE-2) being assigned to the third network node device (ND) in order to authenticate the third network node device (ND) for the network,

(b2) after finishing the authentication send a fourth Push-Button Configuration result message (PBR) including (i) a message identifier and a message source identifier, especially in a message header field and/or (ii) in a TLV-part or an information element or in header field of the message a first identifier indicating the sender or originator of the Push-Button Configuration result message (PBR), a second identifier indicating the address of the first network node device as the originator of the first Push-Button-Event (PBE-1) and/or a third identifier indicating an event ID of the first Push-Button-Event (PBE-1) and/or (iii) in a TLV-part or an information element an address or abstraction layer identifier of the third network node device (ND) directly or indirectly via at least one of the rest of the second network node devices (D2 . . . D4) to the first network node device (D1).