[{"name":"S2-2411332","title":"KI#8: Architecture for avatar communications","source":"Samsung, [ZTE, vivo, Huawei, HiSilicon]","contact":"DongYeon Kim","contact-id":87763,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The description of IMS DC based avatar communication is introduced. [R04: SA WG2#166] Editor's Notes in clause AC.X.1 General is cleared. Note regarding DC AS URL is clarified. Function description of IMS AS is added in clause AC.X.2. Reference points are added in clause AC.X.2. Procedures are newly added as clause AC.X.3. Service operation parameter is added in clause AA.2.4.2.2.","secretary_remarks":"Revision of (agreed) S2-2411010. Revised in parallel session to S2-2412396.","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":12530,"status":"revised","reservation_date":"2024-10-30 07:43:10","uploaded":"2024-11-08 17:25:34","revisionof":"S2-2411010","revisedto":"S2-2412396","release":"Rel-19","crspec":"23.228","crspecversion":"19.0.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1480.0,"crrevision":4.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2411332.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":true,"clauses_affected":"AA.2.4.2.2, AC.X (new)","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2411333","title":"KI#3: DC interworking with MTSI UE","source":"Samsung, [Ericsson]","contact":"DongYeon Kim","contact-id":87763,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Descriptions on different types of DC interworking with MTSI UE are introduced. It includes the transcoding between the data channel media and the MMTeL media, the DCAS triggering the corresponding actions for terminating MTSI UE and the originating MTSI UE. In addition, Add EN to cover the missing enhancements to services to support the feature. Correctly describe the role to be performed by the MF. Complete some of the steps. Added in rev 4 (SA WG2#166): Editorial fix in AC.7.9.0 General Editorial fix in AC.7.9.1 Editorial fix in AC.7.9.2 The ENs in AC.7.9.3 are resolved by the updated Figure AC.7.9.3-1, steps 1a-1e, and steps 6a-6e. The EN in AC.7.9.0 is resolved by AC.7.9.4.","secretary_remarks":"Revision of (agreed) S2-2410973. Revised in parallel session to S2-2412636.","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":13290,"status":"revised","reservation_date":"2024-10-30 08:11:19","uploaded":"2024-11-08 17:43:21","revisionof":"S2-2410973","revisedto":"S2-2412636","release":"Rel-19","crspec":"23.228","crspecversion":"19.0.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1479.0,"crrevision":4.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2411333.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"AC.2.2.3, AC.7.9, AC.7.9.0 (new), AC.7.9.1, AC.7.9.2, AC.7.9.3, AC.7.9.4 (new)","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2411469","title":"Address ENs in IMS AS Session Management Service","source":"[ZTE, Qualcomm, Huawei], NTT DOCOMO","contact":"Jari Mutikainen","contact-id":38346,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Address the ENs for Nimsas_ImsSessionManagement Service in clause AA.2.4.4 of TS 23.228. Rev-3: Add Nimsas_ImsSessionManagement_Notify service operation. Correct the conditions to include MDC2 media endpoint address into Media information set.","secretary_remarks":"Revision of (agreed) S2-2410967. Revised in parallel session to S2-2412465, merging S2-2411605","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":13020,"status":"revised","reservation_date":"2024-06-11 16:08:04","uploaded":"2024-11-08 14:58:05","revisionof":"S2-2410967","revisedto":"S2-2412465","release":"Rel-19","crspec":"23.228","crspecversion":"19.0.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1483.0,"crrevision":3.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2411469.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2411471","title":"KI#1: IMS Subscribe\/Notify Framework Architecture","source":"Ericsson, [Nokia, T-Mobile USA, NTT DOCOMO, Qualcomm, Samsung]","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1. A new NEF service, based on SUBSCRIBE\/NOTIFY request, is defined for the IMS events and event categories. Event categories includes a collection of individual events. 2. Subscriber specific events and non-subscriber specific events are supported. 3. A subscriber specific request includes the targeted subscribers. The targeted subscriber(s) can be either one distinct subscriber, or multiple subscribers given as a list. The events in the request are common for all targeted subscribers. This request is sent to the HSS instance(s) serving the given subscribers. 4. HSS supports the handling of subscriber specific requests. To that effect, the subscribe requests that are subscriber specific are sent from the NEF to HSS. HSS handles registered and unregistered UEs and ensures that a subscription is persistent when UE registers, deregisters and re-registers in IMS. Hence, HSS stores the subscription request and sends the subscription request to the IMS AS whenever the IMS AS instance supporting the requested event is assigned to the UE. The information about the subscription events stored in HSS is only relevant and consumed by HSS. NEF and AF use a new service to manage subscription requests (e.g. subscribe\/unsubscribe) via HSS for subscriber specific events. 5. The IMS AS instance assigned to a UE during IMS registration is registered in HSS. Existing SBI Nhss_ImsUECM service used for S-CSCF is enhanced to allow the registration of the IMS AS instance in HSS over N71\/Sh. 6. Subscription requests that are non-subscriber specific are sent directly to all IMS AS instances configured in the PLMN. 7. Notifications related to a subscription is sent directly to the NF (e.g. NEF or AF) that triggered the subscription request Enhance Nhss to support IMS AS registration, deregistration. Support a new service Nhss_ImsEE to enable subscription to subscriber related events. Support a new service Nimsas_ImsEE to enable subscription to subscriber related events, as well as non-subscriber related events. Support a new service Nnef_ImsEE to enable subscription to subscriber related events, as well as non-subscriber related events. Update to the CR. Two editor notes are addressed: Handling of subscription to a number of events in a single subscription. Completing the definition of event filters for IMS DC events supported in this release. A new Editor note is also included: The mapping of Sh messages to HSS or IMS AS SBI services is FFS. NOTE: Change on change will be removed when a clean revision is produced.","secretary_remarks":"Revision of (agreed) S2-2410974. Revised in parallel session to S2-2412403, merging S2-2412167, S2-2411949 and S2-2411603","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":12850,"status":"revised","reservation_date":"2024-06-11 18:18:14","uploaded":"2024-11-08 22:39:15","revisionof":"S2-2410974","revisedto":"S2-2412403","release":"Rel-19","crspec":"23.228","crspecversion":"19.0.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1409.0,"crrevision":9.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2411471.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"Annex XX (new), AA.2.1.1, AA.2.1.2.1, AA.2.1.2.2, AA.2.1.X (new), AA.2.2.3, AA.2.4.1AA.2.4.2, AA.2.4.2.2, AA.2.4.2.3 AA.2.X (new), AC.2.2.4, AC.2.2.6","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2411472","title":"KI#1: Enhancements to NEF Services","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: List the Nnef_ImsEE services and makes reference to 23.228 for its description. The list of supported IMS events is included in the NF profile of IMS AS. IMS AS is added as consumer of NRF services. This was missing in the baseline. Update to the CR to remove the editors note on parameter design and complete the service description. NOTE: Change on change will be removed when a clean revision is produced.","secretary_remarks":"Revision of (agreed) S2-2411188. Revised in parallel session to S2-2412404, merging S2-2412168 and S2-2412091","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":12920,"status":"revised","reservation_date":"2024-06-11 18:18:19","uploaded":"2024-11-08 22:39:15","revisionof":"S2-2411188","revisedto":"S2-2412404","release":"Rel-19","crspec":"23.502","crspecversion":"19.1.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":4872.0,"crrevision":8.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2411472.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.2.6.1, 5.2.6.X (NEW), 5.2.7.1, 5.2.7.2.2.","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2411473","title":"KI#8: Architecture for avatar communications","source":"Ericsson, [Samsung, ZTE, vivo, Huawei, HiSilicon]","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The description of IMS DC based avatar communication is introduced.","secretary_remarks":"Revision of (agreed) S2-2411010 Not Handled","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":12580,"status":"not treated","reservation_date":"2024-06-11 18:18:19","uploaded":"2024-11-08 22:39:15","revisionof":"S2-2411010","revisedto":"","release":"Rel-19","crspec":"23.228","crspecversion":"19.0.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1480.0,"crrevision":5.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2411473.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":true,"clauses_affected":"AC.X (new)","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2411519","title":"Procedures of IMS Avatar communication","source":"Qualcomm Incorporated","contact":"Kefeng Zhang","contact-id":103832,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add Avatar procedures for both UE centric and network centric based modes.","secretary_remarks":"Not Handled","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":12610,"status":"not treated","reservation_date":"2024-07-11 03:49:11","uploaded":"2024-11-08 12:23:21","revisionof":"","revisedto":"","release":"Rel-19","crspec":"23.228","crspecversion":"19.0.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1506.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2411519.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":true,"clauses_affected":"AC.X.3 (new), AC.X.3.1 (new), AC.X.3.1.1 (new), AC.X.3.1.2 (new),  AC.X.3.2 (new),","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2411562","title":"Update NEF services to support the conclusion of KI#1 and KI#2","source":"[Huawei, HiSilicon, Qualcomm, ZTE, Samsung], NTT DOCOMO","contact":"Jari Mutikainen","contact-id":38346,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Enhance the NEF service to support IMS event subscription\/notification and data channel establishment, update and termination. Rev-3: Add Nnef_ImsSessionManagement_Notify service operation","secretary_remarks":"Revision of (agreed) S2-2411012. Revised in parallel session to S2-2412467.","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":13150,"status":"revised","reservation_date":"2024-07-11 10:29:50","uploaded":"2024-11-08 14:58:05","revisionof":"S2-2411012","revisedto":"S2-2412467","release":"Rel-19","crspec":"23.502","crspecversion":"19.1.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":5087.0,"crrevision":3.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2411562.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2411589","title":"Network Capability Exposure Procedure","source":"Huawei, HiSilicon, Qualcomm, Samsung, ZTE","contact":"Jari Mutikainen","contact-id":38346,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add the procedures of IMS data channel capabilies exposure. Rev-4: 1. Resolving the EN: 'Whether and how to have intermediate call notification during the procedure is FFS'. In the current procedure, the DC AS needs to wait until both UEs have accepted or rejected the session (or session modification) until it receives the response to the request (HTTP 2xx). It is proposed to add a subscribe\/notify operations under the Nimsas_IMSSessionManagement service, so that the response indicating whether the request is accepted or rejected can be provided immediately, and the actual IMS session progress with the UEs is reported via notify service operation. In this way, the NEF uses the callback URI to find the IMS AS, and discovery from HSS is not needed, and the EN 'the service for step 2 is FFS' on how to discover the IMS AS can be removed. 2. The current procedure refers to OMA API that can be used to notify the non-DC related IMS session events to the DC AS. The OMA API needs to provide a callback URI that the DC AS can use to target the update-request to the same IMS AS that send the notification (and who is anchoring the IMS session). It should be noted that OMA API cannot be used to notify for DC-related events; the item 1 in this CR is used for DC-related events. 3. Resolving the EN 'The need for a new event in step 4 is FFS': it is proposed to re-use the existing Nimsas_SessionEventControl_Notify service operation. The notify request must be enhanced to include the Media information set that the IMS AS has received in Nimsas_ImsSessionManagement_Create or _Update request from the NEF, and new Event IDs: '3rd party session update' and '3rd party session creation'. The media information set indicates to the DCSF the DC type (P2A, P2A2P, P2P, or BDC) and e.g. the MDC2 media end point address if a new DC is added with the DC AS. 4. It is proposed to merge the procedures for adding of data channels and removing of a data channels. 5. Editorial changes.","secretary_remarks":"Revision of agreed) S2-2411011. Revised in parallel session to S2-2412466, merging S2-2412111","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":13080,"status":"revised","reservation_date":"2024-07-11 12:45:24","uploaded":"2024-11-08 14:58:05","revisionof":"S2-2411011","revisedto":"S2-2412466","release":"Rel-19","crspec":"23.228","crspecversion":"19.0.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1489.0,"crrevision":4.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2411589.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"AA.2.4.2, Annex XX (new)","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2411602","title":"Update to Bootstrap and Application Data Channel Setup Signalling Procedure for data channel interworking","source":"SA WG2","contact":"Yi Jiang","contact-id":40863,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Provide the updated procedure for the case Bootstrap and Application Data Channel Setup, when the originating DCMTSI UE initiates an IMS DC session to the terminating MTSI UE. Add interworking instruction parameter to IMS AS services and MF services, so that DCSF can send interworking instruction from DCSF to MF.","secretary_remarks":"Not Handled","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":13340,"status":"not treated","reservation_date":"2024-07-11 14:10:29","uploaded":"2024-11-08 22:24:36","revisionof":"","revisedto":"","release":"Rel-19","crspec":"23.228","crspecversion":"19.0.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1508.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2411602.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"AC.7.9.1, AC.7.9.2, AC.7.9.3, AA.2.4.3.2, AA.2.5.2.2, AA.2.5.2.3","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2411603","title":"KI#1: IMS Subscribe\/Notify Framework Architecture","source":"[Ericsson, Nokia, T-Mobile USA, NTT DOCOMO, Qualcomm, Samsung], China Mobile","contact":"Yi Jiang","contact-id":40863,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1. A new NEF service, based on SUBSCRIBE\/NOTIFY request, is defined for the IMS events and event categories. Event categories includes a collection of individual events. 2. Subscriber specific events and non-subscriber specific events are supported. 3. A subscriber specific request includes the targeted subscribers. The targeted subscriber(s) can be either one distinct subscriber, or multiple subscribers given as a list. The events in the request are common for all targeted subscribers. This request is sent to the HSS instance(s) serving the given subscribers. 4. HSS supports the handling of subscriber specific requests. To that effect, the subscribe requests that are subscriber specific are sent from the NEF to HSS. HSS handles registered and unregistered UEs and ensures that a subscription is persistent when UE registers, deregisters and re-registers in IMS. Hence, HSS stores the subscription request and sends the subscription request to the IMS AS whenever the IMS AS instance supporting the requested event is assigned to the UE. The information about the subscription events stored in HSS is only relevant and consumed by HSS. NEF and AF use a new service to manage subscription requests (e.g. subscribe\/unsubscribe) via HSS for subscriber specific events. 5. The IMS AS instance assigned to a UE during IMS registration is registered in HSS. Existing SBI Nhss_ImsUECM service used for S-CSCF is enhanced to allow the registration of the IMS AS instance in HSS over N71\/Sh. 6. Subscription requests that are non-subscriber specific are sent directly to all IMS AS instances configured in the PLMN. 7. Notifications related to a subscription is sent directly to the NF (e.g. NEF or AF) that triggered the subscription request Enhance Nhss to support IMS AS registration, deregistration. Support a new service Nhss_ImsEE to enable subscription to subscriber related events. Support a new service Nimsas_ImsEE to enable subscription to subscriber related events, as well as non-subscriber related events. Support a new service Nnef_ImsEE to enable subscription to subscriber related events, as well as non-subscriber related events. Change in revision 9: Remove the editor's note of supporting subscription to a collection of events in a single subscription request and update the procedures and services of HSS and IMS AS to support event list, because using a Event-ID representing multiple events requires pre-configuration of mapping between Event-ID and events on IMS AS and AF. Supporting a list of separate events in the subscription request has more flexibility. Moreover CT WG4 has already supported subscription of a event list in a single subscription request. Some functional descriptions in XX.2.3.2 are not for HSS, but for IMS AS, therefore the descriptions are moved to XX.2.3.3. Some other editorial changesand corrections.","secretary_remarks":"Revision of (agreed) S2-2410974. Confirm CR Revision - CR states 9! Merged into S2-2412403","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":12890,"status":"merged","reservation_date":"2024-07-11 14:10:30","uploaded":"2024-11-08 22:24:36","revisionof":"S2-2410974","revisedto":"","release":"Rel-19","crspec":"23.228","crspecversion":"19.0.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1409.0,"crrevision":10.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2411603.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2411604","title":"KI#5: Support of Data off feature for data channel","source":"[vivo, Huawei, HiSilicon, Deutsche Telekom, ZTE, Qualcomm Inc., Samsung], China Mobile","contact":"Yi Jiang","contact-id":40863,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: This contribution: Add 'Data Channel Serivces in IMS' in annex X Add a new optional parameter of PS Data Off Status in Nimsas_SessionEventControl.","secretary_remarks":"Revision of (agreed) S2-2410914 Not Handled","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":13370,"status":"not treated","reservation_date":"2024-07-11 14:10:31","uploaded":"2024-11-08 22:24:36","revisionof":"S2-2410914","revisedto":"","release":"Rel-19","crspec":"23.228","crspecversion":"19.0.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1421.0,"crrevision":4.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2411604.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":true,"clauses_affected":"X.1, X.2.3, X.3.2, AA.2.4.2.1, AA.2.4.2.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2411605","title":"Address ENs in IMS AS Session Management Service","source":"[ZTE, Qualcomm, Huawei], China Mobile","contact":"Yi Jiang","contact-id":40863,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Address the ENs for Nimsas_ImsSessionManagement Service in clause AA.2.4.4 of TS 23.228. Changes in revision 3: Adding PSI of DC AS as Calling ID; Modification on input and output of services, introducing Media Correlation ID and media resource information set Update of text format Changes in revision 4: Adding PSI as the calling ID or called ID for P2A\/A2P standalone DC session; Add media correlation ID to correlate the media components between DC AS and IMS AS; Add media resource information set as the output of creation and update operations to convey the media information of newly added media components; Remove P2P ADC type; Editorial changes to align with other service operation descriptions.","secretary_remarks":"Revision of (agreed) S2-2410967. Confirm CR Revision - CR states 3! Merged into S2-2412465","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":13060,"status":"merged","reservation_date":"2024-07-11 14:10:46","uploaded":"2024-11-08 22:24:36","revisionof":"S2-2410967","revisedto":"","release":"Rel-19","crspec":"23.228","crspecversion":"19.0.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1483.0,"crrevision":4.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2411605.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2411606","title":"Alignment of DC exposure and standalone DC with IMS DC architecture","source":"China Mobile","contact":"Yi Jiang","contact-id":40863,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Remove the limit to allow standalone DC establishment; Add the reference to Annex for IMS DC event exposure and IMS DC capability exposure. Add new clause of NEF.","secretary_remarks":"Revised in parallel session to S2-2412405.","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":12990,"status":"revised","reservation_date":"2024-07-11 14:10:48","uploaded":"2024-11-08 22:24:36","revisionof":"","revisedto":"S2-2412405","release":"Rel-19","crspec":"23.228","crspecversion":"19.0.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1509.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2411606.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"AC.1, AC.2.1, AC.2.2.4, AC.2.2.6, AC.2.2.Y(new)","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2411607","title":"KI#1: Enhancements to NEF Services","source":"[Ericsson], China Mobile","contact":"Yi Jiang","contact-id":40863,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: List the Nnef_ImsEE services and makes reference to 23.228 for its description. The list of supported IMS events is included in the NF profile of IMS AS. IMS AS is added as consumer of NRF services. This was missing in the baseline. Changes in revision 8: update the services of NEF to support subscription of event list, because using a Event-ID representing multiple events requires pre-configuration of mapping between Event-ID and events on IMS AS and AF. Supporting a list of separate events in the subscription request has more flexibility. Moreover CT WG4 has already supported subscription of a event list in a single subscription request. Correct 'Notofication Correlation information' to 'Notofication Correlation ID'.","secretary_remarks":"Revision of (agreed) S2-2411188. Confirm Specification Number - CR states 23.502, CR states 4872, CR Revision states 8,Spec version states 19.1.0! Not Handled","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":12960,"status":"not treated","reservation_date":"2024-07-11 14:10:48","uploaded":"2024-11-08 22:24:36","revisionof":"S2-2411188","revisedto":"","release":"Rel-19","crspec":"23.228","crspecversion":"19.0.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1510.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2411607.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2411608","title":"Support of multiplexing multiple DC applications over single SCTP connection","source":"China Mobile","contact":"Yi Jiang","contact-id":40863,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add functionality requirements and procedure to support multiplexing multiple DC applications over single SCTP connection.","secretary_remarks":"Revised in parallel session to S2-2412394.","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":12470,"status":"revised","reservation_date":"2024-07-11 14:10:49","uploaded":"2024-11-08 22:24:36","revisionof":"","revisedto":"S2-2412394","release":"Rel-19","crspec":"23.228","crspecversion":"19.0.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1511.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2411608.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":true,"clauses_affected":"AC.7.X (new)","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2411609","title":"Service updates to support multiplexing multiple DC applications over single SCTP connection","source":"China Mobile","contact":"Yi Jiang","contact-id":40863,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The services of IMS AS and MF are updated to support data channel multiplexing over single SCTP connection.","secretary_remarks":"Revised in parallel session to S2-2412395.","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":12500,"status":"revised","reservation_date":"2024-07-11 14:10:50","uploaded":"2024-11-08 22:24:36","revisionof":"","revisedto":"S2-2412395","release":"Rel-19","crspec":"23.228","crspecversion":"19.0.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1512.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2411609.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":true,"clauses_affected":"AA.2.4.2.2, AA.2.4.3.2, AA.2.4.5.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2411894","title":"Add DC Application Server Description","source":"ZTE","contact":"Hao Dong","contact-id":75723,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add the function description of DC Application Server.","secretary_remarks":"Not Handled","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":13400,"status":"not treated","reservation_date":"2024-08-11 08:07:14","uploaded":"2024-11-08 09:09:28","revisionof":"","revisedto":"","release":"Rel-19","crspec":"23.228","crspecversion":"19.0.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1515.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2411894.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"3.1, 3.3, AC.2.2.X(new)","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2411895","title":"KI#5: Support of Data off feature for data channel","source":"[vivo, Huawei, HiSilicon, Deutsche Telekom,] ZTE, [Qualcomm Inc., Samsung]","contact":"Hao Dong","contact-id":75723,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: This contribution: Add 'Data Channel Serivces in IMS' in annex X Add a new optional parameter of PS Data Off Status in Nimsas_SessionEventControl. Add PS Data Off Event in Table AA.2.4.2.2-1.","secretary_remarks":"Revision of (agreed) S2-2410914 Not Handled","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":13380,"status":"not treated","reservation_date":"2024-08-11 08:07:15","uploaded":"2024-11-08 09:09:28","revisionof":"S2-2410914","revisedto":"","release":"Rel-19","crspec":"23.228","crspecversion":"19.0.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1421.0,"crrevision":5.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2411895.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":true,"clauses_affected":"X.1, X.2.3, X.3.2, AA.2.4.2.1, AA.2.4.2.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2411896","title":"Transition Between IMS Avatar and Audio\/video Communication","source":"ZTE","contact":"Hao Dong","contact-id":75723,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add procedure for transition between IMS Avatar and audio\/video communication.","secretary_remarks":"Revised in parallel session to S2-2412398.","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":12670,"status":"revised","reservation_date":"2024-08-11 08:07:16","uploaded":"2024-11-08 09:09:28","revisionof":"","revisedto":"S2-2412398","release":"Rel-19","crspec":"23.228","crspecversion":"19.0.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1516.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2411896.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":true,"clauses_affected":"AC.X.y(new)","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2411897","title":"Function Description for Interworking with MTSI UE","source":"ZTE","contact":"Hao Dong","contact-id":75723,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify the function of MF and IMS AS for supporting interworking between DCMTSI UE and MTSI UE.","secretary_remarks":"Not Handled","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":13350,"status":"not treated","reservation_date":"2024-08-11 08:07:17","uploaded":"2024-11-08 09:09:28","revisionof":"","revisedto":"","release":"Rel-19","crspec":"23.228","crspecversion":"19.0.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1517.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2411897.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2411898","title":"Network Capability Exposure Procedure","source":"[Huawei, HiSilicon, Qualcomm, Samsung,] ZTE","contact":"Hao Dong","contact-id":75723,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add the procedures of IMS data channel capabilies exposure.","secretary_remarks":"Revision of (agreed) S2-2411011 Not Handled","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":13120,"status":"not treated","reservation_date":"2024-08-11 08:07:18","uploaded":"2024-11-08 09:09:28","revisionof":"S2-2411011","revisedto":"","release":"Rel-19","crspec":"23.228","crspecversion":"19.0.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1489.0,"crrevision":5.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2411898.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"Annex XX (new)","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2411899","title":"KI#8: Architecture for avatar communications","source":"[Samsung,] ZTE, [vivo, Huawei, HiSilicon]","contact":"Hao Dong","contact-id":75723,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The description of IMS DC based avatar communication is introduced.","secretary_remarks":"Revision of (agreed) S2-2411010 Not Handled","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":12590,"status":"not treated","reservation_date":"2024-08-11 08:07:18","uploaded":"2024-11-08 09:09:28","revisionof":"S2-2411010","revisedto":"","release":"Rel-19","crspec":"23.228","crspecversion":"19.0.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1480.0,"crrevision":6.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2411899.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":true,"clauses_affected":"AC.X (new)","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2411943","title":"Update on support of DC interworking","source":"vivo","contact":"Zhenhua Xie","contact-id":83004,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add a new description that the new added video media is for sendonly","secretary_remarks":"Revision of (unhandled) S2-2409906 Not Handled","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":13360,"status":"not treated","reservation_date":"2024-08-11 08:31:00","uploaded":"2024-11-08 13:37:06","revisionof":"S2-2409906","revisedto":"","release":"Rel-19","crspec":"23.228","crspecversion":"19.0.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1465.0,"crrevision":1.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2411943.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2411944","title":"KI#3: DC interworking with MTSI UE","source":"[Samsung, Ericsson], vivo","contact":"Zhenhua Xie","contact-id":83004,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Descriptions on different types of DC interworking with MTSI UE are introduced. It includes the transcoding between the data channel media and the MMTeL media, the DCAS triggering the corresponding actions for terminating MTSI UE and the originating MTSI UE. In addition, Add EN to cover the missing enhancements to services to support the feature. Correctly describe the role to be performed by the MF. Complete some of the steps. Clarify that the DC AS uses the non-subscriber specific IMS events to subscribe to be notified about 'ADC requires interworking is established'. Update figure AC.7.9.3-1 to resolve the 'Editor's Note: The Figure needs to be updated to properly depict the subscription by the DC AS.' 5. Clarify that the DCSF determines the IMS DC interworking for the requested ADC is to be performed based on the application id and the remote network or UE#2 does not support IMS DC or is not willing to use IMS DC, but not just based on application ID.","secretary_remarks":"Revision of (agreed) S2-2410973 Not Handled","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":13330,"status":"not treated","reservation_date":"2024-08-11 08:31:06","uploaded":"2024-11-08 13:37:06","revisionof":"S2-2410973","revisedto":"","release":"Rel-19","crspec":"23.228","crspecversion":"19.0.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1479.0,"crrevision":5.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2411944.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"AC.2.2.3, AC.7.9, AC.7.9.0 (new), AC.7.9.1, AC.7.9.2, AC.7.9.3","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2411945","title":"Discussion on way forward for KI#6","source":"vivo","contact":"Zhenhua Xie","contact-id":83004,"tdoctype":"discussion","for":"Discussion","abstract":"Discussion on way forward for KI#6","secretary_remarks":"Not Handled","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":13200,"status":"not treated","reservation_date":"2024-08-11 08:31:07","uploaded":"2024-11-08 13:37:06","revisionof":"","revisedto":"","release":"Rel-19","crspec":"23.228","crspecversion":"","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2411945.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2411946","title":"KI#6: Modification on standalone IMS DC session","source":"vivo, Qualcomm","contact":"Zhenhua Xie","contact-id":83004,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1. Editorially modify the general clause to make it clearer. 2. Correct the high level descrption of the procedure in AC.10.2.1\/2\/3 for clarifying. 3. Modify NOTE 2 to add the example for clarifying the purpose of the procedure in AC.10.2.1. 4. Add early media handling description in general clause and AC.10.2.2\/3. 5. Add a NOTE to describe the alert and modify how UE Alert in general clause to make it more clear. 6. Change the title to reflect the procedure more accuracy. 7. Two alternatives for AC.10.2.2 are provided. 8. Some editorial modification.","secretary_remarks":"Revised in parallel session to S2-2412468.","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":13210,"status":"revised","reservation_date":"2024-08-11 08:31:07","uploaded":"2024-11-08 13:37:06","revisionof":"","revisedto":"S2-2412468","release":"Rel-19","crspec":"23.228","crspecversion":"19.0.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1518.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2411946.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":true,"clauses_affected":"AC.10.1, AC.10.2, AC.10.2.1, AC.10.2.2, AC.10.2.3, AC.10.2.4, AC.10.2.5","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2411947","title":"KI#8: Architecture for avatar communications","source":"[Samsung, ZTE, vivo, Huawei, HiSilicon], vivo","contact":"Zhenhua Xie","contact-id":83004,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The description of IMS DC based avatar communication is introduced.","secretary_remarks":"Revision of (agreed) S2-2411010 Not Handled","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":12600,"status":"not treated","reservation_date":"2024-08-11 08:31:08","uploaded":"2024-11-08 13:37:06","revisionof":"S2-2411010","revisedto":"","release":"Rel-19","crspec":"23.228","crspecversion":"19.0.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1480.0,"crrevision":7.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2411947.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":true,"clauses_affected":"AC.X (new)","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2411948","title":"KI#8: Procedures of avatar communications","source":"vivo","contact":"Zhenhua Xie","contact-id":83004,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add new clause to describe procedures of avatar communication.","secretary_remarks":"Not Handled","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":12620,"status":"not treated","reservation_date":"2024-08-11 08:31:09","uploaded":"2024-11-08 13:37:06","revisionof":"","revisedto":"","release":"Rel-19","crspec":"23.228","crspecversion":"19.0.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1519.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2411948.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":true,"clauses_affected":"AC.X.3 (new), AC.X.3.1 (new), AC.X.3.2 (new)","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2411949","title":"KI#1: IMS Subscribe\/Notify Framework Architecture","source":"[Ericsson, Nokia, T-Mobile USA, NTT DOCOMO, Qualcomm, Samsung], vivo","contact":"Zhenhua Xie","contact-id":83004,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1. A new NEF service, based on SUBSCRIBE\/NOTIFY request, is defined for the IMS events and event categories. Event categories includes a collection of individual events. 2. Subscriber specific events and non-subscriber specific events are supported. 3. A subscriber specific request includes the targeted subscribers. The targeted subscriber(s) can be either one distinct subscriber, or multiple subscribers given as a list. The events in the request are common for all targeted subscribers. This request is sent to the HSS instance(s) serving the given subscribers. 4. HSS supports the handling of subscriber specific requests. To that effect, the subscribe requests that are subscriber specific are sent from the NEF to HSS. HSS handles registered and unregistered UEs and ensures that a subscription is persistent when UE registers, deregisters and re-registers in IMS. Hence, HSS stores the subscription request and sends the subscription request to the IMS AS whenever the IMS AS instance supporting the requested event is assigned to the UE. The information about the subscription events stored in HSS is only relevant and consumed by HSS. NEF and AF use a new service to manage subscription requests (e.g. subscribe\/unsubscribe) via HSS for subscriber specific events. 5. The IMS AS instance assigned to a UE during IMS registration is registered in HSS. Existing SBI Nhss_ImsUECM service used for S-CSCF is enhanced to allow the registration of the IMS AS instance in HSS over N71\/Sh. 6. Subscription requests that are non-subscriber specific are sent directly to all IMS AS instances configured in the PLMN. 7. Notifications related to a subscription is sent directly to the NF (e.g. NEF or AF) that triggered the subscription request Enhance Nhss to support IMS AS registration, deregistration. Support a new service Nhss_ImsEE to enable subscription to subscriber related events. Support a new service Nimsas_ImsEE to enable subscription to subscriber related events, as well as non-subscriber related events. Support a new service Nnef_ImsEE to enable subscription to subscriber related events, as well as non-subscriber related events.","secretary_remarks":"Revision of (revised and agreed) S2-2410971. Merged into S2-2412403","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":12900,"status":"merged","reservation_date":"2024-08-11 08:31:09","uploaded":"2024-11-08 13:37:06","revisionof":"S2-2410971","revisedto":"","release":"Rel-19","crspec":"23.228","crspecversion":"19.0.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1409.0,"crrevision":11.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2411949.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"Annex XX (new), AA.2.1.1, AA.2.1.2.1, AA.2.1.2.2, AA.2.1.X (new), AA.2.4.1AA.2.4.2, AA.2.4.2.2, AA.2.4.2.3 AA.2.X (new), AC.2.2.4, AC.2.2.6","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2412073","title":"Corrections to the IMS standalone sessions","source":"NTT DOCOMO","contact":"Jari Mutikainen","contact-id":38346,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is proposed to remove the current description of AC.10.2.2 'Adding Application DC to Standalone IMS DC Session with Bootstrap DC' and replace it with Originating Standalone Bootstrap DC Setup as described in clause AC.10.2.1, following with the Combined Bootstrap DC and Application DC Setup with the terminating UE as described in clause AC.10.2.3.","secretary_remarks":"Revision of (postponed) S2-2410447 Not Handled","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":13250,"status":"not treated","reservation_date":"2024-08-11 11:43:14","uploaded":"2024-11-08 14:58:05","revisionof":"S2-2410447","revisedto":"","release":"Rel-19","crspec":"23.228","crspecversion":"19.0.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1497.0,"crrevision":1.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2412073.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2412085","title":"Support of third party user identity information in IMS","source":"[Nokia, Ericsson, Qualcomm], Samsung","contact":"Ashok Kumar Nayak","contact-id":90702,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Conclusion principles from TR 23.700-77 are implemented in TS 23.228. Especially a new Annex is introdcued showing the overall architecture and descriping the impacts to functional entities. Rev 5: 1) S-CSCF does the authorization of callingparty to use third party user idenitty infromation 2) AF provisoing of RCD information to NEF reusing Nnef_ParamaterProvision service operation 3) NEF invoke one IMS AS and provision RCD information using Nimsas_ParameterProvision service operation 4) IMS AS use existing service operation provision to HSS","secretary_remarks":"Revision of (agreed) S2-2411009. Revised in parallel session to S2-2412399.","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":12700,"status":"revised","reservation_date":"2024-08-11 12:35:44","uploaded":"2024-11-08 13:20:50","revisionof":"S2-2411009","revisedto":"S2-2412399","release":"Rel-19","crspec":"23.228","crspecversion":"19.0.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1478.0,"crrevision":5.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2412085.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":true,"clauses_affected":"2, 3.1, 3.3, 4.6.3, 4.14, 4.16.3, Annex XX (new)","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2412090","title":"Discussion on solution for authorizing calling party to use third party identities.","source":"Samsung","contact":"Ashok Kumar Nayak","contact-id":90702,"tdoctype":"discussion","for":"Information","abstract":"In the SA WG2#165, S2-2411009 was agreed as part of the KI#4 but there is one Editor's Note which need to be addressed.","secretary_remarks":"Not Handled","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":12690,"status":"not treated","reservation_date":"2024-08-11 12:41:12","uploaded":"2024-11-08 13:21:15","revisionof":"","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2412090.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2412091","title":"KI#1: Enhancements to NEF Services","source":"[Ericsson], Samsung","contact":"Ashok Kumar Nayak","contact-id":90702,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: List the Nnef_ImsEE services and makes reference to 23.228 for its description. The list of supported IMS events is included in the NF profile of IMS AS. IMS AS is added as consumer of NRF services. This was missing in the baseline. NF (i.e. IMS AS) discovery clause is added","secretary_remarks":"Revision of (agreed) S2-2411188. Merged into S2-2412404","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":12970,"status":"merged","reservation_date":"2024-08-11 12:44:39","uploaded":"2024-11-08 13:21:29","revisionof":"S2-2411188","revisedto":"","release":"Rel-19","crspec":"23.502","crspecversion":"19.1.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":4872.0,"crrevision":9.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2412091.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.2.6.1, 5.2.6.X (NEW), 5.2.7.1, 5.2.7.2.2., 5.2.7.3","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2412092","title":"KI#4: Enhancements to NEF Services for provisioning of RCD information","source":"Samsung","contact":"Ashok Kumar Nayak","contact-id":90702,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: List the Nnef_ImsPP services and makes reference to 23.228 for its description.","secretary_remarks":"Revised in parallel session to S2-2412402.","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":12810,"status":"revised","reservation_date":"2024-08-11 12:48:20","uploaded":"2024-11-08 13:21:46","revisionof":"","revisedto":"S2-2412402","release":"Rel-19","crspec":"23.502","crspecversion":"19.1.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":5177.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2412092.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.2.6.1, 5.2.6.X (NEW), 5.2.7.1, 5.2.7.2.2.","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2412096","title":"Procedure for supporting of third party user identity information in IMS","source":"Samsung","contact":"Ashok Kumar Nayak","contact-id":90702,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Feature procedural details along in the lines of KI#4 conclusions specified in TR 23.700-77","secretary_remarks":"Revised in parallel session to S2-2412401.","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":12770,"status":"revised","reservation_date":"2024-08-11 12:57:19","uploaded":"2024-11-08 13:22:09","revisionof":"","revisedto":"S2-2412401","release":"Rel-19","crspec":"23.228","crspecversion":"19.0.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1524.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2412096.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":true,"clauses_affected":"Annex AX (New)","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2412111","title":"Network Capability Exposure Procedure","source":"Nokia [, Huawei, HiSilicon, Qualcomm, Samsung, ZTE]","contact":"Rainer Liebhart","contact-id":68375,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add the procedures of IMS data channel capabilies exposure. Rev4: Adding clarifications in existing call flows and adding a new call flow for termintaing a standalone IMS data channel session.","secretary_remarks":"Revision of (agreed) S2-2411011. Merged into S2-2412466","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":13130,"status":"merged","reservation_date":"2024-08-11 13:21:51","uploaded":"2024-11-08 16:37:29","revisionof":"S2-2411011","revisedto":"","release":"Rel-19","crspec":"23.228","crspecversion":"19.0.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1489.0,"crrevision":6.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2412111.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2412132","title":"Support of third party user identity information in IMS","source":"Nokia[, Ericsson, Qualcomm]","contact":"Rainer Liebhart","contact-id":68375,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Conclusion principles from TR 23.700-77 are implemented in TS 23.228. Especially a new Annex is introdcued showing the overall architecture and descriping the impacts to functional entities. Rev5: Two editor's notes are resolved and a figure is added to illustrate the procedure about authorization, signing, and verification of third party user identity information in IMS. EN on NEF provisioning: Although this was concluded at the end of the study phase no solution in TR 23.700-77 has described how it works. Thus, this should be part of a later release. EN on S-CSCF authorization: authorizing use of RCD information should be left to IMS AS as it is part of service authorization. Also, different options in the standard should be avoided.","secretary_remarks":"Revision of (agreed) S2-2411009. Revised in parallel session to S2-2412400.","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":12730,"status":"revised","reservation_date":"2024-08-11 13:41:20","uploaded":"2024-11-08 16:37:29","revisionof":"S2-2411009","revisedto":"S2-2412400","release":"Rel-19","crspec":"23.228","crspecversion":"19.0.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1478.0,"crrevision":6.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2412132.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":true,"clauses_affected":"2, 3.1, 3.3, 4.6.3, 4.14, 4.16.3, Annex XX (new)","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2412163","title":"[DRAFT] LS on IMS DC multiplexing","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"[DRAFT] LS on IMS DC multiplexing","secretary_remarks":"Not Handled","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":12520,"status":"not treated","reservation_date":"2024-08-11 14:39:05","uploaded":"2024-11-08 17:02:13","revisionof":"","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG4","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2412163.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2412164","title":"Address ENs in IMS AS Session Management Service","source":"Huawei, HiSillicon, ZTE?, Qualcomm?","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Address the ENs for Nimsas_ImsSessionManagement Service in clause AA.2.4.4 of TS 23.228.","secretary_remarks":"Revision of (agreed) S2-2410967. Confirm Sources! Not Handled","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":13070,"status":"not treated","reservation_date":"2024-08-11 14:39:05","uploaded":"2024-11-08 17:02:13","revisionof":"S2-2410967","revisedto":"","release":"Rel-19","crspec":"23.228","crspecversion":"19.0.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1483.0,"crrevision":5.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2412164.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"AA.2.4.4.1, AA.2.4.4.2, AA.2.4.4.3, AA.2.4.4.4","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2412165","title":"Update NEF services to support the conclusion of KI#1 and KI#2","source":"Huawei, HiSilicon, Qualcomm?, ZTE?, Samsung?","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Enhance the NEF service to support IMS event subscriptoin\/notification and data channel establishment, update and termination.","secretary_remarks":"Revision of (agreed) S2-2411012. Confirm Sources! Not Handled","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":13190,"status":"not treated","reservation_date":"2024-08-11 14:39:05","uploaded":"2024-11-08 17:02:13","revisionof":"S2-2411012","revisedto":"","release":"Rel-19","crspec":"23.502","crspecversion":"19.1.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":5087.0,"crrevision":4.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2412165.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.2.6.1, 5.2.6.Y (new)","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2412166","title":"Network Capability Exposure Procedure","source":"Huawei, HiSilicon, Qualcomm?, Samsung?, ZTE?","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add the procedures of IMS data channel capabilies exposure.","secretary_remarks":"Revision of (agreed) S2-2411011. Confirm Sources! Not Handled","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":13140,"status":"not treated","reservation_date":"2024-08-11 14:39:06","uploaded":"2024-11-08 17:02:13","revisionof":"S2-2411011","revisedto":"","release":"Rel-19","crspec":"23.228","crspecversion":"19.0.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1489.0,"crrevision":7.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2412166.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2412167","title":"KI#1: IMS Subscribe\/Notify Framework Architecture","source":"Huawei, HiSilicon, Ericsson?, Nokia?, T-Mobile USA?, NTT DOCOMO?, Qualcomm?, Samsung?","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1. A new NEF service, based on SUBSCRIBE\/NOTIFY request, is defined for the IMS events and event categories. Event categories includes a collection of individual events. 2. Subscriber specific events and non-subscriber specific events are supported. 3. A subscriber specific request includes the targeted subscribers. The targeted subscriber(s) can be either one distinct subscriber, or multiple subscribers given as a list. The events in the request are common for all targeted subscribers. This request is sent to the HSS instance(s) serving the given subscribers. 4. HSS supports the handling of subscriber specific requests. To that effect, the subscribe requests that are subscriber specific are sent from the NEF to HSS. HSS handles registered and unregistered UEs and ensures that a subscription is persistent when UE registers, deregisters and re-registers in IMS. Hence, HSS stores the subscription request and sends the subscription request to the IMS AS whenever the IMS AS instance supporting the requested event is assigned to the UE. The information about the subscription events stored in HSS is only relevant and consumed by HSS. NEF and AF use a new service to manage subscription requests (e.g. subscribe\/unsubscribe) via HSS for subscriber specific events. 5. The IMS AS instance assigned to a UE during IMS registration is registered in HSS. Existing SBI Nhss_ImsUECM service used for S-CSCF is enhanced to allow the registration of the IMS AS instance in HSS over N71\/Sh. 6. Subscription requests that are non-subscriber specific are sent directly to all IMS AS instances configured in the PLMN. 7. Notifications related to a subscription is sent directly to the NF (e.g. NEF or AF) that triggered the subscription request Enhance Nhss to support IMS AS registration, deregistration. Support a new service Nhss_ImsEE to enable subscription to subscriber related events. Support a new service Nimsas_ImsEE to enable subscription to subscriber related events, as well as non-subscriber related events. Support a new service Nnef_ImsEE to enable subscription to subscriber related events, as well as non-subscriber related events.","secretary_remarks":"Revision of (agreed) S2-2410974. Confirm Sources! Merged into S2-2412403","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":12910,"status":"merged","reservation_date":"2024-08-11 14:39:07","uploaded":"2024-11-08 17:02:13","revisionof":"S2-2410974","revisedto":"","release":"Rel-19","crspec":"23.228","crspecversion":"19.0.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1409.0,"crrevision":12.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2412167.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"Annex XX (new), AA.2.1.1, AA.2.1.2.1, AA.2.1.2.2, AA.2.1.2.X(new), AA.2.1.X (new), AA.2.4.1AA.2.4.2, AA.2.4.2.2, AA.2.4.2.3 AA.2.X (new), AC.2.2.4, AC.2.2.6","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2412168","title":"KI#1: Enhancements to NEF Services","source":"Huawei, HiSilicon, Ericsson?","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: List the Nnef_ImsEE services and makes reference to 23.228 for its description. The list of supported IMS events is included in the NF profile of IMS AS. IMS AS is added as consumer of NRF services. This was missing in the baseline.","secretary_remarks":"Revision of (agreed) S2-2411188. Confirm Sources! Merged into S2-2412404","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":12980,"status":"merged","reservation_date":"2024-08-11 14:39:08","uploaded":"2024-11-08 17:02:13","revisionof":"S2-2411188","revisedto":"","release":"Rel-19","crspec":"23.502","crspecversion":"19.1.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":4872.0,"crrevision":10.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2412168.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.2.6.1, 5.2.6.X (NEW), 5.2.7.1, 5.2.7.2.2.","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2412169","title":"KI#5: Support of Data off feature for data channel","source":"vivo?, Huawei, HiSilicon, Deutsche Telekom?, ZTE?, Qualcomm Inc.?, Samsung?","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: This contribution: Add 'Data Channel Serivces in IMS' in annex X Add a new optional parameter of PS Data Off Status in Nimsas_SessionEventControl.","secretary_remarks":"Revision of (agreed) S2-2410914. Confirm Sources! Not Handled","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":13390,"status":"not treated","reservation_date":"2024-08-11 14:39:10","uploaded":"2024-11-08 17:02:13","revisionof":"S2-2410914","revisedto":"","release":"Rel-19","crspec":"23.228","crspecversion":"19.0.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1421.0,"crrevision":6.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2412169.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":true,"clauses_affected":"X.1, X.2.3, X.3.2, AA.2.4.2.1, AA.2.4.2.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2412170","title":"Supporting Avatar Communication","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Define the avatar communication call flows","secretary_remarks":"Revised in parallel session to S2-2412397.","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":12630,"status":"revised","reservation_date":"2024-08-11 14:39:10","uploaded":"2024-11-08 17:02:13","revisionof":"","revisedto":"S2-2412397","release":"Rel-19","crspec":"23.228","crspecversion":"19.0.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1525.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2412170.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"AC.X.3 (new), AA.2.X (new), AA.2.5.1, AA.2.5.X (new)","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2412394","title":"Support of multiplexing multiple DC applications over single SCTP connection","source":"China Mobile","contact":"Yi Jiang","contact-id":40863,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add functionality requirements and procedure to support multiplexing multiple DC applications over single SCTP connection.","secretary_remarks":"Revision of S2-2411608. Revised in parallel session to S2-2412681.","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":12480,"status":"revised","reservation_date":"2024-11-20 20:06:35","uploaded":"2024-11-25 06:41:10","revisionof":"S2-2411608","revisedto":"S2-2412681","release":"Rel-19","crspec":"23.228","crspecversion":"19.0.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1511.0,"crrevision":1.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2412394.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":true,"clauses_affected":"AC.7.X (new)","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2412395","title":"Service updates to support multiplexing multiple DC applications over single SCTP connection","source":"China Mobile","contact":"Yi Jiang","contact-id":40863,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The services of IMS AS and MF are updated to support data channel multiplexing over single SCTP connection.","secretary_remarks":"Revision of S2-2411609. Withdrawn","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":12510,"status":"withdrawn","reservation_date":"2024-11-20 20:06:36","uploaded":null,"revisionof":"S2-2411609","revisedto":"","release":"Rel-19","crspec":"23.228","crspecversion":"19.0.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1512.0,"crrevision":1.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2412396","title":"KI#8: Architecture for avatar communications","source":"Samsung, [ZTE, vivo, Huawei, HiSilicon]","contact":"DongYeon Kim","contact-id":87763,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The description of IMS DC based avatar communication is introduced. [R04: SA WG2#166] Editor's Notes in clause AC.X.1 General is cleared. Note regarding DC AS URL is clarified. Function description of IMS AS is added in clause AC.X.2. Reference points are added in clause AC.X.2. Procedures are newly added as clause AC.X.3. Service operation parameter is added in clause AA.2.4.2.2.","secretary_remarks":"Revision of S2-2411332. Revised in parallel session to S2-2412682.","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":12540,"status":"revised","reservation_date":"2024-11-20 20:06:37","uploaded":"2024-11-25 06:41:10","revisionof":"S2-2411332","revisedto":"S2-2412682","release":"Rel-19","crspec":"23.228","crspecversion":"19.0.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1480.0,"crrevision":8.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2412396.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2412397","title":"Supporting Avatar Communication","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Define the avatar communication call flows","secretary_remarks":"Revision of S2-2412170. Revised in parallel session to S2-2412683, merging S2-2412398","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":12640,"status":"revised","reservation_date":"2024-11-20 20:06:38","uploaded":"2024-11-25 06:41:10","revisionof":"S2-2412170","revisedto":"S2-2412683","release":"Rel-19","crspec":"23.228","crspecversion":"19.0.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1525.0,"crrevision":1.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2412397.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2412398","title":"Transition Between IMS Avatar and Audio\/video Communication","source":"ZTE, Samsung","contact":"Hao Dong","contact-id":75723,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add procedure for transition between IMS Avatar and audio\/video communication.","secretary_remarks":"Revision of S2-2411896. Merged into S2-2412683","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":12680,"status":"merged","reservation_date":"2024-11-20 20:06:38","uploaded":"2024-11-25 06:41:10","revisionof":"S2-2411896","revisedto":"","release":"Rel-19","crspec":"23.228","crspecversion":"19.0.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1516.0,"crrevision":1.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2412398.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":true,"clauses_affected":"AC.X.y(new)","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2412399","title":"Support of third party user identity information in IMS","source":"[Nokia, Ericsson, Qualcomm], Samsung","contact":"Ashok Kumar Nayak","contact-id":90702,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Conclusion principles from TR 23.700-77 are implemented in TS 23.228. Especially a new Annex is introdcued showing the overall architecture and descriping the impacts to functional entities. Rev 5: 1) S-CSCF does the authorization of callingparty to use third party user idenitty infromation 2) AF provisoing of RCD information to NEF reusing Nnef_ParamaterProvision service operation 3) NEF invoke one IMS AS and provision RCD information using Nimsas_ParameterProvision service operation 4) IMS AS use existing service operation provision to HSS","secretary_remarks":"Revision of S2-2412085. Revised in parallel session to S2-2412637.","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":12710,"status":"revised","reservation_date":"2024-11-20 20:06:39","uploaded":"2024-11-25 06:41:10","revisionof":"S2-2412085","revisedto":"S2-2412637","release":"Rel-19","crspec":"23.228","crspecversion":"19.0.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1478.0,"crrevision":7.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2412399.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2412400","title":"Support of third party user identity information in IMS","source":"Nokia","contact":"Rainer Liebhart","contact-id":68375,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Conclusion principles from TR 23.700-77 are implemented in TS 23.228. Especially a new Annex is introdcued showing the overall architecture and descriping the impacts to functional entities. Rev5: Two editor's notes are resolved and a figure is added to illustrate the procedure about authorization, signing, and verification of third party user identity information in IMS. EN on NEF provisioning: Although this was concluded at the end of the study phase no solution in TR 23.700-77 has described how it works. Thus, this should be part of a later release. EN on S-CSCF authorization: authorizing use of RCD information should be left to IMS AS as it is part of service authorization. Also, different options in the standard should be avoided.","secretary_remarks":"Revision of S2-2412132. Revised in parallel session to S2-2412685, merging S2-2412637","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":12740,"status":"revised","reservation_date":"2024-11-20 20:06:40","uploaded":"2024-11-25 06:41:10","revisionof":"S2-2412132","revisedto":"S2-2412685","release":"Rel-19","crspec":"23.228","crspecversion":"19.0.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1478.0,"crrevision":8.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2412400.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2412401","title":"Procedure for supporting of third party user identity information in IMS","source":"Samsung","contact":"Ashok Kumar Nayak","contact-id":90702,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Feature procedural details along in the lines of KI#4 conclusions specified in TR 23.700-77","secretary_remarks":"Revision of S2-2412096. Revised in parallel session to S2-2412686.","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":12780,"status":"revised","reservation_date":"2024-11-20 20:06:41","uploaded":"2024-11-25 06:41:10","revisionof":"S2-2412096","revisedto":"S2-2412686","release":"Rel-19","crspec":"23.228","crspecversion":"19.0.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1524.0,"crrevision":1.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2412401.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2412402","title":"KI#4: Enhancements to NEF Services for provisioning of RCD information","source":"Samsung","contact":"Ashok Kumar Nayak","contact-id":90702,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: List the Nnef_ImsPP services and makes reference to 23.228 for its description.","secretary_remarks":"Revision of S2-2412092. Revised in parallel session to S2-2412638.","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":12820,"status":"revised","reservation_date":"2024-11-20 20:06:41","uploaded":"2024-11-25 06:41:10","revisionof":"S2-2412092","revisedto":"S2-2412638","release":"Rel-19","crspec":"23.502","crspecversion":"19.1.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":5177.0,"crrevision":1.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2412402.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2412403","title":"KI#1: IMS Subscribe\/Notify Framework Architecture","source":"Ericsson, [Nokia, T-Mobile USA, NTT DOCOMO, Qualcomm, Samsung]","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1. A new NEF service, based on SUBSCRIBE\/NOTIFY request, is defined for the IMS events and event categories. Event categories includes a collection of individual events. 2. Subscriber specific events and non-subscriber specific events are supported. 3. A subscriber specific request includes the targeted subscribers. The targeted subscriber(s) can be either one distinct subscriber, or multiple subscribers given as a list. The events in the request are common for all targeted subscribers. This request is sent to the HSS instance(s) serving the given subscribers. 4. HSS supports the handling of subscriber specific requests. To that effect, the subscribe requests that are subscriber specific are sent from the NEF to HSS. HSS handles registered and unregistered UEs and ensures that a subscription is persistent when UE registers, deregisters and re-registers in IMS. Hence, HSS stores the subscription request and sends the subscription request to the IMS AS whenever the IMS AS instance supporting the requested event is assigned to the UE. The information about the subscription events stored in HSS is only relevant and consumed by HSS. NEF and AF use a new service to manage subscription requests (e.g. subscribe\/unsubscribe) via HSS for subscriber specific events. 5. The IMS AS instance assigned to a UE during IMS registration is registered in HSS. Existing SBI Nhss_ImsUECM service used for S-CSCF is enhanced to allow the registration of the IMS AS instance in HSS over N71\/Sh. 6. Subscription requests that are non-subscriber specific are sent directly to all IMS AS instances configured in the PLMN. 7. Notifications related to a subscription is sent directly to the NF (e.g. NEF or AF) that triggered the subscription request Enhance Nhss to support IMS AS registration, deregistration. Support a new service Nhss_ImsEE to enable subscription to subscriber related events. Support a new service Nimsas_ImsEE to enable subscription to subscriber related events, as well as non-subscriber related events. Support a new service Nnef_ImsEE to enable subscription to subscriber related events, as well as non-subscriber related events. Update to the CR. Two editor notes are addressed: Handling of subscription to a number of events in a single subscription. Completing the definition of event filters for IMS DC events supported in this release. A new Editor note is also included: The mapping of Sh messages to HSS or IMS AS SBI services is FFS. NOTE: Change on change will be removed when a clean revision is produced.","secretary_remarks":"Revision of S2-2411471, merging S2-2412167, S2-2411949 and S2-2411603. Revised in parallel session to S2-2412688.","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":12860,"status":"revised","reservation_date":"2024-11-20 20:06:42","uploaded":"2024-11-25 06:41:10","revisionof":"S2-2411471","revisedto":"S2-2412688","release":"Rel-19","crspec":"23.228","crspecversion":"19.0.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1409.0,"crrevision":13.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2412403.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2412404","title":"KI#1: Enhancements to NEF Services","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: List the Nnef_ImsEE services and makes reference to 23.228 for its description. The list of supported IMS events is included in the NF profile of IMS AS. IMS AS is added as consumer of NRF services. This was missing in the baseline. Update to the CR to remove the editors note on parameter design and complete the service description. NOTE: Change on change will be removed when a clean revision is produced.","secretary_remarks":"Revision of S2-2411472, merging S2-2412168 and S2-2412091. Revised in parallel session to S2-2412689.","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":12930,"status":"revised","reservation_date":"2024-11-20 20:06:43","uploaded":"2024-11-25 06:41:10","revisionof":"S2-2411472","revisedto":"S2-2412689","release":"Rel-19","crspec":"23.502","crspecversion":"19.1.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":4872.0,"crrevision":11.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2412404.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2412405","title":"Alignment of DC exposure and standalone DC with IMS DC architecture","source":"China Mobile","contact":"Yi Jiang","contact-id":40863,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Remove the limit to allow standalone DC establishment; Add the reference to Annex for IMS DC event exposure and IMS DC capability exposure. Add new clause of NEF.","secretary_remarks":"Revision of S2-2411606. Revised in parallel session to S2-2412690.","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":13000,"status":"revised","reservation_date":"2024-11-20 20:06:44","uploaded":"2024-11-25 06:41:10","revisionof":"S2-2411606","revisedto":"S2-2412690","release":"Rel-19","crspec":"23.228","crspecversion":"19.0.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1509.0,"crrevision":1.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2412405.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"AC.1, AC.2.1, AC.2.2.4, AC.2.2.6, AC.2.2.Y(new)","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2412465","title":"Address ENs in IMS AS Session Management Service","source":"[ZTE, Qualcomm, Huawei], NTT DOCOMO","contact":"Jari Mutikainen","contact-id":38346,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Address the ENs for Nimsas_ImsSessionManagement Service in clause AA.2.4.4 of TS 23.228. Rev-3: Add Nimsas_ImsSessionManagement_Notify service operation. Correct the conditions to include MDC2 media endpoint address into Media information set.","secretary_remarks":"Revision of S2-2411469, merging S2-2411605. Revised in parallel session to S2-2412692.","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":13030,"status":"revised","reservation_date":"2024-11-20 20:07:47","uploaded":"2024-11-25 06:41:11","revisionof":"S2-2411469","revisedto":"S2-2412692","release":"Rel-19","crspec":"23.228","crspecversion":"19.0.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1483.0,"crrevision":6.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2412465.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2412466","title":"Network Capability Exposure Procedure","source":"[Huawei, HiSilicon, Qualcomm, Samsung, ZTE], NTT DOCOMO","contact":"Jari Mutikainen","contact-id":38346,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add the procedures of IMS data channel capabilies exposure. Rev-4: 1. Resolving the EN: 'Whether and how to have intermediate call notification during the procedure is FFS'. In the current procedure, the DC AS needs to wait until both UEs have accepted or rejected the session (or session modification) until it receives the response to the request (HTTP 2xx). It is proposed to add a subscribe\/notify operations under the Nimsas_IMSSessionManagement service, so that the response indicating whether the request is accepted or rejected can be provided immediately, and the actual IMS session progress with the UEs is reported via notify service operation. In this way, the NEF uses the callback URI to find the IMS AS, and discovery from HSS is not needed, and the EN 'the service for step 2 is FFS' on how to discover the IMS AS can be removed. 2. The current procedure refers to OMA API that can be used to notify the non-DC related IMS session events to the DC AS. The OMA API needs to provide a callback URI that the DC AS can use to target the update-request to the same IMS AS that send the notification (and who is anchoring the IMS session). It should be noted that OMA API cannot be used to notify for DC-related events; the item 1 in this CR is used for DC-related events. 3. Resolving the EN 'The need for a new event in step 4 is FFS': it is proposed to re-use the existing Nimsas_SessionEventControl_Notify service operation. The notify request must be enhanced to include the Media information set that the IMS AS has received in Nimsas_ImsSessionManagement_Create or _Update request from the NEF, and new Event IDs: '3rd party session update' and '3rd party session creation'. The media information set indicates to the DCSF the DC type (P2A, P2A2P, P2P, or BDC) and e.g. the MDC2 media end point address if a new DC is added with the DC AS. 4. It is proposed to merge the procedures for adding of data channels and removing of a data channels. 5. Editorial changes.","secretary_remarks":"Revision of S2-2411589, merging S2-2412111. Revised in parallel session to S2-2412691.","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":13090,"status":"revised","reservation_date":"2024-11-20 20:07:47","uploaded":"2024-11-25 06:41:11","revisionof":"S2-2411589","revisedto":"S2-2412691","release":"Rel-19","crspec":"23.228","crspecversion":"19.0.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1489.0,"crrevision":8.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2412466.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2412467","title":"Update NEF services to support the conclusion of KI#1 and KI#2","source":"[Huawei, HiSilicon, Qualcomm, ZTE, Samsung], NTT DOCOMO","contact":"Jari Mutikainen","contact-id":38346,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Enhance the NEF service to support IMS event subscription\/notification and data channel establishment, update and termination. Rev-3: Add Nnef_ImsSessionManagement_Notify service operation","secretary_remarks":"Revision of S2-2411562. Revised in parallel session to S2-2412693.","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":13160,"status":"revised","reservation_date":"2024-11-20 20:08:04","uploaded":"2024-11-25 06:41:11","revisionof":"S2-2411562","revisedto":"S2-2412693","release":"Rel-19","crspec":"23.502","crspecversion":"19.1.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":5087.0,"crrevision":5.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2412467.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2412468","title":"KI#6: Modification on standalone IMS DC session","source":"Vivo, Qualcomm, CMCC","contact":"Zhenhua Xie","contact-id":83004,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1. Editorially modify the general clause to make it clearer. 2. Correct the high level descrption of the procedure in AC.10.2.1\/2\/3 for clarifying. 3. Modify NOTE 2 to add the example for clarifying the purpose of the procedure in AC.10.2.1. 4. Add early media handling description in general clause and AC.10.2.2\/3. 5. Add a NOTE to describe the alert and modify how UE Alert in general clause to make it more clear. 6. Change the title to reflect the procedure more accuracy. 7. Two alternatives for AC.10.2.2 are provided. 8. Some editorial modification.","secretary_remarks":"Revision of S2-2411946. Revised in parallel session to S2-2412695.","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":13220,"status":"revised","reservation_date":"2024-11-20 20:08:04","uploaded":"2024-11-25 06:41:11","revisionof":"S2-2411946","revisedto":"S2-2412695","release":"Rel-19","crspec":"23.228","crspecversion":"19.0.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1518.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2412468.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2412469","title":"[DRAFT] LS on clarification on reply SDP for standalone DC","source":"vivo","contact":"Zhenhua Xie","contact-id":83004,"tdoctype":"LS out","for":"Approval","abstract":"-","secretary_remarks":"Created in parallel session. Revised in parallel session to S2-2412694.","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":13260,"status":"revised","reservation_date":"2024-11-20 20:08:05","uploaded":"2024-11-25 06:41:11","revisionof":"","revisedto":"S2-2412694","release":"Rel-19","crspec":"","crspecversion":"","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"-","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2412469.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2412636","title":"KI#3: DC interworking with MTSI UE","source":"Samsung, [Ericsson]","contact":"DongYeon Kim","contact-id":87763,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Descriptions on different types of DC interworking with MTSI UE are introduced. It includes the transcoding between the data channel media and the MMTeL media, the DCAS triggering the corresponding actions for terminating MTSI UE and the originating MTSI UE. In addition, Add EN to cover the missing enhancements to services to support the feature. Correctly describe the role to be performed by the MF. Complete some of the steps. Added in rev 4 (SA WG2#166): Editorial fix in AC.7.9.0 General Editorial fix in AC.7.9.1 Editorial fix in AC.7.9.2 The ENs in AC.7.9.3 are resolved by the updated Figure AC.7.9.3-1, steps 1a-1e, and steps 6a-6e. The EN in AC.7.9.0 is resolved by AC.7.9.4.","secretary_remarks":"Revision of S2-2411333. Revised in parallel session to S2-2412696.","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":13300,"status":"revised","reservation_date":"2024-11-20 20:10:07","uploaded":"2024-11-25 06:41:12","revisionof":"S2-2411333","revisedto":"S2-2412696","release":"Rel-19","crspec":"23.228","crspecversion":"19.0.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1479.0,"crrevision":6.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2412636.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2412637","title":"Support of third party user identity information in IMS","source":"[Nokia, Ericsson, Qualcomm], Samsung","contact":"Ashok Kumar Nayak","contact-id":90702,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Conclusion principles from TR 23.700-77 are implemented in TS 23.228. Especially a new Annex is introdcued showing the overall architecture and descriping the impacts to functional entities. Rev 5: 1) S-CSCF does the authorization of callingparty to use third party user idenitty infromation 2) AF provisoing of RCD information to NEF reusing Nnef_ParamaterProvision service operation 3) NEF invoke one IMS AS and provision RCD information using Nimsas_ParameterProvision service operation 4) IMS AS use existing service operation provision to HSS","secretary_remarks":"Revision of S2-2412399. Merged into S2-2412685","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":12720,"status":"merged","reservation_date":"2024-11-20 20:10:08","uploaded":"2024-11-25 06:41:12","revisionof":"S2-2412399","revisedto":"","release":"Rel-19","crspec":"23.228","crspecversion":"19.0.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1478.0,"crrevision":9.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2412637.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2412638","title":"KI#4: Enhancements to NEF Services for provisioning of RCD information","source":"Samsung","contact":"Ashok Kumar Nayak","contact-id":90702,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: List the Nnef_ImsPP services and makes reference to 23.228 for its description.","secretary_remarks":"Revision of S2-2412402. Revised in parallel session to S2-2412687.","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":12830,"status":"revised","reservation_date":"2024-11-20 20:10:08","uploaded":"2024-11-25 06:41:12","revisionof":"S2-2412402","revisedto":"S2-2412687","release":"Rel-19","crspec":"23.502","crspecversion":"19.1.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":5177.0,"crrevision":2.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2412638.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2412681","title":"Support of multiplexing multiple DC applications over single SCTP connection","source":"China Mobile, Samsung, ZTE","contact":"Yi Jiang","contact-id":40863,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add functionality requirements and procedure to support multiplexing multiple DC applications over single SCTP connection.","secretary_remarks":"Revision of S2-2412394. Agreed in parallel session. Block approved","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":12490,"status":"agreed","reservation_date":"2024-11-20 20:10:11","uploaded":"2024-11-25 06:51:07","revisionof":"S2-2412394","revisedto":"","release":"Rel-19","crspec":"23.228","crspecversion":"19.0.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1511.0,"crrevision":2.0,"crcategory":"B","tsg_crp":"SP-241491","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2412681.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2412682","title":"KI#8: Architecture for avatar communications","source":"Samsung, ZTE, vivo, [Huawei, HiSilicon]","contact":"DongYeon Kim","contact-id":87763,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The description of IMS DC based avatar communication is introduced. [R04: SA WG2#166] Editor's Notes in clause AC.X.1 General is cleared. Note regarding DC AS URL is clarified. Function description of IMS AS is added in clause AC.X.2. Reference points are added in clause AC.X.2. Procedures are newly added as clause AC.X.3. Service operation parameter is added in clause AA.2.4.2.2.","secretary_remarks":"Revision of S2-2412396. Revised in parallel session to S2-2412911.","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":12550,"status":"revised","reservation_date":"2024-11-20 20:10:11","uploaded":"2024-11-25 06:51:07","revisionof":"S2-2412396","revisedto":"S2-2412911","release":"Rel-19","crspec":"23.228","crspecversion":"19.0.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1480.0,"crrevision":9.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2412682.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2412683","title":"Supporting Avatar Communication","source":"Huawei, HiSilicon, ZTE, Samsung","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Define the avatar communication call flows","secretary_remarks":"Revision of S2-2412397, merging S2-2412398. Revised in parallel session to S2-2412912.","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":12650,"status":"revised","reservation_date":"2024-11-20 20:10:11","uploaded":"2024-11-25 06:51:07","revisionof":"S2-2412397","revisedto":"S2-2412912","release":"Rel-19","crspec":"23.228","crspecversion":"19.0.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1525.0,"crrevision":2.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2412683.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2412685","title":"Support of third party user identity information in IMS","source":"Nokia, Samsung, Ericsson, Qualcomm","contact":"Rainer Liebhart","contact-id":68375,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Conclusion principles from TR 23.700-77 are implemented in TS 23.228. Especially a new Annex is introdcued showing the overall architecture and descriping the impacts to functional entities. Rev5: Two editor's notes are resolved and a figure is added to illustrate the procedure about authorization, signing, and verification of third party user identity information in IMS. EN on NEF provisioning: Although this was concluded at the end of the study phase no solution in TR 23.700-77 has described how it works. Thus, this should be part of a later release. EN on S-CSCF authorization: authorizing use of RCD information should be left to IMS AS as it is part of service authorization. Also, different options in the standard should be avoided.","secretary_remarks":"Revision of S2-2412400, merging S2-2412637. Revised in parallel session to S2-2412909.","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":12750,"status":"revised","reservation_date":"2024-11-20 20:10:11","uploaded":"2024-11-25 06:51:07","revisionof":"S2-2412400","revisedto":"S2-2412909","release":"Rel-19","crspec":"23.228","crspecversion":"19.0.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1478.0,"crrevision":10.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2412685.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2412686","title":"Procedure for supporting of third party user identity information in IMS","source":"Samsung","contact":"Ashok Kumar Nayak","contact-id":90702,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Feature procedural details along in the lines of KI#4 conclusions specified in TR 23.700-77","secretary_remarks":"Revision of S2-2412401. Revised in parallel session to S2-2412910.","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":12790,"status":"revised","reservation_date":"2024-11-20 20:10:11","uploaded":"2024-11-25 06:51:07","revisionof":"S2-2412401","revisedto":"S2-2412910","release":"Rel-19","crspec":"23.228","crspecversion":"19.0.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1524.0,"crrevision":2.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2412686.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2412687","title":"KI#4: Enhancements to NEF Services for provisioning of RCD information","source":"Samsung","contact":"Ashok Kumar Nayak","contact-id":90702,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: List the Nnef_ImsPP services and makes reference to 23.228 for its description.","secretary_remarks":"Revision of S2-2412638. Agreed in parallel session. Block approved","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":12840,"status":"agreed","reservation_date":"2024-11-20 20:10:11","uploaded":"2024-11-25 06:51:07","revisionof":"S2-2412638","revisedto":"","release":"Rel-19","crspec":"23.502","crspecversion":"19.1.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":5177.0,"crrevision":3.0,"crcategory":"B","tsg_crp":"SP-241491","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2412687.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2412688","title":"KI#1: IMS Subscribe\/Notify Framework Architecture","source":"Ericsson, Samsung, [Nokia, T-Mobile USA, NTT DOCOMO, Qualcomm]","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1. A new NEF service, based on SUBSCRIBE\/NOTIFY request, is defined for the IMS events and event categories. Event categories includes a collection of individual events. 2. Subscriber specific events and non-subscriber specific events are supported. 3. A subscriber specific request includes the targeted subscribers. The targeted subscriber(s) can be either one distinct subscriber, or multiple subscribers given as a list. The events in the request are common for all targeted subscribers. This request is sent to the HSS instance(s) serving the given subscribers. 4. HSS supports the handling of subscriber specific requests. To that effect, the subscribe requests that are subscriber specific are sent from the NEF to HSS. HSS handles registered and unregistered UEs and ensures that a subscription is persistent when UE registers, deregisters and re-registers in IMS. Hence, HSS stores the subscription request and sends the subscription request to the IMS AS whenever the IMS AS instance supporting the requested event is assigned to the UE. The information about the subscription events stored in HSS is only relevant and consumed by HSS. NEF and AF use a new service to manage subscription requests (e.g. subscribe\/unsubscribe) via HSS for subscriber specific events. 5. The IMS AS instance assigned to a UE during IMS registration is registered in HSS. Existing SBI Nhss_ImsUECM service used for S-CSCF is enhanced to allow the registration of the IMS AS instance in HSS over N71\/Sh. 6. Subscription requests that are non-subscriber specific are sent directly to all IMS AS instances configured in the PLMN. 7. Notifications related to a subscription is sent directly to the NF (e.g. NEF or AF) that triggered the subscription request Enhance Nhss to support IMS AS registration, deregistration. Support a new service Nhss_ImsEE to enable subscription to subscriber related events. Support a new service Nimsas_ImsEE to enable subscription to subscriber related events, as well as non-subscriber related events. Support a new service Nnef_ImsEE to enable subscription to subscriber related events, as well as non-subscriber related events. Update to the CR. Two editor notes are addressed: Handling of subscription to a number of events in a single subscription. Completing the definition of event filters for IMS DC events supported in this release. A new Editor note is also included: The mapping of Sh messages to HSS or IMS AS SBI services is FFS. NOTE: Change on change will be removed when a clean revision is produced.","secretary_remarks":"Revision of S2-2412403. Revised in parallel session to S2-2412913.","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":12870,"status":"revised","reservation_date":"2024-11-20 20:10:11","uploaded":"2024-11-25 06:51:07","revisionof":"S2-2412403","revisedto":"S2-2412913","release":"Rel-19","crspec":"23.228","crspecversion":"19.0.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1409.0,"crrevision":14.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2412688.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2412689","title":"KI#1: Enhancements to NEF Services","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: List the Nnef_ImsEE services and makes reference to 23.228 for its description. The list of supported IMS events is included in the NF profile of IMS AS. IMS AS is added as consumer of NRF services. This was missing in the baseline. Update to the CR to remove the editors note on parameter design and complete the service description. NOTE: Change on change will be removed when a clean revision is produced.","secretary_remarks":"Revision of S2-2412404. Agreed in parallel session. Revised in parallel session to S2-2412928.","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":12940,"status":"revised","reservation_date":"2024-11-20 20:10:11","uploaded":"2024-11-25 06:51:07","revisionof":"S2-2412404","revisedto":"S2-2412928","release":"Rel-19","crspec":"23.502","crspecversion":"19.1.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":4872.0,"crrevision":12.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2412689.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2412690","title":"Alignment of DC exposure and standalone DC with IMS DC architecture","source":"China Mobile","contact":"Yi Jiang","contact-id":40863,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Remove the limit to allow standalone DC establishment; Add the reference to Annex for IMS DC event exposure and IMS DC capability exposure. Add new clause of NEF.","secretary_remarks":"Revision of S2-2412405. Agreed in parallel session. Block approved","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":13010,"status":"agreed","reservation_date":"2024-11-20 20:10:11","uploaded":"2024-11-25 06:51:07","revisionof":"S2-2412405","revisedto":"","release":"Rel-19","crspec":"23.228","crspecversion":"19.0.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1509.0,"crrevision":2.0,"crcategory":"B","tsg_crp":"SP-241491","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2412690.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2412691","title":"Network Capability Exposure Procedure","source":"[Huawei, HiSilicon, Qualcomm], Samsung,[ ZTE], NTT DOCOMO","contact":"Jari Mutikainen","contact-id":38346,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add the procedures of IMS data channel capabilies exposure. Rev-4: 1. Resolving the EN: 'Whether and how to have intermediate call notification during the procedure is FFS'. In the current procedure, the DC AS needs to wait until both UEs have accepted or rejected the session (or session modification) until it receives the response to the request (HTTP 2xx). It is proposed to add a subscribe\/notify operations under the Nimsas_IMSSessionManagement service, so that the response indicating whether the request is accepted or rejected can be provided immediately, and the actual IMS session progress with the UEs is reported via notify service operation. In this way, the NEF uses the callback URI to find the IMS AS, and discovery from HSS is not needed, and the EN 'the service for step 2 is FFS' on how to discover the IMS AS can be removed. 2. The current procedure refers to OMA API that can be used to notify the non-DC related IMS session events to the DC AS. The OMA API needs to provide a callback URI that the DC AS can use to target the update-request to the same IMS AS that send the notification (and who is anchoring the IMS session). It should be noted that OMA API cannot be used to notify for DC-related events; the item 1 in this CR is used for DC-related events. 3. Resolving the EN 'The need for a new event in step 4 is FFS': it is proposed to re-use the existing Nimsas_SessionEventControl_Notify service operation. The notify request must be enhanced to include the Media information set that the IMS AS has received in Nimsas_ImsSessionManagement_Create or _Update request from the NEF, and new Event IDs: '3rd party session update' and '3rd party session creation'. The media information set indicates to the DCSF the DC type (P2A, P2A2P, P2P, or BDC) and e.g. the MDC2 media end point address if a new DC is added with the DC AS. 4. It is proposed to merge the procedures for adding of data channels and removing of a data channels. 5. Editorial changes.","secretary_remarks":"Revision of S2-2412466. Revised in parallel session to S2-2412915.","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":13100,"status":"revised","reservation_date":"2024-11-20 20:10:11","uploaded":"2024-11-25 06:51:07","revisionof":"S2-2412466","revisedto":"S2-2412915","release":"Rel-19","crspec":"23.228","crspecversion":"19.0.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1489.0,"crrevision":9.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2412691.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2412692","title":"Address ENs in IMS AS Session Management Service","source":"[ZTE, Qualcomm, Huawei], NTT DOCOMO, Samsung","contact":"Jari Mutikainen","contact-id":38346,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Address the ENs for Nimsas_ImsSessionManagement Service in clause AA.2.4.4 of TS 23.228. Rev-3: Add Nimsas_ImsSessionManagement_Notify service operation. Correct the conditions to include MDC2 media endpoint address into Media information set.","secretary_remarks":"Revision of S2-2412465. Revised in parallel session to S2-2412914.","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":13040,"status":"revised","reservation_date":"2024-11-20 20:10:11","uploaded":"2024-11-25 06:51:07","revisionof":"S2-2412465","revisedto":"S2-2412914","release":"Rel-19","crspec":"23.228","crspecversion":"19.0.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1483.0,"crrevision":7.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2412692.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2412693","title":"Update NEF services to support the conclusion of KI#1 and KI#2","source":"[Huawei, HiSilicon, Qualcomm, ZTE,] Samsung, NTT DOCOMO","contact":"Jari Mutikainen","contact-id":38346,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Enhance the NEF service to support IMS event subscription\/notification and data channel establishment, update and termination. Rev-3: Add Nnef_ImsSessionManagement_Notify service operation","secretary_remarks":"Revision of S2-2412467. Revised to S2-2413032.","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":13170,"status":"revised","reservation_date":"2024-11-20 20:10:11","uploaded":"2024-11-25 06:51:07","revisionof":"S2-2412467","revisedto":"S2-2413032","release":"Rel-19","crspec":"23.502","crspecversion":"19.1.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":5087.0,"crrevision":6.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2412693.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2412694","title":"[DRAFT] LS on clarification on reply SDP for standalone DC","source":"vivo","contact":"Zhenhua Xie","contact-id":83004,"tdoctype":"LS out","for":"Approval","abstract":"-","secretary_remarks":"Revision of S2-2412469. Revised to S2-2413033.","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":13270,"status":"revised","reservation_date":"2024-11-20 20:10:11","uploaded":"2024-11-25 06:51:07","revisionof":"S2-2412469","revisedto":"S2-2413033","release":"Rel-19","crspec":"","crspecversion":"","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"-","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2412694.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2412695","title":"KI#6: Modification on standalone IMS DC session","source":"Vivo, Qualcomm, CMCC","contact":"Zhenhua Xie","contact-id":83004,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1. Editorially modify the general clause to make it clearer. 2. Correct the high level descrption of the procedure in AC.10.2.1\/2\/3 for clarifying. 3. Modify NOTE 2 to add the example for clarifying the purpose of the procedure in AC.10.2.1. 4. Add early media handling description in general clause and AC.10.2.2\/3. 5. Add a NOTE to describe the alert and modify how UE Alert in general clause to make it more clear. 6. Change the title to reflect the procedure more accuracy. 7. Two alternatives for AC.10.2.2 are provided. 8. Some editorial modification.","secretary_remarks":"Revision of S2-2412468. Revised in parallel session to S2-2412916.","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":13230,"status":"revised","reservation_date":"2024-11-20 20:10:11","uploaded":"2024-11-25 06:51:07","revisionof":"S2-2412468","revisedto":"S2-2412916","release":"Rel-19","crspec":"23.228","crspecversion":"19.0.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1518.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2412695.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2412696","title":"KI#3: DC interworking with MTSI UE","source":"Samsung, [Ericsson]","contact":"DongYeon Kim","contact-id":87763,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Descriptions on different types of DC interworking with MTSI UE are introduced. It includes the transcoding between the data channel media and the MMTeL media, the DCAS triggering the corresponding actions for terminating MTSI UE and the originating MTSI UE. In addition, Add EN to cover the missing enhancements to services to support the feature. Correctly describe the role to be performed by the MF. Complete some of the steps. Added in rev 4 (SA WG2#166): Editorial fix in AC.7.9.0 General Editorial fix in AC.7.9.1 Editorial fix in AC.7.9.2 The ENs in AC.7.9.3 are resolved by the updated Figure AC.7.9.3-1, steps 1a-1e, and steps 6a-6e. The EN in AC.7.9.0 is resolved by AC.7.9.4.","secretary_remarks":"Revision of S2-2412636. Revised in parallel session to S2-2412917.","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":13310,"status":"revised","reservation_date":"2024-11-20 20:10:11","uploaded":"2024-11-25 06:51:07","revisionof":"S2-2412636","revisedto":"S2-2412917","release":"Rel-19","crspec":"23.228","crspecversion":"19.0.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1479.0,"crrevision":7.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2412696.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2412909","title":"Support of third party user identity information in IMS","source":"Nokia, Samsung, Ericsson, Qualcomm","contact":"Rainer Liebhart","contact-id":68375,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Conclusion principles from TR 23.700-77 are implemented in TS 23.228. Especially a new Annex is introdcued showing the overall architecture and descriping the impacts to functional entities. Rev5: Two editor's notes are resolved and a figure is added to illustrate the procedure about authorization, signing, and verification of third party user identity information in IMS. EN on NEF provisioning: Although this was concluded at the end of the study phase no solution in TR 23.700-77 has described how it works. Thus, this should be part of a later release. EN on S-CSCF authorization: authorizing use of RCD information should be left to IMS AS as it is part of service authorization. Also, different options in the standard should be avoided.","secretary_remarks":"Revision of S2-2412685. Agreed in parallel session. Block approved","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":12760,"status":"agreed","reservation_date":"2024-11-25 06:26:42","uploaded":"2024-11-25 06:51:09","revisionof":"S2-2412685","revisedto":"","release":"Rel-19","crspec":"23.228","crspecversion":"19.0.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1478.0,"crrevision":11.0,"crcategory":"B","tsg_crp":"SP-241491","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2412909.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2412910","title":"Procedure for supporting of third party user identity information in IMS","source":"Samsung, Nokia","contact":"Ashok Kumar Nayak","contact-id":90702,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Feature procedural details along in the lines of KI#4 conclusions specified in TR 23.700-77","secretary_remarks":"Revision of S2-2412686. Agreed in parallel session. Block approved","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":12800,"status":"agreed","reservation_date":"2024-11-25 06:26:42","uploaded":"2024-11-25 06:51:09","revisionof":"S2-2412686","revisedto":"","release":"Rel-19","crspec":"23.228","crspecversion":"19.0.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1524.0,"crrevision":3.0,"crcategory":"B","tsg_crp":"SP-241491","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2412910.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"Annex AX (New)","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2412911","title":"KI#8: Architecture for avatar communications","source":"Samsung, ZTE, vivo, Huawei, HiSilicon, Qualcomm","contact":"DongYeon Kim","contact-id":87763,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The description of IMS DC based avatar communication is introduced. [R04: SA WG2#166] Editor's Notes in clause AC.X.1 General is cleared. Note regarding DC AS URL is clarified. Function description of IMS AS is added in clause AC.X.2. Reference points are added in clause AC.X.2. Procedures are newly added as clause AC.X.3. Service operation parameter is added in clause AA.2.4.2.2.","secretary_remarks":"Revision of S2-2412682. Revised to S2-2413031.","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":12560,"status":"revised","reservation_date":"2024-11-25 06:26:43","uploaded":"2024-11-25 06:51:09","revisionof":"S2-2412682","revisedto":"S2-2413031","release":"Rel-19","crspec":"23.228","crspecversion":"19.0.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1480.0,"crrevision":10.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2412911.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2412912","title":"Supporting Avatar Communication","source":"Huawei, HiSilicon, ZTE, Samsung","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Define the avatar communication call flows","secretary_remarks":"Revision of S2-2412683. Agreed in parallel session. Block approved","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":12660,"status":"agreed","reservation_date":"2024-11-25 06:26:44","uploaded":"2024-11-25 06:51:09","revisionof":"S2-2412683","revisedto":"","release":"Rel-19","crspec":"23.228","crspecversion":"19.0.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1525.0,"crrevision":3.0,"crcategory":"B","tsg_crp":"SP-241491","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2412912.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2412913","title":"KI#1: IMS Subscribe\/Notify Framework Architecture","source":"Ericsson, Samsung, Nokia, T-Mobile USA, NTT DOCOMO, Qualcomm, Huawei","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1. A new NEF service, based on SUBSCRIBE\/NOTIFY request, is defined for the IMS events and event categories. Event categories includes a collection of individual events. 2. Subscriber specific events and non-subscriber specific events are supported. 3. A subscriber specific request includes the targeted subscribers. The targeted subscriber(s) can be either one distinct subscriber, or multiple subscribers given as a list. The events in the request are common for all targeted subscribers. This request is sent to the HSS instance(s) serving the given subscribers. 4. HSS supports the handling of subscriber specific requests. To that effect, the subscribe requests that are subscriber specific are sent from the NEF to HSS. HSS handles registered and unregistered UEs and ensures that a subscription is persistent when UE registers, deregisters and re-registers in IMS. Hence, HSS stores the subscription request and sends the subscription request to the IMS AS whenever the IMS AS instance supporting the requested event is assigned to the UE. The information about the subscription events stored in HSS is only relevant and consumed by HSS. NEF and AF use a new service to manage subscription requests (e.g. subscribe\/unsubscribe) via HSS for subscriber specific events. 5. The IMS AS instance assigned to a UE during IMS registration is registered in HSS. Existing SBI Nhss_ImsUECM service used for S-CSCF is enhanced to allow the registration of the IMS AS instance in HSS over N71\/Sh. 6. Subscription requests that are non-subscriber specific are sent directly to all IMS AS instances configured in the PLMN. 7. Notifications related to a subscription is sent directly to the NF (e.g. NEF or AF) that triggered the subscription request Enhance Nhss to support IMS AS registration, deregistration. Support a new service Nhss_ImsEE to enable subscription to subscriber related events. Support a new service Nimsas_ImsEE to enable subscription to subscriber related events, as well as non-subscriber related events. Support a new service Nnef_ImsEE to enable subscription to subscriber related events, as well as non-subscriber related events. Update to the CR. Two editor notes are addressed: Handling of subscription to a number of events in a single subscription. Completing the definition of event filters for IMS DC events supported in this release. A new Editor note is also included: The mapping of Sh messages to HSS or IMS AS SBI services is FFS. NOTE: Change on change will be removed when a clean revision is produced.","secretary_remarks":"Revision of S2-2412688. Agreed in parallel session. Block approved","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":12880,"status":"agreed","reservation_date":"2024-11-25 06:26:45","uploaded":"2024-11-25 06:51:09","revisionof":"S2-2412688","revisedto":"","release":"Rel-19","crspec":"23.228","crspecversion":"19.0.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1409.0,"crrevision":15.0,"crcategory":"B","tsg_crp":"SP-241491","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2412913.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"Annex XX (new), AA.2.1.1, AA.2.1.2.1, AA.2.1.2.2, AA.2.1.X (new), AA.2.2.3, AA.2.4.1AA.2.4.2, AA.2.4.2.2, AA.2.4.2.3 AA.2.X (new), AC.2.2.4, AC.2.2.6","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2412914","title":"Address ENs in IMS AS Session Management Service","source":"ZTE, Qualcomm, Huawei, NTT DOCOMO, Samsung","contact":"Jari Mutikainen","contact-id":38346,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Address the ENs for Nimsas_ImsSessionManagement Service in clause AA.2.4.4 of TS 23.228. Rev-3: Add Nimsas_ImsSessionManagement_Notify service operation. Correct the conditions to include MDC2 media endpoint address into Media information set.","secretary_remarks":"Revision of S2-2412692. Agreed in parallel session. Block approved","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":13050,"status":"agreed","reservation_date":"2024-11-25 06:26:45","uploaded":"2024-11-25 06:51:09","revisionof":"S2-2412692","revisedto":"","release":"Rel-19","crspec":"23.228","crspecversion":"19.0.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1483.0,"crrevision":8.0,"crcategory":"B","tsg_crp":"SP-241491","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2412914.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2412915","title":"Network Capability Exposure Procedure","source":"Huawei, HiSilicon, Qualcomm, Samsung, ZTE, NTT DOCOMO, Nokia","contact":"Jari Mutikainen","contact-id":38346,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add the procedures of IMS data channel capabilies exposure. Rev-4: 1. Resolving the EN: 'Whether and how to have intermediate call notification during the procedure is FFS'. In the current procedure, the DC AS needs to wait until both UEs have accepted or rejected the session (or session modification) until it receives the response to the request (HTTP 2xx). It is proposed to add a subscribe\/notify operations under the Nimsas_IMSSessionManagement service, so that the response indicating whether the request is accepted or rejected can be provided immediately, and the actual IMS session progress with the UEs is reported via notify service operation. In this way, the NEF uses the callback URI to find the IMS AS, and discovery from HSS is not needed, and the EN 'the service for step 2 is FFS' on how to discover the IMS AS can be removed. 2. The current procedure refers to OMA API that can be used to notify the non-DC related IMS session events to the DC AS. The OMA API needs to provide a callback URI that the DC AS can use to target the update-request to the same IMS AS that send the notification (and who is anchoring the IMS session). It should be noted that OMA API cannot be used to notify for DC-related events; the item 1 in this CR is used for DC-related events. 3. Resolving the EN 'The need for a new event in step 4 is FFS': it is proposed to re-use the existing Nimsas_SessionEventControl_Notify service operation. The notify request must be enhanced to include the Media information set that the IMS AS has received in Nimsas_ImsSessionManagement_Create or _Update request from the NEF, and new Event IDs: '3rd party session update' and '3rd party session creation'. The media information set indicates to the DCSF the DC type (P2A, P2A2P, P2P, or BDC) and e.g. the MDC2 media end point address if a new DC is added with the DC AS. 4. It is proposed to merge the procedures for adding of data channels and removing of a data channels. 5. Editorial changes.","secretary_remarks":"Revision of S2-2412691. Agreed in parallel session. Block approved","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":13110,"status":"agreed","reservation_date":"2024-11-25 06:26:46","uploaded":"2024-11-25 06:51:09","revisionof":"S2-2412691","revisedto":"","release":"Rel-19","crspec":"23.228","crspecversion":"19.0.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1489.0,"crrevision":10.0,"crcategory":"B","tsg_crp":"SP-241491","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2412915.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2412916","title":"KI#6: Modification on standalone IMS DC session","source":"Vivo, Qualcomm, CMCC, Huawei","contact":"Zhenhua Xie","contact-id":83004,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1. Editorially modify the general clause to make it clearer. 2. Correct the high level descrption of the procedure in AC.10.2.1\/2\/3 for clarifying. 3. Modify NOTE 2 to add the example for clarifying the purpose of the procedure in AC.10.2.1. 4. Add early media handling description in general clause and AC.10.2.2\/3. 5. Add a NOTE to describe the alert and modify how UE Alert in general clause to make it more clear. 6. Change the title to reflect the procedure more accuracy. 7. Two alternatives for AC.10.2.2 are provided. 8. Some editorial modification.","secretary_remarks":"Revision of S2-2412695. Agreed in parallel session. Block approved","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":13240,"status":"agreed","reservation_date":"2024-11-25 06:26:47","uploaded":"2024-11-25 06:51:09","revisionof":"S2-2412695","revisedto":"","release":"Rel-19","crspec":"23.228","crspecversion":"19.0.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1518.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"SP-241491","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2412916.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2412917","title":"KI#3: DC interworking with MTSI UE","source":"Samsung, Ericsson, Huawei, HiSilicon","contact":"DongYeon Kim","contact-id":87763,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Descriptions on different types of DC interworking with MTSI UE are introduced. It includes the transcoding between the data channel media and the MMTeL media, the DCAS triggering the corresponding actions for terminating MTSI UE and the originating MTSI UE. In addition, Add EN to cover the missing enhancements to services to support the feature. Correctly describe the role to be performed by the MF. Complete some of the steps. Added in rev 4 (SA WG2#166): Editorial fix in AC.7.9.0 General Editorial fix in AC.7.9.1 Editorial fix in AC.7.9.2 The ENs in AC.7.9.3 are resolved by the updated Figure AC.7.9.3-1, steps 1a-1e, and steps 6a-6e. The EN in AC.7.9.0 is resolved by AC.7.9.4.","secretary_remarks":"Revision of S2-2412696. Agreed in parallel session. Block approved","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":13320,"status":"agreed","reservation_date":"2024-11-25 06:26:47","uploaded":"2024-11-25 06:51:09","revisionof":"S2-2412696","revisedto":"","release":"Rel-19","crspec":"23.228","crspecversion":"19.0.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1479.0,"crrevision":8.0,"crcategory":"B","tsg_crp":"SP-241491","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2412917.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2412928","title":"KI#1: Enhancements to NEF Services","source":"Ericsson, Samsung","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: List the Nnef_ImsEE services and makes reference to 23.228 for its description. The list of supported IMS events is included in the NF profile of IMS AS. IMS AS is added as consumer of NRF services. This was missing in the baseline. Update to the CR to remove the editors note on parameter design and complete the service description. NOTE: Change on change will be removed when a clean revision is produced.","secretary_remarks":"Revision of S2-2412689. Agreed in parallel session. Block approved","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":12950,"status":"agreed","reservation_date":"2024-11-25 06:26:55","uploaded":"2024-11-25 06:51:09","revisionof":"S2-2412689","revisedto":"","release":"Rel-19","crspec":"23.502","crspecversion":"19.1.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":4872.0,"crrevision":13.0,"crcategory":"B","tsg_crp":"SP-241491","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2412928.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.2.6.1, 5.2.6.X (NEW), 5.2.7.1, 5.2.7.2.2.","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2413031","title":"KI#8: Architecture for avatar communications","source":"Samsung, ZTE, vivo, Huawei, HiSilicon, Qualcomm","contact":"DongYeon Kim","contact-id":87763,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The description of IMS DC based avatar communication is introduced. [R04: SA WG2#166] Editor's Notes in clause AC.X.1 General is cleared. Note regarding DC AS URL is clarified. Function description of IMS AS is added in clause AC.X.2. Reference points are added in clause AC.X.2. Procedures are newly added as clause AC.X.3. Service operation parameter is added in clause AA.2.4.2.2.","secretary_remarks":"Revision of S2-2412911. This CR was agreed","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":12570,"status":"agreed","reservation_date":"2024-11-25 06:27:39","uploaded":"2024-11-25 06:51:10","revisionof":"S2-2412911","revisedto":"","release":"Rel-19","crspec":"23.228","crspecversion":"19.0.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1480.0,"crrevision":11.0,"crcategory":"B","tsg_crp":"SP-241491","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2413031.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2413032","title":"Update NEF services to support the conclusion of KI#1 and KI#2","source":"Huawei, HiSilicon, Qualcomm, ZTE, Samsung, NTT DOCOMO","contact":"Jari Mutikainen","contact-id":38346,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Enhance the NEF service to support IMS event subscription\/notification and data channel establishment, update and termination. Rev-3: Add Nnef_ImsSessionManagement_Notify service operation","secretary_remarks":"Revision of S2-2412693. This CR was agreed","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":13180,"status":"agreed","reservation_date":"2024-11-25 06:27:39","uploaded":"2024-11-25 06:51:10","revisionof":"S2-2412693","revisedto":"","release":"Rel-19","crspec":"23.502","crspecversion":"19.1.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":5087.0,"crrevision":7.0,"crcategory":"B","tsg_crp":"SP-241491","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2413032.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2413033","title":"LS on clarification on reply SDP for standalone DC","source":"SA WG2","contact":"Zhenhua Xie","contact-id":83004,"tdoctype":"LS out","for":"Approval","abstract":"To: SA WG4","secretary_remarks":"Revision of S2-2412694. This LS OUT was approved","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":13280,"status":"approved","reservation_date":"2024-11-25 06:27:40","uploaded":"2024-11-25 06:51:10","revisionof":"S2-2412694","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG4","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2413033.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2500065","title":"LS from SA WG4: Reply LS on Clarification of DC Binding Information","source":"SA WG4","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Action","abstract":"SA WG4 thanks SA WG2 for their liaison on Clarification of DC Binding Information. SA WG4 understands that this relates to supporting standalone application data channel without any bootstrap data channel, where it is required that both UEs need to acquire a compatible version of the DC app for such application data channel to be established. {. .}","secretary_remarks":"Not Handled. Postponed","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":13380,"status":"postponed","reservation_date":"2024-12-29 10:58:22","uploaded":"2024-12-29 12:18:51","revisionof":"","revisedto":"S2-2501374","release":"Rel-19","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"S4-242111","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2500065.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2500079","title":"LS from SA WG3: LS on IMS support for AF authorization and IMS avatar communication","source":"SA WG3","contact":"Vlasios Tsiatsis","contact-id":76181,"tdoctype":"LS in","for":"Information","abstract":"SA WG3 has been studying the authentication and authorization of an Application Function (AF) in TR 33.790 as part of Key Issue #3: 'Security and privacy aspects of IMS DC capability exposure'. This key issue is related to the IMS event framework and the IMS Data Channel session control work in TS 23.228. In the context of TR 33.790, KI#3 an AF is supposed to be authenticated and authorized before requesting for an IMS event or requesting the establishment\/update\/termination of a data channel. {. . .}","secretary_remarks":"Postponed in e-mail session","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":13420,"status":"postponed","reservation_date":"2024-12-29 10:58:23","uploaded":"2025-01-17 10:35:35","revisionof":"","revisedto":"S2-2501378","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"S3-250170","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2500079.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2500169","title":"Resolving ENs on Avatar communication","source":"Qualcomm Incorporated","contact":"Kefeng Zhang","contact-id":103832,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Added clarification of Avatar ID. Clarified that DC AS URL is pre-configured in DCSF Avatar Representation is selected in Avatar Application and downloaded via ADC. Removed the interworking between DCSF and DCAR in clause AC.11.3.1. Cla","secretary_remarks":"Noted in e-mail session","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":13430,"status":"noted","reservation_date":"2025-01-09 15:18:16","uploaded":"2025-01-10 11:37:15","revisionof":"","revisedto":"S2-2501790","release":"Rel-19","crspec":"23.228","crspecversion":"19.1.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1531.0,"crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2500169.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2500170","title":"Correction on IMS data channel capability exposure","source":"Qualcomm Incorporated","contact":"Kefeng Zhang","contact-id":103832,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Figure AG.2.1-1 is updated by adding the missing steps from IMS AS-2 to NEF and DC AS associated with steps 4 and 5 of the procedural text. The Editor's Note in AG.1 is removed. Other editorial changes.","secretary_remarks":"Merged into S2-2501099","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":13610,"status":"merged","reservation_date":"2025-01-09 15:24:02","uploaded":"2025-01-10 11:37:15","revisionof":"","revisedto":"","release":"Rel-19","crspec":"23.228","crspecversion":"19.1.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1532.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2500170.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2500171","title":"Clarification on PS Data Off status change reporting to DCSF","source":"Qualcomm Incorporated","contact":"Kefeng Zhang","contact-id":103832,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The change clarifies that the IMS AS will notify the DCSF when the user changes the PS Data Off status during the period of IMS Session.","secretary_remarks":"r05 agreedrevised in e-mail session to S2-2501100, merging S2-2500626 and S2-2500637","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":13770,"status":"revised","reservation_date":"2025-01-09 15:26:35","uploaded":"2025-01-10 11:37:15","revisionof":"","revisedto":"S2-2501100","release":"Rel-19","crspec":"23.228","crspecversion":"19.1.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1533.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2500171.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2500173","title":"Clarification on third-party user ID provisioning procedure","source":"Qualcomm Incorporated","contact":"Kefeng Zhang","contact-id":103832,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify the differences in third-party user identity information provisioning for UE and IP-PBX.","secretary_remarks":"Not Handled","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":13830,"status":"not treated","reservation_date":"2025-01-09 15:29:04","uploaded":"2025-01-10 11:37:15","revisionof":"","revisedto":"S2-2501792","release":"Rel-19","crspec":"23.228","crspecversion":"19.1.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1534.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2500173.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2500203","title":"KI#1: Editorial updates to IMS Subscribe\/Notify Framework Architecture","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Mostly ediorial corrections to enhance the flow of information. Remove event category from call flows. Clarified the interworking event. Include AF Identifier as additional input to the subscribe request by an AS so that NEF and HSS can","secretary_remarks":"Not Handled","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":13860,"status":"not treated","reservation_date":"2025-01-10 12:57:35","uploaded":"2025-01-14 21:44:50","revisionof":"","revisedto":"S2-2501501","release":"Rel-19","crspec":"23.228","crspecversion":"19.1.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1536.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2500203.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"AA.2.1.2.1, AA.2.1.5.1, AA.2.2.3, AA.2.4.5.3, AD.1, AD.2.3.2, AD.2.2.3, AD.2.4, AD.2.5.2, AD.3.1, AD.3.2, AD.3.3","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2500204","title":"KI#1: Update to NEF Services","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Include AF identifier to Nnef_ImsEE_Subscribe to enable NEF authorization. Align Nnef_ImsEE_Notify service with the IMS AS and HSS Notify service.","secretary_remarks":"Not Handled","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":13870,"status":"not treated","reservation_date":"2025-01-10 12:57:38","uploaded":"2025-01-14 21:44:50","revisionof":"","revisedto":"S2-2501502","release":"Rel-19","crspec":"23.502","crspecversion":"19.2.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":5209.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2500204.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.2.6.39.2.1, 5.2.6.39.2.3","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2500205","title":"KI#8: Update to Architecture for avatar communications","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add editor notes for security related aspects. Add editor notes related to the means for providing the DC AS URL to the DCSF. Clarify the ways in which MF fetches the Avatar representation, directly from the BAR through redirection from","secretary_remarks":"Not handled at CC#4. Postponed","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":13440,"status":"postponed","reservation_date":"2025-01-10 12:57:39","uploaded":"2025-01-14 21:44:50","revisionof":"","revisedto":"S2-2501503","release":"Rel-19","crspec":"23.228","crspecversion":"19.1.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1537.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2500205.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":true,"clauses_affected":"AC.11.1, AC.11.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2500206","title":"KI#8: Update to Avatar Procedures","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add editor notes related to steps in various procedures that are unclear. Clarified aspects and editorial corrections.","secretary_remarks":"Noted in e-mail session","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":13450,"status":"noted","reservation_date":"2025-01-10 12:57:39","uploaded":"2025-01-14 21:44:50","revisionof":"","revisedto":"","release":"Rel-19","crspec":"23.228","crspecversion":"19.1.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1538.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2500206.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":true,"clauses_affected":"AA.2.4.3.2, AC.11.3.1, AC.3.2,  AC.11.3.2.1, AC.11.3.2.2, AC.11.3.3","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2500207","title":"KI#3: Update to DC interworking with MTSI UE","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Editorial changes and linguistic enhancements. Inconsistenceis relates to the interworking event specified in claue AD.2.5.2 Application Data Channel requires interworking is established Detected when an Application Data Channel that re","secretary_remarks":"Not Handled","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":13900,"status":"not treated","reservation_date":"2025-01-10 12:57:40","uploaded":"2025-01-14 21:44:50","revisionof":"","revisedto":"S2-2501504","release":"Rel-19","crspec":"23.228","crspecversion":"19.1.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1539.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2500207.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"AC.7.9.0, AC.7.9.1, AC.7.9.2, AC.7.9.3, AC.7.9.4","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2500208","title":"KI#2: Generalizing Information Retrieval","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Make the service generic to retrieve any information stored in HSS.","secretary_remarks":"Not Handled","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":13620,"status":"not treated","reservation_date":"2025-01-10 12:57:41","uploaded":"2025-01-14 21:44:50","revisionof":"","revisedto":"S2-2501505","release":"Rel-19","crspec":"23.228","crspecversion":"19.1.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1540.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2500208.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"AA.2.1.1, AA.2.1.2.8.","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2500209","title":"KI#2: Update to Network Capability Exposure Procedures","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Expand the procedure updating an existing IMS session for a Data Channel UpdateAdd the procedures of IMS data channel capabilies exposure. Complete the procedure for creating a stand alone IMS DC Complete the procedure for terminating a","secretary_remarks":"r04 agreedrevised in e-mail session to S2-2501097.","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":13630,"status":"revised","reservation_date":"2025-01-10 12:57:41","uploaded":"2025-01-14 21:44:50","revisionof":"","revisedto":"S2-2501097","release":"Rel-19","crspec":"23.228","crspecversion":"19.1.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1541.0,"crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2500209.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"AA.2.4.2.2, AG.1, AG.2.1, AG.2.2, AG.2.3","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2500210","title":"KI#2: Udpdate to IMS AS Session Management Services","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Make the services\/operations generic","secretary_remarks":"Merged into S2-2501098","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":13650,"status":"merged","reservation_date":"2025-01-10 12:57:42","uploaded":"2025-01-14 21:44:50","revisionof":"","revisedto":"","release":"Rel-19","crspec":"23.228","crspecversion":"19.1.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1542.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2500210.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"AA.2.4.4.1, AA.2.4.4.2, AA.2.4.4.3, AA.2.4.4.5.","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2500287","title":"Abbreviations of ADC and BDC","source":"Vivo","contact":"Zhenhua Xie","contact-id":83004,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Addition of ADC and BDC in clause 3.3.","secretary_remarks":"Not Handled","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":13390,"status":"not treated","reservation_date":"2025-01-12 02:34:23","uploaded":"2025-01-13 14:45:22","revisionof":"","revisedto":"S2-2501662","release":"Rel-19","crspec":"23.228","crspecversion":"19.1.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1543.0,"crrevision":"","crcategory":"D","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2500287.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"3.3","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2500288","title":"Adding more event filters for ADC media type","source":"Vivo","contact":"Zhenhua Xie","contact-id":83004,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Refine the granularity of event filters for ADC media type.","secretary_remarks":"Not Handled","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":13880,"status":"not treated","reservation_date":"2025-01-12 02:34:27","uploaded":"2025-01-13 14:45:22","revisionof":"","revisedto":"S2-2501663","release":"Rel-19","crspec":"23.228","crspecversion":"19.1.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1544.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2500288.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"AD.2.5.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2500289","title":"Multiplexing with duplicated stream ID.","source":"Vivo","contact":"Zhenhua Xie","contact-id":83004,"tdoctype":"discussion","for":"Information","abstract":"This contribution discusses the case of duplicated stream ID in multiplexing case.","secretary_remarks":"Noted in e-mail session","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":13530,"status":"noted","reservation_date":"2025-01-12 02:34:27","uploaded":"2025-01-13 14:45:22","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2500289.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2500290","title":"De-multiplexing ADC in case same stream ID used by both UEs","source":"Vivo","contact":"Zhenhua Xie","contact-id":83004,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add new de-multiplex criteria based on same stream ID used; Add new sub-clause to show the procedure accordingly.","secretary_remarks":"Noted in e-mail session","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":13540,"status":"noted","reservation_date":"2025-01-12 02:34:27","uploaded":"2025-01-13 14:45:22","revisionof":"","revisedto":"","release":"Rel-19","crspec":"23.228","crspecversion":"19.1.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1545.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2500290.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"AC.7.10.1, AC.7.10.3.1, AC.7.10.4.2.x (new)","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2500291","title":"Update on support of DC interworking","source":"Vivo","contact":"Zhenhua Xie","contact-id":83004,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add a new description that the new added video media is for sendonly.","secretary_remarks":"Revision of S2-2411943 Not Handled","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":13910,"status":"not treated","reservation_date":"2025-01-12 02:34:28","uploaded":"2025-01-13 14:45:22","revisionof":"S2-2411943","revisedto":"S2-2501664","release":"Rel-19","crspec":"23.228","crspecversion":"19.1.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1465.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2500291.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"AC.7.9.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2500292","title":"Modification on general description for standalone IMS DC session","source":"Vivo","contact":"Zhenhua Xie","contact-id":83004,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1. Correct the wording of 'user concern' to 'user consent'. 2. Change 'information from application' to 'information for the application' 3. Some editorial change.","secretary_remarks":"Not Handled","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":13930,"status":"not treated","reservation_date":"2025-01-12 02:34:29","uploaded":"2025-01-13 14:45:22","revisionof":"","revisedto":"S2-2501665","release":"Rel-19","crspec":"23.228","crspecversion":"19.1.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1546.0,"crrevision":"","crcategory":"D","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2500292.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"AC.10.1","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2500620","title":"Correction of detection criteria for event exposure","source":"China Mobile","contact":"Yi Jiang","contact-id":40863,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Event detection criteria are updated to include the success of media resource reservation in the criteria. Editorial changes are proposed.","secretary_remarks":"Not Handled","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":13890,"status":"not treated","reservation_date":"2025-01-14 07:43:21","uploaded":"2025-01-14 14:26:45","revisionof":"","revisedto":"S2-2501731","release":"Rel-19","crspec":"23.228","crspecversion":"19.1.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1548.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2500620.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"AD.2.5.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2500621","title":"Updates to IMS data channel capability exposure procedures","source":"China Mobile","contact":"Yi Jiang","contact-id":40863,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Updates the procedures of IMS DC capability exposure. Editor's note is removed accordingly.","secretary_remarks":"Merged into S2-2501099","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":13660,"status":"merged","reservation_date":"2025-01-14 07:43:22","uploaded":"2025-01-14 14:26:45","revisionof":"","revisedto":"","release":"Rel-19","crspec":"23.228","crspecversion":"19.1.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1549.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2500621.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"AG.1, AG.2.1, AG.2.2, AG.2.3","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2500622","title":"Updates to Nimsas_ImsSessionManagement Service","source":"China Mobile","contact":"Yi Jiang","contact-id":40863,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: updates Nimsas_ImsSessionManagement service to align with the updated procedures in S2-2500621x.","secretary_remarks":"r04 agreedrevised in e-mail session to S2-2501098, merging S2-2500210","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":13670,"status":"revised","reservation_date":"2025-01-14 07:43:23","uploaded":"2025-01-14 14:26:45","revisionof":"","revisedto":"S2-2501098","release":"Rel-19","crspec":"23.228","crspecversion":"19.1.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1550.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2500622.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"AA.2.4.4.1, AA.2.4.4.2, AA.2.4.4.3","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2500623","title":"Updates on procedure and service of DC interworking via DC AS","source":"China Mobile","contact":"Yi Jiang","contact-id":40863,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Use Nimsas_MediaControl_MediaInstruction service operation in step 6a with the indication of DC interworking simultaneously with P2A media resource reservation, to trigger the notification from the IMS AS to DC AS; Enhance the existing","secretary_remarks":"Not Handled","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":13920,"status":"not treated","reservation_date":"2025-01-14 07:43:23","uploaded":"2025-01-14 14:26:45","revisionof":"","revisedto":"S2-2501732","release":"Rel-19","crspec":"23.228","crspecversion":"19.1.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1551.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2500623.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"AC.7.9.3, AA.2.4.3.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2500624","title":"Updates to support multiplexing multiple DC applications over single SCTP connection","source":"China Mobile","contact":"Yi Jiang","contact-id":40863,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Editor's notes are removed and texts are added to describe the solution described above.","secretary_remarks":"r01 agreedrevised in e-mail session to S2-2501096.","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":13550,"status":"revised","reservation_date":"2025-01-14 07:43:25","uploaded":"2025-01-14 14:26:45","revisionof":"","revisedto":"S2-2501096","release":"Rel-19","crspec":"23.228","crspecversion":"19.1.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1552.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2500624.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"AC.7.10.2.2, AC.7.10.3.1, AC.7.10.3.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2500625","title":"Service updates to support multiplexing multiple DC applications over single SCTP connection","source":"China Mobile","contact":"Yi Jiang","contact-id":40863,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The services of IMS AS and MF are updated to support data channel multiplexing over single SCTP connection.","secretary_remarks":"Revision of S2-2411609. Postponed in e-mail session","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":13570,"status":"postponed","reservation_date":"2025-01-14 07:43:26","uploaded":"2025-01-14 14:26:45","revisionof":"S2-2411609","revisedto":"","release":"Rel-19","crspec":"23.228","crspecversion":"19.1.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1512.0,"crrevision":2.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2500625.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":true,"clauses_affected":"AA.2.4.2.2, AA.2.4.3.2, AA.2.4.5.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2500626","title":"KI#5: Support of Data off feature for data channel","source":"China Mobile","contact":"Yi Jiang","contact-id":40863,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: remove the parameter of '3GPP PS Data Off Status' in Nimsas_SessionEventControl_Notify service operation; Define a new event to report the updated 3GPP PS data off status;","secretary_remarks":"Merged into S2-2501100","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":13790,"status":"merged","reservation_date":"2025-01-14 07:43:27","uploaded":"2025-01-14 14:26:45","revisionof":"","revisedto":"","release":"Rel-19","crspec":"23.228","crspecversion":"19.1.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1553.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2500626.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":true,"clauses_affected":"AA.2.4.2.1, AA.2.4.2.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2500635","title":"Address EN on Avatar Representation","source":"ZTE","contact":"Hao Dong","contact-id":75723,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Address the EN regarding Avatar Representation in clause AC.11.1.","secretary_remarks":"Noted in e-mail session","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":13460,"status":"noted","reservation_date":"2025-01-14 07:48:58","uploaded":"2025-01-14 11:05:42","revisionof":"","revisedto":"","release":"Rel-19","crspec":"23.228","crspecversion":"19.1.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1554.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2500635.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"AC.11.1, AC.11.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2500636","title":"Address EN in UE Centric Avatar Communication Procedure","source":"ZTE","contact":"Hao Dong","contact-id":75723,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Address the EN regarding MF downloading Avatar Representation in clause AC.11.3.2.1.","secretary_remarks":"Noted in e-mail session","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":13470,"status":"noted","reservation_date":"2025-01-14 07:49:03","uploaded":"2025-01-14 11:05:42","revisionof":"","revisedto":"","release":"Rel-19","crspec":"23.228","crspecversion":"19.1.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1555.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2500636.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"AC.11.3.2.1, AC.11.3.2.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2500637","title":"Address EN on 3GPP PS Data Off Status Notification","source":"ZTE","contact":"Hao Dong","contact-id":75723,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Address the EN regarding 3GPP PS Data Off status notification in clause AA.2.4.2.1.","secretary_remarks":"Merged into S2-2501100","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":13800,"status":"merged","reservation_date":"2025-01-14 07:49:04","uploaded":"2025-01-14 11:05:42","revisionof":"","revisedto":"","release":"Rel-19","crspec":"23.228","crspecversion":"19.1.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1556.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2500637.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"AA.2.4.2.1, AA.2.4.2.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2500638","title":"Clarification on DC Application Server","source":"ZTE","contact":"Hao Dong","contact-id":75723,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add the function description of DC Application Server.","secretary_remarks":"Not Handled","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":13400,"status":"not treated","reservation_date":"2025-01-14 07:49:05","uploaded":"2025-01-14 11:05:42","revisionof":"","revisedto":"S2-2501950","release":"Rel-19","crspec":"23.228","crspecversion":"19.1.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1557.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2500638.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"3.1, 3.3, AC.2.2.X(new)","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2500639","title":"Clarification on DC Capability Exposure Procedure","source":"ZTE","contact":"Hao Dong","contact-id":75723,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Modify the DC capability exposure procedures.","secretary_remarks":"Noted in e-mail session","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":13690,"status":"noted","reservation_date":"2025-01-14 07:49:05","uploaded":"2025-01-14 11:05:42","revisionof":"","revisedto":"","release":"Rel-19","crspec":"23.228","crspecversion":"19.1.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1558.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2500639.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"AG.1, AG.2.1, AG.2.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2500772","title":"Clarification on how DCSF fetch DC AS URL if not pre-configured","source":"China Mobile","contact":"Yi Jiang","contact-id":40863,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify the DCSF may derive DC AS URL from DCSF service specific data.","secretary_remarks":"r04 agreedrevised in e-mail session to S2-2501095.","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":13480,"status":"revised","reservation_date":"2025-01-14 10:23:45","uploaded":"2025-01-14 14:26:45","revisionof":"","revisedto":"S2-2501095","release":"Rel-19","crspec":"23.228","crspecversion":"19.1.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1563.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2500772.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"AC.11.1, AC.11.3.1","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2500794","title":"KI#8: EN resolutions for Avatar communication","source":"Samsung","contact":"DongYeon Kim","contact-id":87763,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: How the DCSF gets the DC AS URL for Avatar ID List download when it is requested through bootstrap data channel is clarified. The DCSF gets from the DCSF service specific data or from its local configuration. It is clarified that MF rec","secretary_remarks":"Postponed in e-mail session","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":13500,"status":"postponed","reservation_date":"2025-01-14 10:59:19","uploaded":"2025-01-14 11:15:40","revisionof":"","revisedto":"","release":"Rel-19","crspec":"23.228","crspecversion":"19.1.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1565.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2500794.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":true,"clauses_affected":"AA.2.4.3.2, AA.2.5.2.2, AC.11","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2500796","title":"KI#7: Services for supporting multiplexing","source":"Samsung","contact":"DongYeon Kim","contact-id":87763,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: In case of multiplexing, one media specification per one data channel stream is included under a media ID in media info list and media instruction set. In case of de-multiplexing, the original (multiplexed) media ID is additionally incl","secretary_remarks":"Postponed in e-mail session","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":13580,"status":"postponed","reservation_date":"2025-01-14 11:02:23","uploaded":"2025-01-14 11:15:40","revisionof":"","revisedto":"","release":"Rel-19","crspec":"23.228","crspecversion":"19.1.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1566.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2500796.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"2, AA.2.4.2.2, AA.2.4.3.2, AA.2.5.2.2, AC.7.10.3, AC.7.10.4.1","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2500820","title":"[DRAFT] LS on IMS DC multiplexing","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"To: SA WG4. CC: -. Attachments: None.","secretary_remarks":"Postponed in e-mail session","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":13590,"status":"postponed","reservation_date":"2025-01-14 11:43:47","uploaded":"2025-01-14 16:35:24","revisionof":"","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG4","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2500820.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2500821","title":"Update procedure of Avatar Communication","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1.Update detail procedure of the avatar communication network centric call flow. 2.Remove the ENs that have been solved. 3.Some editorial correction.","secretary_remarks":"Not handled at CC#4. Postponed","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":13510,"status":"postponed","reservation_date":"2025-01-14 11:43:47","uploaded":"2025-01-14 16:35:24","revisionof":"","revisedto":"S2-2502077","release":"Rel-19","crspec":"23.228","crspecversion":"19.1.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1567.0,"crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2500821.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":true,"clauses_affected":"AC.11.1, AC.11.3","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2500823","title":"Update Network Capability Exposure Procedure","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Address the EN in Annex AG.1 of TS 23.228.","secretary_remarks":"Noted in e-mail session","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":13700,"status":"noted","reservation_date":"2025-01-14 11:43:49","uploaded":"2025-01-14 16:35:24","revisionof":"","revisedto":"","release":"Rel-19","crspec":"23.228","crspecversion":"19.1.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1568.0,"crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2500823.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"AG.1, AG.2.3","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2500824","title":"KI#5: Support of Data off feature for data channel","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Remove Editor's Note","secretary_remarks":"Not Handled","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":13810,"status":"not treated","reservation_date":"2025-01-14 11:43:49","uploaded":"2025-01-14 16:35:24","revisionof":"","revisedto":"","release":"Rel-19","crspec":"23.228","crspecversion":"19.1.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1569.0,"crrevision":"","crcategory":"D","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2500824.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":true,"clauses_affected":"AA.2.4.2.1","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2500825","title":"Correction on standalone data channel description","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Update the general description of each procedure.","secretary_remarks":"Not Handled","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":13940,"status":"not treated","reservation_date":"2025-01-14 11:44:02","uploaded":"2025-01-14 16:35:24","revisionof":"","revisedto":"","release":"Rel-19","crspec":"23.228","crspecversion":"19.1.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1570.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2500825.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":true,"clauses_affected":"AC.10.1, AC.10.2.1, AC.10.2.2, AC.10.2.3","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2500883","title":"Correction on DC multiplexing procedures","source":"China Mobile","contact":"Yi Jiang","contact-id":40863,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Correct the description of IMS AS notifying DCSF about DC multiplexing; Correct the procedures by adding missing step of IMS AS notifying DCSF about the successful media modification.","secretary_remarks":"Not Handled","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":13600,"status":"not treated","reservation_date":"2025-01-14 14:18:16","uploaded":"2025-01-14 14:26:45","revisionof":"","revisedto":"S2-2501735","release":"Rel-19","crspec":"23.228","crspecversion":"19.1.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1572.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2500883.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2500895","title":"Update IMS DC figures to align with other annex","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add a NEF and SCP in Figure AA.1.1-1 to align with other annex","secretary_remarks":"Not Handled","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":13410,"status":"not treated","reservation_date":"2025-01-14 14:19:34","uploaded":"2025-01-14 16:35:24","revisionof":"","revisedto":"","release":"Rel-19","crspec":"23.228","crspecversion":"19.1.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1573.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2500895.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2500946","title":"3GPP PS Data off status for DCSF","source":"Samsung","contact":"Ashok Kumar Nayak","contact-id":90702,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: IMS AS shall store 3GPP PS Data off status to HSS and DCSF read this status while fetching suscription ifnromation from HSS","secretary_remarks":"Noted in e-mail session","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":13820,"status":"noted","reservation_date":"2025-01-14 15:03:21","uploaded":"2025-01-14 15:55:11","revisionof":"","revisedto":"","release":"Rel-19","crspec":"23.228","crspecversion":"19.1.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1574.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2500946.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2500949","title":"Clarification on Third Party identity verification","source":"Samsung","contact":"Ashok Kumar Nayak","contact-id":90702,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The third party network has been replaced with UE or IP-PBX which actually sends INVITE to the network IMS network has been clarified in the NOTE","secretary_remarks":"Not Handled","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":13840,"status":"not treated","reservation_date":"2025-01-14 15:07:07","uploaded":"2025-01-14 15:58:42","revisionof":"","revisedto":"","release":"Rel-19","crspec":"23.228","crspecversion":"19.1.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1575.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2500949.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":true,"clauses_affected":"AF.2.2.3, AF.3","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2500950","title":"HSS handling for subscription with IMS","source":"Samsung","contact":"Ashok Kumar Nayak","contact-id":90702,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: HSS does subscription with IMS AS if the IMS DC is enabled for the IMPU","secretary_remarks":"Postponed in e-mail session","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":13710,"status":"postponed","reservation_date":"2025-01-14 15:09:43","uploaded":"2025-01-14 15:59:28","revisionof":"","revisedto":"S2-2502095","release":"Rel-19","crspec":"23.228","crspecversion":"19.1.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1576.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2500950.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"AD.1, AD.2.3.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2500951","title":"MMTel media removal clarification","source":"Samsung","contact":"Ashok Kumar Nayak","contact-id":90702,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: IMS AS shall release the IMS data channel session when it determines that UE is not allowed to use standlaone IMS DC while removing all MMTel media from an exising IMS session","secretary_remarks":"Not Handled","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":13950,"status":"not treated","reservation_date":"2025-01-14 15:12:26","uploaded":"2025-01-14 16:00:06","revisionof":"","revisedto":"S2-2502096","release":"Rel-19","crspec":"23.228","crspecversion":"19.1.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1577.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2500951.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2500967","title":"Complete the details for KI#2","source":"NTT DOCOMO","contact":"Jari Mutikainen","contact-id":38346,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add the details how DCSF instructs the IMS AS to add\/update\/remove data channels to an existing IMS session or establish a new IMS session with data channels. In case of BDC or ADC with P2A or P2A2P case, the media flow is established b","secretary_remarks":"Merged into S2-2501099","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":13720,"status":"merged","reservation_date":"2025-01-14 15:54:02","uploaded":"2025-01-14 16:33:11","revisionof":"","revisedto":"","release":"Rel-19","crspec":"23.228","crspecversion":"19.1.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1578.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2500967.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2500971","title":"Complete the details for KI#2","source":"NTT DOCOMO","contact":"Jari Mutikainen","contact-id":38346,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Calling and called party IDs are removed from Nimsas_ImsSessionManagement_Update request, since the session is identified by session ID. The MDC1 media endpoint address is added to the Nimsas_ImsSessionManagement_Update and Nimsas_ImsSe","secretary_remarks":"Postponed in e-mail session","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":13730,"status":"postponed","reservation_date":"2025-01-14 15:58:37","uploaded":"2025-01-14 16:33:11","revisionof":"","revisedto":"S2-2502094","release":"Rel-19","crspec":"23.502","crspecversion":"19.2.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":5311.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2500971.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.2.6.40.2, 5.2.6.40.3","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2501012","title":"KI#4: Update of procedure description","source":"Nokia","contact":"Rainer Liebhart","contact-id":68375,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify procedure regarding presence or absence of third party ID information in SIP INVITE from PBX.","secretary_remarks":"Not Handled","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":13850,"status":"not treated","reservation_date":"2025-01-14 16:59:46","uploaded":"2025-01-14 17:15:34","revisionof":"","revisedto":"S2-2501861","release":"Rel-19","crspec":"23.228","crspecversion":"19.1.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1579.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2501012.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":true,"clauses_affected":"AF.3","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2501013","title":"KI#8: Download of Avatar ID List","source":"Nokia","contact":"Rainer Liebhart","contact-id":68375,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: An option for downloading Avatar ID List via bootstrap data channel is added. Related functionalities of HSS and DCSF are updated.","secretary_remarks":"Noted in e-mail session","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":13520,"status":"noted","reservation_date":"2025-01-14 16:59:47","uploaded":"2025-01-14 17:15:34","revisionof":"","revisedto":"","release":"Rel-19","crspec":"23.228","crspecversion":"19.1.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1580.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2501013.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":true,"clauses_affected":"AC.11.1, AC.11.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2501014","title":"KI#2: Update of procedures","source":"Nokia","contact":"Rainer Liebhart","contact-id":68375,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Parameter definition of the service Nimsas_ImsSessionManagement_Create is corrected. Editor's note in AG.1 is removed. Detailed call flows of adding application data channel(s) to an existing IMS session are provided for A2P, P2P, and P","secretary_remarks":"r08 agreedrevised in e-mail session to S2-2501099, merging S2-2500170, S2-2500621 and S2-2500967","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":13740,"status":"revised","reservation_date":"2025-01-14 16:59:48","uploaded":"2025-01-14 17:15:34","revisionof":"","revisedto":"S2-2501099","release":"Rel-19","crspec":"23.228","crspecversion":"19.1.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1581.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2501014.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":true,"clauses_affected":"AA.2.4.4.2, AG.1, AG.2.1, AG.2.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2501015","title":"KI#2: Update the IMS session management service of NEF","source":"Nokia","contact":"Rainer Liebhart","contact-id":68375,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The service Nnef_ImsSessionManagement_Create is updated.","secretary_remarks":"Proposed merged with S2-2500971 (postponed). Postponed","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":13760,"status":"postponed","reservation_date":"2025-01-14 16:59:49","uploaded":"2025-01-14 17:15:34","revisionof":"","revisedto":"","release":"Rel-19","crspec":"23.502","crspecversion":"19.2.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":5315.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2501015.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.2.6.40.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2501095","title":"Clarification on how DCSF fetch DC AS URL if not pre-configured","source":"China Mobile","contact":"Yi Jiang","contact-id":40863,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify the DCSF may derive DC AS URL from DCSF service specific data.","secretary_remarks":"Revision of S2-2500772r04. Approved","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":13490,"status":"agreed","reservation_date":"2025-01-25 09:53:51","uploaded":"2025-01-28 08:51:07","revisionof":"S2-2500772","revisedto":"","release":"Rel-19","crspec":"23.228","crspecversion":"19.1.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1563.0,"crrevision":1.0,"crcategory":"B","tsg_crp":"SP-250056","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2501095.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"AC.11.1, AC.11.3.1","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2501096","title":"Updates to support multiplexing multiple DC applications over single SCTP connection","source":"China Mobile","contact":"Yi Jiang","contact-id":40863,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Editor's notes are removed and texts are added to describe the solution described above.","secretary_remarks":"Revision of S2-2500624r01. Approved","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":13560,"status":"agreed","reservation_date":"2025-01-25 09:53:52","uploaded":"2025-01-28 08:51:07","revisionof":"S2-2500624","revisedto":"S2-2501733","release":"Rel-19","crspec":"23.228","crspecversion":"19.1.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1552.0,"crrevision":1.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2501096.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"AC.7.10.2.2, AC.7.10.3.1, AC.7.10.3.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2501097","title":"KI#2: Update to Network Capability Exposure Procedures","source":"Ericsson, NTT DOCOMO","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Correct th service operation Nimsas_SessionEventControl_Notify service Correct the Session delete procedue. The deletion request need not be reported to the DCSF. There is no reason why the DCSF would reject a session deletion request. Also unclear what will the DC AS do in case of a rejection. Editorial changes.","secretary_remarks":"Revision of S2-2500209r04. Approved","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":13640,"status":"agreed","reservation_date":"2025-01-25 09:53:53","uploaded":"2025-01-28 08:51:07","revisionof":"S2-2500209","revisedto":"S2-2501736, S2-2501952","release":"Rel-19","crspec":"23.228","crspecversion":"19.1.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1541.0,"crrevision":1.0,"crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2501097.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"AA.2.4.2.2, AG.2.3 ","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2501098","title":"Updates to Nimsas_ImsSessionManagement Service","source":"China Mobile, NTT DOCOMO","contact":"Yi Jiang","contact-id":40863,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: updates Nimsas_ImsSessionManagement service to align with the updated procedures in S2-2500621.","secretary_remarks":"Revision of S2-2500622r04, merging S2-2500210. Approved","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":13680,"status":"agreed","reservation_date":"2025-01-25 09:53:54","uploaded":"2025-01-28 08:51:07","revisionof":"S2-2500622","revisedto":"","release":"Rel-19","crspec":"23.228","crspecversion":"19.1.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1550.0,"crrevision":1.0,"crcategory":"B","tsg_crp":"SP-250056","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2501098.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"AA.2.4.4.1, AA.2.4.4.2, AA.2.4.4.3","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2501099","title":"KI#2: Update of procedures","source":"Nokia, NTT DOCOMO, Ericsson","contact":"Rainer Liebhart","contact-id":68375,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: New protocol stack added to AC.6. Editor's note in AG.1 is removed. Detailed call flows of adding application data channel(s) to an existing IMS session are provided for A2P, P2P, and P2A2P DC. The detailed IMS AS behaviour is also described. Editor's note is added that detailes for standalone IMS DC are FFS.","secretary_remarks":"Revision of S2-2501014r08, merging S2-2500170, S2-2500621 and S2-2500967. Endorsed","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":13750,"status":"endorsed","reservation_date":"2025-01-25 09:53:55","uploaded":"2025-01-28 08:51:07","revisionof":"S2-2501014","revisedto":"S2-2501862","release":"Rel-19","crspec":"23.228","crspecversion":"19.1.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1581.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2501099.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":true,"clauses_affected":"AC.6, AG.1, AG.2.1, AG.2.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2501100","title":"Clarification on PS Data Off status change reporting to DCSF","source":"Qualcomm Incorporated, Ericsson, Huawei, vivo, Nokia, ZTE","contact":"Kefeng Zhang","contact-id":103832,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The change clarifies that the IMS AS will notify the DCSF when the user changes the PS Data Off status during the period of IMS Session.","secretary_remarks":"Revision of S2-2500171r05, merging S2-2500626 and S2-2500637. Approved","agenda_item_sort_order":115,"ainumber":"19.2.2","ainame":"System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2)","tdoc_agenda_sort_order":13780,"status":"agreed","reservation_date":"2025-01-25 09:53:56","uploaded":"2025-01-28 08:51:07","revisionof":"S2-2500171","revisedto":"","release":"Rel-19","crspec":"23.228","crspecversion":"19.1.0","workitem":[{"winame":"NG_RTC_Ph2"}],"crnumber":1533.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-250056","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166AH-e_Electronic_2025-01\/Docs\/S2-2501100.zip","group":"S2","meeting":"S2-166-Ad Hoc-e","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0}]