hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 8.11.1 Description | This solution provides the procedure on configuration of application layer caller information on MMTel Enabler server. The configured application layer caller information will be shown to the callee by using the procedure in solution#10.
NOTE: In this release,application layer caller information only applies to the cal... |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 8.11.2 Procedures | The procedure of onfiguration of application layer caller information on MMTel Enabler server is illustrated in figure 8.11.2-1.
Pre-conditions:
1) The Application Server has connected to the serving network successfully.
2). Both the Application Serverand MMTel Enabler Server have been configured with the necessary cr... |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 8.11.3 Impacts on Existing Nodes and Functionality | This solution detailed specified the procedures of configuration of application layer caller information. If the application layer caller information is not needed to be configured in HSS repository data via the NEF, there is no impacts on existing nodes and functionality. Otherwise, the capabilities provided by HSS, e... |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 8.12 Solution #x: MMTel Enabler layer adaptation to CAPIF | |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 8.12.1 Description | This solution provides the MMTel Enabler layer architecture adaptation to CAPIF. This solution is the addition of Solution#01. |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 8.12.2 Procedures | The MMTel Enabler layer architecture may support CAPIF. The MMTel Enabler layer adaptation to CAPIF is illustrated in Figure 8.12.2-1.
Figure 8.12.2-1: MMTel Enabler layer adaptation to CAPIF
When CAPIF is supported:
- the MMTel Enabler Server act as CAPIF API provider domain functions as specified in 3GPP TS 23.222 [9... |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 8.12.3 Impacts on Existing Nodes and Functionality | This solution provides a deployment option for MMTel Enabler layer architecture adaptation to CAPIF. This solution has no impact on 5GC/IMS.
8.13 Solution #13: data channel application related capability exposure
8.13.1 Description
This clause provides solution against Key Issue #7 Support of data channel application r... |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 9 Deployment Guideline | |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 9.1 General | This clause describes deployments of the functional model specified in clause 8.1. |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 9.2 eMMTel Enabler server deployed in PLMN operator domain | The eMMTel Enabler server is recommended to be deployed in the PLMN operator domain. Figure 9.2-1 illustrates the eMMTel Enabler server deployed in PLMN operator domain.
Figure 9.2-1: eMMTel Enabler server deployed in PLMN operator domain
The Application server can be deployed in PLMN operator domain or Application ser... |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 9.3 eMMTel Enabler server deployed in trusted 3rd party call service provider domain | The eMMTel Enabler server can also be deployed in the trusted 3rd party call service provider domain based on the business agreement between PLMN operator and 3rd party call service provider domain. The 3rd party call service provider is a specific Application service provider which provides the enablement of MMTel ser... |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 10 Overall evaluation | |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 10.1 General | This clause will provide the mapping between KIs and solutions. Evaluation of different solutions. will be also captured in this clause. |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 10.2 Mapping of Solutions to Key Issues | Table 10.2-1: Mapping of Solutions to Key Issues
Key Issues
Solutions
1
2
3
4
5
6
7
8
1
2
X
X
3
X
4
X
5
X
6
X
7
X
X
X
8
X
9
X
X
10
X
11
X
12
13
X |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 10.3 Solution evaluation | |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 10.3.1 Key issue #1: Application calling service based on eMMTel service | The open issues of this KI are as follows:
1. Identify whether and how to provide API based Call control capabilities utilizing architecture and procedure provide by IMS subsystem. The control capabilities include the creation, updating, and terminating of a call which includes audio, video and Data Channel.
To address... |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 10.3.2 Key issue #2: Download data channel application to UE | The open issues of this KI are as follows:
1. The application layer should support to provide the capability of indicating how to handle the downloading and processing of a specific data channel application on UE based on the service requirement of the specific data channel application and MNO.
2. The application layer... |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 10.3.3 Key issue #3: support of eMMTel call between application with IMS capability and application without IMS capability | The open issues of this KI are as follows:
1. The architecture, necessary functionalities and procedures of the eMMTel Enabler to support the eMMTel call between application with IMS capability and application without IMS capability.
2. The necessary service APIs on eMMTel Enabler to support the application without IMS... |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 10.3.4 Key issue #4: support of providing application layer caller information to callee | The open issues of this KI are as follows:
1. Analyze whether the existing application layer service capabilities can be used by eMMTel Enabler layer to support providing application layer caller information to callee;
2. How to manage the application layer caller information, e.g. provide the capability to configure t... |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 10.3.5 Key issue #5: Support of virtual number | The open issues of this KI are as follows:
1. How to manage the virtual number in eMMTel Enabler layer, e.g. how to assign a virtual number(s) on demand of a user in one or multiple requested mode.
2. How to maintain the relationship between the virtual number and real number in the requested mode(s) and the related nu... |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 10.3.6 Key issue #6: Multiple call control handling coordination among different Application Servers | The open issues of this KI are as follows:
1. how to support call control handling among different Application Servers in eMMTel Enabler layer:
2. Analyze whether and how the eMMTel Enabler layer can be enhanced to support call control handling.
To address the open issues, only one solution, i.e. solution#08, has been ... |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 10.3.8 Key issue #8: Supporting the multiparty service with the data channel capability | The open issues of this KI are as follows:
1. Analyze what and how the eMMTel service enabler layer provides multiparty services to application providers and vertical service providers.
2. How to provide API based multiparty service capabilities utilizing architecture and procedure provide by IMS subsystem.
To address ... |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 11 Conclusions | |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 11.1 Conclusion of KI#1 | For KI#1 on "Application calling service based on eMMTel service" the following conclusions are agreed:
1. Scenarios including call service between application and UE and call service between UE and UE in this Release.
2. procedures including establishing a call with data channel media, terminating a call with data cha... |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 11.2 Conclusion of KI#2 | For KI#2 on "downloading of data channel application profiles to UE" the following conclusions are agreed:
1. The eMMTel Enabler provides the capability of indicating how to handle the downloading and processing of a specific data channel application on UE by providing data channel application profile to UE. The data c... |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 11.3 Conclusion of KI#3 | For KI#3 on "support of eMMTel call between application with IMS capability and application without IMS capability" the following conclusions are agreed:
1. Based on the gap analysis of OMA OneAPI framework in clause 4.2, IMS data channel is not supported by OMA API, therefore, a set of new APIs for MMTel enabler will ... |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 11.4 Conclusion of KI#4 | The KI#4 on "support of providing application layer caller information to callee" will not go to normative work in Rel-19. |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 11.5 Conclusion of KI#5 | For KI#5 on "Support of virtual number" the following conclusions are agreed:
1. The architecture and solution for this KI can be discussed in normative phase.
2. The architecture and solution for this KI should based on the capabilities provided by OMA APIs and new SA2 specified IMS DC capability APIs.
NOTE: How to us... |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 11.6 Conclusion of KI#6 | For KI#6 on "Multiple call control handling coordination among different Application Servers" the following conclusions are agreed:
1. The MMTel Enabler Server subscribes the call events on DCSF/IMS core on behalf of multiple Application Servers.
2. The MMTel Enabler server enables call control operations of a call ses... |
edb59e43467ea4e1c1b7a9f7cc829abd | 23.700-92 | 11.8 Conclusion of KI#8 | Based on the gap analysis of OMA OneAPI framework in clause 4.2, IMS data channel is not supported by OMA API, Therefore, for KI#8 on "Supporting the multiparty service with the data channel capability", a set of new APIs for MMTel enabler will be considered to be specified for technical specification based on the Solu... |
e9337f2b73429c082193983bf07185ba | 24.008 | 1 Scope | The present document specifies the procedures used at the radio interface core network protocols within the 3rd generation mobile telecommunications system and the digital cellular telecommunications system.
It specifies the procedures used at the radio interface (Reference Point Um or Uu, see 3GPP TS 24.002 [15] or 3G... |
e9337f2b73429c082193983bf07185ba | 24.008 | 1.1 Scope of the Technical Specification | The procedures currently described in this TS are for the call control of circuit-switched connections, session management for GPRS services, mobility management and radio resource management for circuit-switched and GPRS services.
3GPP TS 24.010 [21] contains functional procedures for support of supplementary services... |
e9337f2b73429c082193983bf07185ba | 24.008 | 1.2 Application to the interface structures | The procedures defined in the present document apply to the interface structures defined in 3GPP TS 44.003 [16] and 3GPP TS 25.301 [128]. They use the functions and services provided by lower layers defined in 3GPP TS 44.005 [18] and 3GPP TS 44.006 [19] or 3GPP TS 25.331 [23c], 3GPP TS 25.322 [19b] and 3GPP TS 25.321 [... |
e9337f2b73429c082193983bf07185ba | 24.008 | 1.3 Structure of layer 3 procedures | A building block method is used to describe the layer 3 procedures.
The basic building blocks are "elementary procedures" provided by the protocol control entities of the three sublayers, i.e. radio resource management, mobility management and connection management sublayer.
Complete layer 3 transactions consist of spe... |
e9337f2b73429c082193983bf07185ba | 24.008 | 1.4 Test procedures | Test procedures of the GSM radio interface signalling are described in 3GPP TS 51.010 [39] and 3GPP TS 51.02x series. |
e9337f2b73429c082193983bf07185ba | 24.008 | 1.5 Use of logical channels in A/Gb mode | The logical control channels are defined in 3GPP TS 45.002 [32]. In the following those control channels are considered which carry signalling information or specific types of user packet information:
i) Broadcast Control CHannel (BCCH): downlink only, used to broadcast Cell specific information;
ii) Synchronization CH... |
e9337f2b73429c082193983bf07185ba | 24.008 | 1.6 Overview of control procedures | |
e9337f2b73429c082193983bf07185ba | 24.008 | 1.6.1 List of procedures | The following procedures are specified in the present document:
a) Clause 4 specifies elementary procedures for Mobility Management:
- mobility management common procedures (subclause 4.3):
- TMSI reallocation procedure (subclause 4.3.1);
- authentication procedure (subclause 4.3.2);
- identification procedure (subclau... |
e9337f2b73429c082193983bf07185ba | 24.008 | 1.7 Applicability of implementations | The applicability of procedures of the present document for the mobile station is dependent on the services and functions which are to be supported by a mobile station. |
e9337f2b73429c082193983bf07185ba | 24.008 | 1.7.1 Voice Group Call Service (VGCS) and Voice Broadcast Service (VBS) | Voice Group Call Service and Voice Broadcast Service are applicable in A/Gb mode only.
For mobile stations supporting the Voice Group Call Service or the Voice Broadcast Service, it is explicitly mentioned throughout the present document if a certain procedure is applicable only for such a service and, if necessary, ho... |
e9337f2b73429c082193983bf07185ba | 24.008 | 1.7.2 General Packet Radio Service (GPRS) | |
e9337f2b73429c082193983bf07185ba | 24.008 | 1.7.2.1 Packet services in GSM (A/Gb mode only) | For mobile stations supporting the General Packet Radio Service (GPRS), it is explicitly mentioned throughout the technical specification if a certain procedure is applicable only for such a service and, if necessary, how mobile stations not supporting such a service shall behave.
A GPRS MS may operate in one of the fo... |
e9337f2b73429c082193983bf07185ba | 24.008 | 1.7.2.2 Packet services in Iu mode (Iu mode only) | An MS attached to packet switched domain may operate in one of the following MS operation modes, see 3GPP TS 23.060 [74]:
- CS/PS mode of operation; or
- PS mode of operation.
The terms 'CS/PS mode of operation' and 'PS mode of operation' are not used in the present document with some exceptions. Instead the terms 'MS ... |
e9337f2b73429c082193983bf07185ba | 24.008 | 1.8 Handling of NAS signalling low priority indication | An MS configured for NAS signalling low priority (see 3GPP TS 24.368 [135], 3GPP TS 31.102 [112]) indicates this by including the Device properties IE in the appropriate NAS message and setting the low priority indicator to "MS is configured to NAS signalling low priority" except for the following cases in which the MS... |
e9337f2b73429c082193983bf07185ba | 24.008 | 1.9 Restrictions | Independently of what is stated elsewhere in this and other 3GPP specifications, mobile station support for PBCCH and PCCCH is optional for A/Gb-mode of operation. The network shall never enable PBCCH and PCCCH. This makes use of network operation mode III obsolete. |
e9337f2b73429c082193983bf07185ba | 24.008 | 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.
- Fo... |
e9337f2b73429c082193983bf07185ba | 24.008 | 2.1 Definitions and abbreviations | For the purposes of the present document, the abbreviations defined in 3GPP TR 21.905 [2a] and the followings apply:
CAT Customized Alerting Tone
CHAP Challenge Handshake Authentication Protocol
DRVCC Dual Radio Voice Call Continuity
eDRX Extended idle-mode DRX cycle
IP-CAN IP-Connectivity Access Network
HNB Home Node ... |
e9337f2b73429c082193983bf07185ba | 24.008 | 2.1.1 Random values | In a number of places in the present document, it is mentioned that some value must take a "random" value, in a given range, or more generally with some statistical distribution. Such cases interest only the Mobile Station.
It is required that there is a low probability that two MSs in the same conditions (including th... |
e9337f2b73429c082193983bf07185ba | 24.008 | 2.1.2 Vocabulary | For the purposes of the present document, the following terms and definitions apply:
- A GSM security context is established and stored in the MS and the network as a result of a successful execution of a GSM authentication challenge. The GSM security context for the CS domain consists of the GSM ciphering key and the ... |
e9337f2b73429c082193983bf07185ba | 24.008 | 3 Radio Resource management procedures | See 3GPP TS 44.018 [84]. |
e9337f2b73429c082193983bf07185ba | 24.008 | 4 Elementary procedures for Mobility Management | |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.1 General | This clause describes the procedures used for mobility management for non-GPRS services and for GPRS-services at the radio interface (Reference Point Um and Uu).
The main function of the Mobility Management sublayer is to support the mobility of user terminals, such as informing the network of its present location and ... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.1.1 MM and GMM procedures | |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.1.1.1 Types of MM and GMM procedures | Depending on how they can be initiated, three types of MM procedures can be distinguished:
1) MM common procedures:
A MM common procedure can always be initiated whilst a RR connection exists. The procedures belonging to this type are:
Initiated by the network:
- TMSI reallocation procedure;
- authentication procedure;... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.1.1.1.1 Integrity Checking of Signalling Messages in the Mobile Station (Iu mode only) | In Iu mode only, integrity protected signalling is mandatory with one exception regarding emergency calls (see subclause 4.1.1.1.1a). In Iu mode only, all layer 3 protocols shall use integrity protected signalling once the security mode procedure has been successfully activated in the network and the MS. Integrity prot... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.1.1.2 MM-GMM co-ordination for GPRS MS's | |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.1.1.2.1 GPRS MS operating in mode A or B in a network that operates in mode I | If the network operates in mode I, GPRS MSes that operate in mode A or B and wish to be or are simultaneously IMSI attached for GPRS and non-GPRS services, shall use the combined GPRS attach and the combined and periodic routing area updating procedures instead of the corresponding MM specific procedures IMSI attach an... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.1.1.2.2 GPRS MS operating in mode A or B in a network that operates in mode II | If the network operates in mode II, a GPRS MS that operates in mode A or B and wishes to be or is simultaneously IMSI attached for GPRS and non-GPRS services, shall use the MM specific procedures listed in subclauses 4.3 and 4.4 and the GMM specific procedures listed in subclauses 4.7.3, 4.7.4 and 4.7.5. The applicabil... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.1.1.3 Core Network System Information for MM (Iu mode only) | In the network broadcast system information some of the system information is used by MM.
At reception of new system information, the RRC layer in the MS delivers the contents of the CN common system information and the CS domain specific system information to the MM layer in the MS.
The Core Network system information... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.1.1.4 Core Network System Information for GMM (Iu mode only) | |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.1.1.4.1 General | In the network broadcast system information some of the system information is used by GMM.
At reception of new system information, the RRC layer in the MS delivers the contents of the CN common system information and the PS domain specific system information to the GMM layer in the MS.
The Core Network system informati... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.1.1.4.2 Control of Network Mode of Operation I | The behaviour of the MS with respect to NMO I is determined by the combination of PS domain specific system information IE as defined in subclause 10.5.1.12.3 and the setting of the parameter "NMO_I_Behaviour" in the NAS configuration Management Object as specified in 3GPP TS 24.368 [135] or in USIM file NASCONFIG as s... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.1.1.5 Access class control | The network can restrict the access for certain groups of mobile stations. These groups are also known as access classes.
The restriction can apply for access to both domains (common access class control or EAB, depending on EAB configuration) or to one domain only (domain specific access control) (see 3GPP TS 23.122 [... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.1.1.6 Specific requirements for MS configured to use timer T3245 | The following requirement applies for an MS that is configured to use timer T3245 (see 3GPP TS 24.368 [135] or 3GPP TS 31.102 [112]):
When the MS adds a PLMN identity to the "forbidden PLMN list" or the "forbidden PLMNs for GPRS service" list or sets the SIM/USIM as invalid for non-GPRS services or GPRS services or bot... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.1.1.7 Handling of NAS level mobility management congestion control | The network may detect GMM or MM signalling congestion and perform NAS level mobility management congestion control. PS domain NAS level mobility management congestion control consists of general NAS level mobility management congestion control and subscribed APN based congestion control. CS domain NAS level mobility m... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.1.1.8 Handling of security related parameters at switch on and switch off | At switch on, an ME supporting UTRAN Iu mode shall proceed as follows:
- if a USIM is inserted, the ME shall read the STARTCS and STARTPS value from the USIM. If STARTCS and/or STARTPS read from the USIM are greater than or equal to the maximum value of STARTCS and STARTPS provided on the USIM (see 3GPP TS 31.102 [112]... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.1.1.9 Equivalent PLMNs list | The mobile equipment shall store a list of "equivalent PLMNs". These PLMNs shall be regarded by the MS as equivalent to each other for PLMN selection and cell selection/re-selection. The same list is used by 5GMM, EMM, GMM and MM (see 3GPP TS 24.501 [167] and 3GPP TS 24.301 [120]).
The list of equivalent PLMNs is repla... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.1.1.10 Dedicated core network | The network may reject mobility management signalling requests from MSs due to dedicated core network as specified in 3GPP TS 23.060 [74]. When the network rejects mobility management signalling requests due to dedicated core network, the mechanism for general NAS level mobility management congestion control as specifi... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.1.2 MM sublayer states | The description of the states for the MM sublayer is organized as follows. The main states for the MS side, related to the procedures, are described in subclause 4.1.2.1.1. The MM IDLE state is subdivided in substates for the description of the behaviour in idle mode (subclause 4.1.2.1.2). This behaviour depends on an ... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.1.2.1 MM sublayer states in the mobile station | In this subclause, the possible states for the MM sublayer in the mobile station is described. In figure 4.1 of the present document, an overview of the MM sublayer protocol is given. |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.1.2.1.1 Main states | 0 NULL
The mobile station is inactive (e.g. power down). Important parameters are stored. Only manual action by the user may transfer the MM sublayer to another state.
3 LOCATION UPDATING INITIATED
A location updating procedure has been started and the MM awaits a response from the network. The timer T3210 is running.
... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.1.2.1.2 Substates of the MM IDLE state | For the description of the behaviour of the MS the MM IDLE state is subdivided in several substates, also called the service states. The service state pertains to the whole MS (ME alone if no SIM/USIM is inserted, or ME plus SIM/USIM). The service state depends on the update status (see subclause 4.1.2.2) and on the se... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.1.2.2 The update Status | In parallel with the sublayer states described in subclause 4.1.2.1 and which control the MM sublayer protocol, an update status exists.
The update status pertains to a specific subscriber embodied by a SIM/USIM. This status is defined even when the subscriber is not activated (SIM/USIM removed or connected to a switch... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.1.2.3 MM sublayer states on the network side | 1. IDLE
The MM sublayer is not active except possibly when the RR sublayer is in Group Receive mode.
2. WAIT FOR RR CONNECTION
The MM sublayer has received a request for MM connection establishment from the CM layer. A RR connection to the mobile station is requested from the RR sublayer (i.e. paging is performed).
3. ... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.1.3 GPRS mobility management (GMM) sublayer states | In this subclause, the GMM protocol of the MS and the network are described by means of two different state machines. In subclause 4.1.3.1, the states of the GMM entity in the MS are introduced. The behaviour of the MS depends on a GPRS update status that is described in subclause 4.1.3.2. The states for the network si... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.1.3.1 GMM states in the MS | In this subclause, the possible GMM states are described of a GMM entity in the mobile station. subclause 4.1.3.1.1 summarises the main states of a GMM entity, see figure 4.1b of the present document. The substates that have been defined are described in subclause 4.1.3.1.2 and subclause 4.1.3.1.3.
However, it should b... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.1.3.1.1 Main states | 4.1.3.1.1.1 GMM-NULL
The GPRS capability is disabled in the MS. No GPRS mobility management function shall be performed in this state.
4.1.3.1.1.2 GMM-DEREGISTERED
The GPRS capability has been enabled in the MS, but no GMM context has been established. In this state, the MS may establish a GMM context by starting the G... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.1.3.1.2 Substates of state GMM-DEREGISTERED | The GMM-DEREGISTERED state is subdivided into several substates as explained below. The substates pertain to the whole MS (ME alone if no SIM/USIM is inserted, or ME plus SIM/USIM). The selection of the appropriate substate depends on the GPRS update status, see subclause 4.1.3.2, and on the selected cell.
4.1.3.1.2.1 ... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.1.3.1.3 Substates of state GMM-REGISTERED | The state GMM-REGISTERED is subdivided into several substate as explained below. The substates pertain to the whole MS (ME alone if no SIM/USIM is inserted, or ME plus SIM/USIM).
4.1.3.1.3.1 GMM-REGISTERED.NORMAL-SERVICE
User data and signalling information may be sent and received.
4.1.3.1.3.2 GMM-REGISTERED.SUSPENDED... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.1.3.2 GPRS update status | In addition to the GMM sublayer states described so far, a GPRS update status exists.
The GPRS update status pertains to a specific subscriber embodied by a SIM/USIM. This status is defined even when the subscriber is not activated (SIM/USIM removed or connected to a switched off ME). It is stored in a non volatile mem... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.1.3.3 GMM mobility management states on the network side | In this subsubclause, the possible states are described for the GMM on the network side. Subclause 4.1.3.3.1 summarises the main states. The corresponding substates are described in subclause 4.1.3.3.2.
However, it should be noted that this subclause does not include a description of the detailed behaviour of the netwo... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.1.3.3.1 Main States | 4.1.3.3.1.1 GMM-DEREGISTERED
The network has no GMM context or the GMM context is marked as detached, the MS is detached. In this state, the network may answer to a GPRS attach or combined GPRS attach procedure initiated by the MS.
4.1.3.3.1.2 GMM-COMMON-PROCEDURE-INITIATED
A common GMM procedure, as defined in subclau... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.1.3.3.2 Substates of state GMM-REGISTERED | The state GMM-REGISTERED is subdivided into two substates as explained below.
4.1.3.3.2.1 GMM-REGISTERED.NORMAL-SERVICE
User data and signalling information may be sent and received.
4.1.3.3.2.2 GMM-REGISTERED.SUSPENDED (A/Gb mode only)
In this substate, the lower layers shall be prevented of sending user data or signa... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.2 Behaviour of the MS in MM Idle state, GMM-DEREGISTERED state and GMM-REGISTERED state | In this subclause, the detailed behaviour of the MS in the main states MM IDLE, GMM-DEREGISTERED and GMM-REGISTERED is described. Subclauses 4.2.1 to 4.2.3 refer to the state MM IDLE, whereas subclauses 4.2.4 and 4.2.5 refer to the states GMM-DEREGISTERED and GMM-REGISTERED, respectively.
The MM IDLE state is entered w... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.2.1 Primary Service State selection | |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.2.1.1 Selection of the Service State after Power On. | For an eCall only mobile station (as determined by information configured in the USIM), Timers T3242 and T3243 are considered to have expired at power-on. When mobility management is activated after power-on, the service state is 19.7 PLMN SEARCH. The detailed processing in this state is described in detail in 3GPP TS ... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.2.1.2 Other Cases | The state PLMN SEARCH is also entered in the following cases:
- in state NO IMSI, a SIM/USIM is inserted;
- in any state except NO IMSI, NO CELL AVAILABLE, NORMAL SERVICE and RECEIVING GROUP CALL (NORMAL SERVICE) after the user has asked for a PLMN selection;
- in any state except NO IMSI and NO CELL AVAILABLE, coverag... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.2.2 Detailed Description of the MS behaviour in MM IDLE State. | In the MM IDLE state the mobile station shall behave according to the service state. In the following subclauses the behaviour is described for the non transient service states. It should be noted that after procedures in RR connected mode, e.g. location updating procedures, subclause 4.2.3 applies which specifies the ... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.2.2.1 Service State, NORMAL SERVICE | When in state MM IDLE and service state NORMAL SERVICE, the mobile station shall:
- provided that T3246 is not running, perform normal location updating when a new location area is entered;
- perform location updating procedure at expiry of timer T3211 or T3213;
- perform periodic updating at expiration of timer T3212;... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.2.2.2 Service State, ATTEMPTING TO UPDATE | When in state MM IDLE and service state ATTEMPTING TO UPDATE the mobile station shall:
- perform location updating procedure at expiry of timer T3211, T3213 or T3246;
- perform normal location updating when entering a new PLMN, if timer T3246 is running and the new PLMN is not equivalent to the PLMN where the MS starte... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.2.2.3 Service State, LIMITED SERVICE | When in state MM IDLE and service state LIMITED SERVICE the mobile station shall:
- not perform periodic updating;
- not perform IMSI detach;
- reject any requests from CM entities for MM connections except for emergency calls;
- perform normal location updating when a cell is entered which may provide normal service (... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.2.2.4 Service State, NO IMSI | When in state MM IDLE and service state NO IMSI the mobile station shall (see subclause 3.2, 3GPP TS 43.022 [82] and 3GPP TS 45.008 [34]):
- not start any normal location updating attempt;
- not perform periodic updating;
- not perform IMSI detach if powered down;
- reject any request from CM entities for MM connection... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.2.2.5 Service State, SEARCH FOR PLMN, NORMAL SERVICE | When in state MM IDLE and service state SEARCH FOR PLMN, NORMAL SERVICE the mobile station shall:
- if timer T3211 or T3213 expires in this state perform a location updating procedure at the latest if and when back to NORMAL SERVICE state and if the cell is not changed;
- if timer T3212 expires in this state perform a ... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.2.2.6 Service State, SEARCH FOR PLMN | When in state MM IDLE and service state SEARCH FOR PLMN the mobile station shall:
- not start any normal location updating attempt;
- not perform periodic updating;
- not perform IMSI detach if powered down;
- reject any request from CM entities for MM connections except emergency calls;
- not respond to paging. |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.2.2.7 Service State, RECEIVING GROUP CALL (NORMAL SERVICE) | Only applicable for mobile stations supporting VGCS listening or VBS listening:
When in state MM IDLE and service state RECEIVING GROUP CALL (NORMAL SERVICE), the mobile station shall:
- perform normal location updating when a new location area is entered;
- perform location updating procedure at expiry of timer T3211 ... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.2.2.8 Service State, RECEIVING GROUP CALL (LIMITED SERVICE) | Only applicable for mobile stations supporting VGCS listening or VBS listening:
When in state MM IDLE and service state RECEIVING GROUP CALL (LIMITED SERVICE), the mobile station shall:
- not perform periodic updating;
- not perform IMSI detach;
- reject any requests from CM entities for MM connections except for emerg... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.2.2.9 Service State, eCALL INACTIVE | When in state MM IDLE and service state eCALL INACTIVE, the mobile station shall:
- not perform periodic updating;
- not perform IMSI detach;
- reject any requests from CM entities for MM connections except for emergency calls and calls to a non-emergency MSISDN for test and terminal reconfiguration services;
- not per... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.2.3 Service state when back to state MM IDLE from another state | When returning to MM IDLE, e.g., after a location updating procedure, the mobile station selects the cell as specified in 3GPP TS 43.022 [82] and 3GPP TS 25.304 [98]. With one exception, this is a normal cell selection.
An eCall only mobile station (as determined by information configured in USIM), shall start timer T3... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.2.4 Behaviour in state GMM-DEREGISTERED | The state GMM-DEREGISTERED is entered when:
- the MS is switched on;
- the GPRS capability has been enabled in the MS;
- a GPRS detach or combined GPRS detach procedure has been performed;
- a GMM procedure has failed (except routing area updating, see subclause 4.7.5); or
- the MS attached for emergency bearer service... |
e9337f2b73429c082193983bf07185ba | 24.008 | 4.2.4.1 Primary substate selection |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.