Cardinality of ingestConfiguration.path is incorrect in Content Hosting Configuration

[rjb1000]

Problem description

The Content Hosting Configuration property ingestConfiguration.path is marked with cardinality 1..1 in table 7.6.3.1-1.

The accompanying description implies it is only used in the case of push-based ingest into the 5GMSd AS. And it is nominated by the 5GMS AF in this case:

The relative path which will be used to address the media resources at interface M2d.
This path is provided by the 5GMSd AF in the case of Push-based ingest.

The OpenAPI schema definition in clause C.3.1 does not mark this property (or, in fact, any properties in ingestConfiguration) as required.

Suggested solution

In the specification of the ingestConfiguration.path property in table 7.6.3.1-1:

1. Correct the Cardinality to be 0..1.
2. Clarify in the Description that the property is never present for pull-based ingest.
3. Specify in the Description that it is an error to provide this property in an M1d request. It is only ever present in an M1d response generated by the 5GMSd AF.

In addition, consider renaming the property ingestConfiguration.pushPath to make its limited purpose more self-describing.

Additional context

This issue was discovered when implementing the 5GMSd AF.

[davidjwbbc]

Fix the cardinality in table 7.6.3.1-1 to show this as optional.

@rjb1000 will raise a CR

[rjb1000]

3GPP draft Change Request to TS 26.512 Rel-16 S4aI221386 opened for initial discussion at today's 3GPP SA4 MBS subworking group ad hoc call. Discussion will continue on 20th October.

(Plan is to create a Rel-17 counterpart later that makes equivalent changes there.)

[rjb1000]

Latest draft CR proposes deprecating the confusingly named IngestConfiguration.entryPoint and IngestConfiguration.path in favour of IngestConfiguration.baseURL.

[rjb1000]

Latest draft CRs available to 5G-MAG members on Causeway as CDT0107.3GPP SA4#121 TS26.512 API corrections.

[rjb1000]

Formal CRs submitted to SA4#121:

• Rel-16 CR0027 in S4-221250.
• Rel-17 CR0028 in S4-221251.

[rjb1000]

The following Change Requests were agreed at SA4#121 Closing Plenary yesterday afternoon:

• TS 26.512:
  • Rel-16: CR0027r2 S4-221605.
  • Rel-17: CR0028r2 S4-221606.

[rjb1000]

Change Requests approved at SA#98-e:

• Rel-16: CR0027r2 in SP-221042.
• Rel-17: CR0028r2 in SP-221043.

[rjb1000]

New specifications published:

• TS 26.512 V16.8.0.
• TS 26.512 V17.3.0.