Content for TS 23.195 Word version: 5.4.0

3.1 Definitions 3.2 Abbreviations 4.1 UESBI 4.2 UESBI-Uu 4.3 UESBI-Iu 4.4 UESBI-Iu on A interface
...

1 Scope p. 6

The present document defines the stage-2 description of the mechanism to provide the 3GPP network entities with UE Specific Behaviour Information (UESBI). UESBI may be used by correcting mechanisms to overcome some of the issues that have been recognized by 3GPP in TR 25.994 [13] (Measures employed by the UMTS Radio Access Network (UTRAN) to overcome early User Equipment (UE) implementation faults), and other such documents. The description of these correcting mechanisms is out of the scope of this TS.

ITU-T Recommendation I.130 [1] describes a three-stage method for characterisation of telecommunication services, and ITU-T Recommendation Q.65 [2] defines stage 2 of the method.

2 References p. 6

The following documents contain provisions which, through reference in this text, constitute provisions of the present document.

References are either specific (identified by date of publication, edition number, version number, etc.) or non specific.
For a specific reference, subsequent revisions do not apply.
For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.

[1]

ITU-T Recommendations I.130: "General modelling methods - Method for the characterisation of telecommunication services supported by an ISDN and network capabilities of an ISDN".

[2]

ITU-T Recommendation Q.65: "Methodology - Stage 2 of the method for the characterization of services supported by an ISDN".

[3]

TS 24.008: "Mobile radio interface Layer 3 specification; Core network protocols; Stage 3".

[4]

TS 23.060: "General Packet Radio Service (GPRS) Service description; Stage 2".

[5]

TS 23.009: "Handover procedures".

[6]

TS 25.331: "Radio Resource Control (RRC) protocol specification".

[7]

TS 44.018: "Mobile radio interface layer 3 specification; Radio Resource Control (RRC) protocol".

[8]

TS 44.008: "Mobile radio interface layer 3 specification".
→ to date, withdrawn by 3GPP

[9]

TS 25.413: "UTRAN Iu interface Radio Access Network Application Part (RANAP) signalling".

[10]

TS 23.236: "Intra-domain connection of Radio Access Network (RAN) nodes to multiple Core Network (CN) nodes".

[11]

TS 29.060: "General Packet Radio Service (GPRS); GPRS Tunnelling Protocol (GTP) across the Gn and Gp interface".

[12]

TS 23.116: "Super-Charger technical realization; Stage 2".

[13]

TR 25.994: "Measures employed by the UMTS Radio Access Network (UTRAN) to overcome early User Equipment (UE) implementation faults".

[14]

TR 25.995: "Measures employed by the UMTS Radio Access Network (RAN) to cater for legacy User Equipment (UE) which conforms to superseded versions of the RAN interface specification".

[15]

TR 21.905: "Vocabulary for 3GPP Specifications".

[16]

TS 29.010: "Information element mapping between Mobile Station - Base Station System (MS - BSS) and Base Station System - Mobile-services Switching Centre (BSS - MSC); Signalling procedures and the Mobile Application Part (MAP)".

3 Definitions and abbreviations p. 7

3.1 Definitions p. 7

For the purposes of the present document, the terms and definitions given in TS 21.905 and the following apply.

PUESBINE Feature:

is the functionality described by this TS.

UE Specific Behaviour Information - Uu (UESBI-Uu):

is information that is sent using Access Stratum signalling from the UE to the RAN. It can be used to derive some specific information about the UE's capabilities.

UE Specific Behaviour Information - Iu (UESBI-Iu):

is information that is sent from the MSC and/or SGSN to the RAN that can be used to derive some specific information about the UE's capabilities. The UESBI-Iu is a Bit Map of UE Faults derived from the IMEISV.

3.2 Abbreviations p. 7

For the purposes of the present document, the abbreviations given in TS 21.905 and the following apply:

FIB Register

Faulty IMEISV to Bitmap Register

PUESBINE

Provision of UE Specific Behaviour Information to Network Entities

User Equipment

UESBI

UE Specific Behaviour Information

UESBI-Uu

UE Specific Behaviour Information - Uu

