[{"name":"R5-191147","title":"UE NSSAI pre-configuration as needed for 5GS Mobility- and Session- Management test cases","source":"Intel Corporation (UK) Ltd","contact":"Graham Brand","contact-id":43647,"tdoctype":"discussion","for":"Endorsement","abstract":"During the CT1#114 meeting a new AT command was proposed supporting the setting and deleting of Configured NSSAI, Allowed NSSAI and Rejected NSSAI (see C1-190191). According to the \"Reason of Change\", this is needed by RAN5 in context of the 5GS test case 9.1.5.1.3 in TS 38.523-1 (see R5-190703 was R5-190168).\nBecause of security concerns C1-190191 was revised to C1-190671 which does not have options for setting and deleting of Configured NSSAI, Allowed NSSAI and Rejected NSSAI. \nPlease note that such an AT command would allow an attacker to manipulate the NSSAI configuration, causing non-compliant UE behaviour. A manipulated UE could request slices that are not allowed or are not part of the user subscription. For example a user with a vanilla eMBB subscription could request the URLLC slice which may have higher subscription fees.\n3\tProposal\nDependency: Update TS 24.501 clause 9.11.3.37 to support Configured NSSAI IE and Default Configured NSSAI IE with content length zero (see C1-191044). \nProposal 1\t:\n?\tUpdate TS 38.508-1 clause 4.5 to include generic procedures for NSSAI pre-configuration \nProposal 2\t:\n?\tUpdate TS 38.523-1 clause 9.1.5.1.3 by removing the NSSAI pre-configuration using AT commands, and use the new generic procedures from TS 38.508 (see Proposal 2)","secretary_remarks":"","agenda_item_sort_order":331,"ainumber":"6.3.8.19","ainame":"\tDiscussion Papers \/ Work Plan \/ TC lists","tdoc_agenda_sort_order":114700,"status":"noted","reservation_date":"2019-02-11 23:07:26","uploaded":"2019-02-12 19:56:21","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ran\/WG5_Test_ex-T1\/TSGR5_82_Athens\/Docs\/R5-191147.zip","group":"R5","meeting":"R5-82","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-191347","title":"FR2 default levels for multi-cell Signalling Test cases in 38.508-1","source":"ANRITSU LTD","contact":"Ian Rose","contact-id":9381,"tdoctype":"discussion","for":"Discussion","abstract":"At RAN5#4-5G-NR Adhoc in Singapore, R5-190790 was agreed, and included the RSRP based procedure for finding the UE orientation and providing a wide enough dynamic range for performing the test scenarios with multiple cells. However, the default power settings for NR cells in TS 38.508-1 were not agreed. \nThe RSRP level difference required for the UE to reliably distinguish FR2 cells was addressed in R5-190304. The method of calculation for both intra-frequency and inter-frequency was discussed at RAN5#4-5G-NR Adhoc in Singapore, but not agreed.  \nThis document re-evaluates the RSRP level difference required for the UE to reliably distinguish FR2 cells, for intra-frequency and inter-frequency scenarios. It also considers the likely FR2 RSRP side conditions in TS 38.133, and proposes default cell levels for TS 38.508-1.\n\nAnritsu recommends the following:\n- \tDefault Serving cell SSB_RP is set to -86dBm\/SCS in 38.508-1 Table 6.2.2.2-2   \n- \tDefault Suitable neighbour inter-freq cell SSB_RP is set to -97dBm\/SCS in 38.508-1 Table 6.2.2.2-2   \n- \tDefault Non-suitable neighbour cell SSB_RP is set to -108dBm\/SCS in 38.508-1 Table 6.2.2.2-2\n- \tSpecified absolute threshold values are signalled as (threshold + ?), using ? for that frequency \n- \tThe mapping value ? is estimated by the RSRP-based calibration process\n- \tRE allocation is reduced for 200MHz and 400MHz Channel BW    \n\nNote that further work is required on the use of ? where a relative threshold is applied for cells on different frequencies.","secretary_remarks":"","agenda_item_sort_order":331,"ainumber":"6.3.8.19","ainame":"\tDiscussion Papers \/ Work Plan \/ TC lists","tdoc_agenda_sort_order":134700,"status":"noted","reservation_date":"2019-02-13 16:48:10","uploaded":"2019-02-15 18:02:00","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ran\/WG5_Test_ex-T1\/TSGR5_82_Athens\/Docs\/R5-191347.zip","group":"R5","meeting":"R5-82","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-191665","title":"Multi PDU Session and IMS in SA Option-2","source":"Qualcomm Wireless GmbH (ETSI)","contact":"yogesh tugnawat","contact-id":63855,"tdoctype":"discussion","for":"Endorsement","abstract":"Background\nA 5GS UE can initiate \u2013\nIMS PDU session only\nInternet PDU session only\nIMS and Internet both (in any order)\nExtra PDU sessions in addition to above\nIn EUTRA the PDN was part of the \u201cAttach\u201d process and hence it was predictable which PDN was being used by UE, and in which order, as such based on what UE behavior was, the assignment of EPS Bearer ID and DRB id and QFI flows was made\nIn 5GS, after REGISTRATION complete, UE can trigger any PDU session and the behavior is dynamic and the assignment of corresponding QFI flow, DRB id and QFI\\QRI\nRRC_IDLE and some key generic procedure like PDU session establishment SHALL account for handling of multi PDU session and the behavior in 5GS preamble shall be made \u201cdynamic\u201d rather than \u201cstatic\u201d\nRF TC doesn\u2019t want to involve IMS signaling during RF tests\n\nProposal for executing RF tests \u2013 5GC\t:\nProposal -1 \nUE\u2019s to be configured with 1 PDU session (non-IMS) with \u201cappropriate settings\u201d to ensure that UE stays on NR after running RRC_CONNECTED or RRC_IDLE procedures from TS 38.508-1, 5GC NR preambles can handle any UE configuration and such this UE type (for ex \u2013 1 internet PDU only), will be handled gracefully.\nSome more details on \u201cappropriate setting\u201d could be \u2013\u00a0\nUE Usage Setting \u2013 set to \u201cData Centric\u201d\nDisable IMS in UE\nAllow\\Configure Internet PDU or any other non-IMS PDU session only\nNW will set VOPS indication in REGISTRATION ACCEPT as \u201c1\u201d. As such signaling preambles will have no issues and this will be ignored by UE (Proposal-1).\nPossibly, also ensure SMS settings will not cause unexpected domain selection.\nProposal -2\nTest Mode Shall be ON (i.e Activate Test Mode) for all RF tests, this will ensure that user data signaling is suppressed. For ex \u2013 if Internet PDU is established, then all the data coming from various applications (for ex \u2013 smartphones mobile data)\n\nWay Forward for Proposal 1,2\t:\nProposal -1 \nInsert a note to RF_RRC_CONNECTED procedure in TS 38.508-1, \u201cUE\u2019s to be configured with 1 PDU session (non-IMS) with \u201cappropriate settings\u201d to ensure that UE stays on NR after above procedure\u201d OR insert same note in RF Spec (?)\nProposal -2\nSpecify in RF Test Spec for each TC that Test Mode Shall be ON (i.e Activate Test Mode)","secretary_remarks":"","agenda_item_sort_order":331,"ainumber":"6.3.8.19","ainame":"\tDiscussion Papers \/ Work Plan \/ TC lists","tdoc_agenda_sort_order":166500,"status":"noted","reservation_date":"2019-02-15 01:00:22","uploaded":"2019-02-28 17:47:55","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":[{"winame":"5GS_NR_LTE-UEConTest"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ran\/WG5_Test_ex-T1\/TSGR5_82_Athens\/Docs\/R5-191665.zip","group":"R5","meeting":"R5-82","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-191668","title":"URSP Consideration for 5GC TC","source":"Qualcomm Wireless GmbH (ETSI)","contact":"yogesh tugnawat","contact-id":63855,"tdoctype":"discussion","for":"Endorsement","abstract":"","secretary_remarks":"","agenda_item_sort_order":331,"ainumber":"6.3.8.19","ainame":"\tDiscussion Papers \/ Work Plan \/ TC lists","tdoc_agenda_sort_order":166800,"status":"noted","reservation_date":"2019-02-15 01:00:24","uploaded":"2019-02-28 17:47:55","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":[{"winame":"5GS_NR_LTE-UEConTest"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_ran\/WG5_Test_ex-T1\/TSGR5_82_Athens\/Docs\/R5-191668.zip","group":"R5","meeting":"R5-82","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]