Skip to content

Potential Mismatch in NodeFunctionality Enumeration: Missing "SMS" Value in 3GPP TS 32.291 Section 6.1.6.3.4 #73

@VishalGujela

Description

@VishalGujela

Dear 3GPP/ETSI Team,

I would like to report a possible inconsistency between the 3GPP specification and the corresponding OpenAPI/Swagger (JDGREE) model regarding the NodeFunctionality enumeration defined in 3GPP TS 32.291 (version 17.10.0, Section 6.1.6.3.4).

According to the official 3GPP specification document (ETSI TS 132 291 V17.10.0
), the NodeFunctionality enumeration does not include a value for "SMS".

However, in the Swagger/OpenAPI (JDGREE) definition, an additional enumeration value "SMS" is present under the same NodeFunctionality list.

Observed Behavior:

The Swagger/JDGREE model includes: "SMS"

Image

The 3GPP TS 32.291 Section 6.1.6.3.4 does not list "SMS"

Image

Expected Behavior:

The enumeration values should remain consistent between the 3GPP specification and the Swagger/OpenAPI definition.
If "SMS" is intentionally added to represent SMSF (Short Message Service Function) functionality in 5GC, the specification should be updated to reflect this addition.

References:

3GPP TS 32.291 V17.10.0 (Section 6.1.6.3.4 – NodeFunctionality)

JDGREE/Swagger definition for the Charging Data model

Suggested Action:

Please confirm whether "SMS" is an intentional extension to support SMSF-related charging events in 5GC, or if it is a typographical/implementation mismatch between the specification and the reference API model.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions