Content for TS 23.501 Word version: 19.3.0

1… 3… 4.2.3 4.2.4 4.2.5… 4.2.8… 4.2.8.2.2 4.2.8.2.3… 4.2.8.4… 4.2.9… 4.2.15… 4.3… 4.3.3 4.3.4 4.3.5 4.4… 4.4.6… 4.4.8… 5… 5.3… 5.3.3… 5.4… 5.5… 5.6… 5.6.7… 5.7… 5.7.2… 5.7.3… 5.7.4 5.7.5… 5.8… 5.8.2.11… 5.9… 5.10… 5.11… 5.15… 5.15.11… 5.16… 5.17… 5.18… 5.19… 5.21… 5.22… 5.27… 5.28… 5.29… 5.30… 5.31… 5.32… 5.32.6… 5.33… 5.34… 5.35… 5.38… 5.43… 5.49… 6… 6.3… 6.3.8… 7… 7.2… 8… 8.2.4 8.2.5… 8.3… A… D… E… F G… G.3 G.4… H… J K… M… N… O… P… S… T…

T.1 General T.2 Calculation of Energy Consumption parameters U.1 General U.2 PDU Session establishment for supporting traffic offloading at the H-UPF U.3 Re-establishment of PDU Session due to UP Path failure V.0 General V.1 NR Femto Deployment Options

T Network Energy consumption information calculation |R19| p. 735

T.1 General p. 735

This Annex provides examples on how EIF calculate the energy consumption for required granularities.

T.2 Calculation of Energy Consumption parameters p. 735

The energy consumed at a UPF (E_UPF ) or a gNB (E_gNB ) is known over a time interval T. And the EIF is aware of the data volume (DV ) consumed at a UPF by a UE (DV_UE,UPF ), UE S-NSSAI (DV_S-NSSAI,UPF ), UE PDU session (DV_Session,UPF ) and UE QoS flow (DV_Flow,UPF ) over the time interval T. The EIF is aware of the overall data volume at a gNB (DV_gNB ), as well as at a UPF (DV_UPF ) which serving the UE. Then based on the below example formulas, the required granularities Energy consumption information can be obtained.

To derive the of energy consumed at a gNB over a time interval T by a UE, S-NSSAI, PDU session, QoS flow, the formulas are:

Energy consumed at a gNB, second formula

Energy consumed at a gNB, fourth formula

To derive the energy consumed at a UPF over a time interval T by a UE, S-NSSAI, PDU session, QoS flow the formulas are:

Energy consumed at a UPF, second formula

Energy consumed at a UPF, fourth formula

It should be noted that the values E_gNB / DV_gNB and E_UPF / DV_UPF are coefficients that are common across all granularities, within the time interval T, for the respective network entities and are values that related to the energy consumption per bit of the gNB, and, respectively, the UPF.

To derive the energy consumed in the network in the time interval T by a UE (E_UE ), S-NSSAI (E_S-NSSAI ), PDU Session (E_Session ), QoS flow (E_Flow ), the formula is:

E_UE = ∑_{gNB_i∈gNB^T_UE} E_{UE,gNB_i} + ∑_{UPF_i ∈ UPF^T_UE} E_{UE.UPF_i}

where gNB^T_UE are all gNBs used by the UE in an interval T, UPF^T_UE are all UPFs used by the UE in an interval T.

E_S-NSSAI = ∑_{gNB_i∈gNB^T_S-NSSAI} E_{S-NSSAI,gNB_i} + ∑_{UPF_i ∈ UPF^T_S-NSSAI} E_{S-NSSAI.UPF_i}

where gNB^T_S-NSSAI are all gNBs used by the S-NSSAI in an interval T, UPF^T_S-NSSAI are all UPFs used by the S-NSSAI in an interval T.

E_Session = ∑_{gNB_i∈gNB^T_Session} E_{Session,gNB_i} + ∑_{UPF_i ∈ UPF^T_Session} E_{Session.UPF_i}

where gNB^T_Session are all gNBs used by the PDU Session in an interval T, UPF^T_Session are all UPFs used by the PDU Session in an interval T.

E_Flow = ∑_{gNB_i∈gNB^T_Flow} E_{Flow,gNB_i} + ∑_{UPF_i ∈ UPF^T_Flow} E_{Flow.UPF_i}

where gNB^T_Flow are all gNBs used by the QoS Flow in an interval T, UPF^T_Flow are all UPFs used by the QoS Flow in an interval T.

