Tech-invite3GPPspecsGlossariesIETFRFCsGroupsSIPABNFsWorld Map
Top   in Index   Prev   Next

TR 23.898 (SA2)
Access Class Barring and Overload Protection (ACBOP)

ToC   3GPP‑Page   Help    
V7.0.0 (Wzip)  2005/04  27 p.

Rapporteur:  Mr. Davidian, Jean-Jacques
See also:  –

This TR studies 3GPP system enhancements e.g. CS or PS domain specific access control to cope with several network overload and failure situations. This feasibility study also identifies the potential technical solutions for UTRAN and GERAN access control and overload protection.


Here   Top


1 Scope2 References3 Definitions, symbols and abbreviations3.1 Definitions3.2 Abbreviations4 Congestion and Failure Scenarios4.1 MSC/VLR or SGSN Congestion or Failure4.2 MGW and/or voice transit network overload or failure4.3 SS7 signalling network overload/failure4.4 Terminating calls/events4.5 HLR Overload/Failure4.6 GGSN Overload/Failure4.7 Packet backbone (GTP-U or Gi) overload/failure4.8 Wide area radio interface congestion causing RNC/BSC overload/failure4.9 Cell level congestion/access for emergency services4.10 Multiple RATs4.11 Intra-domain connection of Radio Access Network (RAN) nodes to multiple Core Network (CN) nodes (Iu Flex)4.12 Network Sharing4.13 Handover into overloaded areas4.14 MBMS point to point repair5 Functional Requirements5.1 General overview5.2 Functional requirements for access control mechanisms5.3 Additional requirements6 Potential Technical Solutions6.1 Domain Specific Access Class Barring approach6.2 Service Specific Access Class Barring approach6.3 Handling overload situations by alternative solutions6.4 O&M Guidance7 ConclusionA Interlayer primitives within the UEB Improvements to prevent/delay automatic re-establishment attempts (requirement g)B.1 Classification of exiting GPRS/SMS specific cause valueB.2 Duration of wait timer and other configurations within MTC Combination of Access Class ControlD Change history


1  ScopeWord-p. 5
2  References
3  Definitions, symbols and abbreviationsWord-p. 6
4  Congestion and Failure Scenarios
5  Functional Requirements
6  Potential Technical Solutions
6.1  Domain Specific Access Class Barring approachUp
6.2  Service Specific Access Class Barring approach
6.3  Handling overload situations by alternative solutionsWord-p. 20
6.4  O&M Guidance
7  Conclusion
A  Interlayer primitives within the UEWord-p. 22
B  Improvements to prevent/delay automatic re-establishment attempts (requirement g)Word-p. 24
C  Combination of Access Class Control
D  Change historyWord-p. 27Up

Up   Top