# US 2014/0109108 A1 · Real-Time Communications Client Architecture

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2014/0109108 A1
- Document ID: US20140109108A1
- Status: Published application
- Kind: A1
- Application number: 14/108,262
- Filed: 2013-12-16
- Published: 2014-04-17
- Earliest claimed: 2012-06-19
- Assignees: ecrio, inc.
- Applicants: Ecrio, Inc.
- Inventors: Krishnakumar Narayanan; Michel E. Gannage
- Web page: https://patentgrep.com/patent/US20140109108A1

## CPC

- G06F 9/54: Interprogram communication
- H04W 52/028: {switching on or off only a part of the equipment circuit blocks}
- Y02D 30/70: in wireless communication networks
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)
- Y02D: CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE

## Abstract

A distributed services modular client architecture may be used to implement IP-based real time communication services in a flexible manner among a wide variety of different types of chip sets and systems-on-chip. The various services are distributed among one or more processor cores, at least one of which is a low power core, in accordance with a number of factors, including power consumption, media latency, on-time, performance, and other considerations. A processor “core” may refer to a processor itself where the processor has only a single core, and may also refer to a “core” of a multicore processor. The architecture uses a SIP/IMS framework, and is modularized by placing certain services into their own framework so that a particular service may be plugged into the SIP/IMS framework if and when desired, and otherwise omitted. The frameworks may be installed on various processor cores within the chip set or system-on-chip, including in particular the low power core, to allow for more effective power conservation without unduly sacrificing performance.

## Claims

### Claim at position 1

-6. (canceled)

### Claim 7

A real-time communications client architecture for a mobile digital device having a plurality of processors disposed therein, comprising:
a Session Initiation Protocol/Internet Protocol Multimedia Subsystem (“SIP/IMS”) framework installed on a first one of the processors, the SIP/IMS framework having an interface; and
a first framework for a real-time communications service installed on a second one of the processors other than the first processor, the first framework having an interface;
the interfaces of the SIP/IMS framework and the first framework being coupled to one another for handling communications between the SIP/IMS framework and the first framework.

### Claim 8 (depends on 7)

The real-time communications client architecture of claim 7 wherein the first processor is a communication processor.

### Claim 9 (depends on 8)

The real-time communications client architecture of claim 8 wherein the second processor is an application processor.

### Claim 10 (depends on 9)

The real-time communications client architecture of claim 9 wherein:
the communication processor is a single core processor; and
the application processor is a single core processor.

### Claim 11 (depends on 9)

The real-time communications client architecture of claim 9 wherein:
the communication processor is a single core processor; and
the application processor is a multi-core processor.

### Claim 12 (depends on 9)

The real-time communications client architecture of claim 9 wherein:
the communication processor is a multi-core processor; and
the application processor is a multi-core processor.

### Claim 13 (depends on 9)

The real-time communications client architecture of claim 9 wherein:
the communication processor is a multi-core processor; and
the application processor is a single core processor.

### Claim 14 (depends on 7)

The real-time communications client architecture of claim 7 wherein the first processor is an application processor.

### Claim 15 (depends on 14)

The real-time communications client architecture of claim 14 wherein the second processor is a communication processor.

### Claim 16 (depends on 7)

The real-time communications client architecture of claim 7 wherein:
the interface of the SIP/IMS framework is an inter-processor interface; and
the interface of the first framework is an inter-processor interface.

### Claim 17 (depends on 7)

The real-time communications client architecture of claim 7, wherein the first processor comprises a battery saver core.

### Claim 18 (depends on 7)

The real-time communications client architecture of claim 7, wherein the second processor comprises a battery saver core.

### Claim 19 (depends on 7)

The real-time communications client architecture of claim 7, wherein the first framework is one of a Voice over Internet Protocol (“VoIP”) framework, a video framework, a VoIP and video framework, a Rich Communications Services (“RCS”) framework, and a Short Message Service (“SMS”) over Internet Protocol Multimedia Subsystem (“IMS”) framework.

### Claim 20 (depends on 7)

The real-time communications client architecture of claim 7, further comprising:
a second framework for a real-time communications service installed on one of the first processor and the second processor, the second framework having an interface;
the interfaces of the SIP/IMS framework and the second framework being coupled to one another for handling communications between the SIP/IMS framework and the second framework.

### Claim 21 (depends on 20)

The real-time communications client architecture of claim 20, wherein the interfaces of the SIP/IMS framework and the first framework are coupled to one another, and the interfaces of the SIP/IMS framework and the second framework are coupled to one another, for handling communications between the SIP/IMS framework and the first and second frameworks when active at the same time.

### Claim 22 (depends on 20)

The real-time communications client architecture of claim 20, wherein:
the first framework is one of a Voice over Internet Protocol (“VoIP”) framework, a video framework, a VoIP and video framework, a Rich Communications Services (“RCS”) framework, and a Short Message Service over Internet Protocol Multimedia Subsystem (“SMS over IMS”) framework; and
the second framework is one of a VoIP framework, a video framework, a VoIP and video framework, a RCS framework, and a SMS over IMS framework.

### Claim 23

A real-time communications client architecture for a mobile digital device having a communication processor and an application processor, comprising:
a Session Initiation Protocol/Internet Protocol Multimedia Subsystem (“SIP/IMS”) framework installed on the communication processor, the communication processor having an inter-processor interface;
a plurality of frameworks for respective real-time communications services comprising at least one of a Voice over Internet Protocol (“VoIP”) framework, a video framework, a VoIP and video framework, a Rich Communications Services (“RCS”) framework, and a Short Message Service (“SMS”) over Internet Protocol Multimedia Subsystem (“IMS”) framework installed on the application processor, the application processor having an inter-processor interface;
the inter-processor interfaces of the communication processor and the application processor being coupled to one another for handling communications between the SIP/IMS framework and the real-time communications services frameworks.

### Claim 24 (depends on 23)

The real-time communications client architecture of claim 23 further comprising a Voice over Internet Protocol (“VoIP”) framework installed on the communication processor.

### Claim 25 (depends on 23)

The real-time communications client architecture of claim 23 further comprising a Short Message Service over Internet Protocol Multimedia Subsystem (“SMS over IMS”) framework installed on the communication processor.

### Claim 26 (depends on 23)

The real-time communications client architecture of claim 23 further comprising a Voice over Internet Protocol (“VoIP”) framework and a Short Message Service over Internet Protocol Multimedia Subsystem (“SMS over IMS”) framework installed on the communication processor.

### Claim 27 (depends on 23)

The real-time communications client architecture of claim 23 further comprising a Voice over Internet Protocol (“VoIP”) framework, a video framework, and a Short Message Service over Internet Protocol Multimedia Subsystem (“SMS over IMS”) framework installed on the communication processor.

### Claim 28 (depends on 23)

The real-time communications client architecture of claim 23 further comprising a Voice over Internet Protocol (“VoIP”) and video framework, and a Short Message Service over Internet Protocol Multimedia Subsystem (“SMS over IMS”) framework installed on the communication processor.