[{"name":"SP-220098","title":"New WID on Interconnection and Migration Aspects for Railways","source":"SA WG6","contact":"Bernt Mattsson","contact-id":14585.0,"tdoctype":"WID new","for":"Approval","abstract":"Objective: In order to satisfy remaining interconnection and migration needs for railways, enhancements to technical specifications for MCPTT (3GPP TS 23.379), MCVideo (3GPP TS 23.281), MCData (3GPP TS 23.282) and in the common functional architecture (3GPP TS 23.280) are foreseen. The focus is on the following (according to the study results): 1) Functional architecture enhancements to support location information for interconnected MC systems, including information flows and procedures. 2) Private call using a functional alias towards a partner MC system. 3) Migration towards another MC system during ongoing private communications. 4) Migration towards another MC system during ongoing group communications. 5) Optimize connectivity between MC systems for media and signalling routing and the IP connectivity between MC systems. 6) Support of migration for MC service users towards an MC system when the primary and the partner MC system are not interconnected. 7) Support of private call forwarding between MCPTT systems. 8) Support of private call transfer between MCPTT systems. No dependencies to other 3GPP groups were identified during study phase.","secretary_remarks":"CC#3: Block Approved","agenda_item_sort_order":39,"ainumber":"6.5","ainame":"New Release 18 Work Item Descriptions","tdoc_agenda_sort_order":11420,"status":"approved","reservation_date":"2022-03-02 23:37:26","uploaded":"2022-03-09 20:55:47","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_95E_Electronic_2022_03\/Docs\/SP-220098.zip","group":"SP","meeting":"SP-95-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-220099","title":"New WID on support of the 5GMSG Service phase 2","source":"SA WG6","contact":"Bernt Mattsson","contact-id":14585.0,"tdoctype":"WID new","for":"Approval","abstract":"Objective: This work item is to develop application layer solutions where it is necessary to solve the remaining technical issues in Rel-17. The issues are including (but not limited to): a) the procedures in multiple MSGin5G Server scenario, i.e. the sender and receiver of message are served by different MSGin5G Servers. The sender and the receiver can be in the same PLMN or different PLMNs. E.g: how the message delivery based on Messaging Topic works in this scenario; NOTE 1 When the sender and the receiver are in the same PLMN, they may be served by MSGin5G Servers provided by different vendors, so the procedures between MSGin5G Servers are needed to be specified. b) bulk configuration and bulk registration for UEs, e.g. Non-MSGin5G UEs or constrained devices, and Application Servers; c) the procedures and potential architectural enhancement to support Broadcast massaging either by invoking CBCF or xMBS; d) the procedures, e.g. configuration, registration, for constrained device and relay UE by using MSGin5G-6 reference point; e) the APIs (if necessary) for constrained device by using MSGin5G-5 reference point; f) the service logic between some features, e.g. 1) service logic between message aggregation and segment. If an aggregated message is sent to a recipient whose supported message segment size is smaller than the aggregated message, will the message be split or segmented; 2) service logic between store forward and device triggering. If store and forward is allowed by an MSGin5G message and device triggering is supported by the recipient, how the MSGin5G Server works; etc; and g) the potential architectural requirements to fulfil the charging requirements specified in 3GPP TS 22.262; and h) update the architecture and existing procedures based on the new solutions. NOTE 2: For potential impacts to 5G system, coordination with SA WG2 will be necessary. For potential charging requirements, coordination with SA WG5 will be necessary. NOTE 3: It is recommended that this WID has better not impact the ongoing CT Rel-17 5GMARCH WID in this stage except the necessary technical correction. The new solutions are recommended to be specified in CT WGs in Rel-18.","secretary_remarks":"Title and Acronym to be corrected. Revised to SP-220330","agenda_item_sort_order":39,"ainumber":"6.5","ainame":"New Release 18 Work Item Descriptions","tdoc_agenda_sort_order":11430,"status":"revised","reservation_date":"2022-03-02 23:37:26","uploaded":"2022-03-09 20:55:47","revisionof":"","revisedto":"SP-220330","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_95E_Electronic_2022_03\/Docs\/SP-220099.zip","group":"SP","meeting":"SP-95-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-220149","title":"New WID on 5G Advanced NRM features phase 2","source":"SA WG5","contact":"Mirko Cano Soveri","contact-id":41957.0,"tdoctype":"WID new","for":"Approval","abstract":"Objective: - Enhance NRM to support features, including architecture enhancements for the support of 5G core System Enhancement, fill the gap of 5GC NRM, and enhancement for NR. - Continue leftover of Rel17 NRM, including NR_feMIMO related attributes, stage 3 enhancement and generic NRM enhancement.","secretary_remarks":"_rev2 was approved. Revised to SP-220351.","agenda_item_sort_order":39,"ainumber":"6.5","ainame":"New Release 18 Work Item Descriptions","tdoc_agenda_sort_order":11390,"status":"revised","reservation_date":"2022-03-03 13:49:11","uploaded":"2022-03-08 12:59:18","revisionof":"","revisedto":"SP-220351","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_95E_Electronic_2022_03\/Docs\/SP-220149.zip","group":"SP","meeting":"SP-95-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-220154","title":"New WID on Enhanced Edge Computing Management","source":"SA WG5","contact":"Mirko Cano Soveri","contact-id":41957.0,"tdoctype":"WID new","for":"Approval","abstract":"Objective: The objective of the work item are as follows: 1. Specifying the leftovers from Rel-17 WID on edge computing management, including 1.1. Specifying enhancement to 3GPP NRMs supporting: 1.1.1. Lifecycle management EAS, EES, ECS and EASDF 1.1.2. EAS profile configurations 1.2. Performance Assurance: Specifying appropriate and remaining performance measurements and KPIs for EAS, EES, ECS and EASDF in TS 28.552 and TS 28.554 1.3. Fault Supervision: Enabling 5GC NF alarms collection to support EAS fault supervision 1.4. Specifying enhancements of provisioning MnS needed to support the asynchronous mode of operations for LCM and then update the edge LCM procedures based on the same. 2. Specify solutions to support appropriate GSMA OPG requirements on NBI as defined in GSMA OPG Telco Edge Requirements based on the conclusion and the recommendation from the study (FS_MEC_ECM), as appropriate. The management solutions specified in this WID will fulfil requirements from both SA WG6 EDGAPP architecture and SA WG2 eEDGE_5GC architecture. This work will be done in cooperation with SA WG2, SA WG6, and ETSI NFV ISG. This work will also collaborate with ETSI MEC, avoiding duplication of efforts, when working on the solution related with edge computing.","secretary_remarks":"CC#3: Block Approved","agenda_item_sort_order":39,"ainumber":"6.5","ainame":"New Release 18 Work Item Descriptions","tdoc_agenda_sort_order":11410,"status":"approved","reservation_date":"2022-03-03 13:49:11","uploaded":"2022-03-08 12:59:18","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_95E_Electronic_2022_03\/Docs\/SP-220154.zip","group":"SP","meeting":"SP-95-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-220192","title":"New WID on Security Assurance Specification (SCAS) for 5G Rel-17 Features","source":"SA WG3","contact":"Mirko Cano Soveri","contact-id":41957.0,"tdoctype":"WID new","for":"Approval","abstract":"Objective: The aim of this work is to update the security assurance related specifications in order to cover the new 5G Release 17 features. More specifically, the objectives are to: - identify threats and critical assets for 5G Release 17 features not covered in 3GPP TR 33.926; - identify specific security functional requirements and related test cases for 5G Release 17 features in the 5G SCAS documents; - develop more vulnerability testing requirements and related test cases if deemed necessary; - adopt corrections or potential new security assurance requirements identified during the course of testing practice of 5G SCAS Release 17; - Align with GSMA NESAS specifications on some aspects whenever needed to align with the NESAS documents development; This work item assumes that the SCAS will be independent of whether the NF is based or not based on virtualization architecture. Impact of virtualization is covered in separate work.","secretary_remarks":"CC#3: Block Approved","agenda_item_sort_order":39,"ainumber":"6.5","ainame":"New Release 18 Work Item Descriptions","tdoc_agenda_sort_order":11280,"status":"approved","reservation_date":"2022-03-04 09:52:37","uploaded":"2022-03-07 10:45:12","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_95E_Electronic_2022_03\/Docs\/SP-220192.zip","group":"SP","meeting":"SP-95-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-220195","title":"Revised SID on Standardising Automated Certificate Management in SBA","source":"SA WG3","contact":"Mirko Cano Soveri","contact-id":41957.0,"tdoctype":"SID revised","for":"Approval","abstract":"Objective: The objectives of this study are to identify key issues, potential security and privacy requirements and solutions with respect to - Standardise the use of a single automated certificate management protocol and procedures for certificate life cycle events within intra-PLMN 5G SBA (i.e. to be used by all 5GC NFs including NRF, SCP, SEPP etc.) - Study the impact of service mesh in certificate management within 5G SBA. - Study which lifecycle events (e.g. enrolment, renewal, revocation (e.g., OCSP, CRLs), status monitoring) of a certificate need to be covered. - Study the relation between certificate management lifecycle and NF management lifecycle. - Study to reference at minimum following principles: 1. Principle to be reusable when 5G SBA is for NPN (standalone and PNI) 2. Principles standardised to be able to support NFs doing mutual TLS in Slicing 3. Principles standardized to support both intra and inter PLMN, in the latter referring to SEPP certificates in N32 interfaces and potential cross-certification considerations. 4. Principles involving 'Chain of Trust' of Certificate Authorities hierarchies 5. Principles for security of CA's cryptographic private key","secretary_remarks":"No rev marks in _rm version. Revised to SP-220325","agenda_item_sort_order":39,"ainumber":"6.5","ainame":"New Release 18 Work Item Descriptions","tdoc_agenda_sort_order":11290,"status":"revised","reservation_date":"2022-03-04 09:52:37","uploaded":"2022-03-07 10:45:12","revisionof":"","revisedto":"SP-220325","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"FS_ACM_SBA"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_95E_Electronic_2022_03\/Docs\/SP-220195.zip","group":"SP","meeting":"SP-95-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-220197","title":"New WID on Security Assurance Specification for the Authentication and Key Management for Applications (AKMA) Anchor Function Function (AAnF)","source":"SA WG3","contact":"Mirko Cano Soveri","contact-id":41957.0,"tdoctype":"WID new","for":"Approval","abstract":"Objective: The objective is to develop the SCAS for the AAnF network product class, with the aims to: - identify critical assets and threats of the AAnF not already identified in TR 33.926 - develop and\/or adapt AAnF specific security functional requirements and related test cases - develop and\/or adapt AAnF specific basic vulnerability testing requirements and related test cases","secretary_remarks":"CC#3: Block Approved","agenda_item_sort_order":39,"ainumber":"6.5","ainame":"New Release 18 Work Item Descriptions","tdoc_agenda_sort_order":11310,"status":"approved","reservation_date":"2022-03-04 09:52:37","uploaded":"2022-03-07 10:45:12","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_95E_Electronic_2022_03\/Docs\/SP-220197.zip","group":"SP","meeting":"SP-95-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-220198","title":"New Study of Security aspect of home network triggered primary authentication","source":"SA WG3","contact":"Mirko Cano Soveri","contact-id":41957.0,"tdoctype":"SID new","for":"Approval","abstract":"Objective: The objective of this study is to: 1) Study the use cases which needs HN initiated primary authentication and the associated security threats and requirements. As part of this investigation, the study aims at identifying which network function in the HN is better suitable to trigger the primary authentication, and corresponding procedures, and the potential impacts on visited and home network, and the existing procedures. 2) Investigate solutions for potential normative work.","secretary_remarks":"CC#3: Block Approved","agenda_item_sort_order":39,"ainumber":"6.5","ainame":"New Release 18 Work Item Descriptions","tdoc_agenda_sort_order":11320,"status":"approved","reservation_date":"2022-03-04 09:52:37","uploaded":"2022-03-07 13:11:17","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_95E_Electronic_2022_03\/Docs\/SP-220198.zip","group":"SP","meeting":"SP-95-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-220199","title":"New Study on security aspects of enablers for Network Automation for 5G - phase 3","source":"SA WG3","contact":"Mirko Cano Soveri","contact-id":41957.0,"tdoctype":"SID new","for":"Approval","abstract":"Objective: The aim of this study item is to study the security aspects of enablers for network automation for the 5G-phase 3. More specifically, this study item will identify security issues and requirements and provide corresponding security solutions related to the following scenarios: - Security aspects of potential architecture enhancement: roaming, supporting federated learning, interaction between NWDAF and MDAS\/MDAF, etc. - Handling of sensitive information inherent to application detection, roaming and location information. - KIs from R17 which don't have enough time to proceed, e.g. NWDAF detection related issues. - Any further security enhancements which need to be studied based upon the ongoing SA WG2 eNA Phase 3 work","secretary_remarks":"CC#3: Block Approved","agenda_item_sort_order":39,"ainumber":"6.5","ainame":"New Release 18 Work Item Descriptions","tdoc_agenda_sort_order":11330,"status":"approved","reservation_date":"2022-03-04 09:52:37","uploaded":"2022-03-07 10:45:12","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_95E_Electronic_2022_03\/Docs\/SP-220199.zip","group":"SP","meeting":"SP-95-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-220200","title":"New WID on SCAS for split-gNB product classes","source":"SA WG3","contact":"Mirko Cano Soveri","contact-id":41957.0,"tdoctype":"WID new","for":"Approval","abstract":"Objective: The objective is to create SCAS specifications for split gNB entities. Specifically, the objectives of this work item are to: - identify threats and critical assets for split gNB entities not already identified in TR 33.926; - identify specific security functional requirements and related test cases for split gNB entities; - develop more vulnerability testing requirements and related test cases if deemed necessary; - adopt corrections or potential new security assurance requirements identified during the course of testing practice of 5G SCAS; - add the necessary test cases for split gNBs (i.e. CU, DU, CU-CP, CU-UP); and - align with GSMA NESAS specifications as NESAS documents are developed.","secretary_remarks":"CC#3: Block Approved","agenda_item_sort_order":39,"ainumber":"6.5","ainame":"New Release 18 Work Item Descriptions","tdoc_agenda_sort_order":11340,"status":"approved","reservation_date":"2022-03-04 09:52:37","uploaded":"2022-03-07 10:45:12","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_95E_Electronic_2022_03\/Docs\/SP-220200.zip","group":"SP","meeting":"SP-95-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-220201","title":"New Study on Security Enhancement of support for Edge Computing \u2014 phase 2","source":"SA WG3","contact":"Mirko Cano Soveri","contact-id":41957.0,"tdoctype":"SID new","for":"Approval","abstract":"Objective: The objective of this work is to study the security aspects related to the new features and procedures resulting from the continuation of the work on Edge Computing support in 5G Systems, a.k.a. phase 2. The study will include: - The key issues, threats and potential requirements related to the Edge Computing, phase 2 work, such as, o The security protection for exposing network information to the AF by UPF, o Security aspect on the roaming, etc. - The potential solutions to meet such requirements. NOTE 1: The study will be based on SA WG2, SA WG6's work, and the existing security procedures defined in Rel17.","secretary_remarks":"CC#3: Block Approved","agenda_item_sort_order":39,"ainumber":"6.5","ainame":"New Release 18 Work Item Descriptions","tdoc_agenda_sort_order":11350,"status":"approved","reservation_date":"2022-03-04 09:52:37","uploaded":"2022-03-07 10:45:12","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_95E_Electronic_2022_03\/Docs\/SP-220201.zip","group":"SP","meeting":"SP-95-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-220202","title":"New Study on Security Aspects of Proximity Based Services in 5GS Phase 2","source":"SA WG3","contact":"Mirko Cano Soveri","contact-id":41957.0,"tdoctype":"SID new","for":"Approval","abstract":"Objective: The objective is to study the security and privacy aspects of proximity based services in 5G system phase 2 while basing this study on ProSe security specified in Rel-17. Ensure that security solutions are aligned with the work in SA WG2 (i.e., TR 23.700-33), RANs, SA WG1 (i.e., TS 22.278, TS 22.261, and TS 22.115) and SA WG3 (i.e., TS 33.503 and TR 33.870). The work is comprised of the following parts: - Study the security key issues, threats and requirements of proximity based services in 5G system phase 2. - Elaborate on the potential security solutions to cover these requirements. Both non-roaming and roaming scenarios will be considered. NOTE: Timely feedback on supporting SA WG2\/RAN study needs to be considered.","secretary_remarks":"CC#3: Block Approved","agenda_item_sort_order":39,"ainumber":"6.5","ainame":"New Release 18 Work Item Descriptions","tdoc_agenda_sort_order":11360,"status":"approved","reservation_date":"2022-03-04 09:52:37","uploaded":"2022-03-07 10:45:12","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_95E_Electronic_2022_03\/Docs\/SP-220202.zip","group":"SP","meeting":"SP-95-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-220241","title":"New WID on immersive Real-time Communication for WebRTC","source":"SA WG4","contact":"Jayeeta Saha","contact-id":85340.0,"tdoctype":"WID new","for":"Approval","abstract":"Objective: It is proposed to conduct the following work: Objective: 1: Define a non-vertical\/modularized protocol stack for iRTC clients to support WebRTC-based real-time transport of media over 5G that, - Identifies and integrates WebRTC components into the 5G system, leveraging the 5G_RTP work on RTP optimization and integration - Develops APIs necessary to expose the functionality of these components to features, services, mobile operating systems and applications. Objective: 2: Define functional components of an iRTC client in terminal that (as in Figure 1 of TS 26.110 where video and audio I\/Os are connected to 3G-324M protocol architecture), - Support traditional 3GPP real-time media (e.g., 2D video and EVS mono audio) - Support immersive media including 3D video and spatial audio, leveraging the audio inputs\/outputs considered for IVAS and, where applicable, referencing the immersive audio quality tests defined by ATIAS - Support immersive data channel media via WebRTC-based data channel (including QUIC if adopted by W3C for WebRTC) - Enable interworking with devices tethered to the UE as defined in Table 4.2.2.1-1 of TR 26.998 - Extend architecture and components as defined in Figure 4.2 of TS 26.114 appropriately for WebRTC-based applications - Specify sensor information required \/ recommended for media handling that, - Identifies information to be consumed locally or transmitted with media (e.g., pose info.) - Leverages sensor information currently provided by mobile operating systems when appropriate - Support relevant metadata about user and environment (e.g., user\/object position and direction). Objective: 3: Define inputs into an iRTC client in terminal and their required \/ recommended parameters, if any. This includes outputs from cameras \/ microphones (e.g., N depth streams \/ M RGB streams & their relationships or direction of microphones, in compact and scalable descriptions) with a focus on practical mobile implementations. (More advanced device configurations, e.g., studio-class cameras and microphone set-ups can be considered when available). Objective: 4: Identify the required architecture for radio access network QoS realization over 5G systems, using WebRTC-based transport. Objective: 5: Identify the minimum information \/ elements in the C\/U-Plane signal to establish media sessions with appropriate QoS for WebRTC-based applications. Objective: 6: Document informative examples of iRTC operations to assist implementers.","secretary_remarks":"CC#3: Block Approved","agenda_item_sort_order":39,"ainumber":"6.5","ainame":"New Release 18 Work Item Descriptions","tdoc_agenda_sort_order":11370,"status":"approved","reservation_date":"2022-03-04 19:46:11","uploaded":"2022-03-09 19:31:12","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_95E_Electronic_2022_03\/Docs\/SP-220241.zip","group":"SP","meeting":"SP-95-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-220242","title":"New WID on Media Capabilities for Augmented Reality (MeCAR)","source":"SA WG4","contact":"Jayeeta Saha","contact-id":85340.0,"tdoctype":"WID new","for":"Approval","abstract":"Objective: This work item defines service-independent media capabilities for AR devices. In particular, the following objectives are considered: - Define at least one AR device category that addresses the constraints of an EDGAR-type AR glass o Note: Additional device categories may be defined, but with lower priority. - For each AR device category o Define a reference terminal architecture regarding media capability aspects for this AR device category o Define media types and formats produced and consumed by the AR device, including basic scene descriptions, audio, graphics and video as well as sensor information and metadata about user and environment. o Define the integration of the relevant existing 3GPP codecs into the reference terminal architecture o Define decoding capabilities, including support for multiple parallel decoders o Define encoding capabilities o Define security aspects related to the media capabilities o Define the required, recommended and optional media capabilities for this AR device category - Integrate IVAS into suitable AR device categories, once IVAS is available - Define capability exchange mechanisms based on complexity of AR media and capability of device to support EAS KPIs for provisioning of edge\/cloud resources o Note: Identify a suitable existing capability framework, or if it does not exist, we need to work with the broader industry (e.g., IETF, KHRONOS, W3C, etc.) to get this done. - Identify which QoE metrics from VR QoE metrics can be reused or enhanced for AR media (e.g., resolution per eye, Field of view (FOV), round-trip interaction delay, etc.) and define relevant KPIs that are dedicated to AR\/MR - Specify additional relevant KPIs and simple QoE Metrics for AR media - Specify encapsulations into RTP, ISOBMFF and CMAF - Specify the relevant codec-level parameters for session setup and negotiation of the media delivery and provide instantiations for SDP and DASH MPD - Enable AR media in 5G Media Streaming by defining suitable 5GMS profiles based on AR media capabilities - Define typical traffic characteristics for AR media","secretary_remarks":"CC#3: Block Approved","agenda_item_sort_order":39,"ainumber":"6.5","ainame":"New Release 18 Work Item Descriptions","tdoc_agenda_sort_order":11380,"status":"approved","reservation_date":"2022-03-04 19:46:11","uploaded":"2022-03-09 19:31:12","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_95E_Electronic_2022_03\/Docs\/SP-220242.zip","group":"SP","meeting":"SP-95-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-220325","title":"Revised SID on Standardising Automated Certificate Management in SBA","source":"SA WG3","contact":"Mirko Cano Soveri","contact-id":41957.0,"tdoctype":"SID revised","for":"Approval","abstract":"Updates Release, justification and objetives","secretary_remarks":"Revision of SP-220195. CC#3: Block Approved","agenda_item_sort_order":39,"ainumber":"6.5","ainame":"New Release 18 Work Item Descriptions","tdoc_agenda_sort_order":11300,"status":"approved","reservation_date":"2022-03-10 16:29:13","uploaded":"2022-03-10 16:57:44","revisionof":"SP-220195","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"FS_ACM_SBA"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_95E_Electronic_2022_03\/Docs\/SP-220325.zip","group":"SP","meeting":"SP-95-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-220330","title":"New WID on support of the MSGin5G Service phase 2","source":"SA WG6","contact":"Bernt Mattsson","contact-id":14585.0,"tdoctype":"WID new","for":"Approval","abstract":"Objective: This work item is to develop application layer solutions where it is necessary to solve the remaining technical issues in Rel-17. The issues are including (but not limited to): a) the procedures in multiple MSGin5G Server scenario, i.e. the sender and receiver of message are served by different MSGin5G Servers. The sender and the receiver can be in the same PLMN or different PLMNs. E.g: how the message delivery based on Messaging Topic works in this scenario; NOTE 1 When the sender and the receiver are in the same PLMN, they may be served by MSGin5G Servers provided by different vendors, so the procedures between MSGin5G Servers are needed to be specified. b) bulk configuration and bulk registration for UEs, e.g. Non-MSGin5G UEs or constrained devices, and Application Servers; c) the procedures and potential architectural enhancement to support Broadcast massaging either by invoking CBCF or xMBS; d) the procedures, e.g. configuration, registration, for constrained device and relay UE by using MSGin5G-6 reference point; e) the APIs (if necessary) for constrained device by using MSGin5G-5 reference point; f) the service logic between some features, e.g. 1) service logic between message aggregation and segment. If an aggregated message is sent to a recipient whose supported message segment size is smaller than the aggregated message, will the message be split or segmented; 2) service logic between store forward and device triggering. If store and forward is allowed by an MSGin5G message and device triggering is supported by the recipient, how the MSGin5G Server works; etc; and g) the potential architectural requirements to fulfil the charging requirements specified in 3GPP TS 22.262; and h) update the architecture and existing procedures based on the new solutions. NOTE 2: For potential impacts to 5G system, coordination with SA WG2 will be necessary. For potential charging requirements, coordination with SA WG5 will be necessary. NOTE 3: It is recommended that this WID has better not impact the ongoing CT Rel-17 5GMARCH WID in this stage except the necessary technical correction. The new solutions are recommended to be specified in CT WGs in Rel-18.","secretary_remarks":"Revision of SP-220099. CC#3: Block Approved","agenda_item_sort_order":39,"ainumber":"6.5","ainame":"New Release 18 Work Item Descriptions","tdoc_agenda_sort_order":11440,"status":"approved","reservation_date":"2022-03-11 09:28:01","uploaded":"2022-03-11 09:59:03","revisionof":"SP-220099","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_95E_Electronic_2022_03\/Docs\/SP-220330.zip","group":"SP","meeting":"SP-95-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-220351","title":"New WID on 5G Advanced NRM features phase 2","source":"SA WG5","contact":"Mirko Cano Soveri","contact-id":41957.0,"tdoctype":"WID new","for":"Approval","abstract":"Objective: - Enhance NRM to support features, including architecture enhancements for the support of 5G core System Enhancement, fill the gap of 5GC NRM, and enhancement for NR. - Continue leftover of Rel17 NRM, including NR_feMIMO related attributes, stage 3 enhancement and generic NRM enhancement.","secretary_remarks":"Revision of SP-220149_rev2. This WID NEW was approved","agenda_item_sort_order":39,"ainumber":"6.5","ainame":"New Release 18 Work Item Descriptions","tdoc_agenda_sort_order":11400,"status":"approved","reservation_date":"2022-03-18 17:40:15","uploaded":"2022-03-18 17:41:11","revisionof":"SP-220149","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_95E_Electronic_2022_03\/Docs\/SP-220351.zip","group":"SP","meeting":"SP-95-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]