1. doc.: IEEE 802.15-<doc#>
<month year>
doc.: IEEE <doc#>
November 7, 2001
Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs)
Submission Title: Network configuration optimization
Date Submitted: XXXX
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 defined Geographical Inquiry Process, Specified Command sets that provide an accessible Device count for geographical coverage based PNC Handover.
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
<author>, <company>
<author>, <company>

2. Configuration Inquiry Process: Concept
<month year>
doc.: IEEE <doc#>
November 7, 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
<author>, <company>
<author>, <company>

3. Configuration Inquiry Process: Concept Cont.
<month year>
doc.: IEEE <doc#>
November 7, 2001
Configuration Inquiry Process: Concept Cont.
Sub optimum configuration of a working piconet can result from the exit of the PNC
Therefore, it is useful to be able to optimize the network based on network condition or user command.
The configuration inquiry process supports this.
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.
<author>, <company>
<author>, <company>

4. Basic Discovery Mechanism
November 7, 2001
Basic Discovery Mechanism
Discovery within the piconet – Inquiry transaction
Called Configuration Inquiry Process (CIP)
All DEVs
Receive a GTS for CIP (CI-GTS)
Receive a Configuration Inquiry Request (CI-Request) from PNC
Reply with a Configuration Inquiry Response (CI-Response) in their CI-GTS
Non-Associated DEVs reply with a CI-Response in any part of Non-Associated DEV (NAD) GTS, if Child PNC assigned
Alternate PNCs will
Compile the AD-ADs of nearby DEVs
Broadcast the Configuration Inquiry Feedback (CI-Feedback) with ID list of detected DEVs to the next their CI-GTS
<author>, <company>

5. GTS Allocation for CI Process
November 7, 2001
GTS Allocation for CI Process
PNC Allocates CI-GTS for itself and for each DEV in the piconet
Destination address of the CI-GTS is “broadcast (0xFF)”
PNC will broadcast “ CI-Request” in its CI-GTS
DEVs and A-PNCs will broadcast “ CI-Response” in their CI-GTS
PNC puts CI-GTS for more than 1 super frame
If sleeping DEV exists in piconet, PNC will perform CIP after the DEV become ACTIVE
One superframe (additional) need to collect Alternate PNC Received AD-AD lists
CAP
Time
Contention Free Period
CI-GTS1
CI-GTS0
Super Frame Duration
CI-GTS2
Beacon
CI-GTS3
<author>, <company>

6. Broadcast of DEV ID List
<month year>
doc.: IEEE <doc#>
November 7, 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-Feedback
CI-Feedback
Modified to fit next slide and slide 9.
CI- Feedback
CI Process is Finished after the 2nd round CI Process
1st round CI-Response is to build the DEV List
2nd round CI-Feedback is to distribute DEV Lists
If a known DEV does not respond, the PNC send second CI- request and extends CIP by one superframe
<author>, <company>
<author>, <company>

7. Inside of the piconet inquiry
<month year>
doc.: IEEE <doc#>
November 7, 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
<author>, <company>
<author>, <company>

8. PNC leaves the network procedure
November 7, 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
<author>, <company>

9. CI Process: Leading to PNC handover
November 7, 2001
CI Process: Leading to PNC handover
Non-PNC Capable
Device 4
Current PNC
Device 0
PNC Capable
Device 3
Device 1 B
CAP
CFP 3 4 1
#2,#4,#1
#2,#3
CI-Request
CI-Response
CI-List Feedback
PNC
Handover Request
Beacon
1st round CI-Process
2nd round CI-Process
#3,#4,#1
Time
Procedure of the current PNC performs the PNC Handover
PNC sends CI-GTS (broadcast GTS) for each DEV in the beacon
PNC broadcasts CI-Request in PNC CI-GTS
Each DEV broadcasts CI-Response in assigned CI-GTS
Alternate PNC broadcast CI-Feedback in 2nd round assigned CI-GTS
After 2nd CI Process, configuration information is known for handover Note: CI Process result may be used with other criteria to determine handover.
<author>, <company>

10. doc.: IEEE 802.15-<doc#>
<month year>
doc.: IEEE <doc#>
November 7, 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 Feedback
0x0020-0xFFFF
Reserved
<author>, <company>
<author>, <company>

