Tdoc List
2019-08-29 10:35
| 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‑192000 | Draft Agenda for SA1#87 | Chair | agenda | No |
Yes
| revised | No | S1‑192001 | ||
| S1‑192001 | 2nd Draft Agenda for SA1#87 | Chair | agenda | Decision | No |
Yes
| revised | No | S1‑192002 | |||
| S1‑192002 | Final Schedule and Agenda with document allocation for SA1#87 | Chair | agenda | Decision | No |
YesThe chair reminded the importance of writing the requirements in such a way that they are "implementable" by the downstream groups, in particular SA2 and SA6.
| revised | No | S1‑192003 | S1‑192001 | ||
| S1‑192003 | Rerserved SA1 Chair | Chair | agenda | Decision | No |
Yes
| agreed | No | S1‑192002 | |||
| 1.2 | IPR, antitrust and competition laws | |||||||||||
| 1.3 | Previous SA1 meeting report | S1‑192005 | Minutes of SA1#86 | MCC | report | Approval | Yes |
YesOne spelling mistake in a name.
| revised | No | S1‑192397 | |
| S1‑192397 | Minutes of SA1#86 | MCC | report | Approval | No |
Yes
| agreed | No | S1‑192005 | |||
| 1.4 | Information for delegates | |||||||||||
| 1.5 | Information for rapporteurs | |||||||||||
| 1.6 | Working agreements | |||||||||||
| 2 | Reports and action items | S1‑192004 | Report of SA1 topics at SA#85 | Chair | report | Approval | Yes |
Yes
| noted | No | ||
| S1‑192006 | Extract of the 3GPP Work Plan for SA1#87 | MCC | Work Plan | Information | Yes |
Yes
| agreed | No | ||||
| S1‑192266 | Release 17 RAN work areas, and SA1 related items | KPN N.V. | discussion | Endorsement | Yes |
YesIt might be missing a "joker" area where to put all the SA1 items without a corresponding RAN work area.
| revised | No | S1‑192398 | |||
| S1‑192398 | Release 17 RAN work areas, and SA1 related items | KPN N.V. | discussion | Endorsement | Yes |
Yes
| revised | No | S1‑192703 | S1‑192266 | ||
| S1‑192703 | Release 17 RAN work areas, and SA1 related items | KPN N.V. | discussion | Endorsement | No |
YesTo be provided after the meeting.
Feedback will be asked to the rapporteurs next week.
This is endorsed as the way forward.
| endorsed | No | S1‑192398 | |||
| S1‑192320 | TR 21.915 v.1.2.0 on Rel-15 Description | MCC | draft TR | Information | Yes |
Yes
| noted | No | ||||
| 3 | Liaison Statements (including related contributions) | |||||||||||
| 3.1 | LSs on Network slice constraint requirement clarification | S1‑192007 | Correction to Network Slicing Constraints | LG Electronics Inc. | CR | Yes |
YesSee other related CRs.
| noted | No | |||
| S1‑192034 | Reply LS on network slice constraint requirement clarification | Nokia, Nokia Shanghai Bell | LS out | Approval | Yes |
Yes
| revised | No | S1‑192400 | |||
| S1‑192400 | Reply LS to SA2 on network slice constraint requirement clarification | Nokia, Nokia Shanghai Bell | LS out | Approval | Yes |
YesThe CR has to be attached.
| revised | No | S1‑192812 | S1‑192034 | ||
| S1‑192812 | Reply LS to SA2 on network slice constraint requirement clarification | S1 | LS out | Approval | Yes |
Yes
| agreed | No | S1‑192400 | |||
| S1‑192035 | Clarification of geographic constraint on a network slice | Nokia, Nokia Shanghai Bell | CR | Yes |
Yes
| revised | No | S1‑192399 | ||||
| S1‑192399 | Clarification of geographic constraint on a network slice | Nokia, Nokia Shanghai Bell | CR | - | Yes |
YesShould be from Rel-15 onwards (and not Rel-16).
Rel-15 CR in S1-192401.
Not really a mirror of 2401. This could be clarified.
| revised | No | S1‑192705 | S1‑192035 | ||
| S1‑192401 | Clarification of geographic constraint on a network slice | Nokia, Nokia Shanghai Bell | CR | - | Yes |
YesFrom S1-192399. Rel-15 version of the CR.
Mistake on the release on the cover page.
| revised | No | S1‑192704 | |||
| S1‑192705 | Clarification of geographic constraint on a network slice | Nokia, Nokia Shanghai Bell | CR | - | Yes |
Yes
| agreed | No | S1‑192399 | |||
| S1‑192704 | Alignment of geographic constraint on a network slice | Nokia, Nokia Shanghai Bell | CR | - | Yes |
Yes
| agreed | No | S1‑192401 | |||
| S1‑192039 | Clarify NS requirements | ZTE Trunking Technology Corp. | CR | Yes |
YesEricsson, Qualcomm, NTT DoCoMo, KPN, Siemens, Telefonica, Vodafone support keeping it and clarifying it. Several companies prefer the Nokia's way of clarifying it.
Merged with Nokia's CR.
| merged | No | |||||
| S1‑192040 | Reply LS on network slice constraint requirement clarification | ZTE Trunking Technology Corp. | LS out | Approval | Yes |
YesMerged with Nokia's answer.
| noted | No | ||||
| S1‑192307 | LS on network slice constraint requirement clarification | S2-1908592 | LS in | discussion | Yes |
Yes
| noted | No | ||||
| 3.2 | LSs on UAC for NB-IoT | S1‑192021 | CR to 22.261 on correction for UAC and IoT | LG Electronics | CR | Yes |
YesThis adds a new access category, as to answer the RAN2's LS in 2317.
| noted | No | |||
| S1‑192022 | draft reply LS on on UAC for NB-IoT (R2-1908263) | LG Electronics | discussion | Yes |
YesTo inform RAN2 about the CR.
| noted | No | |||||
| S1‑192233 | Draft Reply LS on UAC for NB-IoT | Qualcomm communications-France | LS out | Approval | Yes |
YesThe CR to be noted (no new access category to be approved at this time).
| revised | No | S1‑192404 | |||
| S1‑192404 | Draft Reply LS to RAN2 (cc CT1, SA2, RAN3) on UAC for NB-IoT | Qualcomm communications-France | LS out | Approval | Yes |
Yes
| revised | No | S1‑192707 | S1‑192233 | ||
| S1‑192707 | LS to RAN2 (cc CT1, SA2, RAN3) on UAC for NB-IoT | Qualcomm communications-France | LS out | Approval | Yes |
Yes
| agreed | No | S1‑192404 | |||
| S1‑192317 | LS on UAC for NB-IoT | R2-1908263 | LS in | discussion | Yes |
YesCR in 2021 proposes to add a new access category.
| noted | No | ||||
| 3.3 | LSs on Enhanced access control for IMS signalling | S1‑192321 | LS on enhanced access control for IMS signalling | C1-1911681/S1-191210 | LS in | discussion | Yes |
YesAccording to CT1, there is a problem with IMS signalling.
3 solutions are proposed by LG in 2143 (proposing to do nothing) then Intel in 2250 and corresponding CRs, and CRs and Huawei in 2142. New access categories needed
A show of hands indicated that 9 companies are in favour of doing nothing (as per LG), 11 are in favour of doing something (introducing New access categories).
Qualcomm proposes to do things only for 5G.
Drafting session to be handled during the coffee break.
On the last day of SA1#87, and given the lack of consensus on the topic, it was decided to postpone the entire topic to the next SA1 meeting.
No answer could be provided.
The SA1 intention is not to delay CT1 work with this.
There was still an attempt for a draft answer in S1-192813.
| revised | No | ||
| S1‑192813 | LS to CT1 (cc RAN2) on enhanced access control for IMS signalling | Huawei | LS out | Approval | Yes |
YesFor Qualcomm, CT1 should decide on a suitable solution and let SA1 know.
Still no easy way out on the last day.
| noted | No | ||||
| S1‑192043 | Reply LS on enhanced access control for IMS signalling | LG Electronics | discussion | Yes |
YesThis topic is postponed to the next SA1 meeting, all related documents are noted.
| noted | No | |||||
| S1‑192044 | Access control for IMS service | LG Electronics | discussion | Yes |
YesThis topic is postponed to the next SA1 meeting, all related documents are noted.
| noted | No | |||||
| S1‑192138 | CR on 22.261 for UAC for IMS signalling | Huawei, KDDI, DOCOMO | CR | Approval | Yes |
YesThis topic is postponed to the next SA1 meeting, all related documents are noted.
| noted | No | ||||
| S1‑192142 | Reply LS on eAC for IMS signalling | Huawei, KDDI, NTT DOCOMO | LS out | Approval | Yes |
Yes
| revised | No | S1‑192788 | |||
| S1‑192788 | Reply LS on eAC for IMS signalling | Huawei, KDDI, NTT DOCOMO | LS out | Approval | Yes |
YesThis topic is postponed to the next SA1 meeting, all related documents are noted.
| noted | No | S1‑192142 | |||
| S1‑192143 | Discussion paper on eAC for IMS signalling | Huawei, KDDI, NTT DOCOMO | discussion | Discussion | Yes |
YesThis topic is postponed to the next SA1 meeting, all related documents are noted.
| noted | No | ||||
| S1‑192250 | Proposal for Different Access Control Treatment for IMS signalling | Intel | discussion | Agreement | Yes |
YesThis topic is postponed to the next SA1 meeting, all related documents are noted.
| noted | No | ||||
| S1‑192253 | Enhanced access control for IMS registration related signalling | Intel | CR | Approval | Yes |
YesThis topic is postponed to the next SA1 meeting, all related documents are noted.
| noted | No | ||||
| S1‑192254 | Enhanced access control for IMS registration realted signalling | Intel | CR | Approval | Yes |
YesThis topic is postponed to the next SA1 meeting, all related documents are noted.
| noted | No | ||||
| 3.4 | LSs on APN storage in USIM | S1‑192033 | Reply LS to SA2, CT1, CT6 on APN storage in USIM | Nokia, Nokia Shanghai Bell | LS out | Approval | Yes |
YesQualcomm support this answer.
| agreed | No | ||
| S1‑192301 | Reply LS on APN storage in USIM | S2-1906034 | LS in | discussion | Yes |
YesSee proposed answer in 2033.
| noted | No | ||||
| 3.5 | LSs on Authentication of group of IoT devices | S1‑192075 | Reply LS on authentication of group of IoT devices | China Mobile Com. Corporation | LS out | Approval | Yes |
YesChina Mobile wants to keep the requirement and add explanations whereas Qualcomm prefers to remove it.
This topic can be postponed to the next SA1 meeting, just to give a chance to SA2 to progress.
Some companies prefer to delete it now since it is kind of known that SA3 and SA2 are not going to address it for Rel-16.
| revised | No | S1‑192408 | |
| S1‑192408 | Reply LS to SA2, SA3 on authentication of group of IoT devices | China Mobile Com. Corporation | LS out | Approval | Yes |
Yes
| revised | No | S1‑192708 | S1‑192075 | ||
| S1‑192708 | Reply LS to SA2, SA3 on authentication of group of IoT devices | China Mobile Com. Corporation | LS out | Approval | Yes |
Yes
| revised | No | S1‑192816 | S1‑192408 | ||
| S1‑192816 | Reply LS to SA2, SA3 on authentication of group of IoT devices | SA1 | LS out | Approval | Yes |
Yes
| agreed | No | S1‑192708 | |||
| S1‑192127 | Discussion on Bulk IoT text in TS 22.261 | Qualcomm communications-France | discussion | Yes |
YesIt is finally agreed to remove the requirement from Rel-16 only.
| noted | No | |||||
| S1‑192129 | Clarify requirements for bulk IoT operation and authentication | Qualcomm communications-France | CR | Yes |
YesThis CR is to be applied to 22.261 Rel-16 after the Rel-17 version has been created.
Clause 8.3 cannot become empty.
| revised | No | S1‑192407 | ||||
| S1‑192407 | Clarify requirements for bulk IoT operation and authentication | Qualcomm communications-France | CR | - | Yes |
Yes
| revised | No | S1‑192814 | S1‑192129 | ||
| S1‑192814 | Clarify requirements for bulk IoT operation and authentication | Qualcomm communications-France | CR | - | Yes |
Yes
| agreed | No | S1‑192407 | |||
| S1‑192222 | Draft Reply LS on authentication of group of IoT devices | Qualcomm communications-France | LS out | Approval | Yes |
YesMerged in 2408.
| merged | No | ||||
| S1‑192309 | Reply LS to on authentication of group of IoT devices | S3-191601 | LS in | discussion | Yes |
YesSee SA2's answer in 2308.
| noted | No | ||||
| S1‑192308 | Reply LS on authentication of group of IoT devices | S2-1908632 | LS in | discussion | Yes |
Yes
| noted | No | ||||
| S1‑192728 | Clarify requirements for group IoT authentication | Qualcomm, Vodafone | CR | discussion | Yes |
YesRevision marks should be used (and not strikethrough font)
| revised | No | S1‑192815 | |||
| S1‑192815 | Clarify requirements for group IoT authentication | Qualcomm, Vodafone | CR | discussion | Yes |
Yes
| agreed | No | S1‑192728 | |||
| 3.6 | LSs on Release 16 Stage 1 MARCOM standardization | S1‑192042 | CR for Rel-16 TS 22.119 Clarification and editorial updates | SyncTechno Inc. | CR | Approval | Yes |
YesThis comes from the IALA's suggested changes in 2322.
| revised | No | S1‑192402 | |
| S1‑192402 | CR for Rel-16 TS 22.119 Clarification and editorial updates | SyncTechno Inc. | CR | Approval | Yes |
YesNot really a category D.
| revised | No | S1‑192709 | S1‑192042 | ||
| S1‑192709 | CR for Rel-16 TS 22.119 Clarification and editorial updates | SyncTechno Inc. | CR | Approval | Yes |
Yes
| agreed | No | S1‑192402 | |||
| S1‑192103 | [DRAFT] Reply LS on IAIA liaison on the update of 3GPP Release 16 Stage 1 MARCOM standardization | SyncTechno Inc. | LS out | Approval | Yes |
YesTo tell IALA that they proposed changes have been taken into account by 3GPP.
| revised | No | S1‑192403 | |||
| S1‑192403 | [DRAFT] Reply LS on IAIA liaison on the update of 3GPP Release 16 Stage 1 MARCOM standardization | SyncTechno Inc. | LS out | Approval | Yes |
YesEditorial corrections needed.
| revised | No | S1‑192710 | S1‑192103 | ||
| S1‑192710 | LS on IAIA (cc SA) on the update of 3GPP Release 16 Stage 1 MARCOM standardization | SyncTechno Inc. | LS out | Approval | Yes |
Yes
| agreed | No | S1‑192403 | |||
| S1‑192322 | LS on the update of 3GPP Release 16 Stage 1 MARCOM standardization | Iala C/IM/3GPP/19-102/S1-191282 | LS in | discussion | Yes |
YesThe proposed changes have been made into a proper 3GPP CR in 2042.
| noted | No | ||||
| 3.7 | LSs on UAS-related terminology and model | S1‑192230 | Draft Reply LS on UAS-related terminology and model | Qualcomm communications-France | LS out | Approval | Yes |
YesProposed answer to 2313
| revised | No | S1‑192406 | |
| S1‑192406 | Draft Reply LS on UAS-related terminology and model | Qualcomm communications-France | LS out | Approval | Yes |
Yes
| revised | No | S1‑192799 | S1‑192230 | ||
| S1‑192799 | Draft Reply LS to SA6 on UAS-related terminology and model | Qualcomm communications-France | LS out | Approval | Yes |
Yes
| revised | No | S1‑192817 | S1‑192406 | ||
| S1‑192817 | LS to SA6 on UAS-related terminology and model | SA1 | LS out | Approval | Yes |
Yes
| agreed | No | S1‑192799 | |||
| S1‑192313 | LS on UAS-related terminology and model | S6-191612 | LS in | discussion | Yes |
Yes
| noted | No | ||||
| 3.8 | LSs on other topics | S1‑192302 | LS on IMS voice over 5GS | S2-1906791 | LS in | discussion | Yes |
YesNoted without presentation.
| noted | No | ||
| S1‑192303 | LS on RAN sharing and Emergency services with Non-Public Networks | S2-1906814 | LS in | discussion | Yes |
YesNoted without presentation.
| noted | No | ||||
| S1‑192304 | LS on maximum value of MDBV | S2-1907955 | LS in | discussion | Yes |
YesNoted without presentation.
| noted | No | ||||
| S1‑192305 | Reply LS on unified access control in SNPNs (Stand-alone Non-Public Networks) | S2-1908331 | LS in | discussion | Yes |
YesNoted without presentation.
| noted | No | ||||
| S1‑192306 | LS on GSMA NG-116 GST-related Work in SA2 | S2-1908591 | LS in | discussion | Yes |
YesGSMA has agreed a new study on NG.116 GST publication and cooperation with 3GPP SA2
| noted | No | ||||
| S1‑192310 | Reply LS on Authentication for UEs not Supporting NAS | S3-191713 | LS in | discussion | Yes |
YesNoted without presentation.
| noted | No | ||||
| S1‑192311 | LS on Reporting all Cell IDs in 5G | S3i190461 | LS in | discussion | Yes |
YesNot for SA1.
| noted | No | ||||
| S1‑192312 | LS on C-V2X Sensor Sharing of Media and Object Information | S4-190795 | LS in | discussion | Yes |
Yes
| noted | No | ||||
| S1‑192314 | LS on the call for proposals for an internationally agreed Vehicular Multimedia Architecture | ITU FGVM-LS007 | LS in | discussion | Yes |
Yes
| noted | No | ||||
| S1‑192315 | LS on the scope of study/work item on support for multi-USIM devices (FS_MUSIM/MUSIM) | SP-190573 | LS in | discussion | Yes |
Yes
| noted | No | ||||
| S1‑192316 | LS on unified access control in SNPNs (Stand-alone Non-Public Networks) | C1-193504 | LS in | discussion | Yes |
YesNoted without presentation.
| noted | No | ||||
| S1‑192318 | GTP Recovery Counter & GSN node behaviour | GSMA RIFS Doc 78_04 | LS in | discussion | Yes |
YesNoted without presentation.
| noted | No | ||||
| S1‑192323 | LS on presentation of the work carried out by STF 547 | SmartM2M(19)051003 | LS in | discussion | Yes |
Yes
| noted | No | ||||
| S1‑192390 | Reply LS on Use Cases for eXtended Reality (XR) in 5G | S4-190972 | other | discussion | Yes |
Yes
| noted | No | ||||
| S1‑192391 | Reply LS on Medical Video Bitrates | S4-191073 | other | discussion | Yes |
Yes
| postponed | No | ||||
| 4 | New Study and Work Items (including related contributions) | S1‑192029 | new WID: Support for Minimization of service Interruption (MINT) | LG Electronics, Samsung, KT Corp, KRRI, SK Telecom, LG Uplus, ITL | WID new | Yes |
Yes
| revised | No | S1‑192405 | ||
| S1‑192405 | new WID: Support for Minimization of service Interruption (MINT) | LG Electronics, Samsung, KT Corp, KRRI, SK Telecom, LG Uplus, ITL | WID new | - | Yes |
Yes
| revised | No | S1‑192409 | S1‑192029 | ||
| S1‑192409 | new WID: Support for Minimization of service Interruption (MINT) | LG Electronics, Samsung, KT Corp, KRRI, SK Telecom, LG Uplus, ITL | WID new | - | Yes |
Yes
| revised | No | S1‑192711 | S1‑192405 | ||
| S1‑192711 | new WID: Support for Minimization of service Interruption (MINT) | LG Electronics, Samsung, KT Corp, KRRI, SK Telecom, LG Uplus, ITL | WID new | - | Yes |
Yes
| agreed | No | S1‑192409 | |||
| S1‑192045 | CR0XXX to to 22.261 on access control for MINT | LG Electronics | CR | Yes |
Yes
| withdrawn | Yes | |||||
| S1‑192046 | CR0XXX to to 22.011 on PLMN selection for MINT | LG Electronics | CR | No |
Yes
| withdrawn | Yes | |||||
| S1‑192052 | Study on requirements to enable AR/VR in 5G multimedia telephony service | China Mobile (Hangzhou) Inf. | SID new | Approval | No |
Yes
| withdrawn | Yes | ||||
| S1‑192074 | evolution of IMS multimedia telephony service | China Mobile | SID new | Approval | Yes |
Yes
| withdrawn | Yes | ||||
| S1‑192083 | Motivation for new SID evolution of IMS multimedia telephony service | China Mobile | other | Yes |
Yes
| withdrawn | Yes | |||||
| S1‑192086 | Enhanced Calling Name (eCNAM) Analytics Interworking | Ericsson, AT&T, T-Mobile US | WID new | Approval | Yes |
Yes
| revised | No | S1‑192377 | |||
| S1‑192377 | New WID on Enhanced Calling Name (eCNAM) Analytics Interworking ( eCNAM_An) | Ericsson, AT&T, T-Mobile US | WID new | Approval | Yes |
YesSection 8 is missing.
| revised | No | S1‑192675 | S1‑192086 | ||
| S1‑192675 | New WID on Enhanced Calling Name (eCNAM) Analytics Interworking ( eCNAM_An) | Ericsson, AT&T, T-Mobile US | WID new | Approval | Yes |
Yes
| revised | No | S1‑192715 | S1‑192377 | ||
| S1‑192715 | New WID on Enhanced Calling Name (eCNAM) Analytics Interworking ( eCNAM_An) | Ericsson, AT&T, T-Mobile US | WID new | Approval | Yes |
Yes
| agreed | No | S1‑192675 | |||
| S1‑192087 | Enhanced Calling Name (eCNAM) Analytics Interworking | Ericsson, AT&T, T-Mobile US | CR | Approval | Yes |
Yes
| revised | No | S1‑192378 | |||
| S1‑192378 | Enhanced Calling Name (eCNAM) Analytics Interworking | Ericsson, AT&T, T-Mobile US | CR | Approval | Yes |
YesThs is for the new WID eCNAM_An.
| revised | No | S1‑192677 | S1‑192087 | ||
| S1‑192677 | Enhanced Calling Name (eCNAM) Analytics Interworking | Ericsson, AT&T, T-Mobile US | CR | Approval | Yes |
Yes
| revised | No | S1‑192716 | S1‑192378 | ||
| S1‑192716 | Enhanced Calling Name (eCNAM) Analytics Interworking | Ericsson, AT&T, T-Mobile US, Charter Communications, Sprint, Verizon | CR | Approval | Yes |
Yes
| agreed | No | S1‑192677 | |||
| S1‑192101 | Discussion for new SID for Providing Textual information in a language appropriate for User (POTUS) | vivo Mobile Communication Co. LTD | CR | Discussion | Yes |
YesThere is some interest n the room. This is not for Rel-17, so it will be for next meeting.
| noted | No | ||||
| S1‑192104 | CR to 22.261 on access control for MINT | LG Electronics | CR | No |
Yes
| withdrawn | Yes | |||||
| S1‑192122 | New WID on Enhancement for the 5G Control Plane Steering of Roaming for UE in CONNECTED mode (eCPSOR_CON) | NTT DOCOMO INC. | WID new | Approval | Yes |
YesThis is to cover the CRs in 2123, S1-192249
and S1-192286.
| revised | No | S1‑192679 | |||
| S1‑192679 | New WID on Enhancement for the 5G Control Plane Steering of Roaming for UE in CONNECTED mode (eCPSOR_CON) | NTT DOCOMO INC. | WID new | Approval | Yes |
YesEricsson to be added as supporting company.
| revised | No | S1‑192717 | S1‑192122 | ||
| S1‑192717 | New WID on Enhancement for the 5G Control Plane Steering of Roaming for UE in CONNECTED mode (eCPSOR_CON) | NTT DOCOMO INC. | WID new | Approval | Yes |
Yes
| agreed | No | S1‑192679 | |||
| S1‑192123 | Enhancement for the 5G Control Plane Steering of Roaming for UE in CONNECTED mode | NTT DOCOMO INC. | CR | Approval | Yes |
Yes"It shall be possible" to be avoided.
Other rephrasing needed.
| revised | No | S1‑192678 | |||
| S1‑192678 | Enhancement for the 5G Control Plane Steering of Roaming for UE in CONNECTED mode | NTT DOCOMO INC. | CR | Approval | Yes |
Yes
| revised | No | S1‑192718 | S1‑192123 | ||
| S1‑192718 | Enhancement for the 5G Control Plane Steering of Roaming for UE in CONNECTED mode | NTT DOCOMO, T-Mobile USA, Perspecta Labs, Convida | CR | Approval | Yes |
Yes
| agreed | No | S1‑192678 | |||
| S1‑192132 | New WID on broadcast / multicast requirements supporting Mission Critical Services in 5G (5MBS_eMC) | BDBOS | WID new | Approval | Yes |
Yes
| revised | No | S1‑192680 | |||
| S1‑192680 | New WID on broadcast / multicast requirements supporting Mission Critical Services in 5G (5MBS_eMC) | BDBOS | WID new | Approval | Yes |
YesFurther edited while projecting.
| revised | No | S1‑192719 | S1‑192132 | ||
| S1‑192719 | New WID on broadcast / multicast requirements supporting Mission Critical Services in 5G (5MBS_eMC) | BDBOS | WID new | Approval | Yes |
Yes
| revised | No | S1‑192855 | S1‑192680 | ||
| S1‑192855 | New WID on broadcast / multicast requirements supporting Mission Critical Services in 5G (5MBS_eMC) | BDBOS | WID new | Approval | Yes |
Yes
| agreed | No | S1‑192719 | |||
| S1‑192133 | Broadcast / multicast requirements supporting Mission Critical Services in 5G | BDBOS | CR | Approval | Yes |
Yes
| revised | No | S1‑192681 | |||
| S1‑192681 | Broadcast / multicast requirements supporting Mission Critical Services in 5G | BDBOS | CR | Approval | Yes |
YesSeveral editorial problems (changes over changes, cover page, etc). Also the text itself should be rewritten for clarity reasons.
| revised | No | S1‑192720 | S1‑192133 | ||
| S1‑192720 | Broadcast / multicast requirements supporting Mission Critical Services in 5G | BDBOS, FirstNet, The Police of the Netherlands, MINISTERE DE L'INTERIEUR, Home Office, KPN | CR | Approval | Yes |
Yes
| revised | No | S1‑192826 | S1‑192681 | ||
| S1‑192826 | Broadcast / multicast requirements supporting Mission Critical Services in 5G | BDBOS, FirstNet, The Police of the Netherlands, MINISTERE DE L'INTERIEUR, Home Office, KPN | CR | Approval | Yes |
Yesproblem with upload.
| revised | No | S1‑192875 | S1‑192720 | ||
| S1‑192875 | Broadcast / multicast requirements supporting Mission Critical Services in 5G | BDBOS, FirstNet, The Police of the Netherlands, MINISTERE DE L'INTERIEUR, Home Office, KPN | CR | Approval | Yes |
No
| available | No | S1‑192826 | |||
| S1‑192158 | Motivation for new SID - evolution of IMS multimedia telephony service | China Mobile | SID new | Approval | Yes |
Yes
| noted | No | ||||
| S1‑192159 | new SID - evolution of IMS multimedia telephony service | China Mobile | SID new | Approval | Yes |
Yes
| withdrawn | Yes | ||||
| S1‑192160 | new SID - evolution of IMS multimedia telephony service | China Mobile | SID new | Approval | No |
Yes
| withdrawn | Yes | ||||
| S1‑192164 | new SID - evolution of IMS multimedia telephony service (FS_eMMTEL) | China Mobile | SID new | Approval | Yes |
Yes"cash-cow" expression should be avoided…
"eMMTEL" was already used in 2008.
| revised | No | S1‑192682 | |||
| S1‑192682 | new SID - evolution of IMS multimedia telephony service (FS_eMMTEL) | China Mobile | SID new | Approval | Yes |
YesParts (if not all) of what is described here is already availlable with the IMS. A gap analysis whould be a nice initial step to mention.
| revised | No | S1‑192721 | S1‑192164 | ||
| S1‑192721 | new SID - evolution of IMS multimedia telephony service (FS_MMTELin5G) | China Mobile | SID new | Approval | Yes |
Yes
| revised | No | S1‑192827 | S1‑192682 | ||
| S1‑192827 | new SID - evolution of IMS multimedia telephony service (FS_MMTELin5G) | China Mobile | SID new | Approval | Yes |
YesStatus Report in S1-192828
| agreed | No | S1‑192721 | |||
| S1‑192190 | Study on sharing administrative configuration between interconnected MCX systems (FS_SACI_MCS) | BDBOS | SID new | Approval | Yes |
YesFor Nokia, this is also already in place.
The Police of the Netherlands explained that this is again to do it in a standardised way rather than the present rather-proprietary ones.
Airbus also support.
| revised | No | S1‑192686 | |||
| S1‑192686 | Study on sharing administrative configuration between interconnected MCX systems (FS_SACI_MCS) | BDBOS | SID new | Approval | Yes |
Yes
| revised | No | S1‑192722 | S1‑192190 | ||
| S1‑192722 | Study on sharing administrative configuration between interconnected MCX systems (FS_SACI_MCS) | BDBOS | SID new | Approval | Yes |
Yes
| revised | No | S1‑192829 | S1‑192686 | ||
| S1‑192829 | Study on sharing administrative configuration between interconnected MCX systems (FS_SACI_MCS) | BDBOS | SID new | Approval | Yes |
YesStatus Report in S1-192830
| revised | No | S1‑192722 | |||
| S1‑192191 | Motivation Study on sharing administrative configuration between interconnected MCX systems | BDBOS | SID new | Discussion | Yes |
YesSee actual WID in 2190.
| noted | No | ||||
| S1‑192220 | New WID on Asset Tracking for 5G (ATRAC) | NOVAMINT | WID new | Yes |
YesMore supporting companies are available.
| revised | No | S1‑192670 | ||||
| S1‑192670 | New WID on Asset Tracking for 5G (ATRAC) | NOVAMINT | WID new | - | Yes |
Yes
| revised | No | S1‑192713 | S1‑192220 | ||
| S1‑192713 | New WID on Asset Tracking for 5G (ATRAC) | NOVAMINT | WID new | - | Yes |
Yes
| revised | No | S1‑192818 | S1‑192670 | ||
| S1‑192818 | New WID on Asset Tracking for 5G (ATRAC) | NOVAMINT | WID new | - | Yes |
YesPresentation in S1-192819
| revised | No | S1‑192713 | |||
| S1‑192237 | 22.261 - Asset Tracking Description and Requirements | NOVAMINT | CR | Yes |
Yes
| revised | No | S1‑192380 | ||||
| S1‑192380 | 22.261 - Asset Tracking Description and Requirements | NOVAMINT | CR | - | Yes |
Yes
| revised | No | S1‑192552 | S1‑192237 | ||
| S1‑192552 | 22.261 - Asset Tracking Description and Requirements | NOVAMINT | CR | - | Yes |
Yes
| revised | No | S1‑192774 | S1‑192380 | ||
| S1‑192774 | 22.261 - Asset Tracking Description and Requirements | NOVAMINT | CR | - | Yes |
Yes
| revised | No | S1‑192822 | S1‑192552 | ||
| S1‑192822 | 22.261 - Asset Tracking Description and Requirements | NOVAMINT | CR | - | Yes |
Yes
| agreed | No | S1‑192774 | |||
| S1‑192240 | KPIs for Asset Tracking in 5G system | NOVAMINT | CR | Yes |
Yes
| revised | No | S1‑192381 | ||||
| S1‑192381 | KPIs for Asset Tracking in 5G system | NOVAMINT | CR | - | Yes |
Yes
| revised | No | S1‑192553 | S1‑192240 | ||
| S1‑192553 | KPIs for Asset Tracking in 5G system | NOVAMINT | CR | - | Yes |
Yes
| revised | No | S1‑192777 | S1‑192381 | ||
| S1‑192777 | KPIs for Asset Tracking in 5G system | NOVAMINT | CR | - | Yes |
Yes
| revised | No | S1‑192873 | S1‑192553 | ||
| S1‑192873 | KPIs for Asset Tracking in 5G system | NOVAMINT | CR | - | No |
Yes
| agreed | No | S1‑192777 | |||
| S1‑192249 | eCSPOR CON requirement | Convida Wireless | other | Approval | Yes |
No
| withdrawn | Yes | ||||
| S1‑192257 | New WID on multi-device and multi-identity enhancements (MuDE) | vivo Mobile Communication Co. LTD | WID new | Approval | Yes |
YesT-Mobile explained that these fonctionalities can already be provided by the present version of the standard, there is no need to add any requirement for these.
For vivo, this might indeed be done but using proprietary solutions, which is not seen as an ideal solution.
Several companies want to further discuss off-line about what is missing.
| revised | No | S1‑192683 | |||
| S1‑192683 | New WID on multi-device and multi-identity enhancements (MuDE) | vivo Mobile Communication Co. LTD | WID new | Approval | Yes |
Yes
| revised | No | S1‑192712 | S1‑192257 | ||
| S1‑192712 | New WID on multi-device and multi-identity enhancements (MuDE) | vivo Mobile Communication Co. LTD | WID new | Approval | Yes |
Yes
| revised | No | S1‑192723 | S1‑192683 | ||
| S1‑192723 | New WID on multi-device and multi-identity enhancements (MuDE) | vivo Mobile Communication Co. LTD | WID new | Approval | Yes |
Yes
| revised | No | S1‑192831 | S1‑192712 | ||
| S1‑192831 | New WID on multi-device and multi-identity enhancements (MuDE) | vivo Mobile Communication Co. LTD | WID new | Approval | Yes |
YesStatus report in S1-192832
| revised | No | S1‑192860 | S1‑192723 | ||
| S1‑192860 | New WID on multi-device and multi-identity enhancements (MuDE) | vivo Mobile Communication Co. LTD | WID new | Approval | Yes |
YesThe grammar of the "objective" is confusing.
| revised | No | S1‑192876 | S1‑192831 | ||
| S1‑192876 | New WID on multi-device and multi-identity enhancements (MuDE) | vivo Mobile Communication Co. LTD | WID new | Approval | No |
Yes
| agreed | No | S1‑192860 | |||
| S1‑192258 | MuD user preferences | vivo Mobile Communication Co. LTD | CR | Approval | Yes |
YesSee comments on 2257.
| revised | No | S1‑192684 | |||
| S1‑192684 | MuD user preferences | vivo Mobile Communication Co. LTD | CR | Approval | Yes |
Yes
| revised | No | S1‑192724 | S1‑192258 | ||
| S1‑192724 | MuD user preferences | vivo Mobile Communication Co. LTD | CR | Approval | Yes |
Yes
| revised | No | S1‑192833 | S1‑192684 | ||
| S1‑192833 | MuD user preferences | vvivo Mobile Communication Co. LTD, Orange | CR | Approval | Yes |
YesSame change needed as in 2860.
Wrong WID acronym.
| revised | No | S1‑192877 | S1‑192724 | ||
| S1‑192877 | MuD user preferences | vvivo Mobile Communication Co. LTD, Orange | CR | Approval | No |
Yes
| revised | No | S1‑192833 | |||
| S1‑192282 | Revision of WID on service requirements on enhancements for cyber-physical control applications in vertical domains (eCAV) | Siemens | WID revised | Approval | Yes |
YesThe revision marks should be shown against the SA-approved version in SP-190310.
| revised | No | S1‑192671 | |||
| S1‑192671 | Revision of WID on service requirements on enhancements for cyber-physical control applications in vertical domains (eCAV) | Siemens | WID revised | Approval | Yes |
Yes
| revised | No | S1‑192714 | S1‑192282 | ||
| S1‑192714 | Revision of WID on service requirements on enhancements for cyber-physical control applications in vertical domains (eCAV) | Siemens | WID revised | Approval | Yes |
Yes
| revised | No | S1‑192823 | S1‑192671 | ||
| S1‑192823 | Revision of WID on service requirements on enhancements for cyber-physical control applications in vertical domains (eCAV) | Siemens | WID revised | Approval | Yes |
Yes"• Non-public networks, non-public networks as private slices, and further implications on security for non-public networks;" to be removed.
| revised | No | S1‑192874 | S1‑192714 | ||
| S1‑192874 | Revision of WID on service requirements on enhancements for cyber-physical control applications in vertical domains (eCAV) | Siemens | WID revised | Approval | No |
Yes
| agreed | No | S1‑192823 | |||
| S1‑192284 | revised SID: Study on enhancements for cyber-physical control applications in vertical domains (FS_eCAV) | Siemens | SID revised | Approval | Yes |
YesExtended date
| revised | No | S1‑192672 | |||
| S1‑192672 | revised SID: Study on enhancements for cyber-physical control applications in vertical domains (FS_eCAV) | Siemens | SID revised | Approval | No |
Yes
| withdrawn | Yes | S1‑192284 | |||
| S1‑192286 | eCSPOR req | Convida Wireless | other | Agreement | Yes |
YesMerged in 2678.
| merged | No | ||||
| S1‑192295 | Motivation for revision of Work Item eCAV on cyberCAV topics | Siemens | discussion | Discussion | Yes |
Yes
| revised | No | S1‑192396 | |||
| S1‑192396 | Motivation for revision of Work Item eCAV on cyberCAV topics | Siemens | discussion | Discussion | Yes |
Yes
| noted | No | S1‑192295 | |||
| S1‑192296 | New study on Supporting of Railway Smart Station Services (FS_RAILSS) | Hansung University | SID new | Agreement | Yes |
YesFor Nokia, Huawei and UIC, it is not clear what is missing in the existing TR 22.889.
| revised | No | S1‑192685 | |||
| S1‑192685 | New study on Supporting of Railway Smart Station Services (FS_RAILSS) | Hansung University | SID new | Agreement | Yes |
YesMore supporting companies to be added.
| revised | No | S1‑192879 | S1‑192296 | ||
| S1‑192879 | New study on Supporting of Railway Smart Station Services (FS_RAILSS) | Hansung University | SID new | Agreement | Yes |
Yes
| agreed | No | S1‑192685 | |||
| S1‑192319 | Introduction of Study on Supporting of Railway Smart Station Services (FS_RAILSS) | Hansung University | discussion | discussion | Yes |
YesSee actual WID in 2296.
| noted | No | ||||
| S1‑192376 | Discussion paper on application of STIR/SHAKEN to Emergency and Callback Calls | AT&T, Ericsson, T-Mobile USA Inc | other | discussion | Yes |
YesMost of the work is expected to be on SA2 but there are still some aspects impacting SA1.
Comments are invited off-line to AT&T and Ericsson.
| noted | No | ||||
| 5 | Quality improvement contributions | S1‑192030 | Clarification of dynamic policy control requirements | Nokia, Nokia Shanghai Bell, Vodafone | CR | Yes |
Yes
| revised | No | S1‑192687 | ||
| S1‑192687 | Clarification of dynamic policy control requirements | Nokia, Nokia Shanghai Bell, Vodafone | CR | - | Yes |
Yes
| agreed | No | S1‑192030 | |||
| S1‑192287 | Clarifications for KPIs on Low latency and high reliability scenarios | LG Electronics Deutschland | CR | Yes |
Yes
| revised | No | S1‑192688 | ||||
| S1‑192688 | Clarifications for KPIs on Low latency and high reliability scenarios | LG Electronics Deutschland | CR | - | Yes |
YesMore off-line work is needed.
| revised | No | S1‑192725 | S1‑192287 | ||
| S1‑192725 | Clarifications for KPIs on Low latency and high reliability scenarios | LG Electronics Deutschland | CR | - | Yes |
Yes"Proposed change affects" is blank.
| revised | No | S1‑192834 | S1‑192688 | ||
| S1‑192834 | Clarifications for KPIs on Low latency and high reliability scenarios | LG Electronics Deutschland | CR | - | Yes |
Yes
| agreed | No | S1‑192725 | |||
| S1‑192288 | Discussion paper on Clarification CR for KPIs on Low latency and high reliability scenarios | LG Electronics Deutschland | discussion | Yes |
Yes
| noted | No | |||||
| 6 | Rel-16 and earlier contributions | S1‑192041 | Information on the new work item related to public warning services over mobile networks in APT member countries | SyncTechno Inc. | discussion | Information | Yes |
Yes
| noted | No | ||
| S1‑192208 | Clarification of treatment of private call and private emergency calls to functional aliases activated by more than one MCX User | Nokia Germany | CR | Approval | Yes |
Yes
| revised | No | S1‑192673 | |||
| S1‑192673 | Clarification of treatment of private call and private emergency calls to functional aliases activated by more than one MCX User | Nokia Germany | CR | Approval | Yes |
Yes"The MC service" to be changed to "The MCX Service".
| revised | No | S1‑192693 | S1‑192208 | ||
| S1‑192693 | Clarification of treatment of private call and private emergency calls to functional aliases activated by more than one MCX User | Nokia Germany | CR | Approval | Yes |
Yes
| agreed | No | S1‑192673 | |||
| S1‑192212 | Clarification of treatment of private call and private emergency calls to functional aliases activated by more than one MCX User | Nokia Germany | CR | Approval | Yes |
Yes
| revised | No | S1‑192674 | |||
| S1‑192674 | Clarification of treatment of private call and private emergency calls to functional aliases activated by more than one MCX User | Nokia Germany | CR | Approval | Yes |
YesSame comments
| revised | No | S1‑192694 | S1‑192212 | ||
| S1‑192694 | Clarification of treatment of private call and private emergency calls to functional aliases activated by more than one MCX User | Nokia Germany | CR | Approval | Yes |
Yes
| agreed | No | S1‑192674 | |||
| 6.1 | Rel-16 correction and clarification CRs | S1‑192073 | Clarification for end-to-end latency | Huawei Tech.(UK) Co., Ltd | CR | Yes |
YesSeveral comments requested for off-line discussions, in particular on the different scenarios which apply.
| revised | No | S1‑192689 | ||
| S1‑192689 | Clarification for end-to-end latency | Huawei Tech.(UK) Co., Ltd | CR | - | No |
Yes
| withdrawn | Yes | S1‑192073 | |||
| S1‑192102 | Adapting text to language settings | vivo Mobile Communication Co., | CR | Approval | Yes |
YesAcronym should be TEI16 since eCNAM is Rel15.
Mistake on the "Release" in the cover page.
| revised | No | S1‑192690 | |||
| S1‑192690 | Adapting text to language settings | vivo Mobile Communication Co., | CR | Approval | No |
Yes
| withdrawn | Yes | S1‑192102 | |||
| S1‑192121 | Editorial corrections of TS 22.261 | China Telecom | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| S1‑192135 | Clarification for CSA requirements | Huawei | CR | Approval | Yes |
YesIt is wondered if a similar change for 22.264 would not be needed.
| revised | No | S1‑192692 | |||
| S1‑192692 | Clarification for CSA requirements | Huawei | CR | Approval | Yes |
Yes
| revised | No | S1‑192729 | S1‑192135 | ||
| S1‑192729 | Clarification for CSA requirements | Huawei, Siemens | CR | Approval | Yes |
YesWID should be cyberCAV.
No changes should be shown in the cover page.
"translation" to be changed in "mapping".
| revised | No | S1‑192835 | S1‑192692 | ||
| S1‑192835 | Clarification for CSA requirements | Huawei, Siemens | CR | Approval | Yes |
Yes
| agreed | No | S1‑192729 | |||
| S1‑192241 | Definition of absolute and relative positioning | Fraunhofer IIS | CR | Approval | Yes |
Yes
| revised | No | S1‑192413 | |||
| S1‑192413 | Definition of absolute and relative positioning | Fraunhofer IIS | CR | Approval | Yes |
Yes
| revised | No | S1‑192427 | S1‑192241 | ||
| S1‑192427 | Definition of absolute and relative positioning | Fraunhofer IIS | CR | Approval | Yes |
Yes
| revised | No | S1‑192460 | S1‑192413 | ||
| S1‑192460 | Definition of absolute and relative positioning | Fraunhofer IIS | CR | Approval | Yes |
Yes
| agreed | No | S1‑192427 | |||
| S1‑192259 | E911 requirements for SNPN | Charter Communications, Inc | discussion | Agreement | Yes |
YesSee actual CR in 2260.
| noted | No | ||||
| S1‑192260 | Emergency service requirement for Non-Public Network | Charter Communications, Inc | CR | Approval | Yes |
YesFor Qualcomm, this is nice to have, but in Rel-17.
Intel support having it in Rel-17.
Siemens objects to this CR (both for Rel-16 and Rel-17), since it was decided that this was not a context for voice calls.
A possible way out would be to clarify that this applies only to Non-Public Network which supports voice service (and which are connected to the public safety…).
For Nokia, this requirement is very strange to have for NPN, since this is a case that would rarely -if never- happens, that a user connected to a NPN needs to make an emergency call.
It could be acceptable to have the requirement if all the pre-conditions are clarified.
| revised | No | S1‑192695 | |||
| S1‑192695 | Emergency service requirement for Non-Public Network | Charter Communications, Inc | CR | Approval | Yes |
Yes
| revised | No | S1‑192726 | S1‑192260 | ||
| S1‑192726 | Emergency service requirement for Non-Public Network | Charter Communications, Inc | CR | Approval | Yes |
YesAsked to be postponed to November by Qualcomm.
| noted | No | S1‑192695 | |||
| S1‑192275 | Correction of a figure number in Annex D.2 | ETRI | CR | Yes |
YesThis should be editorial (category D).
| revised | No | S1‑192696 | ||||
| S1‑192696 | Correction of a figure number in Annex D.2 | ETRI | CR | - | Yes |
Yes
| agreed | No | S1‑192275 | |||
| S1‑192277 | Correction of a figure number in Annex D.2 | ETRI | CR | Yes |
YesWI code should be the same as the original Release.
| revised | No | S1‑192697 | ||||
| S1‑192697 | Correction of a figure number in Annex D.2 | ETRI | CR | - | Yes |
Yes
| agreed | No | S1‑192277 | |||
| S1‑192279 | Deletion of positioning performance requirements | ETRI | CR | Yes |
YesThis is said in particular by Sony to be not the same context: 22.261 is HyPos, 22.104 is for industrial automation.
| noted | No | |||||
| S1‑192280 | Deletion of positioning performance requirements | ETRI | CR | Yes |
YesMirror of 2279, which is not agreed.
| noted | No | |||||
| S1‑192281 | Modification of positioning service and high accuracy positioning | ETRI | CR | Yes |
YesThere seems to be mistake in numberring the notes in the table.
| revised | No | S1‑192698 | ||||
| S1‑192698 | Modification of positioning service and high accuracy positioning | ETRI | CR | - | Yes |
Yes
| agreed | No | S1‑192281 | |||
| 6.2 | Release 15 Alignment CRs (aligning Stage 1 specifications with what has been implemented in Stage 2 and 3) | |||||||||||
| 6.3 | Rel-15 and earlier CRs (other than alignment) | |||||||||||
| 7 | Rel-17 Study Item contributions | |||||||||||
| 7.1 | FS_AVPROD: Feasibility Study on Audio-Visual Service Production [SP-181015] | S1‑192151 | Clarification and pCR to TR 22.827 on AVProd | Tencent | pCR | Approval | Yes |
Yes
| revised | No | S1‑192470 | |
| S1‑192470 | Clarification and pCR to TR 22.827 on AVProd | Tencent | pCR | Approval | Yes |
Yes
| revised | No | S1‑192512 | S1‑192151 | ||
| S1‑192512 | Clarification and pCR to TR 22.827 on AVProd | Tencent | pCR | Approval | Yes |
Yes
| revised | No | S1‑192738 | S1‑192470 | ||
| S1‑192738 | Clarification and pCR to TR 22.827 on AVProd | Tencent | pCR | Approval | Yes |
Yes
| agreed | No | S1‑192512 | |||
| S1‑192152 | New Use Case and Requirements for Video Production with Remote Production Centre | Tencent | pCR | Approval | Yes |
Yes
| noted | No | ||||
| S1‑192203 | TR22.827_EditorialChanges | EBU | pCR | Approval | Yes |
Yes
| revised | No | S1‑192676 | |||
| S1‑192676 | TR22.827_EditorialChanges | EBU | pCR | Approval | Yes |
Yes
| revised | No | S1‑192471 | S1‑192203 | ||
| S1‑192471 | TR22.827_EditorialChanges | EBU | pCR | Approval | Yes |
Yes
| revised | No | S1‑192514 | S1‑192676 | ||
| S1‑192514 | TR22.827_EditorialChanges | EBU | pCR | Approval | Yes |
Yes
| agreed | No | S1‑192471 | |||
| S1‑192204 | TR22.827_ConsolidatedRequirements | EBU | pCR | Approval | Yes |
Yes
| revised | No | S1‑192474 | |||
| S1‑192474 | TR22.827_ConsolidatedRequirements | EBU | pCR | Approval | Yes |
Yes
| revised | No | S1‑192517 | S1‑192204 | ||
| S1‑192517 | TR22.827_ConsolidatedRequirements | EBU | pCR | Approval | Yes |
Yes
| revised | No | S1‑192740 | S1‑192474 | ||
| S1‑192740 | TR22.827_ConsolidatedRequirements | EBU | pCR | Approval | Yes |
Yes
| agreed | No | S1‑192517 | |||
| S1‑192205 | TR22.827_ConsolidatedDualConnectivity | EBU | pCR | Approval | Yes |
Yes
| revised | No | S1‑192473 | |||
| S1‑192473 | TR22.827_ConsolidatedDualConnectivity | EBU | pCR | Approval | Yes |
Yes
| revised | No | S1‑192516 | S1‑192205 | ||
| S1‑192516 | TR22.827_ConsolidatedDualConnectivity | EBU | pCR | Approval | Yes |
Yes
| revised | No | S1‑192739 | S1‑192473 | ||
| S1‑192739 | TR22.827_ConsolidatedDualConnectivity | EBU | pCR | Approval | Yes |
Yes
| agreed | No | S1‑192516 | |||
| S1‑192343 | TR22.887v1.2.0 to include agreements at this meeting | Rapporteur (EBU) | TR | discussion | No |
Yes
| agreed | No | ||||
| S1‑192344 | Cover page for presentation of TR22.887v1.2.0 | Rapporteur (EBU) | other | discussion | Yes |
Yes
| agreed | No | ||||
| S1‑192345 | AVPROD+CMED drafting agenda | Session Chair | AGE | discussion | Yes |
Yes
| noted | No | ||||
| S1‑192346 | AVPROD+CMED drafting report | Session Chair | REP | discussion | Yes |
Yes
| noted | No | ||||
| 7.2 | FS_MPS2: Feasibility Study on Multimedia Priority Service (MPS) Phase 2 [SP-190315] | S1‑192215 | TR 22.854 v1.1.0 Clean-up | Perspecta Labs Inc., CISA ECD, Sprint, Verizon, AT&T, T-Mobile USA | pCR | Agreement | Yes |
Yes
| agreed | No | ||
| S1‑192219 | TR 22.854: Additional MPS for DTS requirements and clarifications | Perspecta Labs, CISA ECD, AT&T, T-Mobile USA, Verizon | pCR | Agreement | Yes |
Yes
| revised | No | S1‑192626 | |||
| S1‑192626 | TR 22.854: Additional MPS for DTS requirements and clarifications | Perspecta Labs, CISA ECD, AT&T, T-Mobile USA, Verizon | pCR | Agreement | Yes |
Yes
| agreed | No | S1‑192219 | |||
| S1‑192221 | TR 22.854: Additional Requirements for MPS Video | Perspecta Labs, CISA ECD, Sprint, Verizon, AT&T, T-Mobile USA | pCR | Agreement | Yes |
Yes
| revised | No | S1‑192627 | |||
| S1‑192627 | TR 22.854: Additional Requirements for MPS Video | Perspecta Labs, CISA ECD, Sprint, Verizon, AT&T, T-Mobile USA | pCR | Agreement | Yes |
Yes
| agreed | No | S1‑192221 | |||
| S1‑192223 | TR 22.854: Additional MPS voice requirements and new use case on MMTEL voice conference host invocation of MPS for all participants | Perspecta Labs, CISA ECD, Sprint, Verizon, AT&T, T-Mobile USA | pCR | Agreement | Yes |
Yes
| revised | No | S1‑192628 | |||
| S1‑192628 | TR 22.854: Additional MPS voice requirements and new use case on MMTEL voice conference host invocation of MPS for all participants | Perspecta Labs, CISA ECD, Sprint, Verizon, AT&T, T-Mobile USA | pCR | Agreement | Yes |
Yes
| agreed | No | S1‑192223 | |||
| S1‑192225 | TR 22.854: Modifications to QoS requirements [PR.6.8.6-002] and [PR.6.8.6-005] | Perspecta Labs, CISA ECD, Sprint, Verizon, AT&T, T-Mobile USA | pCR | Agreement | Yes |
Yes
| revised | No | S1‑192629 | |||
| S1‑192629 | TR 22.854: Modifications to QoS requirements [PR.6.8.6-002] and [PR.6.8.6-005] | Perspecta Labs, CISA ECD, Sprint, Verizon, AT&T, T-Mobile USA | pCR | Agreement | Yes |
Yes
| agreed | No | S1‑192225 | |||
| S1‑192347 | TR 22.854v1.2.0 to include agreements at this meeting | Rapporteur (Perspecta Labs) | TR | discussion | No |
YesAgreed for approval to SA.
| agreed | No | ||||
| S1‑192348 | Cover page for presentation of TR22.854v1.2.0 | Rapporteur (Perspecta Labs) | other | discussion | Yes |
Yes
| agreed | No | ||||
| 7.3 | FS_CMED: Feasibility Study on Communication Services for Critical Medical Applications [SP-180783] | S1‑192053 | Addition of Abbreviations section in TR 22.826 | B-Com | pCR | Approval | Yes |
Yes
| agreed | No | ||
| S1‑192054 | Addition of a synchronisation requirement in use case 5.3.3 (Communication QoS requirement for robotic telesurgery) | B-Com | pCR | Approval | Yes |
Yes
| revised | No | S1‑192476 | |||
| S1‑192476 | Addition of a synchronisation requirement in use case 5.3.3 (Communication QoS requirement for robotic telesurgery) | B-Com | pCR | Approval | Yes |
Yes
| agreed | No | S1‑192054 | |||
| S1‑192055 | TR 22.826 final clean up | B-Com | pCR | Approval | Yes |
Yes
| revised | No | S1‑192475 | |||
| S1‑192475 | TR 22.826 final clean up | B-Com | pCR | Approval | Yes |
Yes
| agreed | No | S1‑192055 | |||
| S1‑192056 | Addition of Conclusion and recommendations section in TR 22.826 | B-Com | pCR | Approval | Yes |
Yes
| revised | No | S1‑192479 | |||
| S1‑192479 | Addition of Conclusion and recommendations section in TR 22.826 | B-Com | pCR | Approval | Yes |
Yes
| revised | No | S1‑192706 | S1‑192056 | ||
| S1‑192706 | Addition of Conclusion and recommendations section in TR 22.826 | B-Com | pCR | Approval | Yes |
Yes
| agreed | No | S1‑192479 | |||
| S1‑192131 | Alignment of use case description text and Survival Time requirements | B-Com | pCR | Approval | Yes |
Yes
| agreed | No | ||||
| S1‑192165 | consolidation for clock synchronization in TR 22.826 | Huawei Tech.(UK) Co., Ltd | other | Yes |
Yes
| revised | No | S1‑192477 | ||||
| S1‑192477 | consolidation for clock synchronization in TR 22.826 | Huawei Tech.(UK) Co., Ltd | other | - | Yes |
Yes
| agreed | No | S1‑192165 | |||
| S1‑192216 | FS_CMED Use Case Mobile Specialist Practice | Siemens AG | pCR | Agreement | Yes |
Yes
| revised | No | S1‑192505 | |||
| S1‑192505 | FS_CMED Use Case Mobile Specialist Practice | Siemens AG | pCR | Agreement | Yes |
Yes
| agreed | No | S1‑192216 | |||
| S1‑192239 | FS_CMED_Integrity protection of medical data at very high datarates | Philips International B.V. | pCR | Approval | Yes |
Yes
| revised | No | S1‑192478 | |||
| S1‑192478 | FS_CMED_Integrity protection of medical data at very high datarates | Philips International B.V. | pCR | Approval | Yes |
Yes
| revised | No | S1‑192741 | S1‑192239 | ||
| S1‑192741 | FS_CMED_Integrity protection of medical data at very high datarates | Philips International B.V. | pCR | Approval | Yes |
Yes
| agreed | No | S1‑192478 | |||
| S1‑192252 | FS_CMED_Updates related to cardiac telemetry monitoring | Philips International B.V. | pCR | Approval | Yes |
Yes
| revised | No | S1‑192504 | |||
| S1‑192504 | FS_CMED_Updates related to cardiac telemetry monitoring | Philips International B.V. | pCR | Approval | Yes |
Yes
| revised | No | S1‑192746 | S1‑192252 | ||
| S1‑192746 | FS_CMED_Updates related to cardiac telemetry monitoring | Philips International B.V. | pCR | Approval | Yes |
YesEditorial typos to be corrected bythe editor.
| agreed | No | S1‑192504 | |||
| S1‑192349 | TR 22.826v1.1.0 to include agreements at this meeting | Rapporteur (b<>com) | TR | discussion | Yes |
Yes
| agreed | No | ||||
| S1‑192350 | Cover page for presentation of TR 22.826v1.1.0 | Rapporteur (b<>com) | TR | discussion | Yes |
YesThe TR will be presented for approval and not fo rinformation.
| revised | No | S1‑192880 | |||
| S1‑192880 | Cover page for presentation of TR 22.826v1.1.0 | Rapporteur (b<>com) | other | discussion | No |
Yes
| agreed | No | S1‑192350 | |||
| 7.4 | FS_5G_ATRAC: Study on Asset Tracking Use Cases [SP-180922] | S1‑192066 | ATRAC – TR Consolidated Requirements | NOVAMINT | pCR | Approval | Yes |
Yes
| revised | No | S1‑192550 | |
| S1‑192550 | ATRAC – TR Consolidated Requirements | NOVAMINT | pCR | Approval | Yes |
Yes
| agreed | No | S1‑192066 | |||
| S1‑192067 | ATRAC – TR Consolidated KPIs | NOVAMINT | pCR | Yes |
Yes
| revised | No | S1‑192551 | ||||
| S1‑192551 | ATRAC – TR Consolidated KPIs | NOVAMINT | pCR | - | Yes |
Yes
| revised | No | S1‑192773 | S1‑192067 | ||
| S1‑192773 | ATRAC – TR Consolidated KPIs | NOVAMINT | pCR | - | Yes |
Yes
| agreed | No | S1‑192551 | |||
| S1‑192070 | ATRAC – TR Clean Up | NOVAMINT | pCR | Approval | Yes |
Yes
| agreed | No | ||||
| S1‑192071 | ATRAC – TR Conclusion | NOVAMINT | pCR | Approval | Yes |
Yes
| agreed | No | ||||
| S1‑192351 | TR22.836v0.3.0 to include agreements at this meeting | Rapporteur (Novamint) | TR | discussion | No |
Yes
| agreed | No | ||||
| S1‑192352 | Cover page for presentation of TR22.836v0.3.0 | Rapporteur (Novamint) | TR | discussion | No |
No
| reserved | No | ||||
| S1‑192353 | REFEC+ATRAC drafting agenda | Session Chair | AGE | discussion | Yes |
Yes
| noted | No | ||||
| S1‑192354 | REFEC+ATRAC drafting report | Session Chair | REP | discussion | Yes |
Yes
| noted | No | ||||
| 7.5 | FS_REFEC: Study on enhanced Relays for Energy eFficiency and Extensive Coverage [SP-180785] | S1‑192088 | Update Use Case 5.1 for Enabling Access Control | Intel | pCR | Approval | Yes |
Yes
| revised | No | S1‑192555 | |
| S1‑192555 | Update Use Case 5.1 for Enabling Access Control | Intel | pCR | Approval | Yes |
YesS1-192785 was allocated for revision but the previous version in S1-192555 can finally be agreed.
| agreed | No | S1‑192088 | |||
| S1‑192785 | Update Use Case 5.1 for Enabling Access Control | Intel | pCR | Approval | No |
YesWas allocated for revision of S1-192555
| withdrawn | Yes | ||||
| S1‑192139 | FS_REFEC_Proposed requirement text for network slicing. | Philips International B.V. | pCR | Approval | Yes |
Yes
| revised | No | S1‑192556 | |||
| S1‑192556 | FS_REFEC_Proposed requirement text for network slicing. | Philips International B.V. | pCR | Approval | Yes |
Yes
| revised | No | S1‑192779 | S1‑192139 | ||
| S1‑192779 | FS_REFEC_Proposed requirement text for network slicing. | Philips International B.V. | pCR | Approval | Yes |
Yes
| noted | No | S1‑192556 | |||
| S1‑192145 | FS_REFEC – TR Overview section | KPN | pCR | Agreement | Yes |
Yes
| revised | No | S1‑192382 | |||
| S1‑192382 | FS_REFEC – TR Overview section | KPN | pCR | Agreement | Yes |
Yes
| revised | No | S1‑192554 | S1‑192145 | ||
| S1‑192554 | FS_REFEC – TR Overview section | KPN | pCR | Agreement | Yes |
Yes
| revised | No | S1‑192778 | S1‑192382 | ||
| S1‑192778 | FS_REFEC – TR Overview section | KPN | pCR | Agreement | Yes |
Yes
| agreed | No | S1‑192554 | |||
| S1‑192146 | FS_REFEC – TR Consolidated Requirements | KPN | pCR | Agreement | Yes |
Yes
| revised | No | S1‑192576 | |||
| S1‑192576 | FS_REFEC – TR Consolidated Requirements | KPN | pCR | Agreement | Yes |
Yes
| revised | No | S1‑192836 | S1‑192146 | ||
| S1‑192836 | FS_REFEC – TR Consolidated Requirements | KPN | pCR | Agreement | Yes |
Yes
| revised | No | S1‑192843 | S1‑192576 | ||
| S1‑192843 | FS_REFEC – TR Consolidated Requirements | KPN | pCR | Agreement | Yes |
Yes
| agreed | No | S1‑192836 | |||
| S1‑192147 | FS_REFEC – TR Conclusion and recommendations | KPN | pCR | Agreement | Yes |
Yes
| revised | No | S1‑192577 | |||
| S1‑192577 | FS_REFEC – TR Conclusion and recommendations | KPN | pCR | Agreement | Yes |
Yes
| agreed | No | S1‑192147 | |||
| S1‑192149 | FS_REFEC_Clean up requirement text about application layer groups | Philips International B.V. | pCR | Approval | Yes |
Yes
| agreed | No | ||||
| S1‑192166 | Update of traffic scenario: InHome | KPN | pCR | Agreement | Yes |
YesSame comment as for 2569.
| revised | No | S1‑192781 | |||
| S1‑192781 | Update of traffic scenario: InHome | KPN | pCR | Agreement | Yes |
Yes
| agreed | No | S1‑192166 | |||
| S1‑192167 | Update of traffic scenario: SmartFactory | KPN | pCR | Agreement | Yes |
Yes
| revised | No | S1‑192569 | |||
| S1‑192569 | Update of traffic scenario: SmartFactory | KPN | pCR | Agreement | Yes |
Yes"maximm" number of hops to be changed to "estimated"
| revised | No | S1‑192780 | S1‑192167 | ||
| S1‑192780 | Update of traffic scenario: SmartFactory | KPN | pCR | Agreement | Yes |
Yes
| agreed | No | S1‑192569 | |||
| S1‑192168 | Update of traffic scenario: Metering use case | KPN | pCR | Agreement | Yes |
Yes
| revised | No | S1‑192570 | |||
| S1‑192570 | Update of traffic scenario: Metering use case | KPN | pCR | Agreement | Yes |
YesSame comment as for 2569.
| revised | No | S1‑192838 | S1‑192168 | ||
| S1‑192838 | Update of traffic scenario: Metering use case | KPN | pCR | Agreement | No |
Yes
| agreed | No | S1‑192570 | |||
| S1‑192169 | Update of traffic scenario: Containers | KPN | pCR | Agreement | Yes |
Yes
| revised | No | S1‑192571 | |||
| S1‑192571 | Update of traffic scenario: Containers | KPN | pCR | Agreement | Yes |
Yes
| revised | No | S1‑192782 | S1‑192169 | ||
| S1‑192782 | Update of traffic scenario: Containers | KPN | pCR | Agreement | Yes |
Yes
| revised | No | S1‑192839 | S1‑192571 | ||
| S1‑192839 | Update of traffic scenario: Containers | KPN | pCR | Agreement | No |
Yes
| agreed | No | S1‑192782 | |||
| S1‑192170 | Update of traffic scenario: Freight wagons | KPN | pCR | Agreement | Yes |
Yes
| revised | No | S1‑192568 | |||
| S1‑192568 | Update of traffic scenario: Freight wagons | KPN | pCR | Agreement | Yes |
Yes
| revised | No | S1‑192572 | S1‑192170 | ||
| S1‑192572 | Update of traffic scenario: Freight wagons | KPN | pCR | Agreement | Yes |
YesSame comment as for 2569.
| revised | No | S1‑192783 | S1‑192568 | ||
| S1‑192783 | Update of traffic scenario: Freight wagons | KPN | pCR | Agreement | Yes |
Yes
| revised | No | S1‑192840 | S1‑192572 | ||
| S1‑192840 | Update of traffic scenario: Freight wagons | KPN | pCR | Agreement | No |
Yes
| agreed | No | S1‑192783 | |||
| S1‑192171 | New traffic scenario: Public Safety | KPN | pCR | Agreement | Yes |
Yes
| revised | No | S1‑192573 | |||
| S1‑192573 | New traffic scenario: Public Safety | KPN | pCR | Agreement | Yes |
Yes
| revised | No | S1‑192841 | S1‑192171 | ||
| S1‑192841 | New traffic scenario: Public Safety | KPN | pCR | Agreement | Yes |
No
| available | No | S1‑192573 | |||
| S1‑192180 | New traffic scenario: Wearables | KPN | pCR | Agreement | Yes |
Yes
| revised | No | S1‑192574 | |||
| S1‑192574 | New traffic scenario: Wearables | KPN | pCR | Agreement | Yes |
YesSame comment as for 2569.
| revised | No | S1‑192784 | S1‑192180 | ||
| S1‑192784 | New traffic scenario: Wearables | KPN | pCR | Agreement | Yes |
Yes
| agreed | No | S1‑192574 | |||
| S1‑192183 | Traffic Scenario - consolidation | KPN | pCR | Agreement | Yes |
Yes
| revised | No | S1‑192575 | |||
| S1‑192575 | Traffic Scenario - consolidation | KPN | pCR | Agreement | Yes |
Yes
| revised | No | S1‑192842 | S1‑192183 | ||
| S1‑192842 | Traffic Scenario - consolidation | KPN | pCR | Agreement | Yes |
Yes
| agreed | No | S1‑192575 | |||
| S1‑192187 | FS_REFEC Coverage enhancements for delay tolerant data | Convida Wireless | pCR | Approval | Yes |
Yes
| revised | No | S1‑192558 | |||
| S1‑192558 | FS_REFEC Coverage enhancements for delay tolerant data | Convida Wireless | pCR | Approval | Yes |
Yes
| revised | No | S1‑192727 | S1‑192187 | ||
| S1‑192727 | FS_REFEC Coverage enhancements for delay tolerant data | Convida Wireless | pCR | Approval | Yes |
YesSony, Vodafone and 3 other companies think that this needs more study.
| noted | No | S1‑192558 | |||
| S1‑192213 | FS_REFEC_Proposed requirement text related to QoS | Philips International B.V. | pCR | Approval | Yes |
Yes
| revised | No | S1‑192557 | |||
| S1‑192557 | FS_REFEC_Proposed requirement text related to QoS | Philips International B.V. | pCR | Approval | Yes |
YesSome companies (including Sony, Alcatel) think this is not needed, no agreement on this requirement.
| noted | No | S1‑192213 | |||
| S1‑192278 | FS_REFEC Considerations | KPN | pCR | Agreement | No |
Yes
| revised | No | S1‑192383 | |||
| S1‑192383 | FS_REFEC Considerations | KPN | pCR | Agreement | Yes |
Yes
| agreed | No | S1‑192278 | |||
| S1‑192355 | TR22.866v0.3.0 to include agreements at this meeting | Rapporteur (KPN) | TR | discussion | No |
YesFor one-step approval to the plenary.
| agreed | No | ||||
| S1‑192356 | Cover page for presentation of TR22.866v0.3.0 | Rapporteur (KPN) | other | discussion | Yes |
YesThe TR goes to one-step approval.
| agreed | No | ||||
| S1‑192587 | Not used | Reserved Greg | other | discussion | No |
Yes
| withdrawn | Yes | ||||
| S1‑192588 | Way Forward for MUSIM | Intel | other | discussion | Yes |
Yes
| revised | No | S1‑192589 | |||
| S1‑192589 | Way Forward for MUSIM | Intel | other | discussion | Yes |
YesThe author wants to remove it.
| noted | No | S1‑192588 | |||
| S1‑192590 | Not used | Reserved Greg | other | discussion | No |
Yes
| withdrawn | Yes | ||||
| S1‑192591 | Not used | Reserved Greg | other | discussion | No |
Yes
| withdrawn | Yes | ||||
| S1‑192592 | Not used | Reserved Greg | other | discussion | No |
Yes
| withdrawn | Yes | ||||
| S1‑192593 | Not used | Reserved Greg | other | discussion | No |
Yes
| withdrawn | Yes | ||||
| S1‑192594 | Not used | Reserved Greg | other | discussion | No |
Yes
| withdrawn | Yes | ||||
| S1‑192595 | Not used | Reserved Greg | other | discussion | No |
Yes
| withdrawn | Yes | ||||
| S1‑192596 | Not used | Reserved Greg | other | discussion | No |
Yes
| withdrawn | Yes | ||||
| S1‑192597 | Not used | Reserved Greg | other | discussion | No |
Yes
| withdrawn | Yes | ||||
| S1‑192598 | Not used | Reserved Greg | other | discussion | No |
Yes
| withdrawn | Yes | ||||
| S1‑192599 | Not used | Reserved Greg | other | discussion | No |
Yes
| withdrawn | Yes | ||||
| S1‑192600 | Not used | Reserved Greg | other | discussion | No |
Yes
| withdrawn | Yes | ||||
| S1‑192601 | Not used | Reserved Greg | other | discussion | No |
Yes
| withdrawn | Yes | ||||
| S1‑192602 | Not used | Reserved Greg | other | discussion | No |
Yes
| withdrawn | Yes | ||||
| S1‑192603 | Not used | Reserved Greg | other | discussion | No |
Yes
| withdrawn | Yes | ||||
| S1‑192604 | Not used | Reserved Greg | other | discussion | No |
Yes
| withdrawn | Yes | ||||
| S1‑192605 | Not used | Reserved Greg | other | discussion | No |
Yes
| withdrawn | Yes | ||||
| S1‑192606 | Not used | Reserved Greg | other | discussion | No |
Yes
| withdrawn | Yes | ||||
| S1‑192607 | Not used | Reserved Greg | other | discussion | No |
Yes
| withdrawn | Yes | ||||
| S1‑192608 | Not used | Reserved Greg | other | discussion | No |
Yes
| withdrawn | Yes | ||||
| S1‑192609 | Not used | Reserved Greg | other | discussion | No |
Yes
| withdrawn | Yes | ||||
| 7.6 | FS_EAV: Study on enhancement for UAVs [SP-180909] | S1‑192016 | CR to 22.829 Correction to potential Consolidated Requirements for UAV | LG Electronics | CR | Yes |
Yes
| revised | No | S1‑192481 | ||
| S1‑192481 | CR to 22.829 Correction to potential Consolidated Requirements for UAV | LG Electronics | CR | - | Yes |
Yes
| agreed | No | S1‑192016 | |||
| S1‑192017 | CR to 22.829 Additional Consolidated Requirements for UAV | LG Electronics | CR | Yes |
Yes
| revised | No | S1‑192482 | ||||
| S1‑192482 | CR to 22.829 Additional Consolidated Requirements for UAV | LG Electronics | CR | - | Yes |
Yes
| agreed | No | S1‑192017 | |||
| S1‑192081 | Processing of editor note of TR 22.829 | China Unicom | CR | Approval | Yes |
Yes
| revised | No | S1‑192483 | |||
| S1‑192483 | Processing of editor note of TR 22.829 | China Unicom | CR | Approval | Yes |
YesChanged while projecting.
| revised | No | S1‑192789 | S1‑192081 | ||
| S1‑192789 | Processing of editor note of TR 22.829 | China Unicom, Futurewei | CR | Approval | Yes |
Yes
| agreed | No | S1‑192483 | |||
| S1‑192137 | CR to 22.829 supplement service experience assurance requirements for UAV | China Unicom | CR | Approval | Yes |
Yes
| revised | No | S1‑192484 | |||
| S1‑192484 | CR to 22.829 supplement service experience assurance requirements for UAV | China Unicom | CR | Approval | Yes |
Yes
| revised | No | S1‑192790 | S1‑192137 | ||
| S1‑192790 | CR to 22.829 supplement service experience assurance requirements for UAV | China Unicom | CR | Approval | No |
Yes
| withdrawn | Yes | S1‑192484 | |||
| S1‑192162 | Delete the editor’s note in 5.11 | CATT | CR | Yes |
Yes
| agreed | No | |||||
| S1‑192357 | TR22.829v0.4.0 to include agreements at this meeting | Rapporteur (China Unicom) | TR | discussion | No |
Yes
| withdrawn | Yes | ||||
| S1‑192358 | Cover page for presentation of TR22.829v0.4.0 | Rapporteur (China Unicom) | TR | discussion | No |
Yes
| withdrawn | Yes | ||||
| S1‑192359 | EAV drafting agenda | Session Chair | AGE | discussion | Yes |
Yes
| noted | No | ||||
| S1‑192360 | EAV drafting report | Session Chair | REP | discussion | Yes |
YesHighlight the following items:;
- FS_EVA: 5 tdocs; 3 agreed;
- EAV: 14 tdocs; 3 noted, 2 merged; issues include: due to SA1’s parallel progress with Study and Work, most EAV Work tdocs still require the outcome of Study tdocs still under discussion at this meeting;
- discussion points include: at which point in TS 22.125, the outcome of EAV to be put; some CR proposals were considered not immediately related to EAV WI, so agreed to have a different WI code (e.g., TEI16 or something else)
| noted | No | ||||
| 7.7 | FS_MINT: Study on Support for Minimization of service Interruption [SP-190090] | S1‑192013 | 23.831 P-CR: MINT Scope | Samsung, LG Electronics | pCR | Agreement | Yes |
Yes
| revised | No | S1‑192493 | |
| S1‑192493 | 23.831 P-CR: MINT Scope | Samsung, LG Electronics | pCR | Agreement | Yes |
Yes
| agreed | No | S1‑192013 | |||
| S1‑192014 | 23.831 P-CR: MINT HPLMN Failure is out of Scope | Samsung | pCR | Agreement | Yes |
Yes
| revised | No | S1‑192768 | |||
| S1‑192768 | 23.831 P-CR: MINT HPLMN Failure is out of Scope | Samsung | pCR | Agreement | Yes |
Yes
| agreed | No | S1‑192014 | |||
| S1‑192015 | Introduction of Minimization of Service Interruption (MINT) | Samsung, LG Electronics | CR | Agreement | Yes |
Yes
| revised | Yes | S1‑192499 | |||
| S1‑192499 | Introduction of Minimization of Service Interruption (MINT) | Samsung, LG Electronics | CR | Agreement | Yes |
Yes
| revised | No | S1‑192845 | S1‑192015 | ||
| S1‑192845 | Introduction of Minimization of Service Interruption (MINT) | Samsung, LG Electronics | CR | Agreement | Yes |
Yes
| agreed | No | S1‑192499 | |||
| S1‑192023 | FS_MINT: General update on TR22.831 V0.1.0 | LG Electronics | pCR | Yes |
Yes
| revised | No | S1‑192492 | ||||
| S1‑192492 | FS_MINT: General update on TR22.831 V0.1.0 | LG Electronics | pCR | - | Yes |
Yes
| agreed | No | S1‑192023 | |||
| S1‑192024 | FS_MINT: Update of Section 5.8 | LG Electronics, KT Corp, LG Uplus | pCR | Yes |
Yes
| revised | No | S1‑192496 | ||||
| S1‑192496 | FS_MINT: Update of Section 5.8 | LG Electronics, KT Corp, LG Uplus | pCR | - | Yes |
Yes
| revised | No | S1‑192769 | S1‑192024 | ||
| S1‑192769 | FS_MINT: Update of Section 5.8 | LG Electronics, KT Corp, LG Uplus | pCR | - | Yes |
Yes
| agreed | No | S1‑192496 | |||
| S1‑192025 | FS_MINT: Update of Section 5.2 and 5.9 | LG Electronics, LG Uplus, KT Corp | pCR | Yes |
Yes
| revised | No | S1‑192497 | ||||
| S1‑192497 | FS_MINT: Update of Section 5.2 and 5.9 | LG Electronics, LG Uplus, KT Corp | pCR | - | Yes |
Yes
| revised | No | S1‑192770 | S1‑192025 | ||
| S1‑192770 | FS_MINT: Update of Section 5.2 and 5.9 | LG Electronics, LG Uplus, KT Corp | pCR | - | Yes |
Yes
| agreed | No | S1‑192497 | |||
| S1‑192026 | FS_MINT: Text proposal for Overview | LG Electronics, Samsung, LG Uplus, KT Corp | pCR | Yes |
Yes
| revised | No | S1‑192494 | ||||
| S1‑192494 | FS_MINT: Text proposal for Overview | LG Electronics, Samsung, LG Uplus, KT Corp | pCR | - | Yes |
Yes
| agreed | No | S1‑192026 | |||
| S1‑192027 | FS_MINT: Text proposal for Conclusion | LG Electronics, Samsung, KT Corp, LG Uplus | pCR | Yes |
Yes
| agreed | No | |||||
| S1‑192028 | FS_MINT: Consolidation of Potential Requirements for TR22.831 | LG Electronics, Samsung, LG Uplus, KT Corp | pCR | Yes |
Yes
| revised | No | S1‑192500 | ||||
| S1‑192500 | FS_MINT: Consolidation of Potential Requirements for TR22.831 | LG Electronics, Samsung, LG Uplus, KT Corp | pCR | - | Yes |
YesThe "Consolidated Potential Requirements" still needs to be written.
| revised | No | S1‑192772 | S1‑192028 | ||
| S1‑192772 | FS_MINT: Consolidation of Potential Requirements for TR22.831 | LG Electronics, Samsung, LG Uplus, KT Corp | pCR | - | Yes |
Yes
| revised | No | S1‑192821 | S1‑192500 | ||
| S1‑192821 | FS_MINT: Consolidation of Potential Requirements for TR22.831 | LG Electronics, Samsung, LG Uplus, KT Corp | pCR | - | Yes |
YesSeveral typos and minor corrections needed.
| revised | No | S1‑192844 | S1‑192772 | ||
| S1‑192844 | FS_MINT: Consolidation of Potential Requirements for TR22.831 | LG Electronics, Samsung, LG Uplus, KT Corp | pCR | - | Yes |
Yes
| agreed | No | S1‑192821 | |||
| S1‑192084 | update the potential requirement for section 5.3 | Huawei Tech.(UK) Co., Ltd | pCR | Yes |
Yes
| revised | No | S1‑192495 | ||||
| S1‑192495 | update the potential requirement for section 5.3 | Huawei Tech.(UK) Co., Ltd | pCR | - | Yes |
Yes
| 2014 | No | S1‑192767 | S1‑192084 | ||
| S1‑192767 | update the potential requirement for section 5.3 | Huawei Tech.(UK) Co., Ltd | pCR | - | Yes |
Yes
| agreed | No | S1‑192495 | |||
| S1‑192085 | update the potential requirement for section 5.10 | Huawei Tech.(UK) Co., Ltd | pCR | Yes |
Yes
| revised | No | S1‑192498 | ||||
| S1‑192498 | update the potential requirement for section 5.10 | Huawei Tech.(UK) Co., Ltd | pCR | - | Yes |
YesNote changed to post-condition.
| revised | No | S1‑192771 | S1‑192085 | ||
| S1‑192771 | update the potential requirement for section 5.10 | Huawei Tech.(UK) Co., Ltd | pCR | - | Yes |
Yes
| agreed | No | S1‑192498 | |||
| S1‑192361 | TR22.831v0.2.0 to include agreements at this meeting | Rapporteur (LG Electronics) | TR | discussion | No |
Yes
| agreed | No | ||||
| S1‑192362 | Cover page for presentation of TR22.831v0.2.0 | Rapporteur (LG Electronics) | TR | discussion | Yes |
Yes
| revised | No | S1‑192884 | |||
| S1‑192884 | Cover page for presentation of TR22.831v0.2.0 | Rapporteur (LG Electronics) | TR | discussion | No |
No
| reserved | No | S1‑192362 | |||
| S1‑192363 | NCIS+MINT drafting agenda | Session Chair | AGE | discussion | Yes |
Yes
| noted | No | ||||
| S1‑192364 | NCIS+MINT drafting report | Session Chair | REP | discussion | Yes |
Yes
| noted | No | ||||
| S1‑192847 | Way forward for NCIS | Rapporteur | REP | discussion | Yes |
YesThis was uploaded very late and Ericsson reminded that the minutes have to reflect what people said and not what a given contribution recommends to put.
Oppo presented questions in 2847.
| noted | No | ||||
| 7.8 | FS_MUSIM: Study on Support for Multi-USIM Devices [SP-190091] | S1‑192009 | Service Categorization in MUSIM | Samsung R&D Institute UK | discussion | Decision | Yes |
Yes
| noted | No | ||
| S1‑192010 | Improved Service Categories for MUSIM Paging | Samsung R&D Institute UK | CR | Agreement | Yes |
YesMerge into S1-192582
| merged | No | ||||
| S1‑192011 | ‘Separate Devices’ assumption in MUSIM | Samsung R&D Institute UK | discussion | Discussion | Yes |
Yes
| noted | No | ||||
| S1‑192012 | Clarifying the ‘Separate Devices’ requirement in MUSIM | Samsung R&D Institute UK | CR | Agreement | Yes |
Yes
| revised | No | S1‑192565 | |||
| S1‑192565 | Clarifying the ‘Separate Devices’ requirement in MUSIM | Samsung R&D Institute UK | CR | Agreement | Yes |
Yes
| revised | No | S1‑192803 | S1‑192012 | ||
| S1‑192803 | Clarifying the ‘Separate Devices’ requirement in MUSIM | Samsung R&D Institute UK | CR | Agreement | Yes |
Yes
| agreed | No | S1‑192565 | |||
| S1‑192018 | CR to 22.834 on MUSIM Emergency call | LG Electronics | CR | Yes |
YesMerge into S1-192584
| merged | No | |||||
| S1‑192019 | CR to 22.834 on MUSIM security | LG Electronics | CR | Yes |
YesMerge into S1-192582
| merged | No | |||||
| S1‑192020 | CR to 22.834 on MUSIM suspension | LG Electronics | CR | Yes |
YesMerge into S1-192583
| revised | No | S1‑192583 | ||||
| S1‑192583 | CR to 22.834 on MUSIM suspension | LG Electronics | CR | - | No |
Yes
| withdrawn | Yes | S1‑192020 | |||
| S1‑192080 | Network resources utilization requirement in MUSIM | China Telecom | CR | Agreement | Yes |
YesMerged with 2012 in 2565
| merged | No | ||||
| S1‑192090 | Clarification on the scope in TR 22.834 | Intel | CR | Approval | Yes |
Yes
| agreed | No | ||||
| S1‑192091 | Clarification on consolidate service requirements in clause 8.1 | Intel | CR | Approval | Yes |
Yes
| revised | No | S1‑192564 | |||
| S1‑192564 | Clarification on consolidate service requirements in clause 8.1 | Intel | CR | Approval | Yes |
Yes
| revised | No | S1‑192787 | S1‑192091 | ||
| S1‑192787 | Clarification on consolidate service requirements in clause 8.1 | Intel | CR | Approval | Yes |
YesThe deleted requirement should be marked as "void" rather than deleted, as to keep the numbering sequence.
Several companies also want to delete the 2nd one.
The "the secure support" on the 4th point has to be rephrased.
| revised | No | S1‑192805 | S1‑192564 | ||
| S1‑192805 | Clarification on consolidate service requirements in clause 8.1 | Intel | CR | Approval | Yes |
Yescolor and highlights are left.
There are concerns from Qualcomm on the 2nd requirement but they are not formally objecting to have it in the TR.
| revised | No | S1‑192862 | S1‑192787 | ||
| S1‑192862 | Clarification on consolidate service requirements in clause 8.1 | Intel | CR | Approval | No |
Yes
| agreed | No | S1‑192805 | |||
| S1‑192092 | Clarification on consolidate service requirements in clause 8.2 | Intel | CR | Approval | Yes |
Yes
| revised | No | S1‑192582 | |||
| S1‑192582 | Clarification on consolidate service requirements in clause 8.2 | Intel | CR | Approval | Yes |
YesThe changes on the 1st requirement can be covered by another CR if needed since this is more contrversial.
| revised | No | S1‑192807 | S1‑192092 | ||
| S1‑192807 | Clarification on consolidate service requirements in clause 8.2 | Intel, Huawei, Huawei Device, China Mobile, vivo mobile communications, Charter Communications Inc, LG Electronics | CR | Approval | Yes |
YesThe 7th requirement is to be removed, no consensus.
It was explained that the 1st requirement was extensively discussed in the drafting session, and in the end there is no change left on ths 1st requirement.
No consensus on the 2nd requirement.
The requirements to be copied to the TS are: (4: no), 5: yes, 6: no.
Changes to 2 and 3 should be ignored.
Huawei do not agree about deleting requirement [CPR.8.2-8], nor on the changes on [CPR.8.2-7] (deleting the Note is OK for Huawei).
Huawei prefers the requirement [CPR.8.2-4] to be formulated in a positive way.
| revised | No | S1‑192863 | S1‑192582 | ||
| S1‑192863 | Clarification on consolidate service requirements in clause 8.2 | Intel, Huawei, Huawei Device, China Mobile, vivo mobile communications, Charter Communications Inc, LG Electronics | CR | Approval | Yes |
Yes
| agreed | No | S1‑192807 | |||
| S1‑192093 | Clarification on emergency service requirements in section 8.3 | Intel | CR | Approval | Yes |
YesMerge into S1-192584
| revised | No | S1‑192584 | |||
| S1‑192584 | Clarification on emergency service requirements in section 8.3 | Intel, Qualcomm, Volkswagen AG, CMCC, Huawei, Huawei Device, LG | CR | Approval | Yes |
Yes2nd requirement to be deleted.
Wrong WI code.
| revised | No | S1‑192808 | S1‑192093 | ||
| S1‑192808 | Clarification on emergency service requirements in section 8.3 | Intel, Qualcomm, Volkswagen AG, CMCC, Huawei, Huawei Device, LG | CR | Approval | Yes |
YesRequirements 1, 2 and 3 will be brought to the TS.
| agreed | No | S1‑192584 | |||
| S1‑192094 | Clarification on security aspects | Intel | CR | Approval | Yes |
Yes
| revised | No | S1‑192559 | |||
| S1‑192559 | Clarification on security aspects | Intel | CR | Approval | Yes |
Yes
| agreed | No | S1‑192094 | |||
| S1‑192099 | Removing solution specific requirements | vivo Mobile Communication Co., Charter Communications Inc, LG Electronics | CR | Approval | Yes |
Yes
| revised | No | S1‑192251 | |||
| S1‑192100 | Editorial Clean up | vivo Mobile Communication Co.,Qualcomm Incorporated | CR | Approval | Yes |
Yes
| revised | No | S1‑192560 | |||
| S1‑192560 | Editorial Clean up | vivo Mobile Communication Co.,Qualcomm Incorporated | CR | Approval | No |
Yes
| withdrawn | Yes | S1‑192100 | |||
| S1‑192110 | Use case to ensure same service for MUSIM than in single SIM | Huawei, Huawei Device, | CR | Agreement | Yes |
Yes
| revised | No | S1‑192562 | |||
| S1‑192562 | Use case to ensure same service for MUSIM than in single SIM | Huawei, Huawei Device, | CR | Agreement | No |
Yes
| withdrawn | Yes | S1‑192110 | |||
| S1‑192111 | Corrections to support Mobile Terminated Services for MUSIM | Huawei, Huawei Device | CR | Agreement | Yes |
YesMerge into S1-192582
| merged | No | ||||
| S1‑192112 | Corrections to MUSIM: Handle MT services | Huawei, Huawei Device,CMCC | CR | Agreement | Yes |
YesMerge into S1-192582
| merged | No | ||||
| S1‑192113 | Corrections to MUSIM: Unnecessary suspension and resumption an active communication | Huawei, Huawei Device,CMCC | CR | Agreement | Yes |
YesMerge into S1-192583
| merged | No | ||||
| S1‑192114 | Corrections to MUSIM | Huawei, Huawei Device | CR | Agreement | Yes |
YesMerge into S1-192582
| merged | No | ||||
| S1‑192115 | Service category in MUSIM | Huawei, Huawei Device | discussion | Decision | Yes |
Yes
| noted | No | ||||
| S1‑192124 | 22834 CR - Service categories | China Mobile | CR | Yes |
YesMerge into S1-192582
| merged | No | |||||
| S1‑192125 | User preferences among MUSIMs | Beijing Xiaomi Mobile Software | CR | Agreement | Yes |
Yes
| revised | No | S1‑192566 | |||
| S1‑192566 | User preferences among MUSIMs | Beijing Xiaomi Mobile Software | CR | Agreement | No |
Yes
| withdrawn | Yes | S1‑192125 | |||
| S1‑192128 | Update existing use case to avoid interruption of emergency call | China Mobile Com. Corporation | CR | Agreement | Yes |
YesMerge into S1-192584
| merged | No | ||||
| S1‑192134 | Power optimization requirement in MUSIM | China Telecommunications | CR | Yes |
Yes
| revised | Yes | S1‑192567 | ||||
| S1‑192567 | Power optimization requirement in MUSIM | China Telecommunications | CR | - | Yes |
YesChanges over changes.
It could be merged into 2803.
Examples asked to be removed.
| revised | No | S1‑192806 | S1‑192134 | ||
| S1‑192806 | Power optimization requirement in MUSIM | China Telecommunications | CR | - | No |
Yes
| withdrawn | Yes | S1‑192567 | |||
| S1‑192144 | Power optimization requirement in MUSIM | China Telecommunications | CR | Agreement | Yes |
Yes
| noted | No | ||||
| S1‑192156 | CR to 22834 - Service categories | China Mobile | CR | Approval | Yes |
Yes
| noted | No | ||||
| S1‑192181 | Use case of data traffic convergence in MUSIM | China Telecom | CR | Agreement | Yes |
Yes
| revised | No | S1‑192563 | |||
| S1‑192563 | Use case of data traffic convergence in MUSIM | China Telecom | CR | Agreement | Yes |
YesThe definitions MUMS and MUMA, used in the CR, are not yet agreed at the time of presentation.
| noted | No | S1‑192181 | |||
| S1‑192229 | Various clarifications in MUSIM | Charter Communications, Inc, vivo Mobile Communications Co. Ltd | discussion | Agreement | Yes |
Yes
| noted | No | ||||
| S1‑192234 | Clarification on MUSIM UE handling requirements | Charter Communications, Inc, vivo Mobile Communications Co. Ltd | CR | Approval | Yes |
Yes
| revised | No | S1‑192581 | |||
| S1‑192581 | Clarification on MUSIM UE handling requirements | Charter Communications, Inc, vivo Mobile Communications Co. Ltd | CR | Approval | Yes |
YesThis seems to be covered by CR in 2787.
| noted | No | S1‑192234 | |||
| S1‑192251 | Removing solution specific requirements | vivo Mobile Communication Co., Charter Communications Inc, LG Electronics | CR | Approval | Yes |
YesMerge into S1-192582
| merged | No | S1‑192099 | |||
| S1‑192261 | Clarification on MUSIM service categories | Qualcomm communications-France | CR | Yes |
YesMerge into S1-192582
| merged | No | |||||
| S1‑192262 | Clarification on MUSIM paging collision | Qualcomm communications-France | CR | Yes |
Yes
| noted | No | |||||
| S1‑192263 | Way Forward Proposal for SA1 FS_MUSIM SI and MUSIM WI | Intel | discussion | Discussion | Yes |
Yes
| revised | No | S1‑192379 | |||
| S1‑192264 | Clarification on MUSIM terminology | Qualcomm communications-France | CR | Yes |
Yes
| revised | No | S1‑192561 | ||||
| S1‑192561 | Clarification on MUSIM terminology | Qualcomm communications-France | CR | - | Yes |
Yes
| revised | No | S1‑192801 | S1‑192264 | ||
| S1‑192801 | Clarification on MUSIM terminology | Qualcomm communications-France | CR | - | Yes |
YesThe note should be rewritten, in particular the "selected USIM" part: a USIM is not "used", it is just that the MS communicates with one or the other USIM at a given point.
| revised | No | S1‑192804 | S1‑192561 | ||
| S1‑192804 | Clarification on MUSIM terminology | Qualcomm communications-France | CR | - | Yes |
YesStill concerns to be solved next time before the next meeting.
| noted | No | S1‑192801 | |||
| S1‑192365 | MUSIM drafting agenda | Session Chair | AGE | discussion | Yes |
Yes
| noted | No | ||||
| S1‑192366 | MUSIM drafting report | Session Chair | REP | discussion | Yes |
Yes41 Documents treated
17 Revisions
3 Agreed
8 Noted
16 Carried over to Plenary
0 Withdrawn
0 Not treated
0 Late document
| noted | No | ||||
| S1‑192766 | Summary of MUSIM drafting session | Intel | report | discussion | Yes |
YesProper minutes of the MUSIM session in S1-192800.
It is not seen as a proper way forward to introduce editor's notes at this point in a stable TS.
| noted | No | ||||
| S1‑192800 | Minutes of the MUSIM drafting session | Samsung | report | discussion | Yes |
YesSummary in S1-192766
| revised | No | S1‑192837 | |||
| S1‑192837 | Minutes of the MUSIM drafting session | Samsung | report | discussion | Yes |
Yes
| noted | No | S1‑192800 | |||
| 7.9 | FS_eCAV: Study on enhancements for cyber-physical control applications in vertical domains [SP-190092] | S1‑192031 | FS_eCAV TSN Reliability enhancement | Nokia, Nokia Shanghai Bell | pCR | Yes |
Yes
| revised | No | S1‑192425 | ||
| S1‑192425 | FS_eCAV TSN Reliability enhancement | Nokia, Nokia Shanghai Bell | pCR | - | Yes |
Yes
| revised | No | S1‑192433 | S1‑192031 | ||
| S1‑192433 | FS_eCAV TSN Reliability enhancement | Nokia, Nokia Shanghai Bell | pCR | - | Yes |
Yes
| revised | No | S1‑192758 | S1‑192425 | ||
| S1‑192758 | FS_eCAV TSN Reliability enhancement | Nokia, Nokia Shanghai Bell | pCR | - | Yes |
Yes
| agreed | No | S1‑192433 | |||
| S1‑192032 | FS_eCAV multi-connectivity for robotic automation | Nokia, Nokia Shanghai Bell | pCR | Yes |
Yes
| revised | No | S1‑192426 | ||||
| S1‑192426 | FS_eCAV multi-connectivity for robotic automation | Nokia, Nokia Shanghai Bell | pCR | - | Yes |
Yes
| revised | No | S1‑192434 | S1‑192032 | ||
| S1‑192434 | FS_eCAV multi-connectivity for robotic automation | Nokia, Nokia Shanghai Bell | pCR | - | Yes |
Yes
| revised | No | S1‑192759 | S1‑192426 | ||
| S1‑192759 | FS_eCAV multi-connectivity for robotic automation | Nokia, Nokia Shanghai Bell | pCR | - | Yes |
YesThe use case is introduced without the requirement, to be introduced at a later meeting.
| revised | No | S1‑192848 | S1‑192434 | ||
| S1‑192848 | FS_eCAV multi-connectivity for robotic automation | Nokia, Nokia Shanghai Bell | pCR | - | Yes |
Yes
| agreed | No | S1‑192759 | |||
| S1‑192047 | FS_eCAV: Industrial communication network architecture | VODAFONE Group Plc, Ericsson | pCR | Approval | Yes |
Yes
| revised | No | S1‑192449 | |||
| S1‑192449 | FS_eCAV: Industrial communication network architecture | VODAFONE Group Plc, Ericsson | pCR | Approval | Yes |
Yes
| agreed | No | S1‑192047 | |||
| S1‑192049 | FS_eCAV: survival time vs. consecutive message loss | VODAFONE Group Plc | pCR | Approval | Yes |
Yes
| revised | No | S1‑192417 | |||
| S1‑192417 | FS_eCAV: survival time vs. consecutive message loss | VODAFONE Group Plc | pCR | Approval | Yes |
Yes
| agreed | No | S1‑192049 | |||
| S1‑192050 | FS_eCAV: communication service availability vs. failure | VODAFONE Group Plc | pCR | Yes |
Yes
| revised | No | S1‑192450 | ||||
| S1‑192450 | FS_eCAV: communication service availability vs. failure | VODAFONE Group Plc | pCR | - | Yes |
Yes
| agreed | No | S1‑192050 | |||
| S1‑192105 | FS_eCAV - Support to application layer for Cooperative carrying of work pieces | ZTE | pCR | Approval | Yes |
Yes
| revised | No | S1‑192419 | |||
| S1‑192419 | FS_eCAV - Support to application layer for Cooperative carrying of work pieces | ZTE | pCR | Approval | Yes |
Yes
| revised | No | S1‑192742 | S1‑192105 | ||
| S1‑192742 | FS_eCAV - Support to application layer for Cooperative carrying of work pieces | ZTE | pCR | Approval | Yes |
Yes
| revised | No | S1‑192753 | S1‑192419 | ||
| S1‑192753 | FS_eCAV - Support to application layer for Cooperative carrying of work pieces | ZTE | pCR | Approval | No |
Yes
| withdrawn | Yes | S1‑192742 | |||
| S1‑192106 | FS_eCAV - Support to application layer for Energy efficiency | ZTE | pCR | Approval | Yes |
Yes
| revised | No | S1‑192420 | |||
| S1‑192420 | FS_eCAV - Support to application layer for Energy efficiency | ZTE | pCR | Approval | Yes |
Yes
| revised | No | S1‑192743 | S1‑192106 | ||
| S1‑192743 | FS_eCAV - Support to application layer for Energy efficiency | ZTE | pCR | Approval | Yes |
Yes
| revised | No | S1‑192754 | S1‑192420 | ||
| S1‑192754 | FS_eCAV - Support to application layer for Energy efficiency | ZTE | pCR | Approval | No |
Yes
| withdrawn | Yes | S1‑192743 | |||
| S1‑192107 | FS_eCAV - Support to application layer for Integration with TSN networks | ZTE | pCR | Approval | Yes |
Yes
| revised | No | S1‑192421 | |||
| S1‑192421 | FS_eCAV - Support to application layer for Integration with TSN networks | ZTE | pCR | Approval | Yes |
Yes
| revised | No | S1‑192744 | S1‑192107 | ||
| S1‑192744 | FS_eCAV - Support to application layer for Integration with TSN networks | ZTE | pCR | Approval | Yes |
Yes
| revised | No | S1‑192755 | S1‑192421 | ||
| S1‑192755 | FS_eCAV - Support to application layer for Integration with TSN networks | ZTE | pCR | Approval | No |
Yes
| withdrawn | Yes | S1‑192744 | |||
| S1‑192108 | FS_eCAV - Support to application layer for Merging of working clock domains | ZTE | pCR | Approval | Yes |
Yes
| revised | No | S1‑192422 | |||
| S1‑192422 | FS_eCAV - Support to application layer for Merging of working clock domains | ZTE | pCR | Approval | Yes |
Yes
| revised | No | S1‑192745 | S1‑192108 | ||
| S1‑192745 | FS_eCAV - Support to application layer for Merging of working clock domains | ZTE | pCR | Approval | Yes |
Yes
| revised | No | S1‑192756 | S1‑192422 | ||
| S1‑192756 | FS_eCAV - Support to application layer for Merging of working clock domains | ZTE | pCR | Approval | No |
Yes
| withdrawn | Yes | S1‑192745 | |||
| S1‑192116 | FS_eCAV - Support to application layer for Mobile Operation Panel | ZTE | pCR | Approval | Yes |
Yes
| revised | No | S1‑192423 | |||
| S1‑192423 | FS_eCAV - Support to application layer for Mobile Operation Panel | ZTE | pCR | Approval | No |
Yes
| withdrawn | Yes | S1‑192116 | |||
| S1‑192117 | FS_eCAV - Support to application layer for Providing vertical positioning | ZTE | pCR | Approval | Yes |
Yes
| revised | No | S1‑192424 | |||
| S1‑192424 | FS_eCAV - Support to application layer for Providing vertical positioning | ZTE | pCR | Approval | No |
Yes
| withdrawn | Yes | S1‑192117 | |||
| S1‑192119 | FS_eCAV - use_case_Industrial application analytics | ZTE | pCR | Approval | Yes |
Yes
| noted | No | ||||
| S1‑192136 | FS_eCAV – Consolidate service requirements on Positioning | Huawei Technologies Co. Ltd. | pCR | Yes |
Yes
| revised | No | S1‑192410 | ||||
| S1‑192410 | FS_eCAV – Consolidate service requirements on Positioning | Huawei Technologies Co. Ltd. | pCR | - | Yes |
Yes
| revised | No | S1‑192444 | S1‑192136 | ||
| S1‑192444 | FS_eCAV – Consolidate service requirements on Positioning | Huawei Technologies Co. Ltd. | pCR | - | Yes |
Yes
| revised | No | S1‑192453 | S1‑192410 | ||
| S1‑192453 | FS_eCAV – Consolidate service requirements on Positioning | Huawei Technologies Co. Ltd. | pCR | - | Yes |
Yes
| revised | No | S1‑192464 | S1‑192444 | ||
| S1‑192464 | FS_eCAV – Consolidate service requirements on Positioning | Huawei Technologies Co. Ltd. | pCR | - | Yes |
Yes
| agreed | No | S1‑192453 | |||
| S1‑192153 | Clarification and pCR for Communication monitoring for CAV applications | Tencent | pCR | Approval | Yes |
Yes
| revised | No | S1‑192431 | |||
| S1‑192431 | Clarification and pCR for Communication monitoring for CAV applications | Tencent | pCR | Approval | Yes |
Yes
| revised | No | S1‑192459 | S1‑192153 | ||
| S1‑192459 | Clarification and pCR for Communication monitoring for CAV applications | Tencent | pCR | Approval | Yes |
Yes
| agreed | No | S1‑192431 | |||
| S1‑192154 | Clarification Multiple Working Clock Domains in gNB and pCR to TR 22.832 | Tencent | pCR | Approval | Yes |
Yes
| noted | No | ||||
| S1‑192155 | Clarification and pCR for Cooperative carrying of work pieces | Tencent | pCR | Approval | Yes |
Yes
| revised | No | S1‑192432 | |||
| S1‑192432 | Clarification and pCR for Cooperative carrying of work pieces | Tencent | pCR | Approval | Yes |
YesMerge into S1-192429
| merged | No | S1‑192155 | |||
| S1‑192157 | Non-public networks as private slices | CATT | pCR | Yes |
Yes
| revised | No | S1‑192435 | ||||
| S1‑192435 | Non-public networks as private slices | CATT | pCR | - | Yes |
Yes
| revised | No | S1‑192760 | S1‑192157 | ||
| S1‑192760 | Non-public networks as private slices | CATT | pCR | - | Yes |
Yes
| revised | No | S1‑192849 | S1‑192435 | ||
| S1‑192849 | Non-public networks as private slices | CATT | pCR | - | Yes |
Yes
| agreed | No | S1‑192760 | |||
| S1‑192161 | Merged potential service requirements: Non-public networks as private slices | CATT | pCR | Yes |
Yes
| revised | No | S1‑192441 | ||||
| S1‑192441 | Merged potential service requirements: Non-public networks as private slices | CATT | pCR | - | Yes |
Yes
| revised | No | S1‑192802 | S1‑192161 | ||
| S1‑192802 | Merged potential service requirements: Non-public networks as private slices | CATT | pCR | - | No |
Yes
| withdrawn | Yes | S1‑192441 | |||
| S1‑192188 | FS_eCAV - Wired to wireless link replacement for Industry 4.0 | Siemens AG | pCR | Agreement | Yes |
Yes
| revised | No | S1‑192436 | |||
| S1‑192436 | FS_eCAV - Wired to wireless link replacement for Industry 4.0 | Siemens AG | pCR | Agreement | Yes |
Yes
| revised | No | S1‑192462 | S1‑192188 | ||
| S1‑192462 | FS_eCAV - Wired to wireless link replacement for Industry 4.0 | Siemens AG | pCR | Agreement | Yes |
Yes
| agreed | No | S1‑192436 | |||
| S1‑192193 | FS_eCAV – Update use case “Integration of 5G networks with TSN networks (time synchronization)” | Siemens AG | pCR | Agreement | Yes |
Yes
| revised | No | S1‑192428 | |||
| S1‑192428 | FS_eCAV – Update use case “Integration of 5G networks with TSN networks (time synchronization)” | Siemens AG | pCR | Agreement | Yes |
Yes
| agreed | No | S1‑192193 | |||
| S1‑192199 | FS_eCAV – Use Case Flexible Manufacturing | Siemens AG | pCR | Agreement | Yes |
Yes
| revised | No | S1‑192437 | |||
| S1‑192437 | FS_eCAV – Use Case Flexible Manufacturing | Siemens AG | pCR | Agreement | Yes |
Yes
| agreed | No | S1‑192199 | |||
| S1‑192214 | FS_eCAV Industrial Wireless Sensors for process and asset monitoring | Ericsson | pCR | Agreement | Yes |
Yes
| revised | No | S1‑192438 | |||
| S1‑192438 | FS_eCAV Industrial Wireless Sensors for process and asset monitoring | Ericsson | pCR | Agreement | Yes |
Yes
| agreed | No | S1‑192214 | |||
| S1‑192224 | Use of sidelink for process monitoring and plant asset management | Qualcomm communications-France | discussion | Yes |
Yes
| revised | No | S1‑192414 | ||||
| S1‑192414 | Use of sidelink for process monitoring and plant asset management | Qualcomm communications-France | discussion | - | Yes |
Yes
| revised | No | S1‑192463 | S1‑192224 | ||
| S1‑192463 | Use of sidelink for process monitoring and plant asset management | Qualcomm communications-France | discussion | - | Yes |
Yes
| agreed | No | S1‑192414 | |||
| S1‑192226 | Consolidation of sidelink requirements for TR 22.832 | Qualcomm communications-France | pCR | Yes |
Yes
| revised | No | S1‑192447 | ||||
| S1‑192447 | Consolidation of sidelink requirements for TR 22.832 | Qualcomm communications-France | pCR | - | Yes |
Yes
| agreed | No | S1‑192226 | |||
| S1‑192235 | FS_eCAV resolution of questions in clause 4.1 | Nokia, Nokia Shanghai Bell | pCR | Yes |
Yes
| revised | No | S1‑192416 | ||||
| S1‑192416 | FS_eCAV resolution of questions in clause 4.1 | Nokia, Nokia Shanghai Bell | pCR | - | Yes |
Yes
| revised | No | S1‑192752 | S1‑192235 | ||
| S1‑192752 | FS_eCAV resolution of questions in clause 4.1 | Nokia, Nokia Shanghai Bell | pCR | - | Yes |
Yes
| agreed | No | S1‑192416 | |||
| S1‑192238 | Definition of absolute and relative positioning | Fraunhofer IIS | discussion | Yes |
Yes
| revised | No | S1‑192412 | ||||
| S1‑192412 | Definition of absolute and relative positioning | Fraunhofer IIS | discussion | - | Yes |
Yes
| noted | No | S1‑192238 | |||
| S1‑192242 | FS_eCAV – merged potential service requirements – Positioning | Fraunhofer IIS | pCR | Approval | Yes |
Yes
| revised | No | S1‑192411 | |||
| S1‑192411 | FS_eCAV – merged potential service requirements – Positioning | Fraunhofer IIS | pCR | Approval | Yes |
Yes
| revised | No | S1‑192445 | S1‑192242 | ||
| S1‑192445 | FS_eCAV – merged potential service requirements – Positioning | Fraunhofer IIS | pCR | Approval | Yes |
Yes
| agreed | No | S1‑192411 | |||
| S1‑192243 | FS_eCAV – merged potential service requirements – Industrial Ethernet integration | Siemens | pCR | Agreement | Yes |
Yes
| revised | No | S1‑192439 | |||
| S1‑192439 | FS_eCAV – merged potential service requirements – Industrial Ethernet integration | Siemens | pCR | Agreement | Yes |
Yes
| revised | No | S1‑192852 | S1‑192243 | ||
| S1‑192852 | FS_eCAV – merged potential service requirements – Industrial Ethernet integration | Siemens | pCR | Agreement | Yes |
Yes
| agreed | No | S1‑192439 | |||
| S1‑192246 | FS_eCAV – merged potential service requirements – Non-public Networks | Siemens | pCR | Agreement | Yes |
Yes
| revised | No | S1‑192440 | |||
| S1‑192440 | FS_eCAV – merged potential service requirements – Non-public Networks | Siemens | pCR | Agreement | No |
Yes
| withdrawn | Yes | S1‑192246 | |||
| S1‑192255 | FS_eCAV – merged potential service requirements –Network operation and maintenance | Siemens, Huawei Technologies | pCR | Agreement | Yes |
Yes
| revised | No | S1‑192442 | |||
| S1‑192442 | FS_eCAV – merged potential service requirements –Network operation and maintenance | Siemens, Huawei Technologies | pCR | Agreement | Yes |
Yes
| agreed | No | S1‑192255 | |||
| S1‑192265 | FS_eCAV – merged potential service requirements – Network performance | Siemens | pCR | Agreement | Yes |
Yes
| revised | No | S1‑192392 | |||
| S1‑192392 | FS_eCAV – merged potential service requirements – Network performance | Siemens | pCR | Agreement | Yes |
Yes
| revised | No | S1‑192443 | S1‑192265 | ||
| S1‑192443 | FS_eCAV – merged potential service requirements – Network performance | Siemens | pCR | Agreement | Yes |
Yes
| revised | No | S1‑192853 | S1‑192392 | ||
| S1‑192853 | FS_eCAV – merged potential service requirements – Network performance | Siemens | pCR | Agreement | No |
Yes
| agreed | No | S1‑192443 | |||
| S1‑192271 | FS_eCAV – merged potential service requirements – ProSe Communication for CAV | Siemens | pCR | Agreement | Yes |
Yes
| revised | No | S1‑192446 | |||
| S1‑192446 | FS_eCAV – merged potential service requirements – ProSe Communication for CAV | Siemens | pCR | Agreement | Yes |
Yes
| revised | No | S1‑192854 | S1‑192271 | ||
| S1‑192854 | FS_eCAV – merged potential service requirements – ProSe Communication for CAV | Siemens | pCR | Agreement | Yes |
Yes
| agreed | No | S1‑192446 | |||
| S1‑192272 | Consolidated potential service requirements on positioning | ETRI | pCR | Yes |
Yes
| noted | No | |||||
| S1‑192276 | FS_eCAV – Update use case “Cooperative carrying of work pieces” | Siemens | pCR | Agreement | Yes |
Yes
| revised | No | S1‑192394 | |||
| S1‑192394 | FS_eCAV – Update use case “Cooperative carrying of work pieces” | Siemens | pCR | Agreement | Yes |
Yes
| revised | No | S1‑192429 | S1‑192276 | ||
| S1‑192429 | FS_eCAV – Update use case “Cooperative carrying of work pieces” | Siemens | pCR | Agreement | Yes |
Yes
| revised | No | S1‑192757 | S1‑192394 | ||
| S1‑192757 | FS_eCAV – Update use case “Cooperative carrying of work pieces” | Siemens | pCR | Agreement | No |
Yes
| agreed | No | S1‑192429 | |||
| S1‑192289 | FS_eCAV – TR 22.832 – Update Use Case Mobile Operation Panel | Siemens | pCR | Agreement | Yes |
Yes
| revised | No | S1‑192395 | |||
| S1‑192395 | FS_eCAV – TR 22.832 – Update Use Case Mobile Operation Panel | Siemens | pCR | Agreement | Yes |
Yes
| revised | No | S1‑192430 | S1‑192289 | ||
| S1‑192430 | FS_eCAV – TR 22.832 – Update Use Case Mobile Operation Panel | Siemens | pCR | Agreement | Yes |
Yes
| revised | No | S1‑192846 | S1‑192395 | ||
| S1‑192846 | FS_eCAV – TR 22.832 – Update Use Case Mobile Operation Panel | Siemens | pCR | Agreement | Yes |
Yes
| agreed | No | S1‑192430 | |||
| S1‑192290 | FS_eCAV – Clustering of potential 5G service requirements | Siemens | discussion | Information | No |
Yes
| withdrawn | Yes | ||||
| S1‑192291 | FS_eCAV – Clustering of potential 5G service requirements | Siemens | discussion | Information | Yes |
Yes
| noted | No | ||||
| S1‑192292 | TR 22.832 – Overview section | Siemens | pCR | Agreement | Yes |
Yes
| revised | No | S1‑192415 | |||
| S1‑192415 | TR 22.832 – Overview section | Siemens | pCR | Agreement | Yes |
Yes
| agreed | No | S1‑192292 | |||
| S1‑192293 | TR 22.832 – Introduction subclause for use case chapter | Siemens | pCR | Agreement | Yes |
Yes
| revised | No | S1‑192418 | |||
| S1‑192418 | TR 22.832 – Introduction subclause for use case chapter | Siemens | pCR | Agreement | Yes |
Yes
| agreed | No | S1‑192293 | |||
| S1‑192294 | TR 22.832 – Conclusion section | Siemens | pCR | Agreement | Yes |
Yes
| revised | No | S1‑192448 | |||
| S1‑192448 | TR 22.832 – Conclusion section | Siemens | pCR | Agreement | Yes |
Yes
| agreed | No | S1‑192294 | |||
| S1‑192367 | TR22.832v1.1.0 to include agreements at this meeting | Rapporteur (Siemens) | TR | discussion | No |
No
| reserved | No | ||||
| S1‑192368 | Cover page for presentation of TR22.832v1.1.0 | Rapporteur (Siemens) | TR | discussion | Yes |
No
| available | No | ||||
| S1‑192369 | eCAV drafting agenda | Session Chair | AGE | discussion | Yes |
Yes
| noted | No | ||||
| S1‑192370 | eCAV drafting report | Session Chair | REP | discussion | Yes |
Yes
| noted | No | ||||
| S1‑192466 | Not used | Reserved Toon (eCAV) | other | discussion | No |
Yes
| withdrawn | Yes | ||||
| S1‑192467 | Not used | Reserved Toon (eCAV) | other | discussion | No |
Yes
| withdrawn | Yes | ||||
| S1‑192468 | Not used | Reserved Toon (eCAV) | other | discussion | No |
Yes
| withdrawn | Yes | ||||
| S1‑192469 | Not used | Reserved Toon (eCAV) | other | discussion | No |
Yes
| withdrawn | Yes | ||||
| S1‑192472 | Clarification and pCR to TR 22.827 on AVProd | Tencent | other | discussion | Yes |
Yes
| withdrawn | Yes | ||||
| S1‑192532 | Not used | Reserved Ki-Dong | other | discussion | No |
Yes
| withdrawn | Yes | ||||
| S1‑192533 | Not used | Reserved Ki-Dong | other | discussion | No |
Yes
| withdrawn | Yes | ||||
| S1‑192534 | Not used | Reserved Ki-Dong | other | discussion | No |
Yes
| withdrawn | Yes | ||||
| S1‑192535 | Not used | Reserved Ki-Dong | other | discussion | No |
Yes
| withdrawn | Yes | ||||
| S1‑192536 | Not used | Reserved Ki-Dong | other | discussion | No |
Yes
| withdrawn | Yes | ||||
| S1‑192537 | Not used | Reserved Ki-Dong | other | discussion | No |
Yes
| withdrawn | Yes | ||||
| S1‑192538 | Not used | Reserved Ki-Dong | other | discussion | No |
Yes
| withdrawn | Yes | ||||
| S1‑192539 | Not used | Reserved Ki-Dong | other | discussion | No |
Yes
| withdrawn | Yes | ||||
| S1‑192540 | Not used | Reserved Ki-Dong | other | discussion | No |
Yes
| withdrawn | Yes | ||||
| S1‑192541 | Not used | Reserved Ki-Dong | other | discussion | No |
Yes
| withdrawn | Yes | ||||
| S1‑192542 | Not used | Reserved Ki-Dong | other | discussion | No |
Yes
| withdrawn | Yes | ||||
| S1‑192543 | Not used | Reserved Ki-Dong | other | discussion | No |
Yes
| withdrawn | Yes | ||||
| S1‑192544 | Not used | Reserved Ki-Dong | other | discussion | No |
Yes
| withdrawn | Yes | ||||
| S1‑192545 | Not used | Reserved Ki-Dong | other | discussion | No |
Yes
| withdrawn | Yes | ||||
| S1‑192546 | Not used | Reserved Ki-Dong | other | discussion | No |
Yes
| withdrawn | Yes | ||||
| S1‑192547 | Not used | Reserved Ki-Dong | other | discussion | No |
Yes
| withdrawn | Yes | ||||
| S1‑192548 | Not used | Reserved Ki-Dong | other | discussion | No |
Yes
| withdrawn | Yes | ||||
| S1‑192549 | Not used | Reserved Ki-Dong | other | discussion | No |
Yes
| withdrawn | Yes | ||||
| 7.10 | FS_FRMCS3 | S1‑192192 | Update gap analysis for requirements in subclause 6 Critical communication applications related use cases | Union Inter. Chemins de Fer | CR | Approval | Yes |
Yes
| revised | No | S1‑192620 | |
| S1‑192620 | Update gap analysis for requirements in subclause 6 Critical communication applications related use cases | Union Inter. Chemins de Fer | CR | Approval | Yes |
Yes
| agreed | No | S1‑192192 | |||
| S1‑192194 | Update gap analysis for requirements in subclause 7 Performance communication applications related use cases | Union Inter. Chemins de Fer | CR | Approval | Yes |
Yes
| revised | No | S1‑192621 | |||
| S1‑192621 | Update gap analysis for requirements in subclause 7 Performance communication applications related use cases | Union Inter. Chemins de Fer | CR | Approval | Yes |
Yes
| agreed | No | S1‑192194 | |||
| S1‑192195 | Update gap analysis for requirements in subclause 9 Critical support applications related use cases | Union Inter. Chemins de Fer | CR | Approval | Yes |
Yes
| revised | No | S1‑192622 | |||
| S1‑192622 | Update gap analysis for requirements in subclause 9 Critical support applications related use cases | Union Inter. Chemins de Fer | CR | Approval | Yes |
Yes
| agreed | No | S1‑192195 | |||
| S1‑192196 | Update gap analysis for requirements in subclause 12 FRMCS System principles related use cases | Union Inter. Chemins de Fer | CR | Approval | Yes |
Yes
| revised | No | S1‑192375 | |||
| S1‑192375 | Update gap analysis for requirements in subclause 12 FRMCS System principles related use cases | Union Inter. Chemins de Fer | CR | Approval | Yes |
Yes
| revised | No | S1‑192623 | S1‑192196 | ||
| S1‑192623 | Update gap analysis for requirements in subclause 12 FRMCS System principles related use cases | Union Inter. Chemins de Fer | CR | Approval | Yes |
Yes
| agreed | No | S1‑192375 | |||
| S1‑192197 | Clarify CS/PS interworking versus interconnection between GSM-R and FRMCS users | Union Inter. Chemins de Fer | CR | Approval | Yes |
Yes
| revised | No | S1‑192624 | |||
| S1‑192624 | Clarify CS/PS interworking versus interconnection between GSM-R and FRMCS users | Union Inter. Chemins de Fer | CR | Approval | Yes |
Yes
| revised | No | S1‑192732 | S1‑192197 | ||
| S1‑192732 | Clarify CS/PS interworking versus interconnection between GSM-R and FRMCS users | Union Inter. Chemins de Fer | CR | Approval | Yes |
Yes
| agreed | No | S1‑192624 | |||
| S1‑192198 | Location information of an FRMCS Equipment | Union Inter. Chemins de Fer | CR | Approval | Yes |
Yes
| agreed | No | ||||
| S1‑192200 | 3GPP building blocks to support Real-time video communication (video conferencing) related use cases | Union Inter. Chemins de Fer | CR | Approval | Yes |
Yes
| revised | No | S1‑192625 | |||
| S1‑192625 | 3GPP building blocks to support Real-time video communication (video conferencing) related use cases | Union Inter. Chemins de Fer | CR | Approval | Yes |
Yes
| revised | No | S1‑192733 | S1‑192200 | ||
| S1‑192733 | 3GPP building blocks to support Real-time video communication (video conferencing) related use cases | Union Inter. Chemins de Fer | CR | Approval | Yes |
Yes
| agreed | No | S1‑192625 | |||
| S1‑192201 | Degradation of a communication link for AVC | Union Inter. Chemins de Fer | CR | Approval | Yes |
Yes
| revised | No | S1‑192632 | |||
| S1‑192632 | Degradation of a communication link for AVC | Union Inter. Chemins de Fer | CR | Approval | Yes |
Yes
| agreed | No | S1‑192201 | |||
| S1‑192247 | Update gap analysis for requirements in subclause 6.18 Train Integrity monitoring data communication related use cases while operating in off-network mode | Union Inter. Chemins de Fer | CR | Approval | Yes |
Yes
| revised | No | S1‑192633 | |||
| S1‑192633 | Update gap analysis for requirements in subclause 6.18 Train Integrity monitoring data communication related use cases while operating in off-network mode | Union Inter. Chemins de Fer | CR | Approval | Yes |
Yes
| agreed | No | S1‑192247 | |||
| S1‑192297 | Gap analysis for 9.13 Autonomous Train Control and Operation | Hansung University | CR | Agreement | Yes |
Yes
| agreed | No | ||||
| S1‑192298 | Gap analysis for 9.14 Vertual Coupling | Hansung University | CR | Agreement | Yes |
Yes
| revised | No | S1‑192634 | |||
| S1‑192634 | Gap analysis for 9.14 Vertual Coupling | Hansung University | CR | Agreement | Yes |
Yes"Consequences if not approved" has to be rewritten
| revised | No | S1‑192734 | S1‑192298 | ||
| S1‑192734 | Gap analysis for 9.14 Vertual Coupling | Hansung University | CR | Agreement | Yes |
Yes
| revised | No | S1‑192775 | S1‑192634 | ||
| S1‑192775 | Gap analysis for 9.14 Vertual Coupling | Hansung University | CR | Agreement | Yes |
Yes2851 used instead
| revised | No | S1‑192851 | S1‑192734 | ||
| S1‑192851 | Gap analysis for 9.14 Vertual Coupling | Hansung University | CR | Agreement | Yes |
Yes
| agreed | No | S1‑192775 | |||
| S1‑192299 | Gap analysis for 9.15 Composite-based train operation | Hansung University | CR | Agreement | Yes |
Yes
| revised | No | S1‑192635 | |||
| S1‑192635 | Gap analysis for 9.15 Composite-based train operation | Hansung University | CR | Agreement | Yes |
Yes"Consequences if not approved" has to be rewritten
| revised | No | S1‑192735 | S1‑192299 | ||
| S1‑192735 | Gap analysis for 9.15 Composite-based train operation | Hansung University | CR | Agreement | Yes |
YesThe author asked offline for a revised number (S1-192776 given) but 2735 was already agreed.
| agreed | No | S1‑192635 | |||
| S1‑192776 | Gap analysis for 9.15 Composite-based train operation | Hansung University | CR | Agreement | Yes |
YesSupposed to be used for a revision S1-192735 but previous version agreed.
| withdrawn | Yes | ||||
| S1‑192300 | Gap analysis for Private call priority during internetworking with LMR | Hansung University | CR | Agreement | Yes |
Yes
| revised | No | S1‑192636 | |||
| S1‑192636 | Gap analysis for Private call priority during internetworking with LMR | Hansung University | CR | Agreement | Yes |
Yes
| revised | No | S1‑192850 | S1‑192300 | ||
| S1‑192850 | Gap analysis for Private call priority during internetworking with LMR | Hansung University | CR | Agreement | Yes |
Yes
| agreed | No | S1‑192636 | |||
| S1‑192371 | Railway drafting agenda | Session Chair | AGE | discussion | Yes |
Yes
| noted | No | ||||
| S1‑192372 | Railway drafting report | Session Chair | REP | discussion | Yes |
Yes
| noted | No | ||||
| S1‑192639 | Drafting Group Agenda for MPS [FS_MPS2 + MPS2] | Session Chair | other | discussion | Yes |
Yes
| noted | No | ||||
| S1‑192640 | MPS drafting report [FS_MPS2 + MPS2] | Session Chair | other | discussion | Yes |
Yes
| noted | No | ||||
| S1‑192641 | Not used | Reserved Jose | other | discussion | No |
Yes
| withdrawn | Yes | ||||
| S1‑192642 | Not used | Reserved Jose | other | discussion | No |
Yes
| withdrawn | Yes | ||||
| S1‑192643 | Not used | Reserved Jose | other | discussion | No |
Yes
| withdrawn | Yes | ||||
| S1‑192644 | Not used | Reserved Jose | other | discussion | No |
Yes
| withdrawn | Yes | ||||
| S1‑192645 | Not used | Reserved Jose | other | discussion | No |
Yes
| withdrawn | Yes | ||||
| S1‑192646 | Not used | Reserved Jose | other | discussion | No |
Yes
| withdrawn | Yes | ||||
| S1‑192647 | Not used | Reserved Jose | other | discussion | No |
Yes
| withdrawn | Yes | ||||
| S1‑192648 | Not used | Reserved Jose | other | discussion | No |
Yes
| withdrawn | Yes | ||||
| S1‑192649 | Not used | Reserved Jose | other | discussion | No |
Yes
| withdrawn | Yes | ||||
| S1‑192650 | Not used | Reserved Jose | other | discussion | No |
Yes
| withdrawn | Yes | ||||
| S1‑192651 | Not used | Reserved Jose | other | discussion | No |
Yes
| withdrawn | Yes | ||||
| S1‑192652 | Not used | Reserved Jose | other | discussion | No |
Yes
| withdrawn | Yes | ||||
| S1‑192653 | Not used | Reserved Jose | other | discussion | No |
Yes
| withdrawn | Yes | ||||
| S1‑192654 | Not used | Reserved Jose | other | discussion | No |
Yes
| withdrawn | Yes | ||||
| S1‑192655 | Not used | Reserved Jose | other | discussion | No |
Yes
| withdrawn | Yes | ||||
| S1‑192656 | Not used | Reserved Jose | other | discussion | No |
Yes
| withdrawn | Yes | ||||
| S1‑192657 | Not used | Reserved Jose | other | discussion | No |
Yes
| withdrawn | Yes | ||||
| S1‑192658 | Not used | Reserved Jose | other | discussion | No |
Yes
| withdrawn | Yes | ||||
| S1‑192659 | Not used | Reserved Jose | other | discussion | No |
Yes
| withdrawn | Yes | ||||
| S1‑192660 | Not used | Reserved Jose | other | discussion | No |
Yes
| withdrawn | Yes | ||||
| S1‑192661 | Not used | Reserved Jose | other | discussion | No |
Yes
| withdrawn | Yes | ||||
| S1‑192662 | Not used | Reserved Jose | other | discussion | No |
Yes
| withdrawn | Yes | ||||
| S1‑192663 | Not used | Reserved Jose | other | discussion | No |
Yes
| withdrawn | Yes | ||||
| S1‑192664 | Not used | Reserved Jose | other | discussion | No |
Yes
| withdrawn | Yes | ||||
| S1‑192665 | Not used | Reserved Jose | other | discussion | No |
Yes
| withdrawn | Yes | ||||
| S1‑192666 | Not used | Reserved Jose | other | discussion | No |
Yes
| withdrawn | Yes | ||||
| S1‑192667 | Not used | Reserved Jose | other | discussion | No |
Yes
| withdrawn | Yes | ||||
| S1‑192668 | Not used | Reserved Jose | other | discussion | No |
Yes
| withdrawn | Yes | ||||
| S1‑192669 | Not used | Reserved Jose | other | discussion | No |
Yes
| withdrawn | Yes | ||||
| 8 | Rel-17 Work Item contributions | |||||||||||
| 8.1 | NCIS: Network Controlled Interactive Service Requirements [SP-190303] | S1‑192076 | General descriptions of network controlled interactive service | China Telecom, OPPO, Samsung, Tencent | CR | Agreement | Yes |
Yes
| revised | No | S1‑192486 | |
| S1‑192486 | General descriptions of network controlled interactive service | China Telecom, OPPO, Samsung, Tencent | CR | Agreement | Yes |
YesMerged into S1-192520
| merged | No | S1‑192076 | |||
| S1‑192077 | Performance requirements of interactive service | OPPO, Tencent | CR | Agreement | Yes |
Yes
| revised | No | S1‑192487 | |||
| S1‑192487 | Performance requirements of interactive service | OPPO, Tencent | CR | Agreement | Yes |
Yes
| revised | No | S1‑192519 | S1‑192077 | ||
| S1‑192519 | Performance requirements of interactive service | OPPO, Tencent | CR | Agreement | Yes |
YesProblem with revision marks.
| revised | No | S1‑192763 | S1‑192487 | ||
| S1‑192763 | Performance requirements of interactive service | OPPO, Tencent | CR | Agreement | Yes |
Yes
| agreed | No | S1‑192519 | |||
| S1‑192078 | Group operation related requirements of interactive service | OPPO, Tencent | CR | Agreement | Yes |
Yes
| revised | No | S1‑192520 | |||
| S1‑192520 | Group operation related requirements of interactive service | OPPO, Tencent | CR | Agreement | Yes |
YesEricsson has several concerns with all of the definitions proposed here.
Also changes to these sections at this time might be quite late in the process, giving the impacts e.g. on SA6.
| revised | No | S1‑192764 | S1‑192078 | ||
| S1‑192764 | Group operation related requirements of interactive service | OPPO, Tencent | CR | Agreement | Yes |
YesSeveral requirements already exist.
References to 22.468 can be added.
To be postponed to next meeting.
| noted | No | S1‑192520 | |||
| S1‑192079 | Service hosting environment aspects of interactive service | OPPO, Samsung, Tencent | CR | Agreement | Yes |
Yes
| revised | No | S1‑192488 | |||
| S1‑192488 | Service hosting environment aspects of interactive service | OPPO, Samsung, Tencent | CR | Agreement | Yes |
Yes
| agreed | No | S1‑192079 | |||
| S1‑192109 | Performance requirements of interactive service | Huawei, Huawei Device,China Telecom | CR | Agreement | Yes |
Yes
| revised | No | S1‑192489 | |||
| S1‑192489 | Performance requirements of interactive service | Huawei, Huawei Device,China Telecom | CR | Agreement | Yes |
Yes
| revised | No | S1‑192518 | S1‑192109 | ||
| S1‑192518 | Performance requirements of interactive service | Huawei, Huawei Device,China Telecom | CR | Agreement | Yes |
Yes
| revised | No | S1‑192523 | S1‑192489 | ||
| S1‑192523 | Performance requirements of interactive service | Huawei, Huawei Device,China Telecom | CR | Agreement | Yes |
YesSeveral problems with the cover page (wrong spelling of the WI Code, wrong version, highlights being shown, clause affected).
Text in added section 7.x should have been shown as added text. This is new text from 2763.
Was supposed to be merged in 2763 but finally revised.
| revised | No | S1‑192765 | S1‑192518 | ||
| S1‑192765 | Performance requirements of interactive service | Huawei, Huawei Device,China Telecom | CR | Agreement | Yes |
YesNo consensus on the last day.
The CR is against text which does not exist.
| noted | No | S1‑192523 | |||
| 8.2 | AVPROD: Audio-Visual Service Production [SP-190304] | S1‑192008 | Service continuity requirements for video production | NICT | pCR | Approval | Yes |
YesMerged into S1-192506
| merged | No | ||
| S1‑192206 | TS22.263_Skeleton | EBU | pCR | Approval | Yes |
Yes
| agreed | No | ||||
| S1‑192207 | TS22.263_MainBody | EBU | pCR | Approval | Yes |
Yes
| revised | No | S1‑192480 | |||
| S1‑192480 | TS22.263_MainBody | EBU | pCR | Approval | Yes |
Yes
| revised | No | S1‑192509 | S1‑192207 | ||
| S1‑192509 | TS22.263_MainBody | EBU | pCR | Approval | Yes |
Yes
| revised | No | S1‑192747 | S1‑192480 | ||
| S1‑192747 | TS22.263_MainBody | EBU | pCR | Approval | Yes |
Yes
| agreed | No | S1‑192509 | |||
| S1‑192209 | TS22.263_DualConnectivity | EBU | pCR | Approval | Yes |
Yes
| revised | No | S1‑192501 | |||
| S1‑192501 | TS22.263_DualConnectivity | EBU | pCR | Approval | Yes |
Yes
| revised | No | S1‑192507 | S1‑192209 | ||
| S1‑192507 | TS22.263_DualConnectivity | EBU | pCR | Approval | Yes |
Yes
| revised | No | S1‑192749 | S1‑192501 | ||
| S1‑192749 | TS22.263_DualConnectivity | EBU | pCR | Approval | Yes |
Yes
| agreed | No | S1‑192507 | |||
| S1‑192210 | TS22.263_PerformanceRequirements | EBU | pCR | Approval | Yes |
Yes
| revised | No | S1‑192502 | |||
| S1‑192502 | TS22.263_PerformanceRequirements | EBU | pCR | Approval | Yes |
Yes
| revised | No | S1‑192508 | S1‑192210 | ||
| S1‑192508 | TS22.263_PerformanceRequirements | EBU | pCR | Approval | Yes |
Yes
| revised | No | S1‑192750 | S1‑192502 | ||
| S1‑192750 | TS22.263_PerformanceRequirements | EBU, BBC, Sennheiser, b<>com | pCR | Approval | Yes |
YesThe text will be further refined at next meeting.
| agreed | No | S1‑192508 | |||
| S1‑192211 | TS22.263_ServiceRequirements | EBU | pCR | Approval | Yes |
Yes
| revised | No | S1‑192503 | |||
| S1‑192503 | TS22.263_ServiceRequirements | EBU | pCR | Approval | Yes |
Yes
| revised | No | S1‑192506 | S1‑192211 | ||
| S1‑192506 | TS22.263_ServiceRequirements | EBU | pCR | Approval | Yes |
Yes
| revised | No | S1‑192748 | S1‑192503 | ||
| S1‑192748 | TS22.263_ServiceRequirements | EBU | pCR | Approval | Yes |
Yes
| agreed | No | S1‑192506 | |||
| S1‑192373 | TS22.263v0.1.0 to include agreements at this meeting | Rapporteur (EBU) | TR | discussion | Yes |
YesUsed by mistake by another company
| revised | No | S1‑192886 | |||
| S1‑192886 | TS22.263v0.1.0 to include agreements at this meeting | Rapporteur (EBU) | TR | discussion | No |
No
| reserved | No | S1‑192373 | |||
| S1‑192374 | Cover page for presentation of TS22.263v0.1.0 | Rapporteur (EBU) | other | discussion | Yes |
Yes
| agreed | No | ||||
| 8.3 | MPS Phase 2: Multimedia Priority Service Ph2 [SP-190561] | S1‑192231 | Common MPS Voice, Video and Data updates based on TR 22.854, MPS Phase 2 Feasibility Study | Perspecta Labs, CISA ECD,Verizon, AT&T, T-Mobile USA | CR | Approval | Yes |
Yes
| revised | No | S1‑192630 | |
| S1‑192630 | Common MPS Voice, Video and Data updates based on TR 22.854, MPS Phase 2 Feasibility Study | Perspecta Labs, CISA ECD,Verizon, AT&T, T-Mobile USA | CR | Approval | Yes |
Yes
| revised | No | S1‑192730 | S1‑192231 | ||
| S1‑192730 | Common MPS Voice, Video and Data updates based on TR 22.854, MPS Phase 2 Feasibility Study | Perspecta Labs, CISA ECD,Verizon, AT&T, T-Mobile USA | CR | Approval | Yes |
Yes
| agreed | No | S1‑192630 | |||
| S1‑192236 | MPS service specific updates based on TR 22.854, MPS Phase 2 Feasibility Study | Perspecta Labs, CISA ECD, Verizon, AT&T, T-Mobile USA | CR | Approval | Yes |
Yes
| revised | No | S1‑192631 | |||
| S1‑192631 | MPS service specific updates based on TR 22.854, MPS Phase 2 Feasibility Study | Perspecta Labs, CISA ECD, Verizon, AT&T, T-Mobile USA | CR | Approval | Yes |
Yesremove highlights
| revised | No | S1‑192731 | S1‑192236 | ||
| S1‑192731 | MPS service specific updates based on TR 22.854, MPS Phase 2 Feasibility Study | Perspecta Labs, CISA ECD, Verizon, AT&T, T-Mobile USA | CR | Approval | Yes |
Yes
| agreed | No | S1‑192631 | |||
| S1‑192248 | Normative work to update TS 22.153 based on the conclusions of TR 22.854, MPS Phase 2 Feasibility Study | Perspecta Labs, CISA ECD, Verizon, AT&T, T-Mobile USA | discussion | Discussion | Yes |
Yes
| noted | No | ||||
| 8.4 | CMED: Communication Service Requirements for Critical Medical Applications [SP-190306] | S1‑192057 | Addition of new definitions in TS 22.263 | B-Com | pCR | Approval | Yes |
YesMerged into S1-192509
| merged | No | ||
| S1‑192058 | Addition of new references in TS 22.263 | B-Com, Orange | pCR | Approval | Yes |
YesMerged into S1-192509
| merged | No | ||||
| S1‑192059 | Addition of section 4.2 in TS 22.263 | B-Com, Orange | pCR | Approval | Yes |
Yes
| withdrawn | Yes | ||||
| S1‑192060 | Addition of new general performance requirements in TS 22.263 | B-Com | pCR | Approval | Yes |
YesMerged into S1-192508
| merged | No | ||||
| S1‑192061 | Addition of new multicast performance requirements in TS 22.263 | B-Com | pCR | Approval | Yes |
YesMerged into S1-192508
| merged | No | ||||
| S1‑192062 | Addition of security requirements for critical medical applications | B-Com, Vodafone | CR | Approval | Yes |
Yes
| revised | No | S1‑192510 | |||
| S1‑192510 | Addition of security requirements for critical medical applications | B-Com, Vodafone | CR | Approval | Yes |
Yes
| agreed | No | S1‑192062 | |||
| S1‑192063 | Addition of medical telemetry requirements | B-Com, Philips | CR | Approval | Yes |
Yes
| revised | No | S1‑192511 | |||
| S1‑192511 | Addition of medical telemetry requirements | B-Com, Philips | CR | Approval | Yes |
Yes
| agreed | No | S1‑192063 | |||
| S1‑192064 | Addition of robotic aided surgery and diagnosis performance requirements | B-Com | CR | Approval | Yes |
Yes
| revised | No | S1‑192515 | |||
| S1‑192515 | Addition of robotic aided surgery and diagnosis performance requirements | B-Com | CR | Approval | Yes |
Yes
| revised | No | S1‑192751 | S1‑192064 | ||
| S1‑192751 | Addition of robotic aided surgery and diagnosis performance requirements | B-Com | CR | Approval | Yes |
Yes
| agreed | No | S1‑192515 | |||
| S1‑192065 | Addition of a new synchronisation performance requirement | B-Com, Huawei | CR | Approval | Yes |
Yes
| revised | No | S1‑192513 | |||
| S1‑192513 | Addition of a new synchronisation performance requirement | B-Com, Huawei | CR | Approval | Yes |
Yes
| agreed | No | S1‑192065 | |||
| 8.5 | REFEC: enhanced Relays for Energy eFficiency and Extensive Coverage [SP-190307] | S1‑192148 | Connectivity models description section updated. | KPN | CR | Agreement | Yes |
Yes
| revised | No | S1‑192578 | |
| S1‑192578 | Connectivity models description section updated. | KPN | CR | Agreement | Yes |
Yes
| agreed | No | S1‑192148 | |||
| S1‑192150 | Connectivity models new functional requirements | KPN | CR | Agreement | Yes |
Yes
| revised | No | S1‑192579 | |||
| S1‑192579 | Connectivity models new functional requirements | KPN | CR | Agreement | Yes |
Yes
| agreed | No | S1‑192150 | |||
| S1‑192186 | KPIs for UE to network relaying in 5G system | KPN | CR | Agreement | Yes |
Yes
| revised | No | S1‑192580 | |||
| S1‑192580 | KPIs for UE to network relaying in 5G system | KPN | CR | Agreement | Yes |
Yes
| agreed | No | S1‑192186 | |||
| 8.6 | EAV: 5G Enhancement for UAVs [SP-190308] | S1‑192036 | CR to 22.125 New Requirements for EAV | LG Electronics France | CR | Yes |
Yes
| noted | No | |||
| S1‑192038 | Adding UxNB related requirements | ZTE Trunking Technology Corp. | CR | Yes |
Yes
| revised | No | S1‑192527 | ||||
| S1‑192527 | Adding UxNB related requirements | ZTE Corporation, China Unicom, ZTE Trunking Technology Corp | CR | - | Yes |
YesChanges on changes to be removed.
| revised | No | S1‑192795 | S1‑192038 | ||
| S1‑192795 | Adding UxNB related requirements | ZTE Corporation, China Unicom, ZTE Trunking Technology Corp | CR | - | Yes |
YesConditionnally agreed.
| agreed | No | S1‑192527 | |||
| S1‑192051 | EAV service level requirements: discussion paper | InterDigital, Inc. | discussion | Discussion | Yes |
Yes
| noted | No | ||||
| S1‑192068 | KPIs for UAV command and control | InterDigital, Inc. | CR | Approval | Yes |
YesMerged into S1-192528
| merged | No | ||||
| S1‑192069 | Service level requirements for UAV | InterDigital, Inc. | CR | Approval | Yes |
Yes
| noted | No | ||||
| S1‑192082 | 22.125 CR of KPIs for UAV services | China Unicom | CR | Approval | Yes |
Yes
| revised | No | S1‑192528 | |||
| S1‑192528 | 22.125 CR of KPIs for UAV services | China Unicom | CR | Approval | Yes |
YesSprint, Blackberry, Qualcomm, would like this to be postponed to the next meeting.
No version should be indicated in the Reference section.
6 companies support this CR, 5 companies prefer to postpone.
The reason why companies prefer to postpone is that it is seen as important to have the KPIs right from the first time.
| revised | No | S1‑192796 | S1‑192082 | ||
| S1‑192796 | 22.125 CR of KPIs for UAV services | China Unicom | CR | Approval | Yes |
YesSeveral companies have asked to postpone this CR to the next meeting to double check the KPIs in between this meeting and the next one.
| noted | No | S1‑192528 | |||
| S1‑192089 | Definition and introduction of C2 Communication | Intel | CR | Approval | Yes |
Yes
| revised | No | S1‑192524 | |||
| S1‑192524 | Definition and introduction of C2 Communication | Intel | CR | Approval | Yes |
Yes
| revised | No | S1‑192791 | S1‑192089 | ||
| S1‑192791 | Definition and introduction of C2 Communication | Intel | CR | Approval | Yes |
Yes
| agreed | No | S1‑192524 | |||
| S1‑192126 | General description for UAV aspects | China Unicom | CR | Approval | Yes |
Yes
| revised | No | S1‑192531 | |||
| S1‑192531 | General description for UAV aspects | China Unicom | CR | Approval | Yes |
Yesstyles are wrong, references, numberring to be corrected.
| revised | No | S1‑192798 | S1‑192126 | ||
| S1‑192798 | General description for UAV aspects | China Unicom | CR | Approval | Yes |
Yes
| agreed | No | S1‑192531 | |||
| S1‑192130 | CR to 22.125 Network exposure requirements for UAV | China Unicom | CR | Approval | Yes |
Yes
| revised | No | S1‑192525 | |||
| S1‑192525 | CR to 22.125 Network exposure requirements for UAV | China Unicom | CR | Approval | Yes |
Yes
| revised | No | S1‑192793 | S1‑192130 | ||
| S1‑192793 | CR to 22.125 Network exposure requirements for UAV | China Unicom | CR | Approval | Yes |
Yes
| agreed | No | S1‑192525 | |||
| S1‑192141 | CR to 22.125 service experience assurance requirements for UAV | China Unicom | CR | Approval | Yes |
Yes
| revised | No | S1‑192529 | |||
| S1‑192529 | CR to 22.125 service experience assurance requirements for UAV | China Unicom, ZTE, CATT | CR | Approval | Yes |
Yes
| revised | No | S1‑192861 | S1‑192141 | ||
| S1‑192861 | CR to 22.125 service experience assurance requirements for UAV | China Unicom, ZTE, CATT | CR | Approval | No |
Yes
| withdrawn | Yes | S1‑192529 | |||
| S1‑192163 | Service restriction requirements for UAV | CATT, China Unicom, Huawei, ZTE | CR | Yes |
Yes
| revised | No | S1‑192530 | ||||
| S1‑192530 | Service restriction requirements for UAV | CATT, China Unicom, Huawei, ZTE | CR | - | Yes |
Yes
| revised | No | S1‑192797 | S1‑192163 | ||
| S1‑192797 | Service restriction requirements for UAV | CATT, China Unicom, Huawei, ZTE | CR | - | Yes |
Yes
| agreed | No | S1‑192530 | |||
| S1‑192228 | Clarifications on UAS terminology and model | Qualcomm, Airbus | CR | Yes |
Yes
| revised | No | S1‑192485 | ||||
| S1‑192485 | Clarifications on UAS terminology and model | Airbus, Qualcomm, Verizon UK Ltd | CR | - | Yes |
Yes
| revised | No | S1‑192792 | S1‑192228 | ||
| S1‑192792 | Clarifications on UAS terminology and model | Airbus, Qualcomm, Verizon UK Ltd | CR | - | Yes |
Yes
| agreed | No | S1‑192485 | |||
| S1‑192268 | Corrections to References | Airbus DS SLC, Qualcomm Incorporated | CR | Agreement | Yes |
YesMerged into S1-192485
| merged | No | ||||
| S1‑192269 | Corrections to Definitions and Abbreviations | Airbus DS SLC, Qualcomm Incorporated | CR | Agreement | Yes |
YesMerged into S1-192485
| merged | No | ||||
| S1‑192270 | Corrections to Requirements | Airbus DS SLC, Qualcomm Incorporated | CR | Agreement | Yes |
Yes
| revised | No | S1‑192526 | |||
| S1‑192526 | Corrections to Requirements | Airbus DS SLC, Qualcomm Incorporated | CR | Agreement | Yes |
YesThe "VoiD" has to be shown with revision marks.
| revised | No | S1‑192794 | S1‑192270 | ||
| S1‑192794 | Corrections to Requirements | Airbus DS SLC, Qualcomm Incorporated | CR | Agreement | Yes |
Yes
| agreed | No | S1‑192526 | |||
| 8.7 | MUSIM: Support for Multi-USIM Devices [SP-190309] | S1‑192095 | Service requirements for enabling Multi-USIM devices support | Intel | CR | Approval | Yes |
Yes
| revised | No | S1‑192585 | |
| S1‑192585 | Service requirements for enabling Multi-USIM devices support | Intel | CR | Approval | Yes |
YesThe requirements are not numbrerred in 22.101.
2 subsections can be introduced: one for description, one for the actual requirements.
| revised | No | S1‑192809 | S1‑192095 | ||
| S1‑192809 | Service requirements for enabling Multi-USIM devices support | Intel | CR | Approval | Yes |
Yes
| revised | No | S1‑192864 | S1‑192585 | ||
| S1‑192864 | Service requirements for enabling Multi-USIM devices support | Intel | CR | Approval | Yes |
YesNo consensus on the definition. Definiton to be changed and simplified.
| revised | No | S1‑192883 | S1‑192809 | ||
| S1‑192883 | Service requirements for enabling Multi-USIM devices support | Intel | CR | Approval | No |
Yes
| agreed | No | S1‑192864 | |||
| S1‑192096 | Definition for devices supporting multiple USIMs | Intel | CR | Approval | Yes |
YesMerge into S1-192561
| merged | No | ||||
| S1‑192097 | Support for Multi-USIM Devices | Intel | CR | Approval | Yes |
Yes
| revised | No | S1‑192586 | |||
| S1‑192586 | Support for Multi-USIM Devices | Intel | CR | Approval | Yes |
YesThere is yet again a description of the MUSIM service. It is not seen as efficient to introduce one description in 22.101 and one in 22.278. 22.261 might be impacted too.
| revised | No | S1‑192810 | S1‑192097 | ||
| S1‑192810 | Support for Multi-USIM Devices | Intel | CR | Approval | Yes |
Yes
| revised | No | S1‑192865 | S1‑192586 | ||
| S1‑192858 | Support for Multi-USIM Devices | Intel | CR | discussion | No |
Yes
| revised | Yes | S1‑192882 | S1‑192810 | ||
| S1‑192865 | Support for Multi-USIM Devices | Intel | CR | Approval | Yes |
YesUsed by mistake by another company.
2858 replaces 2865.
| withdrawn | No | S1‑192882 | S1‑192810 | ||
| S1‑192882 | Support for Multi-USIM Devices | Intel | CR | Approval | No |
No
| reserved | No | S1‑192865 | |||
| S1‑192098 | Support of Emergency Services for Multi-USIM Devices | Intel | CR | Approval | Yes |
Yes
| revised | No | S1‑192786 | |||
| S1‑192786 | Support of Emergency Services for Multi-USIM Devices | Intel | CR | Approval | Yes |
YesThe added text does not seem to be correct.
| revised | No | S1‑192811 | S1‑192098 | ||
| S1‑192811 | Support of Emergency Services for Multi-USIM Devices | Intel | CR | Approval | Yes |
Yes
| revised | No | S1‑192866 | S1‑192786 | ||
| S1‑192866 | Support of Emergency Services for Multi-USIM Devices | Intel | CR | Approval | Yes |
Yes
| revised | No | S1‑192885 | S1‑192811 | ||
| S1‑192885 | Support of Emergency Services for Multi-USIM Devices | Intel | CR | Approval | No |
Yes
| agreed | No | S1‑192866 | |||
| S1‑192379 | Way Forward Proposal for SA1 FS_MUSIM SI and MUSIM WI | Intel | discussion | Discussion | Yes |
Yes
| noted | No | S1‑192263 | |||
| S1‑192857 | Clarification of requirement 1 in section 8.2 | Rapporteur (Intel) | CR | discussion | Yes |
YesThe first sentence is too long and not understandable.
The note is not clear.
| noted | No | ||||
| S1‑192859 | Support of MUSIM UE | Rapporteur (Intel) | other | discussion | No |
Yes
| withdrawn | Yes | ||||
| 8.8 | eCAV: WID on enhancements for CAV (eCAV) [SP-190310] | S1‑192048 | Add one more case for control-to-control communication | VODAFONE Group Plc | CR | Approval | Yes |
Yes
| agreed | No | ||
| S1‑192072 | Network operation requirements | Nokia, Nokia Shanghai Bell | CR | Yes |
Yes
| revised | No | S1‑192451 | ||||
| S1‑192451 | Network operation requirements | Nokia, Nokia Shanghai Bell | CR | - | Yes |
Yes
| agreed | No | S1‑192072 | |||
| S1‑192140 | eCAV – Further 5G service requirements for Positioning | Huawei Technologies Co. Ltd. | CR | Yes |
Yes
| revised | No | S1‑192691 | ||||
| S1‑192691 | eCAV – Further 5G service requirements for Positioning | Huawei Technologies Co. Ltd. | CR | - | Yes |
Yes
| revised | No | S1‑192452 | S1‑192140 | ||
| S1‑192452 | eCAV – Further 5G service requirements for Positioning | Huawei Technologies Co. Ltd. | CR | - | Yes |
Yes
| revised | No | S1‑192465 | S1‑192691 | ||
| S1‑192465 | eCAV – Further 5G service requirements for Positioning | eCAV – Further 5G service requirements for Positioning | CR | - | Yes |
Yes
| agreed | No | S1‑192452 | |||
| S1‑192189 | eCAV – further 5G service requirements for wired to wireless link replacement for smart manufacturing / Industry 4.0 | Siemens AG | CR | Agreement | Yes |
Yes
| revised | No | S1‑192454 | |||
| S1‑192454 | eCAV – further 5G service requirements for wired to wireless link replacement for smart manufacturing / Industry 4.0 | Siemens AG | CR | Agreement | Yes |
YesMerge of 2189 and 2202
| revised | No | S1‑192868 | S1‑192189 | ||
| S1‑192868 | eCAV – further 5G service requirements for wired to wireless link replacement for smart manufacturing / Industry 4.0 | Siemens AG | CR | Agreement | No |
Yes
| agreed | No | S1‑192454 | |||
| S1‑192202 | eCAV – further 5G service requirements for flexible manufacturing (TSN) | Siemens AG | CR | Agreement | Yes |
YesMerged with 2189 in 2454
| merged | No | ||||
| S1‑192217 | eCAV – Service performance requirements for Industrial Wireless Sensors | Ericsson | CR | Approval | Yes |
Yes
| revised | No | S1‑192455 | |||
| S1‑192455 | eCAV – Service performance requirements for Industrial Wireless Sensors | Ericsson | CR | Approval | Yes |
Yeschanges on changes.
| revised | No | S1‑192867 | S1‑192217 | ||
| S1‑192867 | eCAV – Service performance requirements for Industrial Wireless Sensors | Ericsson | CR | Approval | No |
Yes
| agreed | No | S1‑192455 | |||
| S1‑192227 | Indirect communication for industrial applications | Qualcomm communications-France | CR | Yes |
Yes
| noted | No | |||||
| S1‑192244 | eCAV – further 5G service requirements for industrial Ethernet integration (clock synchronization, time-sensitive communication) | Siemens | CR | Agreement | Yes |
Yes
| revised | No | S1‑192456 | |||
| S1‑192456 | eCAV – further 5G service requirements for industrial Ethernet integration (clock synchronization, time-sensitive communication) | Siemens | CR | Agreement | Yes |
Yeschanges on changes
| revised | No | S1‑192869 | S1‑192244 | ||
| S1‑192869 | eCAV – further 5G service requirements for industrial Ethernet integration (clock synchronization, time-sensitive communication) | Siemens | CR | Agreement | No |
No
| reserved | No | S1‑192456 | |||
| S1‑192256 | eCAV – further 5G service requirements for network operation and management | Siemens, Huawei Technologies | CR | Agreement | Yes |
Yes
| revised | No | S1‑192461 | |||
| S1‑192461 | eCAV – further 5G service requirements for network operation and management | Siemens, Huawei Technologies | CR | Agreement | Yes |
Yescahnges on changes
| revised | No | S1‑192872 | S1‑192256 | ||
| S1‑192872 | eCAV – further 5G service requirements for network operation and management | Siemens, Huawei Technologies | CR | Agreement | No |
Yes
| agreed | No | S1‑192461 | |||
| S1‑192267 | eCAV – further 5G service requirements for network performance | Siemens | CR | Agreement | Yes |
Yes
| revised | No | S1‑192393 | |||
| S1‑192393 | eCAV – further 5G service requirements for network performance | Siemens | CR | Agreement | Yes |
Yes
| revised | No | S1‑192457 | S1‑192267 | ||
| S1‑192457 | eCAV – further 5G service requirements for network performance | Siemens | CR | Agreement | Yes |
Yeschanges on changes.
| revised | No | S1‑192870 | S1‑192393 | ||
| S1‑192870 | eCAV – further 5G service requirements for network performance | Siemens | CR | Agreement | No |
Yes
| agreed | No | S1‑192457 | |||
| S1‑192273 | eCAV – further 5G service requirements for ProSe communication for CAV | Siemens | CR | Agreement | Yes |
Yes
| revised | No | S1‑192458 | |||
| S1‑192458 | eCAV – further 5G service requirements for ProSe communication for CAV | Siemens | CR | Agreement | Yes |
Yeschanges on changes
| revised | No | S1‑192871 | S1‑192273 | ||
| S1‑192871 | eCAV – further 5G service requirements for ProSe communication for CAV | Siemens | CR | Agreement | No |
No
| reserved | No | S1‑192458 | |||
| S1‑192274 | eCAV – further 5G service requirements for ProSe communication for CAV | Siemens | CR | Agreement | Yes |
Yes
| noted | No | ||||
| S1‑192283 | Add a new positioning performance requirement | ETRI | CR | Yes |
Yes
| noted | No | |||||
| 8.9 | MONASTERYEND: Complete Gap Analysis for Railways Mobile Communication System [SP-190312] | S1‑192172 | Enhance MCData generic capability with data pull service | Union Inter. Chemins de Fer | CR | Approval | Yes |
Yes
| revised | No | S1‑192616 | |
| S1‑192616 | Enhance MCData generic capability with data pull service | Union Inter. Chemins de Fer | CR | Approval | No |
Yes
| withdrawn | Yes | S1‑192172 | |||
| S1‑192173 | Activate Location Information report of a specific FA in a certain area | Union Inter. Chemins de Fer | CR | Approval | Yes |
Yes
| revised | No | S1‑192610 | |||
| S1‑192610 | Activate Location Information report of a specific FA in a certain area | Union Inter. Chemins de Fer | CR | Approval | Yes |
Yes
| revised | No | S1‑192637 | S1‑192173 | ||
| S1‑192637 | Activate Location Information report of a specific FA in a certain area | Union Inter. Chemins de Fer | CR | Approval | Yes |
Yes
| agreed | No | S1‑192610 | |||
| S1‑192174 | Support the FRMCS use case for Arbitration when a user is registered to multiple UEs | Union Inter. Chemins de Fer | CR | Approval | Yes |
Yes
| revised | No | S1‑192611 | |||
| S1‑192611 | Support the FRMCS use case for Arbitration when a user is registered to multiple UEs | Union Inter. Chemins de Fer | CR | Approval | Yes |
Yes
| agreed | No | S1‑192174 | |||
| S1‑192175 | Support the FRMCS use case for Arbitration | Union Inter. Chemins de Fer | CR | Approval | Yes |
Yes
| revised | No | S1‑192612 | |||
| S1‑192612 | Support the FRMCS use case for Arbitration | Union Inter. Chemins de Fer | CR | Approval | No |
Yes
| withdrawn | Yes | S1‑192175 | |||
| S1‑192176 | Enhance interworking between MCX and GSM-R with presence | Union Inter. Chemins de Fer | CR | Approval | Yes |
Yes
| noted | No | ||||
| S1‑192177 | Correcting inconsistency of call termination condition for MCX Service types | Union Inter. Chemins de Fer | CR | Approval | Yes |
Yes
| noted | No | ||||
| S1‑192178 | Correcting inconsistency of call termination condition for MCX Service types | Union Inter. Chemins de Fer | CR | Approval | Yes |
Yes
| noted | No | ||||
| S1‑192179 | Clarify routing location dependent communications as part of handling MCX Service Private Communication requests | Union Inter. Chemins de Fer | CR | Approval | Yes |
Yes
| revised | No | S1‑192736 | |||
| S1‑192736 | Clarify routing location dependent communications as part of handling MCX Service Private Communication requests | Union Inter. Chemins de Fer | CR | Approval | Yes |
Yes
| agreed | No | S1‑192179 | |||
| S1‑192182 | Extend Functional Alias binding to MCX Service Private Communication | Union Inter. Chemins de Fer | CR | Approval | Yes |
Yes
| revised | No | S1‑192613 | |||
| S1‑192613 | Extend Functional Alias binding to MCX Service Private Communication | Union Inter. Chemins de Fer | CR | Approval | Yes |
Yes
| agreed | No | S1‑192182 | |||
| S1‑192184 | MCData QoS required for rail communication | Union Inter. Chemins de Fer | CR | Approval | Yes |
Yes
| noted | No | ||||
| S1‑192185 | Video category as a rail communication scenario (limited to main lines) | Union Inter. Chemins de Fer | CR | Approval | Yes |
Yes
| noted | No | ||||
| S1‑192218 | Support the FRMCS use case for Arbitration while operating in off-network mode | Union Inter. Chemins de Fer | CR | Approval | Yes |
Yes
| noted | No | ||||
| S1‑192232 | Support the location services related use cases while operating in off-network mode | Union Inter. Chemins de Fer | CR | Approval | Yes |
Yes
| revised | No | S1‑192614 | |||
| S1‑192614 | Support the location services related use cases while operating in off-network mode | Union Inter. Chemins de Fer | CR | Approval | Yes |
Yes
| agreed | No | S1‑192232 | |||
| S1‑192245 | Support the recording of communication related use cases while operating in off-network mode | Union Inter. Chemins de Fer | CR | Approval | Yes |
Yes
| revised | No | S1‑192615 | |||
| S1‑192615 | Support the recording of communication related use cases while operating in off-network mode | Union Inter. Chemins de Fer | CR | Approval | Yes |
Yes
| revised | No | S1‑192737 | S1‑192245 | ||
| S1‑192737 | Support the recording of communication related use cases while operating in off-network mode | Union Inter. Chemins de Fer | CR | Approval | Yes |
Yes
| agreed | No | S1‑192615 | |||
| 9 | Other technical contributions | S1‑192037 | Additional broadcast regroup requirements | FirstNet | CR | Agreement | Yes |
YesS1-192700 was also allocated to revise this document
| revised | No | S1‑192617 | |
| S1‑192617 | Additional broadcast regroup requirements | FirstNet | CR | Agreement | Yes |
Yes
| agreed | No | S1‑192037 | |||
| S1‑192700 | Addition of user broadcast regroup requirement | FirstNet | CR | Agreement | No |
YesSee S1-192701 for Rel-17 version.
| withdrawn | Yes | S1‑192037 | |||
| S1‑192701 | Addition of user broadcast regroup requirement | FirstNet | CR | Agreement | No |
YesMirror of S1-192700.
Related requirement in S1-192702
S1-192618 used instead of 2701.
| withdrawn | Yes | ||||
| S1‑192618 | CR22.280v17.0.0 Additional broadcast regroup requirements | FirstNet | other | discussion | Yes |
Yes
| agreed | No | ||||
| S1‑192619 | CR22.280v17.0.0 New additional broadcast regroup requirements | FirstNet | other | discussion | Yes |
Yes
| revised | No | S1‑192638 | |||
| S1‑192638 | CR22.280v17.0.0 New additional broadcast regroup requirements | FirstNet | other | discussion | Yes |
Yes
| agreed | No | S1‑192619 | |||
| 10 | Work planning contributions | |||||||||||
| 10.1 | Work Plan | S1‑192699 | SA Prioritization of Rel-17 SA2 Items | 3GPP SA Chairman | discussion | discussion | Yes |
Yes
| noted | No | ||
| 10.2 | Work Item/Study Item status update | S1‑192824 | Status Report on Enhanced Calling Name Analytics Interworking (eCNAM_An) | Ericsson | report | Approval | Yes |
NoeCNAM_An
| available | No | ||
| S1‑192825 | Status Report on eCPSOR_CON | NTT DOCOMO | CR | Approval | Yes |
No
| available | No | ||||
| S1‑192828 | Status report for FS_MMTELin5G | China Mobile | report | Approval | Yes |
NoWID in S1-192827
| available | No | ||||
| S1‑192830 | Report on FS_SACI_MCS | BDBOS | report | Approval | Yes |
YesWID in S1-192829
| revised | No | ||||
| S1‑192856 | Report on SACI_MCS | BDBOS | report | Approval | Yes |
No
| available | No | ||||
| S1‑192819 | Status report of ATRAC | NOVAMINT | report | - | No |
YesWID in S1-192818
| revised | No | ||||
| S1‑192820 | Status report of MINT | LG | report | - | Yes |
No
| available | No | ||||
| S1‑192832 | Status report for MuDE | vivo Mobile Communication Co. LTD | report | Approval | No |
YesWithdrawn, double allocation with 2878
| withdrawn | Yes | ||||
| S1‑192878 | Status Report for MuDE | vvivo Mobile Communication (Rapporteur) | report | Approval | Yes |
NoNew WID in S1-192831
| available | No | ||||
| S1‑192324 | FS_AVPROD – Status report | EBU | REP | discussion | Yes |
No
| available | No | ||||
| S1‑192325 | FS_MPS2 – Status report | Vencore Labs | REP | discussion | Yes |
No
| available | No | ||||
| S1‑192326 | Cover page for TR 22.831 on FS_CMED | b<>com | other | discussion | Yes |
Yesnumber used by another contribution
| revised | No | S1‑192881 | |||
| S1‑192881 | Cover page for TR 22.831 on FS_CMED | b<>com | other | discussion | No |
No
| reserved | No | S1‑192326 | |||
| S1‑192327 | FS_5G_ATRAC – Status report | Novamint | REP | discussion | No |
No
| reserved | No | ||||
| S1‑192328 | FS_REFEC – Status report | KPN | REP | discussion | Yes |
No
| available | No | ||||
| S1‑192329 | FS_EAV – Status report | China Unicom | REP | discussion | No |
No
| reserved | No | ||||
| S1‑192330 | FS_MINT – Status report | LG | REP | discussion | Yes |
No
| available | No | ||||
| S1‑192331 | FS_MUSIM – Status report | Intel | REP | discussion | No |
No
| reserved | No | ||||
| S1‑192332 | FS_eCAV – Status report | Siemens | REP | discussion | No |
No
| reserved | No | ||||
| S1‑192333 | FS_FRMCS3 – Status report | UIC | REP | discussion | Yes |
No
| available | No | ||||
| S1‑192334 | NCIS – Status report | OPPO | REP | discussion | No |
No
| reserved | No | ||||
| S1‑192335 | AVPROD – Status report | EBU | REP | discussion | No |
No
| reserved | No | ||||
| S1‑192336 | MPS2 – Status report | Vencore Labs | REP | discussion | Yes |
No
| available | No | ||||
| S1‑192337 | CMED – Status report | b<>com | REP | discussion | Yes |
No
| available | No | ||||
| S1‑192338 | REFEC – Status report | Novamint | REP | discussion | Yes |
No
| available | No | ||||
| S1‑192339 | EAV – Status report | KPN | REP | discussion | No |
No
| reserved | No | ||||
| S1‑192340 | MUSIM – Status report | Intel | REP | discussion | No |
No
| reserved | No | ||||
| S1‑192341 | eCAV – Status report | Siemens | REP | discussion | No |
No
| reserved | No | ||||
| S1‑192342 | MONASTERYEND – Status report | UIC | REP | discussion | Yes |
No
| available | No | ||||
| 10.3 | SA1 process improvements/updates | S1‑192285 | Considerations for SA1 Process Improvement: Unanswered LS in Time | LG Electronics Deutschland | discussion | Yes |
No
| available | No | |||
| 10.4 | Other non-technical contributions | |||||||||||
| 11 | Next meetings | |||||||||||
| 11.1 | Calendar | |||||||||||
| 12 | Any other business | S1‑192384 | Not used | Reserved Chair | other | discussion | No |
Yes
| withdrawn | Yes | ||
| S1‑192385 | Not used | Reserved Chair | other | discussion | No |
Yes
| withdrawn | Yes | ||||
| S1‑192386 | Not used | Reserved Chair | other | discussion | No |
Yes
| withdrawn | Yes | ||||
| S1‑192387 | Not used | Reserved Chair | other | discussion | No |
Yes
| withdrawn | Yes | ||||
| S1‑192388 | Not used | Reserved Chair | other | discussion | No |
Yes
| withdrawn | Yes | ||||
| S1‑192389 | Not used | Reserved Chair | other | discussion | No |
Yes
| withdrawn | Yes | ||||
| 13 | Close |