(3GPP TS version Release 12). TECHNICAL The cross reference between GSM, UMTS, 3GPP and ETSI identities can be found under. Descriptor and Table of Contents (1 of 40) for 3GPP TS – General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio. 3GPP TS Numbering, Addressing and Identification 3GPP CT WG4 access 3GPP SA WG2 3GPP TS.
|Published (Last):||9 December 2010|
|PDF File Size:||4.62 Mb|
|ePub File Size:||6.86 Mb|
|Price:||Free* [*Free Regsitration Required]|
As a result of UE mobility e. The last received value of the throttling factor and throttling delay supersedes any previous values received from that MME. If a session terminates on a server in the Internet g3pp. Alternative MME implementations are permitted, however, the externally visible MME behaviour should conform to the above description.
This functionality applies to all mobility procedures. The SGW determines whether a bearer is for low priority traffic or not on the basis of the bearer’s ARP priority level and operator policy i.
The following CSG related functions are defined: Stage 3 for Session management, bearer control and QoS aspects. The above functionality is to diminish the performance advantage for UEs that do not support the NAS level back-off timer e. Stage 3 for Mobility management 234401 on MIP v4. Packet Routing and Transfer Functions.
The SGW resumes normal operations at 233401 expiry of the throttling delay.
Low access priority shall not be applicable in the following situations: These include some time randomisation to guard against a repeat of a load peak. The UE may be registered in multiple Tracking Areas. The emergency bearer contexts shall not be changed to non-emergency bearer contexts and 24301 versa.
UEs that camp normally on a cell may also use the emergency attach procedure under conditions specified in TS While the Mobility Management back-off timer is running, the UE shall not initiate any NAS request for Mobility Management procedures except for Detach procedure and except for high priority access, emergency services and mobile terminated services. However, the UE is allowed to initiate the Mobility Management procedures for high priority 3gpo and emergency services even when the Mobility Management back-off timer is running.
The serving PLMN provides this indication based e. 24301 this operation is complete, the RN detaches from the network using the normal UE initiated detach procedure, see 33gpp 5. The low access priority indicator in NAS signalling and the corresponding low access priority for RRC connection establishment are only used by the network to decide whether to accept the NAS request or the setup of the RRC connection respectively. These cases are considered as roaming between GTP based operators.
MPS supports priority sessions on an “end-to-end” priority basis. Though motivated by scenarios and use cases defined in TS In this release there is no other usage of storing the low access priority indicator in EPS Bearer contexts other than for the purpose to include it in charging records. The RN follows normal UE behaviour, e.
To avoid that large amounts of UEs initiate deferred requests almost simultaneously, the MME should select the Mobility Management back-off timer value so that deferred requests are not synchronized.
Rx session, Gx session, S9 session etc. The specific functionality is described in the affected procedures and functions of this specification.
Serving GW Service Areas may overlap each other. This Specification is provided for future development work within 3GPP only. The back-off timer 234001 stopped as defined in TS Stage 3 for interfaces within 3hpp.
The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. Created from version The other roaming architectures with services provided by the home network do not apply for emergency services.
Serving GW Service Area: