Tdoc List

2018-11-16 23:48

to SA plenary: For information: SA#83 (03/2019) For approval: SA#84 (06/2019
Agenda Topic TDoc Title Source Type For Avail Treated Decision Wdrn Replaced-by Replaces
1 Opening of the meeting                      
1.1 Agenda and scheduling S1‑183000 Draft Agenda for SA1#84 Chair agenda   No
Yes
 		revised No S1‑183001  
    S1‑183001 2nd Draft Agenda for SA1#84 Chair agenda - No
Yes
 		revised No S1‑183002 S1‑183000
    S1‑183002 Final Schedule and Agenda with document allocation for SA1#84 Chair agenda - Yes
Yes
 		agreed No   S1‑183001
1.2 IPR, antitrust and competition laws                      
1.3 Previous SA1 meeting report S1‑183004 Draft minutes of SA1#83 ETSI MCC report Information Yes
Yes
 		revised No S1‑183005  
    S1‑183005 Final minutes of SA1#83 ETSI MCC report Approval No
Yes
 		approved No    
1.4 Information for delegates S1‑183006 Extract of the 3GPP Work Plan for SA1#84 ETSI MCC Work Plan Information Yes
YesAll the work being progressed by SA1 is listed here. The deadlines are December 2018 for Stage 1 for Rel-16. For Stage 1 for Rel-17, the date will be decided in Dec.
 		noted No    
1.5 Information for rapporteurs                      
1.6 Working agreements                      
2 Reports and action items S1‑183003 Report of SA1 topics at SA#82 Chair report Information No
Yes
 		revised No S1‑183335  
    S1‑183335 Report of SA1 topics at SA#82 Chair report Information Yes
YesAt the December 2018 TSG meetings, the time plan for Release 17 will be discussed. After the SA1 report, it was indicated that SA1 is getting highly loaded and SA1 has to maintain quality control.
 		noted No   S1‑183003
    S1‑183007 Rel-15 Summary Description TR 21.915 ETSI MCC draft TR Information Yes
Yes
 		noted No    
3 Liaison Statements (including related contributions) S1‑183340 Reply LS to SA2, RAN2 (cc RAN3) on Location Service exposure to NG-RAN R2-1813425 LS out Information Yes
YesProposed answer to 3274
 		agreed No    
    S1‑183622 LS on authentication of group of IoT devices S3-183717 LS in discussion Yes
YesIt is wondered why SA3 is asking this question: to save signalling, etc. For Qualcomm and Ericsson, this use case is not clear to start with and should be moved out of Release 15. For Qualcomm, SA2 has to defined the Stage 2 before SA3 is actively involved. For Orangew, this can be handled at the next SA1 meeting, no emergency to answer. For Huawei and Intel, SA3 need the answer to be able to proceed, so this is urgent. For the chair, there is no consensus to send an answer at this stage. The LS came during the SA1 meeting and it cannot be answered right now. For Qualcomm, the main point that is blocking SA3 is the Stage 2 not being defined.
 		postponed No    
3.1 LSs on Access control S1‑183218 Reply LS on RRCReject T302 Timer Exemption for MPS and MCS Vencore Labs, OEC LS out Agreement Yes
Yes
 		revised No S1‑183337  
    S1‑183337 Reply LS on RRCReject T302 Timer Exemption for MPS and MCS Vencore Labs, OEC LS out Agreement Yes
YesThe two options reflect a lack of consensus when drafting the answer. The main difference is that "should be coordinated with CT1" is mentioned or not. For Ericsson, this would be negative to send an LS with not enough details, which might look like the feature is not working. It is preferrable to give more time.
 		revised No S1‑183683 S1‑183218
    S1‑183683 Reply LS on RRCReject T302 Timer Exemption for MPS and MCS Vencore Labs, OEC LS out Agreement Yes
YesFor Nokia, this is too solution-oriented, and an LS should not add new requirements.
 		revised No S1‑183684 S1‑183337
    S1‑183684 Reply LS to RAN2 (cc CT1) on RRCReject T302 Timer Exemption for MPS and MCS Vencore Labs, OEC LS out Agreement Yes
YesThere is not enough time at the end of SA1 meeting to handle it correctly, so the incoming RAN2 LS in 3255 is postponed.
 		noted No   S1‑183683
    S1‑183229 Discussion paper on UAC in RRC_Inactive Qualcomm Incorporated, Nokia, Nokia Shanghai Bell discussion Agreement Yes
Yes
 		noted No    
    S1‑183230 Reply LS on UAC in RRC_Inactive Qualcomm Incorporated LS out Agreement Yes
Yes
 		revised No S1‑183339  
    S1‑183339 Reply LS on UAC in RRC_Inactive Qualcomm Incorporated LS out Agreement Yes
YesSome delegations (Huawei, Intel) would like the LS to also mention t "so CT1 is free to proceed or not with the Stage 3 of this feature", but, for some other companies (Qualcomm), it is not SA1 to decide about this. Nokia and LG support the LS as it is. Editorial clean-up needed.
 		revised No S1‑183623 S1‑183230
    S1‑183623 Reply LS on UAC in RRC_Inactive Qualcomm Incorporated LS out Agreement Yes
Yes
 		agreed No   S1‑183339
    S1‑183248 LS on unified access control in RRC_Inactive C1-185602 LS in Information Yes
YesSee proposed answer in 3229.
 		noted No    
    S1‑183255 LS to SA1 on RRCReject T302 Timer Exemption for MPS and MCS R2-1816068 LS in Information Yes
YesProposed answer in 3218
 		postponed No    
    S1‑183273 LS on Addition of access/load control for CE R2-1808898/S1-182321 LS in discussion Yes
YesLinked to 3341.
 		noted No    
3.2 LSs on Localization S1‑183251 Reply LS on Location Service exposure to NG-RAN R2-1813425 LS in Information Yes
YesSee SA1's answer in S1-183340
 		noted No    
    S1‑183274 LS on Location Service exposure to NG-RAN S2-185792/S1-182324 LS in discussion Yes
YesSee proposed answer in 3251.
 		noted No    
3.3 LSs on Emergency calls S1‑183138 Draft Reply LS on the need of paging reception for the call-back when a UE is in limited service state Intel LS out Approval Yes
Yes
 		revised No S1‑183341  
    S1‑183341 Draft Reply LS to RAN2 (cc SA2) on the need of paging reception for the call-back when a UE is in limited service state Intel LS out Approval Yes
Yes
 		agreed No   S1‑183138
    S1‑183139 Clarification of emergency call-back for a UE in limited state Intel CR Approval Yes
YesIt should be Rel-15
 		noted No    
    S1‑183253 LS on the need of paging reception for the call-back when a UE is in limited service state R2-1816007 LS in Information Yes
Yes
 		noted No    
    S1‑183259 Reply LS on the need of paging reception for the call-back when a UE is in limited service state S2-1811544 LS in Information Yes
Yes
 		noted No    
3.4 LSs on Maritime S1‑183187 Reply to LS on the information of the 3GPP standardization applicable to maritime usage and the request of the additional maritime related information IALA ENAV22 LS in Information Yes
Yes
 		noted No    
3.5 LSs on Time-sensitive networking S1‑183254 LS on TSN requirements evaluation R2-1816043 LS in Information Yes
YesSee proposed answer in 3231 and SA2's answer in 3256.
 		noted No    
    S1‑183256 LS on TSN integration in the 5G System S2-189051 LS in Information Yes
YesSA2's answer to RAN2's LS in 3254. SA1 answer in 3231
 		noted No    
    S1‑183231 Reply LS on TSN requirements evaluation Qualcomm Incorporated LS out Agreement Yes
Yes
 		revised No S1‑183342  
    S1‑183342 Reply LS to RAN2, SA2 (cc RAN1, RAN3 ) on TSN requirements evaluation Qualcomm Incorporated LS out Agreement Yes
Yes"proposed for inclusion" to be changed in "included". Editorial corrections needed.
 		revised No S1‑183624 S1‑183231
    S1‑183624 Reply LS to RAN2, SA2 (cc RAN1, RAN3 ) on TSN requirements evaluation Qualcomm Incorporated LS out Agreement Yes
YesSame change as in 3695 needed
 		revised No S1‑183707 S1‑183342
    S1‑183707 Reply LS to RAN2, SA2 (cc RAN1, RAN3 ) on TSN requirements evaluation Qualcomm Incorporated LS out Agreement Yes
Yes
 		agreed No   S1‑183624
3.6 LSs on Extended reality S1‑183261 LS on Extended Reality over 5G S4-181154 LS in Information Yes
Yesproposed answer in 3711.
 		noted No    
    S1‑183244 Reply LS on Extended Reality over 5G Qualcomm Incorporated LS out Agreement Yes
YesTo be further handled and revised at the drafting session
 		revised No S1‑183349  
    S1‑183349 Reply LS to SA4 on Extended Reality over 5G Qualcomm Incorporated LS out Agreement Yes
Yestypos to be corrected
 		revised No S1‑183711 S1‑183244
    S1‑183711 Reply LS to SA4 on Extended Reality over 5G Qualcomm Incorporated LS out Agreement No
Yes
 		agreed No   S1‑183349
3.7 LSs on V2X S1‑183257 Reply LS on Requirements to enable Predictive QoS for Automotive industry S2-1810867 LS in Information Yes
YesAnswer in S1-183705
 		noted No    
    S1‑183705 Reply LS to SA2, 5GAA WG2 (cc SA) on Requirements to enable Predictive QoS for Automotive industry S2-1810867 LS out Information Yes
YesProposed answer to S1-183257. Further edited while projecting.
 		revised No S1‑183713  
    S1‑183713 Reply LS to SA2, 5GAA WG2 (cc SA) on Requirements to enable Predictive QoS for Automotive industry S2-1810867 LS out Information Yes
Yes
 		agreed No   S1‑183705
    S1‑183250 LS to 3GPP TSG-SA WG6 on Use of ITS Dedicated Spectrum within V2X UE ETSI ITS(18)032030r1 LS in Information Yes
Yes
 		noted No    
3.8 LSs on Multi-identity S1‑183262 Reply LS from SA5 to SA1 on Multi-identity and multi-device requirements S5-186289 LS in Information Yes
YesNo answer needed.
 		noted No    
3.9 LSs on Slicing S1‑183264 LS to SA1 on business roles for 5G networks and network slicing management S5-186321 LS in Information Yes
YesSee proposed answer in 3212.
 		noted No    
    S1‑183212 Reply LS on business roles for 5G networks and network slicing management Orange LS out   Yes
YesNot all the parts of the SA5's proposed role model are relevant to SA1. The idea of adding a picture is appreciated but the proposed one is not fully in line with the SA1 concepts.
 		noted No    
3.10 LSs on other topics S1‑183247 GSMA 5GSI#04 Doc 003 LS to 3GPP RAN and 3GPP SA on 5G Indicator Requirements LS in Information Yes
Yes
 		noted No    
    S1‑183249 Reply LS on establishment causes C1-186967 LS in Information Yes
Yes
 		noted No    
    S1‑183252 LS on establishment causes R2-1813465 LS in Information Yes
Yes
 		noted No    
    S1‑183258 Reply to LS on Slice based Wait timer in NR RRC release S2-1811520 LS in Information Yes
Yes
 		noted No    
    S1‑183260 Reply LS on the applicability of service area restriction and NSSAIs to EPLMNs S2-1811546 LS in Information Yes
Yes
 		noted No    
    S1‑183263 LS reply to ITU-T SG13 on draft Recommendation Y.3103 S5-186320 LS in Information Yes
Yes
 		noted No    
    S1‑183265 Reply LS on Publication of new paper on network slicing and future plans S5-186365 LS in Information Yes
Yes
 		noted No    
4 New Study and Work Items (including related contributions) S1‑183010 normative requirements for V2XIMP LG Electronics Inc, AT&T CR Agreement Yes
Yes
 		revised No S1‑183269  
    S1‑183269 normative requirements for V2XIMP LG Electronics Inc, AT&T CR Agreement Yes
Yes
 		revised No S1‑183621 S1‑183010
    S1‑183621 normative requirements for V2XIMP LG Electronics Inc, AT&T CR Agreement Yes
Yes
 		revised No S1‑183627 S1‑183269
    S1‑183627 normative requirements for V2XIMP LG Electronics Inc, AT&T CR Agreement Yes
Yes
 		revised No S1‑183685 S1‑183621
    S1‑183685 normative requirements for V2XIMP LG Electronics Inc, AT&T CR Agreement Yes
Yes
 		agreed No   S1‑183627
    S1‑183011 Improvement of V2X service Handling LG Electronics, AT&T, ZTE, LG Uplus, Volkswagen, Deutsche Telekom WID new Approval Yes
Yes
 		revised No S1‑183268  
    S1‑183268 Improvement of V2X service Handling LG Electronics, AT&T, ZTE, LG Uplus, Volkswagen, Deutsche Telekom, Huawei, KDDI, Ericsson WID new Approval Yes
YesNokia has some concerns about the exact behaviour of what will be defined with this Work Item. This needs to be further explained, preferably directly on the WID. All the question marks have to be removed. Vodafone mentioned some complains from SA2 during the study phase that should be taken into account for the normative phase.
 		revised No S1‑183350 S1‑183011
    S1‑183350 Improvement of V2X service Handling LG Electronics, AT&T, ZTE, LG Uplus, Volkswagen, Deutsche Telekom, Huawei, KDDI, Ericsson WID new Approval Yes
YesAgreed, status report in S1-183625
 		agreed No   S1‑183268
    S1‑183619 Discussion on V2XIMP LG other discussion Yes
Yes
 		noted No    
    S1‑183620 Annex Role model for V2XIMP LG CR discussion Yes
Yes
 		revised No S1‑183626  
    S1‑183626 Annex Role model for V2XIMP LG CR discussion Yes
Yeswrong version of the spec: it should be 16.0.0 and not 16.1.0
 		revised No S1‑183688 S1‑183620
    S1‑183688 Annex Role model for V2XIMP LG CR discussion Yes
Yes
 		agreed No   S1‑183626
5 Quality improvement contributions S1‑183012 correction on PLMN selection in RLOS LG Electronics Inc. CR Agreement Yes
YesThere is no registration for RLOS, and the proposed changes violate the US regulation, according to Sprint. Intel also has concerns with this CR. For the chair, this is not improving the quality but changing the meaning of the spec. Only the part on clarifications should be kept.
 		revised No S1‑183591  
    S1‑183591 correction on PLMN selection in RLOS LG Electronics Inc. CR Agreement Yes
Yes
 		revised No S1‑183629 S1‑183012
    S1‑183629 correction on PLMN selection in RLOS LG Electronics Inc. CR Agreement Yes
Yes
 		revised No S1‑183686 S1‑183591
    S1‑183686 correction on PLMN selection in RLOS LG Electronics Inc. CR Agreement Yes
Yes
 		revised No S1‑183714 S1‑183629
    S1‑183714 correction on PLMN selection in RLOS LG Electronics Inc. CR Agreement Yes
Yes
 		agreed No   S1‑183686
    S1‑183013 Corrections on requirements for SAT LG Electronics Inc. CR Agreement Yes
YesThis needs further improvements.
 		revised No S1‑183592  
    S1‑183592 Corrections on requirements for SAT LG Electronics Inc. CR Agreement Yes
