1

MC-MAP OverviewMC-MAP Overview

Jan. 12, 2000Jan. 12, 2000Michael Vakulenko, Ragulan Sinnarajah, Avinash Jain, Pradeep Jain, Jack Nasielski, Michael Vakulenko, Ragulan Sinnarajah, Avinash Jain, Pradeep Jain, Jack Nasielski,

Ed Tiedemann, Ramin RezaiifarEd Tiedemann, Ramin Rezaiifar

3Gpp2-________-2000-01-10___-____

©2000 QUALCOMM Incorporated. All rights reserved.The information contained in this contribution is provided for the sole purpose of promoting discussion within the 3GPP2 and its Organization Partners and is not binding on the contributor. The contributor reserves the right to add to, amend, or withdraw the statements contained herein.

QUALCOMM Incorporated grants a free, irrevocable license to 3GPP2 and its Organization Partners to incorporate text or other copyrightable material contained in the contribution and any modifications thereof in the creation of 3GPP2 publications; to copyright and sell in Organizational Partner's name any Organizational Partner's standards publication even though it may include portions of the contribution; and at the Organization Partner's sole discretion to permit others to reproduce in whole or in part such contributions or the resulting Organizational Partner's standards publication.

The contributor may hold one or more patents or copyrights that cover information contained in this contribution. A license will be made available to applicants under reasonable terms and conditions that are demonstrably free of any unfair discrimination.Nothing contained herein shall be construed as conferring by implication, estoppel, or otherwise any license or right under any patent, whether or not the use of information herein necessarily employs an invention of any existing or later issued patent, or copyright. The contributor reserves the right to use all material submitted in this contribution for his own purposes, including republication and distribution to others.

2

MC-MAP RAN ArchitectureMC-MAP RAN Architecture

CDMA MC RAN

CDMA MC BSC CDMA MC BSC

GSM-MAP Core Network

CDMA MCBTS

A/Iu Interface

CDMA MCBTS

CDMA MCBTS

CDMA MCBTS

CDMA MCmobile

Air Interface

3

MC-MAP Protocol StackMC-MAP Protocol Stack

GSM L3 Mobility Management (MM)

CDMA MC MAP L3 Radio Resource Control (RRC)

CDMA MC MAC

CDMA MC L1

GSM L3 Connection Management (CM)

CDMA MC LAC

4

Changes to C.S2000-AChanges to C.S2000-A

• C.S0002-A uses a permutation of the bits of the ESN for the Public Long Code Mask (PLCM)

• MC-MAP will use the TMSI or a mask supplied by the base station, which does not depend on the availability of ESN

• The BS indicates the the PLCM in the ECAM (PLCM_TYPE field)

11000 PLCM_37

41 … 37 36 … 0

1100011000 Perm u ted E S N

41 … 32 31 … 0

ESN-based

Non-ESN-based example

5

Changes to LAC: Addressing in MC-MAPChanges to LAC: Addressing in MC-MAP

• Strict layering in 3GPP requires the maintenance of 3 temporary mobile station identities:

• TMSI: Temporary Mobile Station Identity used by PSTN. Referred to as MAP-TMSI in MC-MAP, it is completely specified by

TMSI (32bits) + MCC (3digits) + MNC (3digits) + LAC (16bits)

• P-TMSI: Packet network Temporary Mobile Station Identity. Referred as MAP-P-TMSI in MC-MAP, it is completely specified by

P-TMSI (32bits) + MCC (3digits) + MNC (3digits) + LAC (16bits) + RAC(8bits)

• RNTI: Radio Network Temporary Identity

used by RR layer to communicate with the corresponding peer entity at the other side. In MC-MAP, R-TMSI (Radio TMSI with structure similar to TMSI defined in C.S000X-A) is used in place of RNTI.

6

LAC Enhanced ServicesLAC Enhanced Services

• Enhanced services apply only to CM and MM messages• Services:

– In-Order Delivery of Layer 3 Messages– Prioritization: Messages are transmitted according to

priorities assigned by Layer 3– Service Access Point Multiplexing: Messages

received and delivered from/to Layer 3 at several SAPIs

– Outgoing Message Queues Flushing

7

LAC Enhanced Services (cont’d)LAC Enhanced Services (cont’d)

• Addition of an Enhanced Services Sublayer above the ARQ Sublayer on the dedicated channels (fwd and rev)

• Parameters of the Enhanced Services Sublayer:– SAPI: Service Access Point Identifier– ORD_IND: Indicates whether the message is to be

delivered in order – L3_MSG_NUM: Sequence number used for

ordering messages

