Configuration system for wireless communication networks - Patents.com

Abstract

The present application relates to a configuration system (100) for a wireless communication network (102), comprising at least one first communication device (104b) and at least one second communication device (104c). The at least one first and second communication devices (104b, 104c) belong to a plurality of communication devices (104, 104a, 104b, 104c, 104d). Each communication device (104, 104a, 104b, 104c, 104d) of the plurality of communication devices is a wireless node device configured to provide bidirectional wireless communication with at least one of the plurality of communication devices. After receiving (220) the contents of network persistent configuration data (CO) from a communication device (104a) belonging to the plurality of communication devices and storing (222) the received contents of the configuration data, each first communication device (104b) is configured to periodically broadcast (224) within the network a configuration data description (DE) including a version identifier (VE) of the configuration data to indicate the capability of that first communication device to transmit (228) upon request the stored contents of the configuration data matching the version identifier.

Description

[Technical field]

[0001] The present application relates generally to configuration systems for wireless communication networks. [Background technology]

[0002] Wireless mesh networks require a variety of network-wide configuration data, such as device and connection management data. The configuration data is used, for example, to configure communication protocols, application layers, or both. The configuration data originates from outside the mesh network and is typically configured from back-end systems located outside the mesh network.

[0003] The configuration data can be sent as an unsolicited push message to the mesh network via the gateway device and its mesh interface. A routed or broadcast approach can be used to communicate within the mesh network, with each node repeating a message containing the configuration data multiple times.

[0004] The unsolicited push method has certain drawbacks, such as, for example, that messages may be lost in a multi-hop path due to bad links, and that the gateway device may not be aware of such losses. This drawback of bad links can be mitigated by end-to-end acknowledgement messages and retransmissions. In addition, nodes may not be constantly connected, for example, due to temporary loss of connectivity caused by link disconnection, rerouting, or other network maintenance tasks, thereby resulting in loss of downlink messages for these nodes. This connectivity drawback can be mitigated by long buffering times for messages and end-to-end acknowledgement messages and retransmissions.

[0005] The configuration data can also be configured via solicited polling messages, where a node requests the configuration data from the gateway device in a solicited multi-hop polling method or from a neighboring node in a solicited single-hop polling method. The gateway device or neighboring node responds with a message containing the configuration data. The gateway device can ask the backend for the configuration data or can use a locally stored copy of the configuration data to respond to requests from the mesh network in a solicited multi-hop method.

[0006] The unsolicited push method and the solicited polling method are typically used in combination, for example, the unsolicited push method is used when configuration is updated to nodes in the mesh network, and the solicited polling method is used when a new node joining the mesh network obtains configuration data.

[0007] The solicited multi-hop polling method has drawbacks such as requiring multi-hop communication in the multi-hop routing path, consuming power and bandwidth resources of multiple nodes in the mesh network, and causing load on a large area of ​​the network, whereas the solicited single-hop polling method requires an unsolicited push method to update configuration data. Summary of the Invention [Problem to be solved by the invention]

[0008] The object of the present invention is to obviate the above-mentioned drawbacks of known configuration solutions and to provide an efficient and robust method for distributing configuration data to node devices in a wireless mesh network, which is also versatile and reliable, independent of the actual content of the distributed configuration data.

[0009] The object of the invention is achieved by providing a configuration system, a wireless communication device, a configuration method, a computer program and a computer readable storage medium as set forth in the independent claims.

[0010] Embodiments of the invention are defined by a configuration system, a wireless communication device, a configuration method, a computer program and a computer readable medium as set forth in the independent claims. [Means for solving the problem]

[0011] A configuration system for a wireless communication network comprises at least one first communication device and at least one second communication device, the at least one first and second communication devices belonging to a plurality of communication devices, each communication device of the plurality of communication devices being a wireless node device configured to provide bidirectional wireless communication with at least one of the plurality of communication devices, after receiving content of network persistent configuration data from a communication device belonging to the plurality of communication devices and storing the received content of the configuration data, each first communication device is configured to periodically broadcast in the network a configuration data description including a version identifier of the configuration data to indicate an ability of the first communication device to transmit, upon request, a stored content of the configuration data matching the version identifier.

[0012] A first configuration method for a wireless communication network includes presenting at least one first communication device and at least one second communication device belonging to a plurality of communication devices operating as wireless node devices. The method further includes providing, by each communication device of the plurality of communication devices, bidirectional wireless communication with at least one of the plurality of communication devices. The method further includes receiving content of network persistent configuration data from communication devices belonging to the plurality of communication devices, and after storing the received content of configuration data, periodically broadcasting, by each first communication device, a configuration data description including a version identifier of the configuration data in the network to indicate an ability of the first communication device to transmit, upon request, stored content of the configuration data matching the version identifier.

[0013] A wireless communication device for distributing configuration data in a wireless communication network comprises a controller and a radio communication unit for operating as a wireless node device in the configuration system described above. The radio communication unit is configured to provide bidirectional wireless communication with at least one of the plurality of communication devices. After receiving content of network persistent configuration data from other communication devices of the plurality of communication devices and storing the received content of the configuration data, the radio communication unit is configured to periodically broadcast in the network a configuration data description including a version identifier of the configuration data to indicate an ability of the communication device to transmit, upon request, stored content of the configuration data matching the version identifier.