Yes
 		revised No S1‑183628 S1‑183013
    S1‑183628 Corrections on requirements for SAT LG Electronics Inc. CR Agreement Yes
Yes
 		agreed No   S1‑183592
    S1‑183089 Removal of mis-aligned descriptions and requirements on ITS LG Electronics Inc. CR   Yes
Yes
 		noted No    
    S1‑183090 Removal of mis-aligned descriptions and requirements on ITS LG Electronics Inc. CR   Yes
YesMirror of 3089.
 		noted No    
    S1‑183092 Clarification on positioning-related descriptions in 7.3.1 LG Electronics Mobile Research CR   Yes
YesThe new text is not seen as clarifying text for the UK Home Office.
 		revised No S1‑183596  
    S1‑183596 Clarification on positioning-related descriptions in 7.3.1 LG Electronics Mobile Research CR - Yes
Yes
 		revised No S1‑183630 S1‑183092
    S1‑183630 Clarification on positioning-related descriptions in 7.3.1 LG Electronics Mobile Research CR - No
Yes
 		agreed No   S1‑183596
    S1‑183093 Clarification on positioning-related descriptions in 7.3.1 LG Electronics Mobile Research CR   Yes
YesMirror
 		revised No S1‑183597  
    S1‑183597 Clarification on positioning-related descriptions in 7.3.1 LG Electronics Mobile Research CR - Yes
Yes
 		revised No S1‑183662 S1‑183093
    S1‑183662 Clarification on positioning-related descriptions in 7.3.1 LG Electronics Mobile Research CR - Yes
Yes
 		revised No S1‑183687 S1‑183597
    S1‑183687 Clarification on positioning-related descriptions in 7.3.1 LG Electronics Mobile Research CR - Yes
Yes
 		agreed No   S1‑183662
    S1‑183094 Termnology correction for positioning-related tables in 7.3.2 LG Electronics Mobile Research CR   Yes
Yes
 		revised No S1‑183598  
    S1‑183598 Termnology correction for positioning-related tables in 7.3.2 LG Electronics Mobile Research CR - Yes
Yes
 		revised No S1‑183631 S1‑183094
    S1‑183631 Termnology correction for positioning-related tables in 7.3.2 LG Electronics Mobile Research CR - No
Yes
 		agreed No   S1‑183598
6 Rel-15 and earlier contributions S1‑183140 Clarification for Communication Waiting Service in early call setup state Intel CR Approval Yes
YesThis is seen as a new requirement by Nokia, and it is too late to add a requirement for Rel-15. For Qualcomm, nothing is needed at all. Ericsson explained that the CW service has been there for decades, coming from PSTN, and there was no problem with it. The current text comes from the agreement made with TISPAN in 2007. Ericsson are concerned about changing this description now. Twelve companies are in favour of not changing anything, while 3 want to improve the text. So the conclusion is that there is no need to change the text.
 		noted No    
6.1 Release 15 Alignment CRs (aligning Stage 1 specifications with what has been implemented in Stage 2 and 3) S1‑183036 Alignment of Markets requiring minimal service levels requirement Orange UK CR Agreement Yes
YesChange on "Description" is not needed.
 		revised No S1‑183600  
    S1‑183600 Alignment of Markets requiring minimal service levels requirement Orange UK CR Agreement Yes
Yes
 		agreed No   S1‑183036
    S1‑183037 Alignment of Extreme long range coverage in low density areas requirement Orange UK CR Agreement Yes
YesThis is another alignment CR. A typo to be corrected.
 		revised No S1‑183601  
    S1‑183601 Alignment of Extreme long range coverage in low density areas requirement Orange UK CR Agreement Yes
Yes
 		agreed No   S1‑183037
    S1‑183142 Alignment of service requirements for Satellite access and Fixed broadband access Intel CR Approval Yes
Yes"(void)" to be changed into "void".
 		revised No S1‑183602  
    S1‑183602 Alignment of service requirements for Satellite access and Fixed broadband access Intel, KPN CR Approval Yes
Yes
 		agreed No   S1‑183142
    S1‑183143 Service requirements for Network Capability Exposure Intel CR Approval Yes
YesThese ones are not listed in Vodafone summary document. For Huawei, some of the requirements proposed for deletion are indeed for Rel-15. To be checked off-line.
 		revised No S1‑183603  
    S1‑183603 Service requirements for Network Capability Exposure Intel CR Approval Yes
Yes
 		agreed No   S1‑183143
    S1‑183144 Service requirements for flexible broadcast/multicast Intel CR Approval Yes
YesAll of section 6.13 should be voided.
 		revised No S1‑183604  
    S1‑183604 Service requirements for flexible broadcast/multicast Intel CR Approval Yes
Yes
 		agreed No   S1‑183144
    S1‑183158 Release 15 alignment for SMARTER Vodafone Romania S.A. discussion Decision Yes
YesA series of CRs are either already written or proposed to be written to address all these points. One more of these CRs in S1-183599.
 		noted No    
    S1‑183171 Release 15 alignment of multiple access requirements KPN CR Agreement Yes
YesMerged/included in 3602.
 		noted No    
    S1‑183245 Alignment - Removing Integrated Access Backhaul from 5GS in Release 15 Qualcomm Incorporated CR   Yes
YesOnly clause 6.12 needs to be voided, the subclauses can be deleted.
 		revised No S1‑183605  
    S1‑183605 Alignment - Removing Integrated Access Backhaul from 5GS in Release 15 Qualcomm Incorporated CR - Yes
Yes
 		agreed No   S1‑183245
    S1‑183599 Alignment of multi-network connectivity Vodafone CR discussion Yes
Yes
 		agreed No    
6.2 Rel-15 correction and clarification CRs (other than alignment) S1‑183015 Correction to emergency number handling LG Electronics Inc. CR Agreement Yes
YesThere is no Stage 2 equivalence. There are several formal mistakes (wrong version of the spec on the cover page, all styles corrupted in the CR).
 		revised No S1‑183606  
    S1‑183606 Correction to emergency number handling LG Electronics Inc. CR Agreement Yes
YesFor RIM, this is a highly controversial topic which is better to leave as such. Nokia and other companies share this point of view.
 		noted No   S1‑183015
    S1‑183016 Correction to emergency number handling LG Electronics Inc. CR Agreement Yes
YesMirror
 		revised No S1‑183607  
    S1‑183607 Correction to emergency number handling LG Electronics Inc. CR Agreement Yes
Yes
 		noted No   S1‑183016
    S1‑183117 Editorial correction table 7.2.2-1 Nokia, Nokia Shanghai Bell CR   Yes
Yes"NOTE1" to be changed into "NOTE 1". All these changes are included in 3160 rev. in 3608.
 		noted No    
    S1‑183160 Minor correction to URLLC clause Vodafone Romania S.A. CR Decision Yes
YesAll the values provided in Table 7.2.2-1 are now examples. Should be category F and not D. Wrong Work Item shown on the cover page ("cyberCAV" instead of "SMARTER"). Wrong release shown on cover page.
 		revised No S1‑183608  
    S1‑183608 Minor correction to URLLC clause Vodafone Romania S.A. CR Agreement Yes
Yes
 		agreed No   S1‑183160
    S1‑183609 Minor correction to URLLC clause Vodafone CR discussion Yes
YesMirror CR of 3608. Revised to take into account the changes from 3612 and avoid overlap in changes.
 		revised No S1‑183691  
    S1‑183691 Minor correction to URLLC clause Vodafone CR discussion Yes
Yes
 		agreed No   S1‑183609
6.3 Rel-14 and earlier CRs                      
7 Rel-16 Work Item contributions S1‑183317 Drafting session A agenda Session Chair agenda discussion Yes
Yes
 		agreed No    
    S1‑183318 Drafting session A report Session Chair report discussion Yes
Yes
 		agreed No    
    S1‑183319 Drafting session B agenda Session Chair agenda discussion Yes
Yes
 		agreed No    
    S1‑183320 Drafting session B report Session Chair report discussion Yes
Yes
 		agreed No    
    S1‑183321 Drafting session C agenda Session Chair agenda discussion Yes
Yes
 		agreed No    
    S1‑183322 Drafting session C report Session Chair report discussion Yes
Yes
 		agreed No    
    S1‑183323 Drafting session D agenda Session Chair agenda discussion Yes
Yes
 		noted No    
    S1‑183324 Drafting session D report Session Chair report discussion Yes
Yes
 		agreed No    
    S1‑183325 Drafting session E agenda Session Chair agenda discussion Yes
Yes
 		agreed No    
    S1‑183326 Drafting session E report Session Chair report discussion Yes
Yes
 		agreed No    
    S1‑183327 Drafting session F agenda Session Chair agenda discussion Yes
Yes
 		agreed No    
    S1‑183328 Drafting session F report Session Chair report discussion Yes
Yes
 		agreed No    
7.1 Rel-16 CRs under TEI16 or for completed work items S1‑183008 Requirement to allow for users to automatically be informed when affiliation information changes in a group HOME OFFICE CR Agreement Yes
YesRelated WI should be changed from "MCImp-MCCoRe, TEI16" to "TEI16, MCImp-MCCoRe". Cat should be B.
 		revised No S1‑183610  
    S1‑183610 Requirement to allow for users to automatically be informed when affiliation information changes in a group HOME OFFICE CR Agreement Yes
Yes
 		agreed No   S1‑183008
    S1‑183014 Clarification on disabling of legacy radio LG Electronics Inc. CR Agreement Yes
YesSprint sees that as weakening the overall security of the system. "part of the radio technology" is too vague, for the UK Home Office.
 		revised No S1‑183611  
    S1‑183611 Clarification on disabling of legacy radio LG Electronics Inc. CR Agreement Yes
Yes"LTE" is not a proper way to refer to the E-UTRA and has to be changed everywhere.
 		revised No S1‑183632 S1‑183014
    S1‑183632 Clarification on disabling of legacy radio LG Electronics Inc. CR Agreement Yes
Yes"reason for change" to be updated.
 		revised No S1‑183689 S1‑183611
    S1‑183689 Clarification on disabling of legacy radio LG Electronics Inc. CR Agreement Yes
Yes
 		agreed No   S1‑183632
7.2 MONASTERY2: Mobile Communication System for Railways 2 [SP-170451] S1‑183024 Addition of new Group Call Commencement Modes FirstNet CR Agreement Yes
Yes
 		revised No S1‑183511  
    S1‑183511 Addition of new Group Call Commencement Modes FirstNet CR Agreement Yes
Yes
 		agreed No   S1‑183024
    S1‑183054 Add conditional media forwarding Kapsch CarrierCom CR Agreement Yes
Yes
 		revised No S1‑183516  
    S1‑183516 Add conditional media forwarding Kapsch CarrierCom CR Agreement Yes
Yes
 		revised No S1‑183544 S1‑183054
    S1‑183544 Add conditional media forwarding Kapsch CarrierCom CR Agreement Yes
Yes"user" to be changed into "MCPTT Users"
 		revised No S1‑183650 S1‑183516
    S1‑183650 Add conditional media forwarding Kapsch CarrierCom CR Agreement Yes
Yes
 		agreed No   S1‑183544
    S1‑183055 Add location based barring Kapsch CarrierCom CR Agreement No
Yes
 		withdrawn Yes    
    S1‑183056 Move interworking of functional alias from MCPTT to MCCoRe TS, MCCoRe part Kapsch CarrierCom, Nokia CR Agreement Yes
Yes
 		revised No S1‑183513  
    S1‑183513 Move interworking of functional alias from MCPTT to MCCoRe TS, MCCoRe part Kapsch CarrierCom, Nokia CR Agreement Yes
Yes
 		agreed No   S1‑183056
    S1‑183057 Move interworking of functional alias from MCPTT to MCCoRe TS, MCPTT part Kapsch CarrierCom, Nokia CR Agreement Yes
Yes
 		revised No S1‑183512  
    S1‑183512 Move interworking of functional alias from MCPTT to MCCoRe TS, MCPTT part Kapsch CarrierCom, Nokia CR Agreement Yes
Yes
 		agreed No   S1‑183057
    S1‑183058 Add interworking between MCData SDS and GSM-R SMS Kapsch CarrierCom, Nokia CR Agreement Yes
Yes
 		agreed No    
    S1‑183068 Notification to a group of users Union Inter. Chemins de Fer CR Agreement Yes
Yes
 		noted No    
    S1‑183073 Changes to recording and audit metadata Union Inter. Chemins de Fer CR Agreement Yes
Yes
 		revised No S1‑183514  
    S1‑183514 Changes to recording and audit metadata Union Inter. Chemins de Fer CR Agreement Yes
Yes
 		agreed No   S1‑183073
    S1‑183123 Quality of Service requirements necessary for rail communication Union Inter. Chemins de Fer discussion Agreement Yes
Yes
 		revised No S1‑183521  
    S1‑183521 Quality of Service requirements necessary for rail communication Union Inter. Chemins de Fer discussion Agreement Yes
Yes
 		revised No S1‑183546 S1‑183123
    S1‑183546 Quality of Service requirements necessary for rail communication Union Inter. Chemins de Fer pCR Agreement Yes
Yes
 		agreed No   S1‑183521
    S1‑183165 Interworking among MCX Service systems Union Inter. Chemins de Fer CR Approval Yes
Yes
 		revised No S1‑183517  
    S1‑183517 Interworking among MCX Service systems Union Inter. Chemins de Fer CR Approval Yes
Yes
 		agreed No   S1‑183165
    S1‑183166 Additional requirements for the use of a gateway UE Union Inter. Chemins de Fer CR Approval Yes
Yes
 		revised No S1‑183518  
    S1‑183518 Additional requirements for the use of a gateway UE Union Inter. Chemins de Fer CR Approval Yes
Yes
 		revised No S1‑183545 S1‑183166
    S1‑183545 Additional requirements for the use of a gateway UE Union Inter. Chemins de Fer CR Approval Yes
Yes
 		agreed No   S1‑183518
    S1‑183167 Unique addressing of MCX Users when using functional alias Union Inter. Chemins de Fer CR Approval Yes
Yes
 		revised No S1‑183515  
    S1‑183515 Unique addressing of MCX Users when using functional alias Union Inter. Chemins de Fer CR Approval Yes
Yes
 		revised No S1‑183543 S1‑183167
    S1‑183543 Unique addressing of MCX Users when using functional alias Union Inter. Chemins de Fer CR Approval Yes
Yes
 		agreed No   S1‑183515
    S1‑183225 Add a requirement for covering the requirement [9.12.5-001] of 22.889 Hansung University, ETRI CR Approval Yes
Yes
 		revised No S1‑183519  
    S1‑183519 Add a requirement for covering the requirement [9.12.5-001] of 22.889 Hansung University, ETRI CR Approval No
Yes
 		withdrawn Yes   S1‑183225
    S1‑183226 Add a interworking requirement in 22.282 for covering the requirement [12.6-002] of 22.889 Hansung University, ETRI CR Approval Yes
Yes
 		revised No S1‑183520  
    S1‑183520 Add a interworking requirement in 22.282 for covering the requirement [12.6-002] of 22.889 Hansung University, ETRI CR Approval No
Yes
 		withdrawn Yes   S1‑183226
    S1‑183547 Not used Not used other discussion No
Yes
 		withdrawn Yes    
    S1‑183548 Not used Not used other discussion No
Yes
 		withdrawn Yes    
    S1‑183549 Not used Not used other discussion No
