UniPro protocol stack: Difference between revisions

Content deleted Content added
ALasry (talk | contribs)
ALasry (talk | contribs)
L4 connections: upgrade to v1.4
Line 329:
 
===L4 connections===
UniPro calls a pair of CPorts that communicate with each other a connectionConnection (hence the C in CPort). Setting up a connection means that one CPort has been initialized to create segments which are addressed to a specific L4 CPort of a specific L3 DeviceID using a particular L2 Traffic Class. Because UniPro connections are bidirectional, the destination CPort is also configured to allow data to be sent back to the source CPort.
 
In UniPro 1.0/1.1 connection setup is implementation specific.
In UniPro 1.0/1.1 connection setup is assumed to be relatively static: the settings of the paired CPorts in somehow made to match (e.g. hardcoded in firmware within both devices or communicated by proprietary means). This will be replaced by a conventional (dynamic) connection management protocol in a future version of UniPro.
 
In UniPro 1v1.0/1.14 connection setup is assumed to be relatively static: the settingsparameters of the paired CPorts inare somehowconfigured madeby tosetting matchthe (e.g.corresponding connection hardcodedAttributes in firmwarethe local withinand bothpeer devices orusing communicated by proprietarythe means)DME. This will be replacedsupplemented by a conventional (dynamic) connection management protocol in a future version of UniPro.
 
===L4 flow control===