8

RRC ProceduresRRC Procedures

• RRC Connection Management Procedures• Radio Access Bearer (RAB) Procedures• MS Capability Request/Response Procedures• Direct Transfer Procedures• Connected Mode Paging Procedures

9

RRC Connection Management ProceduresRRC Connection Management Procedures

• RRC Connection Establishment– MS in “Idle” state (i.e. Monitoring f-csch)– RRC Connection initiated due to either 1) Request

from MS upper layers, 2) General Page Message from the BS

– MS initiates RRC Connection Establishment by sending a MC-MAP RRC Connection Request Message to the BS.

– BS sends an Extended Channel Assignment Message in response to receiving this message.

– Upon receiving the ECAM, MS transitions to the Mobile Station Control on the Traffic Channel State.

10

RRC Connection Management Procedures ..RRC Connection Management Procedures ..

• The MC-MAP RRC Connection Request Message contains: – Establishment Cause– MS Identity– MS Capability

• RRC Connection Release– Similar to connection release in cdma2000– Using Release Order or Extended Release

Message– Upon successful release of the RRC Connection,

MS transitions to the “Idle” state

11

Radio Access Bearer (RAB) ProceduresRadio Access Bearer (RAB) Procedures

• A RAB instance in MC-MAP corresponds to a service option connection instance in cdma2000. – CON_REF corresponds to RAB instance identifier

• RABs are established, reconfigured, and released while the MS is in the Traffic Channel substate of the Mobile Station Control on the Traffic Channel State.

• RABs are established, reconfigured, and released through the cdma2000 service negotiation messages (Ex. Service Connect Message)

12

MS Capability Request/Response ProceduresMS Capability Request/Response Procedures

• MS may receive a “MS Capability” Request from BS, while in “Idle” state or in the Traffic Channel substate of the Mobile Station Control on the Traffic Channel State

• BS requests MS capability through Status Request Message.

• MS responds with (Extended) Status Response Message.

• MS may also initiate sending “MS Capability” to BS

13

Direct Transfer ProceduresDirect Transfer Procedures

• Direct Transfer procedures are used to transparently carry upper layer (Non-Access Stratum) information between MS and BS

• Initial Direct Transfer via MC-MAP Initial L3 Message (MS to BS direction only)

• Subsequent Direct Transfers via MC-MAP L3 Message (both directions)

• Both messages carry (to route to the NAS entity):– CN_DOMAIN_ID– SERVCIE_DESCRIPTOR– FLOW_ID

14

Connected Mode Paging ProceduresConnected Mode Paging Procedures

• Used for paging the MS (Paging Type 2) while the MS is in the Traffic Channel substate of the Mobile Station Control on the Traffic Channel State, to establish a new call.

• Implemented through a modified version of the cdma2000 Call Assignment Message.

• The message carries:– CN Domain Identity– Service Option Number– MC_MAP_BLOB field carries “paging record type

identifier”

15

MS IDMS ID

• Choice of MS identity by base station:

– If temporary identity is assigned, choice of the MS identity depends on where the message/order originates from (IP/PSTN/RAN)

– If MAP-TMSI or MAP-P-TMSI are not assigned, the corresponding CN may address the mobile station by IMSI/IMEI.

• Choice of its identity by mobile station: Preference order is

R-TMSI, MAP-TMSI/MAP-P-TMSI, IMSI, IMEI

• If R-TMSI is not assigned, RR-level communication can not occur between the mobile station and the base station.

• RRC Connection on common channels

- is achieved by maintaining valid R-TMSI while the mobile station is monitoring common channels.

- in MC-MAP, the mobile station achieves it by RR-level Registration.

16

MC-MAP Intersystem HandoffMC-MAP Intersystem Handoff

• Objective– Seamless handoff from/to MC-MAP to/from GSM

(and DS-MAP)• Implementation

– Minimum changes to IS-2000– Transport of the GSM Handover Command

• Note: GPRS does not need handoff (location update is used instead)

17

MC-MAP to GSM HandoffMC-MAP to GSM HandoffMC-MAP to GSM HandoffMC-MAP to GSM Handoff

OldMC-MAP

BS

NewGSMBSS

GSMMSC6. CF Search Report

5. Measurements

7. HO Required

8. HO Req

uest

FCCH+SCH

1.Search trigger

2. CF Search Req.

12. TCH

3. CF Search Resp.

4. CF Search Ctrl

9. HO R

equest

Ack

(Han

dover

Command)

10. Handover Command

11.Handover Command

18

UE/MS BSS BS MCGSM

Handover Preparation

Handover Complete