Yes
 		withdrawn Yes    
    S1‑183550 Not used Not used other discussion No
Yes
 		withdrawn Yes    
    S1‑183551 Not used Not used other discussion No
Yes
 		withdrawn Yes    
    S1‑183552 Not used Not used other discussion No
Yes
 		withdrawn Yes    
    S1‑183553 Not used Not used other discussion No
Yes
 		withdrawn Yes    
    S1‑183554 Not used Not used other discussion No
Yes
 		withdrawn Yes    
    S1‑183555 Not used Not used other discussion No
Yes
 		withdrawn Yes    
    S1‑183556 Not used Not used other discussion No
Yes
 		withdrawn Yes    
    S1‑183557 Not used Not used other discussion No
Yes
 		withdrawn Yes    
    S1‑183558 Not used Not used other discussion No
Yes
 		withdrawn Yes    
    S1‑183559 Not used Not used other discussion No
Yes
 		withdrawn Yes    
    S1‑183560 Not used Not used other discussion No
Yes
 		withdrawn Yes    
    S1‑183588 Not used Not used other discussion No
Yes
 		withdrawn Yes    
    S1‑183589 Not used Not used other discussion No
Yes
 		withdrawn Yes    
    S1‑183590 Not used Not used other discussion No
Yes
 		withdrawn Yes    
    S1‑183618 Dynamic Group Participation FirstNet CR discussion No
Yes
 		revised No S1‑183536  
    S1‑183536 Dynamic Group Participation FirstNet CR discussion Yes
Yes
 		revised No S1‑183542 S1‑183618
    S1‑183542 Dynamic Group Participation FirstNet CR discussion Yes
Yes
 		agreed No   S1‑183536
    S1‑183673 22.289 v.0.3.0 Rapporteur draft TR discussion Yes
Yes
 		agreed No    
    S1‑183674 Cover page for 22.289 v.1.0.0 Rapporteur TS or TR cover discussion Yes
Yes
 		agreed No    
7.3 SMARTER_Ph2: New Services and Markets Technology Enablers – Phase 2 [SP-180589] S1‑183115 Clause 7.2 alignment with other Rel-16 WIDs Nokia, Nokia Shanghai Bell, Vodafone CR   Yes
Yesone company supporting to improve the text while about 12 propose to delete completely. Huawei wondered why to keep the table in Rel-15 and not in Rel-16. The Chiar explained that it is because, in Rel-16, similar information can be found e.g. in 22.104.
 		revised No S1‑183612  
    S1‑183612 Clause 7.2 alignment with other Rel-16 WIDs Nokia, Nokia Shanghai Bell, Vodafone CR - Yes
YesThe deletion of the table supersedes the change on the table from another CR. This comment is no more needed since 3609 has been revised to remove the overlapping changes.
 		revised No S1‑183692 S1‑183115
    S1‑183692 Clause 7.2 alignment with other Rel-16 WIDs Nokia, Nokia Shanghai Bell, Vodafone CR - Yes
Yes
 		agreed No   S1‑183612
    S1‑183116 Editorial correction in header Nokia, Nokia Shanghai Bell CR   Yes
Yes
 		agreed No    
7.4 enIMS: enhancements to IMS for new real time communication services [SP-180137] S1‑183126 Discussion on IMS Slicing Futurewei Technologies discussion   Yes
YesFor Sony, this is the 3rd time this concept is presented, and their view, and assumably Nokia's view, did not change, so the meeting time should not be wasted in discussing this topic again. The Chair proposed a compromise solution where there are not "IMS slices" but "differenciated IMS". It is all a question of wording, and to know at which level the common part is done versus the differenciated parts. For Vodafone, there are pros but also cons in slicing the IMS: the IMS is to be used not only by 3GPP connectivity networks but also by other types of connectivity networks. For T-Mobile, there is no reason why the slicing principle should not apply also to IMS, since the slicing principle already gives the flexibility to chose which functions to differentiate from the ones which remains single. For Sony, the IMS supports the slicing principle by nature, it is just that it is not called "slicing". For Vodafone, there are APIs inside the IMS to enable to already support the concept. Telefonica supports the IMS slicing, and would agree to call it differently if this is the problem. For the Chair, the discussion is quite confused without going deeper in the topic. Huawei disagree that it can be done without changes to the standard. They explain that S2 state that they need S1 input, and S1 state that this is an S2 topic. KPN propose to send an LS to S2 to check if this is doable or not. Huawei wonder what "this" means in "this is doable", so Stage 1 should be defined. S1-183613 is given to draft an LS.
 		noted No    
    S1‑183613 Draft LS to SA2 on IMS Slicing Futurewei Technologies LS out - Yes
YesLS resulting from the discussion in S1-183126. SA1 is seen as been blocked by this question, where some companies think that nothing else is needed while some other think that extra standardisation work is needed. For Nokia, the complete topic is unclear. It looks like SA1 is not even clear on what the requirement is. For the Chair, the problem should remain within SA1 as much as possible, considering the SA2 workload and the fact that the requirement(s) are still not clear. It is too late to have it in Rel-16 since the Stage 1 completion is this present meeting. For Qualcomm, it is also too late for Rel-16, and anyway, some mecanisms are already in place which allow IMS flexibility. SA2 can be asked about the flexibiliy mecanisms already existing. For Huawei, it is worth sending the LS, even if removing the references to Rel-16. The chosen approach is to ask SA2 about the mecanism(s) already in place. Huawei propos to minute something like: If the answer is "no, it is not possible with present mechansims", then SA1 should focus in the future on clarifying the requirement rather than having again the discussion on possible impact/complexity on architecture and protocols.
 		revised No S1‑183633  
    S1‑183633 Draft LS to SA2 on IMS Slicing Futurewei Technologies LS out - Yes
YesA show of hands tells that 8 companies are in favour of sending an LS to SA2 while 13 companies are not in favour. The chairman noted that it appeared to be a consensus that a study item would be an appropriate way forward, but the SA1 delegates will have to see the actual WID before formally approve it.
 		noted No   S1‑183613
    S1‑183127 IMS Slicing CR to 22.261 China Mobile Com. Corporation CR Approval Yes
Yes
 		noted No    
7.5 QoS_MON: QoS Monitoring [SP-180141] S1‑183206 Update to Annex F for Network Diagnostics Futurewei Technologies CR Approval Yes
Yes
 		revised No S1‑183614  
    S1‑183614 Update to Annex F for Network Diagnostics Futurewei Technologies CR Approval Yes
Yes
 		revised No S1‑183635 S1‑183206
    S1‑183635 Update to Annex F for Network Diagnostics Futurewei Technologies CR Approval Yes
Yes
 		agreed No   S1‑183614
7.6 MARCOM: Maritime Communication Services over 3GPP System [SP-180327] S1‑183048 Requirement on the communication range between vessels SyncTechno Inc., Korean Register of shipping pCR Approval Yes
YesThe text is to be rewritten. The conversions to km can be skipped.
 		revised No S1‑183615  
    S1‑183615 Requirement on the communication range between vessels SyncTechno Inc., Korean Register of shipping pCR Approval Yes
YesIt was proposed to remove "antennas" from the requirements because not an SA1-aspect, but several companies support to have it.
 		agreed No   S1‑183048
    S1‑183049 Annex A in 3GPP TS 22.119 SyncTechno Inc., Korean Register of shipping pCR Approval Yes
YesA CR would be proposed on this basis, in S1-183616.
 		noted No    
    S1‑183616 CR on Status of existing and future communication technologies used for ship to shore and ship to ship communication SyncTechno Inc. CR discussion Yes
Yes
 		revised No S1‑183636  
    S1‑183636 CR on Status of existing and future communication technologies used for ship to shore and ship to ship communication SyncTechno Inc. CR discussion No
Yes
 		agreed No   S1‑183616
    S1‑183050 Presentation of Spec 22.119 V2.0.0 to TSG SA for approval SyncTechno Inc. (Rapporteur) TS or TR cover Approval Yes
Yes
 		agreed No    
    S1‑183275 TS22.119v1.1.0 to include agreements at this meeting Rapporteur draft TS discussion Yes
Yes
 		agreed No    
7.7 cyberCAV: cyberCAV [SP-180585] S1‑183276 TS22.104v0.3.0 to include agreements at this meeting Rapporteur draft TS discussion No
YesTO be sent by the rapporteur on 20th Nov, final version on 23rd Nov.
 		agreed No    
    S1‑183277 Cover page for presentation of TS22.104v1.0.0 Rapporteur TS or TR cover discussion Yes
Yes
 		agreed No    
    S1‑183359 Not used Not used other discussion No
Yes
 		withdrawn Yes    
    S1‑183367 5GLAN – BAsic considerations TNO other discussion Yes
Yes
 		noted No    
    S1‑183381 Not used Not used other discussion No
Yes
 		withdrawn Yes    
    S1‑183408 Not used Not used other discussion No
Yes
 		withdrawn Yes    
    S1‑183409 Not used Not used other discussion No
Yes
 		withdrawn Yes    
    S1‑183410 Not used Not used other discussion No
Yes
 		withdrawn Yes    
    S1‑183411 Not used Not used other discussion No
Yes
 		withdrawn Yes    
    S1‑183412 Not used Not used other discussion No
Yes
 		withdrawn Yes    
    S1‑183413 Not used Not used other discussion No
Yes
 		withdrawn Yes    
    S1‑183414 Not used Not used other discussion No
Yes
 		withdrawn Yes    
    S1‑183415 Not used Not used other discussion No
Yes
 		withdrawn Yes    
    S1‑183416 Not used Not used other discussion No
Yes
 		withdrawn Yes    
    S1‑183417 Not used Not used other discussion No
Yes
 		withdrawn Yes    
    S1‑183418 Not used Not used other discussion No
Yes
 		withdrawn Yes    
    S1‑183419 Not used Not used other discussion No
Yes
 		withdrawn Yes    
    S1‑183420 Not used Not used other discussion No
Yes
 		withdrawn Yes    
    S1‑183421 Not used Not used other discussion No
Yes
 		withdrawn Yes    
    S1‑183422 Not used Not used other discussion No
Yes
 		withdrawn Yes    
    S1‑183423 Not used Not used other discussion No
Yes
 		withdrawn Yes    
    S1‑183424 Not used Not used other discussion No
Yes
 		withdrawn Yes    
    S1‑183425 Not used Not used other discussion No
Yes
 		withdrawn Yes    
    S1‑183426 Not used Not used other discussion No
Yes
 		withdrawn Yes    
    S1‑183427 Not used Not used other discussion No
Yes
 		withdrawn Yes    
    S1‑183428 Not used Not used other discussion No
Yes
 		withdrawn Yes    
    S1‑183429 Not used Not used other discussion No
Yes
 		withdrawn Yes    
    S1‑183430 Not used Not used other discussion No
No
 		Withdrawn Yes    
7.7.1 22.104 pCRs– new content S1‑183109 Performance KPIs for TS 22.104 Nokia, Nokia Shanghai Bell, Siemens AG pCR   Yes
Yes
 		withdrawn Yes S1‑183316  
    S1‑183316 Performance KPIs for TS 22.104 Nokia, Nokia Shanghai Bell, Siemens AG pCR - Yes
Yes
 		withdrawn Yes S1‑183354 S1‑183109
    S1‑183354 Performance KPIs for TS 22.104 Nokia, Nokia Shanghai Bell, Siemens AG pCR - Yes
Yes
 		withdrawn Yes S1‑183400 S1‑183316
    S1‑183400 Performance KPIs for TS 22.104 Nokia, Nokia Shanghai Bell, Siemens AG pCR - Yes
Yes
 		agreed No   S1‑183354
    S1‑183110 Descriptive text for overview clause of TS 22.104 Nokia, Nokia Shanghai Bell, Siemens AG, Vodafone, Qualcomm pCR   Yes
Yes
 		revised No S1‑183351  
    S1‑183351 Descriptive text for overview clause of TS 22.104 Nokia, Nokia Shanghai Bell, Siemens AG, Vodafone, Qualcomm pCR - Yes
Yes
 		agreed No   S1‑183110
    S1‑183111 Restructure of 22.104 Nokia, Nokia Shanghai Bell pCR   Yes
YesMerged into S1-183352
 		revised No S1‑183352  
    S1‑183352 Restructure of 22.104 Nokia, Nokia Shanghai Bell pCR - Yes
Yes
 		revised No S1‑183634 S1‑183111
    S1‑183634 Restructure of 22.104 Nokia, Nokia Shanghai Bell pCR - Yes
Yes
 		agreed No   S1‑183352
    S1‑183114 Clarification of TSN requirements in TS 22.104 Nokia, Nokia Shanghai Bell pCR   Yes
Yes
 		revised No S1‑183358  
    S1‑183358 Clarification of TSN requirements in TS 22.104 Nokia, Nokia Shanghai Bell pCR - Yes
Yes
 		revised No S1‑183402 S1‑183114
    S1‑183402 Clarification of TSN requirements in TS 22.104 Nokia, Nokia Shanghai Bell pCR - Yes
Yes
 		agreed No   S1‑183358
    S1‑183119 Update of TSN requirement Siemens AG, Qualcomm, Nokia, Nokia Shanghai Bell pCR Agreement Yes
Yes
 		revised No S1‑183356  
    S1‑183356 Update of TSN requirement Siemens AG, Qualcomm, Nokia, Nokia Shanghai Bell pCR Agreement Yes
Yes
 		agreed No   S1‑183119
    S1‑183120 cyberCAV - 5G in Industrial Automation - Different and Multiple Time Domains for Synchronization Siemens AG, Nokia, Nokia Shanghai Bell pCR Agreement Yes
Yes
 		revised No S1‑183329  
    S1‑183329 cyberCAV - 5G in Industrial Automation - Different and Multiple Time Domains for Synchronization Siemens AG, Nokia, Nokia Shanghai Bell pCR Agreement Yes
Yes
 		revised No S1‑183357 S1‑183120
    S1‑183357 cyberCAV - 5G in Industrial Automation - Different and Multiple Time Domains for Synchronization Siemens AG, Nokia, Nokia Shanghai Bell pCR Agreement Yes
Yes
 		revised No S1‑183640 S1‑183329
    S1‑183640 cyberCAV - 5G in Industrial Automation - Different and Multiple Time Domains for Synchronization Siemens AG, Nokia, Nokia Shanghai Bell pCR Agreement Yes
Yes
 		revised No S1‑183668 S1‑183357
    S1‑183668 cyberCAV - 5G in Industrial Automation - Different and Multiple Time Domains for Synchronization Siemens AG, Nokia, Nokia Shanghai Bell pCR Agreement Yes
Yes
 		agreed No   S1‑183640
    S1‑183134 network performance: Communication service availability HuaWei Technologies Co., Ltd pCR Approval Yes
Yes
 		revised No S1‑183361  
    S1‑183361 network performance: Communication service availability HuaWei Technologies Co., Ltd pCR Approval Yes
Yes
 		revised No S1‑183403 S1‑183134
    S1‑183403 network performance: Communication service availability HuaWei Technologies Co., Ltd pCR Approval Yes
Yes
 		revised No S1‑183641 S1‑183361
    S1‑183641 network performance: Communication service availability HuaWei Technologies Co., Ltd pCR Approval Yes
Yes
 		agreed No   S1‑183403
    S1‑183170 cyberCAV – Network performance requirements Siemens AG pCR Agreement Yes
