ETSI TS V ( )

Transcription

1 TS V ( ) TECHNICAL SPECIFICATION Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; Mobile radio interface signalling layer 3; General Aspects (3GPP TS version Release 14)

2 1 TS V ( ) Reference RTS/TSGC ve00 Keywords GSM,LTE,UMTS 650 Route des Lucioles F Sophia Antipolis Cedex - FRANCE Tel.: Fax: Siret N NAF 742 C Association à but non lucratif enregistrée à la Sous-Préfecture de Grasse (06) N 7803/88 Important notice The present document can be downloaded from: The present document may be made available in electronic versions and/or in print. The content of any electronic and/or print versions of the present document shall not be modified without the prior written authorization of. In case of any existing or perceived difference in contents between such versions and/or in print, the only prevailing document is the print of the Portable Document Format (PDF) version kept on a specific network drive within Secretariat. Users of the present document should be aware that the document may be subject to revision or change of status. Information on the current status of this and other documents is available at If you find errors in the present document, please send your comment to one of the following services: Copyright Notification No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm except as authorized by written permission of. The content of the PDF version shall not be modified without the written authorization of. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute All rights reserved. DECT TM, PLUGTESTS TM, UMTS TM and the logo are Trade Marks of registered for the benefit of its Members. 3GPP TM and LTE are Trade Marks of registered for the benefit of its Members and of the 3GPP Organizational Partners. GSM and the GSM logo are Trade Marks registered and owned by the GSM Association.

