Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TS 26.512: Add missing filterType parameter to ServiceDataFlowDescription #103

Open
rjb1000 opened this issue Dec 22, 2023 · 2 comments
Open
Assignees
Labels
3GPP Rel-16 Issues relating to 3GPP Release 16 specifications. 3GPP Rel-17 Issues relating to 3GPP Release 17 specifications. 3GPP Rel-18 Issues relating to 3GPP Release 18 specifications. 3GPP TS 26.510 Issues relating to SA4's "Media delivery; intrns. and APIs for prov. and media sess. hndlng." spec. 3GPP TS 26.512 Issues relating to SA4's "5G Media Streaming (5GMS); Protocols" specification. 5GMS Dynamic Policies 5GMS Network Assistance Improvement

Comments

@rjb1000
Copy link
Contributor

rjb1000 commented Dec 22, 2023

Context

Service Data Flow filters are used in connection with Dynamic Policy Instances and Network Assistance Sessions in the 5GMS System. They are mapped into data structures that are ultimately used by the UPF to identify IP packets belonging to particular 5GMS application data flows in order to apply special QoS or charging treatments to them.

Problem description

TS 26.512 defines a common enumeration type SdfMethod describing the type of Service Data Flow filter:

  • 5_TUPLE
  • 2_TUPLE
  • TYPE_OF_SERVICE_MARKING
  • FLOW_LABEL
  • DOMAIN_NAME

This enumeration is not currently used anywhere in the M1 or M5 APIs.

The ServiceDataFlowDescription data type can be either a domain name or an IpPacketFilterSet. It is not currently possible for the 5GMS AF to validate whether the correct parameters have been supplied.

Suggested solution

Add a mandatory filterType property (of type SdfMethod) to the ServiceDataFlowDescription data type to explicitly signal which kind of Service Data Flow filter is being described.

@rjb1000 rjb1000 added Improvement 3GPP Rel-16 Issues relating to 3GPP Release 16 specifications. 3GPP Rel-17 Issues relating to 3GPP Release 17 specifications. 3GPP TS 26.512 Issues relating to SA4's "5G Media Streaming (5GMS); Protocols" specification. 3GPP Rel-18 Issues relating to 3GPP Release 18 specifications. 5GMS Network Assistance 5GMS Dynamic Policies 3GPP TS 26.510 Issues relating to SA4's "Media delivery; intrns. and APIs for prov. and media sess. hndlng." spec. labels Dec 22, 2023
@rjb1000 rjb1000 added this to the 3GPP SA4#127→SA#103 milestone Dec 22, 2023
@rjb1000 rjb1000 added this to Pre-Acceptance in 3GPP specification feedback via automation Dec 22, 2023
@rjb1000
Copy link
Contributor Author

rjb1000 commented Feb 23, 2024

Change agreed at SA4#127 (Sophia Antipolis):

  • TS 26.510 Rel-18 "[5GMS_Pro_Ph2] TS 26.510 V1.1.0 editor's draft" in S4-240103.

@rjb1000
Copy link
Contributor Author

rjb1000 commented Mar 19, 2024

Reopening to allow for possible Rel-16/Rel-17 CR later this year.

@rjb1000 rjb1000 reopened this Mar 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3GPP Rel-16 Issues relating to 3GPP Release 16 specifications. 3GPP Rel-17 Issues relating to 3GPP Release 17 specifications. 3GPP Rel-18 Issues relating to 3GPP Release 18 specifications. 3GPP TS 26.510 Issues relating to SA4's "Media delivery; intrns. and APIs for prov. and media sess. hndlng." spec. 3GPP TS 26.512 Issues relating to SA4's "5G Media Streaming (5GMS); Protocols" specification. 5GMS Dynamic Policies 5GMS Network Assistance Improvement
Projects
Status: Pre-Acceptance
Development

No branches or pull requests

2 participants