1. Transport service discussion
October 2012
Transport service discussion
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
S. Filin H. Harada, NICT
Steve Shellhammer, Qualcomm

2. October 2012
Abstract
This contribution discusses functions expected from transport services implemented by TR_SAP
Also, it proposes some modifications to TR_SAP and to CxMessage definition
S. Filin H. Harada NICT

3. Functions needed to transport coexistence protocol message
October 2012
Functions needed to transport coexistence protocol message
F1: Message encoding and decoding
Encode and decode CxMessages from/to arrays of octets with ASN.1 BER or some other encoding
F2: Address resolution
Provide mapping between CxID and IP address and port number
S. Filin H. Harada NICT

4. Functions needed to transport coexistence protocol message
October 2012
Functions needed to transport coexistence protocol message
F3: Connection management
Establish connections to other entities and manage these connections
Accept connect requests coming form other entities and notify them to the coexistence protocol
Detect disconnection and notify it to the coexistence protocol
Apply security options
F4: Sending and receiving coexistence protocol messages
Send coexistence protocol messages to the entities specified by CxID
Receive coexistence protocol messages from other entities and notify them to the coexistence protocol
S. Filin H. Harada NICT

5. October 2012
Separation of functions between transport service and coexistence protocol
From layer separation point of view, if coexistence protocol message encoding and decoding is done by the coexistence protocol, transport service does not need to have access inside encoded coexistence protocol message
Proposed separation
Coexistence protocol
F1: Message encoding and decoding
Transport service
F2: Address resolution
F3: Connection management
F4: Sending and receiving coexistence protocol messages
S. Filin H. Harada NICT

6. October 2012
Separation of functions between transport service and coexistence protocol
Transport service needs to know
Encoded coexistence protocol message length
Source
Destination
Source and destination are expressed
CxID in the coexistence protocol
IP address and port number in the TCP/IP protocol
Transport service does the mapping
S. Filin H. Harada NICT

7. Layer model October 2012 Coexistence protocol Coexistence protocol
CxMessage
TR_SAP
Transport Packet
TR_SAP
Transport service
Transport service
CxMessage
Transport Header
Socket
Socket
TCP Packet
TCP/IP
TCP/IP
CxMessage
Transport Header
TCP/IP Header
S. Filin H. Harada NICT

8. Message parameters October 2012 SEND RECEIVE Coexistence protocol
CxMessage
Destination ID
CxMessage
TR_SAP
Transport service
Source ID
CxMessage
CxMessage
Transport Header
Destination IP/Port
Transport Packet
Socket
Transport Packet
Source IP/Port
Transport Packet
TCP/IP
CxMessage
Transport Header
TCP/IP Header
S. Filin H. Harada NICT

9. Proposed TR_SAP primitives
October 2012
Proposed TR_SAP primitives
CP_PACKET_SEND.request ( destinationID CxID, cxMessage OCTET STRING ) CP_PACKET_SEND.confirm ( transportStatus BOOLEAN CP_PACKET_RECEIVE.indication ( sourceID CxID,
S. Filin H. Harada NICT

10. Proposed TR_SAP primitives
October 2012
Proposed TR_SAP primitives
CP_CONNECT.request ( transportPref TransportPref, sourceID CxID, destinationID CxID, destinationIPAddress OCTET STRING OPTIONAL, destinationPortNumber OCTET STRING OPTIONAL ) CP_CONNECT.indication ( sourceID CxID
S. Filin H. Harada NICT

11. Proposed TR_SAP primitives
October 2012
Proposed TR_SAP primitives
CP_CONNECT.response ( destinationID CxID, connectStatus BOOLEAN ) CP_CONNECT.confirm ( sourceID CxID,
S. Filin H. Harada NICT

12. Proposed TR_SAP primitives
October 2012
Proposed TR_SAP primitives
CP_DISCONNECT.request ( destinationID CxID ) CP_DISCONNECT.indication ( sourceID CxID
S. Filin H. Harada NICT

13. October 2012
Update to CxMessage
-- The coexistence protocol message structure CxMessage ::= SEQUENCE { -- Message header messageHeader MessageHeader, -- Message payload payload CxPayload }
S. Filin H. Harada NICT

14. October 2012
Update to CxMessage
-- Coexistence protocol message header MessageHeader ::= CHOICE { none NULL, -- Request identifier requestID INTEGER ( ), -- Multiple response identifier multipleResponse SEQUENCE { sequenceNumber INTEGER ( ), isLastResponse BOOLEAN }
S. Filin H. Harada NICT

15. Transport packet October 2012 Length of Transport Payload
Transport Packet Header
Length of Transport Payload
[1 to N byte : variable]
Length of Source CxID [1byte : fixed]
Source CxID
[1 to 255byte : variable]
Length of Destination CxID [1byte : fixed]
Destination CxID
[1 to 255 byte : variable]
Transport Packet Payload
ASN.1 BER encoded CxMessage
[0 to M byte : variable]
S. Filin H. Harada NICT

16. Connection establishment
October 2012
Connection establishment
The following connections are possible according to the system architecture:
From CE to CM
From CM to CE
From CM to CDIS
From CDIS to CM
From CM to other CM
From CM to TVWS DB
From CDIS to other CDIS
It is assumed that we have CDIS-CDIS interface
S. Filin H. Harada NICT

17. Connection establishment
October 2012
Connection establishment
From CE to CM
To start connection from CE to CM, the CE transport service gets list of CM ID, CM IP address and CM port number after making contract for a coexistence service
From CM to CE
To start connection from CM to CE, after the CM transport service gets an AuthenticationRequest message from the CE (the first message from the CE), the CM transport service has the CE ID, CE IP address and CE port number
S. Filin H. Harada NICT

18. Connection establishment
October 2012
Connection establishment
From CM to CDIS
To start connection from CM to CDIS, the CM transport service gets list of CDIS ID, CDIS IP address and CDIS port number after making contract for a coexistence discovery service
From CDIS to CM
To start connection from CDIS to CM, after the CDIS transport service gets an AuthenticationRequest message from the CM (the first message from the CM), the CDIS transport service has the CM ID, CM IP address and CM port number
S. Filin H. Harada NICT

19. Connection establishment
October 2012
Connection establishment
From CM to other CM
To start connection from CM to other CM, the CM transport service gets ID, IP address and port number of the neighbor CM from CDIS via CoexistenceSetInformationAnnouncement message.
Form CM to TVWS DB
To start connection from CM to TVWS DB, the CM transport service gets CDIS ID, CDIS IP address and CDIS port number from the CM configuration file
From CDIS to other CDIS
To start connection from CDIS to other CDIS, the CDIS transport service gets list of ID, IP address and port number of other CDISs from the CDIS configuration file
S. Filin H. Harada NICT