3 2 TS V ( ) Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to. The information pertaining to these essential IPRs, if any, is publicly available for members and non-members, and can be found in SR : "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to in respect of standards", which is available from the Secretariat. Latest updates are available on the Web server ( Pursuant to the IPR Policy, no investigation, including IPR searches, has been carried out by. No guarantee can be given as to the existence of other IPRs not referenced in SR (or the updates on the Web server) which are, or may be, or may become, essential to the present document. Foreword The present document may refer to technical specifications or reports using their 3GPP identities, UMTS identities or GSM identities. These should be interpreted as being references to the corresponding deliverables. The cross reference between GSM, UMTS, 3GPP and identities can be found under Modal verbs terminology In the present document "shall", "shall not", "should", "should not", "may", "need not", "will", "will not", "can" and "cannot" are to be interpreted as described in clause 3.2 of the Drafting Rules (Verbal forms for the expression of provisions). "must" and "must not" are NOT allowed in deliverables except when used in direct citation.

4 3 TS V ( ) Contents Intellectual Property Rights... 2 Foreword... 2 Modal verbs terminology... 2 Foreword Scope References Definitions and abbreviations Definitions Abbreviations Introduction General Applicability of functional blocks Technique of description Service description Abstract service primitives Protocols and peer-to-peer communication Contents of layer 3 related Technical Specifications Structure of layer 3 functions Basic groups of functions Protocol architecture Services provided by signalling layer 3 at the MS side Registration services Service state diagram for MS not supporting GPRS service Service primitives MMR_REG_REQ MMR_REG_CNF Void MMR_NREG_REQ MMR_NREG_IND Registration Services for CTS-Services MMR_CTS _ATTACH_REQ MMR_CTS _ATTACH_CNF MMR_CTS _ATTACH_REJ MMR_CTS _DETACH_IND MMR_CTS _ENROLL_REQ MMR_CTS _ENROLL_CNF MMR_CTS _ENROLL_REJ MMR_CTS _DE_ENROLL_IND Call Control services Service state diagram Service primitives MNCC_SETUP_REQ MNCC_SETUP_IND MNCC_SETUP_RES MNCC_SETUP_CNF MNCC_SETUP_COMPL_REQ MNCC_SETUP_COMPL_IND MNCC_REJ_REQ MNCC_REJ_IND MNCC_CALL_CONF_REQ MNCC_CALL_PROC_IND MNCC_PROGRESS_IND... 38

5 4 TS V ( ) MNCC_ALERT_REQ MNCC_ALERT_IND MNCC_NOTIFY_REQ MNCC_NOTIFY_IND MNCC_DISC_REQ MNCC_DISC_IND MNCC_REL_REQ MNCC_REL_IND MNCC_REL_CNF MNCC_FACILITY_REQ MNCC_FACILITY_IND MNCC_START_DTMF_REQ MNCC_START_DTMF_CNF MNCC_STOP_DTMF_REQ MNCC_STOP_DTMF_CNF MNCC_MODIFY_REQ MNCC_MODIFY_IND MNCC_MODIFY_RES MNCC_MODIFY_CNF MNCC_SYNC_IND Call independent Supplementary Services Support Service state diagram Service primitives MNSS_BEGIN_REQ MNSS_BEGIN_IND MNSS_FACILITY_REQ MNSS_FACILITY_IND MNSS_END_REQ MNSS_END_IND Short Message Services Support Session Management Services for GPRS-Services Session Management Services for SMREG-SAP SMREG-PDP-ACTIVATE-REQ SMREG-PDP-ACTIVATE-CNF SMREG-PDP-ACTIVATE-REJ SMREG-PDP-ACTIVATE-IND SMREG-PDP-DEACTIVATE-REQ SMREG-PDP-DEACTIVATE-CNF SMREG-PDP-DEACTIVATE-IND SMREG-PDP-MODIFY-IND Void Void Void Void Void SMREG-PDP-ACTIVATE-REJ-RSP SMREG-PDP-ACTIVATE-SEC-REQ SMREG-PDP-ACTIVATE-SEC-CNF SMREG-PDP-ACTIVATE-SEC-REJ SMREG-PDP-MODIFY-REQ SMREG-PDP-MODIFY-CNF SMREG-PDP-MODIFY-REJ SMREG-MBMS-ACTIVATE-REQ SMREG-MBMS-ACTIVATE-CNF SMREG-MBMS-ACTIVATE-REJ SMREG-MBMS-ACTIVATE-REJ-RSP SMREG-MBMS-ACTIVATE-IND Session Management Services for SNSM-SAP (GSM only) Session Management Services for RABMSM-SAP (UMTS only) RABMSM-ACTIVATE-IND RABMSM-ACTIVATE-RSP RABMSM-DEACTIVATE-IND... 47

6 5 TS V ( ) RABMSM-DEACTIVATE-RSP RABMSM-DEACTIVATE-REQ RABMSM-MODIFY-IND RABMSM-MODIFY-RSP RABMSM-STATUS-REQ Registration Services for GPRS-Services Registration Services for GMMREG-SAP GMMREG-ATTACH-REQ GMMREG-ATTACH-CNF GMMREG-ATTACH-REJ GMMREG-DETACH-REQ GMMREG-DETACH-CNF GMMREG-DETACH-IND Services provided to SNDCP entities by GPRS Logical Link Control services Service state diagram for QoS1-SAP, QoS2-SAP, QoS3-SAP and QoS4-SAP Service primitives for QoS1-SAP, QoS2-SAP, QoS3-SAP and QoS4-SAP LL-ESTABLISH-REQ LL-ESTABLISH-CNF LL-ESTABLISH-IND LL-ESTABLISH-RSP LL-RELEASE-REQ LL-RELEASE-CNF LL-RELEASE-IND LL-XID-REQ LL-XID-IND LL-XID-RSP LL-XID-CNF LL-DATA-REQ LL-DATA-CNF LL-DATA-IND LL-UNITDATA-REQ LL-UNITDATA-IND LL-STATUS-IND Location services at the type A LMU side Service state diagram Service primitives MNLCS_BEGIN_REQ MNLCS_BEGIN_IND MNLCS_FACILITY_REQ MNLCS_FACILITY_IND MNLCS_END_REQ MNLCS_END_IND Services provided by signalling layer 3 on the Network side Call control services Service state diagram Service primitives MNCC_SETUP_REQ MNCC_SETUP_IND MNCC_SETUP_RSP MNCC_SETUP_CNF MNCC_SETUP_COMPL_REQ MNCC_SETUP_COMPL_IND MNCC_REJ_REQ MNCC_REJ_IND MNCC_CALL_CONF_IND MNCC_CALL_PROC_REQ MNCC_PROGRESS_REQ MNCC_ALERT_REQ MNCC_ALERT_IND MNCC_NOTIFY_REQ MNCC_NOTIFY_IND... 58

7 6 TS V ( ) MNCC_DISC_REQ MNCC_DISC_IND MNCC_REL_REQ MNCC_REL_IND MNCC_REL_CNF MNCC_FACILITY_REQ MNCC_FACILITY_IND MNCC_START_DTMF_IND MNCC_START_DTMF_RSP MNCC_STOP_DTMF_IND MNCC_STOP_DTMF_RSP MNCC_MODIFY_REQ MNCC_MODIFY_IND MNCC_MODIFY_RES MNCC_MODIFY_CNF Call independent Supplementary Services Support Service state diagram Service primitives MNSS_BEGIN_REQ MNSS_BEGIN_IND MNSS_FACILITY_REQ MNSS_FACILITY_IND MNSS_END_REQ MNSS_END_IND Short Message Services Support Services provided to SNDCP and SMS entities by GPRS Logical Link Control services Service state diagram for QoS1-SAP, QoS2-SAP, QoS3-SAP and QoS4-SAP Service primitives for QoS1-SAP, QoS2-SAP, QoS3-SAP and QoS4-SAP LL-ESTABLISH-REQ LL-ESTABLISH-CNF LL-ESTABLISH-IND LL-ESTABLISH-RSP LL-RELEASE-REQ LL-RELEASE-CNF LL-RELEASE-IND LL-XID-REQ LL-XID-IND LL-XID-RSP LL-XID-CNF LL-DATA-REQ LL-DATASENT-IND LL-DATA-CNF LL-DATA-IND LL-UNITDATA-REQ LL-UNITDATA-IND LL-STATUS-IND Session Management Services for GPRS and MBMS Session Management Services for SMREG-SAP SMREG-PDP-ACTIVATE-REQ SMREG-PDP-ACTIVATE-REJ SMREG-PDP-DEACTIVATE-REQ SMREG-PDP-DEACTIVATE-CNF SMREG-PDP-MODIFY-REQ SMREG-PDP-MODIFY-CNF SMREG-PDP-MODIFY-REJ SMREG-MBMS-ACTIVATE-REQ SMREG-MBMS-ACTIVATE-REJ Session Management Services for SNSM-SAP Location services at the Network side Service state diagram Service primitives MNLCS_BEGIN_REQ... 66

8 7 TS V ( ) MNLCS_BEGIN_IND MNLCS_FACILITY_REQ MNLCS_FACILITY_IND MNLCS_END_REQ MNLCS_END_IND Services assumed from signalling layers 1 and Priority Unacknowledged information transfer Acknowledged information transfer Random access Channel management and measurements Interlayer service interfaces on the MS side Services provided by the Radio Resource Management entity Service state diagram Service primitives RR_EST_REQ RR_EST_IND RR_EST_CNF RR_REL_IND RR_SYNC_IND a Void b Void RR_DATA_REQ RR_DATA_IND a Void RR_UNIT_DATA_IND RR_ABORT_REQ RR_ABORT_IND Services provided by the Radio Resource Management entity for CTS CTS_RR_ALIVE_CHECK_IND Services provided by the Mobility Management entity Service state diagram Service primitives MMXX_EST_REQ MMXX_EST_IND MMXX_EST_CNF MMXX_REL_REQ MMXX_REL_IND MMXX_DATA_REQ MMXX_DATA_IND MMXX_UNIT_DATA_REQ MMXX_UNIT_DATA_IND MMCC_SYNC_IND MMXX_REEST_REQ MMXX_REEST_CNF MMXX_ERR_IND MMXX_PROMPT_IND MMXX_PROMPT_REJ Services provided by radio resource management entity for GPRS services Service primitives for GRR-SAP (GSM only) Service primitives for GMMRR-SAP (GSM only) GMMRR-ASSIGN-REQ GMMRR-PAGE-IND Service primitives for RABMAS-SAP (UMTS only) RABMAS-RAB-ESTABLISH-IND RABMAS-RAB-ESTABLISH-RES RABMAS-RAB-ESTABLISH-REJ RABMAS-RAB-RELEASE-IND RABMAS-RAB-RELEASE-RES RABMAS-STATUS-IND... 77

9 8 TS V ( ) Service primitives for GMMAS-SAP (UMTS only) GMMAS-SECURITY-IND GMMAS-SECURITY-RES GMMAS-ESTABLISH-REQ GMMAS-ESTABLISH-CNF GMMAS-ESTABLISH-REJ GMMAS- RELEASE-REQ GMMAS- RELEASE-IND GMMAS- DATA-REQ GMMAS- DATA-IND GMMAS-PAGE-IND GMMAS-STATUS-IND Services provided by the LLC entity for GPRS services (GSM only) Service primitives for LLGMM-SAP LLGMM-ASSIGN-REQ LLGMM-TRIGGER-REQ Void LLGMM-SUSPEND-REQ Void Void LLGMM-WINDOW-CNF LL-UNITDATA-REQ LL-UNITDATA-IND LLGMM-STATUS-IND Service primitives for LLSMS-SAP LL-UNITDATA-REQ LL-UNITDATA-IND Services provided by the GMM for GPRS services Service primitives for GMMSM-SAP GMMSM-ESTABLISH-REQ GMMSM-ESTABLISH-CNF GMMSM-ESTABLISH-REJ GMMSM-RELEASE-IND GMMSM-UNITDATA-REQ GMMSM-UNITDATA-IND Void Service primitives for GMMSMS-SAP GMMSMS-REG-STATE-REQ GMMSM- REG-STATE -RSP Service primitives for PMMSMS-SAP PMMSMS_EST _REQ PMMSMS_EST _CNF PMMSMS_ERROR_IND PMMSMS_UNITDATA_REQ PMMSMS_UNITDATA_IND Service primitives for GMMRABM-SAP (UMTS only) GMMRABM-REESTABLISH-REQ GMMRABM-REESTABLISH-RSP GMMRABM-REESTABLISH-REJ Service primitives for GMMSS-SAP GMMSS-ESTABLISH-REQ GMMSS-ESTABLISH-CNF GMMSS-ESTABLISH-REJ GMMSS-RELEASE-IND GMMSS-UNITDATA-REQ GMMSS-UNITDATA-IND Service primitives for GMMSS2-SAP GMMSS2-REG-STATE-REQ GMM SS2- REG-STATE -RSP Interlayer service interfaces on the Network side Services provided by the Radio Resource Management entity... 83

10 9 TS V ( ) Service state diagram Service primitives RR_EST_REQ RR_EST_IND RR_EST_CNF RR_REL_REQ RR_REL_IND RR_SYNC_REQ RR_SYNC_CNF RR_DATA_REQ RR_DATA_IND RR_UNIT_DATA_REQ RR_UNIT_DATA_IND RR_ABORT_REQ RR_ABORT_IND Services provided by the Mobility Management entity Service state diagram Service primitives MMXX_EST_REQ MMXX_EST_IND MMXX_EST_CNF MMXX_REL_REQ MMXX_REL_IND MMXX_DATA_REQ MMXX_DATA_IND MMXX_UNIT_DATA_REQ MMXX_UNIT_DATA_IND MMCC_SYNC_REQ MMCC_SYNC_CNF Services provided by radio resource management entity for GPRS services Service primitives for GRR-SAP Service primitives for GMMRR-SAP GMMRR-PAGE-REQ Services provided by the LLC entity for GPRS services Service primitives for LLGMM-SAP LLGMM-ASSIGN-REQ Void LLGMM-SUSPEND-REQ LLGMM-RESUME-REQ Void Void LLGMM-PAGE-IND LLGMM-PAGE-RESP-IND LL-UNITDATA-REQ LL-UNITDATA-IND LLGMM-STATUS-IND Service primitives for LLSMS-SAP LL-UNITDATA-REQ LL-UNITDATA-IND Services provided by the GMM for GPRS services Service primitives for GMMSM-SAP GMMSM-RELEASE-IND GMMSM-UNITDATA-REQ GMMSM-UNITDATA-IND Service primitives for PMMSMS-SAP PMMSMS_REL_REQ PMMSMS_ERROR_IND PMMSMS_UNITDATA_REQ PMMSMS_UNITDATA_IND Service primitives for GMMSS-SAP GMMSS-RELEASE-IND GMMSS-UNITDATA-REQ... 91

11 10 TS V ( ) GMMSS-UNITDATA-IND Services provided by the Radio Resource Management entity for CTS on the fixed part Service primitives RR_ CTS_ALIVE_CHECK_REQ RR_ CTS_ALIVE_CHECK_IND RR_ CTS_HUNTING_REQ RR_ CTS_GROUP_ALERTING_REQ L3 Messages General Messages Octets Integer Binary complement binary Spare parts Standard L3 messages Components of a standard L3 message Format of standard information elements Information element type and value part Length indicator Information element identifier Categories of IEs; order of occurrence of IEI, LI, and value part Description methods for IE structure Tables Compact notation Imperative part of a standard L3 message Standard L3 message header Protocol discriminator Skip indicator Transaction identifier Sub-protocol discriminator EPS bearer identity Security header type a Procedure transaction identity Message type octet Message type octet (when accessing Release 98 and older networks only) Message type octet (when accessing Release 99 and newer networks) Sequenced message transfer operation Variables and sequence numbers Send state variable V(SD) Send sequence number N(SD) Procedures for the initiation, transfer execution and termination of the sequenced message transfer operation Initiation Transfer Execution Termination Standard information elements of the imperative part Non-imperative part of a standard L3 message Presence requirements of information elements Description of standard L3 messages Non standard L3 messages Case A: BCCH and AGCH/PCH messages L2 Pseudo Length octet Rest Octets Description of a modified standard L3 message Case B: SACCH / SDCCH / FACCH messages sent in unacknowledged mode The first octet The rest of the message Design guidelines for non standard parts General Handling of superfluous information

12 11 TS V ( ) Information elements that are unnecessary in a message Other syntactic errors Annex A (informative): Annex B (informative): MN-Services arrow diagram Description of CSN B.1 The Basic Rules B.1.1 Core Rules B Rule B1: Bits B Rule B2: Null String B Rule B3: Concatenation B Rule B4: Choice B Rule B5: Naming B Rule B6: Definition B.1.2 Spare parts B Rule B7: Spare bits B Rule B8: Padding bits B.1.3 Predefined sets B.1.4 Labelling Parts B Rule A1: Labels B.1.5 Goodies B Rule G1: Comments B.2 Advanced rules B.2.1 Rule A2: Exponent notation Annex C (informative): Annex D (informative): GPRS-Services sequence diagram Change history History

13 12 TS V ( ) Foreword This Technical Specification (TS) has been produced by 3rd Generation Partnership Project (3GPP). The present document defines the architecture of layer 3 and its sublayers on the GSM Um interface, i.e. the interface between Mobile Station and network within the 3GPP system. The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: Version x.y.z where: x the first digit: 1 presented to TSG for information; 2 presented to TSG for approval; 3 or greater indicates TSG approved document under change control. y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the document.

14 13 TS V ( ) 1 Scope The present document defines the principal architecture of layer 3 and its sublayers on the GSM Um interface, i.e. the interface between Mobile Station (MS) and network; for the CM sublayer, the description is restricted to paradigmatic examples, call control, supplementary services, and short message services for non-gprs services. It also defines the basic message format and error handling applied by the layer 3 protocols. For CTS services, the present document defines the principal architecture of layer 3 on the GSM Um* interface, i.e. the interface between a CTS capable Mobile Station (CTS-MS) and a Fixed Part (FP). The corresponding protocols are defined in other Technical Specifications, see subclause For non-gprs services the communication between sublayers and adjacent layers and the services provided by the sublayers are distributed by use of abstract service primitives. But only externally observable behaviour resulting from the description is normatively prescribed by the present document. For GPRS services in addition the local information transfer and stimuli sent between sublayers is informatively included within Annex C of in the present document. This document also defines the principal architecture of the EPS NAS layer 3 protocol and its sublayers, including the message format applied by layer 3. In the present document MS is also used as a synonym for UE. Descriptions in clauses 3 to 10 are not maintained actively. 2 References The following documents contain provisions which, through reference in this text, constitute provisions of the present document. - References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. - For a specific reference, subsequent revisions do not apply. - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document. [1] GSM 01.02(R97): "Digital cellular telecommunications system (Phase 2+); General description of a GSM Public Land Mobile Network (PLMN)". [1a] 3GPP TR : "Vocabulary for 3GPP Specifications". [2] 3GPP TS : "General UMTS Architecture". [3] 3GPP TS : "Mobile Station - Base Station System (MS - BSS) interface; General aspects and principles". [3a] 3GPP TS : "General Packet Radio Service (GPRS) description; Stage 2". [3b] [3c] GSM 03.56(R98): "Digital cellular telecommunications system (Phase 2+); GSM Cordless Telephony System (CTS), Phase 1; CTS Architecture Description; Stage 2". 3GPP TS : "Functional stage 2 description of location services". [4] 3GPP TS : "Data Link (DL) layer; General aspects". [5] 3GPP TS : "Mobile Station - Base Station System (MS - BSS) interface; Data Link (DL) layer specification".

15 14 TS V ( ) [5a] 3GPP TS : "Individual equipment type requirements and interworking; Special conformance testing functions". [6] 3GPP TS : "Mobile radio interface Layer 3 specification Core Network Protocols-Stage 3". [6a] 3GPP TS : "Mobile radio interface Layer 3 specification Core Network Protocols Stage 2 (structured procedures)". [6b] 3GPP TS : "Mobile radio interface layer 3 specification; Radio Resource Control Protocol". [7] 3GPP TS : "Mobile radio interface Layer 3; Supplementary services specification; General aspects". [8] 3GPP TS : "Point-to-Point (PP) Short Message Service (SMS) support on mobile radio interface". [8a] 3GPP TS : "Location Services (LCS); Mobile radio interface layer 3 LCS specification". [9] 3GPP TS : "Mobile radio Layer 3 supplementary services specification; Formats and coding". [10] 3GPP TS : "Line identification supplementary services; Stage 3". [10a] 3GPP TS : "General Packet Radio Services (GPRS); Mobile Station (MS) - Base Station System (BSS) interface; Radio Link Control/Medium Access Control (RLC/MAC) protocol". [10b] 3GPP TS : "GSM Cordless Telephony System (CTS), phase 1; CTS radio interface Layer 3 specification". [11] 3GPP TS : "Call Forwarding (CF) supplementary services - Stage 3". [11a] 3GPP TS : "General Packet Radio Service (GPRS); Mobile Station - Serving GPRS Support Node (MS-SGSN) Logical Link Control (LLC) layer specification". [12] 3GPP TS : "Call Waiting (CW) and Call Hold (HOLD) supplementary services; Stage 3". [12a] 3GPP TS : "General Packet Radio Service (GPRS); Mobile Station (MS) - Serving GPRS Support Node (SGSN); Subnetwork Dependent Convergence Protocol (SNDCP)". [13] 3GPP TS : "MultiParty (MPTY) supplementary services; Stage 3". [14] 3GPP TS : "Closed User Group (CUG) supplementary services; Stage 3". [15] 3GPP TS : "Advice of Charge (AoC) supplementary services; Stage 3". [16] 3GPP TS : "Call Barring (CB) supplementary services; Stage 3". [17] 3GPP TS : "Unstructured Supplementary Service Data (USSD) - Stage 3". [17a] 3GPP TS : "Terminal logical test interface; Special conformance testing functions". [18] ITU-T Recommendation X.200: "Information technology - Open Systems Interconnection - Basic Reference Model: The basic model". [19] 3GPP TS : "Group Call Control (GCC) Protocol". [20] 3GPP TS : "UMTS Access Stratum Services and Functions". [21] 3GPP TS : "Location Services (LCS); Supplementary service operations Stage 3". [22] 3GPP TS : "Network Sharing; Architecture and functional description". [23] 3GPP TS : "UTRAN Iu interface RANAP signalling". [24] 3GPP TS : "Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC) protocol specification".

16 15 TS V ( ) [25] 3GPP TS : "Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3". [26] 3GPP TS : "Evolved Universal Terrestrial Radio Access (E-UTRA); Special conformance testing function for User Equipment (UE)". [27] 3GPP TS : "Single Radio Voice Call Continuity (SRVCC); Stage 2". 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in 3GPP TR [1] apply. 3.2 Abbreviations For the purposes of the present document, the abbreviations defined in 3GPP TR [1a] and the following apply: GMM MNS N-PDU SM UDT CTS LCS MOCN GPRS Mobility Management Mobile Network Signalling Network-Protocol Data Unit Session Management User Data Transfer Cordless Telephony System LoCation Services Multi-Operator Core Network 4 Introduction 4.1 General Four models are defined for Layer 3, one model for non-gprs services, one for GPRS services supporting Class C MSs only, one model for GPRS-services supporting Class A and Class B MSs and one model for EPS services. (The third model is a combination of the first two models listed). In the present document GPRS services and EPS services will be used as synonyms. The layer 3 for non-gprs services provides the functions necessary: - for Radio Resource (RR) management; - for Mobility Management (MM); and - for the Connection Management (CM) functions, i.e. functions for the control, provision, and support of services offered by the network; among which there are, e.g.: - the functions to establish, maintain and terminate circuit-switched connections across a GSM PLMN and other networks to which the GSM PLMN is connected; - supporting functions for supplementary services control; - supporting functions for short messages service control; - supporting functions for location services control (only for a type A LMU). The layer 3 for non-gprs services is composed of three sublayers comprising: - the Radio Resource Management (RR) functions; - the Mobility Management (MM) functions; and

17 16 TS V ( ) - the Connection Management (CM) functions. When CTS services are added to non-gprs services, the following functions are added: - CTS Radio Resource Management (CTS-RR) functions to RR; and - CTS Mobility Management (CTS-MM) functions to MM. The layer 3 for GPRS services is composed of four sublayers comprising: - the Radio Resource Management (RR) functions; - the Mobility Management (GMM); - for the Logical Link Control (LLC); - the Connection Management (CM) functions. The Connection Management (CM) sublayer is composed of functional blocks for: - Call Control (CC) for non-gprs services; - Short Message Service Support (SMS) for non-gprs services; - GPRS Short Message Service Support (GSMS) (for GPRS services supporting Class A, B and C MSs); - Session Management (SM) (for GPRS services supporting Class A, B and C MSs); - Supplementary Services Support (SS) for non-gprs services; - Group Call Control for non-gprs services; - Broadcast Call Control (BCC) for non-gprs services; - Connection Management of Packet Data on Signalling channels for non-gprs services; - Location Services support (LCS) for non-gprs services (only for a type A LMU). Within the context of LCS, for GSM LCS, the services defined for an MS are equally applicable to a type A LMU, unless otherwise stated. However, services defined specifically for a type A LMU are not applicable to an MS. The following is a list of services essential for a type A LMU. The layer 3 for non-gprs services provides the functions necessary: - for Radio Resource (RR) management; - for Mobility Management (MM); and - supporting functions for location service control. The layer 3 for non-gprs services is composed of three sublayers comprising: - the Radio Resource Management (RR) functions; - the Mobility Management (MM) functions; and - the Connection Management (CM) functions. The Connection Management (CM) sublayer is composed of a functional block for: - location services support (LCS) for non-gprs services. The present document does not consider the distribution of signalling functions among the different network equipments. The signalling functions are described between two systems which represent the MS side and the network side of the radio interface of layer 3. Only the functions in the network for signalling communication with one MS is considered.

18 17 TS V ( ) For GPRS services, in addition to the signalling functions also the user data transfer is included in the present document. The layer 3 for EPS services is composed of three sublayers comprising: - the EPS Radio Resource Management (RR) functions; - the EPS Mobility Management (EMM) functions; and - the Connection Management (CM) functions. The Connection Management (CM) sublayer is composed of a functional block for: - the EPS Session Management (ESM) functions. 4.2 Applicability of functional blocks Not for all functional blocks listed in subclause 4.1, support in the MS or in the network is mandatory: - Support of Group Call Control is optional in the MS and in the network. - Support of Broadcast Call Control is optional in the MS and in the network. - Connection Management of Packet Data on Signalling channels. is optional in the MS and in the network. - Support of GPRS services is optional in the MS and in the network. - Support of CTS services is optional in the MS. CTS services are not applicable to the network. - Support of LCS services is optional in the MS and in the network, but not optional in LMU. Further conditions and constraints are defined in other Technical Specifications. 4.3 Technique of description Layer 3 and its sub-layers are specified by: - their service specification, see subclause 4.3.1; - their protocol specification, see subclause 4.3.3; - the specification of functions, see clause 5. Descriptions in clauses 3 to 10 are not maintained actively Service description The services of signalling layer 3 and its sublayers are described in terms of: - services provided to upper (sub-)layers at the service access points; - services assumed from lower (sub-)layers at the service access points. Layer 3 and its supporting lower layers provide the Mobile Network Signalling (MNS) Service and User Data Transfer (UDT) Service (for GPRS services only) to the upper layers. The service provided/assumed at the service access points are described by means of abstract service primitives and parameters as recommended in ITU-T Recommendation X.200 [18] Abstract service primitives The abstract service primitives consist of requests, responses, indications and confirmations. The general syntax of a primitive is specified in 3GPP TR [1a].

19 18 TS V ( ) Protocols and peer-to-peer communication By use of the services provided by lower (sub-)layers, peer entities in a (sub-)layer in the MS and the network exchange information. Exchange of information between two peer entities is performed according to the corresponding (sub-)layer protocols. A protocol is a set of rules and formats by which the information (control information and user data) is exchanged between the two peers. The information is exchanged by use of messages which are defined in the protocol. (Therefore, the messages are also called Protocol Data Units, PDUs). There are several protocols of the RR sublayer, one protocol of the LLC sublayer, three protocols of the MM sublayer, and several protocols of the CM sublayer. For each functional block of the CM sublayer as defined in subclause 4.1 there is one protocol. The CM protocols are specified in the Technical Specifications identified in subclause In the model used in the present document, there are: 1) for non-gprs services: - one RR sub-layer entity in the MS and one RR sub-layer entity in the network; - one MM sub-layer entity in the MS and one MM sub-layer entity in the network; - for each functional block of the CM sublayer as defined in subclause 4.1 which is supported in the MS (in the network), there are, depending on the protocol, one or more entities in the MS (in the network). Two different entities of the same functional block in the MS (in the network) are called parallel entities. The entities of the same functional block in the MS correspond in a one-to-one relation to the entities of the functional block in the network. The corresponding entities are called peer entities; 2) for CTS services (in addition to non-gprs services): - one RR sub-layer entity in the MS and one in the CTS fixed part. These RR sub-layers include one CTS-RR sub-entity on each side; - one MM sub-layer entity in the MS and one in the CTS fixed part These MM sub-layers include one CTS- MM sub-entity on each side; - for each functional block of the CM sublayer as defined in subclause 4.1 which is supported in the MS (in the fixed part), there are, depending on the protocol, one or more entities in the MS (in the fixed part). Two different entities of the same functional block in the MS (in the fixed part) are called parallel entities. The entities of the same functional block in the MS correspond in a one-to-one relation to the entities of the functional block in the fixed part. The corresponding entities are called peer entities; 3) for GPRS services supporting Class C MSs: - one RR sublayer entity (RR) in the MS and one RR sublayer entity in the network; - six LLC sublayer entities (QoS1-QoS4, signalling, SMS) in the MS and six LLC sublayer entities in the network; - one MM sublayer entity (GMM) in the MS and one MM sublayer entity in the network (GMM); - one SM entity in the MS's CM sublayer and one SM sublayer entity in the network's CM sublayer; - one or more GSMS functional blocks in the CM sublayer if supported; 4) for non-gprs and GPRS services supporting Class A and Class B MSs: - two RR sublayer entities (RR) in the MS and two RR sublayer entities in the network; - six LLC sublayer entities (QoS1-QoS4, signalling, SMS) in the MS and six LLC sublayer entities in the network; - two MM sublayer entities (GMM + MM) in the MS and one or two MM sublayer entities in the network (GMM or MM); - one SM entity in the MS's CM sublayer and one SM entity in the network's CM sublayer;