Yes
 		noted No    
    S1‑183183 cyberCAV (Editorial) - Move of Service Requirements to clause 5 Siemens AG pCR   Yes
YesMerged into S1-183352
 		merged No    
    S1‑183188 cyberCAV – 22.104 – summary of service performance requirements Siemens AG, China Telecom pCR Agreement Yes
Yes
 		revised No S1‑183338  
    S1‑183338 cyberCAV – 22.104 – summary of service performance requirements Siemens AG, China Telecom pCR Agreement Yes
Yes
 		revised No S1‑183355 S1‑183188
    S1‑183355 cyberCAV – 22.104 – summary of service performance requirements Siemens AG, China Telecom pCR Agreement Yes
Yes
 		revised No S1‑183401 S1‑183338
    S1‑183401 cyberCAV – 22.104 – summary of service performance requirements Siemens AG, China Telecom pCR Agreement Yes
Yes
 		agreed No   S1‑183355
    S1‑183191 cyberCAV - Communication service terminology w.r.t. 5G network and vertical applications Siemens AG pCR Agreement Yes
Yes
 		revised No S1‑183362  
    S1‑183362 cyberCAV - Communication service terminology w.r.t. 5G network and vertical applications Siemens AG pCR Agreement Yes
Yes
 		revised No S1‑183404 S1‑183191
    S1‑183404 cyberCAV - Communication service terminology w.r.t. 5G network and vertical applications Siemens AG pCR Agreement Yes
Yes
 		agreed No   S1‑183362
    S1‑183207 22.104 - Clock synchronisation across 5G networks Ericsson pCR Agreement Yes
Yes
 		revised No S1‑183360  
    S1‑183360 22.104 - Clock synchronisation across 5G networks Ericsson pCR Agreement Yes
Yes
 		agreed No   S1‑183207
    S1‑183219 cyberCAV – TS 22.104 – Considerations on communication service interface Siemens AG pCR Agreement Yes
Yes
 		revised No S1‑183348  
    S1‑183348 cyberCAV – TS 22.104 – Considerations on communication service interface Siemens AG pCR Agreement Yes
Yes
 		revised No S1‑183363 S1‑183219
    S1‑183363 cyberCAV – TS 22.104 – Considerations on communication service interface Siemens AG CR Agreement Yes
Yes
 		agreed No   S1‑183348
    S1‑183353 Terminology alignment Nokia other discussion No
Yes
 		withdrawn Yes    
7.7.2 22.261 CRs – new requirements and updates S1‑183112 Discussion on normative cyberCAV security requirements Nokia, Nokia Shanghai Bell discussion   Yes
Yes
 		noted No    
    S1‑183113 Support for security requirements based on FS_CAV Nokia, Nokia Shanghai Bell, Siemens AG CR   Yes
Yes
 		revised No S1‑183364  
    S1‑183364 Support for security requirements based on FS_CAV Nokia, Nokia Shanghai Bell, Siemens AG CR - Yes
Yes
 		revised No S1‑183405 S1‑183113
    S1‑183405 Support for security requirements based on FS_CAV Nokia, Nokia Shanghai Bell, Siemens AG CR - Yes
Yes
 		agreed No   S1‑183364
    S1‑183121 Replacing private network with non-public network ETRI CR Agreement Yes
Yes
 		revised No S1‑183366  
    S1‑183366 Replacing private network with non-public network ETRI CR Agreement Yes
Yes
 		revised No S1‑183406 S1‑183121
    S1‑183406 Replacing private network with non-public network ETRI CR Agreement Yes
Yes
 		agreed No   S1‑183366
    S1‑183128 cyberCAV discussion about network selection China Mobile Com. Corporation discussion   Yes
Yes
 		noted No    
    S1‑183129 CR22.261v16.5.0 network selection for cyberCAV China Mobile Com. Corporation CR   Yes
Yes
 		revised No S1‑183393  
    S1‑183393 CR22.261v16.5.0 network selection for cyberCAV China Mobile Com. Corporation CR - No
Yes
 		withdrawn Yes   S1‑183129
    S1‑183145 Access Control for the Non-Public Network Intel CR Approval Yes
Yes
 		noted No    
    S1‑183155 CR on Requirement of UAC for Non-Public Networks Tencent CR Approval Yes
Yes
 		noted No    
    S1‑183157 Discussion on Requirement of UAC for Non-Public Networks Tencent discussion Agreement Yes
Yes
 		noted No    
    S1‑183161 Introduction of cyberCAV Vodafone Romania S.A. CR   Yes
Yes
 		agreed No    
    S1‑183163 Draft LS to SA2 on UAC Requirement for NPN Tencent LS out Approval Yes
Yes
 		withdrawn Yes    
    S1‑183189 cyberCAV - network interaction requirement for uninterrupted real-time video Siemens AG CR   Yes
Yes
 		revised No S1‑183365  
    S1‑183365 cyberCAV - network interaction requirement for uninterrupted real-time video Siemens AG CR - Yes
Yes
 		revised No S1‑183407 S1‑183189
    S1‑183407 cyberCAV - network interaction requirement for uninterrupted real-time video Siemens AG CR - Yes
Yes
 		agreed No   S1‑183365
    S1‑183190 cyberCAV – Network interaction requirement for uninterrupted real-time video Siemens AG discussion   Yes
Yes
 		noted No    
    S1‑183213 Clarification on non-public network and private network in TS 22.261 ETRI discussion Decision Yes
Yes
 		noted No    
    S1‑183215 Description of deployment options for non-public networks Siemens AG discussion Discussion Yes
Yes
 		revised No S1‑183332  
    S1‑183332 Description of deployment options for non-public networks Siemens AG discussion Discussion Yes
Yes
 		revised No S1‑183394 S1‑183215
    S1‑183394 Description of deployment options for non-public networks Siemens AG discussion Discussion Yes
Yes
 		noted No   S1‑183332
    S1‑183651 Move of KPIs for wireless RSU-TCC backhaul to 7.2.3 Siemens AG, Nokia, Nokia Shanghai Bell CR discussion Yes
Yes
 		revised No S1‑183690  
    S1‑183690 Move of KPIs for wireless RSU-TCC backhaul to 7.2.3 Siemens AG, Nokia, Nokia Shanghai Bell CR discussion Yes
YesWrong number for the table header. Cover page to be update (clauses affected).
 		revised No S1‑183708 S1‑183651
    S1‑183708 Move of KPIs for wireless RSU-TCC backhaul to 7.2.3 Siemens AG, Nokia, Nokia Shanghai Bell CR discussion Yes
Yes
 		agreed No   S1‑183690
7.7.3 22.104 pCRs – editorial / informational S1‑183122 Removal of CRC from abbreviation list ETRI pCR Agreement Yes
Yes
 		agreed No    
    S1‑183199 cyberCAV - Update of 22.104 Annex C – Characterising communication services Siemens AG pCR   Yes
Yes
 		revised No S1‑183331  
    S1‑183331 cyberCAV - Update of 22.104 Annex C – Characterising communication services Siemens AG pCR - Yes
Yes
 		revised No S1‑183395 S1‑183199
    S1‑183395 cyberCAV - Update of 22.104 Annex C – Characterising communication services Siemens AG pCR - Yes
Yes
 		agreed No   S1‑183331
7.8 5GSAT: Integration of Satellite Access in 5G [SP-180326] S1‑183025 Performance requirements for satellite access THALES CR Agreement Yes
YesSony does not agree with the idea that the performance of the system is different with different types of access network. For the Chair, this is legitimate. For Sony, the best approch is to add row(s) to the table, not to add notes. This is an agreeable approach.
 		revised No S1‑183617  
    S1‑183617 Performance requirements for satellite access THALES CR Agreement No
Yes
 		withdrawn Yes   S1‑183025
7.9 5G_HYPOS: 5G Positioning Services [SP-180329] S1‑183088 Editorial correction for positioning-related tables in 7.3.2 LG Electronics Inc. CR   Yes
Yes
 		revised No S1‑183095  
    S1‑183095 Editorial correction for positioning-related tables in 7.3.2 LG Electronics Mobile Research CR   No
Yes
 		withdrawn Yes   S1‑183088
    S1‑183168 Clarification of requirement on energy per fix in clause 7.3.2.3 ESA CR Approval Yes
Yes
 		revised No S1‑183450  
    S1‑183450 Clarification of requirement on energy per fix in clause 7.3.2.3 ESA CR Approval Yes
Yes
 		revised No S1‑183696 S1‑183168
    S1‑183696 Clarification of requirement on energy per fix in clause 7.3.2.3 ESA CR Approval Yes
Yes
 		agreed No   S1‑183450
    S1‑183169 Functional requirements for 5G positioning services (clause 6) ESA CR Approval Yes
Yes
 		revised No S1‑183451  
    S1‑183451 Functional requirements for 5G positioning services (clause 6) ESA CR Approval Yes
Yes
 		revised No S1‑183471 S1‑183169
    S1‑183471 Functional requirements for 5G positioning services (clause 6) ESA CR Approval Yes
Yes
 		agreed No   S1‑183451
    S1‑183242 Very accurate positioning in support of precision agriculture NOVAMINT CR Agreement Yes
Yes
 		revised No S1‑183452  
    S1‑183452 Very accurate positioning in support of precision agriculture NOVAMINT CR Agreement Yes
YesSome companies do not see the need for this.
 		noted No   S1‑183242
    S1‑183474 Not used Not used other discussion No
No
 		withdrawn Yes    
    S1‑183475 Not used Not used other discussion No
Yes
 		withdrawn Yes    
    S1‑183476 Not used Not used other discussion No
Yes
 		withdrawn Yes    
    S1‑183477 Not used Not used other discussion No
Yes
 		withdrawn Yes    
    S1‑183478 Not used Not used other discussion No
Yes
 		withdrawn Yes    
    S1‑183479 Not used Not used other discussion No
Yes
 		withdrawn Yes    
    S1‑183480 Not used Not used other discussion No
Yes
 		withdrawn Yes    
    S1‑183481 Not used Not used other discussion No
Yes
 		withdrawn Yes    
    S1‑183482 Not used Not used other discussion No
Yes
 		withdrawn Yes    
    S1‑183483 Not used Not used other discussion No
Yes
 		withdrawn Yes    
    S1‑183484 Not used Not used other discussion No
Yes
 		withdrawn Yes    
    S1‑183485 Not used Not used other discussion No
Yes
 		withdrawn Yes    
    S1‑183486 Not used Not used other discussion No
Yes
 		withdrawn Yes    
    S1‑183487 Not used Not used other discussion No
Yes
 		withdrawn Yes    
    S1‑183488 Not used Not used other discussion No
Yes
 		withdrawn Yes    
    S1‑183489 Not used Not used other discussion No
Yes
 		withdrawn Yes    
    S1‑183490 Not used Not used other discussion No
Yes
 		withdrawn Yes    
    S1‑183491 Not used Not used other discussion No
Yes
 		withdrawn Yes    
    S1‑183492 Not used Not used other discussion No
Yes
 		withdrawn Yes    
    S1‑183493 Not used Not used other discussion No
Yes
 		withdrawn Yes    
    S1‑183494 Not used Not used other discussion No
Yes
 		withdrawn Yes    
    S1‑183495 Not used Not used other discussion No
Yes
 		withdrawn Yes    
    S1‑183496 Not used Not used other discussion No
Yes
 		withdrawn Yes    
    S1‑183497 Not used Not used other discussion No
Yes
 		withdrawn Yes    
    S1‑183498 Not used Not used other discussion No
Yes
 		withdrawn Yes    
    S1‑183499 Not used Not used other discussion No
Yes
 		withdrawn Yes    
    S1‑183500 Not used Not used other discussion No
Yes
 		withdrawn Yes    
    S1‑183501 Not used Not used other discussion No
Yes
 		withdrawn Yes    
    S1‑183502 Not used Not used other discussion No
Yes
 		withdrawn Yes    
    S1‑183503 Not used Not used other discussion No
Yes
 		withdrawn Yes    
    S1‑183504 Not used Not used other discussion No
Yes
 		withdrawn Yes    
    S1‑183505 Not used Not used other discussion No
Yes
 		withdrawn Yes    
    S1‑183506 Not used Not used other discussion No
Yes
 		withdrawn Yes    
    S1‑183507 Not used Not used other discussion No
Yes
 		withdrawn Yes    
    S1‑183508 Not used Not used other discussion No
Yes
 		withdrawn Yes    
    S1‑183509 Not used Not used other discussion No
Yes
 		withdrawn Yes    
    S1‑183510 Not used Not used other discussion No
Yes
 		withdrawn Yes    
7.10 MuD: Multi-device and Multi-identity [SP-180315]                      
7.11 5GLAN: LAN support in 5G [SP-180593] S1‑183124 5G LAN- discussion about enabling disabling UE from 5G-LAN based on location China Mobile Com. Corporation discussion Discussion Yes
Yes
 		noted No    
    S1‑183125 5GLAN requirements about enabling disabling UE from 5G-LAN based on location China Mobile Com. Corporation CR   Yes
Yes
 		revised No S1‑183368  
    S1‑183368 5GLAN requirements about enabling disabling UE from 5G-LAN based on location China Mobile Com. Corporation CR - Yes
Yes
 		revised No S1‑183390 S1‑183125
    S1‑183390 5GLAN requirements about enabling disabling UE from 5G-LAN based on location China Mobile Com. Corporation CR - Yes
YesRelease missing on the cover page. Changes on changes to be removed. Further edited online.
 		revised No S1‑183644 S1‑183368
    S1‑183644 5GLAN requirements about enabling disabling UE from 5G-LAN based on location China Mobile Com. Corporation CR - Yes
YesWrong file uploaded by the author
 		revised No S1‑183697 S1‑183390
    S1‑183697 5GLAN requirements about enabling disabling UE from 5G-LAN based on location China Mobile Com. Corporation CR - Yes
Yes
 		agreed No   S1‑183644
    S1‑183133 5G LAN-type service support connected to wired Ethernet KDDI Corporation CR Agreement Yes
Yes
 		revised No S1‑183266  
    S1‑183266 Clarification on Ethernet transport services KDDI Corporation CR Agreement Yes
Yes
 		revised No S1‑183369 S1‑183133
    S1‑183369 Clarification on Ethernet transport services KDDI Corporation CR Agreement Yes
Yes
 		agreed No   S1‑183266
    S1‑183195 Addittion to definition on private communication TNO CR   Yes
Yes
 		revised No S1‑183343  
    S1‑183343 Addittion to definition on private communication TNO CR - Yes
Yes
 		revised No S1‑183370 S1‑183195
    S1‑183370 Addittion to definition on private communication TNO CR - Yes
Yes
 		agreed No   S1‑183343
    S1‑183196 Update of 5GLAN - General TNO CR   Yes
Yes
 		revised No S1‑183344  
    S1‑183344 Update of 5GLAN - General TNO CR - Yes
Yes
 		revised No S1‑183371 S1‑183196
    S1‑183371 Update of 5GLAN - General TNO CR - Yes
Yes
 		agreed No   S1‑183344
    S1‑183197 Update of 5G LAN - virtual network (5G LAN-VN). TNO CR   Yes
Yes
 		revised No S1‑183345  
    S1‑183345 Update of 5G LAN - virtual network (5G LAN-VN). TNO CR - Yes
