User Data Anonymization (SRAN9.0 - 03)

SingleRAN
User Data Anonymization Feature

Parameter Description
Issue 03
Date 2015-09-30
HUAWEI TECHNOLOGIES CO., LTD.

Copyright Huawei Technologies Co., Ltd. 2015. 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: http://www.huawei.com
Email: support@huawei.com
Issue 03 (2015-09-30) Huawei Proprietary and Confidential i

Copyright Huawei Technologies Co., Ltd.
SingleRAN
User Data Anonymization Feature Parameter Description Contents
Contents
1 About This Document.................................................................................................................. 1

1.1 Scope.............................................................................................................................................................................. 1
1.2 Intended Audience.......................................................................................................................................................... 1
1.3 Change History............................................................................................................................................................... 1
1.4 Differences Between Base Station Types....................................................................................................................... 3
2 Overview......................................................................................................................................... 4
2.1 Background.....................................................................................................................................................................4
2.2 Basic Principles.............................................................................................................................................................. 4
3 User Data Anonymization........................................................................................................... 6

3.1 Anonymization Process.................................................................................................................................................. 6
3.2 HMAC Key Update........................................................................................................................................................ 8
3.3 Service Scope of User Data Anonymization.................................................................................................................. 8
3.3.1 Service Scope on RNC................................................................................................................................................ 8
3.3.2 Service Scope on BSC............................................................................................................................................... 10
3.3.3 Service Scope on NodeB........................................................................................................................................... 12
3.4 Impact of User Data Anonymization on Maintenance and Commissioning Functions............................................... 13
3.4.1 Impact on RNC Maintenance and Commissioning Functions.................................................................................. 13
3.4.2 Impact on BSC Maintenance and Commissioning Functions................................................................................... 14
3.4.3 Impact on NodeB Maintenance and Commissioning Functions............................................................................... 14
4 Engineering Guidelines............................................................................................................. 15
4.1 When to Use User Data Anonymization...................................................................................................................... 15
4.2 Deployment Requirements........................................................................................................................................... 15
4.3 Anonymizing User Data During Site Deployment.......................................................................................................16
4.4 Maintaining Anonymization Configuration During an Upgrade................................................................................. 17
4.5 Activation Observation and Troubleshooting...............................................................................................................18
5 Supplementary Information......................................................................................................19
6 Parameters..................................................................................................................................... 20
7 Counters........................................................................................................................................ 21
8 Glossary......................................................................................................................................... 22
Issue 03 (2015-09-30) Huawei Proprietary and Confidential ii

SingleRAN
User Data Anonymization Feature Parameter Description Contents
9 References..................................................................................................................................... 23
Issue 03 (2015-09-30) Huawei Proprietary and Confidential iii

SingleRAN
User Data Anonymization Feature Parameter Description 1 About This Document
1 About This Document
1.1 Scope
This document describes Huawei WCDMA and GSM user data anonymization function,
including background, basic principles, anonymization process, HMAC key update, service
scope, impact of user data anonymization on maintenance and commissioning functions, and
engineering guidelines.
1.2 Intended Audience

This document is intended for personnel who:
l Need to understand the features described herein
l Work with Huawei products
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:
l Feature change
Changes in features of a specific product version
l Editorial change
Changes in wording or addition of information that was not described in the earlier
version
SRAN9.0 03 (2015-09-30)
Compared with Issue 01 (2014-04-30) of SRAN9.0, Issue 03 (2015-09-30) of SRAN9.0
includes the following changes.
Issue 03 (2015-09-30) Huawei Proprietary and Confidential 1

SingleRAN
Change Change Description Paramet

Type er
Change
Feature None None

change
Editorial Revised some descriptions in this document. None

change
SRAN9.0 02 (2015-03-23)
Compared with Issue 01 (2014-04-30) of SRAN9.0, Issue 02 (2015-03-23) of SRAN9.0
includes the following changes.

Type er
Change
Feature None None

change
Editorial Revised some descriptions in this document. None

change
SRAN9.0 01 (2014-04-30)
This issue does not include any changes.
SRAN9.0 Draft A (2014-01-20)

Compared with 01 (2013-04-28) of SRAN8.0, Draft A (2014-01-20) of SRAN9.0 includes the
following changes.

Type er
Change
Feature Changed the name of Huawei mobile element management None

change system from M2000 to U2000.
Editorial None None

change

SingleRAN
1.4 Differences Between Base Station Types

The features described in this document are implemented in the same way on micro, macro,
and LampSite base stations.

SingleRAN
User Data Anonymization Feature Parameter Description 2 Overview
2 Overview
2.1 Background
Huawei wireless network equipment (BSC, RNC, and NodeB) has maintenance and
commissioning functions (such as user tracing, interface tracing, and logging) that use the
following user identity information:
l International mobile subscriber identity (IMSI)

l International mobile equipment identity (IMEI)
l Mobile station international ISDN number (MSISDN)
l User equipment (UE) or mobile station (MS) Internet Protocol (IP) address
Some countries and regions have personal privacy protection laws and regulations. Improper
use, including abuse and disclosure, of personal data by operators or vendors would be a
violation of these laws and regulations.
To protect personal privacy, Huawei wireless network equipment supports user data
anonymization. This function makes user identity information anonymous to the maintenance
and commissioning functions.
NOTE
"User data" in the term "user data anonymization" refers to the user identity information.
User data anonymization is disabled by default. During a site deployment or upgrade, the
operator's maintenance personnel should enable this function as required by local laws or
regulations.
2.2 Basic Principles

User data anonymization uses the Hashed message authentication code-secure hash
algorithm-256 bit length (HMAC-SHA256) algorithm to perform irreversible hash operations
on user identity information for maintenance and commissioning functions (such as message
tracing and logging) and replaces the information in user identity fields with the operation
results. Hash operations use an HMAC key, which is provided and managed by the operator.

SingleRAN
User Data Anonymization Feature Parameter Description 2 Overview
The user data anonymization function is enabled or disabled on the M2000, and the HMAC
key is also maintained on the M2000. For the detailed procedures, see section" 4 Engineering
Guidelines" .
With user data anonymization enabled, maintenance personnel cannot use the IMSI, IMEI, or
MSISDN of a UE or MS to perform a maintenance or commissioning task. They cannot see
the identity of the traced user. This prevents abuse of the maintenance and commissioning
functions.
Enabling user data anonymization does not affect the uniqueness of user identities or the
maintenance and commissioning functions that involve the uniqueness of user identities.

SingleRAN
User Data Anonymization Feature Parameter Description 3 User Data Anonymization
3 User Data Anonymization
3.1 Anonymization Process

Figure 3-1 shows the anonymization process using message tracing as an example.

SingleRAN
Figure 3-1 Anonymization process
1. On the M2000 graphical user interface (GUI), the operator's maintenance personnel
enable user data anonymization and set the HMAC key. After it connects to the M2000,
the wireless network equipment synchronizes the function status and key information
with the M2000.
To query the setting of the anonymization switch, run the LST
USERIDANONSWITCH command on the wireless network equipment side. If the
User Identity Anonymity Switch parameter is set to ON, user data anonymization is
enabled.
2. The vendor's or operator's maintenance personnel submit the user identity (user ID for
short) in plaintext to the operator for anonymization. "User ID" here refers to the IMSI,
IMEI, or MSISDN.
3. The operator's maintenance personnel use the HMACUtil tool to anonymize the user ID
and return the anonymous user ID to the maintenance personnel.
4. The vendor's or operator's maintenance personnel log in to the local maintenance
terminal (LMT) and use the anonymous user IDs to perform maintenance and
commissioning functions.
The user IDs are anonymous in the maintenance and commissioning results.

SingleRAN
NOTE
If the maintenance personnel want to anonymize a batch of user IDs, they must provide a user ID list.
After verifying the user ID list, the operator's maintenance personnel use the HMACUtil tool to generate
an anonymous user ID list, and they return the anonymous user ID list to the maintenance personnel.
The maintenance personnel use the anonymous user IDs to perform maintenance and commissioning on
specified equipment.
3.2 HMAC Key Update

