[{"name":"R5-203613","title":"Discussion paper on tracking of 5GS protocol test cases Rel-16 and beyond","source":"Ericsson","contact":"Leif Mattisson","contact-id":10602,"tdoctype":"discussion","for":"Endorsement","abstract":"For LTE the TS rapporteur of TS 36.523-1 have provided a test case tracking document pre and post every RAN5 meeting. The purpose of the tracking is to provide an overview of test case status and avoid duplication of test cases numbers when new LTE work items and TEI test cases are introduced.\nThe purpose of this paper is to propose to introduce a TS 38.523-1 tracker document and the process and responsibilities for maintaining it.","secretary_remarks":"","agenda_item_sort_order":15,"ainumber":"4.5.3","ainame":"\tOther open issues from joint sessions - original A.I. retained","tdoc_agenda_sort_order":36130,"status":"revised","reservation_date":"2020-08-06 05:46:48","uploaded":"2020-08-08 06:47:22","revisionof":"","revisedto":"R5-204366","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_RAN\/WG5_Test_ex-T1\/TSGR5_88_Electronic\/Docs\/R5-203613.zip","group":"R5","meeting":"R5-88-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-204219","title":"Proposals for new GNSS scenarios for TS 37.571-X","source":"Spirent Communications","contact":"Richard Catmur","contact-id":26952,"tdoctype":"discussion","for":"Information","abstract":"5.5.16, Also AI 6.6.7.5\nFollowing the discussion of issues with the current GNSS scenarios used for testing BeiDou (BDS), described in R5-202023, and following RAN 5 endorsement of a basic way-forward, some companies have held off-line discussions to agree a more detailed way-forward. The proposals are detailed below for information. Any other company wishing to comment or take part in further off-line discussions is invited to contact the author.\nDetail:\n1. It is clear that if the BDS scenarios are to be updated, then all the other GNSS scenarios also should be updated at the same time to bring them up to a similar level of realism. Note that this will also automatically add the new BDS B1C signal.\n2. In order to provide the most realistic simulations possible, we will use \u201clive orbital data\u201d from a web site or websites that lists the actual orbital data used at some (recent) point in time. The websites to be used is currently under discussion off-line. \n3. In order to simplify our work we will only use one scenario\/set of orbital data per GNSS.\n4. In TS 37.571-5 we will record the orbital data in a format(s) to be agreed (TLE or Yuma or Rinex). This may require more than one format as Yuma is only almanac, Rinex is ephemeris and it is agreed that both will be specified (see below).\n5. We will ensure the RAN 4 \/ RAN 5 requirements for the number of satellites per GNSS is achieved. Currently this does not seem possible for BDS but this is still under investigation.\n6. To avoid too many changes, we will use\/specify the same locations as used currently (note therefore we will not take into account the requirements of NavIC). \n7. In order to avoid any issues with UEs when using the current, very old, dates and times, we will specify much more recent (fixed) date(s) and time(s). The date(s) will be at least this year (2020), after the latest GPS roll-over.\n8. In order to reduce the amount of unnecessary work in making the changes above, we will no longer specify in TS 37.571-5 all the assistance data as is done today. Much of this is highly repetitive and prone to errors etc. As well as time(s) and locations we will just specify the almanac (as Yuma?) and the ephemeris (as Rinex?). The atmospheric conditions will be specified in the Rinex files. The specification of the Acquisition assistance is under discussion and it is possible we will just specify search windows etc. It will be for Test Vendors to create and correctly format the appropriate Assistance Data.\n9. We will propose a \u201cgrace period\u201d until the end of 2021 for the final cut-over to the new data discussed above to avoid too much re-validation etc.\n10 It is currently proposed to start introducing the new data etc. into the specifications at the November RAN 5 meeting.","secretary_remarks":"","agenda_item_sort_order":15,"ainumber":"4.5.3","ainame":"\tOther open issues from joint sessions - original A.I. retained","tdoc_agenda_sort_order":42190,"status":"noted","reservation_date":"2020-08-07 17:24:46","uploaded":"2020-08-07 17:53:15","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_RAN\/WG5_Test_ex-T1\/TSGR5_88_Electronic\/Docs\/R5-204219.zip","group":"R5","meeting":"R5-88-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"R5-204366","title":"Discussion paper on tracking of 5GS protocol test cases Rel-16 and beyond","source":"Ericsson","contact":"Ingbert Sigovich","contact-id":28887,"tdoctype":"discussion","for":"Endorsement","abstract":"","secretary_remarks":"","agenda_item_sort_order":15,"ainumber":"4.5.3","ainame":"\tOther open issues from joint sessions - original A.I. retained","tdoc_agenda_sort_order":36131,"status":"noted","reservation_date":"2020-09-02 09:09:04","uploaded":"2020-09-02 09:11:11","revisionof":"R5-203613","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_RAN\/WG5_Test_ex-T1\/TSGR5_88_Electronic\/Docs\/R5-204366.zip","group":"R5","meeting":"R5-88-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]