[0014] A second configuration method for distributing configuration data in a wireless communication network includes providing, by a wireless communication unit of a wireless communication device operating as a wireless node device, bidirectional wireless communication with at least one of a plurality of communication devices, the method further including, after receiving content of network persistent configuration data from other communication devices belonging to the plurality of communication devices and storing the received content of the configuration data, periodically broadcasting, by the wireless communication unit, a configuration data description including a version identifier of the configuration data into the network to indicate an ability of the communication device to transmit, upon request, stored content of the configuration data matching the version identifier.

[0015] The computer program includes instructions, which when the computer program is executed by a computer conforming to the above device, cause the computer to perform at least the steps of the second method above.

[0016] A tangible, non-volatile computer readable medium contains a program consistent with the computer program described above.

[0017] Embodiments are described below with reference to the following drawings: [Brief description of the drawings]

[0018] [Figure 1] A configuration system in a wireless communication environment is presented. [Figure 2A] A flow chart of the configuration method is presented. [Figure 2B] A flow chart of the configuration method is presented. [Figure 3A] 1 presents an exemplary format of information elements for configuration data description and content messages. [Figure 3B] 1 presents an exemplary format of information elements for configuration data description and content messages. [Figure 3C]1 illustrates an exemplary format of an information element for a configuration data description and content message. [Figure 4] An operational portion of a wireless radio communication device is presented. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0019] FIG. 1 presents a configuration system 100 operating in a wireless communication environment.

[0020] The environment comprises a wireless radio communication network (system) 102 comprising a plurality of wireless radio communication devices (nodes) 104. The devices 104, for example, in the presented environment, operate in the same geographic region and on the same spectrum. The use of the same spectrum enables two-way wireless communication between the devices 104 in the network 102, such that a radio transmission transmitted by one device 104 may be received by another device 104 and vice versa.

[0021] The system 100 may be applied to any wireless radio communication network 102 that uses packet transmission in communication. The system 100 may be applied to a wireless communication network 102 that complies with the Digital European Cordless Telecommunications (DECT-2020) standard. Some non-limiting examples to which the system 100 may be applied may include, but are not limited to, a Bluetooth Low Energy (BLE) mesh network, a ZigBee network, a Thread network, a Public Land Mobile Network (PLMN), a wireless local area network (WLAN), a low power wide area network (LPWAN), a cellular-based local area network, a cellular network, a wireless multi-hop network, or a wireless mesh network, such as a wireless sensor network, and / or any other wireless network.

[0022] The devices 104 may be capable of receiving transmissions using one wireless technology, e.g., BLE transmissions or WLAN transmissions, all of which are from the same network 102. However, at least one of the devices 104, e.g., one, two, three, four, or more devices, may be capable of receiving transmissions using at least two wireless technologies, e.g., BLE transmissions and WLAN transmissions, all of which are from the same network 102.

[0023] Some of the devices 104 are referred to below as devices 104a, 104b, 104c, and 104d to explicitly describe single-hop and multi-hop communication between the devices 104. However, these devices 104a, 104b, 104c, and 104d correspond to the devices 104.

[0024] The DECT-2020 standard is a radio access technology developed by ETSI. DECT-2020 supports massive machine type communication (mMTC) and ultra-reliable low latency communication (URLLC). At the physical (PHY) layer, the main technical components of DECT-2020 are Orthogonal Frequency Division Multiplexing (OFDM), Adaptive Modulation and Coding Scheme (MCS), modern channel coding methods (Turbo, LDPC, convolutional coding), HARQ for both scheduled and contention-based transmission, and support for multi-antenna transmission using different multiple-input and multiple-output (MIMO) streams. On the medium access (MAC) layer and from the system aspect, the main technical components of DECT-2020 are support for a large number of Internet of Things (IoT) sensors, actuators, and other industrial applications, support for mesh network topology, support for very low latency URLLC communication (a typical application could be wireless microphones), operation at license-exempt frequencies, and support for multiple overlapping uncoordinated networks with cognitive radio capabilities to share spectrum resources among multiple networks.

[0025] The system 100 is used to obtain and distribute (disseminate) network persistent configuration data (Network Persistent Data (NPD), configuration data) CO, which includes data items for different configuration and management entities in devices 104 in the network 102.

[0026] The system 100 is mainly described using three devices 104a, 104b, 104c belonging to the system 100 and operating within a network 102, forming a group of devices 104a, 104b, 104c. The network 102 may also comprise a number of other devices 104, which also participate in forming the group, where the group comprises the devices 104, 104a, 104b, 104c.

[0027] As explained above, each device 104 is capable of providing bidirectional wireless communication with at least one other device 104 by means of its wireless communication unit 436. This means that each device 104 may operate as a transmitter, as a receiver, or as a transceiver, when it is capable of transmitting at least one message DE, RE, CO to other devices 104 in the network 102 and receiving at least one message DE, RE, CO from other devices 104.

[0028] The system 100 also comprises at least one gateway device 105, e.g., one, two, three, four, or more gateway devices. Each gateway device 105 acts as a gateway between the network 102 and other external networks 106 (e.g., the Internet) and distributes data in and out of the network 102. Each gateway device 105 communicates with at least one sink device (node) 104a, e.g., one, two, three, four, or more sink devices, and each sink device 104a acts as a wireless interface for the gateway device 105 in the network 102. Each sink device 104a may be physically connected to the gateway device 105 or may be located separately in different parts of the network 102. If the gateway 105 comprises several sink devices 104a, one may be connected to the gateway device 105 and the others may be located separately in different parts of the network 102.

[0029] The sink device 104a is a fixed router device (router), while the other node devices 104 can operate in different fixed or non-fixed roles in the network 102. The other devices 104 in the system 100 are router devices and non-router devices (non-routers), depending on whether the device 104 needs to participate in data forwarding. One method for selecting router and non-router roles may follow, for example, the method described in U.S. Patent Publication No. 10,499,264.

