From: "Michał Lowas-Rzechonek" <michal.lowas-rzechonek@silvair.com>
To: linux-bluetooth@vger.kernel.org
Subject: [PATCH BlueZ v7 2/3] mesh: Add documentation for Import() D-Bus API
Date: Wed, 31 Jul 2019 09:16:46 +0200 [thread overview]
Message-ID: <20190731071647.27217-3-michal.lowas-rzechonek@silvair.com> (raw)
In-Reply-To: <20190731071647.27217-1-michal.lowas-rzechonek@silvair.com>
This replaces previously specified ImportLocalNode() call
---
doc/mesh-api.txt | 57 +++++++++++++++++++++++++++++++++++-------------
1 file changed, 42 insertions(+), 15 deletions(-)
diff --git a/doc/mesh-api.txt b/doc/mesh-api.txt
index 7b62c0af4..255104ab6 100644
--- a/doc/mesh-api.txt
+++ b/doc/mesh-api.txt
@@ -151,16 +151,50 @@ Methods:
org.bluez.mesh.Error.InvalidArguments
org.bluez.mesh.Error.AlreadyExists,
- uint64 token ImportLocalNode(string json_data)
+ uint64 token Import(object app_root, array{byte}[16] uuid,
+ array{byte}[16] dev_key,
+ array{byte}[16] net_key, uint16 net_index,
+ dict flags, uint32 iv_index, uint16 unicast)
This method creates a local mesh node based on node
configuration that has been generated outside bluetooth-meshd.
- The json_data parameter is a full JSON representation of a node
- configuration file. The format must conform to the schema
- defined in "Mesh Node Configuration Schema" section. Any
- included token will be ignored in favor of a locally generated
- token value.
+ The app_root parameter is a D-Bus object root path of the
+ application that implements org.bluez.mesh.Application1
+ interface.
+
+ The uuid parameter is a 16-byte array that contains Device UUID.
+ This UUID must be unique (at least from the daemon perspective),
+ therefore attempting to call this function using already
+ registered UUID results in an error.
+
+ The dev_key parameter is the 16-byte value of the dev key of
+ the imported mesh node.
+
+ Remaining parameters correspond to provisioning data:
+
+ The net_key and net_index parameters describe the network (or a
+ subnet, if net_index is not 0) the imported mesh node belongs
+ to.
+
+ The flags parameter is a dictionary containing provisioning
+ flags. Supported values are:
+
+ boolean IVUpdate
+
+ When true, indicates that the network is in the
+ middle of IV Index Update procedure.
+
+ boolean KeyRefresh
+
+ When true, indicates that the specified net key
+ is in the middle of a key refresh procedure.
+
+ The iv_index parameter is the current IV Index value used by
+ the network. This value is known by the provisioner.
+
+ The unicast parameter is the primary unicast address of the
+ imported node.
The returned token must be preserved by the application in
order to authenticate itself to the mesh daemon and attach to
@@ -168,13 +202,10 @@ Methods:
permanently remove the identity of the mesh node by calling
Leave() method.
- It is an error to attempt importing a node with already
- registered Device UUID.
-
PossibleErrors:
org.bluez.mesh.Error.InvalidArguments,
- org.bluez.mesh.Error.AlreadyExists
- org.bluez.mesh.Error.NotFound,
+ org.bluez.mesh.Error.AlreadyExists,
+ org.bluez.mesh.Error.NotSupported,
org.bluez.mesh.Error.Failed
Mesh Node Hierarchy
@@ -1069,7 +1100,3 @@ Properties:
Uniform Resource Identifier points to out-of-band (OOB)
information (e.g., a public key)
-
-Mesh Node Configuration Schema
-==============================
-<TBD>
--
2.19.1
next prev parent reply other threads:[~2019-07-31 7:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-31 7:16 [PATCH BlueZ v7 0/3] Implement org.bluez.mesh.Network1.Import() D-Bus API Michał Lowas-Rzechonek
2019-07-31 7:16 ` [PATCH BlueZ v7 1/3] mesh: Extract read_* functions in mesh-config-json Michał Lowas-Rzechonek
2019-07-31 7:16 ` Michał Lowas-Rzechonek [this message]
2019-07-31 7:16 ` [PATCH BlueZ v7 3/3] mesh: Implement Import() D-Bus API of org.bluez.mesh.Network1 interface Michał Lowas-Rzechonek
2019-08-01 5:48 ` [PATCH BlueZ v7 0/3] Implement org.bluez.mesh.Network1.Import() D-Bus API Stotland, Inga
2019-08-01 20:28 ` Gix, Brian
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190731071647.27217-3-michal.lowas-rzechonek@silvair.com \
--to=michal.lowas-rzechonek@silvair.com \
--cc=linux-bluetooth@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).