20 19 TS V ( ) - for each functional block of the CM sublayer as defined in subclause 4.1 which is supported in the MS (in the network), there are, depending on the protocol, one or more entities in the MS (in the network). Two different entities of the same functional block in the MS (in the network) are called parallel entities. The entities of the same functional block in the MS correspond in a one-to-one relation to the entities of the functional block in the network. The corresponding entities are called peer entities; 5) for EPS services: - one RR entity in the MS and one RR entity in the network; - one EMM entity in the MS and one EMM entity in the network; - for each functional block of the CM sublayer as defined in subclause 4.1 which is supported in the MS (in the network), there are, depending on the protocol, one or more entities in the MS (in the network). Two different entities of the same functional block in the MS (in the network) are called parallel entities. The entities of the same functional block in the MS correspond in a one-to-one relation to the entities of the functional block in the network. The corresponding entities are called peer entities. As each sub-layer entity is specified by one and only one protocol, it is also called a protocol entity or protocol control entity. For GPRS-services supporting Class A and Class B MSs, the MM entities of the MM-sublayer are able to exchange information by means of GMM PDUs as well as MM PDU's. This means if a mobile is GPRS attached, non-gprs mobility management procedures may make use of GRPS mobility management messages. When two peer protocol entities exchange PDUs, a transaction is said to be established (or: to be active; or: to exist). It depends from the protocol when exactly a protocol entity considers the transaction to be active, normally this is the case: - from the moment when it has passed the first suitable message to lower (sub-) layers or received the first suitable message from its peer entity; - up to the moment when it has released the transaction Contents of layer 3 related Technical Specifications - The Radio Resource (RR) management protocol is defined in 3GPP TS [6b]; - the Mobility Management (MM) protocol is defined in 3GPP TS [6]; - the Session Management (SM) protocol is defined in 3GPP TS [6]; - the Call Control (CC) protocol is defined in 3GPP TS [6]; - the Supplementary Services (SS) protocol is defined in 3GPP TS [7], 3GPP TS 24.08x, 3GPP TS 24.09x, and 3GPP TS [21]; - the Short Message Service (SMS) protocol is defined in 3GPP TS [8]; - the Group Call Control (GCC) protocol is defined in 3GPP TS [19]; - the Logical Link Control (LLC) protocol is defined in 3GPP TS [11a]; - the GPRS Radio Resource (GRR) protocol is defined in 3GPP TS [10a] and 3GPP TS [6]; - the CTS Radio Resource (CTS-RR) sub-protocol is defined in 3GPP TS [10b]; - the CTS Mobility Management (CTS-MM) sub-protocol is defined in 3GPP TS [10b]; - the CTS additions to the Call Control (CC) protocol are defined in 3GPP TS [10b]; - the Location Services (LCS) protocol for a type A LMU is defined in 3GPP TS [3c] and 3GPP TS [8a]; - the EPS Radio Resource (RR) management protocol is defined in 3GPP TS [24];

