US 11,991,566 B2
Multi-device communication management
Joe S. Abuan, Cupertino, CA (US); Ian J. Baird, San Jose, CA (US); Xiaosong Zhou, Campbell, CA (US); Christopher M. Garrido, San Jose, CA (US); Dazhong Zhang, Saratoga, CA (US); Keith W. Rauenbuehler, San Francisco, CA (US); Yan Yang, San Jose, CA (US); Patrick Miauton, Redwood City, CA (US); Eric L. Chien, Santa Clara, CA (US); Berkat S. Tung, San Jose, CA (US); and Karthick Santhanam, San Jose, CA (US)
Assigned to Apple Inc., Cupertino, CA (US)
Filed by Apple Inc., Cupertino, CA (US)
Filed on Sep. 27, 2018, as Appl. No. 16/145,071.
Claims priority of provisional application 62/565,910, filed on Sep. 29, 2017.
Prior Publication US 2019/0103983 A1, Apr. 4, 2019
Int. Cl. H04W 36/00 (2009.01); G06F 9/48 (2006.01); H04B 17/318 (2015.01); H04B 17/336 (2015.01); H04L 9/08 (2006.01); H04L 9/40 (2022.01); H04L 12/18 (2006.01); H04L 65/403 (2022.01); H04L 67/14 (2022.01); H04L 67/141 (2022.01); H04L 67/143 (2022.01); H04W 4/08 (2009.01); H04W 12/0433 (2021.01); H04W 12/06 (2021.01); H04W 36/02 (2009.01)
CPC H04W 36/0033 (2013.01) [G06F 9/4856 (2013.01); H04L 9/0819 (2013.01); H04L 12/1822 (2013.01); H04L 12/1827 (2013.01); H04L 12/185 (2013.01); H04L 12/189 (2013.01); H04L 63/065 (2013.01); H04L 65/403 (2013.01); H04L 67/14 (2013.01); H04L 67/141 (2013.01); H04L 67/143 (2013.01); H04W 4/08 (2013.01); H04W 12/0433 (2021.01); H04W 12/06 (2013.01); H04W 36/0009 (2018.08); H04W 36/0016 (2013.01); H04W 36/0022 (2013.01); H04W 36/0027 (2013.01); H04W 36/0058 (2018.08); H04W 36/02 (2013.01); H04B 17/318 (2015.01); H04B 17/336 (2015.01)] 20 Claims
OG exemplary drawing
 
1. A device, comprising:
a memory; and
at least one processor configured to:
generate, for transmission, to a first server, an allocation request requesting allocation of a group communication session with a plurality of devices;
receive, from the first server, an allocation response in response to the allocation request, the allocation response including credential information for the device to use to join the group communication session;
generate, for transmission, to a second server, an allocation bind request with the credential information to join the group communication session using the credential information;
receive, from the second server, an allocation bind success response in response to the allocation bind request, the allocation bind success response indicating that the device has joined the group communication session; and
generate a join notification for transmission to the plurality of devices via a third server to provide notification that the device has joined the group communication session.