MMD EvolutionJune 28, 2005
OutlineMMD BasicsEnd-to-End ExamplePacket Switched Video TelephonyLegacy MS Domain EvolutionTransition to MMD MMD Evolution3GPP2 Project Roadmap
Introduction3GPP2 defines core standards for VoIP and multi-media servicesNot just a replacement for circuit-switched voiceOther example services: voice/video conferencing, PTT, Presence and Instant Messaging.CDMA2000 packet network standards build on results from the IETF and IMS-related standards from 3GPP3GPP2 All-IP network is comprised of two domains:Legacy MS Domain (LMSD)Multimedia Domain (MMD.)
LMSDThe Legacy MS Domain provides support for existing mobiles (e.g., analog, IS-95-A, IS-95-B, IS-2000) with an IP core network.The Legacy MS Domain supports the features and capabilities provided in a legacy network in a manner transparent to the user.LMSD supports Transcoder Free Operation (TrFO) and Remote Transcoder Operation (RTO) operations.
Multi-Media DomainMulti-Media Domain (MMD) provides support for SIP capable mobile stations in an IP core network environment.MMD supports multimedia sessions to and from SIP-capable mobileAlso defines interworking with circuit switched networks via Media Gateways.
IP Multimedia in 3GPP/3GPP23GPP/3GPP2 standards for IP Multimedia servicesIP Multimedia Subsystem (IMS) in 3GPPMultimedia Domain (MMD) in 3GPP2 (IMS plus CDMA packet data transport and enhancements for CDMA operation.)3GPPs decided to harmonize IMS. Now nearly identical at IMS level.
Regulatory issues must be addressed (VoIP surveillance, tax structure for internet services, E911 and position location, etc.)
Basic call flow
Packet Switched Video Telephony (PSVT)An example service for the MMDIncludes air interface, RAN, core network aspects, and terminal procedures Most procedures exist in current standards, e.g.X.S0011 Wireless IP Rev DX.S0013 MMD Rev 0A.S00xxxxxxxxxxxx IOSC.S0024 HRPD Rev AC.S0001 - C.S0006
PSVT ComponentsAir InterfaceService Options to be used for transporting SIP, Audio, Video, and RTCP trafficProcedures for requesting appropriate air link QoS for these different traffic typesIOS (A-interface)Specifications for handoffs and cross paging of HRPD-1x hybrid terminalsPacket Data NetworkIdentifies procedures for QoS establishment and flow treatmentRecommends header compression optionsProcedures for packet data accountingMMDProcedures for session setup using SIPSIP compression and security proceduresProcedures for MMD accounting
Following slides provide architecture and call flows.
PSVT Reference Model
SIP SignalingOTA/IOS SignalingMedia Control for Audio/VideoAudio Bearer PathVideo Bearer PathAAA/HSS InterfacesMP Interfaces
PSVT Call Flow (tbd)
8. Media Flow
1. SIP Capability Exchange (INVITE/183)
2. Bearer Resource Establishment
3. Indicate Bearer setup complete (UPDATE/200 OK)
5. Indicate MS-2 alerted (180 Ringing)
4. Called MS alerted
6. Called MS answers
7. Complete SIP session setup (200 OK/ACK)
Bearer Resource Establishment
PSVT QoS-1Access networks enforce agreed QoS for different IP flows
PSVT QoS-2PDSN enforces DiffServ code pointsEnd-to-End QoS possible within managed network(REDRAW figure)
Drag the side handles to change the width of the text block.
PDSN polices/remarks DSCP then forwards IP packet
BSC/AN tunnels data over A10 connection
Application QoS Negotiation (SIP/SDP)
Air link (RLP)
PDSN uses TFT filter to map packet to A10
BSC/AN maps A10 to RLP link
Air link (RLP)
PSVT ChallengesLow-interruption handoffsRequires low latency inter-PDSN handoffs HRPD does not YET support active handoffsHand-down and hand-upVariations in QoS resources or bearer support due to sector loading or inter-technology handoffsHow to modify media streams (e.g., add/remove video) with minimal interruption?Updating QoS resources for MS.
LMSD EvolutionLegacy Mobile Station Domain (LMSD)IS-2000 RAN, with IP-based Ainterface , VoIP transport between MSC soft-switches Step 1, call deliveryStep 2, handoffs and better feature support.Ability to interwork with other network types:MMD/IMSPacket CableDSLEnhancementsFaster call setup Security for bearer.
Transition ArchitectureEvolution to MMD will occur in stepsTransition architecture will supportInterworking with legacy circuit switched networksHandoffs from MMD services to legacy services where possible.
Placeholder for HRPD/1x interworking figure
MMD EvolutionDefine the path from circuit switched voice networks to LMSD and MMDTransition ArchitectureCall deliveryHandoffWLAN..ServicesConferencingMessaging and PresenceEmergency servicesLocal services.EnhancementsFaster session setupSecurity.
Future DevelopmentTrue End-to-End QoS
Full interworking with other networks, including UMTS, public internet, Next Generation Network
3GPP2 MMD Roadmap
Architecture, Security, LMSDStage 2Stage 3Access network specifications.
(note published documents available at www.3gpp2.org)
Architecture, Security, LMSD
Stage 1 and Overview DocumentsS.R0037-A, IP Network Architecture Model for cdma2000 Spread Spectrum SystemsS.R0062, Presence Stage 1X.S0027-000, Presence Overview X.S0013-000, MMD Overview document Security DocumentsS.R0086-A, MMD Security FrameworkLegacy Mobile Station Domain (LMSD) Documents(IS-95/2000 circuit mode MS+RAN with VoIP core network)S.R0092, System requirementsS.R0096 Transcoder Free Operation, Stage 1 requirementsP.S0002, LMSD - Step 1, incoming PSTN call deliveryX.S0012, MSCe-MSCe Signaling ControlX.S0018, G.711 PCM voice between MGWs.
Stage 2X.S0013-002 IP Multimedia Subsystem (IMS) (based on 3GPP TS 23.228)X.S0013-003 IP Multimedia (IM) session handling; IM call model (based on 3GPP TS 23.218)X.S0013-007 Accounting Architecture (based on TS 32.200)X.S0013-005 IP Multimedia (IM) Subsystem Cx Interface; Signaling flows and message contents (based on TS 29.228)X.S0013-010 IP Multimedia Subsystem (IMS) Sh Interface signaling flows and message contents (based on TS 29.328)X.S0027-001, Presence Architecture
Stage 3Protocol & ProceduresX.S0013-004, IP Multimedia Call Control Protocol based on SIP and SDP; (based on TS 24.229)X.S0013-006, Cx Interface (HSS-CSCF) based on the Diameter protocol; Protocol details (based on TS 29.229)X.S0013-008, Accounting data description (based on TS 32.225)X.S0013-011, Sh interface (HSS-AS) based on the Diameter protocol (based on TS 29.329.)X.S0017 Open Service Access (OSA); Application Programming Interface (based on TS 29.198 series)
CDMA Access Network DocumentsPacket Data Serving Node (PDSN)X.S0011-C, Wireless IP Network Standard (IS-835)CDMA2000 1x air interfaceC.S0001 to C.S0006, cdma2000 Family of Standards for Spread Spectrum SystemsC.S0047, Header compression/removal service options, allows VoIP to be sent efficiently over the air CDMA2000 DO air interfaceC.S0024-A (IS-856-A), Significant upgrades for supporting QoS sensitive servicesC.S0063 (TIA-1054), Enhanced Multi-flow Packet Application, eliminates overhead from PPP and octet-based HDLC-like framing. Two-route RLP facilitates seamless BSC-BSC Connected State handoff to eliminate interruption during the VoIP call.
Current ProjectsX.P0011-D, includes MIP6 and QoS supportX.P00xx, End-to-end QoS X.S0013 revisionIncludes new part for Service Based Bearer Control, X.P0013-012, enables mapping/control of SDP-negotiated QoS to air interface QoS.X.P0027, New parts for presence security, protocol, network presence.X.P0028, CDMA/WLAN interworkingScenarios 1,2Scenarios 3,4X.P0029, ConferencingTSB-58-G, to define QoS Profiles A-interfaceIS-878-A/IS-1878-A, QoS support on the A-interfaceIS-878-B / IS-1878-B, Connected State seamless inter-BSC soft handoff and session transferC.P0023-C, R-UIM cards support for MMD data.PN-0196, Lawfully Authorized Electronic Surveillance for cdma2000 VoIP.HRPD/1x interworkingPacket Switched Video Telephony.