QELS 2-Intro To QChat and Ecosystem

March 7th 2014, Qualcomm Technologies, Inc.
QELS:Intro to QChat and Ecosystem
1
CONFIDENTIAL AND PROPRIETARY - QUALCOMM TECHNOLOGIES, INC. MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION
QChat Introduction
Qchat Ecosystem
Discussion and Review
Agenda
2
QChat Introduction
What is QChat
QChat is a Voice-over-IP (VoIP) application that offers half-duplex communication
between one-to-one and one-to-many endpoints.
One-to-one (private call)
One-to-many (group call)
4
QChat features
As a QChat user, you can:
Establish QChat calls
Alert other users that communication is desired
Invite and add members to established calls
Restrict incoming and outgoing calls
Make group calls
5
QChat design goals

The QChat System was designed to:
Instant access
Always on
Guaranteed talk permit
Reduce latency (Push-to-Talk [PTT] and end-to-end media)
Operate over standard WCDMA
Use open protocols
Communicate with any IP-enabled wireless device
Deploy on off-the-shelf hardware
Interoperate with multiple carrier deployments
6
QChat call types
Direct Call
Simplest type of QChat call
Member list includes only the originator and target (one-to-one)
Originator indicates on-the-fly who they want to call
Enables urgent communication between two users
Half-duplex two-way communication
Forced audio
Configured to chirp before
communication
8
Ad Hoc group call

One-to-many calling
3 to 25 people allowed in call
Forced audio
Any participant can invite other users
or groups to join the call
Allow call to continue when exiting a
group call
Member list
Created on-the-fly
Can be stored locally on mobile device
for future use by user if desired
Not shared among users
9
Ad Hoc group name

Originator allowed to select name for
ad hoc group
User defined name identifies group
Group name can be used for restart
Name not required to be unique
across QChat system
10
Ad Hoc group invite

Originator starting a call can invite
other users or groups to join the
call on the fly
Targets receive an invitation to join
the call which they can accept or
reject
They must explicitly join the call in
order to participate
No forced audio for invitation recipients
Lets see who

has time to chat
about the party
last night
11
Adding new members to a call in progress

Anyone participating in a direct call or ad
hoc group call may add new members
or groups
Newly added members receive an
invitation to join the call
User must take action to join
No forced audio to newly added members
Member:
When will
the report
be ready?
Member:
Need to ask
Tim. Hang on.
New Member:
Report? Jen is
working on it,
lets ask her.
12
Summary: Adding new members
I am participating
in . . .
Can I add a
participant?
When new participant joins .

..
Direct call
Yes, you can invite an

individual or group to join
The invited party must accept to

join, so no forced audio
Ad hoc group
Yes, you can invite an

individual or group to join
The invited party must accept to

join, so no forced audio
13
Add member disable

Call originator sets add member disable option to disable in the call setup
request
Prevents the targets of a call from adding members to the call for the duration
of the call instance
Can be performed per call
14
QChat alerts
Can be used
To notify a target user that communication is desired
Instead of a chirp or voice as a polite way to start a PTT session
A saved alert appears on the recent call list on the mobile device (similar to a
call log for regular voice calls). The user can select the alert in the list to
initiate a QChat call to the originator of the alert.
15
Group in-call status

Provides information to all call participants about their current call.
Supported call types are:
Ad hoc group call
The following events trigger status updates:

Initial call setup
Participants joining or leaving the call
Add member invite transaction is complete
16
Restrictions and controls
17
Call restrictions
Limits communication between subscribers
Defines who a subscriber can call
Defines who can call a subscriber
Allow, Deny or Force communication
User has strict control on

QChat traffic to/from his
device
Operator level
Takes precedence over user level
User level
Block all calls of certain type

From a certain user or all users
Defined by the user
Maintained on the client
Cannot override or conflict with operator level
18
Call restrictions (cont.)

Call type restrictions can also be defined to
Block all calls of certain type
Restrict a certain user or all users
Prevent inter-operator calling
19
Call type provisioning

