[{"name":"S2-2200018","title":"LS from RAN WG2: Reply LS on RAN2 agreements for MUSIM","source":"RAN WG2","contact":"Boubacar Kimba","contact-id":72224,"tdoctype":"LS in","for":"Action","abstract":"RAN WG2 thanks CT WG1 for their reply to LS on NAS-based busy indication. Regarding the NAS-based busy indication, RAN WG2 would like to provide the following responses for the questions asked by the CT WG1 in the LS C1-214917: o Question 1: CT WG1 respectfully asks RAN WG2's guidance on the interaction between the NAS layer and the AS layer when the AS layer receives RAN paging. Answer 1: RAN WG2 has discussed the issue and agreed that the AS-NAS interaction for paging reception in RRC_INACTIVE is left up to the UE implementation. o Question 2: Is a paging cause, if any, indicated together with indication about RAN paging from the AS layer to NAS layer? Answer 2: As mentioned in Answer 1, the AS-NAS interaction for paging reception, including any paging cause, in RRC_INACTIVE is left up to the UE implementation. In addition, RAN WG2 found inconsistent between CT WG1 and SA WG2 specification on alternative IMSI calculation in EPS. Based on the CT WG1 spec, NAS will forward the accepted IMSI offset to lower layers. This is aligned with RAN WG2 agreement on PF\/PO calculation for EPS since the AS layer needs the IMSI offset to calculate the UE_ID. However, SA WG2 specifies that the IMSI offset is used by the NAS layer to calculate an alternative IMSI instead of the UE_ID, and it seems that the NAS layer needs to forward the alternative IMSI to the AS for the determination of paging occasions as specified in TS 36.304. So based on the SA WG2's specification, SA WG2 is not aligned with both RAN WG2 and CT WG1's agreements. RAN WG2 prefers that the alternative IMSI is to be calculated in AS layer (i.e. aligned with CT WG1 specification). Action: RAN WG2 respectfully asks CT WG1 and SA WG2 to take the above responses into consideration and provide feedback if any.","secretary_remarks":"Revision of Postponed S2-2108997 from S2#148E. Response drafted in S2-2200146. CC#2: Final response in S2-2201681","agenda_item_sort_order":72,"ainumber":"8.29","ainame":"Items moved for decision by Deadline #1","tdoc_agenda_sort_order":18440,"status":"replied to","reservation_date":"2022-01-10 13:42:20","uploaded":"2022-01-10 13:44:26","revisionof":"S2-2108997","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1, SA WG2","Cc":"RAN WG3, SA WG3","lsoriginalls":"R2-2111329","lsreply":"S2-2201681","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2200018.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]