TR 23.895
Provision of UE specific behaviour information to network entities
V6.2.0 (Wzip)
2003/06 21 p.
- Rapporteur:
- Mr. Pudney, Chris
VODAFONE Group Plc
full Table of Contents for TR 23.895 Word version: 6.2.0
1 Scope p. 6
This TR studies different possible mechanisms to provide the 3GPP network entities with UE Specific Behavior Information (UESBI). UESBI is used by correcting mechanisms to overcome some of the issues that will be recognized by 3GPP in TR 25.994 [] and other such documents. The description of these correcting mechanisms is out of the scope of this TR.
A comparison of the pros and cons of the different architectures is included, however, the TR is not expected to make a decisive conclusion. Instead, the TSG plenary meetings are expected to use this TR to recommend how to proceed with further work.
2 References p. 6
3 Definitions, symbols and abbreviations p. 6
4 Network Entities that could use UE Specific Behaviour Information p. 7
4.1 Serving RNC p. 7
4.2 Drift RNC p. 7
4.3 Node B p. 7
4.4 GSM BSC (A/Gb mode) p. 7
4.5 GSM BTS p. 7
4.6 Visited MSC/VLR p. 8
4.7 Relay MSC p. 8
4.8 GMSC p. 8
4.9 HLR p. 8
4.10 2G-SGSN p. 8
4.11 3G-SGSN p. 8
4.12 GGSN p. 8
4.13 SMSC p. 8
4.14 CAMEL platforms p. 8
5 Architectures p. 9
5.1 Architecture 1: full IMEISV distribution p. 9
5.1.1 General description p. 9
5.1.2 Gs interface/Network Mode of Operation = 1 p. 10
5.1.3 Emergency Call Handling p. 10
5.1.3.1 Attached Mobile with (U)SIM p. 10
5.1.3.2 (U)SIMless mobile p. 10
5.1.3.3 Non-attached Mobile with (U)SIM p. 11
5.1.4 Inter-MSC Location Updates p. 11
5.1.5 Inter-SGSN Routeing Area Update and Relocation p. 11
5.1.6 Long Lived Iu-ps Connections p. 12
5.1.7 Inter-RNC/BSC and Inter-MSC Handover/Relocation p. 12
5.1.8 Other Impacts on Network elements p. 12
5.1.8.1 MSC/VLR and SGSN p. 12
5.1.8.2 RNC p. 12
5.1.9 Mandatory IMSI Attach to MSC p. 13
5.1.10 Handling of UESBI during the Attach Procedures p. 13
5.1.11 UESBI information in the RANAP paging message p. 14
5.2 Architecture 2: Iu interface carries Bit Map of UE Faults derived from the IMEISV sent to the CN p. 14
5.2.0 Summary p. 14
5.2.1 General description p. 14
5.2.2 Nature of Bit Map of UE Faults p. 14
5.2.3 The content of BMUEF for multivendor UTRAN p. 15
5.2.4 The content and the handling of BMUEF in UTRAN sent by PS and/or CS domains p. 15
5.2.5 Storing the IMEISV / BMUEF information at CN side p. 15
5.2.6 Other Impacts on Network Elements p. 16
5.2.6.1 MSC/VLR and SGSN p. 16
5.2.6.2 RNC p. 16
5.3 Architecture 3: UESBI sent from UE to RAN p. 16
5.3.1 General Description p. 16
5.3.2 BMUEVB p. 17
5.3.3 Possibility to update the BMUEVB sent by the UE p. 17
5.3.4 Applicability of this Architecture for Use with Other Network Entities p. 17
5.3.5 Message length limits on A/E interfaces p. 18
5.3.6 Extra call set up delay on the GSM radio interface. p. 18
5.3.7 Extra connection set up delay on the UTRAN radio interface p. 18
5.3.8 Inter-RNC/BSC and Inter-MSC Handover/Relocation p. 18
6 Initial Comparison of the Different Proposed Architectures p. 18
$ Change History p. 21
