5 Procedures for Real-time Media Communication
26.5063GPP5G Real-time Media Communication Architecture (Stage 2)Release 18TS
5.1 Procedures for Edge Processing
[Editor’s Note: This clause is corresponding to clause 4.2]
5.2 xxx
[Editor’s Note: Detailed procedures will be address per each topic in clause 4.]
Annex A (informative):
Architecture variants for collaboration scenarios
A.1 General
This clause addresses the derivative architecture for each of the collaboration scenarios. The four collaboration scenarios are summarized below and further details is specified in Annex A.
It specifies the four collaboration scenarios as summarized below based on the location of required functional entities in trusted domain as defined as follows.
– 5G support for OTT WebRTC: in this scenario the WebRTC session runs completely over the top. However, the MNO may offer support in form of QoS allocation, bitrate recommendations, and QoE report collection based on request by the UE.
– MNO-provided trusted WebRTC functions: in this scenario the MNO offers trusted support functions such as ICE servers to the WebRTC application on the UE.
– MNO-facilitated WebRTC services: the MNO may host and facilitate WebRTC sessions by providing a trusted WebRTC signaling server, which may also offer 5G network assistance.
– Inter-operable WebRTC services: collaboration scenario 3 is extended with functions to support MNO to MNO inter-operability.
The list of key functional entities in trusted domain differs from collaboration scenarios as described in Table A.1-1.
Table A.1‑1: Mapping of key functions to each collaboration scenarios
|
Functions/CS |
Collaboration scenario 1 |
Collaboration scenario 2 |
Collaboration scenario 3 |
Collaboration scenario 4 |
|
Provisioning function |
Optional |
Optional |
Optional |
Optional |
|
Configuration function |
Optional |
Required |
Optional (maybe fulfilled by WebRTC signalling server) |
Optional (maybe fulfilled by WebRTC signalling server) |
|
MSH |
Required |
Optional |
Optional |
Optional |
|
Network support function |
Required |
Required |
Optional (maybe fulfilled by WebRTC signalling server) |
Optional (maybe fulfilled by WebRTC signalling server) |
|
Trusted ICE function |
N/A |
Required |
Optional |
Optional |
|
Trusted WebRTC signalling server |
N/A |
N/A |
Required |
Required |
|
Trusted media server |
N/A |
Optional |
Optional |
Optional |
NOTE: The collaboration scenario 3 may further split depending on the role of MNO, as addressed in TR 26.930.
A.2 Collaboration scenario 1:
Editor’s NOTE: Detailed text to be added
Figure A.2-1: Derivative 5G-RTC architecture for collaboration scenario 1
Call flow for collaboration scenario 1 is as follows. Session setup part and QoS request part are separately performed.
Figure A.2-2: Session setup flow in Collaboration Scenario #1
Figure A.2-3: QoS request flow in Collaboration Scenario #1
Requests and responses in the sequence are as follows:
– 1 and 2. The session information is exchanged between the client application and WebRTC signalling server. It can be proprietary when the interoperability between operators is not necessary.
– 3 and 10. The application requests MSH the network assistance with iRTC session information. The response includes the result of the request and may include the bitrate recommendation.
– 4 and 5. MSH requests Network Support AF the service access information for following procedures. The response is the result of the request and may include the service access information.
– 6 and 9. MSH requests Network Support AF the network assistance. The response may include the bitrate recommendation.
– 7 and 8 Network Support AF requests PCF the QoS control through N5. The response is the result of the request success or failure. The QoS flow event subscription may be conducted.
A.3 Collaboration scenario 2:
Editor’s NOTE: Detailed text to be added
Figure A.3-1: Derivative 5G-RTC architecture for collaboration scenario 2
Editor’s NOTE: RTC-4m interface is present only when the ICE function contains the TURN server in CS-2.
A.4 Collaboration scenario 3:
Editor’s NOTE: Diagram and discussion are under the developments
Figure A.4-1: Derivative 5G-RTC architecture for collaboration scenario 3x
A.5 Collaboration scenario 4:
Editor’s NOTE: Diagram and discussion are under the developments
Annex B (informative):
Change history
|
Change history |
|||||||
|
Date |
Meeting |
TDoc |
CR |
Rev |
Cat |
Subject/Comment |
New version |
|
2022-08 |
SA4#120 |
Initial draft |
0.1.0 |
||||
|
2022-11 |
SA4#121 |
S4-221543 |
SA4#121 Agreements: S4-221344, S4-221542, S4-221544, S4-221545, S4-221510, S4-221509, S4-221371, S4-221508 |
0.2.0 |
|||
|
2022-11 |
SA4#121 |
S4-221610 |
Minor update in Scope: word “generic” removed |
0.2.1 |
|||
|
2022-12 |
Created by MCC to be presented to TSG for information |
1.0.0 |
|||||