Core Architecture blocks (Core Architecture module) (2)

Corearchitecture Blocks

Channel Manager

The channel manager isresponsible for creating, managing, and destroying L2CAP channels for thetransport of service protocols and application data streams. the channelmanager uses The L2CAP protocol to interact with a channel manager on a remote (PEER) Device
To create these L2CAP channels and connect their endpoints to theappropriate entities. the channel manager interacts with its local link managerto create new logical links (if necessary) and to configure these links toprovide the required QoS for the Type
Of data being transported.

Core Architecture

Channel Manager

The channel manager is responsible for creating, managing, and abolishing L2CAP channels for service protocol transmission and Application Data Flow tasks. When a remote (peer-to-peer) device creates an L2CAP channel and connects its endpoints to the corresponding entity, the channel manager device uses The L2CAP protocol to work with a channel manager. The channel manager interacts with its local connector to create new logical connections (if needed) and configure these connections to provide the required QoS for the transmission of the data.

 

L2CAP Resource Manager

The L2CAP resource managerblock is responsible for managing the ordering of submission of PDU fragmentsto the baseband and some relative scheduling between channels to ensure channels with QoS commitments are not denied access to the physicalchannel
DueBluetoothController resource exhaustion. This is required because the specified turalmodel does not assume thatBluetoothController has limitless buffering, or that HCI is a pipe of infinitebandwidth.

L2CAP Resource Manager

The L2CAP resource manager module is responsible for managing the submission sequence from PDU fragments to the baseband and scheduling between channels, to ensure that L2CAP channels with QoS guarantee do not reach the physical channel Because Bluetooth controller resources are exhausted. This is required because the architecture model cannot assume that the Bluetooth controller has an endless buffer mechanism, or HCI is an infinite bandwidth pipeline.

 

L2CAP resource managers mayalso carry out traffic conformance grouping ing to ensure that applications aresubmitting L2CAP SDUS within the bounds of their negotiated QoS settings. thegeneralBluetoothDatatransport model assumes well-behaved applications,
And does not define how animplementation is expected to deal with this problem.

The L2CAP Resource Manager also complies with the data consistency principle to ensure that the application can transmit L2CAP SDU data with the negotiated QoS configuration. In general, the bluetooth data transmission mode assumes that the normal behavior of the application does not define how to expect an execution body to handle this problem.

 

Device Manager

The Device Manager is thefunctional block in the baseband that controls the general behavior ofBluetoothEnabled device. It is responsible for all operationofBluetoothSystemthat is not directly related to data transport, such
Inquiring for thepresence of other nearbyBluetoothEnabled devices, connecting to otherBluetoothEnabled devices or making the localBluetoothEnabled device discoverable or connectable by otherdevices.

Device Manager

The Device Manager is a functional module in the baseband. It is responsible for controlling the general basic behavior of devices enabled by the Bluetooth function. It is responsible for all operations of the Bluetooth system, that is, it does not directly communicate with data transmission, for example, requiring nearby bluetooth functions to enable the display of devices, connect to a bluetooth device or enable the device to be detected or connected to another device.

The Device Manager requestsaccess to the transport medium from the baseband Resource Controller in orderto carry out its functions.

The device controller needs a channel from the baseband Resource Controller to the transmission media to complete these functions.

The Device Manager alsocontrols local device behavior implied by a number of the HCI commands, such asmanaging the device local name, any stored link keys, and other functionality.

The device controller also implicitly controls the behavior of local devices through many HCI commands, such as managing local device names, any stored link keys, and other functions.

 

Link Manager

The link manager isresponsible for the creation, modification, and release of logical links (and, if required, their associated logical transports), as well as the update ofparameters related to physical links between devices. the link manager achievesthis
By communicating with the link manager in remoteBluetoothDevices using The Link Management Protocol (LMP ).

The Connection Manager is responsible for creating, modifying, and releasing logical links (as well as logical transmission related to them, if needed), and updating parameters related to physical connections between devices. The Connection Manager uses the connection management protocol to communicate with the connection manager on the remote Bluetooth device to complete its functions.