Yes
 		revised No S1‑183372 S1‑183197
    S1‑183372 Update of 5G LAN - virtual network (5G LAN-VN). TNO CR - Yes
Yes
 		agreed No   S1‑183345
    S1‑183198 Update of 5GLAN - Creation and management TNO CR   Yes
Yes
 		revised No S1‑183346  
    S1‑183346 Update of 5GLAN - Creation and management TNO CR - Yes
Yes
 		revised No S1‑183373 S1‑183198
    S1‑183373 Update of 5GLAN - Creation and management TNO CR - Yes
Yes
 		revised No S1‑183386 S1‑183346
    S1‑183386 Update of 5GLAN - Creation and management TNO CR - Yes
Yes
 		agreed No   S1‑183373
    S1‑183200 Update of 5GLAN – Privacy TNO CR   Yes
Yes
 		revised No S1‑183347  
    S1‑183347 Update of 5GLAN – Privacy TNO CR - Yes
Yes
 		revised No S1‑183374 S1‑183200
    S1‑183374 Update of 5GLAN – Privacy TNO CR - Yes
Yes
 		revised No S1‑183387 S1‑183347
    S1‑183387 Update of 5GLAN – Privacy TNO CR - Yes
Yes
 		revised No S1‑183392 S1‑183374
    S1‑183392 Update of 5GLAN – Privacy TNO CR - Yes
YesOne typo to be corrected.
 		revised No S1‑183646 S1‑183387
    S1‑183646 Update of 5GLAN – Privacy TNO CR - Yes
Yes
 		agreed No   S1‑183392
    S1‑183201 Update of 5GLAN – Discovery TNO CR   Yes
Yes
 		revised No S1‑183267  
    S1‑183267 Update of 5GLAN – Discovery TNO CR - Yes
Yes
 		revised No S1‑183375 S1‑183201
    S1‑183375 Update of 5GLAN – Discovery TNO CR - Yes
Yes
 		revised No S1‑183388 S1‑183267
    S1‑183388 Update of 5GLAN – Discovery TNO CR - Yes
YesWrong CR number on the cover page.
 		revised No S1‑183645 S1‑183375
    S1‑183645 Update of 5GLAN – Discovery TNO CR - Yes
Yes
 		agreed No   S1‑183388
    S1‑183202 Update of 5GLAN – Indirect Communication Mode TNO CR   Yes
Yes
 		agreed No    
    S1‑183203 Update of 5GLAN – Service exposure TNO CR   Yes
Yes
 		revised No S1‑183376  
    S1‑183376 Update of 5GLAN – Service exposure TNO CR - Yes
Yes
 		agreed No   S1‑183203
    S1‑183204 Update of 5GLAN – Security TNO CR   Yes
Yes
 		revised No S1‑183377  
    S1‑183377 Update of 5GLAN – Security TNO CR - Yes
Yes
 		revised No S1‑183389 S1‑183204
    S1‑183389 Update of 5GLAN – Security TNO CR - Yes
Yes
 		agreed No   S1‑183377
    S1‑183205 5G LAN- CRs explanation TNO discussion   Yes
Yes
 		noted No    
    S1‑183378 CR22.261v16.5.0: Editorial clean-up of 5GLAN KPN other discussion Yes
Yes
 		withdrawn Yes    
7.12 ID_UAS: Remote Identification of Unmanned Aerial Systems [SP-180771] S1‑183026 pCR to 22.125 for configuring the UTM SHARP Corporation pCR Agreement No
Yes
 		withdrawn Yes    
    S1‑183135 Proposal for normative ID_UAS general requirements HuaWei Technologies Co., Ltd pCR Approval Yes
Yes
 		revised No S1‑183432  
    S1‑183432 Proposal for normative ID_UAS general requirements HuaWei Technologies Co., Ltd pCR Approval Yes
Yes
 		revised No S1‑183672 S1‑183135
    S1‑183672 Proposal for normative ID_UAS general requirements HuaWei Technologies Co., Ltd pCR Approval Yes
Yes
 		agreed No   S1‑183432
    S1‑183232 ID_UAS - Introduction Qualcomm Incorporated pCR Agreement Yes
Yes
 		agreed No    
    S1‑183233 ID_UAS - Scope Qualcomm Incorporated pCR Agreement Yes
Yes
 		agreed No    
    S1‑183234 ID_UAS - Overview of UAS Qualcomm Incorporated pCR Agreement Yes
Yes
 		revised No S1‑183431  
    S1‑183431 ID_UAS - Overview of UAS Qualcomm Incorporated pCR Agreement Yes
Yes
 		agreed No   S1‑183234
    S1‑183235 ID_UAS - General Requirements Qualcomm Incorporated pCR Agreement Yes
Yes
 		withdrawn Yes    
    S1‑183236 ID_UAS - Centralised UAV traffic management requirements Qualcomm Incorporated pCR Agreement Yes
Yes
 		revised No S1‑183433  
    S1‑183433 ID_UAS - Centralised UAV traffic management requirements Qualcomm Incorporated pCR Agreement Yes
Yes
 		revised No S1‑183466 S1‑183236
    S1‑183466 ID_UAS - Centralised UAV traffic management requirements Qualcomm Incorporated pCR Agreement Yes
Yes
 		agreed No   S1‑183433
    S1‑183237 ID_UAS - Decentralised UAV traffic management requirements requirements Qualcomm Incorporated pCR Agreement Yes
Yes
 		revised No S1‑183434  
    S1‑183434 ID_UAS - Decentralised UAV traffic management requirements requirements Qualcomm Incorporated pCR Agreement Yes
Yes
 		agreed No   S1‑183237
    S1‑183238 ID_UAS - Security requirements Qualcomm Incorporated pCR Agreement Yes
Yes
 		revised No S1‑183435  
    S1‑183435 ID_UAS - Security requirements Qualcomm Incorporated pCR Agreement Yes
Yes
 		revised No S1‑183467 S1‑183238
    S1‑183467 ID_UAS - Security requirements Qualcomm Incorporated pCR Agreement Yes
Yes"support lawful interception": it has to be made more generic and said "it has to support regulatory requirements, e.g. LI". The Note on Non-repudiation seems to contradict the requirement just above.
 		revised No S1‑183675 S1‑183435
    S1‑183675 ID_UAS - Security requirements Qualcomm Incorporated pCR Agreement Yes
Yes
 		agreed No   S1‑183467
    S1‑183278 TS22.125v0.2.0 to include agreements at this meeting Rapporteur draft TS discussion Yes
Yes
 		agreed No    
    S1‑183279 Cover page for presentation of TS22.125v1.0.0 Rapporteur TS or TR cover discussion Yes
Yes
 		agreed No    
7.13 MSGin5G: Message service with 5G system requirements [SP-180920] S1‑183038 TS 22.262 skeleton China Mobile (Hangzhou) Inf. pCR   Yes
Yes
 		agreed No    
    S1‑183039 TS 22.262 overview China Mobile (Hangzhou) Inf. pCR   Yes
Yes
 		revised No S1‑183453  
    S1‑183453 TS 22.262 overview China Mobile (Hangzhou) Inf. pCR - Yes
Yes
 		revised No S1‑183472 S1‑183039
    S1‑183472 TS 22.262 overview China Mobile (Hangzhou) Inf. pCR - Yes
Yes
 		agreed No   S1‑183453
    S1‑183040 TS 22.262 service requirements China Mobile (Hangzhou) Inf. pCR   Yes
Yes
 		revised No S1‑183457  
    S1‑183457 TS 22.262 service requirements China Mobile (Hangzhou) Inf. pCR - Yes
Yes
 		agreed No   S1‑183040
    S1‑183041 TS 22.262 charging security and other requirments China Mobile (Hangzhou) Inf. pCR   Yes
Yes
 		revised No S1‑183454  
    S1‑183454 TS 22.262 charging security and other requirments China Mobile (Hangzhou) Inf. pCR - Yes
Yes
 		agreed No   S1‑183041
    S1‑183087 MSGin5G requirements on the 5G system China Mobile (Hangzhou) Inf. CR   Yes
Yes
 		revised No S1‑183455  
    S1‑183455 MSGin5G requirements on the 5G system China Mobile (Hangzhou) Inf. CR - Yes
Yes
 		agreed No   S1‑183087
    S1‑183096 5GMSG of TS 22.262 Abbreviations China Unicom pCR Approval Yes
Yes
 		agreed No    
    S1‑183097 5GMSG of TS 22.262 Definitions China Unicom pCR Approval Yes
Yes
 		revised No S1‑183456  
    S1‑183456 5GMSG of TS 22.262 Definitions China Unicom pCR Approval Yes
Yes
 		agreed No   S1‑183097
    S1‑183136 Cover page for presentation of TS 22.262 China Mobile (Hangzhou) Inf. TS or TR cover   Yes
YesOne step approval to be mentioned.
 		revised No S1‑183698  
    S1‑183698 Cover page for presentation of TS 22.262 China Mobile (Hangzhou) Inf. TS or TR cover - Yes
Yes
 		agreed No   S1‑183136
    S1‑183137 TS22.262 V0.1.0 to include agreements at this meeting China Mobile (Hangzhou) Inf. draft TS   Yes
Yes
 		agreed No    
    S1‑183141 Service requirements in support of RDS in 5GMSG Intel, China Mobile CR Approval Yes
Yes
 		noted No    
    S1‑183152 MSGin5G performance requirement for application originated messaging. Sony Corporation pCR Agreement Yes
Yes
 		agreed No    
    S1‑183153 Application originated messageing for IOT sensors Sony, China Mobile CR Agreement Yes
Yes
 		revised No S1‑183458  
    S1‑183458 Application originated messageing for IOT sensors Sony, China Mobile CR Agreement No
Yes
 		withdrawn Yes   S1‑183153
7.14 BRMNS: Business Role Models for Network Slicing [SP-180774] S1‑183017 Correction to BRMNS requirements LG Electronics Inc. CR Agreement Yes
Yes
 		revised No S1‑183459  
    S1‑183459 Correction to BRMNS requirements LG Electronics Inc. CR Agreement Yes
Yes
 		revised No S1‑183637 S1‑183017
    S1‑183637 Correction to BRMNS requirements LG Electronics Inc. CR Agreement Yes
YesSome formatting problems
 		revised No S1‑183642 S1‑183459
    S1‑183642 Correction to BRMNS requirements LG Electronics Inc. CR Agreement Yes
Yes
 		agreed No   S1‑183637
    S1‑183100 Discussion on completion of normative BRMNS requirements Nokia, Nokia Shanghai Bell discussion   Yes
Yes
 		revised No S1‑183315  
    S1‑183315 Discussion on completion of normative BRMNS requirements Nokia, Nokia Shanghai Bell discussion - Yes
Yes
 		noted No   S1‑183100
    S1‑183101 Enhanced network slice requirements based on business role models Nokia, Nokia Shanghai Bell CR   Yes
Yes
 		revised No S1‑183460  
    S1‑183460 Enhanced network slice requirements based on business role models Nokia, Nokia Shanghai Bell CR - Yes
Yes
 		revised No S1‑183473 S1‑183101
    S1‑183473 Enhanced network slice requirements based on business role models Nokia, Nokia Shanghai Bell CR - Yes
Yes
 		agreed No   S1‑183460
    S1‑183146 Review and Proposal for Service Requirements of FS_BMNS Intel discussion Agreement Yes
Yes
 		noted No    
    S1‑183147 Service requirements for Business Roles of Network Slice Intel CR Approval Yes
Yes
 		revised No S1‑183461  
    S1‑183461 Service requirements for Business Roles of Network Slice Intel CR Approval No
Yes
 		withdrawn Yes   S1‑183147
    S1‑183239 Adding the description about a private slice for Network capability exposure ETRI CR Approval Yes
Yes
 		revised No S1‑183468  
    S1‑183468 Adding the description about a private slice for Network capability exposure ETRI CR Approval No
Yes
 		withdrawn Yes   S1‑183239
    S1‑183240 Update the requirements about a private slice for Network capability exposure ETRI CR   Yes
YesV/NF is not defined. Nokia and T-Mobile do not think this is needed.
 		noted No S1‑183469  
    S1‑183469 Update the requirements about a private slice for Network capability exposure ETRI CR - Yes
Yes
 		noted No   S1‑183240
8 Study Item contributions                      
8.1 Rel-16 CRs for completed study items S1‑183099 Completion of consolidation potential requirements Nokia, Nokia Shanghai Bell CR   Yes
Yes
 		agreed No    
    S1‑183184 Clean-up of clause 4.3 and batch processing Siemens AG CR Agreement Yes
Yes
 		revised No S1‑183396  
    S1‑183396 Clean-up of clause 4.3 and batch processing Siemens AG CR Agreement Yes
Yes
 		agreed No   S1‑183184
    S1‑183185 Update to TR 22.804 clause 5.6 Siemens AG CR Agreement Yes
Yes
 		revised No S1‑183397  
    S1‑183397 Update to TR 22.804 clause 5.6 Siemens AG CR Agreement Yes
Yes
 		agreed No   S1‑183185
    S1‑183186 TR 22.804 - General editorial corrections Siemens AG CR Agreement Yes
Yes
 		revised No S1‑183330  
    S1‑183330 TR 22.804 - General editorial corrections Siemens AG CR Agreement Yes
Yes
 		revised No S1‑183399 S1‑183186
    S1‑183399 TR 22.804 - General editorial corrections Siemens AG CR Agreement Yes
Yes
 		agreed No   S1‑183330
    S1‑183227 Discussion on resolution of editor’s notes in TR 22.804 Siemens AG discussion   Yes
Yes
 		revised No S1‑183333  
    S1‑183333 Discussion on resolution of editor’s notes in TR 22.804 Siemens AG discussion - Yes
Yes
 		noted No   S1‑183227
    S1‑183228 Resolution of editor’s notes in TR 22.804 Siemens AG CR Agreement Yes
Yes
 		revised No S1‑183334  
    S1‑183334 Resolution of editor’s notes in TR 22.804 Siemens AG CR Agreement Yes
Yes
 		revised No S1‑183398 S1‑183228
    S1‑183398 Resolution of editor’s notes in TR 22.804 Siemens AG CR Agreement Yes
Yes
 		agreed No   S1‑183334
8.2 FS_NCIS: Study on Network Controlled Interactive Service in 5GS [SP-180341] S1‑183042 Response to SA4 regarding VR service requirements OPPO discussion Approval Yes
Yes
 		revised No S1‑183572  
    S1‑183572 Response to SA4 regarding VR service requirements OPPO discussion Approval Yes
YesSome new material to be taken into account
 		revised No S1‑183699 S1‑183042
    S1‑183699 Response to SA4 regarding VR service requirements OPPO discussion Approval No
Yes
 		agreed No   S1‑183572
    S1‑183043 NCIS TR Scope OPPO discussion Approval Yes
Yes
 		agreed No    
    S1‑183044 NCIS TR Introduction OPPO discussion Approval Yes
Yes
 		noted No    
    S1‑183045 NCIS TR Overview OPPO discussion Approval Yes
Yes
 		revised No S1‑183573  
    S1‑183573 NCIS TR Overview OPPO discussion Approval Yes
Yes
 		agreed No   S1‑183045
    S1‑183046 Gap Analyses for High Speed Scenario OPPO discussion Approval Yes
