PoC WW Communication 2-5-08

PTT Roadmap Path Assessment
Background:
Motorolas server supports two types of PTT protocols. Devices based
on these two protocols will interoperate with each other in Release 6.1
which is GA today
1. MPTT Championed by operators around the world who wish to
use next gen 3G RAN performance coupled with proprietary Push to beep
enhancements to compete with iDEN operators. MPTT also brings unique
differentiating features to market such as enterprise administration.
2. OMA-1 PoC Standard which was approved 6-06. OMA is championed by
operators desiring a standard with interoperability between servers and devices
Motorola
Business Information, MOTOwi4 Wireless SP, Rev 1
Motorola General
Internal Document
Add additional legal text here if required by your local Legal Counsel. MOTOROLA and the Stylized M Logo are registered in the US Patent & Trademark Office. All other product or service names are the property of their respective owners. Motorola, Inc. 2007
What is the formula for PoC success (either OMA or MPTT)?
To date, no carrier worldwide has had great success with PTT other than Nextel
U.S. (before they were acquired by Sprint) and Nextel International.
1. An array of devices are required with PTT ergonomics such as real PTT
button and high audio speaker. Models to cover all segments (Low end
PDA, rugged, high end)
Tier 1 operators are needed to drive device manufacturers (Motorola and

others) with volume commitments. OMA is a standard and with MPTT
Motorola provides a Symbian GSM client.
Motorola
Motorola General
Internal Document

2. Pricing strategy.
For Enterprise subscribers:
Post paid recommended pricing is between $5 and $15/mo.
For Consumers:
Pre-paid recommended approach is pay per push with pricing
similar to SMS and voice to address concerns of cannibalization
* Recommended price is $0.03 per push or $1.00 a day ($ U.S.)
* While SMS exchange for a short conversation would be 2-3
messages, PTT is ~ 4-5 messages given greeting and
good byes.
Successful operators with PTT have treated PTT as a differentiated service
to land or take away large enterprise accounts from competitors.
Its about landing new $60/ARPU accounts versus $5-$10 PoC revenue
Motorola
Motorola General
Internal Document

3. A focus on the core PTT market segment with an enterprise sales channel first.
This is the foundation. Primarily mobile users who need information fast.
Consumers can be targeted next with instant, personalized Push to X applications.
Attractive Verticals for PTT:
PTT Usage by Enterprise Vertical
PTT
Users
who report working (N=1,868)
Building Trades, Health Care,
Manufacturing, Transportation &
Hospitality, 2%
Landscaping
Energy/Utilities, 1%
Media and Entertainment,
1%
Pharmaceuticals/Biotech,
1%
Real Estate, 2%
Professional/Business
Services , 4%
Transportation , 5%
Other, 23%
Financial
Svcs/Banking/Insurance, 5%
Includes
Landscaping
Retail, 6%
Building Trades , 12%
Strong PMR
Presence
IT/Telecommunications, 6%
Education, 7%
Health care, 9%
Government, 8%
Strong PMR
Presence
Manufacturing, 7%
Data Source: Telephia & Motorola

4. Performance. Nextel has ~ 1 second push to beep time. This instant
communication differentiates it from making a regular PSTN call.
Conversations are short and productive.
With 3G RANs now rolling out, PoC performance will be competitive with
iDEN. For example, 2008 will bring CDMA DOrA devices optimized for
Push to Beep time of ~ 1 sec.
5. Customer training
Operator training for customers to best use PTT for productivity. Its very
important also to train users on barge call etiquette as PTT barge calls
can be disruptive in certain situations. For example, one push to inform
the target if they are free to chat. The target can then barge call back or
push once to inform originator that now is not a good time to chat.
6. It is assumed that operators will provide for adequate network capacity,
availability and call quality/coverage.
Motorola
Motorola General
Internal Document
MPTT & OMA Roadmap Paths

Key operator decision is path after R6.1 (MPTT or OMA)
FOA Dates
2Q 07
OMA and
MPTT
July 08
Jan 08
R6.1
July 09
4Q 09
R7.2.X
R6.2
Last committed
OMA-1 release
Std MRS capacity

upgrade (software only)
NNI NAT fix
Prepaid Fixes
R9 will support MPTT.

OMA is uncommitted
pending market demand.
MPTT only
path
R7.0
Committed Releases
2010
R8.0
R9.0
PoC/PTX 4.0 Feature List

