QoS framework (PR0002) Rev.0.5 (Work in progress)

Objective and scope of the framework Define QoS signaling and transport mechanisms to support traffic handling differentiation between real time and non-real time services. The focus in release C3 is to define those mechanisms between the MS and PDSN including impacts on RAN to support voice over IP and streaming. Based on the current IS-835 architecture Evolve in an ALLIP environment

Scope of PR0002 The framework includes the following items: -QoS requirements -Traffic classes -Service instances -Mapping of traffic classes to service instances -End-to-End QoS model -QoS signalling -QoS transport -QoS policy

QoS requirements QoS requirements are based on 3GPP2-S00- QoS R1. They are described in section A-1 of the framework.

Traffic classes Adopted the 3GPP traffic classes as per the output of the QoS JEM meeting The main distinguishing factor between these QoS classes is how delay sensitive the traffic is: conversational class (voice over IP); streaming class; interactive class; background class.

Service instances Circuit service instance: used for CS voice services and CS data services packet service instance: refers to a service instance that is switched/routed through the PDSN –primary service instance: is first negotiated when establishing the packet service (existing S0 33) –secondary or auxiliary service instances (QoS): is requested/set up on a per need basis

Packet Service instances Currently three packet service instance types are defined for release C3, using RLP characteristics as a QoS distinguishing factor :  SI-TYPE _1: identifies a primary service instance for re-transmitting RLP that carries PPP traffic that are delay insensitive but error sensitive media (e.g. FTP, HTTP, etc.).  SI-TYPE _2 identifies a secondary/auxilliary service instance with no RLP overhead that serves to carry cdma voice codecs (e.g. EVRC, SMV) that are synchronous with the cdma2000 air framing.  SI-TYPE _3 identifies a secondary/auxilliary service instance for non re-transmitting RLP that carries PPP traffics that are delay sensitive and asynchronous with the cdma2000 air framing (eg. Multimedia)

Mapping of traffic classes to service instances Background -> Primary (SI-TYPE-1) Interactive -> Primary (SI-TYPE -1) Streaming ->secondary (SI-TYPE 2) Conversational: CDMA2000 Voice over IP ->secondary (SI-TYPE 2) Other conversational->secondary (SI- TYPE 3)

End-to-End QoS model

QoS signaling QoS signalling has the following aspects: -It is Edge-to-Edge (only between MS, RAN and PDSN). No End-to-End QoS signaling. -It is a Link layer level signaling (CDMA2000 and PPP) -signaling of CDMA2000 QoS parameters on a per service instance (user data rate, priority, data loss rate, maximum delay) using IS-2000 x and IOS 4.x. -signaling of traffic flow template over PPP.

QoS transport Ongoing discussions - no decision so far: Multiple service instances capability raises questions on how PPP should be supported on mobile stations. Mainly: - single PPP for all packet service instances (PPP for the primary service instance) - vs. multiple PPP, a PPP per packet service instance (except for the CDMA2000 voice over IP service instance) Mobile stations may be self contained network model phones, relay phones to TEs, or network model phones with attached TEs.

QoS transport (2) Under discussion –marking of packets in the R-P network could be done in a number of ways: per service instance: Mapping of CDMA2K blob to a DiffServ Code Point (DSCP) using operator’s policy in the PDSN. The DSCP is used in the outer IP header of the GRE tunnel. Per flow: This option will allow differentiation of flows with varying QoS characteristics when sent over the same service instance. –Diffserv is assumed to be used on the bearer to the external network

QoS policy The PDSN acts as a policy enforcement point. At reception of a QoS- signaled request from the MS, the PDSN enforces the policy that it may receive from a policy server (eg. AAA or core QoS manager). Statically provisioned policy is also possible. The policy may involve: -User’s policy : user’s profile containing QoS subscription. The QoS subscription may consist of the policy for a given service instance class (air policy) and/or the IP QoS which consists of the set of differentiated services codepoints that are allowed for the user or packet classification information in support of the marking of unmarked packets. -Network policy: resource status, allowed number of user’s with a particular request, time of day, etc. -PPP policy: describes the allowed PPP options such as number of IP addresses, associated PPP header/payload compression types that the user may invoke for the associated secondary service instances.

End of presentation