Handover Completion

System Acquisition andAccess

Candidate FrequencySearch Request M.

Candidate FrequencySearch Response M.

MC-MAP GSM HandoverCommand Message

[GSM Payload]

Candidate FrequencySearch Report M.

Candidate FrequencySearch Report M.

Candidate FrequencySearch Control M.

Candidate FrequencySearch Report M.

MC-MAP to GSM HandoffMC-MAP to GSM HandoffMC-MAP to GSM HandoffMC-MAP to GSM Handoff

19

UE/MS BS BSSMC GSM

Extended MeasurementReport

Extended MeasurementOrder

Handover Preparation

Handover Command[MC Payload]

Handoff Completion Msg.

Handover Completion

System Acquisition andAccess

Extended MeasurementReport

Extended MeasurementReport

GSM to MC-MAP HandoffGSM to MC-MAP HandoffGSM to MC-MAP HandoffGSM to MC-MAP Handoff

20

U E /M S t-R N C BS M CDS

Candidate Frequency SearchReport M .

Candidate FrequencySearch Contro l M .

Handover P reparation

G eneral Handoff D irectionM .

[DS Payload]

Handover Com plete

Handover Com pletion

System Acquis ition andAccess

Candidate Frequency SearchReport M .

Candidate FrequencySearch Report M .

Candidate FrequencySearch Response M .

Candidate FrequencySearch Request M .

MC-MAP to DS-MAP HandoffMC-MAP to DS-MAP HandoffMC-MAP to DS-MAP HandoffMC-MAP to DS-MAP Handoff

21

U E /M S B S s-R N CM C D S

M easurem ent Report

M easurem ent Contro l

Handover P reparation

Inter-System HandoverCom m and

[M C Payload]

Handoff Com pletion M .

Handover Com pletion

System Acquis ition andAccess

M easurem ent Report

M easurem ent Report

DS-MAP to MC-MAP HandoffDS-MAP to MC-MAP HandoffDS-MAP to MC-MAP HandoffDS-MAP to MC-MAP Handoff

22

Example Location Update Message Flow Example Location Update Message Flow

RR_EST_REQ (LO CATIO N UPDATING REQ UEST,Establishm ent Cause = LU) 1: M APCRM (Establishm ent Cause = LU,

Initia l M S Id, In itia l M S Capability)

2: ECAM (Initia l M S Id, Channel Description)

3: Channel In itia lization

4: M APIM (LO CATIO N UPDATING REQ UEST,CN Id, F low Id, Service Descriptor)RR_EST_CNF RR_EST_IND (LO CATIO N UPDATING REQ UEST)

RR_DATA_REQ (AUTHENTICATIO N REQ UEST)5: M APL3M (AUTHENTICATIO N REQ UEST)

RR_DATA_IND (AUTHENTICATIO N REQ UEST)

RR_DATA_REQ (AUTHENTICATIO N RESPO NSE)6: M APL3M (AUTHENTICATIO N RESPO NSE)

RR_DATA_IND (AUTHENTICATIO N RESPO NSE)

RR_SYNC_REQ (ciph.)

RR_SYNC_IND (Cause = C iphering S tarted) RR_SYNC_CNF (ciph.)

RR_DATA_REQ (LO CATIO N UPDATING ACCEPT(TM SI))9: M APL3M (LO CATIO N UPDATING ACCEPT(TM SI))

RR_DATA_IND (LO CATIO N UPDATING ACCEPT(TM SI))

RR_DATA_REQ (TM SI REALLO CATIO N CO M PLETE)10: M APL3M (TM SI REALLO CATIO N CO M PLETE)

RR_DATA_IND (TM SI REALLO CATIO N CO M PLETE)

RR_REL_REQ

RR_REL_IND(Cause = Network Request)

11: Release O rder

12: Release O rder

7: Security M ode Com m and

8: Encryption S tarts on Action T im e

MSCM / MM

MSRRC / L2 / L2

BSRRC / L2 / L2

MSCCM / MM

A ir In terface

23

Example Mobile Originated Call Setup Message Flow Example Mobile Originated Call Setup Message Flow

MSCM / MM

MSRRC / L2 / L2

BSRRC / L2 / L2

MSCCM / MM

A ir In terface

RR_ DATA_REQ (SETUP)9: MAPL3M (SETUP)

RR_DATA_IND (SETUP)

RR_DATA_REQ (CALL PROCEED)10: MAPL3M (CALL PROCEED)

RR_ DATA_IND (CALL PROCEED)

RR_SYNC_REQ (resource assigned)