To better protect personal privacy, the operator's maintenance personnel can update the
HMAC key when necessary.
The operator's maintenance personnel update the HMAC key in the Anonymous Policy
Management window on the U2000 client. On the Anonymous Cypher Key Management
tab page, press F1 on the keyboard to display the Help topic on how to update the HMAC
key.
3.3 Service Scope of User Data Anonymization

This section provides the service scope of the user data anonymization function for the
Huawei RNC, BSC, and NodeB.
3.3.1 Service Scope on RNC

The tables in this section list the anonymized data inputs and outputs of the maintenance and
commissioning functions on the RNC.
Table 3-1 Message tracing function on the RNC LMT
Tracing Type Anonymized Input Anonymized Output in

Message Tracing Result
Tracing messages on the Iu None IMSI, IMEI, MSISDN, and

interface UE IP address
Tracing messages on the Iub None IMSI, IMEI, and MSISDN

interface
Tracing messages on the Iur None IMSI, IMEI, MSISDN, and

Tracing messages on the Uu None IMSI, IMEI, MSISDN, and

Tracing messages on the None IMSI, IMEI, MSISDN, and

Iupc interface UE IP address
Tracing intelligent optimum None IMSI, IMEI, MSISDN, and

sample (IOS) messages UE IP address
Tracing UE messages IMSI, IMEI, and MSISDN IMSI, IMEI, MSISDN, and
UE IP address

SingleRAN

Tracing cell messages None IMSI, IMEI, MSISDN, and

UE IP address
Table 3-2 Performance monitoring function on the RNC LMT

Monitoring Type Anonymized Input Anonymized Output in
Performance Monitoring
Result
Monitoring connection IMSI N/A

performance
Table 3-3 RNC MML-based configuration function

MML Command Anonymized Input
l ADD UVIPIMSI IMSI

l RMV UVIPIMSI
Table 3-4 RNC logging function

Log Type Anonymized Information in Log
Measurement report (MR) IMSI, IMEI, MSISDN, and UE IP address
Call history record (CHR) IMSI, IMEI, MSISDN, and UE IP address
With user data anonymization enabled, the message tracing results, performance monitoring
results, and CHR/MR logs described in Table 3-1 through Table 3-4 no longer contain
original user identity information.
Figure 3-2 shows an example of user tracing on the RNC. In this example, the IMSI in the
traced COMMON ID message on the Iu interface is anonymized. The IMSI now contains
hexadecimal digits, such as A and F, unlike a normal IMSI that contains decimal digits from 0
to 9.

SingleRAN
Figure 3-2 Example of user data anonymization
3.3.2 Service Scope on BSC

Table 3-5 Message tracing function on the BSC LMT
Trace Type Anonymized Input Anonymized Output in
Message tracing over the A None IMSI, IMEI, and MSISDN

interface (BSSAP message
tracing)
CS domain message tracing None IMSI, IMEI, and MSISDN

over the Um interface
PS domain message tracing None IMSI

over the Um interface
CS domain message tracing None IMSI and IMEI

over the Abis interface (RSL
message tracing)
SIG message tracing over the None IMSI

Gb interface
PTP message tracing over the None IMSI, IMEI, and MS IP

Gb interface address
Group call message tracing None IMSI, IMEI, MSISDN, and

MS IP address
Single-user CS tracing IMSI, IMEI, and IMSI, IMEI, and MSISDN

MSISDN

SingleRAN

Single-user PS tracing IMSI IMSI, IMEI, and MS IP

address
Inter-BSC interface tracing None IMSI
Message tracing over the LB None IMSI and IMEI

interface
Table 3-6 BSC MML-based configuration function

MML Command Anonymized Input
ADD GCSCHRUSER IMSI, MSISDN, and IMEI
ADD GPSCHRUSER IMSI
Table 3-7 BSC logging function

CHR IMSI, IMEI, MSISDN, and MS IP address
MR IMSI
One-way audio log IMSI, IMEI, and MSISDN
Service Scope on NodeB
Table 3-8 User tracing function on the NodeB LMT

