REG Overview

Shrivastava, Sushim (sushims) 03/17/06
Released - Internal Use Only
AMSS Packet Data Signaling

QUALCOMM CDMA Technologies
80-V3909-1 B
QUALCOMM® Proprietary
Restricted Distribution: This document contains critical information about QUALCOMM products and may not be distributed to anyone that is
not an employee of QUALCOMM, its affiliates or subsidiaries without the approval of Configuration Management.
Export of this technology may be controlled by the United States Government. Diversion contrary to U.S. law prohibited.
All data and information contained in or disclosed by this document is confidential and proprietary information of QUALCOMM Incorporated and
all rights therein are expressly reserved. By accepting this material the recipient agrees that this material and the information contained therein is to
be held in confidence and in trust and will not be used, copied, or reproduced in whole or in part, nor its contents revealed in any manner to others
without the express written permission of QUALCOMM Incorporated.
QUALCOMM Incorporated reserves the right to make changes to the product(s) or information contained herein without notice. No liability is assumed for
any damages arising directly or indirectly by their use or application. The information provided in this document is provided on an “as is” basis.
This document contains QUALCOMM proprietary information and must be shredded when discarded.
QUALCOMM is a registered trademark and registered service mark of QUALCOMM Incorporated. CDMA2000 is a registered certification mark of the
Telecommunications Industry Association, used under license. ARM is a registered trademark of ARM Limited. QDSP is a registered trademark of
QUALCOMM Incorporated in the United States and other countries. Other product and brand names may be trademarks or registered trademarks of their
respective owners.
QUALCOMM Incorporated
5775 Morehouse Drive
San Diego, CA 92121-1714
Copyright © 2002, 2005 QUALCOMM Incorporated. All rights reserved.
80-V3909-1 B Page 1 QUALCOMM Proprietary

October 2005

The following information

is licensed and
proprietary material.
Copyright © 2002, 2005
Revision history
Version Date Description
A Feb 2002 Initial release
B Oct 2005 Updated call flow scenario for UMTS

October 2005

Contents
• Functional Overview
• Packet Switch (PS) Signaling Components
• Protocol Architecture (PS domain control plane)
• SM Protocol Architecture for GPRS (in GSM)
• Protocol Architecture for SM/RABM in PS mode for UMTS
• Software Architecture (SM/RABM)
• SM Operations
• PDP State Machine
• SM Timers
• RABM Operations
• RAB Configurations
• Call Flow Scenario

October 2005

Functional Overview
• The GSM/WCDMA infrastructure is logically divided into a
Core network and an Access network. The Core network
contains functions to support features and services that
are independent of the Access Stratum.
• The Core network, also called Non-Access Stratum
(NAS), is further divided into two domains: Circuit
Switched (CS) domain and Packet Switched (PS) domain.
• The SM/RABM entities are part of NAS that provide
signaling functionality to achieve the PS services in the
user terminal.

October 2005

Functional Overview (cont.)

• The main purpose of SM is to support the Packet Data
Protocol (PDP) context handling of the user terminal (both
in GSM and UMTS). The RABM hides the concepts of
RABs that can be activated /released while a PDP context
is active (only in UMTS).

October 2005


• The SM/RABM provides Layer 3 signaling functionality to
achieve the PS services in the user terminal. The main
purpose of SM is to support the PDP context handling of
the user terminal (both in GSM and UMTS) based on a
specific QoS. The RABM hides the concepts of RABs that
can be activated/released while a PDP context is active
(only in UMTS).
• The GMM entity provides connection management
services for the SM and transmission of Layer 3 NAS
messages between the UE and the UTRAN. It coordinates
with RRC in accomplishing its services. GMM also
performs the GPRS attach and detach procedures.

October 2005


• The RRC entity in AS provides connection services to
GMM and also performs RAB establishment procedures
when a PS RAB is received. It coordinates with lower
layers and also interacts with RABM.

October 2005

Packet Switch (PS) Signaling Components

• The Packet Data Signaling functionality is composed of
the following entities of the SIMBA software:
– NAS
» Session Management (SM)
» Radio Bearer Access Management (RABM)
» GPRS Mobility Management (GMM)
– AS
» Radio Resource Controller (RRC)
– User plane
» Call Manager (CM)
» Data Services (DS)
» User Interface (UI)

October 2005

Protocol Architecture (PS Domain Control Plane)

