802.19.1 Reference Model Date: 2010-09-15 Authors: September 2010 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. Release: The contributor grants a free, irrevocable license to the IEEE to incorporate material contained in this contribution, and any modifications thereof, in the creation of an IEEE Standards publication; to copyright in the IEEE’s name any IEEE Standards publication even though it may include portions of this contribution; and at the IEEE’s sole discretion to permit others to reproduce in whole or in part the resulting IEEE Standards publication. The contributor also acknowledges and accepts that this contribution may be made public by IEEE 802.19. Patent Policy and Procedures: The contributor is familiar with the IEEE 802 Patent Policy and Procedures <http:// ieee802.org/guides/bylaws/sb-bylaws.pdf>, including the statement "IEEE standards may include the known use of patent(s), including patent applications, provided the IEEE receives assurance from the patent holder or applicant with respect to patents essential for compliance with both mandatory and optional portions of the standard." Early disclosure to the TAG of patent information that might be relevant to the standard is essential to reduce the possibility for delays in the development process and increase the likelihood that the draft publication will be approved for publication. Please notify the Chair <shellhammer@ieee.org> as early as possible, in written or electronic form, if patented technology (or technology under patent application) might be incorporated into a draft standard being developed within the IEEE 802.19 TAG. If you have questions, contact the IEEE Patent Committee Administrator at <patcom@ieee.org>. Hyunduk Kang, et al, ETRI

Contents Introduction 802.19.1 reference model CXPM September 2010 Contents Introduction 802.19.1 reference model CXPM CX_DME_SAP (service access point) CX_NET_SAP Hyunduk Kang, et al, ETRI

September 2010 Introduction 802.19.1 system architecture consists of three (internal) logical entities and six logical interfaces 802.19.1 system architecture Hyunduk Kang, et al, ETRI

September 2010 802.19.1 Reference Model (1/2) 802.19.1 entities are located on the application layer Each 802.19.1 entity has one or more the following service access point (SAP) CX_DME_SAP (CoeXistence Device Management Entity SAP): to communicate with TVBD management entities, e.g., 802.11 SME, 802.22 NCMS CX_NET_SAP (CoeXistence NETwork SAP): to communicate with remote 802.19.1 internal entities or OME or TVWS DB Hyunduk Kang, et al, ETRI

802.19.1 Reference Model (2/2) CE shall have CM/CDIS shall have September 2010 802.19.1 Reference Model (2/2) CE shall have CX_DME_SAP: to communicate with TVBD management entities CX_NET_SAP: to communicate with remote CM CM/CDIS shall have CX_NET_SAP: to communicate with remote 802.19.1 internal entities or OME or TVWS DB TVBD management entity shall provide CXPM (coexistence primitive mapping) service Hyunduk Kang, et al, ETRI

September 2010 CXPM CXPM converts CX_DME_SAP primitives into TVBD-specific management/control primitives. 1-to-1 mapping might be highly desirable to fully support 802.19.1 standard, but it might depend upon the degree of modification of each TVDB standard. How to implement CXPM is out of scope of this standard. Hyunduk Kang, et al, ETRI

CX_DME_SAP supports interface A September 2010 CX_DME_SAP supports interface A abstracts media dependent interface to communicate with TVBD management entities, e.g., 802.11 SME, 802.22 NCMS Hyunduk Kang, et al, ETRI

CX_NET_SAP supports interface B1, B2, B3, C, and D September 2010 CX_NET_SAP supports interface B1, B2, B3, C, and D abstracts media dependent (for L2 transport) or independent (for L3 transport) interface to communicate remote 802.19.1 entities or TVWS DB or OME exchanges 802.19.1 logical entities’ information and messages with remote 802.19.1 logical entities or TVWS DB or OME might use L2 transport for intra-domain communications, and L3 transport for inter and intra-communications is not needed between CM and CE if both CM and CE are located on the same TVBD Hyunduk Kang, et al, ETRI