User tracing IMSI N/A
NOTE
For other tracing functions, such as message tracing over the Iub interface, the NodeB removes the IMSI
to protect user privacy data before sending messages to the LMT or U2000.

SingleRAN
Table 3-9 Feature monitoring function on the NodeB LMT

Result
HSPA monitoring IMSI N/A
Table 3-10 NodeB logging function
CHR IMSI
3.3.3 Service Scope on NodeB

The tables in this section list the anonymized data inputs and outputs of the maintenance and
commissioning functions on the NodeB.
Table 3-11 User tracing function on the NodeB LMT

Tracing user messages IMSI N/A
NOTE
For other tracing functions, such as Iub interface tracing, before sending messages to the LMT or
M2000, the NodeB removes the IMSI to protect user privacy data.
Table 3-12 Feature monitoring function on the NodeB LMT

Result
HSPA monitoring IMSI N/A
Table 3-13 NodeB logging function
CHR IMSI

SingleRAN
3.4 Impact of User Data Anonymization on Maintenance

and Commissioning Functions
After user data anonymization is enabled, maintenance and commissioning operations that
involve user identity information need to be modified on the Huawei RNC, BSC, and NodeB
as described in this section.
3.4.1 Impact on RNC Maintenance and Commissioning Functions

l User tracing and connection performance monitoring tasks require an anonymous user
ID.
Figure 3-3 uses a user tracing task as an example. In this example, an anonymous IMSI
is entered.
Figure 3-3 UE Trace dialog box after user data anonymization is enabled
NOTE
If the anonymization switch is turned on or the HMAC key changes during user tracing or connection
performance monitoring, maintenance personnel must stop the task and restart the task with an
anonymous user ID. If the personnel do not restart the task, no result will be provided, because of IMSI/
IMEI/MSISDN match failures.
l The VIPIMSI(BSC6900,BSC6910) parameter in the ADD UVIPIMSI or RMV
UVIPIMSI command requires an anonymous user ID.
Before creating an IOS tracing task, maintenance personnel typically take the optional
step to run the ADD UVIPIMSI command to set the IMSI to be traced. If user data
anonymization is enabled, the VIPIMSI(BSC6900,BSC6910) parameter in the ADD
UVIPIMSI command requires an anonymous user ID.
After user data anonymization is enabled or the HMAC key is updated, the original
parameter configuration in the ADD UVIPIMSI command becomes ineffective. To
solve this problem, maintenance personnel must perform the following steps:
a. Run the LST UVIPIMSI command to check whether a VIP IMSI has been set for
tracing.
b. If the VIP IMSI has been set, run the RMV UVIPIMSI command to remove the
configuration.
c. Run the ADD UVIPIMSI command to reconfigure the VIP IMSI of the UE to be
traced.
When reconfiguring the VIP IMSI, set the VIPIMSI(BSC6900,BSC6910) parameter to the
anonymous IMSI, which is provided by the operator.

SingleRAN
3.4.2 Impact on BSC Maintenance and Commissioning Functions

l CS-domain single-user tracing tasks require an anonymous user ID.
NOTE
If the anonymization switch is turned on or the HMAC key changes during CS-domain single-user
tracing, maintenance personnel must stop the task and restart the task with an anonymous user ID. If the
personnel do not restart the task, no result will be provided, because of IMSI/IMEI/MSISDN match
failures.
l The IMSI, MSISDN, and IMEI parameters in the ADD GCSCHRUSER command and
the IMSI parameter in the ADD GPSCHRUSER command require an anonymous user
ID.
If maintenance personnel need to provide CHR logs for specified users, first they need to
run the ADD GCSCHRUSER or ADD GPSCHRUSER command to configure the user
identity (IMSI/MSISDN/IMEI) list. If user data anonymization is enabled, the IMSI/
MSISDN/IMEI parameter in the ADD GCSCHRUSER command and the IMSI
parameter in the ADD GPSCHRUSER command require an anonymous user ID.
After user data anonymization is enabled or the HMAC key is updated, the original
parameter configuration in the ADD GCSCHRUSER and ADD GPSCHRUSER
commands becomes ineffective. To solve this problem, maintenance personnel must
perform the following steps:
1. Run the LST GCSCHRUSER or LST GPSCHRUSER command to check whether the
IMSI/MSISDN/IMEI of the specified user has been configured.
2. If the IMSI/MSISDN/IMEI has been configured, run the RMV GCSCHRUSER or
RMV GPSCHRUSER command to remove the configuration.
3. Run the ADD GCSCHRUSER or ADD GPSCHRUSER command to reconfigure the
IMSI/MSISDN/IMEI of the specified user.
In the command, set the IMSI(ADD GCSCHRUSER)/IMSI(ADD GPSCHRUSER)/
MSISDN/IMEI parameter to the anonymous IMSI/MSISDN/IMEI provided by the
operator.
3.4.3 Impact on NodeB Maintenance and Commissioning

Functions
User tracing and HSPA monitoring tasks require an anonymous user ID.
NOTE
If the anonymization switch is turned on or the HMAC key changes during user tracing or HSPA
monitoring, maintenance personnel must stop the task and restart the task with an anonymous user ID. If
the personnel do not restart the task, no result will be provided, because of IMSI match failures.

SingleRAN
User Data Anonymization Feature Parameter Description 4 Engineering Guidelines
4 Engineering Guidelines
4.1 When to Use User Data Anonymization

Decide whether to enable user data anonymization according to the laws and regulations of
the country or region.
4.2 Deployment Requirements

License
User data anonymization does not require licenses.
Tool
You can log in to http://support.huawei.com, view the information about HMACUtil or
search HMACUtil on the Product Software tab page, and download the HMACUtil
installation package to the local computer.
Version
NE/Client/Tool Product Model/Series Earliest Version to Which This
Function Applies
RNC/BSC BSC6900 BSC6900 V900R015C00
NodeB 3900 series base station BSC6910 V100R015C00
DBS3800 BTS3900V100R008SPC100
BTS3812E/BTS3812AE DBS3800V100R015C00
U2000 iManager U2000 V100R015C00
HMACUtil HMACUtil iManager U2000 V200R013C00SPC100

V100R002

SingleRAN
4.3 Anonymizing User Data During Site Deployment

Use the U2000 to set the anonymization switch and maintain the HMAC key. On the U2000
client, choose Monitor > Signaling Trace > Anonymous Policy Management. Then, the
Anonymous Cypher Key Management tab page is displayed.
User data anonymization is performed by the operator's maintenance personnel as follows:
Step 1 Turn on the anonymization switch on the U2000 client.

To view the Help topic with details about how to turn on the anonymization switch, press F1
on the Anonymous Cypher Key Management tab page.
Step 2 Set the HMAC key on the U2000 client.
To view the Help topic with details about how to set the HMAC key, press F1 on the
Anonymous Cypher Key Management tab page. The HMAC key entered must be
hexadecimal.
Step 3 Use the HMACUtil tool to anonymize the user ID.
----End
In the save path of the HMACUtil installation package, decompress the package. To start the
HMACUtil tool, double-click HMACUtil.jar. Figure 4-1 shows the user interface of the
tool.
For details about how to use HMACUtil to anonymize a user ID, see HMACUtil V100R001
Release Notes V1.2. You can log in to http://support.huawei.com, view the information
about HMACUtil or search HMACUtil on the Product Software tab page, and download the
HMACUtil installation package to the local computer.

SingleRAN
Figure 4-1 HMACUtil window
4.4 Maintaining Anonymization Configuration During an

Upgrade
During an upgrade, newly added wireless network equipment automatically synchronizes the
anonymization switch and HMAC key settings with the M2000.
To view the synchronization result, choose Monitor > Signaling Trace > Anonymous Policy
Management on the M2000 client. The synchronization result is displayed on the
Consistency Check tab page, as shown in Figure 4-2. If any pieces of equipment failed to
synchronize, select them and manually trigger batch synchronization.

SingleRAN
Figure 4-2 Consistency Check tab page
To view the Help topic with details about how to perform a consistency check, press F1 on
the Consistency Check tab page.
4.5 Activation Observation and Troubleshooting

