Content for TS 29.502 Word version: 18.5.0

1… 5… 5.2.2… 5.2.2.2.4… 5.2.2.3… 5.2.2.3.2… 5.2.2.3.3… 5.2.2.3.6… 5.2.2.3.8… 5.2.2.3.10… 5.2.2.3.17… 5.2.2.3.23… 5.2.2.4… 5.2.2.8… 5.2.2.8.2… 5.2.2.8.2.7… 5.2.2.8.2.12… 5.2.2.8.2.20… 5.2.2.8.3… 5.2.2.8.3.6… 5.2.2.9… 5.2.3… 6… 6.1.2… 6.1.3… 6.1.3.3… 6.1.3.5… 6.1.3.6… 6.1.3.7… 6.1.4… 6.1.6… 6.1.6.2… 6.1.6.2.5… 6.1.6.2.11… 6.1.6.2.18… 6.1.6.2.27… 6.1.6.2.40… 6.1.6.2.54… 6.1.6.2.65… 6.1.6.3… 6.1.6.4… 6.1.7… A… B… C…

C.1 General C.2 ABNF definitions (Filename: "TS29502_CustomHeaders.abnf") D.1 Usage of Charging ID and SMF Charging ID

C (Normative) ABNF grammar for 3GPP SBI HTTP custom headers |R18| p. 359

C.1 General p. 359

This Annex contains a self-contained set of ABNF rules, comprising the re-used rules from IETF RFCs, and the rules defined by the 3GPP custom headers defined in this specification (see clause 6.1.2.3).

This grammar may be used as input to existing tools to help implementations to parse 3GPP custom headers.

C.2 ABNF definitions (Filename: "TS29502_CustomHeaders.abnf") p. 360

; ----------------------------------------
;   RFC 5234
; ----------------------------------------
HTAB  = %x09 ; horizontal tab
SP    = %x20
DIGIT = %x30-39 ; 0-9
; ----------------------------------------
;   RFC 9110
; ----------------------------------------
OWS = *( SP / HTAB )
date1       = day SP month SP year ; e.g., 02 Jun 1982
day         = 2DIGIT
month       = %x4A.61.6E ; "Jan", case-sensitive
            / %x46.65.62 ; "Feb", case-sensitive
            / %x4D.61.72 ; "Mar", case-sensitive
            / %x41.70.72 ; "Apr", case-sensitive
            / %x4D.61.79 ; "May", case-sensitive
            / %x4A.75.6E ; "Jun", case-sensitive
            / %x4A.75.6C ; "Jul", case-sensitive
            / %x41.75.67 ; "Aug", case-sensitive
            / %x53.65.70 ; "Sep", case-sensitive
            / %x4F.63.74 ; "Oct", case-sensitive
            / %x4E.6F.76 ; "Nov", case-sensitive
            / %x44.65.63 ; "Dec", case-sensitive
year        = 4DIGIT
day-name    = %x4D.6F.6E ; Mon
            / %x54.75.65 ; Tue
            / %x57.65.64 ; Wed
            / %x54.68.75 ; Thu
            / %x46.72.69 ; Fri
            / %x53.61.74 ; Sat
            / %x53.75.6E ; Sun
time-of-day = hour ":" minute ":" second
hour        = 2DIGIT
minute      = 2DIGIT
second      = 2DIGIT
; ----------------------------------------
;   3GPP TS 29.502
;
;   Version: 18.5.0 (December 2023)
;
;   (c) 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
; ----------------------------------------
;
; Header: 3gpp-Sbi-Origination-Timestamp
;
Sbi-Origination-Timestamp-Header = "3gpp-Sbi-Origination-Timestamp:" OWS day-name ","
                                   SP date1 SP time-of-day "." milliseconds SP "GMT" OWS
milliseconds                     = 3DIGIT

D Charging Identifier Handling |R18| p. 361

D.1 Usage of Charging ID and SMF Charging ID p. 361

D.1.1 General p. 361

The Charging ID has been defined (from Rel-15 onwards) as a Uint32 value which is unique within one SMF (the V-SMF or H-SMF that assigns it). To avoid possible charging identifiers' collision in H-SMF for Home Routed PDU sessions, an SMF Charging ID has been defined (from Rel-18 onwards) as a string which contains the Uint32 value and the SMF NF Instance ID (see TS 29.571).

This clause summarizes the principles on using Charging ID and SMF Charging ID for HR PDU sessions, especially when not all the V-SMF(s) and H-SMF of a PDU session support the SMF Charging ID.

This Annex is informative and the normative requirements in this specification or in other 3GPP specifications prevail over the description in this Annex if there is any difference.

D.1.2 HPLMN supporting the SMF Charging ID p. 361

An SMF, CHF and PCF complying with Rel-18 onwards support the SMF Charging ID.

If the HPLMN (H-SMF, CHF and PCF) supports the SMF Charging ID, the H-SMF indicates support of the SCID (String based Charging Identifier) feature (in its NF Profile in NRF and towards the V-SMF).

The HPLMN uses the SMF Charging ID as the charging identifier for the PDU session.

If the VPLMN supports the SMF Charging ID:

The VPLMN uses the SMF Charging ID as the charging identifier for the PDU session.

If the VPLMN does not support the SMF Charging ID (e.g. the V-SMF complies with a release earlier than Rel-18):

The VPLMN uses the Charging ID as the charging identifier for the PDU session.
The VPLMN only provides the Charging ID to the H-SMF during the HR PDU session establishment. The H-SMF derives the SMF Charging ID using the received Charging ID and V-SMF Instance ID.

D.1.3 HPLMN not supporting the SMF Charging ID p. 361

When the HPLMN does not support the SMF Charging ID (e.g. the H-SMF complies with a release earlier than Rel-18), the charging identifier used by both the V-SMF and the H-SMF is the Charging ID.

D.1.4 Transfer of (SMF) Charging ID between SMFs p. 361

The following principles applies to support mobility scenarios where the source and/or target (V-) SMF may or may not support the SCID feature:

During a HR PDU session establishment:
- the V-SMF provides the Charging ID to the H-SMF; and
- the V-SMF additionally provides the SMF Charging ID if both the V-SMF and H-SMF support the SCID feature.
During a V-SMF change or insertion:
- the Charging ID is passed from the source (V-)SMF to the target V-SMF;
- the SMF Charging ID is also passed from the source (V-)SMF to the target V-SMF, if it is available at the source (V-)SMF and both the source and target (V-)SMFs support the SCID feature; and
- the H-SMF provides the SMF Charging ID to the new V-SMF if both the H-SMF and the new V-SMF support the SCID feature.
NOTE:
This enables the SMF Charging ID to be used by the new V-SMF and H-SMF, when both the new V-SMF and H-SMF support the SCID feature but the source V-SMF does not support the SCID feature.
During EPS to 5GS mobility:
- the H-SMF provides the Charging ID to the new V-SMF; and
- the H-SMF additionally provides the SMF Charging ID to the new V-SMF if both the H-SMF and the V-SMF support the SCID feature.