1 / 15

Project: IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs)

Project: IEEE P802.15 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

hilary-finch
Télécharger la présentation

Project: IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs)

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Project: IEEE P802.15 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: 2-17-1 Higashi-Gotanda Oval Court 13F Shinagawa-ku, Tokyo Japan 141-0022 Voice: +81.3.6409.3238, FAX: +81.3.6409.3203 E-Mail: sugaya@wcs.sony.co.jp, takamura@wcs.sony.co.jp, akahane@wcs.sony.co.jp, robert.huang@am.sony.com Re: P802.15.3/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 802.15.3 MAC Notice:This document has been prepared to assist the IEEE P802.15. 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 P802.15. S.Sugaya,K.Takamura,M.Akahane,B.Huang, Sony Corp.

  2. Bad Piconet Configuration Good Piconet Configuration Good Piconet Configuration PNC PNC PNC Out of service DEV 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. S.Sugaya,K.Takamura,M.Akahane,B.Huang, Sony Corp.

  3. 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 S.Sugaya,K.Takamura,M.Akahane,B.Huang, Sony Corp.

  4. 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 S.Sugaya,K.Takamura,M.Akahane,B.Huang, Sony Corp.

  5. 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.

  6. Basic Discovery Mechanism • What other DEVs do ... • DEVs will broadcast a ConfigurationInquiry 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.

  7. CI-Terminate CI-Request CFP CI Process: Leading to PNC Handover PNC Capable Device 1 CI-Response CI-Response #0,#3 Current PNC Device 0 ? • 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 PNC Capable Device 3 Beacon Beacon PNC Handover Request Beacon CI-TimeWindow #0,#4,#1 CI-Response Non-PNC Capable Device 4 CI-Response Time CI-Response #0,#3 B CAP B CAP CFP B CAP CFP B CAP CFP 0 0 3 4 1 0 3 4 1 0 1st round CI-Process 2ndround CI-Process, etc. S.Sugaya,K.Takamura,M.Akahane,B.Huang, Sony Corp.

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

  9. 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 roundCI Process CI-Response CI-Response CI-Response 2nd round CI Process CI-Response CI-Response CI- Response • 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.

  10. 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.

  11. 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 BestPNC Select Old PNC leaves Network S.Sugaya,K.Takamura,M.Akahane,B.Huang, Sony Corp.

  12. CI Command Types (New) Add CI Command type for CI-Request, CI-Response and CI-Feedback: 7.5 Command types Table 63 : Command types S.Sugaya,K.Takamura,M.Akahane,B.Huang, Sony Corp.

  13. Configuration Inquiry Commands (New) Octets:2 2 2 2 Command Type Length MTS Start Time MTS End Time Add: 7.5.22 Configuration Inquiry Commands 7.5.22.1 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. Figure AA：CI-Request Command S.Sugaya,K.Takamura,M.Akahane,B.Huang, Sony Corp.

  14. Configuration Inquiry Commands (New) Add: 7.5.22 Configuration Inquiry Commands 7.5.22.1 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. Figure FF: CI-Terminate Command S.Sugaya,K.Takamura,M.Akahane,B.Huang, Sony Corp.

  15. Configuration Inquiry Commands (New) Octets:2 2 N 0-1 Received AD-AD List Pad octet Command Type Length Add: 7.5.22.3 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. Figure BB: CI Response Command S.Sugaya,K.Takamura,M.Akahane,B.Huang, Sony Corp.

More Related