Run the LST USERIDANONSWITCH command and query the value of the User Identity
Anonymity Switch parameter to determine whether the user data anonymization function is
enabled.
l The function is enabled if the parameter is set to ON on the wireless network equipment
side and M2000.
l The function is not enabled if the parameter is set to ON on the M2000 but to OFF on
the wireless network equipment side. When this occurs, check whether the operation and
maintenance (O&M) channel between the wireless network equipment and M2000 is
disconnected.
If the channel is disconnected, restore the channel.
If the channel is connected, contact Huawei technical support personnel.
When the function is enabled, the user identity information in the message tracing results,
performance monitoring results, and CHR/MR logs described in Table 3-1 through Table 3-4
is no longer in a plaintext form.
If the user identity information is still in a plaintext form, contact Huawei technical support
personnel.

SingleRAN
User Data Anonymization Feature Parameter Description 5 Supplementary Information
5 Supplementary Information
An IMSI is a character string composed of 14 or 15 decimal digits (0 through 9). The HMAC-
SHA256 algorithm uses an IMSI as input to produce a string. Then, the algorithm takes the
leftmost eight bytes of the string and converts each of the bytes into two hexadecimal digits (0
through F). Finally, the algorithm generates a 16-digit hexadecimal character string. This
character string is the anonymous IMSI.
An IMEI is a character string composed of 15 decimal digits and an international mobile
station equipment identity and software version (IMEISV) is a character string composed of
16 decimal digits. The leftmost eight digits of an IMEI/IMEISV, known as the type allocation
code (TAC), are not hashed. The remaining digits of the IMEI/IMEISV are used by the
HMAC-SHA256 algorithm as input to produce a string. The algorithm takes the leftmost four
bytes of the string and converts each of the bytes into two hexadecimal digits. Finally, the
algorithm generates an 8-digit hexadecimal character string. The TAC plus this character
string is the anonymous IMEI/IMEISV.
An MSISDN is a character string composed of less than 22 decimal digits. The HMAC-
SHA256 algorithm uses an MSISDN as input to produce a string. Then, the algorithm takes
the leftmost 11 bytes of the string and converts each of the bytes into two hexadecimal digits.
Finally, the algorithm generates a 22-digit hexadecimal character string. This character string
is the anonymous MSISDN.
An IPv4 address is a 4-byte character string. The HMAC-SHA256 algorithm uses an IPv4
address as input to produce a string. The leftmost four bytes of the string form the anonymous
IPv4 address.
An IPv6 address is a 16-byte character string. The HMAC-SHA256 algorithm uses an IPv6
address as input to produce a string. The leftmost 16 bytes of the string form the anonymous
IPv6 address.
NOTE
Anonymous MSISDNs are now presented in CHR and MR logs. When initiating a message tracing or a
performance monitoring task, you must enter anonymous MSISDNs. In tracing results, however, all the
anonymous MSISDNs are replaced by 0.
IPv4/IPv6 addresses are hashed only when the RNC/BSC uses the software version RAN14.0/GBSS14.0
or later. When the RNC/BSC uses the software version RAN12.0/GBSS12.0 or RAN13.0/GBSS13.0, all
the digits of an IPv4/IPv6 address are replaced by 0. When the RNC/BSC uses a software version earlier
than RAN12.0/GBSS12.0, all IPv4/IPv6 addresses are presented in a plaintext form.

SingleRAN
User Data Anonymization Feature Parameter Description 6 Parameters
6 Parameters
Table 6-1 Parameters

Parame NE MML Feature Feature Description
ter ID Comma ID Name
nd
VIPIMS BSC690 ADD None None Meaning: IMSI of the UE, A 6- to 15-character string
I 0 UVIPIM that consists of numbers 0 to 9, case-insensitive letters
SI A to F, or both.
MOD GUI Value Range: 6~15 characters
UVIPIM Unit: None
SI
Actual Value Range: 6~15 characters
RMV
UVIPIM Default Value: None
SI
VIPIMS BSC691 ADD None None Meaning: IMSI of the UE, A 6- to 15-character string
I 0 UVIPIM that consists of numbers 0 to 9, case-insensitive letters
SI A to F, or both.
MOD GUI Value Range: 6~15 characters
UVIPIM Unit: None
SI
Actual Value Range: 6~15 characters
RMV
UVIPIM Default Value: None
SI

