Tdoc List

2021-02-10 22:17

Agenda Topic TDoc Title Source Type For Avail Treated Decision Wdrn Replaced-by Replaces
1 Opening of the e-meeting: Monday February 1st, at 09:00 hours CET                      
2 Approval of the agenda and registration of documents S4‑210001 Agenda for SA4#112-e Dolby Laboratories Inc. agenda Approval Yes
Yes
 		agreed No    
    S4‑210094 Proposed meeting schedule for SA4#112-e SA4 chairman other Agreement Yes
Yes
 		revised No S4‑210255  
    S4‑210095 Guidelines for 3GPP SA4#112-e as Electronic Meeting SA4 chair other Information Yes
Yes
 		noted No    
    S4‑210255 Proposed meeting schedule for SA4#112-e SA4 chairman other Agreement Yes
Yes
 		noted No   S4‑210094
3 IPR and antitrust reminder                      
4 Approval of previous meeting report S4‑210002 Meeting Report of SA4#111-e 3GPP MCC report Approval Yes
Yes
 		revised No S4‑210290  
    S4‑210290 Meeting Report of SA4#111-e 3GPP MCC report Approval Yes
Yes
 		approved No   S4‑210002
5 Reports/Liaisons from other groups/meetings                      
5.1 SA4 SWG ad hoc meetings S4‑210010 LS_In 3GPP MCC LS in Discussion No
No
 		reserved No    
    S4‑210011 LS_In 3GPP MCC LS in Discussion No
No
 		reserved No    
    S4‑210016 Draft Report for MTSI SWG 2 December 2020 Teleconference #15 on ITT4RT MTSI SWG Chair report Approval Yes
Yes
 		approved No    
    S4‑210017 Draft Report for MTSI SWG 9 December 2020 Teleconference on FS_FLUS_NBMP MTSI SWG Chair report Approval Yes
Yes
 		approved No    
    S4‑210018 Draft Report for MTSI SWG 16 December 2020 Teleconference #16 on ITT4RT MTSI SWG Chair report Approval Yes
Yes
 		approved No    
    S4‑210019 Draft Report for MTSI SWG 20 January 2021 Teleconference #17 on ITT4RT MTSI SWG Chair report Approval Yes
Yes
 		approved No    
    S4‑210031 VIDEO SWG telco report 24th November 2020 VIDEO SWG Chair (Tencent) report Approval Yes
Yes
 		approved No    
    S4‑210032 VIDEO SWG telco report 1st December 2020 VIDEO SWG Chair (Tencent) report Approval Yes
Yes
 		approved No    
    S4‑210033 VIDEO SWG telco report 8th December 2020 VIDEO SWG Chair (Tencent) report Approval Yes
Yes
 		approved No    
    S4‑210034 VIDEO SWG telco report 15th December 2020 VIDEO SWG Chair (Tencent) report Approval Yes
Yes
 		approved No    
    S4‑210035 VIDEO SWG telco report 22nd December 2020 VIDEO SWG Chair (Tencent) report Approval Yes
Yes
 		approved No    
    S4‑210036 VIDEO SWG telco report 12th January 2021 VIDEO SWG Chair (Tencent) report Approval Yes
Yes
 		approved No    
    S4‑210037 VIDEO SWG telco report 19th January 2021 VIDEO SWG Chair (Tencent) report Approval Yes
Yes
 		approved No    
    S4‑210090 Report of SA4 MBS SWG AH Telco (3rd Dec. 2020) MBS SWG Chair report Approval Yes
Yes
 		approved No    
    S4‑210091 Report of SA4 MBS SWG AH Telco (10th Dec. 2020) MBS SWG Chair report Approval Yes
Yes
 		approved No    
    S4‑210092 Report of SA4 MBS SWG AH Telco (17th Dec. 2020) MBS SWG Chair report   Yes
Yes
 		approved No    
    S4‑210093 Report of SA4 MBS SWG AH Telco (21st Jan. 2021) MBS SWG Chair report Approval Yes
Yes
 		approved No    
    S4‑210164 3GPP SA4 SQ SWG report from teleconference on HInT (7 December 2020) SA4 SQ SWG Chair report Agreement Yes
Yes
 		approved No    
    S4‑210166 3GPP SA4 SQ SWG report from teleconference on ATIAS, HaNTE, HInT (18 January 2021) SA4 SQ SWG Chair report Approval Yes
Yes
 		approved No    
5.2 Other 3GPP groups S4‑210006 LS from 3GPP SA2 on New Standardized 5QIs for 5G-AIS (Advanced Interactive Services) 3GPP MCC LS in Action Yes
Yes
 		revised No S4‑210283  
    S4‑210007 LS from 3GPP SA2 on 5MBS progress and issues to address 3GPP MCC LS in Action Yes
Yes
 		noted No    
    S4‑210008 LS from 3GPP TSG SA on Use of Inclusive Language in 3GPP 3GPP MCC LS in Action Yes
Yes
 		noted No    
    S4‑210096 Brief report from SA#90-e on SA4 topics SA4 Chair report Information Yes
Yes
 		noted No    
    S4‑210256 Status of non-inclusive language in SA4 specifications Qualcomm Incorporated other discussion Yes
YesThomas: Presented the document. Tomas: suggested to have searches on 'black-list' with various combinations in the SA4 specifications. Chair: The plan is to do for Rel 17. Edward: Does not matter to keep it alike. Thomas: MPEG has corrected it most of the specification. Chair: To discuss with MCC on the way forward.
 		agreed No    
    S4‑210283 Reply LS on New Standardized 5QIs for 5G-AIS (Advanced Interactive Services) Video SWG LS out Agreement Yes
YesQi, Huawei: In the Video SWG, it was agreed that the information to complete the work by May 2021 is not updated accordinly in the LS. Thomas, Qc: It was changed online during Vedio SWG on request by Apple. Gilles, Tencent: Second Qualcomm on the above.
 		approved No   S4‑210006
5.3 Other groups S4‑210004 Liaison on availability of DASH 3GPP MCC LS in Presentation Yes
Yes
 		noted No    
    S4‑210005 LS from ISO/IEC JTC SC 29/WG 03 on OMAF 2nd edition 3GPP MCC LS in Discussion Yes
Yes
 		noted No    
    S4‑210009 Reply to the LS on 8K VR 360 operation point and VRIF Guidelines 2.3 3GPP MCC LS in Discussion Yes
Yes
 		revised No S4‑210274  
    S4‑210329 Reply LS on on 8K VR 360º operation points 3GPP TSG SA WG4 (SA4) LS out Agreement Yes
Yes
 		revised No S4‑210344 S4‑210274
    S4‑210344 Reply LS on on 8K VR 360º operation points 3GPP TSG SA WG4 (SA4) LS out Agreement Yes
Yes
 		agreed No   S4‑210329
6 Issues for immediate consideration                      
7 Enhanced Voice Service (EVS) SWG S4‑210099 Draft EVS SWG Agenda QUALCOMM JAPAN LLC. agenda Approval Yes
Yes
 		approved No    
    S4‑210287 EVS Agenda EVS SWG agenda Approval Yes
Yes
 		approved No    
    S4‑210289 (reserved) EVS SWG other discussion Yes
No
 		reserved No    
7.1 Opening of the session                      
7.2 Registration of documents                      
7.3 CRs to Features in Release 16 and earlier                      
7.4 Liaisons with other groups/meetings                      
7.5 IVAS_Codec (EVS Codec Extension for Immersive Voice and Audio Services) S4‑210123 Draft IVAS codec development overview (IVAS-1) Huawei Device Co., Ltd other Agreement No
No
 		reserved No    
    S4‑210130 Schedule for planned IVAS MASA C Reference Software updates Nokia Corporation discussion Information Yes
Yes
 		noted No    
    S4‑210133 Draft IVAS codec development overview (IVAS-1) HuaWei Technologies Co., Ltd other Agreement Yes
Yes
 		revised No S4‑210262  
    S4‑210138 Test methodologies for IVAS codec testing Dolby Laboratories Inc. discussion   Yes
Yes
 		noted No    
    S4‑210139 Working assumptions for IVAS Codec Selection & Characterization Testing Campaigns Dolby Laboratories Inc. discussion Agreement Yes
Yes
 		noted No    
    S4‑210149 IVAS test methods for stereo Ericsson LM, Fraunhofer IIS discussion Discussion Yes
Yes
 		noted No    
    S4‑210150 Considerations for IVAS processing plans Ericsson LM discussion Agreement Yes
Yes
 		revised No S4‑210315  