• The UE Network protocol stack is viewed as being comprised of
two planes:
– User Plane – Consists of protocols for transfer of user information
and data
– Control Plane – Consists of signaling protocols that control and
support the user plane functionality
GMM/SM/ GMM/SM/
SMS SMS
RRC RRC RANAP/SCCP RANAP/SCCP
RLC RLC Signaling Bearer Signaling Bearer
MAC MAC AAL5 AAL5
L1 L1 ATM ATM
Uu Iu-PS
MS UTRAN SGSN

October 2005

SM Protocol Architecture for GPRS (in GSM)

SNDCP SNSM-
(user SAP
payload)
SMREG-SAP
SM GSMS CC SS
CNM
GMMSM-SAP
GMM MM
MM -Sublayer
LLC sub-layer

October 2005

Protocol Architecture for SM/RABM in

PS Mode for UMTS
DS
RAB1 RAB1 SMREG_SAP
RABM-SAP
SM GSMS
RABM
CM sublayer
RABMSM-SAP
GMMSM-SAP
GMM MM sublayer
GMMRABM-SAP
GMMAS-SAP
RABMAS-SAP
pdcp Access Stratum

October 2005

Software Architecture (SM/RABM)

DS / UTE RABs
Users
RABM
SNDCP
(UMTS)
(GSM)
Call Manager
(CM) RABMA
S_SAP
SNSM- RABMSM- NAS

SAP SAP
Session Management (SM)
GMMSM-SAP GMM
GMMRABM-SAP
PDCP
LLC RRC
sublayer
AS
RLC
GSM Dotted lines: Data UMTS

Solid lines: Signaling

October 2005

SM Operations
• Session Management performs operations involved in PDP
context management.
• PDP context:
– The PDP context describes the characteristics of the connection to
the external packet data network. These are PDP type (IP, PPP),
the PDP address (may be static or dynamic), Access Point Name
(APN), and QoS
– Each user may subscribe to one or more PDP addresses. Each
PDP address could be associated with one or more PDP contexts.
The first PDP context activated for a PDP address is known as the
primary PDP context, any subsequent PDP contexts for the same
PDP address are known as secondary PDP contexts. Either the MS
or the network initiates PDP context activation. Secondary PDP
context is only originated by the MS

October 2005

SM Operations (cont.)
• PDP context parameters
– Network Service Access Point (NSAPI) – Identifies the SAP
to be used for data transfer
– LLC SAPI – Identifies the service access point that is used
for the GPRS data transfer at the LLC layer. This is set to a
valid value in case of GSM, but left unspecified during UMTS
PDP context activation
– Requested QoS – Specifies the QoS parameters for a PDP
context
– PDP address – Identifies an address associated with a PDP.
The PDP type in the address can be either PPP or IP. Both
the IPV4 and IPV6 are supported

October 2005

• Access point name – Identifies the packet data network to
which the GPRS user wishes to connect and notifies the
access point of the packet data network that wishes to
connect to the MS. The access point name is a label or a
full-qualified domain name according to DNS naming
conventions.
• Radio priority – Specifies the priority level that the MS
shall use at the lower layers for transmission of data
related to a PDP context or for mobile-originated SMS
transmission

October 2005

• Linked TI – Specifies the active PDP context from which
the PDP address for the new PDP context could be
derived by the network (used for secondary context)
• Traffic Flow Template (TFT ) – Specifies the TFT
parameters and operations for a PDP context. TFT shall
be sent transparently to GGSN to enable packet
classification and policing for downlink data transfer

October 2005

PDP State Machine

