METHOD AND DEVICES FOR RUNNING PUSH-BUTTON CONFIGURATION SESSIONS
1 Assignment
0 Petitions
Accused Products
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.
15 Citations
86 Claims
-
1-43. -43. (canceled)
-
44. A 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, comprising:
-
triggering a first network node device, the first network node device being authenticated for the network, the first network node device being triggered by a first virtual or physical Push-Button-Event assigned to the first network node device, the first network node device being triggered to send directly or indirectly a notification message notifying about the first Push-Button-Event to second network node devices being each authenticated for the network; triggering authentication of at least two third network node devices not yet authenticated for the network, each by a second virtual or physical Push-Button-Event being assigned to the third network node device to run a Push-Button Configuration Protocol, the at least two third network node devices each being authenticated for the network with the first network node device and an authenticating second network node device or with at least two authenticating second network node devices; and after authenticating the at least two third network node devices, initiating a Push-Button Configuration Roll-Back procedure, the Push-Button Configuration Roll-Back procedure being initiated by the first network node device and the authenticating second network node device or by the at least two authenticating second network node devices in order to delete or deactivate credentials established when authenticating the at least two third network node devices. - View Dependent Claims (45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 72, 83)
-
-
61. A 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, comprising:
-
triggering a first network node device, the first network node device being authenticated for the network, the first network node device being triggered by a first virtual or physical Push-Button-Event assigned to the first network node device, the first network node device being triggered to send directly or indirectly a notification message notifying about the first Push-Button-Event to second network node devices being each authenticated for the network; triggering a third network node device not yet authenticated for the network, the third network node device being triggered by a second virtual or physical Push-Button-Event assigned to the third network node device, the third network node device being triggered to run a Push-Button Configuration Protocol with the first network node device or with an authenticating second network node device to authenticate the third network node device for the network; 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 (i) a message identifier and a message source identifier 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 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/or (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 with or without each third network node device. - View Dependent Claims (73, 84)
-
-
62. A 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, comprising:
-
triggering a first network node device, the first network node device being authenticated for the network, the first network node device being triggered by a first virtual or physical Push-Button-Event assigned to the first network node device, the first network node device being triggered to send directly or indirectly a notification message notifying about the first Push-Button-Event to second network node devices being each authenticated for the network; triggering authentication of a single third network node device not yet authenticated for the network, the authentication being triggered by a second virtual or physical Push-Button-Event assigned to the third network node device, the single third network node device being triggered to run a Push-Button Configuration Protocol with the first network node device or with an authenticating second network node device, to authenticate the third network node device for the network; and after authenticating the third network node device and terminating a Push-Button Configuration session, sending a fourth Push-Button Configuration result message including (i) a message identifier and a message source identifier in a message header field, and/or (ii) in a TLV-part or an information element or in the message header field, 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/or a third identifier indicating an event ID of the first Push-Button-Event and/or in a TLV-part or an information element an address or abstraction layer identifier of the third network node devices, the fourth Push-Button Configuration result message being sent from the authenticating second network node device directly or indirectly via at least one non-authentication second network node device, to the first network node device.
-
-
63. First 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 via at least one interface and/or over multiple hops and authenticated or unauthenticated for the network, being authenticated for the network, comprising:
-
(a) Means for performing a first virtual or physical Push-Button-Event, (b) Means for sending/receiving information and/or messages, which are triggered by the performing means, send directly or indirectly a notification message notifying about the first Push-Button-Event to second authenticated network node devices of the other network node devices being each 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 designed such that they (c1) run a Push-Button Configuration Protocol with a third network node device not being yet authenticated for the network, which is triggered by a second virtual or physical Push-Button-Event being assigned to the third network node device in order 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 by broadcast or relayed multicast to all network node devices in the heterogeneous network with or without the third network node device and due to a first Push-Button Configuration result message being received from at least one of the other network node devices directly or indirectly via at least one of the rest 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. - View Dependent Claims (64, 65, 66, 67, 68, 69, 70, 71)
-
-
74. Second 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 via at least one interface and/or over multiple hops and authenticated or unauthenticated for the network, being authenticated for the network, comprising:
-
(a) Means for sending/receiving information and/or messages receive a notification message, which is triggered by a first virtual or physical Push-Button-Event being assigned to a first network node device of the other network node devices, being authenticated for the network, and send to further second authenticated network node devices of the other network node devices, (b) 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 designed such that they (b1) run a Push-Button Configuration Protocol with a third network node device not being yet authenticated for the network, which is triggered by a second virtual or physical Push-Button-Event being assigned to the third network node device in order to authenticate the third network node device for the network, (b2) after finishing the authentication and due to a first Push-Button Configuration result message 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 and due to a first Push-Button Configuration result message being received from at least one of the other network node devices directly or indirectly via at least one of the rest 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 directly or indirectly via at least one of the rest 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 or received, are different to each other, a number of the first Push-Button Configuration result messages by counting is greater than 1. - View Dependent Claims (75, 76, 77, 78, 79, 80, 81, 82, 85, 86)
-
Specification