7.6 New Work Items and Study Items                      
7.7 Any Other Business                      
7.8 Close of the session                      
8 Multicast-Broadcast-Streaming (MBS) SWG S4‑210227 LS to ISO/JTC 1 3GPP SA4 response Approval Yes
YesThis LS covers the implications on the copyright issues that 26.244 was publicly available. The proponent has proficiently drafted the LS citing the problems encoutered, as certain standards (like ISO/IEC 23009-1) are not made available free of cost to the codecs community. Also, few of them has a direct reference to the 3GPP specifications. Further, it has been requested that, publication of the latest editions of ISO/IEC 23009-1 and ISO/IEC 14496-12 on ISO’s available website (i.e. https://standards.iso.org/ittf/PubliclyAvailableStandards) be made available free of charge.
 		revised No S4‑210247  
    S4‑210231 CR to TS 26.512 Aggregated CR Ericsson LM, BBC, Enensys, Qualcomm Inc CR Agreement Yes
Yes
 		revised No S4‑210317  
    S4‑210242 LS to SA2 and SA6 on FS_5GMS_Multicast and 5MBS MBS LS out discussion Yes
Yes
 		revised No S4‑210312  
    S4‑210244 Discussion on the scope of FS_5GMS-Multicast wrt 5MBS Ericsson LM discussion Agreement Yes
Yes
 		agreed No   S4‑210154
    S4‑210327 (reserved) MBS other discussion No
No
 		reserved No    
    S4‑210328 (reserved) MBS other discussion No
No
 		reserved No    
8.1 Opening of the session                      
8.2 Registration of documents S4‑210042 Proposed Corrections to TS 26.511 Qualcomm Incorporated draftCR Agreement Yes
Yes
 		revised No S4‑210228  
    S4‑210228 Proposed Corrections to TS 26.511 Qualcomm Incorporated draftCR Agreement Yes
Yes
 		revised No S4‑210246 S4‑210042
8.3 Reports/Liaisons from other groups/meetings S4‑210003 Liaison from DVB on Phase I technical specification “DVB-MABR” 3GPP MCC LS in Decision Yes
YesThe discussion revolved around the use in MBMS for integrity check that it should'nt affect the backward compatibility. However, it was felt that, it could be an issue in the scope of 26.346 for MBMS deployment and if DVB was prepared to have an extention to be done by 3GPP for ths purpose. There were views on deiciding the use cases to move forward and extending the same. Hearing all the views, the Chairman felt to prepare a response to the liaison statement.
 		replied to No    
8.4 Issues for immediate consideration                      
8.5 CRs to features in Release 16 and earlier S4‑210012 Essential corrections to Consumption Reporting APIs BBC, Enensys Technology, Ericsson draftCR Agreement Yes
Yes
 		agreed No    
    S4‑210038 Replacement client architecture figures BBC draftCR Agreement Yes
Yes
 		agreed No    
    S4‑210039 Corrections on Procedures and APIs for Downlink and Uplink Streaming Qualcomm Incorporated, BBC CR Agreement No
Yes
 		withdrawn Yes    
    S4‑210043 Proposed Corrections to TS 26.512 Qualcomm Incorporated draftCR Agreement Yes
Yes
 		withdrawn Yes    
    S4‑210044 3GPP DASH – More relevant than ever? Qualcomm Incorporated, Comcast, Orange, Dolby Laboratories discussion Agreement Yes
Yes
 		revised No S4‑210140  
    S4‑210082 Removal of Editor’s notes in 5GMS3 HUAWEI Technologies Japan K.K. CR Agreement Yes
Yes
 		revised No S4‑210230 S4‑201365
    S4‑210106 Draft LS on App ID Usage in NEF Related Service API HUAWEI Technologies Japan K.K. response Agreement Yes
YesDiscussion: Thorsten: if the group agrees to send the LS to ST3 and SA2, then need to phrase approproate questions. I work with my CT3 collegues to prepare a CR in CT3 to fix netwrok connections. AF up ID, AF application identifier, AF Does the group agree to send the LS, then agree to work on the payloads. Imed: don’t see the abckgroumd in the draft lS. It seems we are helping CT3 in this group. Why do we questin the Application IDs in presence. Thorsten: the domain name nees to be specific for detection. Imed: PF3 can be a domain name or the five tupple is better. Thorsten: which properties/fuctions should 5GMS3 do ? What is the mapping between the parameters inbetween the 5G management APIs. Chair: this is related to 159. keep 106 open in email discussion and there is rev 2 available.
 		revised No S4‑210235  
    S4‑210116 Editorial Improvements Samsung Electronics Co., Ltd draftCR Agreement Yes
Yes
 		revised No S4‑210229  
    S4‑210117 On editorial improvement on TS 26.501 Samsung Electronics Co., Ltd discussion Agreement Yes
Yes
 		noted No    
    S4‑210134 Corrections on Procedures and APIs for Downlink and Uplink Streaming Qualcomm Incorporated, BBC, Ericsson LM draftCR Agreement Yes
Yes
 		revised No S4‑210232  
    S4‑210140 3GPP DASH – More relevant than ever? Qualcomm Incorporated, Comcast, Orange, Dolby Laboratories, Tencent discussion Agreement Yes
YesWE will use the publication of DASH specification / this LS asks 3GPP to adopt DASH specificcations. But we need to deliberate on the copyright issues. Gaelle: how can company put CRs to get DASh incorporated to 3GPP. Chair: it would require the contributing companies Thomas: Is JTC 1 is the right ;evel to target it Gaelle: it has to go to TMB Iraj: to send to SC 29 so that they are aware of LS of being sent to JTC 1. Gaelle: SC 29 in copy.
 		revised No S4‑210226 S4‑210044
    S4‑210157 M5 definition in OpenAPI 3.0 format Ericsson LM draftCR Agreement Yes
Yes
 		agreed No    
    S4‑210158 Various Corrections Ericsson LM draftCR Agreement Yes
YesThe reason of the changes in this CR are: • The specification still contains a number of Editor’s Notes, which are to a certain extend obsolete and can be removed. • The service announcement information data model contains a serverAddress property (Network Assistance), which is not following the format of the other serverAddresses properties.
 		revised No S4‑210241  
    S4‑210159 Discussion on PFD referencing within Dynamic Policy API Ericsson LM discussion Discussion Yes
Yes
 		noted No    
    S4‑210174 CR on OpenAPI Implementation of m1 interface Qualcomm Wireless GmbH CR   Yes
YesImed: This is on openAPI implementation for the m1 interface in the branch m1-dev. There is a request to merge the branch in 3GPP forge. Thorsten: other CRs from Charles, Richard int eh m1 harmonization. So alignment of this CR with others is needed. Imed: as soon as the CR gets agreed, the integration can be done. Chair: Suggest to park S4-210174 to align to the content S4-210234. MCC: The author creates
 		revised No S4‑210292  
    S4‑210230 Removal of Editor’s notes in 5GMS3 HUAWEI Technologies Japan K.K. CR Agreement Yes
Yes
 		postponed No   S4‑210082
    S4‑210235 Draft LS on App ID Usage in NEF Related Service API HUAWEI Technologies Japan K.K. response Agreement Yes
YesThis doscussion revolves around the use of the domain name used by SA4. Imed: AF session in QoS has the domain name. Thorsten: Missed the domain name. Reformulation of the problem in the SA2 domain as well. More discussion on this document.
 		revised No S4‑210311 S4‑210106
    S4‑210232 Corrections on Procedures and APIs for Downlink and Uplink Streaming Qualcomm Incorporated, BBC, Ericsson LM draftCR Agreement Yes
Yes
 		agreed No   S4‑210134
    S4‑210226 3GPP DASH – More relevant than ever? Qualcomm Incorporated, Interdigital, Comcast, Orange, Dolby Laboratories, Tencent, Ericsson. BBC, Interdigital discussion Agreement Yes
Yes
 		agreed No   S4‑210140
    S4‑210241 TS 26.512 on removal of editor’s notes and handling of multiple AF instances Ericsson LM draftCR Agreement Yes
Yes
 		agreed No   S4‑210158
8.6 FS_5GMS_Multicast (Feasibility Study on Multicast Architecture Enhancements for 5GMSA) S4‑210045 [FS_5GMS_Multicast] Key issue on re-use of MBMS service layer Qualcomm Incorporated pCR Agreement Yes
Yes
 		not pursued No    
    S4‑210046 [FS_5GMS_Multicast] Client Architectures Qualcomm Incorporated pCR Agreement Yes
Yesclause 7 of 26.347 is the reference. Should add media player in the non 5GMS case. Thomas: not sure if a media player to be added as it would load the 5GMS Cedric: Use case of no 5GMS but only a DASH player. Thomas: the first figure is independent of 5GMS, so it can be added through a separate figure. Charles: Enquires about the control asects of API. Thomas: MBS is more aligned to 26.347. Richard: is it a case where the media player requests over MBS7 and media client fails through receive it . Thomas: for hybrid, who makes the decision and redirects the requests. Richard: should not the reference architecure describes all the possibilties. Thomas: dynamic management is a challenge. There could be multicast and unicast scenarios. Richard: I agree that thre are two cases - MBSu and MBSc. There is a 3rd option where the unicast request terminates in the AS. Cedric: There is similar contribution (B2 scenario) from Thorsten on the same and not exactly aligned with the current document. Thorsten: in B2 scenario, the NEF is located a bit differently. Thomas: haven't contributed to the network side of it. Decision: The r01 of the current document is revised to S4-210236
 		revised No S4‑210236  
    S4‑210047 [FS_5GMS_Multicast] Hybrid use case Qualcomm Incorporated pCR Agreement Yes
Yes
 		revised No S4‑210237  
    S4‑210048 [FS_5GMS_Multicast] Interworking with EPC and enTV Qualcomm Incorporated pCR Agreement Yes
Yes
 		revised No S4‑210238  
    S4‑210079 pCR TR 26.802 - key issues on MABR support in 5GMS TELUS, BBC, Qualcomm, Ericsson, Telecom Italia, Enensys pCR Agreement Yes
Yes
 		agreed No   S4aI201117
    S4‑210080 [FS_5GMS_Multicast] Updated time and work plan TELUS Work Plan   Yes
Yes
 		revised No S4‑210234  
    S4‑210081 draft TR 26.802 TELUS draft TR Agreement Yes
Yes
 		revised No S4‑210233  
    S4‑210152 Review of xMB-C wrt User Plane properties Ericsson LM, BBC pCR Agreement Yes
Yes
 		agreed No    
    S4‑210153 New Key Issue on 'Collaboration and deployment scenarios' Ericsson LM pCR Agreement Yes
YesDiscussion during 3rd Feb online session: This document is a bit similar to the S4-210236. Thomas: the contribution has cople of client boxes included. Thorsten: to simplify the architecture. Thomas: it is important to address the level of service. Richard: Compliance with 3GPP specification is not enough to distinguish between collaboration. Thorsten: This is based on the transperent deliveries in 26.346. The revision 2 of this document was revised.
 		revised No S4‑210239  
    S4‑210154 Discussion on the scope of FS_5GMS-Multicast wrt 5MBS Ericsson LM discussion Agreement Yes
YesThe discussion revolves on the 1. looking on the preogress, focus on user service architecture. 2. to study more in the group before sending to SA6/SA2. Some of the MB2 should also be studied in SA4. Chiar: are we just leveraging streaming in the light of MBS. Is it is the xMB or M1. Thomas: should all service use xMB or MB2 ? Chair: with regards to service requirements, if xMB is used, then SA4 does stage 3 as well. Thorsten: It's CT3's scope. From LS from SA2, SA4 is asked to ask into the MBU. Peng: to address the key issues in MBS media streaming. Chair: the service requirements of MBS is sought after. Thorsten: the existing one from the LTE can be taken. Chair: however, it would be a strong assumption. Now that SA4 is tasked to define the MBSu, then it would be nice to ask SA6 and SA2 asking clarification. Thorsten: to draft a LS. Chair: to draft LS Qi Pan: some functionalities has been moved to 5GC. So, SA2 is requried to define the scope of MBSu. We can define the delivery regardless of the payload. Thorsten: moving to non-5GMS MBS service specification, might not loop in SA6 fot that purpose.
 		revised No S4‑210244  
    S4‑210236 [FS_5GMS_Multicast] Client Architectures Qualcomm Incorporated pCR Agreement Yes
Yes
 		revised No S4‑210249 S4‑210046
    S4‑210249 [FS_5GMS_Multicast] Client Architectures Qualcomm Incorporated pCR Agreement Yes
Yes
 		agreed No   S4‑210236
    S4‑210237 [FS_5GMS_Multicast] Hybrid use case Qualcomm Incorporated pCR Agreement Yes
Yes
 		revised No S4‑210250 S4‑210047
    S4‑210250 [FS_5GMS_Multicast] Hybrid use case Qualcomm Incorporated pCR Agreement Yes
Yes
 		agreed No   S4‑210237
    S4‑210238 [FS_5GMS_Multicast] Interworking with EPC and enTV Qualcomm Incorporated pCR Agreement Yes
Yes
 		revised No S4‑210251 S4‑210048
    S4‑210251 Interworking with EPC and enTV Qualcomm Incorporated pCR Agreement Yes
Yes
 		revised No S4‑210308 S4‑210238
    S4‑210308 Interworking with EPC and enTV Qualcomm Incorporated pCR Agreement Yes
Yes
 		agreed No   S4‑210251
    S4‑210233 TR 26.802 Multicast Architecture Enhancement for 5G Media Streaming TELUS draft TR Agreement Yes
Yes
 		revised No S4‑210245 S4‑210081
    S4‑210239 New Key Issue on 'Collaboration and deployment scenarios' Ericsson LM pCR Agreement Yes
Yes
 		agreed No   S4‑210153
    S4‑210243 Draft revised SID FS_5GMS_Multicast Ericsson LM SID revised Agreement Yes
Yes
 		revised No S4‑210248  
    S4‑210312 LS to SA2 and SA6 on FS_5GMS_Multicast and 5MBS MBS LS out discussion Yes
Yes
 		revised No S4‑210319 S4‑210242
    S4‑210296 Discussion on 3GPP OpenAPI documentation guidelines Ericsson LM discussion discussion Yes
Yes
 		revised No S4‑210309  
    S4‑210309 Discussion on 3GPP OpenAPI documentation guidelines Ericsson LM discussion discussion Yes
YesThere is a bit of tension between SA and CT groups. The guidelines are open to the openAPI specifications irrespective of 5G. There should be a 3GPP harmonization way of working. Since SA4 is doing all the openAPI specification, the consequence for SA4. As per the existing guideline, S4-210174 (M1 OpenAPI spec) and S4-210231 (M5 OpenAPI Spec) needs to be updated according to the guidelines in TS 21.900 Clause 5B. Chair: we can't produce yaml files in a good way by tomorrow. Power to agree a CR for implementation of annex to openAPIs in 26.512.
 		noted No   S4‑210296
8.7 FS_EMSA (Feasibility Study on Streaming Architecture extensions For Edge processing) S4‑210083 Clarification of EAS discovery solutions during UE mobility in SA2 HUAWEI Technologies Japan K.K. pCR Agreement Yes
YesDiscussion on revision 2 of the document: The discussion revolved around the UE route slection procedure for PDU sessions. There were comments on the DS sessions of the type authoritative and recursive. Thorsten, Ericsson mentioned that operators typically deploy the latter for resolving third-party domain names for which they are not authoritative.
 		revised No S4‑210253  
    S4‑210253 Clarification of EAS discovery solutions during UE mobility in SA2 HUAWEI Technologies Japan K.K. pCR Agreement Yes
Yes
 		revised No S4‑210304 S4‑210083
    S4‑210304 Clarification of EAS discovery solutions during UE mobility in SA2 HUAWEI Technologies Japan K.K. pCR Agreement Yes
Yes
 		agreed No   S4‑210253
    S4‑210084 Overview of concluded edge application relocation solutions in SA2 HUAWEI Technologies Japan K.K. discussion Agreement Yes
Yes
 		revised No S4‑210313  
    S4‑210313 Overview of concluded edge application relocation solutions in SA2 HUAWEI Technologies Japan K.K. discussion Agreement Yes
Yes
 		agreed No   S4‑210084
    S4‑210085 Discussion for architecture mapping from SA6 to SA4 HUAWEI Technologies Japan K.K. discussion Agreement Yes
YesHuawei presented the proposal. Imed, Qualcomm: Concerns about the second part of the architectural mapping by putting additional layer. This has been discussed in S4-210161 already. There is no need to put an interface between AF and EES in the architecture. There can be private interfaces at this juncture. Qi, Huawei: From SA6 presepctive, a specific EAS can be defined having specific 5GMS AF unctionalities. Iraj, Tencent: To avoid the confusion, the realtionship without having any new interface could be a way forward. Richard, BBC: It’s a low-level diagram. Chair: The diagram in S4-210161 is preferred. Thorsten: Supports BBC Chair: Deployment options could be added to the Annex. Of 26.512 when there is a nromative work on the same. Iraj: Good to capture this discussion in the TR. Chair: To put an Editor's Note in the TR.
 		revised No S4‑210295  
    S4‑210100 FS_EMSA: Architecture update Tencent discussion Agreement Yes
YesThe discussion revolved around the call flows where the Chair mentioned that 3GMS AS and AF to be updated to 5GMS. Finally call flow in section 5 and 6 are agreed with changes.
 		endorsed No    
    S4‑210120 On EMSA architecture Samsung Electronics Co., Ltd discussion Agreement Yes
Yes
 		noted No    
    S4‑210161 EMSA architecture Qualcomm Wireless GmbH discussion Agreement Yes
YesThe discussion was in the lines of difining functionalities of edge enabled 5GMS. Iraj: Proposed to be called as edge enabled 5GMS AS - but each of the functions are a mix of two entities. Richard: simplifying diagram can help to deduce things better. Iraj: better to come up with a diagrams howing interaction between different modules. EAS and EES are effectively invisible in this diagram. Imed: Edge enabled 5GMS AS. Chair: not clear on edge enabled 5GMS AS. A 5GMS AF may support additional fucntionalities somewhere. There has been reservation on defining new entities in the architecture diagram - which can have new functionalaties.
 		revised No S4‑210254  
    S4‑210162 Split Rendering Use Case Walkthrough Qualcomm Wireless GmbH discussion   Yes
Yes
 		revised No S4‑210252  
    S4‑210295 Discussion for architecture mapping from SA6 to SA4 HUAWEI Technologies Japan K.K. discussion Agreement Yes
Yes
 		noted No   S4‑210085
    S4‑210254 EMSA architecture Qualcomm Wireless GmbH discussion - Yes
Yes
 		revised No S4‑210320 S4‑210161
    S4‑210252 Split Rendering Use Case Walkthrough Qualcomm Wireless GmbH discussion - Yes
Yes
 		noted No   S4‑210162
8.8 FS_5GMS_EXT (Study on 5G media streaming extensions) S4‑210049 [FS_5GMS-EXT] Key Topic Content Preparation Qualcomm Incorporated pCR Agreement Yes
YesThe discussion revolves around RIST and SRT. Thorsten: Is it a downlink distribution ? Clarification required. Thomas: It is an ingest to downlink. Richard: The scope to be defined which says ingest for D/L or the content prepapartion for U/L. Thorsten: Content preparation can be applied to both U/L and D/L. Iraj: It might be applicable to all possible scenarios. Chair: The intention of FFS is to be done later in next Release ? Thomas: It was for D/L. Still bit sceptical on uplink ingest. Imed: Whether TDD or FFS, has not been decided as of now.# Chair: To be merged with 101 and to remove the FFS as of now.
 		revised No S4‑210306  
    S4‑210050 [FS_5GMS-EXT] Key Topic Traffic Identification Qualcomm Incorporated pCR Agreement Yes
Yes
 		revised No S4‑210307  
    S4‑210051 [FS_5GMS-EXT] Key Topic Additional / New transport protocols Qualcomm Incorporated pCR Agreement Yes
Yes
 		revised No S4‑210298  
    S4‑210298 [FS_5GMS-EXT] Key Topic Additional / New transport protocols Qualcomm Incorporated pCR Agreement No
Yes
 		agreed No   S4‑210051
    S4‑210052 [FS_5GMS-EXT] Key Topic Uplink media streaming Qualcomm Incorporated pCR Agreement Yes
Yes
 		revised No S4‑210299  
    S4‑210053 [FS_5GMS-EXT] Key Topic Background traffic Qualcomm Incorporated pCR Agreement Yes
Yes
 		revised No S4‑210300  
    S4‑210054 [FS_5GMS-EXT] Key Topic Content Aware Streaming Qualcomm Incorporated pCR Agreement Yes
YesThomas, Qualcomm presented this document. Richard: ok to study this proposed pCR. It's about the bank of encoders, or the selction of algorithms that could deal with various tehcnologies by content providers.
 		agreed No    
    S4‑210055 [FS_5GMS-EXT] Key Topic Network Event usage Qualcomm Incorporated pCR Agreement Yes
Yes
 		revised No S4‑210301  
    S4‑210056 [FS_5GMS-EXT] Key Topic Per-application-authorization Qualcomm Incorporated pCR Agreement Yes
Yes
 		agreed No    
    S4‑210057 [FS_5GMS-EXT] Key Topic Support for encrypted and high-value content Qualcomm Incorporated pCR Agreement Yes
Yes
 		revised No S4‑210302  
    S4‑210302 [FS_5GMS-EXT] Key Topic Support for encrypted and high-value content Qualcomm Incorporated pCR Agreement Yes
Yes
 		agreed No   S4‑210057
    S4‑210058 [FS_5GMS-EXT] Key Topic Scalable distribution of unicast Live Services Qualcomm Incorporated pCR Agreement Yes
Yes
 		revised No S4‑210303  
    S4‑210303 [FS_5GMS-EXT] Key Topic Scalable distribution of unicast Live Services Qualcomm Incorporated pCR Agreement Yes
Yes
 		agreed No   S4‑210058
    S4‑210101 FS_5GMS_EXT: Content preparation deployment scenarios and functional description Tencent discussion Agreement Yes
YesMerged into S4-210306.
 		merged No    
    S4‑210136 First version of TR 26.804 "Study on 5G media streaming extensions" Ericsson LM draft TR   Yes
Yes
 		revised No S4‑210305  
    S4‑210155 Collaboration Scenarios for Uplink streaming Ericsson LM pCR Agreement Yes
YesMerged to S4-210299.
 		merged No    
    S4‑210156 Discussion on Traffic Identification Ericsson LM pCR Agreement Yes
YesThis document identifies collaboration models and review of existing protocols. Members discussed the rev 02 of this submission. A study on HTTP protocols for Youtube was suggested to be studied and UPF should be able to determine the new protocol. Members felt that this document could be merged with S4-210050. Thorsten Lohmar, Ericsson suggested a change in the diagram from UDF to UDR. Chair suggested to move the HTTP protool study into the annex. This document has to be merged with 50 and this document will be the basis for the same. [Merged with 307]
 		merged No S4‑210307  
    S4‑210163 FS_5GMS_EXT: Uplink media streaming missing features Tencent discussion Agreement Yes
YesMerged to S4-210299.
 		merged No    
8.9 New Work Items and Study Items S4‑210160 New Study Item on Media Production over 5G NPNs Ericsson LM, AT&T, BBC, B-Com, Dolby Laboratories Inc., EBU, Orange SID new Agreement Yes
Yes
 		revised No S4‑210240  
8.10 Others including TEI                      
8.11 Review of the future work plan (next conf. call meeting dates, hosts)                      
8.12 Any Other Business                      
8.13 Close of the session                      
9 Speech Quality (SQ) SWG S4‑210264 (reserved) SQ other discussion No
No
 		reserved No    
    S4‑210265 (reserved) SQ other discussion No
No
 		reserved No    
    S4‑210266 (reserved) SQ other discussion Yes
No
 		reserved No    
9.1 Opening of the session                      
9.2 Registration of documents                      
9.3 Liaison Statements                      
9.4 CRs to Features in Release 16 and earlier, and other contributions on terminal acoustics                      
9.5 ATIAS (Terminal Audio quality performance and Test methods for Immersive Audio Services) S4‑210137 Evaluation of simplified communication systems for ATIAS HEAD acoustics GmbH discussion Discussion Yes
Yes
 		not treated No    
9.6 HaNTE (Handsets Featuring Non-Traditional Earpieces) S4‑210089 Updated results of HaNTE round robin test HEAD acoustics GmbH discussion Information Yes
Yes
 		noted No    
    S4‑210167 Report on HaNTE round robin test for Lab 3 Orange discussion Discussion Yes
Yes
 		noted No    
9.7 HInT (Extension for headset interface tests of UE)                      
9.8 New Work Items and Study Items                      
9.9 Any Other Business                      
9.10 Close of the session                      
10 Video SWG S4‑210215 Draft TR 26.998 v.0.4 3GP SA4 draft TR Decision Yes
Yes
 		revised No S4‑210267  
    S4‑210269 pCR template on the 5G system mapping Qualcomm Incorporated other discussion Yes
Yes
 		agreed No    
    S4‑210276 CR to 26.511 Video SWG CR Agreement Yes
Yes
 		revised No S4‑210282  
10.1 Opening of the session                      
10.2 Registration of documents                      
10.3 Reports and liaisons from other groups S4‑210274 Reply LS on on 8K VR 360º operation points 3GPP TSG SA WG4 (SA4) LS out Agreement Yes
Yes
 		revised No S4‑210329 S4‑210009
10.4 CRs to features in Release 16 and earlier                      
10.5 8K_VR_5G (Operation Points for 8K VR 360 Video over 5G) S4‑210027 8K_VR_5G: Proposed Time Plan v.0.1.0 Intel (Rapporteur) Work Plan Agreement Yes
Yes
 		revised No S4‑210277  
    S4‑210028 Operation Points for 8K VR 360 Video Intel draftCR Agreement Yes
Yes
 		revised No S4‑210272  
    S4‑210272 Operation Points for 8K VR 360 Video Intel draftCR Agreement Yes
Yes
 		agreed No   S4‑210028
    S4‑210029 Decoding Capabilities and Operation Points for 8K VR 360 Video over 5GMS Intel draftCR Agreement Yes
YesMerged to S4-210275
 		merged No S4‑210275  
    S4‑210030 Proposed Way Forward for 8K Viewport-Independent Delivery Intel discussion Agreement Yes
Yes
 		agreed No    
    S4‑210059 Comments on draftCR for 8K_VR Qualcomm Incorporated draftCR Agreement Yes
Yes
 		revised No S4‑210273  
    S4‑210060 8K Decoding Capabilities Qualcomm Incorporated draftCR Agreement Yes
Yes
 		revised No S4‑210275  
    S4‑210273 Comments on draftCR for 8K_VR Qualcomm Incorporated draftCR Agreement Yes
Yes
 		agreed No   S4‑210059
    S4‑210275 8K Decoding Capabilities Qualcomm Incorporated draftCR Agreement Yes
Yes
 		agreed No   S4‑210060
10.6 FS_VR_CoGui (Feasibility Study on VR Streaming Conformance and Guidelines)                      
10.7 FS_5GVideo (Feasibility Study on 5G Video Codec Characteristics) S4‑210061 Proposed Updated Work Plan for FS_5GVideo Qualcomm Incorporated Work Plan Agreement Yes
Yes
 		revised No S4‑210210  
    S4‑210062 TR26.955: Proposed Editor's Update Qualcomm Incorporated draft TR Agreement Yes
Yes
 		revised No S4‑210097  
    S4‑210063 pCR26.955: Metrics Qualcomm Incorporated pCR Agreement Yes
Yes
 		agreed No    
    S4‑210064 pCR26.955: Data Management Qualcomm Incorporated pCR Agreement Yes
Yes
 		agreed No    
    S4‑210065 pCR26.955: Proposed anchors for FullHD Streaming Qualcomm Incorporated pCR Agreement Yes
Yes
 		withdrawn Yes    
    S4‑210066 pCR26.955: Proposed anchors for Messaging and Social Sharing Qualcomm Incorporated pCR Agreement No
Yes
 		withdrawn Yes    
    S4‑210067 pCR26.955: Reference Sequences Qualcomm Incorporated pCR Agreement Yes
Yes
 		agreed No    
    S4‑210097 TR26.955: Proposed Editor's Update Qualcomm Incorporated draft TR Agreement Yes
Yes
 		agreed No   S4‑210062
    S4‑210098 5GVideo-Anchor tuple Metrics InterDigital France R&D, SAS discussion   Yes
Yes
 		agreed No    
    S4‑210105 [FS_5GVideo] pCR26.955: Updated EVC verification test results Samsung, Qualcomm pCR Agreement Yes
Yes
 		revised No S4‑210208  
    S4‑210131 4K-HDR Test Material Selection for FS_5GVideo ATEME, InterDigital, Ericsson pCR Agreement Yes
Yes
 		revised No S4‑210209  
    S4‑210165 Proposed updates on Gaming sequences description Tencent, InterDigital pCR Agreement Yes
Yes
 		agreed No    
    S4‑210168 Proposed updates on Screen Content sequences description Tencent, InterDigital pCR Agreement Yes
Yes
 		agreed No    
    S4‑210208 [FS_5GVideo] pCR26.955: Updated EVC verification test results Samsung, Qualcomm pCR Agreement Yes
Yes
 		agreed No   S4‑210105
    S4‑210209 4K-HDR Test Material Selection for FS_5GVideo ATEME, InterDigital, Ericsson pCR Agreement Yes
Yes
 		noted No   S4‑210131
    S4‑210205 Screen Content scenario evaluation results InterDigital France R&D, SAS discussion Discussion Yes
Yes
 		noted No    
    S4‑210206 MS-SSIM Definition InterDigital France R&D, SAS discussion discussion Yes
YesThe document S4-210206 is agreed with the following 2 modifications: 1) Clause 5.5.2: The max PSNR for a frame is fixed to 999.99 dB. 2) Replacement of a. An informative overview of metrics is provided below based on equations. However, the reported metrics in this TR are defined and reported based on the metric output of a computer software as defined in Annex F. By b. An overview of the metrics is provided below. These metrics are implemented in the software defined in Annex F. This software is used to compute and report all the metrics.
 		agreed No    