[0030] Each router device 104 maintains connectivity for the system 100 and routes (forwards) data for other devices 104 when necessary. Each non-router node 104 can provide bidirectional communication to transmit its own data and receive data directed to it as well as sink and router devices 104, but the non-router devices 104 do not route data for other devices 104. Each of the devices 104 can operate at least as a router or a non-router device.

[0031] The system 100 comprises devices 104, and therefore, due to the wide range of distances between the devices 104 and limited wireless ranges, not all devices 104 can communicate directly with the sink device 104 (gateway device 105), thereby necessitating the use of multi-link (multi-hop) communication between each device 104 and the sink device 104.

[0032] 2A presents a configuration method 208 for obtaining and distributing (first) configuration data CO in the above described system 100. Although the method 208 is described using one backend system (device) having one gateway device 105 and one sink device 104a, the system 100 may additionally have at least one other backend system, e.g., one, two, three, four or more other backend systems, each of which may communicate with at least one gateway device 105 including the one gateway device 105. The system 100 may additionally comprise at least one other gateway device 105, e.g., one, two, three, four or more other gateway devices, each of which may comprise at least one sink device 104a, e.g., one, two, three, four or more sink devices including the one sink device 104a.

[0033] The back-end system may be an external control system, a monitoring system, or both, implemented in a high-computing computer. Alternatively, the back-end system may be lightly implemented in a mobile device (phone) that communicates with the gateway device 105 or directly with one of the devices 104, 104a, 104b, 104d by using the wireless interface of the network 102 or another wireless interface, for example a BLE or radio frequency identification (RFID) interface for delivering the contents of the configuration data CO to the network 102. In such an arrangement, the mobile device may also have a connection to a high-computing computer, thereby acting as the gateway device 105.

[0034] In step 210, the gateway device 105 in the system 100 receives a message from outside the network 102, the message including the contents of the configuration data CO. The configuration data CO is configured by a back-end system of the system 100 located in the external network 106. If the system 100 has several back-end systems, each back-end system manages a dedicated operation or a dedicated application of the network 102 and transmits operation or application related configuration data CO to the network 102.

[0035] The configuration data CO may include, for example, Internet Protocol version 6 (IPv6) configuration information, IPv6 over Low Power Wireless Personal Area Network (6LoWPAN) configuration information, Dynamic Host Configuration Protocol (DHCP) information, Domain Name System (DNS) information, service, server, or both information, public keys or digital certificates, software update control information, software images, or software related metadata, security keys, security key lists, or security key related metadata, or other configuration or management information used by a communications protocol (stack), e.g., transmission configuration information such as the maximum allowed transmit (TX) power in the network 102, applications, or other internal components of the communications device 104.

[0036] The IPv6 configuration information includes, for example, at least one IPv6 network or subnet prefix of variable length. The prefix information provides the communication device 104 with information of prefixes used in the network 102 (on-link or on-mesh prefixes) and prefixes used for IPv6 stateless address autoconfiguration (SLAAC). The prefix information may be extended with at least one of an on-link flag, an autonomous address configuration flag, a valid lifetime field, and a preferred lifetime field associated with the prefix. The IPv6 configuration may further include, for example, information regarding a maximum transmission unit (MTU) to be used by the Internet Protocol (IP) layer.

[0037] The 6LoWPAN configuration information includes, for example, at least one IPv6 header compression context, where a single context includes a context identifier (CID) and a context prefix, which may be a variable-length IPv6 network or subnet prefix or a full IPv6 address. In addition, the context may include a compression flag, a valid lifetime field associated with the particular CID and prefix, or both.

[0038] The DHCP information may include, for example, at least one DHCP server address, availability information of an IPv6 address via DHCP (managed address configuration flag), availability information of other configuration information via DHCP (other configuration flags), or other DHCP related information.

[0039] The DNS information includes, for example, at least one DNS server address, at least one DNS AAAA record that maps a hostname to an IPv6 address, and at least one other DNS related content or records.

[0040] The IPv6 configuration, 6LoWPAN configuration, DHCP, and DNS information may be in a format specified in the relevant Internet Standards and Requests for Comments (RFCs), or in another format, eg, a size-optimized format.

[0041] The public keys or digital certificates include, for example, at least one of: at least one root or certification authority (CA) certificate, at least one intermediate certificate or certificate chain, and at least one leaf certificate, for example, at least one of a DTLS client, a TLS client, a server certificate, and a code signing certificate. The information may be in a format specified in relevant Internet standards and requests for comments (RFCs), for example, X.509, or in another format, such as a size-optimized format.

[0042] The service and server information includes, for example, at least one server address, at least one host name, at least one service UDP port, at least one TCP port, at least one service identifier (ID), e.g., at least one name for identifying at least one of the application servers and services, and device management servers and services.

[0043] The software update control information may include, for example, when enabling software or firmware to be distributed, enabled for use, or both, in the network 102 and communication device 104, at least one of the versions of the software or firmware to be distributed over the network 102, the time when the new software or firmware should be used, and other identifiers of the software or firmware, such as a cyclic redundancy check (CRC) or a message integrity code (MIC).

[0044] A software image may, for example, include at least one software or firmware image to be distributed to and used at some point in network 102. Additionally, a software image may include the software or at least one image in a clear or encrypted format, and metadata, such as at least one of the following: software or firmware version, encryption method, software signing method and signature, and MIC. Additionally, a software image may include software or firmware for at least one of applications, communication protocols, and other components in communication device 104.

