Third party application control of a client
AssigneeZoom Communications, Inc.
InventorsKaren Kuei Ren Hong, Haibing Xu, Dan Yang
Life of this patent
Estimating the term…
Abstract
A third party application is used to control a client over a software platform. The third party application sends a control command to a microservice of the software platform. The microservice generates an event socket command based on the control command. The microservice transmits the event socket command to a private branch exchange (PBX) server of the software platform over a transmission control protocol (TCP) connection. The PBX server transmits the event socket command to the client to perform the function based on a binding status that indicates a binding between the third party application and the client.
Claims20
A method, comprising:
- receiving a control command from a first client associated with a third party application configured to run on a software platform, the control command indicating a function for a second client to perform, the second client associated with the software platform, wherein the first client and the second client are connected to a cloud-based communication system based on a telephony extension;
- generating an event socket command based on the control command;
- transmitting the event socket command to a private branch exchange (PBX) server of the software platform over a transmission control protocol (TCP) connection;
- determining, by the PBX server, a binding status from a database indicating an existence of a wireless binding between the first client and the second client, wherein the wireless binding is an association between the first client and the second client based on the first client and the second client sharing a user account, and enables shared control of the second client via the third party application;
- and
- transmitting the event socket command to the second client to execute the function based on the binding status indicating the existence of the wireless binding between the first client and the second client, wherein the wireless binding between the first client and the second client is based on a multi-step confirmation received from the first client and the second client, and wherein the multi-step confirmation includes creating a binding record and updating the binding record.
A system, comprising:
- a private branch exchange (PBX) server comprising a non-transitory computer-readable medium comprising stored instructions;
- and
- a server comprising a non-transitory computer-readable medium comprising stored instructions configured to:
- receive a control command from a first client associated with a third party application configured to run on a software platform, the control command indicating a function for a second client to perform, the second client associated with the software platform, wherein the first client and the second client are connected to a cloud-based communication system based on a telephony extension;
- generate an event socket command based on the control command;
- and
- transmit the event socket command to the PBX server over a transmission control protocol (TCP) connection;
- the PBX server configured to:
- determine a binding status from a database that indicates an existence of a wireless binding between the first client and the second client, wherein the wireless binding is an association between the first client and the second client based on the first client and the second client sharing a user account, and enables shared control of the second client via the third party application;
- and
- transmit the event socket command to the second client to execute the function based on the binding status that indicates the existence of the wireless binding between the first client and the second client, wherein the wireless binding between the first client and the second client is based on a multi-step confirmation received from the first client and the second client, and wherein the multi-step confirmation includes creation of a binding record and an update of the binding record.
A non-transitory computer-readable medium comprising instructions stored on a memory, that when executed by a processor, cause the processor to perform operations comprising:
- receiving a control command from a first client associated with a third party application configured to run on a software platform, the control command indicating a function for a second client to perform, the second client associated with the software platform, wherein the first client and the second client are connected to a cloud-based communication system based on a telephony extension;
- generating an event socket command based on the control command;
- transmitting the event socket command to a private branch exchange (PBX) server of the software platform over a transmission control protocol (TCP) connection;
- determining, by the PBX server, a binding status from a database indicating an existence of a wireless binding between the first client and the second client, wherein the wireless binding is an association between the first client and the second client based on the first client and the second client sharing a user account, and enables shared control of the second client via the third party application;
- and
- transmitting the event socket command to the second client to execute the function based on the binding status indicating the existence of the wireless binding between the first client and the second client, wherein the wireless binding between the first client and the second client is based on a multi-step confirmation received from the first client and the second client, and wherein the multi-step confirmation includes creating a binding record and updating the binding record.
Dependencies are inferred from the claim text.