10.8 FS_XRTraffic (Feasibility Study on Typical Traffic Characteristics for XR Services and other Media) S4‑210068 Proposed Updates to Work Plan for FS_XRTraffic Qualcomm Incorporated Work Plan Agreement Yes
YesRequest SA4 to approve the special power in two ashoc calls for: 1. sending LS to RAN 1 in March 2. Sending the updated TR to SA#91. 3. To extend the timeline fro XR_Traffic work till end of 2021.
 		revised No S4‑210281  
    S4‑210069 [FS_XRTraffic] Proposed Updated to Work Item Description Qualcomm Incorporated discussion Agreement Yes
Yes
 		revised No S4‑210211  
    S4‑210070 [FS_XRTraffic] Proposed Annex to TR26.925 Qualcomm Incorporated discussion Agreement Yes
Yes
 		agreed No    
    S4‑210071 [FS_XRTraffic] Proposed Additional Traffic Models Qualcomm Incorporated discussion Agreement No
Yes
 		agreed No    
    S4‑210072 [FS_XRTraffic] Traffic Model Overview and Status Qualcomm Incorporated discussion Agreement Yes
Yes
 		agreed No    
    S4‑210073 [FS_XRTraffic] From Traces to Statisical Models Qualcomm Incorporated discussion Agreement Yes