Yes
 		revised No S1‑183574  
    S1‑183574 Gap Analyses for High Speed Scenario OPPO discussion Approval Yes
Yes
 		agreed No   S1‑183046
    S1‑183047 Gap Analyses and Requirements for NCIS services OPPO discussion Approval Yes
Yes
 		revised No S1‑183575  
    S1‑183575 Gap Analyses and Requirements for NCIS services OPPO discussion Approval Yes
Yes
 		revised No S1‑183653 S1‑183047
    S1‑183653 Gap Analyses and Requirements for NCIS services OPPO discussion Approval Yes
Yes
 		agreed No   S1‑183575
    S1‑183108 Use case on IoE based social networking services OMESH pCR Approval Yes
Yes
 		revised No S1‑183582  
    S1‑183582 Use case on IoE based social networking services OMESH pCR Approval Yes
YesThis introduces several hanging paragraphs and should be avoided. Text should be improved.
 		revised No S1‑183656 S1‑183108
    S1‑183656 Use case on IoE based social networking services OMESH pCR Approval Yes
YesConfusion "notes" and "editor's notes", wrong styles
 		revised No S1‑183700 S1‑183582
    S1‑183700 Use case on IoE based social networking services OMESH pCR Approval Yes
YesConfusion with note/editor's note.
 		revised No S1‑183709 S1‑183656
    S1‑183709 Use case on IoE based social networking services OMESH pCR Approval Yes
Yes
 		agreed No   S1‑183700
    S1‑183150 Discussion on Latency Requirements and Updates to NCIS Use Case 5.3 Tencent, China Telecom pCR Approval Yes
Yes
 		revised No S1‑183576  
    S1‑183576 Discussion on Latency Requirements and Updates to NCIS Use Case 5.3 Tencent, China Telecom pCR Approval Yes
YesFurther edited while projecting.
 		revised No S1‑183655 S1‑183150
    S1‑183655 Discussion on Latency Requirements and Updates to NCIS Use Case 5.3 Tencent, China Telecom pCR Approval Yes
Yes
 		agreed No   S1‑183576
    S1‑183151 Discussion on Packet Loss Requirement and Update to NCIS Use Case 5.3 Tencent, China Telecom pCR Approval Yes
Yes
 		revised No S1‑183577  
    S1‑183577 Discussion on Packet Loss Requirement and Update to NCIS Use Case 5.3 Tencent, China Telecom pCR Approval Yes
Yes
 		revised No S1‑183652 S1‑183151
    S1‑183652 Discussion on Packet Loss Requirement and Update to NCIS Use Case 5.3 Tencent, China Telecom pCR Approval Yes
YesOne of the Notes should be an editor's note. Further edited while projecting.
 		revised No S1‑183654 S1‑183577
    S1‑183654 Discussion on Packet Loss Requirement and Update to NCIS Use Case 5.3 Tencent, China Telecom pCR Approval Yes
Yes
 		agreed No   S1‑183652
    S1‑183280 TR22.842v0.2.0 to include agreements at this meeting Rapporteur draft TR discussion Yes
Yes
 		agreed No    
    S1‑183281 Cover page for presentation of TR22.842v1.0.0 Rapporteur draft TR discussion Yes
Yesfile corrupted
 		revised No S1‑183702  
    S1‑183702 Cover page for presentation of TR22.842v1.0.0 Rapporteur draft TR discussion Yes
YesFile corrupted
 		revised No S1‑183710 S1‑183281
    S1‑183710 Cover page for presentation of TR22.842v1.0.0 Rapporteur draft TR discussion Yes
Yesfile corrupted
 		revised No S1‑183712 S1‑183702
    S1‑183712 Cover page for presentation of TR22.842v1.0.0 Rapporteur draft TR discussion Yes
Yes
 		agreed No   S1‑183710
8.3 FS_AVPROD: Feasibility Study on Audio-Visual Service Production [SP-180340] S1‑183059 Single-Camera Uncompressed Outside Broadcast Contribution EBU, BBC pCR Agreement Yes
Yes
 		revised No S1‑183564  
    S1‑183564 Single-Camera Uncompressed Outside Broadcast Contribution EBU, BBC pCR Agreement Yes
Yes
 		revised No S1‑183658 S1‑183059
    S1‑183658 Single-Camera Uncompressed Outside Broadcast Contribution EBU, BBC pCR Agreement No
Yes
 		agreed No   S1‑183564
    S1‑183060 Single-Camera compressed Outside Broadcast Contribution EBU, BBC pCR Agreement Yes
Yes
 		revised No S1‑183565  
    S1‑183565 Single-Camera compressed Outside Broadcast Contribution EBU, BBC pCR Agreement Yes
Yes
 		revised No S1‑183659 S1‑183060
    S1‑183659 Single-Camera compressed Outside Broadcast Contribution EBU, BBC pCR Agreement Yes
Yes
 		agreed No   S1‑183565
    S1‑183061 Professional TV Production Contribution from a Multi-Camera Outside using Uncompressed Video EBU, Ericsson pCR Agreement Yes
Yes
 		revised No S1‑183566  
    S1‑183566 Professional TV Production Contribution from a Multi-Camera Outside using Uncompressed Video EBU, Ericsson pCR Agreement Yes
Yes
 		revised No S1‑183660 S1‑183061
    S1‑183660 Professional TV Production Contribution from a Multi-Camera Outside using Uncompressed Video EBU, Ericsson pCR Agreement Yes
Yes
 		agreed No   S1‑183566
    S1‑183062 Simple Live Sports Commentary EBU, BBC pCR Agreement Yes
Yes
 		revised No S1‑183567  
    S1‑183567 Simple Live Sports Commentary EBU, BBC pCR Agreement Yes
Yes"[10-15v] " can be removed at this stage. Editor's note to be added instead.
 		revised No S1‑183661 S1‑183062
    S1‑183661 Simple Live Sports Commentary EBU, BBC pCR Agreement Yes
Yes
 		agreed No   S1‑183567
    S1‑183063 Local deployment of a 5G cell EBU pCR Agreement Yes
Yes
 		revised No S1‑183568  
    S1‑183568 Local deployment of a 5G cell EBU pCR Agreement Yes
YesSome typos to be corrected.
 		revised No S1‑183663 S1‑183063
    S1‑183663 Local deployment of a 5G cell EBU pCR Agreement Yes
Yes
 		agreed No   S1‑183568
    S1‑183064 TR 22.827 - Modifications for Definition Section EBU, BBC pCR Agreement Yes
Yes
 		revised No S1‑183583  
    S1‑183583 TR 22.827 - Modifications for Definition Section EBU, BBC pCR Agreement Yes
Yes
 		agreed No   S1‑183064
    S1‑183065 Background Information on AV Production Use Cases EBU, BBC other Information Yes
Yes
 		noted No    
    S1‑183098 Revised WID on Study on Audio-Visual Service Production (FS_AVPROD) SA WG1 SID new Approval Yes
Yes
 		revised No S1‑183585 SP‑180340
    S1‑183585 Revised WID on Study on Audio-Visual Service Production (FS_AVPROD) SA WG1 SID new Approval Yes
YesThis revision is identical to the previous version. "rapporteurs" to be changed into "editors" TR number to be added.
 		revised No S1‑183667 S1‑183098
    S1‑183667 Revised WID on Study on Audio-Visual Service Production (FS_AVPROD) SA WG1 SID new Approval Yes
Yes
 		agreed No   S1‑183585
    S1‑183149 Use Case of Live Immersive Media Production Intel pCR Approval Yes
Yes
 		revised No S1‑183569  
    S1‑183569 Use Case of Live Immersive Media Production Intel pCR Approval Yes
YesEditor's note to be added, guidance to be removed, etc.
 		revised No S1‑183657 S1‑183149
    S1‑183657 Use Case of Live Immersive Media Production Intel pCR Approval Yes
Yes
 		agreed No   S1‑183569
    S1‑183172 Audio Streaming in Professional Live Performances Sennheiser Electronic GmbH pCR Agreement Yes
Yes
 		revised No S1‑183270  
    S1‑183270 Audio Streaming in Professional Live Performances Sennheiser Electronic GmbH pCR Agreement Yes
Yes
 		revised No S1‑183570 S1‑183172
    S1‑183570 Audio Streaming in Professional Live Performances Sennheiser Electronic GmbH pCR Agreement Yes
Yes"To the best of the editor’s knowledge," is to be deleted.
 		revised No S1‑183664 S1‑183270
    S1‑183664 Audio Streaming in Professional Live Performances Sennheiser Electronic GmbH pCR Agreement Yes
Yes
 		agreed No   S1‑183570
    S1‑183173 Live production with integrated audience services Sennheiser Electronic GmbH pCR Agreement Yes
Yes
 		revised No S1‑183271  
    S1‑183271 Live production with integrated audience services Sennheiser Electronic GmbH pCR Agreement Yes
Yes
 		revised No S1‑183571 S1‑183173
    S1‑183571 Live production with integrated audience services Sennheiser Electronic GmbH pCR Agreement Yes
Yes
 		revised No S1‑183665 S1‑183271
    S1‑183665 Live production with integrated audience services Sennheiser Electronic GmbH pCR Agreement Yes
Yes
 		agreed No   S1‑183571
    S1‑183174 Intercom system for large live events Sennheiser Electronic GmbH pCR Agreement Yes
Yes
 		revised No S1‑183272  
    S1‑183272 Intercom system for large live events Sennheiser Electronic GmbH pCR Agreement Yes
Yes
 		revised No S1‑183584 S1‑183174
    S1‑183584 Intercom system for large live events Sennheiser Electronic GmbH pCR Agreement Yes
Yes
 		revised No S1‑183666 S1‑183272
    S1‑183666 Intercom system for large live events Sennheiser Electronic GmbH pCR Agreement Yes
Yes
 		revised No S1‑183703 S1‑183584
    S1‑183703 Intercom system for large live events Sennheiser Electronic GmbH pCR Agreement Yes
Yes
 		agreed No   S1‑183666
    S1‑183175 Annex (Informative): Real-time audio-streaming latency budget Sennheiser Electronic GmbH pCR Agreement Yes
Yes
 		agreed No    
    S1‑183282 TR22.827v0.2.0 to include agreements at this meeting Rapporteur draft TR discussion No
YesIt is not judeged 60% stable
 		agreed No    
    S1‑183283 Cover page for presentation of TR22.827v1.0.0 Rapporteur TS or TR cover discussion No
Yes
 		agreed No    
    S1‑183701 TR 22.827 Editor other discussion No
YesAlready in S1-183282
 		withdrawn Yes    
8.4 FS_FRMCS2: Study on Future Railway Mobile Communication System 2 [SP-170588] S1‑183051 Update gap analysis for requirements in subclause 6 critical communications applications Kapsch CarrierCom, Nokia CR Agreement Yes
Yes
 		revised No S1‑183522  
    S1‑183522 Update gap analysis for requirements in subclause 6 critical communications applications Kapsch CarrierCom, Nokia CR Agreement Yes
Yes
 		agreed No   S1‑183051
    S1‑183052 Update gap analysis for requirements in subclause 9.3 Service interworking with GSM-R Kapsch CarrierCom, Nokia CR Agreement Yes
Yes
 		agreed No    
    S1‑183053 Update gap analysis for requirements in subclause 12 related to interworking with GSM-R Kapsch CarrierCom, Nokia CR Agreement Yes
Yes
 		agreed No    
    S1‑183066 Changes to Off-network use Union Inter. Chemins de Fer CR Agreement Yes
Yes
 		agreed No    
    S1‑183067 Notification to a group of users Union Inter. Chemins de Fer CR Agreement Yes
Yes
 		revised No S1‑183535  
    S1‑183535 Notification to a group of users Union Inter. Chemins de Fer CR Agreement Yes
Yes
 		agreed No   S1‑183067
    S1‑183069 Changes to QoS Union Inter. Chemins de Fer CR Agreement Yes
Yes
 		withdrawn Yes    
    S1‑183070 Availability - Increasing measures related use cases Union Inter. Chemins de Fer CR Agreement Yes
Yes
 		revised No S1‑183537  
    S1‑183537 Availability - Increasing measures related use cases Union Inter. Chemins de Fer CR Agreement Yes
Yes
 		agreed No   S1‑183070
    S1‑183071 Flexible use of spectrum Union Inter. Chemins de Fer CR Agreement Yes
Yes
 		revised No S1‑183538  
    S1‑183538 Flexible use of spectrum Union Inter. Chemins de Fer CR Agreement Yes
Yes
 		agreed No   S1‑183071
    S1‑183072 Charging and billing related use cases Union Inter. Chemins de Fer CR Agreement Yes
Yes
 		revised No S1‑183539  
    S1‑183539 Charging and billing related use cases Union Inter. Chemins de Fer CR Agreement Yes
Yes
 		agreed No   S1‑183072
    S1‑183074 Update gap analysis for requirement of subclause 5 Union Inter. Chemins de Fer CR Agreement Yes
Yes
 		agreed No    
    S1‑183075 Update gap analysis for requirement of subclause 6.5 Union Inter. Chemins de Fer CR Agreement Yes
Yes
 		agreed No    
    S1‑183076 Update gap analysis for requirement of subclause 6.6 Union Inter. Chemins de Fer CR Agreement Yes
YesMerged into S1-183522
 		merged No    
    S1‑183077 Update gap analysis for requirement of subclause 6.17 Union Inter. Chemins de Fer CR Agreement Yes
Yes
 		noted No    
    S1‑183078 Update gap analysis for requirement of subclause 6.18 Union Inter. Chemins de Fer CR Agreement Yes
Yes
 		revised No S1‑183523  
    S1‑183523 Update gap analysis for requirement of subclause 6.18 Union Inter. Chemins de Fer CR Agreement Yes
Yes
 		agreed No   S1‑183078
    S1‑183079 Update gap analysis for requirement of subclause 9.9 Union Inter. Chemins de Fer CR Agreement Yes
Yes
 		agreed No    
    S1‑183080 Update gap analysis for requirement of subclause 9.17 Union Inter. Chemins de Fer CR Agreement Yes
Yes
 		noted No    
    S1‑183081 Update gap analysis for requirement of subclause 12.10 Union Inter. Chemins de Fer CR Agreement Yes
Yes
 		revised No S1‑183524  
    S1‑183524 Update gap analysis for requirement of subclause 12.10 Union Inter. Chemins de Fer CR Agreement Yes
Yes
 		agreed No   S1‑183081
    S1‑183082 Update gap analysis for requirement of subclause 12.12 Union Inter. Chemins de Fer CR Agreement Yes
Yes
 		agreed No    
    S1‑183083 Update gap analysis for requirement of subclause 12.15 Union Inter. Chemins de Fer CR Agreement Yes
Yes
 		agreed No    
    S1‑183084 Update gap analysis for requirement of subclause 12.17 Union Inter. Chemins de Fer CR Agreement Yes
Yes
 		agreed No    
    S1‑183085 Update gap analysis for requirement of subclause 12.20 Union Inter. Chemins de Fer CR Agreement Yes
Yes
 		agreed No    
    S1‑183086 Update gap analysis for requirement of subclause 12.21 Union Inter. Chemins de Fer CR Agreement Yes
Yes
 		agreed No    
    S1‑183164 Gap Analysis of Key Management System in FRMCS Ericsson CR Approval Yes
