1 / 14

TG1 Draft Topics for January 2013 Meeting

TG1 Draft Topics for January 2013 Meeting. Authors:. Date: 2013-01-14.

laurie
Download Presentation

TG1 Draft Topics for January 2013 Meeting

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. TG1 Draft Topics for January 2013 Meeting Authors: Date:2013-01-14 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. Abstract This presentation contains discussion material on topics which rise from open comments and which are proposed to be discussed in the TG as complete topics instead of addressing related comments individually • Many of the comments are interconnected and related to a bigger issue which should be treated as whole • These issues are named here topics and the author believes that it is more beneficial for the TG to discuss the topics from the overall system and its operation perspective so that the TG members can see what all the implications to different entities and interfaces are Mika Kasslin, Nokia

  3. Topic list • Follow-up items • New features • Interface setup and use • Profiles • CDIS and coexistence discovery • Protocol message and data type review Mika Kasslin, Nokia

  4. Topic 1: Follow-up items • This topic contains items that have been discussed in the TG but that have not been resolved yet • Frequency range notification • Mobility support • Radio environment information Mika Kasslin, Nokia

  5. Topic 2: New features • 22 technical/general comments (CID 34-55) have been grouped together and they have been titled as ”New features” comments • Following remaining questions/items can be identified from the comments in the topic group • Support of secondary users with different priorities • Management of a WSO by a non-802.19.1 entity Mika Kasslin, Nokia

  6. Topic 3: Interface setup and use • The draft needs to specify how entities setup interfaces and how they become connected when needed • The draft needs to specify also how the interfaces are used in interoperable manner Mika Kasslin, Nokia

  7. Topic 4: Profiles • The TG has agreed to use profiles but the draft lacks details on them Mika Kasslin, Nokia

  8. Topic 5: CDIS and coexistence discovery • In general there is still an open question on how does coexistence discovery work • What the responsibilities of CM and CDIS are? • What is communicated between a CM and a CDIS and what is expected between CMs? Mika Kasslin, Nokia

  9. Topic 6: Protocol message and data type review • Currently there are a few comments which ask for updates to the data type definitions • Once we have all the functionality in place and we know what each entity responsibilities are we should review the message content and data type definitions in details • Thus the proposal is to have this done as the last item before proceeding in the draft approval process Mika Kasslin, Nokia

  10. Annex slides Mika Kasslin, Nokia

  11. Background info on profiles IEEE 802.19.1 system shall operate as per the following principles • A CDIS shall be able to provide coexistence discovery service to any type of CM • A CM shall be able to exchange information with any other type of CM • A CM doesn’t have to be able to serve all profiles but a CM shall be able to support at least one profile Mika Kasslin, Nokia

  12. Background info on profiles (cont’d) The following shall apply to each IEEE 802.19.1 compliant CE • Each CE shall support basic procedures (e.g. authentication, subscription, registration) • Each CE shall support at least one profile • A profile determines which procedures are mandatory and which are optional. A profile covers also the basic procedures. • A profile determines which messages, parameters and functions are mandatory and which are optional. • Each CE shall support at least management service or information service or may support both. Its support may be dependent on the WSO it interfaces. • Each CE shall interface a WSO to a CM Mika Kasslin, Nokia

  13. Background info on profiles (cont’d) The following shall apply to each IEEE 802.19.1 compliant CM • Each CM shall support basic procedures (e.g. authentication, subscription, registration) • Each CM shall support at least one profile • A profile determines which procedures are mandatory and which are optional. A profile covers also the basic procedures. • A profile determines which messages, parameters and functions are mandatory and which are optional. • Each CM shall support both management service and information service Mika Kasslin, Nokia

  14. Background info on profiles (cont’d) The following shall apply to each IEEE 802.19.1 compliant CDIS • Each CDIS shall support basic procedures (e.g. authentication, subscription, registration) • Each CDIS shall be able to provide coexistence discovery service to any type of CM Mika Kasslin, Nokia

More Related