Yes
 		agreed No    
    S4‑210074 [FS_XRTraffic] Proposed Quality Evaluation Framework Qualcomm Incorporated discussion Agreement Yes
YesThomas: You can decode upto the first packet being lost. So, the prefix could be used for decoding. This is the config for a receiver but in quality evaluation, this model could still be applied. Gilles: How to compute the quality of the damaged picture including the propagation of all the blocks for the missing segment. Thomas: The coding unit is lost and there is a mapping of the damaged ones. Differentiation between lost and damaged at the CU level. Gilles: Assesment of the quality of damage in case of a complete loss. Qi: The evaluation parametets/tools in Gitlab needs to be available. Will provide the required information to the RAN CR. Thomas: Should be LS instead of CR ?
 		agreed No    
    S4‑210075 [FS_XRTraffic] Proposed Reply LS to SA2 (S2-2009227) Qualcomm Incorporated LS out Agreement Yes
Yes
 		revised No S4‑210283  
    S4‑210121 Proposed Content Delivery Models and Quality Evaluation for VR1 China Mobile Com. Corporation discussion Agreement Yes
YesDiscussion revolved around the use of ITU T P.910 CMCC: okay, to remove the subjective video quality assesment method. Gilles: to put a note stating that, subjective quality testing can be an alternative to provide quality assesment. CMCC: it is not proper for simulative system, so it is okay to remove this part and if there are other ways, then it can be added later. Thomas: We need to look into it for the view port dependent streaming and it needs to mulled over on how the simulation has to be done. S4-210071 has relevant information than this current one and these documents can be merged to a permanent document. Gilles: are the contents of this current document is agreeable ? Thomas: agree Decision: this information of this document will be merged with 71 and subsequently included in the Permanent document.
 		agreed No    
    S4‑210122 Quality Measurement Consideration for VR1 China Mobile Com. Corporation discussion   Yes
