[{"name":"SP-220424","title":"Presentation of TR 23.700-61 to TSG SA#96 for approval","source":"SA WG2","contact":"Maurice Pope","contact-id":648,"tdoctype":"draft TR","for":"Approval","abstract":"Abstract of document: In SA#94E the study was approved in SP-211654. Following the agreed objective of the study, SA WG2 had started the study from SA WG2#149E and following key issue was agreed: Key Issue #1: Determination of unavailability period in 5GS for a specific UE. Changes since last presentation: This is the first time the TR is presented to TSG SA. The TR includes 1 Key Issue, along with the 6 candidate solutions. The TR also includes the evaluations and conclusions for the key issue. Outstanding Issues: None. Contentious Issues: None.","secretary_remarks":"Block Approved","agenda_item_sort_order":45,"ainumber":"6.11","ainame":"Specifications for Approval \/ for Information and Approval","tdoc_agenda_sort_order":11550,"status":"approved","reservation_date":"2022-05-25 06:03:46","uploaded":"2022-05-31 15:51:11","revisionof":"","revisedto":"","release":"Rel-18","crspec":"23.700-61","crspecversion":"1.0.0","workitem":[{"winame":"FS_SUECR"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_96_Budapest_2022_06\/Docs\/SP-220424.zip","group":"SP","meeting":"SP-96","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-220464","title":"Presentation of TR 23.783 v2.0.0 for Approval","source":"SA WG6","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"draft TR","for":"Approval","abstract":"Abstract of document: TR 23.783 has analysed how to ensure that the set of Mission Critical services is supported over the 5GS. Key issues have been derived and solutions have been developed for the impacts on existing or new Stage 2 Mission Critical specifications. The study has helped SA WG6 to decide how to specify Mission Critical Services over 5GS and how to phase the normative Stage 2 work. Changes since last presentation to SA Plenary Meeting #90: Solutions were developed and conclusions were drawn for key issues related to multicast\/broadcast and to off-network aspects. Based on the outcome of the study normative work items have been initiated subsequently for on-network unicast communication for Mission Critical Services, for Mission Critical Services over 5MBS and for Mission Critical services over 5GProSe. Outstanding Issues: None Contentious Issues: None","secretary_remarks":"Block Approved","agenda_item_sort_order":45,"ainumber":"6.11","ainame":"Specifications for Approval \/ for Information and Approval","tdoc_agenda_sort_order":11560,"status":"approved","reservation_date":"2022-05-29 12:42:40","uploaded":"2022-06-01 18:58:36","revisionof":"","revisedto":"","release":"Rel-18","crspec":"23.783","crspecversion":"2.0.0","workitem":[{"winame":"FS_MCOver5GS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_96_Budapest_2022_06\/Docs\/SP-220464.zip","group":"SP","meeting":"SP-96","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-220491","title":"TS 28.312 Management and orchestration; Intent driven management services for mobile networks","source":"SA WG5","contact":"Mirko Cano Soveri","contact-id":41957,"tdoctype":"draft TS","for":"Approval","abstract":"Abstract of document: The TS specifies the concept, use cases, requirements and solutions for the intent driven management for service or network management. Changes since last presentation to TSG SA Meeting #96: Address the remaining Editor's Notes Outstanding Issues: None Contentious Issues: None","secretary_remarks":"Block Approved","agenda_item_sort_order":45,"ainumber":"6.11","ainame":"Specifications for Approval \/ for Information and Approval","tdoc_agenda_sort_order":11570,"status":"approved","reservation_date":"2022-05-30 08:13:09","uploaded":"2022-05-31 08:51:52","revisionof":"","revisedto":"","release":"Rel-17","crspec":"28.312","crspecversion":"2.0.0","workitem":[{"winame":"IDMS_MN"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_96_Budapest_2022_06\/Docs\/SP-220491.zip","group":"SP","meeting":"SP-96","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-220492","title":"TS 28.105 Management and orchestration; Artificial Intelligence\/ Machine Learning (AI\/ML) management","source":"SA WG5","contact":"Mirko Cano Soveri","contact-id":41957,"tdoctype":"draft TS","for":"Approval","abstract":"Abstract of document: It is the TS for AI\/ML management. Changes since last presentation to SA Meeting #95e: - Added some new AI\/ML training use cases; - Enhanced AI\/ML NRMs; - Added stage 3 YAML definitions; - Made some rapporteur clean-ups. Outstanding Issues: None. Contentious Issues: None.","secretary_remarks":"Block Approved","agenda_item_sort_order":45,"ainumber":"6.11","ainame":"Specifications for Approval \/ for Information and Approval","tdoc_agenda_sort_order":11580,"status":"approved","reservation_date":"2022-05-30 08:13:10","uploaded":"2022-05-31 08:51:53","revisionof":"","revisedto":"","release":"Rel-17","crspec":"28.105","crspecversion":"2.0.0","workitem":[{"winame":"eMDAS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_96_Budapest_2022_06\/Docs\/SP-220492.zip","group":"SP","meeting":"SP-96","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-220493","title":"TR 28.819 Study on continuous integration continuous delivery support for 3GPP NFs","source":"SA WG5","contact":"Mirko Cano Soveri","contact-id":41957,"tdoctype":"draft TR","for":"Approval","abstract":"Abstract of document: This TR specifies key issues for 3GPP system in supporting automating NF CI-CD, including the standardized supporting information for a newly delivered NF, capabilities and requirements for supporting operational and simulation testing, and so on. Changes since last presentation to TSG SA Meeting #96: This is the first presentation. Outstanding Issues: None. Contentious Issues: None.","secretary_remarks":"Block Approved","agenda_item_sort_order":45,"ainumber":"6.11","ainame":"Specifications for Approval \/ for Information and Approval","tdoc_agenda_sort_order":11590,"status":"approved","reservation_date":"2022-05-30 08:13:12","uploaded":"2022-05-31 08:51:51","revisionof":"","revisedto":"","release":"Rel-18","crspec":"28.819","crspecversion":"1.0.0","workitem":[{"winame":"FS_CICDNS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_96_Budapest_2022_06\/Docs\/SP-220493.zip","group":"SP","meeting":"SP-96","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-220494","title":"TS 28.104 Management and orchestration; Management Data Analytics","source":"SA WG5","contact":"Mirko Cano Soveri","contact-id":41957,"tdoctype":"draft TS","for":"Approval","abstract":"Abstract of document: It is the TS for Management Data Analytics. Changes since last presentation to SA Meeting #95e: - Clarified and enhanced some use cases and requirements; - Enhanced data definitions for some MDA capabilities; - Enhanced the MDA request NRM; - Added MDA report NRM; - Added service components for MDA MnS; - Added stage 3 YAML definitions for MDA NRM and MDA Report. - Made some rapporteur clean-ups. Outstanding Issues: None. Contentious Issues: The following issues need more time to be solved and are proposed to be addressed in Rel-18: - Definitions of analytics data for failure prediction. - Analytics for existing PM, KPI or alarm; - Recommended action related to non-3GPP domain.","secretary_remarks":"Block Approved","agenda_item_sort_order":45,"ainumber":"6.11","ainame":"Specifications for Approval \/ for Information and Approval","tdoc_agenda_sort_order":11600,"status":"approved","reservation_date":"2022-05-30 08:13:13","uploaded":"2022-05-31 08:51:52","revisionof":"","revisedto":"","release":"Rel-17","crspec":"28.104","crspecversion":"2.0.0","workitem":[{"winame":"eMDAS"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_96_Budapest_2022_06\/Docs\/SP-220494.zip","group":"SP","meeting":"SP-96","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-220495","title":"TS 32.257 Telecommunication management; Charging management; Edge Computing domain charging; stage 2","source":"SA WG5","contact":"Mirko Cano Soveri","contact-id":41957,"tdoctype":"draft TS","for":"Approval","abstract":"Abstract of document: It is the TS for Edge Computing domain charging. Changes since last presentation to SA Meeting #95e: - Added charging data definition for direct edge enabling services; - Added charging data definition for exposed 5G NF services; - Some rapporteur clean-ups. Outstanding Issues: Relation between EC service provision (in TS 23.558) and EC charging (in TS 32.257). Contentious Issues: None.","secretary_remarks":"Block Approved","agenda_item_sort_order":45,"ainumber":"6.11","ainame":"Specifications for Approval \/ for Information and Approval","tdoc_agenda_sort_order":11610,"status":"approved","reservation_date":"2022-05-30 08:13:14","uploaded":"2022-05-31 08:51:52","revisionof":"","revisedto":"","release":"Rel-17","crspec":"32.257","crspecversion":"2.0.0","workitem":[{"winame":"EDGE_CH"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_96_Budapest_2022_06\/Docs\/SP-220495.zip","group":"SP","meeting":"SP-96","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-220540","title":"TR 33.874 'Study on enhanced security for Phase 2 network slicing'","source":"SA WG3","contact":"Mirko Cano Soveri","contact-id":41957,"tdoctype":"draft TR","for":"Approval","abstract":"Abstract of document: This technical reports covers the study on enhanced security for Network Slicing Phase 2. Changes since last presentation to Meeting #: This is the first presentation Outstanding Issues: Add abbreviations etc and possibly some clean up amendments. Contentious Issues: None","secretary_remarks":"Block Approved","agenda_item_sort_order":45,"ainumber":"6.11","ainame":"Specifications for Approval \/ for Information and Approval","tdoc_agenda_sort_order":11620,"status":"approved","reservation_date":"2022-05-30 10:06:42","uploaded":"2022-05-31 10:09:48","revisionof":"","revisedto":"","release":"Rel-18","crspec":"33.874","crspecversion":"1.0.0","workitem":[{"winame":"FS_eNS2_SEC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_96_Budapest_2022_06\/Docs\/SP-220540.zip","group":"SP","meeting":"SP-96","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-220541","title":"TS 33.503 'Security Aspects of Proximity based Services (ProSe) in the 5G System (5GS)'","source":"SA WG3","contact":"Mirko Cano Soveri","contact-id":41957,"tdoctype":"draft TS","for":"Approval","abstract":"Abstract of document: TS 33.503 ('Security Aspects of Proximity based Services (ProSe) in the 5G System (5GS)') specifies security requirements and procedures that are specific to the Proximity based services in the 5G System: - Security for Open 5G ProSe Direct Discovery - Security for Restricted 5G ProSe Direct Discovery - Security for unicast mode 5G ProSe Direct Communication - Security for 5G ProSe Communication via 5G ProSe Layer-3 UE-to-Network Relay over User Plane - Security for 5G ProSe Communication via 5G ProSe Layer-3 UE-to-Network Relay over Control Plane - Security for 5G ProSe Remote UE Secondary Authentication via a 5G ProSe Layer-3 UE-to-Network Relay without N3IWF - Security for 5G ProSe Communication via 5G ProSe Layer-2 UE-to-Network Relay Changes since last presentation to TSG Meeting: This is the first presentation to TSG SA. Outstanding Issues: There are 4 Editor s Notes related secondary authentication that need to be resolved. Contentious Issues: None","secretary_remarks":"Block Approved","agenda_item_sort_order":45,"ainumber":"6.11","ainame":"Specifications for Approval \/ for Information and Approval","tdoc_agenda_sort_order":11630,"status":"approved","reservation_date":"2022-05-30 10:06:43","uploaded":"2022-05-31 10:09:48","revisionof":"","revisedto":"","release":"Rel-17","crspec":"33.503","crspecversion":"1.0.0","workitem":[{"winame":"5G_ProSe"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_96_Budapest_2022_06\/Docs\/SP-220541.zip","group":"SP","meeting":"SP-96","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-220603","title":"TS 26.531, Version 2.1.0, 'Data Collection and Reporting; General Description and Architecture'","source":"SA WG4","contact":"Jayeeta Saha","contact-id":85340,"tdoctype":"draft TS","for":"Approval","abstract":"Abstract of document: Created at the request of SA WG2, TS 26.531 provides a stage 2 specification for data collection and reporting as part of the EVEX Work Item. It includes a reference architecture defining a generic Data Collection AF that: 1. Receives UE data reports directly from the UE ( direct reporting ) or via an Application Service Provider ( indirect reporting ) or from an AS. 2. Optionally processes the UE data to aggregate, filter or otherwise summarise it into a form suitable for exposure to subscribed event consumers. 3. Exposes the processed UE data in the form of events to authorised subscribers such as the Network Data Analytics Function (NWDAF) and\/or the Event Consumer AF of the Application Service Provider associated with the application. This generic architecture is intended to be instantiated in other 3GPP technical specifications for the collection, reporting and exposure of UE data pertaining to particular application domains. The first such domain anticipated is 5G Media Streaming. The generic architecture is also intended to collect, report and expose UE data using the events already specified by SA WG2 in TS 23.288. Changes presentation of V1.0.0 to SA Meeting #94: - Stage 2 specification of data exposure restriction model in new clause 4.5.2, including Data Access Profile model, definitions of three restriction axes for event exposure to event consumers and six baseline aggregation functions for UE data processing by the Data Collection AF. - Editor s Notes resolved: - Requirement for data collection client to present credentials to the Data Collection AF in new clause 4.5.3. - Clarification on use of NEF exposure in new clause 4.7.1. - Use of CAPIF moved from clause 4 to new clause 4.7.2. - Added R7 client API invocations to procedures in clause 5.4 and 5.5. - Added procedure for event consumer authorisation using an OAuth-based Application Server in clause 5.8. Outstanding Issues: None. Contentious Issues: There are no known contentious issues at this point.","secretary_remarks":"Block Approved","agenda_item_sort_order":45,"ainumber":"6.11","ainame":"Specifications for Approval \/ for Information and Approval","tdoc_agenda_sort_order":11640,"status":"approved","reservation_date":"2022-05-31 15:27:28","uploaded":"2022-06-01 16:01:09","revisionof":"","revisedto":"","release":"Rel-17","crspec":"26.531","crspecversion":"2.1.0","workitem":[{"winame":"EVEX"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_96_Budapest_2022_06\/Docs\/SP-220603.zip","group":"SP","meeting":"SP-96","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-220604","title":"TS 26.532, Version 2.0.0,'Data Collection and Reporting; Protocols and Formats;'","source":"SA WG4","contact":"Jayeeta Saha","contact-id":85340,"tdoctype":"draft TS","for":"Approval","abstract":"Abstract of document: The EVEX Work Item identified the creation of TS 26.532 as stage 3 specification for UE data collection and reporting functionality, to complement the stage 2 specification in TS 26.531 on generic data collection and reporting architecture. TS 26.532 V2.0.0 specifies the following functionality: 1. Detailed description of network-side, UE-to-network, and UE-internal procedures involving configuration, collection, reporting and event exposure of UE application-specific data ( UE data ) interactions between functional entities and reference points as described by the generic network architecture in TS 26.531. 2. General aspects of the APIs for UE data collection and reporting including HTTP URL structure and methods, and applicable data types 3. Definition of the Data Reporting Provisioning service API, used by an Application Service Provider to provision a data collection and reporting configuration in a Data Collection AF. 4. Definition of the Data Reporting service API, used by clients of a Data Collection AF to obtain their data collection and reporting configuration from, and then report data to, the Data Collection AF. 5. Definition of the UE-internal or Client API offered by the Direct Data Collection Client to the UE Application for mutual exchange of relevant data. 6. Specification of the data models associated with the various UE data collection and reporting procedures. 7. OpenAPI representation of REST APIs associated with UE data collection and reporting. The APIs associated with event exposure services provided by the Data Collection AF to consumer entities, along with APIs associated with NEF mediation of UE data collection and reporting related interactions between network entities, are specified by CT WG3 in their relevant specifications. Changes to presentation of V1.0.0 to SA Meeting #95: - Addition in clause 4 of call flow diagrams and corresponding descriptions of network-internal, UE-internal and UE-to-network interactions regarding the configuration and reporting of UE data between the Data Collection AF and different types of data collection clients. - Description in clause 5 of HTTP protocol usage for the access to RESTful and regular HTTP resources associated with UE data collection and reporting and offered by the Data Collection AF. - Specification in clause 6 of the Ndcaf_DataReportingProvisioning service and associated resources and API methods offered by a Data Collection AF to the Provisioning server ( Provisioning AF ) of an Application Service Provider. This service and associated API enable the Provisioning AF to provision the Data Collection AF with its UE data collection, reporting and event exposure configuration, a portion of that information is intended to be forwarded by the Data Collection AF to its data collection clients. The provisioning information may contain one or more sets of event exposure restrictions to be followed by the Data Collection AF in controlling the amount or granularity of UE data related information accessible to different consumer entities via Event services offered by the Data Collection AF. - Corrections, additions to, and reorganization of clause 7 regarding the Ndcaf_DataReporting service and associated resources and associated API methods offered by a Data Collection AF to its data collection clients. This service and associated API enable a data collection client to obtain its UE data collection and reporting configuration from and subsequently send collected UE data reports to a Data Collection AF, according to its configuration. - Specification in clause 8 of UE-internal procedures between an optionally instantiated UE Application entity and the data collection client regarding the acquisition of a data collection and reporting configuration by the UE Application and subsequent reporting of collected UE data in accordance with that configuration to the data collection client. - Specification in clause 9 of security and access control","secretary_remarks":"Block Approved","agenda_item_sort_order":45,"ainumber":"6.11","ainame":"Specifications for Approval \/ for Information and Approval","tdoc_agenda_sort_order":11650,"status":"approved","reservation_date":"2022-05-31 15:27:29","uploaded":"2022-06-01 16:01:09","revisionof":"","revisedto":"","release":"Rel-17","crspec":"26.532","crspecversion":"2.0.0","workitem":[{"winame":"EVEX"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_96_Budapest_2022_06\/Docs\/SP-220604.zip","group":"SP","meeting":"SP-96","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-220605","title":"TS 26.517, Version 2.0.0, '5G Multicast Broadcast User Services; Protocols and Formats'","source":"SA WG4","contact":"Jayeeta Saha","contact-id":85340,"tdoctype":"draft TS","for":"Approval","abstract":"Abstract of document: As part of the 5MBP3 Work Item, TS 26.517 provides a Release 17 stage 3 specification of the protocols and data formats supporting Multicast Broadcast User Services in the 5G System. In particular: 1. The data model, syntax and semantics of the User Service Announcement used to advertise MBS User Services to the MBS Client in the UE. 2. The protocols for ingesting and delivering media objects using the Object Distribution Method, including how the MBS Distribution Session is advertised in the User Service Announcement, and how the delivery method operates in the specific cases of file delivery mode and real-time media segment 'streaming' mode. 3. The protocols for ingesting and delivering data packets using the Packet Distribution Method, including how the MBS Distribution Session is advertised in the User Service Announcement, and how the delivery method operates in the specific cases of proxy mode and forward-only mode. Application Layer FEC is also considered. NOTE: The stage 3 OpenAPI data model (based on the stage 2 specification TS 26.502) is being specified by CT WG3. Changes since last presentation to SA Meeting #95: Clauses on User Service Announcement, Object Distribution Model and Packet Distribution Method have been elaborated. Outstanding Issues: In the definition of the User Service Announcement: - 3GP-DASH Representation mappings. - Delivery envelope for the User Service Bundle Description. - Controlled vocabulary of conformance profiles. Contentious Issues: The definition of additional transport protocols for the Object Distribution Method has been postponed until a future release.","secretary_remarks":"Block Approved","agenda_item_sort_order":45,"ainumber":"6.11","ainame":"Specifications for Approval \/ for Information and Approval","tdoc_agenda_sort_order":11660,"status":"approved","reservation_date":"2022-05-31 15:27:29","uploaded":"2022-06-01 16:31:12","revisionof":"","revisedto":"","release":"Rel-17","crspec":"26.517","crspecversion":"2.0.0","workitem":[{"winame":"5MBP3"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_96_Budapest_2022_06\/Docs\/SP-220605.zip","group":"SP","meeting":"SP-96","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-220606","title":"TR 26.805, Version 2.0.0, 'Study on Media Production over 5G NPN Systems'","source":"SA WG4","contact":"Jayeeta Saha","contact-id":85340,"tdoctype":"draft TR","for":"Approval","abstract":"Abstract of document: The study on Media Production over 5G NPN aims to identify standardization needs and potential standards gaps when using 5G Systems for media production. This Technical Report provides a detailed description of existing media production content delivery protocols for audio-visual, camera control (Tally, lighting control, etc) and talkback media data. The TR contains a summary of the NMOS based media device and network orchestration solution, which is often used in combination with ST 2110 based production networks. Finally, it contains a set of key issues with according solutions. While the study has not identified an urgent technical area for standardisation at this point in time, a number of practical guidelines for implementers are identified and documented in the TR. Those are intended to support media production device manufactures and media producers to leverage different 3GPP features for their purposes. These guidelines may be further promoted and expanded, and more specific aspects are likely worthwhile to be defined. Changes since last presentation to SA Meeting #96: The documentation of solutions and key issues have been finalized, conclusions and recommendations are documented. Outstanding Issues: None Contentious Issues: None.","secretary_remarks":"Block Approved","agenda_item_sort_order":45,"ainumber":"6.11","ainame":"Specifications for Approval \/ for Information and Approval","tdoc_agenda_sort_order":11670,"status":"approved","reservation_date":"2022-05-31 15:27:30","uploaded":"2022-06-01 16:01:09","revisionof":"","revisedto":"","release":"Rel-17","crspec":"26.805","crspecversion":"2.0.0","workitem":[{"winame":"FS_NPN4AVProd"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_96_Budapest_2022_06\/Docs\/SP-220606.zip","group":"SP","meeting":"SP-96","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-220607","title":"TR 26.955, Version 2.0.0, '5G Video Codec Characteristics'","source":"SA WG4","contact":"Jayeeta Saha","contact-id":85340,"tdoctype":"draft TR","for":"Approval","abstract":"Abstract of document: The Technical Report provides a full characterization framework for video codecs in the context of 5G services. This framework permits the evaluation of the performance of existing 3GPP codecs, and also permits the identification of potential benefits of new codecs. The framework fulfils the following aspects: - A comprehensive set of scenarios relevant to 3GPP services is described in clause 6. For each scenario the anchor(s), the version of the reference software for the anchor(s), and their configuration(s) are defined. - A set of reference sequences is identified per scenario and each sequence is described in more details in Annex C. - For each scenario, one or more performance metrics are defined. Each metric is described in more details in clause 5.5 - The overall characterization framework process is defined in clause 5 and in Annex B, D, E, F, and G. - New codecs are identified in clause 8. For each scenario, a version of their respective reference software is identified and configurations as close as possible to the anchor configurations are defined. The framework clearly has some limitations; for example, encoder configurations for each scenario may have not been stringent enough in the definition, leading to results that may not be fully comparable. Further, the encoders used for the evaluation of the various codecs have different maturity and features. Results in this document should always be considered with caution, and the reader should understand how these results were derived. The framework does not include subjective evaluation; it is purely based on objective metrics. Results are complete for 3GPP codecs - H.264\/AVC and H.265\/HEVC - for all scenarios. One important outcome of the work documented in this Technical Report is the characterization and evaluation of H.265\/HEVC against relevant scenarios and its characterization against H.264\/AVC. Also, a first understanding of H.265\/HEVC performances versus new codecs was developed. From the scenarios and results in this Technical Report it is observed that: - H.265\/HEVC does not show any functional deficiencies or gaps, nor does it lack any relevant features. - In terms of compression efficiency, H.265\/HEVC, evaluated based on the HM, performs sufficiently well for all the scenarios in this technical report. Providing consistent HEVC-based interoperability in 3GPP services, for traditional and new scenarios, is definitely beneficial. It is recommended that 3GPP consider upgrading specifications to support profiles, levels, and possibly features available in HEVC. Features may include better support for screen content and computer-generated content, XR\/AR type of services, as well as low and very low latency services. The framework and the initial results for new codecs, while demonstrating coding performance improvements over H.265\/HEVC, are not mature enough to support concrete recommendations. The potential addition of any new codec in 3GPP services and specifications requires diligent preparation, including the identification of needs and requirements for different scenarios, as well as a complete characterization against existing codecs. The information in this TR, as well as any new developments in 3GPP with respect to codecs in latest specifications, could serve as a baseline for future work. Such an effort may lead to conclusions on the potential addition of any new codec in 3GPP services and specifications. However, no immediate need has been identified to initiate such follow-up work. Changes since last presentation to SA Meeting 91: The following aspects are still outstanding: - Selection of reference sequences for FullHD and Messaging scenario - Anchor definition and generation for FullHD, 4K-TV and messaging scenario for HEVC - Anchor definition and generation for H.264\/AVC - Test results for new codecs - Verification of all results - Characterization of new codecs - Gap analysis for video in 5G - Conclusions Outstanding Issues:","secretary_remarks":"Block Approved","agenda_item_sort_order":45,"ainumber":"6.11","ainame":"Specifications for Approval \/ for Information and Approval","tdoc_agenda_sort_order":11680,"status":"approved","reservation_date":"2022-05-31 15:27:32","uploaded":"2022-06-01 16:01:09","revisionof":"","revisedto":"","release":"Rel-17","crspec":"26.955","crspecversion":"2.0.0","workitem":[{"winame":"FS_5GVideo"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_96_Budapest_2022_06\/Docs\/SP-220607.zip","group":"SP","meeting":"SP-96","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]