Single RAN, Rel.

SRAN 20B,
Operating Documentation,
Issue 06

Personal Data Inventory

for Single RAN
DN1000000186
Issue 01
Approved on 2018-08-14

001753Nokia internal Copyright

# use © 2020 Nokia. Nokia confidential.
Nokia is committed to diversity and inclusion. We are continuously reviewing our customer documentation and
consulting with standards bodies to ensure that terminology is inclusive and aligned with the industry. Our future
customer documentation will be updated accordingly.
 

This document includes Nokia proprietary and confidential information, which may not be distributed or disclosed to
any third parties without the prior written consent of Nokia.

This document is intended for use by Nokia’s customers (“You”/ “Your”) in connection with a product purchased or
licensed from any company within Nokia Group of Companies. Use this document as agreed. You agree to notify
Nokia of any errors you may find in this document; however, should you elect to use this document for any
purpose(s) for which it is not intended, You understand and warrant that any determinations You may make or
actions You may take will be based upon Your independent judgment and analysis of the content of this document.

Nokia reserves the right to make changes to this document without notice. At all times, the controlling version is the
one available on Nokia’s site.

No part of this document may be modified.

NO WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY
WARRANTY OF AVAILABILITY, ACCURACY, RELIABILITY, TITLE, NON-INFRINGEMENT, MERCHANTABILITY
OR FITNESS FOR A PARTICULAR PURPOSE, IS MADE IN RELATION TO THE CONTENT OF THIS
DOCUMENT. IN NO EVENT WILL NOKIA BE LIABLE FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO
SPECIAL, DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT
LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY OR DATA
THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATION IN IT, EVEN IN THE CASE OF
ERRORS IN OR OMISSIONS FROM THIS DOCUMENT OR ITS CONTENT.

Copyright and trademark: Nokia is a registered trademark of Nokia Corporation. Other product names mentioned in
this document may be trademarks of their respective owners.

© 2021 Nokia.

001753Nokia internal Copyright

# use © 2020 Nokia. Nokia confidential.
001753Nokia internal Copyright
# use © 2020 Nokia. Nokia confidential.
er documentation and
the industry. Our future

distributed or disclosed to

h a product purchased or
eed. You agree to notify
document for any
ons You may make or
content of this document.

e controlling version is the

OT LIMITED TO ANY
NT, MERCHANTABILITY
ENT OF THIS
G BUT NOT LIMITED TO
SUCH AS BUT NOT
OPPORTUNITY OR DATA
T, EVEN IN THE CASE OF

oduct names mentioned in

001753Nokia internal Copyright

# use © 2020 Nokia. Nokia confidential.
Summary of changes
Changes between document issues are cumulative for a release. Therefore, the latest document issue
contains all changes made to previous issues of this release.

This is the first issue of the document.

001753Nokia internal Copyright

# use © 2020 Nokia. Nokia confidential.
02/28/2022 - 579380914.xls - 6 / 15

Num Data Explanation

1 Data subject VoIP calls It is the flow carrying voice calls.

2 Data subject data traffic It is the flow carrying data calls.

3 Data subject AS signaling (RRC) and transport signaling data It is the signaling flow that carries
personal information such as phone
number, service request, IMSI and IMEI.

4 IMSI (for paging coordination) The IMSI is used to identify the mobile
subcriber.

5 IMSI (for subscriber tracing) The IMSI is used to identify the mobile
subcriber.

Copyright © 2012 Nokia. All rights reserved. 001753Nokia internal use

#
02/28/2022 - 579380914.xls - 7 / 15

6 IMEI (for equipment tracing) The IMEI is used to identify the mobile
equipment.

7 Cell Trace with IMSI (for cell tracing) The IMSI is used to identify the mobile
subscriber.

8 Data subject current location (for troubleshooting purposes) N/A

9 Data subject current location (for subscriber trace purposes) N/A

10 Data subject current location (for Location Based Services) N/A

11 Data subject mobility Mobility of the UE within the network

(path followed in the network, with
timestamps)

12 User data (Radio Layer 2, RLC-AM) User data (IP data ISO OSI Layer 7)
stored in case of RLC-AM
(Acknowledged Mode) inside the SBTS.

13 User data (Radio Layer 2, PDCPu) User data (IP data, ISO OSI Layer 7)
stored by PDCP inside the SBTS.

14 IMSI can be read from BTS traffic. The IMSI is used to identify the mobile
subscriber.

15 Voice data can be caught from BTS transport traffic Voice data of mobile subscribers

16 Data connection can be caught from BTS transport traffic. User data of mobile subscribers

Copyright © 2012 Nokia. All rights reserved. 001753Nokia internal use

