Method and system for voicemail operations management
US-2015281458-A1 · Oct 1, 2015 · US
US10277749B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-10277749-B2 |
| Application number | US-201715471049-A |
| Country | US |
| Kind code | B2 |
| Filing date | Mar 28, 2017 |
| Priority date | Mar 28, 2017 |
| Publication date | Apr 30, 2019 |
| Grant date | Apr 30, 2019 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
A mobile device executes an operating system (OS) call manager and an over-the-top (OTT) calling application. The OTT calling application receives a notification for a first OTT call, and notifies the OS call manager of the first OTT call. The OS call manager assigns shared device resources of the mobile device to the first OTT call. The OTT calling application receives a notification for a second OTT call, and sends, to an OTT Telephony Application Server (TAS) without notifying the OS call manager of the second OTT call, a request to switch from the first OTT call to a second OTT call. The OTT calling app identifies the first OTT call as inactive and the second OTT call as active, and allocates the shared device resources assigned to the first OTT call to the second OTT call.
Opening claim text (preview).
What is claimed is: 1. A method, comprising: executing, at a mobile device, an operating system (OS) call manager and an over-the-top (OTT) calling application (app); receiving, at the OTT calling app, a notification for a first OTT call; sending, by the OTT calling app, an internal notification to the OS call manager, wherein the internal notification notifies the OS call manager of the first OTT call; assigning, by the OS call manager, shared device resources of the mobile device to the first OTT call; receiving, at the OTT calling app, a notification for a second OTT call; sending, from the OTT calling app to an OTT Telephony Application Server (TAS) without notifying the OS call manager of the second OTT call, a request to switch from the first OTT call to the second OTT call; identifying, by the OTT calling app, the first OTT call as inactive and the second OTT call as active; and allocating, by the OTT calling app, the shared device resources assigned to the first OTT call, to the second OTT call. 2. The method of claim 1 , wherein the first OTT call comprises a Voice over Internet Protocol (VoIP) call. 3. The method of claim 1 , wherein the OS call manager comprises operating system software that manages incoming and outgoing calls, including calls to and from a Mobile Directory Number (MDN) associated with the mobile device and including incoming and outgoing OTT calls. 4. The method of claim 1 , wherein the shared device resources comprise a speaker and a microphone of the mobile device. 5. The method of claim 1 , further comprising: designating, by the OS call manager if the first OTT call is accepted by a user of the mobile device, the first OTT call as active; and inactivating any active Mobile Directory Number (MDN) calls. 6. The method of claim 1 , wherein the OS call manager, if the second OTT call is accepted by a user of the mobile device, does not change any call statuses due to the OTT calling app not notifying the OS call manager of the second OTT call. 7. The method of claim 1 , further comprising: placing, by the OTT calling app, the first OTT call on hold subsequent to identifying the first OTT call as inactive. 8. The method of claim 1 , further comprising: determining, by the OTT calling app, if the second OTT call has ended; sending, by the OTT calling app to the OTT TAS, a message indicating termination of the second OTT call; designating, by the OTT calling app, the second OTT call status as terminated; and removing the second OTT call from the OTT calling app user interface. 9. A mobile device, comprising: one or more communication interfaces; and a processing unit configured to execute an operating system (OS) call manager and an over-the-top (OTT) calling application (app) and further configured to: receive, via the one or more communication interfaces by the OTT calling app, a notification for a first OTT call, send, by the OTT calling app, an internal notification to the OS call manager, wherein the internal notification notifies the OS call manager of the first OTT call, assign, by the OS call manager, shared device resources of the mobile device to the first OTT call, receive, via the one or more communication interfaces by the OTT calling app, a notification for a second OTT call, send, via the one or more communication interfaces, from the OTT calling app to an OTT Telephony Application Server (TAS) without notifying the OS call manager of the second OTT call, a request to switch from the first OTT call to the second OTT call, identify, by the OTT calling app, the first OTT call as inactive and the second OTT call as active, and allocate, by the OTT calling app, the shared device resources assigned to the first OTT call, to the second OTT call. 10. The mobile device of claim 9 , wherein the first OTT call comprises a Voice over Internet Protocol (VoIP) call. 11. The mobile device of claim 9 , wherein the OS call manager comprises operating system software that manages incoming and outgoing calls, including calls to and from a Mobile Directory Number (MDN) associated with the mobile device and including incoming and outgoing OTT calls. 12. The mobile device of claim 9 , wherein the shared device resources comprise a speaker and a microphone of the mobile device. 13. The mobile device of claim 9 , wherein the processing unit is further configured to: designate, by the OS call manager if the first OTT call is accepted by a user of the mobile device, the first OTT call as active, and inactivate any active Mobile Directory Number (MDN) calls. 14. The mobile device of claim 9 , wherein the OS call manager, if the second OTT call is accepted by a user of the mobile device, does not change any call statuses due to the OTT calling app not notifying the OS call manager of the second OTT call. 15. The mobile device of claim 9 , wherein the processing unit is further configured to: place, by the OTT calling app, the first OTT call on hold subsequent to identifying the first OTT call as inactive. 16. The mobile device of claim 9 , wherein the processing unit is further configured to: determine, by the OTT calling app, if the second OTT call has ended; send, by the OTT calling app to the OTT TAS, a message indicating termination of the second OTT call; designate, by the OTT calling app, the second OTT call status as terminated; and remove the second OTT call from the OTT calling app user interface. 17. A non-transitory storage medium storing instructions executable by a mobile device, wherein the instructions comprise instructions to cause the mobile device to: execute an operating system (OS) call manager and an over-the-top (OTT) calling application (app); receive, by the OTT calling app, a notification for an incoming first OTT call; send, by the OTT calling app, an internal notification to the OS call manager, wherein the internal notification notifies the OS call manager of the first OTT call; assign, by the OS call manager, shared device resources of the mobile device to the first OTT call; receive, by the OTT calling app, a notification for an incoming second OTT call; send, from the OTT calling app to an OTT Telephony Application Server (TAS) without notifying the OS call manager of the second OTT call, a request to switch from the first OTT call to a second OTT call; identify, by the OTT calling app, the first OTT call as inactive and the second OTT call as active; and allocate, by the OTT calling app, the shared device resources assigned to the first OTT call, to the second OTT call. 18. The non-transitory storage medium of claim 17 , wherein the first OTT call comprises a Voice over Internet Protocol (VoIP) call. 19. The non-transitory storage medium of claim 17 , wherein the OS call manager comprises operating system software that manages incoming and outgoing calls, including calls to and from a Mobile Directory Number (MDN) associated with the mobile device and including incoming and outgoing OTT calls. 20. The non-transitory storage medium of claim 17 , further comprising instructions to cause the mobile device to: place, by the OTT calling app, the first OTT call on hold subsequent to identifying the first OTT call as inactive.
Application servers providing network services (systems providing special services to telephonic subscribers H04M3/42) · CPC title
Electricity · mapped topic
Arrangements for signalling the class or number of called or calling line from one exchange to another · CPC title
where the session control protocols comprise SIP and SS7 · CPC title
Networks other than PSTN/ISDN providing telephone service, e.g. Voice over Internet Protocol (VoIP) , including next generation networks with a packet-switched transport layer (H04L65/00 takes precedence; aspects not specific to the type of network H04M3/00; special services in those networks H04M3/42) · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.