What is rfcomm
You also have the option to opt-out of these cookies. But opting out of some of these cookies may affect your browsing experience. Necessary Necessary. Non-necessary Non-necessary. Thanks for your feedback. Choose where you want to search below Search Search the Community. Search the community and support articles Windows Windows 8.
Other items showing up under network adpaters make sense to me, but not this one. This thread is locked. You can follow the question or vote as helpful, but you cannot reply to this thread. I have the same question Report abuse. Details required :. However, in the real world some problems arise : The RFCOMM-based port driver is running on top of a packet-based protocol where data may be buffered somewhere in the communication path.
Thus, the port driver cannot perform flow control with the same precision as in the wired case. The application may decide to apply the flow control mechanism itself in addition to requesting flow control from the port driver.
These problems suggest that the port driver must do some additional work to perform flow control emulation properly.
Here are the basic rules for flow control emulation. The port driver will not solely rely on the mechanism requested by the application but use a combination of flow control mechanisms. The port driver must be aware of the flow control mechanisms requested by the application and behave like the wired case when it sees changes on the non-data circuits hardware flow control or flow control characters in the incoming data software flow control.
If the application sets a flow control mechanism via the port driver interface and then proceeds to invoke the mechanism on its own, the port driver must behave in a manner similar to that of the wired case e. If XOFF and XON characters would have been passed through to the wire in the wired case the port driver must also pass these characters. Therefore, its use is subject to negotiation before the first DLC establishment. Implementations conforming to this specification must support it, and must try to use it when connecting to other devices.
The credit based flow control feature provides flow control on a per - DLC basis. A sending entity may send as many frames on a DLC as it has credits; if the credit count reaches zero, the sender must stop and wait for further credits from the peer. This mechanism operates independently for each DLC, and for each direction. This figure shows how the RFComm protocol can be used to emulate a wired connection between a serial mouse and a standard computer RS port.
This example shows that the computer requests an RS connection request to the Bluetooth radio through the RF communication port. The RFComm protocol determines the need for a communication session so it requests that the L2CA layer initiate a logical connection to the mouse Bluetooth radio.
0コメント