1. doc.: IEEE 802.15-<01/xxxr0>
<October 2001>
doc.: IEEE <01/xxxr0>
October, 2001
Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs)
Submission Title: Configuration Inquiry Process
Date Submitted: 7 November 2001
Source: Shige Sugaya, Kaz Takamura, Masa Akahane, Bob Huang
Company: Sony Corporation
Address: Higashi-Gotanda Oval Court 13F Shinagawa-ku, Tokyo Japan
Voice: , FAX:
Re: P /D0.7, 01/304r2
Abstract: This proposal presents a process to optimize a piconet configuration based an accessible device count for for the PNC and each A-PNC. This information is useful for supporting a PNC Handover decision.
Purpose: To provide an improvement to the current version of the MAC
Notice:This document has been prepared to assist the IEEE P It is offered as a basis for discussion and is not binding on the contributing individual(s) or organization(s). The material in this document is subject to change in form and content after further study. The contributor(s) reserve(s) the right to add, amend or withdraw material contained herein.
Release: The contributor acknowledges and accepts that these viewgraphs becomes the property of IEEE and may be made publicly available by P
S.Sugaya,K.Takamura,M.Akahane,B.Huang, Sony Corp.
S. Sugaya, Sony Corporation

2. Configuration Inquiry Process: Concept
<October 2001>
doc.: IEEE <01/xxxr0>
October, 2001
Configuration Inquiry Process: Concept
It is possible that a piconet will have a sub optimum configuration.
The configuration inquiry procedure (CIP) will provide information for optimization.
Bad Piconet Configuration
PNC
Out of service DEV
Good Piconet Configuration
PNC
Good Piconet Configuration
PNC
S.Sugaya,K.Takamura,M.Akahane,B.Huang, Sony Corp.
S. Sugaya, Sony Corporation

3. Review of Concept and Suggestions
<October 2001>
doc.: IEEE <01/xxxr0>
October, 2001
Review of Concept and Suggestions
499r0 procedure and suggested mod (Ping command):
Ping use here changes fundamental protocol rules
Requires reading of ACKs, not just ‘set bit’, and send to higher layer
A command by any other name….is still a command.
499r0 difficult to implement: Initiate command to response command turn around difficult because must go to higher layer
We don’t have to think about moving the device and PNC.
In case of New DEV join a piconet, current PNC is best position in the piconet.
S.Sugaya,K.Takamura,M.Akahane,B.Huang, Sony Corp.
S. Sugaya, Sony Corporation

4. Review of Concept and suggestions
<October 2001>
doc.: IEEE <01/xxxr0>
October, 2001
Review of Concept and suggestions
Therefore:
Keep the CI-Response Command
Delay the response until the next superframe (allow time from the CI-Initiate to go up to higher layer)
Three commands required.
PNC sends CI-Request
(Sets CI-Timewindow for monitoring)
Devs sends CI-Response
(Distributes accessible AD-AD list)
PNC sends CI-Terminate
We don’t have to think about moving the device and PNC.
In case of New DEV join a piconet, current PNC is best position in the piconet.
S.Sugaya,K.Takamura,M.Akahane,B.Huang, Sony Corp.
S. Sugaya, Sony Corporation

5. Basic Discovery Mechanism
<October 2001>
doc.: IEEE <01/xxxr0>
October, 2001
Basic Discovery Mechanism
What PNC will do ...
PNC sets Pseudo Static GTS (or MTS)
For each DEVs (contiguous slots)
Within CI-TimeWindow
PNC will broadcast the Configuration Inquiry Request (CI-Request)
Contains CI-TimeWindow: window for monitoring receive connectivity
All DEVs have to AWAKE in the CI-TimeWindow period
S.Sugaya,K.Takamura,M.Akahane,B.Huang, Sony Corp.
S. Sugaya, Sony Corporation

6. Basic Discovery Mechanism
<October 2001>
doc.: IEEE <01/xxxr0>
October, 2001
Basic Discovery Mechanism
What other DEVs do ...
DEVs will broadcast a Configuration Inquiry Response (CI-Response) when their own Static GTS (Management GTS) is assigned (may not be immediately)
When a DEV receives CI-Response in the CI-TimeWindow, the DEV will add the Source AD-AD to the list of detected DEVs.
S.Sugaya,K.Takamura,M.Akahane,B.Huang, Sony Corp.
S. Sugaya, Sony Corporation

7. CI Process: Leading to PNC Handover
October, 2001
CI Process: Leading to PNC Handover
PNC Capable
Device 1
CI-Response
CI-Response
#0,#3
Current PNC
Device 0
CI-Request ?
CI-Terminate
PNC Capable
Device 3
Beacon
Beacon
Beacon
PNC
Handover Request
CI-TimeWindow
CI-Response
#0,#4,#1
Non-PNC Capable
Device 4
CI-Response
Time
CI-Response
#0,#3 B
CAP
CFP B
CAP
CFP B
CAP
CFP B
CAP
CFP 3 4 1 3 4 1
1st round CI-Process
2nd round CI-Process, etc.
The procedure
PNC broadcasts CI-Request
Each devs receive CI-Request and acquire the CI-TimeWindow
Each DEV broadcasts CI-Response in assigned pseudo static-GTS in the CI-TimeWindow
Repeat until complete
S.Sugaya,K.Takamura,M.Akahane,B.Huang, Sony Corp.

8. GTS Allocation for CI Process
October, 2001
GTS Allocation for CI Process
PNC allocates GTS/MTS for itself and for each DEV in the piconet
PNC will broadcast “ CI-Request” in its time slot
All devs will broadcast “ CI-Response” in their time slot
PNC continues the process for multiple cycles
PNC will perform CIP after a sleeping DEV become ACTIVE
CAP
Time
Contention Free Period
CI-GTS1
CI-GTS0
Super Frame Duration
CI-GTS2
Beacon
CI-GTS3
S.Sugaya,K.Takamura,M.Akahane,B.Huang, Sony Corp.

9. Broadcast of DEV ID List
<October 2001>
doc.: IEEE <01/xxxr0>
October, 2001
Broadcast of DEV ID List
Alternate PNC DEV 1
Current PNC
DEV 0
Alternate PNC DEV 3
Non Alternate PNC DEV 4
CI-Request
1st round CI Process
CI-Response
CI-Response
CI-Response
2nd round CI Process
CI-Response
CI-Response
CI- Response
Modified to fit next slide and slide 9.
CI Process is Finished after several round CI Process
If a known DEV does not respond, the PNC send second CI- request
CI Process can repeat as necessary
S.Sugaya,K.Takamura,M.Akahane,B.Huang, Sony Corp.
S. Sugaya, Sony Corporation

10. Inside of the Piconet Inquiry
<October 2001>
doc.: IEEE <01/xxxr0>
October, 2001
Inside of the Piconet Inquiry
Alternate PNC
PNC
Alternate PNC
New PNC
PNC Handover
Old PNC
New PNC
Old PNC
Out of service DEV
Good PNC Handover
Current PNC DEV
Bad PNC Handover
Alternate PNC DEV
Non-Alternate PNC DEV
S.Sugaya,K.Takamura,M.Akahane,B.Huang, Sony Corp.
S. Sugaya, Sony Corporation

11. PNC Leaves the Network Procedure
October, 2001
PNC Leaves the Network Procedure
Before the PNC leaves the network, start the CI process
As a result of the CI process, PNC will perform the PNC handover to optimal alternate PNC
Geographical Inquiry Process
PNC Handover Process
New Best PNC Select
Old PNC leaves Network
S.Sugaya,K.Takamura,M.Akahane,B.Huang, Sony Corp.

12. doc.: IEEE 802.15-<01/xxxr0>
<October 2001>
doc.: IEEE <01/xxxr0>
October, 2001
CI Command Types (New)
Add CI Command type for CI-Request, CI-Response and CI-Feedback:
7.5 Command types
Table 63 : Command types
Command type hex value
Command name
0x0000
Retransmission request …
0x001C
Child or neighbor information response
0x001D
Configuration Inquiry Request
0x001E
Configuration Inquiry Response
0x001F
Configuration Inquiry Terminate
0x0020-0xFFFF
Reserved
S.Sugaya,K.Takamura,M.Akahane,B.Huang, Sony Corp.
S. Sugaya, Sony Corporation

13. Configuration Inquiry Commands (New)
<October 2001>
doc.: IEEE <01/xxxr0>
October, 2001
Configuration Inquiry Commands (New)
Add:
Configuration Inquiry Commands
CI-Request Command
The PNC broadcasts CI-Request command, to initiate the CI process with devices in the piconet. The CI-Request Command structure is illustrated in figure AA.
MTS Start Time
Length
Command Type 2
Octets:2
MTS End Time
Figure AA：CI-Request Command
S.Sugaya,K.Takamura,M.Akahane,B.Huang, Sony Corp.
S. Sugaya, Sony Corporation

14. Configuration Inquiry Commands (New)
<October 2001>
doc.: IEEE <01/xxxr0>
October, 2001
Configuration Inquiry Commands (New)
Add:
Configuration Inquiry Commands
CI-Termination Command
The PNC broadcasts CI-Termination command, to terminate monitoring of the CI-TimeWindow by the devices. The CI-Terminate Command structure is illustrated in figure FF.
Octets:2 2
Command Type
Length
Figure FF: CI-Terminate Command
S.Sugaya,K.Takamura,M.Akahane,B.Huang, Sony Corp.
S. Sugaya, Sony Corporation

15. Configuration Inquiry Commands (New)
<October 2001>
doc.: IEEE <01/xxxr0>
October, 2001
Configuration Inquiry Commands (New)
Add:
CI-Response Commands
All Devices send the CI-Response command with its Received AD-AD List plus its complied list of AD-ADs. The CI-Response Command structure is illustrated in figure BB.
Pad octet
0-1
Received AD-AD List
Length
Command Type N 2
Octets:2
Octets:1
･･･ 1
Received AD-AD #1
Received AD-AD #N
Figure BB: CI Response Command
S.Sugaya,K.Takamura,M.Akahane,B.Huang, Sony Corp.
S. Sugaya, Sony Corporation