qels 2-intro to qchat and ecosystem

7/18/2019 QELS 2-Intro to QChat and Ecosystem

http://slidepdf.com/reader/full/qels-2-intro-to-qchat-and-ecosystem 1/48

CONFIDENTIAL AND PROPRIETARY - QUALCOMM TECHNOLOGIES, INC. MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

QELS:Intro to QChat and Ecosyste

March 7th 2014, Qualcomm Technologies, Inc.



QChat Introduction

1Qchat Ecosystem

2

Agenda

3Discussion and R





QChat Introduction




What is QChat

QChat is a Voice-over-IP (VoIP) application that offers half-duplex c

between one-to-one and one-to-many endpoints.

One-to-one (private call) One-to-many (group call)




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




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





QChat call types



Direct 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 beforecommunication

Simplest type of QChat call




One-to-many calling3 to 25 people allowed in call

Forced audio

Any participant can invite other usersor 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 devicefor future use by user if desired

− Not shared among users

Ad Hoc group call




Originator allowed to select name forad hoc group

User defined name identifies group

Group name can be used for restart

Name not required to be unique

across QChat system

Ad Hoc group name




Originator starting a call can inviteother 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

Ad Hoc group invite

Let’s see who

has time to chatabout the partylast night




Summary: Adding new members

I am participatingin . . .

Can I add aparticipant?

When new participant jo. .

Direct callYes, you can invite anindividual or group to join

The invited party must accept join, so no forced audio

Ad hoc groupYes, you can invite anindividual or group to join

The invited party must accept join, so no forced audio




Call originator sets add member disable option to disable in the carequest

Prevents the targets of a call from adding members to the call for tof the call instance

Can be performed per call

Add member disable




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 (scall log for regular voice calls). The user can select the alert in the initiate a QChat call to the originator of the alert.

QChat alerts




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

Group in-call status



http://slidepdf.com/reader/full/qels-2-intro-to-qchat-and-ecosystem 17/48CONFIDENTIAL AND PROPRIETARY - QUALCOMM TECHNOLOGIES, INC. MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

Restrictions and controls



Limits communication between subscribers

− Defines who a subscriber can call− Defines who can call a subscriber

− Allow, Deny or Force communication

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

Call restrictionsUser has strict

QChat traffic to

device




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

Call restrictions (cont.)




Users can be provisioned to originate or participate in types of QCha

Call type provisioning





Call scenarios



Intra-regional call

All members, including the originator, are registered within thesame region.

Call establishment and media delivery latency impact variesdepending on call type Direct or ad hoc

Inter-regional call

An inter-regional call is one in which any member, including theoriginator, is located in a different region than other members

PTT latency and end-to-end media latency is greater than intra-regional call

Intra-regional call, inter-regional call and latenc




QChat Regions


QChat Region 1

QChat Region 2

QChat Region 3

QChat Region n

…

Core in MXC

Region 1 – Mexico

Region 2 – Monterrey

Region 3 – Guadalajara

Region 4 – Tijuana

Region 5 - Merida



Originator and target(s) are located in two or more QChat carrier n

Requires communication between two or more QChat carrier netwestablish the call

At least one call member (originator or target) is registered in a dicarrier network than the carrier network hosting the call

Also known as a cross-carrier call

Inter-carrier call

MEXICO CHILE




Originator or target(s) is located in a QChat network and at least onparticipant is located in a foreign dispatch network (for example, iDE

Types of PTT features supported between QChat and iDEN users a

− 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

Inter-operability call scenarios

MEXICO - QCHAT




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

QChat addressing

Address 1:

[email protected]

Address 2:

525563020456

Address 3:

42*1048502*25




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 user’s permission to talk

QChat call termination




1

Agenda

3Discussion and R

2QChat EcosystemQchat Introduction





QChat Ecosystem



The QChat system

The big picture

QChatdevice

BTS / Node BBSC / RNC

PDSN / GGSN

Service providernetwork

R1

QAS farm

R3

R2

Ope

gate

RNS 1

QChat

device

BTS / Node B BSC / RNC

RNS 2

PCF / SGSN

PCF / SGSN

QChat servers

End users




QChat ecosystem




QChat ecosystem


Operator Wide Area Network

− Comprises existing components in the Operator network, as well as QChatrecommended components.

QChat Core Network

− Comprises the database and the QChat component that stores the location osubscriber in the QChat system.

QChat Regional Network

− Comprises multiple servers within each QChat component, as well as multipland 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



QChat ecosystem (cont.)

PresenceServer

ProvisioningSystem

User / GroupDatabase

AuthenticationServer (AAA)

Operator Billing

System

NetworkManagement

System DNS

LID Administration

Console

Operator Wide Area Network

QChat Core Network

QChat Regional Network

MediaControl

Complex

RegionalUsage

Log Server RegionalGateway

RegionalLawful Intercept

Server

RegionalDispatcher

RegionalLocationServer LOMOMC-QCDNS

LOM

CoreLawful Intercept

Server OMC-QCHome

Dispatcher DatabaseFront End




QChat handset architecture

OEM Concurrency

Management

QChat Optimizations

(UPK)

QChat Platform Independent Client (PIC)

Application Adaptation Layer

(QAAL or QBAL)

OEM

Prov App

OEM

UI APP

OEMCustom App

(Tone Play, DB

Storage)

Processor boundary(if applicable, ex: Android)

QChatprivate interface

OEM customerinterface

App Framework

(BMP/Android)

AMSS

QChat

private interface

OEM customerinterface

QChat interface

Legend

QChat interfaceImplemented by Q

and used by OEMsdevelopment

QChat private int

OEM customer inDefined by Qualco

implemented by O




Client registration handler

HADHADHADHAD

MySQL

DFE

CCD

MySQL

CID

CRHCRHCRHCRH

RLS

Provisioned user information lookup

User registration information updates

User cache

updates

U s e r c a c h e

u p d a t e s

User registration

Registration complete indication

User registration

subscription

User registration

notifications




Dispatch call handler

RULS

GSRGSRGSRGSR

DCH

MCC

CID

Call setup/User add/User late join

Userlookup

Group lookup/Ad hoc group updates

Call setup/User add/User late join/MCU

load information

Billing information/Lawful

intercept information




Sample Message Flow by Component


Originator joe

RLS RD RULSDFE MCCHD

Where am I?

Hello Carrier

ok [email protected]

is here

Your call is ready!

I know joe who is jack?

[email protected]

Mr. MCC Please take care of joe and jack

Hello joe I will be your operator, you have the floor

Hello jack,

I will be your operator,

joe has the floor

Hey jack, joe is calling

CALL myGroup@ourdomain

TARGET

jack

QSP/RTP QSP/RTP

ok Who is [email protected]

joe@ourdomain

joe@ourdomain = [email protected]

ok

Welcome to QChat

ACK

One Moment

Hello Carrier

Hello QChat

ok

Ok great!

Thanks!

ok

Log callok

ok ok

Sure thing!

R e g i o n a l B o u n d a r y

Registration

Direct Call



QChat Client registration flow

Client RLS CRH CID(s) CCD HAD DFE

Regional Dispatcher

NOTIFY

200 OK

GetUserDataRequest

GetUserDataReply

LOAD Reg Info

Protocol

version

OK

INFO (service available)

ACK (accept)

QChat Registration

Load Reg Info

Load Reg Response

Home Dispatcher

REGISTER

200 OK

LOAD Reg Info




Direct call setup flow

Originator:

Client ADCH CID Client BMCC RUL

CALL BLookup originator by IP

Originator InfoACK (accept)

Lookup target client

Client Info

Matching vocoder found

MCC selected

ANNOUNCE (invite)

CONTACT

STATUS (success)

Handle Call

Handle Call Resp (success)

ACK (accept)

CONTACT

CONTACT ACKCONTACT ACK

QSP/RTP QSP/RTP

ACK (accept)

Send UDE

Regional Dispatcher




All QChat application layer protocols operate over standard Internenetwork protocol stacks

The illustration shows protocol stacks for a QChat Client, the QAS, air interface infrastructure, which is the interface between the two e

QChat application protocols

IP

PPP/PDP

RLP

RF physical layer

Vocoder

RTPQSPSIP

TCP/UDPTCP/UDPTCP/UDP

QChat client

PPP/PDP

RLP

RF physical layer

Air interface and data

network

infrastructure

IP

Ethernet

(for example)

TCP/UDPTCP/UDPTCP/UDP

RTPQSPSIP

QChat servers





Network ManagementOverview



Network management configuration




OMC-QC

Menu bar

Navigation

Tree

Fault StatusTable

Display Pane:

The content of this pane is based on the node

selected in the Navigation Tree




1

Agenda

3Discussion and R

2QChat EcosystemQchat Introduction




For QELS Intro to QChat course: Alin Barrera [email protected]

QELS general Info:Ricardo Anaya [email protected]

QELS Training info:Sandra [email protected]

Reference documents:- QC01-E Introduction to QChat 4.x (Module 1,2,3)- 4.x QC02 QChatSysOverview

Questions?


mailto:[email protected]











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 respectiveowners

Thank youFollow us on:



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 Tech

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 pr

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 QP

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 respectiv

QELS – QChat Enhanced Local Support

March 7th, 2014

qels 2-intro to qchat and ecosystem

Documents