21 20 TS V ( ) - the EPS Mobility Management (EMM) protocol is defined in 3GPP TS [25]; - the EPS Session Management (ESM) protocol is defined in 3GPP TS [25]. 5 Structure of layer 3 functions 5.1 Basic groups of functions Most functions of layer 3 and its sub-layers are described by the service specifications and protocol specifications of the (sub-)layers. These functions are in the model realized by protocol control entities, see subclause In addition, routing functions are contained in layer 3 which are related to the transport of messages, e.g. multiplexing and splitting. These routing functions are defined in the Radio Resource Management and Mobility Management sub-layers. 1) They have the task to pass the messages from upper (sub-)layers to lower (sub-)layers. 2) They also have the task to pass messages provided by lower (sub-layers) to the appropriate sub-layer and, if applicable, entity. The routing functions with task 2 make use of the protocol discriminator (PD) which is part of the message header. A CM sublayer protocol may also define a transaction identifier (TI), procedure transaction identity (PTI) or EPS bearer identity as a part of the message header. This is at least the case if there are parallel entities of the same functional block, see subclause If they are a part of a message, the TI, PTI, EPS bearer identity, or both PTI and EPS bearer identity are also used by the routing functions. - The MM-sublayer routing function passes the messages of the CM entities as well as of the MM, GMM and CTS-MM entities of its own sublayer to the service access point of RR, GRR, LLC or CTS-RR. Furthermore it multiplexes them in case of parallel transactions. - The routing function of Radio Resource Management distributes the messages to be sent according to their message type and protocol discriminator (PD), to the actual channel configuration, and, if applicable, to further information received from upper sub-layers to the appropriate service access point of layer 2 (identified by SAPI and logical channel). Paging messages received from the PPCH are always routed to GMM, while paging messages received from the PCH are distributed to GMM or MM based on the temporary identifier (TMSI or TLL). For EPS services, the Paging messages received from the PCH are always routed to EMM. - The messages provided at the different service access points of layer 2 are distributed by the RR sublayer routing function according to their protocol discriminator (PD). Messages with a PD equal to RR are passed to the RR entity of the own sublayer, all other messages are passed to the MM sublayer at the service access point RR- SAP. - The routing function of MM-sublayer passes Standard L3 messages according to the protocol discriminator (PD) and, if applicable, the transaction identifier (TI) or the PDP address towards the MM entity or towards the CM entities via the various MM-SAP's. GPRS L3 messages are routed to mobility management or session management according to the protocol discriminator. - For EPS services, the routing function of EPS NAS passes standard L3 messages according to the protocol discriminator (PD) and, if applicable, the procedure transaction identity (PTI) and/or EPS bearer identity towards the EMM entity or towards the CM (ESM) entities of the various EPS NAS SAP's. - The routing function of LLC passes the messages according to the SAPIs to the MM sublayer or to the SNDCP entities. The message (message header or other parts of the message) are neither changed nor removed by the RR routing function or MM routing function before passing it to the appropriate service access point.