E_UE can also be obtained as the sum of E_Session for the given UE:

E_UE = ∑_{Session_i∈Session_UE} E_{Session_i}

U Support of traffic offloading at the H-UPF deployed nearby VPLMN for HR PDU Session |R19| p. 737

U.1 General p. 737

The Home PLMN operator can deploy H-UPFs on sites located physically close to the VPLMN (e.g. visited region) for the support of the local traffic routing at the H-UPF, i.e. home session breakout performed at the H-UPF controlled by H-SMF.

Reproduction of 3GPP TS 23.501, Fig. U.1-1: Deployment scenario for traffic offloading at the H-UPF deployed nearby VPLMN region for HR PDU Session

Figure U.1-1: Deployment scenario for traffic offloading at the H-UPF deployed nearby VPLMN region for HR PDU Session

Figure U.1-1 depicts the deployment scenario of H-UPF nearby VPLMN for HR PDU Session for traffic offloading at the H-UPF. For simplicity, other network functions are not shown.

U.2 PDU Session establishment for supporting traffic offloading at the H-UPF p. 737

This clause describes the HR PDU Session establishment for the roaming traffic offloading at the H-UPF deployed nearby VPLMN.

The following are some considerations:

The H-SMF decides to support roaming traffic offloading at the H-UPF for HR PDU Session based on the configured operator policy
When performing H-UPF selection as described in clause 6.3.3.3, UE location information (e.g. MNC and MCC of the VPLMN) can be considered in order to select a H-UPF nearby VPLMN for a given HR PDU Session, based on the HPLMN operator policy.
Based on the operator policy, the selected H-UPF deployed nearby VPLMN can provide the H-SMF with the DNS server information, if it is locally configured, as described in clause 5.8.2.2.

U.3 Re-establishment of PDU Session due to UP Path failure p. 738

For the deployment scenario where the H-UPF of HR PDU Session is deployed nearby VPLMN, if the H-SMF receives from H-UPF the UP Path failure report for the path between the H-UPF (PSA) and V-UPF, the H-SMF acts as described in TS 23.527. If the H-SMF decides to delete the PDU session contexts associated with the path in failure as described in TS 23.527, the H-SMF can trigger release of the HR PDU Session as described in clause 4.3.4.3 of TS 23.502 and include an existing cause value indicating that a PDU Session re-establishment is requested. During the new HR PDU Session re-establishment, a new H-UPF and possibly new DNS server information (and DNS security information) are selected based on operator policy.

V NR Femto |R19| p. 739

V.0 General p. 739

This Annex provides information on how the NR Femto can be deployed and used by means of functionalities defined in clause 5.50 and existing functionalities.

V.1 NR Femto Deployment Options p. 739

Figure V.1-1 depicts the deployment options of NR Femto with a locally deployed UPF close to the location of NR Femto node(s). The locally deployed UPF is a 5GC entity, has a direct N4/N9 interface with the 5GC and can be selected based on the edge computing functionality specified in clause 5.13. The NR Femto GW is optionally used as a concentrator for N2 interface. N3 interface directly goes to a centrally deployed UPF (behind the NR Femto GW) or to a locally deployed UPF (close to NR Femto node location). N3 interface may also go via the NR Femto GW where in this case, the NR Femto GW only performs routing at IP layer.

Reproduction of 3GPP TS 23.501, Fig. V.1-1: NR Femto deployment options for 5GS

Figure V.1-1: NR Femto deployment options for 5GS

W (Normative) UDP-Option carrying media related information over UDP tunnel |R19| p. 740

When the DL traffic is end-to end encrypted and transported from the AS proxy through a UDP tunnel established using connect-udp between the AS proxy and the PSA UPF as described in clause 5.37.9.2, the AS proxy generates a XRM packet which inner UDP datagram contains the DL UDP media packets, i.e. QUIC packet between AS proxy and UE and the outer UDP datagram between AS proxy and UPF contains UDP-Option carrying encrypted media related information. Figure W-1 shows XRM packet structure.

Reproduction of 3GPP TS 23.501, Fig. W-1: XRM packet structure

Figure W-1: XRM packet structure

After the UPF establishes a QUIC connection to the AS proxy using connect-udp according to clause 5.37.9.2, the AS proxy and the PSA UPF negotiates security keys using connect-udp upgrade token in tunnelled mode. Then the AS proxy encodes media related information into the UDP-Option in outer UDP datagram and uses security keys for encrypting media related information carried in the UDP-Option.