DI (REQ PDP CONTX. ACTIV)
PDP-INACTIVE
DI (DEACTIV. PDP CONTX. ACC) PDP-INACTIVE – This
indicates that no PDP
context exists.
DR (ACTIV. PDP CONTX. REQ)
DR (DEACTIV. PDP
CONTX. ACC) PDP-ACTIVE-PENDING –
DR (ACTIV. PDP DR (DEACTIV. PDP
CONTX. REQ) CONTX. ACC) This state exists when the
MS requested PDP context
DI (ACTIV. PDP CONTX. REJ) DI (DEACTIV. PDP CONTX. REQ)
activation.
PDP-ACTIVE-
DI (DEACTIV. PDP CONTX. REQ)
PDP-INACTIVE- PDP-INACTIVE-PENDING –
PENDING
PENDING
This state exists when the
MS requested deactivation
of the PDP contexts.
DI (ACTIV. PDP CONTX. ACC) DR (DEACTIV. PDP CONTX. REQ)
DR (DEACTIV. PDP
PDP-ACTIVE – This state
CONTX. REQ)
indicates that the PDP
context is active.
DR (MOD. PDP CONTX. REQ) PDP-ACTIVE DR (MOD PDP CONTXT ACC)
PDP-MODIFY_PENDING –
DI(MOD. PDP CONTX. ACC)
PDP-MODIFY-
PENDING
DI (MOD PDP CONTXT REQ) This state exists when the
DI(MOD. PDP CONTX. REJ) MS requested modification
DR: GMMSM-DATA-REQUEST (Message), i.e. message sent by an MS
of the PDP context.
DI: GMMSM-DATA-INDICATION (Message), i.e. message received by an MS

October 2005

SM Timers
Timer Value State

T3380 30 sec PDP_ACTIVE_PENDING
T3381 8 sec PDP_MODIFY_PENDING
T3390 8 sec PDP_INACTIVE_PENDING

October 2005

RABM Operations
• RABM receives indication from SM about any PDP
activation, modification, or deactivation
• RABM coordinates with the Access Stratum to
setup/release radio access bearer (based on the RABID)
• RABM reestablishes a specified RAB upon a
reestablishment request from the DS (through CM)
• RABM notifies the RAB establish/release indication to the
DS (through CM) upon receiving the indication from the
RRC, during an Active PDP context

October 2005

RAB Configurations
• The following are various RAB configurations available for PS call:
Test case in RAB setup Configuration

TS 34.123
14.2.23.1 Interactive or background / UL:32 DL:8 kbps / PS RAB + UL:3.4
DL:3.4 kbps SRBs for DCCH / (TC, 10 ms TTI)
DL:3.4 kbps SRBs for DCCH / (CC, 10 ms TTI)
14.2.24 Interactive or background / UL:64 DL:8 kbps / PS RAB + UL:3.4
DL:3.4 kbps SRBs for DCCH
14.2.25.1 Interactive or background / UL:32 DL: 64 kbps / PS RAB + UL:3.4
DL:3.4 kbps SRBs for DCCH/ (TC, 10 ms TTI)

October 2005

RAB Configurations (cont.)

14.2.26 Interactive or background / UL:64 DL: 64 kbps /
PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH
14.2.27 Interactive or background / UL:64 DL:128 kbps /
PS RAB + UL:3.4 DL: 3.4 kbps SRBs for DCCH
14.2.31.1 Interactive or background / UL:64 DL:256 kbps /
/10 ms TTI
/20 ms TTI
PS RAB + UL:3.4 DL: 3.4 kbps SRBs for DCCH /
10 ms TTI
PS RAB + UL:3.4 DL: 3.4 kbps SRBs for DCCH /
20 ms TTI
Note: Not all RAB configurations are supported in current AMSS software.

October 2005

Call Flow Scenario

MS-Originated PDP Context Activation - UMTS
CM SM RABM GMM AS
1. SMREG-
PDP-ACTI
VATE_REQ
2.SM creates
RABID
4. RABMSM-
ACTIVATE-IND
3 start t3380 (QOS,NSAPI)
3. PDP-ACTIVE- 5. GMMSM-
PENDING UNITDATA-IND)
6. GMMAS
DATA-REQ
(PDP activate
req)
7. RABMAS-RAB-
ESTABLISH-IND (query)
8. AS will
establish
the RAB.
8. RABMSM_ 9. GMMAS
ACTIVATE_RSP DATA-IND
10. GMMSM- (PDP activate
UNITDATA-REQ accept)
(SMPDU)
11. stop t3380
11. PDP-ACTIVE
validate QOS
invalid QOS,
start deactivation
procedures
12. SMREG-PDP-
ACTIVATE-REJ
valid QOS
12. SMREG-PDP-
ACTIVATE-CNF

October 2005

Call Flow Scenario (cont.)

MS-Originated PDP Context Modification - UMTS

October 2005

Call Flow Scenario