22 21 TS V ( ) 5.2 Protocol architecture The protocol architecture is visualized for each of the three models: - Figure 5.1/3GPP TS shows the protocol architecture for a MS not supporting the GPRS service, restricting the representation of CM sublayer protocols to three paradigmatic examples, CC, SS, and SMS. The LCS protocol entity of a type A LMU would be included in the same manner. Note that the protocol stack for a class C GPRS service may be present in the MS, but it is not active simultaneously. - Figure 5.2 shows the protocol architecture for a MS supporting the Class C GPRS service. (Note that the protocol stack for a circuit switched services may be present in the MS, but it is not active simultaneously). - Figure 5.3 shows the protocol architecture for non-gprs and GPRS-services supporting Class A and Class B MSs. - Figure 5.4 shows the protocol architecture for a MS supporting CTS services in addition to non-gprs services. - Figure 5.5 shows the protocol architecture for a MS supporting the PS mode of operation UMTS service. - Figure 5.6 shows the protocol architecture for UMTS services supporting CS/PS mode of operation MSs. - Figure 5.7 shows the protocol architecture for a MS supporting EPS services. - Figure 5.8 shows the protocol architecture for an MS supporting EPS services and CS fallback.

23 22 TS V ( ) NOTE: The LCS protocol entity for a type A LMU would be included in the figure in the same manner as the protocol entities for CC, SS and SMS. Figure 5.1: Protocol Architecture not supporting GPRS service - MS side

