for location and SMS, as well as many other functions with which developers will be able<strong>to</strong> build innovative applications.Table 3 summarizes the available Parlay X specifications. 29 Opera<strong>to</strong>rs are beginning <strong>to</strong>selectively deploy these functions. The advantage of this approach is that developers canbuild applications that are compatible with multiple opera<strong>to</strong>r networks.Table 3: Parlay X SpecificationsPart Title Functions1 Common Definitions common across Parlay X specifications2 Third Party Call Creates and manages calls3 Call Notification Management of calls initiated by a subscriber4 Short Messaging Send and receive of SMS including delivery receipts5 Multimedia Messaging Send and receive of multimedia messages6 Payment Pre-paid and post-paid payments and paymentreservations7 Account Management Management of accounts of prepaid cus<strong>to</strong>mers8 Terminal Status Obtain status such as reachable, unreachable or busy9 Terminal Location Obtain location of terminal10 Call Handling Control by application for call handling of specificnumbers11 Audio Call Control for media <strong>to</strong> be added/dropped during call12 Multimedia Conference Create multimedia conferences including dynamicmanagement of participants13 Address List Manage subscriber groupsManagement14 Presence Provide presence information15 Message Broadcast Send messages <strong>to</strong> all users in specified area16 Geocoding Obtain location address of subscriber17 Application-driven QoS Control quality of service of end-user connection18 Devices Capabilities Obtain device capability information and be able <strong>to</strong>and Configuration push device configuration <strong>to</strong> device19 Multimedia Streaming Control multimedia streaming <strong>to</strong> deviceControl20 Multimedia MulticastSession ManagementControl multicast sessions, members, multimediastream, and obtain channel presence informationA related project is GSM Association (GSMA) OneAPI, a project <strong>to</strong> also define networkinterfaces, but that prioritizes implementation based on expected market demand.OneAPI defines a simplified Web service for most functions that is essentially a subset ofthe related Parlay X Web service. 30 It also defines a REST (Representational StateTransfer) interface for most functions as an alternative <strong>to</strong> using the Web service. RESTfulinterfaces are simpler for developers <strong>to</strong> work with and experiment with than Webservices.Regardless of whether opera<strong>to</strong>rs deploy with Parlay X or OneAPI, these are mainstreaminterfaces that will open wireless networks <strong>to</strong> thousands of Internet programmers who29 See http://www.parlay.org/en/specifications/pxws.asp for actual specifications.30 See http://oneapi.aepona.com/portal/tws_gsma/Resources for more information about OneAPI.Transition <strong>to</strong> <strong>4G</strong>: <strong>3GPP</strong> <strong>Broadband</strong> <strong>Evolution</strong> <strong>to</strong> <strong>IMT</strong>-<strong>Advanced</strong>, Rysavy Research/3G <strong>Americas</strong>, Aug 2010 Page 26
will be able <strong>to</strong> build applications that leverage the latent information and capabilities ofwireless networks.Mobile Application ArchitecturesMany applications used over wireless connections will be the same as those used over theInternet with desk<strong>to</strong>p/lap<strong>to</strong>p PCs. An increasing number of applications, however, will bedeveloped specifically for mobile devices. This can be a challenge for developers, becausethere are a number of different mobile platforms now available including Android, AppleiPhone, LiMo, Palm Pre, RIM BlackBerry, Symbian, and Windows Mobile. Unlike thedesk<strong>to</strong>p market, the mobile device market has become fragmented. Each of the deviceplatforms comes with its own application development environment, and developers mustface a learning curve <strong>to</strong> become adept at programming for any specific platform. Somedevelopers may be content targeting specific platforms. Others, however, may need theirapplications <strong>to</strong> operate across multiple platforms.Fortunately, there are various developments that address the fragmentation challenge.These include:Mobile Middleware. These are software infrastructures that consist of a clientcomponent that operates on the mobile device, and a server component that actsas a proxy for the client. Vendors provide <strong>to</strong>ols with which developers can developan application in a platform-neutral manner, and which then operates on multipledevice types. Mobile middleware is mostly used for business applications.Mobile Web 2.0. Mobile browsers are adopting many of the same sophisticatedcapabilities as desk<strong>to</strong>p browsers. Combined with networks that have higherthroughputs and lower latency, an increasing number of applications can be Webhosted, making the applications available from diverse platforms. Mobile Web 2.0technologies include items such as Ajax, offline operation, video capabilities, fastJavaScript execution, and mashups (combining data from multiple Web sources).Cloud computing, enabled by Mobile Web 2.0, will play as important a role formobile systems as for desk<strong>to</strong>ps.Push Architectures. Many mobile applications are notification oriented, meaningusers want <strong>to</strong> know when new information is available in applications like e-mailor social networking. “Pushing” small amounts of data on a regular basis <strong>to</strong> largenumbers of users, or having devices poll on a regular basis, can strain impactnetwork capacity. In response, <strong>3GPP</strong> has specified supporting mechanisms such asPaging Channel (PCH) states and <strong>to</strong>ols for enabling rapid transitions betweenactive and inactive states.Eventual Market Consolidation. Though the market is currently fragmented, thereare certain platforms (e.g., Android, BlackBerry, iPhone) that represent relativelydominant market share. Increasingly, developers are choosing <strong>to</strong> develop for justa small number of these platforms using the development <strong>to</strong>ols specific <strong>to</strong> thatenvironment.<strong>Broadband</strong>-Wireless Deployment ConsiderationsMuch of the debate in the wireless industry is on the merits of different radiotechnologies, yet other fac<strong>to</strong>rs are equally important in determining the services andcapabilities of a wireless network. These fac<strong>to</strong>rs include the amount of spectrumavailable, backhaul, and network <strong>to</strong>pology.Transition <strong>to</strong> <strong>4G</strong>: <strong>3GPP</strong> <strong>Broadband</strong> <strong>Evolution</strong> <strong>to</strong> <strong>IMT</strong>-<strong>Advanced</strong>, Rysavy Research/3G <strong>Americas</strong>, Aug 2010 Page 27
- Page 11 and 12: Quality of service (QoS). By priori
- Page 13: Figure 4: WCDMA-HSPA Voice and Data
- Page 16 and 17: It is clear that both EDGE and UMTS
- Page 18: TechnologyNameType Characteristics
- Page 21 and 22: Europe are providing operators with
- Page 23 and 24: MHz, in Japan at 1500 MHz and in Eu
- Page 25: and VoIP operation. These approache
- Page 29 and 30: Leveraging this success, operators
- Page 31 and 32: VoIP for HSPA. Since LTE uses an IP
- Page 33 and 34: Figure 10: Different Deployment Sce
- Page 35 and 36: Figure 11: Radio Resource Managemen
- Page 37 and 38: IEEE 802.16e-2005 and now IEEE 802.
- Page 39 and 40: attempts, no terrestrial wireless-d
- Page 41 and 42: DownlinkPeakNetworkSpeedPeakand/orT
- Page 43 and 44: DownlinkUplinkPeakNetworkSpeedPeaka
- Page 45 and 46: Figure 13: HSDPA Performance of a 7
- Page 47 and 48: Figure 15: HSPA+ Performance Measur
- Page 49 and 50: Figure 17: LTE Throughput in Variou
- Page 51 and 52: Figure 19: Latency of Different Tec
- Page 53 and 54: Figure 20: Performance Relative to
- Page 55 and 56: Figure 21: Comparison of Downlink S
- Page 57 and 58: Incremental redundancy in error cor
- Page 59 and 60: Figure 23: Comparison of Voice Spec
- Page 61 and 62: Figure 24: Relative Volume of Subsc
- Page 63 and 64: Technology EDGE/HSPA/LTE CDMA2000 W
- Page 65 and 66: capacity of OFDMA-based approaches
- Page 67 and 68: In this section, we consider differ
- Page 69 and 70: To understand the evolution of data
- Page 71 and 72: how EDGE functions including networ
- Page 73 and 74: Alternatively, the original number
- Page 75 and 76: In today’s EDGE systems, f12 thro
- Page 77 and 78:
DAS-9 16 QAM 217.6DAS-10 32 QAM 262
- Page 79 and 80:
Operators can also use their entire
- Page 81 and 82:
HSDPAHSPA refers to networks that s
- Page 83 and 84:
Figure 33: User DiversitySignal Qua
- Page 85 and 86:
Initial devices enabled peak user r
- Page 87 and 88:
“single-stream MIMO” or “MIMO
- Page 89 and 90:
Given the large amount of backhaul
- Page 91 and 92:
connection between the network and
- Page 93 and 94:
Figure 39: HSPA One-Tunnel Architec
- Page 95 and 96:
Figure 40: High-Speed Forward Acces
- Page 97 and 98:
elatively straightforward changes i
- Page 99 and 100:
on LTE began in 2004 with an offici
- Page 101 and 102:
Figure 45: LTE OFDMA Downlink Resou
- Page 103 and 104:
Single base-station antenna versus
- Page 105 and 106:
TX antennas and most devices will o
- Page 107 and 108:
Figure 48: Evolution of Voice in an
- Page 109 and 110:
Table 19: IMT-Advanced Requirements
- Page 111 and 112:
Beyond wider bandwidths, LTE-Advanc
- Page 113 and 114:
As discussed in more detail in the
- Page 115 and 116:
Different technologies spanning Wi-
- Page 117 and 118:
stations, and because of the narrow
- Page 119 and 120:
Support for new radio-access networ
- Page 121 and 122:
AbbreviationsThe following abbrevia
- Page 123 and 124:
GBR - Guaranteed Bit RateGbyte - Gi
- Page 125 and 126:
PHY - Physical LayerPMI - Precoding
- Page 127 and 128:
Additional Information3G Americas m
- Page 129 and 130:
Ericsson: HSPA voice migration, Jun
- Page 131 and 132:
SNL Kagan: press release, “SNL Ka