[{"name":"S2-2411851","title":"Monitoring event for S&F","source":"Samsung, [Sateliot, China Telecom, NEC, CATT]","contact":"Lalith Kumar","contact-id":80547,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Monitoring event for S&F feature is implemented based on the conclusions reached for KI#2 in TR 23.700-29. This revision over agreed version in SA WG2#165 proposes to resolve this EN: Editor's note: Whether feeder link availability period will be provided to SCS\/AS is FFS. There are two choices: a) Introduce this feeder link availability period parameter (as proposed in this CR - highlighted with yellow); or b) Remove the EN with a conclusion that this parameter is not required. After the discussion, this CR can be updated in one of the above directions. As a compromise for companies who are not interested in feeder link availability period parameter, this parameter can be kept optional. This implies: a) If this parameter is included, AF can accurately know when to send the data and delay in sending data b) If this parameter is not included then AF will have to estimate that data will be delivered to the UE with the max time of 'Estimated time to delivery' and this Estimated time to delivery network also considers the feeder link link availability time. For e.g.: Consider: a) Delivery time of data when feeder link available is 1 hour. b) Feeder link(FL) is available at 10 O clock and next FL availability time is after 6 hours. a) If feeder link availability information is provided(i.e. at 10) to the AF, then AF is aware based on when it has sent the data(e.g. at 9) UE will receive the data(e.g. by 11). b) If feeder link availability information is not provided. Then estimated delivery time value considering FL availability is 7 hours(1 hour to send data + 6 hours maximum time for FL to establish depeding on when data is sent to CN) AF will assume data will be delivered in 7 hours without accurately knowing when it can be delivered.","secretary_remarks":"Revision of (agreed) S2-2410985. Revised in parallel session to S2-2412642.","agenda_item_sort_order":113,"ainumber":"19.1.2","ainame":"Integration of satellite components in the 5G architecture Phase III (5GSAT_Ph3_ARCH)","tdoc_agenda_sort_order":11850,"status":"revised","reservation_date":"2024-08-11 07:22:38","uploaded":"2024-11-08 07:42:15","revisionof":"S2-2410985","revisedto":"S2-2412642","release":"Rel-19","crspec":"23.682","crspecversion":"19.0.0","workitem":[{"winame":"5GSAT_Ph3-ARC"}],"crnumber":495.0,"crrevision":9.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_166_Orlando_2024-11\/Docs\/S2-2411851.zip","group":"S2","meeting":"S2-166","year":2024,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"(new)5.6.1.X, (new)5.6.3.X","crsinpack":null,"crsinpacknumber":0}]