46 <dt>ISDN</dt> |
46 <dt>ISDN</dt> |
47 <dd><p>Integrated Services Digital Network </p> </dd> |
47 <dd><p>Integrated Services Digital Network </p> </dd> |
48 </dlentry> |
48 </dlentry> |
49 <dlentry> |
49 <dlentry> |
50 <dt>ECUART</dt> |
50 <dt>ECUART</dt> |
51 <dd><p>Serial RS232 driver for Symbian OS. UART means Universal Asynchronous |
51 <dd><p>Serial RS232 driver for Symbian platform. UART means Universal Asynchronous |
52 Receiver/Transmitter. </p> </dd> |
52 Receiver/Transmitter. </p> </dd> |
53 </dlentry> |
53 </dlentry> |
54 <dlentry> |
54 <dlentry> |
55 <dt>C32</dt> |
55 <dt>C32</dt> |
56 <dd><p>Serial Communications Server in Symbian OS (see <xref href="GUID-9B83CDD4-FC94-51A0-AC67-CD04BCAFEF08.dita">Serial |
56 <dd><p>Serial Communications Server in Symbian platform (see <xref href="GUID-9B83CDD4-FC94-51A0-AC67-CD04BCAFEF08.dita">Serial Communications Server</xref>) </p> </dd> |
57 Communications Server</xref>) </p> </dd> |
|
58 </dlentry> |
57 </dlentry> |
59 </dl> </section> |
58 </dl> </section> |
60 <section id="GUID-FEB0738E-8AB9-48DD-8648-493AC70258A0"><title>Introduction</title> <p>The Baseband Channel Adapter (BCA) |
59 <section id="GUID-FEB0738E-8AB9-48DD-8648-493AC70258A0"><title>Introduction</title> <p>The |
61 provides a telephony-specific abstraction of the baseband driver. </p> <p>You |
60 Baseband Channel Adapter (BCA) provides a telephony-specific abstraction of |
62 implement your BCA components depending on the level of abstraction you require, |
61 the baseband driver. </p> <p>You implement your BCA components depending on |
63 providing a standard interface to the component above it in the Communications |
62 the level of abstraction you require, providing a standard interface to the |
64 stack. You can also stack BCA components for more flexibility. </p> <p>Performance |
63 component above it in the Communications stack. You can also stack BCA components |
65 is a critical requirement for the Comms Data Plane. To improve throughput, |
64 for more flexibility. </p> <p>Performance is a critical requirement for the |
66 update your BCA components and your link layer protocol plugins to use the <xref href="GUID-55442FD0-FD97-3FA3-A61A-C1288C4D5670.dita"><apiname>MBca2</apiname></xref> interface. </p> </section> |
65 Comms Data Plane. To improve throughput, update your BCA components and your |
|
66 link layer protocol plugins to use the <xref href="GUID-55442FD0-FD97-3FA3-A61A-C1288C4D5670.dita"><apiname>MBca2</apiname></xref> interface. </p> </section> |
67 <section id="GUID-5D32EEFF-FFF5-51DE-AF53-F182A4E49F9D"><title>Architecture</title> <p>This |
67 <section id="GUID-5D32EEFF-FFF5-51DE-AF53-F182A4E49F9D"><title>Architecture</title> <p>This |
68 topic focuses on a general case where there is one BCA component between the |
68 topic focuses on a general case where there is one BCA component between the |
69 driver and the lower layer of the Data Plane. In the case of a stack of BCA |
69 driver and the lower layer of the Data Plane. In the case of a stack of BCA |
70 components, the same design is repeated between each BCA layer. </p> <p>In |
70 components, the same design is repeated between each BCA layer. </p> <p>In |
71 a "pull" communication model, the destination requests data from the source. |
71 a "pull" communication model, the destination requests data from the source. |
74 is ready. </p> <p>BCA2 is based on a "push" architecture. The link layer component |
74 is ready. </p> <p>BCA2 is based on a "push" architecture. The link layer component |
75 registers with the BCA component. The BCA component provides the data to its |
75 registers with the BCA component. The BCA component provides the data to its |
76 registered clients as soon as the data becomes available. </p> <p>The API |
76 registered clients as soon as the data becomes available. </p> <p>The API |
77 is split into five classes to separate control flow and data flow methods. </p> <fig id="GUID-699CB340-3DBB-50F5-8555-D4E2609BDECC"> |
77 is split into five classes to separate control flow and data flow methods. </p> <fig id="GUID-699CB340-3DBB-50F5-8555-D4E2609BDECC"> |
78 <title> MBca2 design </title> |
78 <title> MBca2 design </title> |
79 <image href="GUID-0B45D491-F88A-5036-A51C-9BFD6DB574D5_d0e62608_href.png" placement="inline"/> |
79 <image href="GUID-0B45D491-F88A-5036-A51C-9BFD6DB574D5_d0e68899_href.png" placement="inline"/> |
80 </fig> <p>Moreover, the <xref href="GUID-55442FD0-FD97-3FA3-A61A-C1288C4D5670.dita"><apiname>MBca2</apiname></xref> interface |
80 </fig> <p>Moreover, the <xref href="GUID-55442FD0-FD97-3FA3-A61A-C1288C4D5670.dita"><apiname>MBca2</apiname></xref> interface |
81 relies on shared buffers instead of regular buffers. Using shared buffers |
81 relies on shared buffers instead of regular buffers. Using shared buffers |
82 avoids data copies between different layers of the stack. For more information, |
82 avoids data copies between different layers of the stack. For more information, |
83 see <xref href="GUID-A248C2C0-5F64-5484-85B2-57C86E3499E1.dita">Memory Management |
83 see <xref href="GUID-A248C2C0-5F64-5484-85B2-57C86E3499E1.dita">Memory Management |
84 in the Communications Framework</xref>. </p> </section> |
84 in the Communications Framework</xref>. </p> </section> |
140 common BCA components and illustrate how they integrate with the Communications |
140 common BCA components and illustrate how they integrate with the Communications |
141 Framework. For definition of the abbreviations used in the diagrams, see the <xref href="GUID-18C39927-625C-5B24-919F-469FCBCD501D.dita#GUID-18C39927-625C-5B24-919F-469FCBCD501D/GUID-679587F9-CD73-51C2-8D7E-AE5817533660">Key |
141 Framework. For definition of the abbreviations used in the diagrams, see the <xref href="GUID-18C39927-625C-5B24-919F-469FCBCD501D.dita#GUID-18C39927-625C-5B24-919F-469FCBCD501D/GUID-679587F9-CD73-51C2-8D7E-AE5817533660">Key |
142 concepts and terms</xref> section. </p> <fig id="GUID-4B18CDAD-FDF3-5AF2-8B7C-85DC77C3E5FE"> |
142 concepts and terms</xref> section. </p> <fig id="GUID-4B18CDAD-FDF3-5AF2-8B7C-85DC77C3E5FE"> |
143 <title> Use case for BCA: IP communication through the serial |
143 <title> Use case for BCA: IP communication through the serial |
144 port </title> |
144 port </title> |
145 <image href="GUID-0F5C8DA1-EF91-588B-A917-350793DA03A5_d0e62806_href.png" placement="inline"/> |
145 <image href="GUID-0F5C8DA1-EF91-588B-A917-350793DA03A5_d0e69097_href.png" placement="inline"/> |
146 </fig> <fig id="GUID-1297D10A-59C2-5C15-877D-7CF94B667878"> |
146 </fig> <fig id="GUID-1297D10A-59C2-5C15-877D-7CF94B667878"> |
147 <title> Use case for BCA: PPP communication through the serial |
147 <title> Use case for BCA: PPP communication through the serial |
148 port </title> |
148 port </title> |
149 <image href="GUID-760222AA-59F0-58E6-A494-F9CB6D739960_d0e62814_href.png" placement="inline"/> |
149 <image href="GUID-760222AA-59F0-58E6-A494-F9CB6D739960_d0e69105_href.png" placement="inline"/> |
150 </fig> <fig id="GUID-4A636F57-AF70-5646-A957-4B4F4AD5EA70"> |
150 </fig> <fig id="GUID-4A636F57-AF70-5646-A957-4B4F4AD5EA70"> |
151 <title> Use case for BCA: PPP communication over Ethernet |
151 <title> Use case for BCA: PPP communication over Ethernet |
152 </title> |
152 </title> |
153 <image href="GUID-96F5CB06-F1C2-5F37-B5B8-DA8C086B73AA_d0e62822_href.png" placement="inline"/> |
153 <image href="GUID-96F5CB06-F1C2-5F37-B5B8-DA8C086B73AA_d0e69113_href.png" placement="inline"/> |
154 </fig> </section> |
154 </fig> </section> |
155 </conbody><related-links> |
155 </conbody><related-links> |
156 <link href="GUID-E054E7F6-3918-5F76-8489-D5CFC9EE257A.dita"><linktext>BCA2 Control |
156 <link href="GUID-E054E7F6-3918-5F76-8489-D5CFC9EE257A.dita"><linktext>BCA2 Control |
157 Options</linktext></link> |
157 Options</linktext></link> |
158 </related-links></concept> |
158 </related-links></concept> |