Users can be provisioned to originate or participate in types of QChat calls
20
Call scenarios
21
Intra-regional call, inter-regional call and latency

Intra-regional call
All members, including the originator, are registered within the
same region.
Call establishment and media delivery latency impact varies
depending on call type Direct or ad hoc
Inter-regional call
An inter-regional call is one in which any member, including the
originator, is located in a different region than other members
PTT latency and end-to-end media latency is greater than intraregional call
22
QChat Regions
QChat Region 1
QChat Region 2
QChat Region 3
QChat
Core
Core in MXC
Region 1 Mexico
Region 2 Monterrey
Region 3 Guadalajara
Region 4 Tijuana
Region 5 - Merida
QChat Region n
23
Inter-carrier call
Originator and target(s) are located in two or more QChat carrier networks
Requires communication between two or more QChat carrier networks to
establish the call
At least one call member (originator or target) is registered in a different
carrier network than the carrier network hosting the call
Also known as a cross-carrier call
MEXICO
CHILE
24
Inter-operability call scenarios

Originator or target(s) is located in a QChat network and at least one other
participant is located in a foreign dispatch network (for example, iDEN).
Types of PTT features supported between QChat and iDEN users are:
Direct call, QChat originated

Direct call, iDEN originated
Ad hoc group call, QChat originated, QChat hosted
Ad hoc group call, iDEN originated, iDEN hosted
Alert QChat originated
Alert iDEN originated
Types of PTT features Unsupported:

Add member feature for QChat originated
Add member feature for iDEN originated
MEXICO - QCHAT
MEXICO- IDEN
25
QChat addressing
A QChat device may have up to three unique user addresses
The user address is exchanged between QChat users as contact information
Any of the provisioned user addresses can be used to make calls
Format
SIP address: <username>@<domain>
PTN address: <unique_id>
UFMI address: <x*x*x>
Allows alias addresses for interoperability

Address 1:
525563020456@nexteldata.com.mx
Address 2:
525563020456
Address 3:
42*1048502*25
26
QChat call termination

Call termination
Talk inactivity timer expires (known as hang-time timer)
or
All participants leave
Hang-time timer values

Operator configurable
Hang-time timers are defined:
Direct calls
Ad hoc group calls
Failsafe timer
The configurable failsafe timer revokes the floor
Ends one users permission to talk
27
Qchat Introduction
QChat Ecosystem
Agenda
28
QChat Ecosystem
29
The QChat system

The big picture
RNS 1
PDSN / GGSN
R3
R1
BTS / Node B
BSC / RNC
PCF / SGSN
Operator
gateway
R2
RNS 2
QAS farm
QChat
device
PCF / SGSN
Service provider
network
QChat servers
BTS / Node B
End users
BSC / RNC
QChat
device
30
QChat ecosystem
31
QChat ecosystem
Operator Wide Area Network
Comprises existing components in the Operator network, as well as QChat
recommended components.
QChat Core Network

Comprises the database and the QChat component that stores the location of every
subscriber in the QChat system.
QChat Regional Network

Comprises multiple servers within each QChat component, as well as multiple DNS
and SIP Registration Manager Servers.
Packet Core Network

Comprises standard components used to provide mobile data functionality
Radio Access Network

Base stations and controllers provide standards based RF interface
32
QChat ecosystem (cont.)

Presence
Server
Provisioning
System
User / Group
Database
Authentication
Server (AAA)
Operator
Billing
System
Network
Management
System
DNS
LID
Administration
Console
Operator Wide Area Network
OMC-QC
Core
Lawful Intercept
Server
LOM
Home
Dispatcher
Legend
Database
Front End
Carrier-supplied
components
QChat-supplied
components
QChat Core Network
DNS
OMC-QC
LOM
Regional
Location
Server
Regional
Dispatcher
Media
Control
Complex
Regional
Usage
Log Server
Regional
Gateway
Regional
Lawful Intercept
Server
Lawful
Enforcement
Agency
QChat Regional Network
33
QChat handset architecture

