[{"name":"S2-2303983","title":"LS from SA WG6: LS on Alignment of SA WG3 security aspects for Personal IoT Networks","source":"SA WG6","contact":"Michel Roy","contact-id":72161,"tdoctype":"LS in","for":"Information","abstract":"SA WG6 has concluded the Release-18 study TR 23.700-78 (FS_PINAPP) on an enablement layer for Personal IoT Networks and is now transposing the conclusions of the TR to normative text in the corresponding TS 23.542 (PINAPP). SA WG6 is delighted that SA WG3 has included the following security aspects as part of the FS_PIN_Sec study (SD-220525): SA WG6 also has agreed to study the application-level aspects for PIN. If there s potential security impacts in SA WG6 study, potential solutions shall be studied. SA WG6 would like to inform SA WG3 that TS 23.542 defines service procedures of the PIN enablement layer that require authorization and\/or authentication between various PIN participants (e.g., PINE, PEMC, PEGC, PIN server), in a manner similar to what SA WG3 has specified in TS 33.558 for the SA WG6 edge enablement layer (TS 23.558). SA WG6 provides one illustrative example, other examples are available in TS 23.542. In the PIN Join procedure, the PINE sends a PIN Join request to the PEGC that includes security credentials; upon receiving the request, the PEGC performs an authorization check on the provided PINE credentials before processing the request.","secretary_remarks":"Noted","agenda_item_sort_order":78,"ainumber":"9.3.2","ainame":"Personal IoT Networks (5G_PIN)","tdoc_agenda_sort_order":13170,"status":"noted","reservation_date":"2023-03-04 14:37:47","uploaded":"2023-04-04 11:14:06","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3","Cc":"SA WG2","lsoriginalls":"S6-230792","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2303983.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2304175","title":"PDU session sharing among PINs","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Specify the pre-condition for multiple PINs share one PDU session","secretary_remarks":"r13 agreed. Revised to S2-2306176, merging S2-2305297, S2-2304850 and S2-2305310","agenda_item_sort_order":78,"ainumber":"9.3.2","ainame":"Personal IoT Networks (5G_PIN)","tdoc_agenda_sort_order":13190,"status":"revised","reservation_date":"2023-05-04 19:14:57","uploaded":"2023-04-07 15:58:55","revisionof":"","revisedto":"S2-2306176","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"PIN"}],"crnumber":4224.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2304175.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.44.3.1, 5.44.3.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2304176","title":"PIN communication via different PEGCs","source":"Ericsson, Nokia, Nokia Shanghai Bell","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Specifiy the 5GC related handling of PINE communication via 5GC and different PEGCs","secretary_remarks":"","agenda_item_sort_order":78,"ainumber":"9.3.2","ainame":"Personal IoT Networks (5G_PIN)","tdoc_agenda_sort_order":13560,"status":"not treated","reservation_date":"2023-05-04 19:14:59","uploaded":"2023-04-07 15:58:55","revisionof":"","revisedto":"","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"PIN"}],"crnumber":4225.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2304176.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.44.3.1","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2304177","title":"PIN related subscription for PEGC and PIN realization in 5GC","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Introduce PIN service indication in SM subscription data for PEGC and specify the realization of PIN in 5GC based on external and internal group ID during parameters provision in 5GC","secretary_remarks":"Postponed","agenda_item_sort_order":78,"ainumber":"9.3.2","ainame":"Personal IoT Networks (5G_PIN)","tdoc_agenda_sort_order":13390,"status":"postponed","reservation_date":"2023-05-04 19:15:00","uploaded":"2023-04-07 15:58:55","revisionof":"","revisedto":"S2-2306651","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"PIN"}],"crnumber":4226.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2304177.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.44.1, 5.44.3.1","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2304178","title":"PDU session control related PIN service support","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Introduce the enhancement of session establishment procedure for PIN service","secretary_remarks":"Revision of S2-2302316 from S2#155. Postponed","agenda_item_sort_order":78,"ainumber":"9.3.2","ainame":"Personal IoT Networks (5G_PIN)","tdoc_agenda_sort_order":13490,"status":"postponed","reservation_date":"2023-05-04 19:15:01","uploaded":"2023-04-07 15:58:55","revisionof":"S2-2302316","revisedto":"S2-2306652","release":"Rel-18","crspec":23.502,"crspecversion":"18.1.0","workitem":[{"winame":"PIN"}],"crnumber":3881.0,"crrevision":1.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2304178.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":true,"clauses_affected":"4.3.2.2.1, 5.2.3.3.1","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2304359","title":"Clarifying SMF behaviour for non-3GPP delay budget","source":"Qualcomm, Nokia, Nokia Shanghai Bell, Ericsson","contact":"Sebastian Speicher","contact-id":94901,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clause 5.44.3.4: Clarify that, if allowed, SMF shall increase the dynamic CN PDB for the related GBR QoS flow by the requested non-3GPP delay budget and signal the updated CN PDB to NG-RAN. Update EN to reflect that how to determine that SMF is allowed to appyl non-3GPP delay budget is FFS. Clause 6.2.2: clarify non-3GPP delay budget support by SMF","secretary_remarks":"r02 agreed. Revised to S2-2306177.","agenda_item_sort_order":78,"ainumber":"9.3.2","ainame":"Personal IoT Networks (5G_PIN)","tdoc_agenda_sort_order":13250,"status":"revised","reservation_date":"2023-06-04 11:16:12","uploaded":"2023-04-06 18:04:30","revisionof":"","revisedto":"S2-2306177","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"PIN"}],"crnumber":4284.0,"crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2304359.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2304360","title":"Clarifying SMF behaviour for non-3GPP delay budget and non-3GPP QoS Assistance Information","source":"Qualcomm","contact":"Sebastian Speicher","contact-id":94901,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: This CR clarifies that, if allowed, SMF increases the dynamic CN PDB for the related GBR QoS flow by the requested non-3GPP delay budget and signal the updated CN PDB to NG-RAN. The SMF sends non-3GPP QoS Asisstance Information in N1 SM container in the response of PDU Session Establishment.","secretary_remarks":"","agenda_item_sort_order":78,"ainumber":"9.3.2","ainame":"Personal IoT Networks (5G_PIN)","tdoc_agenda_sort_order":13650,"status":"not treated","reservation_date":"2023-06-04 11:21:57","uploaded":"2023-04-06 18:04:30","revisionof":"","revisedto":"","release":"Rel-18","crspec":23.502,"crspecversion":"18.1.1","workitem":[{"winame":"PIN"}],"crnumber":3993.0,"crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2304360.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2304373","title":"PIN identifiers","source":"Nokia, Nokia Shanghai Bell","contact":"Pallab Gupta","contact-id":87959,"tdoctype":"CR","for":"Approval","abstract":"It is proposed that a PIN is identified externally by a PIN ID. It is also proposed that External Group ID and Internal Group ID is used to identify and manage the PEGC UEs that are part of a PIN.","secretary_remarks":"r08 agreed. Revised to S2-2306178.","agenda_item_sort_order":78,"ainumber":"9.3.2","ainame":"Personal IoT Networks (5G_PIN)","tdoc_agenda_sort_order":13270,"status":"revised","reservation_date":"2023-06-04 11:53:16","uploaded":"2023-04-06 17:48:09","revisionof":"","revisedto":"S2-2306178","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"PIN"}],"crnumber":4287.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2304373.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"new 5.44.x","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2304487","title":"Solve the EN about handling of the PEMC in 5GC in relation with PIN","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"This CR aims to solve the EN about handling of the PEMC in 5GC in relation with PIN","secretary_remarks":"Approved","agenda_item_sort_order":78,"ainumber":"9.3.2","ainame":"Personal IoT Networks (5G_PIN)","tdoc_agenda_sort_order":13290,"status":"agreed","reservation_date":"2023-06-04 15:53:33","uploaded":"2023-04-07 13:59:31","revisionof":"","revisedto":"S2-2306717, S2-2307338","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"PIN"}],"crnumber":4326.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-230484","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2304487.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.44.3, 5.44.3.1","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2304488","title":"Solve the EN about PIN deletion, activation and deactivation","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"This CR aims to solve the EN about PIN deletion, activation and deactivation","secretary_remarks":"r01 agreed. Revised to S2-2306179.","agenda_item_sort_order":78,"ainumber":"9.3.2","ainame":"Personal IoT Networks (5G_PIN)","tdoc_agenda_sort_order":13340,"status":"revised","reservation_date":"2023-06-04 15:53:34","uploaded":"2023-04-07 13:59:31","revisionof":"","revisedto":"S2-2306179","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"PIN"}],"crnumber":4327.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2304488.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.44, 5.44.1, 5.44.3.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2304489","title":"Solve the EN about PINs sharing a PDU session","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"This CR aims to solve the EN about PINs sharing a PDU session","secretary_remarks":"Noted","agenda_item_sort_order":78,"ainumber":"9.3.2","ainame":"Personal IoT Networks (5G_PIN)","tdoc_agenda_sort_order":13210,"status":"noted","reservation_date":"2023-06-04 15:53:35","uploaded":"2023-04-07 13:59:31","revisionof":"","revisedto":"","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"PIN"}],"crnumber":4328.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2304489.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.44.3.1","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2304490","title":"Update PIN policy delivery for PIN","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"This CR aims to clarify the PIN ID in the URSP to keep aligned with the terminology used in PIN","secretary_remarks":"Noted","agenda_item_sort_order":78,"ainumber":"9.3.2","ainame":"Personal IoT Networks (5G_PIN)","tdoc_agenda_sort_order":13370,"status":"noted","reservation_date":"2023-06-04 15:53:35","uploaded":"2023-04-07 13:59:31","revisionof":"","revisedto":"","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"PIN"}],"crnumber":4329.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2304490.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.44.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2304547","title":"Support for local routing of PIN traffic","source":"Apple","contact":"Sudeep M Vamanan","contact-id":87305,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: This CR proposes the following: i). PIN that requires local routing of traffic has a dedicated PDU Session and removes the EN ii). URSP rules guide the PIN traffic to the dedicated PDU Session iii). SMF may preferentially select the same UPF for PDU Sessions from PEGCs that require local routing iv). The N4 rule attribute Network Instance is used in addition to UPF internal interface for local routing and it is set to the value of PIN internal identifier.","secretary_remarks":"Merged into S2-2306180","agenda_item_sort_order":78,"ainumber":"9.3.2","ainame":"Personal IoT Networks (5G_PIN)","tdoc_agenda_sort_order":13310,"status":"merged","reservation_date":"2023-06-04 17:34:09","uploaded":"2023-04-07 18:01:03","revisionof":"","revisedto":"","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"PIN"}],"crnumber":4340.0,"crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2304547.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2304643","title":"Mapping relation of PIN with PDU Session for PEGC","source":"Qualcomm Incorporated","contact":"Kefeng ZHANG","contact-id":91388,"tdoctype":"discussion","for":"Agreement","abstract":"This paper addresses the questions whether PINs can share a PDU session and whether one PIN can be served by multiple PDU sessions, and proposes a way forward.","secretary_remarks":"Noted","agenda_item_sort_order":78,"ainumber":"9.3.2","ainame":"Personal IoT Networks (5G_PIN)","tdoc_agenda_sort_order":13100,"status":"noted","reservation_date":"2023-07-04 03:20:44","uploaded":"2023-04-07 03:43:46","revisionof":"","revisedto":"","release":"Rel-18","crspec":23.501,"crspecversion":"","workitem":[{"winame":"PIN"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2304643.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2304645","title":"Clarification on the mapping between PIN and PDU session","source":"Qualcomm Incorporated, Nokia, Nokia Shanghai Bell","contact":"Kefeng ZHANG","contact-id":91388,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that in the PEGC one PDU session can be shared by multiple PINs, and one PIN can be routed to only one PDU session.","secretary_remarks":"","agenda_item_sort_order":78,"ainumber":"9.3.2","ainame":"Personal IoT Networks (5G_PIN)","tdoc_agenda_sort_order":13580,"status":"not treated","reservation_date":"2023-07-04 03:25:26","uploaded":"2023-04-07 03:43:46","revisionof":"","revisedto":"","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"PIN"}],"crnumber":4368.0,"crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2304645.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2304840","title":"Clarification on URSP for PIN","source":"LG Electronics","contact":"Laeyoung Kim","contact-id":40613,"tdoctype":"CR","for":"Approval","abstract":"Clarification on URSP for PIN","secretary_remarks":"Revised at S2#157 in S2-2306363","agenda_item_sort_order":78,"ainumber":"9.3.2","ainame":"Personal IoT Networks (5G_PIN)","tdoc_agenda_sort_order":13680,"status":"not treated","reservation_date":"2023-07-04 08:29:49","uploaded":"2023-04-07 09:54:17","revisionof":"","revisedto":"S2-2306363","release":"Rel-18","crspec":23.503,"crspecversion":"18.1.0","workitem":[{"winame":"PIN"}],"crnumber":1004.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2304840.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":true,"clauses_affected":"6.1.2.2.1","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2304850","title":"Clarification on PDU Session for PIN","source":"LG Electronics","contact":"Laeyoung Kim","contact-id":40613,"tdoctype":"CR","for":"Approval","abstract":"Clarification on PDU Session for PIN","secretary_remarks":"Merged into S2-2306176","agenda_item_sort_order":78,"ainumber":"9.3.2","ainame":"Personal IoT Networks (5G_PIN)","tdoc_agenda_sort_order":13230,"status":"merged","reservation_date":"2023-07-04 08:31:30","uploaded":"2023-04-07 11:36:36","revisionof":"","revisedto":"","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"PIN"}],"crnumber":4417.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2304850.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.44.3.1","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2304852","title":"PEGC operation related to PDU Session for PIN","source":"LG Electronics","contact":"Laeyoung Kim","contact-id":40613,"tdoctype":"CR","for":"Approval","abstract":"PEGC operation related to PDU Session for PIN","secretary_remarks":"Noted","agenda_item_sort_order":78,"ainumber":"9.3.2","ainame":"Personal IoT Networks (5G_PIN)","tdoc_agenda_sort_order":13400,"status":"noted","reservation_date":"2023-07-04 08:33:48","uploaded":"2023-04-07 15:18:17","revisionof":"","revisedto":"","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"PIN"}],"crnumber":4419.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2304852.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.44.3.1","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2304928","title":"Discussion on support of local switching","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"discussion","for":"Agreement","abstract":"This paper discusses the EN in the TR regarding whether PINs can share a PDU session and how to support local switching, and proposes way forward.","secretary_remarks":"Noted","agenda_item_sort_order":78,"ainumber":"9.3.2","ainame":"Personal IoT Networks (5G_PIN)","tdoc_agenda_sort_order":13110,"status":"noted","reservation_date":"2023-07-04 09:28:16","uploaded":"2023-04-07 19:42:25","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"PIN"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2304928.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2304929","title":"Traffic routing within PIN","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Local switching is described for the PINEs communication within the PIN via different PEGCs connected via different PDU sessions to the same UPF.","secretary_remarks":"Postponed","agenda_item_sort_order":78,"ainumber":"9.3.2","ainame":"Personal IoT Networks (5G_PIN)","tdoc_agenda_sort_order":13320,"status":"postponed","reservation_date":"2023-07-04 09:28:16","uploaded":"2023-04-07 19:42:25","revisionof":"","revisedto":"","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"PIN"}],"crnumber":4438.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2304929.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.44.3.1","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2304930","title":"URSP extension for PIN","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Add the Internal Group ID to the URSP","secretary_remarks":"","agenda_item_sort_order":78,"ainumber":"9.3.2","ainame":"Personal IoT Networks (5G_PIN)","tdoc_agenda_sort_order":13690,"status":"not treated","reservation_date":"2023-07-04 09:28:17","uploaded":"2023-04-07 19:42:25","revisionof":"","revisedto":"","release":"Rel-18","crspec":23.503,"crspecversion":"18.1.0","workitem":[{"winame":"PIN"}],"crnumber":1011.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2304930.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":" 6.6.2.1, Annex A ","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2304993","title":"Way forward proposal for PIN","source":"vivo","contact":"Zhenhua Xie","contact-id":83004,"tdoctype":"discussion","for":"Information","abstract":"","secretary_remarks":"Noted","agenda_item_sort_order":78,"ainumber":"9.3.2","ainame":"Personal IoT Networks (5G_PIN)","tdoc_agenda_sort_order":13120,"status":"noted","reservation_date":"2023-07-04 10:39:45","uploaded":"2023-04-07 11:04:42","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2304993.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2304994","title":"PIN identifier","source":"vivo","contact":"Zhenhua Xie","contact-id":83004,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: PIN is identified by a PIN ID, and 5GC assigns Internal Group ID for a PIN ID","secretary_remarks":"","agenda_item_sort_order":78,"ainumber":"9.3.2","ainame":"Personal IoT Networks (5G_PIN)","tdoc_agenda_sort_order":13620,"status":"not treated","reservation_date":"2023-07-04 10:39:45","uploaded":"2023-04-07 11:04:42","revisionof":"","revisedto":"","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"PIN"}],"crnumber":4448.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2304994.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.44.X (new)","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2304995","title":"Remove EN for PIN activation\/deactivation","source":"vivo","contact":"Zhenhua Xie","contact-id":83004,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Remove EN for PIN activation\/deactivation","secretary_remarks":"","agenda_item_sort_order":78,"ainumber":"9.3.2","ainame":"Personal IoT Networks (5G_PIN)","tdoc_agenda_sort_order":13640,"status":"not treated","reservation_date":"2023-07-04 10:39:46","uploaded":"2023-04-07 11:04:42","revisionof":"","revisedto":"","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"PIN"}],"crnumber":4449.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2304995.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.44.3.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2304996","title":"Support QoS management for PIN","source":"vivo","contact":"Zhenhua Xie","contact-id":83004,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add description to reuse group QoS configuration and QoS configuration for traffic between group UEs for PIN","secretary_remarks":"r06 agreed. Revised to S2-2306180, merging S2-2304998 and S2-2304547.","agenda_item_sort_order":78,"ainumber":"9.3.2","ainame":"Personal IoT Networks (5G_PIN)","tdoc_agenda_sort_order":13410,"status":"revised","reservation_date":"2023-07-04 10:39:46","uploaded":"2023-04-07 11:04:42","revisionof":"","revisedto":"S2-2306180","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"PIN"}],"crnumber":4450.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2304996.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.44.3.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2304997","title":"UE 5GSM Core Network Capability handling for PIN","source":"vivo","contact":"Zhenhua Xie","contact-id":83004,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add Traffic manangement for PIN in UE 5GSM Core Network Capability","secretary_remarks":"Noted","agenda_item_sort_order":78,"ainumber":"9.3.2","ainame":"Personal IoT Networks (5G_PIN)","tdoc_agenda_sort_order":13430,"status":"noted","reservation_date":"2023-07-04 10:39:47","uploaded":"2023-04-07 11:04:42","revisionof":"","revisedto":"","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"PIN"}],"crnumber":4451.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2304997.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.4.4b, 5.44.3.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2304998","title":"UP management for PIN","source":"vivo","contact":"Zhenhua Xie","contact-id":83004,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add UP management for supporting PIN communication","secretary_remarks":"Merged into S2-2306180","agenda_item_sort_order":78,"ainumber":"9.3.2","ainame":"Personal IoT Networks (5G_PIN)","tdoc_agenda_sort_order":13300,"status":"merged","reservation_date":"2023-07-04 10:39:48","uploaded":"2023-04-07 11:04:42","revisionof":"","revisedto":"","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"PIN"}],"crnumber":4452.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2304998.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.8.2.X (New), 5.8.2.X.1 (new), 5.8.2.X.2 (new), 5.8.2.X.3 (new), 5.8.2.X.4 (new), 5.44.3.1","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2304999","title":"Update UE policy delivery for PIN","source":"vivo","contact":"Zhenhua Xie","contact-id":83004,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 5GS is able to provide URSP rule without PIN ID to PEGC for PIN management purpose","secretary_remarks":"CC#4: Postponed","agenda_item_sort_order":78,"ainumber":"9.3.2","ainame":"Personal IoT Networks (5G_PIN)","tdoc_agenda_sort_order":13380,"status":"postponed","reservation_date":"2023-07-04 10:39:49","uploaded":"2023-04-07 11:04:42","revisionof":"","revisedto":"","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"PIN"}],"crnumber":4453.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2304999.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.44.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2305000","title":"Way for handling of one PIN multiple PDU Sessions","source":"vivo","contact":"Zhenhua Xie","contact-id":83004,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Remove the corresponding EN and the text related to the EN","secretary_remarks":"","agenda_item_sort_order":78,"ainumber":"9.3.2","ainame":"Personal IoT Networks (5G_PIN)","tdoc_agenda_sort_order":13590,"status":"not treated","reservation_date":"2023-07-04 10:39:50","uploaded":"2023-04-07 11:04:42","revisionof":"","revisedto":"","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"PIN"}],"crnumber":4454.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2305000.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.44.3.1","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2305001","title":"Way for multiple PINs share one PDU Session","source":"vivo","contact":"Zhenhua Xie","contact-id":83004,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Remove the corresponding EN","secretary_remarks":"","agenda_item_sort_order":78,"ainumber":"9.3.2","ainame":"Personal IoT Networks (5G_PIN)","tdoc_agenda_sort_order":13570,"status":"not treated","reservation_date":"2023-07-04 10:39:51","uploaded":"2023-04-07 11:04:42","revisionof":"","revisedto":"","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"PIN"}],"crnumber":4455.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2305001.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.44.3.1","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2305002","title":"PDU Session Release for PIN","source":"vivo","contact":"Zhenhua Xie","contact-id":83004,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Releases N19 tunnel when PIN does not exist anymore.","secretary_remarks":"CR Cover sheet error!","agenda_item_sort_order":78,"ainumber":"9.3.2","ainame":"Personal IoT Networks (5G_PIN)","tdoc_agenda_sort_order":13660,"status":"not treated","reservation_date":"2023-07-04 10:39:52","uploaded":"2023-04-07 11:04:42","revisionof":"","revisedto":"","release":"Rel-18","crspec":23.502,"crspecversion":"18.1.1","workitem":[{"winame":"PIN"}],"crnumber":4091.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2305002.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2305003","title":"PIN parameters configuration procedure","source":"vivo","contact":"Zhenhua Xie","contact-id":83004,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add procedure for PIN parameters configuration, and modify service operations accordingly.","secretary_remarks":"CR Cover sheet error! Postponed","agenda_item_sort_order":78,"ainumber":"9.3.2","ainame":"Personal IoT Networks (5G_PIN)","tdoc_agenda_sort_order":13530,"status":"postponed","reservation_date":"2023-07-04 10:39:53","uploaded":"2023-04-07 11:04:42","revisionof":"","revisedto":"","release":"Rel-18","crspec":23.502,"crspecversion":"18.1.1","workitem":[{"winame":"PIN"}],"crnumber":4092.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2305003.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2305004","title":"Subscription data modification for PIN","source":"vivo","contact":"Zhenhua Xie","contact-id":83004,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add subscription data for PIN","secretary_remarks":"CR Cover sheet error! Postponed","agenda_item_sort_order":78,"ainumber":"9.3.2","ainame":"Personal IoT Networks (5G_PIN)","tdoc_agenda_sort_order":13500,"status":"postponed","reservation_date":"2023-07-04 10:39:53","uploaded":"2023-04-07 11:04:42","revisionof":"","revisedto":"","release":"Rel-18","crspec":23.502,"crspecversion":"18.1.1","workitem":[{"winame":"PIN"}],"crnumber":4093.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2305004.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2305005","title":"UE Policy Association update for PIN","source":"vivo","contact":"Zhenhua Xie","contact-id":83004,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Modify UE poilcy association proceudres for PIN","secretary_remarks":"CR Cover sheet error! Noted","agenda_item_sort_order":78,"ainumber":"9.3.2","ainame":"Personal IoT Networks (5G_PIN)","tdoc_agenda_sort_order":13520,"status":"noted","reservation_date":"2023-07-04 10:39:54","uploaded":"2023-04-07 11:04:42","revisionof":"","revisedto":"","release":"Rel-18","crspec":23.502,"crspecversion":"18.1.1","workitem":[{"winame":"PIN"}],"crnumber":4094.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2305005.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2305100","title":"Definition of services for PIN support","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"This CR defined the new NEF service for exposing PIN support and updated all related services","secretary_remarks":"Postponed","agenda_item_sort_order":78,"ainumber":"9.3.2","ainame":"Personal IoT Networks (5G_PIN)","tdoc_agenda_sort_order":13510,"status":"postponed","reservation_date":"2023-07-04 13:17:06","uploaded":"2023-04-07 14:33:41","revisionof":"","revisedto":"","release":"Rel-18","crspec":23.502,"crspecversion":"18.1.0","workitem":[{"winame":"PIN"}],"crnumber":4109.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2305100.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"4.15.6.x (new), 4.15.6.x.1 (new), 4.15.6.x.2 (new), 5.2.3.3.1, 5.2.6.1, 5.3.2.6.2, 5.3.2.6.3, 5.6.2.6.4, 5.2.6.x (new)","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2305131","title":"PIN communication definition","source":"Huawei, Hisilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Revision of definitions for PIN communication and addition of missing definitions","secretary_remarks":"CR Cover sheet error! r06 agreed. Revised to S2-2306181.","agenda_item_sort_order":78,"ainumber":"9.3.2","ainame":"Personal IoT Networks (5G_PIN)","tdoc_agenda_sort_order":13440,"status":"revised","reservation_date":"2023-07-04 14:13:52","uploaded":"2023-04-07 14:33:41","revisionof":"","revisedto":"S2-2306181","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"PIN"}],"crnumber":4492.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2305131.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2305160","title":"[DRAFT] LS on Information about PEGC not being able to serve PIN","source":"LG Electronics","contact":"Laeyoung Kim","contact-id":40613,"tdoctype":"LS out","for":"Approval","abstract":"[DRAFT] LS on Information about PEGC not being able to serve PIN","secretary_remarks":"Noted","agenda_item_sort_order":78,"ainumber":"9.3.2","ainame":"Personal IoT Networks (5G_PIN)","tdoc_agenda_sort_order":13180,"status":"noted","reservation_date":"2023-07-04 15:08:02","uploaded":"2023-04-07 15:18:17","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"PIN"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG6","Cc":"CT WG1","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2305160.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2305241","title":"Editorial change for the PIN","source":"xiaomi","contact":"Jianning(Carry) LIU","contact-id":88587,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The three changes above","secretary_remarks":"r02 agreed. Revised to S2-2306182.","agenda_item_sort_order":78,"ainumber":"9.3.2","ainame":"Personal IoT Networks (5G_PIN)","tdoc_agenda_sort_order":13460,"status":"revised","reservation_date":"2023-07-04 17:34:20","uploaded":"2023-04-07 17:58:01","revisionof":"","revisedto":"S2-2306182","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"PIN"}],"crnumber":4535.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2305241.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":false,"clauses_affected":"3.1; 5.44.1; 5.44.3.1;","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2305242","title":"Remove the EN for Non-3GPP delay budget","source":"xiaomi","contact":"Jianning(Carry) LIU","contact-id":88587,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Remove the EN above as it is resolved by existing normative text Add clarification for scenarios or conditions when applying the non-3GPP delay budget Remove the NOTE above, by adding new NOTE to state when the non-3GPP delay budget between PINE and the PEGC is not stable, the PEGC will not provide it to 5GC.","secretary_remarks":"","agenda_item_sort_order":78,"ainumber":"9.3.2","ainame":"Personal IoT Networks (5G_PIN)","tdoc_agenda_sort_order":13610,"status":"not treated","reservation_date":"2023-07-04 17:34:20","uploaded":"2023-04-07 17:58:01","revisionof":"","revisedto":"","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"PIN"}],"crnumber":4536.0,"crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2305242.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.44.3.4","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2305243","title":"Remove the EN for handling the PEMC and PINE (UE) in PIN","source":"Xiaomi","contact":"Jianning(Carry) LIU","contact-id":88587,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding text to support for the UE acting as PEMC or PINE cases in general description Update the UE policy delivery for PIN to support the case of UE acting as PEMC or PINE. With a new EN when the URSP includes the PIN ID or other necessary elements is FFS Add description for the UE acting as PEMC\/PINE to establish PDU session for the PIN traffic, or use the PDU session established by PEGC, and remove the EN. Additional PIN traffic type for the UE acting as PEMC\/PINE","secretary_remarks":"Noted","agenda_item_sort_order":78,"ainumber":"9.3.2","ainame":"Personal IoT Networks (5G_PIN)","tdoc_agenda_sort_order":13360,"status":"noted","reservation_date":"2023-07-04 17:34:21","uploaded":"2023-04-07 17:58:01","revisionof":"","revisedto":"","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"PIN"}],"crnumber":4537.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2305243.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.44.1; 5.44.2; 5.44.3.1; 5.44.3.2;","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2305244","title":"PIN capability exchange between UE and 5GC","source":"xiaomi","contact":"Jianning(Carry) LIU","contact-id":88587,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: To add PIN support indication in the registration request from UE To add PIN supported indication in the registration accept from AMF","secretary_remarks":"Postponed","agenda_item_sort_order":78,"ainumber":"9.3.2","ainame":"Personal IoT Networks (5G_PIN)","tdoc_agenda_sort_order":13540,"status":"postponed","reservation_date":"2023-07-04 17:34:22","uploaded":"2023-04-07 17:58:01","revisionof":"","revisedto":"S2-2307336","release":"Rel-18","crspec":23.502,"crspecversion":"18.1.1","workitem":[{"winame":"PIN"}],"crnumber":4134.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2305244.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":true,"clauses_affected":"4.2.2.2.2;","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2305245","title":"PIN policy delivery requested by UE","source":"Xiaomi","contact":"Jianning(Carry) LIU","contact-id":88587,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: adding PIN policy request indication in the UE policy container during registration request","secretary_remarks":"CR Cover sheet error!. Confirm Specification Number - CR states 23.501! Postponed","agenda_item_sort_order":78,"ainumber":"9.3.2","ainame":"Personal IoT Networks (5G_PIN)","tdoc_agenda_sort_order":13550,"status":"postponed","reservation_date":"2023-07-04 17:34:23","uploaded":"2023-04-07 17:58:01","revisionof":"","revisedto":"S2-2307342","release":"Rel-18","crspec":23.502,"crspecversion":"18.1.1","workitem":[{"winame":"PIN"}],"crnumber":4135.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2305245.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2305246","title":"PIN identifier","source":"Xiaomi","contact":"Jianning(Carry) LIU","contact-id":88587,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add new text for identifiers for External PIN ID, and Internal PIN ID","secretary_remarks":"","agenda_item_sort_order":78,"ainumber":"9.3.2","ainame":"Personal IoT Networks (5G_PIN)","tdoc_agenda_sort_order":13630,"status":"not treated","reservation_date":"2023-07-04 17:34:26","uploaded":"2023-04-07 17:58:01","revisionof":"","revisedto":"","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"PIN"}],"crnumber":4538.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2305246.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"New 5.44.x;","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2305293","title":"Way forward proposal for Session Management for PIN","source":"Google","contact":"Ellen C. Liao","contact-id":96126,"tdoctype":"discussion","for":"Agreement","abstract":"This paper proposes way forwards for the following Editor s Notes in TS23.501 clause 5.44.3.","secretary_remarks":"Noted","agenda_item_sort_order":78,"ainumber":"9.3.2","ainame":"Personal IoT Networks (5G_PIN)","tdoc_agenda_sort_order":13130,"status":"noted","reservation_date":"2023-07-04 19:21:00","uploaded":"2023-04-07 21:58:52","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"PIN"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2305293.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2305296","title":"Clarification on PEMC role in a PIN","source":"Google","contact":"Ellen C. Liao","contact-id":96126,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is proposed to remove these two Editor s note and clarify the followings: PEMC functionality of PIN management depends on PIN application implementation and is out of scope of this specification. Clarify the AF for FEMC role to add if AF deployed for PEMC PEMC or AF if deployed for PEMC manages PIN and PINEs using user plane traffic, including PIN traffic or non-PIN traffic, which is on top of available connections.","secretary_remarks":"Covered by S2-2304487","agenda_item_sort_order":78,"ainumber":"9.3.2","ainame":"Personal IoT Networks (5G_PIN)","tdoc_agenda_sort_order":13330,"status":"noted","reservation_date":"2023-07-04 19:25:04","uploaded":"2023-04-07 21:58:52","revisionof":"","revisedto":"","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"PIN"}],"crnumber":4543.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2305296.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2305297","title":"Clarification on Session Management Associations with multiple PINs","source":"Google","contact":"Ellen C. Liao","contact-id":96126,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is proposed to address the following aspects for clarification and resolving Editor s notes: For case1: the PEGC shall indicate PDU session ID with PIN indication or PIN ID in the PDU session Establishment request to differetiate PDU sessions with same DNN and S-NSSAI for different PINs. For case 1-3: Based on operator s policy, URSP rules needs to enhance as follows: one PEGC serving more than one PIN may use different PDU Sessions with same DNN and S-NSSAI for different PIN. The RSD for PIN needs enhancement to support this case. one PEGC serving more than one PIN may have one PDU Session for each PIN or share one PDU Session for PIN service. The TD for PIN needs enhancement to support this case, e.g. allow more than one PIN ID in a URSP rule. one PEGC serving one PIN may use different PDU Sessions for different groups of PINEs. The TD for PIN needs new component to support this case. For PDU Session Establishment\/Modification request procedure for PIN service, the SMF may requests PIN subscription of the PEGC from the UDM to perform IP address allocation for a PIN or a group of PINEs of a PIN and to configure UPF with PDR including packet filter set that indicates destination PIN, e.g. using External Group Identifier or IP address group, or a destination group of PINEs within the same PIN. For PINE to PINE indirect communication handling, the PEGC shall base on IP header information to route PIN traffics to the destination PIN (in case of shared PDU session) or PIN subgroup (in case of multiple PDU sessions per PIN). Ultimately, the PEGC shall forward PIN traffic to destination PINEs (including UEs or non-3GPP devices) based on the IP address information of destination PINE, e.g. MAC address mapped from virtual interface ID in IPv6 header. Enhance SMF, UPF, UDM for PIN service","secretary_remarks":"Merged into S2-2306176","agenda_item_sort_order":78,"ainumber":"9.3.2","ainame":"Personal IoT Networks (5G_PIN)","tdoc_agenda_sort_order":13220,"status":"merged","reservation_date":"2023-07-04 19:27:35","uploaded":"2023-04-07 21:58:52","revisionof":"","revisedto":"","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"PIN"}],"crnumber":4544.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2305297.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2305301","title":"Clarification on Session Management Procedures for multiple PINs","source":"Google","contact":"Ellen C. Liao","contact-id":96126,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is proposed to consider one of the following option for clarification: Option1: using PDU Session ID to differentiate PDU Sessions with the same DNN and S-NSSAI. NOTE: The corresponding enhancement in TS23.503 includes: URSP rule for PIN needs to enhance RSD with new component: PDU Session ID. Option2: using PIN ID to differentiate PDU Sessions with the same DNN and S-NSSAI. PDU Session Establishment\/Modification request message, the UE needs to include PIN ID as one of PDU Session attributes, e.g. PDU Session ID, DNN, S-NSSAI, SSC mode, etc. NOTE: The corresponding enhancement in TS23.503 includes: URSP rule for PIN needs to enhance RSD with new component: PIN ID.","secretary_remarks":"","agenda_item_sort_order":78,"ainumber":"9.3.2","ainame":"Personal IoT Networks (5G_PIN)","tdoc_agenda_sort_order":13670,"status":"not treated","reservation_date":"2023-07-04 19:31:07","uploaded":"2023-04-07 21:58:52","revisionof":"","revisedto":"","release":"Rel-18","crspec":23.502,"crspecversion":"18.1.1","workitem":[{"winame":"PIN"}],"crnumber":4142.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2305301.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2305302","title":"Clarification on URSP rules for PIN and PDU Session association","source":"Google","contact":"Ellen C. Liao","contact-id":96126,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is proposed to consider one of the following option for clarification: Option1: URSP rule for PIN needs to enhance RSD with new component: PDU Session ID if using PDU Session ID to differentiate PDU Sessions with the same DNN and S-NSSAI. Option2: URSP rule for PIN needs to enhance RSD with new component: PIN ID if using PIN ID to differentiate PDU Sessions with the same DNN and S-NSSAI. In this case, the UE needs to include PIN ID as one of PDU Session attributes, e.g. PDU Session ID, DNN, S-NSSAI, SSC mode, etc.","secretary_remarks":"","agenda_item_sort_order":78,"ainumber":"9.3.2","ainame":"Personal IoT Networks (5G_PIN)","tdoc_agenda_sort_order":13700,"status":"not treated","reservation_date":"2023-07-04 19:33:52","uploaded":"2023-04-07 21:58:52","revisionof":"","revisedto":"","release":"Rel-18","crspec":23.503,"crspecversion":"18.1.0","workitem":[{"winame":"PIN"}],"crnumber":1034.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2305302.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2305303","title":"Which PIN IDs?","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"discussion","for":"Decision","abstract":"This contribution discussed the usage of PIN ID, External Group ID and Internal group ID in the context of PIN","secretary_remarks":"Noted","agenda_item_sort_order":78,"ainumber":"9.3.2","ainame":"Personal IoT Networks (5G_PIN)","tdoc_agenda_sort_order":13140,"status":"noted","reservation_date":"2023-07-04 19:46:26","uploaded":"2023-04-07 19:47:33","revisionof":"","revisedto":"","release":"Rel-18","crspec":23.501,"crspecversion":"","workitem":[{"winame":"PIN"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2305303.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2305307","title":"Multiple PINs sharing the same PDU Session in a PEGC","source":"InterDigital Inc.","contact":"Michael Starsinic","contact-id":72107,"tdoctype":"discussion","for":"Agreement","abstract":"The paper discusses supporting the case where multiple PINs share the same PDU Session in a PEGC.","secretary_remarks":"Noted","agenda_item_sort_order":78,"ainumber":"9.3.2","ainame":"Personal IoT Networks (5G_PIN)","tdoc_agenda_sort_order":13150,"status":"noted","reservation_date":"2023-07-04 19:53:39","uploaded":"2023-04-07 21:52:44","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"PIN"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2305307.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2305308","title":"Update to remove the EN about PINs Sharing a PDU Session","source":"InterDigital Inc.","contact":"Michael Starsinic","contact-id":72107,"tdoctype":"CR","for":"Approval","abstract":"Addressing an EN on sharing of a PDU Session between PINs.","secretary_remarks":"CR Cover sheet error!","agenda_item_sort_order":78,"ainumber":"9.3.2","ainame":"Personal IoT Networks (5G_PIN)","tdoc_agenda_sort_order":13600,"status":"not treated","reservation_date":"2023-07-04 19:53:39","uploaded":"2023-04-07 21:52:44","revisionof":"","revisedto":"","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"PIN"}],"crnumber":4545.0,"crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2305308.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2305309","title":"One PIN Served by more than one PDU Session in a PEGC","source":"InterDigital Inc.","contact":"Michael Starsinic","contact-id":72107,"tdoctype":"discussion","for":"Agreement","abstract":"The paper discusses supporting the case where one PIN is Served by more than one PDU Session in a PEGC.","secretary_remarks":"Noted","agenda_item_sort_order":78,"ainumber":"9.3.2","ainame":"Personal IoT Networks (5G_PIN)","tdoc_agenda_sort_order":13160,"status":"noted","reservation_date":"2023-07-04 19:53:39","uploaded":"2023-04-07 21:52:44","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"PIN"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2305309.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2305310","title":"Update to remove the EN about one PIN using more than one PDU Session","source":"InterDigital Inc.","contact":"Michael Starsinic","contact-id":72107,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Removed the following editor s note: Editor's note: One PIN served by more than one PDU sessions in PEGC is FFS.","secretary_remarks":"Merged into S2-2306176","agenda_item_sort_order":78,"ainumber":"9.3.2","ainame":"Personal IoT Networks (5G_PIN)","tdoc_agenda_sort_order":13240,"status":"merged","reservation_date":"2023-07-04 19:53:39","uploaded":"2023-04-07 21:52:44","revisionof":"","revisedto":"","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"PIN"}],"crnumber":4546.0,"crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2305310.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2305311","title":"URSP Rule Update so that one PIN can use more than one PDU Session","source":"InterDigital Inc.","contact":"Michael Starsinic","contact-id":72107,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Updated the usage of the PIN ID so that other components of the traffic descriptor can also be used to select a PDU Session.","secretary_remarks":"","agenda_item_sort_order":78,"ainumber":"9.3.2","ainame":"Personal IoT Networks (5G_PIN)","tdoc_agenda_sort_order":13710,"status":"not treated","reservation_date":"2023-07-04 19:53:40","uploaded":"2023-04-07 21:52:44","revisionof":"","revisedto":"S2-2307169","release":"Rel-18","crspec":23.503,"crspecversion":"18.1.0","workitem":[{"winame":"PIN"}],"crnumber":1035.0,"crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2305311.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2305347","title":"PDU Session Establishment for PIN","source":"Intel","contact":"Suresh Srinivasan","contact-id":94961,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: PEGC establishing a PDU session and serving as gateway for all the PINE with the intended QoS. PEGC establishes single\/multiple PDU session based the QoS requested by the PINE.","secretary_remarks":"No revision marks shown! Noted","agenda_item_sort_order":78,"ainumber":"9.3.2","ainame":"Personal IoT Networks (5G_PIN)","tdoc_agenda_sort_order":13480,"status":"noted","reservation_date":"2023-07-04 20:44:26","uploaded":"2023-04-07 20:52:12","revisionof":"","revisedto":"","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"PIN"}],"crnumber":4557.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2305347.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.44.3.1","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2306176","title":"PDU session sharing among PINs","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add solution to resove the EN -Specify that no differentiation among PINs in 5GC if PDU session is shared among PINs - Existing meachanisms for session management can be applied for PIN if such can be applied for PIN related PDU session.","secretary_remarks":"Revision of S2-2304175r13, merging S2-2305297, S2-2304850 and S2-2305310. Approved","agenda_item_sort_order":78,"ainumber":"9.3.2","ainame":"Personal IoT Networks (5G_PIN)","tdoc_agenda_sort_order":13200,"status":"agreed","reservation_date":"2023-04-24 18:16:58","uploaded":"2023-04-24 18:51:13","revisionof":"S2-2304175","revisedto":"S2-2306713","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"PIN"}],"crnumber":4224.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-230484","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2306176.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.44.3.1","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2306177","title":"Clarifying SMF behaviour for non-3GPP delay budget","source":"Qualcomm, Nokia, Nokia Shanghai Bell, Ericsson","contact":"Sebastian Speicher","contact-id":94901,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clause 5.44.3.4: Clarify that, if allowed, SMF shall increase the dynamic CN PDB for the related GBR QoS flow by the requested non-3GPP delay budget and signal the updated CN PDB to NG-RAN. Update EN to reflect that how to determine that SMF is allowed to appyl non-3GPP delay budget is FFS. Clause 6.2.2: clarify non-3GPP delay budget support by SMF","secretary_remarks":"Revision of S2-2304359r02. Approved. Revised at S2#157 in S2-2306718","agenda_item_sort_order":78,"ainumber":"9.3.2","ainame":"Personal IoT Networks (5G_PIN)","tdoc_agenda_sort_order":13260,"status":"revised","reservation_date":"2023-04-24 18:16:59","uploaded":"2023-04-24 18:51:13","revisionof":"S2-2304359","revisedto":"S2-2306654, S2-2306718, S2-2306724, S2-2307335","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"PIN"}],"crnumber":4284.0,"crrevision":1.0,"crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2306177.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2306178","title":"PIN identifiers","source":"Nokia, Nokia Shanghai Bell","contact":"Pallab Gupta","contact-id":87959,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add a new clause to describe identifers for PIN. The 5G System already supports group identification and group membership management through External Group ID and Internal Group ID. A PIN also has exactly the same requirements that can be already fullfilled using this group management feature. It is proposed that a PIN is identified externally by a PIN ID. It is also proposed that External Group ID and Internal Group ID is used to identify and manage the PEGC UEs that are part of a PIN.","secretary_remarks":"Revision of S2-2304373r08. CC#4: Approved. Revised at S2#157 in S2-2306834","agenda_item_sort_order":78,"ainumber":"9.3.2","ainame":"Personal IoT Networks (5G_PIN)","tdoc_agenda_sort_order":13280,"status":"revised","reservation_date":"2023-04-24 18:17:00","uploaded":"2023-04-24 18:51:13","revisionof":"S2-2304373","revisedto":"S2-2306385, S2-2306712, S2-2306834","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"PIN"}],"crnumber":4287.0,"crrevision":1.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2306178.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"new 5.44.x","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2306179","title":"Solve the EN about PIN deletion, activation and deactivation","source":"Huawei, HiSilicon, vivo","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Delete the Editor s Note and add the PIN creation, deletion and update to clarify what the PIN management is in the general description clause.","secretary_remarks":"Revision of S2-2304488r01. Approved","agenda_item_sort_order":78,"ainumber":"9.3.2","ainame":"Personal IoT Networks (5G_PIN)","tdoc_agenda_sort_order":13350,"status":"agreed","reservation_date":"2023-04-24 18:17:01","uploaded":"2023-04-24 18:51:13","revisionof":"S2-2304488","revisedto":"","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"PIN"}],"crnumber":4327.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-230484","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2306179.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.44, 5.44.1, 5.44.3.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2306180","title":"Support QoS management for PIN","source":"Vivo","contact":"Zhenhua Xie","contact-id":83004,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add description to reuse group QoS configuration and QoS configuration for traffic between group UEs for PIN","secretary_remarks":"Revision of S2-2304996r06, merging S2-2304998 and S2-2304547. Approved. Revised at S2#157 in S2-2306715","agenda_item_sort_order":78,"ainumber":"9.3.2","ainame":"Personal IoT Networks (5G_PIN)","tdoc_agenda_sort_order":13420,"status":"revised","reservation_date":"2023-04-24 18:17:03","uploaded":"2023-04-24 18:51:13","revisionof":"S2-2304996","revisedto":"S2-2306715","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"PIN"}],"crnumber":4450.0,"crrevision":1.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2306180.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.44.3.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2306181","title":"PIN communication definition","source":"Huawei, Hisilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: New PIN communication definitions are introduced in definition clause 3.1 and then in later clause 5.44 the new definitions are used where required.","secretary_remarks":"Revision of S2-2305131r06. Endorsed. Revised at S2#157 in S2-2306411","agenda_item_sort_order":78,"ainumber":"9.3.2","ainame":"Personal IoT Networks (5G_PIN)","tdoc_agenda_sort_order":13450,"status":"revised","reservation_date":"2023-04-24 18:17:04","uploaded":"2023-04-24 18:51:17","revisionof":"S2-2305131","revisedto":"S2-2306411, S2-2306716, S2-2306835, S2-2306853","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"PIN"}],"crnumber":4492.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2306181.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":true,"clauses_affected":"3.1, 5.44.1","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2306182","title":"Editorial change for the PIN","source":"Xiaomi","contact":"Jianning(Carry) LIU","contact-id":88587,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The three changes above","secretary_remarks":"Revision of S2-2305241r02. Approved","agenda_item_sort_order":78,"ainumber":"9.3.2","ainame":"Personal IoT Networks (5G_PIN)","tdoc_agenda_sort_order":13470,"status":"agreed","reservation_date":"2023-04-24 18:17:05","uploaded":"2023-04-24 18:51:13","revisionof":"S2-2305241","revisedto":"","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"PIN"}],"crnumber":4535.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-230484","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_156E_Electronic_2023-04\/Docs\/S2-2306182.zip","group":"S2","meeting":"S2-156-e","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":false,"clauses_affected":"3.1; 5.44.1; 5.44.3.1;","crsinpack":null,"crsinpacknumber":0}]