1. CX_NET_SAP Primitives
September 2010
CX_NET_SAP Primitives
Date:
Authors:
Notice: This document has been prepared to assist IEEE 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
Patent Policy and Procedures: The contributor is familiar with the IEEE 802 Patent Policy and Procedures < 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 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 TAG. If you have questions, contact the IEEE Patent Committee Administrator at
Hyunduk Kang, et al, ETRI

2. Contents Introduction CX_NET_SAP CX_NET_SAP primitives September 2010
Hyunduk Kang, et al, ETRI

3. September 2010
Introduction
system architecture consists of three logical entities and six logical interfaces
system architecture
Hyunduk Kang, et al, ETRI

4. 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 with remote entities or TVWS DB or OME
exchanges logical entities’ information and messages with remote logical entities or TVWS DB or OME
might use L2 transport for intra-domain communications, and L3 transport for inter and intra-communications
does not needed between CM and CE if CM and CE are located on the same TVBD
Hyunduk Kang, et al, ETRI

5. CX_NET_SAP Primitives (1/4)
September 2010
CX_NET_SAP Primitives (1/4)
The CX_NET_SAP primitives associated with data transfers are as follows:
CX_TP_Data.request: logical entities use it to request that an CX PDU be transported
CX_TP_Data.confirm: The transport service provider uses it to indicate the arrival of an CX PDU
CX_TP_Data.indication: it is used to acknowledge the successful transfer of the CX PDU
Hyunduk Kang, et al, ETRI

6. CX_NET_SAP Primitives (2/4)
September 2010
CX_NET_SAP Primitives (2/4)
CX_TP_Data.request
This primitive is used to request that a CX PDU be transported to a remote entity or TVWS DB.
Name
Data Type
Description
TransportType
TRANSPORT_TYPE
Identifies the protocol layer specific transport option.
SourceAddress
TRANSPORT_ADDR
Protocol layer specific Transport Address of entity that has the Source entity.
DestinationAddress
Protocol layer specific Transport Address of entity that has the Destination entity.
ReliableDeliveryFlag
BOOLEAN
Indicate that the data is sent reliably and an error is generated if delivery fails.
True: Reliable delivery is required.
False: Reliable delivery is not required.
CXProtocolPDU
OCTET_STRING
CX Protocol PDU to be transferred.
Hyunduk Kang, et al, ETRI

7. CX_NET_SAP Primitives (3/4)
September 2010
CX_NET_SAP Primitives (3/4)
CX_TP_Data.confirm
This primitive is the notification of a received CX PDU.
Name
Data Type
Description
TransportType
TRANSPORT_TYPE
Identifies the protocol layer specific transport option.
SourceAddress
TRANSPORT_ADDR
Protocol layer specific Transport Address of entity that has the Source entity.
DestinationAddress
Protocol layer specific Transport Address of entity that has the Destination entity.
ReliableDeliveryFlag
BOOLEAN
Indicate that the data is sent reliably and an error is generated if delivery fails.
True: Reliable delivery is required.
False: Reliable delivery is not required.
CXProtocolPDU
OCTET_STRING
CX Protocol PDU to be transferred.
Hyunduk Kang, et al, ETRI

8. CX_NET_SAP Primitives (4/4)
September 2010
CX_NET_SAP Primitives (4/4)
CX_TP_Data.indication
This primitive is used to indicate an acknowledged transfer.
Name
Data Type
Description
Status
STATUS
Status of operation.
TransportType
TRANSPORT_TYPE
Identifies the protocol layer specific transport option.
SourceAddress
TRANSPORT_ADDR
Protocol layer specific Transport Address of entity that has the Source entity.
DestinationAddress
Protocol layer specific Transport Address of entity that has the Destination entity.
Hyunduk Kang, et al, ETRI