RR_ SYNC_IND (Cause = resource assigned) RR_SYNC_CNF (resource assigned)

RR_DATA_REQ (ALERT)13: MAPL3M(ALERT)

RR_ DATA_IND (ALERT)RR_DATA_REQ (CONNECT)

14: MAPL3M(CONNECT)RR_ DATA_IND (CONNECT)

RR_ DATA_REQ (CONNECT ACK)15: MAPL3M(CONNECT ACK)

RR_DATA_IND (CONNECT ACK)

16: User Data Flow

RR_EST_REQ (CM SERVICE REQUEST, Establishment Cause = Originating Speech Call)

1: MAPCRM (Establishment Cause = Originating Speech Call,

Initial MS Id, Initial MS Capability)

2: ECAM (Initial MS Id, Channel Description)

4: MAPIM (CM SERVICE REQUEST,CN Id, Flow Id, Service Descriptor)RR_EST_CNF RR_EST_IND (CM SERVICE REQUEST)

RR_DATA_REQ (AUTHENTICATION REQUEST)5: MAPL3M (AUTHENTICATION REQUEST)

RR_DATA_IND (AUTHENTICATION REQUEST)

RR_DATA_REQ (AUTHENTICATION RESPONSE)6: MAPL3M (AUTHENTICATION RESPONSE)

RR_DATA_IND (AUTHENTICATION RESPONSE)

RR_SYNC_REQ (ciph.)

RR_SYNC_IND (Cause = Ciphering Started) RR_SYNC_CNF (ciph.)

11: Service Connect Message (GSM SO, SCR, NN-SCR)

12: Service Connect Completion Message

3: Channel Initialization

7: Security Mode Command

8: Encryption Starts on Action Time

24

Example Mobile Terminated Call Setup Message Flow Example Mobile Terminated Call Setup Message Flow

MSCM / MM

MSRRC / L2 / L2

BSRRC / L2 / L2

MSCCM / MM

A ir In terface

17: User Data Flow

RR_NOTIFICATION_REQ (Mobile Id , Reason)1: General Page Message (CN Id, Mobile Id , Reason)

RR_DATA_REQ (SETUP)10: MAPL3M (SETUP)

RR_ DATA_IND (SETUP)

RR_ DATA_REQ (CALL CONFIRM)11: MAPL3M (CALL CONFIRM)

RR_DATA_IND (CALL CONFIRM)

RR_ DATA_REQ (ALERT)14: MAPL3M (ALERT)

RR_DATA_IND (ALERT)RR_ DATA_REQ (CONNECT)

15: MAPL3M (CONNECT)RR_DATA_IND (CONNECT)

RR_DATA_REQ (CONNECT ACK)16: MAPL3M (CONNECT ACK)

RR_ DATA_IND (CONNECT ACK)

2: MAPCRM (Establishment Cause = Terminating Speech Call,

Initial MS Id, Initial MS Capability)

3: ECAM (Initial MS Id, Channel Description)

5: MAPIM (PAGING RESPONSE, CN Id, Flow Id, Service Descriptor)

RR_NOTIFICATION_IND(CN Id, Mobile Id, Reason)

RR_EST_IND (PAGING RESPONSE)

RR_DATA_REQ (AUTHENTICATION REQUEST)6: MAPL3M (AUTHENTICATION REQUEST)

RR_DATA_IND (AUTHENTICATION REQUEST)

RR_DATA_REQ (AUTHENTICATION RESPONSE)7: MAPL3M (AUTHENTICATION RESPONSE)

RR_DATA_IND (AUTHENTICATION RESPONSE)

RR_SYNC_REQ (ciph.)

RR_SYNC_IND (Cause = Ciphering Started) RR_SYNC_CNF (ciph.)

RR_SYNC_REQ (resource assigned)

RR_ SYNC_IND (Cause = resource assigned) RR_SYNC_CNF (resource assigned)

12: Service Connect Message (GSM SO, SCR, NN-SCR)

13: Service Connect Completion Message

4: Channel Initialization

8: Security Mode Command

9: Encryption Starts on Action Time

RR_EST_REQ (PAGING RESPONSE, Establishment Cause = Terminating Speech Call)

RR_EST_CNF

25

Example Mobile Originated Call Release Message Flow Example Mobile Originated Call Release Message Flow

MSCM / MM

MSRRC / L2 / L2

BSRRC / L2 / L2

MSCCM / MM

A ir In terface

1: User Data Flow

RR_SYNC_REQ (resource assigned)

RR_ SYNC_IND (Cause = resource assigned) RR_SYNC_CNF (resource assigned)