OEM
Prov App
OEM
Custom App
(Tone Play, DB
Storage)
OEM
UI APP
OEM customer
interface
QChat interface
App Framework
(BMP/Android)
Application Adaptation Layer

(QAAL or QBAL)
QChat
private interface
Processor boundary
(if applicable, ex: Android)
Legend
QChat interface
QChat Platform Independent Client (PIC)
QChat
private interface
AMSS
QChat Optimizations
(UPK)
OEM customer
interface
OEM Concurrency
Management
Implemented by Qualcomm
and used by OEMs for UI
development
QChat private interface

OEM customer interface
Defined by Qualcomm and
implemented by OEMs
34
QAS subcomponent and interface diagram

Presence information
SBC user registration
iDEN routing table updates
CAT
(Has interfaces to
CID, CRH, DCH,
MCH, RULS, and
GCH)
Core
components
Lawful intercept provisioning
LMF
Lawful intercept information
MySQL
Lawful
intercept
information
RULS
ASN.1
lawful
intercept
information
LDF
HTTP lawful
intercept
provisioning
LAC
XCAP-provisioned user information lookup
DFE
ODBC user/Group information lookups

RADIUS user authentication
LEA
Migrated user deletion
HAD
HAD
HAD
Provisioned user information lookup
AAA
User registration information updates
MySQL
Billing information
RADIUS
user authentication
Operator
database
User registration
Floor control/Group in-call status/In-call user management

Registration complete indication
Call setup/User add/User late join
Media
Billing information/Lawful intercept information
User registration
subscription
DCH
Call termination
In-call user management/Floor control/Call termination
SBC
Media
Alerts/Call establishment/Call
termination/In-call user management/
Floor control/Group in-call status
Alerts/Call establishment/Call termination/

In-call user management/Floor control/Group in-call status
GMH*
Media
GCM*
Media session establishment/

Media session management/
Media session teardown
GCH*
Presence
CID
User cache
sync
Presence notifications
subscriptions
CCD
User presence
information
MySQL
RPD*
RPD
RPD
Group presence information
Predefined group
information synchronization
RGA
RGA
RGA
Predefined group information download
MySQL
Local Operations and Maintenance (in the core and each region)
Group lookup
Interregional group lookups/
Interregional group updates
SWL
(ssh interface to all
subcomponents)
iDEN user location cache updates/

iDEN user location cache lookups/
iDEN user UFMI routing table updates/
iDEN user UFMI routing table lookups
Call establishment/Call termination/

In-call user management/Floor
IGW
control/Group in-call status
iDEN user location cache sync/

iDEN user UFMI routing table sync
GSR
GSR
GSR
Presence
Server
Shared LOM
database access
LML
(SNMP interface to
all subcomponents)
MyS
QL
Shared LOM database access
GSR
GSR
GSR
GCF*
Software management
Diagnostic log management
MySQL
Gateway
Fault
management
MBCP Floor
control/Media
GICH
User presence
information
Shared LOM
database access
Media session establishment/

Media session management/
Media session teardown
Other
QChat
operators
GIMH
Alerts/Call setup/User late join
In-call user management/Floor control/

Group in-call status/Call termination
User cache
updates
Group lookup/Ad hoc group updates
Alerts/Call setup/
User add/User late join
Media
CRH
CRH
CRH
User cache updates
User presence information
Media
Floor
control
User registration
notifications
Predefined group information download
RMM
User lookup
Call setup/User add/

User late join/MCH load
information/Call termination
Predefined group information subscription and notifications

User late join/MCU load information
MCH
RLS
User lookup
Media Control Unit
Performance attribute
management
Shared LOM
database access
PML
(SNMP interface to
all subcomponents)
Software management/
Configuration management/
Performance management/
Diagnostic management
Fault management
iDEN user lookup

