System and method for providing additional functionality to existing software in an integrated manner

• US 9,491,233 B2
• Filed: 02/22/2016
• Issued: 11/08/2016
• Est. Priority Date: 07/16/2013
• Status: Active Grant

• Current Assignee: Damaka, Inc.
• Original Assignee: Damaka, Inc.
• Inventors: Chaturvedi, Sivakumar, Gundabathula, Satish, Hiremath, Rashmi
• Primary Examiner(s): DORAIS, CRAIG C
• Application Number:
  US15/049,891
• Publication Number:
  US 20160173577A1
• Time in Patent Office: 260 Days
• Field of Search: None
• US Class Current: 1/1
• CPC Class Codes: G06F 15/167 using a common memory, e.g. mailbox
• CPC Class Codes: G06F 21/00 Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
• CPC Class Codes: G06F 9/44526 Plug-ins; Add-ons
• CPC Class Codes: G06F 9/54 Interprogram communication
• CPC Class Codes: G06F 9/541 via adapters, e.g. between incompatible applications
• CPC Class Codes: G06F 9/542 Event management; Broadcasting; Multicasting; Notifications
• CPC Class Codes: H04L 41/20 Network management software packages
• CPC Class Codes: H04L 41/28 Restricting access to network management systems or functions, e.g. using authorisation function to access network configuration
• CPC Class Codes: H04L 63/0457 wherein the sending and receiving network entities apply dynamic encryption, e.g. stream encryption cryptographic mechanisms or cryptographic arrangements for stream encryption H04L9/065
• CPC Class Codes: H04L 65/1069 Session establishment or de-establishment
• CPC Class Codes: H04L 65/1089 by adding media; by removing media
• CPC Class Codes: H04L 65/60 Network streaming of media packets
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/60 Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources admission control or resource allocation H04L47/70
• CPC Class Codes: H04M 1/724 User interfaces specially adapted for cordless or mobile telephones
• CPC Class Codes: H04N 2007/145 Handheld terminals
• CPC Class Codes: H04N 7/141 between two video terminals, e.g. videophone telephonic communication systems combined with television receiver for reception of entertainment or information matter H04M11/085
• CPC Class Codes: H04W 12/08 Access security

Abstract

An improved system and method are disclosed for improving functionality in software applications. In one example, the method includes a mobile device having a network interface, a processor, and a memory configured to store a plurality of instructions. The instructions include instructions for a superblock application having instructions for a function block included therein. The function block is configured to provide functions that are accessible to the superblock application via an application programming interface (API). The functions are provided within the superblock application itself and are accessible within the superblock application without switching context to another application on the mobile device.

Claims

1. A mobile device comprising:

a network interface;

a processor coupled to the network interface; and

a memory coupled to the processor and configured to store a plurality of instructions executable by the processor, the instructions including instructions for;

receiving, by a function block stored in the memory of the mobile device, a request for an audio/video (A/V) service from a superblock application stored in the memory of the mobile device;

determining, by the function block, that the superblock application is authorized to access A/V service functionality provided by the function block;

determining, by the function block, that the A/V service requires access to a resource that is external to the mobile device;

establishing, by the function block, the A/V service between the superblock application and the resource via the network interface, wherein the establishing is not supported by the superblock application;

providing, by the function block, video output for the A/V service to a video window within a display window of the superblock application on the mobile device, wherein the video window is displayed simultaneously with the display window of the superblock application on a screen of the mobile device; and

providing, by the function block, audio for the A/V service via the mobile device.

2. The mobile device of claim 1 wherein providing the A/V service includes operating, by the function block, as a bridge between the superblock application and the external device.

3. The mobile device of claim 1 wherein the request is an application programming interface (API) call from the superblock application to the function block.

4. The mobile device of claim 1 wherein the instructions further include initializing the function block, by the superblock application, when the superblock application is loaded into the memory and executed.

5. The mobile device of claim 1 wherein the instructions further include determining, by the function block, that the superblock application is authorized to access functionality provided by the function block for the A/V service.

6. The mobile device of claim 1 wherein the instructions further include providing at least one configuration parameter for the function block, wherein the configuration parameter enables the function block to be configured after the function block is distributed as part of the superblock application.

7. A mobile device comprising:

a network interface;

a processor coupled to the network interface; and

a memory coupled to the processor and configured to store a plurality of instructions executable by the processor, the instructions including instructions for;

receiving, by a function block stored in the memory of the mobile device, a request from an external device for a communication session with a superblock application that is stored in the memory of the mobile device, wherein the function block is configured to provide functionality for the communication session to the superblock application;

notifying, by the function block, the superblock application that the communication session is being requested by the external device;

establishing by the function block a connection with the external device via the network interface to support the communication session; and

providing, by the function block, the communication session to the superblock application, wherein the steps of receiving, notifying, establishing, and providing are performed without switching context from the superblock application to another application on the mobile device.

8. The mobile device of claim 7 wherein the instructions further include determining, by the function block, whether the function block has a capability to perform any rendering needed by the communication session.

9. The mobile device of claim 7 wherein the instructions further include determining, by the function block, whether the superblock has a capability to perform any rendering needed by the communication session.

10. The mobile device of claim 7 wherein the instructions further include determining, by the function block, that the superblock application is authorized to access functionality provided by the function block for the communication session.

11. The mobile device of claim 7 wherein the function block and the superblock application communicate via an application programming interface (API) provided by the function block.

12. A method comprising:

receiving, by a function block stored in a memory of a mobile device, a request from an external device for a communication session with a superblock application that is stored in the memory of the mobile device, wherein the function block is configured to provide functionality for the communication session to the superblock application;

notifying, by the function block, the superblock application that the communication session is being requested by the external device;

establishing, by the function block, a connection with the external device via a network interface of the mobile device to support the communication session; and

providing, by the function block, the communication session to the superblock application, wherein the steps of receiving, notifying, establishing, and providing are performed without switching context from the superblock application to another application on the mobile device.

13. The method of claim 12 wherein providing the communication session includes operating, by the function block, as a bridge between the superblock application and the external device.

14. The method of claim 12 wherein the request is an application programming interface (API) call from the superblock application to the function block.

15. The method of claim 12 further comprising determining, by the function block, whether the function block has a capability to provide the communication session.

16. The method of claim 12 further comprising determining, by the function block, whether the function block has a capability to perform any rendering needed by the communication session.

17. The method of claim 12 further comprising determining, by the function block, whether the superblock has a capability to perform any rendering needed by the communication session.

18. The method of claim 12 further comprising initializing the function block, by the superblock application when the superblock application is loaded into the memory and executed.

19. The method of claim 12 further comprising determining, by the function block, that the superblock application is authorized to access functionality provided by the function block for the communication session.

20. The method of claim 12 further comprising providing at least one configuration parameter for the function block, wherein the configuration parameter enables the function block to be configured after the function block is distributed as part of the superblock application.