11. Configuration Inquiry Commands (New)
<month year>
doc.: IEEE <doc#>
November 7, 2001
Configuration Inquiry Commands (New)
Add:
Configuration Inquiry Commands
CI-Request Command
The PNC broadcast CI-Request command, with the AD-AD of 0x00, to initiate the CI process with devices in the piconet. The CI-Request Command structure is illustrated in figure AA.
CI-Response Command
The device respond to the CI-Request, using the CI-Response command with the Device’s AD-AD. The CI-Response Command structure is illustrated in figure AA.
Octets:2 2 1
Command Type
Length
AD-AD
Figure AA：CI-Request and CI-Response Command
<author>, <company>
<author>, <company>

12. Configuration Inquiry Commands (New)
<month year>
doc.: IEEE <doc#>
November 7, 2001
Configuration Inquiry Commands (New)
Add:
CI-Feedback Commands
The Alternate PNC send the CI Feedback command with its Received AD-AD List plus its complied list of AD-ADs. The CI Feedback Command structure is illustrated in figure BB.
Octets:2 2 1 N
Command Type
Length
Capability field
AD-AD
Received AD-AD List
Octets:1
･･･ 1
Received AD-AD #1
Received AD-AD #N
Figure BB: CI Response Command
<author>, <company>
<author>, <company>

13. Outside of the (parent) piconet inquiry
<month year>
doc.: IEEE <doc#>
November 7, 2001
Outside of the (parent) piconet inquiry
Piconet
Parent Piconet
Parent PNC
PNC
Child PNC
Alternate PNC
We needs the child network setup trigger for something process.
Out of service DEV
Parent Piconet PNC
Child Piconet
Parent Piconet DEV
Alternate PNC DEV
Child Piconet PNC
Child Piconet DEV
<author>, <company>
<author>, <company>

14. Child network setup procedure
<month year>
doc.: IEEE <doc#>
November 7, 2001
Child network setup procedure
Before the Child network setup, Alternate PNC start the CI Process
Alternate PNC Device
Upper Layer control
(User sets switch)
Child GTS request
Child Beacon Transmit
(with CIP GTSs)
Child Network Terminate
Configuration Inquiry Process
Child Network Operation
No DEV
Find DEV
<author>, <company>
<author>, <company>

15. GTS Allocation for CI Process
<month year>
doc.: IEEE <doc#>
November 7, 2001
GTS Allocation for CI Process
Child PNC Allocates CI-GTS itself and Non-Associated DEV (NAD) GTS for Non-Associated and Non-Authenticated Device
Child PNC broadcast “ CI-Request” in the PNC CI-GTS
Non-Associated DEVs will broadcast “ CI-Response” in the NAD-GTS
Non-Associated DEV (NAD) GTS
Source address of the NAD-GTS is “Non-Associates DEV(0xFE)”
Destination address of the NAD-GTS is “broadcast (0xFF)”
Child PNC puts CI-GTS and NAD-GTS for more than 1 super frame
Time
CAP
Contention Free Period
Beacon
CI-GTS 0
NAD-GTS 1
NAD-GTS 2
NAD-GTS N
Parent-GTS
Super Frame Duration
<author>, <company>
<author>, <company>

16. Child network setup inquiry
<month year>
doc.: IEEE <doc#>
November 7, 2001
Child network setup inquiry
Time
Parent PNC
Device 0
Beacon
Beacon
Beacon
Beacon
CI-Request
CI-Request
Child PNC
Device 1
Beacon
CI-Response
Beacon
CI-Response
Beacon
Non Associated
Device 2
Association
CI-Response
CI-Response
Non-Associated
Device 3
Association
Parent B C B C B C B C 1 F F F
Parent 1 F F F
Parent 1 F F F
Parent
1st round CI-Process
2nd round CI-Process
Child PNC performs the Geographical Inquiry Process
Child PNC sends CI-GTS and NAD GTS for Non-Associated DEV in the beacon
Child PNC broadcasts CI-Request in PNC CI-GTS
Each Non-Associated DEV broadcast CI-Response in any part of NAD-GTS
Child PNC more than one CI-Request broadcast for collision avoidance,
If the Non-Associated DEV respond, Child PNC starts child piconet operation
<author>, <company>
<author>, <company>