cellular networking perspectives

Editor DavidCrowecnp-wirelesscom Vol 11 No 10 October 2002

PerspectivesNetworking

Cellular

Editor DaviAccounts EvelyDistribution DebbProduction Doug

In This Issu

Feedback on HeCompression

The chair of the IETGroup claims that Rthan our Septembe

TIA Organizatio

New Chair for Tad hoc Group

3GPP2 ConsiderTSG-P Merger

An All-IP network Core Network withnetwork Does this3GPP2 TSGrsquos studyshould merge

SMS Value-AddAccess Methods

Can the use of Serv(eg 800) boost the SMS-based service

3GPP TSG CN U

The latest status ofdeveloped by the 3GTSG for GSM and W

TIA TR-4543GPRadio Access NeStandards

The latest status ofprojects and standaof active 3GPP2 TS

Next Issue No

r TIA ESN

roup

on Wireless is the SNUIM

ad hoc

This nt role in ensuring

nishing ESNUIM ID source is not

PP2TIA standards Mobile Equipment

n extension of the information on the ult our

August

and

our

July 2002

issues

ers

Merger

the merger of TSG-N and TSG-P (Packet ese groups 452 and TIA TR-456) d early 3G systems

ntrated on mobility ls such as TIAR-456 focussed on rotocols (CDPD)