[0045] The security key or security key list may include, for example, at least one security key for protecting network communications within the network 102, at least one security key for protecting end-to-end communications, for example, from the communication device 104 to an external backend system, at least one application security key, and metadata, for example, at least one of a key index, a key rotation policy, or a time to use a new key, and key expiration information.

[0046] The configuration data CO may be in plaintext, encrypted, or partly in plaintext and partly encrypted, and may be protected by at least one digital signature, by at least one MIC, or by both.

[0047] The backend system sends the configuration data CO unsolicited without any request from the gateway device 105, from one of the devices 104, 104a, 104b, 104d via the gateway device 105, or directly from one of the devices 104, 104a, 104b, 104d. Alternatively, the backend system may solicit the configuration data CO in response to a request message sent by the gateway device 105, by one of the devices 104, 104a, 104b, 104d via the gateway device 105, or directly by one of the devices 104, 104a, 104d.

[0048] In step 212, after receiving the configuration data CO, the sink device 104a, by its controller 430, stores the contents of the configuration data CO in its memory 434, and enables the stored configuration data CO to be distributed upon request. The sink device 104a then identifies, by its controller 430, whether the contents of the received configuration data CO fully, partially, or completely includes the associated payload (part) therefor, and employs, by its controller 430, the identified associated payload of the received configuration data CO, if present.

[0049] In addition, the gateway device 105 may receive another (second) message including the content of another configuration data CO from another backend system outside the network 102. The configuration data CO and the content of the other configuration data CO are related to different purposes. After receiving the other configuration data CO, the sink device 104a, by its controller 430, stores the content of the other configuration data CO in the memory 434 for distribution upon request, and identifies by its controller 430 whether the content of the other configuration data CO includes the associated payload completely, partially, or not at all. The sink device 104a then adopts the identified associated payload of the other configuration data CO, if it exists, by its controller 430. When the sink device 104a receives multiple different configuration data CO for different purposes, it operates in the same manner as in the case of a single configuration data CO in the relevant steps 212, 214, 215, 216, 217, 218, 220 of the method 208, as described below, thereby allowing the system 100 to distribute multiple different configuration data CO in parallel from each sink device 104a (local source).

[0050] In addition, the gateway device 105 may include at least one other sink device 104a configured to distribute content of different (third) configuration data within the network, similar to the sink device 104a and another sink device 104a.

[0051] The sink device 104a then generates, by its controller 430, a description DE of the configuration data CO, including a version identifier VE that identifies the (new) version of the configuration data CO, to indicate the availability of the configuration data CO.

[0052] In addition, the generated configuration data description DE may include a source identifier SO of the configuration data CO that identifies a source of the configuration data CO, e.g., the address of the sink device 104a that distributes the configuration data CO. The source identifier SO may locally specify each sink device 104a that distributes the configuration data CO to the network 102, e.g., by the device address of the sink device 104a.

[0053] In addition, the sink device 104a includes, via its controller 430, a configuration data description DE as part of the beacon message.

[0054] A beacon message contains information about devices 104 in the network 102 and is typically broadcast to all devices 104 within wireless range. In this method 208, each device 104 acting as a sink device or a router device is configured to transmit a beacon message.

[0055] 3A and 3B present an exemplary format of an information element IE for configuration data description DE, which is included in the beacon message in this method and in the following related method steps.

[0056] The information element IE comprises at least a header field identifying the type of the information element, in this case a configuration data description DE, and at least a payload field identifying a version identifier VE that identifies whether the receiving device 104 of the configuration data description DE should request new content of the configuration data CO from the sending device 104 of the configuration data description DE. The version identifier VE may be, for example, a sequence number, a sequence identifier or any other identifier that identifies the version of the configuration data CO. The payload field may also identify a source identifier SO that identifies the source (origin, source address, source device) of the content of the configuration data CO.

[0057] Then, in step 212, the sink device 104a, acting in the example as a (local) source, periodically broadcasts (sends) by its wireless communication part 436 a beacon message including the configuration data description DE in order to notify (announce) upon demand within the system 100 that the stored configuration data CO is available and, when necessary, simultaneously to initiate upon demand association with other devices 104, 104b, 104c, 104d.

[0058] In step 214, the (first) device 104b, acting in this example as a router device, receives the broadcasted beacon message by its wireless communication unit 436. The configuration data description DE may also be received by other devices 104 in the network 102, so that the device 104b is not just a receiver, but one of multiple receiving devices 104. In either case, each receiving device 104, 104b that is a router device operates independently and similarly according to the following communication between the devices 104a, 104b. The operation of the non-router devices 104, 104b will be described later.

[0059] In step 215, the device 104b identifies, by its controller 430, from the received configuration data description DE, whether the device 104b lacks a stored version identifier VE, meaning that the device 104b does not have configuration data CO, or its stored version identifier VE is different from the version identifier VE in the beacon message, meaning that the device 104b has an old version of the configuration data CO. In addition, if the received message contains a source identifier SO, the device 104b also identifies, by its controller 430, whether the device 104b lacks a stored source identifier SO, meaning that the device 104b does not have stored configuration data CO, or the stored source identifier SO is different from the source identifier SO in the beacon message. The identification is performed by comparing the respective stored identifiers VE, SO in the memory 434 of the device 104b with the received identifiers VE, SO, if the device 104b has the respective stored identifiers VE, SO.

[0060] If the version identifier VE has not changed, or if the beacon message also contains a source identifier SO, and both identifiers VE, SO have not changed based on the identification, then the device 104b does not need to update its configuration data CO and continues to operate as described above in step 214.

