Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x
Top   in Index   Prev   Next

TR 23.895
Provision of UE specific behaviour information to network entities

3GPP‑Page   ToC  
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

Here   Top

1  ScopeWord‑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.
Up

2  ReferencesWord‑p. 6

3  Definitions, symbols and abbreviationsWord‑p. 6

3.1  DefinitionsWord‑p. 6

3.2  SymbolsWord‑p. 6

3.3  AbbreviationsWord‑p. 6

4  Network Entities that could use UE Specific Behaviour InformationWord‑p. 7

4.1  Serving RNCWord‑p. 7

4.2  Drift RNCWord‑p. 7

4.3  Node BWord‑p. 7

4.4  GSM BSC (A/Gb mode)Word‑p. 7

4.5  GSM BTSWord‑p. 7

4.6  Visited MSC/VLRWord‑p. 8

4.7  Relay MSCWord‑p. 8

4.8  GMSCWord‑p. 8

4.9  HLRWord‑p. 8

4.10  2G-SGSNWord‑p. 8

4.11  3G-SGSNWord‑p. 8

4.12  GGSNWord‑p. 8

4.13  SMSCWord‑p. 8

4.14  CAMEL platformsWord‑p. 8

5  ArchitecturesWord‑p. 9

5.1  Architecture 1: full IMEISV distributionWord‑p. 9

5.2  Architecture 2: Iu interface carries Bit Map of UE Faults derived from the IMEISV sent to the CNWord‑p. 14

5.3  Architecture 3: UESBI sent from UE to RANWord‑p. 16

6  Initial Comparison of the Different Proposed ArchitecturesWord‑p. 18

$  Change HistoryWord‑p. 21


Up   Top