ay be based on a core ponsibility) that uses cols (a TSG-P

nsmit not only data naling

nsibilities is causing

e

ader p 1

F ROHC Working OHC is even better

r article claimed

nal Changesp 1

IA ESNUIM p 1

s TSG-Np 1would merge the the Packet Data mean that the ing these areas

ed Service p 2ice Access Codes acceptance of s

pdatep 4 specifications

PP Core Network -CDMA systems

P2 TSG-A twork Interface

Feedback on Header Compression

Lars-Erik JonssonIETF ROHC WG Chair

Dear Editor

The article on header compression in your September 2002 issue was an unusually good summary of the various IP header compression schemes currently available However I would like to comment on the compression ratio table (September 2002 Table 1 page 5)

ROHC differs from older schemes in one way that was not mentioned which is an important factor in compression performance Other schemes require the link layer to identify the compressed header type for each packet Normally this is done with a 2-byte identifier for example the Protocol field in HDLC (for PPP) ROHC on the other hand handles its own packet types and can also encapsulate non-ROHC packets into a distinct packet type This means that bits can also be saved at the link layer when using ROHC if the link layer does not mandate this identifier anyway This property has been exploited in the 3GPP standards where the identifier can only be omitted if ROHC is used

A fairer comparison would be to add 1 or 2 octets to the minimum compressed header size when using any scheme but ROHC

New Chair foUIM ad hoc G

Chris Carroll of Veriznew chair of the TIA Egroup has an importathat the rapidly dimimanufacturer code redepleted and that 3Gcan migrate to the 3GIdentity the MEID aGSM IMEI For more MEID and IMEI consSeptember 2001 and

3GPP2 ConsidTSG-NTSG-P

3GPP2 is considering(Network Protocols) Data) The roles of thpredecessors (TIA TR-were distinct in 2G anTSG-NTR-452 concemanagement procotoEIA-41 and TSG-PTpacket data adjunct p

Future 3G systems mnetwork (a TSG-N resIP-based packet protoresponsibility) to trabut also voice and sig

This collision of respo

e inefficiencies and

being proposed are ard merger or a nsibilities between

p 8 TIA TR-454 rds and the status

G-A projects

vember 5th 2002

TIA Organizational Changes

TIA Committee TR-32 (Personal Radio Equipment) will be absorbed into TR-41 (User Premises Telecommunications Requirements) and committees FO-2 and FO-6 (Fiber Optics) will be merged

the potential for somconfusion Solutionseither a straightforwrealignment of respothe two groups

d

Cellular Networking Perspectives (issn 1195-3233) is published monthly by Cellular Networking Perspectives Ltd 2636 Toronto Crescent NW Calgary AB T2N 3W1 Canada Phone 1-800-633-5514 (+1-403-274-4749) Fax +1-403-289-6658 Email cnpsalescnp-wirelesscom Web wwwcnp-wirelesscom Subscriptions CDN$350 in Canada (incl GST) US$350 in the USA and US$400 elsewhere Payment by cheque bank transfer American Express Diners Club MasterCard or Visa Delivery Email or 1st class mail Back Issues Single issues are $40 in the US and Canada and $45 elsewhere or in bulk at reduced rates Discounts Educational and small businesses 25 off any order Copies Each subscriber is licensed to make up to 10 copies of each issue or back issue Please call for rates to allow more copies

Crowe n Gorehamie Brandelli Scofield

SMS Value-Added Service Access Methods

Randall Snyder m-Qube Inc

Todayrsquos economic climate is difficult for wireless carriers Maintaining traditional revenue streams reducing churn and creating new markets to generate data services revenue are primary concerns Voice services and digital technology have matured and the once spectacular growth rates in subscriber numbers and wireless revenues have slowed Consequently wireless network infrastructure spending has also decreased tremendously The industry must provide compelling new data services to restart the growth of wireless revenues

Enter the world of SMS (short message services) a thriving not-so-new technology just beginning to gain a serious foothold in North America which was until recently a haven of multiple incompatible technologies More commonly known as ldquotext messagingrdquo SMS enables mobile subscribers to send short messages to each other All major North American carriers support SMS in their networks and every new mobile handset has two-way capability SMS is available for all of the digital wireless technologies (ie GSM CDMA TDMA and iDEN) and inter-carrier SMS is now supported by the all of the largest US and Canadian carriers

SMS was originally envisioned as a peer-to-peer wireless messaging service (meaning between subscribers) As the technology matured in both Asia and Europe SMS expanded well beyond this model Many very successful SMS-based services are between a subscriber and an application platform They opened a new market to third party application providers that could connect to a wireless carrierrsquos SMS infrastructure to interact with a subscriber using this basic text messaging mechanism Examples of these applications are airline schedule updates stock quotes weather reports sports scores trivia contests and advertising campaigns and promotions

The key to the value of new services is in the simplicity of accessing them Easy access implies user-friendliness which translates into more service usage Subscribers should be able to access offered services the same as most other network features seamlessly and ubiquitously and in a commonly recognized way SMS has become successful because it is easy to use and because even in North America the artificial wall of radio technology incompatibilities is finally being knocked down

Short Codes

The most common method of accessing SMS application services today is by using ldquoshort codesrdquo A short code is a special number used by a subscriber as the address to direct an SMS message to an application These codes are typically 4 to 8 digits long with each digit being any value from 0 through 9 Short codes are supposed to be deployed so that they are not confused with the standard North American Numbering Plan (NANP) used for directory (lsquophonersquo) numbers They also do not use a ldquordquo or ldquordquo prefix like some voice feature codes

The problem with short codes is that they are not standardized Because of this they may not work when a subscriber is roaming An effort is being made by the SMS Forum and the CTIA to standardize these codes but progress is slow and the market may not wait Specific issues with short codes are

bull Their length is not standard which can cause subscriber confusion

bull Their format is not standard which can cause confusion with 7-digit local directory numbers

bull Subscribers are not accustomed to using them

bull Identical short codes may be used in different networks for different services

bull To standardize short codes each would need to be provisioned at each short message service center (SMSC) and mapped to the address of the application

Carriers are reluctant to standardize these short codes since it would mean changing codes that are currently in use Also the format of short codes is sometimes limited to what the carrierrsquos SMSC vendor allows This is the same issue with feature codes such as dialing XX (eg 73) to access calling features such as call waiting and call forwarding Even though there have been sporadic efforts since the 1980rsquos these feature codes have never been formally standardized because standard-ization could disrupt codes that subscribers are already used to

Service Access Codes

Another method for accessing SMS value-added applications is with the use of ldquoalready standardizedrdquo service access codes (SACs) SACs are special codes of the format N-0-0 that are part of the standard NANP The NANP supports numbers of the format N00-NXX-XXXX which can be used for calls requiring special call treatment such as ldquo800-rdquo toll-free numbers SACs can also be the terminating address for SMS messages

Cellular Networking Perspectives

As in standard dialable voice calls SACs require special treatment when used as message addresses The use of SACs for SMS addressing enables SMS applications to be accessed by any mobile subscriber since the address format is standardized and supported by the wireless networks and SMS The accessible applications could be either within existing wireless carrier networks or can be provided independent of these wireless network by application service providers (ASPs)

As a purely functional solution use of SAC-based addresses enables a great deal of freedom for the deployment of value-added SMS-based applications These applications can be ubiquitous and seamless as they are dependent only on Internet connectivity which is essentially ubiquitous today SAC-based addresses are especially appropriate for value-added wireless messaging services for the following reasons

bull The numbers can be used anywhere in the North American Numbering Plan Area (NANPA ndash the US Canada and most Caribbean islands) and by any mobile subscriber to access value-added services That is because numbers begin-ning with N00 have no relationship with a geographic area All mobile-originated SMS messages require the subscriber to provide an NANP formatted address to send the message To send a message to value-added messaging applications the SAC-based NANP address requires a translation to an address that is universally recognized (eg an IP address) All SMSC platforms today support IP connectivity including address and protocol translation

bull SAC-based messaging addresses enable application service providers (ASPs) to quickly provide a nation-wide footprint for value-added messaging services SACs are supported by all tele-communications carriers in the NANPA ASPs can provide nation-wide coverage of services so that subscribers from any network can access these services anywhere

bull The use of standard NANP numbers is culturally accepted by mobile subscribers in the US and Canada It is therefore logical to use these numbers as SMS addresses for value-added network applications

bull The use of SAC-based SMS addresses can rapidly increase and expedite the growth of SMS traffic in the US and Canada Value-added services enable mobile subscribers to originate SMS messages that are received processed and responded to by an application entity These value-added services are in great demand As such they will serve the dual-purpose of educating the mass market on the ease of use of SMS and increase mass market acceptance of SMS technology

- 2 - October 2002

The use of SAC-based addresses for SMS value-added services does not preclude the use of these numbers for voice calls This enables applications to be message-based call-based or a hybrid of both with no functional changes to existing wireless networks

International Caveat

The use of SAC codes however may not be appropriate for carriers outside North America or for international roaming This is because the NANP numbering format is not used there The solution in this case would be the standardization of short codes (ie their format length and use)

typically a long and tedious standards process and one that is not guaranteed to succeed

Example of SAC SMS Routing

Figure 1 shows an example of SAC-based routing for short message service

1 The subscriber initiates a mobile-originated SMS message addressed using a SAC code of the format N00-NXX-XXXX

2 The mobile-originated SMS message is forwarded to the serving MSCVLR by the Base Station

3 The serving MSCVLR queries the HLR to validate the SMS feature

4 The SMS message is forwarded to the Short Message Service Center (SMSC) for routing to the message destination

5 The SMSC or SME gateway maintains routing tables to map the routing address (ie N00-NXX-XXXX) to the IP address of the application that should receive the message The SMS message is encapsulated within lower layers of

the protocol and routed as a layer 3 IP packet

6 The message is routed through the public Internet or a private intranet based on the translated IP address

7 The application receives the short message and executes the specified service

About the Author

Randall A Snyder is Vice President for Carrier Marketing at m-Qube a Boston-based company specializing in SMS-based mobile marketing solutions He is also the co-author of the book Wireless Telecommunications Networking with ANSI-41

Our New Look

We are changing our look slightly by employing fonts from the Canadian designer Nick Shinn Our headings are now in Brown Gothic and our body text is in Worldwide As always we would appreciate your feedback on these changes

Figure 1 Example of Routing for a SAC-based SMS Service

Value Added Apps

Value Added Apps

Wireless Network

BaseStation

Internet orIntranet

Value Added Apps

ServingMSCVLR

HLR

Example SMS Routing Table

SMS Address Prefix

IP Address

500-200 234555789000

500-201

hellip500-209

234555789000

600-200 222456654000

700-300 333435221000

800-200 445122334000

900-300 522236999000

N00-NXX-XXXX

CDMA TDMA or GSM

SME Gateway

SMSC

Cellular Networking Perspectives - 3 - October 2002

3GPP TSG CN Update

3GPP TSG Core Network (TSG CN) is responsible for the specifications of the internal signaling network of 3GPP systems as they evolve from GSM This includes

bull User Equipment ndash Core network layer 3 radio protocols (Call Control Session Management Mobility Management)

bull Signalling between the core network nodes

bull Interconnection with external networks

bull Core network aspects of the Iu interface

bull OampM requirements

bull Packet related matters such as mapping of QoS

TSG CN has completed majority of its work for Release 5 (Rel-5) IP Multimedia Subsystem the first AllndashIP version of 3GPP standards More time was allowed for completion of Release 5 versions of the following specifications

Specification Reason for Delay in Completion of Release 5 Version

TS 24228 ndash Signalling Flows for the IP multimedia call control based on SIP and SDP

bull ToFrom header encodingbull IETF Draft referencingbull Security Association related parameter inclusion in SIP messages bull Missing clause for error handling session initiationbull XML body vs P-headersbull Rework of Path header compliant with draft willis and ServRoutebull Privacy updatesbull Security Association setup proceduresbull R99 USIM compatibility checkbull Need to apply drafting rules

TS 24229 ndash IP Multimedia Call Control Protocol based on SIP and SDP Stage 3

bull ToFrom header encodingbull IETF Draft referencingbull Security Association related parameter inclusion in SIP bull SigComp failure handlingbull Local emergency calls for roaming subscribersbull Clause 224 Status codes tablebull Annex A2 SDP typesbull Clause amp2 SIP headers defined in 3GPPbull 763 IMS XML bodybull SndashCSCF not available error cases at IndashCSCFbull R99 USIM public identity barring in the SndashCSCFbull Remote party ID insertion into initial requestbull Public identity validation at the PndashCSCFbull Multiple media types per PDP contextbull Security Association setup proceduresbull 3GPP specific warn codesbull R99 USIM compatibility checkbull Need to apply drafting rules

TS 29207 ndash Policy control over Go interface bull The sections for DiffServ edge function are still empty since the requirement for DiffServ interworking has been given lower priority by SA2

bull The wildcarding of source IP address bull The handling of IMS charging ID bull The handling of an error case caused by discrepancy between authorized QoS

information and TFT parametersbull Mapping authorized data rate into UMTS QoS bit rate parameterbull Initialization and maintenance of GGSN and PCFbull A solution for possible theft of servicebull The location of UE specific descriptions (annex A)bull The limitation table of Go PIB has to be updated (annex B)

TS 29208ndash End-to-end QoS Signalling flows bull Resource reservation flows with end-to-end RSVP interactions are missing

TS 29229ndash Cx and Dx Interfaces based on the Diameter protocol Protocol details

bull Definition of a mechanism for the negotiation of protocol versionsbull Diameter base draft is incomplete

TS 29328ndash IP Multimedia (IM) Subsystem Sh Inter-face Signalling flows and message contents

bull Exact nature of the subscriber state information element is for further studybull Multiplicity of service indication needs examinationbull Definition of the format of location information is required in annex C1

TS 29329ndash Sh Interface based on the Diameter protocol Protocol details

bull Commands for the Sh may be allocated to start at 100 (to differ from Cx)bull Diameter base draft is incomplete


TSG CN WG1 (Mobility Management Call Control Session Management SMS)

TSG CN Working Group 1 (CN1) defines the User Equipment ndash Core network Layer 3 radio protocols (Call Control Session Management Mobility Management SMS) CN WG1 addresses specifically SIP Call Control and SDP protocols for the IM subsystem

As of June 2002 IMS specifications TS 24228 and 24229 were proposed to be closed to new features while still allowing agreed and documented open items to be covered by CRs

Very little time has been spent by CN1 on Rel-6 items so far mainly due to lack of time at CN1 meetings due to the focus on Rel-5

The status of CN1 specifications is shown below

Document Title Status

tbd Support of the Multimedia Broadcast Multicast Service (MBMS) in CN Protocols bull New work item

TS 23009 Handover procedures bull R99 Rel 4 and Rel-5 being revised

TS 23122 NAS Functions related to Mobile Station (MS) in idle mode bull Rel-5 being published

TS 23218 IP Multimedia (IM) Session Handling IP Multimedia (IM) call model Stage 2 bull Rel-5 being revised

TS 24007 Mobile radio interface signalling Layer 3 General aspects bull R99 and Rel-4 being revised

TS 24008 Mobile radio interface Layer 3 specification Core network protocols Stage 3 bull R99 Rel-4 and Rel-5 being revised

TS 24228 Signalling flows for the IP multimedia call control based on SIP and SDP Stage 3bull Rel-5 being revised

TS 24229 IP Multimedia Call Control Protocol based on SIP and SDP Stage 3

TS 29016 Serving GPRS Support Node (SGSN) ndash VLR Gs interface network service bull Rel-4 being revised

TS 29018 Serving GPRS Support Node (SGSN) ndash VLR Gs interface layer 3 bull R99 Rel-4 and Rel-5 being revised

TS 29994 Recommended infrastructure measures to overcome specific Mobile Station (MS) faults

bull R99 and Rel-4 being revisedbull Rel-5 being published

TS 44001 Mobile Station ndash Base Station System (MS ndash BSS) interface General aspects and principles

bull Rel-4 being revisedTS 44013 Performance requirements on the mobile radio interface

TS 44068 Group Call Control (GCC) protocol

TS 44069 Broadcast Call Control (BCC) protocol

TSG CN WG2 (CAMEL ndash Customized Applications for Mobile Network Enhanced Logic)

TSG CN WG2 is responsible for stage 2 and 3 specifications of CAMEL (Customized Applications for Mobile network Enhanced Logic) which provides mechanisms to support services independently of the serving network It is intended to facilitate control of operator specific services outside of the serving PLMN and it is hoped that it

will help operators provide subscribers with their specific services even when roaming outside the HPLMN

During the June 2002 meeting the main focus of CN2 was the completion of Release 5 CAMEL4 It also worked on R99 CAMEL3 CRs mainly small corrections and clarifications GPRS packet data prepaid is

still the area of most contributions for CAMEL3



tbd Support of CAMEL by the IMS bull New work item

TS 23078 CAMEL Phase 4 ndash Stage 2 bull R99 and Rel-4 versions being revised

bull Rel-5 version being publishedTS 29078 CAMEL Application Part (CAP) specification


TSG CN WG3 (Interworking with External Networks)

TSG CN Working Group 3 (CN3) specifies the bearer capabilities for circuit and packet switched data services and necessary interworking functions towards both the user equipment in the UMTS

PLMN and the terminal equipment in the external network In addition CN3 is responsible for end-to-end QoS for the UMTS core network in Release 5 and

beyond The status of its specifications is shown below


tbd Revised work item description (WID) on interworking between IMS and CS bull Revised WID update WID descriptiontbd Revised WID for Service Change and UDI Fallback

TS 23172 Technical Realization of Circuit Switched (CS) Multimedia Service UDIRDI Fallback and Service Modification

bull Rel-5 version being published

TS 27001 General on Terminal Adaptation Functions (TAF) for Mobile Stations (MS) bull Rel-5 version being revised

TS 27060 Packet Domain Mobile Station (MS) supporting Packet Switched Services bull R99 Rel-4 and Rel-5 versions being revised

TS 29007 General requirements on interworking between the PLMN and the Integrated Services Digital Network (ISDN) or PSTN

bull R99 Rel-4 and Rel-5 versions being revised

TS 29061 Packet Domain Interworking between the Public Land Mobile Network (PLMN) supporting Packet Based Services and Packet Data Networks (PDN)


TS 29207 Policy control over Go Interfacebull Rel-5 version being published

TS 29208 End to end QoS Signalling flows

TSG CN WG4 (MAPGTPBCHSS)

TSG CN Working Group 4 (CN4) standardizes stage 2 aspects within the Core Network focusing on

bull Supplementary Services

bull Basic Call Processing

bull Mobility Management

bull Bearer Independent Architecture

bull The mobile-specific protocol specifica-tions within the mobile core network



tbd Interworking of CS user plane between 3GPP and external PLMNPSTNISDN bull New Work Item

TS 23003 Numbering addressing and identification bull R99 Rel-4 and Rel-5 versions being revised

TS 23007 Restoration procedures bull R99 and Rel-4 versions being revised

TS 23008 Organization of subscriber data bull R99 Rel-4 and Rel-5 versions being revised

TS 23016 Subscriber data management Stage 2 bull Rel-4 and Rel-5 versions being revised

TS 23079 Support of Optimal Routeing (SOR) Technical realization bull R99 Rel-4 and Rel-5 versions being revised

TS 23082 Call Forwarding (CF) supplementary services Stage 2 bull R99 and Rel-4 versions being revised

TS 23153 Out of Band Transcoder Control Stage 2 bull Rel-5 being revised

TS 23205 Bearer independent circuitndashswitched core network Stage 2 bull Rel-4 and Rel-5 versions being revised

TS 24030 Location Services (LCS) Supplementary service operations Stage 3 bull Rel-5 being revised

TS 24080 Mobile radio interface layer 3 supplementary services specification Formats and coding



TSG CN WG5 (OSA ndash Open Service Architecture)

TSG CN Working Group 5 (CN5) is responsible for stage 3 specifications of interfaces for the UMTS Open Service Access (OSA) CN5 develops Application Programming Interfaces (APIs) for the OSA

the UMTS network provides these inter-faces to facilitate service implementations The work of CN5 is based on Service Requirements set by TSG SA WG1 and the Architecture defined by TSG SA WG2

CN5rsquos biggest accomplishment in June 2002 was the completion of OSA Rel-5 specifications The status of CN5 specifications is shown below

TSG CN Meeting Schedules

The last plenary meeting of TSG CN was held from June 5 ndash 7 2002 on Marco Island Florida The next plenaries will be held in September 2002 in Biarritz France and December 2002 in New Orleans USA

TS 29002 Mobile Application Part (MAP) specification bull R99 Rel-4 and Rel-5 versions being revised

TS 29010 Information element mapping between MSBSS BSSMSC Signalling procedures and the Mobile Application Part (MAP)

bull R99 and Rel-4 versions being revised

TS 29060 General Packet Radio Service (GPRS) GPRS Tunnelling Protocol (GTP) across the Gn and Gp Interface


TS 29228 IP Multimedia (IM) Subsystem Cx and Dx interfaces Signalling flows and message contents bull Rel-5 version being published

TS 29229 Cx and Dx Interface based on the Diameter protocol Protocol Details

TS 29232 Media Gateway Controller (MGC) ndash Media Gateway (MGW) Interface Stage 3 bull Rel-4 and Rel-5 versions being revised

TS 29328 IP Multimedia (IM) Subsystem Sh interface Signalling flows and message content bull Rel-5 version being published

TS 29329 Sh Interface based on the Diameter protocol Protocol Details



TS 29198-01 API Part 1 Overviewbull Rel-5 version being published

TS 29198-02 API Part 2 Common data

TS 29198-03 API Part 3 Framework bull Rel-4 being revised


TS 29198-04 API Part 4 Call Control


TS 29198-05 API Part 5 Generic User Interaction

TS 29198-06 API Part 6 Mobility

TS 29198-07 API Part 7 Terminal Capabilities

TS 29198-08 API Part 8 Data Session Control

TS 29198-11 API Part 11 Account Management

TS 29198-12 API Part 12 Charging

TS 29198-13 API Part 13 Policy Management SCF

TS 29198-14 API Part 14 Presence and Availability Management (PAM)

TR 29998-04-4 Mapping for OSA Part 4 Call Control Service Mapping Subpart 4 Multiparty Call Control ISC

bull Rel-4 being revised



TIA TR-4543GPP2 TSG-A

Radio Access Network

Interface StandardsEditor DavidCrowecnp-wirelesscom

Note 1 IS- Interim Standard TSB- Telecommunications Systems Bulletin PN- Project Number SP- ANSI Standards ProposalAPxxxx - TSG-A project ARxxxx - TSG-A report ASxxxx - TSG-A specification Due to space considerations projects of the formatPN-3-xxxx are shown without the ldquo-3rdquo (which means lsquoTIArsquo)

2 Bold Type indicates a modification since the previous publication of this information3 Published TIA standards can be obtained from TIA at wwwtiaonlineorgstandardssearch_n_ordercfm

Thanks to David Ott and Lisa Collichio (Qualcomm) for their assistance compiling the information in this table

CellularNetworking

Perspectives

Description

TR-454 Projects and StandardsStandard StatusProject

SP-4277 Published 0499TIAEIA-634-B ANSI version of IS-634-ASP-4377 Project cancelledTIAEIA-634-C Revision of BS-MSC A interfacePN-3473-RV1 DevelopmentTIAEIA-658-A Data services interworking function for cdma2000 (L-interface)SP-4604 Published 1201TIAEIA-828 Abis interface specification for CDMA2000PN-4683 Published 0801TIAEIA-829 Tandem free operation (eliminates intermediate vocoders in

mobile-to-mobile calls with compatible vocoders)SP-0030 Published 0502TIAEIA-895 CDMA tandem free operation (elimination of voice coders in

mobile-to-mobile calls)SP-0030-RV1 In pressTIAEIA-895-A CDMA tandem free operation (elimination of voice coders in

mobile-to-mobile calls)Published 1295IS-634-0 MSC-BS A Interface Standard

PN-3539 Published 1098IS-634-A MSC-BS Interface including support for IS-95-A EIATIA-553-A IS-41-CSMS data and frame relay

PN-4374 Published 0796IS-658 Data Services Interworking Function Interface (egmodempool)This version developed by TR-455

PN-4545 Published 1200IS-2001 cdma2000 Access Network Interface (A Interface) based on 3GPP2TSG-A IOS V41

PN-4545-AD1 Published 0501IS-2001-1 Addendum 1 for IS-2001PN-4545-RV1 Published 0801IS-2001-A cdma2000 Access Network Interface based on IOS v42PN-0009 In pressTIA-878 1xEVDO (HRPD) interoperability specification (IOS) for cdma2000 ldquoArdquo

interfacePN-0009-AD1 Ballot 1002TIA-878-1 Addendum to TIA-878 (1 page erratum)PN-0009-RV1 DevelopmentTIA-878-A HRPD IOS Phase 2 moving session control and mobility

management from AN to PCFSP-4545-RV2 Published 0502TIA-2001-B cdma2000 Access Network Interface based on IOS v42SP-4545-RV3 DevelopmentTIA-2001-C cdma2000 Access Network Interface based on IOS v43

Published 1196TSB80 IS-634-0 Addendum (corrections SMS subrate voice frame format)Published 0694TSB104 PCS Service Description (now IS-104 in committee TR-46)


Description

Active 3GPP2 TSG-A ProjectsStandard Status

Study of IP-based RAN architecture for CDMA2000 DevelopmentAR0006CDMA access network ldquoArdquo interface to support IS-2000 (IOS v40) See IS-2001AS0001CDMA access network ldquoArdquo interface to support IS-2000-A (IOS v41) See IS-2001-AAS0001-ABTS-BSC interoperability (Abis interface) (see IS-828) Published 0300AS0003BTS-BSC (Abis) interface for cdma2000 systems (see IS-828-A) Published 0701AS0003-ACDMATDMA Tandem free operation (eliminates intermediate vocoders) - SeeTIAEIA-829

Published 1299AS0004

Addendum to CDMA tandem free operations Published 0101AS0004-01Revision A of tandem free operations for CDMA (TIAEIA-895) Published 0701AS0004-ARevision B of tandem free operations Published 0802AS0004-B1xEV-DO interoperability specification (IOS) for cdma2000 ldquoArdquo interface (see IS-878) Published 0701AS0007-0HRPD IOS Phase 2 Published 0902AS0007-AInteroperability specification to support TIA-2000-B (IOS v42)Part 1 - Overview

See TIA-2001-BAS0011

Interoperability specification (7 parts) (IOS v43) See TIA-2001-CAS0011~17-APart 2 - TransportAS0012Part 3 - FeaturesAS0013Part 4 - A1 A2 A5 interfacesAS0014Part 5 - A3 A7 interfacesAS0015Part 6 - A8 A9 interfacesAS0016Part 7 - A10 A11 interfacesAS0017


SMS Value-Added Service Access Methods

Randall Snyder m-Qube Inc

Todayrsquos economic climate is difficult for wireless carriers Maintaining traditional revenue streams reducing churn and creating new markets to generate data services revenue are primary concerns Voice services and digital technology have matured and the once spectacular growth rates in subscriber numbers and wireless revenues have slowed Consequently wireless network infrastructure spending has also decreased tremendously The industry must provide compelling new data services to restart the growth of wireless revenues

Enter the world of SMS (short message services) a thriving not-so-new technology just beginning to gain a serious foothold in North America which was until recently a haven of multiple incompatible technologies More commonly known as ldquotext messagingrdquo SMS enables mobile subscribers to send short messages to each other All major North American carriers support SMS in their networks and every new mobile handset has two-way capability SMS is available for all of the digital wireless technologies (ie GSM CDMA TDMA and iDEN) and inter-carrier SMS is now supported by the all of the largest US and Canadian carriers

SMS was originally envisioned as a peer-to-peer wireless messaging service (meaning between subscribers) As the technology matured in both Asia and Europe SMS expanded well beyond this model Many very successful SMS-based services are between a subscriber and an application platform They opened a new market to third party application providers that could connect to a wireless carrierrsquos SMS infrastructure to interact with a subscriber using this basic text messaging mechanism Examples of these applications are airline schedule updates stock quotes weather reports sports scores trivia contests and advertising campaigns and promotions

The key to the value of new services is in the simplicity of accessing them Easy access implies user-friendliness which translates into more service usage Subscribers should be able to access offered services the same as most other network features seamlessly and ubiquitously and in a commonly recognized way SMS has become successful because it is easy to use and because even in North America the artificial wall of radio technology incompatibilities is finally being knocked down

Short Codes

The most common method of accessing SMS application services today is by using ldquoshort codesrdquo A short code is a special number used by a subscriber as the address to direct an SMS message to an application These codes are typically 4 to 8 digits long with each digit being any value from 0 through 9 Short codes are supposed to be deployed so that they are not confused with the standard North American Numbering Plan (NANP) used for directory (lsquophonersquo) numbers They also do not use a ldquordquo or ldquordquo prefix like some voice feature codes

The problem with short codes is that they are not standardized Because of this they may not work when a subscriber is roaming An effort is being made by the SMS Forum and the CTIA to standardize these codes but progress is slow and the market may not wait Specific issues with short codes are

bull Their length is not standard which can cause subscriber confusion

bull Their format is not standard which can cause confusion with 7-digit local directory numbers

bull Subscribers are not accustomed to using them

bull Identical short codes may be used in different networks for different services

bull To standardize short codes each would need to be provisioned at each short message service center (SMSC) and mapped to the address of the application

Carriers are reluctant to standardize these short codes since it would mean changing codes that are currently in use Also the format of short codes is sometimes limited to what the carrierrsquos SMSC vendor allows This is the same issue with feature codes such as dialing XX (eg 73) to access calling features such as call waiting and call forwarding Even though there have been sporadic efforts since the 1980rsquos these feature codes have never been formally standardized because standard-ization could disrupt codes that subscribers are already used to

Service Access Codes

Another method for accessing SMS value-added applications is with the use of ldquoalready standardizedrdquo service access codes (SACs) SACs are special codes of the format N-0-0 that are part of the standard NANP The NANP supports numbers of the format N00-NXX-XXXX which can be used for calls requiring special call treatment such as ldquo800-rdquo toll-free numbers SACs can also be the terminating address for SMS messages

Cellular Networking Perspectives

As in standard dialable voice calls SACs require special treatment when used as message addresses The use of SACs for SMS addressing enables SMS applications to be accessed by any mobile subscriber since the address format is standardized and supported by the wireless networks and SMS The accessible applications could be either within existing wireless carrier networks or can be provided independent of these wireless network by application service providers (ASPs)

As a purely functional solution use of SAC-based addresses enables a great deal of freedom for the deployment of value-added SMS-based applications These applications can be ubiquitous and seamless as they are dependent only on Internet connectivity which is essentially ubiquitous today SAC-based addresses are especially appropriate for value-added wireless messaging services for the following reasons

bull The numbers can be used anywhere in the North American Numbering Plan Area (NANPA ndash the US Canada and most Caribbean islands) and by any mobile subscriber to access value-added services That is because numbers begin-ning with N00 have no relationship with a geographic area All mobile-originated SMS messages require the subscriber to provide an NANP formatted address to send the message To send a message to value-added messaging applications the SAC-based NANP address requires a translation to an address that is universally recognized (eg an IP address) All SMSC platforms today support IP connectivity including address and protocol translation

bull SAC-based messaging addresses enable application service providers (ASPs) to quickly provide a nation-wide footprint for value-added messaging services SACs are supported by all tele-communications carriers in the NANPA ASPs can provide nation-wide coverage of services so that subscribers from any network can access these services anywhere

bull The use of standard NANP numbers is culturally accepted by mobile subscribers in the US and Canada It is therefore logical to use these numbers as SMS addresses for value-added network applications

bull The use of SAC-based SMS addresses can rapidly increase and expedite the growth of SMS traffic in the US and Canada Value-added services enable mobile subscribers to originate SMS messages that are received processed and responded to by an application entity These value-added services are in great demand As such they will serve the dual-purpose of educating the mass market on the ease of use of SMS and increase mass market acceptance of SMS technology

- 2 - October 2002















About the Author


Our New Look



Value Added Apps

Value Added Apps

Wireless Network

BaseStation

Internet orIntranet

Value Added Apps

ServingMSCVLR

HLR


SMS Address Prefix

IP Address

500-200 234555789000

500-201

hellip500-209

234555789000

600-200 222456654000

700-300 333435221000

800-200 445122334000

900-300 522236999000

N00-NXX-XXXX

CDMA TDMA or GSM

SME Gateway

SMSC


3GPP TSG CN Update










































































































































CellularNetworking

Perspectives

Description














Description






















About the Author


Our New Look



Value Added Apps

Value Added Apps

Wireless Network

BaseStation

Internet orIntranet

Value Added Apps

ServingMSCVLR

HLR


SMS Address Prefix

IP Address

500-200 234555789000

500-201

hellip500-209

234555789000

600-200 222456654000

700-300 333435221000

800-200 445122334000

900-300 522236999000

N00-NXX-XXXX

CDMA TDMA or GSM

SME Gateway

SMSC


3GPP TSG CN Update










































































































































CellularNetworking

Perspectives

Description














Description








3GPP TSG CN Update










































































































































CellularNetworking

Perspectives

Description














Description

























































































































CellularNetworking

Perspectives

Description














Description








Description








cellular networking perspectives

Documents