2. In 1:1 share, this connectionToken value will be the same as that one in the ConnectionAttempt (same as the BandwidthUpgradeAttempt or the EstablishedConnection).
3. In group share, this connectionToken value will be the combination of all the connectionTokens in above point 2 (separated by comma).
PiperOrigin-RevId: 584767628
2. In NS, passing the saved advertising flow id into NC so the client_flow_id in receiver side could be the same as the NS one, which could have the correct records mapping between the NS and NC.
PiperOrigin-RevId: 582876537
Storage increase will be 4 bytes increasing in ConnetionAttemptMetadata.
(4 bytes in each sharing * 2610000 shares/daily * 7 days/week) / GB = about 0.7 GB)
(2610000 was based on current daily connection attempts count on 20221017.)
PiperOrigin-RevId: 483115234
1. 2499483 is the "Daily Initial Connection Attempts by Medium" from product data of 2022/10/10
2. http://shortn/_XocswsePbY
PiperOrigin-RevId: 482691333
1. 2499483 is the "Daily Initial Connection Attempts by Medium" from product data of 2022/10/10
2. http://shortn/_XocswsePbY
PiperOrigin-RevId: 482681421
1. the transfer speed in initial connection stage or upgraded stage.
2. when doing the end to end mapping, we could map the right metadate field into right established connection for getting more correct analysis.
PiperOrigin-RevId: 451156631
1. Add Bluetooth multipleAdvertisement support status into metrics.
2. Add the send buffer size and receive buffer size of the created WiFi Hotspot, WiFi Direct, WiFi Aware, WiFi LAN sockets.
PiperOrigin-RevId: 428175918
hai007