24 23 TS V ( ) SN-SAP User payload services (SNDCP) SNSM-SAP SMREG-SAP MNSMS-SAP MNSS-SAP CM SESSION MANAGEMENT GSMS SS PDP TI TI GMMSM-SAP GMMREG-SAP GMMSS-SAP MM-sublayer GMM PD / TLLI QoS4-SAP LLC-sublayer QoS3-SAP QoS2-SAP QoS1-SAP LLGMM-SAP LLSMS-SAP LLC management entity SAPI RR-sublayer GRR-SAP GRR (shared mode RR) GMMRR- SAP P B C C H P R A C H P A G C H P P C H P N C H P D T C H P A C C H B C C H R A C H A G C H P C H Figure 5.2: Protocol architecture supporting GPRS class C MSs, MS - side

25 24 TS V ( ) SN-SAP User payload services (SNDCP) SNSM-SAP SMREG-SAP MNSMS-SAP MNCC-SAP MNSS-SAP SM GSMS CC SS CM PDP TI TI TI TI TI MM-sublayer GMMSM- SAP GMMREG -SAP GMMSMS- SAP MMSMS- SAP MMCC-SAP GMMSM- SAP GMMSS2- SAP MMSSSAP GMM GMM coord MM coord MM PD PD / TLLI LLC sublayer QoS1-4 SAP s LLGMM- SAP Internal structure see figure 5.2 LLSMS-SAP GRR-SAP GMMRR-SAP RR-SAP RR-sublayer GRR (shared mode RR) RR (dedicated mode RR) PD distribution P D T C H P A C C H P B C C H P R A C H P P C H P N C H P A G C H B C C H R A C H A G C H P C H T C H Incl. - FACCH - SACCH S D C C H Figure 5.3/3GPP TS : Protocol architecture supporting GPRS class A and B MSs, MS - side