2007
4Q
JUL AUG SEP OCT NOV DEC
Planning EOL
1Q
2Q
3Q
1Q
4Q
JAN FEB MAR APR MAY JUN JUL AUG SEP OCT NOV DEC
2Q
3Q
OAM&P
Buddy and Group Size by Class of Service

Push-To-View
Pay per Push
Enterprise Enhancements
SSL on EMS and Web Server

EMS UI Updates
MTAS Provisioning XML Updates
MIB Enhancements Including
Improved MIB Documentation Including Expanded Definitions
Intrusion Detection using Tripwire
Permissive Dialing upon Registration to handle Area Code Splits
New Hardware Optional upgrade
Closed User Group using the Enterprise
1.6 GHz CPU Card

146GB Drives for RAID Array
Settable via CoS

Allows some subscribers in an Enterprise to make/receive
calls outside of Enterprise, some are limited to only within
Enterprise
KEY
Proposed Released
VOL = Volume Deployment
Planned Release
CI = Controlled Introduction
Committed Release
Note: All volume deployment dates are dependent on customer decisions and reference suitable Controlled Introduction rollout dates in their networks
Motorola Internal Document
4Q
RET
User Visible Features
2009
2008
3Q
PoC 4.0
Value
Added

2007
3Q
Planning EOL
Pre-OMA Standards
(These have been updated per OMA approved specs in R6.1)
Registration, talk burst control

1-1 Calls, Group Calls, Ad-Hoc Calls
Instant Personal Alerts
Buddy, Group List management (XDMS)
Services settings
Integrated SIP core (no IMS req)
Handset editing of groups

Buddy Add translations
Group size limit by limit of group members
MPTT Talk Burst Limit
2009
2008
4Q
PoC 5.0
Value
Added
1Q
2Q
3Q
4Q
1Q
2Q
3Q
RET
OAM&P
Push to View Billing

Cell ID in UDR
New Hardware Optional upgrade
New NMHost P4
KEY
Proposed Released
Planned Release
Committed Release
4Q
PoC/PTX 6.0-02 Feature List

2007
3Q
4Q
Currently Available
(These have been updated per OMA approved specs in R6.1)

IMS integration/ISC interface
Presence and Presence RLS
Privacy
Network-to- Network Interface NNI
Large Enterprises
Asymmetric Presence
1Q
2Q
3Q
4Q
1Q
2Q
3Q
OAM&P
New MIB Stats

XML Provisioning of Enterprises
Improved logging
Auto Provisioning
Prepaid Enhancements
PTV and Pay-Per-Push support
KEY
Proposed Released
Planned Release
Committed Release
4Q
RET
Pre-OMA Standards
2009
2008
PoC 6.0-02
Value
Added

2007
4Q
Currently Available
2009
2008
3Q
PoC 6.1
Value
Added
1Q
2Q
3Q
4Q
1Q
2Q
3Q
VOL
OMA PoC Standards Compliant
Enterprise Enhancements
Updates to meet key OMA 1 finalized PoC spec.

Integrated IMS (registration, authentication, SigComp)
OMA Pre-finalized presence
Webserver for OMA available through XDM
Enhanced passwords/security
Enhanced GUI enterprise operations
KEY
Proposed Released
Planned Release
Committed Release
4Q
PoC/PTX 6.2 Point Release

2007
3Q
2009
2008
4Q
PoC 6.2
Value
Added
1Q
2Q
3Q
4Q
CI
Uncommitted
1Q
2Q
3Q
VOL
Capacity enhancement to
standard MRS cards. Software only!
Network to Network Interface Enh.
- Addresses NATing and private addresses
configuration
KEY
Proposed Released
Planned Release
Committed Release
4Q
PoC/PTX 7.0 MPTT Feature List

2007
3Q
Committed
2009
2008
4Q
PoC 7.0
Value
Added
CI
1Q
2Q
3Q
4Q
1Q
2Q
3Q
VOL
OAM&P
MPTT Features
Push to Beep DOrA optimizations
- Binary SIP
- RTP ack vs waiting for SIP 200 OK
Enterprise Admin enhancements
Increased limits (Requires new client)
* No. of Client Contacts to 500 from 250
* Groups to 100 from 50
* Members to 50 from 25
Deactivation of client from server
Security Updates, new commercial software vs (Apache, ssl,etc)

Reason indicators for dropped calls. (Add disconnect UDR code)
AD to CS link robustness
Improved logging and alarming capabilities
NNI Enhancement
NNI implementation moves to standard IMS based approach
KEY
Proposed Released
Planned Release
Committed Release
4Q
PoC/PTX 7.2 OMA Feature List

2007
3Q
2009
2008
4Q
PoC 7.2
Value
Added
1Q
2Q
3Q
4Q
1Q
2Q
3Q
Committed
CI
OAM&P
All R7.0 MPTT Features PLUS:

OMA PoC Enabler Features
OMA IPA Billing. Post paid (UDR) and Prepaid.
Std OMA/3GPP Diameter Billing interface
OMA Mid Call Add user

Group participant info
MPTT to OMA interop

No loss of buddies/groups if migrate to OMA
OMA Automatic Answer Override (MPTT to OMA call alert)
OMA Plus
Web server support for OMA
XDM TLS/SSL support
CoS Support for OMA subscribers
256 configs (timers, prepaid, etc)
KEY
Proposed Released
Planned Release
Committed Release
4Q
VOL
PoC/PTX 8.0 Feature Candidates

Value
Added
2007
3Q
4Q
PoC 8.0
2009
2008
1Q
2Q
3Q
4Q
1Q
2Q
3Q
CI
Uncommitted
MPTT Enterprise Administrator enhancements to

simplify GUI and ease of use
PTT metrics and reports
Increase amount of pre-defined groups
supported in the PTT phone book from 100 to
250 (requires new client)
KEY
Proposed Released
Planned Release
Committed Release
4Q
VOL
PoC Release Retirement Planning

End Of Life (EOL)/M0 Planned for R4.X & R5.X
All software support will end on January 15, 2008.
Starting January 15, 2008, CNRC support would be limited to outage
recovery and available only with a special service level agreement
with Motorola account team approved by CNRC.
Outage recovery includes restoration of call processing,
system redundancy and billing.
No bug fixes or problem root cause analysis would be
available for this level of support.
End of Life (EOL)/M0 in-Planning phase

Planning EOL date in 2-Q 2008 (with anticipation of R7.0 GA in March
2008)
Feature Candidates beyond R8.0 are driven by customer demand

Market research guides us to consider integrating regarding popular
features with instant PTT for a richer experience
Leading Features Desired on Next Device by User Group
Likely upgrader Q1 2007 (N=2,158)
Total
How can we tie popularity to PTT?
Camera capabilities
48%
PT view available today in server. Device client

required. Also, in the future could add picture to
push to email
Downloadable ring
tones/screensavers
32%
A future client could support ring tones vs

the current barge call approach
Send and receive email
31%
Can use PTT to send voice messages through

email today. Target can reply with SMS
Send and receive SMS messages
30%
Can use PTT to send voice messages through

email today. Target can reply with SMS
Instant messaging
23%
A future application server could broker IM (SMS,

MSN, Google,etc users in the same group)
Location-based service
21%
A future client or location server could provide

location info to a PC based client. Also, push to
location services
Push-to-talk
20%
Available Today
Push-to-PC. Wireline / Wireless

convergence
NA
Motorola is currently investigating PTT client for

PC to extend the mobile PTT network WW.
Source: Telephia, Motorola Intelligence
Operator Roadmap Choices for PoC

Operator PoC
growth plans
Device status
(As of1st Qtr 2008)
Comment
MPTT only.
No interest in OMA due
to KPI 1 performance
and differentiation
CDMA Core Mobility is

recommended neutral 3rd party to
provide client and integrate into DOrA
devices from Mot and others
GSM - Check with Mot MD for MPTT
devices supported by region.
Symbian client available. Contact
John Dilworth for info.
MPTT devices will be available

throughout 2008 and continue into
2009 with OMA available in 2H 2008.
OMA only.
Willing to wait and bet
on OMA adoption, so
only add OMA devices
moving forward.
Check with Mot MD for OMA device

roadmap by region.
OMA server features beyond R7.5 are

dependent on marketplace success
with OMA-1 (~1M/yr WW).
Continue with MPTT

now and move to OMA
when it matures
Same as MPTT only above
Operators must request roadmaps

from non Motorola vendors as these
are not shared with Motorola.
PoC Capital Upgrades

