1Conference Call

2
1

2
3
4TITLE
5

X31-20040503-xxx

TSG-X.PSN.PDS

Example 3GPP2 QoS Signaling Flow

7SOURCE
8
Alan.Hsu@nokia.com
Haihong.Zheng@nokia.com
Marc.Greis@nokia.com

9
10

11ABSTRACT
12

13This contribution proposes the message flow for the support of E2E QoS mechanism following the approach as
14currently agreed upon in the TSG-X.PSN.PDS SWG. This contribution is a revision of the Section 3 (Message Flow)
15of contribution [1]
16

17RECOMMENDATION
18
19Discuss and adopt in X.S0011-D.
20
21
22
Notice
23The contributors grants a free, irrevocable license to 3GPP2 and its Organizational Partners to incorporate text or other copyrightable material
24contained in the contribution and any modifications thereof in the creation of 3GPP2 publications; to copyright and sell in Organizational
25Partner's name any Organizational Partner's standards publication even though it may include all or portions of this contribution; and at the
26Organizational Partner's sole discretion to permit others to reproduce in whole or in part such contribution or the resulting Organizational
27Partner's standards publication. The contributors are also willing to grant licenses under such contributor copyrights to third parties on
28reasonable, non-discriminatory terms and conditions for purpose of practicing an Organizational Partners standard which incorporates this
29contribution.
30
31This document has been prepared by the contributors to assist the development of specifications by 3GPP2. It is proposed to the Committee as a
32basis for discussion and is not to be construed as a binding proposal on the contributors. The contributors specifically reserves the right to amend
33or modify the material contained herein and to any intellectual property of the contributors other than provided in the copyright statement above.

34

1Conference Call
2
11 INTRODUCTION

X31-20040503-xxx

2
3
4
5
6
7
8
9
10
11
12
132

In the December 2003 TSG-X.PSN.PDS SWG meetings held in Maui, HI, the PDS SWG have reached agreement
on some criteria [2] with regard to the E2E QoS solution:

14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29

The 3GPP2 QoS parameters, contained in a QoS IE of 3GPP2_OBJECT, convey the QoS requirements of a
particular flow among different network entities. The minimum set of these QoS parameters, proposed in
contribution [1] and is revised in a new contribution [3], is carried in the 3GPP2 RSVP-RESV message over the
main service instance as shown in Figure 1.

Use enhanced flow mapping/treatment protocol for Qos signaling from the MS to the PDSN.
Having the capability in the PDSN to request an R-P connection with specific QoS parameters.
Adopt the approach, i.e., the MS sends QoS Requirement to the PDSN and the PDSN sends the QoS requirement
to the RAN.
This contribution proposes an example message flows for the support of E2E QoS mechanism following the
approach as outlined above. The proposal utilizes the PDS architecture that underlies the X.P0011-C release.
SUPPORTING MESSAGE FLOW

Figure 1 illustrates the signaling procedures among the CDMA2000 network entities (i.e., MS, RAN, and PDSN)
to establish an end-to-end QoS session. The message flow shows initiation of an auxiliary service instance from
the PDSN, signaling of packet filters, and communicating service instance (and IP flow) level specification.
These procedures are based on CDMA2000/IOS standard and 3GPP2 flow mapping and treatments protocol
specified in 3GPP2 X.S0011-C, with enhancements.
The RESV message containing the TFT for the new auxiliary service instance is sent to the PDSN. 3GPP2
OBJECT defined in X.S0011-C is enhanced to convey the QoS requirements/parameters (which can be defined as
a new QoS Information Element (IE) of the OBJECT) for the application. The PDSN extract and/or derive the
QoS parameters that are applicable to the radio interface and send a R-P update message with the corresponding
QoS parameters to the radio interface.

30
31
32
33
34
35
36

Based on the QoS parameters sent from the PDSN, the RAN determines the radio link related QoS attributes and
determines that if a new service instance is required for the flow. If yes, the RAN then initiates the establishment
of the radio link for an auxiliary service instance. After the auxiliary service instance is established, the RAN
requests the PDSN to establish a R-P connection with the granted QoS attributes. The PDSN sends a
RESV_CONF message with the granted QoS parameter set to the MS to confirm the completion of end-to-end
QoS signaling.

37
38
39
40

In addition to the parameters aforementioned, a unique request ID is assigned by the MS and carried in multiple
messages to correlate the messages together. The request ID carried in R-P update message and Aux SI setup
message ensures that the auxiliary service correlates tothe RSVP RESV message. The pair of request ID and
SR_ID in the R-P setup request message is necessary for the PDSN when sending RESV_CONF message.

41
42

1Conference Call
2
MS

X31-20040503-xxx

RAN

PDSN

3GPP2 RSVP-RESV mess age over main SI

(3gpp2 object: TFT,flowQoSreverse, flowQoSforwa
rd, req
uest ID)
R-Pupdate(QoS attributes, request ID)
R-Pupdate response
AuxSI set up (QoS_ BLOB, SR_ ID, request ID)
AuxSI set up ack

R-Psetupresponse
3GPP2 RSVPRESV_ CONFmessage over main SI (SR_ ID, granted QoS, request ID)

3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27

2
3
4
5

R-Psetuprequest (granted QoSattributes, SR_ ID, request ID)

1
2

6
7
8

Figure 2-1. QoS Negotiation Procedure with network initiated SI establishment

1

2
3
4

5
6

7
8

After exchanging the SDP information with the CN using end-to-end application level signalling such as SIP
(not shown in the diagram), the MS sends a 3GPP2-RSVP Resv message to the PDSN containing the flow
level end-to-end QoS attributes (i.e. QoS IE) in the 3GPP2_OBJECT for both the forward link and reverse
link. A request ID is included in QoS IE and it facilitates the MS, RAN and PDSN to correlate the request
with the assigned SR_ID.
After successful authorization of the requested QoS attributes, the PDSN processes the request, and derives the
radio related QoS parameters from the flow level QoS attributes and sends them to the RAN using the R-P
update message. The request ID carried in step 1 is included as well.
RAN acknowledges the R-P update message (i.e. R-P Update Response Message or other message that will be
determined by TSG-A).
The RAN determines if a new auxiliary service instance is needed. If yes, RAN determines if it can honour the
QoS request as specified in Step 2 (i.e. R-P Update Message). If yes, according to cdma2000 air interface
procedure, RAN requests establishment of a Service instance to satisfy the radio QoS request. . The presence
of the request ID in the message also allows the MS to correlate this message with the previously sent RESV
message before accepting the request.
The MS accepts the request.
The RAN sends R-P setup request message to the PDSN, and the request message may contain actual granted
QoS parameters if the requested one could not be honoured (to be used for accounting). The message also
contains the assigned SR_ID and the request ID. This enables PDSN to correlate the R-P setup request
message with the R-P update message and thereafter the 3GPP2 RSVP RESV message.
PDSN acknowledges the R-P setup message.
Based on the granted QoS attributes sent from the RAN, the PDSN generates the granted end-to-end QoS
attributes based on certain system configurations or parameters, and then sends the RESV_CONF message to
the MS and includes the SRID, the request ID and the granted end-to-end QoS.

28
293

RECOMMENDATIONS

30

Use the proposed signaling flow as the baseline to develop the QoS signaling procedure in 3GPP2 networks.

1Conference Call
2
1
24

X31-20040503-xxx

REFERENCES

3[1] X31-20040315_19R1 QoS-Parameters-Msg-Flow, Nokia, Ericsson, and Samsung, Vancouver, March, 2004
4[2] X31-20031208-019R4 Support for End-to-End QoS: QoS Signaling procedure.
5[3] X31_20040419_xxx, 3GPP2 QoS Parameters, April 2004.
6