[{"name":"S2-2103799","title":"Consistent handling of NF documentation","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: This CR updates the general text in clause 4.2.1, 4.2.2 and clause 6.1 to clarify the principles of including NFs and adding references to other specifications containing archtecture and network function descriptions.","secretary_remarks":"CC#2: Moved to AI 9.4. r06 agreed. Revised to S2-2105129, merging S2-2104766.","agenda_item_sort_order":75,"ainumber":"9.4","ainame":"Holder for left-overs from Deadline 1","tdoc_agenda_sort_order":24350,"status":"revised","reservation_date":"2021-05-06 21:17:50","uploaded":"2021-05-10 21:15:45","revisionof":"","revisedto":"S2-2105129","release":"Rel-17","crspec":23.501,"crspecversion":"17.0.0","workitem":[{"winame":"5GS_Ph1"},{"winame":" TEI17"}],"crnumber":2858.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_145E_Electronic_2021-05\/Docs\/S2-2103799.zip","group":"S2","meeting":"S2-145-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2104006","title":"Session Management Policy Data per PLMN for LBO case","source":"Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Provide SA WG2 specification consistency to ensure that, as already specified by SA WG2, in LBO the V-PCF can interact with the UDR of the VPLMN to get Session Management Policy Data valid for any user of a HPLMN; Such Session Management Policy Data at the VPLMN cannot be stored per subscriber, since the subscribers of the HPLMN are not managed by the VPLMN.","secretary_remarks":"CC#2: Moved to 9.4. Noted","agenda_item_sort_order":75,"ainumber":"9.4","ainame":"Holder for left-overs from Deadline 1","tdoc_agenda_sort_order":24320,"status":"noted","reservation_date":"2021-05-09 20:11:45","uploaded":"2021-05-10 15:55:59","revisionof":"","revisedto":"","release":"Rel-17","crspec":23.503,"crspecversion":"17.0.0","workitem":[{"winame":"SBIProtoc17"}],"crnumber":578.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_145E_Electronic_2021-05\/Docs\/S2-2104006.zip","group":"S2","meeting":"S2-145-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2104141","title":"Clarification on Session Management Policy Data per PLMN","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Some Notes are added to clarify that PDU Session policy control data and Remaining allowed Usage data are not available in V-UDR, and V-PCF uses locally configured policies according to the roaming agreement with the HPLMN operator.","secretary_remarks":"CC#2: Moved to 9.4. Noted","agenda_item_sort_order":75,"ainumber":"9.4","ainame":"Holder for left-overs from Deadline 1","tdoc_agenda_sort_order":24340,"status":"noted","reservation_date":"2021-05-10 07:09:17","uploaded":"2021-05-10 15:52:06","revisionof":"","revisedto":"","release":"Rel-17","crspec":23.502,"crspecversion":"17.0.0","workitem":[{"winame":"TEI17"},{"winame":" 5GS_Ph1"}],"crnumber":2777.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_145E_Electronic_2021-05\/Docs\/S2-2104141.zip","group":"S2","meeting":"S2-145-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2104224","title":"Session Management Policy Data per PLMN for LBO case","source":"Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Provide SA WG2 specification consistency to ensure that, as already specified by SA WG2, in LBO the V-PCF can interact with the UDR of the VPLMN to get Session Management Policy Data valid for any user of a HPLMN; Such Session Management Policy Data at the VPLMN cannot be stored per subscriber, since the subscribers of the HPLMN are not managed by the VPLMN.","secretary_remarks":"CC#2: Moved to 9.4. Noted","agenda_item_sort_order":75,"ainumber":"9.4","ainame":"Holder for left-overs from Deadline 1","tdoc_agenda_sort_order":24330,"status":"noted","reservation_date":"2021-05-10 09:30:30","uploaded":"2021-05-10 15:55:59","revisionof":"","revisedto":"","release":"Rel-17","crspec":23.502,"crspecversion":"17.0.0","workitem":[{"winame":"SBIProtoc17"}],"crnumber":2790.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_145E_Electronic_2021-05\/Docs\/S2-2104224.zip","group":"S2","meeting":"S2-145-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2104628","title":"Adding protocol stacks for trusted WLAN access for N5CW device","source":"Huawei, Hisilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add the control and user plane protocol stacks for trusted WLAN access for N5CW device.","secretary_remarks":"CC#2: Moved to 9.4. r13 agreed. Revised to S2-2105130.","agenda_item_sort_order":75,"ainumber":"9.4","ainame":"Holder for left-overs from Deadline 1","tdoc_agenda_sort_order":24400,"status":"revised","reservation_date":"2021-05-10 14:53:34","uploaded":"2021-05-10 16:14:44","revisionof":"","revisedto":"S2-2105130","release":"Rel-16","crspec":23.501,"crspecversion":"16.8.0","workitem":[{"winame":"5WWC"}],"crnumber":2957.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_145E_Electronic_2021-05\/Docs\/S2-2104628.zip","group":"S2","meeting":"S2-145-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2104681","title":"4G <-> 5GS mobility corrections to cope with areas of GERAN\/UTRAN-only coverage","source":"Vodafone, Qualcomm","contact":"Chris Pudney","contact-id":1122,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Existing TEI-17 for N7 support of GERAN\/UTRAN is assumed. In GERAN\/UTRAN, the UE and SMF+PGW-C exchange PDU Session ID and 5GS QoS parameters in the PCO during the PDP Context Activation procedure. The SGSN can use the 'N1 mode supported' indication sent by the UE to select a SMF+PGW-C to act as a GGSN, or, the operators may configure the SGSN\/APN's set of PGWs to only include the PGWs that are SMF+PGW-Cs. in signalling sent on the N26 interface, the MME and AMF send the TI of the default EPS bearer in the Bearer Context within the PDN Connection IE in the Forward Relocation Request and Context Response messages.","secretary_remarks":"CC#2: Moved to 9.4. CC#4: r37 + changes agreed. Revised to S2-2105154.","agenda_item_sort_order":75,"ainumber":"9.4","ainame":"Holder for left-overs from Deadline 1","tdoc_agenda_sort_order":24370,"status":"revised","reservation_date":"2021-05-10 17:05:12","uploaded":"2021-05-10 17:15:52","revisionof":"","revisedto":"S2-2105154","release":"Rel-17","crspec":23.501,"crspecversion":"17.0.0","workitem":[{"winame":"5GS_Ph1"},{"winame":" TEI17"}],"crnumber":2970.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_145E_Electronic_2021-05\/Docs\/S2-2104681.zip","group":"S2","meeting":"S2-145-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2104684","title":"4G <-> 5GS mobility corrections to cope with areas of GERAN\/UTRAN-only coverage","source":"Vodafone (Based on S2-2103059 from Nokia, Nokia Shanghai Bell, Ericsson)","contact":"Chris Pudney","contact-id":1122,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Existing TEI-17 for N7 support of GERAN\/UTRAN is assumed. In GERAN\/UTRAN, the UE and SMF+PGW-C exchange PDU Session ID and 5GS QoS parameters in the PCO during the PDP Context Activation procedure. in signalling sent on the N26 interface, the MME and AMF send the TI of the default EPS bearer in the Bearer Context within the PDN Connection IE in the Forward Relocation Request and Context Response messages. *********** For CR 2603: Solving interworking to 5GS with N26 issue due to UE's N1 mode capability disabling\/enabling At EPS to 5GS mobility UE consider as released the PDN connections that were established over EPS while the UE did not receive 5GS parameters from the network as answer to the PDN connection request. This covers the case where the UE did not provide a PDU Session ID to the network when establishing a PDN connection while the N1 mode is diasabled The MME does not transfer to 5GS a PDN connection that is not possible to be transferred to 5GS, e.g. PDN connection was established over EPC on a stand-alone PGW. (the UE has released it per item 1 above) The MME tries to transfer to 5GS a PDN connection that was established over EPC on a SMF+ PGW-c. what happens next is discussed below. At EPS to 5GS HO, the initial AMF invokes (step 4 of figure 4.11.1.2.2.2-1) the Nsmf_PDUSession_CreateSMContext service operation (UE EPS PDN Connection, initial AMF ID, data Forwarding information, Target ID) on the SMF identified by the SMF+PGW-C address and indicates HO Preparation Indication (to avoid switching the UP path). \u2026. The SMF finds the corresponding PDU Session based on EPS Bearer Context(s). IF the PDU Session Id was not received from the UE; the SMF rejects the AMF request and the PDN connection is not further transferred to 5GS (assumed to be released by the UE per item 1 above). In summary, the R17 behavior is the same than in R16 except that R17 specifications supports the UE option where the UE sends a PDU Session ID to the network when establishing a PDN connection while N1 mode is Disabled R17 specificiation supports MME initiating PDN disconnection with reactivation required when N1 mode is (re-)enabled if MME has selected standalone PGW.","secretary_remarks":"CC#2: Moved to 9.4. Postponed","agenda_item_sort_order":75,"ainumber":"9.4","ainame":"Holder for left-overs from Deadline 1","tdoc_agenda_sort_order":24390,"status":"postponed","reservation_date":"2021-05-10 17:10:00","uploaded":"2021-05-10 17:16:35","revisionof":"","revisedto":"S2-2105391","release":"Rel-17","crspec":23.502,"crspecversion":"17.0.0","workitem":[{"winame":"5GS_Ph1"},{"winame":" TEI17"}],"crnumber":2858.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_145E_Electronic_2021-05\/Docs\/S2-2104684.zip","group":"S2","meeting":"S2-145-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2105005","title":"Adding PDU session limitation and protocol stacks for trusted WLAN access for N5CW device","source":"Huawei, HiSilicon, Ericsson, Nokia, Nokia Shanghai Bell","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add the control and user plane protocol stacks for trusted WLAN access for N5CW device. In this release of the specification, Trusted WLAN Access for N5CW Device only supports IP PDU Session type","secretary_remarks":"Created at CC#2: Mirror CR to S2-2104628. Cat F ? r01 agreed. Revised to S2-2105131.","agenda_item_sort_order":75,"ainumber":"9.4","ainame":"Holder for left-overs from Deadline 1","tdoc_agenda_sort_order":24420,"status":"revised","reservation_date":"2021-05-25 06:17:36","uploaded":"2021-06-01 06:21:39","revisionof":"","revisedto":"S2-2105131","release":"Rel-17","crspec":23.501,"crspecversion":"17.0.0","workitem":[{"winame":"5WWC"},{"winame":" TEI17"}],"crnumber":2991.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_145E_Electronic_2021-05\/Docs\/S2-2105005.zip","group":"S2","meeting":"S2-145-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2105129","title":"Consistent handling of NF documentation","source":"Ericsson, Matrixx, Nokia, Nokia Shanghai Bell","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: This CR updates the general text in clause 4.2.1and clause 6.1 to clarify the principles of including NFs and adding references to other specifications containing archtecture and network function descriptions.","secretary_remarks":"Revision of S2-2103799r06, merging S2-2104766. Approved","agenda_item_sort_order":75,"ainumber":"9.4","ainame":"Holder for left-overs from Deadline 1","tdoc_agenda_sort_order":24360,"status":"agreed","reservation_date":"2021-06-01 06:07:13","uploaded":"2021-06-01 06:31:38","revisionof":"S2-2103799","revisedto":"","release":"Rel-17","crspec":23.501,"crspecversion":"17.0.0","workitem":[{"winame":"5GS_Ph1"},{"winame":" TEI17"}],"crnumber":2858.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-210341","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_145E_Electronic_2021-05\/Docs\/S2-2105129.zip","group":"S2","meeting":"S2-145-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2105130","title":"Limitation to PDU session type IP for N5CW","source":"Huawei, HiSilicon, Ericsson, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: In this release of the specification, Trusted WLAN Access for N5CW Device only supports IP PDU Session type","secretary_remarks":"Revision of S2-2104628r13. Approved","agenda_item_sort_order":75,"ainumber":"9.4","ainame":"Holder for left-overs from Deadline 1","tdoc_agenda_sort_order":24410,"status":"agreed","reservation_date":"2021-06-01 06:07:14","uploaded":"2021-06-01 06:31:38","revisionof":"S2-2104628","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.8.0","workitem":[{"winame":"5WWC"}],"crnumber":2957.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-210331","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_145E_Electronic_2021-05\/Docs\/S2-2105130.zip","group":"S2","meeting":"S2-145-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2105131","title":"Adding PDU session limitation and protocol stacks for trusted WLAN access for N5CW device","source":"Huawei, HiSilicon, Ericsson, Nokia, Nokia Shanghai Bell","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add the control and user plane protocol stacks for trusted WLAN access for N5CW device. In this release of the specification, Trusted WLAN Access for N5CW Device only supports IP PDU Session type","secretary_remarks":"Revision of S2-2105005r01. Approved","agenda_item_sort_order":75,"ainumber":"9.4","ainame":"Holder for left-overs from Deadline 1","tdoc_agenda_sort_order":24430,"status":"agreed","reservation_date":"2021-06-01 06:07:16","uploaded":"2021-06-01 06:31:38","revisionof":"S2-2105005","revisedto":"","release":"Rel-17","crspec":23.501,"crspecversion":"17.0.0","workitem":[{"winame":"5WWC"},{"winame":" TEI17"}],"crnumber":2991.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-210331","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_145E_Electronic_2021-05\/Docs\/S2-2105131.zip","group":"S2","meeting":"S2-145-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2105154","title":"4G <-> 5GS mobility corrections to cope with areas of GERAN\/UTRAN-only coverage","source":"Vodafone","contact":"Chris Pudney","contact-id":1122,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that UE may initiate PDN connection re-establishment in EPS to support the mobility to 5GS. in signalling sent on the N26 interface, the MME and AMF send the TI of the default EPS bearer in the Bearer Context within the PDN Conn","secretary_remarks":"Revision of S2-2104681r37 + changes. CC#4: Approved","agenda_item_sort_order":75,"ainumber":"9.4","ainame":"Holder for left-overs from Deadline 1","tdoc_agenda_sort_order":24380,"status":"agreed","reservation_date":"2021-06-01 06:07:36","uploaded":"2021-06-01 06:31:37","revisionof":"S2-2104681","revisedto":"","release":"Rel-17","crspec":23.501,"crspecversion":"17.0.0","workitem":[{"winame":"5GS_Ph1"},{"winame":" TEI17"}],"crnumber":2970.0,"crrevision":1.0,"crcategory":"B","tsg_crp":"SP-210341","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_145E_Electronic_2021-05\/Docs\/S2-2105154.zip","group":"S2","meeting":"S2-145-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]