SingleRAN
User Data Anonymization Feature Parameter Description 7 Counters
7 Counters
There are no specific counters associated with this feature.

SingleRAN
User Data Anonymization Feature Parameter Description 8 Glossary
8 Glossary
For the acronyms, abbreviations, terms, and definitions, see Glossary.

SingleRAN
User Data Anonymization Feature Parameter Description 9 References
9 References
There are no specific reference documents associated with this feature.


User Data Anonymization (SRAN9.0 - 03)

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

User Data Anonymization (SRAN9.0 - 03)

Загружено:

Авторское право:

Доступные форматы

SingleRAN

User Data Anonymization Feature

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 03 (2015-09-30) Huawei Proprietary and Confidential i

1 About This Document.................................................................................................................. 1

3 User Data Anonymization........................................................................................................... 6

Issue 03 (2015-09-30) Huawei Proprietary and Confidential ii

Issue 03 (2015-09-30) Huawei Proprietary and Confidential iii

1 About This Document

1.2 Intended Audience

1.3 Change History

Issue 03 (2015-09-30) Huawei Proprietary and Confidential 1

Change Change Description Paramet

Feature None None

Editorial Revised some descriptions in this document. None

Change Change Description Paramet

Feature None None

Editorial Revised some descriptions in this document. None

SRAN9.0 Draft A (2014-01-20)

Change Change Description Paramet

Feature Changed the name of Huawei mobile element management None

Editorial None None

Issue 03 (2015-09-30) Huawei Proprietary and Confidential 2

1.4 Differences Between Base Station Types

Issue 03 (2015-09-30) Huawei Proprietary and Confidential 3

l International mobile subscriber identity (IMSI)

2.2 Basic Principles

Issue 03 (2015-09-30) Huawei Proprietary and Confidential 4

Issue 03 (2015-09-30) Huawei Proprietary and Confidential 5

3 User Data Anonymization

3.1 Anonymization Process

Issue 03 (2015-09-30) Huawei Proprietary and Confidential 6

Figure 3-1 Anonymization process

Issue 03 (2015-09-30) Huawei Proprietary and Confidential 7

3.2 HMAC Key Update

3.3 Service Scope of User Data Anonymization

3.3.1 Service Scope on RNC

Table 3-1 Message tracing function on the RNC LMT

Tracing Type Anonymized Input Anonymized Output in

Tracing messages on the Iu None IMSI, IMEI, MSISDN, and

Tracing messages on the Iub None IMSI, IMEI, and MSISDN

Tracing messages on the Iur None IMSI, IMEI, MSISDN, and

Tracing messages on the Uu None IMSI, IMEI, MSISDN, and

Tracing messages on the None IMSI, IMEI, MSISDN, and

Tracing intelligent optimum None IMSI, IMEI, MSISDN, and

Issue 03 (2015-09-30) Huawei Proprietary and Confidential 8

Tracing Type Anonymized Input Anonymized Output in

Tracing cell messages None IMSI, IMEI, MSISDN, and

Table 3-2 Performance monitoring function on the RNC LMT

Monitoring connection IMSI N/A

Table 3-3 RNC MML-based configuration function

l ADD UVIPIMSI IMSI

Table 3-4 RNC logging function

Measurement report (MR) IMSI, IMEI, MSISDN, and UE IP address

Call history record (CHR) IMSI, IMEI, MSISDN, and UE IP address

Issue 03 (2015-09-30) Huawei Proprietary and Confidential 9

Figure 3-2 Example of user data anonymization

3.3.2 Service Scope on BSC

Message tracing over the A None IMSI, IMEI, and MSISDN

CS domain message tracing None IMSI, IMEI, and MSISDN

PS domain message tracing None IMSI