From: "Brian Redding" <bredding@codeaurora.org>
To: "'Mike Tsai'" <Mike.Tsai@Atheros.com>,
"'Claudio Takahasi'" <claudio.takahasi@openbossa.org>
Cc: "'BlueZ development'" <linux-bluetooth@vger.kernel.org>
Subject: RE: [RFC] LE connections and advertising management
Date: Tue, 2 Nov 2010 15:23:29 -0500 [thread overview]
Message-ID: <000201cb7acb$d05ac330$71104990$@org> (raw)
In-Reply-To: <35B17FE5076C7040809188FBE7913F983F847B44A8@SC1EXMB-MBCL.global.atheros.com>
> [Claudio]
> Is it allowed duplicated UUIDs for the same primary service? We are
> not handling this right now.
> It seems that you already have a proprietary implementation ;-)
>
> [Mike Tsai] I think it is probably not allowed to duplicate
> characteristic within the same primary services. However, there may be
> duplicated primary services within a server or duplicated included
> service within a server, or same characteristic inside 2 different
> primary services. So I don't know if you have any mechanism to let
> GAttrib get the correct characteristic within all these duplicated
> services by just passing the 128 bits UUID?
The GATT places no limitation on multiple instances of characteristics or
services. The recommendation to profile writers when duplicate
characteristics exist within a service is that each characteristic has a
characteristic presentation descriptor that distinguishes each instance of
the characteristic. The same would apply to multiple instances of a
service. There are other methods to distinguish multiple instances of
services and characteristics including different UUIDs so there isn't a
single approach. The approach though is specified by the profile.
Brian
---
Brian A. Redding
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum
prev parent reply other threads:[~2010-11-02 20:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-25 12:53 [RFC] LE connections and advertising management Claudio Takahasi
2010-10-25 13:34 ` Anderson Lizardo
2010-10-25 17:11 ` Mike Tsai
2010-10-25 17:55 ` Claudio Takahasi
2010-10-25 18:16 ` Mike Tsai
2010-10-25 18:54 ` Claudio Takahasi
2010-10-25 19:27 ` Brian Redding
2010-10-26 2:51 ` Claudio Takahasi
2010-10-26 20:26 ` Brian Redding
2010-10-26 21:10 ` Mike Tsai
2010-10-27 1:01 ` Claudio Takahasi
2010-10-27 22:01 ` Mike Tsai
2010-11-02 20:23 ` Brian Redding [this message]
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='000201cb7acb$d05ac330$71104990$@org' \
--to=bredding@codeaurora.org \
--cc=Mike.Tsai@Atheros.com \
--cc=claudio.takahasi@openbossa.org \
--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).