Authentication

Contents
3.6.13 Authentication

GSM BSS
GBSS17.1
Authentication Feature Parameter
Description
Issue 01
Date 2015-04-20
 HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2020. All rights reserved.

No part of this document may be reproduced or transmitted in any form or by any means without prior written
consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions

and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective holders.
 Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or
representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.

Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base Bantian, Longgang Shenzhen 518129 People's Republic of China

Website: https:/

Email: support@huawei.com

3.6.13 Contents
1 About This Document
1.1 Scope
1.2 General Statements
1.3 Change History

2 Overview
2.1 Introduction
2.2 NEs Supporting the Feature

3 Technical Description
3.1 Authentication Principles
3.2 Authentication Procedure
3.2.1 Authentication Success
3.2.2 Authentication Failure

4 Parameters

5 Counters

6 Glossary

7 Reference Documents

1 About This Document

1.1 Scope

This document describes the technical principles of GBFD-110304 Authentication.

1.2 General Statements

Purpose

Feature Parameter Description documents are intended to acquaint readers with:

 The technical principles of features and their related parameters
 The scenarios where these features are used, the benefits they provide, and the impact
they have on networks and functions
 Requirements of the operating environment that must be met before feature activation
 Parameter configuration required for feature activation, verification of feature
activation, and monitoring of feature performance

This document only provides guidance for feature activation. Feature deployment and feature gains depend
on the specifics of the network scenario where the feature is deployed. To achieve the desired gains, contact
Huawei professional service engineers.

Software Interfaces

Any parameters, alarms, counters, or managed objects (MOs) described in Feature Parameter
Description documents apply only to the corresponding software release. For future software
releases, refer to the corresponding updated product documentation.
1.3 Change History

This section provides information about the changes in different document versions. There
are two types of changes, which are defined as follows:
 Feature change
Changes in features of a specific product version
 Editorial change
Changes in wording or addition of information that was not described in the earlier version

01 (2015-04-20)

This issue does not include any changes.

Draft A (2015-03-23)

Compared with Issue 01 (2013-05-06) of GBSS15.0, Draft B (2015-03-23) of GBSS17.1

includes the following changes.

Change Change Description Parameter

Type Change

Feature Added a new function subset "Authentication Measurement None

change <per Cell>", see 5 Counters.

Editorial None None

 Change Change Description Parameter
Type Change

change

2 Overview

2.1 Introduction

Authentication is a procedure in which the GSM network verifies the validity of the identity
of an MS, that is, verifies the validity of the International Mobile Subscriber Identity (IMSI)
or Temporary Mobile Subscriber Identity (TMSI) transmitted over the Um interface.
Authentication aims to prevent unauthorized subscribers from accessing the network and to
protect the private information of authorized subscribers.
Authentication provides the following functions:
 To check whether the MS is authorized to access the network
 To provide parameters that enable the MS to calculate a new ciphering key
The authentication procedure is always initiated and controlled by the network side.
2.2 NEs Supporting the Feature

Table 2-1 NEs supporting the feature

Feature BSC6900 BSC6910 GBTS eGBTS

Authentication √ √ √ √

√ indicates that the NE supports this feature. × indicates that the NE does not support this feature.

3 Technical Description

3.1 Authentication Principles

The network initiates the authentication procedure in the following situations:

 The MS requests to change the subscriber information restored in the visitor location
register (VLR) or home location register (HLR).
  Services are accessed, such as a mobile originated call (MOC), mobile terminated call
(MTC), MS activation and deactivation, or supplementary services.
 The MS accesses the network for the first time after the MSC/VLR restarts.
 The ciphering key Kc on the network side does not match that on the MS.
During an authentication procedure, an authentication triplet, namely, RAND, Kc, and SERS,
is used. The authentication triplet is calculated in the authentication center (AUC) of the
GSM network. When registering in a GSM network, each subscriber is assigned a mobile
station international ISDN number (MSISDN) and an IMSI. The IMSI is written into the SIM
by a SIM writer. The SIM writer also generates an authentication parameter Ki, which is
stored in the SIM as well as the authentication center. The IMSI and Ki are permanent
information.
A pseudo-random number generator is used in the AUC to generate an unpredictable pseudo
random number RAND. In the AUC, the RAND and Ki are used to generate a signed
response (SRES) by using algorithm A3 and to generate a ciphering key Kc by using
algorithm A8. The three parameters RAND, Kc, and SERS constitute an authentication
triplet, which is stored as part of the subscriber data in the HLR.
Generally, the AUC sends five groups of authentication triplets to the HLR at one time, and
the HLR automatically stores them. The HLR can store a maximum of ten groups of
authentication triplets. Upon request, the HLR sends five groups of authentication triplets to
the MSC or the VLR at one time. The MSC or the VLR uses the authentication triplets one
by one. When only two groups are left, the MSC or VLR requests the HLR for new
authentication triplets again.
The network initiates an authentication procedure by sending an Authentication Request
message to the MS and starts timer T3260. The Authentication Request message carries a
128-bit RAND, which is used to calculate the values of the authentication response
parameters. This message also carries the Ciphering Key Sequence Number (CKSN) assigned
to the ciphering key.
Upon receiving the Authentication Request message, the MS calculates the SRES required by
the Authentication Response message and the new ciphering key Kc. After writing the new
ciphering key Kc and the CKSN into the SIM, the MS sends the network an Authentication
Response message.
Upon receiving the Authentication Response message, the network stops timer T3260 and
checks whether the Authentication Response message is valid.
3.2 Authentication Procedure