Yes
 		agreed No    
    S4‑210125 [FS_XRTraffic] Proposed Update to PD Qualcomm CDMA Technologies discussion Agreement Yes
Yes
 		revised No S4‑210278  
    S4‑210211 [FS_XRTraffic] Proposed Updated to Work Item Description Qualcomm Incorporated WID revised Agreement Yes
YesQi, Huawei: To document a TS for XR_Traffic, however, there could be some more serivce type could be added into this WID. By June 2021, the XRTraffic could be completed by June 2021 otherwise, it would be a strech over 9 months from the initial deadline. Gilles: as per the comment, should the study be stopped in between June, 2021 to March,2022 Thomas: SI alsways included more than XR traffic. Just that the XR_traffic took longer due to COVID and e-meetings were slow. Rel 17 extended from 6 to 9 months. Lei, Tencent: It could be more clear to Thomas: XR_Traffic is terminated in June 2021. It could be added to the remarks. Gilles: If SA4 is not able to provide the information to SA2 for stage 2, then it falls into the stage 3 timeframe. Lei, Tencent: This kind of note can be confusing. This is common in WID to clarify the same. Thomas, Qc: all XR traffic related work to be completed by June 2021. This has been added in the remarks section of the WID template.
 		revised No S4‑210280 S4‑210069
    S4‑210213 Support of 5G Glass-type Augmented Reality / Mixed Reality (AR/MR) devices Qualcomm Incorporated draft TR Agreement Yes
Yes
 		agreed No    
    S4‑210212 Discussion Paper on SA4 support for XR and other media application in 5G Qualcomm Incorporated discussion discussion Yes
YesLei, Tencent: This is a good discussion paper, however it would be nice to discuss it in SA instead of SA4. Gilles: this document states that how SA4 can be more efficient ,in terms of answering the questions asked to the group. Qi, Huawei: In order to prepare answers to be prepared for answers from various WG group (SA1,RAN1,SA2), most of response is documented in 211. This is however a good discussion document and can be mapped to a PD ? James, AT&T: This new proposal is quite useful which partciularly talks about services and evaluation metrics. Also in technical deployment, user,operator or 3rd party - this is another aspect where PD can be proposed. Lei, Tencent: If the intern group co-ordiantion needs to be improved, it should be discussed at the plenary level. Futher, SA1 has a different release planning relative to SA4. Thomas, Qualcomm:SA4 delegates and experts have to given the time to develop on XR traffic models and SA4 is the most relevant group to work on 5G codecs, and multimedia. James, AT&T: Support Qualcomm in this issue. Gilles: Revise the contribution and present to the SA4 closing plenary. Thomas: some time needed to analyse the use cases - and to be extended to antoher meeting cycle. Some more time needed to identify these services. Chris, Vodafone: agreed.
 		revised No S4‑210279  
10.9 FS_5GSTAR (Feasibility Study on 5G Glass-type AR/MR Devices) S4‑210013 Proposed Architectures for AR Conversational HiSilicon Technologies Co. Ltd pCR   No
Yes
 		withdrawn Yes    
    S4‑210014 Editorial corrections of the use cases on AR Conversational HiSilicon Technologies Co. Ltd pCR   Yes
Yes
 		revised No S4‑210214  
    S4‑210076 [FS_5GSTAR] Device Names Qualcomm Incorporated pCR Agreement Yes
YesRyan: Not necessary to run through the previous discussion. However, the current nomenclature needs to be changed. Gabin: To find good name for glasses. Thomas: there is no proposal on 'good names' except for the ones existing. Gilles: the proposal is to agree on 'good names' and trigger email discussion to find appropriate names. Thomas: These names are requested to be taken as baseline nomenclature: - Type 1: 5G Standalone AR HMD - Type 2: 5G Standalone Smart AR glasses - Type 3: 5G Wireless Tethered AR glasses - Type 4: 5G Wired Tethered AR glasses Gilles: Agreed. Ali: Often confused by present nomenclature and there is a scope to improve this contribution. Thomas: To make this exercise sucessful, there should be more companies participating in the email discussion. Gabin: Will you have telco/email ? Gilles: Having an offline dedicated email thread. Propose to use the video swg email reflector. Mary: Significance of noting ? Gilles: If the document status is not going anyway, then the document is noted. Decision in 3rd Feb Call: No decision as of now.
 		revised No S4‑210224  
    S4‑210224 [FS_5GSTAR] Device Names Qualcomm Incorporated pCR Agreement Yes
Yes
 		agreed No   S4‑210076
    S4‑210077 [FS_5GSTAR] Use Case to Architecture Mappings Qualcomm Incorporated pCR Agreement Yes
Yesokia: is the aim of ht edocument is to analyse the type of delivery. What is ment by 'more simple use cases' Thomas: TO bring the architecture in a simplied model where call flows can be eased. Also, baseline usecases can be identified to get down to the call flows. Nokia: transformation of the use case is necessary to be brought up. Gilles: This contribution is more considered as the way forward.
 		agreed No    
    S4‑210078 [FS_5GSTAR] OpenXR and Khronos Qualcomm Incorporated pCR Agreement Yes
YesRyan, Samsung: more discussion on the meaning of 'reference' is needed. Thomas, Qc: The platform where the application could function over the network. Gilles: these can be the candidates technologies to be the reference for openXR Jaeyon: A study on the Khronos is necessary as acandidate technologity before making them as a 'reference'.
 		agreed No    
    S4‑210110 FS_5GSTAR: Bidirectional media flows Samsung Electronics Iberia SA discussion Agreement Yes
Yes
 		agreed No    
    S4‑210111 FS_5GSTAR: Unidirectional media flow from server to UE Samsung R&D Institute UK discussion Agreement Yes
Yes
 		revised No S4‑210216  
    S4‑210112 FS_5GSTAR: Unidirectional media flow from UE to server Samsung R&D Institute UK discussion Agreement Yes
Yes
 		agreed No    
    S4‑210113 Draft TR 26.998 Samsung R&D Institute UK draft TR Agreement Yes
YesThere was discussion between the other group members on the contributions added to this draft TR. Thomas: urge to publish all the agreements from the meeting. There would be one oneput document taking all the agreements in the previous adhoc meeting.
 		revised No S4‑210213  
    S4‑210114 FS_5STAR: Permanent Document v0.2.0 Samsung R&D Institute UK other Agreement Yes
YesComents on reference handling to be done by the rapporteur. There were no other comments and rev1 of this Tdoc has been agreed.
 		revised No S4‑210214  
    S4‑210115 5GSTAR: Proposed Updates to Work Plan Samsung R&D Institute UK Work Plan Agreement Yes
Yes
 		revised No S4‑210222  
    S4‑210124 [5G_STAR] pCR Proposed architecture for streaming volumetric video Fraunhofer HHI pCR Agreement Yes
YesThomas: you render the screen which includes the volumetric video and produce the video creation of the screen. Yago,FFH: According to the Fig.2, where a volumetric video is places in a real screen. Thomas: Is there more to rendering the volumetric video. Yago, FFH: only the volumetric video. Imed, Qc: split rendering is quite complex and then getting 2D video. When tracking is done, some knowledge of local environement is needed. Yago, FFH: In this case, the instructors are rendered and it is a real screen. Imed, Qc: Not in favour of disparity because the screen camera could automatically render the video. Gilles: to have detailed discussion untill tomorrow. This document to be mapped to a permanent document. Imed: the use case can be documented because, still having reservations regarding the rendering processes. Thomas: the comments can be taken into accound before converting it into a PD. Gilles: revision suggested.
 		revised No S4‑210219  
    S4‑210214 Editorial corrections of the use cases on AR Conversational HiSilicon Technologies Co. Ltd pCR - Yes
Yes
 		agreed No   S4‑210014
    S4‑210151 Gaps and architecture extensions for conversational AR services Ericsson LM discussion Agreement Yes
YesThis document was decided to be integrated into the permanen document. Thomas: Then fate of the comments need to be decided. Gilles: propose to revise to include the comments.
 		revised No S4‑210220  
    S4‑210173 [FS_5GSTAR] pCR on Use case on AR IoT Beijing Xiaomi Electronics pCR Agreement Yes
YesThomas: need to clarify if there are immersive split rendering aspects are put in. Mary-Luc: it is not 'split rendering'. Relation with 5G: as there are more devices to be used in 5G, and this pCR becomes relevant.
 		revised No S4‑210221  
    S4‑210216 FS_5GSTAR: Unidirectional media flow from server to UE Samsung R&D Institute UK discussion Agreement Yes
Yes
 		agreed No   S4‑210111
    S4‑210222 5GSTAR: Proposed Updates to Work Plan Samsung R&D Institute UK Work Plan Agreement Yes
Yes
 		revised No S4‑210271 S4‑210115
    S4‑210219 [5G_STAR] pCR Proposed architecture for streaming volumetric video Fraunhofer HHI pCR Agreement Yes
Yes
 		agreed No   S4‑210124
    S4‑210220 Gaps and architecture extensions for conversational AR services Ericsson LM discussion Agreement Yes
Yes
 		agreed No   S4‑210151
    S4‑210221 [FS_5GSTAR] pCR on Use case on AR IoT Beijing Xiaomi Electronics pCR Agreement Yes
YesIs this proposed to be a permanent document or a TR ? Gilles: a TR is proposed. We can further do the mapping to 5G device systems in future.
 		agreed No   S4‑210173
    S4‑210217 Use case to 5G system mapping template Samsung et.al pCR discussion Yes