5: Service Connect Message (GSM SO, SCR, NN-SCR)

6: Service Connect Completion Message

RR_ DATA_REQ (DISCONNECT)2: MAPL3M (DISCONNECT)

RR_DATA_IND (DISCONNECT)

RR_DATA_REQ (RELEASE)3: MAPL3M (RELEASE)

RR_ DATA_IND (RELEASE)

RR_ DATA_REQ (RELEASE COMPLETE)4: MAPL3M (RELEASE COMPLETE)

RR_DATA_IND (RELEASE COMPLETE)

RR_REL_REQ

RR_REL_IND(Cause = Network Request)

7: Release Order

8: Release Order

26

Message Usage in MC-MAPMessage Usage in MC-MAP

• The MC-MAP messaging consists of the following:– RRC Layer Messages:

> some cdma2000 messages used as they are> some cdma2000 messages used with modifications> new RRC messages defined for MC-MAP

– Some cdma2000 messages (corr. to MM & CM functionality) are not used in MC-MAP

– MM & CM Layer messages: GSM-MAP messages defined in 3GPP.

• Similar classification for cdma2000 “Orders” and “Information Records”

27

Examples of cdma2000 Messages used as they are in MC-MAPExamples of cdma2000 Messages used as they are in MC-MAP

• Pilot Strength Measurement Message (r-dsch)• Outer Loop Report Message (r-dsch)• Supplemental Channel Request Message (r-dsch)• Extended CDMA Channel List Message (f-csch)• Universal Neighbor List Message (f-csch)• Service Connect Message (f-dsch)• Power Control Message (f-dsch)• Resource Allocation Message (f-dsch)

28

Examples of cdma2000 Messages used with Modifications in Examples of cdma2000 Messages used with Modifications in MC-MAPMC-MAP

• Candidate Frequency Search Report Message (new SEARCH_MODE for GSM channel search)

• Systems Parameters Message (ignore SID, NID, REG_ZONE)

• Security Mode Command Message (new fields CN_ENC_DOMAIN, CONC_EXT_SEQ_H)

• MC-RR Parameters Message (added R_TMSI related fields)

• Universal Handoff Direction Message (ignore PACKET_ZONE_ID, etc.)

• Call Assignment Message (ignore RESPOND_IND, TAG, etc.; new field MC_MAP_BLOB to carry NAS info)

29

Examples of cdma2000 Messages not used in MC-MAPExamples of cdma2000 Messages not used in MC-MAP

• Registration Message (MM)• Origination Message (replaced by new RRC conn req

msg)• Page Response Message (replaced by new RRC

conn req msg)• Flash With Information Message (CM)• Enhanced Origination Message (CM)• Authentication Challenge Message (MM)• ANSI-41 System Parameters Message (CM)• Alert With Information Message (CM)• TMSI Assignment Message (MM)

30

New Messages defined in MC-MAP New Messages defined in MC-MAP (MS side)(MS side)

• r-csch:– MC-MAP Initial L3 Message– MC-MAP L3 Message– MC-MAP RRC Connection Request Message– Radio TMSI Assignment Completion Message

• r-dsch:– MC-MAP L3 Message– Radio TMSI Assignment Completion Message

31

New Messages defined in MC-MAP New Messages defined in MC-MAP (BS side)(BS side)

• f-csch:– MC-MAP Sync Channel Message

> Core network identification is sent encapsulated in CN_ID records.> CDMA MC-specific parameters may be read from Sync Channel

Message.

– MC-MAP System Information Message> sends core network identification and information encapsulated in

CN_INFO records.

– MC-MAP L3 Message– Radio TMSI Assignment Message

• f-dsch:– MC-MAP L3 Message– Radio TMSI Assignment Message

32

Examples of cdma2000 “Orders”usage in MC-MAPExamples of cdma2000 “Orders”usage in MC-MAP

• Used as they are:– Mobile Station Acknowledgement Order– Pilot Measurement Request Order

• Used with mods:– Mobile Station Reject Order (some “reasons” not

used)• Not Used:

– Connect Order (CM)– Registration Accepted Order (MM)

• No new orders defined for MC-MAP

33

Examples of cdma2000 “Information Records”usage in MC-MAPExamples of cdma2000 “Information Records”usage in MC-MAP

• Used as they are:– Multiplex Option Information– Non-Negotiable Service Configuration

• Used with mods:– Security Status (ignore AUTH_MODE)– Service Configuration (new field

CN_ENC_DOMAIN)• Not Used:

– Calling Party Number (CM)– Call Waiting Indicator (CM)

• No new information records defined for MC-MAP