#
02/28/2022 - 579380914.xls - 8 / 15

Collection
Purpose Classification

Collecting the data serves for R&D Possibly Identifiable Yes, it can be collected for
tasks. troubleshooting from the service
terminal.

Collecting the data serves for R&D Possibly Identifiable Yes, it can be collected for
tasks. troubleshooting from the service
terminal.

Collecting the data serves for R&D Possibly Identifiable Yes, it is received from the UE.
tasks.

Yes, it is required to provide the Possibly Identifiable Yes, it is received from the Core.
related services.

3GPP specified functionality Possibly Identifiable Trace Collection Entity (TCE): Yes, it
is received from the Core if tracing
has been requested for this one
subscriber.

Copyright © 2012 Nokia. All rights reserved. 001753Nokia internal use

#
02/28/2022 - 579380914.xls - 9 / 15
3GPP specified functionality
3GPP specified functionality
N/A
3GPP specified functionality
Support for location services
Support terminating calls to a UE,
paging, mobility speed estimation,
and so on.
3GPP specified functionality
3GPP specified functionality
3GPP specified functionality
Support for voice calls
Support for internet access
Copyright © 2012 Nokia. All rights reserved.
Possibly Identifiable Trace Collection Entity (TCE): Yes, it
is received from the Core if tracing
has been requested for this one
equipment.
Possibly Identifiable Trace Collection Entity (TCE): Yes, it
is received from the MME if tracing
has been requested for equipment or
subscribers served by the radio cell
for which tracing has been activated.
Possibly Identifiable N/A
Possibly Identifiable N/A
Possibly Identifiable Yes. The location server is forwarded.
Possibly Identifiable Yes, the network is aware of the
movements of the UE.
Possibly Identifiable Yes, storage location inside the
SBTS (TUPu).
Possibly Identifiable Yes, storage location inside the
SBTS (TUPu).
Possibly Identifiable
IMSI is collected for tracing purposes.
Possibly Identifiable
Can be collected on Wireshark or
NetHack on the backhaul interface.
Possibly Identifiable
Can be collected on Wireshark or
NetHack on the backhaul interface.
001753Nokia internal use
#
02/28/2022 - 579380914.xls - 10 / 15

Storage
Retention Processing

Yes, it can be recorded. No Offline analysis

Note: This data is not recorded on

the SBTS itself, but stored on
external hardware which is the
service terminal.

Yes, it can be recorded. No Offline analysis

Note: This data is not recorded on

the SBTS itself, but stored on
external hardware which is the
service terminal.

Yes, it can be recorded. No Offline analysis

Note: This data is not recorded on

the SBTS itself, but stored on
external hardware which is the
service terminal.

Yes, for paging coordination accross As long as the UE is in connected Yes, for paging coordination accross
domains and IMSI-based handovers. mode. For troubleshooting, see domains and IMSI-based handovers.
location.
Yes, storage location inside TCE. No. Offline analysis

Note: IMSI is required when tracing is

activated. Then the IMSI can be
deleted. In the "IMSI to trace data
collection" mapping tables the IMSI is
still present.

To be added into T&R for subscriber

tracing, for example IMSI deletion
request.

Copyright © 2012 Nokia. All rights reserved. 001753Nokia internal use

#
02/28/2022 - 579380914.xls - 11 / 15

Yes, storage location inside TCE. No. Offline analysis

Note: IMEI is required when tracing is

activated. Then the IMEI can be
deleted.

To be added into T&R for subscriber

tracing, for example IMSI deletion
request.

Yes, storage location inside TCE. No. Offline analysis

Note: IMEI is required when tracing is

activated. Then the IMEI can be
deleted.

To be added into T&R for subscriber

tracing, i.e. IMSI deletion request.

N/A N/A N/A

No N/A No

N/A N/A No

It is stored as long as the UE is in N/A Yes, it is used to support the mobility

connected mode. of the UE.

Yes. No. No.

After call drop, the user data is

deleted.

Yes. No.
No.

After call drop, the user data is

deleted (similar to RLC-AM packets)
and additionally deleted by PDCP IP
packet discard implementation.
Not stored Only available in RAM for a short Data between BSC and mobile with
period of time. the BTS in between.

Not stored Only available in RAM for a short Data between BSC and mobile with
period of time. the BTS in between.

Not stored Only available in RAM for a short Data between BSC and mobile with
period of time. the BTS in between.

Copyright © 2012 Nokia. All rights reserved. 001753Nokia internal use

#
02/28/2022 - 579380914.xls - 12 / 15

Access Anonymization Safeguards