Yes
 		revised No S4‑210268  
    S4‑210218 Updated Permanent Doc FS_5GSTAR Permanent Document v0.3.0 Samsung Electronics Co., Ltd. (Rapporteur) Work Plan Agreement Yes
Yes
 		agreed No    
    S4‑210268 Use case to 5G system mapping Way forward Video SWGSamsung, Qualcomm, Interdigital, Fraunhofer, Ericsson, Tencent, Xiaomi, and Dolby pCR discussion Yes
Yes
 		agreed No   S4‑210217
10.10 New Work Items and Study Items                      
10.11 Liaisons and Liaison Responses S4‑210086 Discussion on LS on New Standardized 5QIs for 5G-AIS(S2-2009227) Tencent discussion Decision Yes
Yes
 		noted No    
    S4‑210087 Draft Reply LS to S2-2009227 Tencent LS out Agreement Yes
YesMerged with S4-210283
 		merged No S4‑210283  
10.12 Any Other Business                      
10.13 Close of the session                      
11 Multimedia Telephony Service for IMS (MTSI) SWG S4‑210182 Draft CR Updates on Camera Calibration for Network-based Stitching Intel, Nokia Corporation draftCR Agreement Yes
Yes
 		revised No S4‑210189  
    S4‑210189 Draft CR Updates on Camera Calibration for Network-based Stitching Intel, Nokia Corporation draftCR Agreement Yes
Yes
 		agreed No   S4‑210182
    S4‑210183 Improved text on SDP for ITT4RT Nokia Corporation draftCR discussion Yes
Yes
 		agreed No    
    S4‑210184 Introduction of pause/resume functionality Qualcomm Wireless GmbH, Intel other discussion Yes
Yes
 		agreed No    
    S4‑210185 Updates on Introduction of Pause/Resume in ITT4RT Qualcomm Wireless GmbH, Intel other discussion Yes
Yes
 		agreed No    
    S4‑210186 Formats and protocols for transport of non-A/V overlays Intel, Qualcomm Incorporated, Nokia Corporation, other discussion Yes
Yes
 		agreed No    
    S4‑210187 On SEI Messages for ITT4RT Intel other discussion Yes
Yes
 		revised No S4‑210199 S4‑210025
    S4‑210199 On SEI Messages for ITT4RT Intel other discussion Yes
Yes
 		agreed No   S4‑210187
    S4‑210188 Improved text on Overlay configuration for ITT4RT Nokia Corporation other discussion Yes
Yes
 		revised No S4‑210198  
    S4‑210203 (reserved) MTSI SWG other discussion No
No
 		reserved No    
    S4‑210204 (reserved) MTSI SWG other discussion No
No
 		reserved No    
11.1 Opening of the session                      
11.2 Registration of documents                      
11.3 Reports and liaisons from other groups                      
11.4 CRs to Features in Release 16 and earlier                      
11.5 ITT4RT (Support of Immersive Teleconferencing and Telepresence for Remote Terminals) S4‑210015 Frame packing of overlays Nokia Corporation discussion   Yes
Yes
 		revised No   S4‑210181
    S4‑210020 Proposed Timeplan for ITT4RT (v0.10.0) Intel, Nokia Corporation (ITT4RT Rapporteurs) Work Plan Agreement Yes
Yes
 		revised No S4‑210176  
    S4‑210021 ITT4RT Permanent Document - Requirements, Working Assumptions and Potential Solutions (v0.10.0) Intel, Nokia Corporation (ITT4RT Rapporteurs) other Agreement Yes
Yes
 		agreed No    
    S4‑210022 Draft CR 26.114 Video Support for ITT4RT Intel draftCR Agreement Yes
Yes
 		agreed No    
    S4‑210023 Draft CR Updates on Camera Calibration for Network-based Stitching Intel draftCR Endorsement Yes
Yes
 		revised No S4‑210183  
    S4‑210024 Usage of the IMS Data Channel in ITT4RT Intel discussion Agreement Yes
Yes
 		revised No S4‑210186  
    S4‑210025 On SEI Messages for ITT4RT Intel discussion Agreement Yes
Yes
 		revised No    
    S4‑210118 Improved text on SDP for ITT4RT Draft CR Nokia Corporation draftCR Agreement Yes
Yes
 		revised No S4‑210183  
    S4‑210119 Conditional overlays for ITT4RT Nokia Corporation discussion Agreement Yes
Yes
 		noted No    
    S4‑210126 ITT4RT: On text for media configuration Samsung Electronics Iberia SA discussion Agreement Yes
Yes
 		agreed No    
    S4‑210127 ITT4RT: On viewport dependent fisheye video delivery Samsung Electronics Iberia SA discussion Agreement Yes
Yes
 		agreed No    
    S4‑210128 ITT4RT: On viewport independent and viewport dependent delivery Samsung Electronics Iberia SA discussion Agreement Yes
Yes
 		revised No S4‑210196  
    S4‑210129 Update to: Audio mixing of multiple streaming in ITT4RT Tencent discussion Agreement Yes
Yes
 		revised No S4‑210197  
    S4‑210132 Improved text on Overlays for ITT4RT Draft CR Nokia Corporation discussion Agreement Yes
Yes
 		withdrawn Yes    
    S4‑210141 Basic Conditional Overlay Support Qualcomm Wireless GmbH discussion Agreement Yes
Yes
 		revised No S4‑210184  
    S4‑210142 Pseudo CR on Conditional Overlays Qualcomm Wireless GmbH draftCR Agreement Yes
Yes
 		revised No S4‑210185  
    S4‑210143 HEIF Image Format for ITT4RT Qualcomm Wireless GmbH discussion   Yes
Yes
 		revised No S4‑210186  
    S4‑210181 Frame packing of overlays Frame packing of overlays other discussion Yes
Yes
 		agreed No    
    S4‑210198 Improved text on Overlay configuration for ITT4RT Nokia Corporation discussion discussion Yes
Yes
 		agreed No   S4‑210188
    S4‑210196 On viewport independent and viewport dependent delivery Samsung Electronics Iberia SA discussion Agreement Yes
Yes
 		agreed No    
    S4‑210197 Update to: Audio mixing of multiple streaming in ITT4RT Tencent discussion Agreement Yes
Yes
 		revised No S4‑210202  
    S4‑210202 Update to: Audio mixing of multiple streaming in ITT4RT Tencent discussion Agreement No
Yes
 		agreed No   S4‑210197
11.6 FS_FLUS_NBMP (Feasibility Study on the use of NBMP in E_FLUS) S4‑210041 FS_FLUS_NBMP: 2nd Update to NBMP-FLUS-AF Call flow Tencent discussion Agreement Yes
Yes
 		revised No S4‑210194  
    S4‑210103 FS_FLUS_NBMP: Workplan update (0.6) Tencent discussion Agreement Yes
Yes
 		revised No S4‑210177  
    S4‑210194 2nd Update to NBMP-FLUS-AF Call flow Tencent, Qualcomm Incorporated discussion discussion Yes
Yes
 		agreed No    
11.7 Others including TEI S4‑210026 Updates on IETF References Intel draftCR Endorsement Yes
Yes
 		revised No S4‑210193  
    S4‑210170 IETF Reference Update for MMCMH Ericsson LM CR Agreement Yes
Yes
 		revised No S4‑210178  
    S4‑210171 IETF Reference Update for MMCMH Ericsson LM CR Agreement Yes
Yes
 		revised No S4‑210179  
    S4‑210172 IETF Reference Update for MMCMH Ericsson LM CR Agreement Yes
Yes
 		revised No S4‑210180  
11.8 New Work Items and Study Items                      
11.9 Any Other Business                      
11.10 Close of the session                      
12 LSs received during the meeting and Postponed Liaisons (from A. I. 5) S4‑210318 Reply LS on 5MBS progress and issues to address 3GPP RAN3 LS in Discussion Yes
YesThorsten: What about RoHC function ? Chair: they have not ruled out that Thorsten: RoHC is on gNB and we shpuld check why the RoHC is not addressed ? Thomas: Can we take sometime to send a LS to RAN3.
 		postponed No    
13 Reports and general issues from sub-working-groups                      
13.1 EVS SWG S4‑210288 EVS SWG Report during SA4#112-e EVS SWG Chair report Approval Yes
Yes
 		approved No    
13.2 MBS SWG S4‑210314 MBS SWG report at SA4#112-e MBS SWG Chair/Dolby Laboratories Ltd. report Approval Yes
Yes
 		approved No    
13.3 MTSI SWG S4‑210175 MTSI SWG Report during SA4#112-e MTSI SWG Chairman report Approval Yes
Yes
 		approved No    
13.4 SQ SWG S4‑210257 SW SWG Report during SA4#112-e SQ SWG Chairman report Approval Yes
Yes
 		approved No    
13.5 Video SWG S4‑210223 Video SWG Report for Block A Plenary Video SWG Chairman report Approval Yes
Yes
 		noted No    
    S4‑210284 Block B summary from the VIDEO SWG Chair Video SWG other discussion Yes
Yes
 		revised No S4‑210285  
    S4‑210285 Block B summary from the VIDEO SWG Chair Video SWG Chair report Presentation Yes
Yes
 		revised No S4‑210330 S4‑210284
    S4‑210330 Summary of Block B progress during SA4#112-e Video SWG Chair report Presentation Yes
Yes
 		noted No   S4‑210285
    S4‑210336 VIDEO SWG Report VIDEO SWG Chair report Approval Yes
Yes
 		approved No    
14 CRs to features in Release 16 and earlier S4‑210135 Bug Fix on Main USD Schema in Annex J.1 Qualcomm Incorporated CR Agreement Yes
Yes
 		agreed No    
    S4‑210144 IETF Reference Update Ericsson LM CR Agreement Yes
Yes
 		agreed No    
    S4‑210145 IETF Reference Update Ericsson LM CR Agreement Yes
Yes
 		agreed No    
    S4‑210146 IETF Reference Update Ericsson LM CR Agreement Yes
Yes
 		agreed No    
    S4‑210147 IETF Reference Update Ericsson LM CR Agreement Yes
Yes
 		revised No S4‑210294  
    S4‑210148 IETF Reference Update for Data Channel Media Ericsson LM CR Agreement Yes
Yes
 		agreed No    
    S4‑210311 LS on App ID Usage in NEF Related Service API HUAWEI Technologies Japan K.K. LS out Approval Yes
