# 3GPP TSGS4 ad hoc meeting post SA4#127-bis-e

TDoc: | S4aI240045
Agenda Item: | 2.5
Work Item: | 5GMS_Pro_Ph2
Title: | TS 26.510 V1.2.0 Editor's draft
Source: | BBC (editor)

## Summary

The attached editor's draft implements the following pCR draft agreed at SA4#127-bis-e Closing Plenary:

- S4-240812: Add Background Data Transfer support to Dynamic Policies feature.

It also implements the following pCR draft agreed at the MBS subworking group ad hoc meeting after SA4#127-bis-e:

- S4aI240049: Add missing implicit data reporting parameters to DynamicPolicy, NetworkAssistanceSession and ConsumptionReportingUnit resources.

In addition the following change was proposed on the the MBS subworking group ad hoc call on 2nd May 2024:

- Moved locationReporting property from ConsumptionReportingConfiguration to ProvisioningSession so that it controls location reporting for Dynamic Policies and Network Assistance Sessions as well as consumption reporting. Also made corresponding change in Service Access Information resource.

The draft also includes the following editorial improvements to:

1. Resolved Editor's Note in clause 5.3.2.1 concerning Media Entry Point for uplink media streaming and RTC.
2. Editorial corrections to PCF interactions in clause 5.5.3 and 5.5.4.
3. Reworked table NOTEs with normative requirements in clauses 7.3.3 and 8.7.3.1.
4. Respecified metrics as fully-qualified URIs in clauses 8.10.3.1 and 9.2.3.1 (corresponding to TS 26.512 CR).

## Editor's detailed commentary

### S4-240812

- Renumbered clause 5.5.x to accommodate insertion of new clause as 5.5.2.
- I encountered difficulties implementing this pCR due to the eleventh hour factoring out of BDTWindowType to support the signalling of Background Data Transfer opportunity windows in Service Access Information.

- (This missing feature was added between the end of the MBS SWG meeting and the presentation at SA4 Closing Plenary, so there wasn't time for careful review.)
- Because the Background Data Transfer windows are provisioned per Policy Template, they need to be bound to a particular Policy Template in the Service Access Information. I therefore moved the newly added property inside the policyTemplateBindings object array in clause 9.2.3.1. I also adjusted the description to reflect this.
- The newly introduced BDTWindowType is referenced by both the ServiceAccessInformation resource and the DynamicPolicy resource, so I moved it into clause 7.3.3.14 ("Common OpenAPI data types").

- I had to delete the first property of this data type (windows) which was an overhang from its previous existence as part of (the unshared) M5BDTSpecificationType.

- Based on the above binding, I realised that the Dynamic Policy client API of the Media Session Handler needs to expose additional method parameters to allow the API invoker (Media-aware Application at M6 or Media Access Function at M11) to specify which media delivery session it is referring to and which Policy Template it is interested in requesting a Background Data Transfer for.

- The external identifier of the Policy Template is used to provide a unique reference and this is included in the Policy Template binding signalled in the Service Access Information.

- Recall that this realises the more abstract concept of Service Operation Point.

- Returning to the provisioning side of things, I realised that the separate enforceAggregateBitRate is not needed in M1BDTSpecificationType because the mere presence of aggregate[Down|Up]linkBitRateLimit is sufficient to tell that Media AF that it needs to enforce a maximum aggregate bit rate for all currently instances of a given Policy Template.

- Removed bullet in clause 5.2.7.1.
- Removed property in clause 8.7.3.2.
- Also adjusted text in clause 5.3.3.2 to clarify that the Media Session Handler bids for aggregate[Down|Up]linkBitRateLimit when instantiating the Dynamic Policy, and the Media AF replaces these values with its grant in the response.

- Other notable changes:

- Clarified mapping of Dynamic Policies and Network Assistance Sessions to MediaComponent of ApplicationSessionContext in PCF at clauses 5.5.3 and 5.5.4.
- Replaced "UE" with "Media Client" to be more specific in some cases.

### S4aI240049

- I additionally implemented the idea I proposed of moving the locationReporting flag from ConsumptionReportingConfiguration to ProvisioningSession so that the exposure of the UEs location can be permitted more broadly than just to consumption reporting when provisioning 5G Media Streaming services. This avoids the need to repeat that flag for QoE metrics reporting, Dynamic Policy instantiation and Network Assistance (the last of which isn't even a provisionable feature in the Maf_Provisioning API).

- This property moves from table 8.11.3.1-1 to table 8.2.3.1-1.

- The corresponding move of the locationReporting flag in ServiceAccessInformation can be found in table 9.2.3.1-1.