Content for  TS 26.501  Word version:  18.6.0

In a second variant of this collaboration scenario, content contributed to the 5GMS System by the 5GMSu Client is egested by the 5GMSu AS at reference point M2u (by either push- or pull-based means) and directly ingested by the 5GMSd AS at reference point M2d (with push- or pull-based content ingest provisioned the same way as for the corresponding content egest). The content thus bypasses the external 5GMS Application Provider altogether.

Figure A.15.3-2 shows the call flow for this scenario when push-based egest/ingest is used for direct content re-ingestion. (To simplify the call flow, the details of the content preparation process are omitted.)

The steps for this call flow are identical to those in clause A.15.2 except for the following: If pull-based egest/ingest is instead used between the 5GMSu AS and the 5GMSd AS, the order of the provisioning (steps 1-5 and 6-10 of Figure A.15.3-2) is reversed to the order shown in Figure A.15.3-3 with uplink streaming provisioned before downlink streaming:

The steps for this call flow are identical to those in clause A.15.2 except for the following:

In a third variant of this collaboration scenario, the 5GMS System is provisioned by the 5GMS Application Provider for uplink-downlink content redistribution per clause A.15.3. The 5GMS System recognises this and arranges for content to be transferred directly from the 5GMSu AS to the 5GMSd AS via an internal interface not specified by 3GPP (as an implementation-specific optimisation) instead of egesting the content at reference point M2u and re-ingesting it at M2d. Content may additionally be egested by the 5GMSu AS at reference point M2u for ingestion by the 5GMS Application Provider and possible redistribution to other 5GMS Systems and/or other destination networks.