26 25 TS V ( ) MOBILE NETWORK SERVICE MNCC-SAP MNSS-SAP MNSMS-SAP CC SS SMS MMSS-SAP MMREG-SAP MMCC-SAP MMSMS-SAP =CTS-MM SPD MM = CTS-MM TI TI TI MM CC SS SMS L A Y E R 3 CTS-MM MM PD RR-SAP S I G N A L L I N G =CTS-RR SPD = CTS-RR RR RR PD =RR CTS-RR RR SAPI 0 SAPI 3 C T S A R C H C T S B C H C T S A G C H C T S P C H C T S S A C C H C T S F A C C H C T S S A C C H Figure 5.4/3GPP TS : Protocol architecture supporting CTS services in addition to non- GPRS services, MS - side

27 26 TS V ( ) RAB1-SAP RAB2-SAP RABn-SAP SMREG-SAP MNSMS-SAP MNSMS-SAP RABM RABMSM-SAP CM RAB Entity 1 RAB Entity 2 RAB Entity n RAB Control SESSION MANAGEMENT GMMRABM_SAP MM-sublayer PDP GMMSM-SAP GMMREG- SAP GSMS TI PMMSMS-SAP SS TI GMMSS-SAP GMM PD PDCP1-SAP PDCP2-SAP PDCPn-SAP RABMAS-SAP GMMAS-SAP Access Stratum sublayer PDCP BMC RRC Figure 5.5/3GPP TS : Protocol architecture of Non Access Stratum supporting PS mode of operation MSs, MS-side