The LMP allows the creation ofnew logical links and logical transports between devices when required, as wellas the general control of link and transport attributes such as the enabling ofencryption on the logical transport, the adapting of transmit power
On thephysical link or the adjustment of QoS settings for a logical link.

When necessary, LMP allows you to create new logical links and logical transmission between devices, as well as general control over links with transport entities, such as encrypted enabling of logical transmission, the adjustment of the energy transmission on the physical link, or the adjustment of the QoS settings on the Logical Link.

Baseband Resource Manager

The baseband resource manageris responsible for all access to the radio medium. it has two main functions. at its heart is a scheduler that grants time on the physical channels to all ofthe entities that have negotiated an access contract. the other main
Functionis to negotiate access contracts with these entities. An access contract isinclutively a commitment to deliver a certain QoS that is required in order toprovide a user application with an expected performance.

Baseband Resource Manager

The baseband Resource Manager is responsible for all channels that reach the radio media. It has two main functions. There is a scheduler in its center that negotiates contracts with entities that have channels to ensure their time on physical channels. Another major function is to negotiate a channel contract with these entities. A channel contract is a valid commitment to provide a required QoS to provide a user application with the expected performance.

 

The access contract andscheduling function must take account of any behavior that requires use ofBluetoothRadio. This includes des, for example, the normalexchange of data between connected devices over logical links and logicaltransports, as well
As the use of the radio medium to carry out inquiries, makeconnections, be discoverable or connectable, or to take readings from unusedcarriers during the use of AFH mode.

The channel contract and scheduling functions must take into account any behavior required by the Bluetooth radio application. This includes, for example, the normal exchange of data between devices connected to the logical link and logical transmission, and the use of radio media for execution needs to establish connections, A connection is used to enable a non-detected spark, or the information is read from the sender in the afh mode application.

In some cases the schedulingof a logical link results in changing to a different physical channel from theone that was previusly used. this may be, for example, due to involvement inscatternet, a periodic inquiry function, or page scanning. when the physicalchannels
Are not Time Slot aligned, then the resource manager also accounts forthe realignment time between slots on the original physical channel and slotson the new physical channel. in some cases the slots will be naturally aligneddue to the same device clock being
Used as a reference for both physicalchannels.

In some scenarios, logical link scheduling may lead to the transformation of some physical channels from the original used to a different channel. For example, this may be due to scattered networks, a periodic query function, or page scanning. When the physical channel is not allocated to the time slot, the resource manager will re-allocate the time slot of the initial physical channel and the new physical channel. In some scenarios, because the same device clock is used as a reference value for two physical channels, these time slots are naturally allocated.

Link Controller

The link controller isresponsible for the encoding and decodingBluetoothPackets from the data payload and parameters relatedto the physical channel, logical transport and logical link.

The link controller carriesout The Link Control Protocol signaling (in close conjunction with thescheduling function of the Resource Manager), which is used to communicate flowcontrol and acknowledgement and retransmission request signals. theinterpretation
Of these signals is a characteristic of the logical transportassociated with the baseband packet. interpretation and control of the linkcontrol signaling is normally associated with the resource manager's scheduler.

Link Controller

The link Controller is responsible for encoding and decoding bluetooth data packets from data loads related to physical channels, logical transport layers, and logical chainsaw. The link controller implements the signal communication function of The Link Control Layer (which is highly compatible with the scheduling function of the Resource Controller). It performs traffic control communication, confirms communication results, and retransmits request signals. These signals are interpreted as a feature of logical transmission related to the baseline package. The interpretation and control of link control signals are associated with the resource manager scheduler.

RF

The RF block is responsiblefor transmitting and processing ing packets of information on the physical channel. A control path between the baseband and the RF block allows the baseband blockto control the timing and frequency carrier of the RF block. the RF blocktransforms
A stream of data to and from the physical channel and the basebandinto required formats.

 

RF

The RF module sends and receives packets over physical channels. The control channel between the baseband and RF block allows the baseband block to control the time and RF block carrier. The RF block transmits data streams back and forth between physical channels and converts the baseband into the required data format.

Notice: next article: Bluetooth spec version comaration (V2.0 3.0 4.0) (Comparison of Bluetooth spec versions)