DGL
(ssh interface to all
subcomponents)
FML
(SNMP interface to
all subcomponents)
Web services (SOAP/XML)

Northbound interface
OMC-QC*
NMS
MySQL
Sliced component
text
text
Highly available
component
Component w/
MySQL DB MySQL
Pooled
component
Vendorsupplied
SIP
QSP/Media
RADIUS
MySQL
ODBC/XCAP
MTL
Request
Response
SOAP
HTTP
Web services
(SOAP/XML) GUI
Group
Msg
* Optional componentonly required if

corresponding feature is enabled
User Interface
35
Client registration handler

DFE
HAD
HAD
HAD
HAD
MySQL
User registration information updates

Provisioned user information lookup
User registration
subscription
User registration
notifications
User cache
updates
CRH
CRH
CRH
CRH
RLS
User registration
CID
User cache
updates
Registration complete indication
CCD
MySQL
36
Dispatch call handler

RULS
Billing information/Lawful
intercept information
MCC
Call setup/User add/User late join

User
lookup

User late join/MCU
load information
CID
DCH
Group lookup/Ad hoc group updates
GSR
GSR
GSR
GSR
37
Sample Message Flow by Component

Originator
joe
RLS
RD
HD
DFE
MCC
TARGET
jack
RULS
Hello Carrier
Where am I?
ok
Hello QChat
Registration
ok
Hello Carrier
ok
joe@11.12.13.14
is here
ok
Who is joe@11.12.13.14
joe@ourdomain
joe@ourdomain = joe@11.12.13.14
ok
Regional Boundary
Welcome to QChat
ACK
CALL myGroup@ourdomain
One Moment
I know joe who is jack?

jack@12.34.56.78
Direct Call
Hey jack, joe is calling

Your call is ready!
Thanks!
Ok great!
Mr. MCC Please take care of joe and jack
Sure thing!
Log call
ok
ok
Hello jack,
I will be your operator,
joe has the floor
ok
QSP/RTP
QSP/RTP
Hello joe I will be your operator, you have the floor
38
QChat Client registration flow

Regional Dispatcher
Client
RLS
CRH
CID(s)
Home Dispatcher
CCD
HAD
DFE
REGISTER
NOTIFY
200 OK
200 OK
GetUserDataRequest
GetUserDataReply
Protocol
version
OK
Load Reg Info

Load Reg Response
LOAD Reg Info

LOAD Reg Info
INFO (service available)
ACK (accept)
QChat Registration
39
Direct call setup flow

Regional Dispatcher
Originator:
Client A
CALL B
DCH
CID
MCC
Client B
RULS
Lookup originator by IP
Originator Info
ACK (accept)
Lookup target client
Client Info
Matching vocoder found
MCC selected
ANNOUNCE (invite)
ACK (accept)
STATUS (success)
ACK (accept)
Handle Call
Handle Call Resp (success)
Send UDE
CONTACT
CONTACT ACK
QSP/RTP
CONTACT
CONTACT ACK
QSP/RTP
40
QChat application protocols

All QChat application layer protocols operate over standard Internet-based
network protocol stacks
The illustration shows protocol stacks for a QChat Client, the QAS, and the
air interface infrastructure, which is the interface between the two entities
QChat client
Vocoder
SIP
QSP
RTP
TCP/UDP
TCP/UDP
TCP/UDP
Air interface and data

network
infrastructure
QChat servers
SIP
QSP
RTP
TCP/UDP
TCP/UDP
TCP/UDP
IP
IP
PPP/PDP
PPP/PDP
RLP
RLP
RF physical layer
RF physical layer
Ethernet
(for example)
41
Network Management
Overview
42
Network management configuration
43
OMC-QC
Menu bar
Navigation
Tree
Display Pane:
The content of this pane is based on the node
selected in the Navigation Tree
Fault Status
Table
44
Qchat Introduction
QChat Ecosystem
Agenda
45
Questions?
For QELS Intro to QChat course:
Alin Barrera Gonzalez
alinb@qti.qualcomm.com
QELS general Info:

Ricardo Anaya Puebla
ranaya@qti.qualcomm.com
QELS Training info:
Sandra Medina
smedina@qti.qualcomm.com
Reference documents:
- QC01-E Introduction to QChat 4.x (Module 1,2,3)
- 4.x QC02 QChatSysOverview
46
Thank you
Follow us on:
For more information on QTI, visit us at:
www.QTI.com & www.QTI.com/blog
QTI is a trademark of QTI Incorporated, registered in the United States and other countries.
Other products and brand names may be trademarks or registered trademarks of their respective
owners
47
Qualcomm Technologies, Inc.

5775 Morehouse Drive
San Diego, CA. 92121-1714
U.S.A.
2013 Qualcomm Technologies, Inc.
All rights reserved.
Not to be used, copied, reproduced in whole or in part, nor its contents revealed in any manner to others without the express written permission of Qualcomm Technologies, Inc.
This technical data may be subject to U.S. and international export, re-export or transfer (export) laws. Diversion contrary to U.S. and international law is strictly prohibited.
Qualcomm, Brew, Brew MP, the Brew MP logo, Brew SDK, MobileShop, mShop, MSM, Plaza, the Plaza logo, Plaza Retail, QChat, the QChat logo, QPoint, the QPoint logo, uiOne, and Yagatta are
trademarks of QUALCOMM Incorporated, registered in the United States and other countries.
YagattaTalk, Vuforia, and the Brew logo are trademarks of QUALCOMM Incorporated.
Alljoyn and Vellamo are trademarks of Qualcomm Innovation Center, Inc., registered in the United States and other countries.
iSkoot is a trademark of Qualcomm Connected Experiences, registered in the United States and other countries.
Social Source and Zynto are trademarks of Qualcomm Connected Experiences.
Consia and Haystack are trademarks of Xiam Technologies Limited.
All QUALCOMM Incorporated trademarks are used with permission. Other product and brand names may be trademarks or registered trademarks of their respective owners.
QELS QChat Enhanced Local Support

March 7th, 2014
48

QELS 2-Intro To QChat and Ecosystem

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

QELS 2-Intro To QChat and Ecosystem

Transféré par

Droits d'auteur :

Formats disponibles

March 7th 2014, Qualcomm Technologies, Inc.

QELS:Intro to QChat and Ecosystem

Discussion and Review

One-to-one (private call)

One-to-many (group call)

QChat design goals

QChat call types

Ad Hoc group call

Ad Hoc group name

Ad Hoc group invite

Lets see who

Adding new members to a call in progress

Summary: Adding new members

When new participant joins .

Yes, you can invite an

The invited party must accept to

Yes, you can invite an

The invited party must accept to

Add member disable

Group in-call status

The following events trigger status updates:

Restrictions and controls

User has strict control on

Block all calls of certain type

Call restrictions (cont.)

Call type provisioning

Intra-regional call, inter-regional call and latency

Inter-operability call scenarios

Direct call, QChat originated

Types of PTT features Unsupported:

Allows alias addresses for interoperability

QChat call termination

Hang-time timer values

Discussion and Review

The QChat system

QChat Core Network

QChat Regional Network

Packet Core Network

Radio Access Network

QChat ecosystem (cont.)

Operator Wide Area Network

QChat Core Network

QChat Regional Network

QChat handset architecture

Application Adaptation Layer

QChat Platform Independent Client (PIC)

QChat private interface

QAS subcomponent and interface diagram

Lawful intercept information

ODBC user/Group information lookups

Provisioned user information lookup

User registration information updates

Floor control/Group in-call status/In-call user management

In-call user management/Floor control/Call termination

Alerts/Call establishment/Call termination/

Media session establishment/

Predefined group information download

iDEN user location cache updates/

Call establishment/Call termination/

iDEN user location cache sync/

Shared LOM database access

Diagnostic log management

Media session establishment/