[0061] If the identification in step 215 indicates that the version identifier VE has changed or is missing, or, when the beacon message also contains a source identifier SO, indicates that at least one of the identifiers VE, SO has changed or is missing, the method 208 continues at step 216 or step 218 depending on whether the device 104b is part of the network 102 and whether configuration data distribution is included (integrated) in the association communication (procedure).

[0062] In step 216, if device 104b is not part of network 102 and association and distribution communications are separate, device 104b generates an association request (message) via its controller 430 to request association with network 102 (and sink device 104a) and transmits the association request to sink device 104a via its wireless communication unit 436.

[0063] In step 217, sink device 104a receives the association request via its wireless communication unit 436 and generates an association acknowledgement response (message) via its controller 430. Sink device 104a then transmits the generated response via its wireless communication unit 436 to device 104b to complete the association between devices 104a, 104b.

[0064] Alternatively, the association procedure between the devices 104a, 104b may include more communications than those described above when the association procedure is completed, which also pertains to other association procedures described below.

[0065] In step 218, if the device 104b is already part of the network 102, the device 104b that lacks the configuration data CO, has an older version of the configuration data CO, or has a different source identifier SO generates, by its controller 430, a configuration data request RE to request the actual content of the available configuration data CO from the sink device 104a. Alternatively, the configuration data distribution may be included in the association communication, such that, in step 218, if the device 104b is not part of the network 102, the device 104b may include, by its controller 430, the generated configuration data request RE as part of the association request.

[0066] Device 104b then transmits, via its wireless communication unit 436, the request message generated in step 218 to sink device 104a.

[0067] In step 220, the sink device 104a receives, via its wireless communication unit 436, a configuration data request RE or an association request including the configuration data request RE from the device 104b.

[0068] When sink device 104a receives a configuration data request RE, it generates, via its controller 430, a message including the contents of the configuration data CO to send the actual contents of the configuration data CO as a response to device 104b. Alternatively, when sink device 104a receives an association request, it includes, via its controller 430, the contents of the configuration data CO as part of an association acknowledgement.

[0069] Alternatively, if the association procedure involves more communications than an association request and an association acknowledgement as described above, the configuration data request RE may be included as part of the association request or other message belonging to the association procedure and correspondingly the configuration data CO may be included as part of the association acknowledgement or other response message belonging to the completion of the association procedure, which also relates to the other association procedures described later.

[0070] FIG. 3C presents an exemplary format of the structure of an information element IE for configuration data content CO, which is included in a dedicated response message or a response message pertaining to the completion of the association procedure in this method and in the following related method steps.

[0071] The structure includes several Information Element IEs, one of which is dedicated to a configuration data description DE and has similar options for fields as described above, the rest of the Information Element IEs are Payload Information Element IEs, each of which includes a header field that identifies the type of information element, in this case the content and format of the payload, and a payload field that contains the actual data content of the configuration data CO for a particular use A, B, C in the receiving device 104.

[0072] The sink device 104a then transmits the response message generated in step 220 to the device 104b via its wireless communication unit 436 to transmit the actual contents of the configuration data CO, and if the contents of the configuration data CO are included in the association confirmation response, completes the association of the device 104b to the network 102 (between the devices 104a, 104b).

[0073] In addition, in step 220, the device 104b receives, by its wireless communication part 436, a response message from the sink device 104a, which in any case includes the actual content of the configuration data CO.

[0074] If the size of the configuration data description DE and payload information element IE that the sending device 104 needs to include in the response message may be larger than the maximum payload size of the communication protocol stack used, the sending device 104 segments (fragments) and reassembles the response message so that the contents of the configuration data CO are transmitted in multiple response messages to the receiving device 104, and the receiving device 104 needs to send a status message after receiving each segmented response message.

[0075] If segmentation of the response message is required, the sending device 104 sends a first segmented response message including a segmentation information element IE, which indicates to the receiving device 104 that the contents of the configuration data CO will be sent in a subsequent segmented response message. After receiving the first segmented response message, the receiving device 104 sends a request message including a segmentation status information element IE indicating that the receiving device 104 has received a segmentation indication, to request the next segmented response message including the first portion of the contents of the configuration data CO.

[0076] The sending device 104 then sends a second segmented response message, where the second segmented response message includes the first portion of the content of the configuration data CO, an indication that this is the first portion of the content of the configuration data CO, and the number of subsequent portions of the content of the configuration data CO that the sending device 104 is still sending. After receiving the first portion of the content of the configuration data CO, the receiving device 104 sends a second request message indicating that it has received the first portion of the content of the configuration data CO.

[0077] The exchange of segment response and request messages continues until the sending device 104 sends a final segmented response message containing the last portion of the content of the configuration data CO and an indication that it is the last portion, and the receiving device 104 has received all portions of the segmented content of the configuration data CO.

[0078] The exchange of segment response and request messages ensures that all segmented response messages are received and that none are dropped.

[0079] Regardless of the message format used, at the latest, in step 222, the device 104b, now part of the network 102, by its controller 430 identifies whether the content of the received configuration data CO includes the associated payload therefor completely, partially or not at all. Since the device 104b operates as a router device, the device 104b stores all the content of the received configuration data CO in its memory 434 by its controller 430, so that the stored configuration data CO can be distributed on request. If the device 104b was operating as a non-router device, the device 104b would only store the associated payload, if any. Alternatively, the device 104b may store all the content of the received configuration data CO, even if the device 104b was operating as a non-router device. The device 104b then employs, by its controller 430, the identified associated payload of the received configuration data CO, if any, in the same manner as the sink device 104a in step 212.