Required By Release
Release
Not Optional
Optional
SR5.0 (EOL soon)
None
New NMHost/Web Server

(P4 version)
SR6.0 (EOL soon)
None
None
SR6.1.x
If NNI or OMA is desired,

then replace MRS 1200 with
STD MRS cards
None
SR7.0
None
None
SR7.X
None
If ROHS/WEE new hardware

required then schedule FOA
SR8.0 MPTT
None
None forecasted
Latin America Mobile Device Roadmap

Provided by Osvaldo Meneghel of Motorola
Mobile devices 1-08
1H-08
2H-08
P5
W
Genghis
P5
W510
LJ
Onyx
P5
V3
P4
W5-ACTV
O
Windows
P4
U3
Ischia MT
O ODM P4 P2K4P5 P2K5 LJ LJ
Downloadable
Application
MPTT
S SymbianW
OMA
3G
EMEA Mobile Device Roadmap
Under construction Ian Renwick
Asia Pac Mobile Device Roadmap

Under construction
West Asia - Black Jyoti
- South East Asia and China - Michelle Gattuso
Comparison of MPTT and OMA paths

MPTT Path
OMA Path
Comment
Interoperation
between MPTT
and OMA
Not an issue
Some minor differences end

users must be aware of
See next slide
Systems
integration effort
Low risk and cost due to one

end to end solution from
Motorola.
A System integration role is

required to test and certify all
OMA vendors. Customer or
services to champion.
PC Client
A proof of concept demo

w/budgetary pricing is
targeted for 1 Qtr 08 with
encrypted voice. Will
commercialize if market
interest.
3rd party solutions available.

Motorola can provide IOT
support for a nominal fee.
MPTT price is
expected to be
substantially lower
than 3rd party OMA.
Server Capacity
impact of OMA (If
fixed server
hardware)
500K users if 100% MPTT
300K users if 100% OMA
OMA de-rate ~ 40%

with same hardware
due to 3.5X signaling
IMS
MPTT does not require IMS
Motorola server supports

OMA devices without IMS as
it integrates the IMS
functions.
OMA FOA in an IMS

environment would
follow OMA market
traction.
Summary of user experiences in a Network with

both MPTT and OMA users in R6.1
OMA adds SIP URI

Presence states between MPTT and OMA are different and mapped by
the server. Also, OMA allows for variations in presence approach!
Therefore, even OMA clients may not be in sync
For group calls, participants not shown on an OMA device in R6.1, but
will be in R7.5
Call alerts are very different between MPTT and OMA.
MPTT sets up a call whereas OMA sends a text message.
Therefore,
- If MPTT user tries to alert OMA user, it will fail
- If an OMA user initiates a call alert to the MPTT user it will fail in R6.1
In R7.5, If an OMA user initiates an call alert call to the MPTT user,
the server will call alert the MPTT user (without text of course)
MPTT and OMA Addressing

What changes on the business card when moving to OMA?
MPTTUser
BusinessCard1
JoeSmith
CellandPTT:(501)2221234
OMAUser
BusinessCard2
OMAUser
BusinessCard2
JoeSmith
CellorPTT:(501)2221234
PTT:JoeSmith@carrier.com
R6.0 & R6.1

MPTT user calls MPTT user only through a MDN
JoeSmith
CellorPTT:(501)2221234
PTT:
5012221234@carrier.com
(MDN as provisioned in the
system)
MPTT user calls OMA user only through a MDN

OMA user calls OMA user with either MDN or friendly SIP URI
OMA user calls MPTT user only with a MDN
R7.5
Allow OMA to use a dial plan for MDNs
R6.1 15012221234
R7.0 5012221234
Presence Mapping
Background:
* MPTT has 7 fixed and consistent presence states
* OMA leaves quantity and definition of presence states up to the
client/handset provider. These may differ between OMA vendors!
Motorola server approach
* Presence between MPTT devices have no issues given the fixed states
* For OMA, the servers approach is to communicate the states between devices.
* Server Function:
-Receive presence state sent (PUBLISH) by a user whenever it changes.
-Send such presence state as is to user buddy list (NOTIFY)
-Ensures communication is as per OMA and SIP specs
-- Processes push and pull of presence updates, processes timers, communicates
errors, records activities in activity UDRs
-Enforces presence authorization rules ( some users to get presence while others might
be prevented from receiving)
Note: This feature is available on server R6.1 however it is not found to be widely supported by many
handsets.
* Client/Handset Function:
In addition to server functions above, client defines syntax and number
of presence states.
Presence Mapping examples OMA to OMA