Yes
 		revised No S1‑183525  
    S1‑183525 Gap Analysis of Key Management System in FRMCS Ericsson CR Approval Yes
Yes
 		agreed No   S1‑183164
    S1‑183176 Editorial corrections and updates to 22.889 Nokia (Rapporteur) CR Agreement Yes
Yes
 		revised No S1‑183541  
    S1‑183541 Editorial corrections and updates to 22.889 Nokia (Rapporteur) CR Agreement Yes
Yes
 		agreed No   S1‑183176
    S1‑183177 Adding gap analysis section to “7.1 Use cases related to transmission of real time video” Nokia, Nokia Shanghai Bell CR Agreement Yes
Yes
 		revised No S1‑183526  
    S1‑183526 Adding gap analysis section to “7.1 Use cases related to transmission of real time video” Nokia, Nokia Shanghai Bell CR Agreement Yes
Yes
 		agreed No   S1‑183177
    S1‑183178 Adding gap analysis section to “7.5 On-train outgoing voice communication from train staff towards a ground user related use cases” Nokia, Nokia Shanghai Bell CR Agreement Yes
Yes
 		revised No S1‑183527  
    S1‑183527 Adding gap analysis section to “7.5 On-train outgoing voice communication from train staff towards a ground user related use cases” Nokia, Nokia Shanghai Bell CR Agreement Yes
Yes
 		agreed No   S1‑183178
    S1‑183179 Adding gap analysis section to “9.2 Assured voice communication (AVC)” Nokia, Nokia Shanghai Bell CR Agreement Yes
Yes
 		revised No S1‑183528  
    S1‑183528 Adding gap analysis section to “9.2 Assured voice communication (AVC)” Nokia, Nokia Shanghai Bell CR Agreement Yes
Yes
 		agreed No   S1‑183179
    S1‑183180 Adding gap analysis section to “9.5 FRMCS-userFRMCS User communication handling related use cases” Nokia, Nokia Shanghai Bell CR Agreement Yes
Yes
 		revised No S1‑183529  
    S1‑183529 Adding gap analysis section to “9.5 FRMCS-userFRMCS User communication handling related use cases” Nokia, Nokia Shanghai Bell CR Agreement Yes
Yes
 		agreed No   S1‑183180
    S1‑183181 Adding gap analysis section to “9.7 Multi user talker control related use cases” Nokia, Nokia Shanghai Bell CR Agreement Yes
Yes
 		revised No S1‑183530  
    S1‑183530 Adding gap analysis section to “9.7 Multi user talker control related use cases” Nokia, Nokia Shanghai Bell CR Agreement Yes
Yes
 		agreed No   S1‑183181
    S1‑183182 Adding explanatory text to overview section Nokia, Nokia Shanghai Bell CR Agreement Yes
Yes
 		revised No S1‑183540  
    S1‑183540 Adding explanatory text to overview section Nokia, Nokia Shanghai Bell CR Agreement Yes
Yes
 		agreed No   S1‑183182
    S1‑183221 Gap analysis of wayside-centric automatic train control Hansung University, ETRI CR Agreement Yes
Yes
 		revised No S1‑183531  
    S1‑183531 Gap analysis of wayside-centric automatic train control Hansung University, ETRI CR Agreement Yes
Yes
 		agreed No   S1‑183221
    S1‑183222 Gap analysis of Interworking with legacy systems including LMR Hansung University, ETRI CR Approval Yes
Yes
 		revised No S1‑183532  
    S1‑183532 Gap analysis of Interworking with legacy systems including LMR Hansung University, ETRI CR Approval Yes
Yes
 		agreed No   S1‑183222
    S1‑183223 Gap analysis of providing broadband and mission critical services with seamless connectivity Hansung University,ETRI CR Approval Yes
Yes
 		revised No S1‑183533  
    S1‑183533 Gap analysis of providing broadband and mission critical services with seamless connectivity Hansung University,ETRI CR Approval Yes
Yes
 		agreed No   S1‑183223
    S1‑183224 Gap analysis of offering railway services high-quality control functions with real-time train status monitoring Hansung University, ETRI CR Approval Yes
Yes
 		revised No S1‑183534  
    S1‑183534 Gap analysis of offering railway services high-quality control functions with real-time train status monitoring Hansung University, ETRI CR Approval Yes
Yes
 		agreed No   S1‑183224
8.5 FS_5GMSG: Study on 5G message service for MIoT [SP-170704]                      
8.6 FS_BMNS: Study on Business Role Models for Network Slicing [SP-180169] S1‑183243 Replacing tenant with 3rd party ETRI CR Approval Yes
Yes
 		revised No S1‑183470  
    S1‑183470 Replacing tenant with 3rd party ETRI CR Approval Yes
Yeswrong Work Item code.
 		revised No S1‑183643 S1‑183243
    S1‑183643 Replacing tenant with 3rd party ETRI CR Approval Yes
Yes
 		agreed No   S1‑183470
8.7 FS_MPS2: Feasibility Study on Multimedia Priority Service (MPS) Phase 2 [SP-170996] S1‑183208 MPS for Operator Video Call Invoked from a MPS Subscribed UE Vencore Labs, OEC, AT&T, T-Mobile USA pCR Agreement Yes
Yes
 		revised No S1‑183436  
    S1‑183436 MPS for Operator Video Call Invoked from a MPS Subscribed UE Vencore Labs, OEC, AT&T, T-Mobile USA pCR Agreement Yes
Yes
 		agreed No   S1‑183208
    S1‑183209 MPS for Operator Video Invoked from a Public UE Vencore Labs pCR Agreement Yes
Yes
 		revised No S1‑183437  
    S1‑183437 MPS for Operator Video Invoked from a Public UE Vencore Labs pCR Agreement Yes
Yes
 		agreed No   S1‑183209
    S1‑183210 MPS Operator Video Call during International Roaming Vencore Labs, OEC, AT&T, T-Mobile USA pCR Agreement Yes
Yes
 		revised No S1‑183438  
    S1‑183438 MPS Operator Video Call during International Roaming Vencore Labs, OEC, AT&T, T-Mobile USA pCR Agreement Yes
Yes
 		agreed No   S1‑183210
    S1‑183211 MPS Operator Video Conference Call Using a MPS Subscribed UE Vencore Labs, OEC, AT&T, T-Mobile USA pCR Agreement Yes
Yes
 		revised No S1‑183439  
    S1‑183439 MPS Operator Video Conference Call Using a MPS Subscribed UE Vencore Labs, OEC, AT&T, T-Mobile USA pCR Agreement Yes
Yes
 		revised No S1‑183676 S1‑183211
    S1‑183676 MPS Operator Video Conference Call Using a MPS Subscribed UE Vencore Labs, OEC, AT&T, T-Mobile USA pCR Agreement No
Yes
 		agreed No   S1‑183439
    S1‑183214 MPS Operator Video Conference Call Using a Public UE Vencore Labs, AT&T, T-Mobile USA pCR Agreement Yes
Yes
 		revised No S1‑183440  
    S1‑183440 MPS Operator Video Conference Call Using a Public UE Vencore Labs, AT&T, T-Mobile USA pCR Agreement Yes
Yes
 		revised No S1‑183677 S1‑183214
    S1‑183677 MPS Operator Video Conference Call Using a Public UE Vencore Labs, AT&T, T-Mobile USA pCR Agreement No
Yes
 		agreed No   S1‑183440
    S1‑183216 Operator Video Conference Host Invocation of MPS for All Participants Vencore Labs, OEC, AT&T, T-Mobile USA pCR Agreement Yes
Yes
 		revised No S1‑183441  
    S1‑183441 Operator Video Conference Host Invocation of MPS for All Participants Vencore Labs, OEC, AT&T, T-Mobile USA pCR Agreement Yes
YesAll styles are wrong here too. Some typos, in particular on Note 2.
 		revised No S1‑183678 S1‑183216
    S1‑183678 Operator Video Conference Host Invocation of MPS for All Participants Vencore Labs, OEC, AT&T, T-Mobile USA pCR Agreement No
Yes
 		agreed No   S1‑183441
    S1‑183217 MPS Operator Video Conference during International Roaming Vencore Labs, OEC, AT&T, T-Mobile USA pCR Agreement Yes
Yes
 		revised No S1‑183442  
    S1‑183442 MPS Operator Video Conference during International Roaming Vencore Labs, OEC, AT&T, T-Mobile USA pCR Agreement Yes
Yes"5.X.3" to be changed into "7.X.3". All styles wrong.
 		revised No S1‑183679 S1‑183217
    S1‑183679 MPS Operator Video Conference during International Roaming Vencore Labs, OEC, AT&T, T-Mobile USA pCR Agreement No
Yes
 		agreed No   S1‑183442
    S1‑183284 TR22.854v0.5.0 to include agreements at this meeting Rapporteur draft TR discussion No
YesTo be sent by e-mail on Nov 19th, final agreement on Nov. 23rd.
 		agreed No    
    S1‑183285 Cover page for presentation of TR22.854v1.0.0 Rapporteur TS or TR cover discussion No
YesNot to be presented for information.
 		withdrawn Yes    
8.8 FS_V2XIMP: Study on Improvement of V2X Service Handling [SP-180247] S1‑183009 corrections to FS_V2XIMP LG Electronics Inc. CR Agreement Yes
Yes
 		revised No S1‑183443  
    S1‑183443 corrections to FS_V2XIMP LG Electronics Inc. CR Agreement Yes
Yes
 		agreed No   S1‑183009
    S1‑183034 FS_V2XIMP Consolidation of Requirements Set 1 - DP ZTE Corporation discussion   Yes
Yes
 		revised No S1‑183462  
    S1‑183462 FS_V2XIMP Consolidation of Requirements Set 1 - DP ZTE Corporation discussion - Yes
Yes
 		noted No   S1‑183034
    S1‑183035 Supplementary consolidated requirements for FS_V2XIMP ZTE Corporation CR   Yes
Yes
 		revised No S1‑183444  
    S1‑183444 Supplementary consolidated requirements for FS_V2XIMP ZTE Corporation CR - Yes
Yes
 		agreed No   S1‑183035
    S1‑183091 Clarification on details of estimation information for different V2X applications LG Electronics Mobile Research, ZTE CR   Yes
Yes
 		revised No S1‑183445  
    S1‑183445 Clarification on details of estimation information for different V2X applications LG Electronics Mobile Research, ZTE CR - Yes
Yes
 		agreed No   S1‑183091
8.9 FS_CMED: Feasibility Study on Communication Services for Critical Medical Applications [SP-170783] S1‑183018 TR22.826 on Communication Services for Critical Medical Applications B-Com draft TR Approval Yes
Yes
 		agreed No    
    S1‑183019 Skeleton for TR22.826 on Communication Services for Critical Medical Applications B-Com discussion Agreement Yes
Yes
 		revised No S1‑183578  
    S1‑183578 Skeleton for TR22.826 on Communication Services for Critical Medical Applications B-Com discussion Agreement Yes
Yes
 		agreed No   S1‑183019
    S1‑183020 FS_CMED: Discussion on use case on Augmented Reality Assisted Surgery B-Com discussion Agreement Yes
Yes
 		revised No S1‑183562  
    S1‑183562 FS_CMED: Discussion on use case on Augmented Reality Assisted Surgery B-Com discussion Agreement Yes
Yes
 		revised No S1‑183581 S1‑183020
    S1‑183581 FS_CMED: Discussion on use case on Augmented Reality Assisted Surgery B-Com discussion Agreement Yes
Yes
 		revised No S1‑183669 S1‑183562
    S1‑183669 FS_CMED: Discussion on use case on Augmented Reality Assisted Surgery B-Com discussion Agreement Yes
Yes
 		agreed No   S1‑183581
    S1‑183021 FS_CMED: Use case on Duplicating Video on multiple monitors B-Com discussion Agreement Yes
Yes
 		revised No S1‑183561  
    S1‑183561 FS_CMED: Use case on Duplicating Video on multiple monitors B-Com discussion Agreement Yes
Yes
 		revised No S1‑183586 S1‑183021
    S1‑183586 FS_CMED: Use case on Duplicating Video on multiple monitors B-Com discussion Agreement Yes
Yes
 		revised No S1‑183670 S1‑183561
    S1‑183670 FS_CMED: Use case on Duplicating Video on multiple monitors B-Com discussion Agreement Yes
Yes
 		agreed No   S1‑183586
    S1‑183022 FS_CMED: Proposal for section 5.2.1 B-Com discussion Agreement Yes
Yes
 		revised No S1‑183580  
    S1‑183580 FS_CMED: Proposal for section 5.2.1 B-Com discussion Agreement Yes
Yes
 		agreed No   S1‑183022
    S1‑183023 FS_CMED: Use case on Emergency Care - Remote Interventional Support B-Com discussion Agreement Yes
Yes
 		revised No S1‑183563  
    S1‑183563 FS_CMED: Use case on Emergency Care - Remote Interventional Support B-Com discussion Agreement Yes
Yes
 		revised No S1‑183587 S1‑183023
    S1‑183587 FS_CMED: Use case on Emergency Care - Remote Interventional Support B-Com discussion Agreement Yes
Yes
 		revised No S1‑183671 S1‑183563
    S1‑183671 FS_CMED: Use case on Emergency Care - Remote Interventional Support B-Com discussion Agreement Yes
Yes
 		agreed No   S1‑183587
    S1‑183118 FS_CMED - TR22.826 Scope B-Com discussion Agreement Yes
Yes
 		revised No S1‑183579  
    S1‑183579 FS_CMED - TR22.826 Scope B-Com discussion Agreement Yes
Yes
 		agreed No   S1‑183118
8.10 FS_5G_ATRAC: Study on Asset Tracking Use Cases [SP-170784] S1‑183154 Skeleton for TR22.836 on Asset Tracking Use Cases (5G_ATRAC) NOVAMINT discussion Agreement Yes
Yes
 		agreed No    
    S1‑183156 FS_5G_ATRAC - TR22.836 Scope NOVAMINT pCR Agreement Yes
Yes
 		revised No S1‑183593  
    S1‑183593 FS_5G_ATRAC - TR22.836 Scope NOVAMINT pCR Agreement Yes
Yes
 		agreed No   S1‑183156
    S1‑183159 Use Case on Container Tracking NOVAMINT other Agreement Yes
Yes
 		revised No S1‑183594  
    S1‑183594 Use Case on Container Tracking NOVAMINT other Agreement Yes
Yes
 		revised No S1‑183379 S1‑183159
    S1‑183379 Use Case on Container Tracking NOVAMINT other Agreement Yes
Yes
 		revised No S1‑183648 S1‑183594
    S1‑183648 Use Case on Container Tracking NOVAMINT other Agreement Yes
YesThe comment is to be put back in the requirement at some point. Some other formatting problems.
 		revised No S1‑183693 S1‑183379
    S1‑183693 Use Case on Container Tracking NOVAMINT other Agreement No
Yes
 		agreed No   S1‑183648
    S1‑183220 Use Case on Wagon Tracking NOVAMINT pCR Agreement Yes
Yes
 		revised No S1‑183595  
    S1‑183595 Use Case on Wagon Tracking NOVAMINT pCR Agreement Yes
Yes
 		revised No S1‑183649 S1‑183220
    S1‑183649 Use Case on Wagon Tracking NOVAMINT pCR Agreement Yes
