1. Service level connection release
Process for Publishing Service Level Connections
Disconnection of a service level connection shall result in the immediate deletion of the corresponding RFCOMM data link channel between HF and AG. Also, since the service level connection is removed, the existing audio connection must be removed. Optionally remove L2CAP and Link Layer.
An established Service Level Connection should be released using the Service Level Connection Delete procedure.
- Due to an explicit user request, the HF or AG shall initiate a "service level connection release" procedure.
- If the Bluetooth function is disabled in HF or AG, the "Service Level Connection Release" procedure should be started.
- Executing "Audio Connection Transfer" in the AG can start the "Service Level Connection Release" procedure. In case of a service level connection being deleted, the AG shall attempt to re-establish the service level connection.
As a prerequisite for this procedure, there should be a continuous service level connection between AG and HF.
2. Transmission of registration status
The AT+CMER command will enable the "Registration Status Update" function in AG.
AT+BIA command allows HF to deactivate/reactivate individual indicators.
When the CMER function is enabled and the registration status indicator is not deactivated by the AT+BIA command, it shall send +CIEV unsolicited result code and value with the corresponding service indicator when the registration status of the AG changes. HF shall be able to interpret the information provided by the +CIEV result code to determine the service availability status.
AG shall not send unsolicited result codes if the CMER function is disabled or the indicator has been deactivated by the AT+BIA command.