[0080] In step 224, the device 104b generates, via its controller 430, a configuration data description DE that includes the stored version identifier VE and, if present, the stored source identifier SO. In addition, the device 104a, via its controller 430, includes the configuration data description DE as part of the beacon message, similar to the sink device 104a in step 212.

[0081] Then, in step 224, the device 104b periodically broadcasts, by its wireless communication unit 436, a beacon message including the configuration data description DE in order to notify upon request that the stored configuration data CO is available and, when necessary, simultaneously to initiate upon request association with other devices 104, 104c, 104d, similar to the sink device 104a in step 212.

[0082] The (second) device 104c, acting in this example as a non-router device, receives the broadcasted beacon message by its wireless communication unit 436, similar to the device 104b in step 214. The device 104c may also act as a router device. The configuration data description DE may also be received by the other devices 104. Again, in both cases, each receiving device 104, 104c that is a non-router device operates independently and similarly according to the following communication between the devices 104b, 104c, and each receiving device 104, 104c that is a router device operates independently and similarly according to the above-described communication between the devices 104a, 104b.

[0083] Then, in step 224, the device 104c identifies, by its controller 430, whether the device 104c lacks a version identifier VE or whether the stored version identifier VE is different from the version identifier VE in the beacon message. In addition, if the beacon message includes a source identifier SO, the device 104c also identifies, by its controller 430, whether the device 104c lacks a stored source identifier SO or whether the stored source identifier SO is different from the source identifier SO in the beacon message. The identification is performed similarly to the device 104b in step 215.

[0084] If the identifiers indicate that the version identifier VE has not changed, or if the beacon message includes a source identifier SO and both identifiers VE, SO have not changed, device 104c does not need to update its configuration data and continues to operate as described above.

[0085] If the version identifier VE has changed or is missing, or if at least one of the identifiers VE, SO has changed or is missing when the beacon message also contains a source identifier SO, the method 208 continues at step 225 or step 227 depending on whether the device 104c is part of the network 102 and whether configuration data distribution is included in the association communication.

[0086] In step 225, if device 104c is not part of network 102 and association and distribution communications are separate, device 104c generates, by its controller 430, an association request to request device 104b to associate with network 102, and transmits, by its wireless communication unit 436, the association request to device 104b. Device 104b then receives, by its wireless communication unit 436, the association request.

[0087] In step 226, the device 104b generates, by its controller 430, an association acknowledgement response and transmits, by its wireless communication unit 436, the response to the device 104c to complete the association between the devices 104b, 104c.

[0088] In step 227, if the device 104c is already part of the network 102, the device 104c that lacks the configuration data CO, has an old version of the configuration data CO, or has a different source identifier SO, generates, by its controller 430, a configuration data request RE to request the actual contents of the available configuration data CO from the device 104b, similar to the device 104b in step 218. Alternatively, the configuration data distribution may be included in the association communication, and if the device 104c is not yet part of the network 102, the device 104c may include, by its controller 430, the generated configuration data request RE as part of the association request.

[0089] Device 104c then transmits, via its wireless communication unit 436, the request message generated in step 227 to device 104b, similar to device 104a in step 218.

[0090] In step 227, the device 104b receives, by its wireless communication unit 436, a configuration data request RE or an association request including the configuration data request RE from the device 104c, similar to the sink device 104a in step 220.

[0091] When device 104b receives the configuration data request RE, it generates, by its controller 430, a message including the contents of the configuration data CO to send the actual contents of the configuration data CO to device 104c. Alternatively, when device 104b receives the association request, it includes, by its controller 430, the contents of the configuration data CO as part of the association acknowledgement, similar to sink device 104a in step 220. In either case, device 104b independently sends the contents of the configuration data CO to device 104c without further requesting the contents of the configuration data CO from sink device 104a.

[0092] Then, in step 228, device 104b sends the response message generated in step 227 to device 104c via its wireless communication unit 436 to transmit the actual content of the configuration data CO, and if the content of the configuration data CO is included in the association confirmation response, completes the association between devices 104b, 104c, similar to sink device 104a in step 220.

[0093] Additionally, in step 228, device 104c receives, by its wireless communication unit 436, a response message from device 104b in any case including the actual content of the configuration data CO. Alternatively, if necessary, the actual content of the configuration data CO can be communicated by an exchange of segmented response and request messages as described above.

[0094] At the latest, the device 104c, now part of the network 102, by its controller 430 at least identifies whether the content of the received configuration data CO includes an associated payload therefor and by its controller 430 stores the identified associated payload of the received configuration data CO, if any, in its memory 434. Alternatively, the device 104c by its controller 430 stores all the content of the received configuration data CO, similar to the device 104b in step 222. The device 104c then employs the identified associated payload of the received configuration data CO by its controller 430.

[0095] Device 104c may change its role as a router device, and if device 104c has already stored all the contents of configuration data CO, device 104c may generate a configuration data description DE by its controller 430 and broadcast a beacon message including the configuration data description DE by its wireless communication unit 430, similar to device 104b in step 224.

[0096] When device 104c receives the configuration data description DE in step 224, if device 104c is already operating as a router device, router device 104c will have stored all the contents of the received configuration data CO as described above, and may generate the configuration data description DE and broadcast a beacon message including the configuration data description DE, similar to device 104b in step 224.

[0097] In either case, whether device 104c has changed its role as a router device or is already operating as a router device, device 104c may independently transmit the stored contents of the configuration data CO to another device 104 that sent a configuration data request RE to device 104c without further requesting the contents of the configuration data CO from device 104b.