UESBI-Iu

UE Specific Behaviour Information - Iu

4 General description p. 7

4.1 UESBI p. 7

Due to the potential problems that may happen in the standard or in its implementation by different types of UE, it may be needed to transfer to the RAN "information on the specific behavior of particular sets of UE" with regard to some 3GPP features. This aims at helping the infrastructure to handle UE(s) already in the field that are facing problems to support some 3GPP features. This "information on the specific behavior of particular sets of UE" is called UE Specific Behavior Information (UESBI).

UESBI actually corresponds to 2 different sets of information:

UESBI-Uu which is sent from UE to RAN using signalling specified in the RRC protocol (TS 25.331)
UESBI-Iu which is sent by CN to UTRAN/GERAN over the Iu interface and is derived from IMEISV retrieved by CN from UE.

UESBI-Uu and UESBI-Iu may have a different nature, their coding is defined in RRC and RANAP respectively, and have different handling within the network. Whether or not UESBI-Uu or UESBI-Iu is used to describe an inter-operability issue will be determined on a case by case basis and all uses should be documented in TRs such as 25.994 [13] and 25.995 [14]. As a result of this process, RAN nodes should not receive conflicting information in UESBI-Uu and UESBI-Iu.

The SRNC uses both UESBI-Iu and UESBI-Uu to derive the specific behaviour of the UE.

In the context of this specification, the terms RNS and RNC refer also to a GERAN BSS or BSC (respectively) when serving UE in Iu mode.

4.2 UESBI-Uu p. 8

UESBI-Uu information is sent:

(at RRC connection establishment from idle mode) directly by UE to Serving RNC at RRC connection establishment
(at SRNS relocation) from Serving RNC to Target RNC in the RRC: SRNS RELOCATION INFO message carried through CN during SRNS relocation in the RANAP: Source RNC to Target RNC Transparent Container IE.
(at RRC connection establishment for an UE coming from another Radio Access Technology e.g. in case of 2G to 3G Hand-Over) from UE to Serving RNC via "Inter RAT Hand-Over" Information. This "Inter RAT Hand-Over Information" is sent to the source RAN (e.g. BSS), and at handover copied by the source RAN into a transparent container that is carried through the CN towards the Target RNC.
(at RR connection establishment) the UE can directly send the "Inter RAT Handover Information" which contains the UESBI-Uu to the GERAN BSS. However, if control of GERAN BSS functions using the UESBI-Uu is needed, then new functionality will be required within the BSS to decode the ASN.1 PER information contained in the Inter-RAT Handover Information IE.

4.3 UESBI-Iu p. 8

When the UE attaches to the VLR or SGSN or makes its first Location Update in the VLR, the IMEISV information is retrieved from the UE and stored in the VLR or SGSN.

At each subsequent Iu interface connection establishment (eg for a CS domain voice call or a PS domain data transfer), the IMEISV is retrieved from the VLR or from the MM context in the SGSN and, the UESBI-Iu is derived. The UESBI-Iu is then sent to the SRNC. The UESBI-Iu is normally sent in the Common Id procedure (the same procedure that currently carries the IMSI) or by the UESBI-Iu Information procedure. This is summarised in Figure 4.3-1.

Copy of original 3GPP image for 3GPP TS 23.195, Fig. 4.3-1: UESBI-Iu architecture

Figure 4.3-1: UESBI-Iu architecture
(⇒ copy of original 3GPP image)

If the UE state is changed from RRC Connected to RRC Idle, all information derived from the received UESBI is released in the RNS. Thus if the UE state is changed afterwards back to RRC Connected the delivery of the UESBI-Iu from MSC or SGSN to SRNC shall be repeated.

At inter-SRNS relocation or at inter-system handover, the anchor MSC (and not the source RAN node) sends the UESBI-Iu to the target RAN node.

4.4 UESBI-Iu on A interface p. 8

With GERAN, usage of UESBI is aimed to only solve issues related to CS domain GERAN to UTRAN handover. To smooth rollout of features, a Handover Reject cause is defined to provide minimal functionality (see clause 5.1.4.2).