OMA defines presence as a mechanism and
a process but not the syntax or number of presence states
Server
User A
OMA Client A States

Available
Unavailable
Busy
Do Not Disturb
Out to lunch
Not at My Desk
On Vacation
Away
Unknown
OMA Client B States

Available
Unavailable
Busy
Do Not Disturb
Out of Office
Be Right Back
Stepped out
Driving
Unknown
User B
Server transfers presence states transparently as per OMA specs

States will be meaningful only when they exist on both sides
Any state that is defined by one client but is not defined by the other, will be mapped to Unknown
by the client.
Operators are required to specify a common subset of states to be supported among HS
vendors
Presence Mapping examples OMA to MPTT

Legend (presence states)
Same state
Server translates state
Server
Likely OMA States

Unavailable
UNIT 1
Available
Busy
Do Not Disturb
Out to lunch
Unknown
Unit 1 will see available as
presence status for unit 2
UNIT 2
MPTT States
Off line
Available
Busy
On the phone
On data session
Out of office
Unknown
Unit 2 will see Off line as presence

status for unit 1.
Motorola Server will map Unavailable
to Off line for all OMA devices. This
is the only state server will map.
Presence Mapping examples OMA to MPTT

Legend (presence states)
Same state
Different state
(no server intervention)
Server
Likely OMA States

Unavailable
Available
Busy
Do Not Disturb
Out to lunch
Unknown
UNIT 1
Unit 1 will see Unknown as

presence status for unit 2
since Out of office is not
known to the Unit 1 client
UNIT 2
MPTT States
Off line
Available
Busy
On the phone
On data session
Unknown
Out of office
Unit 2 will see Unknown as

presence status for unit 1.
Motorola Server does not
know out to lunch therefore
it passes unknown
Group Calling Participant List

R6.1
MPTT Handset
OMA & MPTT participants shown
User drops from list if they drop from the call
R7.5
OMA Handset
R6.1 No participants shown
R7.5 Similar to MPTT
MPTT Style Alert

With R6.1
If MPTT user tries to alert OMA user, it will fail
If an OMA user initiates an AAO call to the MPTT user it will fail
In R7.5, If an OMA user initiates an AAO call to the MPTT user,
the server will call alert the MPTT user (without text of course)
Maintain the OMA MPTT floor control mechanism to preserve the MPTT alert
user experience.
Implementation approach with devices - OMA

STEP 1 Bi-lateral client IOT with Motorola server. In the past vendors have
connected remotely to our development servers using clients.
STEP 2 System Integration of actual devices and back end systems
While bi-lateral IOT greases the skids for interop between the server and the device, it is not
a substitute for system integration with the actual commercial devices. We have seen that
the OMA standards are not as mature as SMS for a plug and play approach. The operator is
recommended to play this role.
The system integration responsibilities include:
- Alignment of all Motorola and/or non Motorola mobile device handset features with the server.
All devices should function in the same fashion
- Certify that all devices interoperate with each other smoothly in their lab.
- Manage the process to add and certify devices in the end to end system
- Ensure RAN and WAN have adequate capacity to support service
- Manage ongoing certification of end to end system as new releases are brought to market
- Manage issues to closure across all ecosystem parties such as device vendors, IMS, billing,
PC clients, etc..
STEP 3 IMS is not required to launch OMA PoC. This interface is available
with R6.1 and Motorola has successfully interoperated at test fests with
major IMS vendors. 80% of IOT efforts would be between IMS and
the handset. Prioritization of IOT will consider business case.
Future Enterprise MPTT PC Client Products

Enterprise PC client
Users Enterprise back office personnel who do not
require a cell phone, but desire lower cost, secure
communications to the field.
- Adequate for small to medium businesses
(Taxis, couriers, contractors, maintenance, etc)
- Worldwide PC to PC or mobile comm. to get answers fast
- Client can leverage existing Enterprise features.
- Secure SSL tunnel approach acceptable by IT
departments
GUI Similar to cell phone for small screen footprint.
Enterprise PC Client - Concept GUI
Carrier banner
User-selected Image
Perhaps Enterprise logo
Input Box labels:

User Credentials
for Registration on
PoC Server
Sign In Control
Green: Customizable items
Enterprise PC Client - Concept GUI
Custom Input:
Enter Target MDN
Contact Name:
Phonebook
with Presence Info
Change View to
Group Phonebook
and other views
Icon Tray
Add New Entry

To Phonebook
Green: Customizable items
PTT Button
Solution approach for Soft PC Client

(Secure voice and signaling for Enterprise market)
Law Interface (LI)

Access Point
(Recommended option)
Innovation to commercialization status for PC Client

ENTERPRISE BASED PRODUCT FOCUS ON DISPATCHING
4Q 2007 MPTT based PC Client feasibility with SSL VPN concentrator.
1Q 2008 - Customer proof of concept demos
2Q 2008 - Customer funding champion identified and capture requirements
for commercial release
CONSUMER BASED PRODUCT

A consumer based product does not have a customer champion at this time.
Changes would be required vs the enterprise version such as:
- Downloadable ring tones vs barging audio
- Potential advertising links embedded in the client
- Etc..
What is the Enterprise Administration Feature?

Total Operator Subscriber
Database
Unique to MPTT only.

OMA standards do not define.
Supplier 1
Super-Admin
User 3
Admin 1
Enterprise B
Admin 2
Enterprise A
Group 1
User 2
Group 3
Enterprise C
Operators can create /

delete enterprises and
add or remove MPTT
subscribers to or from
an enterprise.
Closed
User 1
Group 2
Instead of the enterprise subscriber managing his/her own buddy and group lists
through the subscriber web portal, the enterprise administrator (employed by the
enterprise and not the operator) uses a special web server GUI to create and
manage the buddy list and group list on behalf of the subscriber. Updates are
downloaded automatically.

PoC WW Communication 2-5-08

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

PoC WW Communication 2-5-08

Hochgeladen von

Copyright:

Verfügbare Formate

PTT Roadmap Path Assessment

PTT Roadmap Path Assessment

What is the formula for PoC success (either OMA or MPTT)?

Tier 1 operators are needed to drive device manufacturers (Motorola and

PTT Roadmap Path Assessment

PTT Roadmap Path Assessment

Building Trades , 12%

Data Source: Telephia & Motorola

PTT Roadmap Path Assessment

MPTT & OMA Roadmap Paths

Std MRS capacity

R9 will support MPTT.

PoC/PTX 4.0 Feature List

JUL AUG SEP OCT NOV DEC

Buddy and Group Size by Class of Service

SSL on EMS and Web Server

New Hardware Optional upgrade

Closed User Group using the Enterprise

1.6 GHz CPU Card

Settable via CoS

VOL = Volume Deployment

User Visible Features

PoC/PTX 5.0 Feature List

Registration, talk burst control

User Visible Features

Handset editing of groups

JUL AUG SEP OCT NOV DEC

Push to View Billing

New Hardware Optional upgrade

VOL = Volume Deployment

PoC/PTX 6.0-02 Feature List

(These have been updated per OMA approved specs in R6.1)

User Visible Features

New MIB Stats

VOL = Volume Deployment

JUL AUG SEP OCT NOV DEC

PoC/PTX 6.1 Feature List

JUL AUG SEP OCT NOV DEC

OMA PoC Standards Compliant

Updates to meet key OMA 1 finalized PoC spec.

VOL = Volume Deployment

PoC/PTX 6.2 Point Release

JUL AUG SEP OCT NOV DEC

VOL = Volume Deployment

PoC/PTX 7.0 MPTT Feature List

JUL AUG SEP OCT NOV DEC

Security Updates, new commercial software vs (Apache, ssl,etc)

VOL = Volume Deployment

PoC/PTX 7.2 OMA Feature List

JUL AUG SEP OCT NOV DEC

All R7.0 MPTT Features PLUS:

OMA IPA Billing. Post paid (UDR) and Prepaid.

Std OMA/3GPP Diameter Billing interface

OMA Mid Call Add user

MPTT to OMA interop

VOL = Volume Deployment

PoC/PTX 8.0 Feature Candidates

JUL AUG SEP OCT NOV DEC

MPTT Enterprise Administrator enhancements to

VOL = Volume Deployment

PoC Release Retirement Planning

End of Life (EOL)/M0 in-Planning phase

Feature Candidates beyond R8.0 are driven by customer demand

How can we tie popularity to PTT?