13 Information Storage
23.4023GPPArchitecture enhancements for non-3GPP accessesRelease 18TS
13.0 General
This clause describes the additional information stored in different nodes while the UE is in non-3GPP access.
The information provided in clauses 13.1, 13.2 and 13.3 is incomplete in this Release of the specification and intended only for information. Detailed information is available in corresponding stage 3 specifications.
13.1 HSS
The data held in the HSS when non 3GPP accesses are not used is defined in TS 23.401 [4].
The additional data held in the HSS when non 3GPP accesses are used is defined in table 13.1-1 below.
Table 13.1-1: HSS EPS Data (additional aspects for non 3GPP accesses)
|
Field |
Description |
|---|---|
|
3GPP AAA Server name |
The Identity of the 3GPP AAA Server serving the UE currently. |
|
QoS profile per access |
The quality of service profile subscribed for a particular access for a specific APN |
|
ODB |
Indicates that the status of the operator determined barring for a specific access. |
|
Access Restriction |
Indicates the access restriction subscription information. |
13.2 MME
Information storage for the MME is described in TS 23.401 [4]. The additional data held in the MME when optimized interworking with CDMA2000 HRPD is used is defined in table 13.2‑1 below.
Table 13.2-1: MME storage requirements to support optimized interworking with CDMA2000 HRPD
|
Field |
Description |
|
S101 HRPD access node IP address |
The IP address of the HRPD AN used for the S101 tunnel for a UE. This is stored on a per UE basis. |
|
S103 Forwarding Address |
HS GW IP address used for data forwarding to the HRPD access over S103 interface. This is stored on a per UE basis. |
|
S103 GRE key(s) |
GRE Key(s) used for the data forwarding tunnel to the HS GW – one per PDN connection. This is stored on a per PDN connection basis. |
13.3 S‑GW
Information storage for the S‑GW is described in TS 23.401 [4]. The additional data held in the S‑GW when optimized interworking with CDMA2000 HRPD is used is defined in table 13.3‑1 below.
Table 13.3-1: S‑GW storage requirements to support optimized interworking with CDMA2000 HRPD
|
Field |
Description |
|
S103 Forwarding Address |
HS‑GW IP address used for data forwarding to the HRPD access over S103 interface. This is stored on a per UE basis. |
|
S103 GRE key(s) |
GRE Key(s) used for the data forwarding tunnel to the HS‑GW – one per PDN connection. This is stored on a per PDN connection basis. |
13.4 Handling of Wild Card APN
When the wild card APN is present in the subscription context, the UE is authorized to connect to APNs which are not present in the subscription context.
When a request is received for registering a PDN GW ID for such an active APN which is not present in the subscription context, the nodes (HSS/MME/ S4 SGSN/AAA Server/Non-3GPP access) shall store the PDN GW ID and the APN for the UE.
When a request is received for deregistering of PDN GW ID, for such an active APN which is not present in the subscription context, the nodes (HSS/MME/ S4 SGSN/AAA Server/Non-3GPP access) shall delete the PDN GW ID and the APN for the UE.
13.5 ePDG
Information storage for the ePDG required for emergency services is defined in table 13.5-1 below.
The ePDG Emergency Configuration Data is used instead of UE subscription data received from the HSS, for all emergency bearer services that are established by an ePDG on UE request.
Table 13.5-1: ePDG Emergency Configuration Data
|
Field |
Description |
|---|---|
|
Emergency Access Point Name (em APN) |
A label according to DNS naming conventions describing the access point used for Emergency PDN connection (wild card not allowed). |
|
Emergency QoS profile |
The bearer level QoS parameter values for Emergency APN’s default bearer (QCI and ARP). The ARP is an ARP value reserved for emergency bearers. |
|
Emergency APN-AMBR |
The Maximum Aggregated uplink and downlink MBR values to be shared across all Non-GBR bearers, which are established for the Emergency APN, as decided by the PDN GW. |
|
Emergency PDN GW identity |
The statically configured identity of the PDN GW used for emergency APN. The PDN GW identity may be either an FQDN or an IP address. |
|
Emergency fallback PDN GW identity |
Optional. The statically configured identity of the fallback PDN GW used for emergency APN. The fallback PDN GW identity may be either an FQDN or an IP address. |
NOTE: QCI for Emergency APN’s default bearer is set per operator configuration.
13.6 TWAN
Information storage for the TWAN required for emergency services is defined in table 13.6-1 below.
The TWAN Emergency Configuration Data is used instead of UE subscription data received from the HSS, for all emergency bearer services that are established by an TWAN on UE request.
Table 13.6-1: TWAN Emergency Configuration Data
|
Field |
Description |
|---|---|
|
Emergency Access Point Name (em APN) |
A label according to DNS naming conventions describing the access point used for Emergency PDN connection (wild card not allowed). |
|
Emergency QoS profile |
The bearer level QoS parameter values for Emergency APN’s default bearer (QCI and ARP). The ARP is an ARP value reserved for emergency bearers. |
|
Emergency APN-AMBR |
The Maximum Aggregated uplink and downlink MBR values to be shared across all Non-GBR bearers, which are established for the Emergency APN, as decided by the PDN GW. |
|
Emergency PDN GW identity |
The statically configured identity of the PDN GW used for emergency APN. The PDN GW identity may be either an FQDN or an IP address. |
|
Emergency fallback PDN GW identity |
Optional. The statically configured identity of the fallback PDN GW used for emergency APN. The fallback PDN GW identity may be either an FQDN or an IP address. |
NOTE: QCI for Emergency APN’s default bearer is set per operator configuration.