Yes
 		revised No S1‑183694 S1‑183595
    S1‑183694 Use Case on Wagon Tracking NOVAMINT pCR Agreement No
Yes
 		agreed No   S1‑183649
    S1‑183246 Overview section for TR 22.836 NOVAMINT pCR Agreement Yes
Yes
 		revised No    
    S1‑183638 Overview section for TR 22.836 NOVAMINT pCR Agreement Yes
Yes
 		revised No S1‑183695 S1‑183246
    S1‑183695 Overview section for TR 22.836 NOVAMINT pCR Agreement Yes
Yes10.000 sqm was proposed to be shown, but Ericsson prefers 100x100m.
 		revised No S1‑183706 S1‑183638
    S1‑183706 Overview section for TR 22.836 NOVAMINT pCR Agreement Yes
Yes
 		agreed No   S1‑183695
    S1‑183286 TR22.836v0.1.0 to include agreements at this meeting Rapporteur draft TR discussion No
Yes
 		agreed No    
8.11 FS_REFEC: Study on enhanced Relays for Energy eFficiency and Extensive Coverage [SP-170785] S1‑183102 TP on Multihop Communications in 3GPP 5G OMESH pCR Approval Yes
Yes
 		revised No S1‑183380  
    S1‑183380 Overview of Multihop Communications in 3GPP 5GS OMESH pCR Approval Yes
YesOverlaps with a KPN contribution
 		noted No   S1‑183102
    S1‑183639 TP on Multihop Communications in 3GPP 5G OMESH pCR Approval No
Yes3380 used for revision of 3102
 		withdrawn Yes   S1‑183102
    S1‑183103 TP on smart city and community services OMESH pCR Approval Yes
Yes
 		revised No S1‑183382  
    S1‑183382 TP on smart city and community services OMESH pCR Approval Yes
Yes
 		agreed No   S1‑183103
    S1‑183104 Use case on Micro-environment services OMESH pCR Approval Yes
Yes
 		revised No S1‑183383  
    S1‑183383 Use case on Micro-environment services OMESH pCR Approval No
Yes
 		withdrawn Yes   S1‑183104
    S1‑183105 Use case on elder and child services OMESH pCR Approval Yes
Yes
 		revised No S1‑183384  
    S1‑183384 Use case on elder and child services OMESH pCR Approval No
Yes
 		withdrawn Yes   S1‑183105
    S1‑183106 Use case on parking and transportation services OMESH pCR Approval Yes
Yes
 		revised No S1‑183391  
    S1‑183391 Use case on parking and transportation services OMESH pCR Approval No
Yes
 		withdrawn Yes   S1‑183106
    S1‑183107 Use case on new retailer services OMESH pCR Approval Yes
Yes
 		noted No    
    S1‑183131 Use case for multi-hop relays on the factory floor InterDigital, Inc. pCR Agreement Yes
Yes
 		revised No S1‑183385  
    S1‑183385 Use case for multi-hop relays on the factory floor InterDigital, Inc. pCR Agreement Yes
YesThe terminology should be aligned to the rest of the TR.
 		revised No S1‑183647 S1‑183131
    S1‑183647 Use case for multi-hop relays on the factory floor InterDigital, Inc. pCR Agreement Yes
YesFurther edited while projecting
 		revised No S1‑183704 S1‑183385
    S1‑183704 Use case for multi-hop relays on the factory floor InterDigital, Inc. pCR Agreement Yes
Yes
 		available No   S1‑183647
    S1‑183192 Skeleton for FS_REFEC TNO draft TR Approval Yes
Yes
 		agreed No    
    S1‑183193 Scope section FS_REFEC TNO pCR   Yes
Yes
 		agreed No    
    S1‑183194 Overview section FS_REFEC TNO pCR   Yes
Yes
 		noted No    
    S1‑183287 TR22.866v0.1.0 to include agreements at this meeting Rapporteur draft TR discussion Yes
Yes
 		agreed No    
8.12 FS_EAV: Study on enhancement for UAVs [SP-170786] S1‑183027 Use case for uplink transmission of a UAV China Unicom pCR Approval Yes
Yes
 		noted No    
    S1‑183028 Use case for UL and DL transmission of a UAV China Unicom pCR Approval Yes
Yes
 		revised No S1‑183448  
    S1‑183448 Use case for UL and DL transmission of a UAV China Unicom pCR Approval No
Yes
 		withdrawn Yes   S1‑183028
    S1‑183029 Use case for network slicing of UAVs China Unicom pCR Approval Yes
Yes
 		revised No S1‑183449  
    S1‑183449 Use case for network slicing of UAVs China Unicom pCR Approval No
Yes
 		withdrawn Yes   S1‑183029
    S1‑183030 Use case for the edge computing of UAVs China Unicom pCR Approval Yes
Yes
 		noted No    
    S1‑183031 TR22.829 FS_EAV skeleton China Unicom pCR Approval Yes
Yes
 		agreed No    
    S1‑183032 FS_EAV TR 22.829 introduction China Unicom pCR Approval Yes
Yes
 		revised No S1‑183446  
    S1‑183446 FS_EAV TR 22.829 introduction China Unicom pCR Approval Yes
Yes
 		revised No S1‑183680 S1‑183032
    S1‑183680 FS_EAV TR 22.829 introduction China Unicom pCR Approval Yes
YesThe introduction is an optional clause. There is no need to provide one if there is nothing specific to write. So the introduction is deleted.
 		agreed No   S1‑183446
    S1‑183033 FS_EAV TR 22.829 scope China Unicom pCR Approval Yes
Yes
 		revised No S1‑183447  
    S1‑183447 FS_EAV TR 22.829 scope China Unicom pCR Approval Yes
Yes"This study " to be changed into "This present document".
 		revised No S1‑183681 S1‑183033
    S1‑183681 FS_EAV TR 22.829 scope China Unicom pCR Approval Yes
Yes
 		agreed No   S1‑183447
    S1‑183130 Use case for varied UAV control KPIs InterDigital, Inc. pCR Agreement Yes
Yes
 		not treated No    
    S1‑183132 Use case of UAV supporting evolved high resolution video live broadcast ZTE Corporation pCR   Yes
Yes
 		revised No S1‑183463  
    S1‑183463 Use case of UAV supporting evolved high resolution video live broadcast ZTE Corporation, China Unicom pCR - Yes
Yes
 		agreed No   S1‑183132
    S1‑183148 Use Case of UAS Command and Control (C2) Communication Intel pCR Approval Yes
Yes
 		revised No S1‑183464  
    S1‑183464 Use Case of UAS Command and Control (C2) Communication Intel pCR Approval Yes
YesRight styles to be used, right template to be used.
 		revised No S1‑183682 S1‑183148
    S1‑183682 Use Case of UAS Command and Control (C2) Communication Intel pCR Approval Yes
Yes
 		agreed No   S1‑183464
    S1‑183162 Use case for UAV on-board Base Station CATT other   Yes
Yes
 		revised No S1‑183465  
    S1‑183465 Use case for UAV on-board Base Station CATT other - Yes
Yes
 		agreed No   S1‑183162
    S1‑183288 TR22.829v0.1.0 to include agreements at this meeting Rapporteur draft TR discussion Yes
Yes
 		agreed No    
9 Other technical contributions                      
10 Work planning contributions                      
10.1 Work Plan S1‑183241 Release 17 stage 1 freeze date Qualcomm Incorporated discussion Agreement Yes
Yes
 		revised No S1‑183336  
    S1‑183336 Release 17 stage 1 freeze date Qualcomm Incorporated discussion Agreement Yes
YesSony and Nokia support this idea. Nokia proposes not to start Rel-18 topics before Rel-17 work is finished. For Huawei, 9 months to complete Rel-17 might be too aggressive. For Qualcomm, it is the deadline that should come first, then the content is to be aligned to this deadline rather than the other way round. For T-Mobile, it is OK to have an overlap between Stages. They prefer December 2019 for Stage 1 freeze. Ericsson prefers September, remembering that SA1 work will continue after September. The chair wanted to disociate the discussions on the ideal case versus the practical case for next Release. Qualcomm proposes to have the Stage 1 freeze 3 month after Stage 2 start. For the SA chair, this overlap doesn't work. Vodafone reminded that there is in practice delay, exceptions, etc. Nokia supports no overlap too. For MCC, the discussion about "overlap" is a bit artificial: SA1 is not controlling the start of SA2 work. What is to be discussed is the Stage 1 freezing date and then Stage 2 can start their work whenever they want, preferably when Stage 1 is stable. Huawei also support that the key point is that Stage 1 is stable as to enable Stage 2 to start their work. September is a good date for Stage 1 Rel-17 freeze: 18 companies support September is too early: 15 companies support Qualcomm proposes September with extensions possible or December without exception. The chair propose is to have Stage 1 Rel-17 freeze in December 2019 with no possible extension, and then SA1 will work with the assumption that SA1 will have less time for specifying Stage 1 for Rel-18. 15 companies are supporting this view. 10 companies are not supporting this view. NEC reminded that this is a plenary decision so there is no need to have an SA1 consolidated view. Qualcomm proposes to report the two possible dates (Sept or Dec) without a consolidated view on which date to set. For T-Mobile, SA1 is producing already too many requirements and other groups are overwhelmed. There is no consensual view on Stage 1 freezing date in SA1 (either Sept or Dec) and this is what will be reported byu SA1 chair to SA.
 		noted No   S1‑183241
10.2 Work Item/Study Item status update S1‑183625 V2XIMP – Status report LG Electronics, AT&T, ZTE, LG Uplus, Volkswagen, Deutsche Telekom, Huawei, KDDI, Ericsson report Approval Yes
YesFor newly approved WID in S1-183350. Work/Study Item Completion: 95% Controversial issues Will be reported as 100%.
 		noted No    
    S1‑183289 MONASTERY2 – Status report Rapporteur report discussion Yes
YesCurrent expected dates to send TS22.289 to SA plenary: For information: SA#82 (12/2018) For approval: SA#82 (12/2018) Guide: SA plenary meeting number and date (not SA1) Guide: Remove bullets above if there is no new TR/TS Have these dates been changed at this meeting? N Estimated percentage completion: SA#82: <100%>
 		noted No    
    S1‑183290 FS_FRMCS2 – Status report Rapporteur report discussion Yes
YesCurrent expected dates to send TR22.889 to SA plenary: TR is under change control Guide: SA plenary meeting number and date (not SA1) Guide: Remove bullets above if there is no new TR/TS Have these dates been changed at this meeting? N Estimated percentage completion: SA#82: <100%>
 		noted No    
    S1‑183291 enIMS – Status report Rapporteur report discussion Yes
YesEstimated percentage completion: SA#82: 100%
 		noted No    
    S1‑183292 SMARTER Ph2 – Status report Rapporteur report discussion Yes
YesEstimated percentage completion: now: 80% Next meeting: 90%. Will be changed to 100% in the Chair's report to SA.
 		noted No    
    S1‑183293 QoS_MON – Status report Rapporteur report discussion Yes
YesWork/Study Item Completion: 100% Controversial issues: None
 		noted No    
    S1‑183294 MuD – Status report Rapporteur report discussion Yes
YesProgress made at this meeting LS from SA5 arrived which didn’t indicate any outstanding charging issues Work/Study Item Completion: 100%
 		noted No    
    S1‑183295 MOBRT – Status report Rapporteur report discussion No
YesAlready copmpleted.
 		withdrawn Yes    
    S1‑183296 5GLAN – Status report Rapporteur report discussion Yes
YesWork/Study Item Completion: 100% Draft Section TS 22.261 Completion: 100%
 		noted No    
    S1‑183297 cyberCAV – Status report Rapporteur report discussion Yes
YesWork/Study Item Completion: 100% Draft TS 22.104 Completion: 100%
 		noted No    
    S1‑183298 5GSAT – Status report Rapporteur report discussion Yes
YesWork/Study Item Completion: 100% Controversial issues: None
 		noted No    
    S1‑183299 MARCOM – Status report Rapporteur report discussion Yes
YesEstimated percentage completion: SA#82: 95% SA#83: 100% Controversial issues: None
 		noted No    
    S1‑183300 UIA – Status report Rapporteur report discussion No
YesAlready completed
 		withdrawn Yes    
    S1‑183301 5G_HYPOS – Status report Rapporteur report discussion Yes
YesWork Item Completion: 100% Controversial issues: none
 		noted No    
    S1‑183302 FS_5GMSG – Status report Rapporteur report discussion Yes
YesWork/Study Item Completion: 100% Controversial issues None
 		noted No    
    S1‑183303 FS_BMNS – Status report Rapporteur report discussion Yes
YesWork/Study Item Completion: 100% Controversial issues none
 		noted No    
    S1‑183304 FS_MPS2 – Status report Rapporteur report discussion Yes
YesEstimated percentage completion: SA#82: <65%> SA#83: <80%> SA#84: <90%> SA#85: <100%> Change of completion date.
 		noted No    
    S1‑183305 FS_V2XIMP – Status report Rapporteur report discussion Yes
YesWork/Study Item Completion: 100% Controversial issues: none
 		noted No    
    S1‑183306 FS_AVPROD – Status report Rapporteur report discussion Yes
YesWork/Study Item Completion: 50% Draft TR 22.827 Completion: 50% Controversial issues: none Completion changed from SA82 to SA83
 		noted No    
    S1‑183307 FS_NCIS – Status report Rapporteur report discussion Yes
YesStudy Item Completion 60% Draft TR 22.842 Completion 60% Controversial issues None
 		noted No    
    S1‑183308 BRMNS – Status report Rapporteur report discussion Yes
YesWork/Study Item Completion: 100% Controversial issues none
 		noted No    
    S1‑183309 FS_CMED – Status report Rapporteur report discussion Yes
YesWork/Study Item Completion: 15% Draft TR 22.826 Completion: 15% Controversial issues n/a Current expected dates to send TR to SA plenary: For information: SA#84 (06/2019) For approval: SA#85 (09/2019)
 		noted No    
    S1‑183310 FS_ATRACT – Status report Rapporteur report discussion Yes
YesWork/Study Item Completion: 15% Draft TR 22.836 Completion: 15% Controversial issues n/a Current expected dates to send TR to SA plenary: For information: SA#83 (03/2019) For approval: SA#84 (06/2019)
 		noted No    
    S1‑183311 FS_REFEC – Status report Rapporteur report discussion Yes
Yes Work/Study Item Completion: 20% Draft TR 22.866 Completion: 20% Controversial issues Use cases must be within the scope of the study Current expected dates to send
noted No    
    S1‑183312 ID_UAS – Status report Rapporteur report discussion Yes
YesWork/Study Item Completion: 100% Draft TS 22.125 Completion: 100% Controversial issues None
 		noted No    
    S1‑183313 FS_EAV – Status report Rapporteur report discussion Yes
YesWork/Study Item Completion: 20% Draft TR 22.829 Completion: 20% Controversial issues none Current expected dates to send TR to SA plenary: For information: SA#83 (after SA1#85) For approval: SA#84 (after SA1 #86)
 		noted No    
    S1‑183314 5GMSG – Status report Rapporteur report discussion Yes
YesWork/Study Item Completion: 100% Draft TS 22.262 Completion: 100% Controversial issues None
 		noted No    
10.3 SA1 process improvements/updates                      
10.4 Other non-technical contributions                      
11 Next meetings                      
11.1 Calendar                      
12 Any other business                      
13 Close