System and method for implementing video soft phone applications

US11412013B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-11412013-B2
Application numberUS-202016987635-A
CountryUS
Kind codeB2
Filing dateAug 7, 2020
Priority dateAug 7, 2019
Publication dateAug 9, 2022
Grant dateAug 9, 2022

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

An embodiment of the present invention is directed to a soft phone solution for voice and video calling. This allows for migration away from physical hard phones. The soft phone solution may be designed to be simple to use, and further infrastructure and vendor agnostic. An embodiment of the present invention may run cross-platform between corporate and Bring Your Own Devices (BYOD) for a consistent user experience. An embodiment of the present invention may then ultimately replace other existing clients to provide an any-device, any-time and anywhere solution.

First claim

Opening claim text (preview).

What is claimed is: 1. A system that implements a soft phone interaction, the system comprising: a centralized framework that delivers API driven communication capabilities and micro-services; a set of communications clients to deliver a plurality of communication and collaboration tools across a plurality of disparate devices associated with a plurality of different employees of an entity; and a computer processor, coupled to the centralized framework and the set of communication clients, configured to perform the steps of: receiving a request for communication at an input interface; determine if the request is originating from an employee associated with the entity; determine, upon verifying the request is from an employee associated with the entity, whether the request is originating from (1) a first personal device not issued from the entity or an entity issued device and (2) an internal network managed and controlled by the entity or a network external to entity; upon determining the request is originating from the first personal device and not from the internal network managed and controlled by the entity: conduct a first authentication of the employee and first personal device through physical security as a service at a tier 1 demilitarized zone via one or more of a single sign-on and Active Directory Federation Services; and upon first authentication, transfer the communication request to a tier 2 internal web server where an internal secondary authentication of the employee and first personal device is performed via one or more of a local user accounts service and a directory service that manages a plurality of devices, the first and second authentications comprising a complete authentication; upon determining the request is originating from the internal network managed and controlled by the entity, authenticate the employee at a tier 3 internal web server via one or more of a local user accounts service and a directory service that manages a plurality of devices, this authentication also comprising the complete authentication; upon complete authentication, connecting, via an api interface of the centralized framework, the request for communication to a recipient, wherein the recipient and the employee are employed by the entity; and directing, via a call manager, the request for communication to a second device from a plurality of devices associated with the recipient wherein the first device is different in type and model from the second device; wherein the centralized framework is infrastructure and vendor agnostic and the plurality of communication and collaboration tools are executed in a uniform and consistent manner across the first device and the second device. 2. The system of claim 1 , wherein the request is authenticated and registered through an API framework connection. 3. The system of claim 1 , wherein the request for communication is received by Physical Security as a Service (PSaaS) component. 4. The system of claim 1 , wherein at least one of the first device and the second device communicates via a web server associated with a Tier 3/Internal layer to the centralized framework. 5. The system of claim 1 , wherein at least one of the first device and the second device communicates via the Internet and Tier 1/DMZ layer. 6. The system of claim 1 , wherein the centralized framework accesses an entity's internal directory. 7. The system of claim 1 , wherein the centralized framework communicates with a Tier 2 layer via a cloud communications platform. 8. The system of claim 1 , wherein the plurality of communication and collaboration tools comprise video conferencing, unified enterprise communication and team collaboration. 9. The system of claim 1 , wherein at least one of the first device and the second device interacts with virtual representations of one or more hardware peripheral devices. 10. The system of claim 1 , wherein the centralized framework is coupled to a personal virtual assistant application that communicates with one or more end users. 11. A method that implements a soft phone interaction, the method comprising the steps of: receiving, at a centralized framework, a request for communication at an input interface, wherein a centralized framework that delivers API driven communication capabilities and micro-services and provides a set of communications clients to deliver a plurality of communication and collaboration tools across a plurality of disparate devices associated with a plurality of different employees of an entity; determining if the request for communication is originating from an employee associated with the entity; determining, upon verifying the request is from an employee associated with the entity, whether the request is originating from (1) a first personal device not issued from the entity or an entity issued device and (2) an internal network managed and controlled by the entity or a network external to entity; upon determining the request is originating from the first personal device and not from the internal network managed and controlled by the entity: conducting a first authentication of the employee and first personal device through physical security as a service at a tier 1 demilitarized zone via one or more of a single sign-on and Active Directory Federation Services; and transferring, upon first authentication, the communication request to a tier 2 internal web server where an internal secondary authentication of the employee and first personal device is performed via one or more of a local user accounts service and a directory service that manages a plurality of devices, the first and second authentications comprising a complete authentication; upon determining the request is originating from the internal network managed and controlled by the entity, authenticating the employee at a tier 3 internal web server via one or more of a local user accounts service and a directory service that manages a plurality of devices, this authentication also comprising the complete authentication; connecting, upon complete authentication and via an api interface of the centralized framework, the request for communication to a recipient, wherein the recipient and the employee are employed by the entity; and directing, via a call manager, the request for communication to a second device from a plurality of devices associated with the recipient wherein the first device is different in type and model from the second device; wherein the centralized framework is infrastructure and vendor agnostic and the plurality of communication and collaboration tools are executed in a uniform and consistent manner across the first device and the second device. 12. The method of claim 11 , wherein the request is authenticated and registered through an API framework connection. 13. The method of claim 11 , wherein the request for communication is received by Physical Security as a Service (PSaaS) component. 14. The method of claim 11 , wherein at least one of the first device and the second device communicates via a web server associated with a Tier 3/Internal layer to the centralized framework. 15. The method of claim 11 , wherein at least one of the first device and the second device communicates via the Internet and Tier 1/DMZ layer. 16. The method of claim 11 , wherein the centralized framework accesses an entity's internal directory. 17. The method of claim 11 , wherein the centralized framework communicates with a Tier 2 layer via a cloud communications platform. 18. The method of claim 11 , wherein th

Assignees

Inventors

Classifications

  • at the transport layer · CPC title

  • Call controllers; Call servers · CPC title

  • for authentication of entities (cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32) · CPC title

  • H04L65/403Primary

    Arrangements for multi-party communication, e.g. for conferences (data switching systems for conference H04L12/18; arrangements for connecting several subscribers to a common circuit, i.e. affording conference facilities H04M3/56; television conferencing systems H04N7/15) · CPC title

  • Architectural arrangements, e.g. perimeter networks or demilitarized zones · CPC title

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US11412013B2 cover?
An embodiment of the present invention is directed to a soft phone solution for voice and video calling. This allows for migration away from physical hard phones. The soft phone solution may be designed to be simple to use, and further infrastructure and vendor agnostic. An embodiment of the present invention may run cross-platform between corporate and Bring Your Own Devices (BYOD) for a consi…
Who is the assignee on this patent?
Jpmorgan Chase Bank Na
What technology area does this patent fall under?
Primary CPC classification H04L65/403. Mapped technology areas include Electricity.
When was this patent published?
Publication date Tue Aug 09 2022 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 12 related publications on this page (citations in our corpus or others sharing the same primary CPC).