Dear Dominique:
I suggest that we can consider to integrate WiNet framework into Tizen
3.0, could you please let me know the process of it? thanks in advance!
Regards,
Zhang Zhengguang
From: Zhang, Zhengguang
Sent: Wednesday, July 30, 2014 4:54 PM
To: [email protected]
Cc: Laperie, Andrei; [email protected]; [email protected];
[email protected]; [email protected]; PRADEEPKUMAR BELLARY; Liu,
Bingwei; Baptiste Durand; Zhu, Peter J; Xu, Martin; '[email protected]';
'[email protected]'; Le Foll, Dominique; Stephen Clymans
Subject: Tizen WiNet (WiFi & Network) Framework Version 0.1 is Released!
Hi, All
WiNet framework version 0.1 is released, and you can get the related source
codes(4 packages) from tizen.org(tizen_devel branch) now.
platform/core/connectivity/connman-lib
Platform/core/connectivity/winet-service
Platform/core/api/wifi
Platform/core/api/tethering
And the current status is:
Generally, it can support most of the interfaces of Tethering and WiFi
Station feature, for example:
WiFi Station: WiFi Power on/off, scan, connect/disconnect, get/set
ipv4, get/set proxy and so on.
Tethering: WiFi/Bluetooth/USB tethering power on/off,
get/set open/hidden mode, get/set passphrase/security type, tethering data
usage statistics and so on.
And the details are:
1. ConnMan lib layer:
Wrappers for ConnMan manager/technology/service have been done, so it can
support Tethering and WiFi Station feature completely.
2. WiNet service daemon layer:
It has added Tizen vconf support, ConnMan agent support, tethering data usage
staticstics support, WiFi work mode and scan mode support.
3. CAPI layer:
Most of the tethering and WiFi station CAPIs have been implemented, some others
will be supported in near future.
Next Step work plan:
1. Continue to optimize and bug fixing.
2. Continue to implement the CAPIs which are not supported by now.
3. Investigate Multi-user support in WiNet framework.
4. Combine WiFi P2P feature into WiNet framework basing on ConnMan-based
WiFi P2P solution.
Check it please, any suggestions, feel free to contact me.
Regards,
Zhang Zhengguang
From: Dev [mailto:[email protected]] On Behalf Of Zhang, Zhengguang
Sent: Friday, July 25, 2014 4:59 PM
To: Baptiste Durand
Cc: Laperie, Andrei;
[email protected]<mailto:[email protected]>;
[email protected]<mailto:[email protected]>;
[email protected]<mailto:[email protected]>;
[email protected]<mailto:[email protected]>;
[email protected]<mailto:[email protected]>; PRADEEPKUMAR
BELLARY; Liu, Bingwei
Subject: Re: [Dev] Tizen WiNet (WiFi & Network) Framework Prototype Version is
Released!
Hi, Durand
Please check my embedded comments below, correct me if I am wrong, thanks!
From: Baptiste Durand [mailto:[email protected]]
Sent: Friday, July 25, 2014 4:43 PM
To: Zhang, Zhengguang
Cc: Xu, Martin; Stephen Clymans;
[email protected]<mailto:[email protected]>;
[email protected]<mailto:[email protected]>; Laperie, Andrei;
[email protected]<mailto:[email protected]>;
[email protected]<mailto:[email protected]>;
[email protected]<mailto:[email protected]>; PRADEEPKUMAR
BELLARY; Liu, Bingwei
Subject: Re: [Dev] Tizen WiNet (WiFi & Network) Framework Prototype Version is
Released!
Hi Zang,
To clarify the situation,
As indicated to TDC NO apps can communicate directly with a deamon responsible
of a ressource.
In your case, All network CAPI should be managed by Winet Deamon.
Indeed, for use case related to Network interfaces configurations we should
delegate the User request to this deamon not connman to avoid collision request.
ConnMan can handle the incoming request itself to avoid collision, so maybe it
don’t need winet daemon to handle it.
In a same way as App Fw , we should introduce admin concept to allow
configuration changes for some user not for all.
IMHO， authority related issues are system level issues and should not be
handled in winet daemon, otherwise, we will need too many daemons to handle the
similar issues for different modules, right?
So All Ntwork CAPI should be managed by Winet deamon.
Thanks in advance to apply changes according to this.
Regards
Baptiste
2014-07-25 3:57 GMT+02:00 Zhang, Zhengguang
<[email protected]<mailto:[email protected]>>:
Hi, Stephen
For multiuser, we don’t think it need to be considered it in a dynamically
library, such as CAPI. For different users calling CAPI lie in different
processes.
So we think we only need to consider multiuser in the winet service daemon, and
user apps can talk to ConnMan directly.
Correct me if I am wrong, thanks!
Regards,
Zhang Zhengguang
From: Xu, Martin
Sent: Friday, July 25, 2014 12:49 AM
To: Stephen Clymans; [email protected]<mailto:[email protected]>;
Zhang, Zhengguang; '[email protected]<mailto:[email protected]>'
Cc: Laperie, Andrei;
'[email protected]<mailto:[email protected]>'; PRADEEPKUMAR
BELLARY; '[email protected]<mailto:[email protected]>';
Liu, Bingwei; Zhu, Peter J; TAESOO JUN; TAESUB KIM; Le Foll, Dominique;
[email protected]<mailto:[email protected]>
Subject: RE: [Dev] Tizen WiNet (WiFi & Network) Framework Prototype Version is
Released!
Hi:
Why user app can’t direly talk to ConnMan?
Ubuntu has integrate ConnMan. As a typical multi-user system. I do not know
they have this restriction.
From: Stephen Clymans [mailto:[email protected]]
Sent: Thursday, July 24, 2014 8:00
To: [email protected]<mailto:[email protected]>; Zhang, Zhengguang;
Xu, Martin; '[email protected]<mailto:[email protected]>'
Cc: Laperie, Andrei;
'[email protected]<mailto:[email protected]>'; PRADEEPKUMAR
BELLARY; '[email protected]<mailto:[email protected]>';
Liu, Bingwei; Zhu, Peter J; TAESOO JUN; TAESUB KIM; Le Foll, Dominique;
[email protected]<mailto:[email protected]>
Subject: Re: [Dev] Tizen WiNet (WiFi & Network) Framework Prototype Version is
Released!
Hello,
About the multiuser aspect the main idea is to link all CAPI function to the
Winet deamon in order to have only Winet deamon to communicate with connman
(and not directly user).
There will be a few more modifications but I could manage it when needed.
Regards,
Stephen
------- Original Message -------
Sender : Zhang,
Zhengguang<[email protected]><mailto:[email protected]>
Date : Jul 23, 2014 06:51 (GMT+05:30)
Title : RE: [Dev] Tizen WiNet (WiFi & Network) Framework Prototype Version is
Released!
Hi, Stephen
The current status of WiNet framework is:
We plan to release 0.1 version this week which will support most of the
functions of Tethering and WiFi station feature. And now we are focus on
implementing more CAPI basing on latest ConnMan lib and WiNet service daemon.
For multiuser, by our understanding, it don’t need to support it in CAPI
library, but we have taken it into account in WiNet service daemon during our
design and development. However, we are not clear how to test it yet.
For we are not multiuser expert, any suggestions on how to support/test it in
WiNet framework are really appreciated. Of course, any patches are also welcome.
Regards,
Zhang Zhengguang
From: Stephen Clymans [mailto:[email protected]]
Sent: Tuesday, July 22, 2014 10:48 PM
To: Xu, Martin; Zhang, Zhengguang;
'[email protected]<mailto:[email protected]>'
Cc: Laperie, Andrei;
'[email protected]<mailto:[email protected]>'; 'C S
BHARGAVA'; 'PRADEEPKUMAR BELLARY';
'[email protected]<mailto:[email protected]>'; Liu,
Bingwei; Zhu, Peter J; '[email protected]<mailto:[email protected]>';
???; Le Foll, Dominique
Subject: Re: [Dev] Tizen WiNet (WiFi & Network) Framework Prototype Version is
Released!
Hello,
Could you give us a status about this feature ? I saw the reviews you sent to
me but I dont have the global map.
Furthermore, I would like to know if you already thought about multiuser
aspects in WiNet CAPI ?
BR,
Stephen
On 07/07/2014 05:37, Xu, Martin wrote:
BTW,
Any patch to WiNet is welcome!
Let’s work together to make Tizen better.
Thanks!
From: Zhang, Zhengguang
Sent: Friday, July 04, 2014 0:59
To: Stephen Clymans; '[email protected]<mailto:[email protected]>'
Cc: Laperie, Andrei;
'[email protected]<mailto:[email protected]>'; 'C S
BHARGAVA'; 'PRADEEPKUMAR BELLARY';
'[email protected]<mailto:[email protected]>'; Liu,
Bingwei; Zhu, Peter J; Xu, Martin;
'[email protected]<mailto:[email protected]>'; ???; Le Foll, Dominique
Subject: RE: [Dev] Tizen WiNet (WiFi & Network) Framework Prototype Version is
Released!
Hi, Stephen
We have updated winet-service daemon and merged the related patches into
tizen.org<http://tizen.org>, now it calls through connman-lib instead of
connman.
You can get the latest source code from tizen.org<http://tizen.org> and review
again, any suggestions, don’t hesitate to let me know, thanks in advance!
Regards,
Zhang Zhengguang
From: Dev [mailto:[email protected]] On Behalf Of Zhang, Zhengguang
Sent: Friday, July 4, 2014 9:13 AM
To: Stephen Clymans; '[email protected]<mailto:[email protected]>'
Cc: Laperie, Andrei;
'[email protected]<mailto:[email protected]>'; 'C S
BHARGAVA'; 'PRADEEPKUMAR BELLARY';
'[email protected]<mailto:[email protected]>'; Liu,
Bingwei
Subject: Re: [Dev] Tizen WiNet (WiFi & Network) Framework Prototype Version is
Released!
Hi, Stephen
Thanks for review our source code of WiNet framework.
You are right that winet-service daemon should call connman-lib instead of
calling ConnMan dbus to register agent.
For the prototype version, in order to speed up the development, we developed
connman-lib and winet-service in parallel, that’s why winet-service didn’t call
connman-lib interface.
Now we have implemented in winet-service daemon to call connman-lib instead of
connman, and we are testing it, if no serious issues found, we will submit the
patches soon, then you can review it again. ☺
Thanks,
Zhang Zhengguang
From: Stephen Clymans [mailto:[email protected]]
Sent: Thursday, July 3, 2014 11:00 PM
To: Xu, Martin; Zhang, Zhengguang;
'[email protected]<mailto:[email protected]>'
Cc: Laperie, Andrei;
'[email protected]<mailto:[email protected]>'; 'C S
BHARGAVA'; 'PRADEEPKUMAR BELLARY';
'[email protected]<mailto:[email protected]>'; Liu,
Bingwei
Subject: Re: [Dev] Tizen WiNet (WiFi & Network) Framework Prototype Version is
Released!
Hi all,
I've took a look at the code and it looks great to me.
However winet-service register a connman's agent directly through dBus instead
of using the related function available in connman-lib. Its seems more logical
to me to call the connman-lib from winet-service to limit dBus calls only to
connman-lib.
Is this current status only temporary ? Or maybe there's a reason to rely on
this current architecture ?
BR,
Stephen
On 03/07/2014 04:32, Xu, Martin wrote:
+ Steve
According to our plan at Comms F2F meeting ,We have finished the first stage
work to deliver WiNet High Level Design, Prototype and Benchmark. we also
shared the prototype code on Tizen.org.
I’d like to get feedback from all the Tizen community, which is very valuable
for us. According to the feedback, we will finalize the design and release
WiNet 0.1, and then, the new features will added step by step.
Thanks!
From: Zhang, Zhengguang
Sent: Wednesday, July 02, 2014 19:23
To: '[email protected]<mailto:[email protected]>'
Cc: '[email protected]<mailto:[email protected]>'; 'C S BHARGAVA';
'[email protected]<mailto:[email protected]>'; 'PRADEEPKUMAR
BELLARY'; Le Foll, Dominique; Liu, Bingwei; Zhu, Peter J; Xu, Martin;
'[email protected]<mailto:[email protected]>';
'[email protected]<mailto:[email protected]>'
Subject: RE: Tizen WiNet (WiFi & Network) Framework Prototype Version is
Released!
Hi, All
We tested the WiNet framework prototype version on our Mobile platform, and
below are some memory consumption data comparing with the current Tizen
solution:
Opertions
Current Tizen Solution
WiNet Framework Solution
Improved Percent
WiFi Enabled
net-config: ~840K
winet-service: ~520K
(840-520)/840 = 38%
WiFi Connected
net-config: ~850K
winet-service: ~530K
(850-530)/850 = 38%
WiFi Tethering Enabled
net-config: ~840K
mobileap-agent: ~1230K
winet-service: ~520K
(840+1230-520)/(840+1230) = 75%
From the prototype data, we can see WiNet framework solution can save much more
memory than current tizen solution from middle layer.
We will continue to optimize and implement it, and any suggestions during your
review process, don’t hesitate to let me know please.
Thanks,
Zhang Zhengguang
From: Zhang, Zhengguang
Sent: Friday, June 27, 2014 10:20 AM
To: [email protected]<mailto:[email protected]>
Cc: '[email protected]<mailto:[email protected]>'; 'C S BHARGAVA';
'[email protected]<mailto:[email protected]>'; PRADEEPKUMAR BELLARY;
Le Foll, Dominique; Liu, Bingwei; Zhu, Peter J; Xu, Martin;
[email protected]<mailto:[email protected]>;
[email protected]<mailto:[email protected]>
Subject: Tizen WiNet (WiFi & Network) Framework Prototype Version is Released!
Hi, All
Tizen WiNet(WiFi & Network) Framework prototype version is released, now it can
support the basic functionality of Tethering and WiFi Station features, we will
continue to optimize and implement it. When it can support the total feature of
Tethering and WiFi station stably, we will release 0.1 version formally, also
we plan to combine WiFi P2P and hotspot 2.0 features in the framework in future.
Attachment is a simple slide to introduce what WiNet framework is and what it
aims to do, you can refer to it for details.
WiNet framework includes 3 layers: ConnMan Lib, WiNet Service Daemon and CAPI
layer, and the source code have been submitted to tizen.org<http://tizen.org>,
you can get them from the locations below:
1). ConnMan-lib
Platform/core/connectivity/connman-lib (tizen_devel branch)
2). WiNet Service Daemon
Platform/core/connectivity/winet-service (tizen_devel branch)
3). CAPI layer
In the first phrase, we keep all the related CAPI packages and
interfaces unchanged, so you can get it from the old packages:
Platform/core/api/wifi
(tizen_devel branch, for WIFI station CAPI support)
Platform/core/capi/tethering (tizen_devel branch,
for tethering CAPI support)
There is a test program for every layer of the framework, so you can test every
layer by installing the related test program in your device.
Also you can review the source code and give your proposal freely, any
suggestions, feel free to let me know, thanks!
Regards,
Zhang Zhengguang
_______________________________________________
Dev mailing list
[email protected]<mailto:[email protected]>
https://lists.tizen.org/listinfo/dev
[cid:[email protected]]
[http://ext.samsung.net/mailcheck/SeenTimeChecker?do=f4fb70ba8b72c9ec0cbf49758999c7ca73111486ba64359970b0f5bb811d56dca0f4a4f0cebc795f15556c16c1fb7e9ccc8b9f2c88ff1b900e1512b5810ef4c349e5ff3dfdc8681d76f80bf81d31c863cf878f9a26ce15a0]
_______________________________________________
Dev mailing list
[email protected]<mailto:[email protected]>
https://lists.tizen.org/listinfo/dev
--
Baptiste DURAND
Eurogiciel Vannes/FR
_______________________________________________
Dev mailing list
[email protected]
https://lists.tizen.org/listinfo/dev
