1 / 7

Keep Alive Mechanism Review

Keep Alive Mechanism Review. Authors:. Date: 2013-03-21.

justus
Download Presentation

Keep Alive Mechanism Review

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. Keep Alive Mechanism Review Authors: Date:2013-03-21 Notice:This document has been prepared to assist IEEE 802.19. 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. Mika Kasslin, Nokia

  2. Introduction • This slide set is intended to facilitate discussion and decision making on comments (CIDs 70, 71, 124 and 125) related to the keep alive mechanism specified in the DF3.02 Mika Kasslin, Nokia

  3. Basics of the mechanism • A CM shall use the keep alive mechanism to direction of each CE which the CM serves and to direction of other CMs with which the CM needs to communicate with due to coexistence set relationship. • A CDIS shall use the keep alive mechanism to direction of each CM the CDIS serves. • The entity which runs the mechanism acts as the initiator of the procedure and is called requesting entity. The entity with which the requesting entity runs the mechanism is called responding entity. Mika Kasslin, Nokia

  4. Rules • The requesting entity shall determine what the time period between two successful consecutive keep alive messages from the requesting device is after which the responding entity determines the requesting entity to be unavailable. This time period is called KeepAliveExpiryTime and the requesting entity shall communicate it to the responding entity in each KeepAliveRequest message. • A responding entity shall determine that the requesting entity has become unavailable once it has not received a KeepAliveRequest message from the requesting entity for the KeepAliveExpiryTime. • The requesting entity shall determine that the responding entity has become unavailable once it has not received aKeepAliveResponse message to 5 consecutive KeepAliveRequest messages which it has sent to the responding entity. Mika Kasslin, Nokia

  5. Responding entity view • A responding entity shall determine that the requesting entity has become unavailable once it has not received a KeepAliveRequest message from the requesting entity for the KeepAliveExpiryTime Mika Kasslin, Nokia

  6. Requesting entity view • The requesting entity shall determine that the responding entity has become unavailable once it has not received a KeepAliveResponsemessage to 5 consecutive KeepAliveRequest messages which it has sent to the responding entity. Mika Kasslin, Nokia

  7. Discussion • Do we need the specification to specify the number of consecutive responses that lead to unavailability of the requesting entity? • Should we have figures like the ones in this presentation in the specification illustrating the keep alive mechanism? Mika Kasslin, Nokia

More Related