[0098] Alternatively, if the device 104c acting as a non-router device does not have all the stored contents of the configuration data CO, and another device 104 requests the configuration data CO from the device 104c by a configuration data request RE, the device 104c generates a configuration data request RE by its controller 430 to request the contents of the configuration data CO from the device 104b, similar to step 227. The device 104b transmits the stored contents of the configuration data CO to the device 104c in response, similar to step 228, and the device 104c stores all the received contents of the configuration data CO. The device 104c then transmits the stored contents of the configuration data CO to the requesting device 104 by its controller 430.

[0099] 2B presents the principle of multi-hop communication. Even if the above description is mainly made by referring to the devices 104a, 104b, 104c, each message, for example, configuration data description DE, broadcast by the single device 104a can be received by multiple node devices, including the device 104b. Thus, the device 104b comprises at least one node device, for example, one, two, three, four or more node devices, each of which communicates independently and similarly with the device 104a according to the principles of mesh networks, even if the communication is described as being performed between the device 104a and the single device 104b.

[0100] The same also applies to each message broadcast by a single device 104b that may be received by multiple node devices, including device 104c, and to the communication between device 104b and single device 104c. This means that device 104c also includes at least one node device, for example, one, two, three, four, or more node devices, and device 104b may communicate with multiple node devices by independent communication with each of the node devices. Of course, the same also applies to each message broadcast by a single device 104c that may be received by multiple node devices, including other devices 104, and to the communication between device 104c and single other device 104.

[0101] Correspondingly, the same concerns each message broadcast by a single other device 104 that can be received by multiple node devices, including a second other device 104, and the communication between the other device 104 and the single second other device 104. Each second other device 104 then continues the automatic distribution of each message through the network 102 according to the multi-hop principle.

[0102] FIG. 4 presents devices 104 (104a, 104b, 104c, 104d) capable of communicating within the network 102 and performing the relevant features (steps) of the configuration method 208, as described above.

[0103] The device 104 comprises a controller (control portion) 430 that controls the operation of its portions 432, 434, 436, 438, 440 such that the device 104 operates as described above.

[0104] The controller 430 includes a processor 432 that executes operator-initiated instructions and / or computer program-initiated instructions and processes data to execute applications. The processor 432 may include at least one processor, for example, one, two, three, four, or more processors.

[0105] The controller 430 also includes a memory (memory portion) 434 for storing and maintaining data. The data can be instructions, computer programs, and data files. The memory 434 includes at least one memory, for example, one, two, three, four, or more memories.

[0106] The device 104 also includes a wireless communication unit (wireless communication portion, data transfer machine) 436 and an antenna (antenna portion) 438, which are used by the controller 430 to transmit commands, requests, and data to at least one of the entities in the system 100, e.g., the devices 104, via the antenna 438. The wireless communication unit 436 also receives commands, requests, and data from at least one of the entities in the system 100, e.g., the devices 104, via the antenna 438. Communications between the wireless communication unit 436 of the device 104 and other entities in the system 100 are provided wirelessly via the antenna 438.

[0107] The device 104 also includes a power supply 440. The power supply 440 includes components for powering the device 104, such as a battery and a regulator.

[0108] The memory 434 stores at least a wireless communication application 442 for operating (controlling) the wireless communication unit 436 and a power supply application 444 for operating the power supply unit 440.

[0109] The memory 434 also stores a computer program (computer software, computer application) 448 which, when executed (run) by the controller 430 in a computer, e.g., the device 104, uses at least one of the portions 436, 438, 440 to perform at least the operations of the device 104 described in the context of the above figures.

[0110] The computer program 448 may be stored on a tangible, non-volatile computer readable storage medium, for example a Compact Disc (CD) or Universal Serial Bus (USB) type storage device.

Claims

1. A configuration system (100) for a wireless communication network (102), comprising: at least one first communication device (104b); at least one second communication device (104c); wherein the at least one first and second communication devices (104b, 104c) belong to a plurality of communication devices (104, 104a, 104b, 104c, 104d); each communication device (104, 104a, 104b, 104c, 104d) of the plurality of communication devices is a wireless node device configured to provide two-way wireless communication with at least one of the plurality of communication devices; after receiving (220) the content of network persistent configuration data (CO) from a communication device (104a) belonging to the plurality of communication devices and storing (222) the received content of the network persistent configuration data, each first communication device (104b) broadcasts (224) periodically within the wireless communication network in order to indicate the ability of the first communication device to transmit (228) a configuration data description (DE) including a version identifier (VE) of the network persistent configuration data in response to a request for the stored content of the network persistent configuration data that matches the version identifier; System.

2. The system according to claim 1, wherein the at least one first communication device is configured to receive (214) the broadcast configuration data description from the communication device before receiving the content of the network persistent configuration data from the communication device.

3. The system according to claim 1, wherein the communication device is a sink device (104a), and after receiving the content of the network persistent configuration data from outside the wireless communication network, the sink device is configured to store (210) the received content of the network persistent configuration data and operate as a source of the network persistent configuration data within the wireless communication network.

4. The system according to claim 3, wherein the sink device and at least one other sink device (104a) from a plurality of sink devices operate as a source of the network persistent configuration data, and the sink device belongs to the plurality of sink devices (104a) in the wireless communication network.

