8.16 Common ID
25.4133GPPRelease 17TSUTRAN Iu interface Radio Access Network Application Part (RANAP) signalling
8.16.1 General
The purpose of the Common ID procedure is to inform the RNC about the permanent NAS UE Identity (i.e. IMSI) of a user. This is used by the RNC e.g. to create a reference between the permanent NAS UE identity of the user and the RRC connection of that user for UTRAN paging co-ordination. The procedure may also be used to provide the SNA Access Information IE to the RNC or to provide the Management Based MDT Allowed IE to the RNC or to provide the Management Based MDT PLMN List IE to the RNC.
The procedure uses connection oriented signalling.
8.16.2 Successful Operation
Figure 17: Common ID procedure. Successful operation.
After having established an Iu signalling connection, and if the Permanent NAS UE identity (i.e. IMSI) is available, the CN shall send to the RNC a COMMON ID message containing the Permanent NAS UE Identity IE and optionally the SNA Access Information IE. The COMMON ID message may also include the UESBI-Iu IE. The RNC shall associate the permanent identity to the RRC Connection of that user and shall save it for the duration of the RRC connection.
The RNC shall, if supported, use the UESBI-Iu IE when received in the COMMON ID message. If UESBI-Iu IE contains an IMEISV the RNC may use this information to determine the characteristics of the UE for subsequent handling.
If the CSG Membership Status IE is included in the COMMON ID message the RAN shall, if supported, take the following actions:
– If the cell that serves the UE is a Hybrid cell, the RNC shall store the value contained in the CSG Membership Status IE and replace any previously stored membership status value by this new one. The RNC may use such information to perform differentiated treatment for member and non-member UEs.
– If the cell that serves the UE is a CSG cell, and the CSG Membership Status IE is set to “non-member”, the RNC should initiate actions to ensure that the UE is no longer served by the CSG cell as defined in TS 25.467 [55].
If the SNA Access Information IE is contained in the COMMON ID message, the RNC shall store this information and use it to determine whether the UE has access to radio resources in the UTRAN. The RNC shall consider that the UE is authorised to access only the PLMNs identified by the PLMN identity IEs in the SNA Access Information IE. If the Authorised SNAs IE is included for a given PLMN (identified by the PLMN identity IE), then the RNC shall consider that the access to radio resources for the concerned UE is restricted to the LAs contained in the SNAs identified by the SNAC IEs.
If the Power Saving Indicator IE is contained in the COMMON ID message and the RNC shall if supported, store this information and use when determining to send the UE back to the PSM mode if the value is "PSM Configured" or to send the UE back to the eDRX mode in Idle if the value is "eDRX Configured", as defined in TS 23.682 [68].
In case of GWCN configuration for a network sharing non-supporting UE, the COMMON ID message shall include, if available, the Selected PLMN identity IE. If received, the RNC shall store this information.
In case SRVCC functionality is supported by the UE and CN, the CN shall include SRVCC Operation Possible IE in COMMON ID message.
In case rSRVCC functionality is supported by the UE and CN, the CN shall include rSRVCC Operation Possible IE in COMMON ID message.
If the Management Based MDT Allowed IE is included in the COMMON ID message, the RNC shall use it, if supported, together with information in the Management Based MDT PLMN List IE, if available, to allow subsequent selection of the UE for management based MDT as defined in TS 32.422 [38].
Upon receipt of the COMMON ID message the RNC shall
– store the Subscriber Profile ID for RAT/Frequency priority IE and use it as defined in TS 36.300 [52].
Upon receipt of the COMMON ID message the RNC may
– store the Last E-UTRAN PLMN Identity IE and use it as defined in TS 23.272 [67].
8.16.3 Abnormal Conditions
Not applicable.