Thanks for the clarification regarding the caching behavior of CBPeripheral.name. We now understand that: CBPeripheral.name initially reflects the Advertised Name. After connection, it switches to the GAP Name, which is then cached. Given this, we would like to ask some more questions as follows: Is there a reliable way to explicitly retrieve the current Advertised Name (not the cached GAP Name)? Can we access the advertised name directly from the advertisement data during scanning? Are there any best practices for handling peripherals that frequently change their name (e.g., dynamic naming based on state)? Any code snippets or implementation tips would be greatly appreciated! Thanks again for the insights.