5. Receiving the content of another network persistent configuration data (CO) from outside the wireless communication network, storing the received content of the another network persistent configuration data, and then each sink device (104a) includes a version identifier (VE) of the another network persistent configuration data in another configuration data description (DE), and transmitting (214) the stored content of the another network persistent configuration data different from the content of the network persistent configuration data in response to a request from at least one of the plurality of communication devices. The system according to claim 3, configured to periodically broadcast (212) within the wireless communication network to indicate the ability of the sink device.

6. The system according to claim 1, wherein the at least one second communication device (104, 104c) is configured to receive (224) the broadcast configuration data description from one of the at least one first communication device.

7. After receiving the configuration data description, the at least one first communication device or the at least one second communication device determines whether the version identifier or source identifier (SO) of the network persistent configuration data is missing or changed when the source identifier is present in the configuration data description (215, 224). The system according to claim 1, configured to identify.

8. The at least one first communication device is configured to transmit (218) a network persistent configuration data request (RE) to the communication device, or if the at least one second communication device determines that when the source identifier is present in the received configuration data description, the version identifier or source identifier (SO) of the network persistent configuration data is missing, or when the source identifier is present in the received configuration data description, the version identifier or the source identifier has been changed, the system according to claim 1, wherein the system is configured to transmit (227) the network persistent configuration data request to one of the at least one first communication devices after indicating the identification.

9. The system according to claim 1, wherein the at least one first communication device or the second communication device is configured to transmit (218, 227) a network persistent configuration data request (RE) as part of a message belonging to an association procedure in accordance with the association with the wireless communication network.

10. In accordance with the completion of the association with the wireless communication network, when the at least one first communication device transmits the network persistent configuration data request, the content of the network persistent configuration data is transmitted (220) to the at least one first communication device as part of a response message belonging to the association procedure, or when the at least one second communication device transmits the network persistent configuration data request, the system according to claim 8, wherein the at least one first communication device is configured to transmit (228) to the second communication device.

11. After receiving the content of the network persistent configuration data from one of the at least one first communication devices and storing the received content of the network persistent configuration data, each second communication device is configured to periodically broadcast in the wireless communication network in order to indicate the ability of the second communication device to transmit a configuration data description (DE) in response to a request for the stored content of the network persistent configuration data. The system according to claim 1.

12. The system according to claim 1, wherein the wireless communication network is a Digital European Cordless Telecommunications 2020-based network, a wireless multi-hop network, a wireless mesh network, a wireless local area network, a cellular-based local area network, a low-power wide area network, a cellular network, a wireless Bluetooth low energy-based wireless network, a ZigBee network, a Thread network, or a public land mobile network.

13. The system according to claim 1, wherein the network persistent configuration data includes at least one of Internet Protocol version 6 configuration information, IPv6 configuration information on a low-power wireless personal area network, Dynamic Host Configuration Protocol information, Domain Name System information, service and server information, at least one public key or digital certificate, software update control information, at least one software image, and at least one of software-related metadata, at least one security key, at least one security key list, and at least one of security key-related metadata, or other configuration information configured to be used by a communication device-related communication protocol, a communication device-related application, or other internal communication device-related components.

14. A configuration method (208) for a wireless communication network (102), comprising: presenting at least one first communication device (104b) and at least one second communication device (104c) belonging to a plurality of communication devices (104, 104a, 104b, 104c, 104d) operating as wireless node devices; providing, by each communication device (104, 104a, 104b, 104c, 104d) of the plurality of communication devices, two-way wireless communication with at least one of the plurality of communication devices; Receive (220) the content of the network persistent configuration data (CO) from a communication device (104a) belonging to the plurality of communication devices, store (222) the received content of the network persistent configuration data, and then, by each first communication device (104b), a configuration data description (DE) including a version identifier (VE) of the network persistent configuration data is transmitted (228) in response to a request for the stored content of the network persistent configuration data that matches the version identifier. A step of periodically broadcasting (224) within the wireless communication network to indicate the ability of the first communication device; A method including.

15. A wireless communication device (104b) for distributing network persistent configuration data (CO) within a wireless communication network (102), A controller (430); A wireless communication unit (436) for operating as a wireless node device, The wireless communication unit is configured to provide two-way wireless communication with at least one of the plurality of communication devices (104, 104a, 104c, 104d), Receive (220) the content of the network persistent configuration data (CO) from another communication device (104a) belonging to the plurality of communication devices, store (222) the received content of the network persistent configuration data, and then the wireless communication unit includes a version identifier (VE) of the network persistent configuration data. The configuration data description (DE) is configured to be periodically broadcast (224) within the wireless communication network to indicate the ability of the communication device to transmit (228) the stored content of the network persistent configuration data that matches the version identifier in response to a request. Wireless communication device.

16. A configuration method (208) for distributing network persistent configuration data (CO) within a wireless communication network (102), A step of providing two-way wireless communication with at least one of the plurality of communication devices (104, 104a, 104c, 104d) by a wireless communication unit (436) of a wireless communication device (104b) operating as a wireless node device; Receiving (220) the content of the network persistent configuration data (CO) from another communication device (104a) belonging to the plurality of communication devices, storing (222) the received content of the network persistent configuration data, and then periodically broadcasting (224) in the wireless communication network a configuration data description (DE) including a version identifier (VE) of the network persistent configuration data in response to a request for the stored content of the network persistent configuration data that matches the version identifier, in order to indicate the ability of the communication device to transmit (228). A configuration method including the above.

17. A computer program (446) including instructions, wherein when the computer program is executed by a computer (104b), the instructions cause the computer to execute at least the steps of the configuration method according to claim 16.

18. A tangible non-volatile computer-readable medium including the computer program (446) according to claim 17.

Images