hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
e7022876aaebc1074115c0f4962825be | 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.
|
e7022876aaebc1074115c0f4962825be | 21.900 | 8 E‑mail decisions
| |
e7022876aaebc1074115c0f4962825be | 21.900 | 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 hav... |
e7022876aaebc1074115c0f4962825be | 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 It... |
e7022876aaebc1074115c0f4962825be | 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 ... |
e7022876aaebc1074115c0f4962825be | 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 befor... |
e7022876aaebc1074115c0f4962825be | 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.
|
e7022876aaebc1074115c0f4962825be | 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.
|
e7022876aaebc1074115c0f4962825be | 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;... |
e7022876aaebc1074115c0f4962825be | 21.900 | 9 Meeting contribution document types and status values
| |
e7022876aaebc1074115c0f4962825be | 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... |
e7022876aaebc1074115c0f4962825be | 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 r... |
d569219f924e19aa434b82e7c8e6973b | 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-... |
d569219f924e19aa434b82e7c8e6973b | 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.
-... |
d569219f924e19aa434b82e7c8e6973b | 24.007 | 3 Definitions and abbreviations
| |
d569219f924e19aa434b82e7c8e6973b | 24.007 | 3.1 Definitions
| For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1a] apply.
|
d569219f924e19aa434b82e7c8e6973b | 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 ... |
d569219f924e19aa434b82e7c8e6973b | 24.007 | 4 Introduction
| |
d569219f924e19aa434b82e7c8e6973b | 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 combin... |
d569219f924e19aa434b82e7c8e6973b | 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. ... |
d569219f924e19aa434b82e7c8e6973b | 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.
|
d569219f924e19aa434b82e7c8e6973b | 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 ... |
d569219f924e19aa434b82e7c8e6973b | 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].
|
d569219f924e19aa434b82e7c8e6973b | 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 (co... |
d569219f924e19aa434b82e7c8e6973b | 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 S... |
d569219f924e19aa434b82e7c8e6973b | 24.007 | 5 Structure of layer 3 functions
| |
d569219f924e19aa434b82e7c8e6973b | 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... |
d569219f924e19aa434b82e7c8e6973b | 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 wou... |
d569219f924e19aa434b82e7c8e6973b | 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 MN... |
d569219f924e19aa434b82e7c8e6973b | 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.
|
d569219f924e19aa434b82e7c8e6973b | 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
|
d569219f924e19aa434b82e7c8e6973b | 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
|
d569219f924e19aa434b82e7c8e6973b | 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.
|
d569219f924e19aa434b82e7c8e6973b | 24.007 | 6.1.2.2 MMR_REG_CNF
| Registration confirmation. Indicates to the user that the MS is ready to start a transaction.
|
d569219f924e19aa434b82e7c8e6973b | 24.007 | 6.1.2.3 Void
| |
d569219f924e19aa434b82e7c8e6973b | 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.
|
d569219f924e19aa434b82e7c8e6973b | 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.
|
d569219f924e19aa434b82e7c8e6973b | 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_A... |
d569219f924e19aa434b82e7c8e6973b | 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.
|
d569219f924e19aa434b82e7c8e6973b | 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.
|
d569219f924e19aa434b82e7c8e6973b | 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.
|
d569219f924e19aa434b82e7c8e6973b | 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.
|
d569219f924e19aa434b82e7c8e6973b | 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.
|
d569219f924e19aa434b82e7c8e6973b | 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.
|
d569219f924e19aa434b82e7c8e6973b | 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.
|
d569219f924e19aa434b82e7c8e6973b | 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.
|
d569219f924e19aa434b82e7c8e6973b | 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 ma... |
d569219f924e19aa434b82e7c8e6973b | 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)
|
d569219f924e19aa434b82e7c8e6973b | 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_R... |
d569219f924e19aa434b82e7c8e6973b | 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.
|
d569219f924e19aa434b82e7c8e6973b | 24.007 | 6.2.2.2 MNCC_SETUP_IND
| Receipt of a SETUP message, the Mobile terminated call establishment has been initiated.
|
d569219f924e19aa434b82e7c8e6973b | 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).
|
d569219f924e19aa434b82e7c8e6973b | 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.
|
d569219f924e19aa434b82e7c8e6973b | 24.007 | 6.2.2.5 MNCC_SETUP_COMPL_REQ
| Request to send a CONNECT ACKNOWLEDGE message, the mobile originating call has been accepted.
|
d569219f924e19aa434b82e7c8e6973b | 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.
|
d569219f924e19aa434b82e7c8e6973b | 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.
|
d569219f924e19aa434b82e7c8e6973b | 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.
|
d569219f924e19aa434b82e7c8e6973b | 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.
|
d569219f924e19aa434b82e7c8e6973b | 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.
|
d569219f924e19aa434b82e7c8e6973b | 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.
|
d569219f924e19aa434b82e7c8e6973b | 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.
|
d569219f924e19aa434b82e7c8e6973b | 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.
|
d569219f924e19aa434b82e7c8e6973b | 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.
|
d569219f924e19aa434b82e7c8e6973b | 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.
|
d569219f924e19aa434b82e7c8e6973b | 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.
|
d569219f924e19aa434b82e7c8e6973b | 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.
|
d569219f924e19aa434b82e7c8e6973b | 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.
|
d569219f924e19aa434b82e7c8e6973b | 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.
|
d569219f924e19aa434b82e7c8e6973b | 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.
|
d569219f924e19aa434b82e7c8e6973b | 24.007 | 6.2.2.21 MNCC_FACILITY_REQ
| Request to transport a facility IE for a call related supplementary service invocation.
|
d569219f924e19aa434b82e7c8e6973b | 24.007 | 6.2.2.22 MNCC_FACILITY_IND
| Indication that a facility IE for a call related supplementary service invocation has been received.
|
d569219f924e19aa434b82e7c8e6973b | 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.
|
d569219f924e19aa434b82e7c8e6973b | 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.
|
d569219f924e19aa434b82e7c8e6973b | 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.
|
d569219f924e19aa434b82e7c8e6973b | 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.
|
d569219f924e19aa434b82e7c8e6973b | 24.007 | 6.2.2.27 MNCC_MODIFY_REQ
| Request to start Mobile originating in‑call modification by sending a MODIFY message.
|
d569219f924e19aa434b82e7c8e6973b | 24.007 | 6.2.2.28 MNCC_MODIFY_IND
| RECEIPT OF A MODIFY message, a Mobile terminating in‑call modification has been initiated.
|
d569219f924e19aa434b82e7c8e6973b | 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.
|
d569219f924e19aa434b82e7c8e6973b | 24.007 | 6.2.2.30 MNCC_MODIFY_CNF
| Receipt of a MODIFY COMPLETE message, the Mobile originating in‑call modification has been completed.
|
d569219f924e19aa434b82e7c8e6973b | 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.
|
d569219f924e19aa434b82e7c8e6973b | 24.007 | 6.3 Call independent Supplementary Services Support
| |
d569219f924e19aa434b82e7c8e6973b | 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 Supplem... |
d569219f924e19aa434b82e7c8e6973b | 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
... |
d569219f924e19aa434b82e7c8e6973b | 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.
|
d569219f924e19aa434b82e7c8e6973b | 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.
|
d569219f924e19aa434b82e7c8e6973b | 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.
|
d569219f924e19aa434b82e7c8e6973b | 24.007 | 6.3.2.4 MNSS_FACILITY_IND
| Receipt of a FACILITY message for a call independent supplementary service invocation.
|
d569219f924e19aa434b82e7c8e6973b | 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.
|
d569219f924e19aa434b82e7c8e6973b | 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.
|
d569219f924e19aa434b82e7c8e6973b | 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].
|
d569219f924e19aa434b82e7c8e6973b | 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-... |
d569219f924e19aa434b82e7c8e6973b | 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 op... |
d569219f924e19aa434b82e7c8e6973b | 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.
|
d569219f924e19aa434b82e7c8e6973b | 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 towar... |
d569219f924e19aa434b82e7c8e6973b | 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.
|
d569219f924e19aa434b82e7c8e6973b | 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.
|
d569219f924e19aa434b82e7c8e6973b | 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 t... |
d569219f924e19aa434b82e7c8e6973b | 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 t... |
d569219f924e19aa434b82e7c8e6973b | 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 rel... |
d569219f924e19aa434b82e7c8e6973b | 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.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.