Service personnel with access to the When using troubleshooting tools, all Access to service terminal is
service terminal the sensitive information is rendered authenticated.
anonymous (IMSI, IMEI, location).
Call data is stored with the air
interface encryption.
When using R&D tools, it is not
rendered anonymous.
The log files that may contain privacy
data are tagged, then the CAPS-RT
privacy application engine/EMIL is
used to scramble this data (render it
anonymous). More information on the
kind of log files and the
anonymization tool used can be
found with the NSA tool.

Service personnel with access to the When using troubleshooting tools, all Access to service terminal is
service terminal the sensitive information is rendered authenticated.
anonymous (IMSI, IMEI, location).
Call data is stored with the air
interface encryption.
When using R&D tools, it is not
rendered anonymous.
The log files that may contain privacy
data are tagged, then the CAPS-RT
privacy application engine/EMIL is
used to scramble this data (render it
anonymous). More information on the
kind of log files and the
anonymization tool used can be
found with the NSA tool.

Service personnel with access to the When using troubleshooting tools, all Access to service terminal is
service terminal. the sensitive information is rendered authenticated.
anonymous (IMSI, IMEI, location).
Call data is stored with the air
interface encryption.
When using R&D tools, it is not
rendered anonymous.
The log files that may contain privacy
data are tagged, then the CAPS-RT
privacy application engine/EMIL is
used to scramble this data (render it
anonymous). More information on the
kind of log files and the
anonymization tool used can be
found with the NSA tool.

No Call data is stored with the air Not applicable as the IMSI is
interface encryption. required.

Not accessible via BTS SM.
Accessible through a login. IMSI is
transferred in cleartext.
Call data is stored with the air
interface encryption.
TS 32.421: When the security key or
keys transported on control signalling
messages are included in the trace
file, the key values are removed and
replaced with the value “Unavailable”.

Copyright © 2012 Nokia. All rights reserved. 001753Nokia internal use

#
02/28/2022 - 579380914.xls - 13 / 15

Not accessible via BTS SM.
Accessible through a login. IMSI is
transferred in cleartext.
Call data is stored with the air
interface encryption.
TS 32.421: When the security key or
keys transported on control signalling
messages are included in the trace
file, the key values are removed and
replaced with the value “Unavailable”.

Not accessible via BTS SM.
Accessible through a login. IMSI is
transferred in cleartext.
N/A TS 32.421: When the security key or
keys transported on control signalling
messages are included in the trace
file, the key values are removed and
replaced with the value “Unavailable”.

Service personnel with access to the For troubleshooting, all the sensitive Access to the service terminal is
service terminal information is rendered anonymous authenticated.
(IMSI, IMEI, location). Call data is
stored with the air interface
encryption.
When using R&D tools, it is not
rendered anonymous.
The log files that may contain privacy
data are tagged, then the CAPS-RT
privacy application engine/EMIL is
used to scramble this data (render it
anonymous). More information on the
kind of log files and the
anonymization tool used can be
found with the NSA tool.

No No No

No No No

No No No

No. Yes. User data is cipher protected

There is only binding information (optional, configurable by operator).
available, such as bearer ID to TEID AS user data is integrity protected
of GTPu. (mandatory) and cipher protected
(optional, configurable by operator).

No. No. No.

It is not rendered anonymous.

There is no access from the outside
the network element.
Can be accessed outside networks
using packet collection tools such as
Wireshark.
Link to IMSI can be calculated if all
traffic can be fetched.
The IMSI cannot be accessed from
outside the network element.
U-plane CS can be IPSec protected
in case of IPoEth. Traffic is
unprotected in case of IPoTDM or
legacy TDM.

Can be accessed outside networks Link to IMSI can be calculated if all U-plane PS is normally encrypted on
using packet collection tools such as traffic can be fetched. air interface, except if A5/0 is used.
Wireshark.

Copyright © 2012 Nokia. All rights reserved. 001753Nokia internal use

#
02/28/2022 - 579380914.xls - 14 / 15

Accuracy Comments
Relevance

Yes Yes

Yes Yes

Yes Yes

Yes, it is required to provide the Yes (There is no granularity

related services. associated with the IMSI.)

Yes Yes

Copyright © 2012 Nokia. All rights reserved. 001753Nokia internal use

#
02/28/2022 - 579380914.xls - 15 / 15

Yes Yes

Yes Yes

N/A N/A

N/A N/A

N/A N/A

N/A N/A

N/A N/A

N/A N/A

Data is relevant for the defined Data is accurate for the defined
purpose. purpose.

Data is relevant for the defined Data is accurate for the defined
purpose. purpose.

Data is relevant for the defined Data is accurate for the defined
purpose. purpose.

Copyright © 2012 Nokia. All rights reserved. 001753Nokia internal use

#