Annex A Co-ordinates of TSG and WG Officials
A.1 TSG SA Officials
GRP | Position | oName | Organization | PartnerOrg | PhneFix | PhoneMob | appointed | Remarks |
TSG SA | Chairman | MAYER, Georg | Huawei Technologies Co. Ltd. | ETSI | +4369919005758 | +43 699 1900 5758 | 2019-03-22 | Elected at SA#83 |
TSG SA | ViceChairman | SCHUMACHER, Greg | Sprint Corporation | ATIS | +1 571 426 7940 | +1 571 426 7940 | 2019-03-22 | re-elected atSA#93 |
TSG SA | ViceChairman | KIM, Laeyoung | LG Electronics Inc. | TTA | +821048100298 | 2019-03-22 | re-elected atSA#83 | |
TSG SA | ViceChairman | NAKANO, Yusuke | KDDI Corporation | ARIB | +81 80 5066 9308 | 2019-03-22 | re-eleced at SA#83 | |
TSG SA | SECRETARY | POPE, Maurice | 3GPP Support | +33 4 92 94 42 59 | +33 (0)6 07 59 08 49 | 1998-12-07 | ||
SA WG1 | Chairman | ALMODOVAR CHICO, Jose Luis | KPN N.V. | ETSI | 2019-05-11 | elected at SA1#86 | ||
SA WG1 | ViceChairman | SCHUMACHER, Greg | SPRINT Corporation | ETSI | +1 571 426 7940 | +1 571 426 7940 | 2017-11-29 | elected #80 |
SA WG1 | ViceChairman | LEE, Ki-Dong | LG Electronics Inc. | TTA | +1 858 805 6648 | +1 760 593 7589 | 2017-11-29 | re-elected at S1#80 (2nd term) |
SA WG1 | SECRETARY | SULTAN, Alain | 3GPP Support | +33 4 92 94 42 71 | +33 6 74 40 83 70 | 2007-08-03 | Re-appointed from end of #37bis | |
SA WG4 | ViceChairman | LEUNG, Nikolai | Qualcomm Incorporated | ATIS | +17033468351 | 2017-11-17 | re-elected at SA4#96 (2nd term | |
SA WG4 | ViceChairman | TENIOU, Gilles | Orange | ETSI | +33299124786 | +33689326512 | 2018-10-19 | re-elected at SA4#100 2nd term |
SA WG4 | SECRETARY | SAHA, Jayeeta | 3GPP Support | +33 4 92 94 42 36 | +33 6 80 34 34 14 | 2020-01-08 | ||
SA WG5 | Chairman | TOVINGER, Thomas | Ericsson LM | ETSI | +46 10 712 3010 | +46 709 87 3010 | 2019-08-31 | re-elected at S5#126 2nd term |
SA WG5 | ViceChairman | ZOU, Lan | HuaWei Technologies Co., Ltd | CCSA | +86-13651919688 | 2019-08-31 | re-elected at S5#126 2nd term | |
SA WG5 | ViceChairman | GARDELLA, Maryse | Nokia France | ETSI | +33 1 7323 2751 | 2019-08-31 | re-elected at S5#126 2nd term | |
SA WG5 | SECRETARY | CANO SOVERI, Mirko | 3GPP Support | +33 4 92 94 42 97 | +33 6 73 99 62 94 | 2012-03-05 | ||
SA WG6 | Chairman | CHITTURI, Suresh | Samsung Electronics Co., Ltd | TTA | +91-9591700224 | 2018-03-10 | Elected at SA6#22 | |
SA WG6 | ViceChairman | VIALEN, Jukka | Airbus DS SLC | ETSI | +358401806260 | +358401806260 | 2019-03-04 | Elected at SA6#29 |
SA WG6 | ViceChairman | SOLOWAY, Alan | Qualcomm Incorporated | ATIS | +1-858-736-5491 | 2018-04-21 | Elected at SA6#23 | |
SA WG6 | SECRETARY | MATTSSON, Bernt | 3GPP Support | +33 4 92 94 42 18 | +33 6 87 69 12 50 | 2014-12-12 | ||
SA WG2 | Chairman | JAIN, Puneet | Intel | ATIS | +1-503-712-6214 | 2019-05-18 | Elected at S2#133 | |
SA WG2 | ViceChairman | BENNETT, Andy | Samsung R&D Institute UK | ETSI | +44 1784 428 600 | 2019-05-18 | Elected at S2#133 | |
SA WG2 | ViceChairman | SUN, Tao | China Mobile Com. Corporation | CCSA | 2019-05-18 | Elected at S2#133 | ||
SA WG2 | SECRETARY | POPE, Maurice | 3GPP Support | +33 4 92 94 42 59 | +33 (0)6 07 59 08 49 | 2005-03-11 | ||
SA WG3 | Chairman | BEN HENDA, Noamen | Ericsson LM | ETSI | +0046107160754 | 2019-05-11 | elected at SA3#95 | |
SA WG3 | ViceChairman | ESCOTT, Adrian | Qualcomm Incorporated | ATIS | +44 1252 363209 | 2017-12-01 | re-elected at S3#89 (2nd term) | |
SA WG3 | ViceChairman | ZUGENMAIER, Alf | NTT DOCOMO INC. | ARIB | +49 89 1265 3753 | 2017-12-01 | re-elected at S3#89 (2nd term) | |
SA WG3 | SECRETARY | RIZZO, Carmine | 3GPP Support | +33 4 92 94 42 28 | +33 6 07 59 08 48 | 2016-07-18 | SA3-LI ad hoc subgroup | |
SA WG3 | SECRETARY | CANO SOVERI, Mirko | 3GPP Support | +33 4 92 94 42 97 | +33 6 73 99 62 94 | 2012-03-05 | ||
SA WG4 | Chairman | GABIN, Frederic | Ericsson LM | ETSI | +33 6 78 44 85 75 | +33 6 78 44 85 75 | 2018-10-19 | re-elected at SA4#100 2nd term |
A.2 TSG CT Officials
GRP | Position | oName | Organization | PartnerOrg | PhneFix | PhoneMob | appointed | Remarks |
TSG CT | Chairman | MORAND, Lionel | Orange | ETSI | +33 6 0775 8936 | 2019-03-19 | elected at CT#83 | |
TSG CT | ViceChairman | AGHILI, Behrouz | InterDigital Communications | ATIS | +1-631-7476920 | +1-631-7476920 | 2019-03-19 | re-elected at CT#83 |
TSG CT | ViceChairman | AI, Ming | CATT | CCSA | +86 10 62305566-2180 | 2019-03-19 | elected at CT#83 | |
TSG CT | ViceChairman | ACHTER, Johannes | Deutsche Telekom AG | ETSI | +43 1 79585 6322 | +43 676 3456322 | 2019-03-19 | re-elected at CT#83 |
TSG CT | SECRETARY | KYMALAINEN, Kimmo | 3GPP Support | |||||
CT WG1 | Chairman | LEIS, Peter | Nokia Germany | ETSI | +49 160 90526212 | 2019-04-15 | Elected at CT1#116 | |
CT WG1 | ViceChairman | AXELL, Jörgen | Ericsson LM | ETSI | +46 10 719 4450 | +46 70 519 4450 | 2019-05-17 | Elected at CT1#117 |
CT WG1 | ViceChairman | CHAPONNIERE, Lena | Qualcomm Incorporated | ATIS | +18588452278 | 2019-08-31 | Elected at CT1#119 | |
CT WG1 | SECRETARY | FIRMIN, Frederic | 3GPP Support | +33 4 92 94 43 09 | +33 6 85 76 89 73 | 2008-06-09 | ||
CT WG2 | Chairman | FERNANDEZ, Susana | Ericsson GmbH, Eurolab | ETSI | +34646006865 | 2019-08-31 | re-elected at CT3#105 2rd term | |
CT WG2 | ViceChairman | INOUE, Yoshihiro | NTT | TTC | +81 422 36 7502 | 2019-08-31 | re-elected at CT3#105 2nd term | |
CT WG2 | ViceChairman | ZHENNING, Huang | China Mobile Com. Corporation | CCSA | +86 3488795219 | 2019-08-31 | elected at CT3#105 | |
CT WG2 | SECRETARY | JING, Hao | 3GPP Support | 2019-08-12 | ||||
CT WG2 | SECRETARY | ARORA, Saurav | 3GPP Support | +33 4 92 94 43 08 | 2015-09-01 | |||
CT WG4 | Chairman | SCHMITT, Peter | HuaWei Technologies Co., Ltd | CCSA | +49 171 7450251 | 2019-04-15 | Elected at CT4#90 | |
CT WG4 | ViceChairman | KOZA, Yvette | Deutsche Telekom AG | ETSI | +431795856176 | +436763456176 | 2019-05-18 | elected at CT4#91 |
CT WG4 | ViceChairman | SONG, Yue | China Mobile Com. Corporation | CCSA | +86 13910593416 | 2018-11-30 | elected at CT4#87 | |
CT WG4 | SECRETARY | KYMALAINEN, Kimmo | 3GPP Support | +33 4 92 94 42 38 | +33 6 85 76 89 74 | 2005-03-11 | ||
CT WG6 | Chairman | KRUSE, Heiko | IDEMIA | ETSI | +49 4347-715-0 | +49 175 4383519 | 2018-01-10 | |
CT WG6 | ViceChairman | PHAN, Ly Thanh | Gemalto N.V. | ETSI | +33 1 5501 6112 | +33 6 2411 2444 | 2017-12-01 | elected at CT6#86 |
CT WG6 | SECRETARY | MKINSI, Hakim | 3GPP Support | +33 4 92 94 49 34 | 2017-02-06 | |||
CT WG6 | SECRETARY | KYMALAINEN, Kimmo | 3GPP Support | +33 4 92 94 42 38 | +33 6 85 76 89 74 | 2019-02-21 |
A.3 TSG RAN Officials
GRP | Position | oName | Organization | PartnerOrg | PhneFix | PhoneMob | appointed | Remarks |
TSG RAN | Chairman | BERTENYI, Balazs | Nokia Corporation | ETSI | +36 209849152 | 2019-03-21 | re-elected at RAN#83 | |
TSG RAN | ViceChairman | XU, Xiaodong | China Mobile Com. Corporation | CCSA | +86-10-61198755 | 2019-03-21 | re-elected at RAN#83 | |
TSG RAN | ViceChairman | HAYES, Stephen | Ericsson Inc. | ATIS | +1 469 360 8500 | +1 469 360 8500 | 2019-03-21 | re-elected at RAN#83 |
TSG RAN | ViceChairman | NAGATA, Satoshi | NTT DOCOMO INC. | ARIB | +81 468 40 3333 | 2019-03-21 | re-elected at RAN#83 | |
TSG RAN | SECRETARY | KRAUSE, Joern | 3GPP Support | +33 4 92 94 42 61 | +33 607 59 08 45 | 2009-11-01 | ||
RAN WG1 | Chairman | CHEN, Wanshi | Qualcomm Incorporated | ATIS | +18583663080 | 2017-08-21 | elected at RAN1#90 | |
RAN WG1 | ViceChairman | KIM, Younsun | Samsung Electronics Co., Ltd | TTA | +821028762589 | 2017-08-23 | elected at RAN1#90 | |
RAN WG1 | ViceChairman | KOORAPATY, Havish | Ericsson LM | ETSI | +1 919 2713539 | 2017-10-09 | elected at RAN1#90bis | |
RAN WG1 | SECRETARY | MERIAS, Patrick | 3GPP Support | +33 4 92 94 42 06 | +33 6 07 59 08 47 | 2013-10-01 | (as ETSI staff) | |
RAN WG2 | Chairman | JOHANSSON, Johan | MediaTek Beijing Inc. | CCSA | +46700962260 | 2019-08-31 | elected at RAN2#107 | |
RAN WG2 | ViceChairman | PAROLARI, Sergio | ZTE Corporation | ETSI | +39 3395658207 | 2019-08-31 | elected at RAN2#107 | |
RAN WG2 | ViceChairman | HENTTONEN, Tero | Nokia Corporation | ETSI | +358504836369 | 2019-08-31 | elected at RAN2#107 | |
RAN WG2 | SECRETARY | KORHONEN, Juha | 3GPP Support | +33 4 92 94 43 52 | 06 74 40 83 78 | 2017-01-01 | ||
RAN WG3 | Chairman | MASINI, Gino | Ericsson LM | ETSI | +46 10 7175167 | +46 76 7729167 | 2019-05-18 | re-elected at RAN3#104 |
RAN WG3 | ViceChairman | GAO, Yin | ZTE Corporation | ETSI | +86-021-68895728 | 2017-08-21 | elected at RAN3#97 | |
RAN WG3 | ViceChairman | SIROTKIN, Sasha | Intel | ATIS | +972507288473 | 2019-05-18 | re-elected at RAN3#104 | |
RAN WG3 | SECRETARY | TOUFIK, Issam | 3GPP Support | +33 4 92 94 49 63 | +33.6.14.92.11.41 | 2016-09-28 | ||
RAN WG4 | Chairman | ZHOU, Xutao | Samsung Electronics Co., Ltd | TTA | +86-10-84439777 | +86-18601163270 | 2017-12-01 | re-elected at R4#85 (2nd term) |
RAN WG4 | ViceChairman | CHERVYAKOV, Andrey | Intel | ATIS | +7 831 296 94 44 | 2019-08-31 | elected at R4#92b | |
RAN WG4 | ViceChairman | QUI, Haijie | Samsung Electronics Co., Ltd | TTA | +82 342 779 6818 | 2019-08-31 | elected at R4#92b | |
RAN WG4 | SECRETARY | OH, Kyoungseok | 3GPP Support | +33 49294 4231 | +33 607 59 08 55 | 2017-01-01 | ||
RAN WG5 | Chairman | JOHN, Jacob | Motorola Mobility España SA | ETSI | +61 419 147 260 | 2017-08-21 | re-elected at RAN5#76 | |
RAN WG5 | ViceChairman | GOWDA, Pradeep | Qualcomm Incorporated | ATIS | +1858-845-7131 | 2017-12-01 | re-elected at R5#77 (3rd term) | |
RAN WG5 | ViceChairman | CHEN, Xiaozhong | CATT | ETSI | +8613911652018 | 2017-08-21 | re-elected at R5#76 | |
RAN WG5 | SECRETARY | SIGOVICH, Ingbert | 3GPP Support | +33 4 92 94 43 24 | +33 674 408 375 | 2008-04-29 | ||
RAN WG6 | Chairman | HOFMANN, Juergen | Nokia Germany | ETSI | +49 170 7869957 | +49 170 7869957 | 2018-11-16 | Re-elected at RAN6#10 |
RAN WG6 | SECRETARY | USAI, Paolino | 3GPP Support | +33 4 92 94 42 36 | +33 6 74 40 83 73 | 2016-06-16 | ||
RAN ITU AH | Convenor | ROMANO, Giovanni | TELECOM ITALIA S.p.A. | ETSI | +39 011 228 7069 | 2013-03-01 | Confirmed 2017-05-25 | |
RAN ITU AH | SECRETARY | KRAUSE, Joern | 3GPP Support | +33 4 92 94 42 61 | +33 607 59 08 45 | 2009-11-01 |
Annex B Lists of documents
B.1 List of documents by TD number
AI | TD# | Type | Title | Source | Specification | CRNo | CRrev | Cat | Ver | Rel | WI | Comment | Decision | Revised to TD# |
1.4 | SP-200632 | AGENDA | Agenda & Procedures & Time Schedule for TSG SA#88-e | TSG SA Chairman | - | - | - | - | Approved | Approved | ||||
1.5 | SP-200633 | REPORT | Draft report of TSG SA meeting #88E | TSG SA Secretary | - | - | - | - | Approved | Approved | ||||
2.2 | SP-200634 | LS In | LS from IALA: Liaison Note to TSG SA - Request for information | IALA | - | - | - | - | Postponed SP-200310 from SA#88E. Response drafted in SP-200655. Final response in SP-200877 | Replied to | ||||
2.1 | SP-200635 | LS In | LS from ITU-R WP 5D: LIAISON STATEMENT TO RIT/SRIT PROPONENTS ON THE COMPLETION AND CONCLUSIONS OF STEPS 5 TO 7 OF THE IMT-2020 PROCESS FOR THE FIRST RELEASE OF NEW RECOMMENDATION ITU-R M.[IMT-2020.SPECS] | ITU-R WP 5D | - | - | - | - | CC#1: This was block noted | Noted | ||||
2.1 | SP-200636 | LS In | LS from ITU-R WP5D: LIAISON STATEMENT TO TRANSPOSING ORGANIZATIONS ON THE COMPLETION OF STEP 8 OF IMT-2020 PROCESS FOR THE FIRST RELEASE OF NEW RECOMMENDATION ITU-R M.[IMT-2020.SPECS] | ITU-R WP5D | - | - | - | - | CC#1: This was block noted | Noted | ||||
2.1 | SP-200637 | LS In | LS from ETSI ISG E4P: Request for information exchange | ETSI ISG E4P | - | - | - | - | CC#1: This was block noted | Noted | ||||
2.2 | SP-200638 | LS In | LS from ITU-T JCA-IMT2020: LS on Invitation to update the information in the IMT2020 roadmap | ITU-T JCA-IMT2020 | - | - | - | - | Response drafted in SP-200856. Final response in SP-200887 | Replied to | ||||
2.1 | SP-200639 | LS In | LS from TM Forum Autonomous Networks: Introduction of TM Forum Autonomous Network project and Coordination Proposal | TM Forum Autonomous Networks | - | - | - | - | CC#1: This was block noted | Noted | ||||
2.1 | SP-200640 | LS In | LS from IETF: Re: LS on need for Multi-Path QUIC for ATSSS | IETF | - | - | - | - | CC#1: This was block noted | Noted | ||||
2.1 | SP-200641 | LS In | LS from IETF DRIP: Drone Remote ID Protocol Working Group (DRIP) | IETF DRIP | - | - | - | - | CC#1: This was block noted | Noted | ||||
2.1 | SP-200642 | LS In | LS from ITU-R WP5A: LIAISON STATEMENT TO EXTERNAL ORGANIZATIONS ON ITS Connected Automated Vehicles (CAV) | ITU-R WP5A | - | - | - | - | CC#1: This was block noted | Noted | ||||
2.1 | SP-200643 | LS In | LS from TSG RAN: Reply LS to RP-200030 on relevant 3GPP Specs for PC5 Sidelink | TSG RAN | - | - | - | - | CC#1: This was block noted | Noted | ||||
2.1 | SP-200644 | LS In | LS from TSG RAN: Reply LS to GSMA_5GSI_28_Doc003 = RP-193053 on 5G indicator enhancement | TSG RAN | - | - | - | - | CC#1: This was block noted | Noted | ||||
2.1 | SP-200645 | LS In | LS from ITU-T SG13: LS/o on information about consent of Machine Learning related ITU-T Recommendation Y.3176 | ITU-T SG13 | - | - | - | - | CC#1: This was block noted | Noted | ||||
2.2 | SP-200646 | LS In | LS from TM Forum: TM Forum implementation experiences 3GPP NRM Models | TM Forum | - | - | - | - | CC#2: This was Block Noted | Noted | ||||
2.2 | SP-200647 | LS In | LS from SA WG2: LS on mandatory support of full rate user plane integrity protection for 5G | SA WG2 | - | - | - | - | Rel-16 | TEI16 | CC#2: This was Block Noted | Noted | ||
2.2 | SP-200648 | LS In | LS on mandatory support of full rate user plane integrity protection for 5G | CT WG1 | - | - | - | - | Rel-16 | TEI16 | CC#2: This was Block Noted | Noted | ||
2.1 | SP-200649 | LS In | LS from CT WG4: LS on AUSF/UDM discovery based on SUCI information | CT WG4 | - | - | - | - | Rel-17 | SBIProtoc17 | CC#1: This was block noted | Noted | ||
2.2 | SP-200650 | LS In | LS from RAN WG2: Response LS to TSG SA on mandatory support of full rate user plane integrity protection for 5G | RAN WG2 | - | - | - | - | Rel-16 | CC#2: This was Block Noted | Noted | |||
2.2 | SP-200651 | LS In | LS from RAN WG3: Reply LS on mandatory support of full rate user plane integrity protection for 5G | RAN WG3 | - | - | - | - | Rel-16 | CC#2: This was Block Noted | Noted | |||
2.2 | SP-200652 | LS In | LS from SA WG2: LS on RAN impact of FS_5MBS Study | SA WG2 | - | - | - | - | Rel-17 | FS_5MBS, NR_MBS-Core | Response drafted in SP-200810. Final response in SP-200884 | Replied to | ||
2.1 | SP-200653 | LS In | LS from SA WG5: LS reply to LS on M.resm-AI “Requirements for energy saving management of 5G RAN system with AI” | SA WG5 | - | - | - | - | Rel-17 | CC#1: This was block noted | Noted | |||
2.2 | SP-200654 | LS In | LS from CT WG1: LS on the stage 2 aspects of MINT | CT WG1 | - | - | - | - | Rel-17 | MINT | Response drafted in SP-200775. Final response in SP-200880 | Replied to | ||
2.2 | SP-200655 | LS OUT | [DRAFT] Reply LS on request for information from IALA | SyncTechno Inc. | - | - | - | - | MARCOM | Response to SP-200634. MCC will need to revise to remove 'draft'. Revised to SP-200877. | Revised | SP-200877 | ||
6.2 | SP-200656 | WID REVISED | Revised WID on the normative aspects of User Plane Integrity Protection for NR. | Vodafone | - | - | - | - | Rel-17 | UPIP_SEC | Approved. The 3GPP Work Plan will need to be updated to indicate Rel-16 for UPIP_SEC. | Approved | ||
16 | SP-200657 | CR | 21.900 CR0064 (Rel-16, 'C'): CR to TR 21.900 on Relaxation of mini-WID requirement for Cat.B/C TEI CRs | NEC on behalf of TSG RAN | 21.900 | 0064 | - | C | 16.3.0 | Rel-16 | TEI16 | Same as draft CR proposed by TSG RAN in SP-200868. CC#4: Postponed | Postponed | |
4.4 | SP-200658 | REPORT | SA WG4 Chairman's Report | 3GPP SA4 | - | - | - | - | Noted | Noted | ||||
16.4 | SP-200659 | CR PACK | CRs to TS 26.116 | SA WG4 | 26.116 | - | - | - | - | Rel-16 | 5GMS3 | This was Block approved in CC#3 | Approved | |
16.4 | SP-200660 | CR PACK | CRs to TS 26.223 | SA WG4 | 26.223 | - | - | - | - | Rel-16 | TEI16 | This was Block approved in CC#3 | Approved | |
16.4 | SP-200661 | CR PACK | CRs to TS 26.234 | SA WG4 | 26.234 | - | - | - | - | Rel-16 | RM_H263_MP4V | This was Block approved in CC#3 | Approved | |
16.4 | SP-200662 | CR PACK | CRs to TS 26.238 | SA WG4 | 26.238 | - | - | - | - | Rel-16 | E_FLUS | This was Block approved in CC#3 | Approved | |
16.4 | SP-200663 | CR PACK | CRs to TS 26.501 | SA WG4 | 26.501 | - | - | - | - | Rel-16 | 5GMSA | This was Block approved in CC#3 | Approved | |
16.4 | SP-200664 | CR PACK | CRs to TS 26.511 | SA WG4 | 26.511 | - | - | - | - | Rel-16 | 5GMS3 | This was Block approved in CC#3 | Approved | |
16.4 | SP-200665 | CR PACK | CRs to TS 26.114 | SA WG4 | 26.114 | - | - | - | - | Rel-16 | TEI16, E2E_DELAY | This was Block approved in CC#3 | Approved | |
6.10 | SP-200666 | DRAFT TS | Draft TS 26.512: 5G Media Streaming (5GMS); Protocols | SA WG4 | 26.512 | - | - | - | - | Rel-16 | 5GMS3 | This was Block approved in CC#3 | Approved | |
6.4 | SP-200667 | WID NEW | New Work Item on 'Operation Points for 8K VR 360 Video over 5G'. | Intel, NHK, Ericsson LM, AT&T, Qualcomm Incorporated, Dolby Laboratories Inc., Beijing Xiaomi Electronics, Tencent, Huawei Technologies Co Ltd. | - | - | - | - | Rel-17 | This was Block approved in CC#3 | Approved | |||
16.4 | SP-200668 | CR PACK | CR to 26.247 | SA WG4 | 26.247 | - | - | - | - | Rel-16 | 5GMS3 | This was Block approved in CC#3 | Approved | |
4.3 | SP-200669 | REPORT | SA WG3 Status report | SA WG3 Chairman | - | - | - | - | Noted | Noted | ||||
4.2 | SP-200670 | REPORT | SA WG2 Report to TSG SA | SA WG2 Chairman | - | - | - | - | Noted | Noted | ||||
15 | SP-200671 | CR PACK | CRs to 23.501, 23.502 on 5GS_Ph1 (Rel-15, Rel-16) | SA WG2 | - | - | - | - | This was Block approved in CC#3 | Approved | ||||
15 | SP-200672 | CR PACK | CRs to 23.401 on NB_IOTenh-Core, CIoT_ext (Rel-15, Rel-16) | SA WG2 | - | - | - | - | This was Block approved in CC#3 | Approved | ||||
16.2 | SP-200673 | CR PACK | CRs to 23.501, 23.502, 23.503 on 5G_CIoT (Rel-16) | SA WG2 | - | - | - | - | This was Block approved in CC#3 | Approved | ||||
16.2 | SP-200674 | CR PACK | CRs to 23.501, 23.502 on 5G_eSBA (Rel-16) | SA WG2 | - | - | - | - | This was Block approved in CC#3 | Approved | ||||
16.2 | SP-200675 | CR PACK | CR to 23.501 on 5G_URLLC (Rel-16) | SA WG2 | - | - | - | - | This was Block approved in CC#3 | Approved | ||||
16.2 | SP-200676 | CR PACK | CRs to 23.316, 23.502 on 5WWC (Rel-16) | SA WG2 | - | - | - | - | This was Block approved in CC#3 | Approved | ||||
16.2 | SP-200677 | CR PACK | CR to 23.501 on ATSSS (Rel-16) | SA WG2 | - | - | - | - | This was Block approved in CC#3 | Approved | ||||
16.2 | SP-200678 | CR PACK | CRs to 23.228, 23.501 on eIMS5G_SBA (Rel-16) | SA WG2 | - | - | - | - | This was Block approved in CC#3 | Approved | ||||
16.2 | SP-200679 | CR PACK | CRs to 23.228, 23.502, 23.503 on eNA (Rel-16) | SA WG2 | - | - | - | - | This was Block approved in CC#3 | Approved | ||||
16.2 | SP-200680 | CR PACK | CRs to 23.502 on eNS (Rel-16) | SA WG2 | - | - | - | - | This was Block approved in CC#3 | Approved | ||||
16.2 | SP-200681 | CR PACK | CRs to 23.502 on ETSUN (Rel-16) | SA WG2 | - | - | - | - | This was Block approved in CC#3 | Approved | ||||
16.2 | SP-200682 | CR PACK | CRs to 23.285, 23.287, 23.502, 23.503 on eV2XARC (Rel-16) | SA WG2 | - | - | - | - | This was Block approved in CC#3 | Approved | ||||
16.2 | SP-200683 | CR PACK | CR to 23.501 on IABARC (Rel-16) | SA WG2 | - | - | - | - | This was Block approved in CC#3 | Approved | ||||
16.2 | SP-200684 | CR PACK | CR to 23.401 on PARLOS (Rel-16) | SA WG2 | - | - | - | - | This was Block approved in CC#3 | Approved | ||||
16.2 | SP-200685 | CR PACK | CRs to 23.401, 23.502 on RACS (Rel-16) | SA WG2 | - | - | - | - | Company proposed revision of 23.501 CR2383R1 in SP-200802. CC#1: 23.501 CR2383R1 was considered as revised and other CRs in this CR pack were approved. | Partially approved | ||||
16.2 | SP-200686 | CR PACK | CRs to 23.214, 23.501, 23.502, 23.682 on TEI16 (Rel-16) | SA WG2 | - | - | - | - | This was Block approved in CC#3 | Approved | ||||
16.2 | SP-200687 | CR PACK | CR to 23.501 on UDICOM (Rel-16) | SA WG2 | - | - | - | - | This was Block approved in CC#3 | Approved | ||||
16.2 | SP-200688 | CR PACK | CRs to 23.501, 23.502, 23.503 on Vertical_LAN (Rel-16) | SA WG2 | - | - | - | - | CC#1: 23.501 CR2448R1 was reported needing further work and was postponed. All other CRs in this CR pack were approved. | Partially approved | ||||
16.2 | SP-200689 | CR PACK | CR to 23.502 on xBDT (Rel-16) | SA WG2 | - | - | - | - | This was Block approved in CC#3 | Approved | ||||
6.5 | SP-200690 | SID REVISED | Revised SID: Architectural enhancements for 5G multicast-broadcast services. | SA WG2 | - | - | - | - | Rel-17 | FS_5MBS | This was Block approved in CC#3 | Approved | ||
6.9 | SP-200691 | DRAFT TR | Presentation of TR 23.748 for information to TSG SA (FS_enh_EC) | SA WG2 | 23.748 | - | - | - | - | Rel-17 | FS_enh_EC | This was block noted in CC#3 | Noted | |
6.9 | SP-200692 | DRAFT TR | Presentation of TR 23.700-20 for information to TSG SA (FS_IIoT) | SA WG2 | 23.700-20 | - | - | - | - | Rel-17 | FS_IIoT | This was block noted in CC#3 | Noted | |
6.9 | SP-200693 | DRAFT TR | Presentation of TR 23.761 for information to TSG SA (FS_MUSIM) | SA WG2 | 23.761 | - | - | - | - | Rel-17 | FS_MUSIM | This was block noted in CC#3 | Noted | |
6.9 | SP-200694 | DRAFT TR | Presentation of TR 23.700-91 for Information to TSG SA (FS_eNA_Ph2) | SA WG2 | 23.700-91 | - | - | - | - | Rel-17 | FS_eNA_Ph2 | This was block noted in CC#3 | Noted | |
6.9 | SP-200695 | DRAFT TR | Presentation of presentation of TR 23.700-07 for information to TSG SA (FS_eNPN) | SA WG2 | 23.700-07 | - | - | - | - | Rel-17 | FS_eNPN | This was block noted in CC#3 | Noted | |
6.9 | SP-200696 | DRAFT TR | Presentation of TR 23.757 for information to TSG SA (FS_5MBS) | SA WG2 | 23.757 | - | - | - | - | Rel-17 | FS_5MBS | This was block noted in CC#3 | Noted | |
6.9 | SP-200698 | DRAFT TR | Presentation of TR 23.700-40 to TSG SA for information (FS_eNS_Ph2) | SA WG2 | 23.700-40 | - | - | - | - | Rel-17 | FS_eNS_Ph2 | This was block noted in CC#3 | Noted | |
6.9 | SP-200699 | DRAFT TR | Presentation of TR 23.700-93 to TSG SA for information (FS_ATSSS_Ph2) | SA WG2 | 23.700-93 | - | - | - | - | Rel-17 | FS_ATSSS_Ph2 | This was block noted in CC#3 | Noted | |
6.9 | SP-200700 | DRAFT TR | Presentation of TR 23.754 for information to TSG SA (FS_ID_UAS_SA2) | SA WG2 | 23.754 | - | - | - | - | Rel-17 | FS_ID_UAS_SA2 | This was block noted in CC#3 | Noted | |
16.3 | SP-200701 | CR PACK | Rel-16 CRs on TEI | SA WG3 | - | - | - | - | TEI16 | This was Block approved in CC#3 | Approved | |||
15 | SP-200702 | CR PACK | Rel-15 CRs on Security Assurance Specification for eNB network product class | SA WG3 | - | - | - | - | SCAS_eNB | This was Block approved in CC#3 | Approved | |||
16.3 | SP-200703 | CR PACK | Rel-16 CRs on Security Assurance Specification for 5G | SA WG3 | - | - | - | - | SCAS_5G | This was Block approved in CC#3 | Approved | |||
16.3 | SP-200705 | CR PACK | Rel-16 CRs on Security Aspects of eV2XARC | SA WG3 | - | - | - | - | eV2XARC | CC#1: 33.536 CR0002 was reported needing further work and was postponed. All other CRs in this CR pack were approved. | Partially approved | |||
16.3 | SP-200706 | CR PACK | Rel-16 CRs on Security for enhancements to the Service Based 5G System Architecture | SA WG3 | - | - | - | - | 5G_eSBA | 33.501 CR0908R1 should be a CR to 33.310, so should be rejected. Replacement CR to 33.310 provided in SP-200857. 33.501 CR0908R1 was rejected. Al other CRs in this CR Pack were approved | Partially approved | |||
16.3 | SP-200707 | CR PACK | Rel-16 CRs on Security for IAB | SA WG3 | - | - | - | - | NR_IAB | This was Block approved in CC#3 | Approved | |||
16.3 | SP-200708 | CR PACK | Rel-16 CRs on Authentication and key management for applications based on 3GPP credential in 5G | SA WG3 | - | - | - | - | AKMA | This was Block approved in CC#3 | Approved | |||
15 | SP-200709 | CR PACK | Rel-15 CRs on Security aspects of 5G System - Phase 1 batch 1 | SA WG3 | - | - | - | - | 5GS_Ph1-SEC | This was Block approved in CC#3 | Approved | |||
16.3 | SP-200710 | CR PACK | Rel-16 CRs on User Plane Gateway Function for Inter-PLMN Security | SA WG3 | - | - | - | - | UPGF | This was Block approved in CC#3 | Approved | |||
19 | SP-200711 | CR PACK | Rel-16 CRs for Study on Security Aspects of 3GPP support for Advanced V2X Services | SA WG3 | - | - | - | - | FS_eV2X_Sec | This was Block approved in CC#3 | Approved | |||
19 | SP-200712 | CR PACK | Rel-16 CRs onStudy on Security Aspects of the 5G Service Based Architecture | SA WG3 | - | - | - | - | FS_SBA_Sec | This was Block approved in CC#3 | Approved | |||
19 | SP-200713 | CR PACK | Rel-16 CRs on Study on evolution of Cellular IoT security for the 5G System | SA WG3 | - | - | - | - | FS_CIoT_sec_5G | This was Block approved in CC#3 | Approved | |||
13 | SP-200714 | CR PACK | Rel-13 CRs on Enhancements to WEBRTC interoperability | SA WG3 | - | - | - | - | eWebRTCi | This was Block approved in CC#3 | Approved | |||
16.3 | SP-200715 | CR PACK | Rel-16 CRs on Security aspects of SEAL | SA WG3 | - | - | - | - | SEAL | This was Block approved in CC#3 | Approved | |||
16.3 | SP-200716 | CR PACK | Rel-16 CRs on Security aspects of Enhanced Network Slicing | SA WG3 | - | - | - | - | eNS | This was Block approved in CC#3 | Approved | |||
6.3 | SP-200717 | SID NEW | New SID on security aspects of the 5GMSG Service. | SA WG3 | - | - | - | - | CC#2: SP 200717_rev1 was approved. Revised to SP-200878. | Revised | SP-200878 | |||
6.4 | SP-200718 | WID NEW | New WID on mission critical security enhancements phase 2. | SA WG3 | - | - | - | - | CC#3: SP-200718_rev2 was approved. (To be revised into a new TD number by MCC). Revised to SP-200879. | Revised | SP-200879 | |||
6.4 | SP-200719 | WID NEW | New WID on UPIP support in 5GS. | SA WG3 | - | - | - | - | This was Block approved in CC#3 | Approved | ||||
6.4 | SP-200720 | WID NEW | New WID on Security Assurance Specification for Network Slice-Specific Authentication and Authorization Function (NSSAAF). | SA WG3 | - | - | - | - | This was Block approved in CC#3 | Approved | ||||
6.3 | SP-200721 | SID NEW | New study on the security of AMF re-allocation. | SA WG3 | - | - | - | - | This was Block approved in CC#3 | Approved | ||||
6.3 | SP-200722 | SID NEW | New SID on security aspects of enablers for Network Automation (eNA) for the 5G System (5GS) Phase 2. | SA WG3 | - | - | - | - | This was Block approved in CC#3 | Approved | ||||
16.5 | SP-200723 | CR PACK | Rel-16 CRs on Streaming trace reporting | SA WG5 | - | - | - | - | Rel-16 | OAM_RTT | This was Block approved in CC#3 | Approved | ||
16.5 | SP-200724 | CR PACK | Rel-16 CRs on TEI | SA WG5 | - | - | - | - | TEI16 | This was Block approved in CC#3 | Approved | |||
15 | SP-200725 | CR PACK | Rel-15 CRs on TEI | SA WG5 | - | - | - | - | TEI15 | This was Block approved in CC#3 | Approved | |||
12 | SP-200726 | CR PACK | Rel-12 CRs on TEI | SA WG5 | - | - | - | - | TEI12 | This was Block approved in CC#3 | Approved | |||
11 | SP-200727 | CR PACK | Rel-11 CRs on TEI | SA WG5 | - | - | - | - | TEI12 | This was Block approved in CC#3 | Approved | |||
10 | SP-200728 | CR PACK | Rel-10 CRs on TEI | SA WG5 | - | - | - | - | TEI10 | This was Block approved in CC#3 | Approved | |||
16.5 | SP-200729 | CR PACK | Rel-16 CRs on NRM enhancements | SA WG5 | - | - | - | - | eNRM | This was Block approved in CC#3 | Approved | |||
15 | SP-200730 | CR PACK | Rel-15 CRs on Network Resource Model (NRM) for 5G networks and network slicing | SA WG5 | - | - | - | - | NETSLICE-5GNRM | This was Block approved in CC#3 | Approved | |||
15 | SP-200731 | CR PACK | Rel-15 CRs on Performance Assurance for 5G networks including network slicing | SA WG5 | - | - | - | - | NETSLICE-ADPM5G | This was Block approved in CC#3 | Approved | |||
16.5 | SP-200732 | CR PACK | Rel-16 CRs on Self-Organizing Networks (SON) for 5G networks | SA WG5 | - | - | - | - | SON_5G | This was Block approved in CC#3 | Approved | |||
16.5 | SP-200733 | CR PACK | Rel-16 CRs on Charging Access of ATSSS | SA WG5 | - | - | - | - | ATSSS | This was Block approved in CC#3 | Approved | |||
16.5 | SP-200734 | CR PACK | Rel-16 CRs on Energy efficiency of 5G | SA WG5 | - | - | - | - | EE_5G | This was Block approved in CC#3 | Approved | |||
15 | SP-200735 | CR PACK | Rel-15 CRs on Provisioning of network slicing for 5G networks and services | SA WG5 | - | - | - | - | NETSLICE-PRO_NS | This was Block approved in CC#3 | Approved | |||
15 | SP-200736 | CR PACK | Rel-15 CRs on Management and orchestration of 5G networks and network slicing | SA WG5 | - | - | - | - | NETSLICE | This was Block approved in CC#3 | Approved | |||
16.5 | SP-200737 | CR PACK | Rel-16 CRs on Integration of ONAP and 3GPP 5G management framework | SA WG5 | - | - | - | - | ONAP3GPP | This was Block approved in CC#3 | Approved | |||
16.5 | SP-200738 | CR PACK | Rel-16 CRs on Enhancement of performance assurance for 5G networks including network slicing batch 1 | SA WG5 | - | - | - | - | 5G_SLICE_ePA | This was Block approved in CC#3 | Approved | |||
16.5 | SP-200740 | CR PACK | Rel-16 CRs on Charging Enhancement of 5GC interworking with EPC | SA WG5 | - | - | - | - | 5GIEPC_CH | This was Block approved in CC#3 | Approved | |||
16.5 | SP-200741 | CR PACK | Rel-16 CRs on CHF-controlled quota management | SA WG5 | - | - | - | - | CHFCQM | This was Block approved in CC#3 | Approved | |||
15 | SP-200742 | CR PACK | Rel-15 CRs on Service Based Interface for 5G Charging | SA WG5 | - | - | - | - | 5GS_Ph1-SBI_CH | This was Block approved in CC#3 | Approved | |||
16.5 | SP-200743 | CR PACK | Rel-16 CRs on Network Slice Performance and Analytics Charging in 5G System | SA WG5 | - | - | - | - | 5GS_NSPACH | This was Block approved in CC#3 | Approved | |||
16.5 | SP-200744 | CR PACK | Rel-16 CRs on Management of MDT in 5G | SA WG5 | - | - | - | - | 5GMDT | This was Block approved in CC#3 | Approved | |||
16.5 | SP-200745 | CR PACK | Rel-16 CRs on Network Slice Management Charging in 5G System | SA WG5 | - | - | - | - | 5GS_NSMCH | This was Block approved in CC#3 | Approved | |||
17.5 | SP-200746 | CR PACK | Rel-17 CRs on Management of MDT enhancement in 5G | SA WG5 | - | - | - | - | e_5GMDT | This was Block approved in CC#3 | Approved | |||
17.5 | SP-200747 | CR PACK | Rel-17 CRs on Enhancements of 5G performance measurements and KPIs | SA WG5 | - | - | - | - | ePM_KPI_5G | This was Block approved in CC#3 | Approved | |||
17.5 | SP-200748 | CR PACK | Rel-17 CRs on Additional NRM features | SA WG5 | - | - | - | - | adNRM | This was Block approved in CC#3 | Approved | |||
17.5 | SP-200749 | CR PACK | Rel-17 CRs on Enhancement on Management Aspects of 5G Service-Level Agreement | SA WG5 | - | - | - | - | EMA5SLA | This was Block approved in CC#3 | Approved | |||
16.5 | SP-200750 | CR PACK | Rel-16 CRs on Closed loop SLS Assurance | SA WG5 | - | - | - | - | COSLA | This was Block approved in CC#3 | Approved | |||
16.5 | SP-200751 | CR PACK | Rel-16 CRs on KPI reporting | SA WG5 | - | - | - | - | 5G_SLICE_ePA-KPI | This was Block approved in CC#3 | Approved | |||
17.5 | SP-200752 | CR PACK | Rel-17 CRs on Enhancements of Self-Organizing Networks (SON) for 5G networks | SA WG5 | - | - | - | - | eSON_5G | This was Block approved in CC#3 | Approved | |||
16.5 | SP-200753 | CR PACK | Rel-16 CRs on Trace Management in the context of Services Based Management Architecture | SA WG5 | - | - | - | - | TM_SBMA | This was Block approved in CC#3 | Approved | |||
16.5 | SP-200754 | CR PACK | Rel-16 CRs on Management Aspects of 5G Service-Level Agreement | SA WG5 | - | - | - | - | MA5SLA | This was Block approved in CC#3 | Approved | |||
6.9 | SP-200755 | DRAFT TR | Draft TR 28.809 'Study on enhancement of management data analytics' | SA WG5 | 28.809 | - | - | - | - | Rel-16 | FS_eMDAS | This was block noted in CC#3 | Noted | |
6.10 | SP-200756 | DRAFT TR | Draft TR 28.812 'Study on scenarios for Intent driven management services for mobile networks' | SA WG5 | 28.812 | - | - | - | - | Rel-17 | IDMS_MN | This was Block approved in CC#3 | Approved | |
6.10 | SP-200757 | DRAFT TS | Draft TS 28.309 'Management of Quality of Experience (QoE) measurement collection Integration Reference Point (IRP); Solution Set (SS) definitions' | SA WG5 | 28.309 | - | - | - | - | Rel-16 | QOED | This was Block approved in CC#3 | Approved | |
6.10 | SP-200758 | DRAFT TS | Draft TS 28.313 'Study on new aspects of Energy Efficiency (EE) for 5G' | SA WG5 | 28.313 | - | - | - | - | Rel-16 | SON_5G | This was Block approved in CC#3 | Approved | |
6.10 | SP-200759 | DRAFT TR | Draft TR 28.810 'Study on concept, requirements and solutions for levels of autonomous network' | SA WG5 | 28.810 | - | - | - | - | Rel-16 | FS_ANL | This was Block approved in CC#3 | Approved | |
6.10 | SP-200760 | DRAFT TS | Draft TS 28.201 'Network slice performance and analytics charging in the 5G System (5GS); Stage 2' | SA WG5 | 28.201 | - | - | - | - | Rel-16 | 5GS_NSPACH | This was Block approved in CC#3 | Approved | |
6.10 | SP-200761 | DRAFT TS | Draft TS 28.202 'Network slice management charging in the 5G System (5GS); Stage 2' | SA WG5 | 28.202 | - | - | - | - | Rel-16 | 5GS_NSMCH | This was Block approved in CC#3 | Approved | |
6.9 | SP-200762 | DRAFT TS | Draft TS 28.555 'Network policy management for 5G mobile networks; Stage 1' | SA WG5 | 28.555 | - | - | - | - | Rel-17 | NPM | Revised in SP-200820 | Revised | SP-200820 |
6.2 | SP-200763 | WID REVISED | Revised WID Self-Organizing Networks (SON) for 5G networks. | SA WG5 | - | - | - | - | Rel-16 | SON_5G | This was Block approved in CC#3 | Approved | ||
6.3 | SP-200764 | SID NEW | New SID on the access control for management service. | SA WG5 | - | - | - | - | Revised to SP-200853 | Revised | SP-200853 | |||
6.3 | SP-200765 | SID NEW | New SID on YANG PUSH. | SA WG5 | - | - | - | - | This was Block approved in CC#3 | Approved | ||||
6.5 | SP-200766 | SID NEW | New SID on network slice management enhancement to include security aspects. | SA WG5 | - | - | - | - | This was Block approved in CC#3. CC#4: WGs to avoid agreeing to multiple rapporteurs for WIDs and SIDs. | Approved | ||||
6.3 | SP-200767 | SID NEW | New SID on charging aspects of Enhanced Proximity-based Services in 5GC. | SA WG5 | - | - | - | - | This was Block approved in CC#3 | Approved | ||||
6.4 | SP-200768 | WID NEW | New WID on N40 Interface Enhancements to Support GERAN and UTRAN. | SA WG5 | - | - | - | - | Revised to SP-200854 | Revised | SP-200854 | |||
6.4 | SP-200769 | WID NEW | New work item on charging enhancement for URLLC. | SA WG5 | - | - | - | - | This was Block approved in CC#3 | Approved | ||||
6.2 | SP-200770 | WID REVISED | Revised WID on Discovery of management services in 5G. | SA WG5 | - | - | - | - | Rel-16 | 5GDMS | This was Block approved in CC#3 | Approved | ||
6.3 | SP-200771 | SID NEW | Study on charging aspects of 5GS CIoT. | SA WG5 | - | - | - | - | This was Block approved in CC#3 | Approved | ||||
6.4 | SP-200772 | CR PACK | Rel-17 CRs on Mission critical security enhancements phase 2 | SA WG3 | - | - | - | - | DUMMY | This was Block approved in CC#3 | Approved | |||
15 | SP-200773 | CR PACK | Rel-15 CRs on Security aspects of 5G System - Phase 1 Batch 2 | SA WG3 | - | - | - | - | 5GS_Ph1-SEC | This was Block approved in CC#3 | Approved | |||
2.2 | SP-200774 | DISCUSSION | Discussion on the WI MINT | LG Electronics | - | - | - | - | Rel-17 | MINT | Noted | Noted | ||
2.2 | SP-200775 | LS OUT | [DRAFT] Reply LS on the stage 2 aspects of MINT | LG Electronics | - | - | - | - | Rel-17 | MINT | Response to SP-200654. CC#1: A revision will be provided based on the comments received. SP 200775_rev3 was approved. (This will be cleaned up and revised into a new TD number by MCC). Revised to SP-200880. | Revised | SP-200880 | |
20.3 | SP-200776 | WI SUMMARY | Work Item Summary for 5G_eSBA | China Mobile | - | - | - | - | Rel-16 | 5G_eSBA | This was Block endorsed in CC#3 | Endorsed | ||
20.3 | SP-200777 | WI SUMMARY | Work Item Summary for Rel-16 UDICOM | Nokia Korea | 21.916 | - | - | - | - | Rel-16 | UDICOM | This was Block endorsed in CC#3 | Endorsed | |
4.1 | SP-200778 | REPORT | SA WG1 Report to TSG SA#89e | SA WG1 Chairman | - | - | - | - | The SA WG1 Chairman presented rev1 of the report. Noted | Noted | ||||
4.7 | SP-200779 | LS In | LS from TSG RAN ITU AH: Draft Letter to ITU - Response LS on 3GPP's activities related to WRC-19 Resolutions | TSG RAN ITU AH | - | - | - | - | For 3GPP review: in: 3GPP TSG RAN feedback LS before: September 17, 2020 To: 3GPP PCG, CC: TSG SA. This was block noted at CC#2 | Noted | ||||
4.7 | SP-200780 | LS In | LS from TSG RAN ITU AH: DRAFT LTI - answer to ITU-R WP5A LS on CONNECTED AUTOMATED VEHICLES (CAV) | TSG RAN ITU AH | - | - | - | - | For 3GPP review: in: 3GPP TSG RAN feedback LS before: September 17, 2020 to: 3GPP TSG SA in: 3GPP TSG SA feedback LS before: September 18, 2020 to: 3GPP PCG. This was block noted at CC#2 | Noted | ||||
4.7 | SP-200781 | LS In | LS from TSG RAN ITU AH: DRAFT LTI - answer to ITU-R WP5D LS on DEVEOPMENT OF DRAFT NEW RPORT ITU-R.M[IMT.C-V2X] - APPLICATION OF THE TERRESTRIAL COMPONENT OF IMT FOR CELLULAR-V2X | TSG RAN ITU AH | - | - | - | - | For 3GPP review: in: 3GPP TSG RAN feedback LS before: September 17, 2020 to: 3GPP TSG SA in: 3GPP TSG SA feedback LS before: September 18, 2020 to: 3GPP PCG. This was block noted at CC#2 | Noted | ||||
4.7 | SP-200782 | LS In | LS from TSG RAN ITU AH: Draft Letter to ITU in reply to ITU_R_WP5D_TEMP_39 = RP-200037 on update submission for LTE-Advanced towards Revision 5 of Recommendation ITU-R M.2012 | TSG RAN ITU AH | - | - | - | - | For 3GPP review: in: 3GPP TSG RAN feedback LS before: September 17, 2020 to: 3GPP SA in: 3GPP TSG SA feedback LS before: September 18, 2020 to: 3GPP PCG. This was block noted at CC#2 | Noted | ||||
4.7 | SP-200783 | LS In | LS from TSG RAN ITU AH: Draft Letter to ITU in answer to LS to RIT/SRIT Proponents on the completion and conclusions of steps 5 to 7 of the IMT-2020 process for the first release of new Recommendation ITU-R M.[IMT-2020.SPECS] | TSG RAN ITU AH | - | - | - | - | For 3GPP review: in: 3GPP TSG RAN feedback LS before: September 17, 2020 to: 3GPP SA in: 3GPP TSG SA feedback LS before: September 18, 2020 to: 3GPP PCG. This was block noted at CC#2 | Noted | ||||
16.1 | SP-200784 | CR PACK | Stage 1 CRs on cyberCAV | SA WG1 | - | - | - | - | CC#3: 22.104 CR0054r1 and 22.261 CR0464 removed from the pack for further discussion (postponed). The other CRs in this CR Pack were approved. (This CR Pack was partially approved). | Partially approved | ||||
16.1 | SP-200785 | CR PACK | Stage 1 CRs on REAR | SA WG1 | - | - | - | - | This was Block approved in CC#3 | Approved | ||||
16.1 | SP-200786 | CR PACK | Stage 1 CRs on MARCOM | SA WG1 | - | - | - | - | This was Block approved in CC#3 | Approved | ||||
16.1 | SP-200787 | CR PACK | Stage 1 CRs on 5GSAT | SA WG1 | - | - | - | - | This was Block approved in CC#3 | Approved | ||||
16.1 | SP-200788 | CR PACK | Stage 1 CRs on UIA | SA WG1 | - | - | - | - | This was Block approved in CC#3 | Approved | ||||
16.1 | SP-200789 | CR PACK | Stage 1 CRs on TEI16 | SA WG1 | - | - | - | - | This was Block approved in CC#3 | Approved | ||||
16.1 | SP-200790 | CR PACK | Stage 1 CRs on eCAV | SA WG1 | - | - | - | - | CC#4: 22.261 CR0462R2 revised in SP-200869. 22.104 0053r1 and 22.261 0465r1 were postponed. The other CRs in this CR pack were approved | Partially approved | ||||
16.1 | SP-200791 | CR PACK | Stage 1 CRs on ID_UAS | SA WG1 | - | - | - | - | CC#3: SP-200791_Rev1 was approved. (To be revised by MCC to provide a new TD number). Revised to SP-200881. | Revised | SP-200881 | |||
16.1 | SP-200792 | CR PACK | Stage 1 CRs on AVPROD | SA WG1 | - | - | - | - | This was Block approved in CC#3 | Approved | ||||
16.1 | SP-200793 | CR PACK | Stage 1 CRs FS_FRMCS3 | SA WG1 | - | - | - | - | CC#3: SP-200793_Rev1 was approved. (To be revised by MCC to provide a new TD number). Revised to SP-200882. | Revised | SP-200882 | |||
16.1 | SP-200794 | CR PACK | Stage 1 CRs on TEI17 | SA WG1 | - | - | - | - | This was Block approved in CC#3 | Approved | ||||
3.4 | SP-200795 | DISCUSSION | On 5G GUTI reallocation for CIoT | Qualcomm Incorporated | - | - | - | - | Rel-16 | 5G_CIoT | Noted | Noted | ||
3.4 | SP-200796 | LS OUT | [DRAFT] LS On 5G GUTI reallocation for CIoT | Qualcomm Korea | - | - | - | - | Rel-16 | 5G_CIoT | CC#1: This LS was left for further consideration over e-mail. CC#3: This was left for further off-line discussion. CC#4: SP-200796_Rev1 was approved. Revised to SP-200883. | Revised | SP-200883 | |
6.7 | SP-200797 | WID NEW | New WID on Subscriber-aware Northbound API access (SNA). | SA WG1 (from S1-203296) | - | - | - | - | Rel-18 | This was Block approved in CC#3 | Approved | |||
6.6 | SP-200798 | SID NEW | New SID: Study on vehicle-mounted relays (FS_VMR). | SA WG1 | - | - | - | - | CC#3: China Mobile withdrew their objection. Approved | Approved | ||||
6.6 | SP-200799 | SID NEW | New SID: Study on 5G Networks Providing Access to Localized Services (FS_PALS). | SA WG1 | - | - | - | - | Rel-18 | CC#3: China Mobile withdrew their objection. Approved | Approved | |||
7.3 | SP-200800 | DISCUSSION | On Release 17 Schedule | Qualcomm Incorporated | - | - | - | - | Rel-17 | Noted | Noted | |||
20.3 | SP-200801 | WI SUMMARY | Summary for Work Item on 'Removal of H.263 and MPEG-4 Visual from 3GPP Services' | Qualcomm Incorporated | - | - | - | - | Rel-16 | RM_H263_MP4V | This was Block endorsed in CC#3 | Endorsed | ||
16.2 | SP-200802 | CR | 23.501 CR2383R2 (Rel-16, 'F'): Signalling of UE Radio Capability ID in Registration procedure | Qualcomm Incorporated | 23.501 | 2383 | 2 | F | 16.5.1 | Rel-16 | RACS | Revision of S2-2006493 (23.501 CR2383R1) in CR Pack SP-200685. CC#1: Vodafone supported this CR. This CR was approved. This CR was agreed | Approved | |
20.5 | SP-200803 | REPORT | Support Team report | MCC | - | - | - | - | CC#4: Noted | Noted | ||||
16.4 | SP-200804 | CR PACK | CRs to RM_H263_MP4V (postponed from SA#88-e) | SA WG4 | - | - | - | - | Rel-16 | RM_H263_MP4V | These CRs were postponed from SA#88-e. This was Block approved in CC#3 | Approved | ||
4.5 | SP-200805 | REPORT | SA WG5 Status Report to SA#89-e | SA WG5 Chairman | - | - | - | - | Noted | Noted | ||||
15 | SP-200806 | CR PACK | Rel-15 CRs on Lawful Interception | SA WG3-LI | - | - | - | - | Rel-15 | LI15 | This was Block approved in CC#3 | Approved | ||
16.3 | SP-200807 | CR PACK | Rel-16 CRs on Lawful Interception | SA WG3-LI | - | - | - | - | Rel-16 | LI16 | This was Block approved in CC#3 | Approved | ||
20.3 | SP-200808 | WI SUMMARY | Work Item Summary for Rel-16 eIMS5G_SBA | T-Mobile USA Inc. | - | - | - | - | Rel-16 | TEI16 | This was Block endorsed in CC#3 | Endorsed | ||
2.2 | SP-200809 | DISCUSSION | Discussion on support for broadcast in Rel-17 MBS | Huawei, HiSilicon | - | - | - | - | Rel-17 | FS_5MBS | Noted | Noted | ||
2.2 | SP-200810 | LS OUT | [DRAFT] Reply LS on RAN impact of FS_5MBS Study | Huawei [SA] | - | - | - | - | Rel-17 | FS_5MBS | Response to SP-200652. SP 200810_Rev2 was approved. (To be revised into a new TD number by MCC). Revised to SP-200884. | Revised | SP-200884 | |
7.3 | SP-200811 | DISCUSSION | Discussion on Rel-17 Schedule | Huawei, HiSilicon | - | - | - | - | Rel-17 | Noted | Noted | |||
6.3 | SP-200812 | SID NEW | New Study on User Consent for 3GPP services | Huawei, Hisilicon, China Unicom, CAICT, CATT | - | - | - | - | Rel-17 | CC#1: SP 200812_r01 was approved (to be revised by MCC). Revised to SP-200885. | Revised | SP-200885 | ||
16.5 | SP-200813 | CR PACK | REl-16 CRs on TEI batch 2 | SA WG5 | - | - | - | - | TEI16 | This was Block approved in CC#3 | Approved | |||
2.2 | SP-200814 | DISCUSSION | The Importance of Maintaining Broadcast Services in Rel-17 NR MBS | CBN, ABS, ABP, China Telecom, China Unicom, IRT, Reliance Jio | - | - | - | - | Rel-17 | NR_MBS | Noted | Noted | ||
7.1 | SP-200815 | DISCUSSION | 3GPP Meeting Planning H1/2021 | TSG SA Chairman | - | - | - | - | Noted | Noted | ||||
16.5 | SP-200816 | CR PACK | Rel-16 CRs on Charging Aspects for 5WWC | SA WG5 | - | - | - | - | 5WWC | This was Block approved in CC#3 | Approved | |||
16.5 | SP-200817 | CR PACK | REl-16 CRs on Nchf Online and Offline charging services | SA WG5 | - | - | - | - | OFSBI_CH | This was Block approved in CC#3 | Approved | |||
18.1 | SP-200818 | CR PACK | Stage 1 CRs on SNA | SA WG1 | - | - | - | - | Rel-18 | This was Block approved in CC#3 | Approved | |||
7.1 | SP-200819 | DISCUSSION | Thoughts about enumerating SA WG1 requirements | Siemens, Philips | - | - | - | - | Rel-18 | CC#3: TSG SA Chairman will start a moderated TSG SA e-mail discussion on the enumeration issue until the next TSG SA meeting. This was then noted. | Noted | |||
6.9 | SP-200820 | DRAFT TS | Draft TS 28.555 'Network policy management for 5G mobile networks; Stage 1' | SA WG5 | 28.555 | - | - | - | - | Rel-17 | NPM | Revision of SP-200762. Noted | Noted | |
6.6 | SP-200821 | Discussion | Study on Support _x00B_for Service Function Chaining in 5G System (FS_SFCin5GS) | Intel, Deutsche Telekom AG, Tencent, Telefónica, Affirmed Network, AT&T, Sandvine, Convida Wireless, InterDigital, KPN, Verizon UK Ltd., KDDI, Vodafone, Telecom Italia, Cisco, b<>com, Spirent Communications | - | - | - | - | Rel-18 | Noted | Noted | |||
6.6 | SP-200822 | SID NEW | New SID on Study on Support for Service Function Chaining in 5G System. | Intel Corporation, Deutsche Telekom AG, Tencent, Telefónica, Affirmed Network, AT&T, Sandvine, Convida Wireless, InterDigital, KPN, Verizon UK Ltd., KDDI, Vodafone, Telecom Italia, Cisco, b<>com, Spirent Communications | - | - | - | - | Rel-18 | CC#1: This was left for further consideration over e-mail. CC#3: This issue will be handled further in SA WG1. Saso will provide a WID proposal for discussion on Friday. CC#4: Postoned | Postponed | |||
20.1 | SP-200823 | WORK PLAN | Work Plan review at TSG#89 | Work Plan Coordinator (MCC) | - | - | - | - | CC#4: SP-200823_Rev2 was provided to take comments into account. Noted | Noted | ||||
20.3 | SP-200824 | DRAFT TR | TR 21.916 v.0.6.0 on Rel-16 Summary | Work Plan Coordinator (MCC) | 21.916 | - | - | - | - | Rel-16 | TEI16 | This was Block noted in CC#3 | Noted | |
4.6 | SP-200825 | REPORT | SA WG6 status report to TSG SA#89 | SA WG6 Chairman | - | - | - | - | Noted | Noted | ||||
6.10 | SP-200826 | DRAFT TS | Presentation of TS 23.180 v2.0.0 for approval | SA WG6 | 23.180 | - | - | - | - | Rel-17 | MCIOPS | This was Block approved in CC#3 | Approved | |
6.10 | SP-200827 | DRAFT TR | Presentation of TR 23.764 v2.0.0 for approval | SA WG6 | 23.764 | - | - | - | - | Rel-17 | FS_eV2XAPP | This was Block approved in CC#3 | Approved | |
6.9 | SP-200828 | DRAFT TS | Presentation of TS 23.558 v1.0.0 for information | SA WG6 | 23.558 | - | - | - | - | Rel-17 | EDGEAPP | This was block noted in CC#3 | Noted | |
6.9 | SP-200829 | DRAFT TR | Presentation of TR 23.745 v1.0.0 for information | SA WG6 | 23.745 | - | - | - | - | Rel-16 | FS_FFAPP | This was block noted in CC#3 | Noted | |
6.9 | SP-200830 | DRAFT TR | Presentation of TR 23.700-24 v1.0.0 for information | SA WG6 | 23.700-24 | - | - | - | - | Rel-17 | FS_5GMARCH | This was block noted in CC#3 | Noted | |
6.4 | SP-200831 | WID NEW | New WID for enhanced application layer support for V2X services. | SA WG6 | - | - | - | - | This was Block approved in CC#3 | Approved | ||||
6.4 | SP-200832 | WID NEW | New WID Application Architecture for MSGin5G Service. | SA WG6 | - | - | - | - | This was Block approved in CC#3 | Approved | ||||
6.4 | SP-200833 | WID NEW | New WID Mission Critical Services over 5GS. | SA WG6 | - | - | - | - | This was Block approved in CC#3 | Approved | ||||
6.5 | SP-200834 | WID REVISED | Revised WID on Architecture for enabling Edge Applications . | SA WG6 | - | - | - | - | Rel-17 | EDGEAPP | CC#2: SP 200834_rev1 was approved. Revised to SP-200886. | Revised | SP-200886 | |
6.5 | SP-200835 | SID REVISED | Revised SID Study on support of the 5GMSG Service. | SA WG6 | - | - | - | - | Rel-17 | FS_5GMARCH | This was Block approved in CC#3 | Approved | ||
6.5 | SP-200836 | SID REVISED | Revised SID Study on application layer support for . Factories of the Future in 5G network . | SA WG6 | - | - | - | - | Rel-17 | FS_FFAPP | This was Block approved in CC#3 | Approved | ||
6.5 | SP-200837 | SID REVISED | Revised SID Study on Mission Critical services support over 5G System. | SA WG6 | - | - | - | - | Rel-17 | FS_MCOver5GS | This was Block approved in CC#3 | Approved | ||
16.6 | SP-200838 | CR PACK | Rel-16 CRs to TS 23.283 for eMCCI | SA WG6 | - | - | - | - | eMCCI | This was Block approved in CC#3 | Approved | |||
16.6 | SP-200839 | CR PACK | Rel-16 CRs to TS 23.282 for eMCData2 | SA WG6 | - | - | - | - | eMCData2 | This was Block approved in CC#3 | Approved | |||
16.6 | SP-200840 | CR PACK | Rel-16 CRs to TS 23.222 for eCAPIF | SA WG6 | - | - | - | - | eCAPIF | This was Block approved in CC#3 | Approved | |||
16.6 | SP-200841 | CR PACK | Rel-16 CRs to TS 23.434 for SEAL | SA WG6 | - | - | - | - | SEAL | This was Block approved in CC#3 | Approved | |||
16.6 | SP-200842 | CR PACK | Rel-16 CRs to TS 23.286 for V2XAPP | SA WG6 | - | - | - | - | V2XAPP | This was Block approved in CC#3 | Approved | |||
17.6 | SP-200843 | CR PACK | Rel-17 CRs to TS 23.280, TS 23.281, TS 23.282 and TS 23.379 for eMONASTERY2 | SA WG6 | - | - | - | - | eMONASTERY2 | This was Block approved in CC#3 | Approved | |||
17.6 | SP-200844 | CR PACK | Rel-17 CRs to TS 23.280 and TS 23.379 for enh3MCPTT | SA WG6 | - | - | - | - | enh3MCPTT | This was Block approved in CC#3 | Approved | |||
17.6 | SP-200845 | CR PACK | Rel-17 CRs to TS 23.282 for eMCData3 | SA WG6 | - | - | - | - | eMCData3 | This was Block approved in CC#3 | Approved | |||
17.6 | SP-200846 | CR PACK | Rel-17 CRs to TS 23.281 and TS 23.283 for TEI17 | SA WG6 | - | - | - | - | TEI17 | This was Block approved in CC#3 | Approved | |||
17.6 | SP-200847 | CR PACK | Rel-17 CR to TR 23.744 for FS_enhMCLoc | SA WG6 | - | - | - | - | FS_enhMCLoc | This was Block approved in CC#3 | Approved | |||
20.3 | SP-200848 | WI SUMMARY | Work item Summary for 5GMS3 | Sony (Rapporteur) | - | - | - | - | Rel-16 | 5GMS3 | This was Block endorsed in CC#3 | Endorsed | ||
20.3 | SP-200849 | WI SUMMARY | Work item Summary for Enhancement of performance assurance for 5G | Intel (Rapporteur) | - | - | - | - | Rel-16 | 5G_SLICE_ePA | This was Block endorsed in CC#3 | Endorsed | ||
20.1 | SP-200850 | DISCUSSION | A Feature is like a worm: don't cut it | 3GPP Work Plan Coordinator | - | - | - | - | CC#3: Postponed | Postponed | ||||
20.3 | SP-200851 | WI SUMMARY | Work Item Summary for Rel-16 eCAPIF | Samsung | - | - | - | - | Rel-16 | eCAPIF | This was Block endorsed in CC#3 | Endorsed | ||
20.3 | SP-200852 | WI SUMMARY | Work Item Summary for Rel-16 SEAL | Samsung | - | - | - | - | Rel-16 | SEAL | This was Block endorsed in CC#3 | Endorsed | ||
6.3 | SP-200853 | SID NEW | New SID on the access control for management service. | SA WG5 | - | - | - | - | Revision of SP-200764. Change of 'Other related Work Items and dependencies' as suggested by the Work Plan Manager. This was Block approved in CC#3 | Approved | ||||
6.4 | SP-200854 | WID NEW | New WID on N40 Interface Enhancements to Support GERAN and UTRAN. | SA WG5 | - | - | - | - | Revision of SP-200768. Alignment of acronym with SA WG2's acronym TEI17_NIESGU. This was Block approved in CC#3 | Approved | ||||
1.4 | SP-200855 | AGENDA | SA#89-e GoToMeetings Agenda | TSG SA Chairman | - | - | - | - | Noted | Noted | ||||
2.2 | SP-200856 | LS OUT | [DRAFT] Reply to LS on Invitation to update the information in the IMT2020 roadmap | Samsung | - | - | - | - | Created at meeting. Response to SP-200638. MCC will need to revise to remove 'draft'. Revised to SP-200887. | Revised | SP-200887 | |||
16.3 | SP-200857 | CR | 33.310 CR0112 (Rel-16, 'F'): Making NF instance id in SBA certificate profile mandatory to support | Nokia | 33.310 | 0112 | - | F | 16.4.0 | Rel-16 | 5G_eSBA | Incorrect TS was specified in the SA WG3 TD request. New CR allocated at TSG SA#89-e. CC#3: This CR was approved. | Approved | |
4.8 | SP-200858 | REPORT | Status report of TSG CT#89-e | TSG CT Chairman | - | - | - | - | Noted | Noted | ||||
4.8 | SP-200859 | REPORT | Draft report of TSG CT#89-e | TSG CT Secretary (MCC) | - | - | - | - | Noted | Noted | ||||
4.8 | SP-200860 | REPORT | IETF Status report | TSG CT Chairman | - | - | - | - | Noted | Noted | ||||
4.8 | SP-200861 | LS In | LS from TSG CT: LS on information of stage 3 aspects for AKMA | TSG CT | - | - | - | - | Rel-17 | AKMA-CT | SA WG3 and SA WG1 will work on CRs that will propose to shift AKMA SA WG3 to Rel-17. Additional changes for separate discussions. Proposal to change BB to Feature for discussion in SA WG3. Noted | Noted | ||
7.3 | SP-200862 | LS OUT | [DRAFT] LS on R17 schedule | TSG SA | - | - | - | - | CC#3: A corrected version was provided in the revisions folder as SP-200862_rev1. CC#4: SP-200862_Rev2 approved. Revised to SP-200888. | Revised | SP-200888 | |||
4.7 | SP-200863 | LS In | LS from TSG RAN: Draft Letter to ITU - Response LS on 3GPP’s activities related to WRC-19 Resolutions | TSG RAN | - | - | - | - | To be noted. CC#4: This LS was noted. | Noted | ||||
4.7 | SP-200864 | LS In | LS from TSG RAN: DRAFT LTI - answer to ITU-R WP5D LS on DEVEOPMENT OF DRAFT NEW RPORT ITU-R.M[IMT.C-V2X] – APPLICATION OF THE TERRESTRIAL COMPONENT OF IMT FOR CELLULAR-V2X | TSG RAN | - | - | - | - | For endorsement and creating an LS to the PCG. CC#4: This was endorsed and a LS OUT to PCG was created by MCC in SP-200873 | Endorsed | ||||
4.7 | SP-200865 | LS In | LS from TSG RAN: Draft Letter to ITU in reply to ITU_R_WP5D_TEMP_39 = RP-200037 on update submission for LTE-Advanced towards Revision 5 of Recommendation ITU-R M.2012 | TSG RAN | - | - | - | - | For endorsement and creating an LS to the PCG. CC#4: This was endorsed and a LS OUT to PCG was created by MCC in SP-200874 | Endorsed | ||||
4.7 | SP-200866 | LS In | LS from TSG RAN: DRAFT LTI - answer to ITU-R WP5A LS on CONNECTED AUTOMATED VEHICLES (CAV) | TSG RAN | - | - | - | - | For endorsement and creating an LS to the PCG. CC#4: This was endorsed and a LS OUT to PCG was created by MCC in SP-200875 | Endorsed | ||||
4.7 | SP-200867 | LS In | LS from TSG RAN: Draft Letter to ITU in answer to LS to RIT/SRIT Proponents on the completion and conclusions of steps 5 to 7 of the IMT-2020 process for the first release of new Recommendation ITU-R M.[IMT-2020.SPECS] | TSG RAN | - | - | - | - | For endorsement and creating an LS to the PCG. CC#4: This was endorsed and a LS OUT to PCG was created by MCC in SP-200876 | Endorsed | ||||
16 | SP-200868 | LS In | LS from TSG RAN: LS on Relaxation of mini-WID requirement for Cat.B/C TEI CRs | TSG RAN | - | - | - | - | Rel-16 | TEI16 | Attached CR is the same change as in SP-200657. CC#4: This LS was postponed. | Postponed | ||
16.1 | SP-200869 | CR | 22.261 CR0462R3 (Rel-17, 'D'): Quality improvement of TS 22.261 (R17) – editorial modifications | Siemens | 22.261 | 0462 | 3 | D | 17.3.0 | Rel-17 | eCAV | Revision of 22.261 CR0462R2 from CR Pack SP-200790. CC#4: SP-200869_Rev3 was approved. Revised to SP-200889. | Revised | SP-200889 |
3.4 | SP-200870 | DISCUSSION | Presentation on 5G GUTI reallocation | Qualcomm Incorporated | - | - | - | - | Endorsed. A working Agreement will be created based on this proposal | Endorsed | ||||
2.2 | SP-200871 | LS In | LS from TSG RAN: Reply LS on RAN impact of FS_5MBS Study | TSG RAN | - | - | - | - | Rel-17 | FS_5MBS, NR_MBS-Core | Related to incoming LS in SP-200652. CC#4: This LS was noted. | Noted | ||
20.3 | SP-200872 | WI SUMMARY | Work Item Summary for QOED | Ericsson | - | - | - | - | Rel-16 | QOED | Late submission. CC#4: This WI Summary was endorsed. | Endorsed | ||
4.7 | SP-200873 | LS OUT | LS to PCG: DRAFT LTI - answer to ITU-R WP5D LS on DEVEOPMENT OF DRAFT NEW RPORT ITU-R.M[IMT.C-V2X] – APPLICATION OF THE TERRESTRIAL COMPONENT OF IMT FOR CELLULAR-V2X | TSG SA | - | - | - | - | Approved at CC#4 | Approved | ||||
4.7 | SP-200874 | LS OUT | LS to PCG: Draft Letter to ITU in reply to ITU_R_WP5D_TEMP_39 = RP-200037 on update submission for LTE-Advanced towards Revision 5 of Recommendation ITU-R M.2012 | TSG SA | - | - | - | - | Approved at CC#4 | Approved | ||||
4.7 | SP-200875 | LS OUT | LS to PCG: DRAFT LTI - answer to ITU-R WP5A LS on CONNECTED AUTOMATED VEHICLES (CAV) | TSG SA | - | - | - | - | Approved at CC#4 | Approved | ||||
4.7 | SP-200876 | LS OUT | LS to PCG: Draft Letter to ITU in answer to LS to RIT/SRIT Proponents on the completion and conclusions of steps 5 to 7 of the IMT-2020 process for the first release of new Recommendation ITU-R M.[IMT-2020.SPECS] | TSG SA | - | - | - | - | Approved at CC#4 | Approved | ||||
2.2 | SP-200877 | LS OUT | Reply LS on request for information from IALA | TSG SA | - | - | - | - | MARCOM | Revision of SP-200655. Approved | Approved | |||
6.3 | SP-200878 | SID NEW | New SID on security aspects of the MSGin5G Service | SA WG3 | - | - | - | - | Revision of SP-200717_Rev1. Approved | Approved | ||||
6.4 | SP-200879 | WID NEW | New WID on mission critical security enhancements phase 2 | SA WG3 | - | - | - | - | Revision of SP-200718_Rev2. Approved | Approved | ||||
2.2 | SP-200880 | LS OUT | Reply LS on the stage 2 aspects of MINT | TSG SA | - | - | - | - | Rel-17 | MINT | Revision of SP-200775_Rev3. Approved | Approved | ||
16.1 | SP-200881 | CR | 22.125 CR0028R6 (Rel-17, 'F'): Stage 1 CRs on ID_UAS | SA WG1 | 22.125 | 0028 | 6 | F | 17.1.0 | Rel-17 | EAV | Revision of 22.125 CR0028R5 in SP-200791_Rev1. Approved | Approved | |
16.1 | SP-200882 | CR | 22.889 CR0169R3 (Rel-17, 'F'): Stage 1 CRs FS_FRMCS3 | SA WG1 | 22.889 | 0169 | 3 | F | 17.2.0 | Rel-17 | FS_FRMCS3 | Revision of 22.889 CR0169R2 in SP-200793_Rev1. Approved | Approved | |
3.4 | SP-200883 | LS OUT | LS on 5G GUTI re-allocation | TSG SA | - | - | - | - | Rel-16 | 5G_CIoT | Revision of SP-200796_Rev1. Approved | Approved | ||
2.2 | SP-200884 | LS OUT | Reply LS on RAN impact of FS_5MBS Study | TSG SA | - | - | - | - | Rel-17 | FS_5MBS | Revision of SP-200810_Rev2. Approved | Approved | ||
6.3 | SP-200885 | SID NEW | New Study on User Consent for 3GPP services | Huawei, HiSilicon, China Unicom, CAICT, CATT | - | - | - | - | Rel-17 | Revision of SP-200812_Rev1. Approved | Approved | |||
6.5 | SP-200886 | WID REVISED | Revised WID on Architecture for enabling Edge Applications . | SA WG6 | - | - | - | - | Rel-17 | EDGEAPP | Revision of SP-200834_Rev1. Approved | Approved | ||
2.2 | SP-200887 | LS OUT | Reply to LS on Invitation to update the information in the IMT2020 roadmap | TSG SA | - | - | - | - | Revision of SP-200856. Approved | Approved | ||||
7.3 | SP-200888 | LS OUT | LS on Rel-17 schedule | TSG SA | - | - | - | - | Revision of SP-200862_Rev2. Approved | Approved | ||||
16.1 | SP-200889 | CR | 22.261 CR0462R4 (Rel-17, 'D'): Quality improvement of TS 22.261 (R17) – editorial modifications | Siemens | 22.261 | 0462 | 4 | D | 17.3.0 | Rel-17 | eCAV | Revision of SP-200869. Approved | Approved | |
4.7 | SP-200890 | REPORT | Chairmans Report of TSG RAN#89-e | TSG RAN Chairman | - | - | - | - | CC#5: Noted | Noted |
B.2 List of documents by Agenda Item
AI | TDoc | Type | Title | Source | Specification | CRNo | CRrev | Cat | Ver | Rel | WI | Comment | Decision | Revised to TD |
1.4 | S2-200632 | AGENDA | Agenda & Procedures & Time Schedule for TSG SA#88-e | TSG SA Chairman | - | - | - | - | Approved | Approved | ||||
1.4 | S2-200855 | AGENDA | SA#89-e GoToMeetings Agenda | TSG SA Chairman | - | - | - | - | Noted | Noted | ||||
1.5 | S2-200633 | REPORT | Draft report of TSG SA meeting #88E | TSG SA Secretary | - | - | - | - | Approved | Approved | ||||
2.1 | S2-200635 | LS In | LS from ITU-R WP 5D: LIAISON STATEMENT TO RIT/SRIT PROPONENTS ON THE COMPLETION AND CONCLUSIONS OF STEPS 5 TO 7 OF THE IMT-2020 PROCESS FOR THE FIRST RELEASE OF NEW RECOMMENDATION ITU-R M.[IMT-2020.SPECS] | ITU-R WP 5D | - | - | - | - | CC#1: This was block noted | Noted | ||||
2.1 | S2-200636 | LS In | LS from ITU-R WP5D: LIAISON STATEMENT TO TRANSPOSING ORGANIZATIONS ON THE COMPLETION OF STEP 8 OF IMT-2020 PROCESS FOR THE FIRST RELEASE OF NEW RECOMMENDATION ITU-R M.[IMT-2020.SPECS] | ITU-R WP5D | - | - | - | - | CC#1: This was block noted | Noted | ||||
2.1 | S2-200637 | LS In | LS from ETSI ISG E4P: Request for information exchange | ETSI ISG E4P | - | - | - | - | CC#1: This was block noted | Noted | ||||
2.1 | S2-200639 | LS In | LS from TM Forum Autonomous Networks: Introduction of TM Forum Autonomous Network project and Coordination Proposal | TM Forum Autonomous Networks | - | - | - | - | CC#1: This was block noted | Noted | ||||
2.1 | S2-200640 | LS In | LS from IETF: Re: LS on need for Multi-Path QUIC for ATSSS | IETF | - | - | - | - | CC#1: This was block noted | Noted | ||||
2.1 | S2-200641 | LS In | LS from IETF DRIP: Drone Remote ID Protocol Working Group (DRIP) | IETF DRIP | - | - | - | - | CC#1: This was block noted | Noted | ||||
2.1 | S2-200642 | LS In | LS from ITU-R WP5A: LIAISON STATEMENT TO EXTERNAL ORGANIZATIONS ON ITS Connected Automated Vehicles (CAV) | ITU-R WP5A | - | - | - | - | CC#1: This was block noted | Noted | ||||
2.1 | S2-200643 | LS In | LS from TSG RAN: Reply LS to RP-200030 on relevant 3GPP Specs for PC5 Sidelink | TSG RAN | - | - | - | - | CC#1: This was block noted | Noted | ||||
2.1 | S2-200644 | LS In | LS from TSG RAN: Reply LS to GSMA_5GSI_28_Doc003 = RP-193053 on 5G indicator enhancement | TSG RAN | - | - | - | - | CC#1: This was block noted | Noted | ||||
2.1 | S2-200645 | LS In | LS from ITU-T SG13: LS/o on information about consent of Machine Learning related ITU-T Recommendation Y.3176 | ITU-T SG13 | - | - | - | - | CC#1: This was block noted | Noted | ||||
2.1 | S2-200649 | LS In | LS from CT WG4: LS on AUSF/UDM discovery based on SUCI information | CT WG4 | - | - | - | - | Rel-17 | SBIProtoc17 | CC#1: This was block noted | Noted | ||
2.1 | S2-200653 | LS In | LS from SA WG5: LS reply to LS on M.resm-AI “Requirements for energy saving management of 5G RAN system with AI” | SA WG5 | - | - | - | - | Rel-17 | CC#1: This was block noted | Noted | |||
2.2 | S2-200652 | LS In | LS from SA WG2: LS on RAN impact of FS_5MBS Study | SA WG2 | - | - | - | - | Rel-17 | FS_5MBS, NR_MBS-Core | Response drafted in SP-200810. Final response in SP-200884 | Replied to | ||
2.2 | S2-200809 | DISCUSSION | Discussion on support for broadcast in Rel-17 MBS | Huawei, HiSilicon | - | - | - | - | Rel-17 | FS_5MBS | Noted | Noted | ||
2.2 | S2-200810 | LS OUT | [DRAFT] Reply LS on RAN impact of FS_5MBS Study | Huawei [SA] | - | - | - | - | Rel-17 | FS_5MBS | Response to SP-200652. SP 200810_Rev2 was approved. (To be revised into a new TD number by MCC). Revised to SP-200884. | Revised | S2-200884 | |
2.2 | S2-200884 | LS OUT | Reply LS on RAN impact of FS_5MBS Study | TSG SA | - | - | - | - | Rel-17 | FS_5MBS | Revision of SP-200810_Rev2. Approved | Approved | ||
2.2 | S2-200871 | LS In | LS from TSG RAN: Reply LS on RAN impact of FS_5MBS Study | TSG RAN | - | - | - | - | Rel-17 | FS_5MBS, NR_MBS-Core | Related to incoming LS in SP-200652. CC#4: This LS was noted. | Noted | ||
2.2 | S2-200634 | LS In | LS from IALA: Liaison Note to TSG SA - Request for information | IALA | - | - | - | - | Postponed SP-200310 from SA#88E. Response drafted in SP-200655. Final response in SP-200877 | Replied to | ||||
2.2 | S2-200655 | LS OUT | [DRAFT] Reply LS on request for information from IALA | SyncTechno Inc. | - | - | - | - | MARCOM | Response to SP-200634. MCC will need to revise to remove 'draft'. Revised to SP-200877. | Revised | S2-200877 | ||
2.2 | S2-200877 | LS OUT | Reply LS on request for information from IALA | TSG SA | - | - | - | - | MARCOM | Revision of SP-200655. Approved | Approved | |||
2.2 | S2-200654 | LS In | LS from CT WG1: LS on the stage 2 aspects of MINT | CT WG1 | - | - | - | - | Rel-17 | MINT | Response drafted in SP-200775. Final response in SP-200880 | Replied to | ||
2.2 | S2-200774 | DISCUSSION | Discussion on the WI MINT | LG Electronics | - | - | - | - | Rel-17 | MINT | Noted | Noted | ||
2.2 | S2-200775 | LS OUT | [DRAFT] Reply LS on the stage 2 aspects of MINT | LG Electronics | - | - | - | - | Rel-17 | MINT | Response to SP-200654. CC#1: A revision will be provided based on the comments received. SP 200775_rev3 was approved. (This will be cleaned up and revised into a new TD number by MCC). Revised to SP-200880. | Revised | S2-200880 | |
2.2 | S2-200880 | LS OUT | Reply LS on the stage 2 aspects of MINT | TSG SA | - | - | - | - | Rel-17 | MINT | Revision of SP-200775_Rev3. Approved | Approved | ||
2.2 | S2-200814 | DISCUSSION | The Importance of Maintaining Broadcast Services in Rel-17 NR MBS | CBN, ABS, ABP, China Telecom, China Unicom, IRT, Reliance Jio | - | - | - | - | Rel-17 | NR_MBS | Noted | Noted | ||
2.2 | S2-200638 | LS In | LS from ITU-T JCA-IMT2020: LS on Invitation to update the information in the IMT2020 roadmap | ITU-T JCA-IMT2020 | - | - | - | - | Response drafted in SP-200856. Final response in SP-200887 | Replied to | ||||
2.2 | S2-200856 | LS OUT | [DRAFT] Reply to LS on Invitation to update the information in the IMT2020 roadmap | Samsung | - | - | - | - | Created at meeting. Response to SP-200638. MCC will need to revise to remove 'draft'. Revised to SP-200887. | Revised | S2-200887 | |||
2.2 | S2-200887 | LS OUT | Reply to LS on Invitation to update the information in the IMT2020 roadmap | TSG SA | - | - | - | - | Revision of SP-200856. Approved | Approved | ||||
2.2 | S2-200646 | LS In | LS from TM Forum: TM Forum implementation experiences 3GPP NRM Models | TM Forum | - | - | - | - | CC#2: This was Block Noted | Noted | ||||
2.2 | S2-200647 | LS In | LS from SA WG2: LS on mandatory support of full rate user plane integrity protection for 5G | SA WG2 | - | - | - | - | Rel-16 | TEI16 | CC#2: This was Block Noted | Noted | ||
2.2 | S2-200648 | LS In | LS on mandatory support of full rate user plane integrity protection for 5G | CT WG1 | - | - | - | - | Rel-16 | TEI16 | CC#2: This was Block Noted | Noted | ||
2.2 | S2-200650 | LS In | LS from RAN WG2: Response LS to TSG SA on mandatory support of full rate user plane integrity protection for 5G | RAN WG2 | - | - | - | - | Rel-16 | CC#2: This was Block Noted | Noted | |||
2.2 | S2-200651 | LS In | LS from RAN WG3: Reply LS on mandatory support of full rate user plane integrity protection for 5G | RAN WG3 | - | - | - | - | Rel-16 | CC#2: This was Block Noted | Noted | |||
3.4 | S2-200795 | DISCUSSION | On 5G GUTI reallocation for CIoT | Qualcomm Incorporated | - | - | - | - | Rel-16 | 5G_CIoT | Noted | Noted | ||
3.4 | S2-200796 | LS OUT | [DRAFT] LS On 5G GUTI reallocation for CIoT | Qualcomm Korea | - | - | - | - | Rel-16 | 5G_CIoT | CC#1: This LS was left for further consideration over e-mail. CC#3: This was left for further off-line discussion. CC#4: SP-200796_Rev1 was approved. Revised to SP-200883. | Revised | S2-200883 | |
3.4 | S2-200883 | LS OUT | LS on 5G GUTI re-allocation | TSG SA | - | - | - | - | Rel-16 | 5G_CIoT | Revision of SP-200796_Rev1. Approved | Approved | ||
3.4 | S2-200870 | DISCUSSION | Presentation on 5G GUTI reallocation | Qualcomm Incorporated | - | - | - | - | Endorsed. A working Agreement will be created based on this proposal | Endorsed | ||||
4.1 | S2-200778 | REPORT | SA WG1 Report to TSG SA#89e | SA WG1 Chairman | - | - | - | - | The SA WG1 Chairman presented rev1 of the report. Noted | Noted | ||||
4.2 | S2-200670 | REPORT | SA WG2 Report to TSG SA | SA WG2 Chairman | - | - | - | - | Noted | Noted | ||||
4.3 | S2-200669 | REPORT | SA WG3 Status report | SA WG3 Chairman | - | - | - | - | Noted | Noted | ||||
4.4 | S2-200658 | REPORT | SA WG4 Chairman's Report | 3GPP SA4 | - | - | - | - | Noted | Noted | ||||
4.5 | S2-200805 | REPORT | SA WG5 Status Report to SA#89-e | SA WG5 Chairman | - | - | - | - | Noted | Noted | ||||
4.6 | S2-200825 | REPORT | SA WG6 status report to TSG SA#89 | SA WG6 Chairman | - | - | - | - | Noted | Noted | ||||
4.7 | S2-200863 | LS In | LS from TSG RAN: Draft Letter to ITU - Response LS on 3GPP’s activities related to WRC-19 Resolutions | TSG RAN | - | - | - | - | To be noted. CC#4: This LS was noted. | Noted | ||||
4.7 | S2-200866 | LS In | LS from TSG RAN: DRAFT LTI - answer to ITU-R WP5A LS on CONNECTED AUTOMATED VEHICLES (CAV) | TSG RAN | - | - | - | - | For endorsement and creating an LS to the PCG. CC#4: This was endorsed and a LS OUT to PCG was created by MCC in SP-200875 | Endorsed | ||||
4.7 | S2-200875 | LS OUT | LS to PCG: DRAFT LTI - answer to ITU-R WP5A LS on CONNECTED AUTOMATED VEHICLES (CAV) | TSG SA | - | - | - | - | Approved at CC#4 | Approved | ||||
4.7 | S2-200864 | LS In | LS from TSG RAN: DRAFT LTI - answer to ITU-R WP5D LS on DEVEOPMENT OF DRAFT NEW RPORT ITU-R.M[IMT.C-V2X] – APPLICATION OF THE TERRESTRIAL COMPONENT OF IMT FOR CELLULAR-V2X | TSG RAN | - | - | - | - | For endorsement and creating an LS to the PCG. CC#4: This was endorsed and a LS OUT to PCG was created by MCC in SP-200873 | Endorsed | ||||
4.7 | S2-200873 | LS OUT | LS to PCG: DRAFT LTI - answer to ITU-R WP5D LS on DEVEOPMENT OF DRAFT NEW RPORT ITU-R.M[IMT.C-V2X] – APPLICATION OF THE TERRESTRIAL COMPONENT OF IMT FOR CELLULAR-V2X | TSG SA | - | - | - | - | Approved at CC#4 | Approved | ||||
4.7 | S2-200865 | LS In | LS from TSG RAN: Draft Letter to ITU in reply to ITU_R_WP5D_TEMP_39 = RP-200037 on update submission for LTE-Advanced towards Revision 5 of Recommendation ITU-R M.2012 | TSG RAN | - | - | - | - | For endorsement and creating an LS to the PCG. CC#4: This was endorsed and a LS OUT to PCG was created by MCC in SP-200874 | Endorsed | ||||
4.7 | S2-200874 | LS OUT | LS to PCG: Draft Letter to ITU in reply to ITU_R_WP5D_TEMP_39 = RP-200037 on update submission for LTE-Advanced towards Revision 5 of Recommendation ITU-R M.2012 | TSG SA | - | - | - | - | Approved at CC#4 | Approved | ||||
4.7 | S2-200867 | LS In | LS from TSG RAN: Draft Letter to ITU in answer to LS to RIT/SRIT Proponents on the completion and conclusions of steps 5 to 7 of the IMT-2020 process for the first release of new Recommendation ITU-R M.[IMT-2020.SPECS] | TSG RAN | - | - | - | - | For endorsement and creating an LS to the PCG. CC#4: This was endorsed and a LS OUT to PCG was created by MCC in SP-200876 | Endorsed | ||||
4.7 | S2-200876 | LS OUT | LS to PCG: Draft Letter to ITU in answer to LS to RIT/SRIT Proponents on the completion and conclusions of steps 5 to 7 of the IMT-2020 process for the first release of new Recommendation ITU-R M.[IMT-2020.SPECS] | TSG SA | - | - | - | - | Approved at CC#4 | Approved | ||||
4.7 | S2-200779 | LS In | LS from TSG RAN ITU AH: Draft Letter to ITU - Response LS on 3GPP's activities related to WRC-19 Resolutions | TSG RAN ITU AH | - | - | - | - | For 3GPP review: in: 3GPP TSG RAN feedback LS before: September 17, 2020 To: 3GPP PCG, CC: TSG SA. This was block noted at CC#2 | Noted | ||||
4.7 | S2-200780 | LS In | LS from TSG RAN ITU AH: DRAFT LTI - answer to ITU-R WP5A LS on CONNECTED AUTOMATED VEHICLES (CAV) | TSG RAN ITU AH | - | - | - | - | For 3GPP review: in: 3GPP TSG RAN feedback LS before: September 17, 2020 to: 3GPP TSG SA in: 3GPP TSG SA feedback LS before: September 18, 2020 to: 3GPP PCG. This was block noted at CC#2 | Noted | ||||
4.7 | S2-200781 | LS In | LS from TSG RAN ITU AH: DRAFT LTI - answer to ITU-R WP5D LS on DEVEOPMENT OF DRAFT NEW RPORT ITU-R.M[IMT.C-V2X] - APPLICATION OF THE TERRESTRIAL COMPONENT OF IMT FOR CELLULAR-V2X | TSG RAN ITU AH | - | - | - | - | For 3GPP review: in: 3GPP TSG RAN feedback LS before: September 17, 2020 to: 3GPP TSG SA in: 3GPP TSG SA feedback LS before: September 18, 2020 to: 3GPP PCG. This was block noted at CC#2 | Noted | ||||
4.7 | S2-200782 | LS In | LS from TSG RAN ITU AH: Draft Letter to ITU in reply to ITU_R_WP5D_TEMP_39 = RP-200037 on update submission for LTE-Advanced towards Revision 5 of Recommendation ITU-R M.2012 | TSG RAN ITU AH | - | - | - | - | For 3GPP review: in: 3GPP TSG RAN feedback LS before: September 17, 2020 to: 3GPP SA in: 3GPP TSG SA feedback LS before: September 18, 2020 to: 3GPP PCG. This was block noted at CC#2 | Noted | ||||
4.7 | S2-200783 | LS In | LS from TSG RAN ITU AH: Draft Letter to ITU in answer to LS to RIT/SRIT Proponents on the completion and conclusions of steps 5 to 7 of the IMT-2020 process for the first release of new Recommendation ITU-R M.[IMT-2020.SPECS] | TSG RAN ITU AH | - | - | - | - | For 3GPP review: in: 3GPP TSG RAN feedback LS before: September 17, 2020 to: 3GPP SA in: 3GPP TSG SA feedback LS before: September 18, 2020 to: 3GPP PCG. This was block noted at CC#2 | Noted | ||||
4.7 | S2-200890 | REPORT | Chairmans Report of TSG RAN#89-e | TSG RAN Chairman | - | - | - | - | CC#5: Noted | Noted | ||||
4.8 | S2-200861 | LS In | LS from TSG CT: LS on information of stage 3 aspects for AKMA | TSG CT | - | - | - | - | Rel-17 | AKMA-CT | SA WG3 and SA WG1 will work on CRs that will propose to shift AKMA SA WG3 to Rel-17. Additional changes for separate discussions. Proposal to change BB to Feature for discussion in SA WG3. Noted | Noted | ||
4.8 | S2-200858 | REPORT | Status report of TSG CT#89-e | TSG CT Chairman | - | - | - | - | Noted | Noted | ||||
4.8 | S2-200859 | REPORT | Draft report of TSG CT#89-e | TSG CT Secretary (MCC) | - | - | - | - | Noted | Noted | ||||
4.8 | S2-200860 | REPORT | IETF Status report | TSG CT Chairman | - | - | - | - | Noted | Noted | ||||
6.2 | S2-200656 | WID REVISED | Revised WID on the normative aspects of User Plane Integrity Protection for NR. | Vodafone | - | - | - | - | Rel-17 | UPIP_SEC | Approved. The 3GPP Work Plan will need to be updated to indicate Rel-16 for UPIP_SEC. | Approved | ||
6.2 | S2-200763 | WID REVISED | Revised WID Self-Organizing Networks (SON) for 5G networks. | SA WG5 | - | - | - | - | Rel-16 | SON_5G | This was Block approved in CC#3 | Approved | ||
6.2 | S2-200770 | WID REVISED | Revised WID on Discovery of management services in 5G. | SA WG5 | - | - | - | - | Rel-16 | 5GDMS | This was Block approved in CC#3 | Approved | ||
6.3 | S2-200812 | SID NEW | New Study on User Consent for 3GPP services | Huawei, Hisilicon, China Unicom, CAICT, CATT | - | - | - | - | Rel-17 | CC#1: SP 200812_r01 was approved (to be revised by MCC). Revised to SP-200885. | Revised | S2-200885 | ||
6.3 | S2-200885 | SID NEW | New Study on User Consent for 3GPP services | Huawei, HiSilicon, China Unicom, CAICT, CATT | - | - | - | - | Rel-17 | Revision of SP-200812_Rev1. Approved | Approved | |||
6.3 | S2-200717 | SID NEW | New SID on security aspects of the 5GMSG Service. | SA WG3 | - | - | - | - | CC#2: SP 200717_rev1 was approved. Revised to SP-200878. | Revised | S2-200878 | |||
6.3 | S2-200878 | SID NEW | New SID on security aspects of the MSGin5G Service | SA WG3 | - | - | - | - | Revision of SP-200717_Rev1. Approved | Approved | ||||
6.3 | S2-200721 | SID NEW | New study on the security of AMF re-allocation. | SA WG3 | - | - | - | - | This was Block approved in CC#3 | Approved | ||||
6.3 | S2-200722 | SID NEW | New SID on security aspects of enablers for Network Automation (eNA) for the 5G System (5GS) Phase 2. | SA WG3 | - | - | - | - | This was Block approved in CC#3 | Approved | ||||
6.3 | S2-200765 | SID NEW | New SID on YANG PUSH. | SA WG5 | - | - | - | - | This was Block approved in CC#3 | Approved | ||||
6.3 | S2-200767 | SID NEW | New SID on charging aspects of Enhanced Proximity-based Services in 5GC. | SA WG5 | - | - | - | - | This was Block approved in CC#3 | Approved | ||||
6.3 | S2-200771 | SID NEW | Study on charging aspects of 5GS CIoT. | SA WG5 | - | - | - | - | This was Block approved in CC#3 | Approved | ||||
6.3 | S2-200764 | SID NEW | New SID on the access control for management service. | SA WG5 | - | - | - | - | Revised to SP-200853 | Revised | S2-200853 | |||
6.3 | S2-200853 | SID NEW | New SID on the access control for management service. | SA WG5 | - | - | - | - | Revision of SP-200764. Change of 'Other related Work Items and dependencies' as suggested by the Work Plan Manager. This was Block approved in CC#3 | Approved | ||||
6.4 | S2-200718 | WID NEW | New WID on mission critical security enhancements phase 2. | SA WG3 | - | - | - | - | CC#3: SP-200718_rev2 was approved. (To be revised into a new TD number by MCC). Revised to SP-200879. | Revised | S2-200879 | |||
6.4 | S2-200879 | WID NEW | New WID on mission critical security enhancements phase 2 | SA WG3 | - | - | - | - | Revision of SP-200718_Rev2. Approved | Approved | ||||
6.4 | S2-200667 | WID NEW | New Work Item on 'Operation Points for 8K VR 360 Video over 5G'. | Intel, NHK, Ericsson LM, AT&T, Qualcomm Incorporated, Dolby Laboratories Inc., Beijing Xiaomi Electronics, Tencent, Huawei Technologies Co Ltd. | - | - | - | - | Rel-17 | This was Block approved in CC#3 | Approved | |||
6.4 | S2-200719 | WID NEW | New WID on UPIP support in 5GS. | SA WG3 | - | - | - | - | This was Block approved in CC#3 | Approved | ||||
6.4 | S2-200720 | WID NEW | New WID on Security Assurance Specification for Network Slice-Specific Authentication and Authorization Function (NSSAAF). | SA WG3 | - | - | - | - | This was Block approved in CC#3 | Approved | ||||
6.4 | S2-200768 | WID NEW | New WID on N40 Interface Enhancements to Support GERAN and UTRAN. | SA WG5 | - | - | - | - | Revised to SP-200854 | Revised | S2-200854 | |||
6.4 | S2-200854 | WID NEW | New WID on N40 Interface Enhancements to Support GERAN and UTRAN. | SA WG5 | - | - | - | - | Revision of SP-200768. Alignment of acronym with SA WG2's acronym TEI17_NIESGU. This was Block approved in CC#3 | Approved | ||||
6.4 | S2-200769 | WID NEW | New work item on charging enhancement for URLLC. | SA WG5 | - | - | - | - | This was Block approved in CC#3 | Approved | ||||
6.4 | S2-200772 | CR PACK | Rel-17 CRs on Mission critical security enhancements phase 2 | SA WG3 | - | - | - | - | DUMMY | This was Block approved in CC#3 | Approved | |||
6.4 | S2-200831 | WID NEW | New WID for enhanced application layer support for V2X services. | SA WG6 | - | - | - | - | This was Block approved in CC#3 | Approved | ||||
6.4 | S2-200832 | WID NEW | New WID Application Architecture for MSGin5G Service. | SA WG6 | - | - | - | - | This was Block approved in CC#3 | Approved | ||||
6.4 | S2-200833 | WID NEW | New WID Mission Critical Services over 5GS. | SA WG6 | - | - | - | - | This was Block approved in CC#3 | Approved | ||||
6.5 | S2-200690 | SID REVISED | Revised SID: Architectural enhancements for 5G multicast-broadcast services. | SA WG2 | - | - | - | - | Rel-17 | FS_5MBS | This was Block approved in CC#3 | Approved | ||
6.5 | S2-200766 | SID NEW | New SID on network slice management enhancement to include security aspects. | SA WG5 | - | - | - | - | This was Block approved in CC#3. CC#4: WGs to avoid agreeing to multiple rapporteurs for WIDs and SIDs. | Approved | ||||
6.5 | S2-200834 | WID REVISED | Revised WID on Architecture for enabling Edge Applications . | SA WG6 | - | - | - | - | Rel-17 | EDGEAPP | CC#2: SP 200834_rev1 was approved. Revised to SP-200886. | Revised | S2-200886 | |
6.5 | S2-200886 | WID REVISED | Revised WID on Architecture for enabling Edge Applications . | SA WG6 | - | - | - | - | Rel-17 | EDGEAPP | Revision of SP-200834_Rev1. Approved | Approved | ||
6.5 | S2-200835 | SID REVISED | Revised SID Study on support of the 5GMSG Service. | SA WG6 | - | - | - | - | Rel-17 | FS_5GMARCH | This was Block approved in CC#3 | Approved | ||
6.5 | S2-200836 | SID REVISED | Revised SID Study on application layer support for . Factories of the Future in 5G network . | SA WG6 | - | - | - | - | Rel-17 | FS_FFAPP | This was Block approved in CC#3 | Approved | ||
6.5 | S2-200837 | SID REVISED | Revised SID Study on Mission Critical services support over 5G System. | SA WG6 | - | - | - | - | Rel-17 | FS_MCOver5GS | This was Block approved in CC#3 | Approved | ||
6.6 | S2-200799 | SID NEW | New SID: Study on 5G Networks Providing Access to Localized Services (FS_PALS). | SA WG1 | - | - | - | - | Rel-18 | CC#3: China Mobile withdrew their objection. Approved | Approved | |||
6.6 | S2-200821 | Discussion | Study on Support _x00B_for Service Function Chaining in 5G System (FS_SFCin5GS) | Intel, Deutsche Telekom AG, Tencent, Telefónica, Affirmed Network, AT&T, Sandvine, Convida Wireless, InterDigital, KPN, Verizon UK Ltd., KDDI, Vodafone, Telecom Italia, Cisco, b<>com, Spirent Communications | - | - | - | - | Rel-18 | Noted | Noted | |||
6.6 | S2-200822 | SID NEW | New SID on Study on Support for Service Function Chaining in 5G System. | Intel Corporation, Deutsche Telekom AG, Tencent, Telefónica, Affirmed Network, AT&T, Sandvine, Convida Wireless, InterDigital, KPN, Verizon UK Ltd., KDDI, Vodafone, Telecom Italia, Cisco, b<>com, Spirent Communications | - | - | - | - | Rel-18 | CC#1: This was left for further consideration over e-mail. CC#3: This issue will be handled further in SA WG1. Saso will provide a WID proposal for discussion on Friday. CC#4: Postoned | Postponed | |||
6.6 | S2-200798 | SID NEW | New SID: Study on vehicle-mounted relays (FS_VMR). | SA WG1 | - | - | - | - | CC#3: China Mobile withdrew their objection. Approved | Approved | ||||
6.7 | S2-200797 | WID NEW | New WID on Subscriber-aware Northbound API access (SNA). | SA WG1 (from S1-203296) | - | - | - | - | Rel-18 | This was Block approved in CC#3 | Approved | |||
6.9 | S2-200762 | DRAFT TS | Draft TS 28.555 'Network policy management for 5G mobile networks; Stage 1' | SA WG5 | 28.555 | - | - | - | - | Rel-17 | NPM | Revised in SP-200820 | Revised | S2-200820 |
6.9 | S2-200820 | DRAFT TS | Draft TS 28.555 'Network policy management for 5G mobile networks; Stage 1' | SA WG5 | 28.555 | - | - | - | - | Rel-17 | NPM | Revision of SP-200762. Noted | Noted | |
6.9 | S2-200691 | DRAFT TR | Presentation of TR 23.748 for information to TSG SA (FS_enh_EC) | SA WG2 | 23.748 | - | - | - | - | Rel-17 | FS_enh_EC | This was block noted in CC#3 | Noted | |
6.9 | S2-200692 | DRAFT TR | Presentation of TR 23.700-20 for information to TSG SA (FS_IIoT) | SA WG2 | 23.700-20 | - | - | - | - | Rel-17 | FS_IIoT | This was block noted in CC#3 | Noted | |
6.9 | S2-200693 | DRAFT TR | Presentation of TR 23.761 for information to TSG SA (FS_MUSIM) | SA WG2 | 23.761 | - | - | - | - | Rel-17 | FS_MUSIM | This was block noted in CC#3 | Noted | |
6.9 | S2-200694 | DRAFT TR | Presentation of TR 23.700-91 for Information to TSG SA (FS_eNA_Ph2) | SA WG2 | 23.700-91 | - | - | - | - | Rel-17 | FS_eNA_Ph2 | This was block noted in CC#3 | Noted | |
6.9 | S2-200695 | DRAFT TR | Presentation of presentation of TR 23.700-07 for information to TSG SA (FS_eNPN) | SA WG2 | 23.700-07 | - | - | - | - | Rel-17 | FS_eNPN | This was block noted in CC#3 | Noted | |
6.9 | S2-200696 | DRAFT TR | Presentation of TR 23.757 for information to TSG SA (FS_5MBS) | SA WG2 | 23.757 | - | - | - | - | Rel-17 | FS_5MBS | This was block noted in CC#3 | Noted | |
6.9 | S2-200698 | DRAFT TR | Presentation of TR 23.700-40 to TSG SA for information (FS_eNS_Ph2) | SA WG2 | 23.700-40 | - | - | - | - | Rel-17 | FS_eNS_Ph2 | This was block noted in CC#3 | Noted | |
6.9 | S2-200699 | DRAFT TR | Presentation of TR 23.700-93 to TSG SA for information (FS_ATSSS_Ph2) | SA WG2 | 23.700-93 | - | - | - | - | Rel-17 | FS_ATSSS_Ph2 | This was block noted in CC#3 | Noted | |
6.9 | S2-200700 | DRAFT TR | Presentation of TR 23.754 for information to TSG SA (FS_ID_UAS_SA2) | SA WG2 | 23.754 | - | - | - | - | Rel-17 | FS_ID_UAS_SA2 | This was block noted in CC#3 | Noted | |
6.9 | S2-200755 | DRAFT TR | Draft TR 28.809 'Study on enhancement of management data analytics' | SA WG5 | 28.809 | - | - | - | - | Rel-16 | FS_eMDAS | This was block noted in CC#3 | Noted | |
6.9 | S2-200828 | DRAFT TS | Presentation of TS 23.558 v1.0.0 for information | SA WG6 | 23.558 | - | - | - | - | Rel-17 | EDGEAPP | This was block noted in CC#3 | Noted | |
6.9 | S2-200829 | DRAFT TR | Presentation of TR 23.745 v1.0.0 for information | SA WG6 | 23.745 | - | - | - | - | Rel-16 | FS_FFAPP | This was block noted in CC#3 | Noted | |
6.9 | S2-200830 | DRAFT TR | Presentation of TR 23.700-24 v1.0.0 for information | SA WG6 | 23.700-24 | - | - | - | - | Rel-17 | FS_5GMARCH | This was block noted in CC#3 | Noted | |
6.10 | S2-200666 | DRAFT TS | Draft TS 26.512: 5G Media Streaming (5GMS); Protocols | SA WG4 | 26.512 | - | - | - | - | Rel-16 | 5GMS3 | This was Block approved in CC#3 | Approved | |
6.10 | S2-200756 | DRAFT TR | Draft TR 28.812 'Study on scenarios for Intent driven management services for mobile networks' | SA WG5 | 28.812 | - | - | - | - | Rel-17 | IDMS_MN | This was Block approved in CC#3 | Approved | |
6.10 | S2-200757 | DRAFT TS | Draft TS 28.309 'Management of Quality of Experience (QoE) measurement collection Integration Reference Point (IRP); Solution Set (SS) definitions' | SA WG5 | 28.309 | - | - | - | - | Rel-16 | QOED | This was Block approved in CC#3 | Approved | |
6.10 | S2-200758 | DRAFT TS | Draft TS 28.313 'Study on new aspects of Energy Efficiency (EE) for 5G' | SA WG5 | 28.313 | - | - | - | - | Rel-16 | SON_5G | This was Block approved in CC#3 | Approved | |
6.10 | S2-200759 | DRAFT TR | Draft TR 28.810 'Study on concept, requirements and solutions for levels of autonomous network' | SA WG5 | 28.810 | - | - | - | - | Rel-16 | FS_ANL | This was Block approved in CC#3 | Approved | |
6.10 | S2-200760 | DRAFT TS | Draft TS 28.201 'Network slice performance and analytics charging in the 5G System (5GS); Stage 2' | SA WG5 | 28.201 | - | - | - | - | Rel-16 | 5GS_NSPACH | This was Block approved in CC#3 | Approved | |
6.10 | S2-200761 | DRAFT TS | Draft TS 28.202 'Network slice management charging in the 5G System (5GS); Stage 2' | SA WG5 | 28.202 | - | - | - | - | Rel-16 | 5GS_NSMCH | This was Block approved in CC#3 | Approved | |
6.10 | S2-200826 | DRAFT TS | Presentation of TS 23.180 v2.0.0 for approval | SA WG6 | 23.180 | - | - | - | - | Rel-17 | MCIOPS | This was Block approved in CC#3 | Approved | |
6.10 | S2-200827 | DRAFT TR | Presentation of TR 23.764 v2.0.0 for approval | SA WG6 | 23.764 | - | - | - | - | Rel-17 | FS_eV2XAPP | This was Block approved in CC#3 | Approved | |
7.1 | S2-200815 | DISCUSSION | 3GPP Meeting Planning H1/2021 | TSG SA Chairman | - | - | - | - | Noted | Noted | ||||
7.1 | S2-200819 | DISCUSSION | Thoughts about enumerating SA WG1 requirements | Siemens, Philips | - | - | - | - | Rel-18 | CC#3: TSG SA Chairman will start a moderated TSG SA e-mail discussion on the enumeration issue until the next TSG SA meeting. This was then noted. | Noted | |||
7.3 | S2-200800 | DISCUSSION | On Release 17 Schedule | Qualcomm Incorporated | - | - | - | - | Rel-17 | Noted | Noted | |||
7.3 | S2-200811 | DISCUSSION | Discussion on Rel-17 Schedule | Huawei, HiSilicon | - | - | - | - | Rel-17 | Noted | Noted | |||
7.3 | S2-200862 | LS OUT | [DRAFT] LS on R17 schedule | TSG SA | - | - | - | - | CC#3: A corrected version was provided in the revisions folder as SP-200862_rev1. CC#4: SP-200862_Rev2 approved. Revised to SP-200888. | Revised | S2-200888 | |||
7.3 | S2-200888 | LS OUT | LS on Rel-17 schedule | TSG SA | - | - | - | - | Revision of SP-200862_Rev2. Approved | Approved | ||||
10 | S2-200728 | CR PACK | Rel-10 CRs on TEI | SA WG5 | - | - | - | - | TEI10 | This was Block approved in CC#3 | Approved | |||
11 | S2-200727 | CR PACK | Rel-11 CRs on TEI | SA WG5 | - | - | - | - | TEI12 | This was Block approved in CC#3 | Approved | |||
12 | S2-200726 | CR PACK | Rel-12 CRs on TEI | SA WG5 | - | - | - | - | TEI12 | This was Block approved in CC#3 | Approved | |||
13 | S2-200714 | CR PACK | Rel-13 CRs on Enhancements to WEBRTC interoperability | SA WG3 | - | - | - | - | eWebRTCi | This was Block approved in CC#3 | Approved | |||
15 | S2-200671 | CR PACK | CRs to 23.501, 23.502 on 5GS_Ph1 (Rel-15, Rel-16) | SA WG2 | - | - | - | - | This was Block approved in CC#3 | Approved | ||||
15 | S2-200672 | CR PACK | CRs to 23.401 on NB_IOTenh-Core, CIoT_ext (Rel-15, Rel-16) | SA WG2 | - | - | - | - | This was Block approved in CC#3 | Approved | ||||
15 | S2-200702 | CR PACK | Rel-15 CRs on Security Assurance Specification for eNB network product class | SA WG3 | - | - | - | - | SCAS_eNB | This was Block approved in CC#3 | Approved | |||
15 | S2-200709 | CR PACK | Rel-15 CRs on Security aspects of 5G System - Phase 1 batch 1 | SA WG3 | - | - | - | - | 5GS_Ph1-SEC | This was Block approved in CC#3 | Approved | |||
15 | S2-200725 | CR PACK | Rel-15 CRs on TEI | SA WG5 | - | - | - | - | TEI15 | This was Block approved in CC#3 | Approved | |||
15 | S2-200730 | CR PACK | Rel-15 CRs on Network Resource Model (NRM) for 5G networks and network slicing | SA WG5 | - | - | - | - | NETSLICE-5GNRM | This was Block approved in CC#3 | Approved | |||
15 | S2-200731 | CR PACK | Rel-15 CRs on Performance Assurance for 5G networks including network slicing | SA WG5 | - | - | - | - | NETSLICE-ADPM5G | This was Block approved in CC#3 | Approved | |||
15 | S2-200735 | CR PACK | Rel-15 CRs on Provisioning of network slicing for 5G networks and services | SA WG5 | - | - | - | - | NETSLICE-PRO_NS | This was Block approved in CC#3 | Approved | |||
15 | S2-200736 | CR PACK | Rel-15 CRs on Management and orchestration of 5G networks and network slicing | SA WG5 | - | - | - | - | NETSLICE | This was Block approved in CC#3 | Approved | |||
15 | S2-200742 | CR PACK | Rel-15 CRs on Service Based Interface for 5G Charging | SA WG5 | - | - | - | - | 5GS_Ph1-SBI_CH | This was Block approved in CC#3 | Approved | |||
15 | S2-200773 | CR PACK | Rel-15 CRs on Security aspects of 5G System - Phase 1 Batch 2 | SA WG3 | - | - | - | - | 5GS_Ph1-SEC | This was Block approved in CC#3 | Approved | |||
15 | S2-200806 | CR PACK | Rel-15 CRs on Lawful Interception | SA WG3-LI | - | - | - | - | Rel-15 | LI15 | This was Block approved in CC#3 | Approved | ||
16 | S2-200657 | CR | 21.900 CR0064 (Rel-16, 'C'): CR to TR 21.900 on Relaxation of mini-WID requirement for Cat.B/C TEI CRs | NEC on behalf of TSG RAN | 21.900 | 0064 | - | C | 16.3.0 | Rel-16 | TEI16 | Same as draft CR proposed by TSG RAN in SP-200868. CC#4: Postponed | Postponed | |
16 | S2-200868 | LS In | LS from TSG RAN: LS on Relaxation of mini-WID requirement for Cat.B/C TEI CRs | TSG RAN | - | - | - | - | Rel-16 | TEI16 | Attached CR is the same change as in SP-200657. CC#4: This LS was postponed. | Postponed | ||
16.1 | S2-200790 | CR PACK | Stage 1 CRs on eCAV | SA WG1 | - | - | - | - | CC#4: 22.261 CR0462R2 revised in SP-200869. 22.104 0053r1 and 22.261 0465r1 were postponed. The other CRs in this CR pack were approved | Partially approved | ||||
16.1 | S2-200869 | CR | 22.261 CR0462R3 (Rel-17, 'D'): Quality improvement of TS 22.261 (R17) – editorial modifications | Siemens | 22.261 | 0462 | 3 | D | 17.3.0 | Rel-17 | eCAV | Revision of 22.261 CR0462R2 from CR Pack SP-200790. CC#4: SP-200869_Rev3 was approved. Revised to SP-200889. | Revised | S2-200889 |
16.1 | S2-200889 | CR | 22.261 CR0462R4 (Rel-17, 'D'): Quality improvement of TS 22.261 (R17) – editorial modifications | Siemens | 22.261 | 0462 | 4 | D | 17.3.0 | Rel-17 | eCAV | Revision of SP-200869. Approved | Approved | |
16.1 | S2-200784 | CR PACK | Stage 1 CRs on cyberCAV | SA WG1 | - | - | - | - | CC#3: 22.104 CR0054r1 and 22.261 CR0464 removed from the pack for further discussion (postponed). The other CRs in this CR Pack were approved. (This CR Pack was partially approved). | Partially approved | ||||
16.1 | S2-200791 | CR PACK | Stage 1 CRs on ID_UAS | SA WG1 | - | - | - | - | CC#3: SP-200791_Rev1 was approved. (To be revised by MCC to provide a new TD number). Revised to SP-200881. | Revised | S2-200881 | |||
16.1 | S2-200881 | CR | 22.125 CR0028R6 (Rel-17, 'F'): Stage 1 CRs on ID_UAS | SA WG1 | 22.125 | 0028 | 6 | F | 17.1.0 | Rel-17 | EAV | Revision of 22.125 CR0028R5 in SP-200791_Rev1. Approved | Approved | |
16.1 | S2-200793 | CR PACK | Stage 1 CRs FS_FRMCS3 | SA WG1 | - | - | - | - | CC#3: SP-200793_Rev1 was approved. (To be revised by MCC to provide a new TD number). Revised to SP-200882. | Revised | S2-200882 | |||
16.1 | S2-200882 | CR | 22.889 CR0169R3 (Rel-17, 'F'): Stage 1 CRs FS_FRMCS3 | SA WG1 | 22.889 | 0169 | 3 | F | 17.2.0 | Rel-17 | FS_FRMCS3 | Revision of 22.889 CR0169R2 in SP-200793_Rev1. Approved | Approved | |
16.1 | S2-200785 | CR PACK | Stage 1 CRs on REAR | SA WG1 | - | - | - | - | This was Block approved in CC#3 | Approved | ||||
16.1 | S2-200786 | CR PACK | Stage 1 CRs on MARCOM | SA WG1 | - | - | - | - | This was Block approved in CC#3 | Approved | ||||
16.1 | S2-200787 | CR PACK | Stage 1 CRs on 5GSAT | SA WG1 | - | - | - | - | This was Block approved in CC#3 | Approved | ||||
16.1 | S2-200788 | CR PACK | Stage 1 CRs on UIA | SA WG1 | - | - | - | - | This was Block approved in CC#3 | Approved | ||||
16.1 | S2-200789 | CR PACK | Stage 1 CRs on TEI16 | SA WG1 | - | - | - | - | This was Block approved in CC#3 | Approved | ||||
16.1 | S2-200792 | CR PACK | Stage 1 CRs on AVPROD | SA WG1 | - | - | - | - | This was Block approved in CC#3 | Approved | ||||
16.1 | S2-200794 | CR PACK | Stage 1 CRs on TEI17 | SA WG1 | - | - | - | - | This was Block approved in CC#3 | Approved | ||||
16.2 | S2-200685 | CR PACK | CRs to 23.401, 23.502 on RACS (Rel-16) | SA WG2 | - | - | - | - | Company proposed revision of 23.501 CR2383R1 in SP-200802. CC#1: 23.501 CR2383R1 was considered as revised and other CRs in this CR pack were approved. | Partially approved | ||||
16.2 | S2-200802 | CR | 23.501 CR2383R2 (Rel-16, 'F'): Signalling of UE Radio Capability ID in Registration procedure | Qualcomm Incorporated | 23.501 | 2383 | 2 | F | 16.5.1 | Rel-16 | RACS | Revision of S2-2006493 (23.501 CR2383R1) in CR Pack SP-200685. CC#1: Vodafone supported this CR. This CR was approved. This CR was agreed | Approved | |
16.2 | S2-200688 | CR PACK | CRs to 23.501, 23.502, 23.503 on Vertical_LAN (Rel-16) | SA WG2 | - | - | - | - | CC#1: 23.501 CR2448R1 was reported needing further work and was postponed. All other CRs in this CR pack were approved. | Partially approved | ||||
16.2 | S2-200673 | CR PACK | CRs to 23.501, 23.502, 23.503 on 5G_CIoT (Rel-16) | SA WG2 | - | - | - | - | This was Block approved in CC#3 | Approved | ||||
16.2 | S2-200674 | CR PACK | CRs to 23.501, 23.502 on 5G_eSBA (Rel-16) | SA WG2 | - | - | - | - | This was Block approved in CC#3 | Approved | ||||
16.2 | S2-200675 | CR PACK | CR to 23.501 on 5G_URLLC (Rel-16) | SA WG2 | - | - | - | - | This was Block approved in CC#3 | Approved | ||||
16.2 | S2-200676 | CR PACK | CRs to 23.316, 23.502 on 5WWC (Rel-16) | SA WG2 | - | - | - | - | This was Block approved in CC#3 | Approved | ||||
16.2 | S2-200677 | CR PACK | CR to 23.501 on ATSSS (Rel-16) | SA WG2 | - | - | - | - | This was Block approved in CC#3 | Approved | ||||
16.2 | S2-200678 | CR PACK | CRs to 23.228, 23.501 on eIMS5G_SBA (Rel-16) | SA WG2 | - | - | - | - | This was Block approved in CC#3 | Approved | ||||
16.2 | S2-200679 | CR PACK | CRs to 23.228, 23.502, 23.503 on eNA (Rel-16) | SA WG2 | - | - | - | - | This was Block approved in CC#3 | Approved | ||||
16.2 | S2-200680 | CR PACK | CRs to 23.502 on eNS (Rel-16) | SA WG2 | - | - | - | - | This was Block approved in CC#3 | Approved | ||||
16.2 | S2-200681 | CR PACK | CRs to 23.502 on ETSUN (Rel-16) | SA WG2 | - | - | - | - | This was Block approved in CC#3 | Approved | ||||
16.2 | S2-200682 | CR PACK | CRs to 23.285, 23.287, 23.502, 23.503 on eV2XARC (Rel-16) | SA WG2 | - | - | - | - | This was Block approved in CC#3 | Approved | ||||
16.2 | S2-200683 | CR PACK | CR to 23.501 on IABARC (Rel-16) | SA WG2 | - | - | - | - | This was Block approved in CC#3 | Approved | ||||
16.2 | S2-200684 | CR PACK | CR to 23.401 on PARLOS (Rel-16) | SA WG2 | - | - | - | - | This was Block approved in CC#3 | Approved | ||||
16.2 | S2-200686 | CR PACK | CRs to 23.214, 23.501, 23.502, 23.682 on TEI16 (Rel-16) | SA WG2 | - | - | - | - | This was Block approved in CC#3 | Approved | ||||
16.2 | S2-200687 | CR PACK | CR to 23.501 on UDICOM (Rel-16) | SA WG2 | - | - | - | - | This was Block approved in CC#3 | Approved | ||||
16.2 | S2-200689 | CR PACK | CR to 23.502 on xBDT (Rel-16) | SA WG2 | - | - | - | - | This was Block approved in CC#3 | Approved | ||||
16.3 | S2-200706 | CR PACK | Rel-16 CRs on Security for enhancements to the Service Based 5G System Architecture | SA WG3 | - | - | - | - | 5G_eSBA | 33.501 CR0908R1 should be a CR to 33.310, so should be rejected. Replacement CR to 33.310 provided in SP-200857. 33.501 CR0908R1 was rejected. Al other CRs in this CR Pack were approved | Partially approved | |||
16.3 | S2-200857 | CR | 33.310 CR0112 (Rel-16, 'F'): Making NF instance id in SBA certificate profile mandatory to support | Nokia | 33.310 | 0112 | - | F | 16.4.0 | Rel-16 | 5G_eSBA | Incorrect TS was specified in the SA WG3 TD request. New CR allocated at TSG SA#89-e. CC#3: This CR was approved. | Approved | |
16.3 | S2-200701 | CR PACK | Rel-16 CRs on TEI | SA WG3 | - | - | - | - | TEI16 | This was Block approved in CC#3 | Approved | |||
16.3 | S2-200703 | CR PACK | Rel-16 CRs on Security Assurance Specification for 5G | SA WG3 | - | - | - | - | SCAS_5G | This was Block approved in CC#3 | Approved | |||
16.3 | S2-200705 | CR PACK | Rel-16 CRs on Security Aspects of eV2XARC | SA WG3 | - | - | - | - | eV2XARC | CC#1: 33.536 CR0002 was reported needing further work and was postponed. All other CRs in this CR pack were approved. | Partially approved | |||
16.3 | S2-200707 | CR PACK | Rel-16 CRs on Security for IAB | SA WG3 | - | - | - | - | NR_IAB | This was Block approved in CC#3 | Approved | |||
16.3 | S2-200708 | CR PACK | Rel-16 CRs on Authentication and key management for applications based on 3GPP credential in 5G | SA WG3 | - | - | - | - | AKMA | This was Block approved in CC#3 | Approved | |||
16.3 | S2-200710 | CR PACK | Rel-16 CRs on User Plane Gateway Function for Inter-PLMN Security | SA WG3 | - | - | - | - | UPGF | This was Block approved in CC#3 | Approved | |||
16.3 | S2-200715 | CR PACK | Rel-16 CRs on Security aspects of SEAL | SA WG3 | - | - | - | - | SEAL | This was Block approved in CC#3 | Approved | |||
16.3 | S2-200716 | CR PACK | Rel-16 CRs on Security aspects of Enhanced Network Slicing | SA WG3 | - | - | - | - | eNS | This was Block approved in CC#3 | Approved | |||
16.3 | S2-200807 | CR PACK | Rel-16 CRs on Lawful Interception | SA WG3-LI | - | - | - | - | Rel-16 | LI16 | This was Block approved in CC#3 | Approved | ||
16.4 | S2-200659 | CR PACK | CRs to TS 26.116 | SA WG4 | 26.116 | - | - | - | - | Rel-16 | 5GMS3 | This was Block approved in CC#3 | Approved | |
16.4 | S2-200660 | CR PACK | CRs to TS 26.223 | SA WG4 | 26.223 | - | - | - | - | Rel-16 | TEI16 | This was Block approved in CC#3 | Approved | |
16.4 | S2-200661 | CR PACK | CRs to TS 26.234 | SA WG4 | 26.234 | - | - | - | - | Rel-16 | RM_H263_MP4V | This was Block approved in CC#3 | Approved | |
16.4 | S2-200662 | CR PACK | CRs to TS 26.238 | SA WG4 | 26.238 | - | - | - | - | Rel-16 | E_FLUS | This was Block approved in CC#3 | Approved | |
16.4 | S2-200663 | CR PACK | CRs to TS 26.501 | SA WG4 | 26.501 | - | - | - | - | Rel-16 | 5GMSA | This was Block approved in CC#3 | Approved | |
16.4 | S2-200664 | CR PACK | CRs to TS 26.511 | SA WG4 | 26.511 | - | - | - | - | Rel-16 | 5GMS3 | This was Block approved in CC#3 | Approved | |
16.4 | S2-200665 | CR PACK | CRs to TS 26.114 | SA WG4 | 26.114 | - | - | - | - | Rel-16 | TEI16, E2E_DELAY | This was Block approved in CC#3 | Approved | |
16.4 | S2-200668 | CR PACK | CR to 26.247 | SA WG4 | 26.247 | - | - | - | - | Rel-16 | 5GMS3 | This was Block approved in CC#3 | Approved | |
16.4 | S2-200804 | CR PACK | CRs to RM_H263_MP4V (postponed from SA#88-e) | SA WG4 | - | - | - | - | Rel-16 | RM_H263_MP4V | These CRs were postponed from SA#88-e. This was Block approved in CC#3 | Approved | ||
16.5 | S2-200723 | CR PACK | Rel-16 CRs on Streaming trace reporting | SA WG5 | - | - | - | - | Rel-16 | OAM_RTT | This was Block approved in CC#3 | Approved | ||
16.5 | S2-200724 | CR PACK | Rel-16 CRs on TEI | SA WG5 | - | - | - | - | TEI16 | This was Block approved in CC#3 | Approved | |||
16.5 | S2-200729 | CR PACK | Rel-16 CRs on NRM enhancements | SA WG5 | - | - | - | - | eNRM | This was Block approved in CC#3 | Approved | |||
16.5 | S2-200732 | CR PACK | Rel-16 CRs on Self-Organizing Networks (SON) for 5G networks | SA WG5 | - | - | - | - | SON_5G | This was Block approved in CC#3 | Approved | |||
16.5 | S2-200733 | CR PACK | Rel-16 CRs on Charging Access of ATSSS | SA WG5 | - | - | - | - | ATSSS | This was Block approved in CC#3 | Approved | |||
16.5 | S2-200734 | CR PACK | Rel-16 CRs on Energy efficiency of 5G | SA WG5 | - | - | - | - | EE_5G | This was Block approved in CC#3 | Approved | |||
16.5 | S2-200737 | CR PACK | Rel-16 CRs on Integration of ONAP and 3GPP 5G management framework | SA WG5 | - | - | - | - | ONAP3GPP | This was Block approved in CC#3 | Approved | |||
16.5 | S2-200738 | CR PACK | Rel-16 CRs on Enhancement of performance assurance for 5G networks including network slicing batch 1 | SA WG5 | - | - | - | - | 5G_SLICE_ePA | This was Block approved in CC#3 | Approved | |||
16.5 | S2-200740 | CR PACK | Rel-16 CRs on Charging Enhancement of 5GC interworking with EPC | SA WG5 | - | - | - | - | 5GIEPC_CH | This was Block approved in CC#3 | Approved | |||
16.5 | S2-200741 | CR PACK | Rel-16 CRs on CHF-controlled quota management | SA WG5 | - | - | - | - | CHFCQM | This was Block approved in CC#3 | Approved | |||
16.5 | S2-200743 | CR PACK | Rel-16 CRs on Network Slice Performance and Analytics Charging in 5G System | SA WG5 | - | - | - | - | 5GS_NSPACH | This was Block approved in CC#3 | Approved | |||
16.5 | S2-200744 | CR PACK | Rel-16 CRs on Management of MDT in 5G | SA WG5 | - | - | - | - | 5GMDT | This was Block approved in CC#3 | Approved | |||
16.5 | S2-200745 | CR PACK | Rel-16 CRs on Network Slice Management Charging in 5G System | SA WG5 | - | - | - | - | 5GS_NSMCH | This was Block approved in CC#3 | Approved | |||
16.5 | S2-200750 | CR PACK | Rel-16 CRs on Closed loop SLS Assurance | SA WG5 | - | - | - | - | COSLA | This was Block approved in CC#3 | Approved | |||
16.5 | S2-200751 | CR PACK | Rel-16 CRs on KPI reporting | SA WG5 | - | - | - | - | 5G_SLICE_ePA-KPI | This was Block approved in CC#3 | Approved | |||
16.5 | S2-200753 | CR PACK | Rel-16 CRs on Trace Management in the context of Services Based Management Architecture | SA WG5 | - | - | - | - | TM_SBMA | This was Block approved in CC#3 | Approved | |||
16.5 | S2-200754 | CR PACK | Rel-16 CRs on Management Aspects of 5G Service-Level Agreement | SA WG5 | - | - | - | - | MA5SLA | This was Block approved in CC#3 | Approved | |||
16.5 | S2-200813 | CR PACK | REl-16 CRs on TEI batch 2 | SA WG5 | - | - | - | - | TEI16 | This was Block approved in CC#3 | Approved | |||
16.5 | S2-200816 | CR PACK | Rel-16 CRs on Charging Aspects for 5WWC | SA WG5 | - | - | - | - | 5WWC | This was Block approved in CC#3 | Approved | |||
16.5 | S2-200817 | CR PACK | REl-16 CRs on Nchf Online and Offline charging services | SA WG5 | - | - | - | - | OFSBI_CH | This was Block approved in CC#3 | Approved | |||
16.6 | S2-200838 | CR PACK | Rel-16 CRs to TS 23.283 for eMCCI | SA WG6 | - | - | - | - | eMCCI | This was Block approved in CC#3 | Approved | |||
16.6 | S2-200839 | CR PACK | Rel-16 CRs to TS 23.282 for eMCData2 | SA WG6 | - | - | - | - | eMCData2 | This was Block approved in CC#3 | Approved | |||
16.6 | S2-200840 | CR PACK | Rel-16 CRs to TS 23.222 for eCAPIF | SA WG6 | - | - | - | - | eCAPIF | This was Block approved in CC#3 | Approved | |||
16.6 | S2-200841 | CR PACK | Rel-16 CRs to TS 23.434 for SEAL | SA WG6 | - | - | - | - | SEAL | This was Block approved in CC#3 | Approved | |||
16.6 | S2-200842 | CR PACK | Rel-16 CRs to TS 23.286 for V2XAPP | SA WG6 | - | - | - | - | V2XAPP | This was Block approved in CC#3 | Approved | |||
17.5 | S2-200746 | CR PACK | Rel-17 CRs on Management of MDT enhancement in 5G | SA WG5 | - | - | - | - | e_5GMDT | This was Block approved in CC#3 | Approved | |||
17.5 | S2-200747 | CR PACK | Rel-17 CRs on Enhancements of 5G performance measurements and KPIs | SA WG5 | - | - | - | - | ePM_KPI_5G | This was Block approved in CC#3 | Approved | |||
17.5 | S2-200748 | CR PACK | Rel-17 CRs on Additional NRM features | SA WG5 | - | - | - | - | adNRM | This was Block approved in CC#3 | Approved | |||
17.5 | S2-200749 | CR PACK | Rel-17 CRs on Enhancement on Management Aspects of 5G Service-Level Agreement | SA WG5 | - | - | - | - | EMA5SLA | This was Block approved in CC#3 | Approved | |||
17.5 | S2-200752 | CR PACK | Rel-17 CRs on Enhancements of Self-Organizing Networks (SON) for 5G networks | SA WG5 | - | - | - | - | eSON_5G | This was Block approved in CC#3 | Approved | |||
17.6 | S2-200843 | CR PACK | Rel-17 CRs to TS 23.280, TS 23.281, TS 23.282 and TS 23.379 for eMONASTERY2 | SA WG6 | - | - | - | - | eMONASTERY2 | This was Block approved in CC#3 | Approved | |||
17.6 | S2-200844 | CR PACK | Rel-17 CRs to TS 23.280 and TS 23.379 for enh3MCPTT | SA WG6 | - | - | - | - | enh3MCPTT | This was Block approved in CC#3 | Approved | |||
17.6 | S2-200845 | CR PACK | Rel-17 CRs to TS 23.282 for eMCData3 | SA WG6 | - | - | - | - | eMCData3 | This was Block approved in CC#3 | Approved | |||
17.6 | S2-200846 | CR PACK | Rel-17 CRs to TS 23.281 and TS 23.283 for TEI17 | SA WG6 | - | - | - | - | TEI17 | This was Block approved in CC#3 | Approved | |||
17.6 | S2-200847 | CR PACK | Rel-17 CR to TR 23.744 for FS_enhMCLoc | SA WG6 | - | - | - | - | FS_enhMCLoc | This was Block approved in CC#3 | Approved | |||
18.1 | S2-200818 | CR PACK | Stage 1 CRs on SNA | SA WG1 | - | - | - | - | Rel-18 | This was Block approved in CC#3 | Approved | |||
19 | S2-200711 | CR PACK | Rel-16 CRs for Study on Security Aspects of 3GPP support for Advanced V2X Services | SA WG3 | - | - | - | - | FS_eV2X_Sec | This was Block approved in CC#3 | Approved | |||
19 | S2-200712 | CR PACK | Rel-16 CRs onStudy on Security Aspects of the 5G Service Based Architecture | SA WG3 | - | - | - | - | FS_SBA_Sec | This was Block approved in CC#3 | Approved | |||
19 | S2-200713 | CR PACK | Rel-16 CRs on Study on evolution of Cellular IoT security for the 5G System | SA WG3 | - | - | - | - | FS_CIoT_sec_5G | This was Block approved in CC#3 | Approved | |||
20.1 | S2-200850 | DISCUSSION | A Feature is like a worm: don't cut it | 3GPP Work Plan Coordinator | - | - | - | - | CC#3: Postponed | Postponed | ||||
20.1 | S2-200823 | WORK PLAN | Work Plan review at TSG#89 | Work Plan Coordinator (MCC) | - | - | - | - | CC#4: SP-200823_Rev2 was provided to take comments into account. Noted | Noted | ||||
20.3 | S2-200776 | WI SUMMARY | Work Item Summary for 5G_eSBA | China Mobile | - | - | - | - | Rel-16 | 5G_eSBA | This was Block endorsed in CC#3 | Endorsed | ||
20.3 | S2-200777 | WI SUMMARY | Work Item Summary for Rel-16 UDICOM | Nokia Korea | 21.916 | - | - | - | - | Rel-16 | UDICOM | This was Block endorsed in CC#3 | Endorsed | |
20.3 | S2-200801 | WI SUMMARY | Summary for Work Item on 'Removal of H.263 and MPEG-4 Visual from 3GPP Services' | Qualcomm Incorporated | - | - | - | - | Rel-16 | RM_H263_MP4V | This was Block endorsed in CC#3 | Endorsed | ||
20.3 | S2-200808 | WI SUMMARY | Work Item Summary for Rel-16 eIMS5G_SBA | T-Mobile USA Inc. | - | - | - | - | Rel-16 | TEI16 | This was Block endorsed in CC#3 | Endorsed | ||
20.3 | S2-200848 | WI SUMMARY | Work item Summary for 5GMS3 | Sony (Rapporteur) | - | - | - | - | Rel-16 | 5GMS3 | This was Block endorsed in CC#3 | Endorsed | ||
20.3 | S2-200849 | WI SUMMARY | Work item Summary for Enhancement of performance assurance for 5G | Intel (Rapporteur) | - | - | - | - | Rel-16 | 5G_SLICE_ePA | This was Block endorsed in CC#3 | Endorsed | ||
20.3 | S2-200851 | WI SUMMARY | Work Item Summary for Rel-16 eCAPIF | Samsung | - | - | - | - | Rel-16 | eCAPIF | This was Block endorsed in CC#3 | Endorsed | ||
20.3 | S2-200852 | WI SUMMARY | Work Item Summary for Rel-16 SEAL | Samsung | - | - | - | - | Rel-16 | SEAL | This was Block endorsed in CC#3 | Endorsed | ||
20.3 | S2-200824 | DRAFT TR | TR 21.916 v.0.6.0 on Rel-16 Summary | Work Plan Coordinator (MCC) | 21.916 | - | - | - | - | Rel-16 | TEI16 | This was Block noted in CC#3 | Noted | |
20.3 | S2-200872 | WI SUMMARY | Work Item Summary for QOED | Ericsson | - | - | - | - | Rel-16 | QOED | Late submission. CC#4: This WI Summary was endorsed. | Endorsed | ||
20.5 | S2-200803 | REPORT | Support Team report | MCC | - | - | - | - | CC#4: Noted | Noted |
Annex C List of attendees
TITLE | Family Name | Given Name | Representing | Partner | Membership Status |
Dr. | Abhishek | Rohit | Tencent | CCSA | 3GPPMEMBER |
Mr. | Achter | Johannes | Deutsche Telekom AG | ETSI | 3GPPMEMBER |
Mr. | Adema | Jos | KPN N.V. | ETSI | 3GPPMEMBER |
Mr. | Agbede | Afolabi | BT plc | ETSI | 3GPPMEMBER |
Mr. | Agrone | Roberto | Leonardo SpA | ETSI | 3GPPMEMBER |
Mr. | Ahmad | Saad | InterDigital, Inc. | ETSI | 3GPPMEMBER |
Mr. | Ai | Ming | CATT | CCSA | 3GPPMEMBER |
Ms. | Akansha | Akansha Arora | TSDSI | TSDSI | 3GPPORG_REP |
Mr. | Ali | Irfan | Cisco Systems Belgium | ETSI | 3GPPMEMBER |
Ing. | Almodovar Chico | Jose Luis | TNO | ETSI | 3GPPMEMBER |
Mr. | Amogh | Niranth | Huawei Telecommunication India | TSDSI | 3GPPMEMBER |
Mr. | Askerup | Anders | Hewlett-Packard Enterprise | ETSI | 3GPPMEMBER |
Dr. | Baboescu | Florin | BROADCOM CORPORATION | ETSI | 3GPPMEMBER |
Mr. | Bahr | Michael | Siemens AG | ETSI | 3GPPMEMBER |
Dr. | Bari | Farooq | AT&T | ATIS | 3GPPMEMBER |
Dr. | Ben Henda | Noamen | Ericsson LM | ETSI | 3GPPMEMBER |
Mr. | Bennett | Andy | Samsung R&D Institute UK | ETSI | 3GPPMEMBER |
Mr. | Berisot | Thierry | NOVAMINT | ETSI | 3GPPMEMBER |
Dr. | Beutler | Roland | EBU | ETSI | 3GPPMEMBER |
Mr. | Bischinger | Kurt | Deutsche Telekom AG | ETSI | 3GPPMEMBER |
Mr. | Bladenis | Alex | Telstra Corporation Limited | ETSI | 3GPPMEMBER |
Mr. | Boixadera | Francesc | MediaTek (Hefei) Inc. | CCSA | 3GPPMEMBER |
Mr. | Brown | Michael | Affirmed Networks Inc. | ETSI | 3GPPMEMBER |
Mr. | Buckley | Adrian | vivo Communication Technology | CCSA | 3GPPMEMBER |
Mr. | Cao | Aijun | ZTE Wistron Telecom AB | ETSI | 3GPPMEMBER |
Mrs. | Carrion | Inma | CommScope Technologies AG | ETSI | 3GPPMEMBER |
Mr. | Casati | Alessio | Nokia Korea | TTA | 3GPPMEMBER |
Mr. | Champel | Mary-Luc | Beijing Xiaomi Electronics | CCSA | 3GPPMEMBER |
Dr. | Chan | Yee Sin | ETSI | 3GPPMEMBER | |
Mr. | Chang | Jaehyun | LG Uplus | TTA | 3GPPMEMBER |
Dr. | CHEN | LI | vivo Mobile Com. (Chongqing) | CCSA | 3GPPMEMBER |
Miss | chen | shan | GEESPACE | CCSA | 3GPPMEMBER |
Dr. | Chen | Wanshi | Qualcomm Incorporated | ATIS | 3GPPMEMBER |
Dr. | Chen | Xiaobao | Orange UK | ETSI | 3GPPMEMBER |
Dr. | Chengjun | Sun | Samsung Electronics Benelux BV | ETSI | 3GPPMEMBER |
Dr. | Chiba | Tsunehiko | Rakuten Mobile, Inc | ARIB | 3GPPMEMBER |
Mr. | Chitturi | Suresh | Samsung R&D Institute India | TSDSI | 3GPPMEMBER |
Dr. | Choi | Woo-Jin | KT Corp. | TTA | 3GPPMEMBER |
Mr. | Chu | Ting-yi | III | ETSI | 3GPPMEMBER |
Mr. | Chuberre | Nicolas | THALES | ETSI | 3GPPMEMBER |
Mr. | Chun | SungDuck | LG Electronics France | ETSI | 3GPPMEMBER |
Mr. | Clemons | Peter | Quixoticity | ETSI | 3GPPMEMBER |
Mr. | Cong | Shi | Dongguan OPPO Precision Elec. | CCSA | 3GPPMEMBER |
Dr. | Corbett | Cherita | Johns Hopkins University APL | ATIS | 3GPPMEMBER |
Mr. | Courbon | Pierre | Ministère Economie et Finances | ETSI | 3GPPMEMBER |
Mr. | Dawes | Peter | Vodafone GmbH | ETSI | 3GPPMEMBER |
Mr. | Dawkins | Spencer | Tencent | CCSA | 3GPPMEMBER |
Mr. | Dees | Walter | Philips International B.V. | ETSI | 3GPPMEMBER |
Mr. | Deng | Qiang | CATT | CCSA | 3GPPMEMBER |
Mr. | Dewaele | Jo | A.S.T.R.I.D. S.A. | ETSI | 3GPPMEMBER |
Mr. | Dodd-noble | Aeneas | Cisco Systems France | ETSI | 3GPPMEMBER |
Dr. | Dolan | Michael | FirstNet | ATIS | 3GPPMEMBER |
Dr. | Dushchuluun | Khishigbayar | IRT | ETSI | 3GPPMEMBER |
Ms. | Ebrahim Rezagah | Roya | Fraunhofer HHI | ETSI | 3GPPMEMBER |
Mr. | EL KOLLI | Yacine | CANON Research Centre France | ETSI | 3GPPMEMBER |
Miss | EL MOUMOUHI | Sanaa | Eutelsat S.A. | ETSI | 3GPPMEMBER |
Mr. | elliott | simon | BBC | ETSI | 3GPPMEMBER |
Mr. | Evans | Tim P. | Vodafone Italia SpA | ETSI | 3GPPMEMBER |
Mr. | Everett | Jared | Johns Hopkins University APL | ATIS | 3GPPMEMBER |
Mr. | Ferrus | Ramon | Sateliot | ETSI | 3GPPMEMBER |
Mr. | fine | jean-yves | THALES | ETSI | 3GPPMEMBER |
Mr. | Firmin | Frederic | ETSI | ETSI | 3GPPORG_REP |
Mr. | Foldoy | Johan | Nkom | ETSI | 3GPPMEMBER |
Dr. | Fu | I-Kang | Shanghai Chen Si Electronics | CCSA | 3GPPMEMBER |
Dr. | Gaal | Peter | Qualcomm communications-France | ETSI | 3GPPMEMBER |
Mr. | Gabin | Frederic | Dolby Laboratories Inc. | ETSI | 3GPPMEMBER |
Mr. | Gach | Guillaume | Union Inter. Chemins de Fer | ETSI | 3GPPMEMBER |
Ms. | Galante | Maria Pia | TELECOM ITALIA S.p.A. | ETSI | 3GPPMEMBER |
Dr. | Gao | Qiubin | Datang Linktester Technology | CCSA | 3GPPMEMBER |
Mr. | Gao | Yang | ABP, NRTA | CCSA | 3GPPMEMBER |
Mr. | Gheorghiu | Valentin | Qualcomm India Pvt Ltd | TSDSI | 3GPPMEMBER |
Mr. | Goldberg | Martin | U.S. Department of Defense | ATIS | 3GPPMEMBER |
Mr. | Görmer | Gerald | Matrixx | ETSI | 3GPPMEMBER |
Mr. | Graves | Benoit | Orange Romania | ETSI | 3GPPMEMBER |
Mr. | Guirguis | Ihab | FirstNet | ATIS | 3GPPMEMBER |
Mr. | Gupta | Vivek | Intel Russia A/O | ETSI | 3GPPMEMBER |
Mr. | Guttman | Erik | Samsung Electronics GmbH | ETSI | 3GPPMEMBER |
Prof. | Han | Andrew Min-gyu | Hansung University | TTA | 3GPPMEMBER |
Mr. | Harper | Colby | Pivotal Commware | ATIS | 3GPPMEMBER |
Mr. | Hasegawa | Fumiki | Mitsubishi Electric Co. | ARIB | 3GPPMEMBER |
Mr. | Hawbaker | Tyler | OTD | ETSI | 3GPPMEMBER |
Mr. | Hayes | Stephen | Ericsson Inc. | ATIS | 3GPPMEMBER |
Mr. | Hédé | Patrice | Huawei Technologies R&D UK | ETSI | 3GPPMEMBER |
Mr. | Holley | Kevin | BT plc | ETSI | 3GPPMEMBER |
Mr. | Hong | Wei | Xiaomi Communications | CCSA | 3GPPMEMBER |
Mr. | Honma | Keita | Kyocera Corporation | ARIB | 3GPPMEMBER |
Mr. | Howell | Andrew | NCSC | ETSI | 3GPPMEMBER |
Ms. | Hu | Haijing | Apple Switzerland AG | ETSI | 3GPPMEMBER |
Mr. | Hwang | Chungwoo | KT Corp. | TTA | 3GPPMEMBER |
Mr. | Jain | Puneet | Intel | ATIS | 3GPPMEMBER |
Mr. | Janky | William | FirstNet | ATIS | 3GPPMEMBER |
Dr. | Jeong | Sangsoo | Samsung Electronics France SA | ETSI | 3GPPMEMBER |
Miss | Jerichow | Anja | Nokia Germany | ETSI | 3GPPMEMBER |
Mr. | Jo | Soonki | SK Telecom | TTA | 3GPPMEMBER |
Ms. | Kang | Yanchao | vivo Mobile Communication Co., | CCSA | 3GPPMEMBER |
Dr. | Karampatsis | Dimitrios | Lenovo Mobile Com. Technology | CCSA | 3GPPMEMBER |
Mr. | Kerry | Stuart | Ruckus | ETSI | 3GPPMEMBER |
Ms. | Kim | Eunah | ETRI | TTA | 3GPPMEMBER |
Dr. | Kim | Hyunsook | LG Electronics Inc. | TTA | 3GPPMEMBER |
Mr. | Kim | Jeong Yun | ETRI | TTA | 3GPPMEMBER |
Dr. | Kim | Joonwoong | SK Telecom | TTA | 3GPPMEMBER |
Dr. | Kim | Laeyoung | LG Electronics Inc. | TTA | 3GPPMEMBER |
Mr. | Kim | Soenghun | Samsung Research America | ATIS | 3GPPMEMBER |
Mr. | KIM | TaeHyun | SyncTechno Inc. | TTA | 3GPPMEMBER |
Dr. | Kim | Wuk | Samsung Electronics Romania | ETSI | 3GPPMEMBER |
Mr. | Kim | Youngbum | Harman GmbH | ETSI | 3GPPMEMBER |
Dr. | Kim | Youn-Kwan | SyncTechno Inc. | TTA | 3GPPMEMBER |
Dr. | Kim | Younsun | SAMSUNG R&D INSTITUTE JAPAN | ARIB | 3GPPMEMBER |
Mr. | Kim | Yunsung | LG Uplus | TTA | 3GPPMEMBER |
Dr. | Kimba | Boubacar | vivo Mobile Communication Co., | CCSA | 3GPPMEMBER |
Mr. | Kiss | Krisztian | Apple Hungary Kft. | ETSI | 3GPPMEMBER |
Mr. | Kitazoe | Masato | QUALCOMM JAPAN LLC. | ARIB | 3GPPMEMBER |
Mr. | Klatt | Axel | Telekom Deutschland GmbH | ETSI | 3GPPMEMBER |
Mr. | Koo | Eng Wei | ViaviSolutions Deutsch. GmbH | ETSI | 3GPPMEMBER |
Ms. | Koo | Hyounhee | SyncTechno Inc. | ETSI | 3GPPMEMBER |
Dr. | KORI | M H | TSDSI | TSDSI | 3GPPORG_REP |
Ms. | Koser | Elizabeth | U.S. Department of Defense | ATIS | 3GPPMEMBER |
Mr. | Kruse | Heiko | IDEMIA | ETSI | 3GPPMEMBER |
Mr. | Krzemienski | Pawel | HOME OFFICE | ETSI | 3GPPMEMBER |
Mr. | Kuchibhotla | Ravi | Motorola Mobility España SA | ETSI | 3GPPMEMBER |
Ms. | Kumar | Pamela | TSDSI | TSDSI | 3GPPORG_REP |
Mr. | Kymalainen | Kimmo | ETSI | ETSI | 3GPPORG_REP |
Mr. | Lagrange | Pascal | CANON Research Centre France | ETSI | 3GPPMEMBER |
Dr. | Lai | Chia-Lin | MediaTek (Chengdu) Inc. | CCSA | 3GPPMEMBER |
Mr. | Lair | Yannick | Nokia France | ETSI | 3GPPMEMBER |
Mr. | Larsson | Bo | Sony Europe B.V. | ETSI | 3GPPMEMBER |
Mr. | Leadbeater | Alex | BT plc | ETSI | 3GPPMEMBER |
Dr. | Lee | Brian | Dolby Laboratories Inc. | ETSI | 3GPPMEMBER |
Mr. | Lee | Juho | Samsung Electronics Iberia SA | ETSI | 3GPPMEMBER |
Dr. | Lee | Ki-Dong | LG Electronics Deutschland | ETSI | 3GPPMEMBER |
Mr. | Lee | Seungik | ETRI | TTA | 3GPPMEMBER |
Mr. | Lee | Soohwan | ETRI | TTA | 3GPPMEMBER |
Mr. | Lee | Youn-Tai | III | ETSI | 3GPPMEMBER |
Dr. | Lei | Yixue | Tencent | CCSA | 3GPPMEMBER |
Mr. | Leisse | Volker | CableLabs | ETSI | 3GPPMEMBER |
Mr. | Leung | Nikolai | Qualcomm Wireless GmbH | ETSI | 3GPPMEMBER |
Mr. | Li | He | HuaWei Technologies Co., Ltd | CCSA | 3GPPMEMBER |
Mr. | Li | Shuang | CBN | CCSA | 3GPPMEMBER |
Ms. | Liang | Jing | Datang Mobile Com. Equipment | CCSA | 3GPPMEMBER |
Mr. | Libunao | Gerardo | Verizon UK Ltd | ETSI | 3GPPMEMBER |
Mr. | Liebhart | Rainer | Nokia Germany | ETSI | 3GPPMEMBER |
Mrs. | Lim | Hanna | TTA | TTA | 3GPPORG_REP |
Mr. | lin | hao | OPPO | ETSI | 3GPPMEMBER |
Dr. | Lin | Kevin | Chengdu OPPO Mobile Com. corp. | CCSA | 3GPPMEMBER |
Ms. | Liu | Aijuan | Fiberhome Technologies Group | CCSA | 3GPPMEMBER |
Miss | Liu | Jianhua | Guangdong OPPO Mobile Telecom. | CCSA | 3GPPMEMBER |
Miss | Liu | Jiayifan | China Telecomunication Corp. | CCSA | 3GPPMEMBER |
Dr. | Liu | Yajian | Huawei Tech.(UK) Co., Ltd | ETSI | 3GPPMEMBER |
Mr. | Long | Biao | China Telecomunication Corp. | CCSA | 3GPPMEMBER |
Mr. | Long | Biao | China Telecomunication Corp. | CCSA | 3GPPMEMBER |
Mr. | Lopes | Luis | Qualcomm Technologies Int | ETSI | 3GPPMEMBER |
Mr. | Lorenzo | Casaccia | Qualcomm Austria RFFE GmbH | ETSI | 3GPPMEMBER |
Mr. | Lu | Fei | OnePlus | CCSA | 3GPPMEMBER |
Mr. | Luft | Achim | IPCom GmbH & Co.KG | ETSI | 3GPPMEMBER |
Mr. | Ma | Ruitao | China Unicom | CCSA | 3GPPMEMBER |
Mr. | Martin | Jesus | Telefonica Germany GmbH | ETSI | 3GPPMEMBER |
Mrs. | Masuda | Hiroyo | Fujitsu Limited | TTC | 3GPPMEMBER |
Mr. | Mayer | Georg | HUAWEI TECHNOLOGIES Co. Ltd. | ETSI | 3GPPMEMBER |
Mr. | Meredith | John M | ETSI | ETSI | 3GPPORG_REP |
Mr. | MICHEL | Cyril | THALES | ETSI | 3GPPMEMBER |
Mr. | Migaldi | Scott | T-Mobile USA Inc. | ATIS | 3GPPMEMBER |
Mr. | Minokuchi | Atsushi | NTT DOCOMO INC. | TTC | 3GPPMEMBER |
Mr. | Mittal | Ajay Kumar | TSDSI | TSDSI | 3GPPORG_REP |
Dr. | Montojo | Juan | QUALCOMM Europe Inc. - Spain | ETSI | 3GPPMEMBER |
Mr. | Morand | Lionel | Orange | ETSI | 3GPPMEMBER |
Dr. | Muhanna | Ahmad | Mavenir | ETSI | 3GPPMEMBER |
Mr. | Murphy | Andrew | BBC | ETSI | 3GPPMEMBER |
Ms. | Mustapha | Mona | Apple France | ETSI | 3GPPMEMBER |
Mr. | Mysore Annaiah | Mahesh Nayaka | Reliance Jio | TSDSI | 3GPPMEMBER |
Mr. | Nagata | Satoshi | NTT DOCOMO INC. | ARIB | 3GPPMEMBER |
Mr. | Nakamura | Kazuo | ARIB | ARIB | 3GPPORG_REP |
Mr. | Nakano | Yusuke | KDDI Corporation | ARIB | 3GPPMEMBER |
Mr. | Nakatogawa | Tsuyoshi | NHK | ARIB | 3GPPMEMBER |
Mr. | Ng | Chenghock | NEC Telecom MODUS Ltd. | ETSI | 3GPPMEMBER |
Mr. | Niemann | Bernhard | Fraunhofer IIS | ETSI | 3GPPMEMBER |
Mr. | Niemi | Marko | MediaTek Inc. | ETSI | 3GPPMEMBER |
Dr. | Nilsson | Ulf | Telia Company AB | ETSI | 3GPPMEMBER |
Dr. | Ning | Yang | Beijing OPPO Com. corp., ltd | CCSA | 3GPPMEMBER |
Mr. | Nord | Lars | Sony Europe B.V. | ETSI | 3GPPMEMBER |
Mr. | Norp | Toon | TNO | ETSI | 3GPPMEMBER |
Mr. | Norton | Mark | U.S. Department of Defense | ATIS | 3GPPMEMBER |
Mr. | Oettl | Martin | Nokia Corporation | ETSI | 3GPPMEMBER |
Dr. | OH | ChoongKeun | TTA | TTA | 3GPPORG_REP |
Mr. | Oh | Kyoungseok | TTA | TTA | 3GPPORG_REP |
Mr. | Ohtani | Jun | KDDI Corporation | TTC | 3GPPMEMBER |
Mr. | Oprescu | Val | AT&T | ATIS | 3GPPMEMBER |
Mr. | Ouyang | Guowei | HiSilicon Technologies Co. Ltd | CCSA | 3GPPMEMBER |
Dr. | Panaitopol | Dorin | THALES | ETSI | 3GPPMEMBER |
Mr. | Park | Sang Min | LG Electronics Finland | ETSI | 3GPPMEMBER |
Mr. | Pattan | Basavaraj (Basu) | Samsung R&D Institute UK | ETSI | 3GPPMEMBER |
Dr. | Perez Guirao | Maria Dolores | Sennheiser Electronic GmbH | ETSI | 3GPPMEMBER |
Mr. | Pesonen | Tero | Erillisverkot | ETSI | 3GPPMEMBER |
Mr. | Phan | Ly-Thanh | THALES | ETSI | 3GPPMEMBER |
Mr. | Pica | Francesco | Qualcomm CDMA Technologies | ETSI | 3GPPMEMBER |
Mr. | Pilz | Jens | Sennheiser Electronic GmbH | ETSI | 3GPPMEMBER |
Mr. | PIROARD | Francois | Airbus | ETSI | 3GPPMEMBER |
Dr. | Pittampalli | Eshwar | FirstNet | ATIS | 3GPPMEMBER |
Mr. | Poikselka | Miikka | Nokia Corporation | ETSI | 3GPPMEMBER |
Mr. | Pope | Maurice | ETSI | ETSI | 3GPPORG_REP |
Mr. | prakasam | sridhar | Apple (UK) Limited | ETSI | 3GPPMEMBER |
Mr. | Prochaska | Dean | FirstNet | ATIS | 3GPPMEMBER |
Mr. | Pudney | Chris | Vodafone Telekomünikasyon A.S. | ETSI | 3GPPMEMBER |
Dr. | QI | Tao | ZTE Photonics | CCSA | 3GPPMEMBER |
Mr. | Qiu | Haijie | Samsung Electronics Co., Ltd | TTA | 3GPPMEMBER |
Mrs. | Quan | Haiyang | Morningcore Technology Co.,Ltd | CCSA | 3GPPMEMBER |
Mr. | Rajadurai | Rajavelsamy | Samsung R&D Institute India | TSDSI | 3GPPMEMBER |
Mr. | Ram | Vishnu | TSDSI | TSDSI | 3GPPORG_REP |
Mr. | Rebellon | Manuel | Sandvine Incorporated | ETSI | 3GPPMEMBER |
Mr. | Rengasami | Selvam | OTD | ETSI | 3GPPMEMBER |
Dr. | Rico Alvarino | Alberto | QUALCOMM Europe Inc. - Italy | ETSI | 3GPPMEMBER |
Mr. | Rutkowski | Tony | CIS | ETSI | 3GPPMEMBER |
Miss | Sabater | Susana | VODAFONE Group Plc | ETSI | 3GPPMEMBER |
Mr. | Saboorian | Tony | Futurewei Technologies | ATIS | 3GPPMEMBER |
Mr. | Saha | Anindya | Saankhya Labs | TSDSI | 3GPPMEMBER |
Mr. | Sällberg | Krister | Ericsson GmbH, Eurolab | ETSI | 3GPPMEMBER |
Dr. | Savaglio | Frank | Telstra Corporation Limited | ETSI | 3GPPMEMBER |
Mr. | Schaffnit | Tom | U.S. Department of Transport. | ATIS | 3GPPMEMBER |
Mr. | Schmitz | Steffen | Volkswagen AG | ETSI | 3GPPMEMBER |
Mr. | Schumacher | Greg | T-Mobile USA | ETSI | 3GPPMEMBER |
Mr. | Sebire | Guillaume | MediaTek Inc. | ETSI | 3GPPMEMBER |
Dr. | Seibert | Cristina | NextNav | ATIS | 3GPPMEMBER |
Mr. | Shaikh | Viqar | Perspecta Labs Inc. | ATIS | 3GPPMEMBER |
Mr. | Sharp | Iain | ATIS | ATIS | 3GPPORG_REP |
Dr. | shen | chong | China Mobile Com. Corporation | CCSA | 3GPPMEMBER |
Mr. | Shen | Jia | Chongqing Angying | CCSA | 3GPPMEMBER |
Ms. | Shen | Yang | Beijing Xiaomi Mobile Software | CCSA | 3GPPMEMBER |
Dr. | SHI | Zhihua | Hangzhou Douku | CCSA | 3GPPMEMBER |
Mr. | Shieh | Shinlin | III | ETSI | 3GPPMEMBER |
Dr. | Shin | MyungKi | ETRI | TTA | 3GPPMEMBER |
Mr. | Shu | Lin | Huawei Device Co., Ltd | CCSA | 3GPPMEMBER |
Dr. | Shyy | DJ | MITRE Corporation | ETSI | 3GPPMEMBER |
Mr. | Singh | Ray | Perspecta Labs Inc. | ATIS | 3GPPMEMBER |
Miss | So | Tricci | ZTE Wistron Telecom AB | ETSI | 3GPPMEMBER |
Mr. | Soloway | Alan | Qualcomm Finland RFFE Oy | ETSI | 3GPPMEMBER |
Miss | Song | Yuexia | GOHIGH DATA NETWORKS TECH. | CCSA | 3GPPMEMBER |
Dr. | Soomro | Amjad | U.S. Department of Defense | ATIS | 3GPPMEMBER |
Mr. | Starsinic | Michael | Convida Wireless | ETSI | 3GPPMEMBER |
Mr. | Stojanovski | Saso | Intel Russia A/O | ETSI | 3GPPMEMBER |
Mr. | Streijl | Robert | Perspecta Labs Inc. | ATIS | 3GPPMEMBER |
Ms. | Suh | Kyungjoo Grace | Samsung Electronics Polska | ETSI | 3GPPMEMBER |
Mr. | Sultan | Alain | ETSI | ETSI | 3GPPORG_REP |
Miss | Sultana | Shabnam | Ericsson Inc. | ATIS | 3GPPMEMBER |
Dr. | Sun | Feifei | Samsung Electronics Polska | ETSI | 3GPPMEMBER |
Mr. | Suzuki | Kunikazu | DENSO CORPORATION | ARIB | 3GPPMEMBER |
Dr. | Taira | Akinori | Mitsubishi Electric Co. | ARIB | 3GPPMEMBER |
Mr. | Takada | Terufumi | DENSO CORPORATION | ARIB | 3GPPMEMBER |
Mr. | Tamura | Toshiyuki | NEC Corporation | TTC | 3GPPMEMBER |
Mr. | Tangudu | Narendranath Durga | Samsung Electronics Iberia SA | ETSI | 3GPPMEMBER |
Mr. | Teniou | Gilles | Tencent | CCSA | 3GPPMEMBER |
Mr. | Thalanany | Sebastian | US Cellular Corporation | ETSI | 3GPPMEMBER |
Mr. | Thiessen | Andrew | NTIA | ATIS | 3GPPMEMBER |
Mrs. | Thorpe-Taylor | Carol-lyn | CISA ECD | ATIS | 3GPPMEMBER |
Mr. | Todorovic | Goran | BOUYGUES Telecom | ETSI | 3GPPMEMBER |
Mr. | Toufik | Issam | ETSI | ETSI | 3GPPORG_REP |
Mr. | Tovinger | Thomas | Ericsson LM | ETSI | 3GPPMEMBER |
Dr. | Tsai | Yi-Hsueh | III | ETSI | 3GPPMEMBER |
Mr. | Tsang kwong u | Steve | Orange Spain | ETSI | 3GPPMEMBER |
Mr. | Tsuda | Shinichiro | Sony Corporation | ARIB | 3GPPMEMBER |
Mr. | van der Veen | Hans | NEC Corporation | ARIB | 3GPPMEMBER |
Dr. | Vargas | David | BBC | ETSI | 3GPPMEMBER |
Mr. | Velev | Genadi | Motorola Mobility Germany GmbH | ETSI | 3GPPMEMBER |
Mr. | Vibhuti | Anurag | TSDSI | TSDSI | 3GPPORG_REP |
Mr. | Vintola | Ville | Qualcomm Tech. Netherlands B.V | ETSI | 3GPPMEMBER |
Mr. | Vogedes | Jerome | Omnispace | ATIS | 3GPPMEMBER |
Mr. | Vucetic | Vojislav | Infoblox | ETSI | 3GPPMEMBER |
Dr. | Walewski | Joachim | Siemens AG | ETSI | 3GPPMEMBER |
Dr. | Wan | Tao | CableLabs | ETSI | 3GPPMEMBER |
Dr. | Wang | Feiei | CUC | CCSA | 3GPPMEMBER |
Dr. | Wang | Hucheng | CATT | CCSA | 3GPPMEMBER |
Mr. | Wang | Ke | CICT | CCSA | 3GPPMEMBER |
Mr. | Wendler | Ingo | Union Inter. Chemins de Fer | ETSI | 3GPPMEMBER |
Mr. | Werner | Benjamin | OTD | ETSI | 3GPPMEMBER |
Mr. | Wild | Peter A. | Vodafone GmbH | ETSI | 3GPPMEMBER |
Mr. | Wong | Curt | Charter Communications, Inc | ATIS | 3GPPMEMBER |
Mr. | Woodward | Tim | Motorola Solutions Danmark A/S | ETSI | 3GPPMEMBER |
Mr. | Xiaodong | Xu | China Mobile E-Commerce Co. | CCSA | 3GPPMEMBER |
Mr. | Xiong | Chunshan | Tencent | CCSA | 3GPPMEMBER |
Miss | Xu | Hui | CICT | CCSA | 3GPPMEMBER |
Ms. | Xu | Lixiang | Samsung Guangzhou Mobile R&D | CCSA | 3GPPMEMBER |
Mr. | YANG | DELONG | CEPRI | CCSA | 3GPPMEMBER |
Mr. | Yang | Xiaodong | vivo Mobile Communication Co., | CCSA | 3GPPMEMBER |
Mr. | Yeo | Jeongho | Samsung Electronics Nordic AB | ETSI | 3GPPMEMBER |
Mr. | Yokota | Daisuke | SoftBank Corp. | ARIB | 3GPPMEMBER |
Mr. | Youn | Myungjune | LG Electronics France | ETSI | 3GPPMEMBER |
Mr. | Younge | Mark | T-Mobile USA Inc. | ATIS | 3GPPMEMBER |
Dr. | Yu | Tsang-wei | MediaTek (Shenzhen) Inc. | CCSA | 3GPPMEMBER |
Mr. | Yuda | Tetsuya | Kyocera Corporation | ARIB | 3GPPMEMBER |
Mr. | Zelmer | Donald E. | AT&T | ATIS | 3GPPMEMBER |
Mr. | Zhang | Wanqiang | HuaWei Technologies Co., Ltd | CCSA | 3GPPMEMBER |
Dr. | ZHANG | Yu | ABS | CCSA | 3GPPMEMBER |
Dr. | Zhang | Zhuoyun | Tencent | CCSA | 3GPPMEMBER |
Dr. | Zhao | Shuai | Tencent | CCSA | 3GPPMEMBER |
Dr. | ZHAO | XIAOWU | ZTE Corporation | CCSA | 3GPPMEMBER |
Mr. | Zhou | Xutao | BEIJING SAMSUNG TELECOM R&D | CCSA | 3GPPMEMBER |
Mr. | Zhu | Chunhui | Spreadtrum Communications | CCSA | 3GPPMEMBER |
Mr. | Zhu | Fenqin | HuaWei Technologies Co., Ltd | CCSA | 3GPPMEMBER |
Mr. | Zhu | Jinguo | ZTE Corporation | CCSA | 3GPPMEMBER |
Mrs. | Zhu | Wenruo | HUAWEI TECH. GmbH | ETSI | 3GPPMEMBER |
Mr. | Zisimopoulos | Haris | Qualcomm Korea | TTA | 3GPPMEMBER |
Ms. | Zou | Lan | Huawei Tech.(UK) Co., Ltd | ETSI | 3GPPMEMBER |
Mr. | Zuo | Zhisong | Shenzhen YZF Network Technolog | CCSA | 3GPPMEMBER |
Annex D Incoming and Outgoing Liaison Statements
D.1 Incoming LSs
TD# | LS_From | Title | LS_Source_file | To | CC | Attachments | ResponseTD | Decision |
SP-200634 | IALA | LS from IALA: Liaison Note to TSG SA - Request for information | C71-11.5.1 | TSG SA | SP-200877 | Replied to | ||
SP-200635 | ITU-R WP 5D | LS from ITU-R WP 5D: LIAISON STATEMENT TO RIT/SRIT PROPONENTS ON THE COMPLETION AND CONCLUSIONS OF STEPS 5 TO 7 OF THE IMT-2020 PROCESS FOR THE FIRST RELEASE OF NEW RECOMMENDATION ITU-R M.[IMT-2020.SPECS] | 5D_TD_159R1 | 3GPP Proponents, ETSI TC DECT, DECT Forum | GCS Proponents | Attachment 1, Draft_new_Rec M.[IMT-2020.SPECS] | Noted | |
SP-200636 | ITU-R WP5D | LS from ITU-R WP5D: LIAISON STATEMENT TO TRANSPOSING ORGANIZATIONS ON THE COMPLETION OF STEP 8 OF IMT-2020 PROCESS FOR THE FIRST RELEASE OF NEW RECOMMENDATION ITU-R M.[IMT-2020.SPECS] | 5D_TD_163R1e_IMT-2020. | 3GPP SDOs | RIT/SRIT PROPONENTS | Attachment 1, Draft_new_Rec M.[IMT-2020.SPECS] | Noted | |
SP-200637 | ETSI ISG E4P | LS from ETSI ISG E4P: Request for information exchange | E4P(20)000_022 | Bluetooth SIG, TSG SA, GSMA TSG | ISG_E4P_Introduction_Pandemic_Tracing.pptx | Noted | ||
SP-200638 | ITU-T JCA-IMT2020 | LS from ITU-T JCA-IMT2020: LS on Invitation to update the information in the IMT2020 roadmap | JCA-IMT2020-O-015-R1_LS08 | ITU-T SGs, External IMT-2020 liaison partners | SP-200887 | Replied to | ||
SP-200639 | TM Forum Autonomous Networks | LS from TM Forum Autonomous Networks: Introduction of TM Forum Autonomous Network project and Coordination Proposal | Liaison AN results ETSI GSMA 3GPPv2 | ETSI, SA WG5, GSMA, NGMN, CCSA TC7 | TSG SA | 22553 whitepaper, IG1193, IG1218 | Noted | |
SP-200640 | IETF | LS from IETF: Re: LS on need for Multi-Path QUIC for ATSSS | LS_from_IETF | TSG SA | SA WG2 | Noted | ||
SP-200641 | IETF DRIP | LS from IETF DRIP: Drone Remote ID Protocol Working Group (DRIP) | LSs_from_IETF_9June2020 | 3GPP | Noted | |||
SP-200642 | ITU-R WP5A | LS from ITU-R WP5A: LIAISON STATEMENT TO EXTERNAL ORGANIZATIONS ON ITS Connected Automated Vehicles (CAV) | 5A_TEMP_29_R1 | EXTERNAL | R19-WP5A-C-0085!N16!MSW-E | Noted | ||
SP-200643 | TSG RAN | LS from TSG RAN: Reply LS to RP-200030 on relevant 3GPP Specs for PC5 Sidelink | RP-201285 | 5GAA WG4 | TSG SA | RP-200679 | Noted | |
SP-200644 | TSG RAN | LS from TSG RAN: Reply LS to GSMA_5GSI_28_Doc003 = RP-193053 on 5G indicator enhancement | RP-201358 | GSMA Network Group (NG) | TSG SA, TSG CT | R2-2006081 | Noted | |
SP-200645 | ITU-T SG13 | LS from ITU-T SG13: LS/o on information about consent of Machine Learning related ITU-T Recommendation Y.3176 | SG13-LS160 | ITU SGs, TSG SA, ETSI ISG ENI, IETF NMRG, ISO/IEC JTC1/SC42, ISO/IEC JTC1/SC29, NGMN | Noted | |||
SP-200646 | TM Forum | LS from TM Forum: TM Forum implementation experiences 3GPP NRM Models | Liaison 3GPP SA5 TM Forum SID and NRM Models | TSG SA, SA WG5 | IG1217, IG1211 | Noted | ||
SP-200647 | SA WG2 | LS from SA WG2: LS on mandatory support of full rate user plane integrity protection for 5G | S2-2006181 | TSG SA | CT WG1, SA WG3, RAN WG2, RAN WG3, TSG RAN, TSG CT | TS 23.501 CR 2400, TS 23.502 CR 2341 | Noted | |
SP-200648 | CT WG1 | LS on mandatory support of full rate user plane integrity protection for 5G | C1-205392 | TSG SA | TSG CT, TSG RAN, RAN WG3, RAN WG2, SA WG3, SA WG2 | C1-205294 | Noted | |
SP-200649 | CT WG4 | LS from CT WG4: LS on AUSF/UDM discovery based on SUCI information | C4-204337 | SA WG2 | TSG CT, TSG SA, SA WG3 | C4-204078, C4-204339 | Noted | |
SP-200650 | RAN WG2 | LS from RAN WG2: Response LS to TSG SA on mandatory support of full rate user plane integrity protection for 5G | R2-2008643 | TSG SA, CT WG1, SA WG2, SA WG3, TSG CT, TSG RAN | RAN WG3 | Noted | ||
SP-200651 | RAN WG3 | LS from RAN WG3: Reply LS on mandatory support of full rate user plane integrity protection for 5G | R3-205653 | TSG SA, TSG RAN, TSG CT, CT WG1, SA WG2, SA WG3, RAN WG2 | Noted | |||
SP-200652 | SA WG2 | LS from SA WG2: LS on RAN impact of FS_5MBS Study | S2-2006044 | TSG SA, TSG RAN, RAN WG2, RAN WG3 | TR 23.757 v0.4.0 (version before SA2#140e) | SP-200884 | Replied to | |
SP-200653 | SA WG5 | LS from SA WG5: LS reply to LS on M.resm-AI “Requirements for energy saving management of 5G RAN system with AI” | S5-204516 | ITU-T Q5/2 | 3GPP SA, 3GPP RAN3, ITU-R WP 5D | Noted | ||
SP-200654 | CT WG1 | LS from CT WG1: LS on the stage 2 aspects of MINT | C1-205332 | TSG SA | TSG CT, SA WG2, SA WG3, CT WG3, CT WG4 | SP-200880 | Replied to | |
SP-200779 | TSG RAN ITU AH | LS from TSG RAN ITU AH: Draft Letter to ITU - Response LS on 3GPP's activities related to WRC-19 Resolutions | RT-200037 | TSG RAN | TSG SA | Noted | ||
SP-200780 | TSG RAN ITU AH | LS from TSG RAN ITU AH: DRAFT LTI - answer to ITU-R WP5A LS on CONNECTED AUTOMATED VEHICLES (CAV) | RT-200039 | TSG RAN | TSG SA | Noted | ||
SP-200781 | TSG RAN ITU AH | LS from TSG RAN ITU AH: DRAFT LTI - answer to ITU-R WP5D LS on DEVEOPMENT OF DRAFT NEW RPORT ITU-R.M[IMT.C-V2X] - APPLICATION OF THE TERRESTRIAL COMPONENT OF IMT FOR CELLULAR-V2X | RT-200040 | TSG RAN | TSG SA | Noted | ||
SP-200782 | TSG RAN ITU AH | LS from TSG RAN ITU AH: Draft Letter to ITU in reply to ITU_R_WP5D_TEMP_39 = RP-200037 on update submission for LTE-Advanced towards Revision 5 of Recommendation ITU-R M.2012 | RT-200041 | TSG RAN | TSG SA | 21915-f00.zip, 21916-050.zip | Noted | |
SP-200783 | TSG RAN ITU AH | LS from TSG RAN ITU AH: Draft Letter to ITU in answer to LS to RIT/SRIT Proponents on the completion and conclusions of steps 5 to 7 of the IMT-2020 process for the first release of new Recommendation ITU-R M.[IMT-2020.SPECS] | RT-200042 | TSG RAN | TSG SA | Noted | ||
SP-200861 | TSG CT | LS from TSG CT: LS on information of stage 3 aspects for AKMA | CP-202255 | TSG SA, SA WG3 | CT WG1, CT WG3, CT WG4, CT WG6 | AKMA-CT WID | Noted | |
SP-200863 | TSG RAN | LS from TSG RAN: Draft Letter to ITU - Response LS on 3GPP’s activities related to WRC-19 Resolutions | RP-202054 | PCG | TSG SA | Noted | ||
SP-200864 | TSG RAN | LS from TSG RAN: DRAFT LTI - answer to ITU-R WP5D LS on DEVEOPMENT OF DRAFT NEW RPORT ITU-R.M[IMT.C-V2X] – APPLICATION OF THE TERRESTRIAL COMPONENT OF IMT FOR CELLULAR-V2X | RP-202055 | TSG SA | Endorsed | |||
SP-200865 | TSG RAN | LS from TSG RAN: Draft Letter to ITU in reply to ITU_R_WP5D_TEMP_39 = RP-200037 on update submission for LTE-Advanced towards Revision 5 of Recommendation ITU-R M.2012 | RP-202056 | TSG SA | 21915-f00.zip, 21916-050.zip | Endorsed | ||
SP-200866 | TSG RAN | LS from TSG RAN: DRAFT LTI - answer to ITU-R WP5A LS on CONNECTED AUTOMATED VEHICLES (CAV) | RP-202057 | TSG SA | Endorsed | |||
SP-200867 | TSG RAN | LS from TSG RAN: Draft Letter to ITU in answer to LS to RIT/SRIT Proponents on the completion and conclusions of steps 5 to 7 of the IMT-2020 process for the first release of new Recommendation ITU-R M.[IMT-2020.SPECS] | RP-202058 | TSG SA | Endorsed | |||
SP-200868 | TSG RAN | LS from TSG RAN: LS on Relaxation of mini-WID requirement for Cat.B/C TEI CRs | RP-202001 | TSG SA | RP-201291 | Postponed | ||
SP-200871 | TSG RAN | LS from TSG RAN: Reply LS on RAN impact of FS_5MBS Study | RP-202086 | TSG SA, SA WG2 | RAN WG2, RAN WG3 | Noted |
D.2 Outgoing LSs
TD# | Title | To | CC | Attachments | Response to TD | Decision |
SP-200873 | LS to PCG: DRAFT LTI - answer to ITU-R WP5D LS on DEVEOPMENT OF DRAFT NEW RPORT ITU-R.M[IMT.C-V2X] – APPLICATION OF THE TERRESTRIAL COMPONENT OF IMT FOR CELLULAR-V2X | PCG | Approved | |||
SP-200874 | LS to PCG: Draft Letter to ITU in reply to ITU_R_WP5D_TEMP_39 = RP-200037 on update submission for LTE-Advanced towards Revision 5 of Recommendation ITU-R M.2012 | PCG | 21915-f00.zip, 21916-050.zip | Approved | ||
SP-200875 | LS to PCG: DRAFT LTI - answer to ITU-R WP5A LS on CONNECTED AUTOMATED VEHICLES (CAV) | PCG | Approved | |||
SP-200876 | LS to PCG: Draft Letter to ITU in answer to LS to RIT/SRIT Proponents on the completion and conclusions of steps 5 to 7 of the IMT-2020 process for the first release of new Recommendation ITU-R M.[IMT-2020.SPECS] | PCG | Approved | |||
SP-200877 | Reply LS on request for information from IALA | IALA, SA WG1 | SP-200634 (C71-11.5.1) | Approved | ||
SP-200880 | Reply LS on the stage 2 aspects of MINT | CT WG1 | TSG CT, SA WG2, SA WG3, CT WG3, CT WG4 | SP-200654 (C1-205332) | Approved | |
SP-200883 | LS on 5G GUTI re-allocation | SA WG2, SA WG3, CT WG1 | TSG CT | Approved | ||
SP-200884 | Reply LS on RAN impact of FS_5MBS Study | TSG RAN, SA WG2 | RAN WG2, RAN WG3 | SP-200652 (S2-2006044) | Approved | |
SP-200887 | Reply to LS on Invitation to update the information in the IMT2020 roadmap | ITU-T JCA-IMT2020 | SP-200638 (JCA-IMT2020-O-015-R1_LS08) | Approved | ||
SP-200888 | LS on Rel-17 schedule | SA WG1, SA WG2, SA WG3, SA WG4, SA WG5, SA WG6, TSG CT | TSG RAN | Approved |
Annex E TS, TR, WID, SID and CR Lists
E.1 List of newly approved TSs and TRs
TD# | Type | Title | Specification | Ver | Source | WI Code | Comment | Decision |
SP-200666 | DRAFT TS | Draft TS 26.512: 5G Media Streaming (5GMS); Protocols | 26.512 | - | SA WG4 | 5GMS3 | This was Block approved in CC#3 | Approved |
SP-200756 | DRAFT TR | Draft TR 28.812 'Study on scenarios for Intent driven management services for mobile networks' | 28.812 | - | SA WG5 | IDMS_MN | This was Block approved in CC#3 | Approved |
SP-200757 | DRAFT TS | Draft TS 28.309 'Management of Quality of Experience (QoE) measurement collection Integration Reference Point (IRP); Solution Set (SS) definitions' | 28.309 | - | SA WG5 | QOED | This was Block approved in CC#3 | Approved |
SP-200758 | DRAFT TS | Draft TS 28.313 'Study on new aspects of Energy Efficiency (EE) for 5G' | 28.313 | - | SA WG5 | SON_5G | This was Block approved in CC#3 | Approved |
SP-200759 | DRAFT TR | Draft TR 28.810 'Study on concept, requirements and solutions for levels of autonomous network' | 28.810 | - | SA WG5 | FS_ANL | This was Block approved in CC#3 | Approved |
SP-200760 | DRAFT TS | Draft TS 28.201 'Network slice performance and analytics charging in the 5G System (5GS); Stage 2' | 28.201 | - | SA WG5 | 5GS_NSPACH | This was Block approved in CC#3 | Approved |
SP-200761 | DRAFT TS | Draft TS 28.202 'Network slice management charging in the 5G System (5GS); Stage 2' | 28.202 | - | SA WG5 | 5GS_NSMCH | This was Block approved in CC#3 | Approved |
SP-200826 | DRAFT TS | Presentation of TS 23.180 v2.0.0 for approval | 23.180 | - | SA WG6 | MCIOPS | This was Block approved in CC#3 | Approved |
SP-200827 | DRAFT TR | Presentation of TR 23.764 v2.0.0 for approval | 23.764 | - | SA WG6 | FS_eV2XAPP | This was Block approved in CC#3 | Approved |
E.2 List of TSs and TRs presented for information
TD# | Type | Title | Specification | Ver | Source | WI Code | Comment | Decision |
SP-200691 | DRAFT TR | Presentation of TR 23.748 for information to TSG SA (FS_enh_EC) | 23.748 | - | SA WG2 | FS_enh_EC | This was block noted in CC#3 | Noted |
SP-200692 | DRAFT TR | Presentation of TR 23.700-20 for information to TSG SA (FS_IIoT) | 23.700-20 | - | SA WG2 | FS_IIoT | This was block noted in CC#3 | Noted |
SP-200693 | DRAFT TR | Presentation of TR 23.761 for information to TSG SA (FS_MUSIM) | 23.761 | - | SA WG2 | FS_MUSIM | This was block noted in CC#3 | Noted |
SP-200694 | DRAFT TR | Presentation of TR 23.700-91 for Information to TSG SA (FS_eNA_Ph2) | 23.700-91 | - | SA WG2 | FS_eNA_Ph2 | This was block noted in CC#3 | Noted |
SP-200695 | DRAFT TR | Presentation of presentation of TR 23.700-07 for information to TSG SA (FS_eNPN) | 23.700-07 | - | SA WG2 | FS_eNPN | This was block noted in CC#3 | Noted |
SP-200696 | DRAFT TR | Presentation of TR 23.757 for information to TSG SA (FS_5MBS) | 23.757 | - | SA WG2 | FS_5MBS | This was block noted in CC#3 | Noted |
SP-200698 | DRAFT TR | Presentation of TR 23.700-40 to TSG SA for information (FS_eNS_Ph2) | 23.700-40 | - | SA WG2 | FS_eNS_Ph2 | This was block noted in CC#3 | Noted |
SP-200699 | DRAFT TR | Presentation of TR 23.700-93 to TSG SA for information (FS_ATSSS_Ph2) | 23.700-93 | - | SA WG2 | FS_ATSSS_Ph2 | This was block noted in CC#3 | Noted |
SP-200700 | DRAFT TR | Presentation of TR 23.754 for information to TSG SA (FS_ID_UAS_SA2) | 23.754 | - | SA WG2 | FS_ID_UAS_SA2 | This was block noted in CC#3 | Noted |
SP-200755 | DRAFT TR | Draft TR 28.809 'Study on enhancement of management data analytics' | 28.809 | - | SA WG5 | FS_eMDAS | This was block noted in CC#3 | Noted |
SP-200820 | DRAFT TS | Draft TS 28.555 'Network policy management for 5G mobile networks; Stage 1' | 28.555 | - | SA WG5 | NPM | Revision of SP-200762. Noted | Noted |
SP-200824 | DRAFT TR | TR 21.916 v.0.6.0 on Rel-16 Summary | 21.916 | - | Work Plan Coordinator (MCC) | TEI16 | This was Block noted in CC#3 | Noted |
SP-200828 | DRAFT TS | Presentation of TS 23.558 v1.0.0 for information | 23.558 | - | SA WG6 | EDGEAPP | This was block noted in CC#3 | Noted |
SP-200829 | DRAFT TR | Presentation of TR 23.745 v1.0.0 for information | 23.745 | - | SA WG6 | FS_FFAPP | This was block noted in CC#3 | Noted |
SP-200830 | DRAFT TR | Presentation of TR 23.700-24 v1.0.0 for information | 23.700-24 | - | SA WG6 | FS_5GMARCH | This was block noted in CC#3 | Noted |
E.3 List of Approved CR Packs
TD# | Subject | Source | Comment | Status |
SP-200714 | Rel-13 CRs on Enhancements to WEBRTC interoperability | SA WG3 | This was Block approved in CC#3 | Approved |
SP-200744 | Rel-16 CRs on Management of MDT in 5G | SA WG5 | This was Block approved in CC#3 | Approved |
SP-200732 | Rel-16 CRs on Self-Organizing Networks (SON) for 5G networks | SA WG5 | This was Block approved in CC#3 | Approved |
SP-200772 | Rel-17 CRs on Mission critical security enhancements phase 2 | SA WG3 | This was Block approved in CC#3 | Approved |
SP-200754 | Rel-16 CRs on Management Aspects of 5G Service-Level Agreement | SA WG5 | This was Block approved in CC#3 | Approved |
SP-200753 | Rel-16 CRs on Trace Management in the context of Services Based Management Architecture | SA WG5 | This was Block approved in CC#3 | Approved |
SP-200752 | Rel-17 CRs on Enhancements of Self-Organizing Networks (SON) for 5G networks | SA WG5 | This was Block approved in CC#3 | Approved |
SP-200751 | Rel-16 CRs on KPI reporting | SA WG5 | This was Block approved in CC#3 | Approved |
SP-200750 | Rel-16 CRs on Closed loop SLS Assurance | SA WG5 | This was Block approved in CC#3 | Approved |
SP-200749 | Rel-17 CRs on Enhancement on Management Aspects of 5G Service-Level Agreement | SA WG5 | This was Block approved in CC#3 | Approved |
SP-200748 | Rel-17 CRs on Additional NRM features | SA WG5 | This was Block approved in CC#3 | Approved |
SP-200747 | Rel-17 CRs on Enhancements of 5G performance measurements and KPIs | SA WG5 | This was Block approved in CC#3 | Approved |
SP-200784 | Stage 1 CRs on cyberCAV | SA WG1 | CC#3: 22.104 CR0054r1 and 22.261 CR0464 removed from the pack for further discussion (postponed). The other CRs in this CR Pack were approved. (This CR Pack was partially approved). | Partially approved |
SP-200745 | Rel-16 CRs on Network Slice Management Charging in 5G System | SA WG5 | This was Block approved in CC#3 | Approved |
SP-200813 | REl-16 CRs on TEI batch 2 | SA WG5 | This was Block approved in CC#3 | Approved |
SP-200743 | Rel-16 CRs on Network Slice Performance and Analytics Charging in 5G System | SA WG5 | This was Block approved in CC#3 | Approved |
SP-200742 | Rel-15 CRs on Service Based Interface for 5G Charging | SA WG5 | This was Block approved in CC#3 | Approved |
SP-200741 | Rel-16 CRs on CHF-controlled quota management | SA WG5 | This was Block approved in CC#3 | Approved |
SP-200740 | Rel-16 CRs on Charging Enhancement of 5GC interworking with EPC | SA WG5 | This was Block approved in CC#3 | Approved |
SP-200738 | Rel-16 CRs on Enhancement of performance assurance for 5G networks including network slicing batch 1 | SA WG5 | This was Block approved in CC#3 | Approved |
SP-200737 | Rel-16 CRs on Integration of ONAP and 3GPP 5G management framework | SA WG5 | This was Block approved in CC#3 | Approved |
SP-200736 | Rel-15 CRs on Management and orchestration of 5G networks and network slicing | SA WG5 | This was Block approved in CC#3 | Approved |
SP-200735 | Rel-15 CRs on Provisioning of network slicing for 5G networks and services | SA WG5 | This was Block approved in CC#3 | Approved |
SP-200734 | Rel-16 CRs on Energy efficiency of 5G | SA WG5 | This was Block approved in CC#3 | Approved |
SP-200712 | Rel-16 CRs onStudy on Security Aspects of the 5G Service Based Architecture | SA WG3 | This was Block approved in CC#3 | Approved |
SP-200746 | Rel-17 CRs on Management of MDT enhancement in 5G | SA WG5 | This was Block approved in CC#3 | Approved |
SP-200807 | Rel-16 CRs on Lawful Interception | SA WG3-LI | This was Block approved in CC#3 | Approved |
SP-200846 | Rel-17 CRs to TS 23.281 and TS 23.283 for TEI17 | SA WG6 | This was Block approved in CC#3 | Approved |
SP-200845 | Rel-17 CRs to TS 23.282 for eMCData3 | SA WG6 | This was Block approved in CC#3 | Approved |
SP-200844 | Rel-17 CRs to TS 23.280 and TS 23.379 for enh3MCPTT | SA WG6 | This was Block approved in CC#3 | Approved |
SP-200843 | Rel-17 CRs to TS 23.280, TS 23.281, TS 23.282 and TS 23.379 for eMONASTERY2 | SA WG6 | This was Block approved in CC#3 | Approved |
SP-200842 | Rel-16 CRs to TS 23.286 for V2XAPP | SA WG6 | This was Block approved in CC#3 | Approved |
SP-200841 | Rel-16 CRs to TS 23.434 for SEAL | SA WG6 | This was Block approved in CC#3 | Approved |
SP-200840 | Rel-16 CRs to TS 23.222 for eCAPIF | SA WG6 | This was Block approved in CC#3 | Approved |
SP-200839 | Rel-16 CRs to TS 23.282 for eMCData2 | SA WG6 | This was Block approved in CC#3 | Approved |
SP-200838 | Rel-16 CRs to TS 23.283 for eMCCI | SA WG6 | This was Block approved in CC#3 | Approved |
SP-200818 | Stage 1 CRs on SNA | SA WG1 | This was Block approved in CC#3 | Approved |
SP-200773 | Rel-15 CRs on Security aspects of 5G System - Phase 1 Batch 2 | SA WG3 | This was Block approved in CC#3 | Approved |
SP-200816 | Rel-16 CRs on Charging Aspects for 5WWC | SA WG5 | This was Block approved in CC#3 | Approved |
SP-200731 | Rel-15 CRs on Performance Assurance for 5G networks including network slicing | SA WG5 | This was Block approved in CC#3 | Approved |
SP-200806 | Rel-15 CRs on Lawful Interception | SA WG3-LI | This was Block approved in CC#3 | Approved |
SP-200804 | CRs to RM_H263_MP4V (postponed from SA#88-e) | SA WG4 | These CRs were postponed from SA#88-e. This was Block approved in CC#3 | Approved |
SP-200794 | Stage 1 CRs on TEI17 | SA WG1 | This was Block approved in CC#3 | Approved |
SP-200792 | Stage 1 CRs on AVPROD | SA WG1 | This was Block approved in CC#3 | Approved |
SP-200790 | Stage 1 CRs on eCAV | SA WG1 | CC#4: 22.261 CR0462R2 revised in SP-200869. 22.104 0053r1 and 22.261 0465r1 were postponed. The other CRs in this CR pack were approved | Partially approved |
SP-200789 | Stage 1 CRs on TEI16 | SA WG1 | This was Block approved in CC#3 | Approved |
SP-200788 | Stage 1 CRs on UIA | SA WG1 | This was Block approved in CC#3 | Approved |
SP-200787 | Stage 1 CRs on 5GSAT | SA WG1 | This was Block approved in CC#3 | Approved |
SP-200786 | Stage 1 CRs on MARCOM | SA WG1 | This was Block approved in CC#3 | Approved |
SP-200785 | Stage 1 CRs on REAR | SA WG1 | This was Block approved in CC#3 | Approved |
SP-200817 | REl-16 CRs on Nchf Online and Offline charging services | SA WG5 | This was Block approved in CC#3 | Approved |
SP-200674 | CRs to 23.501, 23.502 on 5G_eSBA (Rel-16) | SA WG2 | This was Block approved in CC#3 | Approved |
SP-200733 | Rel-16 CRs on Charging Access of ATSSS | SA WG5 | This was Block approved in CC#3 | Approved |
SP-200685 | CRs to 23.401, 23.502 on RACS (Rel-16) | SA WG2 | Company proposed revision of 23.501 CR2383R1 in SP-200802. CC#1: 23.501 CR2383R1 was considered as revised and other CRs in this CR pack were approved. | Partially approved |
SP-200684 | CR to 23.401 on PARLOS (Rel-16) | SA WG2 | This was Block approved in CC#3 | Approved |
SP-200683 | CR to 23.501 on IABARC (Rel-16) | SA WG2 | This was Block approved in CC#3 | Approved |
SP-200682 | CRs to 23.285, 23.287, 23.502, 23.503 on eV2XARC (Rel-16) | SA WG2 | This was Block approved in CC#3 | Approved |
SP-200681 | CRs to 23.502 on ETSUN (Rel-16) | SA WG2 | This was Block approved in CC#3 | Approved |
SP-200680 | CRs to 23.502 on eNS (Rel-16) | SA WG2 | This was Block approved in CC#3 | Approved |
SP-200679 | CRs to 23.228, 23.502, 23.503 on eNA (Rel-16) | SA WG2 | This was Block approved in CC#3 | Approved |
SP-200678 | CRs to 23.228, 23.501 on eIMS5G_SBA (Rel-16) | SA WG2 | This was Block approved in CC#3 | Approved |
SP-200677 | CR to 23.501 on ATSSS (Rel-16) | SA WG2 | This was Block approved in CC#3 | Approved |
SP-200687 | CR to 23.501 on UDICOM (Rel-16) | SA WG2 | This was Block approved in CC#3 | Approved |
SP-200675 | CR to 23.501 on 5G_URLLC (Rel-16) | SA WG2 | This was Block approved in CC#3 | Approved |
SP-200688 | CRs to 23.501, 23.502, 23.503 on Vertical_LAN (Rel-16) | SA WG2 | CC#1: 23.501 CR2448R1 was reported needing further work and was postponed. All other CRs in this CR pack were approved. | Partially approved |
SP-200673 | CRs to 23.501, 23.502, 23.503 on 5G_CIoT (Rel-16) | SA WG2 | This was Block approved in CC#3 | Approved |
SP-200672 | CRs to 23.401 on NB_IOTenh-Core, CIoT_ext (Rel-15, Rel-16) | SA WG2 | This was Block approved in CC#3 | Approved |
SP-200671 | CRs to 23.501, 23.502 on 5GS_Ph1 (Rel-15, Rel-16) | SA WG2 | This was Block approved in CC#3 | Approved |
SP-200668 | CR to 26.247 | SA WG4 | This was Block approved in CC#3 | Approved |
SP-200665 | CRs to TS 26.114 | SA WG4 | This was Block approved in CC#3 | Approved |
SP-200664 | CRs to TS 26.511 | SA WG4 | This was Block approved in CC#3 | Approved |
SP-200663 | CRs to TS 26.501 | SA WG4 | This was Block approved in CC#3 | Approved |
SP-200662 | CRs to TS 26.238 | SA WG4 | This was Block approved in CC#3 | Approved |
SP-200661 | CRs to TS 26.234 | SA WG4 | This was Block approved in CC#3 | Approved |
SP-200660 | CRs to TS 26.223 | SA WG4 | This was Block approved in CC#3 | Approved |
SP-200676 | CRs to 23.316, 23.502 on 5WWC (Rel-16) | SA WG2 | This was Block approved in CC#3 | Approved |
SP-200711 | Rel-16 CRs for Study on Security Aspects of 3GPP support for Advanced V2X Services | SA WG3 | This was Block approved in CC#3 | Approved |
SP-200730 | Rel-15 CRs on Network Resource Model (NRM) for 5G networks and network slicing | SA WG5 | This was Block approved in CC#3 | Approved |
SP-200729 | Rel-16 CRs on NRM enhancements | SA WG5 | This was Block approved in CC#3 | Approved |
SP-200728 | Rel-10 CRs on TEI | SA WG5 | This was Block approved in CC#3 | Approved |
SP-200727 | Rel-11 CRs on TEI | SA WG5 | This was Block approved in CC#3 | Approved |
SP-200726 | Rel-12 CRs on TEI | SA WG5 | This was Block approved in CC#3 | Approved |
SP-200725 | Rel-15 CRs on TEI | SA WG5 | This was Block approved in CC#3 | Approved |
SP-200724 | Rel-16 CRs on TEI | SA WG5 | This was Block approved in CC#3 | Approved |
SP-200723 | Rel-16 CRs on Streaming trace reporting | SA WG5 | This was Block approved in CC#3 | Approved |
SP-200716 | Rel-16 CRs on Security aspects of Enhanced Network Slicing | SA WG3 | This was Block approved in CC#3 | Approved |
SP-200715 | Rel-16 CRs on Security aspects of SEAL | SA WG3 | This was Block approved in CC#3 | Approved |
SP-200686 | CRs to 23.214, 23.501, 23.502, 23.682 on TEI16 (Rel-16) | SA WG2 | This was Block approved in CC#3 | Approved |
SP-200713 | Rel-16 CRs on Study on evolution of Cellular IoT security for the 5G System | SA WG3 | This was Block approved in CC#3 | Approved |
SP-200659 | CRs to TS 26.116 | SA WG4 | This was Block approved in CC#3 | Approved |
SP-200710 | Rel-16 CRs on User Plane Gateway Function for Inter-PLMN Security | SA WG3 | This was Block approved in CC#3 | Approved |
SP-200709 | Rel-15 CRs on Security aspects of 5G System - Phase 1 batch 1 | SA WG3 | This was Block approved in CC#3 | Approved |
SP-200708 | Rel-16 CRs on Authentication and key management for applications based on 3GPP credential in 5G | SA WG3 | This was Block approved in CC#3 | Approved |
SP-200707 | Rel-16 CRs on Security for IAB | SA WG3 | This was Block approved in CC#3 | Approved |
SP-200706 | Rel-16 CRs on Security for enhancements to the Service Based 5G System Architecture | SA WG3 | 33.501 CR0908R1 should be a CR to 33.310, so should be rejected. Replacement CR to 33.310 provided in SP-200857. 33.501 CR0908R1 was rejected. Al other CRs in this CR Pack were approved | Partially approved |
SP-200705 | Rel-16 CRs on Security Aspects of eV2XARC | SA WG3 | CC#1: 33.536 CR0002 was reported needing further work and was postponed. All other CRs in this CR pack were approved. | Partially approved |
SP-200703 | Rel-16 CRs on Security Assurance Specification for 5G | SA WG3 | This was Block approved in CC#3 | Approved |
SP-200702 | Rel-15 CRs on Security Assurance Specification for eNB network product class | SA WG3 | This was Block approved in CC#3 | Approved |
SP-200701 | Rel-16 CRs on TEI | SA WG3 | This was Block approved in CC#3 | Approved |
SP-200689 | CR to 23.502 on xBDT (Rel-16) | SA WG2 | This was Block approved in CC#3 | Approved |
SP-200847 | Rel-17 CR to TR 23.744 for FS_enhMCLoc | SA WG6 | This was Block approved in CC#3 | Approved |
E.4 List of Approved CRs
Meeting | Spec | CR | Rev | Phase | Subject | Cat | Version-Current | TD# | Source | Status | Work Item | Affected_Clauses |
SP-89E | 22.125 | 0028 | 6 | Rel-17 | Stage 1 CRs on ID_UAS | F | 17.1.0 | SP-200881 | SA WG1 | Approved | EAV | 3.1, 4.2, 5.1, 6.2, 6.3, 6.4, 6.5, 7.4, A.1 |
SP-89E | 22.261 | 0462 | 4 | Rel-17 | Quality improvement of TS 22.261 (R17) – editorial modifications | D | 17.3.0 | SP-200889 | Siemens | Approved | eCAV | 3.2, 5.1.2.2, 6.4.1, 6.6.2, 6.7.1, 6.9.1, 6.10.2, 6.11.1, 6.13.2, 6.16.2, 6.17.1, 6.20.2, 6.22.2.1, 6.22.2.3, 6.23, 6.24, 6.25, 6.26.2.2, 6.26.2.7, 6.27.2, 6.34.1, 7.1, 7.2.3.1, 7.3, 7.3.2.2, 7.4, 7.5, 7.6, 7.7, 8.1, 8.2, 8.3, 8.4, E, F.1, G.1 |
SP-89E | 22.889 | 0169 | 3 | Rel-17 | Stage 1 CRs FS_FRMCS3 | F | 17.2.0 | SP-200882 | SA WG1 | Approved | FS_FRMCS3 | 12.16.2.5, 12.17.2.5, 12.23.6. |
SP-89E | 23.501 | 2383 | 2 | Rel-16 | Signalling of UE Radio Capability ID in Registration procedure | F | 16.5.1 | SP-200802 | Qualcomm Incorporated | Approved | RACS | |
SP-89E | 33.310 | 0112 | - | Rel-16 | Making NF instance id in SBA certificate profile mandatory to support | F | 16.4.0 | SP-200857 | Nokia | Approved | 5G_eSBA |
Annex F List of new and revised WIDs / SIDs
F.1 List of Approved WIDs / SIDs
TD# | Type | Title | Source | WI Code | Comment | Decision |
SP-200667 | WID NEW | New Work Item on 'Operation Points for 8K VR 360 Video over 5G'. | Intel, NHK, Ericsson LM, AT&T, Qualcomm Incorporated, Dolby Laboratories Inc., Beijing Xiaomi Electronics, Tencent, Huawei Technologies Co Ltd. | This was Block approved in CC#3 | Approved | |
SP-200719 | WID NEW | New WID on UPIP support in 5GS. | SA WG3 | This was Block approved in CC#3 | Approved | |
SP-200720 | WID NEW | New WID on Security Assurance Specification for Network Slice-Specific Authentication and Authorization Function (NSSAAF). | SA WG3 | This was Block approved in CC#3 | Approved | |
SP-200721 | SID NEW | New study on the security of AMF re-allocation. | SA WG3 | This was Block approved in CC#3 | Approved | |
SP-200722 | SID NEW | New SID on security aspects of enablers for Network Automation (eNA) for the 5G System (5GS) Phase 2. | SA WG3 | This was Block approved in CC#3 | Approved | |
SP-200765 | SID NEW | New SID on YANG PUSH. | SA WG5 | This was Block approved in CC#3 | Approved | |
SP-200766 | SID NEW | New SID on network slice management enhancement to include security aspects. | SA WG5 | This was Block approved in CC#3. CC#4: WGs to avoid agreeing to multiple rapporteurs for WIDs and SIDs. | Approved | |
SP-200767 | SID NEW | New SID on charging aspects of Enhanced Proximity-based Services in 5GC. | SA WG5 | This was Block approved in CC#3 | Approved | |
SP-200769 | WID NEW | New work item on charging enhancement for URLLC. | SA WG5 | This was Block approved in CC#3 | Approved | |
SP-200771 | SID NEW | Study on charging aspects of 5GS CIoT. | SA WG5 | This was Block approved in CC#3 | Approved | |
SP-200797 | WID NEW | New WID on Subscriber-aware Northbound API access (SNA). | SA WG1 (from S1-203296) | This was Block approved in CC#3 | Approved | |
SP-200798 | SID NEW | New SID: Study on vehicle-mounted relays (FS_VMR). | SA WG1 | CC#3: China Mobile withdrew their objection. Approved | Approved | |
SP-200799 | SID NEW | New SID: Study on 5G Networks Providing Access to Localized Services (FS_PALS). | SA WG1 | CC#3: China Mobile withdrew their objection. Approved | Approved | |
SP-200831 | WID NEW | New WID for enhanced application layer support for V2X services. | SA WG6 | This was Block approved in CC#3 | Approved | |
SP-200832 | WID NEW | New WID Application Architecture for MSGin5G Service. | SA WG6 | This was Block approved in CC#3 | Approved | |
SP-200833 | WID NEW | New WID Mission Critical Services over 5GS. | SA WG6 | This was Block approved in CC#3 | Approved | |
SP-200853 | SID NEW | New SID on the access control for management service. | SA WG5 | Revision of SP-200764. Change of 'Other related Work Items and dependencies' as suggested by the Work Plan Manager. This was Block approved in CC#3 | Approved | |
SP-200854 | WID NEW | New WID on N40 Interface Enhancements to Support GERAN and UTRAN. | SA WG5 | Revision of SP-200768. Alignment of acronym with SA WG2's acronym TEI17_NIESGU. This was Block approved in CC#3 | Approved | |
SP-200878 | SID NEW | New SID on security aspects of the MSGin5G Service | SA WG3 | Revision of SP-200717_Rev1. Approved | Approved | |
SP-200879 | WID NEW | New WID on mission critical security enhancements phase 2 | SA WG3 | Revision of SP-200718_Rev2. Approved | Approved | |
SP-200885 | SID NEW | New Study on User Consent for 3GPP services | Huawei, HiSilicon, China Unicom, CAICT, CATT | Revision of SP-200812_Rev1. Approved | Approved |
F.2 List of Updated WIDs / SIDs
TD# | Type | Title | Source | WI Code | Comment | Decision |
SP-200656 | WID REVISED | Revised WID on the normative aspects of User Plane Integrity Protection for NR. | Vodafone | UPIP_SEC | Approved. The 3GPP Work Plan will need to be updated to indicate Rel-16 for UPIP_SEC. | Approved |
SP-200690 | SID REVISED | Revised SID: Architectural enhancements for 5G multicast-broadcast services. | SA WG2 | FS_5MBS | This was Block approved in CC#3 | Approved |
SP-200763 | WID REVISED | Revised WID Self-Organizing Networks (SON) for 5G networks. | SA WG5 | SON_5G | This was Block approved in CC#3 | Approved |
SP-200770 | WID REVISED | Revised WID on Discovery of management services in 5G. | SA WG5 | 5GDMS | This was Block approved in CC#3 | Approved |
SP-200835 | SID REVISED | Revised SID Study on support of the 5GMSG Service. | SA WG6 | FS_5GMARCH | This was Block approved in CC#3 | Approved |
SP-200836 | SID REVISED | Revised SID Study on application layer support for . Factories of the Future in 5G network . | SA WG6 | FS_FFAPP | This was Block approved in CC#3 | Approved |
SP-200837 | SID REVISED | Revised SID Study on Mission Critical services support over 5G System. | SA WG6 | FS_MCOver5GS | This was Block approved in CC#3 | Approved |
SP-200886 | WID REVISED | Revised WID on Architecture for enabling Edge Applications . | SA WG6 | EDGEAPP | Revision of SP-200834_Rev1. Approved | Approved |
Annex G List of endorsed WI summaries
TD# | Type | Title | Source | WI Code | Comment |
SP-200776 | WI SUMMARY | Work Item Summary for 5G_eSBA | China Mobile | 5G_eSBA | This was Block endorsed in CC#3 |
SP-200777 | WI SUMMARY | Work Item Summary for Rel-16 UDICOM | Nokia Korea | UDICOM | This was Block endorsed in CC#3 |
SP-200801 | WI SUMMARY | Summary for Work Item on 'Removal of H.263 and MPEG-4 Visual from 3GPP Services' | Qualcomm Incorporated | RM_H263_MP4V | This was Block endorsed in CC#3 |
SP-200808 | WI SUMMARY | Work Item Summary for Rel-16 eIMS5G_SBA | T-Mobile USA Inc. | TEI16 | This was Block endorsed in CC#3 |
SP-200848 | WI SUMMARY | Work item Summary for 5GMS3 | Sony (Rapporteur) | 5GMS3 | This was Block endorsed in CC#3 |
SP-200849 | WI SUMMARY | Work item Summary for Enhancement of performance assurance for 5G | Intel (Rapporteur) | 5G_SLICE_ePA | This was Block endorsed in CC#3 |
SP-200851 | WI SUMMARY | Work Item Summary for Rel-16 eCAPIF | Samsung | eCAPIF | This was Block endorsed in CC#3 |
SP-200852 | WI SUMMARY | Work Item Summary for Rel-16 SEAL | Samsung | SEAL | This was Block endorsed in CC#3 |
SP-200872 | WI SUMMARY | Work Item Summary for QOED | Ericsson | QOED | Late submission. CC#4: This WI Summary was endorsed. |
Annex I Notes from Conference Calls
I.1 SA#89E_CC#1
Third Generation Partnership Project (3GPP™)
SUMMARY Report for TSG SA meeting: #89E (Electronic meeting) Conference Call #1
Opened: Tuesday, (2020-09-15) 13:00 UTC
There were ~160 participants on this CC.
Attendees: The following companies were recorded as present (list not exhaustive or verified)
Affirmed Networks
Apple
AT&T
BBC
BMWi
Broadcom
BT
Canon
CBN
Charter
Cisco
CMCC
DENSO
Deutsche Telekom
DoD
Dolby
EBU
Ericsson
FirstNet
Futurewei
Huawei
Intel
IPCom
JHU/APL
KDDI
KPN
KT
Kyocera
LG Uplus
LGE
Matrixx
MediaTek
NCSC
Nkom
Nokia
NTIA
NTT DOCOMO
OPPO
Orange
OTD
Perspecta Labs
Qualcomm
Samsung
Siemens
SoftBank
Sony
SyncTechno
TEF
Telstra
Tencent
TIM
T-Mobile USA
TTA
UIC
Verizon
Vivo
Vodafone
Xiaomi
ZTE
NOTE: Meeting notes are not exhaustive and may not contain all the comments made during the conference call.
Opening of meeting
The TSG SA Chairman opened this CC at 13.00 UTC.
1.4 Approval of Agenda
TD SP 200855 (AGENDA) SA#89-e GoToMeetings Agenda. (Source: TSG SA Chairman).
Document for: Approval.
Discussion and conclusion:
The meeting agenda was approved.
TD SP 200632 (AGENDA) Agenda & Procedures & Time Schedule for TSG SA#88-e. (Source: TSG SA Chairman).
Document for: Approval.
Discussion and conclusion:
The agenda for the CCs was noted.
1.5 Report from previous SA meetings
TD SP 200633 (REPORT) Draft report of TSG SA meeting #88E. (Source: TSG SA Secretary).
Document for: Approval.
Discussion and conclusion:
The report of TSG SA#88-e was approved.
Incoming Liaisons which need online discussion
2 Liaisons Statements
2.1 Incoming LSs - proposed to note
Block 1: For Block Noting - Tuesday 15:00 UTC
TD SP 200635 LS from ITU-R WP 5D: LIAISON STATEMENT TO RIT/SRIT PROPONENTS ON THE COMPLETION AND CONCLUSIONS OF STEPS 5 TO 7 OF THE IMT-2020 PROCESS FOR THE FIRST RELEASE OF NEW RECOMMENDATION ITU-R M.[IMT-2020.SPECS]. (ITU-R WP 5D)
Document for: Information.
Discussion and conclusion:
Block noted.
TD SP 200636 LS from ITU-R WP5D: LIAISON STATEMENT TO TRANSPOSING ORGANIZATIONS ON THE COMPLETION OF STEP 8 OF IMT-2020 PROCESS FOR THE FIRST RELEASE OF NEW RECOMMENDATION ITU-R M.[IMT-2020.SPECS]. (ITU-R WP5D)
Document for: Information.
Discussion and conclusion:
Block noted.
TD SP 200637 LS from ETSI ISG E4P: Request for information exchange. (ETSI ISG E4P)
Document for: Information.
Discussion and conclusion:
Block noted.
TD SP 200639 LS from TM Forum Autonomous Networks: Introduction of TM Forum Autonomous Network project and Coordination Proposal. (TM Forum Autonomous Networks)
Document for: Information.
Discussion and conclusion:
Block noted.
TD SP 200640 LS from IETF: Re: LS on need for Multi-Path QUIC for ATSSS. (IETF)
Document for: Information.
Discussion and conclusion:
Block noted.
TD SP 200641 LS from IETF DRIP: Drone Remote ID Protocol Working Group (DRIP). (IETF DRIP)
Document for: Information.
Discussion and conclusion:
Block noted.
TD SP 200642 LS from ITU-R WP5A: LIAISON STATEMENT TO EXTERNAL ORGANIZATIONS ON ITS Connected Automated Vehicles (CAV). (ITU-R WP5A)
Document for: Information.
Discussion and conclusion:
Block noted.
TD SP 200643 LS from TSG RAN: Reply LS to RP-200030 on relevant 3GPP Specs for PC5 Sidelink. (TSG RAN)
Document for: Information.
Discussion and conclusion:
Block noted.
TD SP 200644 LS from TSG RAN: Reply LS to GSMA_5GSI_28_Doc003 = RP-193053 on 5G indicator enhancement. (TSG RAN)
Document for: Information.
Discussion and conclusion:
Block noted.
TD SP 200645 LS from ITU-T SG13: LS/o on information about consent of Machine Learning related ITU-T Recommendation Y.3176. (ITU-T SG13)
Document for: Information.
Discussion and conclusion:
Block noted.
TD SP 200649 LS from CT WG4: LS on AUSF/UDM discovery based on SUCI information. (CT WG4)
Document for: Information.
Discussion and conclusion:
Block noted.
TD SP 200653 LS from SA WG5: LS reply to LS on M.resm-AI “Requirements for energy saving management of 5G RAN system with AI”. (SA WG5)
Document for: Information.
Discussion and conclusion:
Block noted.
2.2 Incoming LSs which need an outgoing LS
LSs with related documents/replies
TD SP 200652 LS from SA WG2: LS on RAN impact of FS_5MBS Study. (SA WG2)
Document for: Action.
Abstract: SA WG2 has been discussing on Rel 17 FS_5MBS solutions since SA WG2 #135 meeting in TR 23.757, and captured several proposed solutions. SA WG2 would like to kindly inform RAN WG2 and RAN WG3 the following interim agreements in SA WG2: - SA WG2 will develop means to provide QoS requirements for an MBS Session to RAN nodes. - SA WG2 agrees that for N3 transport of the shared delivery method of MBS data, GTP-U tunnelling using a transport layer IP multicast method and shared N3 (GTP-U) Point-to-Point tunnel shall be supported from MB-UPF to NG-RAN nodes. This tunnel can use either IP multicast transport (NG-RAN sends IGMP/MLD Join/Leave to a multicast router) or point-to-point unidirectional N3 tunnels from MB-UPF to NG-RAN nodes. For unicast transport there shall be 1-1 mapping between MBS Session and GTP-U tunnel towards a RAN node, and for multicast transport there shall be 1-1 mapping between MBS Session and the GTP-U tunnel. - SA WG2 agreed that the UE shall be able to receive on-going data of a multicast MBS session while in CM-CONNECTED state. - Based on SA plenary decisions, Key Issue #5 ('Support of Broadcast TV Video and Radio communication services') is out of scope of Rel 17. {. . .}.
Discussion and conclusion:
Response drafted in SP-200810.
TD SP 200809 (DISCUSSION) Discussion on support for broadcast in Rel 17 MBS. (Source: Huawei, HiSilicon).
Document for: Endorsement.
Abstract: Proposal: The scope of Rel 17 5MBS SID remains as it is (i.e. NR broadcast is included), and no further down-scoping or prioritization is needed.
Discussion and conclusion:
This was noted.
TD SP 200810 [DRAFT] reply LS on RAN impact of FS_5MBS Study. (Huawei [SA])
Document for: Approval.
Abstract: SA would like to clarify that NR-based broadcast is within the scope of SA SID for 'Study on architectural enhancements for 5G multicast-broadcast services',
Discussion and conclusion:
Response to TD SP 200652. Huawei introduced this proposed response LS which states that the NR Broadcast is within the scope of the SID. Qualcomm commented that there is also a discussion in TSG RAN on this LS and requested more time to determine the results of those discussions before agreeing a response from TSG SA. It was understood that a response LS will be needed from this meeting. This should be discussed over e-mail.
TD SP 200634 LS from IALA: Liaison Note to TSG SA - Request for information. (IALA) (Revision of TD SP 200310).
Document for: Action.
Abstract: Introduction: The International Association of Marine Aids to Navigation and Lighthouse Authorities (IALA) focuses on the maritime domain, particularly Aids to Navigation (AtoN), including Vessel Traffic Services (VTS), and their associated communication systems. 3GPP is becoming an important element in digital communications, including the exchange of digital data. IALA would like to thank TSG SA for their appointment of a liaison between IALA and 3GPP currently fulfilled by Ms Hyounhee Koo (koo@synctechno.com). IALA would like to invite Ms. Koo to participate at the ENAV26 meeting scheduled from 28 September to 2 October at the IALA HQ to provide an update on 3GPP developments and assist in the drafting of relevant IALA documentation related to 3GPP. It is noted by IALA that 3GPP has a work item focusing maritime communication services over 3GPP Systems in Release 16 called 'MARCOM'. IALA 3GPP interest: At the fifteenth meeting of the Joint IMO/ITU Experts Group on Maritime radiocommunication matters (8 to 12 July 2019, IMO Headquarters, London) IALA was requested to report to IMO in respect of 3GPP developments. The report of the meeting (IMO document NCSR7/12) records this decision in paragraph 8.9: 8.9 During the ensuing discussion, the delegations that took the floor recognized that these were relevant developments and that IMO should be more proactive and get involved in the work of the 3rd Generation Partnership Project (3GPP). Noting that IALA had been approached already by 3GPP, the Group invited IALA to keep IMO informed of future developments. In response to this, IALA provided an information paper to IMO (NCSR7 INF.6). This document was developed from the IALA perspective on the operational aspects of the developments in 3GPP that may be of interest to the members of NCSR7. In document SP-191366, 3GPP provided a liaison to IALA noting proposed amendments to the NCSR document. The paper was not addressed at NCSR7 plenary, according to the standard procedures of IMO. IALA will prepare an updated input for NCSR8 and would welcome input from 3GPP in the preparation of that document. Given this request, and IALA's own role in the development of AtoN and VTS technology, IALA closely following the development of maritime services within 3GPP. IALA would therefore like to register an interest in the work of 3GPP, particularly the maritime vertical domain. Action requested: The TSG SA is requested to: 1. Inform IALA which 5G enabling technologies that are specified in the 3GPP Release 16 technical specification which could be applicable in the maritime domain. 2. Inform IALA of ongoing 5G standardization works in 3GPP Release 17 which could be applicable in the maritime domain. 3. Advise IALA regarding appropriate inputs [to support] development of 3GPP Release 17 for use within the maritime domain. 4. Advise IALA on the schedule for future meetings and other opportunities for input relevant to the maritime domain (such as MARCOM) allowing adequate time to prepare inputs.
Discussion and conclusion:
Postponed TD SP 200310 from SA#88E. Response drafted in TD SP 200655.
TD SP 200655 [DRAFT] Reply LS on request for information from IALA. (SyncTechno Inc)
Document for: Approval.
Abstract: This contribution is the reply liaison on request information from IALA.
Discussion and conclusion:
Response to TD SP 200634. SyncTechno Inc introduced this proposed response LS. This LS was approved. MCC will need to revise to remove 'draft'.
TD SP 200654 LS from CT WG1: LS on the Stage 2 aspects of MINT. (CT WG1)
Document for: Action.
Abstract: CT WG1 has discussed a WID proposal for CT aspects of Minimization of Service Interruption (MINT-CT) in the CT WG August meetings, in order to support the service requirements specified for Rel 17. The WID on MINT-CT includes a study phase on both stage-2 and stage-3 aspects. CT WG1 is also planning to define end-to-end call flow regarding registration after selection of a disaster roaming PLMN in the stage-2 specification owned by CT WG1. CT WG1 would like to ask TSG SA if there is any concern on this approach. CT WG1 expects any feedback on this way forward until the next WG meeting so that both study phase and normative phase can progress within Rel 17 timeframe. Action: CT WG1 kindly asks TSG SA to take the information above into account and to provide feedback.
Discussion and conclusion:
Response drafted in TD SP 200775.
TD SP 200774 (DISCUSSION) Discussion on the WI MINT. (Source: LG Electronics).
Document for: Endorsement.
Abstract: Discussion paper for LS from CT WG1 (C1-205332) on the Stage 2 aspects of MINT.
Discussion and conclusion:
LGE presented these background discussion slides. It concludes that there is no concern on the approach suggested by CT WG1. This was then noted.
TD SP 200775 [DRAFT] Reply LS on the Stage 2 aspects of MINT. (LG Electronics)
Document for: Approval.
Abstract: [DRAFT] Reply LS on the Stage 2 aspects of MINT (CT WG1 LS, C1-205332).
Discussion and conclusion:
Response to SP-200654. LG Electronics introduced this proposed response LS which indicates that there is no concern on the approach suggested by CT WG1. MediaTek raised some concerns on how the UE will be informed about the use of disaster recovery networks. Vodafone commented that also cases of network overload needs to be taken into consideration to prevent one failing network overloading it's neighbouring network, causing it's failure, and so on. AT&T suggested that in order to be able to manage prioritisation correctly, if there is work needed in other groups, such as SA WG1 or SA WG2, that this is determined before leaving everything to CT WG1. MediaTek commented that the information to the UE is necessary and whether there are existing solutions for this or not, SA WG2 will need to be involved in this. Vivo commented that CT WG1 could indicate that provision of such a list is TBD, so that SA WG2 could handle this later. Huawei agreed with Vivo that this is network selection related and should be lead by CT WG1 and LSs used to get information needed from other WGs. The LS should be updated to take these concerns into account. LG Electronics stressed that this is a needed feature for South Korean operators. LG Uplus supported the way forward and would like to see work started as soon as possible. This should be discussed over e-mail and a revision proposed.
TD SP 200814 (DISCUSSION) The Importance of Maintaining Broadcast Services in Rel 17 NR MBS. (Source: CBN, ABS, ABP, China Telecom, China Unicom, IRT, Reliance Jio).
Document for: Decision.
Abstract: Broadcast is essential to NR MBS - SA WG2 is debating whether broadcast (for other use cases than the ones excluded already for Rel 17) should be further down-scoped in Rel 17 for remaining broadcast requirement in the SID. Some companies have provided solutions on broadcast (which are documented in the TR). SA WG2 sent an LS to SA asking the above question. - NR MBS with only multicast is just a feature improving network efficiency. With Broadcast, NR MBS creates new business models serving more scenarios, as well as enabling the 5G refarming of the broadcast-dedicated spectrum in many countries. - Down-scoping broadcast will cause NR MBS incapable to deal with emerging demand in many new businesses for 5G NR. NR Broadcast: Enable new business cases - Public Services - Government and public service entities have urgent demand for 5G-enabled innovative ways of communicating with citizens. Broadcast shall be adopted to more efficiently deliver real-time emergency multi-media notifications to a wide variety of devices under the scope of public safety (like disaster warning, security, pandemic control, etc.). - Multimedia Live Streaming in crowed activities(Concerts/Sport Games) - Innovative broadcast services like Multi-angle live viewing, game statistics broadcasting, XR enhanced viewing, etc. Broadcast mode is essential for such highbitrate-high-concurrency services. CBN is planning to showcase innovative NR MBS broadcast services in Beijing Olympic Winter Games 2022. - Massive IoT - Identical content needs to be distributed to a massive number of devices like smart home appliances. It is inefficient to use unicast/multicast for this, but ideal for broadcast. It makes OTA (over-the-air) firmware upgrades/group messaging/etc. much more efficient. - V2X - Broadcast enables vehicles to efficiently communicate with the network and its surroundings, making the network to more efficiently deliver real-time information, such as software and traffic updates, as well as the emergency Multimedia notifications to the vehicle driver/passengers.
Discussion and conclusion:
This was related to the LS in TD SP 200810. CBN presented these slides, which argues against reducing the scope of the broadcast work, as this is needed for many new business demands on 5G NR. FirstNet supported this proposal and added that all Mission Critical procedures use broadcast and do not use multicast. AT&T, SynchTechno, Huawei, ZTE supported this contribution proposal. Qualcomm asked what was intended for massive IoT work on this. ZTE added that the original scoping of Rel-17 should not be changed now. FirstNet asked all delegates with interest in Mission Critical to also follow and contribute to this topic in the TSG RAN meeting. This was then noted.
7.3 Release 17 Planning (schedule, prioritization, etc.)
TD SP 200800 (DISCUSSION) On Release 17 Schedule. (Source: Qualcomm Incorporated).
Document for: Approval.
Abstract: Proposes finalisation of rel.17 schedule.
Discussion and conclusion:
Qualcomm presented these slides which propose finalisation of the Rel-17 schedule, taking into account the current electronic meeting environment and expected slower progress of the normative work in electronic meetings. This proposed to extend the Rel-17 schedule at this TSG SA meeting (+6 months). This was then noted.
TD SP 200811 (DISCUSSION) Discussion on Rel 17 Schedule. (Source: Huawei, HiSilicon).
Document for: Agreement.
Abstract: Discussion on Rel 17 Schedule.
Discussion and conclusion:
Huawei presented these slides which indicate tht SA WG2 study work is slower than originally predicted and normative work will consequently be delayed and proposed to extend the Rel 17 schedule at this TSG SA meeting (+3 months) and review again at the next TSG SA meeting. This was then noted.
General discussion:
Qualcomm asked that if Stage 2 freeze is moved from September to March, then will SA WG2 need to finish all their normative work by March 2021? Huawei replied that a final decision should be made in December TSG SA meeting based on the completion at that time. Intel commented that how to handle work in Stage 2 can be decided by TSG SA, but the impact on other TSGs of moving the Rel 17 timeline will need to be agreed between the TSGs and they prefer to make this decision at the next TSG meetings. ZTE suggested a 6 month shift should be considered for the whole Release. Samsung commented that there has already been a 3 months slip of Stage 2 and agreed with Qualcomm that there are a large number of solution evaluations needed so concluding the normative work in the current timescale is unfeasible. Nokia commented that it is unreasonable to expect the stage 2 to be stabilised in 3 months and that a Stage 2 shift without the corresponding Stage 3 shift is against the principles used in the past, where a 9 month period is needed between the stage freezes. The TSG SA Chairman commented that TSG CT had indicated that they would not expect a big problem with a Stage 2 slip of 3 months. FutureWei commented that SA WG2 should be allowed to continue to try to meet the current schedule and review this when an issue is raised. Ericsson supported the FutureWei view and would prefer to keep the pressure on the Stage 2 work to complete and debate any change to timelines in December. Huawei commented that a final decision on the necessary slip should be made in December when the progress has been determined. MediaTek commented that many of the studies are in poor shape and did not consider it realistic to be able to complete the work by March 2021. FirstNet commented that this would need to be coordinated with TSG RAN and added that there has been a lot of discussion about downscoping but preferred to extend the dates to have a reasonable content in the Release. Vodafone commented that it would be useful to target the work which can be completed by March over that which needs until June, in order to allow some stable input to the Stage 3 groups. OPPO commented that if it is assumed the SA WG2 Studies are completed by December, at least 6 months more will be needed for the normative work. The SA WG2 Chairman commented that the idea is to complete the Studies by December 2020, but this also depends upon some RAN WG feedback and decisions. Therefore the final stage 2 freeze date should be decided at the next TSG meetings, also so that exception sheets will not be needed for all the SA WG2 Work Items. This was left for further offline consideration and will be added to the agenda for CC#2.
Issues raised for early treatment which need online discussion
3.4 Discussion papers on work in Rel-16
TD SP 200795 (DISCUSSION) On 5G GUTI reallocation for CIoT. (Source: Qualcomm Incorporated).
Document for: Approval.
Abstract: Discusses the requirement of 5G GUTI re-allocation and how it impacts the CIoT signalling transactions.
Discussion and conclusion:
This was presented by Qualcomm and discusses the requirement of 5G GUTI re-allocation and how it impacts the CIoT signalling transactions. It proposes two options (Qualcomm prefer option 1):
Option 1: Allocation of a new 5G-GUTI temporary identifier to the UE in response to paging in 5G is mandatory and shall apply in all cases including all CIoT optimisations.
Option 2: Allow an exception to the strict requirement for 5G CIoT. The trade-off between user privacy protection and signalling optimisation becomes configurable but is applicable to all different procedures defined in the context of CIoT optimisations in rel.16 and beyond.
Huawei supported Option 1, which was the preference of the majority of companies in CT WG1. Intel supported Option 1. Ericsson commented that it has traditionally been an operator decision depending on the security risks inherent and supported Option 2. Nokia preferred Option 1. MediaTek supported Option 1. Vodafone commented that assuming the mandatory requirement was only in the SA WG3 TS and not the CT WG1 TS, in reality Option 2 will be implemented. As many IoT devises are likely to be used by individual users, there is likely to be a large exposure risk to users. Qualcomm commented that the complication was dependent on whether the signalling procedures allow the allocation of a new 5G GUTI or not. Vodafone replied that in this case Option 1 was preferred. Sony supported Option 2. This document was then noted.
TD SP 200796 [DRAFT] LS On 5G GUTI reallocation for CIoT. (Qualcomm Korea)
Document for: Approval.
Abstract: Provides instructions on allocating new 5G GUTI at every signalling transaction trigged by paging.
Discussion and conclusion:
This LS was left for further consideration over e-mail.
6.2 Revised Release 16 and earlier Study Item Descriptions and Work Item Descriptions
TD SP 200656 (WID REVISED) Revised WID for UPIP Release 16 changes. (Source: Vodafone Italia SpA).
Document for: Approval.
Abstract: Updates Objectives, Impacted TSs and Supporting companies.
Discussion and conclusion:
The SA WG3 Chairman reported that this revision of the WID was provided after the revisions deadline and has been circulated over the SA WG3 e-mail list. It was clarified that this should be a Rel-16 WI to align the Rel-16 work. This revised WID was then approved. The 3GPP Work Plan will need to be updated to indicate Rel-16 for UPIP_SEC.
6.3 New Release 17 Study Item Descriptions
TD SP 200812 (SID NEW) New Study on User Consent for 3GPP services. (Source: Huawei, Hisilicon, China Unicom, CAICT, CATT).
Document for: Approval.
Abstract: This SID is to identify and evaluate the requirements and solutions to support user consent for 3GPP services.
Discussion and conclusion:
NTT DOCOMO confirmed that they were happy with SP 200812_r01. This new SID, SP 200812_r01, was then approved.
6.6 New Release 18 Study Item Descriptions
TD SP 200821 (DISCUSSION) Study on Support _x00B_for Service Function Chaining in 5G System (FS_SFCin5GS). (Source: Intel, Deutsche Telekom AG, Tencent, Telefónica, Affirmed Network, AT&T, Sandvine, Convida Wireless, InterDigital, KPN, Verizon UK Ltd., KDDI, Vodafone, Telecom Italia, Cisco, b<>com, Spirent Communications).
Document for: Discussion.
Abstract: Summary: The proposed Rel 18 SA WG1 study (FS_SFCin5GS; S1-203293; updated for SA plenary in SP-200822) is supported by a large number of companies. The study proposal was noted in SA WG1 based on objections that do not challenge the technical aspects of the proposal. The comments from objecting companies focused on the wording and whether the work should proceed directly with normative work in SA WG1, or whether it can be carried out directly by Stage 2 groups. This contribution provides a clear illustration of the potential Stage 1 specification impact, but that a study is necessary before a conclusion can be made. Proposal: Based on the above, it is proposed to approve this SA WG1 Rel 18 SID proposal (Support of Service function chaining in 5G system (FS_SFCin5GS)).
Discussion and conclusion:
This was presented by Intel which proposes to approve this SA WG1 Rel 18 SID proposal in TD SP 200822 (Support of Service function chaining in 5G system (FS_SFCin5GS)). This was then noted.
TD SP 200822 (SID NEW) New SID on Study on Support for Service Function Chaining in 5G System. (Source: Intel Corporation, Deutsche Telekom AG, Tencent, Telefónica, Affirmed Network, AT&T, Sandvine, Convida Wireless, InterDigital, KPN, Verizon UK Ltd., KDDI, Vodafone, Telecom Italia, Cisco, b<>com).
Document for: Approval.
Abstract: Objective: The aim of this work is to study the enable support of service function chaining in 5G system for value-added services provided by network operators to third parties, including:. The study will consider useUse cases and service requirements related to: - provide service definition of supported service functions and service function paths; - provide service configuration and management support of service functions and service function paths to third parties for applications and their users with value-added services, e.g. provided by 5GS only or both of 5GS and 3rd parties; - provide continuing same value-added service experiences for UEs using 5G services, e.g. eMBB, V2X, AVPROD, NCIS, etc., and moving between networks. Gap analysis between the identified service requirements and existing 5GS service requirements or functionalities. Note: the gap analysis takes into account previous work related to Stage 1 services requirements on SFC already developed in other SDOs (e.g. IETF RFC 7665, IETF RFC 8300, IETF RFC 8459, ITU-T Y.2242, etc).
Discussion and conclusion:
Ericsson commented that this was studied in Rel-13, continuing to Rel-14 in SA WG1. The confusion appears in the boundary between this functionality the 5G system, which cannot be viewed from the stage 1 into the stage 2 architecture. Nokia agreed with the issues raised by Ericsson and suggested that if there are stage 1 requirements which need to be addressed that these gaps should be identified and can be handled if necessary by normative WID and CR proposals, but did not see the need of a study for it. This was left for further consideration over e-mail.
TD SP 200820 (DRAFT TS) Draft TS 28.555 'Network policy management for 5G mobile networks; Stage 1'. (Source: SA WG5). (Revision of TD SP 200762).
Document for: Information.
Abstract: Abstract of document: The present document describes background, concepts, scenario, requirements and standard consideration for policy management in 5G network. Changes since last presentation to SA Meeting #: This is the first presentation. Outstanding Issues: Actor roles, telecommunication resources. Contentious Issues: No contentious issues.
Discussion and conclusion:
Revision of SP-200762. It was clarified that this was revised because the previous submission was marked for approval, whereas it is for information. This draft TS was noted. Members were asked to provide any comments and update proposals to SA WG5.
7.1 General Release Planning issues
TD SP 200815 (DISCUSSION) 3GPP Meeting Planning H1/2021. (Source: TSG SA Chairman).
Document for: Information.
Abstract: H1/2021 WG and e-meetings should be planned as e-meetings.
Discussion and conclusion:
This was presented by the TSG SA Chairman and indicates that it is likely that Q1/2021 and Q2/2021 will need to be e-meetings. It is possible that Elections may be held in March 2021, in which case the meeting may be extended to start early to allow time to hold electronic elections. It was clarified that any such extensions would not be for technical discussion. This was then noted.
16.2 SA WG2 Rel-16 CRs
TD SP 200685 (CR PACK) CRs to 23.401, 23.502 on RACS (Rel 16). (Source: SA WG2).
Document for: Approval.
Abstract: 23.501 CR2383R1; 23.502 CR2326R1; 23.401 CR3605R1.
Discussion and conclusion:
Company proposed revision of 23.501 CR2383R1 in SP-200802. 23.501 CR2383R1 was considered as revised and other CRs in this CR pack were approved. (This CR Pack was partially approved).
TD SP 200802 23.501 CR2383R2 (Rel 16, 'F'): Signalling of UE Radio Capability ID in Registration procedure. (Source: Qualcomm Incorporated).
Document for: Approval.
Abstract: Summary of change: Clarifies the signalling of UE Radio Capability ID in Registration procedures.
Discussion and conclusion:
Revision of S2-2006493 (23.501 CR2383R1) in CR Pack SP-200685. Vodafone supported this CR. This CR was approved.
TD SP 200688 (CR PACK) CRs to 23.501, 23.502, 23.503 on Vertical_LAN (Rel 16). (Source: SA WG2).
Document for: Approval.
Abstract: 23.503 CR0475; 23.502 CR2382; 23.501 CR2435; 23.502 CR2390; 23.503 CR0488; 23.501 CR2449; 23.501 CR2437R1; 23.502 CR2388R1; 23.501 CR2438R1; 23.501 CR2439R1; 23.501 CR2440R1; 23.501 CR2392R1; 23.501 CR2393R1; 23.501 CR2394R1; 23.502 CR2338R1; 23.501 CR2396R1; 23.501 CR2446R1; 23.503 CR0477R1; 23.501 CR2398R1; 23.501 CR2403R1; 23.501 CR2404R1; 23.501 CR2405R1; 23.501 CR2410R1; 23.503 CR0484R1; 23.501 CR2421R1; 23.501 CR2448R1; 23.501 CR2451R1; 23.502 CR2396R1; 23.503 CR0482R1; 23.502 CR2357R1; 23.501 CR2430R1; 23.502 CR2386R1; 23.501 CR2455R1; 23.501 CR2266R2; 23.501 CR2395R3.
Discussion and conclusion:
23.501 CR2448R1 was reported needing further work and was postponed. All other CRs in this CR pack were approved. (This CR Pack was partially approved).
TD SP 200705 (CR PACK) Rel 16 CRs on Security Aspects of eV2XARC. (Source: SA WG3).
Document for: Approval.
Abstract: 33.536 CR0001; 33.536 CR0002; 33.536 CR0014R1; 33.536 CR0007R1; 33.536 CR0009R1; 33.536 CR0010R1; 33.536 CR0011R1; 33.536 CR0013R1.
Discussion and conclusion:
33.536 CR0002 was reported needing further work and was postponed. All other CRs in this CR pack were approved. (This CR Pack was partially approved).
Noting of Block 1
All LSs for noting under 2.1 were noted.
22 Close of CC
The TSG SA Chairman closed this CC at 15.00 UTC.
I.1 SA#89E_CC#2
Third Generation Partnership Project (3GPP™)
SUMMARY Report for TSG SA meeting: #89E (Electronic meeting) Conference Call #2
Opened: Wednesday, (2020-09-16) 13:00 UTC
There were ~130 participants on this CC.
Attendees: The following companies were recorded as present (list not exhaustive or verified)
Airbus
Apple
AT&T
ATIS
BMWi
BT
CATT
CBN
Charter
China Telecom
Cisco
CMCC
Dolby
DTAG
Ericsson
FirstNet
Futurewei
Huawei
IDEMIA
Intel
Interdigital
IPCom
KDDI
KPN
KT
Kyocera
LGE
Matrixx
MediaTek
Motorola Solutions
Nkom
Nokia
NTIA
OPPO
Orange
OTD
Perspecta Labs
Qualcomm
Samsung
Sepura
Siemens
SoftBank
Sony
Sony
Spreadtrum
TEF
Telstra
Tencent
Thales
TIM
T-Mobile USA
TNO
UIC
Verizon
Vivo
Vodafone
Xiaomi
ZTE
NOTE: Meeting notes are not exhaustive and may not contain all the comments made during the conference call.
Opening of meeting
The TSG SA Chairman opened this CC at 13.00 UTC.
The CCs agenda was revised for this in:
https://www.3gpp.org/ftp/tsg_sa/TSG_SA/TSGs_89E_Electronic/Inbox/Revisions/SP-200855_rev1.zip
Rel-17 Timeline (AI 7.3) SP-200800 and SP-200811
Decision on this issue needs to be made latest Wednesday 15:00 UTC, too coordinate with RAN
TD SP 200800 (DISCUSSION) On Release 17 Schedule. (Source: Qualcomm Incorporated).
Document for: Approval.
Abstract: Proposes finalisation of rel.17 schedule.
TD SP 200811 (DISCUSSION) Discussion on Rel 17 Schedule. (Source: Huawei, HiSilicon).
Document for: Agreement.
Abstract: Discussion on Rel 17 Schedule.
Discussion and conclusion:
The latest proposed text from e-mail was reviewed. Huawei commented that there could be objections to a WID produced for item 2) which should not automatically result in the removal of the WID from Rel 17. ZTE asked for clarifications on item 3). CATT commented that there was no advantage to generating exception sheets for SIDs and asked to add that coordination with RAN work can be done in the normative phase. Nokia commented that item 3) was unnecessary as we never had exceptions for Study items in the past. It was clarified that the Work Items will be produced as a result of the Study Item conclusions. Vivo asked to clarify item 3) to indicate which items exceptions can be provided for. Orange commented that it should be clarified that SA WG2 should only include already prioritised Rel 17 work items in item 1). Orange also commented that as this is the second time Rel 17 is being considered for extension, it should be stated that this will not happen again. The TSG SA Chairman replied that if we take into account all possible misinterpretations of the bullets, it would need a lot of time to draft the guidelines and the spirit of the text should be taken into account. The SA WG6 Charman asked to add some actions to clarify which parts apply to SA WG2 and which apply to SA WG6. This should be further discussed over the e-mail.
40min Issues highlighted in reports from WG chairs & CT Chair
4.1 SA WG1 reporting
TD SP 200778 (REPORT) SA WG1 Report to TSG SA#89e. (Source: SA1 Chair).
Document for: Presentation.
Abstract: SA WG1 Report to TSG SA#89-e.
Discussion and conclusion:
The SA WG1 Chairman presented rev1 of the report:
https://www.3gpp.org/ftp/tsg_sa/TSG_SA/TSGs_89E_Electronic/Inbox/Revisions/SP-200778_rev1.zip
Slide 4: The TSG SA Chairman asked for confirmation that these times can be adjected if changes are made in the Rel-17 planning in December 2020. This was confirmed.
Slide 3: AT&T commented that it was too soon to start considering Rel-19 and asked SA WG1 not to do this at this time. Also if further deprioritization is needed then items may slip from one Release to the next.
Slide 3: Intel asked how the limit of 15 units was arrived at, if it assumed all WIs need the same amount of time. The SA WG1 Chairman replied this is not a rule, but a recommendation from the SA WG1 Chairman and 15 is not a 'rule' but a workable limit to the time without needing to start using time units. CMCC commented that it can be useful to make SA WG1 more efficient, but as there are a large number of studies ongoing the limits should be set earlier in the cycle. Xiaomi commented that is no new Rel-18 work can be proposed after September 2021 and asked whether given the Rel-17 slippage, more Rel-18 proposals could be possible. This should be discussed over the e-mail. Ericsson commented that there are two issues, the capacity of SA WG1 and its delegates' availability for the diverse topics and also the expectation of deprioritised Rel-17 work which is likely to be included in Rel-18. Huawei commented that imposing a limit of 15 study items is acceptable as a guideline, but should not block SID proposals just because it has been reached.
General: The proposed Rel-18 Freeze dates should be further discussed over e-mail.
The SA WG1 Chairman was thanked for this report, which was noted.
4.2 SA WG2 reporting
TD SP 200670 (REPORT) SA WG2 Report to TSG SA. (Source: SA WG2 Chairman).
Document for: Presentation.
Abstract: SA WG2 Report to TSG SA#89-e.
Discussion and conclusion:
Slide 50: Orange asked whether the Rel-17 timeline should be decided now rather than in December, in order allow better planning in SA WG2. The TSG SA Chairman replied that this is part of the e-mail discussions, but it is also unlikely that TSG RAN will come to a decision at this meeting.
The SA WG2 Chairman was thanked for this report, which was noted.
4.3 SA WG3 reporting
TD SP 200669 (REPORT) SA WG3 Status report. (Source: SA WG3 Chairman).
Document for: Presentation.
Abstract: SA WG3 Status report o TSG SA#89-e.
Discussion and conclusion:
Slide 2: Adrian Escott was congratulated for receiving the 2019 excellence award.
The SA WG3 Chairman was thanked for this report, which was noted.
4.4 SA WG4 reporting
TD SP 200658 (REPORT) SA WG4 Chairman's Report. (Source: 3GPP SA4).
Document for: Presentation.
Abstract: SA WG4 Chairman's Report to TSG SA#89-e.
Discussion and conclusion:
The SA WG4 Chairman was thanked for this report, which was noted.
4.5 SA WG5 reporting
TD SP 200805 (REPORT) SA WG5 Status Report to SA#89-e. (Source: SA WG5 Chairman).
Abstract: SA WG5 Status Report to SA#89-e.
Discussion and conclusion:
The SA WG5 Chairman was thanked for this report, which was noted.
4.6 SA WG6 reporting
TD SP 200825 (REPORT) SA WG6 status report to TSG SA#89. (Source: SA WG6 Chairman).
Document for: Presentation.
Abstract: -
Discussion and conclusion:
The SA WG6 Chairman was thanked for this report, which was noted.
Issues for early treatment
TD SP 200638 LS from ITU-T JCA-IMT2020: LS on Invitation to update the information in the IMT2020 roadmap. (ITU-T JCA-IMT2020)
Document for: Action.
Abstract: The ITU-T Joint Coordination Activity for IMT2020 (JCA IMT2020) thanks all that have replied to previous requests for input on IMT-2020 related standardization work. The current online version of the roadmap is available from the JCA-IMT2020 website. The Objective: of the roadmap is to support IMT-2020 standardization coordination. IMT-2020 is an important topic for our industry, and many standardization-related activities are held in various entities. The JCA is progressing this work in a form of roadmap of IMT2020 standardization. JCA-IMT2020 will keep updating this roadmap, and therefore we solicit your information about updates. If you send us the latest information of your activity related to 5G as well as Network Function Virtualization (NFV), programmable networks, self-managed networks, slicing (including orchestration and capability exposure), fixed-mobile convergence (FMC) and Information-Centric Networking (ICN), machine learning and other activities that are strongly related to IMT 2020, we will reflect it in the next roadmap update, which will be performed online soon after the next JCA IMT2020 meeting. Please submit your updates using the template to be found in appendix below. Should you wish to communicate any additional information about your specifications and projects, we invite you to do so. In addition, if not done yet, we invite the ITU-T Study Groups, SDOs, fora to nominate a representative to this group. JCA-IMT2020 anticipates having its next meeting in 2021, modalities and exact date/timing will be fix and communicated later. We invite your inputs/updates to the roadmap.
Discussion and conclusion:
Response drafted in SP-200856.
TD SP-200856 (LS OUT) [DRAFT] Reply to LS on Invitation to update the information in the IMT2020 roadmap (Samsung).
Discussion and conclusion:
Created at meeting. Response to SP 200638. There were no adverse comments and this LS was approved. (MCC will need to revise to remove 'draft' so there is time for final review and comments).
TD SP 200819 (DISCUSSION) Thoughts about enumerating SA WG1 requirements. (Source: Siemens, Philips).
Document for: Endorsement.
Abstract: We share our thoughts about an enumeration process for SA WG1 reports and specifications.
Discussion and conclusion:
Deutsche Telekom asked whether the enumeration was intended only for requirements related to Verticals, as they have some concerns over doing this for all requirements including architecture requirements, etc. Currently, this was only related to SA WG1. LG Electronics welcomed this proposal which can be very useful, but could foresee problems if this goes beyond SA WG1 as suggested in clause 4, and also into other groups and bodies' specifications. The SA WG1 Chairman commented that within SA WG1 they should be consistent in all their specifications starting at Rel-18, so to enumerate all requirements and not only a subset of them. Qualcomm commented that currently requirements are not enumerated in 21.801 drafting rules and without a change to these this mechanism cannot be fully enabled. Samsung commented that this has been done already for Mission Critical requirements and this could be used as a basis on how to maintain the enumeration with added and removed requirements, without a need to update the drafting rules. Qualcomm asked whether there was any guidance in the drafting rules to ensure that removed lines are marked 'Void' rather than deleting the whole requirement to preserve enumeration. This should be further discussed over e-mail.
TD SP 200850 (DISCUSSION) A Feature is like a worm: don't cut it. (Source: 3GPP Work Plan Coordinator).
Document for: Agreement.
Discussion and conclusion:
The message of this was 'keep all WIDs for a feature in the same Release'. The TSG SA Chairman raised concerns that there may be cases where stage 2 is completed but stage 3 is then not ready and the whole Feature moves to the next Release, which would be counter-productive. The current process protects from unintentional splitting of work in the Work Plan. The Work Plan manager clarified that normal practice has been to keep all parts of feature in the same Release and they have not been split before. The SA WG6 Chairman suggested also tying this discussion with how Release Summaries are done for Features. CMCC agreed with the spirit of this paper and suggested that each non-conformance issue is determined on a case by case basis. The SA WG1 Chairman commented that the normal procedure is to trim the SA WG1 requirements to reflect the final content of the Release. The TSG SA Chairman commented that extracting Features at the stage 2 level is more complicated. The SA WG3 Chairman reported a case for ACMA where a Stage 2 change had needed Stage 3 work which had not been done in Rel-16. The TSG SA Chairman commented that is such a shift of a Feature from a Release is being considered, then this needs to be brought to the attention of all relevant groups and not done purely by MCC. This should be further discussed over e-mail.
TD SP 200798 (SID NEW) Study on vehicle-mounted relays (FS_VMR). (Source: SA WG1).
Document for: Approval.
Abstract: Objective: The aim of this work is to study use cases and potential new service requirements for 5G system support of base station relays mounted on vehicles, using NR self-backhauling to connect with donor gNB and 5GC, including: - Use cases and requirements related to: o Vehicle (base station) relays providing service to UEs inside the vehicle or in the vicinity of the vehicle; o End-to-end service continuity during mobility scenarios (including mobility of the relays); o Provisioning, policies and control mechanisms, e.g. ? Provisioning of spectrum used by the relays, geographic area restrictions for relays; ? Control of relay operation, UEs access and connectivity via relays. - Aspects related to roaming of relays, security, regulatory requirements (e.g. for emergency services), charging, spectrum interference. - Gap analysis between the identified requirements and existing 5GS requirements or functionalities. NOTE 1: potential conflicts with other ongoing studies/work on relays (e.g. RAN IAB) should be avoided. NOTE 2: the base station relay is assumed to use NR-Uu for the connection with the UE, and with donor gNB. NOTE 3: the study should investigate potential new requirements for both UEs and Network; support and impacts for legacy UEs should also be considered. NOTE 4: single-hop (NR-Uu) relay should be the main/baseline scenario; multi-hop (NR-Uu) can also be considered. NOTE 5: main focus should be on relays mounted on ground/land moving vehicles; applicability of general/common requirements to other types of mobile base station relays (e.g. using other moving vehicles or devices) may be considered.
e-mail comment: Tao (China Mobile) objects to SP-200798 and all its revisions. The SID is related with RAN on-going R17 work. In view of potential delay of R17, we believe neither it is right time nor need a study.
Discussion and conclusion:
Qualcomm suggested noting China Mobile comment and proceed to the approval of the SID. AT&T commented that their RAN colleagues did not see any overlap with their work with this proposed study. The TSG SA Chairman pointed out that this had been agreed in SA WG1 and should be further discussed. China Mobile commented that the TSG meeting was considered the right place to make their objections as this is where the approval takes place. This should be further discussed over e-mail.
TD SP 200799 (SID NEW) New Study on network providing access to specific services (FS_PALS). (Source: SA WG1).
Document for: Approval.
Abstract: Objective: The objectives of this study are: - Study use cases for enhanced 5G system support of a hosting network providing users/devices access to specific services, offered by the hosting network operator, other mobile operator(s) or 3rd party provider(s). Including scenarios where: o Access to services through the hosting network could be on demand, temporary and/or cover specific location(s); o The operator of the hosting network, or other mobile operator offering services to users, can be a PLMN or NPN operator; o Different RATs (3GPP or non-3GPP) and spectrum (licensed or unlicensed) could be considered; o The hosting network can also provide specific network services, e.g. location based service, time synchronization etc. - Investigate potential new service requirements, including: o Enabling users/UEs to discover availability of specific target networks and specific services through a hosting network; o Network functionalities to negotiate and configure access and requirements for a specific service (e.g. QoS, network slicing, charging, onboarding etc.); ? Can include policy management, service/QoS monitoring, and interaction between the hosting network and other mobile operator or 3rd party (offering the service) , e.g. via API or other standard mechanisms o Enabling users/UEs to concurrently use specific target services offered through a hosting network and the regular services offered by the HPLMN of the user/UE; o Enabling access to the hosting network and specific services for users/UEs without previous relationship with the hosting network; o Consideration of regulatory and security aspects. - Gap analysis between potential new requirements and existing requirements and functionalities supported by 3GPP, e.g. VIAPA, NPN, slicing, QoS, etc.
e-mail comment: Tao (China Mobile) objects to SP-200799 and all its revisions. The SID shall justified why current VIAPA, NPN, slicing, QoS, edge computing cannot meet the requirement.
Discussion and conclusion:
China Mobile clarified that the proposal was to do the Gap analysis in the normative work, rather than in the study and they did not consider the study necessary as the functionality can be handled by existing Stage 2 features. Samsung replied that this was a Stage 1 study and agreed by SA WG1 and should be allowed to proceed. Intel commented that these SIDs do have a gap analysis in their scopes. The SA WG1 Chairman reported that these two SIDs were agreed without objection in SA WG1 and a Gap analysis is always done in SA WG1, even though there is no requirement to do one. Qualcomm suggested noting China Mobile comment and proceed to the approval of the SID. The TSG SA Chairman asked China Telecom to further discuss this to determine whether some minor changes can resolve their issues with these SIDs and TSG SA should carefully consider whether WG agreed Study items should be rejected this early into their target Release. This should be further discussed over e-mail.
TD SP 200717 (SID NEW) New SID on security aspects of 5G MSG Service. (Source: SA WG3).
Document for: Approval.
Abstract: Objective: The objectives of this study item are - Analyze the security requirements from SA WG1 and SA WG6 about 5GMSG service, and further identify security key issues to fulfil the security requirements. - Based on the security key issues, find out solutions to ensure the functional architecture (including APIs) and the procedures for 5GMSG to avoid security vulnerabilities.
Discussion and conclusion:
e-mail comment: Request for Revision. SA6 Chair (Suresh Chitturi) requests the revision of SA3 SID in SP-200717, to align the terminology with SA6 work on MSGin5G service. The changes are fine and were confirmed offline by the rapporteur. Rev1 based on the proposed changes is available in the Revisions folder.
SP 200717_rev1 was approved.
TD SP 200834 (WID REVISED) Revised WID on Architecture for enabling Edge Applications. (Source: SA WG6).
Document for: Approval.
Abstract: -
Discussion and conclusion:
e-mail comment: Gerald (Matrixx) requests the revision to cover charging management aspects. Suresh Chitturi (SA6 Chair): SP-200834_Rev1 is provided with the help of Rapporteur, taking into account the feedback from Gerald (Matrixx). In addition to Charging aspects from SA5, study on Edge management aspects from SA5 and security enhancements for Edge from SA3 have also been included in the clause 2.3 Other related work-items. Gerald (Matrixx) is fine with the revision.
SP 200834_rev1 was approved.
15min Already available revisions and outgoing LS's
Noting of Block 2
All items marked for Block 2 noting were noted.
Close of CC
The TSG SA Chairman closed this CC at 15.00 UTC.
I.1 SA#89E_CC#3
Third Generation Partnership Project (3GPP™)
SUMMARY Report for TSG SA meeting: #89E (Electronic meeting) Conference Call #3
Opened: Thursday, (2020-09-16) 13:00 UTC
There were ~130 participants on this CC.
Attendees: The following companies were recorded as present (list not exhaustive or verified)
Airbus
Apple
AT&T
BMWi
BT
Charter
China Telecom
CMCC
DENSO
DTAG
Ericsson
FirstNet
Futurewei
Huawei
Intel
Interdigital
IPCom
KDDI
KPN
Kyocera
LGE
Matrixx
MediaTek
Motorola Solutions
Nkom
Nokia
NTIA
NTT DOCOMO
Omnispace
OPPO
Orange
OTD
Perspecta Labs
Qualcomm
Samsung
Sandvine
Siemens
Sony
TEF
Telstra
Tencent
Thales
TIM
T-Mobile USA
TNO
UIC
Verizon
Vivo
Vodafone
Xiaomi
ZTE
NOTE: Meeting notes are not exhaustive and may not contain all the comments made during the conference call.
Opening of meeting
The TSG SA Chairman opened this CC at 13.00 UTC.
The CCs agenda was revised for this in:
https://www.3gpp.org/ftp/tsg_sa/TSG_SA/TSGs_89E_Electronic/Inbox/Revisions/SP-200855_rev2.zip
Issues for early treatment which have not been opened yet
SP-200861 (LS In) LS from TSG CT: LS on information of stage 3 aspects for AKMA (TSG CT).
Document for: Action.
Abstract: TSG CT has approved the WID AKMA-CT in Release 17 to implement the AKMA in stage 3, whereas the corresponding stage 2 requirements are in Rel-16. Action: TSG CT kindly ask TSG SA and SA WG3 to take above into account.
Discussion and conclusion:
The question on whether to leave AKMA in Rel-16 or to move it to Rel-17 in the specifications. The SA WG3 Chairman commented that there is no issue with either decision and there are two TSs which will need update if the AKMA functionality needs to be removed from Rel 16. SA WG3 wee asked to create CRs to remove functionality from Rel 16 and include it in Release 17. Huawei commented that this should be done by first inserting it into Rel 17 with a TS upgrade to Rel 17 and then to remove from Rel 16 with CRs. The SA WG3 Chairman commented that the provision of any necessary WID update and CRs should follow the usual contribution-based process at SA WG3 meetings. CMCC commented that SA WG2 can move the AKMA functionality to Rel-17 but it should not be re-scoped due to this decision. Any proposals for change to the scope of the work should follow the usual procedures. Matrixx suggested moving this from a Building Block to a Feature in the Work Plan.
Summary:
SA WG3 and SA WG1 will work on CRs that will propose to shift AKMA SA WG3 to Rel-17. If additional changes are requested in SA WG3/SA WG1 then those requests need to be handled in separate discussions. Matrixx proposed to change SA WG3 WID from BB to Feature – this will be handled in SA WG3 discussions.
This LS was then noted.
SP-200718 (WID NEW) New WID on mission critical security enhancements phase 2.
e-mail comments:
AT&T supports approval of 'New WID on mission critical security enhancements phase 2' in SP-200718.
'Airbus' supports approval of 'New WID on mission critical security enhancements phase 2' in SP-200718
The WID has been revised to correct and extend the list of supporting companies.
'Erillisverkot' supports approval of 'New WID on mission critical security enhancements phase 2' in SP-200718
FirstNet supports approval of 'New WID on mission critical security enhancements phase 2' in SP-200718
The WID has been further revised to extend the list of supporting companies.
Discussion and conclusion:
SP-200718_rev2 was provided and was approved. (To be revised into a new TD number by MCC).
TD SP 200790 (CR PACK) Stage 1 CRs on eCAV. (Source: SA WG1).
Document for: Approval.
Abstract: 22.104 CR0055; 22.832 CR0029; 22.832 CR0030; 22.261 CR0465R1; 22.104 CR0053R1; 22.104 CR0058R1; 22.261 CR0462R2.
e-mail comments:
The tdocs SP-200790 to SP-200794 were submitted under agenda item 16.1 but include SA1 CRs against Rel-17 specs. Therefore they are shifted to Agenda Item 17.1
LG Electronics raises hands for minor admin stuff: (1) SP-200791 is an R17 CR but is using an R16 WI code (not a mirror from R16) (2) SP-200793 is using an R16 WI code (FS_FRMCS2 is not for R17). These may be addressed/corrected.
Haris (Qualcomm) comments that this CR pack relates to the discussion of enumeration of requirements in SP-200819 and wants to flag it up for discussion
Discussion and conclusion:
This was removed from block approval due to issues raised. Qualcomm clarified that all the CRs in this pack are related to the Stage 1 Requirements enumeration discussion. LG Electronics requested that 22.261 CR 0462R2 should be revised to remove requirement 10. Other changes were also needed and this was left for e-mail discussion.
LG Electronics added the following clarification for their comments in the CC:
LG Electronics appreciates the effort on this quality improvement CR proposal but expresses their concerns about the change component #10 of CR0462r2 and #20 of CR0465r1 (from SP-200790) which had "accidentally" not been reviewed correctly before agreed in SA1#91e due to some difficulty in e-meeting setup. Clause 6.20 of TS 22.261 is intended to serve as a pointer, but not as a clause providing a technical requirement itself. Therefore, it was originally intended and agreed to be written in a normal tense as a pointer instead of a "shall" tense, which means it itself is just a pointer for the reader.
LG proposes to take CR0462r2 out from the CR pack SP-200790 and not to accept the change component #10 (for clause 6.20.2).
LG proposes to take CR0465r1 out from the CR pack SP-200790 and not to accept the change component #20 (for clause 6.20.2).
TD SP 200706 (CR PACK) Rel 16 CRs on Security for enhancements to the Service Based 5G System Architecture. (Source: SA WG3).
Document for: Approval.
Abstract: 33.536 CR0006R1; 33.501 CR0880R1; 33.501 CR0900R1; 33.501 CR0904R1; 33.501 CR0903R1; 33.501 CR0908R1; 33.501 CR0905R2.
e-mail comments:
CR 0908 33501 in CR pack SP-200706 belongs to the wrong specification and hence it should be removed from the pack.
Discussion and conclusion:
33.501 CR0908R1 was rejected. Al other CRs in this CR Pack were approved. (The CR Pack was partially approved).
TD SP 200857 (CR) Making NF instance id in SBA certificate profile mandatory to support. (Source: Nokia).
Document for: Approval.
Abstract: 22.889 CR0169R2.
Discussion and conclusion:
This CR was approved.
Already available revisions and outgoing LS's
TD SP 200810 [DRAFT] reply LS on RAN impact of FS_5MBS Study. (Huawei [SA])
Document for: Approval.
Abstract: SA would like to clarify that NR-based broadcast is within the scope of SA SID for 'Study on architectural enhancements for 5G multicast-broadcast services',
e-mail comments:
Haris (Qualcomm) proposes that SA conveys the message to SA2 that for NR broadcast SA2 needs to spend more time to document more solutions
Wanqiang (Huawei) give the feedback on QC proposal and make further update.
Discussion and conclusion:
SP 200810_Rev2 was provided. It was noted that the document file in the zip was marked rev3, although it was rev2 on the zip file. SP 200810_Rev2 was approved. (To be revised into a new TD number by MCC).
TD SP 200654 LS from CT WG1: LS on the Stage 2 aspects of MINT. (CT WG1)
Document for: Action.
Abstract: CT WG1 has discussed a WID proposal for CT aspects of Minimization of Service Interruption (MINT-CT) in the CT WG August meetings, in order to support the service requirements specified for Rel 17. The WID on MINT-CT includes a study phase on both stage-2 and stage-3 aspects. CT WG1 is also planning to define end-to-end call flow regarding registration after selection of a disaster roaming PLMN in the stage-2 specification owned by CT WG1. CT WG1 would like to ask TSG SA if there is any concern on this approach. CT WG1 expects any feedback on this way forward until the next WG meeting so that both study phase and normative phase can progress within Rel 17 timeframe. Action: CT WG1 kindly asks TSG SA to take the information above into account and to provide feedback.
Discussion and conclusion:
Response drafted in SP-200775.
TD SP 200775 [DRAFT] Reply LS on the Stage 2 aspects of MINT. (LG Electronics)
Document for: Approval.
Abstract: [DRAFT] Reply LS on the Stage 2 aspects of MINT (CT WG1 LS, C1-205332).
e-mail comments:
Chia-Lin (MediaTek) still think SA2 should be involved from the study phase
Hyunsook (LGE) initiates discussion for the revision of SP-200775, and provides rev1.
Guillaume (MediaTek) can agree moving forward as proposed
Hyunsook (LGE) provides comments.
Chris (Vodafone) believes that it will be OK for CT (1) to open a SID on this topic provided that the study includes the topics of protecting non-failed PLMNs and recovering PLMNs from signalling overload. Once the STUDY is completed, 3GPP should then decide on how to proceed with any normative work.
Hyunsook (LGE) think Chris's suggestion is same to CT1 approach.
CT1 LS already describes a study phase, and as usual CT1 business, CT1 will have normative work based on study results.
Chris (Vodafone): it is OK for CT(1) to commence a SID but NOT to include a normative work in it. The SID needs to include at least:
a) How one PLMN failure does not lead to signalling overload in other PLMNs; and
b) how to avoid 'returning UEs' overloading the PLMN that had earlier failed.
Discussion and conclusion:
Response to SP-200654. SP 200775_rev2 was provided. There was some discussion and a further revision was proposed by Vodafone in _rev3. SP 200775_rev3 was approved. (This will be cleaned up and revised into a new TD number by MCC).
TD SP 200796 [DRAFT] LS On 5G GUTI reallocation for CIoT. (Qualcomm Korea)
Document for: Approval.
Abstract: Provides instructions on allocating new 5G GUTI at every signalling transaction trigged by paging.
e-mail comments:
Haris (Qualcomm) starts email discussion
Krister (Ericsson) states that me the option 1 is a special case of option 2. As said I see that the frequency of refresh of a temporary identifier is decided by the network operator. The operator may then configure AMF so option 1 is the behavior. That can be the correct behavior for normal UEs as there is a risk of an attack of tracking a UE, which is a privacy concern for the user.
There may be other IoT devices which does not have the same strict privacy requirement, and as such could benefit from a less often refresh of GUTI. The gain would be in signaling optimizations.
Wanqiang (Huawei) comment that option 2 brings extra complexity and makes the system unmanageable. It is not a reasonable approach to move forward.
Johannes (Deutsche Telekom) supports option1 and supports the text in the LS as is. DT ranks the privacy and security issues as higher priority than optimizations. Exception to the existing procedures shall not be granted.
Lars (Sony) comment that option 1 will bring extra complexity and new triggers for AMF to perform UCU. And ask a question on the privacy issue.
Krister (Ericsson) comments that there is has only been a discussion here about privcay related to tracking a UE moving. No other security related issues identified.
Johannes (Deutsche Telekom) clarifies that option1 reflects the specified solution of 5GS and option2 is the request for exceptional hanlding of certain UEs in 5GS
Lars (Sony) option1 goes beyond the existing procedures.
Haris (Qualcomm) provides response to Wangqiang
Erik/Andy (Samsung) supports option 1, as there is privacy threat.
Hucheng(CATT) supports option1, but thinks, if understanding is correct, the wording of option 1 could be enhanced:
'Option 1: Allocation of a new 5G-GUTI temporary identifier to the UE in IDLE mode in response to paging in 5G is mandatory and shall apply in all cases including all CIoT optimisations'
From the clarifying question(s) I (Chris, Vodafone) asked in the Tuesday web call, I understand that the options are actually:
Option 1: the standards shall enable GUTI reallocation at every Mobile Terminating RRC connection establishment.
Option 2: the standard prevents GUTI reallocation at every Mobile Terminating RRC connection establishment.
In which case Vodafone prefers option 1.
Haris (Qualcomm) observes that there is preference to go with Option 1 and suggests companies to propose comments to the wording
Orange supports Option 1.
While Option 2 may give operators the flexibility of managing the (signalling) optimization which can be of significance for CIoT devices/applications without temporary GUTI allocated each time paging is performed, it may introduce some extra complexity, if, e.g. the exception should be given by HPLMN and/or VPLMN in roaming, when and for what CIoT devices/applications should be given the exception, even if it is configurable. This may adversely affect the optimization intended by Option 2.
In addition, SA3 has already clearly defined in TS 33.501 from Release 15 that the mandatory allocation by AMF of a new 5G-GUTI temporary identifier to the UE in response to a Paging message as a security and privacy protection enhancement of 5G. Option 2 would cause some mis-alignment and even contradictions with the SA3 specifications and open up more discussions/work in SA2, SA3 and CT1 at least about to dynamically configure GUTI for those that requires enhanced security for some CIoT devices/applications vs those that may have less security constraints. This may adversely affect achievable optimization after all.
Saad (Interdigital). Interdigital also preferers option 1.
Wanqiang (Huawei) provides further comments regarding the update from Ericsson and propose to stick to the original text in SP-200796.
Krister (Ericsson) provides update of the text in option 1. Option 1: Upon receiving a temporary identifier (S-TMSI or I-RNTI) sent by a UE in response to a paging message, it is mandatory for the network to re-allocate the used temporary identifier that was sent in the response message from the UE. This requirement is valid for any type of UE.
Haris (Qualcomm) provides response to Chris(Vodafone)
Lars (Sony) provides further comments on the privacy issue.
Krister (Ericsson) asks Wanqiang to explain the loose comment which missed to explain 'track the link'. Ericsson can not agree the original text of QC as it is not covering the 3rd case that I describe below.
Wanqiang (Huawei) provides response and ask further question.
Lars (Sony) We support Krister's alternative option 1 wording.
Haris (Qualcomm) comments that the thread is for the approval of original or potentially revised text in SP-200796 and the text in SP-200795 is not going to be further modified since the paper is already noted
Krister (Ericsson) provides provide revision to the draft LS in rev1.
(Samsung) provides details on the privacy threat. Clarifies that temporary identifiers (S-TMSI and/or I-RNTI) that were used in the paging message and sent by a UE in response to a paging message should be re-allocated. Re-allocation of I-RNTI is mandated by TS 33.501, similarly 5G-GUTI needs to be reallocated.
Discussion and conclusion:
SP-200796_Rev3 was the latest proposal. Qualcomm commented that they objected to Rev3. Ericsson commented that it was unfortunate that there were 'hidden agendas' in companies leading to a blocking in progress on these discussions. Intel asked how urgent it was to make a decision at this meeting and whether SA WG3 would be asked to further discuss this. Nokia commented that SA WG3 had already discussed this extensively and supported the proposal of Qualcomm and asked to consider the latest proposals. Huawei commented that no further progress can be expected from SA WG3 and suggested making a Working Agreement if this cannot be resolved. Ericsson commented that there is higher security being considered for this feature, rather than lower, and there are studies done by outside bodies which identify the difficulties of different methods of tracking UE identities and recommended companies review these. The TSG SA Chairman commented that a Working Agreement on the LS may not be possible and will check on this as a possibility if required. This was left for further off-line discussion.
Further issues arising from ongoing e-mail discussions
TD SP 200822 (SID NEW) New SID on Study on Support for Service Function Chaining in 5G System. (Source: Intel Corporation, Deutsche Telekom AG, Tencent, Telefónica, Affirmed Network, AT&T, Sandvine, Convida Wireless, InterDigital, KPN, Verizon UK Ltd., KDDI, Vodafone, Telecom Italia, Cisco, b<>com).
Document for: Approval.
Abstract: Objective: The aim of this work is to study the enable support of service function chaining in 5G system for value-added services provided by network operators to third parties, including:. The study will consider useUse cases and service requirements related to: - provide service definition of supported service functions and service function paths; - provide service configuration and management support of service functions and service function paths to third parties for applications and their users with value-added services, e.g. provided by 5GS only or both of 5GS and 3rd parties; - provide continuing same value-added service experiences for UEs using 5G services, e.g. eMBB, V2X, AVPROD, NCIS, etc., and moving between networks. Gap analysis between the identified service requirements and existing 5GS service requirements or functionalities. Note: the gap analysis takes into account previous work related to Stage 1 services requirements on SFC already developed in other SDOs (e.g. IETF RFC 7665, IETF RFC 8300, IETF RFC 8459, ITU-T Y.2242, etc).
e-mail comments:
Saso (Intel) initiates discussion thread on SP-200822.
Nokia has concerns with approving a SID on this topic as we believe that the best course of action would be to ask companies to propose a WID and related CRs in Q4 with the delta requirements that are not yet captured in TS 22.261 ( also by inheritance of those in TS 22.101 clause 30).
Patrice (Huawei) provides concerns, and proposes that discussion continues further in WGs before we can approve something (for minutiae: objects to the original paper).
Adrian (vivo) asks a question for clarification.
Krister (Ericsson) has the same view as expressed by Huawei. In addition pointing out that the 22.261 has the requirement that
, the 5G system shall support all EPS capabilities (e.g. from TSs 22.011, 22.101, 22.278, 22.185, 22.071, 22.115, 22.153, 22.173, 22.468),
In SA1 we are with term 5G System including SA2 N6-LAN as part of 5G System.
Saso (Intel) replies to comments. Seeks clarification from SA1 Chairman.
Discussion and conclusion:
Intel reported that there was no consensus on this and suggested going forward with a WID update and CRs in SA WG1 and asked TSG SA to endorse the 3 items:
1 Acknowledging that N6-LAN is in scope (22.101 currently states SGi-LAN is out of scope)
2. Allowing third parties to configure service functions and SF paths for their applications
3. Adding requirements for management of SFs and SFPs intended primarily for enabling SA WG5 work.
Huawei commented that these issues should be raised in an input document to the meeting and suggested discussing this at the next meeting. Vodafone commented that this has been extensively discussed in SA WG1 and proposed TSG SA endorse such bullets and asked whether the SID should be also converted to a WID. Nokia considered it too late in the meeting to submit a new WID for discussion and asked whether this could be left for the next meeting, which would allow SA WG1 to discuss the detail and agree CRs. Deutsche Telekom agreed with Nokia and supported converting the SID to a WID at this meeting as objections to progressing a SID are difficult to understand from a technical point of view. Vodafone, Deutsche Telekom and Telecom Italia supported attempting to produce a WID for approval at this meeting. Intel agreed to provide a proposal as a rev of this SID. AT&T and Vivo supported this proposal.
Summary:
This issue will be handled further in SA WG1. Saso will provide a WID proposal for discussion on Friday.
TD SP 200798 (SID NEW) Study on vehicle-mounted relays (FS_VMR). (Source: SA WG1).
Document for: Approval.
Abstract: Objective: The aim of this work is to study use cases and potential new service requirements for 5G system support of base station relays mounted on vehicles, using NR self-backhauling to connect with donor gNB and 5GC, including: - Use cases and requirements related to: o Vehicle (base station) relays providing service to UEs inside the vehicle or in the vicinity of the vehicle; o End-to-end service continuity during mobility scenarios (including mobility of the relays); o Provisioning, policies and control mechanisms, e.g. ? Provisioning of spectrum used by the relays, geographic area restrictions for relays; ? Control of relay operation, UEs access and connectivity via relays. - Aspects related to roaming of relays, security, regulatory requirements (e.g. for emergency services), charging, spectrum interference. - Gap analysis between the identified requirements and existing 5GS requirements or functionalities. NOTE 1: potential conflicts with other ongoing studies/work on relays (e.g. RAN IAB) should be avoided. NOTE 2: the base station relay is assumed to use NR-Uu for the connection with the UE, and with donor gNB. NOTE 3: the study should investigate potential new requirements for both UEs and Network; support and impacts for legacy UEs should also be considered. NOTE 4: single-hop (NR-Uu) relay should be the main/baseline scenario; multi-hop (NR-Uu) can also be considered. NOTE 5: main focus should be on relays mounted on ground/land moving vehicles; applicability of general/common requirements to other types of mobile base station relays (e.g. using other moving vehicles or devices) may be considered.
e-mail comments:
Tao (China Mobile) objects to SP-200798 and all its revisions. The SID is related with RAN on-going R17 work. In view of potential delay of R17, we believe neither it is right time nor need a study.
Discussion and conclusion:
China Mobile withdrew their objection with the understanding that there will be a gap analysis done in the study phase and expressed their disappointment that this could not move forward after long discussions, contribution, clarification and merging of proposals. This new SID was then approved.
China Mobile provided the following statement:
With the understanding that requirement gap can be identified in study phase, as clearly stated in this SID, Tao Sun (China Mobile) recall the objection. China Mobile expect the same chance and raise the concern that R18 stage 1 Study proposal cannot move forward after 6 month effort with two companies' claim of insufficient gap analysis even contributors provided discussion paper, online and offline clarifications, long list of supporting companies, merge multiple proposals as requested.
TD SP 200799 (SID NEW) New Study on network providing access to specific services (FS_PALS). (Source: SA WG1).
Document for: Approval.
Abstract: Objective: The objectives of this study are: - Study use cases for enhanced 5G system support of a hosting network providing users/devices access to specific services, offered by the hosting network operator, other mobile operator(s) or 3rd party provider(s). Including scenarios where: o Access to services through the hosting network could be on demand, temporary and/or cover specific location(s); o The operator of the hosting network, or other mobile operator offering services to users, can be a PLMN or NPN operator; o Different RATs (3GPP or non-3GPP) and spectrum (licensed or unlicensed) could be considered; o The hosting network can also provide specific network services, e.g. location based service, time synchronization etc. - Investigate potential new service requirements, including: o Enabling users/UEs to discover availability of specific target networks and specific services through a hosting network; o Network functionalities to negotiate and configure access and requirements for a specific service (e.g. QoS, network slicing, charging, onboarding etc.); ? Can include policy management, service/QoS monitoring, and interaction between the hosting network and other mobile operator or 3rd party (offering the service) , e.g. via API or other standard mechanisms o Enabling users/UEs to concurrently use specific target services offered through a hosting network and the regular services offered by the HPLMN of the user/UE; o Enabling access to the hosting network and specific services for users/UEs without previous relationship with the hosting network; o Consideration of regulatory and security aspects. - Gap analysis between potential new requirements and existing requirements and functionalities supported by 3GPP, e.g. VIAPA, NPN, slicing, QoS, etc.
e-mail comments:
Tao (China Mobile) objects to SP-200799 and all its revisions. The SID shall justified why current VIAPA, NPN, slicing, QoS, edge computing cannot meet the requirement.
Discussion and conclusion:
China Mobile withdrew their objection with the understanding that there will be a gap analysis done in the study phase and expressed their disappointment that this could not move forward after long discussions, contribution, clarification and merging of proposals. This new SID was then approved.
China Mobile provided the following statement:
With the understanding that requirement gap can be identified in study phase, as clearly stated in this SID, Tao Sun (China Mobile) recall the objection. China Mobile expect the same chance and raise the concern that R18 stage 1 Study proposal cannot move forward after 6 month effort with two companies' claim of insufficient gap analysis even contributors provided discussion paper, online and offline clarifications, long list of supporting companies, merge multiple proposals as requested.
Listing issues which will stay under discussion until Friday
TD SP 200819 (DISCUSSION) Thoughts about enumerating SA WG1 requirements. (Source: Siemens, Philips).
Document for: Endorsement.
Abstract: We share our thoughts about an enumeration process for SA WG1 reports and specifications.
e-mail comments:
LG Electronics indicates the facts that it is beneficial to have requirements enumerated in some specifications, if not all, and that the idea of enumeration can be made 'Recommended Practice' within a WG, which means that if enumeration of some requirements of a certain TR or TS is considered needed, it can be done in that particular WG but it does not have to be enforced. Generalization of this idea of enumeration may require careful consideration and examination as maintenance of them, if happens, is a different story requiring different dimension of complexity compared to the benefit it seems to bring in. No discussion for 21.801 is necessary. LG Electronics proposes the following sentence to be added to the revision of SP-200819 for endorsement.
The enumeration of requirements of a TR/TS is recommended on a need basis but is not necessarily required for all TR/TS's. The requirement numbers go with the TR/TS version, which mean they might be different in a different version of the TR/TS, i.e., changed, deleted, or replaced along with how an existing requirement is destined to be in the next version of TR/TS during the casual course of work, including changes by technical (p)CRs and/or maintenance CRs.
Adrian (vivo) asks LG what do they mean 'on a need basis?'
In response to NCSC's comment, LG provides the following:
The enumeration of requirements of a TR/TS is recommended on a need basis but is not necessarily required for all TR/TS's. The requirement numbers go with the TR/TS version, and are recommended not to change drastically in order to keep the ease of reference unless there are relevant reasons (e.g., deletion, merge, relocation, etc.) which mean they might be different in a different version of the TR/TS, i.e., changed, deleted, or replaced along with how an existing requirement is destined to be in the next version of TR/TS during the casual course of work, including changes by technical (p)CRs and/or maintenance CRs.
Haris (Qualcomm) would like to see first a CR to TR 21.801 before agreeing on this idea of enumerating SA1 requirements endorsed officially. Recommends to have some email discussion e.g. moderated by someone, that will discuss all aspects mentioned below and we can come to some smooth discussion in SA#90e.
Tony (Futurewei) would like to support the enumeration of the requirements in stage-1 specifications with the understanding that procedures for doing so will be captured/specified officially.
Ki-Dong (LGE) raises comments on what Puneet (SA2 Chairman) responded to Adrian(Vivo) to clarify that we do not need both mappings (e.g., b/w CPR and PR, CPR and UC) but one mapping table between CPRs and PRs is enough for traceability purposes as long as PRs come with clause numbers.
Puneet (SA2 Chairman) responds to Adrian(Vivo).
Adrian (vivo) support the enumeration of the requirements in stage-1 specifications and asks Puneet a question for clarification.
Puneet (SA2 Chairman) support the enumeration of the requirements in stage-1 specifications. Proposes further enhancements.
Ericsson wants to point out that it should not be any tracking process between SA1 TRs and TSs. The reason is that potential requirements are just potential and important that there is a freedom to change requirements in normative work, even beyond recognition. As we work consensus based that should be the principle.
Siemens agrees with Ericson that there should not be any tracking process between SA1 TRs and TSs and points out that SP-200819 does not stipulate such process.
Siemens also thinks that a change to a 21 document, for instance TR 21.801, is needed before requirement enumeration in Stage-1 specifications can become officially endorsed by SA. Siemens also agrees with Qualcomm that a pertinent CR should be discussed on the email reflector before presenting it at SA#90-e.
Johannes (Deutsche Telekom) does see a heavy overcomplication of introducing the need for requirements numbering and objects to endorsing a guidance before this is discussed in more details, potentially ending up in a CR to the drafting rules in TR 21.801.
Siemens uploaded SP-200819rev01 to the Revisions folder. Changes made: added Daimler and Sennheiser as source; included a sentence in clause 3.1, stating that the requirements in technical specifications do not track potential and consolidated potential requirements in technical reports.
Huawei support to develop a mechanism to better trace the requirements in stage-1. This is beneficial not only for verticals but also for coordination between SA1 and other WGs. We would also like to see a CR capturing the details in 21.801 and we can have an offline email discussion on it, and target to provide the concrete mechanism in next plenary. Whether we implement it to all the specifications in SA1 can also be discussed once the mechanism is clear.
ZTE prefers to stick to existing drafting rule and does not support the enumerating of requirement.
Philips responds to ZTE and DT.
Jinguo response to Philips and is fine if the enumerating requirement is only applied to SA1.
Johannes (Duetsche Telekom) asks for clarification on the proposal from SA1 chair: currently we have SA1 CRs submitted to this plenary even for Rel16 specs to implement the enumeration of requirements before we have concluded on a way forward. Do we postpone these CRs for a treatment in SA#90-e?
Discussion and conclusion:
Latest proposal was SP-200819_rev01. The TSG SA Chairman asked whether we can review and approve the related CR packs. Qualcomm commented that they could not agree to the CRs at this time and suggested further discussion. Deutsche Telekom commented that the CRs are only editorial categories (D) and suggested this is further discussed to have a method for handling such changes in the future. Vodafone agreed that this should be taken as a general procedural discussion on whether and how such changes should be allowed to frozen Releases. Siemens accepted that further discussion was required but these should not be rejected based on their category and only some of the CRs can be discarded. TSG SA Chairman will start a moderated TSG SA e-mail discussion on the enumeration issue until the next TSG SA meeting. This was then noted.
TD SP 200791 (CR PACK) Stage 1 CRs on ID_UAS. (Source: SA WG1).
Document for: Approval.
Abstract: 22.125 CR0028R5.
Discussion and conclusion:
SP-200791_Rev1 was provided. This was approved. (To be revised by MCC to provide a new TD number).
LG Electronics added the following clarification for their comments in the CC:
LG Electronics raises hands for minor admin stuff: (1) SP-200791 is an R17 CR but is using an R16 WI code (not a mirror from R16). This may be addressed/corrected.
MCC responded that ID_UAS is Rel-16 WI code and will be replaced by EAV.
TD SP 200793 (CR PACK) Stage 1 CRs FS_FRMCS3. (Source: SA WG1).
Document for: Approval.
Abstract: 22.889 CR0169R2.
Discussion and conclusion:
SP-200793_Rev1 was provided. This was approved. (To be revised by MCC to provide a new TD number).
LG Electronics added the following clarification for their comments in the CC:
LG Electronics raises hands for minor admin stuff: (2) SP-200793 is using an R16 WI code (FS_FRMCS2 is not for R17). This may be addressed/corrected.
MCC responded that FS-FRMCS3 will be used in the next revision.
TD SP 200784 (CR PACK) Stage 1 CRs on cyberCAV. (Source: SA WG1).
Document for: Approval.
Abstract: 22.261 CR0455R1; 22.261 CR0456R1; 22.261 CR0464R1; 22.104 CR0054R1.
Discussion and conclusion:
This was removed from block approval due to issues raised. 22.104 CR0054r1 and 22.261 CR0464 removed from the pack for further discussion. The other CRs in this CR Pack were approved. (This CR Pack was partially approved).
TD SP 200862 [DRAFT] LS on R17 schedule (TSG SA).
Document For: Approval.
Abstract: To: SA WG1, SA WG2, SA WG3, SA WG4, SA WG5, SA WG6. CC: TSG RAN, TSG CT
Discussion and conclusion:
A draft_r0 was provided and was reviewed on-line. TSG CT should be included in the "To" field and Work items should be WIDs. Some further clarifications were needed and the corrected version was provided in the revisions folder as SP-200862_rev1.
TD SP 200850 (DISCUSSION) A Feature is like a worm: don't cut it. (Source: 3GPP Work Plan Coordinator).
Document for: Agreement.
e-mail comments:
SA Chair disagrees with the paper, as it holds implications which might work negatively in progressing the work of 3GPP. The proposal from the SA Chair is to investigate features, which are only partially complete, on a case-by-case basis. This can be done as only very few such features appear in the end of the release.
Johannes (Deutsche Telekom) raises the point that SA1 is performing in each release a clean-up of requirements, which did not conclude in stage2 and stage3, e.g. just refer to documents SP-200785 (REAR), SP-200788 (UIA) and SP-200787 (5GSAT). DT concurs with the assessment of the conclusion in SP-200850 to have a full operational system per Release. So the general aim of 3GPP should be to have self-contained releases with functionable features. Exception sheets are sommonly used to conclude past the freeze date.
MCC clarifies that SP-200850 is not meant to open a debate but to remind delegates of a 3GPP basic principle: see 3GPP Working Procedures TR 21.900 clauses 4.0B and 4. The principle of not cutting a Feature onto different Releases has been emphasized on several occasions, e.g. in SP-120387 (co-signed by the former SA1 and SA chairs), and it is the usual way of working in SA1, where the (elements of the) Stage 1 of the Features not completed in time for a given Release are removed from the documentation of this Release (see SP-200785, SP-200788 or SP-200789 just for TSG#89e), while retained in the documentation of the next Release.
Whatever the approach, it has to be consistent across all 3GPP WGs and TSGs. If this approach is not valid anymore, the Work Procedures should be amended.
Telefonica strongly disagrees with this paper. It goes against the independency of the work already developed in previous stages and it gives higher decision powers to the working groups (and therefore the companies) working on later stages
The SA5 chair supports the objection (on the contribution's original contents) and comments from the SA chair and SA3-LI chair.
Orange stated the Workplan and the Release roadmap is based on the principle that stage 1, stage 2 and stage 3 for a given feature are completed at the release date freeze. We can agree decide to allow exception to complete the work but it also assumed that features will be shift to the next release if not possible to complete in a given time. As long as 3GPP will rely on the notion of 'Release', the principles given in SP-200850 should be used as guidance, even if it is always possible to agree on a specific handling for a given feature.
The SA2 chair supports the objections and disagrees with the conclusions of the paper.
SA6 Chair (Suresh) agrees with points made by Georg (SA Chair) and Lionel (CT Chair), but prefers to defer any guidance to SA#90-e and continue this discussion offline with interested parties.
Telefonica still disagrees with v1 since it does not solve the issues pointed out by our previous comment
Upon providing SP-200850rev2, the MCC Work Plan manager (Alain) clarified that this document is not meant to modify anything in the 3GPP Working Procedures. On the contrary: it is meant to remind to all delegates the current, long-standing, 3GPP principles and check how they can be followed even better than now.
This document can be further improved, as e.g. to include the CT Chair's comments.
Discussion and conclusion:
The latest revision SP-200850_Rev2 was presented. The SA WG6 Chairman commented that these proposals should be taken into account as far as possible with respect to determining when a feature is fully complete and there are no missing components which may be discovered later. This should be handled using the current rules of decision by company input contributions and consensus. Telefonica commented that this would need further consideration and that there are places where the wording can be significantly clarified. The TSG CT Chairman commented that this has resulted in a better understanding of the 3GPP procedures and could benefit from further clarification. This was then postponed.
TD SP 200649 LS from CT WG4: LS on AUSF/UDM discovery based on SUCI information. (CT WG4)
Document for: Information.
Abstract: CT WG4 has analyzed the issue of insufficient length of Routing Indicator within SUCI, see attached discussion paper in C4-204078 for details. The current 4 digits of the Routing Indicator enables only 10 K ranges of subscriptions, which may not provide enough granularity and flexibility for moving subscriptions across UDRs not controlled by the same AUSF/UDM, for operators with a large number of subscriptions (e.g. 100 K users per range for a PLMN with 1 billion subscriptions). CT WG4 agreed that the above limitation should be addressed. CT WG4 has also discussed the solution proposed in C4-204339 (attached) for solving this problem, enabling to use the Home Public Key ID as an additional parameter (that allows to encode e.g. a 5th digit, in addition to the key ID on 4 bits) for the discovery of the AUSF/UDM. CT WG4 would be fine in principle to specify this solution in Rel 17, provided corresponding stage-2 requirements are agreed first.
e-mail comments:
Tao (China Mobile) ask for SA discussion on proper way forward in stage 2 so that stage 3 can start.
Discussion and conclusion:
This was presented by China Mobile. The TSG CT Chairman asked SA WG2 to make time to progress the Stage 2 enhancement in the next Quarter, to allow CT WG4 to progress with this. The SA WG2 Chairman replied that this will be on the agenda for the e-meeting and will require company contribution of CRs for this, with Category F CRs, as no exception is expected to be produced for Rel-17 work. This remained noted.
Approval Block 4, Block 5, Noting Block 6
The documents indicated for Blocks 4, 5 and 6 were approved, endorsed or noted, as appropriate.
SP-200659 CR PACK Approval CRs to TS 26.116 SA WG4 Approved
SP-200660 CR PACK Approval CRs to TS 26.223 SA WG4 Approved
SP-200661 CR PACK Approval CRs to TS 26.234 SA WG4 Approved
SP-200662 CR PACK Approval CRs to TS 26.238 SA WG4 Approved
SP-200663 CR PACK Approval CRs to TS 26.501 SA WG4 Approved
SP-200664 CR PACK Approval CRs to TS 26.511 SA WG4 Approved
SP-200665 CR PACK Approval CRs to TS 26.114 SA WG4 Approved
SP-200666 DRAFT TS Approval Draft TS 26.512: 5G Media Streaming (5GMS); Protocols SA WG4 Approved
SP-200667 WID NEW Approval New Work Item on 'Operation Points for 8K VR 360 Video over 5G'. Intel, NHK, Ericsson LM, AT&T, Qualcomm Incorporated, Dolby Laboratories Inc., Beijing Xiaomi Electronics, Tencent, Huawei Technologies Co Ltd. Approved
SP-200668 CR PACK Approval CR to 26.247 SA WG4 Approved
SP-200671 CR PACK Approval CRs to 23.501, 23.502 on 5GS_Ph1 (Rel-15, Rel-16) SA WG2 Approved
SP-200672 CR PACK Approval CRs to 23.401 on NB_IOTenh-Core, CIoT_ext (Rel-15, Rel-16) SA WG2 Approved
SP-200673 CR PACK Approval CRs to 23.501, 23.502, 23.503 on 5G_CIoT (Rel-16) SA WG2 Approved
SP-200674 CR PACK Approval CRs to 23.501, 23.502 on 5G_eSBA (Rel-16) SA WG2 Approved
SP-200675 CR PACK Approval CR to 23.501 on 5G_URLLC (Rel-16) SA WG2 Approved
SP-200676 CR PACK Approval CRs to 23.316, 23.502 on 5WWC (Rel-16) SA WG2 Approved
SP-200677 CR PACK Approval CR to 23.501 on ATSSS (Rel-16) SA WG2 Approved
SP-200678 CR PACK Approval CRs to 23.228, 23.501 on eIMS5G_SBA (Rel-16) SA WG2 Approved
SP-200679 CR PACK Approval CRs to 23.228, 23.502, 23.503 on eNA (Rel-16) SA WG2 Approved
SP-200680 CR PACK Approval CRs to 23.502 on eNS (Rel-16) SA WG2 Approved
SP-200681 CR PACK Approval CRs to 23.502 on ETSUN (Rel-16) SA WG2 Approved
SP-200682 CR PACK Approval CRs to 23.285, 23.287, 23.502, 23.503 on eV2XARC (Rel-16) SA WG2 Approved
SP-200683 CR PACK Approval CR to 23.501 on IABARC (Rel-16) SA WG2 Approved
SP-200684 CR PACK Approval CR to 23.401 on PARLOS (Rel-16) SA WG2 Approved
SP-200686 CR PACK Approval CRs to 23.214, 23.501, 23.502, 23.682 on TEI16 (Rel-16) SA WG2 Approved
SP-200687 CR PACK Approval CR to 23.501 on UDICOM (Rel-16) SA WG2 Approved
SP-200689 CR PACK Approval CR to 23.502 on xBDT (Rel-16) SA WG2 Approved
SP-200690 SID REVISED Approval Revised SID: Architectural enhancements for 5G multicast-broadcast services. SA WG2 Approved
SP-200701 CR PACK Approval Rel-16 CRs on TEI SA WG3 Approved
SP-200702 CR PACK Approval Rel-15 CRs on Security Assurance Specification for eNB network product class SA WG3 Approved
SP-200703 CR PACK Approval Rel-16 CRs on Security Assurance Specification for 5G SA WG3 Approved
SP-200707 CR PACK Approval Rel-16 CRs on Security for IAB SA WG3 Approved
SP-200708 CR PACK Approval Rel-16 CRs on Authentication and key management for applications based on 3GPP credential in 5G SA WG3 Approved
SP-200709 CR PACK Approval Rel-15 CRs on Security aspects of 5G System - Phase 1 batch 1 SA WG3 Approved
SP-200710 CR PACK Approval Rel-16 CRs on User Plane Gateway Function for Inter-PLMN Security SA WG3 Approved
SP-200711 CR PACK Approval Rel-16 CRs for Study on Security Aspects of 3GPP support for Advanced V2X Services SA WG3 Approved
SP-200712 CR PACK Approval Rel-16 CRs onStudy on Security Aspects of the 5G Service Based Architecture SA WG3 Approved
SP-200713 CR PACK Approval Rel-16 CRs on Study on evolution of Cellular IoT security for the 5G System SA WG3 Approved
SP-200714 CR PACK Approval Rel-13 CRs on Enhancements to WEBRTC interoperability SA WG3 Approved
SP-200715 CR PACK Approval Rel-16 CRs on Security aspects of SEAL SA WG3 Approved
SP-200716 CR PACK Approval Rel-16 CRs on Security aspects of Enhanced Network Slicing SA WG3 Approved
SP-200719 WID NEW Approval New WID on UPIP support in 5GS. SA WG3 Approved
SP-200720 WID NEW Approval New WID on Security Assurance Specification for Network Slice-Specific Authentication and Authorization Function (NSSAAF). SA WG3 Approved
SP-200721 SID NEW Approval New study on the security of AMF re-allocation. SA WG3 Approved
SP-200722 SID NEW Approval New SID on security aspects of enablers for Network Automation (eNA) for the 5G System (5GS) Phase 2. SA WG3 Approved
SP-200723 CR PACK Approval Rel-16 CRs on Streaming trace reporting SA WG5 Approved
SP-200724 CR PACK Approval Rel-16 CRs on TEI SA WG5 Approved
SP-200725 CR PACK Approval Rel-15 CRs on TEI SA WG5 Approved
SP-200726 CR PACK Approval Rel-12 CRs on TEI SA WG5 Approved
SP-200727 CR PACK Approval Rel-11 CRs on TEI SA WG5 Approved
SP-200728 CR PACK Approval Rel-10 CRs on TEI SA WG5 Approved
SP-200729 CR PACK Approval Rel-16 CRs on NRM enhancements SA WG5 Approved
SP-200730 CR PACK Approval Rel-15 CRs on Network Resource Model (NRM) for 5G networks and network slicing SA WG5 Approved
SP-200731 CR PACK Approval Rel-15 CRs on Performance Assurance for 5G networks including network slicing SA WG5 Approved
SP-200732 CR PACK Approval Rel-16 CRs on Self-Organizing Networks (SON) for 5G networks SA WG5 Approved
SP-200733 CR PACK Approval Rel-16 CRs on Charging Access of ATSSS SA WG5 Approved
SP-200734 CR PACK Approval Rel-16 CRs on Energy efficiency of 5G SA WG5 Approved
SP-200735 CR PACK Approval Rel-15 CRs on Provisioning of network slicing for 5G networks and services SA WG5 Approved
SP-200736 CR PACK Approval Rel-15 CRs on Management and orchestration of 5G networks and network slicing SA WG5 Approved
SP-200737 CR PACK Approval Rel-16 CRs on Integration of ONAP and 3GPP 5G management framework SA WG5 Approved
SP-200738 CR PACK Approval Rel-16 CRs on Enhancement of performance assurance for 5G networks including network slicing batch 1 SA WG5 Approved
SP-200740 CR PACK Approval Rel-16 CRs on Charging Enhancement of 5GC interworking with EPC SA WG5 Approved
SP-200741 CR PACK Approval Rel-16 CRs on CHF-controlled quota management SA WG5 Approved
SP-200742 CR PACK Approval Rel-15 CRs on Service Based Interface for 5G Charging SA WG5 Approved
SP-200743 CR PACK Approval Rel-16 CRs on Network Slice Performance and Analytics Charging in 5G System SA WG5 Approved
SP-200744 CR PACK Approval Rel-16 CRs on Management of MDT in 5G SA WG5 Approved
SP-200745 CR PACK Approval Rel-16 CRs on Network Slice Management Charging in 5G System SA WG5 Approved
SP-200746 CR PACK Approval Rel-17 CRs on Management of MDT enhancement in 5G SA WG5 Approved
SP-200747 CR PACK Approval Rel-17 CRs on Enhancements of 5G performance measurements and KPIs SA WG5 Approved
SP-200748 CR PACK Approval Rel-17 CRs on Additional NRM features SA WG5 Approved
SP-200749 CR PACK Approval Rel-17 CRs on Enhancement on Management Aspects of 5G Service-Level Agreement SA WG5 Approved
SP-200750 CR PACK Approval Rel-16 CRs on Closed loop SLS Assurance SA WG5 Approved
SP-200751 CR PACK Approval Rel-16 CRs on KPI reporting SA WG5 Approved
SP-200752 CR PACK Approval Rel-17 CRs on Enhancements of Self-Organizing Networks (SON) for 5G networks SA WG5 Approved
SP-200753 CR PACK Approval Rel-16 CRs on Trace Management in the context of Services Based Management Architecture SA WG5 Approved
SP-200754 CR PACK Approval Rel-16 CRs on Management Aspects of 5G Service-Level Agreement SA WG5 Approved
SP-200756 DRAFT TR Approval Draft TR 28.812 'Study on scenarios for Intent driven management services for mobile networks' SA WG5 Approved
SP-200757 DRAFT TS Approval Draft TS 28.309 'Management of Quality of Experience (QoE) measurement collection Integration Reference Point (IRP); Solution Set (SS) definitions' SA WG5 Approved
SP-200758 DRAFT TS Approval Draft TS 28.313 'Study on new aspects of Energy Efficiency (EE) for 5G' SA WG5 Approved
SP-200759 DRAFT TR Approval Draft TR 28.810 'Study on concept, requirements and solutions for levels of autonomous network' SA WG5 Approved
SP-200760 DRAFT TS Approval Draft TS 28.201 'Network slice performance and analytics charging in the 5G System (5GS); Stage 2' SA WG5 Approved
SP-200761 DRAFT TS Approval Draft TS 28.202 'Network slice management charging in the 5G System (5GS); Stage 2' SA WG5 Approved
SP-200763 WID REVISED Approval Revised WID Self-Organizing Networks (SON) for 5G networks. SA WG5 Approved
SP-200765 SID NEW Approval New SID on YANG PUSH. SA WG5 Approved
SP-200766 SID REVISED Approval New SID on network slice management enhancement to include security aspects. SA WG5 Approved
SP-200767 SID NEW Approval New SID on charging aspects of Enhanced Proximity-based Services in 5GC. SA WG5 Approved
SP-200769 WID NEW Approval New work item on charging enhancement for URLLC. SA WG5 Approved
SP-200770 WID REVISED Approval Revised WID on Discovery of management services in 5G. SA WG5 Approved
SP-200771 SID NEW Approval Study on charging aspects of 5GS CIoT. SA WG5 Approved
SP-200772 CR PACK Approval Rel-17 CRs on Mission critical security enhancements phase 2 SA WG3 Approved
SP-200773 CR PACK Approval Rel-15 CRs on Security aspects of 5G System - Phase 1 Batch 2 SA WG3 Approved
SP-200776 WI SUMMARY Endorsement Work Item Summary for 5G_eSBA China Mobile Endorsed
SP-200777 WI SUMMARY Endorsement Work Item Summary for Rel-16 UDICOM Nokia Korea Endorsed
SP-200785 CR PACK Approval Stage 1 CRs on REAR SA WG1 Approved
SP-200786 CR PACK Approval Stage 1 CRs on MARCOM SA WG1 Approved
SP-200787 CR PACK Approval Stage 1 CRs on 5GSAT SA WG1 Approved
SP-200788 CR PACK Approval Stage 1 CRs on UIA SA WG1 Approved
SP-200789 CR PACK Approval Stage 1 CRs on TEI16 SA WG1 Approved
SP-200792 CR PACK Approval Stage 1 CRs on AVPROD SA WG1 Approved
SP-200794 CR PACK Approval Stage 1 CRs on TEI17 SA WG1 Approved
SP-200797 WID NEW Approval New WID on Subscriber-aware Northbound API access (SNA). SA WG1 Approved
SP-200801 WI SUMMARY Endorsement Summary for Work Item on 'Removal of H.263 and MPEG-4 Visual from 3GPP Services' Qualcomm Incorporated Endorsed
SP-200804 CR PACK Approval CRs to RM_H263_MP4V (postponed from SA#88-e) SA WG4 Approved
SP-200806 CR PACK Approval Rel-15 CRs on Lawful Interception SA WG3-LI Approved
SP-200807 CR PACK Approval Rel-16 CRs on Lawful Interception SA WG3-LI Approved
SP-200808 WI SUMMARY Endorsement Work Item Summary for Rel-16 eIMS5G_SBA T-Mobile USA Inc. Endorsed
SP-200813 CR PACK Approval REl-16 CRs on TEI batch 2 SA WG5 Approved
SP-200816 CR PACK Approval Rel-16 CRs on Charging Aspects for 5WWC SA WG5 Approved
SP-200817 CR PACK Approval REl-16 CRs on Nchf Online and Offline charging services SA WG5 Approved
SP-200818 CR PACK Approval Stage 1 CRs on SNA SA WG1 Approved
SP-200824 DRAFT TR Information TR 21.916 v.0.6.0 on Rel-16 Summary Work Plan Coordinator (MCC) Noted
SP-200826 DRAFT TS Approval Presentation of TS 23.180 v2.0.0 for approval SA WG6 Approved
SP-200827 DRAFT TR Approval Presentation of TR 23.764 v2.0.0 for approval SA WG6 Approved
SP-200831 WID NEW Approval New WID for enhanced application layer support for V2X services. SA WG6 Approved
SP-200832 WID NEW Approval New WID Application Architecture for MSGin5G Service. SA WG6 Approved
SP-200833 WID NEW Approval New WID Mission Critical Services over 5GS. SA WG6 Approved
SP-200835 SID REVISED Approval Revised SID Study on support of the 5GMSG Service. SA WG6 Approved
SP-200836 SID REVISED Approval Revised SID Study on application layer support for . Factories of the Future in 5G network . SA WG6 Approved
SP-200837 SID REVISED Approval Revised SID Study on Mission Critical services support over 5G System. SA WG6 Approved
SP-200838 CR PACK Approval Rel-16 CRs to TS 23.283 for eMCCI SA WG6 Approved
SP-200839 CR PACK Approval Rel-16 CRs to TS 23.282 for eMCData2 SA WG6 Approved
SP-200840 CR PACK Approval Rel-16 CRs to TS 23.222 for eCAPIF SA WG6 Approved
SP-200841 CR PACK Approval Rel-16 CRs to TS 23.434 for SEAL SA WG6 Approved
SP-200842 CR PACK Approval Rel-16 CRs to TS 23.286 for V2XAPP SA WG6 Approved
SP-200843 CR PACK Approval Rel-17 CRs to TS 23.280, TS 23.281, TS 23.282 and TS 23.379 for eMONASTERY2 SA WG6 Approved
SP-200844 CR PACK Approval Rel-17 CRs to TS 23.280 and TS 23.379 for enh3MCPTT SA WG6 Approved
SP-200845 CR PACK Approval Rel-17 CRs to TS 23.282 for eMCData3 SA WG6 Approved
SP-200846 CR PACK Approval Rel-17 CRs to TS 23.281 and TS 23.283 for TEI17 SA WG6 Approved
SP-200847 CR PACK Approval Rel-17 CR to TR 23.744 for FS_enhMCLoc SA WG6 Approved
SP-200848 WI SUMMARY Endorsement Work item Summary for 5GMS3 Sony (Rapporteur) Endorsed
SP-200849 WI SUMMARY Endorsement Work item Summary for Enhancement of performance assurance for 5G Intel (Rapporteur) Endorsed
SP-200851 WI SUMMARY Endorsement Work Item Summary for Rel-16 eCAPIF Samsung Endorsed
SP-200852 WI SUMMARY Endorsement Work Item Summary for Rel-16 SEAL Samsung Endorsed
SP-200853 SID NEW Approval New SID on the access control for management service. SA WG5 Approved
SP-200854 WID NEW Approval New WID on N40 Interface Enhancements to Support GERAN and UTRAN. SA WG5 Approved
Close of CC
The TSG SA Chairman closed this CC at 14.55 UTC.
I.1 SA#89E_CC#4
Third Generation Partnership Project (3GPP™)
SUMMARY Report for TSG SA meeting: #89E (Electronic meeting) Conference Call #4
Opened: Friday, (2020-09-18) 13:00 UTC
There were ~130 participants on this CC.
Attendees: The following companies were recorded as present (list not exhaustive or verified)
Affirmed Networks
Apple
AT&T
BMWi
BT
CATT
China Telecom
CMCC
DENSO
Dolby
DTAG
ERICSSON
FirstNet
Futurewei
HPE
Huawei
Intel
IPCom
JHU/APL
KDDI
KPN
Kyocera
LGE
Matrixx
MediaTek
NCSC
Nkom
Nokia
NTT DOCOMO
OPPO
Orange
Perspecta Labs
Qualcomm
Samsung
Siemens
Sony
TEF
Tencent
Thales
TIM
T-Mobile USA
TNO
UIC
Verizon
Vivo
Vodafone
Xiaomi
ZTE
NOTE: Meeting notes are not exhaustive and may not contain all the comments made during the conference call.
Opening of meeting
The TSG SA Chairman opened this CC at 13.00 UTC.
The CCs agenda was revised for this in:
https://www.3gpp.org/ftp/tsg_sa/TSG_SA/TSGs_89E_Electronic/Inbox/Revisions/SP-200855_rev3.zip
Documents which still need conclusions
855 - GTM Agendas - to be noted
TD SP 200855 (AGENDA) SA#89-e GoToMeetings Agenda. (Source: TSG SA Chairman).
Document for: Approval.
Abstract: SA#89-e GoToMeetings Conference Calls Agenda.
Discussion and conclusion:
The latest revision of the CC agenda was Rev3. Slide 7 should read "Friday" rather than "Thursday". The agenda (and it's revisions) was noted.
796 / 870 - GUTI LS out + slide for approval
TD SP 200796 [DRAFT] LS On 5G GUTI reallocation for CIoT. (Qualcomm Korea)
Document for: Approval.
Abstract: Provides instructions on allocating new 5G GUTI at every signalling transaction trigged by paging.
e-mail comments:
Haris (Qualcomm) starts email discussion
Krister (Ericsson) states that me the option 1 is a special case of option 2. As said I see that the frequency of refresh of a temporary identifier is decided by the network operator. The operator may then configure AMF so option 1 is the behavior. That can be the correct behavior for normal UEs as there is a risk of an attack of tracking a UE, which is a privacy concern for the user.
There may be other IoT devices which does not have the same strict privacy requirement, and as such could benefit from a less often refresh of GUTI. The gain would be in signaling optimizations.
Wanqiang (Huawei) comment that option 2 brings extra complexity and makes the system unmanageable. It is not a reasonable approach to move forward.
Johannes (Deutsche Telekom) supports option1 and supports the text in the LS as is. DT ranks the privacy and security issues as higher priority than optimizations. Exception to the existing procedures shall not be granted.
Lars (Sony) comment that option 1 will bring extra complexity and new triggers for AMF to perform UCU. And ask a question on the privacy issue.
Krister (Ericsson) comments that there is has only been a discussion here about privcay related to tracking a UE moving. No other security related issues identified.
Johannes (Deutsche Telekom) clarifies that option1 reflects the specified solution of 5GS and option2 is the request for exceptional hanlding of certain UEs in 5GS
Lars (Sony) option1 goes beyond the existing procedures.
Haris (Qualcomm) provides response to Wangqiang
Erik/Andy (Samsung) supports option 1, as there is privacy threat.
Hucheng(CATT) supports option1, but thinks, if understanding is correct, the wording of option 1 could be enhanced:
'Option 1: Allocation of a new 5G-GUTI temporary identifier to the UE in IDLE mode in response to paging in 5G is mandatory and shall apply in all cases including all CIoT optimisations'
From the clarifying question(s) I (Chris, Vodafone) asked in the Tuesday web call, I understand that the options are actually:
Option 1: the standards shall enable GUTI reallocation at every Mobile Terminating RRC connection establishment.
Option 2: the standard prevents GUTI reallocation at every Mobile Terminating RRC connection establishment.
In which case Vodafone prefers option 1.
Haris (Qualcomm) observes that there is preference to go with Option 1 and suggests companies to propose comments to the wording
Orange supports Option 1.
While Option 2 may give operators the flexibility of managing the (signalling) optimization which can be of significance for CIoT devices/applications without temporary GUTI allocated each time paging is performed, it may introduce some extra complexity, if, e.g. the exception should be given by HPLMN and/or VPLMN in roaming, when and for what CIoT devices/applications should be given the exception, even if it is configurable. This may adversely affect the optimization intended by Option 2.
In addition, SA3 has already clearly defined in TS 33.501 from Release 15 that the mandatory allocation by AMF of a new 5G-GUTI temporary identifier to the UE in response to a Paging message as a security and privacy protection enhancement of 5G. Option 2 would cause some mis-alignment and even contradictions with the SA3 specifications and open up more discussions/work in SA2, SA3 and CT1 at least about to dynamically configure GUTI for those that requires enhanced security for some CIoT devices/applications vs those that may have less security constraints. This may adversely affect achievable optimization after all.
Saad (Interdigital). Interdigital also preferers option 1.
Wanqiang (Huawei) provides further comments regarding the update from Ericsson and propose to stick to the original text in SP-200796.
Krister (Ericsson) provides update of the text in option 1. Option 1: Upon receiving a temporary identifier (S-TMSI or I-RNTI) sent by a UE in response to a paging message, it is mandatory for the network to re-allocate the used temporary identifier that was sent in the response message from the UE. This requirement is valid for any type of UE.
Haris (Qualcomm) provides response to Chris(Vodafone)
Lars (Sony) provides further comments on the privacy issue.
Krister (Ericsson) asks Wanqiang to explain the loose comment which missed to explain 'track the link'. Ericsson can not agree the original text of QC as it is not covering the 3rd case that I describe below.
Wanqiang (Huawei) provides response and ask further question.
Lars (Sony) We support Krister's alternative option 1 wording.
Haris (Qualcomm) comments that the thread is for the approval of original or potentially revised text in SP-200796 and the text in SP-200795 is not going to be further modified since the paper is already noted
Krister (Ericsson) provides provide revision to the draft LS in rev1.
(Samsung) provides details on the privacy threat. Clarifies that temporary identifiers (S-TMSI and/or I-RNTI) that were used in the paging message and sent by a UE in response to a paging message should be re-allocated. Re-allocation of I-RNTI is mandated by TS 33.501, similarly 5G-GUTI needs to be reallocated.
Lars (Sony) we support rev1 of the LS.
Patrice (Huawei) proposes to produce a slide with the statement for working agreement based on the original proposal.
Haris (Qualcomm) agrees with the proposal from Patrice and produces first draft
Krister (Ericsson) provides response giving an explanation how the failure case also will be handled including a S-TMSI reallocation taking place. Ericsson clear see that that the text proved by Ericsson in LS response rev1 covers mandatory re-allocation requirement needed to handle the privacy issue of tracking threat.
Wanqiang(Huawei) supports the draft from Haris and provides a small update.
Lars(Sony) The ppt is only a copy of the original LS and serves no additional purpose than the original version of the LS.
Krister (Ericsson)
Dear all,
This discussion we are having in SA plenary #89-e is to protect privacy threat through tracking of a CIoT UE.
In Rel-16 we have two solutions fully specified including ASN.1 coding. The Control Plane CIoT solution as well as the User Plane CIoT solution. As shown with reasonable logical evidence in the mails sent by Ericsson and SONY to SA public mail reflector show that the UP CIoT solution has higher protection against tracking of a UE, since there is no one-to-one correlation between the temporary
Identifier sent by the network and the paging response sent by the UE.
It has also been showed that procedures are specified for the Network to re-allocate the 5G-GUTI (S-TMSI) as frequent as network finds appropriate (similar to legacy specifications) are also specified.
It has also been shown and proposed as a new requirement to clarify in TS 33.501:
Upon receiving a temporary identifier (S-TMSI or I-RNTI) sent by a UE in response to a paging message, it is mandatory for the network to re-allocate the used temporary identifier that was sent in the response message from the UE. This requirement is valid for any type of UE.
This text will also fully answer the question from CT1 in the LS to SA3 (S3-2000615/C1-200967)
Furthermore, It has also been shown that current procedures of the RCC resume failure will lead to release of RRC connection and that NAS level procedures will follow on. It is then required to re-allocate the 5G-GUTI as already required and specified.
It has also been seen that two of the main companies behind the UP CIoT solutions are providing all these evidence. Still the companies with main interest in the CP CIoT Solution are putting unjustified demand on the UP CIoT solution. This without any detailed analysis presented that is showing that the protection level against a tracking attack of the UE is less compared to a CP CIoT UE. On the contrary, the protection level against tracking is higher than for the CP CIoT solution.
Going back to any text in mails on SA3 mailing list and tdocs over the last three SA3 meetings, it is clear that this weeks SA plenary discussion on this subject is more detailed on both describing possible attack scenario as well as on how the currently Rel-16 procedures for the UP CIoT are specified and expected to work.
Therefore, I finds it unfair and unjustified for companies, with little interest in UP CIoT solution, to go for a working agreement on these grounds presented in SP-200870. I would rather task SA3 to make a detailed analysis of the potential tracking attack scenarios that shows any evidence.
Furthermore that CT1 clarifies where it may be unclear in specifications if determined necessary. Our analysis of specifications are that procedures cross interfaces are in place to handle this properly but as always behavior description can be more clear in particular related to failure cases.
BR / Krister
Krister (Ericsson) thanks Lars for the analysis. After going through a mails and tdoc over the last 3 SA3 meeting it is clear that the analysis of both the attack scenarios and analysis of the current Rel-16 specifications has been in more details in SA#89-e than what has been in done in SA3. Clearly SA3 needs to do their job here in upcoming meetings.
Discussion and conclusion:
Sony objected to approving the original LS. The proposal for a way forward in TD SP 200870 was reviewed and a Working agreement was established based upon it. Ericsson asked to clarify in the LS that the statement is based upon an unconfirmed working agreement. Orange asked to use the normative terminology of the working agreement in the LS. The LS was revised accordingly. Qualcomm asked whether the LS was still needed if SP-200870 can be endorsed. The SA WG3 chairman asked whether companies need to bring CRs to SA WG3 based on the working agreement or whether the leadership needs to identify the CRs. Objections on these CRs based on objection to the working agreement should not be allowed, but objections for other valid technical reasons need to be resolved. The SA WG2 Chairman asked if there are objections to a number of CRs, it may be difficult to determine whether the objections are valid with respect to the Working Agreement. Such CRs which have sustained objections can either be brought by the WG to TSG SA for resolution or can be contributed directly to TSG SA by company contribution. Ericsson commented that TSG SA has had a procedural discussion and SA WG3 should be expected to do a full analysis of this issue before agreeing to CRs. The SA WG2 Chairman asked to add that WGs take the working agreement into account and provide relevant CRs into account. The working agreement in SP-3200870 should be referenced and attached to the LS. Qualcomm provided the updated LS in SP-200796_Rev1. SP-200796_Rev1 was approved. (This will be revised by MCC into a new TD number with correction from TSG SA#90-e to TSG SA#89-e).
TD SP 200870 [DISCUSSION] Presentation on 5G GUTI reallocation. (Qualcomm Incorporated)
Document for: Approval.
Abstract: Proposal for endorsement:
TSG SA discussed and acknowledged the trade-off between user privacy protection and signalling optimisation for 5G CIoT.
Considering this trade off if the same 5G-GUTI is used multiple times for paging even for CIoT UEs, there exists a privacy risk (identification of the UE's presence in a particular location). Therefore, for a UE in 5GMM-IDLE mode with suspend indication, the network shall always allocate a new 5G-GUTI after paging and resume of a connection, even if a NAS message is not sent.
Discussion and conclusion:
Qualcomm propose to endorse this text as a way forward. Sony objected to this text as it is the same as in the original LS.
Who would endorse the proposal as a working agreement: 21
Who does not endorse the proposal as a working agreement: 2
A working agreement was made based on TD SP 200870. This will be posted on the Web pages and may result in a Vote at TSG #90-e if there are any challenges by the deadline which cannot be resolved at the meeting. This contribution was then endorsed.
778 - R18/R19 handling in SA1 discussion (778r1 stays noted)
TD SP 200778 (REPORT) SA WG1 Report to TSG SA#89e. (Source: SA WG1 Chairman).
Document for: Presentation.
Abstract: SA WG1 Report to TSG SA#89-e.
e-mail comments:
New revision uploaded where slide 8 incorporates all the latest information about future SA1 meetings.
Sherry (Xiaomi) requests for clarification about the timeline for R18 new SIDs proposal.
Wenruo (Huawei) commented that Rel-18 stage1 timeline should keep open before R-17 timeline is stabilized. It is clear the freeze date of R18 stage 1 should not be earlier than Sept. 2021. With that, it is too early to close the door for any new R18 SID proposal in SA1 in the coming SA1 meeting.
Saso (Intel) supports Wenruo's view that the door for new R18 SID proposals in SA1 should remain open at least in Q4. If SA1 is in overload situation, then prioritization exercise should take place.
Ming (CATT) supports Wenruo's view and think the door for new R18 SID proposals in SA1 should remain open. If necessary, prioritization exercise on approved Rel-18 SA1 SID should take place either within SA1 or at SA plenary.
Tony (Futurewei) supports the view expressed by Huawei, Intel, and CATT regarding the Rel-18 timeline (i.e., kept open till Rel-17 timeline is decided), allowing new Rel-18 proposal till then, and doing prioritization exercise of SA1 SID/WIDs if needed.
Tao Sun (China Mobile) share the same view as the previous companies that it is too early to put new SIDs into R19 with the situation that even R17 timeline not fully settled down with likely 6 months delay. We suggest not close the door of R18 stage 1 study in this stage and prioritization within SA1 can be done if considered needed.
Telefonica supports the previous statement by China Mobile
Discussion and conclusion:
There had been discussion over the suggested Stage 1 Rel-18 freeze dates proposed by SA WG1. AT&T suggested that no artificial boundaries are created to a certain SA WG1 meeting. The TSG SA Chairman suggested this is reviewed again at the December TSG SA meeting. SA WG1 should take new Rel-18 proposals (e.g. SID) at least in it's next meeting. TSG SA will discuss this issue again at the December TSG SA meeting. Sony asked whether the SA WG1 ad-hoc meeting had been decided. The SA WG1 Chairman replied that the decision will be made in December. The ad-hoc meeting has been planned and may need to be cancelled in December.
Agenda Item 4.7 - endorse RAN LS to ITU via PCG and note 863
TD SP 200864 LS from TSG RAN: DRAFT LTI - answer to ITU-R WP5D LS on DEVEOPMENT OF DRAFT NEW RPORT ITU-R.M[IMT.C-V2X] - APPLICATION OF THE TERRESTRIAL COMPONENT OF IMT FOR CELLULAR-V2X (Source: TSG RAN (RP-202055))
Document for: Action.
Abstract: For endorsement and creating an LS to the PCG.
Discussion and conclusion:
This was endorsed and a LS OUT to PCG was created by MCC in TD SP 200873 which was approved.
TD SP 200865 LS In Action LS from TSG RAN: Draft Letter to ITU in reply to ITU_R_WP5D_TEMP_39 = RP-200037 on update submission for LTE-Advanced towards Revision 5 of Recommendation ITU-R M.2012(Source: TSG RAN (RP-202056))
Document for: Action.
Abstract: For endorsement and creating an LS to the PCG.
Discussion and conclusion:
This was endorsed and a LS OUT to PCG was created by MCC in TD SP 200874 which was approved.
TD SP 200866 LS In Action LS from TSG RAN: DRAFT LTI - answer to ITU-R WP5A LS on CONNECTED AUTOMATED VEHICLES (CAV) TSG RAN (RP-202057)
Document for: Action.
Abstract: For endorsement and creating an LS to the PCG.
Discussion and conclusion:
This was endorsed and a LS OUT to PCG was created by MCC in TD SP 200875 which was approved.
TD SP 200867 LS from TSG RAN: Draft Letter to ITU in answer to LS to RIT/SRIT Proponents on the completion and conclusions of steps 5 to 7 of the IMT-2020 process for the first release of new Recommendation ITU-R M.[IMT-2020.SPECS] TSG RAN (RP-202058)
Document for: Action.
Abstract: For endorsement and creating an LS to the PCG.
Discussion and conclusion:
This was endorsed and a LS OUT to PCG was created by MCC in TD SP 200876 which was approved.
TD SP 200863 LS from TSG RAN: Draft Letter to ITU - Response LS on 3GPP's activities related to WRC-19 Resolutions. (Source: TSG RAN (RP-202054))
Document for: Information.
Abstract: To be noted.
Discussion and conclusion:
This LS was noted.
822 - SFC SID / WID
TD SP 200822 (SID NEW) New SID on Study on Support for Service Function Chaining in 5G System. (Source: Intel Corporation, Deutsche Telekom AG, Tencent, Telefónica, Affirmed Network, AT&T, Sandvine, Convida Wireless, InterDigital, KPN, Verizon UK Ltd., KDDI, Vodafone, Telecom Italia, Cisco, b<>com).
Document for: Approval.
Abstract: Objective: The aim of this work is to study the enable support of service function chaining in 5G system for value-added services provided by network operators to third parties, including:. The study will consider useUse cases and service requirements related to: - provide service definition of supported service functions and service function paths; - provide service configuration and management support of service functions and service function paths to third parties for applications and their users with value-added services, e.g. provided by 5GS only or both of 5GS and 3rd parties; - provide continuing same value-added service experiences for UEs using 5G services, e.g. eMBB, V2X, AVPROD, NCIS, etc., and moving between networks. Gap analysis between the identified service requirements and existing 5GS service requirements or functionalities. Note: the gap analysis takes into account previous work related to Stage 1 services requirements on SFC already developed in other SDOs (e.g. IETF RFC 7665, IETF RFC 8300, IETF RFC 8459, ITU-T Y.2242, etc).
e-mail comments:
Saso (Intel) initiates discussion thread on SP-200822.
Nokia has concerns with approving a SID on this topic as we believe that the best course of action would be to ask companies to propose a WID and related CRs in Q4 with the delta requirements that are not yet captured in TS 22.261 ( also by inheritance of those in TS 22.101 clause 30).
Patrice (Huawei) provides concerns, and proposes that discussion continues further in WGs before we can approve something (for minutiae: objects to the original paper).
Adrian (vivo) asks a question for clarification.
Krister (Ericsson) has the same view as expressed by Huawei. In addition pointing out that the 22.261 has the requirement that
, the 5G system shall support all EPS capabilities (e.g. from TSs 22.011, 22.101, 22.278, 22.185, 22.071, 22.115, 22.153, 22.173, 22.468),
In SA1 we are with term 5G System including SA2 N6-LAN as part of 5G System.
Saso (Intel) replies to comments. Seeks clarification from SA1 Chairman.
Saso (Intel) provides SP-200822rev1.
Adrian (vivo) suggest to move completion date to June 2021.
Saso (Intel) prefers keeping the completion date to Mar 2021.
Haris (Qualcomm) comments on ticking the ME and AN boxes to NO
Saso (Intel) provides rev2 with ME impact changed to 'No'.
Patrice (Huawei) manages to propose a draft revision (in the drafts folder) that could be something we could work with in such a short notice.
Saso (Intel) provides rev4.
Discussion and conclusion:
SP-200822_Rev4 was the latest proposal, which was presented by Intel. Huawei commented that one of their important comments had not been accepted in this text and asked that any work done in SA WG5 should be made generic and not impose it's provision to third parties by operators. Nokia asked where 'N6-LAN' is to be removed and why this is done only for Rel 18 onwards as this will lead to incompatibility. Nokia also commented that SA WG1 do not deal with interfaces and the interface names should be removed. It was also unclear whether the Stage 1 is needed for SA WG5 to work on OAM features they consider useful. Vivo asked why the deadline for this was set to march when there is no particular time constraint for the work and SA WG1 have other studies to progress, suggesting moving it to June or later. Intel asked for the objections to be recorded as some appeared invalid and suggested allowing SA WG1 to determine their workload and the timescales for this. Deutsche Telekom commented that in SA WG1 discussions objections had made this a SID and then it has been discussed here to become a WID, so returning this to SA WG1 for further discussion will not help. Vodafone commented that if this is returned to SA WG1 there will be a new set of objections and considered this needs to be decided at TSG SA. Huawei commented that delaying the approval of this work until the next TSG will not impact the work, given that it is proposed now as a WID, rather than SID. The TSG SA Chairman suggested postponing this if no resolution can be reached at this meeting. Intel reported a proposed SP-200822_Rev6. Huawei asked to allow more time to work on this off-line and in the next SA WG1 meeting, until the next TSG SA meeting. Nokia also asked to further discuss this offline. Huawei and Nokia were asked to put their concerns or objections with SP-200822_Rev6. into the e-mail minutes comments. This SID was then postponed.
862 - LS out to SA WGs, CT, cc RAN on Rel-17 schedule
TD SP 200862 (LS OUT) [DRAFT] LS on R17 schedule (Source: TSG SA).
Document for: Approval.
Abstract: To: SA WG1, SA WG2, SA WG3, SA WG4, SA WG5, SA WG6. CC: TSG RAN, TSG CT.
Discussion and conclusion:
SP-200862_Rev2 was the latest proposal. This was approved. (To be revised into a new TD number by MCC).
868 + 657 - LS in from RAN and related CR on mini-WIDs
TD SP 200868 LS from TSG RAN: LS on Relaxation of mini-WID requirement for Cat.B/C TEI CRs (Source: (TSG RAN (RP-202001)).
Document for: Action.
Abstract: At TSG SA#83 plenary, TSG SA approved SP-190270 (CR 0057 to TR 21.900). This CR introduced a number of major changes in the way in which TEI is handled. Although TSG RAN and the RAN WGs appreciate the tighter handling of TEI in general that resulted from TSG SA's decision, one of the changes introduced by SP-190270, namely the strict requirement on creating mini-Work Items for Cat. B/C TEI CRs, does not align with the way in which TSG RAN and RAN WGs have decided to handle such TEI CRs. As a result, TSG RAN and RAN WGs have in practice not been following the newly introduced text in TR 21.900 with regard to Cat.B/C TEI CRs, and have no intention of using the mini-WIDs in future either. TSG RAN finally endorsed a draft CR to TR 21.900 in RP-201291 on this topic at RAN#88 plenary. This change aims at keeping the strict requirement for TSG SA and TSG CT, while at the same time allowing TSG RAN to follow TR 21.900 also. TSG RAN thanks TSG SA for its understanding in this matter and requests TSG SA to approve the attached CR. Action: TSG RAN requests TSG SA to approve the attached CR.
Discussion and conclusion:
Attached CR is the same change as in SP-200657. This LS was postponed.
TD SP 200657 21.900 CR0064 (Rel 16, 'C'): CR to TR 21.900 on Relaxation of mini-WID requirement for Cat.B/C TEI CRs. (Source: NEC on behalf of TSG RAN).
Document for: Approval.
Abstract: TSG RAN endorsed (during the RAN#88e plenary) a draft CR to TR 21.900 in RP-200720 on Relaxation of mini-WID requirement for Cat.B/C CRs with the intention to submit the formal CR to SA#89e. It is also planned that RAN#89e plenary approves an accompanying LS to SA with explanation, but to comply with the SA Tdoc deadline and acquire a CR number, this Tdoc number is requested in advance. Summary of change: Restricts the requirement to provide a WID for Cat. B/C TEI CRs in such a way that it applies only to TSGs that have not agreed on an alternative process.
e-mail comments:
Saso (Intel) recommends approving the CR in SP-200657.
Johannes (Deutsche Telekom) comments on the missing/vague justification of the CR.
Hans (NEC) added several examples of how RAN is providing transparency.
Saso (Intel) comments.
Xiaobao (Orange ) asks for the clarification of 'an alternative process' and questions if the propose change should be applied to the description of TEI.
Hans (NEC) responded to the SA Chairman's point on desirability of common procedures between the TSGs, agreeing in principle, but indicating that this also requires a consensus across the TSGs in advance of introducing such procedures and that the mini-WID procedure had been introduced before such consensus could be achieved.
Andy (Samsung) comments.
Alessio(nokia) expresses concerns on approving the CR in SP-200657
Xiaobao (Orange ) asks for the clarification of 'an alternative process' and questions if the propose change should be applied to the description of TEI.
Discussion and conclusion:
Deutsche Telekom commented that the CR introducing the TEI rules was introduced first in TSG SA#82, again in TSG SA#83 and TSG RAN should have been fully aware of this well before it was finally approved by TSG SA. This was postponed.
790/869 - eCAV related CR Pack conclusion (possible revisions)
TD SP 200790 (CR PACK) Stage 1 CRs on eCAV. (Source: SA WG1).
Document for: Approval.
Abstract: 22.104 CR0055; 22.832 CR0029; 22.832 CR0030; 22.261 CR0465R1; 22.104 CR0053R1; 22.104 CR0058R1; 22.261 CR0462R2.
e-mail comments:
The tdocs SP-200790 to SP-200794 were submitted under agenda item 16.1 but include SA1 CRs against Rel-17 specs. Therefore they are shifted to Agenda Item 17.1
LG Electronics raises hands for minor admin stuff: (1) SP-200791 is an R17 CR but is using an R16 WI code (not a mirror from R16) (2) SP-200793 is using an R16 WI code (FS_FRMCS2 is not for R17). These may be addressed/corrected.
Haris (Qualcomm) comments that this CR pack relates to the discussion of enumeration of requirements in SP-200819 and wants to flag it up for discussion
Discussion and conclusion:
22.261 CR0462R2 revised in SP-200869. 22.104 0053r1 and 22.261 0465r1 were related to the recommendations enumeration issue and were postponed. The other CRs in this CR pack were approved. (This CR pack was partially approved).
TD SP 200869 (CR) Quality improvement of TS 22.261 (R17). (Source: Siemens).
Document for: Approval.
Abstract: Summary of change: Correction of editorial slips..
Discussion and conclusion:
LG Electronics commented that some corrections were required and this should be revised accordingly. SP-200869_Rev3 was provided and LG electronics accepted this. SP-200869_Rev3 was then approved. (This will be revised into a new TSD number by MCC).
TD SP 200871 LS from TSG RAN: Reply LS on RAN impact of FS_5MBS Study. TSG RAN (Source: RP-202086))
Document for: Action
Abstract: Regarding the following question, that SA WG2 asked RAN to feedback on: SA WG2 is debating whether broadcast (i.e. without the network's awareness about UEs receiving broadcast contents and for other use cases than the ones excluded already for Rel-17) should be further down-scoped in Rel-17 for remaining broadcast requirement in the SID. Some companies have provided solutions on broadcast (which are documented in the TR). SA WG2 would like to ask SA, RAN, RAN WG2 and RAN WG3 for feedback on broadcast support in Rel-17. RAN would like to clarify that NR-based broadcast is within the scope of RAN WI for NR MBS in Rel-17, as per the WID approved in RP-201038. According to the discussion at RAN#89e, it is concluded that the scope of RAN WI for NR MBS in Rel-17 is kept as was. RAN would like to ask TSG SA and SA WG2 to take the above answer into account.
Discussion and conclusion:
Related to incoming LS in SP-200652. This LS was noted.
TD SP 200872 (WI SUMMARY) WI summary for QOED (Source: Ericsson)
Document for: Action
Abstract: WI summary for QOED.
Discussion and conclusion:
Late submission. This WI Summary was endorsed.
Work Plan (823) and MCC Status report (803)
TD SP 200824 (DRAFT TR) TR 21.916 v.0.6.0 on Rel-16 Summary. (Source: Work Plan Coordinator (MCC)).
Document for: Information.
Abstract: Abstract of document: TR 21.916 summarises all the Release 16 Features and other significant Work Items.
Discussion and conclusion:
This had been noted at CC#3. The MCC Work Plan Manager thanked rapporteurs for the current input received and asked any outstanding ones to be provided with a view to finalising the TR at the next meeting if possible.
TD SP 200823 (WORK PLAN) Work Plan review at TSG#89. (Source: Work Plan Coordinator (MCC)).
Document for: Presentation.
Abstract: Work Plan review at TSG#89.
Discussion and conclusion:
SP-200823_Rev1 was presented by the MCC Work Plan Manager.
General: E-FLUS is 100% complete.
Slide 10: Not all normative WIDs need to be produced, by December, but only SA WG2 WIDs.
Slide 3-4: AT&T asked to also show TSG SA and TSG CT represented in the time-line as this could give the impression outside 3GPP that only RAN are concerned with the time schedule. The MCC Work Plan manager was asked to show this as an overall 3GPP schedule for clarity both inside and outside 3GPP.
SP-200823_Rev2 was provided to take comments into account. The MCC Work Plan Manager was thanked for this presentation, which was noted.
TD SP 200803 (REPORT) Support Team report. (Source: MCC).
Document for: Information.
Abstract: MCC Director's report of MCC-related activities.
Discussion and conclusion:
This was presented by the MCC Director, Issam Toufik.
It was announced that the outgoing MCC Director, John Meredith, will retire from 3GPP at the end of September 2020 and the replacement MCC Director, Issam Toufik will take over full-time. John was thanked for his outstanding and dedicated support to the 3GPP project and overview of MCC and the 3GPP procedures.
The TSG SA Chairman, on behalf of TSG SA and the 3GPP project, thanked John for his excellent support and help and hoped to see him again in a future meeting in order to hold a formal farewell party.
The MCC Director was thanked for this presentation, which was noted.
TD SP 200766 (SID REVISED) New SID on network slice management enhancement to include security aspects. (Source: SA WG5).
Document for: Approval.
Abstract: Objective: The objective of this study item is to: - Investigate and propose the potential network slice information model and management service enhancements to support cross-operator network slice management use case (e.g. for V2X, etc.) - Investigate and propose the potential new management capabilities to support end to end network slicing (e.g. identified by end to end network slicing ETSI ZSM work item, GSMA 5GJA work package 1, etc.) - Investigate and propose the potential new management capabilities to support security management of network slice (e.g. security isolation management, UP protection policy management, etc. ) Note: The study should clarify the meaning of the terms 'cross-operator network slice management' and 'end to end network slicing'.
Discussion and conclusion:
(This was Block approved in CC#3). Intel asked if there were any rules or guidelines to the existence of multiple rapporteurs for SIDs and WIDs. The SA WG5 Chairman reported that this was a merge of an existing SID and a newly proposed SID and proposing companies both wanted rapporteurs for the different aspects of the work. The SA WG5 Chairman undertook to see whether TSG SA have an objection to this. The TSG SA Chairman replied that this is strongly discouraged and asked all WGs to avoid agreeing to multiple rapporteurs for WIDs and SIDs.
Closing of technical part of the meeting
The TSG SA Chairman reported that MCC will create new documents for all necessary approved revisions from the meeting by 12.00 UTC on Monday 21 September 2020, in time for any final review before the conference call.
The TSG SA Chairman thanked all WGs and delegates for their outstanding progress with the work considering the difficult prevailing conditions and wished everybody good health.
Close of CC
The TSG SA Chairman closed this CC at 14.55 UTC.
I.1 SA#89E_CC#5