MS-Initiated PDP Deactivation
CM RABM GMM
SM AS (RRC)
1. SMREG-PDP-
DEACTIVATE-REQ)
2. start t3390
2. PDP-INACTIVE-
PENDING
3. RABMSM-
DEACTIVATE.ind
4. GMMSM-
UNITDATA-REQ
(SMPDU)
PDP Deactivate
Request
5. GMMSM-UNIT
DATA_IND
6. PDP-INACTIVE PDP Deactivate
6. stop Accept
t3390
7. RABMAS-RAB-RELEASE-IND
8. RABMSM-
DEACTIVATE.
9. SMREG-PDP- RSP
DEACTIVATE-CNF

October 2005

Call Flow Scenario

RAB Setup/Teardown While PDP is Active
CM RABM GMM
SM AS (RRC)
1. RABMAS-RAB-RELEASE-IND
2. RABM-RAB-RELEASE-IND-
3. RABMAS-RAB-ESTABLISH-CNF
4. RABM-RAB-ESTABLISH-IND

October 2005

Call Flow Scenario

RAB Reestablishment procedure
RABM GMM AS
CM
1. RABM-RAB-
REESTABLISH-REQ
2. GMMRABM_ESTABLISH_
REQ(RABID)
3. GMM initiates a
service request
procedure to
reestablish a RAB
4. GMMRABM_
REEST-RSP
5. RABMAS-ESTABLISH-IND
6. RABM-RAB-
REESTABLISH-CNF
(status = SUCCESS)
7. GMMRABM_
REEST-REJ
8. RABM-RAB-
REESTABLISH-CNF
(status = FAILURE)

October 2005

Questions?
asicapps@qualcomm.com
October 2005

REG Overview

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

REG Overview

Hochgeladen von

Copyright:

Verfügbare Formate

Shrivastava, Sushim (sushims) 03/17/06

Released - Internal Use Only

AMSS Packet Data Signaling

80-V3909-1 B Page 1 QUALCOMM Proprietary

Released - Internal Use Only

The following information

Copyright © 2002, 2005

80-V3909-1 B Page 2 QUALCOMM Proprietary

Released - Internal Use Only

80-V3909-1 B Page 3 QUALCOMM Proprietary

Released - Internal Use Only

80-V3909-1 B Page 4 QUALCOMM Proprietary

Released - Internal Use Only

Functional Overview (cont.)

80-V3909-1 B Page 5 QUALCOMM Proprietary

Released - Internal Use Only

Functional Overview (cont.)

80-V3909-1 B Page 6 QUALCOMM Proprietary

Released - Internal Use Only

Functional Overview (cont.)

80-V3909-1 B Page 7 QUALCOMM Proprietary

Released - Internal Use Only

Packet Switch (PS) Signaling Components

80-V3909-1 B Page 8 QUALCOMM Proprietary

Released - Internal Use Only

Protocol Architecture (PS Domain Control Plane)

RRC RRC RANAP/SCCP RANAP/SCCP

RLC RLC Signaling Bearer Signaling Bearer

MAC MAC AAL5 AAL5

80-V3909-1 B Page 9 QUALCOMM Proprietary

Released - Internal Use Only

SM Protocol Architecture for GPRS (in GSM)

80-V3909-1 B Page 10 QUALCOMM Proprietary

Released - Internal Use Only

Protocol Architecture for SM/RABM in

pdcp Access Stratum

80-V3909-1 B Page 11 QUALCOMM Proprietary

Released - Internal Use Only

Software Architecture (SM/RABM)

SNSM- RABMSM- NAS

Session Management (SM)

GSM Dotted lines: Data UMTS

80-V3909-1 B Page 12 QUALCOMM Proprietary

Released - Internal Use Only

80-V3909-1 B Page 13 QUALCOMM Proprietary

Released - Internal Use Only

80-V3909-1 B Page 14 QUALCOMM Proprietary

Released - Internal Use Only

80-V3909-1 B Page 15 QUALCOMM Proprietary

Released - Internal Use Only

80-V3909-1 B Page 16 QUALCOMM Proprietary

Released - Internal Use Only

PDP State Machine

80-V3909-1 B Page 17 QUALCOMM Proprietary

Released - Internal Use Only

Timer Value State

80-V3909-1 B Page 18 QUALCOMM Proprietary

Released - Internal Use Only

80-V3909-1 B Page 19 QUALCOMM Proprietary

Released - Internal Use Only

Test case in RAB setup Configuration

80-V3909-1 B Page 20 QUALCOMM Proprietary

Released - Internal Use Only

RAB Configurations (cont.)