Yes
 		approved No   S4‑210235
    S4‑210229 CR to TS 26.501 on clarifications and corrections (Rel-16) Samsung Electronics Co., Ltd CR Agreement Yes
Yes
 		agreed No   S4‑210116
    S4‑210294 IETF Reference Update Ericsson LM CR Agreement Yes
Yes
 		agreed No   S4‑210147
    S4‑210178 IETF Reference Update for MMCMH Ericsson LM CR Agreement Yes
Yes
 		agreed No   S4‑210170
    S4‑210179 IETF Reference Update for MMCMH Ericsson LM CR Agreement Yes
Yes
 		agreed No   S4‑210171
    S4‑210180 IETF Reference Update for MMCMH Ericsson LM CR Agreement Yes
Yes
 		agreed No   S4‑210172
    S4‑210292 CR on OpenAPI Implementation of m1 interface Qualcomm Wireless GmbH CR - Yes
Yes
 		revised No S4‑210324 S4‑210174
    S4‑210324 CR on OpenAPI Implementation of m1 interface Qualcomm Wireless GmbH CR Agreement Yes
YesThis CR has been parked int his meeting and request SA4 to give special permission to agree this CR in the MBS March, 2021 Adhoc Telco meeting.
 		not concluded No   S4‑210292
    S4‑210190 Updates on IETF References Intel CR Agreement Yes
Yes
 		revised No S4‑210331  
    S4‑210331 Updates on IETF References Intel CR Agreement No
Yes
 		agreed No   S4‑210190
    S4‑210191 Updates on IETF References Intel CR Agreement Yes
Yes
 		revised No S4‑210332  
    S4‑210332 Updates on IETF References MTSI SWG CR Agreement No
Yes
 		agreed No   S4‑210191
    S4‑210192 Updates on IETF References Intel CR Agreement Yes
Yes
 		revised No S4‑210333  
    S4‑210333 Updates on IETF References Intel CR Agreement Yes
Yes
 		agreed No   S4‑210192
    S4‑210193 Updates on IETF References Intel CR Agreement Yes
Yes
 		revised No S4‑210334 S4‑210026
    S4‑210334 Updates on IETF References Intel CR discussion Yes
Yes
 		agreed No   S4‑210193
    S4‑210247 LS on DASH Specification Availability 3GPP SA4 response Approval Yes
Yes
 		approved No S4‑210293 S4‑210227
    S4‑210246 various corrections (Rel-16) Qualcomm Inc CR Decision Yes
Yes
 		agreed No   S4‑210228
    S4‑210317 Corrections on Procedures and APIs for Downlink and Uplink Streaming Ericsson LM, BBC, Enensys Technologies, Qualcomm Incorporated CR Agreement Yes
Yes
 		revised No S4‑210323 S4‑210231
    S4‑210323 Aggregated essential corrections from various change requests Ericsson LM, BBC, Enensys Technologies, Qualcomm Incorporated CR Agreement Yes
Yes
 		agreed No   S4‑210317
    S4‑210293 LS on DASH Specification Availability 3GPP SA WG4 LS out Approval Yes
Yes
 		approved No   S4‑210247
15 Release 17 Features                      
15.1 IVAS_Codec (EVS Codec Extension for Immersive Voice and Audio Services) S4‑210315 Considerations for IVAS processing plans Ericsson LM discussion Agreement Yes
Yes
 		agreed No   S4‑210150
    S4‑210262 Draft IVAS codec development overview (IVAS-1) HuaWei Technologies Co., Ltd discussion discussion Yes
Yes
 		agreed No   S4‑210133
15.2 ITT4RT (Support of Immersive Teleconferencing and Telepresence for Remote Terminals) S4‑210107 ITT4RT: On text for media configuration Samsung Electronics Iberia SA discussion Agreement No
Yes
 		withdrawn Yes    
    S4‑210108 ITT4RT: On viewport dependent fisheye video delivery Samsung Electronics Iberia SA discussion Agreement No
Yes
 		withdrawn Yes    
    S4‑210109 ITT4RT: On viewport independent and viewport dependent delivery Samsung Electronics Iberia SA discussion Agreement Yes
Yes
 		withdrawn Yes    
    S4‑210176 IIT4RT: Proposal for TimePLan Intel, Nokia Corporation (ITT4RT Rapporteurs) Work Plan Agreement Yes
YesOzgur: Power to agree on official CRs over adhoc telcos. Chair: Are guidelines maintained as 4 dates are consumed leaving only one session for NBMP. As there were no comments and questions, the Chair deferred it to the next plenary session. Chair: which dates will have special powers. And special power to agree on official telcos 28th Feb and 3rd March, 2021.
 		revised No S4‑210291 S4‑210020
    S4‑210291 IIT4RT: Proposal for TimePlan Intel, Nokia Corporation (ITT4RT Rapporteurs) Work Plan Agreement Yes
Yes
 		agreed No   S4‑210176
    S4‑210316 Video Support for ITT4RT Intel, Nokia Corporation (ITT4RT Rapporteurs) CR Agreement Yes
Yes
 		not concluded No    
    S4‑210200 ITT4RT Permanent Document - Requirements, Working Assumptions and Potential Solutions (v0.10.1) Intel, Nokia Corporation (ITT4RT Rapporteurs) report Agreement Yes
Yes
 		agreed No    
    S4‑210201 26.114 Support for ITT4RT Intel, Nokia Corporation (ITT4RT Rapporteurs), InterDigital, Tencent, Samsung, Qualcomm Incorporated, Fraunhofer IIS draftCR Agreement Yes
YesWill this be changed to a formal CR in the future adhoc meeting on 3rd March, 2021 which has the power provided to the sub working group by SA4 during its closing plenary.
 		agreed No S4‑210316  
15.3 ATIAS (Terminal Audio quality performance and Test methods for Immersive Audio Services) S4‑210259 Draft time plan for ATIAS, v0.4 Orange, Dolby Laboratories, Inc Work Plan discussion Yes
Yes
 		agreed No    
15.4 HaNTE (Handsets Featuring Non-Traditional Earpieces) S4‑210258 Proposals for data collection of HaNTE – test methods Qualcomm Incorporated Work Plan Agreement Yes
Yes
 		agreed No    
15.5 HInT (Extension for headset interface tests of UE) S4‑210040 Headset Interface Description HEAD acoustics GmbH draftCR Agreement Yes
Yes
 		agreed No   S4aQ200156
    S4‑210088 Time Plan for HInT, v0.3 HEAD acoustics GmbH, Orange discussion Agreement Yes
Yes
 		agreed No   S4‑201615
    S4‑210169 dCR 26.131 Extension for headset interface tests of UE Orange draftCR Agreement Yes
Yes
 		agreed No   S4‑201482
15.6 8K_VR_5G (Operation Points for 8K VR 360 Video over 5G) S4‑210277 8K_VR_5G: Proposed Time Plan v.0.1.0 Intel (Rapporteur) Work Plan Agreement Yes
Yes
 		agreed No   S4‑210027
    S4‑210341 Decoding Capabilities and Operation Points for 8K VR 360 Video over 5GMS Intel, Qualcomm Incorporated, Tencent, Fraunhofer HHI CR Agreement Yes
YesThe definition of 'k' is provided in the CR.
 		revised No S4‑210342 S4‑210286
    S4‑210342 Decoding Capabilities and Operation Points for 8K VR 360 Video over 5GMS Intel, Qualcomm Incorporated, Tencent, Fraunhofer HHI CR Agreement No
Yes
 		revised No S4‑210343 S4‑210341
    S4‑210343 Decoding Capabilities and Operation Points for 8K VR 360 Video over 5GMS Intel, Qualcomm Incorporated, Tencent, Fraunhofer HHI CR Agreement No
Yes
 		agreed No   S4‑210342
    S4‑210282 8K Decoding Capabilities Qualcomm Incorporated, Intel, Tencent CR Agreement Yes
YesThis document is first of its kind in 3GPP to have 8K availble in the specifications.
 		agreed No   S4‑210276
    S4‑210286 Operation Points for 8K VR 360 Video Intel, Qualcomm Incorporated, Tencent, Fraunhofer HHI CR Agreement Yes
Yes
 		agreed No S4‑210341  
15.7 TEI17 and any other Rel-17 documents                      
16 Study Items S4‑210225 Reply to: Liaison from DVB on Phase I technical specification “DVB-MABR” 3GPP SA4 LS out approval Yes
Yes
 		revised No S4‑210310  
    S4‑210310 Reply to: Liaison from DVB on Phase I technical specification “DVB-MABR” 3GPP SA4 LS out approval Yes
Yes3GPP SA4 kindly requests DVB TM-MCAST o to take into account the information and answer provided above, and to inform SA4 on whether the use of TS 26.346 Annex L in DVB-MABR requires a different digest algorithm.
 		agreed No   S4‑210225
    S4‑210337 (reserved) SA4 other discussion No
No
 		reserved No    
    S4‑210338 (reserved) SA4 other discussion No
No
 		reserved No    
    S4‑210339 (reserved) closing plenary other discussion No
No
 		reserved No    
16.1 FS_5GMS_Multicast (Feasibility Study on Multicast Architecture Enhancements for 5GMSA) S4‑210234 Updated time and work plan TELUS Work Plan Agreement Yes
Yes
 		agreed No   S4‑210080
    S4‑210248 Draft revised SID FS_5GMS_Multicast Telus SID revised Agreement Yes
Yes
 		agreed No   S4‑210243
    S4‑210245 Multicast Architecture Enhancement for 5G Media Streaming Telus draft TR Agreement Yes
Yes
 		agreed No   S4‑210233
    S4‑210319 LS to SA2 and SA6 on FS_5GMS_Multicast and 5MBS MBS LS out discussion Yes
Yes
 		revised No S4‑210340 S4‑210312
    S4‑210340 LS to SA2 and SA6 on FS_5GMS_Multicast and 5MBS 3GPP SA4 LS out discussion Yes
Yes
 		revised No S4‑210345 S4‑210319
    S4‑210345 LS to SA2 and SA6 on FS_5GMS_Multicast and 5MBS 3GPP SA4 LS out discussion Yes
Yes
 		approved No   S4‑210340
