6 Operational aspects of handling fault information

23.1953GPPProvision of User Equipment Specific Behaviour Information (UESBI) to network entitiesRelease 5TS

6.1 General Aspects

SGSN and MSC derive the UESBI-Iu by mapping from the IMEISV’s TAC+SVN. Local databases in the SGSN and MSC provide the mapping information. Local databases are maintained by O+M functionality. This functionality shall allow for setting/not setting any of the bits/parameters within the UESBI-Iu for each TAC+SVN. In addition a FIB Register (a central database) may be used in the network to provide the mapping information to the local databases.

6.2 FIB Register

The MSC/SGSN interrogates the FIB Register when a not yet known TAC+SVN is to be mapped by the MSC/SGSN. The MSC/SGSN stores in its local database the mapping information received from the FIB Register.

The MSC/SGSN should periodically interrogate the FIB Register to update the mapping information stored in its local database. The period and timing is configuration specific (e.g. to permit the updates to be obtained during periods of lower network activity such as the night and/or weekend). Each signalling message between MSC/SGSN and FIB Register retrieves the UESBI-Iu for just one TAC+SVN.

No functionality is expected on the FIB Register to MSC/SGSN interface for the FIB Register to “push” updated UESBI-Iu to the MSC/SGSNs. Instead, it shall be possible to trigger the MSC/SGSN by O+M mechanisms to update its local database for a specific TAC+SVN.

The FIB Register may be implemented as a stand-alone node, co-located with an EIR, or co-located with any other node (eg HLR).

Note: The FIB Register is expected to process many fewer messages than an EIR, and, might have lesser availability requirements than an EIR.

Annex A (Informative):
Compatibility with network entities not supporting the PUESBINE Feature

A.1 General

This annex gives information on the interworking between network entities that support the PUESBINE Feature and those that do not. Where this interworking leads to actual requirements on a network entity, then these requirements should be documented in the main body of this TS.

A.2 Inter SGSN relocation

From an SGSN that does not support the PUESBINE Feature to an SGSN that does support the PUESBINE Feature:

The target RNC will not receive the UESBI-Iu in the Relocation Request message and adopts some generic behaviour. The later arrival of UESBI-Iu at RNC is used by the RNC for any future processing for that UE.

From an SGSN that does support the PUESBINE Feature to an SGSN that does not support the PUESBINE Feature:

The target RNC does not receive the UESBI-Iu, but, this is reasonable considering that the RNC’s "default" SGSN does not support the PUESBINE Feature. GTP error handling should ensure that reception of the IMEISV is ignored by an SGSN that does not support the PUESBINE Feature.

A.3 Inter SGSN Routing Area Update

From an SGSN that does not support the PUESBINE Feature to an SGSN that does support the PUESBINE Feature:

If an SGSN that supports the PUESBINE Feature does not receive the IMEISV from the old SGSN, then the new SGSN shall get the IMEISV from the MS.

From an SGSN that does support the PUESBINE Feature to an SGSN that does not support the PUESBINE Feature:

GTP error handling should ensure that reception of the IMEISV is ignored by an SGSN that does not support the PUESBINE Feature.

A.4 Iu interface issues

If UESBI-Iu is not received for a UE, then the RNC assumes that the UE has some default capability. This default capability is RNC implementation dependent.

The RNC can assume that a CN that supports the PUESBINE Feature will deliver the UESBI-Iu before the RANAP Security Mode command.

RANAP error handling should ensure that reception of the UESBI-Iu is ignored by an RNC that does not support the PUESBINE Feature.

A.5 Gs issues

If the MSC does not receive the IMEISV in the Gs interface Location Update Request message, then the MSC obtains the IMEISV from the UE at the next Iu-cs/A interface connection establishment.

Gs interface error handling should ensure that reception of the IMEISV in the Gs interface Location Update Request message is ignored by an MSC that does not support the PUESBINE Feature.

A.6 Inter-MSC issues

If the anchor MSC does not pass the UESBI-Iu information to the relay MSC, then the target RNC does not receive the UESBI-Iu information. This is handled as an "Iu interface issue" (see clause A.4).

MAP error handling should ensure that reception of the UESBI-Iu is ignored by a relay MSC that does not support the PUESBINE Feature.

A.7 Iu to A-interface issues

As specified in 3GPP TS 29.010 [16], an MSC that does not support the PUESBINE feature will map RANAP cause values into the A interface cause value “no radio resource available”.

A interface error handling procedures should ensure that reception of the new Cause value is treated in a backwards compatible manner by a BSS that does not support the PUESBINE Feature.

A.8 A interface issues

With regard to the new Handover Reject Cause value, see clause A.7.

With regard to using the "old BSS to new BSS information" IE to transfer the "don’t handover to UMTS flag" between BSSs, then existing A interface error handling procedures should ensure that this flag is ignored by a BSS that does not support the PUESBINE Feature.

Annex B (informative):
Void

Annex C (informative):
Change history

Change history

Date

TSG #

TSG Doc.

CR

Rev

Subject/Comment

Old

New

2003-06

SA#20

SP-030314

Raised to v.2.0.0 for presentation and approval at SA#20

Modified at SA #20 based on the RAN #20 decision on the nature of UESBI

2.0.0

2.1.0

2003-06

SA#20

SP-030335

Raised to v.5.0.0 after approval at SA#20

2.1.0

5.0.0

2003-09

SA#21

SP-030377

001

3

Iu mode correction

5.0.0

5.1.0

2003-09

SA#21

SP-030377

002

2

Clean up of diagrams

5.0.0

5.1.0

2003-09

SA#21

SP-030377

003

2

Additional text for section 6 on (physical) location of FIB function

5.0.0

5.1.0

2003-09

SA#21

SP-030377

004

1

Roll out issue for RANAP-BSSMAP interworking

5.0.0

5.1.0

2003-12

SA#22

SP-030655

009

Change to editor’s note

5.1.0

5.2.0

2004-03

SA#23

SP-040034

008

2

Removal of text passages with unclear status

5.2.0

5.3.0

2004-03

SA#23

SP-040034

010

Alignment of text with figure

5.2.0

5.3.0

2004-09

SA#25

SP-040520

011

1

IMEISV obtaining for UEs supporting only UMTS radio access

5.3.0

5.4.0