3.2.1 Authentication Success

Figure 3-1 shows a successful authentication procedure.

Figure 3-1 Successful authentication procedure

 The Authentication Request message carries a 128-bit RAND and a Ciphering Key
Sequence Number (CKSN).
 The Authentication Response message carries an SRES, which is calculated on the
basis of the RAND and Ki by using algorithm A3.
The network compares the stored SRES with the SRES carried in the Authentication
Response message. If the SRESs are the same, the authentication is successful. After the
authentication succeeds, the subsequent procedure, for example, the ciphering procedure, is
initiated.
3.2.2 Authentication Failure

Authentication Failure
If the authentication fails, that is, if the Authentication Response message is invalid, the
network may distinguish between the following two ways of identification used by the MS:
If the TMSI is used, the network initiates the identification procedure.
 If the IMSI provided by the MS differs from that in the network, the network restarts
the authentication procedure.
 If the IMSI provided by the MS is the expected one, the network responds with an
Authentication Reject message.
If the IMSI is used, the network responds with an Authentication Reject message.
Figure 3-2 shows a failed authentication procedure.
Figure 3-2 Failed authentication procedure

After sending an Authentication Reject message to the MS, the network releases all the
existing MM connections and restarts an RR connection release procedure.
Upon receiving the Authentication Reject message, the MS sets the roaming flag to
prohibited and deletes the information such as TMSI, LAI, and ciphering key.
If the Authentication Reject message is received by an MS in the IMSI Detach Initiated state,
timer T3220 will be stopped after the RR connection is released. The MS, if possible, starts
the local release procedure after the normal release procedure is complete or timer T3220
expires. If not possible, for example, during IMSI detachment at MS power-off, the RR
sublayer on the MS side is aborted.
If the Authentication Reject message is received by an MS in any other state, the MS aborts
any MM connection establishment or call re-establishment procedure, stops timer T3210 or
T3230, releases all the MM connections, starts timer T3240, enters the Wait For Network
Command state, and waits for the release of the RR connection. If the RR connection is not
released after timer T3240 expires, the MS aborts the RR connection. In both cases, either
after an RR connection release triggered by the network or after an RR connection abort
requested by the MS, the MS enters the NO IMSI state, which is a sub-state of the MM Idle
state.

4 Parameters

The following hyperlinked EXCEL files of parameter reference match the software version
with which this document is released.
Base station controller parameter reference
 BSC6900 GSM Parameter Reference: contains the parameters related to the BSC6900
equipment, transport, and radio access functions.
 BSC6910 GSM Parameter Reference: contains the parameters related to the BSC6910
equipment, transport, and radio access functions.
eGBTS Parameter reference
 Node Parameter Reference: contains base station equipment and transport parameters.
 GBTSFunction Parameter Reference: contains all parameters related to radio access
functions, including air interface management, access control, mobility control, and radio
resource management.

You can find the EXCEL files of parameter reference for the software version on the live network from the
product documentation delivered with that version.

FAQ: How do I find the parameters related to a certain feature from parameter
reference?
Step 1: Open the EXCEL file of parameter reference.
Step 2: On the Parameter List sheet, filter the Feature ID column. Click Text Filters and
choose Contains. Enter the feature ID, for example, GBFD-200201.
Step 3: Click OK. All parameters related to the feature are displayed.

5 Counters

The following hyperlinked EXCEL files of performance counter reference match the
software version with which this document is released.
Base station controller performance counter reference
 BSC6900 GSM Performance Counter Reference:
contains the counters related to the
BSC6900 equipment, transport, and radio access functions.
 BSC6910 GSM Performance Counter Reference: contains the counters related to the
BSC6910 equipment, transport, and radio access functions.
eGBTS performance counter reference
 Node Performance Counter Summary: contains base station equipment and transport
counters.
 GBTSFunction Performance Counter Summary: contains all counters related to radio access
functions, including air interface management, access control, mobility control, and radio
resource management.

You can find the EXCEL files of performance counter reference for the software version used on the live
network from the product documentation delivered with that version.
FAQ: How do I find the counters related to a certain feature from performance counter
reference?
Step 1: Open the EXCEL file of performance counter reference.
Step 2: On the Counter Summary(En) sheet, filter the Feature ID column. Click Text
Filters and choose Contains. Enter the feature ID, for example, GBFD-200201.
Step 3: Click OK. All counters related to the feature are displayed.

6 Glossary

For the acronyms, abbreviations, terms, and definitions, see Glossary.

7 Reference Documents

1. 3GPP TS 24.008
2. 3GPP TS 42.009
3. 3GPP TS 43.020
4. BSC6900 Feature List
5. BSC6900 Basic Feature Description