hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
595
| content
stringlengths 0
6.67M
|
|---|---|---|---|
6214fe0cb7fd036169572670b8a939f8 | 21.900 | 7.7 E‑mail reflectors | TSGs, WGs and SWGs have their own e‑mail lists. There are also several additional lists per topic. Further information can be found on 3GPP web pages. |
6214fe0cb7fd036169572670b8a939f8 | 21.900 | 8 E‑mail decisions | 8.0 Overview
WGs may apply e‑mail decision procedures for decisions they are entitled to take, as defined by superior bodies (e.g. on specifications, CRs, Liaison statements, etc.). Each WG may set its rules for making e‑mail decisions, however, it is required that:
- the rules are clearly defined and documented;
- a delegate having participated in plenary meetings is able to identify that he has possibly missed an e‑mail relevant to e‑mail decision.
Clauses 8.1-8.6 describe an e‑mail decision procedure example. |
6214fe0cb7fd036169572670b8a939f8 | 21.900 | 8.1 E‑mail drafting phase | An e‑mail drafting session can be launched, either on a dedicated exploder list as a cybermeeting or as an informal discussion between interested delegates. Objectives can extend from debating an existing contribution, a Liaison Statement or a Change Request to progressing the service requirements of a specific Work Item and involving one or more Working Groups.
In case of "cybermeeting", the Chair of the discussions shall issue an un-ambiguous guideline including:
1) the objectives and agenda of the meeting;
2) input document(s) to be clearly specified;
3) start date and end date of the debates;
4) afterwards, summary of results of the "cybermeeting".
The end-goal being to reach an "agreement" on the deliverable, either at the next meeting or via an e‑mail approval procedure. |
6214fe0cb7fd036169572670b8a939f8 | 21.900 | 8.2 E‑mail decision declaration | Authority for an e‑mail decision to take place should usually be agreed at plenary meeting. If this is not possible, there shall be a clear notification (i.e. status report) indicating that there will be an e‑mail decision. This notification shall be sent on the main mailing lists indicating the mailing list where the discussion will take place (TSG, WG or SWG list). Target and timeframe shall be clearly indicated. A permanent Chair (i.e. WG Chair or Vice Chair) shall be nominated, who will be responsible for managing the e‑mail decision procedure, including initiation, monitoring and announcing when it is complete. |
6214fe0cb7fd036169572670b8a939f8 | 21.900 | 8.3 Status reporting | During the e‑mail decision period, there shall be a clear message stating what the status of each open item is. It is recommended to have a weekly summary of the status of all items, from the previous plenary listing:
- the name of the open item;
- the name of the responsible delegate;
- time left for comments before the deadline & expiration date;
- current work versions of documents: Tdoc number, CR number, Revision number;
- status (Debate ongoing, Agreed, Postponed, Rejected, ...). |
6214fe0cb7fd036169572670b8a939f8 | 21.900 | 8.4 Decision announcement | When a decision is made (Agreed, rejected, postponed, ...) a clear notification on what has been agreed shall be sent on the main mailing lists of the relevant groups. |
6214fe0cb7fd036169572670b8a939f8 | 21.900 | 8.5 Timing | E‑mail decision procedure should start at the latest 3 weeks before relevant plenary:
- the e‑mail decision period is two weeks (one status report required);
- the procedure shall be completed one week before the relevant TSG, WG or SWG plenary, due to practical arrangements. |
6214fe0cb7fd036169572670b8a939f8 | 21.900 | 8.6 General | - in exceptional cases when the procedure cannot be followed a clear notice from Chair is required;
- e‑mails on mailing lists shall contain a subject with meaningful keywords, e.g. SA1 Tdoc xxx on Charging and/or 22xxx‑CR012r4;
- if there are no comments during the allowed period, agreement is granted automatically;
- status reports to higher level body meetings, should be e‑mailed to the mailing list one week before the meeting. This allows delegates a final possibility to review the progress in the last period. |
6214fe0cb7fd036169572670b8a939f8 | 21.900 | 9 Meeting contribution document types and status values | |
6214fe0cb7fd036169572670b8a939f8 | 21.900 | 9.1 Terminology | Written contributions to 3GPP meetings are called "TDocs".
NOTE: The term "TDoc" is an abbreviation of "Temporary Document" and is a legacy of when such documents were prepared in paper form. Temporary Documents were not intended to be retained after the end of the meeting at which they were discussed, contrasted with Permanent Documents which were retained after the end of the meeting for longer term (permanent?) reference. 3GPP retains all TDocs in electronic form and thus there is no need for a separate "PDoc" class, although some working groups do retain some documents informally referred to as "permanent reference documents".
Each TDoc shall be one of the following types:
Table 9.1-1: Permissible TDoc types
TDoc type
Remarks
agenda
Meeting agendas, including those showing allocation of TDocs to agenda items, also timing schedules
Work Plan
Ordered list of work items
LS in
Liaison Statement, received from some other 3GPP group or an external body
LS out
Liaison Statement issued by a group and directed to one or more other 3GPP groups or external bodies.
pCR
Pseudo-Change-Request: similar to a Change Request but has no CR number and is intended to propose new or revised text for inclusion in 3GPP TSs or TRs not yet under change control (i.e. still in the drafting phase). Known in some groups as "text proposal".
draftCR
Similar to a Change Request, but unnumbered; proposes new or revised text for a TS or TR already under change control. May ultimately be revised into a regular Change Request.
CR
A formal proposal to make changes to a TS or TR which is under change control – i.e. which has a version number with the first field greater than 2 (see clause 4.0A).
CR Pack
One or more Change Requests which have been agreed (or endorsed) at working group level and are being presented as a package to TSG for approval.
ToR
Terms of reference for a TSG or working group.
WID new
Work item description for a new work item – i.e. one not already approved at TSG level.
WID revised
Proposes changes to an already TSG-approved Work item description.
SID new
As "WID new", where the work item is of type "study".
SID revised
As "WID revised", where the work item is of type "study".
WI status report
Rapporteur's report (reviewed by the lead WG) of the current state of completion of a work item (degree of completion, target date, contentious issues, …).
WI exception request
Request to TSG to permit an overrun in the schedule for the completion of a work item.
TS or TR cover
Stand-alone cover sheet for a draft TS or TR being presented (normally at TSG level). Typically used in conjunction with a "draft TS" or "draft TR" type where the actual draft TS or TR and its cover are not included in the same TDoc.
draft TS
A complete TS, still in draft state, being presented either for information or approval at TSG level. May also be used at WG level. At TSG level, normally includes a separate "TS or TR cover" indicating the state of development of that TS; if the cover sheet is not included, it can be provided in a separate TDoc of type "TS or TR cover".
draft TR
As "draft TS" but pertaining to a TR rather than a TS.
report
Any report (other than "WI status report", see above). Typically documents the proceedings of a TSG or WG, or a subgroup thereof.
discussion
A TDoc which is intended to be discussed.
response
A TDoc which has been prepared to provide support for, or a counter argument to, another TDoc.
Note: This type is pecular to one particular working group (RAN3).
other
Any other kind of TDoc, for which none of the above types is appropriate.
WI Summary
Summary of a work item (or a group of work items which is decided by the responsible TSG). It explains the purpose of introducing the work item(s) as well as the impacts on the system without requiring that the reader is a specialist in this field. It is issued by the completion time of the work item(s) and describes what has been specified (i.e. the solution finally selected and approved by the TSG). |
6214fe0cb7fd036169572670b8a939f8 | 21.900 | 9.2 TDoc status values | Each TDoc having a formal allocated TDoc number has an associated status chosen from table 9.2-1 below. Table 9.2-1: TDoc status values Status value Meaning Used for TDocs of type … - Retained for compatibility with legacy TDocs. None reserved TDoc number allocated, document not yet available. If this status remains at the end of the meeting, it will be reported in the minutes as "not available". Note: It is not uncommon for revised TDocs to be agreed or approved in principle prior to their becoming available, in which case the appropriate status is set against the TDoc immediately. 3GU keeps a separate field indicating whether the TDoc is, in fact, available. If a TDoc remains unavailable at the end of the meeting, or at the end of any post-meeting decision period, then the Secretary will revert its status to "reserved", and the meeting report will indicate it as being "not available". Any available TDoc available, not yet treated. If this status remains at the end of the meeting, it will be reported in the minutes as "not treated". Any approved Favourable conclusion; the group in question (TSG or WG) has the final say. Any agreed Favourable conclusion; the decision has to be confirmed by a higher body (e.g. WG decision has to be confirmed by TSG). Any noted TDoc has been presented, no specific action results. Any except for CRs, where interpretation is ambiguous. postponed TDoc has been presented but no final decision could be reached; subject is likely to be raised at a subsequent meeting. Any withdrawn Prior to discussion of the TDoc, its author has decided not to present it. Any treated TDoc has been presented, but no other status is appropriate (for example, in the case of a CR pack, some CRs in it were revised, some postponed, and some reissued – none was approved). Any, but principally intended for CR packs. revised TDoc will be modified and presented in a new TDoc. Any partially approved Used for CR packs only. One or more CRs contained in the TDoc has been approved at TSG level; other CRs may have status revised, postponed, not pursued, etc. CR packs endorsed The group believes that the TDoc is valid but has not reached a conclusion of "agreed" or "approved". May be used as a WG status where alternative solutions to a technical matter have been identified, and the choice between them is being left to the TSG. Also by a WG when asked to give an opinion on a matter (typically a WID) for which another WG is responsible. Any, but principally intended for - CRs where two or more solutions are proposed, - WIDs belonging to another group. merged The TDoc is combined with one or more others and presented in a new, composite TDoc. Any, but principally intended for pCRs, draftCRs and CRs. reissued Only used for the status of CRs in a CR Pack. Indicates that the CR appears unchanged in a different CR Pack created because one or more other CRs in the original pack is revised or withdrawn. CRs within CR packs only. replied to Used for incoming Liaisons only. Indicates that an outgoing Liaison has been prepared in reply to this incoming Liaison. LS in conditionally agreed Agreed, but conditional on a decision taken on a different TDoc, possibly in a different group. Any, but principally intended for CRs. conditionally approved Approved, but conditional on a decision taken on a different TDoc, possibly in a different group. Any, but principally intended for CRs (typically in a CR pack at TSG level) not concluded Discussion has started but has not finished. Typically used as a temporary status between the end of a meeting any post-meeting review or agreement/approval (for example, by email). Any not pursued No further action to be taken. Replacement for "rejected", without the emotive implications sometimes inferred for "rejected". Any rejected Retained for compatibility with legacy TDocs. Meaning identical to "not pursued". May be used by groups which are not sensitive to this value. Any Annex A: Change history Change history TSG SA# Version CR Tdoc SA New Version Subject/Comment SP-04 3.0.0 001 SP-99288 3.1.0 Alignment with TSG SA decisions made at TSG#3. Deletion of Strategic/non strategic CR references. Change of PT to Support Team, editorial corrections. 002 SP-99289 Harmonisation of the use of software for 3GPP documents in order to minimise the errors due to software conversion problems and to allow efficient interchange of electronic files for electronic working. SP-05 3.1.0 003 SP-99428 3.2.0 Addition of new text related to electronic working practices. SP-08 3.2.0 005 SP-000279 3.3.0 Clarification and editorial corrections to provisions covering the management of specifications and Work Items. SP-09 3.3.0 007 r1 SP-000402 3.4.0 Role of rapporteur for both Specifications and Work Items. 008 r2 SP-000492 Clarification of CR categories. 010 SP-000461 Clarification of CR categories for a frozen 3GPP release. editorial Change of "Release 2000" into "Release 4", addition of "Release 5". SP-10 3.4.0 011 r1 SP-000693 3.5.0 Release numbers appearing in CR cover sheets 3.4.0 012 r1 SP-000693 Clarification of the "freezing" of specifications 3.4.0 013 r2 SP-000693 Release mechanisms SP-11 3.5.0 014 r1 SP-010178 3.6.0 Inclusion of GSM spec numbering scheme 3.6.0 - - 4.0.0 Upgrade to Rel‑4. SP-16 4.0.0 - - 5.0.0 Upgrade to Rel-5. 2002-09-17 5.0.0 - - 5.0.1 Editorial correction to front cover (change title to read Release 5 instead of Release 4) SP-21 5.0.1 015 SP-030499 6.0.0 Addition of stage 1-2-3 specification structure description SP-22 6.0.0 019 SP-030575 6.1.0 Corrects references SP-23 6.1.0 - - 6.1.1 Corrects Release shown on cover page SP-24 6.1.1 020 SP-040310 6.2.0 Rlease planning: target date setting - Editorial: Correction of second clause 6.0.2 to 6.0.3. SP-25 6.2.0 021 r3 SP-040705 6.3.0 Introduction of "Early Implementation" process 024 SP-040706 Improved tracking of Work Item status SP-26 6.3.0 025 SP-040824 7.0.0 Editorial clarification of version numbering system, upgrade to Rel-7 SP-28 7.0.0 7.0.1 Editorial corrections to harmonize use of capitalization plus a typographical error SP-29 7.0.1 028 SP-050537 7.1.0 Introduction of the concept of "study item" SP-32 7.1.0 029 SP-060403 7.2.0 Inclusion of "study item" in definition of "work item" 030 Change "short" to "long" WG abbreviations 031 r1 Correct references to obsolete TSG. 032 Registration of code points with external bodies SP-37 7.2.0 034 r2 SP-070703 8.0.0 Alignment of working methods with alignment CR practice agreed in TSG SA #36 SP-38 8.0.0 035 SP-070900 8.1.0 Addition of 36.-series to Specs series table 8.1.0 8.1.1 Correct typo in previous entry in history table SP-39 8.1.1 036 r2 SP-080079 8.2.0 Clarification of version nomenclature SP-42 8.2.0 037 r3 SP-080897 8.3.0 Determination of freeze dates for stages of a Release. (Correction recommended by OP ad hoc group on improvements.) 038 r1 SP-080721 Cross-TSG work coordination. (Correction recommended by OP ad hoc group on improvements.) 039 r2 Introduction of concept of "exception sheets" for late-running work items SP-46 8.3.0 9.0.0 Upgrade without technical change to Rel-9 SP-51 9.0.0 10.0.0 Upgrade without technical change to Rel-10 SP-54 10.0.0 045 SP-110802 11.0.0 The use of Category A CRs 11.0.0 11.0.1 2013-06: Corrects cased of letter "i" shown against value 18 in table 5. SP-65 11.0.1 047 SP-140445 11.1.0 Correction to implementation of CR0045 043r2 SP-140446 Encourage allocation of CR number at first sight 11.1.0 12.0.0 Upgrade to Release 12 without technical change SP-70 12.0.0 048r1 SP-150825 13.0.0 TDoc types and status values SP-70 13.0.0 13.0.1 Correction of minor editorial issues Change history Date Meeting TDoc CR Rev Cat Subject/Comment New version 2016-12 SA#74 SP-160967 0052 2 F Withdrawal of specifications and functionality 13.1.0 2017-03 SA#75 Addition of missing spec series to table 1. Upgrade without further technical change on freezing Release 14. 14.0.0 2017-06 SA#80 SP-180617 0054 2 F Clarifying secondary responsibility 14.1.0 2017-06 SA#80 Upgrade unchanged on freeze of Rel-15 15.0.0 2018-09 SA#81 SP-180848 0056 F Spec filenames for version element having a value > 35 15.1.0 2018-10 Correction of typo: version number in history table 15.1.1 2018-12 SA#82 Upgrade without technical change to Release 16 at the request of TSG SA 16.0.0 2019-03 SA#83 SP-190021 0059 C Update of procedures relating to the storage of OpenAPI specification documents 16.1.0 2019-03 SA#83 SP-190270 0057 8 C Update of procedures relating to work items 16.1.0 2019-03 SA#83 SP-190272 0049 5 F Alignment for alignment CRs 16.1.0 2019-09 SA#85 Editorial correction of CR rev number in previous line 16.2.0 2019-09 SA#85 SP-190916 0061 2 F Update of the TS version number in the OpenApi 'externalDocs' object 16.2.0 2020-03 SA#87-e SP-200130 0063 F OpenAPI specification file storage 16.3.0 2021-03 SA#91e SP-210193 0067 F Migration from ETSI forge to 3GPP forge 16.4.0 2021-03 SA#91e SP-210047 0065 F Addition of xx.7xx number series for internal TRs 17.0.0 2021-06 SA#92e SP-210306 0068 - D Replacing Chairman by Chair 17.1.0 2021-06 SA#92e SP-210309 0069 - F Cleanup of CR procedures 17.1.0 2022-06 SA#96 SP-220383 0072 F Clean-up 18.0.0 2022-09 SA#97e Fix cover sheet 18.0.1 2023-09 SA#101 SP-231201 0073 4 B Add Forge as a potential normative storage for stage 3 specification files 18.1.0 2024-03 SA#103 SP-240517 0074 1 F Alignment of TDoc type with latest procedures and clarification of closed releases along with corresponding alignment of frozen releases 18.2.0 2024-03 SA#103 SP-240279 0075 D Editorial clean-up 18.2.0 2025-03 SA#107 SP-250230 0076 1 F Clarification on generations and correction CRs 19.0.0 |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 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 clause 4.3.4.
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 and 5GS NAS layer 3 protocol and their 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 6 to 10 are not maintained actively. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 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 21.905: "Vocabulary for 3GPP Specifications".
[2] 3GPP TS 23.101: "General UMTS Architecture".
[3] 3GPP TS 44.001: "Mobile Station ‑ Base Station System (MS ‑ BSS) interface; General aspects and principles".
[3a] 3GPP TS 23.060: "General Packet Radio Service (GPRS) description; Stage 2".
[3b] GSM 03.56(R98): "Digital cellular telecommunications system (Phase 2+); GSM Cordless Telephony System (CTS), Phase 1; CTS Architecture Description; Stage 2".
[3c] 3GPP TS 23.271: "Functional stage 2 description of location services".
[4] 3GPP TS 44.005: "Data Link (DL) layer; General aspects".
[5] 3GPP TS 44.006: "Mobile Station ‑ Base Station System (MS ‑ BSS) interface; Data Link (DL) layer specification".
[5a] 3GPP TS 44.014: "Individual equipment type requirements and interworking; Special conformance testing functions".
[6] 3GPP TS 24.008: "Mobile radio interface Layer 3 specification Core Network Protocols-Stage 3".
[6a] 3GPP TS 23.108: "Mobile radio interface Layer 3 specification Core Network Protocols Stage 2 (structured procedures)".
[6b] 3GPP TS 44.018: "Mobile radio interface layer 3 specification; Radio Resource Control Protocol".
[7] 3GPP TS 24.010: "Mobile radio interface Layer 3; Supplementary services specification; General aspects".
[8] 3GPP TS 24.011: "Point‑to‑Point (PP) Short Message Service (SMS) support on mobile radio interface".
[8a] 3GPP TS 44.071: "Location Services (LCS); Mobile radio interface layer 3 LCS specification".
[9] 3GPP TS 24.080: "Mobile radio Layer 3 supplementary services specification; Formats and coding".
[10] 3GPP TS 24.081: "Line identification supplementary services; Stage 3".
[10a] 3GPP TS 44.060: "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 44.056: "GSM Cordless Telephony System (CTS), phase 1; CTS radio interface Layer 3 specification".
[11] 3GPP TS 24.082: "Call Forwarding (CF) supplementary services - Stage 3".
[11a] 3GPP TS 44.064: "General Packet Radio Service (GPRS); Mobile Station - Serving GPRS Support Node (MS-SGSN) Logical Link Control (LLC) layer specification".
[12] 3GPP TS 24.083: "Call Waiting (CW) and Call Hold (HOLD) supplementary services; Stage 3".
[12a] 3GPP TS 44.065: "General Packet Radio Service (GPRS); Mobile Station (MS) - Serving GPRS Support Node (SGSN); Subnetwork Dependent Convergence Protocol (SNDCP)".
[13] 3GPP TS 24.084: "MultiParty (MPTY) supplementary services; Stage 3".
[14] 3GPP TS 24.085: "Closed User Group (CUG) supplementary services; Stage 3".
[15] 3GPP TS 24.086: "Advice of Charge (AoC) supplementary services; Stage 3".
[16] 3GPP TS 24.088: "Call Barring (CB) supplementary services; Stage 3".
[17] 3GPP TS 24.090: "Unstructured Supplementary Service Data (USSD) - Stage 3".
[17a] 3GPP TS 34.109: "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 44.068: "Group Call Control (GCC) Protocol".
[20] 3GPP TS 23.110: "UMTS Access Stratum Services and Functions".
[21] 3GPP TS 24.030: "Location Services (LCS); Supplementary service operations – Stage 3".
[22] 3GPP TS 23.251: "Network Sharing; Architecture and functional description".
[23] 3GPP TS 25.413: "UTRAN Iu interface RANAP signalling".
[24] 3GPP TS 36.331: "Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC) protocol specification".
[25] 3GPP TS 24.301: "Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3".
[26] 3GPP TS 36.509: "Evolved Universal Terrestrial Radio Access (E-UTRA); Special conformance testing function for User Equipment (UE)".
[27] 3GPP TS 23.216: "Single Radio Voice Call Continuity (SRVCC); Stage 2".
[28] 3GPP TS 38.331: "NR Radio Resource Control (RRC) Protocol specification".
[29] 3GPP TS 38.509: "5GS; Special conformance testing functions for User Equipment (UE)".
[30] IETF RFC 7296: "Internet Key Exchange Protocol Version 2 (IKEv2)".
[31] 3GPP TS 24.501: "Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3".
[32] 3GPP TS 24.502: "Access to the 3GPP 5G System (5GS) via non-3GPP access networks; Stage 3".
[33] 3GPP TS 24.519: "5G System (5GS); Time-Sensitive Networking (TSN) Application Function (AF) to Device-Side TSN Translator (DS-TT) and Network-Side TSN Translator (NW-TT) protocol aspects; Stage 3".
[34] 3GPP TS 24.587: "Vehicle-to-Everything (V2X) services in 5G System (5GS); Protocol aspects; Stage 3"
[35] 3GPP TS 24.193: "Access Traffic Steering, Switching and Splitting; Stage 3".
[36] 3GPP TS 24.334: "Proximity-services (ProSe) User Equipment (UE) to Proximity-services (ProSe) Function Protocol aspects; Stage 3".
[37] 3GPP TS 29.571: "5G System; Common Data Types for Service Based Interfaces; Stage3".
[38] 3GPP TS 24.554: "Proximity-services (ProSe) in 5G System (5GS) protocol aspects; Stage 3".
[39] 3GPP TS 24.538: "Enabling MSGin5G Service; Protocol specification".
[40] 3GPP TS 24.572: "User Plane Location Services (LCS) Protocols And Procedures; Stage 3".
[41] 3GPP TS 24.514: "Ranging based services and sidelink positioning in 5G system(5GS); Stage 3".
[42] 3GPP TS 24.577: "Aircraft-to-Everything (A2X) services in 5G System (5GS) protocol aspects; Stage 3". |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 3 Definitions and abbreviations | |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1a] apply. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations defined in 3GPP TR 21.905 [1a] and the following apply:
GMM GPRS Mobility Management
MNS Mobile Network Signalling
N-PDU Network-Protocol Data Unit
SM Session Management
UDT User Data Transfer
CTS Cordless Telephony System
LCS LoCation Services
MOCN Multi-Operator Core Network |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 4 Introduction | |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 4.1 General | Five 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, one model for EPS services and one model for 5GS services over either 3GPP access or over non-3GPP access. (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
- 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.
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.
The layer 3 for 5GS services is composed of three sublayers comprising:
- the 5GS radio resource management (5GRR) functions for NAS over 3GPP access or the non-3GPP access functions for NAS over non-3GPP access;
- the 5GS mobility management (5GMM) functions; and
- the 5GS connection management (5GCM) functions.
The 5GS mobility management (5GMM) sublayer is composed of a functional block for:
- the 5GS mobility management (5GMM) functions.
The 5GS connection management (5GCM) sublayer is composed of a functional block for:
- the 5GS session management (5GSM) functions.
NOTE: For NAS over non-3GPP access, the non-3GPP access functions can be supported through functionalities defined in IETF RFC 7296 [30]. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 4.2 Applicability of functional blocks | Not for all functional blocks listed in clause 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. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 4.3 Technique of description | Layer 3 and its sub‑layers are specified by:
- their service specification, see clause 4.3.1;
- their protocol specification, see clause 4.3.3;
- the specification of functions, see clause 5.
Descriptions in clauses 3 to 10 are not maintained actively. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 4.3.1 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]. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 4.3.2 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 21.905 [1a]. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 4.3.3 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 clause 4.1 there is one protocol. The CM protocols are specified in the Technical Specifications identified in clause 4.3.4.
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 clause 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 clause 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;
- for each functional block of the CM sublayer as defined in clause 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 clause 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.
6) for 5GS services:
- one 5GRR entity in the MS and one 5GRR entity in the network for NAS over 3GPP access;
- one non-3GPP access management entity in the MS and one non-3GPP access interworking entity in the N3IWF for the NAS over non-3GPP access;
- one 5GMM entity in the MS and one 5GMM entity in the network;
- for each functional block of the 5GCM sublayer as defined in clause 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. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 4.3.4 Contents of layer 3 related Technical Specifications | - The Radio Resource (RR) management protocol is defined in 3GPP TS 44.018 [6b];
- the Mobility Management (MM) protocol is defined in 3GPP TS 24.008 [6];
- the Session Management (SM) protocol is defined in 3GPP TS 24.008 [6];
- the Call Control (CC) protocol is defined in 3GPP TS 24.008 [6];
- the Supplementary Services (SS) protocol is defined in 3GPP TS 24.010 [7], 3GPP TS 24.08x, 3GPP TS 24.09x, and 3GPP TS 24.030 [21];
- the Short Message Service (SMS) protocol is defined in 3GPP TS 24.011 [8];
- the Group Call Control (GCC) protocol is defined in 3GPP TS 44.068 [19];
- the Logical Link Control (LLC) protocol is defined in 3GPP TS 44.064 [11a];
- the GPRS Radio Resource (GRR) protocol is defined in 3GPP TS 44.060 [10a] and 3GPP TS 24.008 [6];
- the CTS Radio Resource (CTS-RR) sub-protocol is defined in 3GPP TS 44.056 [10b];
- the CTS Mobility Management (CTS-MM) sub-protocol is defined in 3GPP TS 44.056 [10b];
- the CTS additions to the Call Control (CC) protocol are defined in 3GPP TS 44.056 [10b];
- the Location Services (LCS) protocol for a type A LMU is defined in 3GPP TS 23.271 [3c] and 3GPP TS 44.071 [8a];
- the EPS Radio Resource (RR) management protocol is defined in 3GPP TS 36.331 [24];
- the EPS Mobility Management (EMM) protocol is defined in 3GPP TS 24.301 [25];
- the EPS Session Management (ESM) protocol is defined in 3GPP TS 24.301 [25];
- the 5GS Radio Resource management (5GRR) protocol is defined in 3GPP TS 38.331 [28];
- the 5GS Mobility Management (5GMM) protocol is defined in 3GPP TS 24.501 [31];
- the 5GS Session Management (5GSM) protocol is defined in 3GPP TS 24.501 [31];
- the UE policy delivery service is defined in 3GPP TS 24.501 [31];
- the non-3GPP access management protocol is defined in 3GPP TS 24.502 [32];
- the PC5 signalling protocol for V2X communication for 5GS is defined in 3GPP TS 24.587 [34];
- the Time-Sensitive Networking (TSN) Application Function (AF) to Device-Side TSN Translator (DS-TT) and Network-Side TSN Translator (NW-TT) protocol is defined in 3GPP TS 24.519 [33];
- the Performance Measurement Function (PMF) protocol is defined in 3GPP TS 24.193 [35];
- the PC3 and PC5 signalling protocol for Proximity-based Services (ProSe) are defined in 3GPP TS 24.334 [36];
- the PC3a and PC5 signalling protocol for 5G Proximity-based Services (ProSe) are defined in 3GPP TS 24.554 [38];
- the signalling protocol between the Application Client on the constrained UE and the MSGin5G Client on the MSGin5G Gateway UE for Enabling MSGin5G Service is defined in 3GPP TS 24.538 [39];
- the Location Services User Plane (LCS-UP) protocol is defined in 3GPP TS 24.572 [40];
- the User Plane Positioning Connection Management (UPP-CM) protocol is defined in 3GPP TS 24.572 [40];
- the extended PC5 signalling protocol for ranging and sidelink positioning and supplementary RSPP signalling protocol over PC5-U for ranging and sidelink positioning are defined in 3GPP TS 24.514 [41]; and.
- the PC5 signalling protocol for aircraft-to-everything (A2X) communication is defined in 3GPP TS 24.577 [42]. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 5 Structure of layer 3 functions | |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 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 clause 4.3.3.
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 or in the 5GRR (for NAS over 3GPP access) or non-3GPP access management (for NAS over non-3GPP access) and Mobility Management or 5GMM 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 clause 4.3.3. 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.
For 5GS services, the routing functions with task 2 make use of the extended protocol discriminator (EPD) which is part of the message header, or PDU session identity.
A 5GCM sublayer protocol may also define a procedure transaction identity (PTI) as a part of the message header. This is at least the case if there are parallel entities of the same functional block, see clause 6.2.
- The 5GMM-sublayer routing function passes the messages of the 5GCM entities as well as of the 5GMM entities of its own sublayer to the service access point of 5GRR. Furthermore, it multiplexes them in case of parallel transactions.
- For NAS over 3GPP access, the NR or E-UTRA AS sublayer routing function distributes the messages to be sent according to their message type and extended protocol discriminator (EPD), 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. Paging messages received from the PCH are always routed to 5GMM.
- For NAS over 3GPP access, the messages provided at the different service access points of layer 2 are distributed by the 5GRR sublayer routing function according to their extended protocol discriminator (EPD). Messages with a EPD equal to RR are passed to the 5GRR entity of the own sublayer, all other messages are passed to the 5GMM sublayer at the service access point 5GRR-SAP.
- For NAS over non-3GPP access:
- for initial registration, EAP-5G is used to transfer NAS messages between the peer entities of the 5GMM sublayers;
- after successful initial registration, IPSec transport mode and GRE will be used to encapsulate and un-encapsulate the NAS messages between the peer entities of the 5GMM sublayers.
- For 5GS services, the routing function of 5GS NAS passes standard L3 messages according to the extended protocol discriminator (EPD) and, if applicable, the PDU session identity towards the 5GMM entity or towards the 5GSM entities of the various 5GS NAS SAPs.
The message (message header or other parts of the message) are neither changed nor removed by the RR routing function or non-3GPP access management or MM routing function or 5GMM routing function before passing it to the appropriate service access point. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 5.2 Protocol architecture | The protocol architecture is visualized for each of the four models:
- Figure 5.1/3GPP TS 24.007 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.
- Figure 5.9 shows the protocol architecture for a MS supporting 5GS services over 3GPP access.
- Figure 5.10 shows the protocol architecture for a MS supporting 5GS services over non-3GPP access.
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
Figure 5.2: Protocol architecture supporting GPRS class C MSs, MS - side
Figure 5.3/3GPP TS 24.007: Protocol architecture supporting GPRS class A and B MSs, MS - side
Figure 5.4/3GPP TS 24.007: Protocol architecture supporting CTS services in addition to non- GPRS services, MS - side
Figure 5.5/3GPP TS 24.007: Protocol architecture of Non Access Stratum supporting PS mode of operation MSs, MS‑side
Figure 5.6/24.007: Protocol architecture of Non Access Stratum supporting CS/PS mode of operation MSs, MS – side
NOTE: SMS un-related parts of this figure, e.g. SNDCP should be modified for UMTS.
Figure 5.7/3GPP TS 24.007: Protocol architecture of Non Access Stratum supporting PS mode of operation MSs, MS‑side
Figure 5.8/3GPP TS 24.007: Protocol architecture of Non Access Stratum supporting CS/PS mode 1 or CS/PS mode 2 of operation MSs, MS‑side
Figure 5.9/3GPP TS 24.007: Protocol architecture of Non Access Stratum supporting MSs, MS‑side (over 3GPP access)
Figure 5.10/3GPP TS 24.007: Protocol architecture of Non Access Stratum supporting MSs, MS‑side (over non-3GPP access)
As shown in figure 5.1 a hierarchy of 3 sublayers is defined:
- the RR sublayer provides services to the MM sublayer and utilizes the services of signalling layer 2;
- the MM sublayer provides common services to the entities of the Connection Management (CM) sublayer;
- the CM sublayer includes, among others, the CC, SS, and SMS entities, which are independent entities.
Figure 5.2 defines four sublayers for GPRS services supporting Class C MSs:
- the RR sublayer provides services to the MM and LLC sublayers;
- the LLC sublayer provides services to the MM sublayer, the SNDCP and GSMS entities and uses services of the RR sublayer;
- the MM sublayer provides services to the SM and SS entities of the CM. The MM sublayer includes one GMM;
- the CM sublayer includes the SM, SS and GSMS entities. The SM entity provides services to the SNDCP entity and uses services of the MM sublayer. The GSMS entity is identical to the SMS entity for non-GPRS services except it uses the services from the LLC sublayer. The SS entity is identical to the one for non-GPRS services except it uses the services from the LLC or PS signalling connection.
Figure 5.3 defines four sublayers for non-GPRS and GPRS-services supporting Class A and Class B MSs:
- the RR sublayer provides services to the MM and LLC sublayers;
- the LLC sublayer provides services to the MM sublayer, the SNDCP and GSMS entities and uses services of the RR sublayer;
- the MM sublayer provides services to the SNDCP entity and to the entities of the Connection Management (CM) sublayer. In addition to the MM entity for non-GPRS services, the MM sublayer further includes one GMM entity;
- the CM sublayer includes, among others, the CC, SS, GSMS and SM entities, which are independent entities;
- the SM entity provides services to the SNDCP entity and uses services of the MM sublayer.
The GSMS entity is an extension of the SMS entity for non-GPRS services. For message transfer it uses the services both from the LLC sublayer and the MM entity of the MM sublayer. Furthermore it retrieves from the MM entity information about which transport service to use.
Figure 5.4 defines three sub-layers for CTS services:
- the RR sublayer provides services (including CTS services) to the MM sublayer and uses the services of signalling layer 2;
- the MM sublayer provides common services to the entities of the Connection Management (CM) sublayer; it provides also specific CTS services to the entities above CM;
- the CM sublayer includes, among others, the CC, SS, and SMS entities, which are independent entities.
Figure 5.5 defines three sublayers for UMTS PS domain services supporting PS mode of operation:
- the Access Stratum (AS) sublayer provides services to the MM sublayer and the RAB Manager (RABM) entity.
- the MM sublayer provides services to the SM, SS and GSMS entities of the CM. The MM sublayer includes one GMM entity;
- the CM sublayer includes the SM, SS and GSMS entities. The SM entity provides services to the RABM entity and uses services of the MM sublayer. The GSMS entity is identical to the SMS entity for GPRS services in GSM except it uses the services from the GMM sublayer. The SS entity is identical to the one for non-GPRS services except it uses the services from the LLC or PS signalling connection;
- the RABM hides the concepts of RABs that can be activated/released while a PDP context is active. If UL data in the terminal is to be sent on a RAB (NSAPI) that has been released the RABM will trigger a service request procedure in GMM.
Figure 5.6 defines three sublayers for UMTS CS domain services and UMTS PS domain services supporting CS/PS mode of operation MSs:
- the Access Stratum (AS) sublayer provides services to the MM sublayer and the RAB Manager (RABM) entity;
- the MM sublayer provides services to the entities of the Connection Management (CM) sublayer. In addition to the MM entity for CS domain services, the MM sublayer further includes one GMM entity;
- the CM sublayer includes, among others, the CC, SS, GSMS and SM entities, which are independent entities;
- the SM entity provides services to the RABM entity and uses services of the MM sublayer.
The GSMS entity is an extension of the SMS entity for CS domain services. For message transfer it uses the services both from the GMM entity of the MM sublayer and the MM entity of the MM sublayer. Furthermore it retrieves from the MM entity information about which transport service to use;
- the RABM hides the concepts of RABs that can be activated/released while a PDP context is active. If UL data in the terminal is to be sent on a RAB (NSAPI) that has been released, the RABM will trigger a service request procedure in GMM.
Figure 5.7 defines three sublayers for EPS PS domain services:
- the Access Stratum (AS) sublayer provides services to the MM sublayer;
- the MM sublayer provides services to the entities of the Connection Management (CM) sublayer. The MM sublayer further includes one EMM entity;
- the CM sublayer includes ESM entities;
- the ESM entity provides services to the Bearer Control (BC) entity and uses services of the MM sublayer;
- the BC entity hides the concepts of radio bearers that can be established/released while an EPS bearer context is active. If uplink data in the terminal is to be sent, and radio bearers have been released, the BC will trigger a service request procedure in EMM.
Figure 5.8 defines three sublayers for EPS domain services and non-EPS domain services supporting CS/PS mode 1 or CS/PS mode 2 of operation MSs:
- the Access Stratum (AS) sublayer provides services to the MM sublayer;
- the MM sublayer provides services to the entities of the Connection Management (CM) sublayer. In addition to the MM entity for non-EPS services, the MM sublayer further includes one EMM entity;
- the CM sublayer includes among others, the CC, SS, ESMS and ESM entities, which are independent entities;
- the ESM entity provides services to the Bearer Control (BC) entity and uses services of the MM sublayer.
The ESMS entity is an extension of the SMS entity for non-EPS services. For message transfer, it uses the services from the EMM entity of the MM sublayer;
- the BC entity hides the concepts of radio bearers that can be established/released while an EPS bearer context is active. If uplink data in the MS is to be sent, and all radio bearers have been released, the BC will trigger a service request procedure in EMM.
Figure 5.9 defines three sublayers for 5GS services:
- the NR or E-UTRA AS sublayer provides services to the 5GMM sublayer;
- the 5GMM sublayer provides services to the entities of the 5GCM sublayer. The 5GMM sublayer further includes one 5GMM entity;
- the 5GCM sublayer includes 5GSM entities;
- the 5GSM entity provides services to the QoS flow control (QFC) entity and uses services of the 5GMM sublayer;
- the QFC entity hides the concepts of radio resources that can be established, released or suspended while a 5GS context is active. If uplink data in the terminal is to be sent, and 5GS radio resources have been released or suspended, the QFC will notify 5GMM.
Figure 5.10 defines three sublayers for 5GS services:
- the Non-3GPP access stratum sublayer provides services to the 5GMM sublayer;
- the 5GMM sublayer provides services to the entities of the 5GCM sublayer. The 5GMM sublayer further includes one 5GMM entity;
- the 5GCM sublayer includes 5GSM entities;
- the 5GSM entity provides services to the QoS flow control (QFC) entity and uses services of the 5GMM sublayer;
- the QFC entity hides the concepts of non-3GPP access resources that can be established/released while a 5GS context is active. Whenever such resources are available, IPSec security associations will be established and maintained. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6 Services provided by signalling layer 3 at the MS side | The different classes of services provided by signalling layer 3 at the MS side are accessible at the following service access points:
- registration services at the MMREG-SAP or GMMREG-SAP;
- Call Control services for normal and emergency calls including call related Supplementary Services Support services at the MNCC-SAP;
- Short Message Services Support services at the MNSMS-SAP;
- Call independent Supplementary Services Support services at the MNSS-SAP;
- Location Services Support services at the MNLCS-SAP;
- other services corresponding to further functional blocks of the CM sublayer at the appropriate service access points. These services are not further described in this clause;
- Session Management services at the SMREG-SAP and at the SNSM-SAP;
- Logical Link Control services at the QoS1-SAP, QoS2-SAP, QoS3-SAP and QoS4-SAP. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.1 Registration services | The registration services (location updating, IMSI attach/detach) are provided at the service access point MMREG‑SAP. As opposed to all other MN‑Services, these services are provided by and can be directly accessed at the Mobility Management sublayer. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.1.1 Service state diagram for MS not supporting GPRS service | The registration services provided at the service access point MMREG‑SAP are illustrated in the state of figure 6.1 below.
Figure 6.1: Registration services provided at MMREG‑SAP ‑ MS side |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.1.2 Service primitives | Table 6.1: Primitives and Parameters at the MMREG‑SAP ‑ MS side
PRIMITIVE
PARAMETER
REFERENCE
MMR_REG_REQ
IMSI
6.1.2.1
MMR_REG_CNF
‑
6.1.2.2
MMR_NREG_REQ
‑
6.1.2.4
MMR_NREG_IND
cause
6.1.2.5 |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.1.2.1 MMR_REG_REQ | Registration request, triggered by activation of the IMSI, e.g., by activation of the MS with inserted SIM, insertion of the SIM into the activated MS, pressing of a reset button. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.1.2.2 MMR_REG_CNF | Registration confirmation. Indicates to the user that the MS is ready to start a transaction. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.1.2.3 Void | |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.1.2.4 MMR_NREG_REQ | Request to cancel the registration, stimulated either by removing the SIM or automatically in the power off phase. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.1.2.5 MMR_NREG_IND | Indication that registration has been cancelled or that registration was not possible. Only emergency services are available to the user. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.1.3 Registration Services for CTS-Services | The registration services (attach/detach, enrolment/de-enrolment) are provided for CTS services at the service access point MMREG‑SAP.
Table 6.1.3: Primitives and Parameters at the MMREG‑SAP ‑ MS side for CTS
PRIMITIVE
PARAMETER
REFERENCE
MMR_CTS_ATTACH_REQ
IMSI
6.1.3.1
MMR_CTS_ATTACH_CNF
‑
6.1.3.2
MMR_CTS_ATTACH_REJ
IFPSI, cause
6.1.3.3
MMR_CTS_DETACH_IND
‑
6.1.3.4
MMR_CTS_ENROLL_REQ
IMSI
6.1.3.5
MMR_CTS_ENROLL_CNF
‑
6.1.3.6
MMR_CTS_ENROLL_REJ
IFPSI, cause
6.1.3.7
MMR_CTS_
DE_ENROLL_IND
‑
6.1.3.8 |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.1.3.1 MMR_CTS _ATTACH_REQ | MS initiates the CTS attach. CTS‑MM is requested to send a CTS ATTACH REQUEST message to the fixed part. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.1.3.2 MMR_CTS _ATTACH_CNF | The CTS attach was successful. The fixed part confirmed the attach, i.e. the CTS ATTACH ACCEPT message was received by the MS. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.1.3.3 MMR_CTS _ATTACH_REJ | The CTS attach has failed. The fixed part rejected the attach attempt, i.e. the CTS ATTACH REJECT message was received by the MS. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.1.3.4 MMR_CTS _DETACH_IND | MS initiates CTS detach. CTS‑MM is requested to send a CTS DETACH INDICATION message. The detach procedure is initiated. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.1.3.5 MMR_CTS _ENROLL_REQ | MS initiates the CTS enrolment. CTS‑MM is requested to send a CTS ENROLMENT REQUEST message to the fixed part. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.1.3.6 MMR_CTS _ENROLL_CNF | The CTS enrolment was successful. The fixed part confirmed the enrolment, i.e. the CTS ENROLMENT ACCEPT message was received by the MS. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.1.3.7 MMR_CTS _ENROLL_REJ | The CTS enrolment has failed. The fixed part rejected the enrolment attempt, i.e. the CTS ENROLMENT REJECT message was received by the MS. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.1.3.8 MMR_CTS _DE_ENROLL_IND | FP initiates CTS de-enrolment. CTS‑MM is requested to send a CTS DE-ENROLMENT INDICATION message. The de-enrolment procedure is initiated. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.2 Call Control services | The Call Control services are provided by multiple CC entities at the service access point MNCC‑SAP.
The Call Control service class consists of the following services:
- Mobile originated and Mobile terminated call establishment for normal calls;
- Mobile originated call establishment for emergency calls;
- call maintaining;
- call termination;
- call related Supplementary Services Support. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.2.1 Service state diagram | The Call Control services provided at the service access point MNCC‑SAP are illustrated in the state diagram of figure 6.2.
Figure 6.2: Service graph of Call Control entity ‑ MS side (page 1 of 2)
Figure 6.2: Service graph of Call Control entity ‑ MS side Active state (page 2 of 2) |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.2.2 Service primitives | Table 6.2: Primitives and parameters at MNCC‑SAP ‑ MS side
PRIMITIVE
PARAMETER
(message, info elements of message, other parameters)
REFERENCE
MNCC_SETUP_REQ
SETUP or EMERGENCY SETUP
6.2.2.1
MNCC_SETUP_IND
SETUP
6.2.2.2
MNCC_SETUP_RSP
CONNECT
6.2.2.3
MNCC_SETUP_CNF
CONNECT
6.2.2.4
MNCC_SETUP_COMPLETE_REQ
‑
6.2.2.5
MNCC_SETUP_COMPLETE_IND
‑
6.2.2.6
MNCC_REJ_REQ
RELEASE COMPLETE
6.2.2.7
MNCC_REJ_IND
cause
6.2.2.8
MNCC_CALL_CONF_REQ
CALL CONFIRMED
6.2.2.9
MNCC_CALL PROC_IND
CALL PROCEEDING
6.2.2.10
MNCC_PROGRESS_IND
PROGRESS
6.2.2.11
MNCC_ALERT_REQ
ALERTING
6.2.2.12
MNCC_ALERT_IND
ALERTING
6.2.2.13
MNCC_NOTIFY_REQ
NOTIFY
6.2.2.14
MNCC_NOTIFY_IND
NOTIFY
6.2.2.15
MNCC_DISC_REQ
DISCONNECT
6.2.2.16
MNCC_DISC_IND
DISCONNECT
6.2.2.17
MNCC_REL_REQ
RELEASE
6.2.2.18
MNCC_REL_IND
RELEASE
6.2.2.19
MNCC_REL_CNF
RELEASE or RELEASE COMPLETE
6.2.2.20
MNCC_FACILITY_REQ
facility
6.2.2.21
MNCC_FACILITY_IND
facility
6.2.2.22
MNCC_START_DTMF_REQ
START DTMF
6.2.2.23
MNCC_START_DTMF_CNF
START DTMF ACK or START DTMF REJ
6.2.2.24
MNCC_STOP_DTMF_REQ
STOP DTMF
6.2.2.25
MNCC_STOP_DTMF_CNF
STOP DTMF ACK
6.2.2.26
MNCC_MODIFY_REQ
MODIFY
6.2.2.27
MNCC_MODIFY_IND
MODIFY
6.2.2.28
MNCC_MODIFY_RES
MODIFY COMPLETE
6.2.2.29
MNCC_MODIFY_CNF
MODIFY COMPLETE
6.2.2.30
MNCC_SYNC_IND
cause (res. ass., channel mode modify)
6.2.2.31 |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.2.2.1 MNCC_SETUP_REQ | Request to send a SETUP or EMERGENCY SETUP message to initiate Mobile originating establishment of either a normal or an emergency call. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.2.2.2 MNCC_SETUP_IND | Receipt of a SETUP message, the Mobile terminated call establishment has been initiated. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.2.2.3 MNCC_SETUP_RES | Response to send a CONNECT message to indicate call acceptance by the Mobile terminated user; call control is requested to attach the user connection (if it is not yet attached). |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.2.2.4 MNCC_SETUP_CNF | Receipt of a CONNECT message, the Mobile originated call has been accepted by the remote called user. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.2.2.5 MNCC_SETUP_COMPL_REQ | Request to send a CONNECT ACKNOWLEDGE message, the mobile originating call has been accepted. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.2.2.6 MNCC_SETUP_COMPL_IND | Receipt of a CONNECT ACKNOWLEDGE message, the Mobile terminated call establishment has been completed; for a data call, the user is informed that the user connection is attached. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.2.2.7 MNCC_REJ_REQ | Request to reject a Mobile terminated call if the call is refused or if the call cannot be accepted, e.g., because of missing compatibility. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.2.2.8 MNCC_REJ_IND | Indication that the Mobile originated call has been rejected, e.g. if the MM connection cannot be provided or if the call establishment initiation has been rejected by the network. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.2.2.9 MNCC_CALL_CONF_REQ | Request to confirm a Mobile terminated call by sending a CALL CONFIRMED message. A bearer capability different from that given in MNCC_SETUP_IND may be offered to the remote calling user. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.2.2.10 MNCC_CALL_PROC_IND | Indication to the Mobile originating user that call establishment has been initiated in the Network and no more call establishment information will be accepted by the Network. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.2.2.11 MNCC_PROGRESS_IND | Indication to the Mobile user that a PROGRESS message or a message containing a progress IE has been received, e.g., because the call is progressing in the PLMN/ISDN environment, or because the call has left the PLMN/ISDN environment, or because in‑band tones/announcement are available. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.2.2.12 MNCC_ALERT_REQ | Request to send an ALERTING message from the called Mobile user to the remote calling user to indicate that user alerting has been initiated. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.2.2.13 MNCC_ALERT_IND | Indication of the receipt of an ALERTING message, alerting to the remote called user has been initiated. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.2.2.14 MNCC_NOTIFY_REQ | Request to send information pertaining to a call, such as user suspended, to the Network by the Mobile user. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.2.2.15 MNCC_NOTIFY_IND | Indication to the Mobile user that information pertaining to a call, such as remote user suspended, has been received from the Network. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.2.2.16 MNCC_DISC_REQ | Request to send a DISCONNECT message to the Network in order to clear the end‑to‑end connection. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.2.2.17 MNCC_DISC_IND | Indication of reception of a DISCONNECT message, by which the Network indicates that the end‑to‑end connection is cleared. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.2.2.18 MNCC_REL_REQ | Request of the Mobile user to send a RELEASE message to inform the Network that the user intends to release the call reference and the corresponding MM connection so that the Network can release its MM connection and the correspondent call reference. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.2.2.19 MNCC_REL_IND | Indication to the Mobile originating or terminated user that a RELEASE message has been received and the Network intends to release its MM connection. The Mobile user is requested to release the call reference and the corresponding MM connection. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.2.2.20 MNCC_REL_CNF | Confirmation of the Mobile user's request to release the MM connection and call reference in the Network. The Mobile user may release the call reference and the corresponding MM connection. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.2.2.21 MNCC_FACILITY_REQ | Request to transport a facility IE for a call related supplementary service invocation. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.2.2.22 MNCC_FACILITY_IND | Indication that a facility IE for a call related supplementary service invocation has been received. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.2.2.23 MNCC_START_DTMF_REQ | Request to send a START DTMF message in order to start a DTMF control operation. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.2.2.24 MNCC_START_DTMF_CNF | Confirmation of the receipt of a START DTMF ACKNOWLEDGE or START DTMF REJECT message that the start of a DTMF control operation has been acknowledged or rejected. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.2.2.25 MNCC_STOP_DTMF_REQ | Request to send a STOP DTMF message in order to stop a DTMF control operation. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.2.2.26 MNCC_STOP_DTMF_CNF | Confirmation of the receipt of STOP DTMF ACKNOWLEDGE message, the DTMF control operation has been stopped. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.2.2.27 MNCC_MODIFY_REQ | Request to start Mobile originating in‑call modification by sending a MODIFY message. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.2.2.28 MNCC_MODIFY_IND | RECEIPT OF A MODIFY message, a Mobile terminating in‑call modification has been initiated. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.2.2.29 MNCC_MODIFY_RES | Response to send a MODIFY COMPLETE message to indicate Mobile terminating in‑call modification completion by the Mobile user. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.2.2.30 MNCC_MODIFY_CNF | Receipt of a MODIFY COMPLETE message, the Mobile originating in‑call modification has been completed. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.2.2.31 MNCC_SYNC_IND | Indication that a dedicated channel assignment has been performed (res. ass. = "resource assigned") and/or the channel mode has been changed. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.3 Call independent Supplementary Services Support | |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.3.1 Service state diagram | The primitives provided by the call independent Supplementary Services Support entity and the transitions between permitted states are shown in figure 6.3.
STATES:
IDLE ‑ No SS signalling transaction pending.
CONN ‑ SS signalling transaction established.
Figure 6.3: Service graph of the call independent Supplementary Services Support entity ‑ MS side |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.3.2 Service primitives | Table 6.3: Primitives and Parameters at MNSS‑SAP ‑ MS side
PRIMITIVES
PARAMETERS
(Info elements of message)
REFERENCE
MNSS_BEGIN_REQ
REGISTER
6.3.2.1
MNSS_BEGIN_IND
REGISTER
6.3.2.2
MNSS_FACILITY_REQ
FACILITY
6.3.2.3
MNSS_FACILITY_IND
FACILITY
6.3.2.4
MNSS_END_REQ
REL COMPLETE
6.3.2.5
MNSS_END_IND
REL COMPLETE
6.3.2.6 |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.3.2.1 MNSS_BEGIN_REQ | Request to send a REGISTER message in order to establish a signalling transaction for the provision of call independent supplementary services. The request for a call independent supplementary service invocation may be included. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.3.2.2 MNSS_BEGIN_IND | Receipt of a REGISTER message, a signalling transaction is established for the provision of call independent supplementary services after receipt of a REGISTER message. The indication of a supplementary service invocation may be included. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.3.2.3 MNSS_FACILITY_REQ | Request to send a FACILITY message for the provision of a call independent supplementary service invocation. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.3.2.4 MNSS_FACILITY_IND | Receipt of a FACILITY message for a call independent supplementary service invocation. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.3.2.5 MNSS_END_REQ | Request to send a RELEASE COMPLETE message in order to release the signalling transaction. The request for transfer of a supplementary service facility may be included. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.3.2.6 MNSS_END_IND | Receipt of a RELEASE COMPLETE message, the signalling transaction has been released. The indication of a supplementary service facility may be included. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.4 Short Message Services Support | The service provided by the CM sublayer to support the short message service are defined in
3GPP TS 24.011 [8]. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.5 Session Management Services for GPRS-Services | Session Management services are provided at the SMREG-SAP and the SNSM-SAP. The procedures for GPRS Session Management (i.e. PDP context activation, PDP context deactivation and PDP context modification) and MBMS Session Management (i.e. MBMS context activation and MBMS context deactivation) are available at the SMREG-SAP.
Before any user data transfer is initiated (eg.via SNDCP in GSM case), the PDP context activation procedure must be performed. In case of MBMS, the MS must also perform the procedures needed in order to activate a multicast service. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.5.1 Session Management Services for SMREG-SAP | Table 6.5.1: Primitives and Parameters at SMREG-SAP - MS side
PRIMITIVE
PARAMETER
(message, info elements of message, other parameters)
REFERENCE
SMREG-PDP-ACTIVATE-REQ
PDP address, QoS, NSAPI, APN, Protocol configuration options
6.5.1.1
SMREG-PDP-ACTIVATE-CNF
PDP address, QoS, NSAPI, Protocol configuration options
6.5.1.2
SMREG-PDP-ACTIVATE-REJ
Cause, NSAPI, Protocol configuration options
6.5.1.3
SMREG-PDP-ACTIVATE-IND
PDP address, APN, protocol configuration options
6.5.1.4
SMREG-PDP-ACTIVATE-REJ-RSP
Cause, PDP address, APN, protocol configuration options, MBMS protocol configuration options
6.5.1.14
SMREG-PDP-DEACTIVATE-REQ
NSAPI(s) tear down indicator, cause, protocol configuration options, MBMS protocol configuration options
6.5.1.5
SMREG-PDP-DEACTIVATE-CNF
NSAPI(s), protocol configuration options, MBMS protocol configuration options
6.5.1.6
SMREG-PDP-DEACTIVATE-IND
NSAPI(s) (s), tear down indicator, cause, protocol configuration options, MBMS protocol configuration options
6.5.1.7
SMREG-PDP-MODIFY-IND
QoS, NSAPI, protocol configuration options
6.5.1.8
SMREG-PDP-MODIFY-REQ
QoS, NSAPI, TFT, protocol configuration options
6.5.1.18
SMREG-PDP-MODIFY-CNF
QoS, NSAPI, protocol configuration options
6.5.1.19
SMREG-PDP-MODIFY-REJ
Cause, NSAPI, protocol configuration options
6.5.1.20
SMREG-PDP-ACTIVATE-SEC-REQ
QoS, NSAPI, TFT, Primary NSAPI, protocol configuration options
6.5.1.15
SMREG-PDP-ACTIVATE-SEC-CNF
QoS, NSAPI, protocol configuration options
6.5.1.16
SMREG-PDP-ACTIVATE-SEC-REJ
Cause, NSAPI, protocol configuration options
6.5.1.17
SMREG-MBMS-ACTIVATE-REQ
Multicast address, supported MBMS bearer capabilities, NSAPI, APN, MBMS protocol configuration options
6.5.1.21
SMREG-MBMS-ACTIVATE-CNF
Multicast address, NSAPI, MBMS protocol configuration options
6.5.1.22
SMREG-MBMS-ACTIVATE-REJ
Cause, NSAPI, MBMS protocol configuration options
6.5.1.23
SMREG-MBMS-ACTIVATE-IND
Multicast address, APN, MBMS protocol configuration options
6.5.1.24 |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.5.1.1 SMREG-PDP-ACTIVATE-REQ | The MS initiates a primary PDP context activation. SM is requested to send the ACTIVATE PDP CONTEXT REQUEST message to the network. The PDP context is pending activation. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.5.1.2 SMREG-PDP-ACTIVATE-CNF | The MS initiated primary PDP context activation succeeded. The network confirmed the PDP context activation, i.e. the ACTIVATE PDP CONTEXT ACCEPT message was received from the network. In GSM, this implies that SM has ordered SNDCP to establish the needed LLC link. In the UMTS case, this implies that the RLC link towards the RNC has been established and that the SM has been informed about this from the RABM service entity in the MS. (RABM- RAB Management service entity is FFS and could lead to update of the protocol architecture in figure 5.2 and 5.3) The PDP context is active. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.5.1.3 SMREG-PDP-ACTIVATE-REJ | The PDP primary context activation failed, the PDP context is not activated. One reason for failure is that the network rejected the activation attempt, which means the ACTIVATE PDP CONTEXT REJECT message was received. Another reason is e.g. that it was not possible to establish the needed LLC link in the GSM case. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.5.1.4 SMREG-PDP-ACTIVATE-IND | The network asked for a PDP context activation. The REQUEST PDP CONTEXT ACTIVATION message was received from the network. The MS reacts either by initiating a new primary PDP context activation or by rejecting the network's request. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.5.1.5 SMREG-PDP-DEACTIVATE-REQ | The MS initiates a PDP context deactivation: SM is requested to send a DEACTIVATE PDP CONTEXT REQUEST message to the network. The PDP context is pending deactivation. Presence of the teardown indicator will lead to deactivation of all PDP contexts coupled to the identified PDP address. NSAPI(s) to be deallocated from the SNDCP entity via the SNSM-SAP for the GSM case, are included in the primitive. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.5.1.6 SMREG-PDP-DEACTIVATE-CNF | The MS initiated PDP context deactivation has been done. The network confirmed the PDP context deactivation, i.e. the DEACTIVATE PDP CONTEXT ACCEPT message was received from the network. For GSM SM has ordered SNDCP to locally release not further needed LLC links. In the UMTS case, the release of the RLC link towards the RNC takes place as a result of a RAB release trigger from the network side. SM has been informed about this from the RABM service entity in the MS. (RABM- RAB Management service entity is FFS and could lead to update of the protocol architecture in figure 5.2 and 5.3.) The PDP context has been deactivated. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.5.1.7 SMREG-PDP-DEACTIVATE-IND | A network initiated PDP context deactivation has been performed. The DEACTIVATE PDP CONTEXT REQUEST message has been received from the network. The MS has acknowledged with the DEACTIVATE PDP CONTEXT ACCEPT message. The PDP context has been deactivated, the related LLC links in GSM or RLC links in UMTS were locally released. Presence of the teardown indicator will lead to deactivation of all PDP contexts coupled to the identified PDP address. NSAPI is included in the primitive to allow identification of the PDP context(s) needing deactivation. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.5.1.8 SMREG-PDP-MODIFY-IND | A network initiated PDP context modification has been performed. The MODIFY PDP CONTEXT REQUEST message has been received from the network. The modification has been acknowledged by sending the MODIFY PDP CONTEXT ACCEPT message. One PDP context has been modified. LLC links is adjusted. |
bbc07dc9647184161b1f5af7180e8116 | 24.007 | 6.5.1.9 Void |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.