16.2 FS_XRTraffic (Feasibility Study on Typical Traffic Characteristics for XR Services and other Media) S4‑210278 [FS_XRTraffic] Proposed Update to PD Qualcomm CDMA Technologies Work Plan Agreement Yes
Yes
 		agreed No   S4‑210125
    S4‑210281 Proposed Updates to Work Plan for FS_XRTraffic Qualcomm Incorporated Work Plan Agreement Yes
Yes
 		agreed No   S4‑210068
    S4‑210280 [FS_XRTraffic] Proposed Updated to Work Item Description Qualcomm Incorporated WID revised Agreement Yes
Yes
 		agreed No   S4‑210211
    S4‑210279 Discussion Paper on SA4 support for XR and other media application in 5G Qualcomm Incorporated discussion discussion Yes
YesThe discussion revolved around SA1 and RAN1 to inform SA4 beforehand of the study of the usecases. Qualcomm mentioned that, SA4 shouldnot always be seen as stage 3 only. Xiomi seconded the views. It was mentioned that other 3GPP groups sometimes decide for the video traffic characteriestcs which have sub-optimal values. Chair, Dolby mentioned that SA4 has been a bit lagging to comply with the 3GPP timelines and for most of the cases, it had nothing to do with inter group co-ordination - it is SA4's mandate to timely deliver the work. It is SA4's onus to pull the information from other RAN and SA groups. If SA4 can start work early, then there could be better co-ordination.
 		agreed No   S4‑210212
16.3 FS_EMSA (Feasibility Study on Streaming Architecture extensions For Edge processing) S4‑210320 EMSA architecture Qualcomm Wireless GmbH discussion Agreement Yes
YesRichard: Editorial in Lin 5,6, 12, and 14.
 		agreed No   S4‑210254
    S4‑210321 TR EMSA Qualcomm Wireless GmbH draft TR Agreement Yes
YesChange History to be added.
 		revised No S4‑210325  
    S4‑210322 Timeplan for EMSA Qualcomm Wireless GmbH Work Plan Agreement Yes
Yes
 		agreed No    
    S4‑210325 TR EMSA Qualcomm Wireless GmbH draft TR Agreement No
Yes
 		agreed No   S4‑210321
16.4 FS_VR_CoGui (Feasibility Study on VR Streaming Conformance and Guidelines)                      
16.5 FS_5GVideo (Feasibility Study on 5G Video Codec Characteristics) S4‑210210 Proposed Updated Work Plan for FS_5GVideo Qualcomm Incorporated Work Plan Agreement Yes
Yes
 		agreed No   S4‑210061
    S4‑210207 Draft TR26.955v0.5.0 Qualcomm Incorporated draft TR discussion Yes
Yes
 		agreed No    
16.6 FS_FLUS_NBMP (Feasibility Study on the use of NBMP in E_FLUS) S4‑210102 FS_FLUS_NBMP: Proposed updates to dCR Tencent draftCR Agreement Yes
Yes
 		agreed No    
    S4‑210177 FS_FLUS_NBMP: Work Plan v(0.6.1) Tencent Work Plan Agreement Yes
Yes
 		revised No S4‑210335  
    S4‑210335 FS_FLUS_NBMP: Work Plan v(0.6.1) Tencent Work Plan Agreement No
Yes
 		agreed No   S4‑210177
    S4‑210195 Permanent Document v0.6.0: FS_FLUS_NBMP MTSI SWG Work Plan Agreement Yes
Yes
 		agreed No    
16.7 FS_5GSTAR (Feasibility Study on 5G Glass-type AR/MR Devices) S4‑210267 Draft TR 26.998 v.0.4 3GP SA4 draft TR Decision Yes
Yes
 		agreed No   S4‑210215
    S4‑210271 Proposed Updates to Work Plan Qualcomm Incorporated, Samsung other discussion Yes
Yes
 		agreed No   S4‑210222
    S4‑210270 5GSTAR Permanent Document 0.4.0 Samsung Electronics Co., Ltd., Qualcomm Incorporated other discussion Yes
Yes
 		agreed No    
16.8 FS_5GMS_EXT (Study on 5G media streaming extensions) S4‑210299 [FS_5GMS-EXT] Key Topic Uplink media streaming Qualcomm Incorporated pCR Agreement Yes
Yes
 		noted No   S4‑210052
    S4‑210300 [FS_5GMS-EXT] Key Topic Background traffic Qualcomm Incorporated pCR Agreement Yes
Yes
 		noted No   S4‑210053
    S4‑210306 [FS_5GMS-EXT] Key Topic Content Preparation Qualcomm Incorporated pCR Agreement Yes
Yes
 		noted No   S4‑210049
    S4‑210307 [FS_5GMS-EXT] Key Topic Traffic Identification Qualcomm Incorporated pCR Agreement Yes
Yes
 		noted No   S4‑210050
    S4‑210301 [FS_5GMS-EXT] Key Topic Network Event usage Qualcomm Incorporated pCR Agreement Yes
Yes
 		noted No   S4‑210055
    S4‑210104 FS_5GMS_EXT: Proposed workplan Tencent, Ericsson discussion Agreement Yes
Yes
 		revised No S4‑210297  
    S4‑210297 FS_5GMS_EXT: Proposed workplan Tencent, Ericsson discussion Agreement Yes
Yes
 		agreed No   S4‑210104
    S4‑210305 Study on 5G media streaming extensions Ericsson LM draft TR Agreement Yes
Yes
 		agreed No   S4‑210136
17 Work Items and Study Items under the responsibility of other TSGs/WGs impacting SA4 work                      
18 New Work Items and Study Items S4‑210240 New Study Item on Media Production over 5G NPNs Ericsson LM, AT&T, BBC, B-Com, Dolby Laboratories Inc., EBU, Orange SID new Agreement Yes
Yes
 		revised No S4‑210260 S4‑210160
    S4‑210260 New Study Item on Media Production over 5G NPNs [FS_5G_4_AVProd] Ericsson LM, AT&T, B-Com, BBC, Dolby Laboratories Inc., EBU, Orange, Sennheiser Electronic GmbH, Qualcomm Incorporated, Verizon UK Ltd SID new Agreement Yes
YesThorsten Lohmar, Ericsson presented the document. Edward: Bandwidth required for U/L in an open question here. It would be good to include RAN as they could provide a fair idea for trnsmissions. Thpirsten: SA1 has already completed the study requirement. We could add RAN2 in this study. Edward: several broadcasters are sharing the same spectrum in U/L. There has to be more information from RAN directing us to give some headers. Also, unlicensed spectrum could also be thought of. Thorsten: It is more in-line with SA1 requirement. However, we could have a study on the unlicensed spectrum aspects. Thomas: Very supportive for different verticals. The silos need to be very precise and defined. Edward: Need to check the procedures before we could make it commercially available. Darko, EBU: TR 22.827 and 263 and the same resources can be pressed in for this study. Support this study in genral. Edward: We have TCLI, on filtration of public content. there are potential way to identify traffic flows.
 		revised No S4‑210326  
    S4‑210326 New Study Item on Media Production over 5G NPNs [FS_5G_4_AVProd] Ericsson LM, AT&T, B-Com, BBC, Dolby Laboratories Inc., EBU, Orange, Sennheiser Electronic GmbH, Qualcomm Incorporated, Verizon UK Ltd, Tencent SID new Agreement Yes
Yes
 		agreed No   S4‑210260
19 Postponed issues                      
20 Review of the future work plan (next meeting dates, hosts) S4‑210261 Status Update of WI/SI at the closing plenary of SA4#112-e 3GPP MCC Work Plan Agreement Yes
Yes
 		revised No S4‑210263  
    S4‑210263 Status Update of WI/SI at the closing plenary of SA4#112-e 3GPP MCC Work Plan Agreement No
YesRegarding the Future Meeting Plan: Samsung (host of F2F in August 2021) confirmed that due to the strictures imposed by the Korean Govt. in the quarantine rules for international travellers due to lingering COVID-19 pandemic, the F2F meeting in August, 2021 has been changed to an online meeting. The duration of SA4#115-e will be from 18th to 27th August, 2021. There were also discussion about the mode of meeting, where it was felt that members have an inclination of going back to the F2F meetings mode. It is also noticed that MCC would be limited in terms of resources to support online meetings for SA4 for a long time, being a smaller group compared to RAN WGs or SA2. Further, members have also expressed their reservation in having a hybrid meeting set-up in future that's percived to be an ardous scenario than the present one. After a week of discussion amongst the members regarding the dates of the meeting, the following dates for SA4 meetings in 2022 has been agreed at a broad level. Considering the COVID scenario, options of e-meetings were also kept open to one meeting in a year. However, it is to be remembered that none of the future SA4 online meetings will not accrue any voting rights to the members. - SA4#117 F2F:14-18 February 2022 OR, E-meeting:14-23 February 2022 - SA4#118 E-meeting:6-14 April 2022 - SA4#119 F2F:16-20 May 2022 OR, E-meeting:11-20 May 2022 - SA4#120 F2F:22-26 August 2022 OR, E-meeting:17-26 August 2022 - SA4#121 F2F:14-18 November 2022 OR, E-meeting:9-18 November 2022 Election Announcement: The Chairman announced the elections for Chair and Vice-Chair in April SA4#113-e meeting. The current Chairman & Vice-Chairman have expressed their willingness to stand in for a consecutive 3rd term and clarified that they have support from their respective companies to continue for the same role. Thomas Stockhammer, Qualcomm asked a clarification on the same company holding a Chair and Vice-Chair positions in the same group as per 3GPP rules. The Chairman clarified, that according to the 3GPP rules, the same company cannot hold both the Chiar and Vice-Chair positions. So, if the same situation persists in the SA4 leadership after elections in April, 2021, then one of the positions held by the same compmany would be up for election again during the May, 2021 meeting. Mr. Stefan Bruhn, Vice-Chair - SA4 applauded the statement and mentioned that he would be happy to support the decision of the group. MCC would role out the announcement of the Elections for two positions, the Chairperson and one of the Vice-Chairperson respectively over the official SA4 mailing reflector preferably on 11th Feb, 2021. It is to be noted that in 3GPP as per the current rules, online meetings are adhoc ones and no voting rights are accrued by the members during these. Therefore, members-in-goodstanding (eligible for voting) will be calculated as per the presence of the members during SA4#107 (held during January 2020 in Poland). Further, there will not be proxy voting in the online elections.
 		agreed No   S4‑210261
21 Any Other Business