hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
595
| content
stringlengths 0
6.67M
|
|---|---|---|---|
539f847bb6cd6c0ba766caacc29710d4
|
23.008
|
3.15.1 Allowed WAF and/or WWSF Identity List
|
An Allowed WAF or WWSF Identity identifies a WebRTC Authentication Function or WebRTC Web Server Function the subscription is allowed to use. See 3GPP TS 33.203 [49]. Multiple WAF or WWSF identities may be stored within the Allowed WAF and/or WWSF Identity List.
The Allowed WAF and/or WWSF Identity List is permanent data stored in the HSS and in the S-CSCF.
|
539f847bb6cd6c0ba766caacc29710d4
|
23.008
|
3.16 V2X Service (V2X)
| |
539f847bb6cd6c0ba766caacc29710d4
|
23.008
|
3.16.1 General
|
Following clauses describe the data that are defined on per user basis and are related to V2X Service (V2X).
|
539f847bb6cd6c0ba766caacc29710d4
|
23.008
|
3.16.2 V2X Subscription data for the network scheduled LTE sidelink communication
| |
539f847bb6cd6c0ba766caacc29710d4
|
23.008
|
3.16.2.1 V2X-Permission
|
The V2X-Permision is part of the V2X Subscription data information for the network scheduled LTE sidelink communication and is specified in 3GPP TS 29.272 [81].
V2X-Permission is permanent data conditionally stored in HSS and MME.
|
539f847bb6cd6c0ba766caacc29710d4
|
23.008
|
3.16.2.2 UE-PC5-AMBR
|
The UE-PC5-AMBR is part of the V2X Subscription data information for the network scheduled LTE sidelink communication and is specified in 3GPP TS 29.272 [81].
UE-PC5-AMBR is permanent data conditionally stored in HSS and MME.
|
539f847bb6cd6c0ba766caacc29710d4
|
23.008
|
3.16.2.3 V2X-PC5-Allowed-PLMN
|
The V2X-PC5-Allowed-PLMN is part of the V2X Subscription data and is specified in 3GPP TS 29.388 [108].
V2X-PC5-Allowed-PLMN is permanent data conditionally stored in HSS and V2X Control Function.
|
539f847bb6cd6c0ba766caacc29710d4
|
23.008
|
3.16.3 V2X Authorization data
| |
539f847bb6cd6c0ba766caacc29710d4
|
23.008
|
3.16.3.1 V2X-Permission-in-VPLMN
|
The V2X-Permision-VPLMN is part of the V2X authorization data and is specified in 3GPP TS 29.389 [109].
V2X-Permission-in-VPLMN is permanent data conditionally stored in V2X Control Function.
|
539f847bb6cd6c0ba766caacc29710d4
|
23.008
|
3.16.3.2 V2X-Application-Server
|
The V2X-Application-Server is part of the V2X authorization data and is specified in 3GPP TS 29.389 [109].
V2X-Application-Server is permanent data conditionally stored in V2X Control Function.
|
539f847bb6cd6c0ba766caacc29710d4
|
23.008
|
3.16.3.3 PC5-RAT-Type
|
The PC5-RAT-Type is part of the V2X authorization data and is specified in 3GPP TS 29.389 [109].
PC5-RAT-Type is permanent data conditionally stored in HSS and V2X Control Function.
|
539f847bb6cd6c0ba766caacc29710d4
|
23.008
|
3.16.4 V2X Control Function Identity
|
V2X Function Identity is specified in 3GPP TS 29.388 [108].
The V2X Control Function Identity is temporary subscriber data and is conditionally stored in the HSS.
|
539f847bb6cd6c0ba766caacc29710d4
|
23.008
|
3.16.5 V2X Subscription data for the network scheduled NR sidelink communication
| |
539f847bb6cd6c0ba766caacc29710d4
|
23.008
|
3.16.5.1 V2X-Permission
|
The V2X-Permision is part of the V2X Subscription data information for the network scheduled NR sidelink communication and is specified in 3GPP TS 29.272 [81].
V2X-Permission is permanent data conditionally stored in HSS and MME.
|
539f847bb6cd6c0ba766caacc29710d4
|
23.008
|
3.16.5.2 UE-PC5-AMBR
|
The UE-PC5-AMBR is part of the V2X Subscription data information for the network scheduled NR sidelink communication and is specified in 3GPP TS 29.272 [81].
UE-PC5-AMBR is permanent data conditionally stored in HSS and MME.
|
539f847bb6cd6c0ba766caacc29710d4
|
23.008
|
3.16.5.3 V2X-PC5-Allowed-PLMN
|
The V2X-PC5-Allowed-PLMN is part of the V2X Subscription data and is specified in 3GPP TS 29.388 [108].
V2X-PC5-Allowed-PLMN is permanent data conditionally stored in HSS and V2X Control Function.
|
539f847bb6cd6c0ba766caacc29710d4
|
23.008
|
3.16.5.4 UE-PC5-QoS
|
The UE-PC5-QoS is part of the V2X Subscription data information for the network scheduled NR sidelink communication and is specified in 3GPP TS 29.272 [81].
UE-PC5-AMBR is permanent data conditionally stored in HSS and MME.
|
539f847bb6cd6c0ba766caacc29710d4
|
23.008
|
4 Summary of data stored in location registers
|
Table 5.1 gives an overview of data stored in location registers for non-GPRS Network Access Mode (CS).
Table 5.2 shows the data stored in the location registers, in the Gn/Gp-SGSN and in the GGSN for GPRS Network Access Mode.
Tables 5.2A-1 show the data stored in the location registers, in the SGSN, S4-SGSN, MME, S-GW, P-GW, ePDG, 3GPP AAA server and 3GPP AAA server Proxy for EPS Network Access Mode.
Table 5.2B-1 show the data stored by the UDM, AMF, SMF, SMSF, AUSF and NEF in the 5G System.
Table 5.3 gives an overview of data stored for IP Multimedia services.
In the tables, M = mandatory means that this parameter is stored for all subscribers with subscription of the Network Access Mode as shown in the table heading and defining the table; and C = conditional means that the parameter is subject to some condition (e.g. subscription of teleservice or other services, reception of optional message or short-lived data). The type indication indicates whether the subscriber data is temporary (T) or permanent (P) data, where permanent data can be set and modified but by the operator, whereas the temporary data are set and changed automatically by network functions.
|
539f847bb6cd6c0ba766caacc29710d4
|
23.008
|
5 Accessing subscriber or PSI data
|
It shall be possible to retrieve or store subscriber data concerning a specific MS from the HSS by use of each of the following references:
- International Mobile Subscriber Identity (IMSI);
- Mobile Station ISDN Number (MSISDN).
It shall be possible to retrieve CSG subscriber data concerning a specific roaming MS from the CSS by use of each of the following references:
- International Mobile Subscriber Identity (IMSI).
It may be possible to retrieve subscriber data concerning a specific roaming MS from the CSS by use of each of the following references:
- Mobile Station ISDN Number (MSISDN).
It shall be possible to retrieve or store subscriber IP Multimedia service data concerning a specific IMS subscription from the HSS by use of each of the following references:
- Private User Identity;
- Public User Identity.
It shall be possible to retrieve or store PSI IP Multimedia service data from the HSS by use of each of the following references:
- Public Service Identity.
It shall be possible to retrieve or store subscriber data concerning a specific MS from the VLR by use of each of the following references:
- International Mobile Subscriber Identity (IMSI);
- Temporary Mobile Subscriber Identity (TMSI).
It shall be possible to retrieve or store subscriber data concerning a specific MS from the SGSN by use of each of the following references:
- International Mobile Subscriber Identity (IMSI);
- Packet Temporary Mobile Subscriber identity (P-TMSI);
- International Mobile Equipment Identity (IMEI) for emergency attached UEs without IMSI (e.g; UICCless UE) or with an unauthenticated IMSI.
It shall be possible to retrieve or store subscriber data concerning a specific MS from the GGSN by use of the following reference:
- International Mobile Subscriber Identity (IMSI);
- International Mobile Equipment Identity (IMEI) for emergency attached UEs without IMSI (e.g; UICCless UE) or with an unauthenticated IMSI.
It shall be possible to retrieve or store subscriber data concerning a specific MS from the MME by use of each of the following references:
- International Mobile Subscriber Identity (IMSI);
- Globally Unique Temporary Identity (GUTI);
- International Mobile Equipment Identity (IMEI) for emergency attached UEs without IMSI (e.g; UICCless UE) or with an unauthenticated IMSI.
It shall be possible to retrieve or store subscriber data concerning a specific MS from the S-GW and P-GW by use of the following reference:
- International Mobile Subscriber Identity (IMSI);
- International Mobile Equipment Identity (IMEI) for emergency attached UEs without IMSI (e.g; UICCless UE) or with an unauthenticated IMSI.
It shall be possible to retrieve or store subscriber data concerning a specific MS from the 3GPP AAA Server by use of each of the following references:
- International Mobile Subscriber Identity (IMSI);
- Mobile Subscriber ISDN Number (MSISDN).
- International Mobile Equipment Identity (IMEI) for emergency attached UEs without IMSI (e.g; UICCless UE) or with an unauthenticated IMSI.
It shall be possible to retrieve or store subscriber data concerning a specific MS from the 3GPP AAA Proxy by use of the following reference:
- Mobile Subscriber ISDN Number (MSISDN).
It shall be possible to retrieve or store subscriber data concerning a specific MS from the WAG by use of the following reference:
- Mobile Subscriber ISDN Number (MSISDN).
It shall be possible to retrieve or store subscriber data concerning a specific MS from the PDG by use of each of the following references:
- International Mobile Subscriber Identity (IMSI);
- Mobile Subscriber ISDN Number (MSISDN).
- International Mobile Equipment Identity (IMEI) for emergency attached UEs without IMSI (e.g; UICCless UE) or with an unauthenticated IMSI.
NOTE: See clause 4 for explanation of M, C, T and P in table 5.1, table 5.2, table 5.2A-1, table 5.2A-2, table 5.2A-3, table 5.2B-1 and table 5.3.
|
539f847bb6cd6c0ba766caacc29710d4
|
23.008
|
5.1 CS Network Access Mode Data Storage
|
Table 5.1: Overview of data stored for CS Network Access Mode
PARAMETER
CLAUSE
HLR
VLR
TYPE
IMSI
2.1.1.1
M
M
P
Network Access Mode
2.1.1.2
M
-
P
International MS ISDN number
2.1.2
C
C
P
multinumbering MSISDNs
2.1.3
C
-
P
Basic MSISDN indicator
2.1.3.1
C
-
P
MSISDN-Alert indicator
2.1.3.2
C
-
P
TMSI
2.1.4
-
C
T
LMSI
2.1.8
C
C
T
Mobile Station Category
2.2.1
M
M
P
LMU Identifier
2.2.2
C
C
P
IMEISV
2.2.3
C
C
T
RAND, SRES and Kc
RAND, XRES, CK, IK and AUTN
2.3.1
2.3.2
M
C
C
T
T
Ciphering Key Sequence Number
2.3.3
-
M
T
Key Set Identifier (KSI)
2.3.4
-
M
T
Key Status
2.3.9
-
C
T
MSRN
2.4.1
-
C
T
Location Area Identity
2.4.2
-
M
T
VLR number
2.4.5
M
-
T
MSC number
2.4.6
M
C
T
HLR number
2.4.7
-
C
T
Subscription restriction
2.4.10
C
-
P
RSZI lists
2.4.11.1
C
-
P
Zone Code List
2.4.11.2
-
C
P
MSC area restricted flag
2.4.12
M
-
T
LA not allowed flag
2.4.13
-
M
T
ODB-induced barring data
2.4.15.1
C
-
T
Roaming restriction due to unsupported feature
2.4.15.2
M
M
T
Cell Global ID or Service Area ID
2.4.16
-
C
T
LSA Identity
2.4.17.1
C
C
P
LSA Priority
2.4.17.2
C
C
P
LSA Preferential Access Indicator
2.4.17.2A
C
C
P
LSA Active Mode Support Indicator
2.4.17.2B
C
C
P
LSA Only Access Indicator
2.4.17.3
C
C
P
LSA Active Mode Indicator
2.4.17.4
C
C
P
VPLMN Identifier
2.4.17.5
C
-
P
Access Restriction Data
2.4.18
C
C
P
Selected CN operator ID
2.4.19
-
C
T
IP-SM-GW number
2.4.20
C
-
T
IP-SM-GW Diameter Identity
2.4.20A
C
-
T
Paging area
2.4.21
C
C
T
Closed Subscriber Group Information
2.4.22
C
C
P
Service Centre Address
2.4.23
C
-
P
Subscribed Periodic LAU Timer
2.4.24
C
C
P
Provision of bearer service
2.5.1
M
M
P
Provision of teleservice
2.5.2
M
M
P
BC allocation
2.5.3
C
C
P
IMSI detached flag
2.7.1
-
C
T
Confirmed by Radio Contact indicator
2.7.4.1
-
M
T
Subscriber Data Confirmed by HLR indicator
2.7.4.2
-
M
T
Location Information Confirmed in HLR indicator
2.7.4.3
-
M
T
Check SS indicator
2.7.4.4
M
-
T
MS purged for non-GPRS flag
2.7.5
M
-
T
MNRR-MSC
2.7.7
C
-
T
Subscriber data dormant
2.7.8
-
C
T
Cancel Location received
2.7.8A
-
C
T
Subscriber status
2.8.1
C
C
P
Barring of outgoing calls
2.8.2.1
C
C
P
Barring of incoming calls
2.8.2.2
C
-
P
Barring of roaming
2.8.2.3
C
-
P
Barring of premium rate calls
2.8.2.4
C
C
P
Barring of supplementary service management
2.8.2.5
C
C
P
Barring of registration of call forwarding
2.8.2.6
C
-
P
Barring of invocation of call transfer
2.8.2.7
C
C
P
Operator determined barring PLMN-specific data
2.8.3
C
C
P
Notification to CSE flag for ODB
2.8.4
C
-
T
gsmSCF address list for ODB
2.8.5
C
-
P
Handover Number
2.9.1
-
C
T
Messages Waiting Data
2.10.1
C
-
T
Mobile Station Not Reachable Flag
2.10.2
C
M
T
Memory Capacity Exceeded Flag
2.10.3
C
-
T
Trace Reference
2.11.1
C
C
P
Trace Type
2.11.2
C
C
P
Operations Systems Identity
2.11.3
C
C
P
HLR Trace Type
2.11.4
C
-
P
MAP Error On Trace
2.11.5
C
-
T
Trace Activated in VLR
2.11.6
C
C
T
Foreign Subscriber Registered in VLR
2.11.7
-
C
P
Trace Reference 2
2.11.9
C
C
P
Trace depth
2.11.10
C
C
P
List of NE types to trace
2.11.11
C
C
P
Triggering events
2.11.12
C
C
P
List of interfaces to trace
2.11.13
C
C
P
IP address of Trace Collection Entity
2.11.14
C
C
P
MDT-Configuration
2.11.15
C
C
P
MDT User Consent
2.11.16
C
C
P
VGCS Group Membership List
2.12.1
C
C
P
VBS Group Membership List
2.12.2
C
C
P
Broadcast Call Initiation Allowed List
2.12.2.1
C
C
P
Originating CAMEL Subscription Information (O-CSI)
2.14.1.1/3.1
C
C
P
Terminating CAMEL Subscription Information (T-CSI)
2.14.1.2
C
-
P
VMSC Terminating CAMEL Subscription Information (VT-CSI)
2.14.1.2/3.2
C
C
P
Location Information/Subscriber state Information
2.14.1.3
C
-
P
USSD CAMEL subscription information(U-CSI)
2.14.1.4
C
-
P
SS invocation notification (SS-CSI)
2.14.1.5/3.2
C
C
P
Translation information flag(TIF-CSI)
2.14.1.6/3.6
C
C
P
Dialled service CAMEL Subscription Information (D-CSI)
2.14.1.11/3.7
C
C
P
USSD General CAMEL service information (UG-CSI)
2.14.2.4
C
-
P
O-CSI Negotiated CAMEL Capability Handling
2.14.2.1
C
-
T
SS-CSI Negotiated CAMEL Capability Handling
2.14.2.1
C
-
T
VT-CSI Negotiated CAMEL Capability Handling
2.14.2.1
C
-
T
Short Message Service CAMEL Subscription Information(MO‑SMS-CSI)
2.14.1.8/2.14.3.5
C
C
P
Short Message Service CAMEL Subscription Information(MT‑SMS-CSI)
2.14.1.9/2.14.3.6
C
C
P
MO-SMS-CSI VLR Negotiated CAMEL Capability Handling
2.14.2.1
C
-
T
MT-SMS-CSI VLR Negotiated CAMEL Capability Handling
2.14.2.1
C
-
P
M-CSI Negotiated CAMEL Capability Handling
2.14.2.1
C
-
T
VLR Supported CAMEL Phases
2.14.2.3
C
-
T
GsmSCF address for CSI
2.14.2.4
C
-
P
VLR Offered CAMEL4 CSIs
2.14.2.2A
C
-
T
IST Alert Timer
2.15.1
C
C
P
Privacy Exception List
2.16.1.1
C
C
P
GMLC Numbers
2.16.1.2
C
C
P
MO-LR List
2.16.1.3
C
C
P
Service Types
2.16.1.4
C
C
P
Age Indicator
2.17.1
C
C
T
CS Allocation/Retention priority
2.18.1
C
C
P
ICS Indicator
2.20.1
C
C
P
CS to PS SRVCC Allowed
2.21.4
C
C
P
|
539f847bb6cd6c0ba766caacc29710d4
|
23.008
|
5.2 PS Network Access Mode Storage (GPRS)
|
Table 5.2: Overview of data used for PS Network Access Mode (GPRS)
PARAMETER
Clause
HLR
VLR
Gn/Gp-SGSN
GGSN
TYPE
IMSI
2.1.1.1
M
M
C
C
P
Network Access Mode
2.1.1.2
M
-
C note1
-
P
IMSI Unauthenticated indicator
2.1.1.3
-
-
C
C
T
International MS ISDN number
2.1.2
C
C
C
C
P
multinumbering MSISDNs
2.1.3
C
-
-
-
P
Basic MSISDN indicator
2.1.3.1
C
-
-
-
P
MSISDN-Alert indicator
2.1.3.2
C
-
-
-
P
P-TMSI
2.1.5
-
-
C
-
T
TLLI
2.1.6
-
-
C
-
T
Random TLLI
2.1.7
-
-
C
-
T
IMEI
2.1.9
-
-
C
C
T
External Identifier Set
2.1.10
C
-
-
-
P
IMEISV
2.2.3
C
-
C
C
T
RAND/SRES and Kc
2.3.1
-
-
C
-
T
RAND, XRES, CK, IK, AUTN
2.3.2
M
-
C
-
T
Ciphering Key Sequence Number
2.3.3
-
-
M
-
T
Key Set Identifier (KSI)
2.3.4
-
-
M
-
T
Selected Ciphering Algorithm
2.3.5
-
-
M
-
T
Current Kc
2.3.6
-
-
M
-
T
P-TMSI Signature
2.3.7
-
-
C
-
T
Key Status
2.3.9
-
-
C
-
T
Routing Area Identity
2.4.3
-
-
M
-
T
VLR Number
2.4.5
M
-
C note2
-
T
SGSN Number
2.4.8.1
M
C note2
-
-
T
GGSN Number
2.4.8.2
M
-
-
-
P
RSZI Lists
2.4.11.1
C
-
-
-
P
Zone Code List
2.4.11.2
-
-
C
-
P
RA not allowed flag
2.4.14a
-
-
M
-
T
SGSN area restricted flag
2.4.14
M
-
-
-
T
Roaming Restricted in the SGSN due to unsupported feature
2.4.15.3
M
-
M
-
T
Cell Global ID or Service Area ID
2.4.16
-
-
C
C
T
LSA Identity
2.4.17.1
C
C
C
-
P
LSA Priority
2.4.17.2
C
C
C
-
P
LSA Preferential Access Indicator
2.4.17.2A
C
C
C
-
P
LSA Active Mode Support Indicator
2.4.17.2B
C
C
C
-
P
LSA Only Access Indicator
2.4.17.3
C
C
C
-
P
LSA Active Mode Indicator
2.4.17.4
C
C
C
-
P
VPLMN Identifier
2.4.17.5
C
-
-
-
P
Access Restriction Data
2.4.18
C
-
C
-
P
IP-SM-GW number
2.4.20
C
-
-
-
T
IP-SM-GW Diameter Identity
2.4.20A
C
-
-
-
T
Closed Subscriber Group Information
2.4.22
C
C
C
-
P
Service Centre Address
2.4.23
C
-
-
-
P
Provision of teleservice
2.5.2
C
-
C
-
P
Transfer of SM option
2.5.4
M
-
-
-
P
MNRG
2.7.2
M
-
M
M
T
MM State
2.7.3
-
-
M
-
T
Subscriber Data Confirmed by HLR Indicator
2.7.4.2
-
-
M
-
T
Location Info Confirmed by HLR Indicator
2.7.4.3
-
-
M
-
T
VLR-Reliable Indicator
2.7.4.5
-
-
C note1
-
T
MS purged for GPRS flag
2.7.6
M
-
-
-
T
MNRR-SGSN
2.7.7A
C
-
-
-
T
Subscriber Status
2.8.1
C
-
C
-
P
Barring of outgoing calls
2.8.2.1
C
-
-
-
P
Barring of roaming
2.8.2.3
C
-
-
-
P
Barring of Packet Oriented Services
2.8.2.8
C
-
C
-
P
ODB PLMN-specific data
2.8.3
C
-
C
-
P
Notification to CSE flag for ODB
2.8.4
C
-
-
-
T
gsmSCF address list for ODB
2.8.5
C
-
-
-
P
Trace Activated in SGSN
2.11.7
C
-
C
-
P
Trace Reference 2
2.11.9
C
-
C
C
P
Trace depth
2.11.10
C
-
C
C
P
List of NE types to trace
2.11.11
C
-
C
C
P
Triggering events
2.11.12
C
-
C
C
P
List of interfaces to trace
2.11.13
C
-
C
C
P
MDT-Configuration
2.11.15
C
C
C
-
P
PDP Type
2.13.1
C
-
C
M
P
PDP Address
2.13.2
C
-
C
M
P
NSAPI
2.13.3
-
-
C
C
T
PDP State
2.13.4
-
-
C
-
T
New SGSN Address
2.13.5
-
-
C
-
T
Access Point Name
2.13.6
C
-
C
C
P/T
GGSN Address in Use
2.13.7
-
-
C
-
T
VPLMN Address Allowed
2.13.8
C
-
C
-
P
Dynamic Address
2.13.9
-
-
-
C
T
SGSN Address
2.13.10
-
-
-
M
T
GGSN-list
2.13.11
M
-
-
-
T
Quality of Service Subscribed
2.13.12
C
-
C
-
P
Quality of Service Requested
2.13.13
-
-
C
-
T
Quality of Service Negotiated
2.13.14
-
-
C
M
T
SND
2.13.15
-
-
C
C
T
SNU
2.13.16
-
-
C
C
T
DRX Parameters
2.13.17
-
-
M
-
T
Compression
2.13.18
-
-
C
-
T
NGAF
2.13.19
-
-
C note2
-
T
Classmark
2.13.20
-
-
M
-
T
TEID
2.13.21
-
-
C
C
T
Radio Priority
2.13.22
-
-
C
-
T
Radio Priority SMS
2.13.23
-
-
C
-
T
PDP Context Identifier
2.13.24
C
-
C
-
T
PDP Context Charging Characteristics
2.13.25
C
-
C
C
P
UE level APN-OI-Replacement
2.13.29
C
-
C
-
P
Subscribed UE-AMBR
2.13.30
C
-
C
-
P
Used UE-AMBR
2.13.30A
-
-
C
-
T
Subscribed APN-AMBR
2.13.32
C
-
C
C
P
Used APN-AMBR
2.13.32A
-
-
C
C
T
Subscribed-RFSP-ID
2.13.33
C
-
C
-
P
APN Restriction
2.13.43
-
-
C
C
P
RFSP-ID in Use
2.13.108
-
-
C
-
T
APN level APN-OI-Replacement
2.13.109
C
-
C
-
P
SIPTO Permission
2.13.114
C
-
C
-
P
SIPTO Local Network Permission
2.13.114A
C
-
C
-
P
Subscribed Periodic RAU/TAU Timer
2.13.115
C
-
C
-
P
LIPA Permission
2.13.122
C
-
C
-
P
LIPA Allowed VPLMN List
2.13.123
C
-
-
-
P
VPLMN LIPA Allowed
2.13.124
-
-
C
-
P
Higher bitrates than 16Mbps flag
2.13.127
-
-
C
-
T
Co-located GGSN-PGW FQDN
2.13.136
-
-
C
-
T
GERAN Cell Identity Age
2.13.137
-
-
C
-
T
UTRAN Service Area Identity Age
2.13.138
-
-
C
-
T
Homogeneous Support of IMS Voice over PS Sessions
2.13.141
C
-
C
-
T
Signalling Priority Indication
2.13.142
-
-
C
C
T
Active Time Value for PSM
2.13.148
-
-
C
-
T
DL Data Buffer Expiration Time
2.13.150
-
-
C
-
T
DL Buffering Suggested Packet Count
2.13.151
C
-
C
-
P
IMSI-Group Identifier List
2.13.153
C
-
C
-
P
UE Usage Type
2.13.154
C
-
C
-
P
Extended idle mode DRX parameters
2.13.157
-
-
C
-
T
Delay Tolerant Connection Indication
2.13.158
-
-
C
C
P
Pending Network Initiated PDN Connection Signalling Indication
2.13.159
-
-
C
-
T
User Plane Integrity Protection Indicator
2.13.163
C
-
C
-
P
IOV_updates counter
2.13.170
-
-
C
-
T
Dedicated Core Network Identifier
2.13.172
-
-
C
-
T
GPRS CAMEL Subscription Information (GPRS-CSI)
2.14.1.10/2.14.4.4
C
-
C
-
C
MO Short Message Service CAMEL Subscription Information(MO-SMS-CSI)
2.14.1.8/2.14.4.1
C
-
C
-
C
MT Short Message Service CAMEL Subscription Information(MT-SMS-CSI)
2.14.1.9/2.14.4.2.
C
-
C
-
C
MO-SMS-CSI SGSN Negotiated CAMEL Capability Handling
2.14.2.1
C
-
-
-
P
MT-SMS-CSI SGSN Negotiated CAMEL Capability Handling
2.14.2.1
C
-
-
-
P
Mobility Management for GPRS event notification (MG-CSI)
2.14.1.12/2.14.4.4
C
-
C
-
C
MG-CSI Negotiated CAMEL Capability Handling
2.14.2.1
C
-
-
-
P
GPRS-CSI Negotiated CAMEL Capability Handling
2.14.2.1
C
-
-
-
T
SGSN Supported CAMEL Phases
2.14.2.3
C
-
-
-
T
SGSN Offered CAMEL4 CSIs
2.14.2.2A
C
-
-
-
T
GsmSCF address for CSI
2.14.2.4
C
-
-
-
P
Age Indicator
2.16.1
C
-
C
-
T
Privacy Exception List
2.16.1.1
C
-
C
-
P
GMLC Numbers
2.16.1.2
C
-
C
-
P
MO-LR List
2.16.1.3
C
-
C
-
P
Service Types
2.16.1.4
C
-
C
-
P
Subscribed Charging Characteristics
2.19.1
C
-
C
C
P
ICS Indicator
2.20.1
C
C
C
-
P
STN-SR
2.21.1
C
-
C
-
T
Additional MSISDN
3.1.16
C
-
C
-
P
The HLR column indicates only GPRS related use, i.e. if the HLR uses a parameter in non-GPRS Network Access Mode but not in GPRS Network Access Mode, it is not mentioned in this table 5.2.
NOTE 1: This parameter is relevant in the SGSN only when the Gs interface is installed.
NOTE 2: The VLR column is applicable if Gs interface is installed. It only indicates GPRS related data to be stored and is only relevant to GPRS subscribers registered in VLR.
For special condition of storage see in clause 2. See clause 4 for explanation of M, C, T and P in table 5.2.
5.2A PS Network Access Mode Storage (EPS)
Table 5.2A-1: Overview of data used for PS Network Access Mode (EPS 3GPP access)
PARAMETER
Clause
HSS
VLR
(see note3)
S4-SGSN
MME
S-GW
PDN-GW
TYPE
IMSI
2.1.1.1
M
C
C
C
C
C
P
Network Access Mode
2.1.1.2
M
-
-
C (see note 1)
-
-
P
IMSI Unauthenticated indicator
2.1.1.3
-
-
C
C
C
C
T
International MS ISDN number
2.1.2
C
-
C
C
C
C
P
P-TMSI
2.1.5
-
-
C
-
-
-
T
TLLI
2.1.6
-
-
C
-
-
-
T
Random TLLI
2.1.7
-
-
C
-
-
-
T
IMEI
2.1.9
C
-
C
C
C
C
T
External Identifier Set
2.1.10
C
-
-
-
-
-
P
UE radio capability ID
2.1.11
-
-
-
C
-
-
T
IMEISV
2.2.3
C
-
C
C
C
C
T
RAND/SRES and Kc
2.3.1
-
-
C
-
-
-
T
RAND, XRES, CK, IK, AUTN
2.3.2
M
-
C
C
-
-
T
RAND, XRES, KASME, AUTN
2.3.2
M
-
-
C
-
-
T
Ciphering Key Sequence Number
2.3.3
C
-
M
-
-
-
T
Key Set Identifier (KSI)
2.3.4
-
-
M
-
-
-
T
KSIASME
2.3.4
-
-
M
-
-
T
Selected Ciphering Algorithm
2.3.5
-
-
M
-
-
-
T
Current Kc
2.3.6
-
-
M
-
-
-
T
P-TMSI Signature
2.3.7
-
-
C
-
-
-
T
Key Status
2.3.9
-
-
C
-
-
-
T
Routing Area Identity
2.4.3
-
-
M
-
-
-
T
IWF number
2.4.8.3
C
-
-
-
-
-
T
RSZI Lists
2.4.11.1
C
-
-
-
-
P
Zone Code List
2.4.11.2
-
-
C
C
-
-
P
SGSN area restricted Flag
2.4.14
M
-
-
-
-
T
RA not allowed flag
2.4.14a
-
-
M
-
-
-
T
TA not allowed flag
2.4.14b
-
-
M
-
-
T
Roaming Restricted in the SGSN due to unsupported feature
2.4.15.3
M
-
M
-
-
-
T
Roaming Restricted in the MME due to unsupported feature
2.4.15.3a
M
-
-
M
-
-
T
Cell Global Identity or Service Area ID
2.4.16
-
-
C
C
-
C
T
E-UTRAN Cell Global ID
2.4.16A
-
C (see note 2)
-
C
-
C
T
Access Restriction Data
2.4.18
C
-
C
C
-
-
P
Closed Subscriber Group Information
2.4.22
C
C
C
C
-
-
P
IAB-Operation Allowed
2.4.27
C
-
-
C
-
-
P
Confirmed by Radio Contact indicator
2.7.4.1
-
C
-
-
-
-
T
Subscriber Data Confirmed by HLR/HSS Indicator
2.7.4.2
-
-
M
M
-
-
T
Location Info Confirmed by HLR/HSS Indicator
2.7.4.3
-
-
M
M
-
-
T
VLR-Reliable Indicator
2.7.4.5
-
-
C(see note 5)
C (see note 2)
-
-
T
UE purged in SGSN flag
2.7.6
M
-
-
-
-
-
T
UE purged in MME flag
2.7.6A
M
-
-
-
-
-
T
URRP-MME
2.7.9.1
C
-
-
C
-
-
T
URRP-SGSN
2.7.9.2
C
-
C
-
-
-
T
Subscriber Status
2.8.1
C
-
C
C
-
-
P
Barring of outgoing calls
2.8.2.1
C
-
C
-
-
-
P
Barring of roaming
2.8.2.3
C
-
-
-
-
-
P
Barring of Packet Oriented Services
2.8.2.8
C
-
C
C
-
-
P
ODB PLMN-specific data
2.8.3
C
-
C
-
-
-
P
PS and SMS Only
2.10.7
C
-
C
-
-
-
P
SMS in SGSN Allowed
2.10.8
C
-
C
-
-
-
P
Trace Activated in SGSN
2.11.7
C
-
C
-
-
-
P
Trace Reference 2
2.11.9
C
C
C
C
C
C
P
Trace depth
2.11.10
C
C
C
C
C
C
P
List of NE types to trace
2.11.11
C
C
C
C
-
-
P
Triggering events
2.11.12
C
C
C
C
C
C
P
List of interfaces to trace
2.11.13
C
C
C
C
C
C
P
IP address of trace collection entity
2.11.14
C
C
C
C
C
C
P
MDT-Configuration
2.11.15
C
C
C
C
-
-
P
MDT User Consent
2.11.16
C
C
C
C
-
-
P
Access Point Name (APN).
2.13.6
M
-
M
M
M
M
P
MME name
2.13.26
M
C
-
-
-
-
T
VLR name
2.13.27
-
-
-
C (see note 2)
-
-
T
NEAF
2.13.28
-
-
-
C (see note 2)
-
-
T
UE level APN-OI-Replacement
2.13.29
C
-
C
-
-
P
Subscribed UE-AMBR
2.13.30
M
-
M
M
-
-
P
Used UE-AMBR
2.13.30A
-
-
C
C
-
-
T
APN-Configuration-Profile
2.13.31
M
-
M
M
-
-
P
Subscribed APN-AMBR
2.13.32
M
-
M
M
M
-
P
Used APN-AMBR
2.13.32A
-
-
C
C
-
C
T
Subscribed-RFSP-ID
2.13.33
C
-
-
C
-
-
P
GUTI
2.13.34
-
-
-
C
-
-
T
ME identity (IMEISV)
2.13.35
C
-
C
C
C
C
T
Selected NAS Algorithm
2.13.36
-
-
-
M
-
-
T
Selected AS Algorithm
2.13.37
-
-
-
M
-
-
T
Context Identifier
2.13.38
M
-
M
M
M
M
P
PDN Address
2.13.39
C
-
C
C
C
C
P/T (see note4)
VPLMN Address Allowed
2.13.40
M
-
M
M
-
-
P
PDN GW identity
2.13.41
C
-
C
(see note 6)
C
(see note 6)
-
-
P/T
(see note4)
Tracking Area List
2.13.42
-
-
-
M
-
-
T
APN Restriction
2.13.43
-
C
C
C
C
P
APN in use
2.13.44
-
-
M
M
M
M
T
TAI
2.13.45
-
C (see note 2)
-
M
-
-
T
E-UTRAN Cell Identity Age
2.13.46
-
C (see note 2)
-
C
-
-
T
MME F-TEID for S11 (control plane)
2.13.47
-
-
-
C
C
-
T
MME UE S1AP ID
2.13.48
-
-
-
C
-
-
T
S-GW F-TEID for S11 (control plane)
2.13.49
-
-
-
C
C
-
T
S4-SGSN F-TEID for S4 (control plane)
2.13.50
-
-
C
-
-
-
T
S4-SGSN F-TEID for S4 (User plane)
2.13.51
-
-
C
-
-
-
T
S-GW F-TEID for S5/S8
(control plane)
2.13.52
-
-
-
C
C
C
T
S-GW F-TEID for S1-U
2.13.53
-
-
-
C
C
-
T
S-GW F-TEID for S5/S8
(user plane)
2.13.54
-
-
-
-
C
C
T
eNodeB Address
2.13.55
-
-
-
C
-
-
T
eNodeB UE S1AP ID
2.13.56
-
-
-
C
-
-
T
eNodeB F-TEID for S1-U
2.13.57
-
-
-
C
C
-
T
E-UTRAN/UTRAN Key Set flag
2.13.58
-
-
-
C
-
-
T
Selected CN operator id
2.13.59
-
-
-
C
-
-
T
UE Radio Access Capability
2.13.60
-
-
-
C
-
-
T
Location Change Report Required
2.13.62
-
-
C
C
-
-
T
UE specific DRX parameters
2.13.63
-
-
-
C
-
-
T
PDN GW F-TEID for S5/S8
(user plane)
2.13.64
-
-
C
C
C
C
T
PDN GW F-TEID for S5/S8 (control plane)
2.13.65
-
-
C
C
C
C
T
EPS Bearer ID
2.13.66
-
-
C
C
C
C
T
EPS Bearer QoS
2.13.67
-
-
C
C
C
C
T
EPS Subscribed QoS Profile
2.13.67A
M
-
M
M
-
-
P
UL TFT
2.13.68
-
-
-
C
C
C
T
DL TFT
2.13.69
-
-
-
C
C
C
T
Charging Id
2.13.70
-
-
C
-
C
C
T
EPS PDN Connection Charging Characteristics
2.13.71
C
-
C
C
C
C
P
Default bearer
2.13.72
-
-
-
C
C
C
T
URRP-MME
2.13.73
C
-
-
C
T
RAT Type (Access Type)
2.13.75
C
-
C
C
C
C
T
Diameter Server Identity of the HSS
2.13.99
-
-
C
C
-
-
T
SGSN name
2.13.100
M
-
-
-
-
-
T
S-GW F-TEID for S12
2.13.101
-
-
-
-
C
-
T
RNC F-TEID for S12
2.13.102
-
-
C
-
C
-
T
MME F-TEID for S3
2.13.103
-
-
C
C
-
-
T
S4-SGSN F-TEID for S3
2.13.104
-
-
C
C
-
-
T
PDN GW Allocation Type
2.13.105
M
-
-
M
-
-
P
S-GW F-TEID for S4 (control plane)
2.13.106
-
-
C
-
C
-
T
S-GW F-TEID for S4 (user plane)
2.13.107
-
-
C
-
C
-
T
RFSP-ID in Use
2.13.108
-
-
C
C
-
-
T
APN level APN-OI-Replacement
2.13.109
C
-
C
C
-
-
P
PDN Connection ID
2.13.111
-
-
-
-
C
C
T
MS Network Capability
2.13.112
-
-
C
C
-
-
T
Voice Domain Preference and UE's Usage Setting
2.13.113
-
-
C
C
-
-
T
SIPTO Permission
2.13.114
C
-
C
C
-
-
P
SIPTO Local Network Permission
2.13.114A
C
-
C
C
-
-
P
Subscribed Periodic RAU/TAU Timer
2.13.115
C
-
C
C
-
-
P
MPS CS Priority
2.13.120
-
-
-
C
-
-
P
MPS EPS Priority
2.13.121
C
-
-
C
-
-
P
LIPA Permission
2.13.122
C
-
C
C
-
-
P
LIPA Allowed VPLMN List
2.13.123
C
-
-
-
-
-
P
VPLMN LIPA Allowed
2.13.124
-
-
C
C
-
-
P
Relay Node Indicator
2.13.125
C
-
-
C
-
-
P
Higher bitrates than 16Mbps flag
2.13.127
-
-
C
-
-
-
T
H(e)NB Local IP Address
2.13.131
-
-
C
C
-
C
T
H(e)NB UDP Port Number
2.13.132
-
-
C
C
-
C
T
MME/S4 SGSN Identifier
2.13.134
-
-
-
-
C
C
T
SGW node name
2.13.135
-
-
C
C
-
-
T
Co-located GGSN-PGW FQDN
2.13.136
-
-
C
(see note 6)
C
(see note 6)
-
-
T
GERAN Cell Identity Age
2.13.137
-
-
C
-
-
-
T
UTRAN Service Area Identity Age
2.13.138
-
-
C
-
-
-
T
Homogeneous Support of IMS Voice over PS Sessions
2.13.141
C
-
C
C
-
-
T
Signalling Priority Indication
2.13.142
-
-
C
C
C
C
T
Restoration Priority
2.13.143
C
-
C
C
-
-
P
Presence Reporting Area Action
2.13.145
-
-
C
C
-
C
T
WLAN offloadability
2.13.146
C
-
C
C
-
-
P
Expected UE Activity Behaviour
2.13.147.2
-
-
-
C
-
-
T
Expected HO Interval
2.13.147.3
-
-
-
C
-
-
T
Active Time Value for PSM
2.13.148
-
-
C
C
-
-
T
Origination Time Stamp
2.13.149
-
-
-
-
-
C
T
DL Data Buffer Expiration Time
2.13.150
-
-
C
C
C
-
T
DL Buffering Suggested Packet Count
2.13.151
C
-
C
C
-
-
P
Notify-on-available-after-DDN-failure flag
2.13.152
-
-
C
C
-
-
T
IMSI-Group Identifier List
2.13.153
C
-
C
C
-
-
P
UE Usage Type
2.13.154
C
-
C
C
-
-
P
Remote UE Contexts
2.13.156
-
-
-
C
C
C
T
Extended idle mode DRX parameters
2.13.157
C
-
C
C
-
-
P/T (see note 7)
Delay Tolerant Connection Indication
2.13.158
-
-
C
C
-
C
P
Pending Network Initiated PDN Connection Signalling Indication
2.13.159
-
-
C
C
.
-
T
UE Radio Capability for Paging information
2.13.160
-
-
-
C
-
-
T
Information on Recommended Cells and ENBs for Paging
2.13.161
-
-
-
C
-
-
T
Paging Attempt Count
2.13.162
-
-
-
C
-
-
T
User Plane Integrity Protection Indicator
2.13.163
C
-
C
-
-
-
P
Non-IP-PDN-Type-Indicator
2.13.164
C
-
-
C
-
-
P
Non-IP-Data-Delivery-Mechanism
2.13.165
C
-
-
C
-
-
P
SCEF-ID
2.13.166
C
-
-
C
-
-
P
PDN Type
2.13.167
C
-
C
C
C
C
P
PDN-Connection-Restricted flag
2.13.168
C
-
-
C
-
-
P
Preferred-Data-Mode
2.13.169
C
-
-
C
-
-
P
IOV_updates counter
2.13.170
-
-
C
-
-
-
T
Dedicated Core Network Identifier
2.13.172
-
-
C
C
-
-
T
Service Gap Time
2.13.174
C
-
-
C
-
-
P
Subscribed Additional RRM Policy Index
2.13.175
C
-
-
C
-
-
P
Additional RRM Policy Index in use
2.13.176
-
-
-
C
-
-
T
Ethernet-PDN-Type-Indicator
2.13.177
C
-
-
C
-
-
P
Time-Reference-Information-Distribution-Indication
2.13.178
C
-
-
C
-
-
P
Privacy Exception List
2.16.1.1
C
-
C
-
-
-
P
GMLC Numbers
2.16.1.2
C
-
C
-
-
-
P
MO-LR List
2.16.1.3
C
-
C
-
-
-
P
Service Types
2.16.1.4
C
-
C
-
-
-
P
Broadcast Location Assistance Data Types
2.16.7.1
C
-
-
C
-
-
P
Subscribed Charging Characteristics
2.19.1
C
-
C
C
-
-
P
ICS Indicator
2.20.1
C
C
C
C
-
-
P
STN-SR
2.21.1
C
-
C
C
-
-
T
UE SRVCC Capability
2.21.2
C
-
C
C
-
-
T
Subscribed vSRVCC
2.21.3
C
-
-
C
-
-
P
Additional MSISDN
3.1.16
C
-
C
C
-
-
P
NOTE 1: This parameter is relevant in the MME only when the SGs interface is installed.
NOTE 2: Only is applicable if SGs interface is installed. It only indicates EPS related data to be stored and is only relevant to EPS subscribers registered in VLR.
NOTE 3: The VLR column is applicable if SGs/Sv interface is installed. It only indicates EPS related data to be stored and is only relevant to EPS subscribers registered in VLR.
NOTE 4: If Static IP address allocation provisioned in the subscriber profile in the HSS is chosen, PDN address is permanent data.
NOTE 5: Only is applicable if Gs interface is installed. It only indicates EPS related data to be stored and is only relevant to EPS subscribers registered in VLR.
NOTE 6: The MME/S4 SGSN stores either the PDN GW identity or the Co-located GGSN-PGW FQDN since they are identical information.
NOTE 7: The eDRX cycle length may be stored in HSS as a subscribed parameter, and in that case, it is permanent data.
For special condition of storage see in clause 2. See clause 4 for explanation of M, C, T and P in table 5.2A-1.
Table 5.2A-2: Overview of data used for PS Network Access Mode (EPS non 3GPP access)
PARAMETER
Clause
HSS
MME
S-GW
PDN-GW
ePDG
3GPP AAA server
3GPP AAA server
Proxy
TYPE
IMSI
2.1.1.1
M
C
C
C
C
-
-
P
IMSI Unauthenticated indicator
2.1.1.3
-
C
C
C
C
-
-
T
International MS ISDN number
2.1.2
C
C
C
C
C
C
-
P
IMEI
2.1.9
C
-
-
C
C
C
-
T
RAND, XRES, CK, IK, AUTN
2.3.2
M
-
-
-
-
M
-
T
RAND, XRES, KASME, AUTN
2.3.2
M
-
-
-
-
M
-
T
Access Network Identity
2.3.8
C
-
-
-
-
C
-
T
Trace Reference 2
2.11.9
C
-
-
C
-
C
-
P
Trace depth
2.11.10
C
-
-
C
-
C
-
P
List of NE types to trace
2.11.11
C
-
-
-
-
C
-
P
Triggering events
2.11.12
C
-
-
C
-
C
-
P
List of interfaces to trace
2.11.13
C
-
-
C
-
C
-
P
IP address of Trace Collection Entity
2.11.14
C
-
-
C
-
C
-
P
APN-Configuration-Profile
2.13.31
M
-
-
C
C
C
-
T
Subscribed APN-AMBR
2.13.32
M
-
-
C
C
C
-
P
Used APN-AMBR
2.13.32A
-
-
-
C
-
-
-
T
ME Identity (IMEISV)
2.13.35
C
-
-
C
C
C
-
T
PDN Address
2.13.39
C
-
C
C
C
C
-
T/P (see Note)
VPLMN Address Allowed
2.13.40
M
C
-
-
C
C
-
P
PDN GW identity
2.13.41
M
C
-
-
C
C
-
P
APN in use
2.13.44
-
-
-
C
C
-
-
T
EPS Bearer ID
2.13.66
-
-
-
C
C
-
-
T
EPS Bearer QoS
2.13.67
-
-
-
C
C
-
-
T
EPS PDN Connection Charging Characteristics
2.13.71
C
-
-
C
C
C
-
P
RAT Type (Access Type)
2.13.75
C
-
C
C
C
C
-
T
Permanent User Identity
2.13.79
M
-
M
M
M
M
-
P
Mobility Capabilities
2.13.80
-
-
-
M
C
C
-
T
MAG IP address
2.13.81
-
-
-
-
-
C
-
T
Visited Network Identifier
2.13.82
C
-
-
C
C
C
-
T
EAP payload
2.13.83
-
-
-
-
-
C
-
P
MIP Subscriber profile
2.13.86
M
-
-
M
-
-
-
P
Uplink S5 GRE Key
2.13.87
-
C
C
C
-
-
-
T
Downlink S5 GRE Key
2.13.88
-
-
C
C
-
-
-
T
Uplink S8 GRE Key
2.13.89
-
C
C
C
-
-
-
T
Downlink S8 GRE Key
2.13.90
-
-
C
C
-
-
-
T
S2a GRE Keys
2.13.91
-
-
C
C
-
-
-
T
S2b GRE Keys
2.13.92
-
-
C
C
C
-
-
T
Mobile Node Identifier
2.13.93
-
-
C
C
-
-
-
T
IPv4 Default Router Address
2.13.94
-
-
C
C
-
-
-
T
Link-local address
2.13.95
-
-
C
C
-
-
-
T
Non 3GPP User Data
2.13.96
C
-
-
-
C
C
-
3GPP AAA Server Identity
2.13.97
C
-
-
C
C
-
-
T
Selected IP mobility mode
2.13.98
-
-
-
C
C
C
-
T
Diameter Server Identity of HSS
2.13.99
-
C
-
-
-
C
-
T
Unauthenticated IMSI
2.13.110
-
-
C
C
-
-
-
T
PDN Connection ID
2.13.111
-
-
C
C
C
-
-
T
SIPTO Permission
2.13.114
C
-
-
-
-
C
-
P
ePDG F-TEID for S2b (control plane)
2.13.116
-
-
-
C
C
-
-
T
ePDG F-TEID for S2b (user plane)
2.13.117
-
-
-
C
C
-
-
T
PGW F-TEID for S2b (control plane)
2.13.118
-
-
-
C
C
-
-
T
PGW F-TEID for S2b (user plane)
2.13.119
-
-
-
C
C
-
-
T
Restricted RAT Types
2.13.126
C
-
-
-
-
C
-
P
UE Local IP Address
2.13.129
-
-
-
-
C
-
-
T
UE UDP Port Number
2.13.130
-
-
-
-
C
-
-
T
Default APN for Trusted WLAN
2.13.139
C
-
-
-
-
C
-
P
Access Information for Trusted WLAN
2.13.140
C
-
-
-
-
C
-
P
Origination Time Stamp
2.13.149
-
-
-
C
-
C
-
T
Emergency Indication
2.13.155
-
-
-
-
C
C
C
T
Emergency Info
2.13.171
C
C
-
-
C
C
-
T
Subscribed Charging Characteristics
2.19.1
M
-
-
-
C
C
-
P
ERP-Authorization
2.24.2
C
-
-
-
-
C
-
P
ERP Keying Material
2.24.3
-
-
-
-
-
C
C
T
ERP-Realm
2.24.4
-
-
-
-
-
C
C
P
Master session Key
3.11.3. 5
-
-
-
C
C
C
-
T
NOTE: If Static IP address allocation provisioned in the subscriber profile in the HSS is chosen, PDN address is permanent data.
For special condition of storage see in clause 2. See clause 4 for explanation of M, C, T and P in table 5.2A-2.
Table 5.2.A-3 contains additional parameter to be hold when optimised handover to 3GPP2 is supported.
Table 5.2A-3: Overview of data used for PS Network Access Mode (optimized handover to 3GPP2)
PARAMETER
Clause
HSS
MME
S-GW
PDN-GW
ePDG
3GPP AAA server
3GPP AAA server
Proxy
TYPE
Access Restriction Data
2.4.18
C
C
-
-
-
-
-
P
Barring of Packet Oriented Services
2.8.2.8
C
C
-
-
-
-
-
P
RAT Type
2.13.75
C
-
-
-
-
-
-
T
S101 HRPD access node IP address
2.13.76
-
C
-
-
-
-
-
T
S103 Forwarding Address
2.13.77
-
C
C
-
-
-
-
T
S103 GRE key(s)
2.13.78
-
C
C
-
-
-
-
T
NOTE: A UE may be simultaneously attached to EPS and have simultaneously active PDN connections or IP flows via different access systems (3GPP access and a non 3GPP access).
5.2B PS Network Access Mode Data (5GS)
Table 5.2B-1: Overview of data used for PS Network Access Mode (5GS)
PARAMETER
Clause
UDM
AMF
SMF
SMSF
AUSF
NEF
TYPE
Subscribed UE-AMBR
2.13.30
C
C
-
-
-
-
-
P
TAI
2.13.45
-
C
C
-
-
-
-
T
Restricted RAT Types
2.13.126
C
C
-
-
-
-
-
P
IMSI Group Identifier List
2.13.153
C
C
-
-
-
-
P
UE Usage Type
2.13.154
C
C
-
-
-
-
P
STN-SR
2.21.1
C
C
-
-
-
-
-
T
UE 5G SRVCC Capability
2.21.2
C
C
-
-
-
-
-
T
SUPI
2.25.1
M
C
C
C
-
C
-
P
GPSI
2.25.2
M
C
C
-
-
C
-
P
Internal Group ID-list
2.25.3
C
C
C
-
-
-
-
P
Subscribed S-NSSAI
2.25.4
C
C
C
-
-
-
-
P
Default S-NSSAI
2.25.5
C
C
-
-
-
-
-
P
5G QOS Parameter
2.25.6
C
-
C
-
-
-
-
P
Forbidden Area
2.25.7
C
C
-
-
-
-
-
P
Service Area Restriction
2.25.8
C
C
-
-
-
-
-
P
RFSP Index
2.25.9
C
C
-
-
-
-
-
P
Priority Service
2.25.10
C
C
-
-
-
-
-
P
DNN Info
2.25.11
C
-
C
-
-
-
-
P
DNN Configuration
2.25.12
C
-
C
-
-
-
-
P
Steering of Roaming Information
2.25.13
C
C
-
C
T
SMS supported Data
2.25.14
C
C
-
C
-
-
-
T
SMSF Registrations
2.25.15
C
C
-
M
-
-
-
P
SMS subscribed
2.25.16
M
-
-
C
-
-
-
P
SMS barring
2.25.17
M
-
-
C
-
-
-
P
SMS Roaming
2.25.18
C
C
-
C
-
-
-
P
Core Network Type Restriction
2.25.19
C
C
-
-
-
-
-
P
LADN Information
2.25.20
C
C
-
-
-
-
-
P
Subscribed periodic Registration timer
2.25.21
C
C
-
-
-
-
-
P
PEI
2.25.22
C
C
C
-
-
-
-
T
5G GUTI
2.25.23
-
C
-
-
-
-
-
T
PLMN ID
2.25.24
C
C
C
C
-
-
-
P
PDU session
2.25.25
C
C
C
-
-
-
-
T
Trace Data
2.25.26
C
C
C
-
-
-
-
P
Mobile Initiated Connection Only (MICO) mode
2.25.27
C
C
-
-
-
-
-
P
UE purged in AMF flag
2.25.28
M
-
-
-
-
-
-
T
GUAMI
2.25.29
C
C
C
-
-
-
-
T
RAND, AUTN, XRES, CK', IK'
2.25.30
-
-
-
-
-
-
-
T
RAND, AUTN, XRES*
2.25.31
-
-
-
-
-
-
-
T
RAND, AUTN, HXRES*
2.25.32
-
-
-
-
-
-
-
T
Kausf
2.25.33
-
-
-
-
C
-
-
T
Kseaf
2.25.34
-
M
-
-
-
-
-
T
AuthenticationMethod
2.25.35
M
-
-
-
-
-
-
P
PermanentKey
2.25.36
C
-
-
-
-
-
-
P
SequenceNumber
2.25.37
C
-
-
-
-
-
-
T
AuthenticationManagementField
2.25.38
C
-
-
-
-
-
-
P
VectorAlgorithm
2.25.39
C
-
-
-
-
-
-
P
Milenage
2.25.40
C
-
-
-
-
-
-
P
Tuak
2.25.41
C
-
-
-
-
-
-
P
Opc
2.25.42
C
-
-
-
-
-
-
P
Topc
2.25.43
C
-
-
-
-
-
-
P
Authentication Status
2.25.44
C
-
-
-
-
-
-
T
SoR-XMAC-IUE
2.25.45
C
-
-
-
-
-
-
T
Shared Data Ids
2.25.46
C
C
C
C
-
-
-
P
Access Restriction Data
2.25.47
C
C
-
-
-
-
-
P
IAB-Operation Allowed
2.25.48
C
C
-
-
-
-
-
P
UE radio capability ID
2.25.49
-
C
-
-
-
-
-
T
RG Level Wireline Access Characteristics
2.25.50
C
C
-
-
-
-
-
P
RG-TMBR
2.25.51
C
C
-
-
-
-
-
P
List of 5GS Broadcast Location Assistance Data Types
2.25.52
C
C
-
-
-
-
-
P
NOTE: Where the node physically stores data and/or from where it retrieves data for usage (e.g. interactions with the UDR) are not reflected in this table.
|
539f847bb6cd6c0ba766caacc29710d4
|
23.008
|
5.3 IP Multimedia Service Data Storage
|
Table 5.3: Overview of IMS subscriber data used for IP Multimedia services
PARAMETER
Clause
HSS
S-CSCF
IM-SSF
AS
TYPE
Service Centre Address
2.4.23
C
-
-
C
P
Private User Identity
3.1.1
M
M
-
-
P
Public User Identity
3.1.2
M
M
-
-
P
Barring Indication
3.1.3
M
M
-
-
P
List of authorized visited network identifiers
3.1.4
M
-
-
-
P
Services related to Unregistered State
3.1.5
M
-
-
-
P
Implicitly registered Public User Identity sets
3.1.6
C
C
-
-
P
Default Public User Identity indicator
3.1.7
C
-
-
-
P
Display Name
3.1.9
C
C
-
-
P
Alias Public User Identities Set
3.1.10
C
C
-
-
P
Loose-Route Indication
3.1.11
C
C
-
-
P
Service Priority Level
3.1.12
C
C
-
-
P
Extended Priority
3.1.13
C
C
-
-
P
Reference Location Information
3.1.14
C
C
-
-
P
Priviledged-Sender Indication
3.1.15
C
C
-
-
P
Additional MSISDN
3.1.16
C
-
-
C
P
Registration Status
3.2.1
M
-
-
-
T
S-CSCF Name
3.2.2
M
-
-
-
T
Diameter Client Identity of S-CSCF
3.2.3
M
-
-
-
T
Diameter Server Identity of HSS
3.2.4
-
M
-
C
T
UNRI
3.2.5
C
-
-
C
T
UNRR
3.2.6
C
-
-
-
T
S-CSCF Restoration Information
3.2.7
C
C
-
-
T
Maximum Number Of Allowed Simultaneous Registrations
3.2.8
C
C
-
-
P
RAND, XRES, CK, IK and AUTN
3.3.1
M
C
-
-
T
Digest Nonce
3.3.2.1
-
C
-
-
T
Digest HA1
3.3.2.2
C
C
-
-
P
Digest Nextnonce
3.3.2.3
-
C
-
-
T
Authentication Pending Flag
3.3.2.5
C
-
-
-
T
Line Identifier List
3.3.3.1
C
C
-
-
P
Server Capabilities
3.4.1
C
-
-
-
P
S-CSCF Reassignment Pending Flag
3.4.2
C
-
-
-
T
Initial Filter Criteria
3.5.2
C
C
-
-
P
Application Server Information
3.5.3
C
C
-
-
P
Service Indication
3.5.4
M
-
-
M
P
Shared iFC Set Identifier
3.5.5
C
C
-
P
Transparent Data
3.5.6
C
-
-
C
T
Application Server Identity List
3.5.7
C
-
-
-
T
Subscribed Media Profile Identifier
3.6.1
C
C
-
-
P
List of Subscribed Communication Service Identifiers
3.6.2
M
C
-
C
P
Primary Event Charging Function Name
3.7.1
C Note 1
C
-
-
P
Secondary Event Charging Function Name
3.7.2
C
C
-
-
P
Primary Charging Collection Function Name
3.7.3
C Note 1
C
-
-
P
Secondary Charging Collection Function Name
3.7.4
C
C
-
-
P
O-IM-CSI
3.8.1
C
-
C
-
P
VT-IM-CSI
3.8.2
C
-
C
-
P
D-IM-CSI
3.8.3
C
-
C
-
P
GsmSCF address for IM CSI
3.8.4
C
-
-
-
P
IM-SSF address for IM CSI
3.8.5
C
-
-
-
T
IMS Service Level Trace Information
3.9.1
C
C
-
C
T
Allowed WAF and/or WWSF Identity List
3.15.1
C
C
-
-
P
Note 1: At least one of these Primary Charging Function Names shall be mandatorily provisioned in the HSS.
Table 5.3A: Overview of PSI user data used for IP Multimedia services
PARAMETER
Clause
HSS
S-CSCF
IM-SSF
AS
TYPE
Private Service Identity
3.1.2A
M
M
-
-
P
Public Service Identity
3.1.2B
M
M
-
M
P
Services related to Unregistered State
3.1.5
M
-
-
-
P
PSI Activation State
3.1.8
M
-
-
M
T
Display Name
3.1.9
C
C
-
-
P
Registration Status
3.2.1
M
-
-
-
T
S-CSCF Name
3.2.2
C
-
-
-
T
AS Name
3.2.2A
C
-
-
-
P
Diameter Client Identity of S-CSCF
3.2.3
M
-
-
-
T
Diameter Server Identity of HSS
3.2.4
-
M
-
C
T
Server Capabilities
3.4.1
C
-
-
-
P
Initial Filter Criteria
3.5.2
C
C
-
-
P
Application Server Information
3.5.3
C
C
-
-
P
Service Indication
3.5.4
M
-
-
M
P
Shared iFC Set Identifier
3.5.5
C
C
-
-
P
Transparent Data
3.5.6
C
-
C
T
Subscribed Media Profile Identifier
3.6.1
C
C
-
-
P
Primary Event Charging Function Name
3.7.1
C Note 1
C
-
-
P
Secondary Event Charging Function Name
3.7.2
C
C
-
-
P
Primary Charging Collection Function Name
3.7.3
C Note 1
C
-
-
P
Secondary Charging Collection Function Name
3.7.4
C
C
-
-
P
Note 1: At least one of these Primary Charging Function Names shall be mandatorily provisioned in the HSS.
|
539f847bb6cd6c0ba766caacc29710d4
|
23.008
|
5.4 Generic Authentication Architecture Service Data Storage
|
Table 5.4: Overview of data used for GAA services
PARAMETER
Clause
HSS
BSF
NAF
TYPE
Private User Identity
3.1.1
M
M
C
P
GAA Service Type
3.10.1
M
M
M
P
GAA Service Identifier
3.10.2
M
M
M
P
GBA User Security Settings
3.10.3
M
M
-
P
User Security Setting
3.10.4
M
M
M
P
User Public Identity
3.10.5
M
M
M
P
GAA Authorization flag
3.10.6
C
C
C
P
Bootstrapping Transaction Identifier
3.10.7
-
M
M
T
Key Lifetime
3.10.8
C
M
-
P
UICC Security Setting
3.10.9
C
C
-
P
NAF Group
3.10.10
-
M
-
P
NAF Group Identity
3.10.11
C
M
-
P
NAF Address
3.10.12
-
M
-
P
Key Expirytime
3.10.13
-
M
M
T
Boostrapping Info Creation Time
3.10.14
-
M
M
T
Diameter Server Identity of HSS
3.10.15
-
C
-
T
The possible user's GBA User Security Settings (GUSS) are stored in HSS with User Private Identifier (IMPI) as retrieval key.
The bootstrapping procedure creates a bootstrapping information entity to the BSF with B-TID as retrieval key.
|
539f847bb6cd6c0ba766caacc29710d4
|
23.008
|
5.5 I-WLAN Service Data Storage
|
NOTE: The WLAN Network Selection and WLAN/3GPP Radio Interworking features supersede the I-WLAN feature from Rel-12 onwards, therefore all I-WLAN subscriber data specified in the present Clause are no longer maintained.
Table 5.5: Overview of data used for I-WLAN services
PARAMETER
Clause
HSS
3GPP AAA Server
3GPP AAA Proxy
PDG
WAG
TYPE
IMSI
3.11.1.1
M
M
-
C
-
P
MSISDN
3.11.1.2
M
M
M
M
M
P
W-APN
3.11.1.3
C
C
C
C
-
T
List of authorized visited network identifiers
3.11.1.4
M
-
-
-
-
P
3GPP AAA Proxy Name
3.11.1.5
C
C
C
C
C
T
3GPP AAA Server Name
3.11.1.6
C
-
C
C
C
T
Serving PDG List
3.11.1.7
-
C
C
-
-
T
Serving WAG
3.11.1.8
-
C
C
T
WLAN UE Local IP address
3.11.1.9
-
-
-
C
C
T
WLAN UE Remote IP address
3.11.1.10
C
C
-
C
-
P
User Status
3.11.2.1
M
M
-
-
-
T
Emergency Access
3.11.2.2
-
M
-
-
-
T
Diameter Server Identity of HSS
3.11.2.3
-
C
-
-
-
T
RAND, SRES, Kc
3.11.3.1
-
C
-
-
-
T
RAND, XRES CK, IK, AUTN
3.11.3.2
M
C
-
-
-
T
Master Key (MK)
3.11.3.3
-
M
-
-
-
T
Transient EAP Keys (TEKs)
3.11.3.4
-
M
-
-
-
T
Master Session Key (MSK)
3.11.3. 5
-
-
-
C
-
T
Session Identifier
3.11.4.1
-
M
C
C
-
T
Session-Timeout
3.11.4.2
-
C
-
-
-
P
W APN Identifier List
3.11.5.1.1
C
C
-
C
-
P
W-APN Barring Type List
3.11.5.1.2
C
C
-
-
-
P
W-APN Charging Data List
3.11.5.1.3
C
C
-
C
-
P
Static WLAN UE Remote IP Address List
3.11.5.1.4
C
C
-
C
-
P
Maximum-Number-Accesses List
3.11.5.1.5
C
C
-
-
-
P
Access-Number List
3.11.5.1.6
-
M
-
-
-
T
Access Dependence Flag
3.11.5.2
M
M
-
-
-
P
I-WLAN Access Type
3.11.5.3
M
M
-
-
-
T
WLAN Direct IP Access
3.11.5.4
C
C
-
-
-
P
Max Subscribed Bandwidth
3.11.6.1
C
C
-
C
-
P
Routing Policy
3.11.6.2
-
C
C
C
C
T
Subscribed 3GPP WLAN QoS Profile
3.11.6.3
C
C
-
-
P
Authorized 3GPP WLAN QoS Profile
3.11.6.4
-
C
-
C
-
T
Charging Characteristics
3.11.7.1.1
M
M
-
C
-
P
Primary OCS Charging Function Name
3.11.7.2
C Note 1
C
-
C
-
P
Secondary OCS Charging Function Name
3.11.7.3
C
C
-
C
-
P
Primary Charging Collection Function Name
3.11.7.4
C Note 1
C
-
C
-
P
Secondary Charging Collection Function Name
3.11.7.5
C
C
C
-
P
WLAN Session Identifier
3.11.7.6
-
M
C
C
-
T
PDG Session Identifier
3.11.7.7
-
C
C
M
-
T
Note 1: At least one of these Primary Charging Function Names shall be mandatorily provisioned in the HSS.
|
539f847bb6cd6c0ba766caacc29710d4
|
23.008
|
5.6 MBMS Storage (EPS)
|
Table 5.6-1: Overview of data used for MBMS (EPS)
PARAMETER
Clause
SGSN
MME
MBMS GW
BM-SC
TYPE
MBMS GW F-TEID for Sm(Control Plane)
2.22.1
-
C
C
-
T
MBMS GW F-TEID for Sn(Control Plane)
2.22.2
C
-
C
-
T
Temporary Mobile Group Identity
2.22.3
C
C
C
C
P
MBMS Flow Identifier
2.22.4
C
C
C
C
P
MBMS IP Multicast Distribution
2.22.5
C
C
C
-
T
MBMS Service Area
2.22.6
C
C
C
C
P
MME F-TEID for Sm (Control Plane)
2.22.7
-
C
C
-
T
SGSN F-TEID for Sn (Control Plane)
2.22.8
C
-
C
-
T
SGSN F-TEID for Sn (User Plane)
2.22.9
C
-
C
-
T
MBMS session identifier
2.22.10
C
C
C
C
P
MBMS session duration
2.22.11
C
C
C
C
P
QoS parameters
2.22.12
C
C
C
C
P
MBMS Time to Data Transfer
2.22.13
C
C
C
C
P
MBMS Data Transfer Start
2.22.14
-
C
C
C
P
List of downstream nodes
2.22.15
C
C
C
C
T
MBMS Session Re-establishment Indication
2.22.16
C
C
C
C
T
GCS AS Address
2.22.17
-
-
-
C
T
MB2-U Port Number
2.22.18
-
-
-
C
T
MBMS Start Time
2.22.19
-
-
-
C
T
TMGI Expiration Time
2.22.20
-
-
-
C
T
MBMS Alternative IP Multicast Distribution
2.22.21
-
C
C
-
T
MBMS Cell List
2.22.22
-
C
C
C
P
|
539f847bb6cd6c0ba766caacc29710d4
|
23.008
|
5.7 VPLMN Autonomous CSG Roaming Service Data Storage
|
Table 5.7-1: Overview of data used for VPLMN Autonomous CSG Roaming Service
PARAMETER
Clause
CSS
MME
S4-SGSN
Gn/Gp-SGSN
VLR
TYPE
IMSI
2.1.1.1
M
C
C
M
M
P
International MS ISDN number
2.1.2
C
C
C
C
C
P
VLR Number
2.4.5
M
-
-
-
-
T
SGSN Number
2.4.8.1
M
-
-
-
-
T
CSS Number
2.4.25
-
-
-
C
C
T
VPLMN Closed Subscriber Group Information
2.4.26
C
C
C
C
C
P
MME Name
2.13.26
M
-
-
-
-
T
SGSN Name
2.13.100
M
-
-
-
-
T
Diameter Server Identity of CSS
2.13.133
-
C
C
-
-
T
|
539f847bb6cd6c0ba766caacc29710d4
|
23.008
|
5.8 Proximity Services (ProSe) Data Storage
|
Table 5.8-1: Overview of data for Proximity Services
PARAMETER
Clause
HSS
SLP
MME
ProSe Function
ProSe Application Server
TYPE
IMSI
2.1.1.1
M
C
C
C
-
P
MSISDN
2.1.2
C
C
C
C
-
P
ProSe-Permission
3.13.2.1
C
-
C
C
-
P
PLMN-Allowed-ProSe
3.13.2.2
C
-
C
C
-
P
Application layer user ID
3.13.3
-
-
-
C
C
P
EPC ProSe User ID
3.13.4
-
-
-
C
C
T
ProSe Application ID
3.13.5
-
-
-
C
-
P
ProSe Application Code
3.13.6
-
-
-
C
-
T
Filter ID
3.13.7.1
-
-
-
C
-
P
ProSe Application Code
3.13.7.2
-
-
-
C
-
P
ProSe Application Mask
3.13.7.3
-
-
-
C
-
P
TTLTimer T4002
3.13.7.4
-
-
-
C
-
P
ProSe Function Identity
3.13.8
C
-
-
-
C
T
ProSe Metadata Index Mask
3.13.9
-
-
-
C
-
P
PC5-tech
3.13.10
-
-
-
C
-
T
|
539f847bb6cd6c0ba766caacc29710d4
|
23.008
|
5.9 Architecture Enhancements for Service Exposure storage (AESE)
|
Table 5.9-1: Overview of data used for AESE
PARAMETER
Clause
HSS
MME
SGSN
SCEF
TYPE
International MS ISDN number
2.1.2
C
C
C
C
P
External Identifier Set
2.1.10
C
-
-
C
P
SCEF-Reference-ID
3.14.2
C
C
C
C
T
SCEF-ID
3.14.3
C
C
C
C
P
Monitoring-Type
3.14.4
C
C
C
C
P
Maximum-Number-of-Reports
3.14.5
C
C
C
C
P
UE-Reachability-Configuration
3.14.6
C
C
C
C
P
Monitoring-Duration
3.14.7
C
C
C
C
P
Maximum-Detection-Time
3.14.8
C
-
-
C
P
Reachability-Type
3.14.9
C
-
-
C
P
Maximum Latency
3.14.10
C
-
-
C
P
Maximum Response Time
3.14.11
C
C
C
C
P
MONTE-Location-Type
3.14.12
C
C
C
C
P
Accuracy
3.14.13
C
C
C
C
P
Association-Type
3.14.14
C
-
-
C
P
Charged-Party
3.14.15
C
C
C
C
P
Remaining number of reports
3.14.16
C
C
C
C
T
Periodic-Communication-Indicator
3.14.17.1
C
C
-
C
P
Communication-Duration-Time
3.14.17.2
C
C
-
C
P
Periodic-Time
3.14.17.3
C
C
-
C
P
Scheduled-Communication-Time
3.14.17.4
C
C
-
C
P
Stationary-Indication
3.14.17.5
C
C
-
C
P
Validity-Time
3.14.17.6
C
C
-
C
P
AESE-Subscription-Data
3.14.18
C
-
-
-
P
SCEF-Realm
3.14.19
C
C
C
C
P
External-Identifier for Monitoring Event Configuration
3.14.20
C
C
C
C
P
External Group Identifier
3.14.21
C
-
-
C
P
|
539f847bb6cd6c0ba766caacc29710d4
|
23.008
|
5.10 Data related to Cellular IoT Control Plane Optimizations
|
Table 5.10-1: Overview of data used for CIoT
PARAMETER
Clause
HSS
MME
SGSN
SGW
PGW
SCEF
TYPE
IMSI
2.1.1.1
C
C
C
-
-
C
P
MSISDN
2.1.2
C
C
C
-
-
C
P
External Identifier set
2.1.10
C
-
-
-
-
C
P
Access Point Name
2.13.6
C
C
C
-
-
C
P
EPS Bearer Id
2.13.66
-
C
C
-
-
C
T
Acknowledgement-Of-Downlink-NAS-Data-PDUs flag
2.13.173
C
C
-
-
-
-
P
Robust Header Compression Context
2.23.1
-
C
-
-
-
-
T
MME F-TEID for S11 (user plane)
2.23.3
-
C
-
C
-
-
T
S-GW F-TEID for S11 (userplane)
2.23.4
-
C
-
C
-
-
T
Serving-PLMN-Rate-Control
2.23.5
-
C
-
C
C
C
P
APN-Rate-Control
2.23.6
-
-
-
-
C
C
P
Not Reachable for NIDD Flag
2.23.7
-
C
C
-
-
-
T
NIDD Authorization
2.23.8
C
-
-
-
-
C
P
SCEF-ID
3.14.3
C
C
C
-
-
C
P
SCEF-Realm
3.14.19
C
C
C
-
-
C
P
|
539f847bb6cd6c0ba766caacc29710d4
|
23.008
|
5.11 V2X Service (V2X) Data Storage
|
Table 5.11-1: Overview of data for V2X Service PARAMETER Clause HSS SLP MME V2X Control Function TYPE IMSI 2.1.1.1 M C C C P MSISDN 2.1.2 C C C C P V2X-Permission 3.16.2.1 C - C - P UE-PC5-AMBR 3.16.2.2 C - C - P V2X-PC5-Allowed-PLMN 3.16.2.3 C - - C P V2X-Permission-in-VPLMN 3.16.3.1 - - - C P V2X-Application-Server 3.16.3.2 - - - C P PC5-RAT-Type 3.16.3.3 C - - C P V2X Control Function Identity 3.16.4 C - - - T V2X-Permission 3.16.5.1 C - C - P UE-PC5-AMBR 3.16.5.2 C - C - P V2X-PC5-Allowed-PLMN 3.16.5.3 C - - C P UE-PC5-QoS 3.16.5.4 C - C - P Annex A (informative): Annex A (informative): Change history Date TSG # TSG Doc. CR Rev Cat Subject/Comment New Apr 1999 Transferred to 3GPP CN1 0.0.0 CN#03 Approved at CN#03 3.0.0 CN#05 002r1 Approved at CN#05 3.1.0 CN#06 003r1 Introduction of the Super-Charger Concept in TS 23.008 3.2.0 CN#06 004r3 Authentication Enhancements 3.2.0 CN#06 009 Authentication Enhancements 3.2.0 CN#06 010r2 Combined CR on 23.008 3.2.0 CN#06 011 Organization of Subscriber Data for LCS 3.2.0 CN#07 012r2 Introduction of 'Notification to CSE flag' to the operator determined barring data 3.3.0 CN#07 013 Correction of LSA Information 3.3.0 CN#07 014r2 The addition of priority information to subscriber data 3.3.0 CN#07 015r1 Introduction of Multicall 3.3.0 CN#07 016r1 Parallel handling of multiple PDP contexts 3.3.0 CN#07 019r1 Introduction of Service Area Identification 3.3.0 CN#07 020r1 Addition of gsmSCF address list to CSI 3.3.0 CN#07 023r1 Combined CR on 23.008 3.3.0 CN#07 024 Adding D-CSI to table with Negotiated CAMEL Capability Handling variables 3.3.0 CN#07 025 Addition of PDP Context Identifier 3.3.0 CN#08 017 Addition of subscribed charging characteristics information 3.4.0 CN#08 026r2 Editorial changes on 23.008 draft version 3.2.0 3.4.0 CN#08 027 Clarifications on GSM vs. UMTS specific parts 3.4.0 CN#08 029 Addition of charging characteristics per PDP context 3.4.0 CN#09 030 Deletion of "Barring of roaming" stored in SGSN 3.5.0 CN#09 031 Corrections of the description of BC allocation for VLR (Release 99) 3.5.0 CN#11 Version updated from R99 to Rel-4 after CN#11 4.0.0 CN#11 032r1 Declare barring data for ODB PS 4.0.0 CN#11 033r2 Addition of LCS related subscriber data for PS domain 4.0.0 CN#12 035r3 Correction of references 4.1.0 CN#12 037 Supported CAMEL Phases in VLR is temporary 4.1.0 CN#15 038r5 Addition of multimedia information elements 5.0.0 CN#15 039r1 Collective CRs against 23.008 for CAMEL phase4 5.0.0 CN#16 041r2 Filter Criteria Modifications 5.1.0 CN#16 043 Correction to TS 23.008 5.1.0 CN#16 044 Correction of the DP criteria table for T-CSI and VT-CSI on the Rel05 collective CR 5.1.0 CN#16 045r1 Splitting of CAMEL phase 4 5.1.0 CN#16 047r1 Addition of Service Indication 5.1.0 CN#16 048r1 CR on the charging function address format 5.1.0 CN#16 051 Correction of errors introduced with the taken into account CAMEL phase 4 5.1.0 CN#16 052r1 LCS: Service Type and Codeword 5.1.0 CN#16 053 Alignment of 23.008 5.1.0 CN#17 054r1 The Organisation of CAMEL IMS Data 5.2.0 CN#17 056r1 Handling of partial implementations of CAMEL phase 4 5.2.0 CN#17 057 Wrong Camel capability handling for the O‑CSI, T-CSI, VT-CSI and D-CSI 5.2.0 CN#18 058 Addition of Barring Indication of multimedia public identities 5.3.0 CN#18 060 Deleting codeword related information 5.3.0 CN#18 061r1 Correction to the form of public user identity 5.3.0 CN#19 065r1 Clarification of IMPU barring handling 5.4.0 CN#19 067r1 Definition of the Subscribed Media Profile Identifier 5.4.0 CN#20 068 Storage of UESBI in the VLR and SGSN 5.5.0 CN#20 121 Distinction between Roaming Restriction Due To Unsupported Feature and Roaming Restricted in the SGSN Due To Unsupported Feature 5.5.0 CN#21 122r2 Addition of a list of authorized visited network identifiers 5.6.0 CN#22 126 Registration status 5.7.0 CN#22 128r1 Correct table of IMS elements 5.7.0 CN#22 127r4 Services related to unregistered state 6.0.0 CN#23 129 Inclusion of Access_Restriction_Data parameter 6.1.0 CN#24 130r4 Add IMEISV to 'data stored in the HLR' due to ADD function 6.2.0 CN#25 133r3 GAA Domain Data Structure 6.3.0 CN#26 135r1 Inclusion of selected CN operator ID parameter 6.4.0 CN#26 136 Optimization of User Profile Download 6.4.0 CN#26 137 Subscribed Media Profile Identifier 6.4.0 CN#26 138r1 Domain independent GAA 6.4.0 CN#26 140 Correction to authorization flag definition 6.4.0 CN#26 141 Introduction of NAF groups 6.4.0 CN#26 142r1 WLAN-IW data handling: additions to 23.008 6.4.0 CN#27 134r4 Adding trace control and configuration parameters to subscriber data in HSS 6.5.0 CN#27 143r1 Add reference to Implicitly registered Public User Identities set definition 6.5.0 CT#28 148 Change the temporary flag of the MSISDN for GPRS 6.6.0 CT#28 0150 Removal of implied link between MS and IMS subscription 6.6.0 CT#28 0146r2 Corrections on WLAN UE Remote IP Address 6.6.0 CT#28 0147r1 Default Public User Identity per Implicit Registration Set 6.6.0 CT#28 0145r2 Corrections on Serving WAG 6.6.0 CT#28 0151r1 Addition of Maximum-Number-Accesses AVP and Number-Accesses Data types 6.6.0 CT#28 0144r4 Public Service Identity 6.6.0 CT#28 152r2 Correction on I-WLAN Service Data Storage table 6.7.0 CT#28 153 Correction to handling of Maximum-Number-Accesses description 6.7.0 CT#28 154R2 PSI routing 6.7.0 CT#28 155r1 Update to GAA time data items 6.7.0 CT#28 156r1 PSI Activation 6.7.0 CT#28 157r1 Removing references to Diameter draft 6.7.0 CT#28 159r1 IMSI handling at the PDG 6.7.0 CT#28 160 Change of reference from Release 5 to Release 6 6.7.0 CT#28 161 Association of the Charging Information with the IMS Subscription 6.7.0 CT#28 162 Charging-Information Correction 6.7.0 CT#30 0163r1 Incorrect References 6.8.0 CT#30 0164r1 Correction on I-WLAN Sevice Data Storage table 6.8.0 CT#30 0165r2 Updating the table of I-WLAN Data Storage 6.8.0 CT#30 Rel-7 version was created because of ETSI TISPAN references. 7.0.0 CT#31 0169r1 Correction to the Max Requested Bandwidth in I-WLAN data storage 7.1.0 CT#32 0172r2 Roaming handling with implicilty registered Public User IDs 7.2.0 CT#33 0179r1 Correction of the handling of transparent data 7.3.0 CT#33 0176r2 Storage of the Display Name in the IM Core Network Subsystem 7.3.0 CT#34 0170r4 Support of SMS over IP networks 7.4.0 0181r1 Activation Status of a PSI 7.4.0 0183r1 Charging identifier storage 7.4.0 0187r1 User Status valid values 7.4.0 0190r1 Definition of Wildcarded PSIs 7.4.0 0194 Clarification of the definition of the Service Indication 7.4.0 0195r1 Addition of Emergency Access Flag to I-WLAN User data 7.4.0 CT#35 0196r1 Subscriber data for Operator Determined Barring 7.5.0 0198r2 Correction of user data 7.5.0 0199r2 QoS parameter storage in I-WLAN entities 7.5.0 0201 MNRR correction 7.5.0 0205r1 Netwok Access Identifier Update 7.5.0 CT#36 0200r1 Addition of UNRI 7.6.0 0206 Mobile Termination whilst the MS is moving to another MSC 7.6.0 0207r2 Definition of the List of Subscribed IMS Communication Service Identifiers 7.6.0 0209 Negotiated CAMEL Capability Handling for M-CSI and SS-CSI 7.6.0 CT#37 0210 Mandatory Charging Data in the HSS 7.7.0 0211r1 Repository Data for Alias Public User Identities 7.7.0 0213r1 Repository Data for Wildcarded PSIs 7.7.0 CT#38 0220 Addition of Alias Public User Identities 7.8.0 CT#38 0214r5 Updates to 23.008 for Digest 8.0.0 CT#39 0222r2 Update for Supporting NASS-Bundled-Authentication 8.1.0 0223r1 PSI clarification 8.1.0 0226 Wildcarded Public User Identities 8.1.0 CT#40 0221r1 Paging optimization with A/Iu flex 8.2.0 CT#41 0229 Addition of IMS Centralized Service subscription information 8.3.0 0230r1 Support of "Loose-Route" indication from HSS 8.3.0 0232 Add S-CSCF Restoration Information as One Subscriber Data 8.3.0 CT#42 0234r1 Introduction of new subscriber related data for CS fallback 8.4.0 0233r4 Closed Subscriber Group 8.4.0 0236 Support for IMS Service Level Trace 8.4.0 0238r2 EPS related Subscriber Data 8.4.0 CT#43 0245r1 AliasesRepositoryData removal 8.5.0 0239r3 Correction and alignments with interface specifications 8.5.0 0244 EPS Subscription Data 8.5.0 Ct#44 0248r2 Loose Route Indication 8.6.0 0249 Parameters storage related to ISR 8.6.0 0251r3 User data related to UE reachability notification procedure 8.6.0 CT#45 0252r1 Subscribed and EPS PDN Connection Charging Characteristics 8.7.0 0254r1 HSS Data Corrections 8.7.0 0256r1 SA2 alignment in 23.008 8.7.0 0258r1 Correction on some ODB parameters description 8.7.0 0259r3 Removal of URRD 8.7.0 CT#45 0253r1 Managing membership of CSG users 9.0.0 0257r1 Subscriber Data for MBMS in EPS 9.0.0 CT#46 0260r2 Information storage for IMS emergency call over GRPS and EPS 9.1.0 0262r1 Correction on AMBR 9.1.0 0263r3 APN level APN-OI replacement 9.1.0 0266r1 ICS-Flag 9.1.0 0265r1 Information Storage correction 9.1.0 0268r2 RFSP alignment in 23.008 9.1.0 0274 Information storage for IMS emergency call over EPS non 3GPP access 9.1.0 0280 Corrections to "eNB F-TEID for S1-U" 9.1.0 0285r2 S4-SGSN and Gn/Gp-SGSN 9.1.0 0287r2 PDN Connection Id 9.1.0 CT#47 0292r1 Priority service information stored in HSS 9.2.0 0288r2 ANDSF Subscription Data 9.2.0 CT#48 0304r1 Update of IETF Reference 9.3.0 0296r3 Missing IMS information related to AS identities 9.3.0 0298r1 HPLMN ODB 9.3.0 0299 Information storage for UE's usage setting and voice capability 9.3.0 0302r1 URRP for SGSN 9.3.0 CT#49 0309 S-CSCF re-assignment pending flag 9.4.0 CT#49 0305r1 SIPTO Permission Indicator 10.0.0 CT#50 0313r2 Subscriber's data for MAPCON 10.1.0 0322r2 Missing Restoration flags for Gs/SGs interface 10.1.0 0328r1 Addition of UE Purge Flag 10.1.0 0326r1 Periodic TAU/RAU timer in HSS subscription 10.1.0 0325r5 Enhanced SRVCC Subscriber Data 10.1.0 0318r2 Definition of Alias Public User Identities 10.1.0 0316r1 Clarification on SIPTO Permission for Wildcard APN 10.1.0 0315r2 Non-3GPP data storage for S2b-GTP 10.1.0 0312r1 Addition of MPS Priority as Subscriber Data 10.1.0 0311r1 Addition of LIPA permission as Subscriber Data 10.1.0 0317r2 Addition of Service-related Entity Information elements to the Subscriber Data and removal of duplicated information 10.1.0 CT#51 0330r2 Minimization of Drive Tests (MDT) 10.2.0 0333r2 Subscription Data for Relay Node 10.2.0 0334 New Extended Priority data 10.2.0 0335 MT Roaming Retry and Super Charger 10.2.0 0337r1 STN-SR and SRVCC subscription 10.2.0 CT#52 0338r1 MDT user consent 10.3.0 0340r1 Addition of SC Address as Subscriber Data 10.3.0 0341r1 Periodic LAU timer in HSS subscription 10.3.0 CT#52 0336r2 Definition of Referece Location as Subscriber Data 11.0.0 CT#53 0351r1 VPLMN Address Allowed data defined per VPLMN 11.1.0 0345r1 Priviledged sender 11.1.0 0347r1 Add vSRVCC updates for subscriber data 11.1.0 0354r1 Addition of AMBR for GPRS 11.1.0 CT#54 0355r2 Correction on Definition of RAT Type 11.2.0 CT#55 0360r1 Information storage on the Higher bitrates than 16Mbps flag and the Max MBR/APN-AMBR 11.3.0 0363r2 Subscriber data for BBAI 11.3.0 CT#56 0361r2 Maximum Number of simultaneous registrations 11.4.0 0364r1 New IEs for H(e)NB case in BBAI 11.4.0 0362r7 Update of subscriber data with the PS additional number 11.4.0 0365r3 SMS in MME/SGSN 11.4.0 0346r9 CSS information storage 11.4.0 0366r1 Information Storage of the MME/SGSN ID in the PGW 11.4.0 0367r1 Information Storage of the SGW node name/ Co-located GGSN-PGW FQDN 11.4.0 0368r1 External Identifier 11.4.0 0369 Information Storage of the CGI/SAI age 11.4.0 0370r1 User's subscription data for WLAN access to EPC 11.4.0 CT#57 0375r1 PS only subscription w/o MSISDN 11.5.0 0376r1 Information storage of Homogeneous Support of IMS Voice over PS Sessions 11.5.0 0377 Data for I-WLAN service 11.5.0 0378r1 Uniform terminology 11.5.0 0379 Reference corrections 11.5.0 0380r1 Storage of last known cell identity in GGSN/PDN-GW 11.5.0 0381r1 Reference list correction to align with the corrected TS 29.212 title 11.5.0 CT#58 0384 SIPTO support for eHRPD 11.6.0 0393r1 Trace info stored in SGW/PGW 11.6.0 0382r1 Storage of the Signalling Priority Indication 11.6.0 0385 Key Status for UMTS 11.6.0 0386 Closed Subscriber Group Information for Inter-PLMN handover to a CSG cell 11.6.0 0389r1 Trace Info in CS data storage 11.6.0 0387 Removal of Maximum MBR/APN-AMBR 11.6.0 0388r1 PS only subscription without MSISDN 11.6.0 CT#59 0398r1 EPS Subscribed QoS Profile 11.7.0 CT#60 0403r2 Storing of eCGI within the VLR 11.8.0 0401 Restoration Priority during SGW and PGW restoration procedures 11.8.0 CT#60 0402r1 SIPTO permission for Local Network enhancements 12.0.0 0399 MBMS data storage 12.0.0 06-2013 Clause 5 empty cell in tables corrected with "-". 12.0.1 CT#61 0404r1 MBMS Session Re-establishment Indication 12.1.0 0405r1 Clarification of Aggregate Maximum Bit Rate (AMBR) terms 12.1.0 CT#63 0407r2 Storage of RAN assistance data in MME 12.2.0 CT#64 0410r1 CS to PS SRVCC 12.3.0 0412r1 IP-SM-GW address handling clarification 12.3.0 0408r1 Presence Reporting Area Action 12.3.0 0413r1 Consistency of ICS Indicator 12.3.0 CT#65 0420r1 RAN assistant information storage in MME 12.4.0 0421r2 WLAN offloadability 12.4.0 0422r1 Adding data related to the MB2 Interface for GCSE 12.4.0 0423 Storing of MME/S4 SGSN identifier in SGW 12.4.0 CT#66 0424r1 Storage of eNodeB FTEID for S1U at MME and RNC FTEID for S12 at S4-SGSN 12.5.0 0425 Default APN for Trusted WLAN 12.5.0 0426r1 WLAN offloadability indication stored in S4-SGSN 12.5.0 0427r4 UE Radio Access Capability 12.5.0 0429r4 ProSe parameter storage 12.5.0 0430r1 CN-Assisted Parameters 12.5.0 0431r1 Correction on the scope 12.5.0 0432r2 Restricted RAT Types 12.5.0 0433r1 I-WLAN maintenance 12.5.0 CT#67 0439r1 Missing PS-and-SMS-Only subscription parameter 12.6.0 CT#67 0437r1 Storage of MBMS Alternative IP Multicast Distribution Address by MBMS GW and MME 13.0.0 CT#68 0441 Network Access Mode 13.1.0 0444r3 Storage of accesss restriction data per PLMN 13.1.0 0449 Remove S2a GRE Keys from ePDG 13.1.0 0442r1 Storage of IMEI for WLAN access 13.1.0 0448r1 IP-SM-GW registration with Diameter 13.1.0 CT#69 0458r1 Storage of Active Timer for PSM 13.2.0 0450 Storage of Origination Time Stamp parameter 13.2.0 0451r1 Storage of new parameters for extended buffering at the SGW 13.2.0 0452 Storage of new parameter for the "Availability after DDN Failure" monitoring mechanism 13.2.0 0453r1 ProSe Function identifier 13.2.0 0454r2 Storage of IMSI-Group Identifier List 13.2.0 0455r1 Addition of "UE Usage Type" to Subscriber Data 13.2.0 0459r2 Storage of data for monitoring 13.2.0 CT#70 0460r1 Emergency PDN connection over untrusted WLAN access 13.3.0 0461 Storage of MBMS Cell List 13.3.0 0462r2 Storage information of ProSe-Metadata-Index-Mask 13.3.0 0471r1 The storage of a list of remote UEs 13.3.0 0463r3 Storage of CP parameters 13.3.0 0464r1 Storage of Extended idle mode DRX parameters 13.3.0 0469r2 Storage of DTCI and PNSI 13.3.0 466r1 The storage of UE Radio Capability for Paging Information 13.3.0 0468r1 Allowed WAF and/or WWSF Identities 13.3.0 0472r1 Parameters for paging optimisations 13.3.0 0473r2 Remove the storage of DL Buffering Suggested Packet Count in SGW 13.3.0 CT#71 0483r1 IP-SW-GW number format 13.4.0 0476r1 User Plane Integrity Protection Indicator 13.4.0 0477r1 Clarification on usage of P and T needs 13.4.0 0489r2 Subscription for allowed services 13.4.0 0484r1 Handover to Non-3GPP Access Not Allowed 13.4.0 0486r1 Addition of NB-IoT radio access type to the Access-Restriction-Dat-Type for Cellular IoT 13.4.0 2016-06 CT#72 CP-160212 0495 1 Correct the storage of Used UE-AMBR 13.5.0 2016-06 CT#72 CP-160228 0490 2 NIDD authorisation update 13.5.0 2016-06 CT#72 CP-160228 0491 1 Add S11-U MME F-TEID and S11-U SGW F-TEID into TS23.008 13.5.0 2016-06 CT#72 CP-160228 0492 1 PDN type Storage 13.5.0 2016-06 CT#72 CP-160228 0498 2 Address editor's note on ROHC config and security context for small data over control plane 13.5.0 2016-06 CT#72 CP-160228 0499 1 Serving PLMN rate control 13.5.0 2016-06 CT#72 CP-160228 0500 1 APN Rate Control 13.5.0 2016-06 CT#72 CP-160228 0501 2 Not Reachable for NIDD flag 13.5.0 2016-06 CT#72 CP-160225 0496 1 SCEF Realm 13.5.0 2016-06 CT#72 CP-160237 0502 1 Correction on A-MSISDN 13.5.0 2016-09 CT#73 CP-160572 0503 1 PDN-Connection-Restricted flag 13.6.0 2016-09 CT#73 CP-160423 0504 - Preferred Data Mode for an SGi PDN connection 13.6.0 2016-12 CT#74 CP-160660 0506 1 Correction on data used for AESE 13.7.0 2016-12 CT#74 CP-160652 0510 1 The storage of IOV_updates counter 13.7.0 2016-12 CT#74 CP-160679 0507 1 IMSI unauthenticated indicator 14.0.0 2016-12 CT#74 CP-160679 0511 1 Handover of Emergency PDN connection between LTE and WLAN 14.0.0 2016-12 CT#74 CP-160677 0509 1 Storage of DCN ID for eDECOR 14.0.0 2016-12 CT#74 CP-160680 0512 1 Storage of Non-IP related data in SGSN 14.0.0 2017-03 CT#75 CP-170025 0521 - MPS Priority additions to tabular summary 14.1.0 2017-03 CT#75 CP-170039 0513 1 Enhanced Coverage 14.1.0 2017-03 CT#75 CP-170043 0517 1 Storage of V2X Parameters 14.1.0 2017-03 CT#75 CP-170049 0518 2 Add ERP related data 14.1.0 2017-03 CT#75 CP-170038 0519 1 Subscription parameters for eDRX 14.1.0 2017-06 CT#76 CP-171016 0523 1 Explicit References to IWLAN specifications 14.2.0 2017-06 CT#76 CP-171021 0525 2 Correction to description of PDN-Connection-Restricted flag 14.2.0 2017-06 CT#76 CP-171029 0526 2 External-Identifier for Monitoring Event Configuration and External Group Identifier 14.2.0 2017-06 CT#76 CP-171034 0527 1 IMS Trace (ISAT) Reference Updates 14.2.0 2017-06 CT#76 CP-171043 0530 - Clarification of APN-Configuration-Profile for non-IP APNs 15.0.0 2017-09 CT#77 CP-172027 0532 1 Access Restriction for NR 15.1.0 2017-09 CT#77 CP-172018 0533 1 Acknowledgements of downlink NAS data PDUs 15.1.0 2017-12 CT#78 CP-173012 0539 - Discontinuation of TS 32.252 (I-WLAN Charging) 15.2.0 2017-12 CT#78 CP-173030 0540 - NIDD Authorization Subscription Data 15.2.0 2017-12 CT#78 CP-173035 0541 1 Access restriction to unlicensed spectrum as secondary RAT 15.2.0 2017-12 CT#78 CP-173032 0542 1 Storage of PC5-tech for WLAN based ProSe Direct Discovery 15.2.0 2018-03 CT#79 CP-180026 0549 1 Introducing NCGI 15.3.0 2018-03 CT#79 CP-180026 0555 2 Subscriber Data for 5GS 15.3.0 2018-03 CT#79 CP-180022 0556 1 "Service Gap Time" Subscription Data 15.3.0 2018-06 CT#80 CP-181132 0557 1 Storage of data interactions with the UDR 15.4.0 2018-06 CT#80 CP-181124 0558 - Storage of subscription data for ciphering keys in HSS to support broadcast of ciphered assistance data in E-UTRAN 15.4.0 2018-09 CT#81 CP-182084 0560 6 Storage information for 5GS 15.5.0 2018-09 CT#81 CP-182084 0564 2 Data related to authentication, ciphering and keying for 5GS 15.5.0 2018-09 CT#81 CP-182067 0562 1 Correction of the UE radio Access Capability size 15.5.0 2018-09 CT#81 CP-182075 0563 - External Identifier 15.5.0 2018-12 CT#82 CP-183082 0565 1 Note on additional NFs 15.6.0 2018-12 CT#82 CP-183082 0566 1 Kseaf is no longer transmitted with AV in 5G AKA 15.6.0 2018-12 CT#82 CP-183082 0567 1 Storage of Authentication Subscription data 15.6.0 2018-12 CT#82 CP-183082 0568 1 Storage of Authentication Status 15.6.0 2018-12 CT#82 CP-183082 0569 1 Storage of Authentication Data for steering of roaming 15.6.0 2018-12 CT#82 CP-183082 0570 1 Shared Data Ids for 5G 15.6.0 2019-03 CT#83 CP-190032 0571 1 Correction on referenced clause 15.7.0 2019-09 CT#85 CP-192126 0572 2 Additional RRM Policy Index 16.0.0 2019-09 CT#85 CP-192126 0573 1 Ethernet PDN type in EPS 16.0.0 2019-12 CT#86 CP-193036 0574 1 Adding support for subscription-based access restriction in 5GS 16.1.0 2020-03 CT#87e CP-200022 0575 2 Introduce support for 5G SRVCC in PS Network Access Mode Data (5GS) 16.2.0 2020-03 CT#87e CP-200027 0576 1 Addition of IAB-Operation Allowed indication to subscriber data 16.2.0 2020-03 CT#87e CP-200048 0577 - Correction on subscription based access restriction in unlicensed bands 16.2.0 2020-03 CT#87e CP-200021 0578 2 Addition of UE radio capability ID to subscriber data 16.2.0 2020-06 CT#88e CP-201071 0579 1 Support of inter-RAT HO from NR SA to EN-DC 16.3.0 2020-06 CT#88e CP-201049 0580 - Subscription data for NR V2X 16.3.0 2020-06 CT#88e CP-201048 0581 - Subscriber data for wireline access devices 16.3.0 2020-06 CT#88e CP-201032 0582 - Adding 5GS Broadcast Location Assistance subscriber data 16.3.0 2021-12 CT#94e CP-213104 0583 1 B Update of SIP Digest Access Authentication 17.0.0 2021-12 CT#94e CP-213111 0584 - B Adding satellite access restrictions 17.0.0 2022-03 CT#95e CP-220051 0586 2 B RedCap access restriction 17.1.0 2022-03 CT#95e CP-220093 0585 1 B Access Restriction for IoT Satellite Access 17.1.0 2024-03 - - - - Update to Rel-18 version (MCC) 18.0.0 2024-06 CT#104 CP-241029 0588 1 F NR eRedCAP Not Allowed as Primary RAT 18.1.0 2024-12 CT#106 CP-243062 0589 1 B Addition of Time Reference Information Distribution Indication 19.0.0
|
c5195074c429803154bc8b9cf2be11b9
|
23.015
|
1 Scope
|
The network feature Operator Determined Barring (ODB) allows a network operator or service provider to regulate access by subscribers to services (Circuit/Packet Oriented and Interworking WLAN), by the barring of certain categories of incoming or outgoing calls/ Packet Oriented Services or of roaming. Operator Determined Barring applies to all bearer services and teleservices except the Emergency Call teleservice and Emergency Bearer Services; the teleservice Short Message Point-to-Point is therefore subject to Operator Determined Barring in the same way as circuit-switched calls.
The application of specific categories of Operator Determined Barring to a subscription is controlled by the network operator or service provider, using administrative interaction at the HLR; this interface is not standardised.
|
c5195074c429803154bc8b9cf2be11b9
|
23.015
|
1.1 Normative references
|
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] 3GPP TS 21.905: "Abbreviations and acronyms".
[2] 3GPP TS 22.041: "Operator Determined Barring".
[3] 3GPP TS 23.040: "Technical realization of the Short Message Service (SMS)".
[4] 3GPP TS 23.060: " General Packet Radio Service (GPRS) Service description Stage 2".
[5] 3GPP TS 29.234: Release 11 "3GPP system to Wireless Local Area Network (WLAN) interworking; stage 3".
[6] 3GPP TS 23.401: "General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access".
[7] 3GPP TS 23.502: "Procedures for the 5G System; Stage 2".
|
c5195074c429803154bc8b9cf2be11b9
|
23.015
|
1.2 Definitions and abbreviations
|
Abbreviations used in this specification are listed in 3GPP TS 21.905.
|
c5195074c429803154bc8b9cf2be11b9
|
23.015
|
2 Method of realisation
|
The entities which control the application of Operator Determined Barring (ODB), and the methods used, are described in this clause. Two cases are considered for each type of barring: the effect of administrative action in the HLR to modify the application of the category to a particular subscription, and the effect of the category on the handling of calls or other traffic involving the subscriber.
|
c5195074c429803154bc8b9cf2be11b9
|
23.015
|
2.1 Barring of Outgoing Calls or Mobile Originated Short Messages
|
Barring of outgoing calls or mobile originated short messages includes the categories "outgoing calls" and "outgoing premium rate calls" defined in 3GPP TS 22.041 [2], and the "operator specific barring" category where this is defined by the PLMN operator to apply to outgoing calls or mobile originated short messages.
|
c5195074c429803154bc8b9cf2be11b9
|
23.015
|
2.1.1 Application or Change of Barring in the HLR
|
If barring of outgoing calls or mobile originated short messages is applied to a subscription (or existing barring of outgoing calls or mobile originated short messages is modified or removed) by administrative action in the HLR, the HLR will update the subscription information accordingly, and transfer the updated subscription information to the VLR and the SGSN using one or more Insert Subscriber Data operations, as shown in figure 2.1.1/1.
If operator specific barring is applied to a subscription (or existing operator specific barring is modified or removed) by administrative action in the HLR, the HLR will update the subscription information accordingly. If the mobile subscriber is registered in the home PLMN, the HLR will transfer the updated subscription information to the VLR and the SGSN using one or more Insert Subscriber Data operations, as shown in figure2.1.1/ 1.
If the VPLMN does not support Operator Determined Barring of outgoing calls, the VLR and the SGSN shall indicate this in the acknowledgement of the Insert Subscriber Data message. The HLR shall then, as an operator option, apply the Outgoing Calls Barred supplementary service, apply barring of roaming as described in clause 2.3 or take any other action decided by the operator of the HPLMN.
MS MSC VLR or SGSN HLR
ODB of outgoing calls applied, modified or removed
Insert
Subscriber
<-----------
data
Figure 2.1.1/1: Transfer of updated subscription information to VLR or SGSN
|
c5195074c429803154bc8b9cf2be11b9
|
23.015
|
2.1.2 Invocation of Barring
|
Barring of outgoing calls or mobile originated short messages is invoked in the VLR. If the VLR receives a request for subscription information for an outgoing call or mobile originated short message which is prohibited by Operator Determined Barring, the VLR will return a negative response to the request for subscription information, with an appropriate error indication. The MSC may relay this error indication via the BSS/RNS to the mobile station over the radio path, or (in the case of an outgoing call) may connect the mobile station to an address to be determined by the network operator.
Barring of mobile originated short messages is invoked in the SGSN. If the SGSN receives a request for a mobile originated short message which is prohibited by Operator Determined Barring, the SGSN will return a negative response to the request with an appropriate error indication via the BSS/RNS to the mobile station over the radio path.
Barring of all international calls, barring of all international calls except those directed to the home PLMN country, barring of all premium rate (information) calls or barring of all premium rate (entertainment) calls requires the VLR or the SGSN to analyse the called number to determine whether the requested call is barred.
Barring of all outgoing calls when roaming outside the home PLMN country requires the HLR to determine whether a request for location updating originates from a PLMN outside the home PLMN country. If the request does originate from a PLMN outside the home PLMN country, the HLR will transfer subscription information to the requesting node to indicate that the mobile station is subject to barring of all outgoing calls.
Operator Specific Barring may apply to outgoing or incoming calls, or mobile originated or mobile terminated short messages; if it applies to outgoing calls or mobile originated short messages, it is invoked in the VLR or the SGSN, as described above. If the barring applies to calls directed to a specific class of destination, the called number must be analysed to determine whether the requested call is barred.
Indicative message flow diagrams for the handling of Operator Determined Barring of outgoing calls or mobile originated short messages are given in figures 2.1.2/1 and 2.1.2/2. For the case where the mobile station is connected to an address determined by the network operator, this address is assumed to be directly connected to the MSC, so that no inter-MSC signalling is required.
MS MSC VLR
Outgoing call or MO SMS request barred because of ODB
O/G Request
----------------->
Send Info for
---------------->
O/G Call
Reject
<----------------
(cause)
Operator option: error indication returned to MS
Reject
<-----------------
(Cause)
Figure 2.1.2/1: Operator Determined Barring of Outgoing Calls or Mobile Originated Short Messages invocation in the VLR
MS SGSN
MO SMS request barred because of ODB
MO Short
----------------->
Message
Error indication returned to MS
Reject
<-----------------
(cause)
Figure 2.1.2/2: Operator Determined Barring of Mobile Originated Short Messages invocation in the SGSN
|
c5195074c429803154bc8b9cf2be11b9
|
23.015
|
2.2 Barring of Incoming Calls or Mobile Terminated Short Messages
| |
c5195074c429803154bc8b9cf2be11b9
|
23.015
|
2.2.1 Application or Change of Barring in the HLR
|
If barring of incoming calls or mobile terminated short messages is applied to a subscription (or existing barring of incoming calls or mobile terminated short messages is modified or removed) by administrative action in the HLR, the HLR will update the subscription information accordingly. It is not necessary to transfer the updated subscription information to the VLR or the SGSN.
|
c5195074c429803154bc8b9cf2be11b9
|
23.015
|
2.2.2 Invocation of Barring
|
Barring of incoming calls is invoked in the HLR. If the HLR receives a request for routing information for a call directed to a mobile station which is subject to barring of incoming calls, the HLR will return a negative response to the request for routing information, with an appropriate error indication. The Gateway MSC may relay this error indication to the originating network using the appropriate telephony signalling system, or may connect the call to a recorded announcement to be determined by the network operator.
Barring of mobile terminated short messages is invoked in the HLR. If the HLR receives a request for routing information for a short message directed to a mobile station which is subject to barring of incoming calls, the HLR will return a negative response to the request for routing information, with an appropriate error indication. This error indication will be relayed to the originating Short Message service centre by the Gateway MSC using the protocol defined in 3GPP TS 23.040.
Operator Specific Barring may apply to outgoing or incoming calls, or mobile originated or mobile terminated short messages; if it applies to incoming calls or mobile terminated short messages, it is invoked in the HLR, as described above.
An indicative message flow diagram for the handling of Operator Determined Barring of incoming calls is given in figure 2.2.2/1. For the case where the call is connected to an address determined by the network operator, this address is assumed to be directly connected to the GMSC, so that no inter-MSC signalling is required.
HLR GMSC N/W
Incoming call request barred because of ODB
Incoming call
<---------------
(address)
Send routing
<----------------
info request
Reject
---------------->
(cause)
Operator option: error indication returned to network
Reject
--------------->
(cause)
Figure 2.2.2/1: Operator Determined Barring of Incoming Calls
An indicative message flow diagram for the handling of Operator Determined Barring of mobile terminated short messages is given in figure 2.2.2/2.
HLR SMS GMSC SMS SC
MT short message request barred because of ODB
MT short
<---------------
message
Send routing
info for SM
<----------------
request
Reject
---------------->
(cause)
Reject
--------------->
(cause)
Figure 2.2.2/2: Operator Determined Barring of Mobile Terminated Short Messages
|
c5195074c429803154bc8b9cf2be11b9
|
23.015
|
2.3 Barring of Roaming
| |
c5195074c429803154bc8b9cf2be11b9
|
23.015
|
2.3.1 Application or Change of Barring in the HLR/HSS/UDM
|
If barring of roaming is applied to a subscription (or modified or removed) by administrative action in the HLR/HSS/UDM, the HLR/HSS/UDM shall update the subscription information accordingly. If the HLR/HSS/UDM determines from the identity of the VLR and/or the SGSN and/or MME and/or the AMF that the mobile subscriber is currently registered in a barred PLMN, the HLR/HSS/UDM shall put the barring into effect by using a Cancel Location operation to the VLR and/or the SGSN and /or to the MME when applied in HLR/HSS or a UECM Deregistration to AMF when applied in UDM, as shown in figure 2.3.1/1. In the 5G Core case, barring of roaming may be stored in UDR. Upon change of barring of roaming in UDR, UDM clears also user registration in UDR using Nudr_DM_Update operation and unsubscribes to changes on barring of roaming data using Nudr_DM_Unsubscribe operation.
If the mobile subscriber is not currently registered in a barred PLMN, the HLR/HSS/UDM shall take no further action.
MS MSC VLR or SGSN or MME HLR/HSS
ODB of roaming applied
Cancel
<-----------
location
Figure 2.3.1/1: Immediate Application of Barring of Roaming in HLR/HSS
UE AMF UDM
ODB of roaming applied
UECM Deregistration
<----------
Deregistration
<----------
Figure 2.3.1/2: Immediate Application of Barring of Roaming in UDM
|
c5195074c429803154bc8b9cf2be11b9
|
23.015
|
2.3.2 Invocation of Barring
|
Barring of roaming is invoked in the HLR/HSS/UDM. If the HLR receives a request from a VLR for location updating for a mobile which is attempting to roam to an area prohibited by Operator Determined Barring, the HLR shall reject the location updating request with an appropriate error indication and this error indication shall be relayed by the MSC and the BSS/RNS to the mobile station over the radio path. If the HLR receives a request from a SGSN for location updating for a mobile which is attempting to roam to an area prohibited by Operator Determined Barring, the HLR shall reject the location updating request with an appropriate error indication and this error indication shall be relayed by the SGSN and the BSS/RNS to the mobile station over the radio path. If the HSS receives a request from a MME for location updating for a mobile which is attempting to roam to an area prohibited by Operator Determined Barring, the HSS shall reject the location updating request with an appropriate error indication and this error indication shall be relayed by the MME to the mobile station over the radio path. If the UDM receives a request from an AMF for 5G registration for a user equipment who is attempting to roam to an area prohibited by Operator Determined Barring, the UDM shall reject the registration request with an appropriate error indication and this error indication shall be relayed by the AMF to the user equipment over the radio path.
In the 5G Core case, barring of roaming can be optionally stored in UDR. Upon change of barring of roaming in UDR, UDM clears also user registration in UDR using Nudr_DM_Update operation and unsubscribes to changes on barring of roaming data using Nudr_DM_Unsubscribe operation.
Indicative message flow diagrams for the handling of Operator Determined Barring of roaming are given in figures 2.3.2/1, 2.3.2/2, 2.3.2/3 and 2.3.2/4.
MS MSC VLR HLR
Roaming barred because of ODB
LR request
------------->
Location update
---------------->
request Update
Location
----------->
request
Reject
<-----------
(cause)
Reject
<----------------
(cause)
Reject
<-------------
(cause)
Figure 2.3.2/1: Operator Determined Barring of Roaming invocation in HLR. Roaming in a prohibited VLR
MS SGSN HLR
Roaming barred because of ODB
LR request
------------->
GPRS Update
Location
---------------->
request
Reject
<----------------
(cause)
Reject
<-------------
(cause)
Figure 2.3.2/2: Operator Determined Barring of Roaming invocation in HLR. Roaming in a prohibited SGSN
MS MME HSS
Roaming barred because of ODB
LR request
------------->
Update
Location
---------------->
request
Reject
<----------------
(cause)
Reject
<-------------
(cause)
Figure 2.3.2/3: Operator Determined Barring of Roaming invocation in HSS. Roaming in a prohibited MME
UE AMF UDM
Roaming barred because of ODB
Registration request
------------->
UECM Registration
---------------->
request
Reject
<----------------
(cause)
Reject
<-------------
(cause)
Figure 2.3.2/4: Operator Determined Barring of Roaming invocation in UDM. Roaming in a prohibited AMF
|
c5195074c429803154bc8b9cf2be11b9
|
23.015
|
2.4 Barring of Supplementary Services Access
|
Barring of supplementary services access encompasses the general barring of supplementary services management category specified in 3GPP TS 22.041 [2] and the specific categories of barring of registration of a call forwarded-to number and barring of invocation of call transfer.
|
c5195074c429803154bc8b9cf2be11b9
|
23.015
|
2.4.1 Application or Change of Barring in the HLR
|
If barring of supplementary services access is applied to a subscription (or existing barring of supplementary services access is modified or removed) by administrative action in the HLR, the HLR will update the subscription information accordingly, and, if necessary, transfer the updated subscription information to the VLR using one or more Insert Subscriber Data operations, as shown in figure 2.1.1/1.
If the VPLMN does not support Operator Determined Barring of supplementary service access, the VLR shall indicate this in the acknowledgement to the Insert Subscriber Data message. The HLR shall then, as an operator option, apply barring of roaming as described in clause 2.3 or take any other action decided by the operator of the HPLMN.
|
c5195074c429803154bc8b9cf2be11b9
|
23.015
|
2.4.2 Invocation of Barring
|
Barring of supplementary services access is invoked in the HLR or the VLR, depending on the supplementary service operation.
Barring of access to the following supplementary service operations is invoked in the HLR:
- registration;
- erasure;
- activation;
- deactivation;
- password registration;
- processing unstructured SS data.
An indicative message flow diagram for the handling in the HLR of Operator Determined Barring of access to supplementary services is given in figure 2.4.2/1.
MS MSC VLR HLR
Access to Supplementary Services barred because of ODB
SS request
------------->
SS activity
---------------->
request
SS
activity
----------->
request
Reject
<-----------
(cause)
Reject
<----------------
(cause)
Reject
<-------------
(cause)
Figure 2.4.2/1: Operator Determined Barring of Access to Supplementary Services in the HLR
NOTE 1: Although the HLR handles interrogation of some supplementary services, Operator Determined Barring of interrogation of all supplementary services is invoked in the VLR. This reduces the amount of analysis which the VLR must perform on supplementary service requests before deciding whether to relay a supplementary service request to the HLR or reject it because of Operator Determined Barring of access to supplementary services. Operator Determined Barring of control of PLMN specific supplementary services is invoked in the VLR for the same reason.
NOTE 2: Although the VLR handles some processing of unstructured SS data, and therefore has to check for Operator Determined Barring of access to supplementary services, a check is also specified in the HLR to guard against the case where the VLR does not support Operator Determined Barring of access to supplementary services.
Barring of access to the following supplementary service operations is invoked in the VLR:
- interrogation;
- invocation;
- control of PLMN specific supplementary services;
- processing unstructured SS data.
An indicative message flow diagram for the handling in the VLR of Operator Determined Barring of access to supplementary services is given in figure 2.4.2/2.
MS MSC VLR
Access to Supplementary Services barred because of ODB
SS request
------------->
SS activity
---------------->
request
Reject
<----------------
(cause)
Reject
<-----------------
(Cause)
Figure 2.4.2/2: Operator Determined Barring of Access to Supplementary Services in the VLR
|
c5195074c429803154bc8b9cf2be11b9
|
23.015
|
2.4.3 Operator Determined Barring of access to supplementary service not supported in VLR
|
If the VLR does not support Operator Determined Barring of access to supplementary services the HLR shall take the following actions:
The VLR supports only phase 1:
If the HLR receives a request which should normally be barred by the VLR the HLR shall reject the request with the appropriate phase 1 error (illegal SS operation or system failure).
The VLR supports phase 2 but does not support this Operator Determined Barring category:
If the HLR receives a request which should normally be barred by the VLR the HLR shall reject the request instead of the VLR.
Note that requests handled locally by the VLR (e.g. interrogation) will not be barred.
|
c5195074c429803154bc8b9cf2be11b9
|
23.015
|
2.5 Barring of MS initiated PDP context activation
|
Barring of MS initiated PDP context activation shall be performed based on the Operator Determined Barring for Packet Oriented Services defined in 3G TS 22.041 [2].
|
c5195074c429803154bc8b9cf2be11b9
|
23.015
|
2.5.1 Application or Change of Barring in the HLR
|
If barring of Packet Oriented Services is applied to a subscription (or existing barring of Packet Oriented Services is modified or removed) by administrative action in the HLR, the HLR will update the subscription information accordingly, and transfer the updated subscription information to the SGSN using one or more Insert Subscriber Data operations, as shown in figure 2.5.1/1.
If the VPLMN does not support Operator Determined Barring of Packet Oriented Services, the SGSN shall indicate this in the acknowledgement of the Insert Subscriber Data message. The HLR shall then, as an operator option, apply barring of roaming as described in clause 2.3 or take any other action decided by the operator of the HPLMN.
MS SGSN HLR
ODB of Packet Oriented Services applied, modified or removed
Insert
Subscriber
<-----------
data
Figure 2.5.1/1: Transfer of updated subscription information to SGSN
|
c5195074c429803154bc8b9cf2be11b9
|
23.015
|
2.5.2 Invocation of Barring
|
Barring of MS initiated PDP context activation is invoked in the SGSN. If the SGSN receives a request for an MS initiated PDP context activation which is prohibited by Operator Determined Barring, the SGSN will return a negative response to the request with an appropriate error indication via the BSS/RNS to the mobile station over the radio path.
NOTE: Barring of MS initiated PDP context activation for Packet Oriented Services is not applicable for Local IP Access (LIPA).
Barring of MS initiated PDP context activation is performed in the SGSN while the SGSN selects the APN and GGSN. The APN operator identifier, a part of selected APN is referred to make a judgement whether to be barred or not. The detail mechanism of the ODB judgement is specified in the 3G TS 23.060 [4].
Indicative message flow diagram for the handling of Operator Determined Barring of MS initiated PDP context activation is given in figures 2.5.2/1.
MS SGSN
MS initiated PDP context activation barred because of ODB
Activate PDP
context request
---------------->
Reject
<----------------
(cause)
Figure 2.5.2/1: Operator Determined Barring of MS initiated PDP context activation in the SGSN
2.5A Barring of EPS Bearer context establishment
Barring of EPS Bearer context establishment shall be performed based on the Operator Determined Barring for Packet Oriented Services defined in 3GPP TS 22.041 [2].
2.5A.1 Application or Change of Barring in the HSS
If barring of Packet Oriented Services is applied to a subscription (or existing barring of Packet Oriented Services is modified or removed) by administrative action in the HSS, the HSS shall update the subscription information accordingly, and transfer the updated subscription information to the MME using one or more Insert Subscriber Data operations, as shown in figure 2.5A.1/1.
If the VPLMN does not support Operator Determined Barring of Packet Oriented Services, the MME shall indicate this in the acknowledgement of the Insert Subscriber Data message. The HSS shall then, as an operator option, apply barring of roaming as described in clause 2.3 or take any other action decided by the operator of the HPLMN.
MS MME HSS
ODB of Packet Oriented Services applied, modified or removed
Insert
Subscriber
<-----------
data
Figure 2.5A.1/1: Transfer of updated subscription information to MME
2.5A.2 Invocation of Barring
Barring of EPS Bearer context establishment is invoked in the MME. If the MME receives from an UE connected over E-UTRAN an attach or PDN connectivity request which is prohibited by Operator Determined Barring, the MME shall return a negative response to the request with an appropriate error indication to the UE over the E-UTRAN radio path.
NOTE: Barring of EPS Bearer context establishment for Packet Oriented Services is not applicable for Local IP Access (LIPA).
For subscribers completely barred from the Packet Oriented Services, the MME shall reject attach requests.
Barring of EPS Bearer context establishsment for other barring categories for the Packet Oriented Services requires the MME to selects the APN and PDN-GW before it can determine whether a request for EPS Bearer context establishment shall be barred or not:
- For "bar a subscriber from requesting Packet Oriented Services from access points that are within the HPLMN whilst the subscriber is roaming in a VPLMN", MME shall check whether or not the subscriber is located in the HPLMN. If it is not and the PDN-GW being accessed is located in HPLMN, then the MME shall reject the attach or PDN connectivity request,
- For "bar a subscriber from requesting Packet Oriented Services from access points that are within the roamed to VPLMN", MME shall check whether or not the subscriber is located in the HPLMN. If it is not and the PDN-GW being accessed is located in VPLMN, then the MME shall reject the attach or PDN connectivity request.
Indicative message flow diagram for the handling of Operator Determined Barring of EPS Bearer context establishment is given in figures 2.5A.2/1.
UE MME
E-UTRAN PDN connectivity barred because of ODB
Attach Request, or
PDN Connectivity request
---------------->
Reject
<----------------
(cause)
Figure 2.5A.2/1: Operator Determined Barring of EPS Bearer Context Establishment in the MME
2.5B Barring of PDU Session establishment
Barring of PDU Session establishment shall be performed based on the Operator Determined Barring for Packet Oriented Services defined in 3GPP TS 22.041 [2].
2.5B.1 Application or Change of Barring in the UDM
If barring of Packet Oriented Services is applied to a subscription (or existing barring of Packet Oriented Services is modified or removed) by administrative action in the UDM, the UDM shall update the subscription information accordingly, and transfer the updated subscription information to the AMF/SMF using Nudm_SDM Notification operation, as shown in figure 2.5B.1/1.
MS AMF or SMF UDM
ODB of Packet Oriented Services applied, modified or removed
Nudm_SDM
Notification
<-----------
Figure 2.5B.1/1: Transfer of updated subscription information to AMF/SMF
2.5B.2 Invocation of Barring
Barring of PDU Session establishment is invoked in the SMF. If the SMF receives from an UE connected over 5GS a PDU Session connectivity request which is prohibited by Operator Determined Barring, the SMF shall return a negative response to the request with an appropriate error indication to the UE over the 5G radio path.
NOTE: Barring of PDU Session establishment for Packet Oriented Services is not applicable for Local Access Data Network (LADN).
For subscribers completely barred from the Packet Oriented Services, the AMF may reject the registration requests.
Barring of PDU Session establishment for other barring categories for the Packet Oriented Services, the SMF determines whether a request for PDU Session establishment shall be barred or not based on the subscription data from UDM as below:
- For "bar subscribers completely from the Packet Oriented Services", the SMF shall reject the PDU connectivity request.
- For "bar a subscriber from requesting Packet Oriented Services from access points that are within the HPLMN whilst the subscriber is roaming in a VPLMN", if the subscriber is not located in the HPLMN and the SMF being accessed is located in HPLMN, then the SMF shall reject the PDU connectivity request,
- For "bar a subscriber from requesting Packet Oriented Services from access points that are within the roamed to VPLMN", if the subscriber is not located in the HPLMN and the SMF being accessed is located in VPLMN, then the SMF shall reject the PDU connectivity request.
The AMF may also determine a request for PDU Session establishment shall be barred or not based on above scenarios and indicate the SMF to reject the request.
Indicative message flow diagram for the handling of Operator Determined Barring of PDU Session establishment is given in figures 2.5B.2/1.
UE SMF
5G PDU connectivity barred because of ODB
PDU Connectivity request
---------------->
Reject
<----------------
(cause)
Figure 2.5B.2/1: Operator Determined Barring of PDU Session Establishment in the SMF
|
c5195074c429803154bc8b9cf2be11b9
|
23.015
|
2.6 Barring of Network initiated PDP context activation
|
Barring of Network initiated PDP context activation shall be performed based on the Operator Determined Barring for Packet Oriented Services defined in 3G TS 22.041 [2].
|
c5195074c429803154bc8b9cf2be11b9
|
23.015
|
2.6.1 Application or Change of Barring in the HLR
|
If barring of Packet Oriented Services is applied to a subscription (or existing barring of Packet Oriented Services is modified or removed) by administrative action in the HLR, the HLR will update the subscription information accordingly. It is not necessary to transfer the updated subscription information to the SGSN.
|
c5195074c429803154bc8b9cf2be11b9
|
23.015
|
2.6.2 Invocation of Barring
|
Barring of Network initiated PDP context activation is invoked in the HLR. If the HLR receives a request for routing information for a PDP context activation directed to a mobile station which is subject to barring of Packet Oriented Services, the HLR will return a negative response to the request for routing information, with an appropriate error indication. The GGSN may relay this error indication to the PDP PDU incoming network using the appropriate interworking.
An indicative message flow diagram for the handling of Operator Determined Barring of Network initiated PDP context activation is given in figure 2.6.2/1.
HLR GGSN N/W
Network initiated PDP context activation barred because of ODB
Incoming PDP PDU
<---------------
(address)
Send routing
<----------------
info request
for GPRS
Reject
---------------->
(cause)
Operator option: error indication returned to network
Reject
--------------->
(cause)
Figure 2.6.2/1: Operator Determined Barring of Network initiated PDP context activation
2.6A Barring of existing PDP contexts
Barring of existing PDP contexts shall be performed based on the Operator Determined Barring for Packet Oriented Services defined in 3G TS 22.041 [2].
2.6A.1 Application or Change of Barring in the HLR
If barring of Packet Oriented Services is applied to a subscription (or existing barring of Packet Oriented Services is modified or removed) by administrative action in the HLR, the HLR will update the subscription information accordingly, and transfer the updated subscription information to the SGSN using one or more Insert Subscriber Data operations, as shown in figure 2.6A.1/1.
If the VPLMN does not support Operator Determined Barring of Packet Oriented Services, the SGSN shall indicate this in the acknowledgement of the Insert Subscriber Data message. The HLR shall then, as an operator option, apply barring of roaming as described in clause 2.3 or take any other action decided by the operator of the HPLMN.
MS SGSN HLR
ODB of Packet Oriented Services applied, modified or removed
Insert
Subscriber
<-----------
data
Figure 2.6A.1/1: Transfer of updated subscription information to SGSN
2.6A.2 Invocation of Barring
Barring of existing PDP contexts is invoked in the SGSN. If the SGSN receives Insert Subsciber Data message due to barring of Packet Oriented Services is applied to a subscription (or existing barring of Packet Oriented Services is modified or removed) by administrative action in the HLR, the SGSN shall take the following action depending on barring category when one or more PDP contexts exist in SGSN.
- For "bar subscribers completely from the Packet Oriented Services", SGSN shall deactivate all existing PDP contexts.
- For "bar a subscriber from requesting Packet Oriented Services from access points that are within the HPLMN whilst the subscriber is roaming in a VPLMN", SGSN shall check whether or not the subscriber is located in the HPLMN. If it is not and the GGSN being accessed is located in HPLMN, then all associated PDP contexts with this path shall be deactivated..
- For "bar a subscriber from requesting Packet Oriented Services from access points that are within the roamed to VPLMN", SGSN shall check whether or not the subscriber is located in the HPLMN. If it is not and the GGSN being accessed is located in VPLMN, then all associated PDP contexts with this path shall be deactivated.
NOTE: Barring of existing PDP contexts for Packet Oriented Services is not applicable for Local IP Access (LIPA).
2.6B Barring of existing EPS Bearer contexts
Barring of existing EPS Bearer contexts shall be performed based on the Operator Determined Barring for Packet Oriented Services defined in 3GPP TS 22.041 [2].
2.6B.1 Application or Change of Barring in the HSS
If barring of Packet Oriented Services is applied to a subscription (or existing barring of Packet Oriented Services is modified or removed) by administrative action in the HSS, the HSS shall update the subscription information accordingly, and transfer the updated subscription information to the MME using one or more Insert Subscriber Data operations, as shown in figure 2.6B.1/1.
If the VPLMN does not support Operator Determined Barring of Packet Oriented Services, the MME shall indicate this in the acknowledgement of the Insert Subscriber Data message. The HSS shall then, as an operator option, apply barring of roaming as described in clause 2.3 or take any other action decided by the operator of the HPLMN.
UE MME HSS
ODB of Packet Oriented Services applied, modified or removed
Insert
Subscriber
<-----------
data
Figure 2.6B.1/1: Transfer of updated subscription information to MME
2.6B.2 Invocation of Barring
Barring of existing EPS Bearer contexts is invoked in the MME. If the MME receives Insert Subscriber Data message due to barring of Packet Oriented Services being applied to a subscription (or existing barring of Packet Oriented Services is modified) by administrative action in the HSS, the MME shall take the following action depending on barring category when one or more EPS Bearer contexts exist in MME.
- For "bar subscribers completely from the Packet Oriented Services", MME shall deactivate all existing EPS Bearer contexts.
- For "bar a subscriber from requesting Packet Oriented Services from access points that are within the HPLMN whilst the subscriber is roaming in a VPLMN", MME shall check whether or not the subscriber is located in the HPLMN. If it is not and the PDN-GW being accessed is located in HPLMN, then all associated EPS Bearer contexts with this path shall be deactivated.
- For "bar a subscriber from requesting Packet Oriented Services from access points that are within the roamed to VPLMN", MME shall check whether or not the subscriber is located in the HPLMN. If it is not and the PDN-GW being accessed is located in VPLMN, then all associated EPS Bearer contexts with this path shall be deactivated.
NOTE: Barring of existing EPS Bearer contexts for Packet Oriented Services is not applicable for Local IP Access (LIPA).
2.6C Barring of existing PDU Sessions
Barring of existing PDU Sessions shall be performed based on the Operator Determined Barring for Packet Oriented Services defined in 3GPP TS 22.041 [2].
2.6C.1 Application or Change of Barring in the UDM
If barring of Packet Oriented Services is applied to a subscription (or existing barring of Packet Oriented Services is modified or removed) by administrative action in the UDM, the UDM shall update the subscription information accordingly, and transfer the updated subscription information to the AMF using Nudm_SDM Notification operation, as shown in figure 2.6C.1/1.
UE AMF UDM
ODB of Packet Oriented Services applied, modified or removed
Nudm_SDM
Notification
<-----------
Figure 2.6C.1/1: Transfer of updated subscription information to AMF
2.6C.2 Invocation of Barring
Barring of existing PDU Sessions is invoked in the AMF. If the AMF receives Nudm_SDM Notification message due to barring of Packet Oriented Services being applied to a subscription (or existing barring of Packet Oriented Services is modified) by administrative action in the UDM, or if the new AMF received the barring of Packet Oriented Services from the UDM during a mobility registration procedure, the AMF shall take the following action depending on barring category when one or more PDU Sessions exist in AMF.
- For "bar subscribers completely from the Packet Oriented Services", AMF shall request SMF to release all existing PDU Sessions.
- For "bar a subscriber from requesting Packet Oriented Services from access points that are within the HPLMN whilst the subscriber is roaming in a VPLMN", AMF shall check whether or not the subscriber is located in the HPLMN. If it is not and the SMF being accessed is located in HPLMN, then all associated PDU Sessions with this path shall be released by the SMF on request of the AMF.
- For "bar a subscriber from requesting Packet Oriented Services from access points that are within the roamed to VPLMN", AMF shall check whether or not the subscriber is located in the HPLMN. If it is not and the SMF being accessed is located in VPLMN, then all associated PDU sessions with this path shall be released by the SMF on request of the AMF.
NOTE: Barring of existing EPS Bearer contexts for Packet Oriented Services is not applicable for Local Access Data Network (LADN).
|
c5195074c429803154bc8b9cf2be11b9
|
23.015
|
2.7 Interactions of Operator Determined Barring with Supplementary Services
|
The following interactions of Operator Determined Barring with supplementary services have been identified:
|
c5195074c429803154bc8b9cf2be11b9
|
23.015
|
2.7.1 Call Forwarding
|
The interactions between Operator Determined Barring and Call Forwarding are specified in 3GPP TS 22.041 [2].
The interaction where Operator Determined Barring is applied when there is an existing Call Forwarding programme which is in contravention of the Operator Determined Barring programme is shown in the message flow diagram in figure 2.7.1/1. The HLR modifies the subscription information for the mobile subscriber to show that the contravening call forwarding programme is quiescent, and forwards the modified subscription information to the VLR. No indication is forwarded to the mobile station or the user.
MS MSC VLR HLR
ODB applied when Call Forwarding programme contravenes ODB
Insert
Subscriber
<-----------
data
Figure 2.7.1/1: Effect of Operator Determined Barring on Call Forwarding programme
The interaction where the user attempts to activate or register a call forwarding programme which is in contravention of an operator determined barring category is shown in the message flow diagram in figure 2.7.1/2.
MS MSC VLR HLR
Request for Call Forwarding programme contravening ODB
SS request
(register or
------------->
activate CF)
SS activity
---------------->
request
SS
activity
----------->
request
Reject
<-----------
(cause)
Reject
<----------------
(cause)
Operator option: error indication returned to MS
Reject
<-------------
(cause)
Figure 2.7.1/2: Interaction between Operator Determined Barring and Call Forwarding
|
c5195074c429803154bc8b9cf2be11b9
|
23.015
|
2.7.2 Closed User Group
|
The interaction between Operator Determined Barring and Closed User Group is specified in 3GPP TS 22.041 [2]. In order to meet the service requirement, the checks of a call request in the HLR (for incoming calls) or VLR (for outgoing calls) against the Operator Determined Barring programme shall be carried out before the checks for Closed User Group.
|
c5195074c429803154bc8b9cf2be11b9
|
23.015
|
2.7.3 Call Barring
|
The interaction between Operator Determined Barring and the Call Barring supplementary service is specified in 3GPP TS 22.041 [2]. In order to meet the service requirement, the checks of a call request in the HLR (for incoming calls) or VLR (for outgoing calls) against the Operator Determined Barring programme shall be carried out before the checks for the Call Barring supplementary service.
|
c5195074c429803154bc8b9cf2be11b9
|
23.015
|
2.8 Barring of services in I-WLAN
|
NOTE: The WLAN Network Selection and WLAN/3GPP Radio Interworking features supersede the I-WLAN feature from Rel-12 onwards, therefore all I-WLAN related requirements specified in the present Clause are no longer maintained.
Barring of interworked services in I-WLAN upon the activation of W-APN shall be performed based on the Operator Determined Barring for Packet Oriented Services as defined in 3GPP TS 29.234 [5].
|
c5195074c429803154bc8b9cf2be11b9
|
23.015
|
2.8.1 Change of Barring in the HSS
|
If barring of Packet Oriented Services for I-WLAN is applied to a subscription (or existing barring of Packet Oriented Services is modified or removed) by administrative action in the HSS, the HSS shall update the subscription information accordingly. It is necessary to transfer the updated User Profile Data and subscription information to the 3GPP AAA Server if the subscriber is currently using interworked WLAN services. After downloading the update User Profile Data the 3GPP AAA Server shall initiate re-authorization of the W-APN if there is an existing connection established. The HSS initiated User Profile Data update indication followed by the 3GPP AAA Server download of the updated User Profile Data and re-authorization request is shown in the message flow diagram in Figure 2.8.1/1.
WLAN-UE (Visited/Home) PDG 3GPP AAA Server HSS
ODB of Packet Oriented Services applied, modified or removed
Update of
User Profile
<-----------
data
Download
User Profile
<----------->
data
Re-authorization Request
if there is existing W-APN
connection established
<-----------
Figure 2.8.1/1: Transfer of updated User profile Data to 3GPP AAA Server
|
c5195074c429803154bc8b9cf2be11b9
|
23.015
|
2.8.2 Barring of interworked packet services in I-WLAN
|
The interactions between Operator Determined Barring and W-APN activation/authorization are specified in 3GPP TS 29.234 [5].
Barring of interworked WLAN packet services is invoked in the 3GPP AAA Server. If the 3GPP AAA Server receives a request for a W-APN activation/authorization which is prohibited by Operator Determined Barring, the 3GPP AAA Server shall return a negative response to the request with an appropriate error code.
Indicative message flow diagram for the handling of Operator Determined Barring of interworked WLAN packet services is given in figure 2.8.2/1.
WLAN-UE (Visited/Home) PDG 3GPP AAA Server HSS
Activation of W-APN when interworked packet services are barred
W-APN (re-)authorization
----------->
Authorization Reject
<-----------
Figure 2.8.2/1: Authorization attempt of a interworked packet services when the WLAN-UE is connecting via a PDG located either in Visited or Home PLMN
|
c5195074c429803154bc8b9cf2be11b9
|
23.015
|
2.8.3 Barring of W-APN Activation in I-WLAN
|
The interactions between Operator Determined Barring and W-APN activation/authorization are specified in 3GPP TS 29.234 [5].
Barring of specific W-APN is invoked in the 3GPP AAA Server. If the 3GPP AAA Server receives a request for a W-APN activation/authorization which is prohibited by Operator Determined Barring, the 3GPP AAA Server shall return a negative response to the request with an appropriate error code.
Indicative message flow diagram for the handling of Operator Determined Barring of a specific W-APN is given in figure 2.8.3/1.
WLAN-EU (Visited/Home) PDG 3GPP AAA Server HSS
Activation of W-APN when the said W-APN is barred
W-APN (re-)authorization
----------->
Authorization Reject
<-----------
Figure 2.8.3/1: Authorization attempt of a W-APN when the WLAN-UE is connecting via a PDG located either in Visited or Home PLMN
|
c5195074c429803154bc8b9cf2be11b9
|
23.015
|
2.8.4 Barring of public Internet access in I-WLAN
|
The interactions between Operator Determined Barring and W-APN activation/authorization are specified in 3GPP TS 29.234 [5].
Barring of specific public Internet access through a specific W-APN is invoked in the 3GPP AAA Server. If the 3GPP AAA Server receives a request for a W-APN activation/authorization where public Internet access is prohibited by Operator Determined Barring, the 3GPP AAA Server shall return a positive response to the request with appropriate routing policies that allow the PDG filter IP traffic to or from public Internet.
Indicative message flow diagram for the handling of Operator Determined Barring of a specific W-APN is given in figure 2.8.4/1.
WLAN-EU (Visited/Home) PDG 3GPP AAA Server HSS
Activation of W-APN when access to public Internet is barred
W-APN (re-)authorization
----------->
Authorization Accept and
Routing Policy Download
<-----------
Figure 2.8.4/1: Authorization of a W-APN when public Internet access is barred
|
c5195074c429803154bc8b9cf2be11b9
|
23.015
|
2.9 Barring of Access to All Except Some Specific DNNs/APNs
| |
c5195074c429803154bc8b9cf2be11b9
|
23.015
|
2.9.1 General
|
Barring of access to all except some specific DNNs/APNs shall be performed based on the Operator Determined Barring for Packet Oriented Services defined in 3GPP TS 22.041 [2].
|
c5195074c429803154bc8b9cf2be11b9
|
23.015
|
2.9.2 Application or Change of Barring in the UDM/HSS/HLR
|
When barring of access to all except some specific DNNs/APNs is invoked in the UDM/HSS/HLR, the UDM/HSS/HLR shall update the subscription profile to contain only the specific non barred DNNs/APNs as the subscribed DNNs/APNs and indicate the updated subscription information to the AMF, SMF, MME or the SGSN.
If the existing default DNN/APN is barred, one of the specific non barred DNN/APNs shall be the new default DNN/APN.
The UDM/HSS/HLR shall disable any other barring of Packet Oriented Services when this function is used.
When barring of access to all except some specific DNNs/APNs is removed in the UDM/HSS/HLR, the UDM/HSS/HLR shall update the subscription profile to restore the originally subscribed DNNs/APNs, including the original default DNN/APN and indicate the updated subscription information to the AMF, SMF, the MME or the SGSN.
For 5GC, if the AMF/SMF/UDM supports the "OdbExemptedDnn" feature, when barring of access to all except some specific DNNs is invoked, the UDM may provision the odbPacketServices together with odbExemptedDnnData which contains those specific DNNs exempted from the barring, without or with spatial and time validity conditions. When barring of access to all except some specific DNNs is removed in the UDM, the UDM removes the odbPacketServices in the AccessAndMobilitySubscriptionData and SessionManagementSubscriptionData.
|
c5195074c429803154bc8b9cf2be11b9
|
23.015
|
2.9.3 Invocation of Barring
|
When the AMF, the SMF, the MME or the SGSN updates the subscription, and if the subscriber has existing PDN connectivity for DNNs/APNs not in the received list of subscribed DNN/APN, the SMF, MME or the SGSN deactivates the PDU/PDN connectivity for these DNNs/APNs as specified in 3GPP TS 23.502 [7], 3GPP TS 23.401 [6] and 3GPP TS 23.060 [4].
To bar a subscriber from access to all except some specific DNNs/APNs, when the AMF, the MME or the SGSN receives PDU/PDN Connectivity Request message from the UE or the MS, the AMF, the MME or the SGSN shall check whether or not the requested DNN/APN is included in the list of subscribed DNNs/APNs for the subscriber. If included, then the AMF, the MME or the SGSN continues the Attach or UE-requested PDU/PDN connectivity or MS-requested PDP Context Activation procedures as specified in 3GPP TS 23.502 [7], 3GPP TS 23.401 [6] and 3GPP TS 23.060 [4]. If not included, then the AMF, the MME or the SGSN rejects the Attach or UE-requested PDU/PDN connectivity or MS-requested PDP Context Activation requests as specified in 3GPP TS 23.502 [7], 3GPP TS 23.401 [6] and 3GPP TS 23.060 [4].
|
c5195074c429803154bc8b9cf2be11b9
|
23.015
|
3 Information stored in location registers
| |
c5195074c429803154bc8b9cf2be11b9
|
23.015
|
3.1 Information stored in the HLR/HSS
|
The HLR must store subscription information for each mobile subscriber to define which of the following categories of barring is to be applied, independently of each other:
Barring of outgoing calls (including mobile originated short messages) - one of:
- Barring of all outgoing calls;
- Barring of all outgoing international calls;
- Barring of all outgoing international calls except those directed to the home PLMN country;
- Barring of all outgoing calls when roaming outside the home PLMN country;
- Barring of all outgoing inter-zonal calls;
- Barring of all outgoing inter-zonal calls except those directed to the home PLMN country;
- Barring of all outgoing international calls except those directed to the home PLMN country AND barring of all outgoing inter-zonal calls.
Barring of incoming calls (including mobile terminated short messages) - one of:
- Barring of all incoming calls;
- Barring of all incoming calls when roaming outside the home PLMN country;
- Barring of all incoming calls when roaming outside the zone of the home PLMN country.
Barring of roaming - one of:
- Barring of roaming outside the home PLMN;
- Barring of roaming outside the home PLMN country.
Barring of outgoing premium rate calls - one or both of:
- Barring of outgoing premium rate (information) calls;
- Barring of outgoing premium rate (entertainment) calls.
Barring specific to the home PLMN - when the mobile station is registered in its home PLMN, any one or more of:
- Operator Specific Barring (Type 1);
- Operator Specific Barring (Type 2);
- Operator Specific Barring (Type 3);
- Operator Specific Barring (Type 4).
Barring of Supplementary Services Management.
Barring of registration of call forwarding - one of:
- Barring of registration of any forwarded-to number;
- Barring of registration of any international forwarded-to number;
- Barring of registration of any international forwarded-to number except a number within the HPLMN country;
- Barring of registration of any inter-zonal forwarded-to number;
- Barring of registration of any inter-zonal forwarded-to number except a number within the HPLMN country.
Barring of invocation of call transfer:
one of:
- Barring of invocation of any call transfer;
- Barring of invocation of call transfer where at least one of the two calls is a call charged to the served subscriber;
- Barring of invocation of call transfer where at least one of the two calls is a call charged to the served subscriber at international rates, i.e. the call is either an outgoing international call or an incoming call when the served subscriber roams outside the HPLMN country;
- Barring of invocation of call transfer where at least one of the two calls is a call charged to the served subscriber at inter-zonal rates, i.e. the call is either an outgoing inter-zonal call or an incoming call when the served subscriber roams to a VPLMN in a different zone from the HPLMN;
and independently:
- Barring of invocation of call transfer where both calls are calls charged to the served subscriber;
and independently:
- Barring of invocation of call transfer when there is an existing transferred call for the served subscriber in the same MSC/VLR.
Barring of Packet Oriented Services - one of:
- Barring of all Packet Oriented Services;
- Barring of Packet Oriented Services from access points that are within the HPLMN whilst the subscriber is roaming in a VPLMN;
- Barring of Packet Oriented Services from access points that are within the roamed to VPLMN;
- Barring of access to all except some specific APNs.
3.1A Information stored in the UDM/UDR
Barring of roaming - one of:
- Barring of roaming outside the home PLMN;
- Barring of roaming outside the home PLMN country.
- Barring of Packet Oriented Services - one of:
- Barring of all Packet Oriented Services;
- Barring of Packet Oriented Services from access points that are within the HPLMN whilst the subscriber is roaming in a VPLMN;
- Barring of Packet Oriented Services from access points that are within the roamed to VPLMN;
- Barring of access to all except some specific DNNs, optionally with spatial and time validity conditions.
|
c5195074c429803154bc8b9cf2be11b9
|
23.015
|
3.2 Information stored in the VLR
|
The VLR must store subscription information for each mobile subscriber to define which of the following categories of barring is to be applied, independently of each other:
Barring of outgoing calls (including mobile originated short messages) - one of:
- Barring of all outgoing calls;
- Barring of all outgoing international calls;
- Barring of all outgoing international calls except those directed to the home PLMN country;
- Barring of all outgoing inter-zonal calls;
- Barring of all outgoing inter-zonal calls except those directed to the home PLMN country;
- Barring of all outgoing international calls except those directed to the home PLMN country AND barring of all outgoing inter-zonal calls.
Barring of outgoing premium rate calls - one or both of:
- Barring of outgoing premium rate (information) calls;
- Barring of outgoing premium rate (entertainment) calls.
Barring specific to the home PLMN - when the mobile station is registered in its home PLMN, any one or more of:
- Operator Specific Barring (Type 1);
- Operator Specific Barring (Type 2);
- Operator Specific Barring (Type 3);
- Operator Specific Barring (Type 4).
Barring of Supplementary Services Management.
Barring of invocation of call transfer:
one of:
- Barring of invocation of any call transfer;
- Barring of invocation of call transfer where at least one of the two calls is a call charged to the served subscriber;
- Barring of invocation of call transfer where at least one of the two calls is a call charged to the served subscriber at international rates, i.e. the call is either an outgoing international call or an incoming call when the served subscriber roams outside the HPLMN country;
- Barring of invocation of call transfer where at least one of the two calls is a call charged to the served subscriber at inter-zonal rates, i.e. the call is either an outgoing inter-zonal call or an incoming call when the served subscriber roams to a VPLMN in a different zone from the HPLMN.
and independently:
- Barring of invocation of call transfer where both calls are calls charged to the served subscriber;
and independently:
- Barring of invocation of call transfer when there is an existing transferred call for the served subscriber in the same MSC/VLR.
|
c5195074c429803154bc8b9cf2be11b9
|
23.015
|
3.3 Information stored in the SGSN
|
The SGSN shall store subscription information for each mobile subscriber to define which of the following categories of barring is to be applied, independently of each other:
Barring of mobile originated short messages - one of:
- Barring of all outgoing calls;
- Barring of all outgoing international calls;
- Barring of all outgoing international calls except those directed to the home PLMN country;
- Barring of all outgoing inter-zonal calls;
- Barring of all outgoing inter-zonal calls except those directed to the home PLMN country;
- Barring of all outgoing international calls except those directed to the home PLMN country AND barring of all outgoing inter-zonal calls.
Barring specific to the home PLMN of mobile originated short messages - when the mobile station is registered in its home PLMN, any one or more of:
- Operator Specific Barring (Type 1);
- Operator Specific Barring (Type 2);
- Operator Specific Barring (Type 3);
- Operator Specific Barring (Type 4).
Barring of Packet Oriented Services - one of:
- Barring of all Packet Oriented Services;
- Barring of Packet Oriented Services from access points that are within the HPLMN whilst the subscriber is roaming in a VPLMN;
- Barring of Packet Oriented Services from access points that are within the roamed to VPLMN.
3.3A Information stored in the MME
The MME shall store subscription information for each mobile subscriber to define which of the following categories of barring is to be applied, independently of each other:
Barring of mobile originated short messages - one of:
- Barring of all outgoing calls;
- Barring of all outgoing international calls;
- Barring of all outgoing international calls except those directed to the home PLMN country;
- Barring of all outgoing inter-zonal calls;
- Barring of all outgoing inter-zonal calls except those directed to the home PLMN country;
- Barring of all outgoing international calls except those directed to the home PLMN country AND barring of all outgoing inter-zonal calls.
Barring specific to the home PLMN of mobile originated short messages - when the mobile station is registered in its home PLMN, any one or more of:
- Operator Specific Barring (Type 1);
- Operator Specific Barring (Type 2);
- Operator Specific Barring (Type 3);
- Operator Specific Barring (Type 4).
Barring of Packet Oriented Services - one of:
- Barring of all Packet Oriented Services;
- Barring of Packet Oriented Services from access points that are within the HPLMN whilst the subscriber is roaming in a VPLMN;
- Barring of Packet Oriented Services from access points that are within the roamed to VPLMN.
|
c5195074c429803154bc8b9cf2be11b9
|
23.015
|
3.4 Transfer of Subscription Information from HLR to VLR
|
The following subscription information for Operator Determined Barring must be transferred from the HLR to the VLR when a mobile station registers in a VLR:
- Barring of outgoing calls;
- Barring of outgoing premium rate calls;
- Barring of supplementary services management;
- Barring of invocation of call transfer.
In addition, when a mobile station registers in a VLR in its home PLMN the subscription information for Operator Determined Barring specific to the home PLMN must be transferred from the HLR to the VLR.
|
c5195074c429803154bc8b9cf2be11b9
|
23.015
|
3.5 Transfer of Subscription Information from HLR to SGSN
|
The following subscription information for Operator Determined Barring shall be transferred from the HLR to the SGSN when a mobile station registers in a SGSN:
- Barring of outgoing calls (which leads to barring of mobile originated short messages).
The following subscription information for Operator Determined Barring for Packet Oriented Services shall be transferred from the HLR to the SGSN when a mobile station registers in a SGSN:
- Barring of all Packet Oriented Services;
- Barring of Packet Oriented Services from access points that are within the HPLMN whilst the subscriber is roaming in a VPLMN;
- Barring of Packet Oriented Services from access points that are within the roamed to VPLMN.
In addition, when a mobile station registers in a SGSN in its home PLMN the subscription information for Operator Determined Barring specific to the home PLMN shall be transferred from the HLR to the SGSN.
3.5A Transfer of Subscription Information from HSS to MME
The following subscription information for Operator Determined Barring shall be transferred from the HLR to the MME when a mobile station registers in a MME:
- Barring of outgoing calls (which leads to barring of mobile originated short messages).
The following subscription information for Operator Determined Barring for Packet Oriented Services shall be transferred from the HSS to the MME when a mobile station registers in a MME:
- Barring of all Packet Oriented Services;
- Barring of Packet Oriented Services from access points that are within the HPLMN whilst the subscriber is roaming in a VPLMN;
- Barring of Packet Oriented Services from access points that are within the roamed to VPLMN.
In addition, when a mobile station registers in an MME in its home PLMN the subscription information for Operator Determined Barring specific to the home PLMN shall be transferred from the HLR to the MME.
|
c5195074c429803154bc8b9cf2be11b9
|
23.015
|
3.6 I-WLAN Information stored in the HSS
|
The HSS shall store subscription information for each I-WLAN subscriber to define which of the following categories of barring is to be applied, independently of each other. These barring categories are applied to WLAN 3GPP IP Access:
- Barring of Interworking WLAN completely from the interworked service capabilities.
- Barring of a subscriber from requesting interworking through Packet Data Gateways that are within the HPLMN whilst the subscriber is WLAN connected via a VPLMN.
- Barring a subscriber from requesting packet-oriented services from Packet Data Gateways that are within the roamed to VPLMN.
- Barring of a subscriber from requesting direct Internet access from Packet Data Gateways that are within the I-WLAN.
|
c5195074c429803154bc8b9cf2be11b9
|
23.015
|
3.7 Transfer of User Profile Data from HSS to 3GPP AAA Server
|
The following User Profile Data for Operator Determined Barring must be transferred from the HSS to the 3GPP AAA Server when a WLAN-UE authenticates to 3GPP AAA Server and the I-WLAN service:
- Barring of Interworking WLAN completely from the interworked service capabilities
- Barring of a subscriber from requesting interworking through Packet Data Gateways that are within the HPLMN whilst the subscriber is WLAN connected via a VPLMN
- Barring a subscriber from requesting packet-oriented services from Packet Data Gateways that are within the roamed to VPLMN
- Barring of a subscriber from requesting direct Internet access from Packet Data Gateways that are within the I-WLAN
|
c5195074c429803154bc8b9cf2be11b9
|
23.015
|
3.8 Information stored in the AMF/SMF
|
Barring of Packet Oriented Services - one of:
- Barring of all Packet Oriented Services;
- Barring of Packet Oriented Services from access points that are within the HPLMN whilst the subscriber is roaming in a VPLMN;
- Barring of Packet Oriented Services from access points that are within the roamed to VPLMN.
|
c5195074c429803154bc8b9cf2be11b9
|
23.015
|
3.9 Transfer of Subscription Information from UDM to AMF/SMF
|
The following subscription information for Operator Determined Barring for Packet Oriented Services shall be transferred from the UDM to the AMF/SMF: - Barring of all Packet Oriented Services; - Barring of Packet Oriented Services from access points that are within the HPLMN whilst the subscriber is roaming in a VPLMN; - Barring of Packet Oriented Services from access points that are within the roamed to VPLMN. In addition, when a mobile station registers in an AMF in its home PLMN the subscription information for Operator Determined Barring specific to the home PLMN shall be transferred from the UDM to the AMF/SMF. Annex A (informative): Change history Change history Date Meeting TDoc CR Rev Cat Subject/Comment New version Apr 1999 Transferred to 3GPP CN1 CN#03 Approved at CN#03 3.0.0 CN#04 001 Corrections to text to introduce barring of SMS calls for GPRS 3.1.0 CN#11 Version updated from R99 to Rel-4 after CN#11 4.0.0 CN#11 002 Add PDP context activation barring scenario, etc 4.0.0 CN#15 References updated 4.0.1 CN#16 Release 5 after CN#16 5.0.0 CN#24 007r2 2 ODB handling for existing PDP contexts 6.0.0 CT#35 0008 1 Realization of Operator Determined Barring 7.0.0 CT#40 0009 1 ODB for 3GPP access in EPS 8.0.0 CT#42 Copyright Notification updated 8.0.1 CT#42 0011 1 Operator Determined Barring for EPS 8.1.0 CT#46 - Update to Rel-9 version (MCC) 9.0.0 CT#50 0012 2 LIPA for ODB case 10.0.0 CT#57 Update to Rel-11 version (MCC) 11.0.0 CT#58 0014 3 Addition of APN to the condition of the ODB judgment 11.1.0 CT#59 0015 1 Updating Default APN by HSS when Barring of access to all except some specific APNs applied 11.2.0 CT#59 0016 1 Barring of Access to All Except Some Specific APNs 11.2.0 CT#59 0017 ODB Not Applied to Emergency Bearer Services 11.2.0 CT#60 0018 1 SMS in MME 11.3.0 2014-09 - Update to Rel-12 version (MCC) 12.0.0 CT#68 0019 1 Correction to the I-WLAN reference 12.1.0 2015-12 - Update to Rel-13 version (MCC) 13.0.0 2017-03 - Update to Rel-14 version (MCC) 14.0.0 2018-06 - Update to Rel-15 version (MCC) 15.0.0 2018-12 CT#82 CP-183092 0020r3 3 F Introduction of Barring of Roaming in 5GC 15.1.0 2020-03 CT#87e CP-200045 0021 1 F Invocation of ODB 16.0.0 2021-03 CT#91e CP-210053 0022 1 F ODB handling in SMF 16.1.0 2022-03 - - - - - Update to Rel-17 version (MCC) 17.0.0 2023-12 CT#102 CP-233073 0025 - A Clean Up 17.1.0 2023-12 CT#102 CP-233071 0023 1 F Essential Correction for Barring of PDU Session in 5GS 17.1.0 2023-12 CT#102 CP-233044 0026 - F ODB clarification 18.0.0 2024-06 CT#104 CP-241050 0027 3 F AMF Determined PDU Session Establishment Rejection Due to ODB 18.1.0 2024-09 CT#105 CP-242033 0028 - B ODB Exempted DNNs 19.0.0
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
1 Scope
|
The present document describes the Cell Broadcast short message service (CBS) for GSM and UMTS.
For GSM it defines the primitives over the Cell Broadcast Centre - Base Station System (CBC-BSS) interface and the message formats over the Base Station System - Mobile Station (BSS-MS) interface for Teleservice 23 as specified in 3GPP TS 22.003 [2].
For UMTS it defines the interface requirements for the Cell Broadcast Centre – UMTS Radio Network System (RNS) interface and the radio interface requirements for UMTS Radio Acces Networks to support CBS as specified in 3GPP TS 22.003 [2].
The present document also describes the Public Warning System (PWS) for GSM, UMTS, E-UTRAN, satellite E-UTRAN, NG‑RAN, and satellite NG-RAN, see 3GPP TS 22.268 [28].
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
1.1 References
|
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] Void
[2] 3GPP TS 22.003: "Circuit Teleservices supported by a Public Land Mobile Network (PLMN)".
[3] 3GPP TS 23.038: "Alphabets and language‑specific information".
[4] 3GPP TS 23.040: "Technical realization of the Short Message Service (SMS)".
[5] Void.
[6] 3GPP TR 03.49 Version 7.0.0: "Digital cellular telecommunication system (Phase 2+); Example protocol stacks for interconnecting Cell Broadcast Centre (CBC) and Base Station Controler (BSC)".
[7] 3GPP TS 44.012: "Short Message Service Cell Broadcast (SMSCB) support on the mobile radio interface".
[8] 3GPP TS 45.002: "Multiplexing and multiple access on the radio path".
[9] Void.
[10] 3GPP TS 48.052: "Base Station Controller ‑ Base Transceiver Station (BSC - BTS) interface; Interface principles".
[11] 3GPP TS 48.058: "Base Station Controller ‑ Base Transceiver Station (BSC - BTS) interface; Layer 3 specification".
[12] ITU-T Recommendation X.210: "Information technology - Open systems interconnection - Basic Reference Model: Conventions for the definition of OSI services".
[13] 3GPP TS 48.008: "Mobile-services Switching Centre - Base Station System (MSC-BSS) interface; Layer 3 specification".
[14] 3GPP TS 23.042: "Compression algorithm for text messaging services".
[15] 3GPP TS 23.048: "Security Mechanisms for the SIM application toolkit".
[16] 3GPP TS 25.331: "Radio Resource Control (RRC); Protocol specification".
[17] 3GPP TS 25.401: "UTRAN Overall Description".
[18] 3GPP TS 31.102: "Characteristics of the USIM Application".
[19] 3GPP TS 25.324: "Broadcast/Multicast Control BMC".
[20] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[21] 3GPP TR 25.925: "Radio Interface for Broadcast/Multicast Services".
[22] Void.
[23] Void.
[24] Void.
[25] GSMA AD.26: "Coding of Cell Broadcast Functions".
[26] 3GPP TS 44.018: "Mobile radio interface layer 3 specification; Radio Resource Control Protocol".
[27] 3GPP TS 44.060: "General Packet Radio Service (GPRS); Mobile Station (MS) - Base Station System (BSS) interface; Radio Link Control / Medium Access Control (RLC/MAC) protocol".
[28] 3GPP TS 22.268: "Public Warning System (PWS) Requirements".
[29] 3GPP TS 25.419: "UTRAN Iu-BC Interface: Service Area Broadcast Protocol (SABP)".
[30] 3GPP TS 48.049: "Base Station Controller - Cell Broadcast Centre (BSC-CBC) Interface Specification; Cell Broadcast Service Protocol (CBSP)".
[31] Void.
[32] ETSI TS 102 900: "European Public Warning System (EU-ALERT) using the Cell Broadcast Service".
[33] IETF RFC 4960: "Stream Control Transmission Protocol".
[34] 3GPP TS 36.413: "Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP)".
[35] 3GPP TS 29.168: "Cell Broadcast Centre interfaces with the Evolved Packet Core".
[36] 3GPP TS 36.331: "Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification".
[37] Void.
[38] 3GPP TS 23.007: "Restoration Procedures".
[39] 3GPP TS 23.501: "System Architecture for the 5G System; Stage 2".
[40] 3GPP TS 38.413: "NG Radio Access Network (NG-RAN); NG Application Protocol (NGAP)".
[41] 3GPP TS 29.518: "5G System; Access and Mobility Management Services; Stage 3".
[42] IETF RFC 9113: "HTTP/2".
[43] 3GPP TS 23.502: "Procedures for the 5G System; Stage 2".
[44] 3GPP TS 38.300: "NR; NR and NG-RAN Overall Description; Stage 2".
[45] 3GPP TS 23.527: "5G System; Restoration Procedures; Stage 2".
[46] 3GPP TS 36.300: "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access (E-UTRAN); Overall description; Stage 2".
[47] ATIS-0700041: "WEA 3.0: Device-Based Geo-Fencing".
[48] 3GPP TS 38.331: "NR; Radio Resource Control (RRC) protocol specification".
[49] 3GPP TS 23.122: "Non-Access-Stratum functions related to Mobile Station (MS) in idle mode".
[50] 3GPP TS 23.251: "Network Sharing; Architecture and functional description".
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
1.2 Abbreviations
|
For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [20] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [20].
5GS 5G System
5GCN 5G Core Network
EPC Evolved Packet Core
ePWS enhancements of Public Warning System
NR New Radio
SNPN Stand-alone Non-Public Network
WEA Wireless Emergency Alert
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
1.3 Definitions
|
For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1].
For the purposes of the present document, the following terms and definitions given in 3GPP TS 23.501 [39] apply:
5G System
NG-RAN
For the purposes of the present document, the following terms and definitions given in 3GPP TS 38.300 [44] apply:
gNB
NG-RAN node
ng-eNB
For the purposes of the present document, the following terms and definitions given in 3GPP TS 23.122 [39] apply:
Subscribed SNPN
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
2 General description
|
The CBS service is analogous to the Teletex service offered on television, in that like Teletex, it permits a number of unacknowledged general CBS messages to be broadcast to all receivers within a particular region. CBS messages are broadcast to defined geographical areas known as cell broadcast areas. These areas may comprise of one or more cells, or may comprise the entire PLMN or SNPN. Individual CBS messages will be assigned their own geographical coverage areas by mutual agreement between the information provider and the PLMN or SNPN operator. CBS messages may originate from a number of Cell Broadcast Entities (CBEs), which are connected to the Cell Broadcast Centre. CBS messages are then sent from the CBC to the cells, in accordance with the CBS's coverage requirements.
A CBS page comprises of 82 octets, which, using the default character set, equates to 93 characters. Other Data Coding Schemes may also be used, as described in 3GPP TS 23.038 [3]. Up to 15 of these pages may be concatenated to form a CBS messagee. Each page of such CBS message will have the same message identifier (indicating the source of the message), and the same serial number. Using this information, the MS/UE is able to identify and ignore re‑broadcasts of already received messages.
CBS messages are broadcast cyclically by the cell at a frequency and for a duration agreed with the information provider. The frequency at which CBS messages are repeatedly transmitted will be dependent on the information that they contain; for example, it is likely that dynamic information such as road traffic information, will require more frequent transmission than weather information. The repetition period will also be affected by the desire for CBS messages to be received by high speed mobiles which rapidly traverse cells. Reception of CBS messages for an MS/UE is not a requirement if it is connected in the CS domain. It should be possible for an MS/UE to receive messages if it is connected in the PS domain and no data is currently transmitted.
CS-Domain
CS-Connected
CS-Idle
CS-Idle
PS-Domain
-
PS-Idle
PS-Connected
Reception of CBS Message
Not possible
Possible
Depends on RRC mode
NOTE: In case the UE is in CS-Idle and PS-Connected Mode it depends on the Radio Resource Control State whether reception of CBS messages is possible. The relevant states are described in 3GPP TS 25.331 [16].
GSM only [CBS messages may be broadcast on two different cell broadcast channels, which are characterized by different QoS. A MS is always able to read the basic channel (see 3GPP TS 45.002 [8]). The reading of the extended channel may collide with other tasks of the MS. Therefore the probability of receiving a CBS message on the extended channel is smaller than on the basic channel. The reading of the extended channel for MSs is optional. The scheduling on the channels will be done independently].
To permit mobiles to selectively display only those CBS messages required by the MS/UE user, CBS messages are assigned a message class which categorises the type of information that they contain and the language (Data Coding Scheme) in which the CBS message has been compiled. Through the use of appropriate MMI, the user is then able to ignore message types that he does not wish to receive, e.g. advertising information or messages in an unfamiliar language.
A network may be able to remotely activate mobile terminals in order to enable them to receive CBS messages, according to regulatory requirements (see 3GPP TS 25.331 [16]).
PWS provides a service that allows the network to distribute warning messages on behalf of public authority. PWS enables the distribution of ETWS, CMAS (aka WEA), KPAS and EU-Alert warning messages in GSM, UMTS, E-UTRAN, and NG‑RAN.
Some of the PWS warning message distribution mechanisms are access technology specific, but some CBS procedures and related message structures are common for GSM and UMTS, and some CBS procedures and related message structures are common for E-UTRAN and NG‑RAN.
The language-independent content mapped to an event or a disaster can be included in a warning message that is transparently passed from CBC to UEs. UEs with user interface which support the ePWS language-independent content functionality can display the entire warning message that they receive.
UEs with no user interface which support the ePWS disaster characteristics functionality can derive the characteristics of a disaster from the message identifier of a received warning message.
Requirements applicable for E-UTRAN are also applicable for satellite E-UTRAN, unless otherwise specified.
Requirements applicable for NG-RAN are also applicable for satellite NG-RAN, unless otherwise specified.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
3 Network Architecture
| |
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
3.0 General
|
The chosen network architectures differ for GSM, UMTS, EPS, and 5GS. In clause 3.1 the GSM network architecture is descripted, in clause 3.2 the UMTS network architecture, in clause 3.3 the EPS network architecture, and in clause 3.4 the 5GS network architecture.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
3.1 GSM Network Architecture
|
The basic network structure of CBS is depicted by figure 1.
Figure 1
- message transfer on link 1 is outside the scope of 3GPP specifications;
- message transfer on link 2 is described in clause 9.1;
- message transfer on link 3 is described in 3GPP TS 48.058 [11];
- message transfer on link 4 is described in 3GPP TS 44.012 [7] and the timing of messages transferred on link 4 is described in 3GPP TS 45.002 [8].
3GPP TS 23.251 [50] specifies additional requirements for providing CBS in shared GERAN.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
3.2 UMTS Network Architecture
|
The basic network structure of CBS is depicted by figure 2.
Figure 2
The basic network structure replaces the GSM BSS with the UTRAN containing the RNC and the Node B. The cell broadcast centre (CBC) is part of the core network and connected to a routing node e.g. a 3G SGSN via the Bc reference point. Thus the CBC can reach every RNC via the user plane of the Iu interface. On the logical interface between the CBC and the RNC protocol is described in 3GPP TS 25.419 [29]. The other UTRAN related interfaces are described in the according UTRAN specifications based on the 3GPP TR 25.925 [21]. Based on this architecture and the current requirements for cell broadcast the core network elements like MSC, VLR, HLR etc are not involved for the service delivery.
The CBE and the interface between CBE and CBC are out of scope of 3GPP specifications.
3GPP TS 23.251 [50] specifies additional requirements for providing CBS in shared UTRAN.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
3.3 EPS Network Architecture
|
The basic network structure of PWS architecture in E-UTRAN is depicted by figure 3.3-1.
Figure 3.3-1: PWS architecture
The cell broadcast centre (CBC) is part of the core network and connected to the MME via the SBc reference point. The interface between the CBC and the MME is described in 3GPP TS 29.168 [35] and the interface between the MME and the eNodeB is described in 3GPP TS 36.413 [34].
The CBE and the interface between CBE and CBC are out of scope of 3GPP specifications.
3GPP TS 23.251 [50] specifies additional requirements for providing PWS in shared E-UTRAN.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
3.4 5GS Network Architecture
|
Figures 3.4-1, 3.4.-2 and 3.4-3 depict the basic network structure of 5GS PWS architecture.
Figure 3.4-1 depicts the 5GS PWS system architecture, using service-based interfaces between CBCF and AMF, showing how the network functions interact with each other. This option is further described in clauses 4 to 8. The service-based interfaces are further described in clause 9A.
Figure 3.4-1: 5GS PWS architecture
NOTE: No services are provided by CBCF or PWS-IWF, thus no service-based interfaces are depicted for these NFs in the 5GS PWS architecture.
Figure 3.4-2 depicts the basic network structure of 5GS PWS architecture using the reference point representation showing how the network functions interact with each other when no PWS-IWF is used. This option is further described in clauses 4 to 8.
Figure 3.4-2: 5GS PWS architecture in reference point representation without PWS-IWF
Figure 3.4-3 depicts the basic network structure of 5GS PWS architecture using the reference point representation showing how the network functions interact with each other when PWS-IWF is used. This option is further described in Annex B.
Figure 3.4-3: 5GS PWS architecture in reference point representation with PWS-IWF
The 5GS PWS architecture contains the following service-based interface:
Namf: Service-based interface exhibited by AMF.
The 5GS PWS architecture contains the following reference points:
N2: Reference point between the NG-RAN and the AMF.
NOTE 1: NG-RAN can be NR based or E-UTRA based (See 3GPP TS 23.501 [39] , 3GPP TS 38.413 [40] and 3GPP TS 36.413 [34]).
N50: Reference point between the AMF and the CBCF or between the AMF and the PWS-IWF.
NOTE 2: N50 uses service-based interfaces, further described in clause 9A of the present document.
SBc: Reference point between the PWS-IWF and the CBC.
The CBE and the interface between CBE and CBC are out of scope of 3GPP specifications.
In shared NG-RAN, PWS is provided via a single common CBCF which connects to the shared NG-RAN via one or more AMFs, or via a single common CBC which connects to the shared NG-RAN via one or more AMFs and one or more PWS-IWFs. The deployment and configuration of the common CBCF or the common CBC is per agreement between the sharing operators. The sharing operators need to coordinate PWS between each other.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
4 CBE Functionality
|
The functionality of the CBE is outside of the scope of 3GPP specifications; however it is assumed that the CBE is responsible for all aspects of formatting CBS messages, including the splitting of a CBS message into a number of pages.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
5 CBC Functionality
|
In 3GPP the CBC is integrated as a node in the core network.
The CBC may be connected to several BSCs/RNCs/MMEs/PWS-IWFs. The CBC may be connected to several CBEs. The CBC shall be responsible for the management of CBS messages including:
- allocation of serial numbers;
- modifying or deleting CBS messages held by the BSC/RNC/eNodeB/NG-RAN node;
- initiating broadcast by sending fixed length CBS messages to a BSC/RNC/eNodeB/NG-RAN node for each language provided by the cell, and where necessary padding the pages to a length of 82 octets (see 3GPP TS 23.038 [3]);
- determining the set of cells to which a CBS message should be broadcast, and indicating within the Serial Number the geographical scope of each CBS message;
- determining the time at which a CBS message should commence being broadcast;
- determining the time at which a CBS message should cease being broadcast and subsequently instructing each BSC/RNC/eNodeB/NG-RAN node to cease broadcast of the CBS message;
- determining the period at which broadcast of the CBS message should be repeated;
- determining the cell broadcast channel in GSM, on which the CBS message should be broadcast.
- when CBS transmits emergency messages, allocation of "emergency indication" to differentiate it from normal CBS messages, including the "Cell ID/Service Area ID list", "warning type", "warning message". If "warning type" is of 'test', only UEs which are specially designed for testing purposes may display warning message.
To work efficiently on the interfaces, the BSC/RNC - which is normally controlling more than one cell of a broadcast area - should be used as a concentrator as far as CBS message handling is concerned. Hence, the CBC should work on lists of cells when issuing CB related requests towards the BSC/RNC.
5A CBCF Functionality
In 3GPP the CBCF is a network function in the 5G core network.
The CBCF may be connected to several AMFs. The CBCF may be connected to several CBEs. The CBCF shall be responsible for the management of CBS messages including:
- allocation of serial numbers;
- modifying or deleting CBS messages held by the NG-RAN node;
- initiating broadcast by sending fixed length CBS messages to a NG-RAN node for each language provided by the cell, and where necessary padding the pages to a length of 82 octets (see 3GPP TS 23.038 [3]);
- determining the set of cells to which a CBS message should be broadcast, and indicating within the Serial Number the geographical scope of each CBS message;
- determining the time at which a CBS message should commence being broadcast;
- determining the time at which a CBS message should cease being broadcast and subsequently instructing each NG-RAN node to cease broadcast of the CBS message;
- determining the period at which broadcast of the CBS message should be repeated;
- when CBS transmits emergency messages, allocation of "emergency indication" to differentiate it from normal CBS messages, including the "Cell ID/Service Area ID list", "warning type", "warning message". If "warning type" is of 'test', only UEs which are specially designed for testing purposes may display warning message.
The CBCF supports service based interface. The CBCF uses AMF communication services to forward warning messages to the NG-RAN and to subscribe to receive warning delivery related notifications.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
6 BSC/RNC/MME/AMF Functionality
|
The BSC/RNC shall interface to only one CBC. A BSC may interface to several BTSs as indicated by 3GPP TS 48.052 [10]. An RNC may interface to several Node Bs.
The MME may interface to one CBC or multiple CBCs (i.e. the MME is allowed to have SCTP transport associations established with one or multiple CBCs). An MME may interface to several eNodeBs.
The AMF may interface to one CBCF or multiple CBCFs (i.e. the AMF is allowed to have HTTP/2 application layer associations with one or multiple CBCFs). An AMF may interface to several NG-RAN nodes.
The BSC/RNC/MME/AMF shall be responsible for:
BSC
RNC
MME
AMF
Interpretation of commands from the CBC.
Storage of messages from the CBC.
Not applicable
Scheduling of CBS messages on the CBCH.
Scheduling of CBS messages on the CBS related radio resources.
Not applicable
Not applicable
Providing an indication to the CBC when the desired repetition period cannot be achieved.
Not applicable
Providing to the CBC acknowledgement of successful execution/forwarding of commands received from the CBC.
Reporting to the CBC failure when a command received from the CBC is not understood or cannot be executed.
Not applicable.
Not applicable.
Report the Broadcast Completed Area List, the Broadcast Cancelled Area List, PWS Restart Indication and the PWS Failure Indication received from eNB(s) to all CBCs that the MME interfaces with.
Report the Broadcast Completed Area List, the Broadcast Cancelled Area List, PWS Restart Indication and the PWS Failure Indication received from NG-RAN nodes to all CBCFs and PWS-IWFs that the AMF interfaces with.
Routing of CBS messages to the appropriate BTSs.
Routing of CBS messages to the appropriate Node Bs.
Routing of warning messages to the appropriate eNodeBs in the indicated Tracking Area.
Routing of warning messages to the appropriate NG-RAN nodes in the indicated Tracking Area.
Transferring CBS information to each appropriate BTS via a sequence of 4 SMS BROADCAST REQUEST messages or 1 SMS BROADCAST COMMAND message (see 3GPP TS 48.058 [11]), indicating the channel which shall be used.
The Node B has no functionality regarding CBS. This implies that CBS messages do not have to be transmitted explicitly to the Node Bs for further processing.
Not applicable.
Not applicable.
Optionally generating Schedule Messages, indicating the intended schedule of transmissions (see 3GPP TS 44.012 [7]).
Generating Schedule Messages, indicating the intended schedule of transmissions (see 3GPP TS 25.324 [19]). The conversion of GSM related CB DRX Information is a function of the RNC (3GPP TS 25.401 [17]).
Not applicable.
Not applicable.
Optionally receiving CBCH Load Indication messages and reacting by broadcasting a burst of scheduled CBS messages or by suspending the broadcast for a period indicated by BTS (see 3GPP TS 48.058 [11]).
Not applicable.
Not applicable.
Not applicable.
Broadcasting the ETWS Primary Notification message upon receipt of the WRITE-REPLACE message including the Paging-ETWS-Indicator. The ETWS Primary Notification message is broadcasted according to the Warning Period parameter.
Sending ETWS messages to mobile terminals upon receiving CBS transmission request from CBC including the Paging-ETWS-Indicator. Emergency indication can be included in the paging messages, based on the warning type information conveyed from CBC.
Sending the Write-Replace Warning Request message to the appropriate eNodeBs upon receiving warning message transmission request from CBC.
Sending the Write-Replace Warning Request message to the appropriate NG-RAN nodes upon receiving warning message transmission request from CBCF or PWS-IWFs.
To work efficiently on the interfaces, the BSC/RNC should forward CB related messages to the CBC using cell lists as far as applicable.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
7 BTS Functionality
|
Only GSM [The BTS is responsible for conveying CBS information received via SMS BROADCAST REQUEST or SMS BROADCAST COMMAND messages over the radio path to the MS.
- optionally generating CBCH Load Indication messages, indicating an underflow or overflow situation on the CBCH (see 3GPP TS 48.058 [11]).]
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
8 MS/UE Functionality
| |
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
8.1 General MS/UE Functionality
|
Only GSM [The MS is responsible for recombination of the blocks received via the radio path to reconstitute the CBS message.]
The precise method of display of CBS messages is outside the scope of 3GPP specifications, however it is assumed that an MS/UE will:
MS
UE
Discard sequences transferred via the radio path (see 3GPP TS 44.012 [7]) which do not consist of consecutive blocks.
Discard corrupt CBS messages received on the radio interface.
Have the ability to discard CBS information which is not in a suitable data coding scheme.
Have the ability to discard a CBS message which has a message identifier indicating that it is of subject matter which is not of interest to the MS/UE.
Have the ability to detect duplicate messages as specified in clause 8.2;
Have the ability to transfer a CBS message to an external device, when supported ;
Optionally enter CBS DRX mode based upon received Schedule Messages (see 3GPP TS 44.012 [7]);
Enter CBS DRX mode based upon received Schedule Messages (see 3GPP TS 25.324 [19]).
Optionally skip reception of the remaining block(s) of a CBS message which do(es) not contain cell broadcast information (see 3GPP TS 44.012 [7]);
Not applicable.
Optionally read the extended channel.
Not applicable for UMTS, E-UTRAN, and NG-RAN.
Enable the user to activate/deactivate CBS through MMI
Enable the user to maintain a "search list" and receive CBS messages with a Message Identifier in the list while discarding CBS messages with a Message Identifier not in the list.
Discard CBS messages in Message Identifier value range "A000hex-AFFFhex" unless received from HPLMN, EHPLMN, PLMN that is equivalent to HPLMN or EHPLMN, the subscribed SNPN, or an SNPN equivalent to the subscribed SNPN.
Allow the user to enter the Message Identifier via MMI only for the 1 000 lowest codes.
Be capable of receiving CBS messages consisting of up to 15 pages.
Be capable of receiving CBS messages consisting of up to 1230 octets in UTRAN or warning messages of up to 9600 octets in E-UTRAN, or NG-RAN.
When emergency indication is included in the received paging and/or CBS/warning message, behave as specified in 3GPP TS 22.268 [28].
If the emergency indication includes the value for "test", mobile terminals which are not used for testing purpose silently discard the paging message and do not receive the corresponding CBS/warning message.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
8.2 Duplication Detection Function
|
The MS/UE uses a common duplication detection function for all messages received in GSM, UMTS, E-UTRAN and NG-RAN.
In a PLMN or SNPN, upon reception of a new message, the MS/UE shall perform duplication detection on the messages. Those messages that are received from the same PLMN or SNPN, in the certain time period specified by the duplication detection time are subject to duplication detection. The MS/UE shall not perform duplication detection on messages whose duplication detection time has elapsed. The value of the duplication detection time to be used by the MS/UE shall be derived from the MCC of the current PLMN or SNPN as follows:
- If the message was received from a PLMN and the MCC of the PLMN = 440 or = 441 (Japan), duplication detection time shall be 1 hour;
- For all other cases, duplication detection time shall be 24 hours.
If the messages are received from the same PLMN or SNPN, then:
1) the MS/UE shall check whether the Serial Number associated with the Message Identifier of the new message matches the Serial Number of any of those messages with the same Message Identifier that have been received and displayed to the user and that are subject to the duplication detection; and
2) the MS/UE may check other criteria for detecting duplicates. An example of such a criterion is whether the actual contents of the two messages are the same.
NOTE 1: Criterion 2 allows the UE to present more than 1024 different messages received within the duplication detection time period and will prevent those messages with the same Serial Number but with different message content to be rejected as duplicates.
If criterion 1 is fulfilled and any implemented additional checks (as described in criterion 2) are also met, then the MS/UE shall consider the new message as duplicated and shall ignore it. If the Geographical Scope is not PLMN/SNPN wide the validity of the Serial Number may be considered as described in clause 9.4.1.2.1.
If the messages are received from different PLMNs or SNPNs, then (as described in clause 9.4.1.2.1) "the CBS message is only relevant to the PLMN or SNPN in which it is broadcast, so any change of PLMN (including a change to another PLMN which is an ePLMN) or SNPN means the CBS message is "new"". Therefore, the MS/UE is not required to conduct duplication detection on messages received from different PLMNs/SNPNs.
NOTE 2: A duplicate message can only be received once by the user in a PLMN/SNPN during a duplication detection time. When the UE is in a different PLMN /SNPN then receiving a duplicate message once by the user, that was received earlier in a different PLMN/SNPN, can be tolerated.
For ETWS, duplicate message detection shall be performed independently for primary and secondary notifications.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
8.3 ePWS functionality
|
The ePWS functionality consists of the ePWS language-independent content functionality and the ePWS disaster characteristics functionality as follows:
1) UEs with user interface which support the ePWS language-independent content functionality and which are capable of displaying text-based warning messages should be capable of displaying the language-independent content mapped to an event or a disaster (e.g. character such as Unicode based pictogram mapping to a disaster) that is part of user information contained in the content of a warning message transparently passed from CBC to UEs.
NOTE 1: Language-independent contents mapped to disasters need to be formatted to be suitable to be included in a warning message. It could be unicode symbol or symbol based on GSM 7 bit default alphabet. It is desirable that standardised symbols mapped to disasters are applied in all countries that provide warning messages for public safety. This will make it possible for foreigners to intuitively understand the meaning of language-independent contents displayed to their devices.
Editor's note [WI: ePWS, CR#202]: FFS on what character(s) such as Unicode based pictogram(s) are the language-independent content mapped to an event or a disaster.
2) UEs with user interface which support the ePWS language-independent content functionality and which are incapable of displaying text-based warning messages should be capable of mapping message identifiers of received warning messages to language-independent contents stored in those UEs. When a warning message is received, such a UE should be capable of displaying of a language-independent content stored in the UE mapped from the message identifier of the received warning message.
NOTE 2: This ePWS functionality is not applied for such UEs if they are not capable of storing any language-independent content.
3) UEs with no user interface which support the ePWS disaster characteristics functionality should be capable of identifying the characteristics of a disaster derived from the message identifier of a received warning message in order to take appropriate action.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9 Protocols and Protocol Architecture
| |
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.1 Requirements on Core Network and Radio Access Network
| |
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.1.1 GSM Radio Access Network
|
Commands interpreted by the BSC will result in a sequence of 4 SMS BROADCAST REQUEST messages or 1 SMS BROADCAST COMMAND message being sent to a BTS, which in turn result in a sequence of 4 blocks each 22 octets long being transferred via the BTS-MS interface (see 3GPP TS 44.012 [7]).
With the SMS BROADCAST REQUEST mode of operation, the 88 octet fixed length CBS page which is specified in clause 9.3 is split into four 22 octet blocks which are carried in SMS BROADCAST REQUEST messages as follows:
octets 1‑22 are transferred in the 1st SMS BROADCAST REQUEST
with a sequence number (see 3GPP TS 44.012 [7]) indicating first block;
octets 23‑44 are transferred in the 2nd SMS BROADCAST REQUEST
with a sequence number (see 3GPP TS 44.012 [7]) indicating second block;
octets 45‑66 are transferred in the 3rd SMS BROADCAST REQUEST
with a sequence number (see 3GPP TS 44.012 [7]) indicating third block;
octets 67‑88 are transferred in the 4th SMS BROADCAST REQUEST
with a sequence number (see 3GPP TS 44.012 [7]) indicating fourth block.
Figure 3 illustrates the protocol architecture and the scope of the various GSM Specifications for the SMS BROADCAST REQUEST mode of operation.
Figure 3
With the SMS BROADCAST COMMAND mode of operation, the BSC sends to the BTS in one single message the 88 octet fixed length CBS page. The BTS then splits the page into four 22 octet blocks, adds the sequence number (see 3GPP TS 44.012 [7]) and transmits the four resulting blocks on the air.
Figure 4 illustrates the protocol architecture and the scope of the various GSM Specifications for the SMS BROADCAST COMMAND mode of operation.
Figure 4
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.1.2 UMTS Radio Access Network
|
Commands interpreted by the RNC will result in one SMS BROADCAST COMMAND sent to the UE. The CBS messages are completely transparent to the Node B, i.e. no manipulation of the data like e.g. fragmentation is done at the Node B.
Figure 4a
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.1.3 Warning Message Delivery
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.