IPR call reminder:
|
"I draw your attention to your
obligations under the 3GPP Partner Organizations' IPR policies. Every
Individual Member organization is obliged to declare to the Partner
Organization or Organizations of which it is a member any IPR owned by the
Individual Member or any other organization which is or is likely to become
essential to the work of 3GPP. Delegates are asked to take note that they
are thereby invited:
|
Antitrust policy Reminder:
|
"I
also draw your attention to the fact that 3GPP activities are subject to all
applicable antitrust and competition laws and that compliance with said laws
is therefore required of any participant of this TSG/WG meeting including the
Chairman and Vice Chairman. In case of question I recommend that you contact
your legal counsel. The
leadership shall conduct the present meeting with impartiality and in the
interests of 3GPP. Furthermore,
I would like to remind you that timely submission of work items in advance of
TSG/WG meetings is important to allow for full and fair consideration of such
matters." |
| AI | TD# | Type | Doc For | Subject | Source | Rel | Comments | e-mail_Discussion | Result |
| 0 | - | - | - | All Agenda Items | - | - | Docs:=0 | - | |
| 1.1 | - | - | - | Opening of the meeting | - | - | Docs:=0 | - | |
| 2 | - | - | - | Agenda | - | - | Docs:=1 | - | |
| 2 | S2-2400001 | AGENDA | Approval | SA2#160 Ad Hoc-e meeting Agenda | SA WG2 Chair | Approved | ==== Final Comments Deadline ==== | Approved | |
| 2.1 | - | - | - | IPR Call and Antitrust Reminder | - | - | Docs:=0 | - | |
| 3 | - | - | - | SA2#160 Meeting report | - | - | Docs:=1 | - | |
| 3 | S2-2400002 | REPORT | Approval | Draft Report of SA WG2 meeting #159 | SA WG2 Secretary | Approved | ==== Final Comments Deadline ==== | Approved | |
| 4 | - | - | - | General | - | - | Docs:=0 | - | |
| 4.1 | - | - | - | Common issues and Incoming LSs | - | - | Docs:=43 | - | |
| 4.1 | - | - | - | LS In for information (propose to note) | - | - | Docs:=10 | - | |
| 4.1 | S2-2400033 | LS In | Information | LS from ITU-T SG13: LS on initiation of the new work item ITU-T Y.IMT2020-EE-CFW 'Requirements and capability framework of IMT-2020 networks and beyond from the energy efficiency perspective' | ITU-T SG13 (SG13-LS125) | Noted | Shabnam (Ericsson) proposes to note the LS as there are no actions, information sharing only. Laurent (Nokia proposes to note the LS as there are no actions, information sharing only. | Noted | |
| 4.1 | S2-2400035 | LS In | Information | LS from GSMA UPG: LS from NG to 3GPP SA3-LI on Lawful Interception of IMS Data Channel | GSMA UPG (UPG08_127 LS from NG to 3GPP SA3-LI on Lawful Inte) | Noted | Shabnam (Ericsson) proposes to note the LS since SA2 has no action, SA3-LI is the intended WG to look into the questions. | Noted | |
| 4.1 | S2-2400075 | LS In | Information | LS from IETF TSVWG: LS on draft-ietf-tsvwg-ecn-encap-guidelines and draft-ietf-tsvwg-rfc6040updateshim | IETF TSVWG (Liaison_from_IETF_21Dec2023) | Noted | Shabnam (Ericsson) proposes to note the LS as no action directly from the LS itself other than status information shared. | Noted | |
| 4.1 | S2-2400038 | LS In | Information | LS from TSG SA: LS on collaboration and alignment of 3GPP defined application enablers with GSMA Open Gateway | TSG SA (SP-231778) | Noted | Laurent (Nokia): this LSIn for info can be noted | Noted | |
| 4.1 | S2-2400067 | LS In | Information | LS from SA WG1: Reply LS on requirements for slice-based PLMN selection | SA WG1 (S1-233272) | Rel-18 | Noted | Peter Hedman (Ericsson) suggests to note the LS | Noted |
| 4.1 | S2-2400071 | LS In | Information | LS from SA WG5: Further Reply LS on Enhancement on the attribute for 5GLAN management | SA WG5 (S5-238099) | Rel-18 | Noted | Qianghua (Huawei) proposes to note this LS, no actions for SA2 | Noted |
| 4.1 | S2-2400012 | LS In | Information | LS from CT WG4: Reply LS on Enhancement on the attribute for 5GLAN management | CT WG4 (C4-234414) | Rel-18 | Revision of Postponed S2-2311959 from SA WG2#160. Noted | Qianghua (Huawei) proposes to note this LS, No actions for SA2 | Noted |
| 4.1 | S2-2400014 | LS In | Information | LS from RAN WG3: Reply LS on the usage of paging subgrouping information in RAN in case of abnormal scenario | RAN WG3 (R3-235883) | Rel-18 | Revision of Postponed S2-2311966 from SA WG2#160. Noted | Laurent (Nokia): this LSIn for info can be noted | Noted |
| 4.1 | S2-2400019 | LS In | Information | LS from RAN WG2: Reply LS on paging | RAN WG2 (R2-2311591) | Rel-18 | Revision of Postponed S2-2311982 from SA WG2#160. Noted | Laurent (Nokia): proposes to note the LS as there are no actions, information only. | Noted |
| 4.1 | S2-2400024 | LS In | Information | LS from SA WG3: Reply LS on providing a new 5G-GUTI in the REGISTRATION REJECT message to the UE | SA WG3 (S3-235071) | Rel-18 | Revision of Postponed S2-2313232 from SA WG2#160. Noted | Laurent (Nokia): this LSIn for info can be noted | Noted |
| 4.1 | - | - | - | LS in for action (no input/responses?) | - | - | Docs:=3 | - | |
| 4.1 | S2-2400039 | LS In | Action | LS from CT WG1: LS on URSP handling for UE configured with EHPLMN list | CT WG1 (C1-239320) | Rel-18 | Noted | Myungjune (LGE) supports noting the LS. Haiyang (Huawei) suggests to note the LS Srinivas Garikipati (Nokia) This info LS can be noted. Hong (Qualcomm) also suggests noting the LS. | Noted |
| 4.1 | S2-2400046 | LS In | Action | LS from CT WG3: LS on Clarification related to the information exposed by the 5GC to NSCE server | CT WG3 (C3-235717) | Rel-18 | Postponed | Haiyang (Huawei) suggest to postpone the LS | Postponed |
| 4.1 | S2-2400073 | LS In | Action | LS from SA WG5: LS on the progress update of AI/ML Management specifications in SA WG5 | SA WG5 (S5-238107) | Rel-18 | Moved to 4.1 as relates to several studies/work items: AIMLsys, eNA_Ph3 and FS_AIML_CN. Noted | Thomas (Nokia) proposes to Note this LS | Noted |
| 4.1 | - | - | - | User consent for trace reporting | - | - | Docs:=5 | - | |
| 4.1 | S2-2400062 | LS In | Action | LS from RAN WG3: Reply LS on the user consent for trace reporting | RAN WG3 (R3-237964) | Rel-18 | Responses drafted in S2-2400421, S2-2400747, S2-2400803. Final response in S2-2401575 | Replied to | |
| 4.1 | S2-2400421 | LS OUT | Approval | [DRAFT] Reply LS on the user consent for trace reporting | Ericsson | Rel-18 | Response to S2-2400062. r00 + clean up agreed. Revised to S2-2401578, merging S2-2400747 and S2-2400803 | Revised | |
| 4.1 | S2-2401578 | LS OUT | Approval | Reply LS on the user consent for trace reporting | SA WG2 | Rel-18 | Revision of S2-2400421r00 + clean up, merging S2-2400747 and S2-2400803. Approved | Approved | |
| 4.1 | S2-2400747 | LS OUT | Approval | [DRAFT] LS on the user consent for trace reporting | Nokia, Nokia Shanghai Bell | Rel-18 | Response to S2-2400062. Merged into S2-2401578 | Haiyang (Huawei) comments Laurent (Nokia): OK to merge this Tdoc in 0421 (to avoid // threads) ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 4.1 | S2-2400803 | LS OUT | Approval | [DRAFT] Reply LS on the user consent for trace reporting | Huawei, HiSilicon | Rel-18 | Response to S2-2400062. Merged into S2-2401578 | Laurent (Nokia): suggests to merge this Tdoc in 0421 (to avoid // threads on the same topic) Haiyang (Huawei) is OK to merge this Tdoc into 0421 ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 4.1 | - | - | - | Support of interworking between SA WG4 RTC and IMS | - | - | Docs:=2 | - | |
| 4.1 | S2-2400070 | LS In | Action | LS from SA WG4: LS on Support of interworking between SA WG4 RTC and IMS | SA WG4 (S4-232055) | Rel-18 | Response drafted in S2-2400591. Postponed | Leo (Deutsche Telekom) proposes to postpone the LS to the next SA2 meeting. | Postponed |
| 4.1 | S2-2400591 | LS OUT | Approval | [DRAFT] Reply LS on Support of interworking between SA WG4 RTC and IMS | NTT | Rel-18 | Response to S2-2400070. Postponed | Yi (China Mobile) ask question. Yoshihiro (NTT) answer to the questions for clarification. Haris(Qualcomm) comments and asks whether SA3-LI, SA1 and GSMA also needs to be involved in the LS response Yoshihiro (NTT) answer to the comments and propose to provide answer from SA2. Mu (Huawei) propose to postpone the LS out Haris(Qualcomm) responds Yi (China Mobile) comments and support QC comment. Yoshihiro (NTT) responds and asks questions for clarification. Leo (Deutsche Telekom) proposes to postpone this to the next SA2 meeting. ==== Revisions Deadline ==== Yoshihiro (NTT) Agrees to postpone this to the next SA2 meeting. ==== Final Comments Deadline ==== | Postponed |
| 4.1 | - | - | - | QoS to Carrier Mapping for SL CA | - | - | Docs:=3 | - | |
| 4.1 | S2-2400053 | LS In | Action | LS from RAN WG2: LS to SA WG2 on QoS to Carrier Mapping for SL CA | RAN WG2 (R2-2313623) | Rel-18 | Response drafted in S2-2401247. Final response in S2-2401579 | Replied to | |
| 4.1 | S2-2401247 | LS OUT | Approval | [DRAFT] Reply LS on QoS to Carrier Mapping for SL CA | Qualcomm Incorporated | Rel-18 | Response to S2-2400053. r05 Agreed. Revised to S2-2401579. | Fei (OPPO) comments and provides r02. LiMeng (Huawei) provides r01. Hong (Qualcomm) provides r03. LiMeng (Huawei) is fine with r03. LaeYoung (LGE) is also fine with r03. Saubhagya (Nokia) OK with r03, provides minor corrections in r04 Sudeep (Apple) provides r05. Saubhagya (Nokia) OK with r05 LaeYoung (LGE) is fine with r05. ==== Revisions Deadline ==== Fei (OPPO) is fine with r05. Hong (Qualcomm) is fine with r05. ==== Final Comments Deadline ==== | Revised |
| 4.1 | S2-2401579 | LS OUT | Approval | Reply LS on QoS to Carrier Mapping for SL CA | SA WG2 | Rel-18 | Revision of S2-2401247r05. Approved | Approved | |
| 4.1 | - | - | - | Tx profile for SL CA | - | - | Docs:=6 | - | |
| 4.1 | S2-2400052 | LS In | Action | LS from RAN WG2: LS to SA2 on Tx profile for SL CA | RAN WG2 (R2-2313622) | Rel-18 | Response drafted in S2-2400113. Final response in S2-2401581 | Replied to | |
| 4.1 | S2-2400113 | LS OUT | Approval | [DRAFT] Reply LS on Tx profile for SL CA | LG Electronics | Rel-18 | Response to S2-2400052. r00 + clean up agreed. Revised to S2-2401581. | Fei (OPPO) indicates that the approval of the LS is linked to the approval of the corresponding CR. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 4.1 | S2-2401581 | LS OUT | Approval | Reply LS on Tx profile for SL CA | SA WG2 | Rel-18 | Revision of S2-2400113r00 + clean up. Approved | Approved | |
| 4.1 | S2-2400114 | CR | Approval | 23.287 CR0196 (Rel-18, 'B'): Tx Profile per PC5 QoS Flow to AS layer | LG Electronics | Rel-18 | r02 Agreed. Revised to S2-2401580, merging S2-2400505 | Fei (OPPO) responds to LaeYoung (LGE). LaeYoung (LGE) responds to Fei (OPPO). Fei (OPPO) responds. LaeYoung (LGE) asks a Q for clarification on r01 to Fei (OPPO). Fei (OPPO) comments and provides r01. Hong (Qualcomm) asks for clarification from Laeyoung regarding the opt#2. LaeYoung (LGE) responds to Fei (OPPO) and Hong (Qualcomm), and is fine with r01. LaeYoung (LGE) thanks to Fei (OPPO) for co-sign. Fei (OPPO) would like to cosign. Shabnam (Ericsson) asks clarification of the NOTE 4 and 5 interpretation, see below LaeYoung (LGE) replies to Shabnam (Ericsson). Hong (Qualcomm) comments. Fei (OPPO) provides comments. LaeYoung (LGE) provides r02. ==== Revisions Deadline ==== Fei (OPPO) is fine with r02. Shabnam (Ericsson) thanks for the update, yes Hong explained correctly what I mean and ok with r02. ==== Final Comments Deadline ==== | Revised |
| 4.1 | S2-2401580 | CR | Approval | 23.287 CR0196R1 (Rel-18, 'B'): Tx Profile per PC5 QoS Flow to AS layer | LG Electronics, OPPO | Rel-18 | Revision of S2-2400114r02, merging S2-2400505. Approved | Agreed | |
| 4.1 | S2-2400505 | CR | Approval | 23.287 CR0197 (Rel-18, 'F'): Tx Profile for SL CA | OPPO | Rel-18 | Merged into S2-2401580 | LaeYoung (LGE) proposes to Merge this CR into S2-2400114 (LGE). Hong (Qualcomm) also suggests merging this CR into S2-2400114 (LGE). Fei (OPPO) is ok to mark this CR as merged. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 4.1 | - | - | - | Monitoring of Encrypted 5GS Signalling Traffic | - | - | Docs:=4 | - | |
| 4.1 | S2-2400021 | LS In | Action | LS from GSMA 5GPKI: LS to 3GPP re Monitoring of Encrypted 5GS Signalling Traffic | GSMA 5GPKI (LS Monitoring of Encrypted 5GS Signalling Traffic) | Revision of Postponed S2-2313227 from SA WG2#160. Noted | Shabnam (Ericsson) propose to NOTE this LS and handle any input, if available in future SA2 meeting from companies, be handled under SA LS in document 0037 for coordinated response via SA. Susana (Vodafone) proposes to postpone the LS to future SA2 meeting and handle it under SA LS in SA2-2400037. Thomas (Nokia) prefers noting but can live with postponing. Shabnam (Ericsson) SA2 will not respond to this LS directly & companies wanting to contribute SA2 can use the information available without keeping LS open? | Noted | |
| 4.1 | S2-2400023 | LS In | Information | LS from SA WG3: Reply LS on Monitoring of Encrypted 5GS Signalling Traffic | SA WG3 (S3-235009) | Revision of Postponed S2-2313231 from SA WG2#160. Noted | Shabnam (Ericsson) propose to NOTE this LS and handle any input, if available in future SA2 meeting from companies, be handled under SA LS in document 0037. | Noted | |
| 4.1 | S2-2400037 | LS In | Information | Reply LS to GSMA on Monitoring of Encrypted 5GS Signalling Traffic | TSG SA (SP-231668) | Rel-18 | Need co-ordinated response via TSG SA. Postponed | Leo (Deutsche Telekom) proposes to POSTPONE the LS-IN and discuss it at the next SA2 meeting. | Postponed |
| 4.1 | S2-2400031 | LS In | Information | LS from ETSI TC CYBER: Comments from ETSI TC CYBER on GSMA Solutions for Monitoring of Encrypted 5GS Signaling Traffic | ETSI TC CYBER (CYBER(23)35d008r1) | Noted | Noted | ||
| 4.1 | - | - | - | Other | - | - | Docs:=10 | - | |
| 4.1 | S2-2400032 | LS In | Information | LS from GSMA OPG: LS reply on LS on MSISDN exposure to trusted AF | GSMA OPG (OPG_159_Doc_03) | Noted | Noted | ||
| 4.1 | S2-2400345 | CR | Approval | 23.501 CR5011R3 (Rel-18, 'F'): Corrections to remove Nnef_UEId Service restrictions | Ericsson, Verizon, AT&T, Vodafone, Deutsche Telekom, Dish Network | Rel-18 | Revision of (unhandled) S2-2312545. CC#3: r04 endorsed. r04 Agreed. Revised to S2-2401582. | Laurent (Nokia): provides r01 Hui (Huawei) asks for clarification. Magnus (Ericsson) provides r02 Sudeep (Apple) raises concerns on the approach for this CR and prefers to wait till SA3 answer is available. Magnus (Ericsson) Answers Sudeep Sudeep (Apple) replies to Magnus and adds reference to the previous LS from SA3. Laurent (Nokia): provides r03 Sudeep (Apple) comments on UDM configuration. Hui (Huawei) provides further questions. Magnus (Ericsson) provides answers Magnus O (Ericsson) provides r04 Sudeep (Apple) responds to Magnus (Ericsson) on SA3's feedback. Magnus (Ericsson) Provides some further feedback ==== Revisions Deadline ==== Sudeep (Apple) proposes to postpone this CR (considering the progress we made in this meeting) till we get SA3 feedback on the LS sent in SA2#159. Laurent (Nokia): thinks we can proceed now with this CR but objects to R00, R02. Magnus (Ericsson) r04 does not seem to be on the server so to be clear r04 == r03 with the second bullet in the first change removed. Magnus (Ericsson) provides a possible way forward Sudeep (Apple) responds to the proposal for a new LS. Hui (Huawei) asks to postpone the CR Magnus (Ericsson) FYI link to related LS ==== Final Comments Deadline ==== | Revised |
| 4.1 | S2-2401582 | CR | Approval | 23.501 CR5011R4 (Rel-18, 'F'): Corrections to remove Nnef_UEId Service restrictions | Ericsson, Verizon, AT&T, Vodafone, Deutsche Telekom, Dish Network, Nokia | Rel-18 | Revision of S2-2400345r04. Endorsed | Endorsed | |
| 4.1 | S2-2400346 | CR | Approval | 23.502 CR4509R3 (Rel-18, 'F'): Corrections to remove Nnef_UEId Service restrictions | Ericsson, Verizon, AT&T, Vodafone, Deutsche Telekom, Dish Network | Rel-18 | Revision of (unhandled) S2-2312546. CC#3: r04 was endorsed. r04 Agreed. Revised to S2-2401583. | Laurent (Nokia): provides r01 Hui (Huawei) asks for question. Kisuk (Samsung) objects this CRs. Magnus (Ericsson) responds to Hui Kisuk (Samsung) comments Magnus (Ericsson) responds to Laurent Magnus (Ericsson) Responds to Kisuk Jinsook (DISH Network) comments Sudeep (Apple) seeks clarification on the NOTE about 33.501. Laurent (Nokia): answers: UDM (based on configuration) responds with AF specific ID or MSISDN Sudeep (Apple) suggests modification on UDM configuration. Hui(Huawei) provides comments. Kisuk(Samsung) provides comments. Magnus O (Ericsson) provides r02 Laurent (Nokia): provides r03 Sudeep (Apple) comments that NOTE in 4.15.10A about 33.501 is speculative and needs to be removed. Magnus O (Ericsson) provides r04 while still preferring r03 ==== Revisions Deadline ==== Sudeep (Apple) proposes to postpone this CR (considering the progress we made in this meeting) till we get SA3 feedback on the LS sent in SA2#159. Laurent (Nokia): thinks we can proceed now with this CR but objects to R00, R02. We suggest to go with R04 Sudeep (Apple) objects to r00, r01, r02, r03. Editorial fix needed for r04. Hui (Huawei) asks to postpone the CR ==== Final Comments Deadline ==== | Revised |
| 4.1 | S2-2401583 | CR | Approval | 23.502 CR4509R4 (Rel-18, 'F'): Corrections to remove Nnef_UEId Service restrictions | Ericsson, Verizon, AT&T, Vodafone, Deutsche Telekom, Dish Network, Nokia | Rel-18 | Revision of S2-2400346r04. Endorsed | Endorsed | |
| 4.1 | S2-2401576 | LS OUT | Approval | [DRAFT] LS on limited MSISDN exposure | Ericsson | Rel-18 | Created at CC#3. CC#4: r02 + clean up agreed. Revised to S2-2401649. | Magnus (Ericsson) provides draft LS to SA3 on limited MSISDN exposure Hui (Huawei) provides r01 ==== Final Comments Deadline ==== Sudeep (Apple) provides r02. Laurent (Nokia): proposes to go with R00 Magnus (Ericsson) prefers r00 can live with r01 and r02 Sudeep (Apple) objects to r00 and r01. Hui (Huawei) asks to go with r02. | Revised |
| 4.1 | S2-2401649 | LS OUT | Approval | LS on limited MSISDN exposure | SA WG2 | Rel-18 | Revision of S2-2401576r02 + clean up. Approved | Approved | |
| 4.1 | S2-2400525 | CR | Approval | 23.502 CR4692 (Rel-18, 'B'): UE MSISDN exposure to trusted AF | Samsung | Rel-18 | Noted | Laurent (Nokia): Objects to any version of the CR Magnus (Ericsson) propose to note this document and continue the discussion based on the CRs in 0345/0346. Kisuk (Samsung): propose this CR merge into S2-2400346. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Noted |
| 4.1 | S2-2400526 | CR | Approval | 23.501 CR5242 (Rel-18, 'B'): UE MSISDN exposure to trusted AF | Samsung | Rel-18 | Noted | Laurent (Nokia): Objects to any version of the CR Kisuk (Samsung): replies to Nokia Magnus (Ericsson) propose to note this document and continue the discussion based on the CRs in 0345/0346. Kisuk (Samsung): propose this CR merge into S2-2400345. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Noted |
| 4.1 | S2-2400188 | CR | Approval | 23.503 CR1239 (Rel-18, 'F'): Support for periodicity in the Route Selection Description | Ericsson | Rel-18 | Noted | Srinivas Garikipati (Nokia) comments on S2-2400188 <https://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_160AHE_Electronic_2024-01/Docs/S2-2400188.zip> Srinivas Garikipati (Nokia) comments on S2-2400188 <https://protect2.fireeye.com/v1/url?k=3dc167e2-5cbc8fa5-3dc0ecad-74fe485fff30-04f820a2f3334c2b&q=1&e=216feae6-0e50-4ee8-b179-a3aa4b141857&u=https%3A%2F%2Fwww.3gpp.org%2Fftp%2Ftsg_sa%2FWG2_Arch%2FTSGS2_160AHE_Electronic_2024-01%2FDocs%2FS2-2400188.zip> Srinivas Garikipati (Nokia) provides comments Yang (OPPO) ask question for clarification Belen (ericsson) replies to comments. Srinivas Garikipati (Nokia) replies to the feedback shared by Belen Belen (Ericsson) asks to NOTE this paper, as it cannot be agreed ==== Revisions Deadline ==== | Noted |
| 4.2 | - | - | - | P-CRs/CRs related to use of inclusive language in 3GPP | - | - | Docs:=0 | - | |
| 5 | - | - | - | Pre-Rel-17 Maintenance (excluding all 5G topics) | - | - | Docs:=0 | - | |
| 5.1 | - | - | - | 3GPP Packet Access Maintenance | - | - | Docs:=0 | - | |
| 5.2 | - | - | - | QoS and PCC Maintenance | - | - | Docs:=0 | - | |
| 5.3 | - | - | - | Non-3GPP Access Maintenance | - | - | Docs:=0 | - | |
| 5.4 | - | - | - | IMS and IMS-Related Maintenance | - | - | Docs:=0 | - | |
| 6 | - | - | - | Rel-15/Rel-16 Maintenance for 5G (only related to 5GS_Ph1 Work Item) | - | - | Docs:=0 | - | |
| 6.1 | - | - | - | General aspects, concepts and reference models | - | - | Docs:=0 | - | |
| 6.2 | - | - | - | Common Access Control, RM and CM functions and procedure flows | - | - | Docs:=0 | - | |
| 6.3 | - | - | - | Session management and continuity functions and flows | - | - | Docs:=0 | - | |
| 6.4 | - | - | - | Security related functions and flows | - | - | Docs:=0 | - | |
| 6.5 | - | - | - | QoS concept and functionality | - | - | Docs:=0 | - | |
| 6.6 | - | - | - | Policy and charging control | - | - | Docs:=0 | - | |
| 6.7 | - | - | - | 3GPP access specific functionality and flows | - | - | Docs:=0 | - | |
| 6.8 | - | - | - | Specific services support | - | - | Docs:=0 | - | |
| 6.9 | - | - | - | Interworking and Migration | - | - | Docs:=0 | - | |
| 6.10 | - | - | - | Non-3GPP access specific functionality and flows | - | - | Docs:=0 | - | |
| 6.11 | - | - | - | Framework functions | - | - | Docs:=0 | - | |
| 7 | - | - | - | Rel-16 Maintenance for 5G (excluding 5GS_Ph1) | - | - | Docs:=0 | - | |
| 7.1 | - | - | - | Architecture enhancements for 3GPP support of advanced V2X services (eV2XARC) | - | - | Docs:=0 | - | |
| 7.2 | - | - | - | Wireless and Wireline Convergence for the 5G system architecture (5WWC) | - | - | Docs:=0 | - | |
| 7.3 | - | - | - | Access Traffic Steering, Switch and Splitting support in the 5G system architecture (ATSSS) | - | - | Docs:=0 | - | |
| 7.4 | - | - | - | Cellular IoT support and evolution for the 5G System (5G_CIoT) | - | - | Docs:=0 | - | |
| 7.5 | - | - | - | Enablers for Network Automation for 5G (eNA) | - | - | Docs:=0 | - | |
| 7.6 | - | - | - | Enhancement to the 5GC Location Services (5G_eLCS) | - | - | Docs:=0 | - | |
| 7.7 | - | - | - | 5GS Enhanced support of Vertical and LAN Services (Vertical_LAN) | - | - | Docs:=0 | - | |
| 7.8 | - | - | - | Enhancements to the Service-Based 5G System Architecture (5G_eSBA) | - | - | Docs:=0 | - | |
| 7.9 | - | - | - | Architecture enhancements for the support of Integrated access and backhaul (IABARC) | - | - | Docs:=0 | - | |
| 7.10 | - | - | - | Enhancement of URLLC supporting in 5GC (5G_URLLC) | - | - | Docs:=0 | - | |
| 7.11 | - | - | - | Enhancement of Network Slicing (eNS) | - | - | Docs:=0 | - | |
| 7.12 | - | - | - | Optimisations on UE radio capability signalling (RACS) | - | - | Docs:=0 | - | |
| 7.13 | - | - | - | Enhanced IMS to 5GC Integration (eIMS5G_SBA) | - | - | Docs:=0 | - | |
| 7.14 | - | - | - | User Data Interworking and Coexistence (UDICoM) | - | - | Docs:=0 | - | |
| 7.15 | - | - | - | Enhancing Topology of SMF and UPF in 5G Networks (ETSUN) | - | - | Docs:=0 | - | |
| 7.16 | - | - | - | 5GS Transfer of Policies for Background Data Transfer (xBDT) | - | - | Docs:=0 | - | |
| 7.17 | - | - | - | Single radio voice continuity from 5GS to 3G (5G_SRVCC) | - | - | Docs:=0 | - | |
| 8 | - | - | - | Rel-17 Maintenance | - | - | Docs:=0 | - | |
| 8.1 | - | - | - | Enablers for Network Automation for 5G - Phase 2 (eNA_Ph2) | - | - | Docs:=12 | - | |
| 8.1 | - | - | - | Issues related to user consent for retrieving data stored in the ADRF/NWDAF | - | - | Docs:=11 | - | |
| 8.1 | S2-2400044 | LS In | Action | LS from CT WG3: LS on Issues related to user consent for retrieving data stored in the ADRF/NWDAF | CT WG3 (C3-235567) | Rel-17 | Responses drafted in S2-2400280, S2-2400988. Final response in S2-2401584 | Replied to | |
| 8.1 | S2-2400280 | LS OUT | Approval | [DRAFT] LS on Issues related to user consent for retrieving data stored in the ADRF/NWDAF | Huawei, HiSilicon | Rel-17 | Response to S2-2400044. Merged into S2-2401584 | Yannick (Nokia) suggests to merge this contribution into S2-2400988. Haiyang (Huawei) is OK to merge this contribution into S2-2400988. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 8.1 | S2-2400988 | LS OUT | Approval | [DRAFT] Reply LS on Issues related to user consent for retrieving data stored in the ADRF/NWDAF | Nokia, Nokia Shanghai Bell | Rel-17 | Response to S2-2400044. r03 Agreed. Revised to S2-2401584, merging S2-2400280 | Yannick (Nokia) provides r01. Haiyang (Huawei) provides r02. Yannick (Nokia) provides r03. Haiyang (Huawei) is OK with r03. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 8.1 | S2-2401584 | LS OUT | Approval | Reply LS on Issues related to user consent for retrieving data stored in the ADRF/NWDAF | SA WG2 | Rel-17 | Revision of S2-2400988r03, merging S2-2400280. Approved | Approved | |
| 8.1 | S2-2400281 | CR | Approval | 23.288 CR1023 (Rel-17, 'F'): Correction on user consent for retrieving data stored in the ADRF/NWDAF | Huawei, HiSilicon | Rel-17 | r02 Agreed. Revised to S2-2401585, merging S2-2400964 | Haiyang (Huawei) provides r01 based on discussion in 0964 thread Yannick (Nokia) provides r02. Haiyang (Huawei) is OK with r02 ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 8.1 | S2-2401585 | CR | Approval | 23.288 CR1023R1 (Rel-17, 'F'): Correction on user consent for retrieving data stored in the ADRF/NWDAF | Huawei, HiSilicon, Nokia, Nokia Shanghai Bell | Rel-17 | Revision of S2-2400281r02, merging S2-2400964. Correct cover sheet to Rel-17. Revised to S2-2401643. | Revised | |
| 8.1 | S2-2401643 | CR | Approval | 23.288 CR1023R2 (Rel-17, 'F'): Correction on user consent for retrieving data stored in the ADRF/NWDAF | Huawei, HiSilicon, Nokia, Nokia Shanghai Bell | Rel-17 | Revision of S2-2401585. Approved | Agreed | |
| 8.1 | S2-2400282 | CR | Approval | 23.288 CR1024 (Rel-18, 'A'): Correction on user consent for retrieving data stored in the ADRF/NWDAF | Huawei, HiSilicon | Rel-18 | r00 + clean up agreed. Revised to S2-2401586, merging S2-2400976 | ==== Final Comments Deadline ==== | Revised |
| 8.1 | S2-2401586 | CR | Approval | 23.288 CR1024R1 (Rel-18, 'A'): Correction on user consent for retrieving data stored in the ADRF/NWDAF | Huawei, HiSilicon, Nokia, Nokia Shanghai Bell | Rel-18 | Revision of S2-2400282r00 + clean up, merging S2-2400976. Approved | Agreed | |
| 8.1 | S2-2400964 | CR | Approval | 23.288 CR1046 (Rel-17, 'F'): Corrections for user consent checking for data retrieval from ADRF | Nokia, Nokia Shanghai Bell | Rel-17 | Merged into S2-2401585 | Haiyang (Huawei) suggests to merge this paper into 0281 Yannick (Nokia) provides feedback on Huawei's proposal. Haiyang (Huawei) replies Yannick (Nokia) requests to mark this contribution as merged into S2-2400988. Yannick (Nokia) requests to mark this contribution as merged into S2-2400281. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 8.1 | S2-2400976 | CR | Approval | 23.288 CR1047 (Rel-18, 'A'): Corrections for user consent checking for data retrieval from ADRF | Nokia, Nokia Shanghai Bell | Rel-18 | Merged into S2-2401586 | Yannick (Nokia) requests to mark this contribution as merged into S2-2400282. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 8.1 | - | - | - | Other | - | - | Docs:=1 | - | |
| 8.1 | S2-2400045 | LS In | Information | LS from CT WG3: LS on Authorization of NF service consumer for data collection via DCCF | CT WG3 (C3-235594) | Rel-17 | Noted | Leo (Deutsche Telekom) proposes to NOTE the LS, there is no action to SA2 Yannick (Nokia) shares Leo (Deutsche Telekom) view and also proposes to NOTE this LS. | Noted |
| 8.2 | - | - | - | Enhanced support of Non-Public Networks (eNPN) | - | - | Docs:=0 | - | |
| 8.3 | - | - | - | Enhancement of support for Edge Computing in 5GC (eEDGE_5GC) | - | - | Docs:=0 | - | |
| 8.4 | - | - | - | Enhancement of Network Slicing Phase 2 (eNS_Ph2) | - | - | Docs:=0 | - | |
| 8.5 | - | - | - | Enhanced support of Industrial IoT - TSC/URLLC enhancements (IIoT) | - | - | Docs:=0 | - | |
| 8.6 | - | - | - | Access Traffic Steering, Switch and Splitting support in the 5G system architecture Phase 2 (ATSSS_Ph2) | - | - | Docs:=0 | - | |
| 8.7 | - | - | - | Support of Aerial Systems Connectivity, Identification, and Tracking (ID_UAS) | - | - | Docs:=0 | - | |
| 8.8 | - | - | - | System enhancement for Proximity based Services in 5GS (5G_ProSe) | - | - | Docs:=10 | - | |
| 8.8 | - | - | - | Uniqueness of ProSe U2N RSC | - | - | Docs:=6 | - | |
| 8.8 | S2-2400026 | LS In | Action | LS from SA WG3: LS on uniqueness of ProSe U2N RSC | SA WG3 (S3-235076) | Rel-17 | Revision of Postponed S2-2313235 from SA WG2#160. Responses drafted in S2-2400599, S2-2400824, S2-2400977, S2-2401265. Final response in S2-2401587 | Fei (OPPO) comments. | Replied to |
| 8.8 | S2-2400599 | LS OUT | Approval | [DRAFT] Reply LS on uniqueness of ProSe U2N RSC | Nokia, Nokia Shanghai Bell | Rel-17 | Response to S2-2400026. Merged into S2-2401587 | Shabnam (Ericsson) proposes this document to be merged into proposed response in tdoc 1265 Saubhagya (Nokia) agrees to the proposal on merging to 1265 ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 8.8 | S2-2400824 | LS OUT | Approval | [DRAFT] Reply LS on uniqueness of ProSe U2N RSC | vivo | Rel-17 | Response to S2-2400026. Merged into S2-2401587 | Shabnam (Ericsson) proposes this document to be merged into proposed response in tdoc 1265 Wen (vivo)confirms that this paper is merged into 1265 with some clarifications in CR that the U2N RSC is unique used by MNO ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 8.8 | S2-2400977 | LS OUT | Approval | [DRAFT] Reply LS on Uniqueness of ProSe U2N RSC | Ericsson | Rel-18 | Response to S2-2400026. Merged into S2-2401587 | Shabnam (Ericsson) proposes this document to be merged into proposed response in tdoc 1265 ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 8.8 | S2-2401265 | LS OUT | Approval | [DRAFT] Reply LS on uniqueness of ProSe U2N RSC | Qualcomm Incorporated | Rel-17 | Response to S2-2400026. r01 Agreed. Revised to S2-2401587, merging S2-2400599, S2-2400824 and S2-2400977 | Shabnam (Ericsson) proposes to use this reply as baseline and consider 0599, 0824, 0977 merged into this. Fei (OPPO) comments. Saubhagya (Nokia) comments Fei (OPPO) attched CR might be helpful. Hong (Qualcomm) comments. Steve (Huawei) comments. Mehrdad (MediaTek Inc.) provides comment Hong (Qualcomm) provides r01. Steve (Huawei) comments on term alignment - thanks. ==== Revisions Deadline ==== Mehrdad (MediaTek Inc.) is OK with r01 ==== Final Comments Deadline ==== | Revised |
| 8.8 | S2-2401587 | LS OUT | Approval | Reply LS on uniqueness of ProSe U2N RSC | SA WG2 | Rel-17 | Revision of S2-2401265r01, merging S2-2400599, S2-2400824 and S2-2400977. Approved | Approved | |
| 8.8 | - | - | - | Other | - | - | Docs:=4 | - | |
| 8.8 | S2-2400978 | CR | Approval | 23.304 CR0370R1 (Rel-18, 'F'): Clarification of Relay Service Code used by UEs from different PLMNs | Ericsson | Rel-18 | Revision of (unhandled) S2-2310694. r01 Agreed. Revised to S2-2401588. | Hong (Qualcomm) provides r01. ==== Revisions Deadline ==== Steve (Huawei) thanks, r01 is good. ==== Final Comments Deadline ==== | Revised |
| 8.8 | S2-2401588 | CR | Approval | 23.304 CR0370R2 (Rel-18, 'F'): Clarification of Relay Service Code used by UEs from different PLMNs | Ericsson | Rel-18 | Revision of S2-2400978r01. Approved | Agreed | |
| 8.8 | S2-2400028 | LS In | Information | LS from SA WG3: Reply LS on Retrieving keys for decryption of protected IEs for U2N relay | SA WG3 (S3-235098) | Rel-17 | Revision of Postponed S2-2313237 from SA WG2#160. Noted | Fei (OPPO) proposes to note this incoming LS. Steve (Huawei) agrees with Fei. | Noted |
| 8.8 | S2-2400022 | LS In | Information | LS from SA WG3: Reply LS on security for 5G ProSe UE-to-network relay discovery | SA WG3 (S3-234992) | Rel-17 | Revision of Postponed S2-2313230 from SA WG2#160. Noted | Fei (OPPO) proposes to note this incoming LS. Steve (Huawei) agrees with Fei. | Noted |
| 8.9 | - | - | - | Architectural enhancements for 5G multicast-broadcast services (5MBS) | - | - | Docs:=0 | - | |
| 8.10 | - | - | - | System enablers for multi-USIM devices (MUSIM) | - | - | Docs:=0 | - | |
| 8.11 | - | - | - | Architecture aspects for using satellite access in 5G (5GSAT_ARCH) | - | - | Docs:=0 | - | |
| 8.12 | - | - | - | Architecture enhancements for 3GPP support of advanced V2X services - Phase 2 (eV2XARC_Ph2) | - | - | Docs:=0 | - | |
| 8.13 | - | - | - | 5G System Enhancement for Advanced Interactive Services (5G_AIS) | - | - | Docs:=0 | - | |
| 8.14 | - | - | - | Enhancement to the 5GC LoCation Services-Phase 2 (5G_eLCS_Ph2) | - | - | Docs:=0 | - | |
| 8.15 | - | - | - | Multimedia Priority Service (MPS) Phase 2 (MPS2) | - | - | Docs:=0 | - | |
| 8.16 | - | - | - | Dynamic management of group-based event monitoring (TEI17_GEM) | - | - | Docs:=0 | - | |
| 8.17 | - | - | - | N7/N40 Interfaces Enhancements to Support GERAN and UTRAN (TEI17_NIESGU) | - | - | Docs:=0 | - | |
| 8.18 | - | - | - | System enhancement for Redundant PDU Session (TEI17_SE_RPS) | - | - | Docs:=0 | - | |
| 8.19 | - | - | - | IMS Optimization for HSS Group ID in an SBA environment (TEI17_IMSGID) | - | - | Docs:=0 | - | |
| 8.20 | - | - | - | Support for Signed Attestation for Priority and Emergency Sessions (TEI17_SAPES) | - | - | Docs:=0 | - | |
| 8.21 | - | - | - | Dynamically Changing AM Policies in the 5GC (TEI17_DCAMP) | - | - | Docs:=0 | - | |
| 8.22 | - | - | - | IP address pool information from UDM (TEI17_IPU) | - | - | Docs:=0 | - | |
| 8.23 | - | - | - | Same PCF selection for AMF and SMF (TEI17-SPSFAS) | - | - | Docs:=0 | - | |
| 8.24 | - | - | - | Support of different slices over different Non-3GPP access (TEI17_N3SLICE) | - | - | Docs:=0 | - | |
| 8.25 | - | - | - | Minimization of Service Interruption (MINT) | - | - | Docs:=0 | - | |
| 8.26 | - | - | - | Architecture Enhancement for NR Reduced Capability Devices (ARCH_NR_REDCAP) | - | - | Docs:=0 | - | |
| 8.27 | - | - | - | Architecture support for NB-IoT/eMTC Non-Terrestrial Networks in EPS (IoT_SAT_ARCH_EPS) | - | - | Docs:=20 | - | |
| 8.27 | - | - | - | UE Location Information for NB-IoT NTN | - | - | Docs:=11 | - | |
| 8.27 | S2-2400020 | LS In | Action | LS from RAN WG2: LS on UE Location Information for NB-IoT NTN | RAN WG2 (R2-2311326) | Rel-18 | Revision of Postponed S2-2311984 from SA WG2#160. Responses drafted in S2-2400419, S2-2401121. CC#4: Postponed. | Postponed | |
| 8.27 | S2-2400419 | LS OUT | Approval | [DRAFT] Reply LS on UE Location Information for NB-IoT NTN | Qualcomm | Rel-18 | Revision of (unhandled) S2-2313106. Response to S2-2400020. CC#4: Postponed | Steve (Huawei) comments Haris(Qualcomm) provides r01 Yunjing (CATT) provides r02 and asks a question for clarification Stefan (Ericsson) provides comments Haris(Qualcomm) responds to Stefan Haris(Qualcomm) responds to Yunjing Steve (Huawei) comments on pTAU Haris(Qualcomm) responds to Steve Stefan (Ericsson) provides r03 Haris(Qualcomm) is fine with r03 ==== Revisions Deadline ==== Saubhagya (Nokia) provides comments on pTAU and Service request and asks its relation with SMC Ramon (Sateliot) comments on r03 Stefan (Ericsson) replies to Saubhagya Haris(Qualcomm) responds to Ramon Amy (vivo) proposes to modify NB-IoT NTN to IoT NTN in the first sentence of the overall description and the ACTION parts. Ramon(Sateliot) comments on Haris(Qualcomm) response Thierry (Novamint) is fine with r03 Mehrdad (MediaTek Inc.) thinks r03 needs additional update. Agrees with vivo and also proposes to modify NB-IoT NTN to IoT NTN in the first sentence of the overall description and the ACTION parts. Thierry (Novamint) provides further comments linked to CR 351: The reply to LS (0419) can only be agreed once CR351 has been agreed and it may require a further update as proposed by Amy, Luca, Mehrdad based on Ramon's comment Mehrdad (MediaTek Inc.) clarifies that we have already stated new changes needed on the LS. So r03 of S2-2400419 is not agreeable yet. We can re-check status at CC#4. Also on CRs, if they are technically endorsable, we don't see why they can not be agreed at this meeting. ==== Final Comments Deadline ==== Luca (Inmarsat) re-states that indeed the LS should not be limited to NB-IoT and that its outcome does not impact the validity of the proposed CRs for the basic mechanism. We also agree that the CRs should be agreed as a starting point, then we can look at what's needed in addition, but we should take it in steps. Haris(Qualcomm) responds to comments Stefan (Ericsson) follow-up comment and not sure on the completeness of the CR | Postponed |
| 8.27 | S2-2401121 | LS OUT | Approval | [DRAFT] LS reply on UE Location Information for NB-IoT NTN | CATT | Rel-17 | Response to S2-2400020. Noted | Haris(Qualcomm) comments Yunjing(CATT) replies to Haris(Qualcomm). Guillaume (MediaTek Inc.) comments. Yunjing (CATT) replies to Guillaume (MediaTek Inc.). Haris(Qualcomm) asks question for clarification Yunjing (CATT) replies to Haris(Qualcomm). Guillaume (MediaTek Inc.) responds to Yunjing (CATT) ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Noted |
| 8.27 | S2-2400041 | LS In | Action | LS from CT WG1: LS on UE Location Information for NB-IoT NTN | CT WG1 (C1-239363) | Rel-18 | Postponed | Postponed | |
| 8.27 | S2-2400417 | DISCUSSION | Approval | Discussion on UE Location Information for NB-IoT NTN . | Qualcomm Incorporated | Noted | Steve (Huawei) comments as the discussion is marked for approval, should be noted. ==== Revisions Deadline ==== | Noted | |
| 8.27 | S2-2400350 | DISCUSSION | Approval | Support for additional mechanisms for providing UE location with satellite NB-IoT . | Ericsson | Rel-18 | Noted | Steve (Huawei) comments as the discussion is marked for approval, should be noted. ==== Revisions Deadline ==== | Noted |
| 8.27 | S2-2400351 | CR | Approval | 23.401 CR3762 (Rel-18, 'F'): Mechanisms for UE location reporting for NB-IoT satellite access | Ericsson | Rel-18 | CC#4: r01 endorsed. Revised to S2-2401653. | Haris(Qualcomm) provides comments Saubhagya (Nokia) provide comments. Guillaume (MediaTek Inc.) comments and replies to Nokia Stefan (Ericsson) replies to Qualcomm Saubhagya (Nokia) replies to MediaTek Inc Guillaume (MediaTek Inc.) supports the proposal from Ericsson as a way forward to resolve the issue. Stefan (Ericsson) provides r01 Thierry (Novamint) supports Ericsson's proposal & CR as a way forward ==== Revisions Deadline ==== Chris (Vodafone) says the LS in 0419r3 says the CRs are technically endorsed, not approved? Which are we requesting here? Haris(Qualcomm) agrees to endorse r01 NOT approve yet Mehrdad (MediaTek Inc.) only agrees with LS in S2-2400419 with the assumption that this CR is agreed at this meeting. Amy (vivo) supports Mehrdad (MediaTek Inc.) to only agree with LS in S2-2400419 with the assumption that this CR is agreed at this meeting. Thierry (Novamint) proposes the CR 0351r01 to be agreed not just endorsed Haris(Qualcomm) responds to Mehrdad and explains why the CRs should be endorsed Amy (vivo) replies to Haris (Qualcomm) Mehrdad (MediaTek Inc.) replies to Qualcomm and clarifies that we have already stated new changes needed on the LS in the other thread. So r03 of S2-2400419 is not agreeable yet. We can re-check status at CC#4. Also on CRs, if they are technically endorsable, we don't see why they can not be agreed at this meeting. The load for plenary will be minimal. Haris(Qualcomm) proposes to discuss in CC#4 ==== Final Comments Deadline ==== Ramon(Sateliot) supports the CR(s) to be agreed (not just endorsed) and supports referring to 'IoT NTN' instead of 'NB-IoT NTN' in the related LS | Revised |
| 8.27 | S2-2401653 | CR | Approval | 23.401 CR3762R1 (Rel-18, 'F'): Mechanisms for UE location reporting for NB-IoT satellite access | Ericsson | Rel-18 | Revision of S2-2400351r01. Endorsed | Endorsed | |
| 8.27 | S2-2400404 | CR | Approval | 23.401 CR3761R1 (Rel-18, 'F'): NB-IoT NTN: UE Coarse Location Information Reporting | MediaTek Inc., Airbus, CEWiT, Deutsche Telekom, Echostar, ESA, Gatehouse, Inmarsat/Viasat, JSAT, Ligado, Lockheed Martin, Novamint, OQ Technology, Reliance Jio, Sateliot, Skylo, Thales, TNO, vivo | Rel-18 | Revision of (unhandled) SP-231595 from TSG SA#102. Noted | Haris(Qualcomm) provides comments Stefan (Ericsson) comments ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Noted |
| 8.27 | S2-2400652 | DISCUSSION | Discussion | Way forward proposal for NB-IoT UE support for coarse location reporting. | Rel-18 | Noted | Noted | ||
| 8.27 | S2-2400653 | CR | Approval | 23.401 CR3764 (Rel-18, 'B'): Enable eligible NB-IoT UE for coarse location reporting | Rel-18 | Postponed | Haris(Qualcomm) asks question for clarification Steve (Huawei) comments Ellen (Google) provides feedback to Steve (Huawei) comments Ellen (Google) feedback to Harris (Qualcomm) comment. Ellen (Google) provides r01 <https://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_160AHE_Electronic_2024-01/INBOX/Revisions/S2-2400653r01.zip> Guillaume (MediaTek Inc.) expresses concerns on this proposal Ellen (Google) provides r01 <https://protect2.fireeye.com/v1/url?k=6662949d-07e981ab-66631fd2-74fe485fffe0-1a2d894c68cff26d&q=1&e=ef0b950b-9323-4832-90fb-0d7f790a2852&u=https%3A%2F%2Fwww.3gpp.org%2Fftp%2Ftsg_sa%2FWG2_Arch%2FTSGS2_160AHE_Electronic_2024-01%2FINBOX%2FRevisions%2FS2-2400653r01.zip> Haris(Qualcomm) cannot understand r01 Steve (Huawei) has concerns on this subscription information Stefan (Ericsson) requests for clarification Ellen (Google) feedback to Haris, Steven, Stefan, Guillaume Haris(Qualcomm) responds to Ellen and explains further Ellen (Google) responds to Harris and provides r02 ==== Revisions Deadline ==== Ellen (Google) feedback to Jinsook Question about the scenario mentioned by Steve Jinsook (DISH Network) Question about the scenario mentioned by Steve Haris(Qualcomm) comments that more discussion is needed for the user consent aspects and proposes to postpone the CR Chris (Vodafone) says the LS says we are technically endorsing the CRs. Or is this for approval? Steve (Huawei) seems noting is the way to go. Ellen (Google) agrees to postpone this CR and thanks Haris (Qualcomm) and Luca (Inmarsat) for sharing views and history discussion. ==== Final Comments Deadline ==== | Postponed | |
| 8.27 | - | - | - | Other | - | - | Docs:=9 | - | |
| 8.27 | S2-2400068 | LS In | Information | Reply LS on the service requirement of restricting satellite access RAT type | SA WG1 (S1-233296) | Rel-18 | Response drafted in S2-2401577. CC#4: Final response in in S2-2401650. | Replied to | |
| 8.27 | S2-2401577 | LS OUT | Approval | [DRAFT] Response to 'Reply LS on the service requirement of restricting satellite access RAT type' | Vodafone | Rel-18 | Created at CC#3. Response to S2-2400068. CC#4: r01 + clean up agreed. Revised to S2-2401650. | ==== Final Comments Deadline ==== Chris (Vodafone) says that the draft LS triggered by S2-2400068 is in the inbox in 1577. It is also in CC#4 folder along with an r01 that corrects some formal errors. | Revised |
| 8.27 | S2-2401650 | LS OUT | Approval | Response to 'Reply LS on the service requirement of restricting satellite access RAT type' | SA WG2 | Rel-18 | Revision of S2-2401577. Approved | Approved | |
| 8.27 | S2-2401281 | CR | Approval | 23.501 CR5300 (Rel-17, 'F'): Handover control for NR-terrestrial to LTE satellite access | Vodafone | Rel-17 | r02 + changes Agreed. Revised to S2-2401630. | Amy (vivo) provide comments. Chris (Vodafone) replies to vivo. Steve (Huawei) comments in NB-IoT via SAT in 5GC Chris (Vodafone) replies to Huawei saying that this is not for NB-IoT via SAT connected to 5GC Steve (Huawei) provides r01 Chris (Vodafone) is OK with r01 but thinks a bit extra is better and provides r02 Stefan (Ericsson) provides comments Chris (Vodafone) replies to Ericsson Steve (Huawei) comments. Stefan (Ericsson) replies ==== Revisions Deadline ==== Amy (vivo) proposes to postpone this CR as sharing the same concern with Stefan (Ericsson) about sending NB-IoT,,, to AMF Chris (Vodafone) does not see the need to postpone. By error, the 3GPP 5GS standards do not support the intended EPS subscription controls - this should be corrected. Amy (vivo) seeks more clarifications Haris(Qualcomm) agrees with Chris and supports approving r02. Amy (vivo) seeks more clarifications again. The modifications are ok, but the reason for change dos not conform to the modifications. Amy (vivo) proposes to agree r02 + deleting 'Note that there is no need for any RAN Rel 17 radio interface specification support to enable handover to satellite systems that (are commercially deploying and) operate with unmodified LTE handsets.' In reason of change, as a way forward Amy (vivo) replies, and proposes again to agree r02 + deleting 'Note that there is no need for any RAN Rel 17 radio interface specification support to enable handover to satellite systems that (are commercially deploying and) operate with unmodified LTE handsets.' In reason of change, as a way forward Jinsook (DISH Network) Thanks Chris for this contribution, don't we need to reply to LS for this progress? Chris (Vodafone) replies to vivo: as we are on Friday afternoon, I'm OK to remove that sentence ('Note that there is no need for any RAN Rel 17 radio interface specification support to enable handover to satellite systems that (are commercially deploying and) operate with unmodified LTE handsets.') from the cover sheet and keep the rest of r02 unchanged. Chris replies to DISH Network. Not essential, but I'm OK to have a new doc for an LS to reply to 0068 - main recipient should be R3. ==== Final Comments Deadline ==== Chris (Vodafone) says that the related LS in 1577 is now in the inbox. Comments welcome. | Revised |
| 8.27 | S2-2401630 | CR | Approval | 23.501 CR5300R1 (Rel-17, 'F'): Handover control for NR-terrestrial to LTE satellite access | Vodafone | Rel-17 | Revision of S2-2401281r02 + changes. Approved | Agreed | |
| 8.27 | S2-2401282 | CR | Approval | 23.501 CR5301 (Rel-18, 'A'): Handover control for NR-terrestrial to LTE satellite access | Vodafone | Rel-18 | r00 + clean up agreed. Revised to S2-2401631. | Chris (Vodafone) says that this is the mirror CR to his 1281. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 8.27 | S2-2401631 | CR | Approval | 23.501 CR5301R1 (Rel-18, 'A'): Handover control for NR-terrestrial to LTE satellite access | Vodafone | Rel-18 | Revision of S2-2401282r00 + clean up. Approved | Agreed | |
| 8.27 | S2-2401033 | CR | Approval | 23.271 CR0438 (Rel-18, 'F'): Support for UE location verification when location is provided by MME | Ericsson | Rel-18 | CC#4: r01 endorsed. Revised to S2-2401654. | Haris(Qualcomm) provides comments Stefan (Ericsson) replies Haris(Qualcomm) responds Yunjing (CATT) provides comments. Stefan (Ericsson) responds to Haris Stefan (Ericsson) replies to Yunjing Yunjing (CATT) replies to Stefan (Ericsson). Steve (Huawei) comments. Haris(Qualcomm) comments and proposes way forward Stefan (Ericsson) provides r01 ==== Revisions Deadline ==== Haris(Qualcomm) agrees to endorse r01 NOT approve yet Haris(Qualcomm) proposes to discuss in CC#4 since it is related with LS (0419) and TS 23.410 CR (0351) ==== Final Comments Deadline ==== | Revised |
| 8.27 | S2-2401654 | CR | Approval | 23.271 CR0438R1 (Rel-18, 'F'): Support for UE location verification when location is provided by MME | Ericsson | Rel-18 | Revision of S2-2401033r01. Endorsed | Endorsed | |
| 8.28 | - | - | - | Rel-17 CAT B/C alignment CR(s) due to the work led by other 3GPP Working Groups | - | - | Docs:=0 | - | |
| 9 | - | - | - | Rel-18 WIDs | - | - | Docs:=0 | - | |
| 9.1.2 | - | - | - | 5G System with Satellite Backhaul (5GSATB) | - | - | Docs:=8 | - | |
| 9.1.2 | S2-2400307 | CR | Approval | 23.501 CR5226 (Rel-18, 'F'): Clarification on satellite backhaul category change indication | Samsung | Rel-18 | r00 + changes Agreed. Revised to S2-2401483, merging S2-2400702 | Hucheng(CATT) provides comments Heng(China Telecom) provides r01 to merge 0702 DongYeon (Samsung) replies to Hucheng (CATT). ==== Revisions Deadline ==== Heng (China Telecom) is ok with 00 + China Telecom cosign(merge 0702) DongYeon (Samsung) prefers r00, asks to Hucheng (CATT) and Heng (China Telecom) their preferences. ==== Final Comments Deadline ==== | Revised |
| 9.1.2 | S2-2401483 | CR | Approval | 23.501 CR5226R1 (Rel-18, 'F'): Clarification on satellite backhaul category change indication | Samsung, China Telecom | Rel-18 | Revision of S2-2400307r00 + changes, merging S2-2400702. Approved | Agreed | |
| 9.1.2 | S2-2400308 | CR | Approval | 23.502 CR4676 (Rel-18, 'F'): Clarification on satellite backhaul category change indication | Samsung | Rel-18 | r01 Agreed. Revised to S2-2401484, merging S2-2400703 | Heng (China Telecom) provides r01 to merge 0703 DongYeon (Samsung) is OK with r01 ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 9.1.2 | S2-2401484 | CR | Approval | 23.502 CR4676R1 (Rel-18, 'F'): Clarification on satellite backhaul category change indication | Samsung, China Telecom | Rel-18 | Revision of S2-2400308r01, merging S2-2400703. Approved | Agreed | |
| 9.1.2 | S2-2400310 | CR | Approval | 23.503 CR1241 (Rel-18, 'F'): Clarification on satellite backhaul category change indication | Samsung | Rel-18 | r02 Agreed. Revised to S2-2401485. | Haris(Qualcomm) provides comment Stefan (Ericsson) comments Hui (Huawei) provides r01 DongYeon (Samsung) asks to Hui (Huawei) on the r01, and replies to Haris (Qualcomm) and Stefan (Ericsson). Hui (Huawei) provides r02 based on r00. ==== Revisions Deadline ==== DongYeon (Samsung) is OK with r02. ==== Final Comments Deadline ==== | Revised |
| 9.1.2 | S2-2401485 | CR | Approval | 23.503 CR1241R1 (Rel-18, 'F'): Clarification on satellite backhaul category change indication | Samsung | Rel-18 | Revision of S2-2400310r02. Approved | Agreed | |
| 9.1.2 | S2-2400702 | CR | Approval | 23.501 CR5021R1 (Rel-18, 'F'): Clarification of satellite backhaul category change | China Telecom | Rel-18 | Revision of (unhandled) S2-2310851. Confirm CR Number - CR states 5021r1!. Confirm CR Revision - CR states 5021! Merged into S2-2401483 | Heng(China Telecom) provides revision and suggest merge with 0307 Heng(China Telecom) provides a merged revision in 0307 thread. DongYeon (Samsung) agrees to merge 0702 into 0307. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 9.1.2 | S2-2400703 | CR | Approval | 23.502 CR4521R1 (Rel-18, 'F'): Update to support reporting of satellite backhaul category change and clarification of satellite backhaul category change | China Telecom | Rel-18 | Revision of (unhandled) S2-2310853. Confirm CR Number - CR states 4521r1!. Confirm CR Revision - CR states 4521! Merged into S2-2401484 | Heng(China Telecom) provides revision and suggest merge with 0308 Haris(Qualcomm) comments Heng(China Telecom) provides a merged revision in 0308 thread. DongYeon (Samsung) agrees to merge 0703 into 0308. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 9.2.2 | - | - | - | Satellite access Phase 2 (5GSAT_Ph2) | - | - | Docs:=8 | - | |
| 9.2.2 | S2-2400050 | LS In | Information | LS from CT WG4: Reply LS on the need of the NR NTN TAI | CT WG4 (C4-235683) | Rel-18 | Noted | Noted | |
| 9.2.2 | S2-2400066 | LS In | Information | LS from RAN WG3: LS on OAM requirements for UE location verification | RAN WG3 (R3-238056) | Rel-18 | Noted | Noted | |
| 9.2.2 | S2-2400156 | CR | Approval | 23.501 CR5214 (Rel-18, 'F'): Correction for multiple broadcast TA reporting in NR Satellite access | Nokia, Nokia Shanghai Bell | Rel-18 | r05 Agreed. Revised to S2-2401486. | Steve (Huawei) checks the wording Chris (Vodafone) comments that it would be useful to indicate the TAI where the UE is located. Saubhagya (Nokia) responds to Steve (Huawei). Saubhagya (Nokia) replies to Vodafone Chris (Vodafone) provides r01. Saubhagya (Nokia) provides r02 with further fix Steve (Huawei) looking better Saubhagya (Nokia) provides r04 with editorial fixes Yuxin (Xiaomi) comments and provides r03 Chris (Vodafone) says that it is the 'UE's TAI AND the set', not 'UE's TAI or the set' Chris (Vodafone) provides r05. Steve (Huawei) comments on the filtering. Saubhagya (Nokia) OK with r05 ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 9.2.2 | S2-2401486 | CR | Approval | 23.501 CR5214R1 (Rel-18, 'F'): Correction for multiple broadcast TA reporting in NR Satellite access | Nokia, Nokia Shanghai Bell | Rel-18 | Revision of S2-2400156r05. Approved | Agreed | |
| 9.2.2 | S2-2400420 | CR | Approval | 23.501 CR5202R1 (Rel-18, 'F'): UE capability for network verified location | Qualcomm Incorporated | Rel-18 | Revision of (unhandled) S2-2313101. r01 + changes Agreed. Revised to S2-2401487. | Saubhagya (Nokia) provide comments. Haris(Qualcomm) responds Saubhagya (Nokia) comments. Steve (Huawei) comments. Haris(Qualcomm) provides r01 ==== Revisions Deadline ==== Saubhagya (Nokia) do not see the proposed change in r01 and asks to revise Wanqiang (Session Chair): please give a clear text change on top of r01, or else it will be noted. Haris(Qualcomm) proposes to discuss in CC Chris (Vodafone) says CR concept seems OK, but the link to 37.355 is not clear. But does not object. ==== Final Comments Deadline ==== Chris (Vodafone) thanks Haris (Qualcomm) and Saubhagya (Nokia) for the extra information. Perhaps we add the reference to 38.305 in the next meeting? | Revised |
| 9.2.2 | S2-2401487 | CR | Approval | 23.501 CR5202R2 (Rel-18, 'F'): UE capability for network verified location | Qualcomm Incorporated | Rel-18 | Revision of S2-2400420r01 + changes. Approved | Agreed | |
| 9.2.2 | S2-2401302 | CR | Approval | 23.501 CR5304 (Rel-18, 'F'): Clarification on unavailability period | Samsung | Rel-18 | r02 Agreed. Revised to S2-2401488. | Steve (Huawei) comments Chris (Vodafone) suggests an editorial improvement. Lalith(Samsung) provides r01 Steve (Huawei) comments on PPF Lalith (Samsung) provides r02 ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 9.2.2 | S2-2401488 | CR | Approval | 23.501 CR5304R1 (Rel-18, 'F'): Clarification on unavailability period | Samsung | Rel-18 | Revision of S2-2401302r02. Approved | Agreed | |
| 9.3.2 | - | - | - | Personal IoT Networks (5G_PIN) | - | - | Docs:=8 | - | |
| 9.3.2 | S2-2400654 | CR | Approval | 23.502 CR4308R2 (Rel-18, 'D'): Correction to procedure for PIN service | Nokia, Nokia Shanghai Bell | Rel-18 | Revision of (unhandled) S2-2312612. Merged into S2-2401489 | Jianning (XIAOMI) proposes to merge this paper into S2-2400945. Pallab (Nokia) is OK to merge into S2-2400945 ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 9.3.2 | S2-2400783 | CR | Approval | 23.502 CR4583R1 (Rel-18, 'F'): Clarification on procedure for PIN service | Huawei, HiSilicon | Rel-18 | Revision of (unhandled) S2-2312302. Approved | Jianning (XIAOMI) proposes to merge this paper into S2-2400945. Yishan (Huawei) does not agree S2-2400783 can be merged into S2-2400945. Marco(Huawei) the S2-2400945 is editorial while S2-2400783 is technical, therefore we disagree to merge and invite to comments S2-2400783 . ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Agreed |
| 9.3.2 | S2-2400941 | CR | Approval | 23.501 CR5192R1 (Rel-18, 'F'): Correction for terms for PIN | Xiaomi | Rel-18 | Revision of (unhandled) S2-2312993. Merged into S2-2401490 | Jianning (XIAOMI) response to Kenny (Qualcomm). Jianning (XIAOMI) is ok to merge into 1006. Zhenhua (vivo) propose to merge into S2-2401006. Kefeng (Qualcomm) provides comments. Zhenhua (vivo) already propose to merge into S2-2401006. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 9.3.2 | S2-2400945 | CR | Approval | 23.502 CR4649R1 (Rel-18, 'F'): Correction for terminologies | Xiaomi | Rel-18 | Revision of (unhandled) S2-2312991. r03 Agreed. Revised to S2-2401489, merging S2-2400654 | Jianning (XIAOMI) provides r01 by merging S2-2400654 and S2-2400783 Pallab (Nokia) provides comments on r01 Jianning (XIAOMI) replies to Pallab (Nokia). Pallab (Nokia) responds to Jianning (XIAOMI) and OK with r01 Jianning (XIAOMI) comments provides r02 by removing content of S2-2400783. Pallab (Nokia) is OK with r02 and confirms merging S2-2400654 and co-sign Jianning (XIAOMI) provides r03 by adding Nokia as source. Marco(Huawei) OK with R03 ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 9.3.2 | S2-2401489 | CR | Approval | 23.502 CR4649R2 (Rel-18, 'F'): Correction for terminologies | Xiaomi | Rel-18 | Revision of S2-2400945r03, merging S2-2400654. Approved | Agreed | |
| 9.3.2 | S2-2401006 | CR | Approval | 23.501 CR5182R1 (Rel-18, 'F'): Mega CR for editorial modification | Vivo | Rel-18 | Revision of (unhandled) S2-2312884. r04 Agreed. Revised to S2-2401490, merging S2-2400941 | Zhenhua (vivo) provides r01. Kefeng (Qualcomm) provides comments. Pallab (Nokia) provides comments Marco(Huawei) comments and provide r02 Zhenhua (vivo) provides r03 Marco(Huawei) ok with R03. Thanks Zhenhua Jianning (XIAOMI) is ok with r03, and happy to co-sign. Zhenhua (vivo) provides r04 to add co-signer. ==== Revisions Deadline ==== Marco(Huawei) ok with R04 and R03 . object to R00 & R01 ==== Final Comments Deadline ==== | Revised |
| 9.3.2 | S2-2401490 | CR | Approval | 23.501 CR5182R2 (Rel-18, 'F'): Mega CR for editorial modification | Vivo, Xiaomi | Rel-18 | Revision of S2-2401006r04, merging S2-2400941. Approved | Agreed | |
| 9.3.2 | S2-2401008 | CR | Approval | 23.501 CR5184R1 (Rel-18, 'F'): Clarification on AF influence of PIN-DN communication | Vivo | Rel-18 | Revision of (unhandled) S2-2312886. Noted | Zhenhua (vivo) provides r01. Kefeng (Qualcomm) is not OK with the added NOTE.. Marco(Huawei) have concern on R00 and 'based on operator policy' is obvious in AF influence, so propose to note the doc ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Noted |
| 9.4.2 | - | - | - | Phase 2 for UAS, UAV and UAM (UAS_Ph2) | - | - | Docs:=1 | - | |
| 9.4.2 | S2-2400063 | LS In | Action | LS from RAN WG3: LS on RAN WG3 progress for UAV flight path information handling and A2X service support | RAN WG3 (R3-238019) | Rel-18 | Noted | Stefano (Qualcomm) propose to note, no actions. | Noted |
| 9.5.2 | - | - | - | Ranging based services and sidelink positioning (Ranging_SL) | - | - | Docs:=83 | - | |
| 9.5.2 | - | - | - | LS In & LS Out from RAN WGs and related DP/CRs | - | - | Docs:=4 | - | |
| 9.5.2 | S2-2400056 | LS In | Action | LS from RAN WG2: Reply LS on RSPP metadata field in sidelink positioning discovery | RAN WG2 (R2-2313834) | Rel-18 | Noted | Sherry (Xiaomi) proposes to note this LS reply. | Noted |
| 9.5.2 | S2-2400060 | LS In | Information | LS from RAN WG3: LS on LMF involvement in SL-PRS resource allocation | RAN WG3 (R3-237860) | Rel-18 | Noted | Sherry (Xiaomi) proposes to note this LS reply. | Noted |
| 9.5.2 | S2-2400003 | LS In | Information | LS from RAN WG1: LS on the resource selection window for Scheme 2 in a dedicated resource pool for positioning | RAN WG1 (R1-2308651) | Rel-18 | Revision of Postponed S2-2311934 from SA WG2#160. Noted | Sherry (Xiaomi) proposes to note this LS. | Noted |
| 9.5.2 | S2-2400017 | LS In | Information | LS from RAN WG1: Reply LS on SL positioning MAC agreements | RAN WG1 (R1-2310402) | Rel-18 | Revision of Postponed S2-2311976 from SA WG2#160. Noted | Sherry (Xiaomi) proposes to note this LS reply. | Noted |
| 9.5.2 | - | - | - | LS In & LS Out from SA3 and related DP/CRs | - | - | Docs:=19 | - | |
| 9.5.2 | S2-2400025 | LS In | Information | LS from SA WG3: Reply LS on key and security materials used for Ranging_SL | SA WG3 (S3-235075) | Rel-18 | Revision of Postponed S2-2313234 from SA WG2#160. Noted | Sherry (Xiaomi) proposes to note this LS reply. | Noted |
| 9.5.2 | S2-2400027 | LS In | Action | LS from SA WG3: Reply LS on security aspects for Ranging/Sidelink Positioning | SA WG3 (S3-235078) | Rel-18 | Revision of Postponed S2-2313236 from SA WG2#160. Responses drafted in S2-2400115, S2-2400205, S2-2400998, S2-2401263. CC#4: Final response in S2-2401651. | Replied to | |
| 9.5.2 | S2-2400122 | LS OUT | Approval | [DRAFT] Reply LS on security aspects for Ranging/Sidelink Positioning | Sony | Rel-18 | Response to S2-2400027. CC#4: r12 + clean up agreed. Revised, merging S2-2400205, S2-2400998, S2-2401263, to S2-2401651. | Yaxin (OPPO) provides comments. Mehrdad (MediaTek Inc.) requests to adopt one LS reply as the baseline between S2-2400205, S2-2401263 and S2-2400122. Hong (Qualcomm) suggests using S2-2400122 as baseline, and merge S2-2400205 and S2-2401263 into it. Richard (Ericsson) supports to have one discussion thread here, and providing comment to this LS OUT Lars (Sony) I am ok to hold the pen on the LS out, and agree that the current answer1 in r00 is not correct. Lars (Sony) provides r01. Walter (Philips) provides comments. Jungje(Interdigital) comments Lars (Sony) responds to Walter Yaxin (OPPO) moves some discussion content from S2-2401263. OPPO can live with option 1 or option 4. Dario (session chair): let's keep the discussion on this thread (S2-2400122). Sherry (Xiaomi) comments and provides the slides for CC#2. Richard (Ericsson) provides comments to the slides for CC#2. Richard (Ericsson) provides comments to the slides for CC#2 and provides a revision. Lars (Sony) provides comments to the slides for CC#2 and provides a revision (NOT Ericsson). Mehrdad (MediaTek Inc.) asks clarification on options covered in the slide for SoH versus what suggested in this thread Sherry (Xiaomi) provides an update to the show of hands slides. Yaxin (OPPO) replies to clarify option 4 has related CR. Richard (Ericsson) replies to Sherry (Xiaomi) Sherry (Xiaomi) provides R03 of the CC#2 slides. Lars (Sony) provides update on R03. Richard (Ericsson) raises question toward option 4. Yaxin (OPPO) replies to Richard. Sherry (Xiaomi) comments. Yaxin (OPPO) clarify that the option 4 related tdoc number should be S2-2400999. Lars (Sony) responds to Sherry (Xiaomi) Lars (Sony) provides S2-2401373 Walter (Philips) requests clarification to Lars (Sony) on S2-2401373 ==== Revisions Deadline ==== Lars (Sony) provides r02 Richard (Ericsson) generally fine with r02, one comment added Lars (Sony is not ok with r03 ==== Final Comments Deadline ==== Jungje(Interdigital) provides r04 Lars (Sony) provides r05 Yaxin (OPPO) comments and propose to remove the yellow highlighted part in A1. Sherry (Xiaomi) provides comment and r06 Richard (Ericsson) provides comment to remove one sentence. Walter (Philips) provides r07 Lars (Sony) think r07 is a good direction Richard (Ericsson) provides r08 Lars (Sony) comments on r08 and is not ok Sherry (Xiaomi) provides comments and r09 Lars (Sony) provides r10 and r11 Lars (Sony) provides 12 Sherry (Xiaomi) is fine with r12. Lars (Sony) would prefer r11 which is more elaborative than r12 (bare minimum). Yaxin (OPPO) is OK with r12. Richard (Ericsson) accepts r12 Walter (Philips) provides r13 | Revised |
| 9.5.2 | S2-2401651 | LS OUT | Approval | Reply LS on security aspects for Ranging/Sidelink Positioning | SA WG2 | Rel-18 | Revision of S2-2400122r12 + clean up, merging S2-2400205, S2-2400998, S2-2401263. Approved | Approved | |
| 9.5.2 | S2-2400205 | LS OUT | Approval | [DRAFT] Reply LS on security aspects for Ranging/Sidelink Positioning | Ericsson | Rel-18 | Merge into S2-2400122 (For CC#4) Response to S2-2400027. CC#4: Merged into S2-2401651. | Yaxin (OPPO) provides comments. Lars (Sony) provides comments. Richard (Ericsson) answers to Lars and Yaxin Mehrdad (MediaTek Inc.) requests to adopt one LS reply as the baseline between S2-2400205, S2-2401263 and S2-2400122 Hong (Qualcomm) suggests using S2-2400122 as baseline, and merge S2-2400205 and S2-2401263 into it. Jungje(Interdigital) provides comments. Dario (session chair): proposes to merge this into 1022 to move the discussion to that thread. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 9.5.2 | S2-2400998 | LS OUT | Approval | [DRAFT] Reply LS to Reply LS on security aspects for RangingSidelink Positioning | OPPO | Rel-18 | Merge into S2-2400122 (For CC#4) Response to S2-2400027. CC#4: Merged into S2-2401651. | Dario (session chair): proposes to merge this into 1022 to move the discussion to that thread. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 9.5.2 | S2-2401263 | LS OUT | Approval | [DRAFT] Reply LS on Reply LS on security aspects for Ranging/Sidelink Positioning | Xiaomi | Rel-18 | Merge into S2-2400122 (For CC#4) Response to S2-2400027. CC#4: Merged into S2-2401651. | Yaxin (OPPO) provides comments. Sherry (Xiaomi) replies to Yaxin. Yaxin (OPPO) comments. Mehrdad (MediaTek Inc.) requests to adopt one LS reply as the baseline between S2-2400205, S2-2401263 and S2-2400122 Jungje(Interdigital) comments. Hong (Qualcomm) suggests using S2-2400122 as baseline, and merge S2-2400205 and S2-2401263 into it. Yaxin (OPPO) summarize the alternatives and suggests using S2-2401263 as baseline, additionally merge S2-2400122, S2-2400205 and S2-2400998. Richard (Ericsson) supports option 3 Sherry (Xiaomi) replies. Hong (Qualcomm) supports option 3. Wen(vivo) supports option 3 Dario (session chair): proposes to merge this into 1022 to move the discussion to that thread. Jungje(Interdigital) supports option 3 ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 9.5.2 | S2-2400206 | CR | Approval | 23.586 CR0095 (Rel-18, 'F'): Adding info of SL Positioning Client UE in the SL-MO-LR request in case of service exposure through PC5. | Ericsson | Rel-18 | Noted | Yaxin (OPPO) provides comments. Richard (Ericsson) provides comments Wen (vivo) provides comments Lars (Sony) provides comments Richard (Ericsson) answers to Wen (Vivo) Lars (Sony) comments on Richards (Ericsson) response Walter (Philips) comments to Lars (Sony) Lars (Sony) responds to Walter (Philips). Wen (vivo) comments. Mehrdad (MediaTek Inc.) provides comment Wen(vivo) comments Jungje(Interdigital) comments Hong (Qualcomm) comments and agrees with Lars (Sony). Jungje comments Walter (Philips) provides comments Richard (Ericsson) answers to Mehrdad (MediaTek Inc.) Sherry (Xiaomi) comments Walter (Philips) requests additional clarification Lars (Sony responds to Sherry (Xiaomi) comments Hong (Qualcomm) comments and agrees with Lars. Walter (Philips) responds to comments Yaxin (OPPO) mentions some privacy check aspects. Jungje(Interdigital) responds to Walter(Philips) Richard (Ericsson) paper can be noted based on decision on CC#2 ==== Revisions Deadline ==== | Noted |
| 9.5.2 | S2-2400207 | CR | Approval | 23.273 CR0487 (Rel-18, 'F'): Adding info of SL Positioning Client UE in the SL-MO-LR request in case of service exposure through PC5. | Ericsson | Rel-18 | Noted | Yaxin (OPPO) provides comments. Lars (Sony) provides comments Richard (Ericsson) answers to Lars (Sony) Lars (Sony) responds to Richard (Ericsson) Richard (Ericsson) responds to Lars (Sony) Sherry (Xiaomi) comments Richard (Ericsson) paper can be noted based on decision on CC#2 ==== Revisions Deadline ==== | Noted |
| 9.5.2 | S2-2401373 | CR | Approval | 23.586 CR0119 (Rel-18, 'F'): Update service exposure to SL Positioning Client UE through PC5 | Sony, Ericsson?, Qualcomm Incorporated?, Vivo?, Interdigital, Philips?, MediaTek | Rel-18 | Created in CC#2. Confirm Sources! CC#3: Postponed | Lars (Sony) provides S2-2401373 Lars (Sony) provides r01 Yaxin (OPPO) provides comments. Lars (Sony) responds to Yaxin (OPPO) Yaxin (OPPO) replies to Lars (Sony). Walter (Philips) provides comments. Lars (Sony) responds to Walter (Philips). Yaxin (OPPO) replies to Walter and Lars. Lars (Sony) responds to Yaxin (OPPO). Jungje(Interdigital) responds to Yaxin(OPPO) Richard (Ericsson) provides r02 Lars (Sony) provides r03 Sherry (Xiaomi) comments. Lars (Sony) comments. Hong (Qualcomm) comments on r03. Lars (Sony) responds to Hong. Lars (Sony) provides r04. ==== Revisions Deadline ==== Hong (Qualcomm) is fine with r04. Objects r00 to r03. LiMeng (Huawei) r04 is generally OK to us, some minor issues can be addressed later. Richard (Ericsson) is fine with r04. Lars (Sony) agree with LiMeng to remove 'its own' from step 7b. Sherry (Xiaomi) provides comments Lars (Sony) responds to Xiaomi. Lars (Sony) provides a new draft. Hong (Qualcomm) comments. Jungje(Interdigital) replies to Sherry (Xiaomi) Lars (Sony) propose to agree on r04 + the following changes. In clause 5.6.2.2 delete third bullet. In clause 6.7.1.1 Step 2 add 'The SL Positioning Client UE authorization check is performed during PC5 connection establishment as specified in TS 33.533 [13].' Delete step 5a and b Step 6 delete 'UE1 and UE2 share their privacy verification result.' and change ' If the privacy result was negative...' to ' . If the privacy result was negative in any of UE1 and/or UE2...' Step 7. Delete ' for requesting its own location information' + Update figure 6.7.1-1 to the new step numbering. Sherry (Xiaomi) replies. Yaxin (OPPO) shares the same view with Sherry(Xiaomi) Hong (Qualcomm) comments and fine to POSTPONE. Dario (Session Chair): postponed as discussed in CC#3 | Postponed |
| 9.5.2 | S2-2401257 | DISCUSSION | Approval | Discussion about down scoping of Ranging/SL Positioning service exposure to SL Positioning Client UE through PC5. | Xiaomi | Rel-18 | Noted | Noted | |
| 9.5.2 | S2-2401258 | CR | Approval | 23.586 CR0113 (Rel-18, 'F'): Updates to Ranging/SL Positioning service exposure through PC5 | Xiaomi | Rel-18 | CC#3: Postponed | Jungje(Interdigital) provides comments. Lars (Sony) comments. Hong (Qualcomm) comments. Lars (Sony) responds to Hong (Qualcomm). Hong (Qualcomm) replies to Lars. Sherry (Xiaomi) replies. Lasr (Sony) responds to Sherry (Xiaomi). Hong (Qualcomm) replies to Sherry. ==== Revisions Deadline ==== Jungje(Interdigital) comments and suggest to remove proposed changes in clause 6.7.1.1 except step 5, 6, and 7. Hong (Qualcomm) comments and suggest remove newly proposed NOTE 2 from clause 5.6.2.2. Walter (Philips) objects to this CR. Dario (Session Chair): postponed as discussed in CC#3 | Postponed |
| 9.5.2 | S2-2400117 | CR | Approval | 23.586 CR0046R2 (Rel-18, 'F'): Update service exposure via control plane. | Sony | Rel-18 | Revision of (unhandled) S2-2312313. r05 + changes Agreed. Revised to S2-2401378. | Yaxin (OPPO) provides comments. Lars (Sony) provides r01. Sherry (Xiaomi) provides r02. Lars (Sony) responds to Sherry (Xiaomi) and do not agree on r02. Walter (Philips) also does not agree r02, and provides r03 based on r01. Lars (Sony) thanks Walter (Philips) for r03, it looks good. Sherry (Xiaomi) comments. Lars (Sony) provides r04. Sherry (Xiaomi) provides response and suggests revision. Lars (Sony) don't agree with Sherry (Xiaomi) but provides r05. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 9.5.2 | S2-2401378 | CR | Approval | 23.586 CR0046R3 (Rel-18, 'F'): Update service exposure via control plane. | Sony | Rel-18 | Revision of S2-2400117r05 + changes. Approved | Agreed | |
| 9.5.2 | S2-2400119 | CR | Approval | 23.586 CR0077R1 (Rel-18, 'F'): Add missing Ranging/SL Positioning security description | Sony | Rel-18 | Revision of (unhandled) S2-2312332. Approved | Agreed | |
| 9.5.2 | S2-2400120 | CR | Approval | 23.273 CR0466R1 (Rel-18, 'F'): LCS UE Privacy profile updated with a list of allowed UE(s) | Sony | Rel-18 | Revision of (unhandled) S2-2312322. Approved | Jungje(Interdigital) supports this CR. Richard (Ericsson) provides comments Lars (Sony) responds to Richard (Ericsson) Hong (Qualcomm) comments. Lars (Sony) responds to Hong (Qualcomm). Richard (Ericsson) provides additional comments ==== Revisions Deadline ==== Richard (Ericsson) we would need to document at least on the next meeting that SL Positioning Client UE is applicable only for ranging operations. ==== Final Comments Deadline ==== | Agreed |
| 9.5.2 | S2-2401355 | CR | Approval | 23.273 CR0503 (Rel-18, 'F'): Privacy check between LMF and GMLC | Philips International B.V. | Rel-18 | Postponed | Yaxin (OPPO) provides comments. Hong (Qualcomm) comments and agrees with Yanxin's suggestion to focus on Sony paper S2-2400120 for discussion. Walter (Philips) responds to Yaxin (OPPO) and Hong (Qualcomm) Lars (Sony) comments on this new Privacy Checking Walter (Philips) responds to Lars (Sony) Lars (Sony) confirms Walter (Philips) understanding of option B Hong (Qualcomm) proposes to POSTPONE the CR. Hong (Qualcomm) comments. Walter (Philips) responds to Hong. Sherry (Xiaomi) comments. ==== Revisions Deadline ==== Hong (Qualcomm) objects all revision of the CR, and suggests POSTPONE the discussion. ==== Final Comments Deadline ==== | Postponed |
| 9.5.2 | S2-2401359 | CR | Approval | 23.586 CR0016R3 (Rel-18, 'F'): Clarify message request to AMF in case of Exposure though 5GC network via control plane | Xiaomi | Rel-18 | Revision of (unhandled) S2-2312470. Postponed | Yaxin (OPPO) provides comments. Richard (Ericsson) provides comments to Sherry and Yaxin Lars (Sony) proposes to use S2-2400117 to update clause 6.7.1.2.3. Can this tdoc be marked as merged? Richard (Ericsson) says this paper is connected to 2400996. We shall analyze 2401359 and 2400996 together before any merging. Wen (vivo) provides comment Sherry (Xiaomi) provides r01 Richard (Ericsson) answers to Wen (vivo) Lars (Sony) responds to Sherry Richard (Ericsson) provides r02 ==== Revisions Deadline ==== Sherry (Xiaomi) objects r02, agrees with r01. Richard (Ericsson) proposes to postpone the CR ==== Final Comments Deadline ==== Sherry (Xiaomi) replies to Richard. Richard (Ericsson) offers to accept r01 Sherry (Xiaomi) requests to discuss it on CC#4. | Postponed |
| 9.5.2 | S2-2400999 | CR | Approval | 23.586 CR0110 (Rel-18, 'F'): Update about privacy check | OPPO | Rel-18 | Noted | Yaxin (OPPO) provides r01. Jungje(Interdigital) comments Lars (Sony) propose to merge this CR into S2-2400117. Yaxin (OPPO) wants to keep this CR open since it is an alternative option. Lars (Sony) responds and provide r02. Yaxin (OPPO) this tdoc can be noted according to CC#2. ==== Revisions Deadline ==== | Noted |
| 9.5.2 | - | - | - | Updates to Ranging/Sidelink Positioning procedures defined in TS 23.273 | - | - | Docs:=8 | - | |
| 9.5.2 | S2-2400208 | CR | Approval | 23.273 CR0488 (Rel-18, 'F'): Adding SLPP using between target UE and LMF | Ericsson | Rel-18 | Merged into S2-2401379 | Richard (Ericsson) this can be merged into 2401366 ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 9.5.2 | S2-2400852 | CR | Approval | 23.273 CR0492 (Rel-18, 'F'): Updates to SL-MO-LR and SL-MT-LR | Vivo | Rel-18 | Merged into S2-2401379 | Wen (vivo) : this paper is merged into S2-2401366. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 9.5.2 | S2-2400990 | CR | Approval | 23.273 CR0493 (Rel-18, 'F'): Prioritizing direct LMF Connection over Sidelink Communication for in coverage UEs in SL-MO-LR | CEWiT, Reliance Jio | Rel-18 | Noted | Richard Baorfi (Ericsson) provides comments Yaxin (OPPO) provides comments. Hong (Qualcomm) comments and suggest to NOTE. Lars (Sony) objects to this CR as this is not maintenance/alignment and the topic has been discussed and agreed not to pursue. ==== Revisions Deadline ==== Lars (Sony) objects to this CR. Richard (Ericsson) proposes to Note the paper Jishnu (CEWiT) replies and agrees to note. ==== Final Comments Deadline ==== | Noted |
| 9.5.2 | S2-2401132 | CR | Approval | 23.273 CR0497 (Rel-18, 'F'): Update in SL-MO-LR procedure for supplementary RSPP signalling message | InterDigital | Rel-18 | Noted | Jungje(Interdigital) responded to Walter (Philips) Walter (Philips) requests clarification. Walter (Philips) provides comments. Wen (vivo) provides comments. Jungje(Interdigital) response to Wen(vivo) ==== Revisions Deadline ==== | Noted |
| 9.5.2 | S2-2401366 | CR | Approval | 23.273 CR0504 (Rel-18, 'F'): Corrections of usage of SLPP and supplementary service messages for Ranging_SL procedures | Qualcomm Incorporated | Rel-18 | r07 Agreed. Revised to S2-2401379, merging S2-2400208 and S2-2400852 | Yaxin (OPPO) provides comments. Sherry (Xiaomi) provides r01. Wen (vivo) comments on r02. Hong (Qualcomm) comments on r02. Wen (vivo) provides r02. Hong (Qualcomm) replies to Yaxin (OPPO) and thinks the comments was for S2-2401369, not for this thread. Lars (Sony) comments and provides r03 Richard (Ericsson) 2400208 also can be merged into 2401366 Walter (Philips) provides comments and proposes a merge Hong (Qualcomm) provides r04. Hong (Qualcomm) provides r05. Walter (Philips) thanks Hong (Qualcomm) for addressing comments. Hong (Qualcomm) provides r06. Sherry (Xiaomi) provides r07. ==== Revisions Deadline ==== Hong (Qualcomm) is fine with r07. Richard (Ericsson) supports r07 and would cosign it. Lars (Sony) is fine with r07. ==== Final Comments Deadline ==== | Revised |
| 9.5.2 | S2-2401379 | CR | Approval | 23.273 CR0504R1 (Rel-18, 'F'): Corrections of usage of SLPP and supplementary service messages for Ranging_SL procedures | Qualcomm Incorporated, vivo, Xiaomi | Rel-18 | Revision of S2-2401366r07, merging S2-2400208 and S2-2400852. Approved | Agreed | |
| 9.5.2 | S2-2401368 | CR | Approval | 23.273 CR0505 (Rel-18, 'F'): Corrections to SL-MT-LR procedure | Philips International B.V. | Rel-18 | r02 Agreed. Revised to S2-2401380. | Lars (Sony) comment that this CR is not needed. Walter (Philips) responds to comments from Lars (Sony). Lars (Sony) is ok with this CR as explain by Walter (Philips). Hong (Qualcomm) comments and thinks the overlapping changes with S2-2401366 <https://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_160AHE_Electronic_2024-01/Docs/S2-2401366.zip> should be avoided. Sherry (Xiaomi) comments. Hong (Qualcomm) comments. Walter (Philips) provides r01, removing the changes to step 16 which have been merged into 1366 Walter (Philips) responds to comments from Sherry (Xiaomi) and Hong (Qualcomm) Sherry (Xiaomi) responds to Walter. Walter (Philips) responds to Sherry (Xiaomi). Richard (Ericsson) provides comment Walter (Philips) provides r02 ==== Revisions Deadline ==== Richard (Ericsson) asnwers to Walter (Philips) ==== Final Comments Deadline ==== | Revised |
| 9.5.2 | S2-2401380 | CR | Approval | 23.273 CR0505R1 (Rel-18, 'F'): Corrections to SL-MT-LR procedure | Philips International B.V. | Rel-18 | Revision of S2-2401368r02. Approved | Agreed | |
| 9.5.2 | - | - | - | UE role related | - | - | Docs:=4 | - | |
| 9.5.2 | S2-2400826 | CR | Approval | 23.586 CR0087R1 (Rel-18, 'F'): Ranging capability and subscription | Vivo | Rel-18 | Revision of (unhandled) S2-2312682. r03 + changes Agreed. Revised to S2-2401381. | Hong (Qualcomm) provides r01. Wen (vivo) is ok with r01. Sherry (Xiaomi) comments. Wen (vivo) provide r02. Wen (vivo) provide r03. Hong (Qualcomm) replies to Sherry. ==== Revisions Deadline ==== Wen (vivo) thanks Hong's correction and announces that r03+removing duplicate Client UE subscription in 5.8 are correct. Hong (Qualcomm) comments that r03 has introduced an overlapping bullet on Client UE subscription in 5.8 and it should be removed. ==== Final Comments Deadline ==== | Revised |
| 9.5.2 | S2-2401381 | CR | Approval | 23.586 CR0087R2 (Rel-18, 'F'): Ranging capability and subscription | Vivo | Rel-18 | Revision of S2-2400826r03 + changes. Approved | Agreed | |
| 9.5.2 | S2-2400620 | CR | Approval | 23.586 CR0103 (Rel-18, 'F'): Update on Policy/Parameter and scheduled location time | Huawei, HiSilicon | Rel-18 | r02 Agreed. Revised to S2-2401382. | LiMeng (Huawei) provides r01. Hong (Qualcomm) comments on r01. LiMeng (Huawei) provides r02. Sherry (Xiaomi) not agree with the removal of Target/Reference UE and provides reason Hong (Qualcomm) replies to Xiaomi. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 9.5.2 | S2-2401382 | CR | Approval | 23.586 CR0103R1 (Rel-18, 'F'): Update on Policy/Parameter and scheduled location time | Huawei, HiSilicon | Rel-18 | Revision of S2-2400620r02. Approved | Agreed | |
| 9.5.2 | - | - | - | Protocol Stack | - | - | Docs:=1 | - | |
| 9.5.2 | S2-2400516 | CR | Approval | 23.586 CR0100 (Rel-18, 'F'): Protocol stack for RSPP transport | CATT | Rel-18 | Approved | Agreed | |
| 9.5.2 | - | - | - | UE discovery & selection | - | - | Docs:=10 | - | |
| 9.5.2 | S2-2400494 | CR | Approval | 23.586 CR0099 (Rel-18, 'F'): Clarification on the coverage condition in the UE discovery and selection | ZTE | Rel-18 | Postponed | zhendong (ZTE) proposes to discuss in/out-coverage in this thread Yaxin (OPPO) provides questions on this issue. Wen(vivo) provides comments. Jungje(Interdigital) provides comments. zhendong (ZTE) provides response to hong (Qualcomm) Hong (Qualcomm) comments. zhendong (ZTE) provides the r01 ==== Revisions Deadline ==== Hong (Qualcomm) objects all revision of the CR, and proposes to POSTPONE as there is an LS Out related to this topic. ==== Final Comments Deadline ==== | Postponed |
| 9.5.2 | S2-2400495 | LS OUT | Approval | [DRAFT] LS on coverage condition during Ranging/Sidelink Positioning UE Discovery & Selection | ZTE | Rel-18 | r09 + changes Agreed. Revised to S2-2401383. | Wen (vivo) comments. zhendong (ZTE) provides the response Wen (vivo)replies zhendong (ZTE) provides the r01 Lars (Sony) provides the r02 Yaxin (OPPO) provides r03. Lars (Sony) comments on r03. Wen (vivo) comments on r03. Richard (Ericsson) provides comment Yaxin (OPPO) replies to Lars and Wen. Wen (vivo) replies. Yaxin (OPPO) replies to Wen. zhendong (ZTE) provides the r04 zhendong (ZTE) provides the r05 Lars (Sony) provides the r06 Sherry (Xiaomi) provides r06. Sherry (Xiaomi) provides r07. ==== Revisions Deadline ==== Hong (Qualcomm) comments. Hong (Qualcomm) provides r08. Richard (Ericsson) prefers r08. Walter (Philips) provides r09 Lars (Sony) is ok with r09 zhendong (ZTE) is fine with r09 Yaxin (OPPO) is Ok with r09. Richard (Ericsson) is Ok with r09. Hong (Qualcomm) comments that the 'people' in following sentence should be changed to 'companies' as suggested by the session chair: 'During SA2 discussion, people are not sure whether the solutions in clause 6.20 of 23.273 also work in some of the partial coverage scenario' ==== Final Comments Deadline ==== | Revised |
| 9.5.2 | S2-2401383 | LS OUT | Approval | LS on coverage condition during Ranging/Sidelink Positioning UE Discovery & Selection | SA WG2 | Rel-18 | Revision of S2-2400495r09 + changes. Approved | Approved | |
| 9.5.2 | S2-2400617 | CR | Approval | 23.586 CR0101 (Rel-18, 'F'): Update on Located UE Discovery and Selection | Huawei, HiSilicon | Rel-18 | r06 Agreed. Revised to S2-2401384. | Yaxin (OPPO) provides comments. LiMeng (Huawei) provides r01. Yaxin (OPPO) asks for clarification. Hong (Qualcomm) comments, and don't think in-coverage indication is needed. Jungje(Interdigital) provides comments LiMeng (Huawei) responds and provides r02. Walter (Philips) comments on step 2 of 6.8. LiMeng (Huawei) provides r03. Hong (Qualcomm) comments. Walter (Philips) provides comments. LiMeng (Huawei) provides r04 and responds to Hong (Qualcomm) and Walter (Philips). Walter (Philips) provides a few additional comments. LiMeng (Huawei) provides r05. Walter (Philips) provides r06. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 9.5.2 | S2-2401384 | CR | Approval | 23.586 CR0101R1 (Rel-18, 'F'): Update on Located UE Discovery and Selection | Huawei, HiSilicon | Rel-18 | Revision of S2-2400617r06. Approved | Agreed | |
| 9.5.2 | S2-2400829 | CR | Approval | 23.586 CR0106 (Rel-18, 'F'): EN remove for the indication for capability exchange | Vivo | Rel-18 | r03 Agreed. Revised to S2-2401385. | zhendong (ZTE) provides the comments Wen (vivo) responds to zhendong (ZTE) zhendong (ZTE) provides the response Hong (Qualcomm) comments, and agree that PLMN ID is only needed for Located UE discovery. Jungje(Interdigital) provides the comments Wen (vivo) provides r01. Walter (Philips) comments on r01 Wen (vivo) provides r02 Walter (Philips) provides r03 Wen (vivo) replies Jungje (interdigital) commented Jungje(Interdigital) responds to Wen(vivo) ==== Revisions Deadline ==== Jungje(Interdigital) prefer R03 and oppose to R02 ==== Final Comments Deadline ==== | Revised |
| 9.5.2 | S2-2401385 | CR | Approval | 23.586 CR0106R1 (Rel-18, 'F'): EN remove for the indication for capability exchange | Vivo | Rel-18 | Revision of S2-2400829r03. Approved | Agreed | |
| 9.5.2 | S2-2401141 | CR | Approval | 23.586 CR0112 (Rel-18, 'F'): Update in the UE discovery and selection | InterDigital | Rel-18 | r03 + changes Agreed. Revised to S2-2401386. | LiMeng (Huawei) agrees with Hong (Qualcomm) Hong (Qualcomm) comments. Jungje(Interdigital) provides r01 Jungje(Interdigital) responded to Limeng(Huawei) and Hong(Qualcomm) and uploaded r02 Jungje(Interdigital) responded to Walter(Philips) and uploaded r03 Walter (Philips) provides comment. ==== Revisions Deadline ==== Jungje(Interdigital) uploaded r04 ==== Final Comments Deadline ==== | Revised |
| 9.5.2 | S2-2401386 | CR | Approval | 23.586 CR0112R1 (Rel-18, 'F'): Update in the UE discovery and selection | InterDigital | Rel-18 | Revision of S2-2401141r03 + changes. Approved | Agreed | |
| 9.5.2 | S2-2401369 | CR | Approval | 23.586 CR0118 (Rel-18, 'F'): Updates to Located UE discovery | Philips International B.V. | Rel-18 | Postponed | Hong (Qualcomm) comments and doesn't think there should be differentiated 'willingness'. Jungje(Interdigital) comments Wen (vivo) comments. Yaxin (OPPO) doesn't think privacy related parameter should be included in discovery message. Lars (Sony) share the same view as Wen( Vivo) no need for this new indication. Walter (Philips) responds to comments. Hong (Qualcomm) comments. ==== Revisions Deadline ==== Lars (Sony) propose to postpone. Yaxin (OPPO) propose to postpone. ==== Final Comments Deadline ==== | Postponed |
| 9.5.2 | - | - | - | UE ID related | - | - | Docs:=14 | - | |
| 9.5.2 | S2-2400201 | CR | Approval | 23.586 CR0055R2 (Rel-18, 'F'): Correction/clarification to AF provisioning service parameters for Ranging/SL Positioning | Ericsson | Rel-18 | Revision of (unhandled) S2-2312472. Approved | Agreed | |
| 9.5.2 | S2-2400202 | DISCUSSION | Discussion | Handling ID translation and privacy check in case of UEs belong to different PLMNs . | Ericsson | Rel-18 | Revision of (unhandled) S2-2312473. Noted | Noted | |
| 9.5.2 | S2-2400203 | CR | Approval | 23.586 CR0056R2 (Rel-18, 'F'): Handling ID translation and privacy check in case of UEs belong to different PLMNs | Ericsson | Rel-18 | Revision of (unhandled) S2-2312474. Approved | Agreed | |
| 9.5.2 | S2-2400204 | CR | Approval | 23.273 CR0450R2 (Rel-18, 'F'): Handling ID Translation and privacy check in case of UEs belong to different PLMNs | Ericsson | Rel-18 | Revision of (unhandled) S2-2312475. r02 Agreed. Revised to S2-2401387. | Sherry(Xiaomi) provides comments. Sherry(Xiaomi) provides r01. Richard (Ericsson) replies to Sherry(Xiaomi) Richard (Ericsson) provides r02 ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 9.5.2 | S2-2401387 | CR | Approval | 23.273 CR0450R3 (Rel-18, 'F'): Handling ID Translation and privacy check in case of UEs belong to different PLMNs | Ericsson | Rel-18 | Revision of S2-2400204r02. Approved | Agreed | |
| 9.5.2 | S2-2400993 | DISCUSSION | Agreement | Discussion on usage of GPSI and SUPI in SL-MT-LR involving LMF. | OPPO | Rel-18 | Revision of (unhandled) S2-2312903. Noted | Noted | |
| 9.5.2 | S2-2400994 | CR | Approval | 23.273 CR0443R2 (Rel-18, 'F'): Update about the usage of SUPI in SL-MT-LR | OPPO | Rel-18 | Revision of (unhandled) S2-2312904. r01 + changes Agreed. Revised to S2-2401388. | Richard (Ericsson) provides comments Yaxin (OPPO) provides r01 and replies. ==== Revisions Deadline ==== Yaxin (OPPO) replies to Hong. Hong (Qualcomm) comments. Dario (session chair): on cover page replace dependency on 'TS 23.586 CR 0044' (S2-2400995) with 'TS 23.586 CR 0066' (S2-2401127) Richard (Ericsson) accepts r01 ==== Final Comments Deadline ==== | Revised |
| 9.5.2 | S2-2401388 | CR | Approval | 23.273 CR0443R3 (Rel-18, 'F'): Update about the usage of SUPI in SL-MT-LR | OPPO | Rel-18 | Revision of S2-2400994r01 + changes. Approved | Agreed | |
| 9.5.2 | S2-2400995 | CR | Approval | 23.586 CR0044R2 (Rel-18, 'F'): Update about mapping between application layer ID and SUPI | OPPO | Rel-18 | Revision of (unhandled) S2-2312905. Merged into S2-2401390 | Richard (Ericsson) provides comments Yaxin (OPPO) replies to Richard. Richard (Ericsson) replies to Yaxin (OPPO) Yaxin (OPPO) suggest to merge this to S2-2401127. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 9.5.2 | S2-2400997 | CR | Approval | 23.586 CR0109 (Rel-18, 'F'): Update about the usage of application layer ID | OPPO | Rel-18 | r01 Agreed. Revised to S2-2401389. | Dario (session chair): in the cover page, 5.5.2 should be added to 'clause affected'. Yaxin (OPPO) provides r01 to fix the cover sheet. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 9.5.2 | S2-2401389 | CR | Approval | 23.586 CR0109R1 (Rel-18, 'F'): Update about the usage of application layer ID | OPPO | Rel-18 | Revision of S2-2400997r01. Approved | Agreed | |
| 9.5.2 | S2-2401127 | CR | Approval | 23.586 CR0066R2 (Rel-18, 'F'): Update on Application layer ID resolution | Interdigital | Rel-18 | Revision of (unhandled) S2-2312049. r02 + changes Agreed. Revised to S2-2401390, merging S2-2400995 | Dario (session chair): the text of some of the new notes uses 'may' (which is normative). Use instead 'can'. Richard (Ericsson) provides comments Jungje(Interdigital) responded to Richard(Ericsson) and uploaded r01 Yaxin (OPPO) merges S2-2400995 to this CR and cosign. Lars (Sony) provides r02. Jungje(Interdigital) responds to Yaxin(OPPO) ==== Revisions Deadline ==== Jungje(Interdigital) uploaded r04 Jungje(Interdigital) uploaded r03 Dario (session chair): the text in the new last note uses 'may' (which is normative). Use instead 'can'. Lars (Sony) propose to approve r02 + fixing cover page issues Jungje(Interdigital) replies to Lars(Sony) Jungje(Interdigital) propose to approve r02 + fixing cover page issues + change 'may' to 'can' in NOTEs + add 'OPPO' as cosigner. ==== Final Comments Deadline ==== | Revised |
| 9.5.2 | S2-2401390 | CR | Approval | 23.586 CR0066R3 (Rel-18, 'F'): Update on Application layer ID resolution | Interdigital, OPPO | Rel-18 | Revision of S2-2401127r02 + changes, merging S2-2400995. Approved | Agreed | |
| 9.5.2 | S2-2401351 | CR | Approval | 23.586 CR0117 (Rel-18, 'F'): Clarification of Ranging/SL Positioning Application Identifier | Philips International B.V. | Rel-18 | Postponed | Hong (Qualcomm) comments and suggests NOTING the paper. Hong (Qualcomm) replies to Walter and comments on r01. Walter (Philips) provides r01 and requests clarification from Hong. Walter (Philips) provides r02. ==== Revisions Deadline ==== Hong (Qualcomm) objects r00 to r02 of the CR, and suggests POSTPONE. ==== Final Comments Deadline ==== | Postponed |
| 9.5.2 | - | - | - | Others | - | - | Docs:=22 | - | |
| 9.5.2 | S2-2400118 | CR | Approval | 23.586 CR0078R1 (Rel-18, 'F'): Update parameter provisioning | Sony | Rel-18 | Revision of (unhandled) S2-2312334. Approved | Agreed | |
| 9.5.2 | S2-2400491 | CR | Approval | 23.586 CR0096 (Rel-18, 'F'): Clarification on the term and functionality | ZTE | Rel-18 | Approved | Agreed | |
| 9.5.2 | S2-2400492 | CR | Approval | 23.586 CR0097 (Rel-18, 'F'): Modification to the Registration description | ZTE | Rel-18 | r01 Agreed. Revised to S2-2401391. | Dario (session chair): the note in 5.2.3 uses 'may' instead 'can'. Please fix it. zhendong (ZTE) provides the r01 ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 9.5.2 | S2-2401391 | CR | Approval | 23.586 CR0097R1 (Rel-18, 'F'): Modification to the Registration description | ZTE | Rel-18 | Revision of S2-2400492r01. Approved | Agreed | |
| 9.5.2 | S2-2400493 | CR | Approval | 23.586 CR0098 (Rel-18, 'F'): Correction on the Partial coverage and SL Positioning Server UE description | ZTE | Rel-18 | Postponed | Yaxin (OPPO) provides comments. Richard (Ericsson) provides comments Wen (vivo) provides comments Jungje(Interdigital) comments Lars (Sony) agree with Ericsson comment. Is this CR needed? zhendong (ZTE) provides the r01 Wen (vivo) comments zhendong (ZTE) provides the response Wen (vivo) comments r01 Yaxin (OPPO) provides information about RAN2 coordination. Lars (Sony) responds Wen (vivo) comments. Yaxin (OPPO) replies to Wen and Lars. ==== Revisions Deadline ==== Richard (Ericsson) proposes to note the paper zhendong (ZTE) proposes to postpone this CR. ==== Final Comments Deadline ==== | Postponed |
| 9.5.2 | S2-2401259 | CR | Approval | 23.586 CR0114 (Rel-18, 'F'): Corrections for alignments to TS 23.273/TS 23.586/SA WG3/RAN WGs | Xiaomi | Rel-18 | r05 + changes Agreed. Revised to S2-2401392. | Yaxin (OPPO) comments about the absolute location in SL-MT-LR. Lars (Sony) comments on this mega CR and propose way forward for this CR. Walter (Philips) provides comments. Hong (Qualcomm) comments. Wen (vivo) comments. Dario (Session chair): if this CR moves forward, please check that all the affected clauses are listed in the cover page (a few are missing as of now). Sherry (Xiaomi) provides r01, r02, r03 and r04. Lars (Sony) provides r05. ==== Revisions Deadline ==== Walter (Philips) provides late comment Walter (Philips) proposes to approve r05 with 'i.e. absolute location of the Located UE' replaced with 'e.g. absolute location of the Located UE(s)' in clause 5.5.4 ==== Final Comments Deadline ==== | Revised |
| 9.5.2 | S2-2401392 | CR | Approval | 23.586 CR0114R1 (Rel-18, 'F'): Corrections for alignments to TS 23.273/TS 23.586/SA WG3/RAN WGs | Xiaomi | Rel-18 | Revision of S2-2401259r05 + changes. Approved | Agreed | |
| 9.5.2 | S2-2401260 | CR | Approval | 23.273 CR0499 (Rel-18, 'F'): Corrections for alignments to TS 23.273/TS 23.586/SA WG3/RAN WGs | Xiaomi | Rel-18 | r01 + changes Agreed. Revised to S2-2401393. | LiMeng (Huawei) provides comments. Yaxin (OPPO) agrees with LiMeng. Walter (Philips) provides comments. Sherry (Xiaomi) provides r01. ==== Revisions Deadline ==== Dario (session chair): if CR aggregable, fix end of meeting date and check RAN box (why is it ticked?) ==== Final Comments Deadline ==== | Revised |
| 9.5.2 | S2-2401393 | CR | Approval | 23.273 CR0499R1 (Rel-18, 'F'): Corrections for alignments to TS 23.273/TS 23.586/SA WG3/RAN WGs | Xiaomi | Rel-18 | Revision of S2-2401260r01 + changes. Approved | Agreed | |
| 9.5.2 | S2-2401262 | CR | Approval | 23.032 CR0027R1 (Rel-18, 'F'): Updates to Range and Direction | Xiaomi | Rel-18 | Revision of (unhandled) S2-2313193. Postponed | Dario (session chair): the end date of the meeting on the cover page of this CR (as well as of S2-2401259 and S2-2401260) needs to be fixed (1/26 --> 1/29). Hong (Qualcomm) comments and propose to POSTPONE. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Postponed |
| 9.5.2 | S2-2400515 | CR | Approval | 23.503 CR1248 (Rel-18, 'F'): Ranging/SL Positioning policy information | CATT | Rel-18 | Approved | Agreed | |
| 9.5.2 | S2-2400618 | CR | Approval | 23.586 CR0102 (Rel-18, 'F'): Update on functional entity | Huawei, HiSilicon | Rel-18 | Approved | Agreed | |
| 9.5.2 | S2-2400619 | CR | Approval | 23.273 CR0489 (Rel-18, 'F'): Update on GMLC and LMF Services | Huawei, HiSilicon | Rel-18 | r02 Agreed. Revised to S2-2401394. | LiMeng (Huawei) provides r01. Hong (Qualcomm) comments on r01. LiMeng (Huawei) provides r02. Sherry (Xiaomi) not agree with the removal of Target/Reference UE and provides reason Sherry (Xiaomi) takes back the previous comment, which should be for 2400620. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 9.5.2 | S2-2401394 | CR | Approval | 23.273 CR0489R1 (Rel-18, 'F'): Update on GMLC and LMF Services | Huawei, HiSilicon | Rel-18 | Revision of S2-2400619r02. Approved | Agreed | |
| 9.5.2 | S2-2400828 | CR | Approval | 23.586 CR0105 (Rel-18, 'F'): Updates to dicovery | Vivo | Rel-18 | r01 + changes Agreed. Revised to S2-2401395. | Wen (vivo) provides r01. ==== Revisions Deadline ==== Wen (vivo) replies Dario (Session Chair): thanks for remaindering. If the CR is agreeable, 'may' is replaced with 'can' in the note. Dario (Session Chair): the new note includes normative text (may). If the CR is agreeable, please replace 'may' with 'can'. ==== Final Comments Deadline ==== | Revised |
| 9.5.2 | S2-2401395 | CR | Approval | 23.586 CR0105R1 (Rel-18, 'F'): Updates to dicovery | Vivo | Rel-18 | Revision of S2-2400828r01 + changes. Approved | Agreed | |
| 9.5.2 | S2-2400986 | CR | Approval | 23.586 CR0107 (Rel-18, 'F'): Adding SL Positioning Server UE discovery as part of the initial discovery procedure. | CEWiT, Reliance Jio | Rel-18 | Postponed | Richard (Ericsson) provides comments Hong (Qualcomm) comments. LiMeng (Huawei) comments. Abhijeet (CEWiT) response. Abhijeet (CEWiT) comments. Abhijeet (CEWiT) provides r01 based on comments. Lars (Sony) don't agree that this is an optimization. It may result in extra effort at step2 if UE2-n support server functionality. Abhijeet (CEWiT) doesn't agree that it is extra effort at step 2. Rather clarifies step 5 further hence optimizing the process in general. Hong (Qualcomm) provides r02. ==== Revisions Deadline ==== Abhijeet(CEWiT) replies to Hong and proposes a compromised solution. Hong (Qualcomm) replies to Abhijeet, and does not agree to r03 (the version provided past the deadline). Abhijeet (CEWiT) provides r03 and replies to Qualcomm. Lars (Sony) not sure if this CR is needed. Abhijeet (CEWiT) can be postponed to the next meeting. ==== Final Comments Deadline ==== | Postponed |
| 9.5.2 | S2-2400996 | CR | Approval | 23.586 CR0108 (Rel-18, 'F'): Update to align the LR terminology | OPPO | Rel-18 | Noted | Richard (Ericsson) provides comments Yaxin (OPPO) replies to Richard. Hong (Qualcomm) comments. Yaxin (OPPO) provides r01. Dario (session chair): please make sure the list of affected clauses is complete (currently 5.6.2.4 is missing) Yaxin (OPPO) provides r02 to fix the cover sheet. Sherry (Xiaomi) comments. Lars (Sony) this change is not acceptable at this stage. ==== Revisions Deadline ==== Lars (Sony) objects to this CR. Richard (Ericsson) proposes to note the paper. ==== Final Comments Deadline ==== | Noted |
| 9.5.2 | S2-2401116 | CR | Approval | 23.586 CR0111 (Rel-18, 'F'): Updates SL positioning control using supplementary RSPP signalling message | InterDigital | Rel-18 | r01 + changes Agreed. Revised to S2-2401396. | Yaxin (OPPO) this tdoc is in conflict with S2-2400829. Wen(vivo) comments. Jungje(Interdigital) uploaded r01 ==== Revisions Deadline ==== Jungje(Interdigital) uploaded r03 Richard(Ericsson) r03 is a wrong, not ranging related paper. Lars (Sony) is ok with r01. Jungje(Interdigital) replies to Richard(Ericsson) and ask to consider R01 ==== Final Comments Deadline ==== | Revised |
| 9.5.2 | S2-2401396 | CR | Approval | 23.586 CR0111R1 (Rel-18, 'F'): Updates SL positioning control using supplementary RSPP signalling message | InterDigital | Rel-18 | Revision of S2-2401116r01 + changes. Approved | Agreed | |
| 9.5.2 | S2-2401346 | CR | Approval | 23.586 CR0116 (Rel-18, 'F'): Corrections for UE-only operation procedures | Qualcomm Incorporated | Rel-18 | r01 Agreed. Revised to S2-2401397. | Hong (Qualcomm) replies to Mehrdad (MediaTek Inc.). Mehrdad (MediaTek Inc.) provides comment Hong (Qualcomm) provides r01. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 9.5.2 | S2-2401397 | CR | Approval | 23.586 CR0116R1 (Rel-18, 'F'): Corrections for UE-only operation procedures | Qualcomm Incorporated | Rel-18 | Revision of S2-2401346r01. Approved | Agreed | |
| 9.5.2 | - | - | - | Documents exceeding TU budget/quota | - | - | Docs:=1 | - | |
| 9.5.2 | S2-2401264 | CR | Approval | 23.502 CR4513R2 (Rel-18, 'F'): Updates to NEF service | Xiaomi | Rel-18 | Revision of (unhandled) S2-2313192 Not Handled | - | |
| 9.6.2 | - | - | - | 5GC LoCation Services Phase 3 (eLCS_Ph3) | - | - | Docs:=19 | - | |
| 9.6.2 | - | - | - | RAT-Dependent integrity | - | - | Docs:=5 | - | |
| 9.6.2 | S2-2400055 | LS In | Action | LS from RAN WG2: LS on introduction of RAT-Dependent integrity | RAN WG2 (R2-2313796) | Rel-18 | Response drafted in S2-2401120. Final response in S2-2401589 | Replied to | |
| 9.6.2 | S2-2401120 | LS OUT | Approval | [DRAFT] LS reply on introduction of RAT-Dependent integrity | CATT | Rel-18 | Response to S2-2400055. r00 + clean up agreed. Revised to S2-2401589. | Runze (Huawei) supports the LS reply. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 9.6.2 | S2-2401589 | LS OUT | Approval | LS reply on introduction of RAT-Dependent integrity | SA WG2 | Rel-18 | Revision of S2-2401120r00 + clean up. Approved | Approved | |
| 9.6.2 | S2-2401118 | CR | Approval | 23.273 CR0495 (Rel-18, 'F'): Update integrity requirements | CATT | Rel-18 | r03 Agreed. Revised to S2-2401590. | Runze (Huawei) suggests re-wording. Yunjing (CATT) provides r01. Richard (Ericsson) can accept r01 and provides comment. Runze (Huawei) agreed with Richard (Ericsson). Yunjing (CATT) provides r02 and r03. Runze (Huawei) prefers r03. ==== Revisions Deadline ==== Runze (Huawei) proposes to agree r03 and note the other revisions including original version . Richard (Ericsson) accepts r03 ==== Final Comments Deadline ==== | Revised |
| 9.6.2 | S2-2401590 | CR | Approval | 23.273 CR0495R1 (Rel-18, 'F'): Update integrity requirements | CATT | Rel-18 | Revision of S2-2401118r03. Approved | Agreed | |
| 9.6.2 | - | - | - | User plane positioning | - | - | Docs:=6 | - | |
| 9.6.2 | S2-2400649 | CR | Approval | 23.273 CR0490 (Rel-18, 'F'): Clarifications on determination of user plane positioning | China Telecom | Rel-18 | r02 Agreed. Revised to S2-2401591. | Runze (Huawei) provides r01 . Xiaoqian(China Telecom) have some questions on the changes in 0649r01. Runze (Huawei) replies to Xiaoqian(China Telecom) . ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 9.6.2 | S2-2401591 | CR | Approval | 23.273 CR0490R1 (Rel-18, 'F'): Clarifications on determination of user plane positioning | China Telecom | Rel-18 | Revision of S2-2400649r02. Approved | Agreed | |
| 9.6.2 | S2-2400788 | CR | Approval | 23.273 CR0491 (Rel-18, 'F'): Clarifications on user plane positioning | Vivo | Rel-18 | Postponed | Guanglei (Huawei) provides comments. zhendong (ZTE) provides the comment. Richard (Ericsson) provides comments Stephen (Qualcomm) comments Amy (vivo) provides r01 and replies Yunjing (CATT) provides comments. Stephen (Qualcomm) replies to Amy (vivo) Xiaoqian (China Telecom) have some concerns on Stephen's(Qualcomm) comments. Amy (vivo) provides r02 and replies Yunjing (CATT) replies to Amy (vivo). Amy (vivo) provides r03, and replies to Stephen (Qualcomm) and Yunjing (CATT) ==== Revisions Deadline ==== Guanglei (Huawei) propose to postpone, because 'release reason' is in CT1 scope and CT1 is discussing this and does not have consensus as far as I know. Amy (vivo) is ok to postpone this CR. Details can be made based on CT progress. ==== Final Comments Deadline ==== | Postponed |
| 9.6.2 | S2-2400992 | CR | Approval | 23.273 CR0477R1 (Rel-18, 'F'): User plane positioning update for context synchronization | OPPO | Rel-18 | Revision of (unhandled) S2-2312902. Noted | Guanglei (Huawei) provides comments. Richard (Ericsson) provides comments Yaxin (OPPO) replies to Richard and Guanglei. Guanglei (Huawei) further comments. Guanglei (Huawei) provide information. Stephen (Qualcomm) comments Richard (Ericsson) answers to Stephen (Qualcomm) Stephen (Qualcomm) replies to Richard (Ericsson) and Guanglei (Huawei) Richard (Ericsson) has concerns with the CR. Yaxin (OPPO) agrees to note this paper. ==== Revisions Deadline ==== Guanglei (Huawei) proposes to note and thanks Yaxin. | Noted |
| 9.6.2 | S2-2401162 | CR | Approval | 23.273 CR0498 (Rel-18, 'F'): Update of user plane positioning solution | Huawei, HiSilicon | Rel-18 | CC#4: r00 + changes agreed. Revised to S2-2401655. | Yunjing (CATT) asks questions for clarification. Jinguo(ZTE) comments Runze (Huawei) replies to Jinguo(ZTE). Runze (Huawei) replies to Yunjing (CATT). Yunjing (CATT) is fine with the CR. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 9.6.2 | S2-2401655 | CR | Approval | 23.273 CR0498R1 (Rel-18, 'F'): Update of user plane positioning solution | Huawei, HiSilicon | Rel-18 | Revision of S2-2401162r00 + changes. Approved | Agreed | |
| 9.6.2 | - | - | - | Other | - | - | Docs:=8 | - | |
| 9.6.2 | S2-2400051 | LS In | Information | LS from RAN WG1: Reply LS on CPP | RAN WG1 (R1-2312393) | Rel-18 | Noted | Yunjing (CATT) proposes to note the LS as no SA2 action is required. | Noted |
| 9.6.2 | S2-2400093 | CR | Approval | 23.502 CR4591R1 (Rel-18, 'F'): Namf parameter alignment | China Mobile | Rel-18 | Revision of (Unhandled) S2-2312365. WI Code should be 5G_eLCS_Ph3! Noted | Richard (Ericsson) provides comments Dan(China Mobile) reply Richard (Ericsson) responses to Dan(China Mobile) Dan(China Mobile) suggest this paper can be NOTED ==== Revisions Deadline ==== Richard(Ericsson) paper can be Noted ==== Final Comments Deadline ==== | Noted |
| 9.6.2 | S2-2400789 | CR | Approval | 23.273 CR0409R2 (Rel-18, 'F'): Clarification on the reporting indication | Vivo | Rel-18 | Revision of (unhandled) S2-2312122. r01 Agreed. Revised to S2-2401592. | Guanglei (Huawei) ask questions. Amy (vivo) replies to Guanglei (Huawei). Guanglei (Huawei) replies to Amy Yunjing(CATT) agrees with Guanglei (Huawei). Amy (vivo) provides r01 Guanglei (Huawei) provides r02 Amy (vivo) objects r02 Guanglei (Huawei) replies on r02 ==== Revisions Deadline ==== Guanglei (Huawei) can live with r01, prefer r02 Amy (vivo) is ok with r01, objects r02. Richard (Ericsson) accepts r01 ==== Final Comments Deadline ==== | Revised |
| 9.6.2 | S2-2401592 | CR | Approval | 23.273 CR0409R3 (Rel-18, 'F'): Clarification on the reporting indication | Vivo | Rel-18 | Revision of S2-2400789r01. Approved | Agreed | |
| 9.6.2 | S2-2401117 | CR | Approval | 23.273 CR0494 (Rel-18, 'F'): Add description for immediate location request cancellation | CATT | Rel-18 | Not Handled | ==== Final Comments Deadline ==== | - |
| 9.6.2 | S2-2401119 | CR | Approval | 23.273 CR0496 (Rel-18, 'F'): Update LMF service operation | CATT | Rel-18 | r02 Agreed. Revised to S2-2401593. | Richard (Ericsson) provides comments Guanglei (Huawei) provides comments. Yunjing (CATT) provides r01. Stephen (Qualcomm) comments Stephen (Qualcomm) provides an r02 Yunjing (CATT) accepts r02 Richard (Ericsson) accepts r02 ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 9.6.2 | S2-2401593 | CR | Approval | 23.273 CR0496R1 (Rel-18, 'F'): Update LMF service operation | CATT | Rel-18 | Revision of S2-2401119r02. Approved | Agreed | |
| 9.6.2 | S2-2401163 | CR | Approval | 23.273 CR0481R1 (Rel-18, 'F'): Description Update on LCS in PNI-NPN Feature | Huawei, HiSilicon | Rel-18 | Revision of (unhandled) S2-2313073. Approved | ==== Final Comments Deadline ==== | Agreed |
| 9.7.2 | - | - | - | Proximity-based Services in 5GS Phase 2 (5G_ProSe_Ph2) | - | - | Docs:=40 | - | |
| 9.7.2 | - | - | - | LS In for information | - | - | Docs:=1 | - | |
| 9.7.2 | S2-2400040 | LS In | Information | LS from CT WG1: Reply LS on emergency cause value for relay | CT WG1 (C1-239362) | Rel-18 | Noted | Deng Qiang (CATT) it is for information thus can be noted. | Noted |
| 9.7.2 | - | - | - | UE-to-UE relay discovery and communication with security aspects | - | - | Docs:=26 | - | |
| 9.7.2 | S2-2400009 | LS In | Action | LS from CT WG1: LS on 5G ProSe UE-to-UE relay discovery with security aspects | CT WG1 (C1-237897) | Rel-18 | Revision of Postponed S2-2311951 from SA WG2#160. Responses drafted in S2-2400489, S2-2400514. Final response in S2-2401491 | Replied to | |
| 9.7.2 | S2-2400489 | LS OUT | Approval | [DRAFT] Reply LS on 5G ProSe UE-to-UE relay discovery with security aspects | Samsung Research America | Rel-18 | Response to S2-2400009. Merged into S2-2401491 | Deng Qiang (CATT) proposed it be merged into S2-2400514. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 9.7.2 | S2-2400514 | LS OUT | Approval | [DRAFT] Reply LS on 5G ProSe UE-to-UE relay discovery with security aspects | CATT | Rel-18 | Response to S2-2400009. r00 + clean up Agreed. Revised to S2-2401491, merging S2-2400489 | Steve (Huawei) comments on revision needed once CRs are known. Deng Qiang (CATT) clarified CR 0404 from Xiaomi has been attached, and does not think QC CR (1270) needs to be included. Jianning (XIAOMI) comments ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 9.7.2 | S2-2401491 | LS OUT | Approval | Reply LS on 5G ProSe UE-to-UE relay discovery with security aspects | SA WG2 | Rel-18 | Revision of S2-2400514r00 + clean up, merging S2-2400489. Approved | Approved | |
| 9.7.2 | S2-2401160 | LS OUT | Approval | [DRAFT] LS for ProSe U2U relay discovery with model A | InterDigital | Rel-18 | Noted | Deng Qiang (CATT) don't think this LS is needed and proposed to noted. ==== Revisions Deadline ==== Jungje(Interdigital) responded to Fei(OPPO) Fei (OPPO) proposed to note this LS. Jungje(Interdigital) uploaded r01 and r02. Jianning (XIAOMI) supports to Note this LS ==== Final Comments Deadline ==== | Noted |
| 9.7.2 | S2-2400513 | DISCUSSION | Discussion | Further discussion about LS on 5G ProSe UE-to-UE relay discovery with security aspects. | CATT | Rel-18 | Noted | Yali(OPPO) suggests to use this thread to discuss the target UE's L2 ID issue for 2nd hop link setup. Steve (Huawei) comments. Hong (Qualcomm) comments. Jungje(Interdigital) comments Jianning (XIAOMI) comments. Deng Qiang (CATT) proposed a way-forward. Changhong (Intel) supports to use 1270 as baseline. Jianning (XIAOMI) supports to use 1270 as baseline. ==== Revisions Deadline ==== | Noted |
| 9.7.2 | S2-2400304 | DISCUSSION | Approval | Discussion about 5G ProSe UE User Info ID with Security Aspects. | Huawei, HiSilicon | Rel-18 | Noted | Steve (Huawei) comments as the discussion is marked for approval, should be noted. ==== Revisions Deadline ==== | Noted |
| 9.7.2 | S2-2400490 | DISCUSSION | Discussion | Discussion on 5G ProSe UE-to-UE relay discovery and Layer-2 link establishment for PC5 communication via 5G ProSe Lyaer-3 UE-to-UE Relay with security aspects. | Samsung | Rel-18 | Noted | Noted | |
| 9.7.2 | S2-2401145 | DISCUSSION | Discussion | Discussion on U2U relay discovery with model A and security protection. | Interdigital | Rel-18 | Noted | Noted | |
| 9.7.2 | S2-2400946 | CR | Approval | 23.304 CR0404R3 (Rel-18, 'F'): Correction on Layer-2 ID for UE-to-UE Relay Discovery | Xiaomi, CATT | Rel-18 | Revision of (postponed) S2-2313720. Confirm CR Revision - CR states 2! Revised to correct CR rev number in S2-2401476. | Deng Qiang (CATT) proposed to take this CR as way-forward. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 9.7.2 | S2-2401476 | CR | Approval | 23.304 CR0404R4 (Rel-18, 'F'): Correction on Layer-2 ID for UE-to-UE Relay Discovery | Xiaomi, CATT | Rel-18 | Revision of S2-2400946. Approved | Agreed | |
| 9.7.2 | S2-2400305 | CR | Approval | 23.304 CR0409 (Rel-18, 'F'): Update on UE-to-UE Relay Discovery and Link Establishment/Modification for alignment with SA WG3 | Huawei, HiSilicon | Rel-18 | r04 + changes Agreed. Revised to S2-2401492. | Steve (Huawei) provides r01 Qualcomm (Hong) suggest handling this CR after the SoH decision is made. Jungje(Interdigital) comments Deng Qiang (CATT) proposed this CR focus on the Model B discovery alignment with SA3 and remove other changes. Steve (Huawei) provides r02, focusing on stage 3 impacts. Deng Qiang (CATT) comments on r02. Steve (Huawei) enables cases and is commentary Yali (OPPO) comments on r02. Steve (Huawei) comments on the Destination L2-ID Yali (OPPO) replies to Steve (Huawei). Steve (Huawei) comments on new solution - it's not. Walter (Philips) has different comment. Steve (Huawei) provides r03 Deng Qiang (CATT) is reluctant to spend effort on developing solutions for comm. issue. Yali (OPPO) comments on r03 and provides r04 according to the suggestion from Deng Qiang (CATT). ==== Revisions Deadline ==== Hong (Qualcomm) comments that summary of change in the cover page is no longer consistent with the proposed changes. Wanqiang (Session Chair): please give a clear text change about the cover page on top of r04, or else it will be noted. Steve (Huawei) Summary of change update: 'Clarify the Direct Discovery set use and contents in U2U Relay discovery.' Hong (Qualcomm) suggests changing r04 the 'Summary of change' on cover page from '1. Clarify that when the U2U Relay sends Solicitation message, it uses unique Layer-2 IDs that can be associated to per RSC and the Layer-2 ID of the discoverer UE.' to 'Clarify the information included in Direct Discovery set, and other clean ups.' . Steve (Huawei) The proposed coversheet change is good for me. ==== Final Comments Deadline ==== | Revised |
| 9.7.2 | S2-2401492 | CR | Approval | 23.304 CR0409R1 (Rel-18, 'F'): Update on UE-to-UE Relay Discovery and Link Establishment/Modification for alignment with SA WG3 | Huawei, HiSilicon | Rel-18 | Revision of S2-2400305r04 + changes. Approved | Agreed | |
| 9.7.2 | S2-2400306 | CR | Approval | 23.304 CR0410 (Rel-18, 'F'): Update on U2U Identifiers and Candidate U2U Relay Discovery for alignment with SA WG3 | Huawei, HiSilicon | Rel-18 | r03 Agreed. Revised to S2-2401493, merging S2-2401349 | Steve (Huawei) provides r01 Jianning (XIAOMI) comments on r01. Hong (Qualcomm) questions the need of the CR. Jungje(Interdigital) comments Steve (Huawei) comments on first change, provides r02 Walter (Philips) provides r03 as merge with S2-2401349. Steve (Huawei) Thanks Walter (Philips) for the merge, looks good. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 9.7.2 | S2-2401493 | CR | Approval | 23.304 CR0410R1 (Rel-18, 'F'): Update on U2U Identifiers and Candidate U2U Relay Discovery for alignment with SA WG3 | Huawei, HiSilicon, Philips International B.V. | Rel-18 | Revision of S2-2400306r03, merging S2-2401349. Approved | Agreed | |
| 9.7.2 | S2-2400483 | CR | Approval | 23.304 CR0411 (Rel-18, 'F'): Correction on Layer-2 link establishment | Samsung | Rel-18 | Merged into S2-2401495 | Deng Qiang (CATT) proposed it be merged into S2-2401270 and focus on S2-2401270. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 9.7.2 | S2-2400485 | CR | Approval | 23.304 CR0412 (Rel-18, 'F'): Correction on Common identifiers for 5G ProSe UE-to-UE Relay Discovery and Layer-2 link establishment | Samsung | Rel-18 | Covered by S2-2400946. Noted | Kisuk (Samsung) proposed to merge this CR into S2-2400946. Deng Qiang (CATT) proposed to note this CR and focus on S2-2400946 and S2-2401270. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Noted |
| 9.7.2 | S2-2400487 | CR | Approval | 23.304 CR0414 (Rel-18, 'F'): Correction on 5G ProSe UE-to-UE Relay Discovery and Layer-2 link establishment with Source Layer-2 ID of Discoverer UE | Samsung | Rel-18 | Noted | Deng Qiang (CATT) proposed to note this CR and focus on S2-2400946 and S2-2401270. ==== Revisions Deadline ==== Steve (Huawei) objects to all revisions, as it was not the chosen way to go. ==== Final Comments Deadline ==== | Noted |
| 9.7.2 | S2-2400488 | CR | Approval | 23.304 CR0415 (Rel-18, 'F'): Correction on 5G ProSe UE-to-UE Relay Discovery and Layer-2 link establishment with Index | Samsung | Rel-18 | Noted | Deng Qiang (CATT) proposed to note this CR and focus on S2-2400946 and S2-2401270. ==== Revisions Deadline ==== Steve (Huawei) objects to all revisions, as it was not the chosen way to go. ==== Final Comments Deadline ==== | Noted |
| 9.7.2 | S2-2400542 | CR | Approval | 23.304 CR0417 (Rel-18, 'F'): Clarification on Layer-2 ID of the target 5G ProSe End UE with security aspects | OPPO | Rel-18 | Noted | Deng Qiang (CATT) proposed to note this CR and focus on S2-2401270. ==== Revisions Deadline ==== Steve (Huawei) objects to all revisions, as it was not the chosen way to go. ==== Final Comments Deadline ==== | Noted |
| 9.7.2 | S2-2400948 | CR | Approval | 23.304 CR0421 (Rel-18, 'F'): Correction on Layer-2 ID for second hop of Direct Communication Reqeust | Xiaomi, | Rel-18 | Merged into S2-2401495 | Deng Qiang (CATT) proposed this CR be merged into S2-2401270. ==== Revisions Deadline ==== Jianning (XIAOMI) is ok to merge into S2-2401270 ==== Final Comments Deadline ==== | Merged |
| 9.7.2 | S2-2401158 | CR | Approval | 23.304 CR0423 (Rel-18, 'F'): Update procedure for 5G ProSe UE-to-UE Relay Discovery with Model A | InterDigital | Rel-18 | r11 + changes Agreed. Revised to S2-2401494. | Steve (Huawei) comments Jianning (XIAOMI) comments, provides r01. Jungje(Interdigital) responded to Hong(Qualcomm) Hong (Qualcomm) asks questions for clarification. Jianning (XIAOMI) response to Jungje (Interdigital). Jungje(Interdigital) responds to Jianning(Xiaomi) and Steve(Huawei) Jungje(Interdigital) comments and provides r02 Steve (Huawei) comments on alignment and changes needed Jungje (Interdigital) responded to Deng(CATT) Deng Qiang (CATT) also prefers to keep the original figure and only update the text for alignment. Jungje(Interdigital) oppose to r04 and provide r05. Jianning (XIAOMI) comments on r03 and provides r04. Jianning (XIAOMI) comments. Steve (Huawei) comments in circular reference Walter (Philips) thinks r05 is better than r04 Steve (Huawei) comments on 2 phases Jungje(Interdigital) responded to Steve (Huawei) and provided r06. Jianning (XIAOMI) comments on r06. Fei (OPPO) comments and asks questions Jianning (XIAOMI) provides r07 and r08 for selection Steve (Huawei) comments on the update Jungje(Interdigital) provides r09 Jungje(Interdigital) responded to Steve(Huawei) Steve (Huawei) but where to? Jungje(Interdigital) replies to Steve (Huawei) Steve (Huawei) provides r10 Fei (OPPO) provides r11. Jungje(Interdigital) responds to Fei(OPPO) and upload r12. Fei (OPPO) replied to Jung Je (InterDigital). Jungje(Interdigital) replies to Fei (OPPO). ==== Revisions Deadline ==== Fei (OPPO) can only accept r11, object other revisions and the original one. Jungje(Interdigital) comments. Jianning (XIAOMI) suggests to go r08 that is only SA3 alignment, without any controverial issue, hope it is acceptable. Fei (OPPO) is ok with r08, r11 and objects other revisions and r00. Xiaoyan (CATT) asks Jianning (XIAOMI) for clarification. Jianning (XIAOMI) replies to Xiaoyan (CATT). Steve (Huawei) Overall R08 could be as far as we go now. Let's agree that. Jungje(Interdigital) oppose to R08 . Wanqiang(session chair): r11 is good to go? Or it is noted? Jungje(Interdigital) can live with r11 Jianning (XIAOMI) cannot accept r11, suggest to go R08, it is pure alignment which is also agreeable in other CRs. (change 'User Info ID' to 'Direct Discovery set') Jianning (XIAOMI) comments on r11. Fei (OPPO) agree with Steve that r08 is a small step. Jianning (XIAOMI) tries to propose a compromised option based on r11, remove 'model B (as shown in clause 6.3.2.4.3)' Walter (Philips) supports proposal from Jianning (Xiaomi) Fei (OPPO) Jianning's proposal modification on top of r11 works for us. Steve (Huawei) is ok with Jianning's proposal. Jungje(Interdigital) is OK with Jianning's proposal Xiaoyan (CATT) requests further clarification from Jianning (XIAOMI). Xiaoyan (CATT) requests further clarification on Model-A ==== Final Comments Deadline ==== | Revised |
| 9.7.2 | S2-2401494 | CR | Approval | 23.304 CR0423R1 (Rel-18, 'F'): Update procedure for 5G ProSe UE-to-UE Relay Discovery with Model A | InterDigital | Rel-18 | Revision of S2-2401158r11 + changes. Approved | Agreed | |
| 9.7.2 | S2-2401270 | CR | Approval | 23.304 CR0424 (Rel-18, 'F'): Clarifications on Layer-2 IDs used in UE-to-UE Relay link establishment procedure | Qualcomm Incorporated | Rel-18 | r01 Agreed. Revised to S2-2401495, merging S2-2400483 and S2-2400948 | Deng Qiang (CATT) proposed to use this CR as baseline to resolve the issue for U2U Relay comm. Hong (Qualcomm) provides r01, adding supporting companies. Jianning (XIAOMI) comments. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 9.7.2 | S2-2401495 | CR | Approval | 23.304 CR0424R1 (Rel-18, 'F'): Clarifications on Layer-2 IDs used in UE-to-UE Relay link establishment procedure | Qualcomm Incorporated, Samsung, Xiaomi | Rel-18 | Revision of S2-2401270r01, merging S2-2400483 and S2-2400948. Approved | Agreed | |
| 9.7.2 | S2-2401349 | CR | Approval | 23.304 CR0425 (Rel-18, 'F'): Clarification of identifiers used for UE-to-UE relay discovery | Philips International B.V. | Rel-18 | Merged into S2-2401493 | Deng Qiang (CATT) proposed this CR be merged into S2-2400306. Walter (Philips) will try to merge this CR with S2-2400306. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 9.7.2 | - | - | - | Miscellaneous corrections | - | - | Docs:=12 | - | |
| 9.7.2 | S2-2400160 | CR | Approval | 23.304 CR0402R1 (Rel-18, 'F'): Clarification on Cell Reporting in multi-path L2 U2N case | Nokia, Nokia Shanghai Bell, Vivo | Rel-18 | Revision of (unhandled) S2-2312895. Approved | Agreed | |
| 9.7.2 | S2-2400302 | CR | Approval | 23.304 CR0339R2 (Rel-18, 'F'): Clarification on IPv6 only for policy control and session binding for L3 N3IWF Relay | Huawei, HiSilicon | Rel-18 | Revision of (unhandled) S2-2310927. r01 + changes Agreed. Revised to S2-2401496. | Hong (Qualcomm) comments on the reason for change. Steve (Huawei) comments, provides r01. ==== Revisions Deadline ==== Hong (Qualcomm) comments. Steve (Huawei) r01 is ok with the additional typo correction 'add 'is' before 'not available.' at the end of the new note'. ==== Final Comments Deadline ==== | Revised |
| 9.7.2 | S2-2401496 | CR | Approval | 23.304 CR0339R3 (Rel-18, 'F'): Clarification on IPv6 only for policy control and session binding for L3 N3IWF Relay | Huawei, HiSilicon | Rel-18 | Revision of S2-2400302r01 + changes. Approved | Agreed | |
| 9.7.2 | S2-2400303 | CR | Approval | 23.304 CR0340R2 (Rel-18, 'F'): Clarification on how path type is selected when switching between U2N relays | Huawei, HiSilicon, Nokia, Nokia Shanghai Bell | Rel-18 | Revision of (merged) S2-2310928. Approved | Agreed | |
| 9.7.2 | S2-2400506 | CR | Approval | 23.304 CR0416 (Rel-18, 'F'): Alignment with RAN for path switching | OPPO | Rel-18 | r02 Agreed. Revised to S2-2401497. | Steve (Huawei) provides r01 Hong (Qualcomm) comments on r01. Fei (OPPO) responds to Hong (Qualcomm). Shabnam (Ericsson) shares same view as Qualcomm, proposes simply to add additional reference to TS 38.413 clause within existing text and avoid what transparent containers contain. Fei (OPPO) responds and provides r02. ==== Revisions Deadline ==== Steve (Huawei) is ok with r02. ==== Final Comments Deadline ==== | Revised |
| 9.7.2 | S2-2401497 | CR | Approval | 23.304 CR0416R1 (Rel-18, 'F'): Alignment with RAN for path switching | OPPO | Rel-18 | Revision of S2-2400506r02. Approved | Agreed | |
| 9.7.2 | S2-2400548 | CR | Approval | 23.304 CR0418 (Rel-18, 'F'): EN removal for L2 U2U QoS handling | OPPO | Rel-18 | Approved | Agreed | |
| 9.7.2 | S2-2400549 | CR | Approval | 23.304 CR0419 (Rel-18, 'F'): Clarification on association between User Info and L2 ID for L2 U2U | OPPO | Rel-18 | Postponed | Steve (Huawei) asks a question for clarification Yali(OPPO) replies to Steve (Huawei) Steve (Huawei) comments. JungJe(Interdigital) comments. LaeYoung (LGE) also proposes to POSTPONE this CR. Hong (Qualcomm) propose to POSTPONE the CR. Yali(OPPO) provides r01. Deng Qiang (CATT) we should wait for RAN2 feedback. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Postponed |
| 9.7.2 | S2-2400825 | CR | Approval | 23.304 CR0420 (Rel-18, 'F'): Updates to default L2 ID usage for discovery message | Vivo | Rel-18 | Confirm CR Number - CR states -! r01 Agreed. Revised to S2-2401836. | Fei (OPPO) comments that a revision is required to update the CR number in the cover sheet. Wen (vivo) provides r01. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 9.7.2 | S2-2401836 | CR | Approval | 23.304 CR0420R1 (Rel-18, 'F'): Updates to default L2 ID usage for discovery message | Vivo | Rel-18 | Revision of S2-2400825r01. Approved | Agreed | |
| 9.7.2 | S2-2401147 | CR | Approval | 23.304 CR0422 (Rel-18, 'F'): Update policy parameter provisioning for U2U relay | InterDigital | Rel-18 | r01 + cleanup Agreed. Revised to S2-2401498. | Steve (Huawei) provides r01 ==== Revisions Deadline ==== Jungje(Interdigital) uploaded R02 Steve (Huawei) comments, r02 was late?, but the coversheet cleanup is ok. ==== Final Comments Deadline ==== | Revised |
| 9.7.2 | S2-2401498 | CR | Approval | 23.304 CR0422R1 (Rel-18, 'F'): Update policy parameter provisioning for U2U relay | InterDigital | Rel-18 | Revision of S2-2401147r01 + cleanup. Approved | Agreed | |
| 9.7.2 | - | - | - | Documents exceeding TU budget/quota | - | - | Docs:=1 | - | |
| 9.7.2 | S2-2400486 | CR | Approval | 23.304 CR0413 (Rel-18, 'F'): Correction on 5G ProSe UE-to-UE Relay Discovery and Layer-2 link establishment with Source Layer-2 ID of Discoveree UE | Samsung | Rel-18 | Not Handled | - | |
| 9.8.2 | - | - | - | Generic group management, exposure and communication enhancements (GMEC) | - | - | Docs:=16 | - | |
| 9.8.2 | - | - | - | Group management: LADN Service Area, Maximum Group Data Rate | - | - | Docs:=9 | - | |
| 9.8.2 | S2-2400049 | LS In | Action | LS from CT WG4: Reply LS on LADN Service Area Configuration in UDM Subscription | CT WG4 (C4-235539) | Rel-18 | Noted | Qianghua (Huawei) suggests to note this LS, no actions requested Sang-Jun (Samsung) agrees on Qianghua (Huawei)'s suggestion to note this LS. | Noted |
| 9.8.2 | S2-2400349 | CR | Approval | 23.503 CR1244 (Rel-18, 'F'): Handling of updated Maximum Group Data Rate | Ericsson | Rel-18 | r04 Agreed. Revised to S2-2401398. | Qianghua (Huawei) shares the same understanding with the identified problem, prefer alt3 and if alt4, suggests to simplify the updates Georgios (Nokia) prefers alt4. Open to any simplifications. Stefan (Ericsson) replies Qianghua (Huawei) replies Sang-Jun (Samsung) prefers Alt4 with the proposed short description. Stefan (Ericsson) replies to Qianghua and Sang-Jun Qianghua (Huawei) ask questions and provides alt.5 to consider, and suggest more time to discuss Stefan (Ericsson) relies to Qianghua Qianghua (Huawei) suggests to consider alt3 instead or more time to consider alt2/5 Stefan (Ericsson) provides r01 Georgios (Nokia) agrees with r01 Qianghua (Huawei) provides r02 for alt3 (preferred), r03 for alt4 (based on r01), objects r00, r01 Stefan (Ericsson) almost ok with r03, provides r04 to fix one problem Georgios (Nokia) prefers r04, backup r02 ==== Revisions Deadline ==== Qianghua (Huawei) ok with r04, or r02. Object r00/r01 Sang-Jun (Samsung) is OK with r04. Stefan (Ericsson) prefers r04 ==== Final Comments Deadline ==== | Revised |
| 9.8.2 | S2-2401398 | CR | Approval | 23.503 CR1244R1 (Rel-18, 'F'): Handling of updated Maximum Group Data Rate | Ericsson | Rel-18 | Revision of S2-2400349r04. Approved | Agreed | |
| 9.8.2 | S2-2400496 | CR | Approval | 23.501 CR5237 (Rel-18, 'F'): LADN provisioning when there is existing PDU session | ZTE | Rel-18 | r01 Agreed. Revised to S2-2401399. | Qianghua (Huawei) supports the updates in this CR, asks to cosign Georgios (Nokia) supports releasing the session Ashok (Samsung) is ok with the proposal of releasing the session and asks to co-sign zhendong (ZTE) provides the r01 ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 9.8.2 | S2-2401399 | CR | Approval | 23.501 CR5237R1 (Rel-18, 'F'): LADN provisioning when there is existing PDU session | ZTE, Huawei, HiSilicon, Samsung | Rel-18 | Revision of S2-2400496r01. Approved | Agreed | |
| 9.8.2 | S2-2400497 | CR | Approval | 23.502 CR4689 (Rel-18, 'F'): LADN provisioning when there is existing PDU session | ZTE | Rel-18 | r02 Agreed. Revised to S2-2401400. | Qianghua (Huawei) supports the idea in this CR, provides comment Georgios (Nokia) supports releasing the session zhendong (ZTE) provides the r01 Georgios (Nokia) is OK with r01 Qianghua (Huawei) provides r02 and cosigns ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 9.8.2 | S2-2401400 | CR | Approval | 23.502 CR4689R1 (Rel-18, 'F'): LADN provisioning when there is existing PDU session | ZTE, Huawei | Rel-18 | Revision of S2-2400497r02. Approved | Agreed | |
| 9.8.2 | S2-2401149 | CR | Approval | 23.501 CR5033R1 (Rel-18, 'F'): Handling of existing LADN DNN PDU session when LADN information is updated | Samsung | Rel-18 | Revision of (noted) S2-2310945. Noted | Qianghua (Huawei) repeats the concerns expressed at Xi'an meeting and suggests to use 0496?0496 as a way forward Sebastian (Qualcomm) objects to the CR Ashok (Samsung) ready to NOTE it ==== Revisions Deadline ==== | Noted |
| 9.8.2 | S2-2401155 | CR | Approval | 23.502 CR4526R1 (Rel-18, 'F'): Handling of existing LADN DNN PDU session when LADN information is updated | Samsung | Rel-18 | Revision of (unhandled) S2-2310946. Noted | Qianghua (Huawei) repeats the concerns expressed at Xi'an meeting and suggests to use 0496?0497 as a way forward Sebastian (Qualcomm) objects to the CR for the same reasons as expressed for S2-2401149 Ashok (Samsung) ready to NOTE it and agrees with Rapporteur proposal to go with 0496/97 ==== Revisions Deadline ==== | Noted |
| 9.8.2 | - | - | - | Group Exposure: TSCTSF option and UDR/PCF option, temporal invalidity condition | - | - | Docs:=7 | - | |
| 9.8.2 | S2-2400498 | CR | Approval | 23.501 CR5238 (Rel-18, 'F'): Clarification on the temporal invalidity conditions | ZTE | Rel-18 | r02 Agreed. Revised to S2-2401401. | Qianghua (Huawei) comments zhendong (ZTE) provides the clarification Qianghua (Huawei) comments on the overlapping with 1010 zhendong (ZTE) provides the r01 Qianghua (Huawei) provides r02 ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 9.8.2 | S2-2401401 | CR | Approval | 23.501 CR5238R1 (Rel-18, 'F'): Clarification on the temporal invalidity conditions | ZTE, Huawei | Rel-18 | Revision of S2-2400498r02. Approved | Agreed | |
| 9.8.2 | S2-2400499 | CR | Approval | 23.503 CR1247 (Rel-18, 'F'): Clarification on the temporal invalidity conditions | ZTE | Rel-18 | Noted | Qianghua (Huawei) comments, see details for 0498 zhendong (ZTE) agree, this CR is not needed. It can be marked as Noted ==== Revisions Deadline ==== | Noted |
| 9.8.2 | S2-2400724 | CR | Approval | 23.502 CR4704 (Rel-18, 'F'): AF requested QoS for a UE or group of UEs | Samsung | Rel-18 | Approved | Agreed | |
| 9.8.2 | S2-2401010 | CR | Approval | 23.501 CR5283 (Rel-18, 'F'): Removal of the option to use TSCTSF | NTT DOCOMO | Rel-18 | Postponed | Qianghua (Huawei) comments Jari (NTT DOCOMO) responds to Qianghua Sang-Jun (Samsung) has concerns on that this CR also affects TSC-related procedure. Qianghua (Huawei) responds Georgios (Nokia) provides comments Stefan (Ericsson) comments Jari (NTT DOCOMO) proposes to POSTPONE. Responds to Stefan, Qianghua, et all Qianghua (Huawei) ok to postpone Stefan (Ericsson) supports to postpone ==== Revisions Deadline ==== | Postponed |
| 9.8.2 | S2-2401044 | CR | Approval | 23.503 CR1259 (Rel-18, 'F'): Removal of the option to use TSCTSF | NTT DOCOMO | Rel-18 | Postponed | Qianghua (Huawei) comments, same for S2-2401010 Stefan (Ericsson) has also same comments as provided for 01010 Qianghua (Huawei) ok to postpone Stefan (Ericsson) supports to postpone ==== Revisions Deadline ==== | Postponed |
| 9.8.2 | S2-2401086 | CR | Approval | 23.502 CR4723 (Rel-18, 'F'): Removal of the option to use TSCTSF | NTT DOCOMO | Rel-18 | Postponed | Qianghua (Huawei) comments, same for S2-2401010 Stefan (Ericsson) has also same comments as provided for 01010 Qianghua (Huawei) ok to postpone Stefan (Ericsson) supports to postpone ==== Revisions Deadline ==== | Postponed |
| 9.9.2 | - | - | - | System Support for AI/ML-based Services (AIMLsys) | - | - | Docs:=19 | - | |
| 9.9.2 | S2-2400077 | CR | Approval | 23.288 CR1022 (Rel-18, 'F'): DNAI parameter removal from E2E data volume transfer time predictions | OPPO | Rel-18 | Approved | Xiaoyan (CATT) asks for clarification Alla provides clarifications to Xiaoyan (CATT) and confirms that S2-2400672 should be considered as merged into S2-2400077 Haiyang (Huawei) supports the proposal Xiaoyan (CATT) provides further comments. Alla (OPPO) provides further clarifications. Tingyu (Samsung) asks for clarification from Xiaoyan (CATT). ==== Revisions Deadline ==== Xiaoyan (CATT) can live with r00. Xiaoyan (CATT) replies to Tingyu (Samsung). Alla (OPPO) thanks Xiaoyan and proposes to proceed with the agreed initial version (r00). ==== Final Comments Deadline ==== | Agreed |
| 9.9.2 | S2-2400116 | CR | Approval | 23.288 CR0856R2 (Rel-18, 'F'): Removing Editor s Note of the Output of the Network Performance Analytics | NTT DOCOMO | Rel-18 | Revision of (unhandled) S2-2312325. r03 Agreed. Revised to S2-2401499, merging S2-2400314 | Zhao (Huawei) suggests to merge S2-2400314 into S2-2400116, and provides S2-2400116r01. Bahador (NTT DOCOMO) accepts the merged version r01. Alla (OPPO) is OK with the merged version r01. Tingyu (Samsung) provides comments. Bahador (NTT DOCOMO) agrees with Tingyu and provides r02 Zhao (Huawei) clears the text issue and provides r03. Alla (OPPO) supports r03. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 9.9.2 | S2-2401499 | CR | Approval | 23.288 CR0856R3 (Rel-18, 'F'): Removing Editor s Note of the Output of the Network Performance Analytics | NTT DOCOMO | Rel-18 | Revision of S2-2400116r03, merging S2-2400314. Approved | Agreed | |
| 9.9.2 | S2-2400121 | CR | Approval | 23.502 CR4589R1 (Rel-18, 'F'): Correction of chargeable party aspect of PDTQ policy | NTT DOCOMO | Rel-18 | Revision of (unhandled) S2-2312328. Postponed | Belen (Ericsson) provides comments Bahador (NTT DOCOMO) requests further clarification Haiyang (Huawei) provides comments Belen (Ericsson) replies. Bahador (NTT DOCOMO) provides response Belen (Ericsson) is okay to postpone as proposed by DOCOMO. Bahador (NTT DOCOMO) postpones this paper. ==== Revisions Deadline ==== | Postponed |
| 9.9.2 | S2-2400314 | CR | Approval | 23.288 CR1026 (Rel-18, 'F'): Remove the EN regarding Network Performance analytics | Huawei, HiSilicon | Rel-18 | Merged into S2-2401499 | Zhao (Huawei) proposes to merge S2-2400314 into S2-2400116. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 9.9.2 | S2-2400315 | CR | Approval | 23.503 CR1242 (Rel-18, 'F'): Clarification on the PDTQ policy | Huawei, HiSilicon | Rel-18 | r02 Agreed. Revised to S2-2401500. | Belen (Ericsson) provides r01 Zhao (Huawei) replies to Belen(Ericsson) and cannot accept r01. Belen (Ericsson) objects to the initial revision, only accepts r01 so far. Zhao (Huawei) replies to Belen(Ericsson). Dongjoo (Nokia) supports 01 Zhao (Huawei) provides r02. Dongjoo (Nokia) is fine with 02 ==== Revisions Deadline ==== Belen (Ericsson) is okay with r02 ==== Final Comments Deadline ==== | Revised |
| 9.9.2 | S2-2401500 | CR | Approval | 23.503 CR1242R1 (Rel-18, 'F'): Clarification on the PDTQ policy | Huawei, HiSilicon | Rel-18 | Revision of S2-2400315r02. Approved | Agreed | |
| 9.9.2 | S2-2400386 | CR | Approval | 23.502 CR4682 (Rel-18, 'F'): Clarification on filtering criteria of member UE selection | Samsung | Rel-18 | r02 Agreed. Revised to S2-2401501. | Jaewoo (LGE) comments. Jingran (OPPO) comments. Dongjoo (Nokia) asks question for clarification. Zhao (Huawei) provides comments. Tingyu (Samsung) replies and provides r01. Jingran (OPPO) comments on r01. Dongjoo (Nokia) provides comments on r01. Tingyu (Samsung) provides r02 and replies. Dongjoo (Nokia) is fine with r02. Jingran (OPPO) is ok with r02. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 9.9.2 | S2-2401501 | CR | Approval | 23.502 CR4682R1 (Rel-18, 'F'): Clarification on filtering criteria of member UE selection | Samsung | Rel-18 | Revision of S2-2400386r02. Approved | Agreed | |
| 9.9.2 | S2-2400387 | CR | Approval | 23.288 CR1027 (Rel-18, 'F'): Clarification on E2E data volume transfer time analytics | Samsung | Rel-18 | r04 Agreed. Revised to S2-2401502. | Jingran (OPPO) provides comments. Tingyu (Samsung) provides r01 based on offline discussion with Peretz (Verizon). Dongjoo (Nokia) provides comments. Bahador (NTT DOCOMO) provides comments Tingyu (Samsung) replies and provides r02. Jingran (OPPO) comments for the r02. Dongjoo (Nokia) provides comments on r02. Tingyu (Samsung) replies. Jingran (OPPO) is ok with the r03. Dongjoo (Nokia) provides comments on r03. Tingyu (Samsung) provides r04. Dongjoo (Nokia) is happy with r03. Tingyu (Samsung) confirms with Dongjoo (Nokia) whether Dongjoo (Nokia) meant happy with r04. Dongjoo (Nokia) re-confirms we are happy with r04. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 9.9.2 | S2-2401502 | CR | Approval | 23.288 CR1027R1 (Rel-18, 'F'): Clarification on E2E data volume transfer time analytics | Samsung, Verizon | Rel-18 | Revision of S2-2400387r04. Approved | Agreed | |
| 9.9.2 | S2-2400461 | CR | Approval | 23.502 CR4687 (Rel-18, 'F'): Corrections to MemberUESelectionAssistance for updating the list of target member UEs | LG Electronics | Rel-18 | r01 Agreed. Revised to S2-2401503. | Juan Zhang (Qualcomm) provides comment. Jaewoo (LGE) responds to Zhao (Huawei). Zhao (Huawei) provides comments. Jaewoo (LGE) responds to Juan Zhang (Qualcomm). Jingran (OPPO) responds to Jaewoo (LGE). David (Samsung) comments. Belen (Ericsson) comments. Jaewoo (LGE) replies to the previous comments and provides r01. Jingran (OPPO) is ok with r01. Zhao (Huawei) is fine with r01. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 9.9.2 | S2-2401503 | CR | Approval | 23.502 CR4687R1 (Rel-18, 'F'): Corrections to MemberUESelectionAssistance for updating the list of target member UEs | LG Electronics | Rel-18 | Revision of S2-2400461r01. Approved | Agreed | |
| 9.9.2 | S2-2400672 | CR | Approval | 23.288 CR1042 (Rel-18, 'F'): Correction of E2E data volume transfer time | ETRI | Rel-18 | Mistakenly submitted under eNA, should be AIMLsys; identical to S2-2400077. Covered by S2-2400077. Noted | Alla (OPPO) provides proposal to consider S2-2400672 merged into S2-2400077. Jihoon (ETRI) is okay to merge S2-2400672 into S2-2400077. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Noted |
| 9.9.2 | S2-2400680 | CR | Approval | 23.502 CR4652R4 (Rel-18, 'F'): Correction of direct event notification in multi-member AF session with required QoS | Qualcomm Incorporated | Rel-18 | Revision of (revised and postponed) S2-2313618. r01 + changes Agreed. Revised to S2-2401504. | Dongjoo (Nokia) provides comments and asks questions for clarification Dongeun (Samsung) provides comments Haiyang (Huawei) comments Juan Zhang (Qualcomm) replies to Nokia, Samsung and HW. Haiyang (Huawei) suggests to go with option 2 Dongjoo (Nokia) agrees with Huawei to go with option 2 Juan Zhang (Qualcomm) provides r01 Dongjoo (Nokia) is fine with r01 Haiyang (Huawei) is OK with r01 and hope to cosign Dongeun (Samsung) comments Juan Zhang (Qualcomm) replies to Dongeun (Samsung). ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 9.9.2 | S2-2401504 | CR | Approval | 23.502 CR4652R5 (Rel-18, 'F'): Correction of direct event notification in multi-member AF session with required QoS | Qualcomm Incorporated, Huawei | Rel-18 | Revision of S2-2400680r01 + changes. Approved | Agreed | |
| 9.9.2 | S2-2400784 | CR | Approval | 23.502 CR4711 (Rel-18, 'F'): R18 AIMLsys_KI1_23502_CR for clarification on IP domain | Nokia, Nokia Shanghai Bell | Rel-18 | Noted | Dongeun (Samsung) comments Jingran (OPPO) comments. Jaewoo (LGE) comments. Dongjoo (Nokia) responds to Jaewoo (LGE) and Jingran (OPPO), and provides r01. Dongjoo (Nokia) responds to Dongeun (Samsung). Jaewoo (LGE) responds to Dongjoo (Nokia). Dongjoo (Nokia) provides r02. Belen (Ericsson) asks a question for clarification Dongjoo (Nokia) provides r03. Mirko (Huawei) comments that this addition of IP domain information to the AF input should not be necessary. Dongjoo (Nokia) asks a question for clarification to Mirko (Huawei) Dongeun (Samsung) ask a question Dongjoo (Nokia) replies to Dongeun (Samsung) Mirko (Huawei) responds to the question from Dongjoo. Dongjoo (Nokia) asks a question to Mirko (Huawei) ==== Revisions Deadline ==== Mirko (Huawei) objects to this CR and all of its revisions. Dongjoo (Nokia) is ok to note this CR in this meeting. ==== Final Comments Deadline ==== | Noted |
| 9.9.2 | S2-2400785 | CR | Approval | 23.503 CR1254 (Rel-18, 'F'): R18 AIMLsys_KI5_23503_CR for clarification on PDTQ procedures | Nokia, Nokia Shanghai Bell | Rel-18 | r06 Agreed. Revised to S2-2401505. | Zhao (Huawei) provides comments. Dongjoo (Nokia) provides r01. Belen (Ericsson) provides comments on r01 and initial version. Dongjoo (Nokia) replies to Belen (Ericsson). Dongjoo (Nokia) provides r02 Belen (Ericsson) provides r03 Dongjoo (Nokia) provides r05 Belen (ericsson) is okay with r05 Zhao (Huawei) provides comments and r06. Dongjoo (Nokia) can live with r06. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 9.9.2 | S2-2401505 | CR | Approval | 23.503 CR1254R1 (Rel-18, 'F'): R18 AIMLsys_KI5_23503_CR for clarification on PDTQ procedures | Nokia, Nokia Shanghai Bell | Rel-18 | Revision of S2-2400785r06. Approved | Agreed | |
| 9.10.2 | - | - | - | 5G multicast-broadcast services Phase 2 (5MBS_Ph2) | - | - | Docs:=20 | - | |
| 9.10.2 | - | - | - | On RedCap UE Broadcast reception | - | - | Docs:=10 | - | |
| 9.10.2 | S2-2400054 | LS In | Action | LS from RAN WG2: Reply LS to SA WG2 on RedCap UE MBS Broadcast reception | RAN WG2 (R2-2313689) | Rel-18 | Responses drafted in S2-2400144, S2-2400455. Final response in S2-2401506 | Replied to | |
| 9.10.2 | S2-2400061 | LS In | Action | LS from RAN WG3: Reply LS to SA WG2 on RedCap UE MBS Broadcast reception | RAN WG3 (R3-237959) | Rel-18 | Responses drafted in S2-2400144, S2-2400665. Final response in S2-2401506 | Replied to | |
| 9.10.2 | S2-2400451 | DISCUSSION | Information | Further Consideration for 5MBS broadcast support of RedCAP UEs. | Nokia; Nokia Shanghai-Bell | Rel-18 | Noted | Robbie (Ericsson) shares the same view as LiMeng (Huawei) and clarifies. LiMeng (Huawei) seeks to clarify the issues. Robbie (Ericsson) asks a question. Haris(Qualcomm) provides comments and supports sending the LS Thomas(Nokia) replies to Haris, Robbie, and LiMeng Robbie (Ericsson) replies to Thomas(Nokia), Haris (Qualcomm), LiMeng(Huawei) Thomas(Nokia) replies to Robbie and Limeng. LiMeng (Huawei) clarifies. ==== Revisions Deadline ==== | Noted |
| 9.10.2 | S2-2400144 | LS OUT | Approval | [DRAFT] Reply LS on RedCap UE MBS Broadcast reception | Ericsson | Rel-18 | Response to S2-2400054, S2-2400061. Merged into S2-2401506 | Thomas (Nokia) suggest to merge this contribution into S2-2400455 Robbie (Ericsson) is fine to merge it into S2-2400455. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 9.10.2 | S2-2400455 | LS OUT | Approval | [DRAFT] Reply LS on RedCap UE MBS Broadcast reception | Nokia.Nokia Shanghai-Bell | Rel-18 | Response to S2-2400054. r03 + clean up Agreed. Revised to S2-2401506, merging S2-2400144 and S2-2400665 | LiMeng (Huawei) provides r01. Robbie (Ericsson) provides comments. Haris(Qualcomm) provides r02 LiMeng (Huawei) is fine with the principle in r02, provides r03. Thomas (Nokia) is fine with r03. ==== Revisions Deadline ==== Robbie (Ericsson) is fine with r03. ==== Final Comments Deadline ==== | Revised |
| 9.10.2 | S2-2401506 | LS OUT | Approval | Reply LS on RedCap UE MBS Broadcast reception | SA WG2 | Rel-18 | Response to S2-2400054 and S2-2400061. Revision of S2-2400455r03 + clean up, merging S2-2400144 and S2-2400665. Approved | Approved | |
| 9.10.2 | S2-2400665 | LS OUT | Approval | [DRAFT] Reply LS to RAN WG3 on RedCap UE MBS Broadcast reception | Huawei, HiSilicon | Rel-18 | Response to S2-2400061. Merged into S2-2401506 | Thomas (Nokia) suggest to merge this contribution into S2-2400455 LiMeng (Huawei) is fine to merge this contribution into S2-2400455 ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 9.10.2 | S2-2400145 | CR | Approval | 23.247 CR0341R3 (Rel-18, 'F'): Support for RedCap UEs in MBS Broadcast | Qualcomm Incorporated, ZTE, Ericsson | Rel-18 | Revision of (endorsed) S2-2311681. r04 Agreed. Revised to S2-2401507, merging S2-2400438 | Thomas (Nokia) provides r01 to merge S2-2400438 Haris(Qualcomm) proposes r02 Fenqin (Huawei) proposes r03 Robbie (Ericsson) provides r04. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 9.10.2 | S2-2401507 | CR | Approval | 23.247 CR0341R5 (Rel-18, 'F'): Support for RedCap UEs in MBS Broadcast | Qualcomm Incorporated, ZTE, Ericsson, Nokia, Nokia Shanghai-Bell, Huawei, HiSilicon | Rel-18 | Revision of S2-2400145r04, merging S2-2400438. Approved | Agreed | |
| 9.10.2 | S2-2400438 | CR | Approval | 23.247 CR0341R4 (Rel-18, 'F'): Support for RedCap UEs in MBS Broadcast | [Qualcomm Incorporated, ZTE], Nokia, Nokia Shanghai Bell | Rel-18 | Revision of (endorsed) S2-2311681. Merged into S2-2401507 | Robbie (Ericsson) suggests merging it to S2-2400145. Haris(Qualcomm) comments Thomas(Nokia) agrees to merge into S2-2400145 ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 9.10.2 | - | - | - | Others | - | - | Docs:=10 | - | |
| 9.10.2 | S2-2400042 | LS In | Information | LS from CT WG1: LS on the impact of supporting multicast MBS session and Broadcast MBS session for UEs using eDRX | CT WG1 (C1-239661) | Rel-18 | Noted | Robbie (Ericsson) agrees with LiMeng (Huawei). LiMeng (Huawei) proposes to note this LS. | Noted |
| 9.10.2 | S2-2400666 | CR | Approval | 23.247 CR0349 (Rel-18, 'F'): On the general correction in TS 23.247 | Huawei, HiSilicon | Rel-18 | r04 Agreed. Revised to S2-2401508. | LiMeng (Huawei) is fine with r01. Robbie (Ericsson) provides r01. Thomas (Nokia) provides r02. Robbie (Ericsson) asks a question. LiMeng (Huawei) provides r03. Thomas (Nokia) provides r04. Robbie (Ericsson) is fine with r04. LiMeng (Huawei) is fine with r04. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 9.10.2 | S2-2401508 | CR | Approval | 23.247 CR0349R1 (Rel-18, 'F'): On the general correction in TS 23.247 | Huawei, HiSilicon, Ericsson, Nokia, Nokia Shanghai-Bell | Rel-18 | Revision of S2-2400666r04. Approved | Agreed | |
| 9.10.2 | S2-2400667 | CR | Approval | 23.502 CR4700 (Rel-18, 'F'): Correction on the AMF service operation for 5MBS | Huawei, HiSilicon | Rel-18 | r01 Agreed. Revised to S2-2401509. | Robbie (Ericsson) prefers r01 and provides comments. LiMeng (Huawei) responds to Zhendong (ZTE) and provides r01. zhendong (ZTE) provides the comments zhendong (ZTE) provides the response Robbie (Ericsson) asks Zhendong (ZTE). Thomas(Nokia) comments that changes relate to the 5MBS WI rather than the 5MBS_Ph2 WI and should be done from Rel-17 onwards. Robbie (Ericsson) replies to Zhendong (ZTE). ==== Revisions Deadline ==== ==== Final Comments Deadline ==== Thomas(Nokia) requests to handle in CC#4 and suggest postponing. | Revised |
| 9.10.2 | S2-2401509 | CR | Approval | 23.502 CR4700R1 (Rel-18, 'F'): Correction on the AMF service operation for 5MBS | Huawei, HiSilicon | Rel-18 | Revision of S2-2400667r01. Approved | Agreed | |
| 9.10.2 | S2-2400668 | CR | Approval | 23.247 CR0350 (Rel-18, 'F'): Correction on the AMF service operation for 5MBS | Huawei, HiSilicon | Rel-18 | r02 Agreed. Revised to S2-2401510. | LiMeng (Huawei) is fine with r01. Robbie (Ericsson) provides r01. Haris(Qualcomm) provides r02 Thomas(Nokia) comments that changes relate to the 5MBS WI rather than the 5MBS_Ph2 WI and should be done from Rel-17 onwards. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== Thomas(Nokia) requests to handle in CC#4 and suggest postponing. | Revised |
| 9.10.2 | S2-2401510 | CR | Approval | 23.247 CR0350R1 (Rel-18, 'F'): Correction on the AMF service operation for 5MBS | Huawei, HiSilicon, Ericsson | Rel-18 | Revision of S2-2400668r02. Approved | Agreed | |
| 9.10.2 | S2-2400840 | CR | Approval | 23.247 CR0351 (Rel-18, 'F'): Clarification on the mobility procedures for UEs in RRC_INACTIVE state | ZTE | Rel-18 | Postponed | zhendong (ZTE) is fine witgh r01 Robbie (Ericsson) provides r01. Haris(Qualcomm) comments zhendong (ZTE) provides the response Haris(Qualcomm) responds and proposes alternative text zhendong (ZTE) provides the r02 Thomas (Nokia) provides r03 and r04, asks to ignore r03, and objects against r00, r01, r02 and r03. Robbie (Ericsson) raises comments to Thomas (Nokia) LiMeng (Huawei) shares the view from Robbie (Ericsson) zhendong (ZTE) provides the comments Robbie (Ericsson) provides comments. Thomas(Nokia) replies Haris(Qualcomm) proposes to postpone if r04 is all we can agree on ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Postponed |
| 9.10.2 | S2-2400841 | CR | Approval | 23.247 CR0352 (Rel-18, 'F'): Clarification on the Multicast MBS procedures for UEs using power saving functions | ZTE | Rel-18 | r01 Agreed. Revised to S2-2401511. | zhendong (ZTE) provides response Robbie (Ericsson) provides r01. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 9.10.2 | S2-2401511 | CR | Approval | 23.247 CR0352R1 (Rel-18, 'F'): Clarification on the Multicast MBS procedures for UEs using power saving functions | ZTE | Rel-18 | Revision of S2-2400841r01. Approved | Agreed | |
| 9.11.2 | - | - | - | Network Slicing Phase 3 (eNS_Ph3) | - | - | Docs:=71 | - | |
| 9.11.2 | - | - | - | KI#1 | - | - | Docs:=40 | - | |
| 9.11.2 | S2-2400236 | CR | Approval | 23.501 CR5221 (Rel-18, 'F'): Clarification on Slice Replacement | Samsung | Rel-18 | r03 + changes Agreed. Revised to S2-2401512. | Hoyeon (Samsung) replies to Stefano (Qualcomm), Haiyang (Huawei) and Jinguo (ZTE). Jinguo(ZTE) comments. Haiyang (Huawei) comments. Stefano (Qualcomm) requires clarifications. Peter Hedman (Ericsson) provides comments Hoyeon (Samsung) provides replies and r01. Peter Hedman (Ericsson) provides reply to Hoyeon Haiyang (Huawei) clarifies to Hoyeon (Samsung). Hoyeon (Samsung) provides comments. Haiyang (Huawei) provides r03. Hoyeon (Samsung) provides r02. ==== Revisions Deadline ==== Hoyeon (Samsung) provides r04 after revision deadline. Requests to handle this during CC. Hoyeon (Samsung): I'd like check if we can agree r03 in this meeting and do further clean up (e.g. r04) in the Feb meeting? If not, I think we need to request to handle r04 at CC#3. Wanqiang (Session Chair): No new revisions will be accepted (except for LS out) after revision deadline. Please give a clear text change on top of r03 and make sure everybody will be ok with the additional change. Alessio(Nokia) suggests avoiding changes but can live with r04 and supports r03 Peter Hedman (Ericsson) ok with r03 + changes proposed by Hoyeon (note though that the change is part of 2nd change in the CR) Dongeun (Samsung) echoes : On top of r03, remove the last sentence 'If the unsubscribed S-NSSAI(s) that the UE requests are not Alternative S-NSSAI(s) in the UE context, the AMF determines to update the UE configuration' and add 'and based on the verification the AMF determines whether to update the UE configuration.' on the first change. (for CC#3) ==== Final Comments Deadline ==== | Revised |
| 9.11.2 | S2-2401512 | CR | Approval | 23.501 CR5221R1 (Rel-18, 'F'): Clarification on Slice Replacement | Samsung, Huawei, HiSilicon | Rel-18 | Revision of S2-2400236r03 + changes. Approved | Agreed | |
| 9.11.2 | S2-2400237 | CR | Approval | 23.502 CR4675 (Rel-18, 'F'): Clarification on Slice Replacement | Samsung | Rel-18 | r03 Agreed. Revised to S2-2401513. | Haiyang (Huawei) comments Peter Hedman (Ericsson) provides comments Hoyeon (Samsung) provides comments Hoyeon (Samsung) provides r01. Hoyeon (Samsung) replies to Jinguo (ZTE). Hoyeon (Samsung) provides r02. Jinguo(ZTE) provides comments and suggest to remove the first change. Genadi (Lenovo) provides comments and r03. ==== Revisions Deadline ==== Hoyeon (Samsung) provides r04 after revision deadline. Requests to handle this during CC. Hoyeon (Samsung): I'd like check if we can agree r03 in this meeting and do further clean up (e.g. r04) in the Feb meeting? If not, I think we need to request to handle r04 at CC#3. Wanqiang (Session Chair): No new revisions will be accepted (except for LS out) after revision deadline. Please give a clear text change on top of r03 and make sure everybody will be ok with the additional change. Alessio(Nokia) suggests avoiding changes but can live with r04 and supports r03 Peter Hedman (Ericsson) ok with r03 and r04 i.e. r03+<changes> to be determined. Genadi (Lenovo) is OK with r03 + remove 'Mapping Of' + replace sentence. ==== Final Comments Deadline ==== | Revised |
| 9.11.2 | S2-2401513 | CR | Approval | 23.502 CR4675R1 (Rel-18, 'F'): Clarification on Slice Replacement | Samsung | Rel-18 | Revision of S2-2400237r03. Approved | Agreed | |
| 9.11.2 | S2-2400582 | CR | Approval | 23.501 CR4927R2 (Rel-18, 'F'): Clarification on how to handle PDU Session when Alternative S-NSSAI / replaced S-NSSAI is not supported in the target area | LG Electronics | Rel-18 | Revision of (unhandled) S2-2312576. Merged into S2-2401514 | Myungjune (LGE) replies to Haiyang (Huawei). Haiyang (Huawei) comments. Myungjune (LGE) replies to Dongeun (Samsung). Dongeun (Samsung) provides comments Peter Hedman (Ericsson) provides comments Alessio (nokia) provides r01 Peter Hedman (Ericsson) provides comments on r01 and the need for general agreement on whether AMF enforces area for replaced S-NSSAI Alessio(Nokia) believes that according to current behaviour the replaced S-NSSAI cannot be in the Allowed NSSAI when the UE camps in an area where it is not supported. Then, since the Alternative S-NSSAI is included 'additionally' to the replaced S-NSSAI as per current text, it follows the Alternative s-NSSAI is removed unless it is used also for other PDU sessions unrelated to slice replacement, as in LG paper. Fenqin(Huawei) comments Myungjune comments on r02 Jinguo(ZTE) comments and provides r02 Myungjune (LGE) thinks that most of us agree that if UE moves to out of replaced S-NSSAI area, session is released regardless of alternative S-NSSAI area. Alessio(Nokia) can only accept r01, r02 seems to go in a direction that is unclear Jinguo(ZTE) suggests to merge this paper into 970 ==== Revisions Deadline ==== Myungjune (LGE) is ok to merge into S2-2400970 ==== Final Comments Deadline ==== | Merged |
| 9.11.2 | S2-2400970 | CR | Approval | 23.501 CR5277 (Rel-18, 'F'): Support of Network Slice Replacement and area restrictions at UE mobility | Ericsson | Rel-18 | r10 + changes Agreed. Revised to S2-2401514, merging S2-2400582 | Myungjune (LGE) comments Dongeun (Samsung) provides comments Jinguo(ZTE) comments Peter Hedman (Ericsson) provides replies and r01 Myungjune (LGE) is not ok with r01 Jinguo(ZTE) is fine with r01 Genadi (Lenovo) is wondering why both replaced S-NSSAI and Alternative S-NSSAI are included in the Allowed NSSAI. Genadi (Lenovo) provides replies to Peter Hedman (Ericsson). Alessio(Nokia) provides r02 Fenqin (Huawei) comments Jinguo(ZTE) agrees with Myungjune Myungjune replies to Genadi (Lenovo) Genadi (Lenovo) provides further comments. Genadi (Lenovo) provides comments regarding the inclusion of replaced S-NSSAI in the Allowed NSSAI. Jinguo(ZTE) replies to Genadi (Lenovo) Myungjune (LGE) replies to Genadi (Lenovo) Peter Hedman (Ericsson) provides comments that we should try to get an agreement on the wanted behavior/logic at the CC Genadi (Lenovo) replies to Jinguo (ZTE). Jinguo(ZTE) replies to Peter Hedman (Ericsson) Peter Hedman (Ericsson) provides reply to Jinguo and a way forward Fenqin (Huawei) comments. Dongeun (Samsung) support 1, 2a and ask question for 3a/3b Jinguo(ZTE) replies to Myungjune(LGE) Myungjune replies to Jinguo (ZTE) . Myungjune (LGE) comments on proposed logic. Fenqin (Huawei) provides comments Jinguo(ZTE) agree with Fenqin(Huawei) Peter Hedman (Ericsson) provides replies and r03 Genadi (Lenovo) provides comments and r04. Alessio(Nokia) thinks the way forward does not require voting if we agree on a basic principle Alessio replies to Genadi (Lenovo) Alessio provides r05 Genadi (Lenovo) provides r06. Myungjune (LGE) provides r07. Dongeun (Samsung) ask question on r07 Alessio(Nokia) is ok with r07. Myungjune (LGE) replies to Dongeun (Samsung). Dongeun (Samsung) provide r08 Fenqin (Huawei) provide r09 Peter Hedman (Ericsson) provides r10 ==== Revisions Deadline ==== Myungjune (LGE) is ok with r10 Dongeun (Samsung) asks a question Dongeun (Samsung) is ok with r10 and ask to co-sign Peter Hedman (Ericsson) thanks will add Samsung and LG Electronics i.e. ok with r10 + co-signing companies Alessio(Nokia) can also add support by Nokia, Nokia Shanghai Bell. Genadi (Lenovo) suggests to move the new sentence starting with 'If the replaced S-NSSAI cannot be kept in the Allowed NSSAI...' after NOTE 5. Peter Hedman (Ericsson) ok with suggestion from Genadi i.e. r10 + co-signing companies + move new sentence starting with 'If the replaced S-NSSAI cannot be kept in the Allowed NSSAI...' after NOTE 5 Alessio (nokia) requests also another change If the UE moves to a cell where the replaced S-NSSAI is not supported To If the UE moves to a cell outside the NS-AoS of the replaced S-NSSAI With this it is agreeable and we support. Peter Hedman (Ericsson) suggests to agree r10 + co-signing companies + move new sentence starting with 'If the replaced S-NSSAI cannot be kept in the Allowed NSSAI...' after NOTE 5 ==== Final Comments Deadline ==== Alessio (nokia) comments that then you cannot remove NOTE 2. So please reinstate note 2. Peter Hedman (Ericsson) enforcement is done by not allowing UP connectivity, i.e. note 2 is the not needed/correct? Alessio(Nokia) comments that the current text does not require removal of UP resources. So Note two should still be valid at cell level. Peter Hedman (Ericsson) proposes to progress r10+co-signing companies + revised 'NOTE 2: There are no means for the PLMN to prevent the UE from obtaining service in the Alternative network slice in cells outside the NS-AoS while inside the supported TA of the replaced network slice and within the NS-AoS of the Alternative network slice if the Alternative network slice NS-AoS exceeds the NS-AoS of the replaced network slice.' Peter Hedman (Ericsson) proposes to progress r10+co-signing companies + revised 'NOTE 2: There are no means for the PLMN to prevent the UE from obtaining service in the Alternative network slice in cells outside the NS-AoS while inside the supported TA of the replaced network slice and within the NS-AoS of the Alternative network slice if the Alternative network slice NS-AoS exceeds the NS-AoS of the replaced network slice.' Peter Hedman (Ericsson) proposes to progress r10+co-signing companies + revised 'NOTE 2: There are no means for the PLMN to prevent the UE from obtaining service in the Alternative network slice in cells outside the NS-AoS while inside the supported TA of the replaced network slice and within the NS-AoS of the Alternative network slice if the Alternative network slice NS-AoS exceeds the NS-AoS of the replaced network slice.' Alessio (Nokia) is technically ok with revised 'NOTE 2: There are no means for the PLMN to prevent the UE from obtaining service in the Alternative network slice in cells outside the NS-AoS while inside the supported TA of the replaced network slice and within the NS-AoS of the Alternative network slice if the Alternative network slice NS-AoS exceeds the NS-AoS of the replaced network slice.' Alessio (Nokia) is technically ok with revised 'NOTE 2: There are no means for the PLMN to prevent the UE from obtaining service in the Alternative network slice in cells outside the NS-AoS while inside the supported TA of the replaced network slice and within the NS-AoS of the Alternative network slice if the Alternative network slice NS-AoS exceeds the NS-AoS of the replaced network slice.' Peter Hedman (Ericsson) ok with r10+co-signed companies + adding note 2 (as is or revised) Dongeun Suh (Samsung) check if the following works: r10+co-signed companies + add 'If the UE moves outside the NS-AoS of the replaced S-NSSAI, the PDU session associated with the Alternative S-NSSAI and the replaced S-NSSAI is deactivated as per area restriction for the replaced S-NSSAI.' just after the 1st sentence in the 1st change Alessio(Nokia) can live with this text for sake of progress. Fenqin (Huawei) think the proposal from Dongeun is possible way forward. We prefer this way. If this is not possible agreed, then we can keep NOTE 2. Peter Hedman (Ericsson) proposes to re-instate note 2 rather than change the logical text at this point. | Revised |
| 9.11.2 | S2-2401514 | CR | Approval | 23.501 CR5277R1 (Rel-18, 'F'): Support of Network Slice Replacement and area restrictions at UE mobility | Ericsson, Samsung, LG Electronics, Nokia, Nokia Shanghai Bell, Lenovo | Rel-18 | Revision of S2-2400970r10 + changes, merging S2-2400582. CC#4: Approved | Agreed | |
| 9.11.2 | S2-2400971 | CR | Approval | 23.502 CR4717 (Rel-18, 'F'): Support of Network Slice Replacement and area restrictions at UE mobility | Ericsson | Rel-18 | r03 Agreed. Revised to S2-2401515. | Jinguo (ZTE) comments. Peter Hedman (Ericsson) provides comments Jinguo(ZTE) is fine Alessio(Nokia) provides r01 and comments Fenqin (Huawei) comments Peter Hedman (Ericsson) provides reply on whether to use a new row for Alternative S-NSSAI(s) Hoyeon (Samsung) asks to add Samsung as supporting company, and provides comments. Fenqin (Huawei) suggest to use one row. Peter Hedman (Ericsson) provides r02 with cleanup and adding Samsung Alessio(Nokia) asks to add nokia when this is uploaded (unless you want to provide a revision ??) Peter Hedman (Ericsson) provides r03 adding Nokia ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 9.11.2 | S2-2401515 | CR | Approval | 23.502 CR4717R1 (Rel-18, 'F'): Support of Network Slice Replacement and area restrictions at UE mobility | Ericsson, Samsung, Nokia, Nokia Shanghai Bell | Rel-18 | Revision of S2-2400971r03. Approved | Agreed | |
| 9.11.2 | S2-2400453 | CR | Approval | 23.501 CR5233 (Rel-18, 'F'): Clarifications on PDU Sessions due to Network Slice Replacement | Samsung | Rel-18 | r04 Agreed. Revised to S2-2401480, merging S2-2401105 | Dongeun (Samsung) replies to Jinguo (ZTE) and Haiyang (Huawei) Jinguo(ZTE) comments Haiyang (Huawei) comments Genadi (Lenovo) provides comments. Peter Hedman (Ericsson) provides comments Dongeun (Samsung) replies to Genadi (Lenovo) and Peter (Ericsson) Jinguo(ZTE) provides comments Jinguo(ZTE) replies to Dongeun (Samsung) Dongeun (Samsung) replies to Jinguo(ZTE) Alessio(Nokia) Comments that any consideration on AMF support should be removed from CR and adds more comments Iskren (NEC) comments Peter Hedman (Ericsson) provides reply to Dongeun Dongeun (Samsung) provides r01 and replies Jinguo(ZTE) is ok to assume homogenous support for network slice replacement feature. Myungjune (LGE) comments Fenqin(Huawei) comments Dongeun (Samsung) replies to Fenqin(Huawei) Fenqin(Huawei) responds Dongeun (Samsung) replies to Fenqin (Huawei) and provides r02 Jinguo(ZTE) provides r03 Alessio(Nokia) prefers to note this paper and come back with a multi-company paper at next meeting based on offline discussion. R02 is not enough to address NSAC issues in all possible permutations of cases. Jinguo(ZTE) suggest to approve or endorse at this meeting so we can use it as basis for next meeting Jinguo(ZTE) provides r03 again Dongeun (Samsung) is ok with r03 and replies to Alessio (Nokia) Peter Hedman (Ericsson) ok with r03 and support the CR Genadi (Lenovo) provides r04. ==== Revisions Deadline ==== Dongeun (Samsung) is ok with r04 + add missing reference, i.e., just after 'If NSAC for maximum number of UEs is configured for the S-NSSAI and/or the Alternative S-NSSAI, the AMF performs NSAC procedure as described in clause 4.2.11.2', add 'or 4.2.11.2a' (for CC#3) Fenqin (Huawei) comments and suggest to bring this to CC#3. Dongeun(Samsung) is ok with r04 Alessio(Nokia) can accept technically endorsing the two approaches and then do a SoH at next meeting or come with a merged proposal at next meeting if offline we get agreement. but not just endorsing one approach. Also there is a possibility we change the approach altogether and put restrictions on what is allowed in rel-18 Alessio(NoKia ) comments that the text does not say which of the AMFs and SMFs do the action. Let's come back next meeting. none of the CRs is covering the possible scenarios clearly. Jinguo(ZTE) suggests to technique endorse this CR and further work at next meeting. Peter Hedman (Ericsson) ok with r04 Alessio(Nokia) objects r04 Dongeun (Samsung) agree with Jinguo (ZTE) and suggests to technique endorse this CR and further work at next meeting. Alessio(Nokia) objects to approval and endorsements on the basis the CR is technically incorrect. ==== Final Comments Deadline ==== | Revised |
| 9.11.2 | S2-2401480 | CR | Approval | 23.501 CR5233R1 (Rel-18, 'F'): Clarifications on PDU Sessions due to Network Slice Replacement | Samsung, ZTE, Lenovo, Huawei | Rel-18 | Following CC#3 discussions, used as a working assumption and work on these CRs further in February as needed. Revision of S2-2400453r04, merging S2-2401105. Endorsed | Endorsed | |
| 9.11.2 | S2-2400454 | CR | Approval | 23.502 CR4686 (Rel-18, 'F'): Clarifications on PDU Sessions due to Network Slice Replacement | Samsung | Rel-18 | r04 Agreed. Revised to S2-2401481. | Peter Hedman (Ericsson) provides comments Dongeun (Samsung) replies to Peter Hedman (Ericsson) will update the CR in the upcoming revision Alessio(Nokia) comments Peter Hedman (Ericsson) provides reply Dongeun provides r02 (r01 was a mistake) and replies to Peter Hedman (Ericsson) Fenqin(Huawei) provides r03 Dongeun (Samsung) is ok with r03 Peter Hedman (Ericsson) provides comments that principles ok, but we need cleanup of the CR, and asks a question. Iskren (NEC) comments. Dongeun provides r04 (clean-up) and replies to Peter (Ericsson) and Iskren (NEC) Alessio(Nokia) asks to postpone this paper as well as per same request on 453. Clearly it only coves some cases Jinguo(ZTE) suggest to approve or endorse at this meeting so we can use it as basis for next meeting Dongeun (Samsung) agrees with Jinguo (ZTE) and replies to Alessio (Nokia) Peter Hedman (Ericsson) supports the CR as way forward ==== Revisions Deadline ==== Fenqin (Huawei) we also supports this CR as way forward Alessio(Nokia) cannot caccept any of the CRs as technically incorrect as second bullet does not say what SMF is involved in the step . Also we want to ensure we cover all the cases sensibly. We cannot e.g. make subject to NSAC in alternative slice which is not subscribed a UE that had no NSAC in original slice (and viceversa). Also the issue of quotas consumption is relevant: if the alternative slice allows many more UEs of original (whether because of lack of NSAC of much bigger quota) to join, we will experience massive loss of service upon return to original slice. so what was the point to allow the replacement if we do have losses on way back? Jinguo(ZTE) suggests to technique endorse this CR and further work at next meeting. Peter Hedman (Ericsson) ok with r04 Alessio(Nokia) has indicated The CRs is technically incorrect. We know the text of this CR and alternatives so we do not start from scratch. We may also agree approaches that are alternative to both. Alessio not ok with any revision in this thread. ==== Final Comments Deadline ==== | Revised |
| 9.11.2 | S2-2401481 | CR | Approval | 23.502 CR4686R1 (Rel-18, 'F'): Clarifications on PDU Sessions due to Network Slice Replacement | Samsung, Huawei | Rel-18 | Following CC#3 discussions, used as a working assumption and work on these CRs further in February as needed. Revision of S2-2400454r04. Endorsed | Endorsed | |
| 9.11.2 | S2-2401036 | DISCUSSION | Approval | On NSAC for network slice replacement KI#1. | Nokia, Nokia Shanghai Bell | Rel-18 | Noted | Noted | |
| 9.11.2 | S2-2401041 | CR | Approval | 23.502 CR4721 (Rel-18, 'F'): Network slice replacement and NSAC | Nokia, Nokia Shanghai Bell | Rel-18 | Noted | George Foti (Ericsson) provides comments Iskren (NEC) comments Alessio(Nokia) believes the NSAC for slice replacement is an open issue. We see that if we want to achieve the same logic with policy based interactions at the AMF and SMFs it does not scale. On the other hand the related DP explains why applying blidnly NSAC as is produces weird outcomes in terms of service to customers. Jinguo(ZTE) comments that this 502 CR has dependency on outcome of 501 CR in 1045. Jinguo(ZTE) suggests merge this paper into 0327 ==== Revisions Deadline ==== Jinguo(ZTE) withdraws the previous comment. suggests to note this paper and focus on 453 and 454. Jinguo(ZTE) suggests to note this paper and focus 1041 for 502 CR and 1045 for 501 CR. George (Ericsson) provides We are NOT OK with any merge. I don't see a 327. Can U please explain this 327. George (Ericsson) does not accept this CR and any revision. Peter Hedman (Ericsson) suggests to note this paper George (Ericsson) provides response to Jnguo ==== Final Comments Deadline ==== | Noted |
| 9.11.2 | S2-2401045 | CR | Approval | 23.501 CR5201R1 (Rel-18, 'F'): Network slice replacement and NSAC | Nokia, Nokia Shanghai Bell | Rel-18 | Revision of (postponed) S2-2313093. Noted | George Foti (Ericsson) proposes to note the CR Genadi (Lenovo) provides comments. Alessio(Nokia) replies to Genadi and George George (Ericsson) responds. This is not FASMO. Rather a new proposal. What other NSAC issues are U talking about Fenqin(Huawei) comments. Jinguo(ZTE) comments and suggest to use 1105 as basis. Iskren (NEC) comments George (Ericsson) provides comment. Alessio replies to fenqin: Each of AMF and SMF contacts both the NSACFs that apply. Please check the paper and the CR (they do consider the NSACFs are different!) George (Ericsson) provides comments Fenqin(Huawei) give further comments. Jinguo(ZTE) suggests to merge this paper into 0236. ==== Revisions Deadline ==== Jinguo(ZTE) suggests to note this paper and focus on 453 and 454. George (Ericsson) We are NOT OK with any merge of this in 236. George (Ericsson) Does not ACCEPT any revision including the original Peter Hedman (Ericsson) suggests to note this paper ==== Final Comments Deadline ==== | Noted |
| 9.11.2 | S2-2401105 | CR | Approval | 23.501 CR5290 (Rel-18, 'F'): NSAC for Alternative S-NSSAI | ZTE | Rel-18 | Merged into S2-2401480 | Fenqin (Huawei) proposes r01 Peter Hedman (Ericsson) provides comments Jinguo(ZTE) replies to Alessio(nokia) Alessio(nokia) wonders how approving this CR and revisions like r02 could be useful at all and suggested to use the Nokia CRs as basis as they are the ones that really solve the issue at hand meeting commercial and technical issues as explained in DP Fenqin(Huawei) comments Jinguo(ZTE) suggest to merge this paper into 0453 Alessio (nokia) asks to note this paper ==== Revisions Deadline ==== Peter Hedman (Ericsson) assumes the CR is to be marked merged into 0453 ==== Final Comments Deadline ==== | Merged |
| 9.11.2 | S2-2400269 | CR | Approval | 23.501 CR5099R1 (Rel-18, 'F'): Determination of Network Slice Instance congestion | Huawei, HiSilicon | Rel-18 | Revision of (unhandled) S2-2312269. Noted | Peter Hedman (Ericsson) provides r01 Alessio(Nokia) asks to note this CR (r00 and r01) as it is a textbook example of a non FASMO CR (A NOTE providing an example of a behaviour) Haiyang (Huawei) seeks clarification from Nokia Haiyang (Huawei) provides r02 Myungjune (LGE) comments on r02 Haiyang (Huawei) provides r03 Alessio(Nokia) We still see no need, as it is not a FASMO. ==== Revisions Deadline ==== Myungjune (LGE) is ok with r03 Alessio(Nokia) We still see no need, as it is not a FASMO. Asks to note Peter Hedman (Ericsson) ok with r03 and r01 ==== Final Comments Deadline ==== | Noted |
| 9.11.2 | S2-2400270 | CR | Approval | 23.501 CR5101R1 (Rel-18, 'F'): Clarifications on the Allowed NSSAI provided to the RAN | Huawei, HiSilicon | Rel-18 | Revision of (unhandled) S2-2312272. Noted | Myungjune (LGE) comments. Jinguo(ZTE) comments that this paper is not needed Haiyang (Huawei) seeks for clarification. Alessio(Nokia) agrees with the previous comments and proposes to note the paper. We should not change the AMF behavior to send allowed NSSAI to NG-RAN. Alessio(Nokia) the AMF sends the allowed NSSAI in the Allowed NSSAI IE. This is as simple as that. The paper needs to be noted. Myungjune (LGE) replies to Haiyang (Huawei) Peter Hedman (Ericsson) agrees that the changes are not needed ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Noted |
| 9.11.2 | S2-2400271 | CR | Approval | 23.502 CR4578R1 (Rel-18, 'F'): Clarifications on the Allowed NSSAI provided to the RAN | Huawei, HiSilicon | Rel-18 | Revision of (unhandled) S2-2312273. Noted | Peter Hedman (Ericsson) provides comments Alessio (nokia) agrees with Peter Hedman (Ericsson) comments and asks to NOTE this paper. ==== Revisions Deadline ==== Peter Hedman (Ericsson) asks to note the paper ==== Final Comments Deadline ==== | Noted |
| 9.11.2 | S2-2400579 | CR | Approval | 23.501 CR5243 (Rel-18, 'F'): Clarification on subscription retrieval during slice replacement | LG Electronics | Rel-18 | Postponed | Haiyang (Huawei) comments Jinguo (ZTE) comments. Genadi (Lenovo) provides further comments related to Jinguo (ZTE) question. Genadi (Lenovo) provides comments. Peter Hedman (Ericsson) provides comments Myungjune (LGE) replies to Genadi (Lenovo) Alessio(Nokia) comments. Genadi (Lenovo) replies to Myungjune (LGE). Myungjune (LGE) provides r01. Jinguo(ZTE) comments Alessio(Nokia ) provides r02 Peter Hedman (Ericsson) provides comments to r02 Peter Hedman (Ericsson) provides question when Alternative S-NSSAI used by the AF? Genadi (Lenovo) replies to Peter Hedman (Ericsson) that Alternative S-NSSAI is not used by the AF. Myungjune comments on r02 Genadi (Lenovo) provides r03. Fenqin(Huawei) ask a question Myungjune (LGE) answers to Fenqin(Huawei) Fenqin (Huawei) reponds to Myungjune Myungjune (LGE) provides r04 Dongeun (Samsung) provides comments Myungjune (LGE) provides r05. Dongeun (Samsung) ask question Myungjune (LGE) answers Dongeun (Samsung) Alessio (nokia) replies Alessio (nokia) provides r06 which is update of r02 yellow text added (I think) Myungjune (LGE) comments on r06 ==== Revisions Deadline ==== Fenqin (Huawei) is ok with r05 and object r06 Myungjune (LGE) proposes to agree r05. Dongeun (Samsung) comments to Myungjune (LGE) Myungjune(LGE) replies to Dongeun (Samsung) Alessio(Nokia) cannot agree on r06 as it leaves the SMF decision to choose what subscription info to apply. we need testable behavior to have interoperable and uniform solution across vendors. Peter Hedman (Ericsson) ok with r05 (or r04), objects to r06 Alessio(Nokia) mixed up previous comment and confirms we agree on our own r06 but the comment was on r05(i.e. cannot accept R05) as it leaves the SMF decision to choose what subscription info to apply. we need testable behavior to have interoperable and uniform solution across vendors. Dongeun (Samsung) support r05 Genadi (Lenovo) supports r05. Alessio (nokia) objects r05 Jinguo(ZTE) request to approve r05+ one sentence 'The SMF handles the subscription data in such a way that if a conflict exists between the replaced S-NSSAI and the Alternative S-NSSAI the replaced S-NSSAI information takes priority' Alessio (nokia) is ok to approve r05+ one sentence 'The SMF handles the subscription data in such a way that if a conflict exists between the replaced S-NSSAI and the Alternative S-NSSAI the replaced S-NSSAI information takes priority' Myungjune (LGE) is not OK with the proposal. Myungjune (LGE) proposes to postpone. ==== Final Comments Deadline ==== | Postponed |
| 9.11.2 | S2-2400580 | CR | Approval | 23.502 CR4694 (Rel-18, 'F'): Clarification on subscription retrieval during slice replacement | LG Electronics | Rel-18 | r06 + clean up Agreed. Revised to S2-2401516, merging S2-2401056 | Haiyang (Huawei) comments Myungjune (LGE) replies to Dongeun (Samsung). Dongeun (Samsung) provides comments Alessio(Nokia)Comments: we are ok to consider this CR for the aspect of subscription retrieval but we need to discuss what is the subscription that takes precedence really if we consider both. Myungjune (LGE) think that it is hard to give precedence to one subscription. Alessio(Nokia) replies that we need a testable behavior so r00 is not ok for Nokia. Lets' align the 23.502 Cr to the outcome of the 23.501 discussion Myungjune (LGE) provides r01. Myungjune (LGE) provides r02. Genadi (Lenovo) provides r03. Genadi (Lenovo) provides r04. Myungjune (LGE) corrects that r04 is provided by LGE. Alessio(Nokia) objects to r04 Alessio(Nokia) provides r05 Jinguo(ZTE) is ok with r05. The cover page may need to be updated. Myungjune (LGE) provides r06. Peter Hedman (Ericsson) provides comments on ME impacts.... ==== Revisions Deadline ==== Fenqin (Huawei) is ok with r06 or r07. Myungjune (LGE) provides r07 after revision deadline to remove ME tick and add Ericsson as supporting company. Requests to handling during CC. Alessio(Nokia) ok with r06, r07 Peter Hedman (Ericsson) ok with r06 + untick ME impacted box, and add co-signing companies (aka as r07) Dongeun (Samsung) support r06/r07 Genadi (Lenovo) supports ok with r06 + untick ME impacted box, and add Lenovo co-signing. Myungjune (LGE) proposes to agree r06 + untick ME impacted box + add Ericsson, Samsung, Lenovo to supporting company. ==== Final Comments Deadline ==== | Revised |
| 9.11.2 | S2-2401516 | CR | Approval | 23.502 CR4694R1 (Rel-18, 'F'): Clarification on subscription retrieval during slice replacement | LG Electronics, Ericsson, Samsung, Lenovo | Rel-18 | Revision of S2-2400580r06 + clean up, merging S2-2401056. Approved | Agreed | |
| 9.11.2 | S2-2400581 | CR | Approval | 23.503 CR1249 (Rel-18, 'F'): Clarification on subscription retrieval during slice replacement | LG Electronics | Rel-18 | r02 + clean up Agreed. Revised to S2-2401517. | Jinguo (ZTE) suggests to use 0969 as basis for discussion Peter Hedman (Ericsson) provides comments Alessio(Nokia) asks a question for clarification: which PCF is contacted by the SMF? Also: if we consume the data rate of the alternative slice is it fair if the alternative slice is not subscribed (it damages the subscribers conceivably) Myungjune (LGE) replies to Peter (Ericsson), Alessio (Nokia) Jinguo(ZTE) response Alessio(Nokia) comments Alessio(Nokia) provides r01 Peter Hedman (Ericsson) provides r02 ==== Revisions Deadline ==== Myungjune (LGE) is ok with r02 Alessio(Nokia) is ok with r02 please add Nokia, Nokia Shanghai Bell when uploading ==== Final Comments Deadline ==== | Revised |
| 9.11.2 | S2-2401517 | CR | Approval | 23.503 CR1249R1 (Rel-18, 'F'): Clarification on subscription retrieval during slice replacement | LG Electronics, Ericsson, Nokia, Nokia Shanghai Bell | Rel-18 | Revision of S2-2400581r02 + clean up. Approved | Agreed | |
| 9.11.2 | S2-2401056 | CR | Approval | 23.502 CR4722 (Rel-18, 'F'): Clarification on SM Subscription data for PDU Session on Alternative S-NSSAI | Lenovo | Rel-18 | Check Affected Clauses! Merged into S2-2401516 | Haiyang (Huawei) suggests to use 0579 as basis Genadi (Lenovo) replies to Haiyang (Huawei). Let's discuss the concept and then agree whether to use 0579 or 1056 as baseline. Alessio(Nokia) replies to Genadi (Lenovo) and comments Peter Hedman (Ericsson) provides comments Genadi (Lenovo) comments that impacts to the UDM appear required. Jinguo(ZTE) also prefer not to impact the UDM. Genadi (Lenovo) replies to Alessio (Nokia). Alessio (Nokia) replies to. Genadi (Lenovo) Fenqin (Huawei) suggest to merge this paper to 0580 Genadi (Lenovo) agrees that this paper can be merge to 0580r03. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 9.11.2 | S2-2401051 | CR | Approval | 23.501 CR5285 (Rel-18, 'F'): Clarification on SM Subscription data for PDU Session on Alternative S-NSSAI | Lenovo | Rel-18 | Suggested merged with S2-2400579 (postponed). Postponed | Haiyang (Huawei) comments Peter Hedman (Ericsson) provides comments Fenqin (Huawei) suggest to merge this paper to 0579 Genadi (Lenovo) agrees to mark this paper as merged to 0579. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Postponed |
| 9.11.2 | S2-2400969 | CR | Approval | 23.503 CR1257 (Rel-18, 'F'): PCF related corrections to Network Slice Replacement | Ericsson | Rel-18 | r07 + changes Agreed. Revised to S2-2401518. | Myungjune (LGE) comments. Fenqin (Huawei) comments and provides r01. Myungjune (LGE) questions purpose of usage monitoring. Jinguo(ZTE) provides r02. Jinguo(ZTE) replies to Myungjune (LGE) Myungjune (LGE) is ok with Jinguo's proposal, i.e. usage monitoring for Alternative S-NSSAI is performed only when it is subscribed. Dongeun (Samsung) provide comments Peter Hedman (Ericsson) provides replies Alessio(Nokia) provides r03 that covers the comments by jinguo and Myungjune on usage monitoring Genadi (Lenovo) provides r04. Jinguo(ZTE) provides r05 Peter Hedman (Ericsson) provides comments to revisions Jinguo(ZTE) asks one question Peter Hedman (Ericsson) provides r06 Peter Hedman (Ericsson) provides r07 removing overlap with 0581 ==== Revisions Deadline ==== Myungjune (LGE) comments on r05/r06/r07. Peter Hedman (Ericsson) suggests to approve r07 + change 'based on the SUPI for a DNN and replaced S-NSSAI combination and additionally the SUPI for a DNN and Alternative S-NSSAI combination, until the Alternative S-NSSAI is not applicable any longer. The PCF shall stop monitoring control for both the DNN and Alternative S-NSSAI combination and start doing usage monitoring control only for the DNN and replaced S-NSSAI combination when the replaced S-NSSAI is available again' to 'based on the SUPI for a DNN and Alternative S-NSSAI combination or the SUPI for a DNN and replaced S-NSSAI combination. The PCF shall stop monitoring control for the DNN and Alternative S-NSSAI combination and start doing usage monitoring control for the DNN and replaced S-NSSAI combination when the replaced S-NSSAI is available again.' Myungjune (LGE) is ok with r07 + Peter's change in previous comment. ==== Final Comments Deadline ==== | Revised |
| 9.11.2 | S2-2401518 | CR | Approval | 23.503 CR1257R1 (Rel-18, 'F'): PCF related corrections to Network Slice Replacement | Ericsson | Rel-18 | Revision of S2-2400969r07 + changes. Approved | Agreed | |
| 9.11.2 | S2-2400966 | CR | Approval | 23.501 CR4583R4 (Rel-18, 'F'): Congestion handling with Alternative S-NSSAI | Ericsson | Rel-18 | Revision of (unhandled) S2-2312511. r05 Agreed. Revised to S2-2401519. | Haiyang (Huawei) provides comments Dongeun (Samsung) provides comments Jinguo(ZTE) provides comment Myungjune (LGE) provides comments. Peter Hedman (Ericsson) provides comments Genadi (Lenovo) supports the concept and provides suggestion to document the details in 23.502. Peter Hedman (Ericsson) provides reply to Genadi Genadi (Lenovo) provides r01. Peter Hedman (Ericsson) provides r02 Alessio(Nokia) provides r03 Genadi (Lenovo) is OK with r02. Peter Hedman (Ericsson) provides comments to r03 and to the question Dongeun (Samsung) provides r04 Myungjune (LGE) asks question on r04 Dongeun (Samsung) replies to Myungjune (LGE) Peter Hedman (Ericsson) provides question to Dongeun Peter Hedman (Ericsson) provides r05 ==== Revisions Deadline ==== Fenqin (Huawei) suggest to go with r05 and object r04 Dongeun (Samsung) answers to Peter Hedman (Ericsson) Peter Hedman (Ericsson) suggests to agree r05 ==== Final Comments Deadline ==== | Revised |
| 9.11.2 | S2-2401519 | CR | Approval | 23.501 CR4583R5 (Rel-18, 'F'): Congestion handling with Alternative S-NSSAI | Ericsson | Rel-18 | Revision of S2-2400966r05. Approved | Agreed | |
| 9.11.2 | S2-2400967 | CR | Approval | 23.502 CR4326R3 (Rel-18, 'F'): Congestion handling with Alternative S-NSSAI | Ericsson | Rel-18 | Revision of (unhandled) S2-2312512. r02 Agreed. Revised to S2-2401520. | Haiyang (Huawei) comments Alessio(Nokia) provides r01 Peter Hedman (Ericsson) provides r02 with AMF logic Alessio(Nokia) ok with r02 ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 9.11.2 | S2-2401520 | CR | Approval | 23.502 CR4326R4 (Rel-18, 'F'): Congestion handling with Alternative S-NSSAI | Ericsson | Rel-18 | Revision of S2-2400967r02. Approved | Agreed | |
| 9.11.2 | S2-2401028 | DISCUSSION | Discussion | On SMF selection for slice replacement . | Nokia, Nokia Shanghai Bell | Rel-18 | Revision of (unhandled) S2-2312987. Noted | Haiyang (Huawei) comments Peter Hedman (Ericsson) provides comments Genadi (Lenovo) provides comments. Alessio(Nokia) Replies to all comments ==== Revisions Deadline ==== | Noted |
| 9.11.2 | S2-2401030 | CR | Approval | 23.501 CR5053R2 (Rel-18, 'F'): SMF selection for network slice replacement | Nokia, Nokia Shanghai Bell | Rel-18 | Revision of (unhandled) S2-2312995. Noted | Haiyang (Huawei) comments Peter Hedman (Ericsson) provides comments and propose to not do SMF selection by UPF capabilities. Alessio(Nokia) our take is that in a network eventually many SMFs can be capable of replacement for two slices but only some may need to be able to choose a common UPF and control these shared UPFs (we do not think all SMFs in the two slices should be able to do so) Jinguo(ZTE) comment Alessio(Nokia) replies that since we need to downlod susbncription data of two slices and we need to contact PCR with two s_NSSAI we need to contact a SMF that is capable to handle slice replacement and for SSC 1 do SSC 1 for the two slice (as a preferfence) ==== Revisions Deadline ==== Haiyang (Huawei) suggests to note the paper Alessio(Nokia) disagrees with analysis by Huawei: we do not impact SMF selection policy (which anyhow has to take into account SSC mode) but the AMF policy to select SMFs that support SSC1 for the two slices. ==== Final Comments Deadline ==== | Noted |
| 9.11.2 | S2-2401034 | CR | Approval | 23.502 CR4540R2 (Rel-18, 'F'): SMF selection for network slice replacement | Nokia, Nokia Shanghai Bell | Rel-18 | Revision of (unhandled) S2-2312996. Noted | Haiyang (Huawei) comments Peter Hedman (Ericsson) see comments to 1030 and 1028 Alessio(Nokia) our take is that in a network eventually many SMFs can be capable of replacement for two slices but only some may need to be able to choose a common UPF and control these shared UPFs (we do not think all SMFs in the two slices should be able to do so) ==== Revisions Deadline ==== Haiyang (Huawei) suggests to note the paper Alessio(Nokia) disagrees with analysis by Huawei: we do not impact SMF selection policy (which anyhow has to take into account SSC mode) but the AMF policy to select SMFs that support SSC1 for the two slices. Peter Hedman (Ericsson) propose to note the CR as we see no reason to change the SMF selection wrt e.g. SSC mode and UPF capabilities ==== Final Comments Deadline ==== | Noted |
| 9.11.2 | S2-2401064 | DISCUSSION | Agreement | KI#1, Issues with Allowed NSSAI. | Nokia, Nokia Shanghai Bell | Rel-18 | Noted | Stefano (Qualcomm) Propose to note, see comments in S2-2401054. Alessio(Nokia) asks to consider the reply to comments in S2-2401054. The statements by Qualcomm are unrelated to the discussion on what to include in the allowed NSSAI which is in SA2 23.501. ==== Revisions Deadline ==== | Noted |
| 9.11.2 | S2-2401054 | CR | Approval | 23.501 CR5286 (Rel-18, 'F'): Clarification on Allowed NSSAI for network slice replacement | Nokia, Nokia Shanghai Bell | Rel-18 | r03 + changes Agreed. Revised to S2-2401521. | Fenqin (Huawei) provides r01 Stefano (Qualcomm) Propose to note. Jinguo(ZTE) comments Jinguo(ZTE) comments and propose to note Alessio(Nokia) provides clarifications so the CR can be approved as is in r00 (r01 text does not reflect the intention of the CR) Peter Hedman (Ericsson) proposes to note the CR Alessio(Nokia) disagree that other CRs cover what to do with the alternative S-NSSAI when it is only used for replacement and what logic applies when max of 8 would be overflown. Peter Hedman (Ericsson) would logic be different if replaced S-NSSAI is removed from Allowed NSSAI due to max 8 restriction vs due to other reasons? Alessio(Nokia) comments that when replacement is ongoing the Alternative s-NSSAI can be in allowed NSSAI only if the replaced S_NSSAI can be in the Allowed NSSAI. Otherwise the Alternative S-NSSAI starts having a life of its own and replaces no slice. Fenqin(Huawei) comments. Hoyeon (Samsung) provides comments. Genadi (Lenovo) comments that the replaced S-NSSAI is not required in the Allowed NSSAI. Peter Hedman (Ericsson) provides comments Jinguo(ZTE) provides r02 Myungjune (LGE) comments Alessio(Nokia) assumes that we should not keep the Alternative S-NSSAI in allowed NSSAI (due to slice replacement) if the replaced NSSAI would not be kept in the Allowed NSSAI in the event the causes of replacement did not happen. Logically it would make little sense as it means expanding the service area and availability by replacing slices ultimately. Dongeun (Samsung) provides r03 Alessio(Nokia) ok with r03 assuming the removal condition for replaced NSSAI is handled in another paper at this or a future meeting. Genadi (Lenovo) comments that there seem to be overlap between 1054 and 0970 r05/06 regarding the removal of the Alt S-NSSAI. Peter Hedman (Ericsson) provides reply to Genadi ==== Revisions Deadline ==== Jinguo(ZTE) propose to take at CC#3, simply remove the last sentence of the change'If thereplaced S-NSSAI is removed from the Allowed NSSAI, the AMF alsoremovesthe mapping of the replaced S-NSSAI to Alternative S-NSSAI andremovesthe Alternative S-NSSAI from the Allowed NSSAI and the Configured NSSAI if the Alternative S-NSSAI is only used forthenNetwork sSlice rReplacement.' Fenqin (Huawei) is ok open the 1054 during the CC#3. Myungjune (LGE) also supports Jinguo's proposal to open the 1054 during the CC#3. Genadi (Lenovo) supports Jinguo's proposal to open the 1054 during the CC#3. Peter Hedman (Ericsson) ok with r03 + remove sentence 'If the replaced S-NSSAI is removed from the Allowed NSSAI, the AMF also removes the mapping of the replaced S-NSSAI to Alternative S-NSSAI and removes the Alternative S-NSSAI from the Allowed NSSAI and the Configured NSSAI if the Alternative S-NSSAI is only used for Network Slice Replacement.' + co-signing companies. ==== Final Comments Deadline ==== | Revised |
| 9.11.2 | S2-2401521 | CR | Approval | 23.501 CR5286R1 (Rel-18, 'F'): Clarification on Allowed NSSAI for network slice replacement | Nokia, Nokia Shanghai Bell, Samsung | Rel-18 | Revision of S2-2401054r03 + changes. Approved | Agreed | |
| 9.11.2 | S2-2401050 | LS OUT | Approval | [DRAFT] LS on Clarification of Allowed NSSAI for network slice replacement | Nokia, Nokia Shanghai Bell | Rel-18 | Noted | Stefano (Qualcomm) Propose to note, see comments in S2-2401054. Alessio(Nokia) invites Qualcomm to check the reply to their comments in S2-2401054. Peter Hedman (Ericsson) provides r01 Genadi (Lenovo) provides r02. Alessio(Nokia) proposes to not discuss the LS anymore till we know the result of SA2 discussion. No need to ask CT1. Intention is to provide them input. ==== Revisions Deadline ==== Alessio(Nokia) asks to note ==== Final Comments Deadline ==== | Noted |
| 9.11.2 | - | - | - | KI#3 and KI#5 | - | - | Docs:=18 | - | |
| 9.11.2 | S2-2401009 | DISCUSSION | Discussion | KI#3: issues with normative text on support of non supporting UEs. | Nokia, Nokia Shanghai Bell | Rel-18 | Noted | Noted | |
| 9.11.2 | S2-2401011 | DISCUSSION | Agreement | KI#3 Allowed NSSAI behaviour. | Nokia, Nokia Shanghai Bell | Rel-18 | Noted | Noted | |
| 9.11.2 | S2-2401079 | DISCUSSION | Agreement | KI#5, KI#3 on decision to deactivate or release the PDU session at SMF. | Nokia, Nokia Shanghai Bell | Rel-18 | Noted | Noted | |
| 9.11.2 | S2-2401071 | DISCUSSION | Decision | Considerations partially Rejected and Allowed S-NSSAI handling from a RRM steering perspective [KI#5 and KI#3]. | Nokia, Nokia Shanghai Bell | Rel-18 | Revision of (unhandled) S2-2312978. Noted | Noted | |
| 9.11.2 | S2-2401107 | CR | Approval | 23.501 CR5292 (Rel-18, 'F'): Clarification on Network based monitoring and enforcement for NS-AoS and partially Allowed NSSAI | ZTE, LG Electronics., Samsung, Ericsson | Rel-18 | r07 Agreed. Revised to S2-2401522. | Fenqin(Huawei) provides comments. Jinguo(ZTE) provides r01 Jinguo(ZTE) comments that this topic has been discussed for several F2F meetings, Postpone to next meeting doesn't help in my view. Alessio(nokia) cannot accept r01 this topic should be postponed to next meeting as it is too difficult to resolve in this e-meeting. Fenqin(Huawei) provides r02. Ashok (Samsung) provides r03. Myungjune replies to Ashok (Samsung) . Ashok (Samsung) provides further clarification Jinguo(ZTE) replies to Ashok (Samsung) Ashok (Samsung) clarifies to Jinguo(ZTE) Ashok (Samsung) is not ok with r04 Jinguo(ZTE) provides r04 Myungjune (LGE) comments on r03. Ashok (Samsung) provides explanation Jinguo(ZTE) provides one example to Ashok (Samsung) Ashok (Samsung) thanks Jinguo(ZTE) for the example Jinguo(ZTE) provides r05 Jinguo(ZTE) provides r06 Fenqin (Huawei) provides r07 Jinguo(ZTE) asks question to Fenqin Fenqin (Huawei) responds Alessio(Nokia) cannot accept this paper. This mechanism is too complicated for the purpose. We need further discussion on the goal of all of this complexity Jinguo(ZTE) replies to Alessio(Nokia) and request for SoH at CC#3 ==== Revisions Deadline ==== Alessio(Nokia) believes the CR should provide a reason why this mechanism that is complicated is needed. Especially when the connected mode mobility is based on first and foremost on a message from RAN to SMF and the aMF cannot inspect the content of this message. We have serious concerns. Alessio(Nokia) replies to Jinguo(ZTE) | Revised |
| 9.11.2 | S2-2401522 | CR | Approval | 23.501 CR5292R1 (Rel-18, 'F'): Clarification on Network based monitoring and enforcement for NS-AoS and partially Allowed NSSAI | ZTE, LG Electronics., Samsung, Ericsson | Rel-18 | Used as a working assumption and work on these CRs further in February as needed. Revision of S2-2401107r07. Endorsed | Endorsed | |
| 9.11.2 | S2-2401108 | CR | Approval | 23.502 CR4725 (Rel-18, 'F'): Clarification on Network based monitoring and enforcement for NS-AoS and partially Allowed NSSAI | ZTE | Rel-18 | r07 Agreed. Revised to S2-2401523. | Fenqin(Huawei) provides comments. Peter Hedman (Ericsson) provides comments to Fenqin Jinguo(ZTE) replies to Fenqin(Huawei) Ashok (Samsung) comments Jinguo(ZTE) provides r01 Fenqin (Huawei) give a feedback Peter Hedman (Ericsson) ok with r01 and wants to co-sign Jinguo(ZTE) replies to Alessio(Nokia) Alessio(Nokia) cannot understand the rationale of subscribing an unsubscribing to Aoi reporting based on this indication or revocation of this indication. How I this used at SMF? Fenqin(Huawei) comments Ashok (Samsung) provides r02 and co-sign Jinguo(ZTE) provides r04 Jinguo(ZTE) provides r03 Myungjune (LGE) comments on r02 Jinguo(ZTE) provides r05 Ashok (Samsung) comments on r05 Fenqin (Huawei) comments Jinguo(ZTE) provides r06 Alessio(Nokia) also askes to postpone this as the mechanism is complicated and the SMF ue of this unclear. Especially why should we have updates to interrupt the subscription Jinguo(ZTE) replies to Alessio(Nokia) and request for SoH at CC#3 Fenqin(Huawei) is ok with r06 Jinguo(ZTE) provides r07 ==== Revisions Deadline ==== Alessio(Nokia) believes the CR should provide a reason why this mechanism that is complicated is needed. Especially when the connected mode mobility is based on first and foremost on a message from RAN to SMF and the aMF cannot inspect the content of this message. We have serious concerns. | Revised |
| 9.11.2 | S2-2401523 | CR | Approval | 23.502 CR4725R1 (Rel-18, 'F'): Clarification on Network based monitoring and enforcement for NS-AoS and partially Allowed NSSAI | ZTE, Samsung, Ericsson, LG Electronics | Rel-18 | Used as a working assumption and work on these CRs further in February as needed. Revision of S2-2401108r07. Endorsed | Endorsed | |
| 9.11.2 | S2-2401076 | CR | Approval | 23.501 CR5287 (Rel-18, 'F'): Clarifications on Network slice with NS-AoS not matching deployed TA and Partial Network Slice support in a Registration Area. | Nokia, Nokia Shanghai Bell | Rel-18 | Postponed | Jinguo(ZTE) provides comments Alessio(nokia) replies to Jinguo(ZTE) and provides comments Peter Hedman (Ericsson) provides comments and suggests to use 01107 Alessio(Nokia) does not agree that 'shall ' changes the NSAC logic, actually it keeps it as is. Should would change it and make the identification of exit from the NS-AoS impossible. Jinguo(ZTE) suggest to use 1076 to discuss 'should/shall' and use 1107 to address the EN Peter Hedman (Ericsson) provides comments to keep the should Alessio(Nokia) comments that the should was not discussed at all recently after it was inserted by a company in an unrelated CR ? and this went unnoticed. Ther CR does not change the NS-AoS definition, it clarifies it as it is already used as per this CR e.g in clause 5.15.19 Peter Hedman (Ericsson) provides additional comments and agree with Jinguo that the CR brings up aspects we already discussed multiple times. Jinguo(ZTE) suggest to merge this paper into 1107 Alessio(Nokia) proposes to postpone the topic to F2F ==== Revisions Deadline ==== Peter Hedman (Ericsson) propose to note the CR and postpone the NS-AoS definition aspects of the CR Alessio(Nokia) ok to postpone the CR Alessio(Nokia) OK to postpone. But really there are fundamental aspects not resolved in our specs like this NS-AoS definition people debate while it is already used in the spec as we define in this CR! (and of course other aspects) ==== Final Comments Deadline ==== | Postponed |
| 9.11.2 | S2-2400583 | CR | Approval | 23.501 CR4928R2 (Rel-18, 'F'): Alignment of non supporting UE handling for temporay slice and cell level slice | LG Electronics | Rel-18 | Revision of (unhandled) S2-2312578. Postponed | Jinguo(ZTE) provides comments Myungjune (LGE) replies to Jinguo (ZTE) Jinguo(ZTE) asks further question to Myungjune (LGE) Fenqin (Huawei) provides comments. Myungjune (LGE) replies to Jinguo (ZTE) and Fenqin (Huawei) Peter Hedman (Ericsson) provides comments Jinguo(ZTE) comments Ashok (Samsung) comments Fenqin(Huawei) provides further comment Myungjune (LGE) response to Fenqin(Huawei) and Ashok (Samsung) Ashok (Samsung) responds to Myungjune (LGE) Myungjune (LGE) replies to Ashok (Samsung) Alessio(Nokia) asks what is the FASMO issue to be resolved by this CR. We propose that if no FASMO issue is found this CR is noted. Myungjune (LGE) responds to Ashok (Samsung) Ashok (Samsung) provides further comments Myungjune (LGE) replies to Jinguo(ZTE) that there is no perfect solution for non supporting UEs. Jinguo(ZTE) comments that this new option is not perfect Myungjune (LGE) replies to Alessio(Nokia) Ashok (Samsung) clarifies to Myungjune (LGE) Myungjune (LGE) clarifies to Ashok (Samsung) ==== Revisions Deadline ==== Jinguo(ZTE) suggest to postpone this paper Alessio (nokia ) asks to note Myungjune (LGE) replies to Alessio (Nokia) Alessio(Nokia) thinks this is a CAT C CR so the issue is procedural and the fact it is not needed and may cause further issues to be discussed. We are past freeze. Myungjune (LGE) proposes to postpone and replies to Alessio (Nokia). Alessio(Nokia) objects this CR (to be very clear) ==== Final Comments Deadline ==== | Postponed |
| 9.11.2 | S2-2400972 | CR | Approval | 23.501 CR5278 (Rel-18, 'F'): Determination of release or deactivation of PDU Session due to S-NSSAI not supported | Ericsson | Rel-18 | r08 Agreed. Revised to S2-2401524. | Fenqin (Huawei) provides comments Peter Hedman (Ericsson) provides comments Peter Hedman (Ericsson) provides r01 Fenqin (Huawei) comments Peter Hedman (Ericsson) provides replies to Fenqin and r02 Alessio (nokia) provides r03 Jinguo(ZTE) comments on r02 Fenqin(Huawei) responds Peter Hedman (Ericsson) provides reply to Fenqin Peter Hedman (Ericsson) provides reply to Jinguo Peter Hedman (Ericsson) provides comments and r04 Fenqin (Huawei) give a further feedback Ashok (Samsung) comments on r04 Fenqin (Samsung) provides r05 Peter Hedman (Ericsson) provides reply to Ashok and r06 Ashok (Samsung) provides r07 Alessio provides replies to ericsson on why legacy impacting changes need a separate CR Alessio(Nokia) provides r08 which is what we can agree with only Fenqin (Huawei) comments. Peter Hedman (Ericsson) provides comments and ok with r08 ==== Revisions Deadline ==== Fenqin (Huawei) provides comments and live with r08 ==== Final Comments Deadline ==== | Revised |
| 9.11.2 | S2-2401524 | CR | Approval | 23.501 CR5278R1 (Rel-18, 'F'): Determination of release or deactivation of PDU Session due to S-NSSAI not supported | Ericsson | Rel-18 | Revision of S2-2400972r08. Approved | Agreed | |
| 9.11.2 | S2-2400973 | CR | Approval | 23.502 CR4718 (Rel-18, 'F'): Determination of release or deactivation of PDU Session due to S-NSSAI not supported | Ericsson | Rel-18 | Noted | Jinguo(ZTE) provides comments Fenqin (Huawei) provides comments Peter Hedman (Ericsson) provides comments Peter Hedman (Ericsson) provides reply to Fenqin and r01. Peter Hedman (Ericsson) provides r02 Alessio(Nokia) does not see the changes related to eNS_ph3 hence proposes to note. Peter Hedman (Ericsson) provides reply to Alessio that we are using these steps in multiple cases for eNS_Ph3 Ashok (Samsung) agrees with Alessio that all changes are not related to eNS_Ph3 Fenqin (Huawei) suggest to note this paper ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Noted |
| 9.11.2 | S2-2401043 | CR | Approval | 23.502 CR4528R2 (Rel-18, 'F'): Handling of UE initiated request when not present in area where slice is supported | Samsung | Rel-18 | Revision of (unhandled) S2-2312928. Postponed | Jinguo(ZTE) provides comments Myungjune (LGE) comments Fenqin (Huawei) share the same view as Myungjune and Jinguo. Ashok (Samsung) provides r01 Jinguo(ZTE) comments Ashok (Samsung) responds to Jinguo Peter Hedman (Ericsson) provides questions Alessio(Nokia) provides r02 Jinguo(ZTE) comments on r02 Ashok (Samsung) provides r03 Peter Hedman (Ericsson) provides r04 Ashok (Samsung) thanks Peter Hedman (Ericsson) for r04 and OK with it Myungjune (LGE) replies to Ashok (Samsung). Ashok (Samsung) comments Myungjune (LGE) comments r03 and r04 Ashok (Samsung) provides r05 Myungjune (LGE) provides r06 Fenqin (Huawei) agree it is SMF do the rejection. Alessio(Nokia) can accept r07 which we provide Fenqin (Huawei) comments. Ashok (Samsung) comments on revisions. Ashok (Samsung) replies to Jinguo(ZTE) Jinguo(ZTE) replies to Ashok (Samsung) ==== Revisions Deadline ==== Fenqin (Huawei) object r07 Myungjune (LGE) replies to Jinguo(ZTE) Alessio(Nokia) cannot really understand the objection as technically the failure of a SR is always at AMF. Ashok (Samsung) as author of the CR, after checking offline propose to approve r05 which is neutral and does not have AMF or SMF in the proposal. Alessio(Nokia) insists it is r07 or we postpone. The AMF knows all what the SMF could possibly know at reactivation time so the SMF cannot take conflicting decisions upon reactivation. Ashok (Samsung) provides explanation on r05 to Alessio (Nokia). Fenqin (Huawei) suggest to postpone. ==== Final Comments Deadline ==== | Postponed |
| 9.11.2 | S2-2401042 | CR | Approval | 23.501 CR4489R7 (Rel-18, 'F'): Registration status after S-NSSAI removal based on S-NSSAI validity time information | Samsung | Rel-18 | Revision of (unhandled) S2-2312920. r06 Agreed. Revised to S2-2401525. | Jinguo(ZTE) provides comments Peter Hedman (Ericsson) provides comments and suggests to let CT1 sort out the issue, see 00968 Ashok (Samsung) comments Peter Hedman (Ericsson) provides reply Alessio(nokia) provides r01 Peter Hedman (Ericsson) provides comments on r01 Myungjune (LGE) comments on r02 Ashok (Samsung) thanks Myungjune (LGE) for pointing out that r02 is not available, uploaded r02 Myungjune (LGE) points out that r02 is not available. Ashok (Samsung) provides r02 Ashok (Samsung) provides r03 Fenqin (Huawei) comments Peter Hedman (Ericsson) provides comments and see no need for guard timer, and provide r04 which is the similar text as in E/// previously submitted CR in 2312513 on the same topic. Ashok (Samsung) explains that r04 does not address the issue and hence not acceptable. Myungjune (LGE) responds to Ashok (Samsung) Ashok (Samsung) replies to Myungjune (LGE) Myungjune (LGE) is ok with r04 Myungjune (LGE) replies Alessio(Nokia) suggests a compromise Peter Hedman (Ericsson) provides reply to Ashok and explains that r04 addresses the problem Jinguo(ZTE) agree r04 is ok Ashok (Samsung) provides r05 Fenqin (Huawei) agree with r04 Ashok (Samsung) provides response to Jinguo Peter Hedman (Ericsson) provides r06 Ashok (Samsung) is fine with r06 Alessio(nokia) can live with r06 ==== Revisions Deadline ==== Jinguo(ZTE) can live with r06 Myungjune (LGE) is ok with r06 ==== Final Comments Deadline ==== | Revised |
| 9.11.2 | S2-2401525 | CR | Approval | 23.501 CR4489R8 (Rel-18, 'F'): Registration status after S-NSSAI removal based on S-NSSAI validity time information | Samsung, Ericsson | Rel-18 | Revision of S2-2401042r06. Approved | Agreed | |
| 9.11.2 | S2-2400968 | LS OUT | Approval | [DRAFT] LS on handling at expiry of S-NSSAI validity time | Ericsson | Rel-18 | Noted | Alessio(Nokia ) asks why we need to send this LS to CT1. It seems that we did not have papers on this at this meeting? if so we have concerns to send this LS. Ashok (Samsung) comments this LS to CT1 is not needed and the scenario need to be resolved at SA2 only. Peter Hedman (Ericsson) provides reply to Alessio Peter Hedman (Ericsson) ok to note the LS if CR in 01042 is approved ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Noted |
| 9.11.2 | S2-2400272 | CR | Approval | 23.503 CR1208R1 (Rel-18, 'F'): Correction on RFSP index generation | Huawei, HiSilicon | Rel-18 | Revision of (unhandled) S2-2312275. Approved | Agreed | |
| 9.11.2 | - | - | - | KI#6 | - | - | Docs:=13 | - | |
| 9.11.2 | S2-2400043 | LS In | Action | LS from CT WG1: Reply LS on Implementation of de-registration inactivity timer | CT WG1 (C1-239680) | Rel-18 | Noted | Jinguo(ZTE) suggests to note this LS | Noted |
| 9.11.2 | S2-2400584 | CR | Approval | 23.502 CR4452R2 (Rel-18, 'F'): Clarification on on demand slice | LG Electronics | Rel-18 | Revision of (unhandled) S2-2312579. r08 Agreed. Revised to S2-2401526. | Myungjune (LGE) provides r01. George Foti (Ericsson) provides comments Fenqin (Huawei) provides comments and r02. Ashok (Samsung) comments. Myungjune (LGE) replies to Fenqin (Huawei) and Ashok (Samsung). George (Ericsson) provides comments Myungjune (LGE) proposes to discuss two timer issue in S2-2400797. Alessio(Nokia) provides r03 Ashok (Samsung) responds to Myungjune (LGE) George (Ericsson) Not Ok with any revision Myungjune (LGE) provides r04 Fenqin (Huawei) provides r05 Myungjune (LGE) provides r06 George (Ericsson) provides r07, editorial in yellow. I no longer see any change in change 3. What happened ? Myungjune (LGE) provides r08 and replies George (Ericsson) that 3rd change is removed since it's covered in Fenqin's CR. Fenqin (Huawei) is ok with r08. Alessio(Nokia) is ok with r08. ==== Revisions Deadline ==== George (Ericsson) Accepts R08 ONLY. ==== Final Comments Deadline ==== | Revised |
| 9.11.2 | S2-2401526 | CR | Approval | 23.502 CR4452R3 (Rel-18, 'F'): Clarification on on demand slice | LG Electronics | Rel-18 | Revision of S2-2400584r08. Approved | Agreed | |
| 9.11.2 | S2-2400797 | CR | Approval | 23.501 CR5265 (Rel-18, 'F'): Clarification on Network Slice usage control timer | Huawei, HiSilicon | Rel-18 | r01 Agreed. Revised to S2-2401527. | Myungjune (LGE) comments. Fenqin (Huawei) responds. Ashok (Samsung) comments. Myungjune (LGE) replies to Fenqin (Huawei). Fenqin (Huawei) responds to Ashok and Myungjune. Myungjune (LGE) response to Fenqin (Huawei). George (Ericsson) provides comments Fenqin (Huawei) give a feedback Myungjune replies to Fenqin (Huawei) Fenqin (Huawei) replies to Myungjune Myungjune replies to Fenqin (Huawei). Alessio(nokia) provides a comment Fenqin (Huawei) provides further feedback to Myungjune Myungjune (LGE) is ok with r01 Fenqin (Huawei) provides feedback Fenqin (Huawei) provides r01 Myungjune (LGE) provides feedback to Fenqin (Huawei) George (Ericsson) provides OK with r01 Alessio(nokia) OK with r01 ==== Revisions Deadline ==== George (Ericsson) Accepts R01 ONLY ==== Final Comments Deadline ==== | Revised |
| 9.11.2 | S2-2401527 | CR | Approval | 23.501 CR5265R1 (Rel-18, 'F'): Clarification on Network Slice usage control timer | Huawei, HiSilicon | Rel-18 | Revision of S2-2400797r01. Approved | Agreed | |
| 9.11.2 | S2-2400798 | CR | Approval | 23.502 CR4712 (Rel-18, 'F'): Clarification on Network Slice usage control timer | Huawei, HiSilicon | Rel-18 | r02 Agreed. Revised to S2-2401528. | George Foti (Ericsson) provides comments Fenqin (Huawei) responds Myungjune (LGE) proposes to merge this CR into S2-2400584. George (Ericsson) provides response inline. Alessio(nokia) proposes this CR is noted as the 501 behavior on application of the timer. The two timers topic seems difficult to resolve by e-meeting Fenqin (Huawei) provides r01 George (Ericsson) provides comments to Fenqin Myungjune (LGE) provides r02 Alessio(nokia) OK with r02 Fenqin (Huawei) is OK with r02 Ashok (Samsung) is fine with r02 ==== Revisions Deadline ==== George (Ericsson) Accepts R02 ONLY ==== Final Comments Deadline ==== | Revised |
| 9.11.2 | S2-2401528 | CR | Approval | 23.502 CR4712R1 (Rel-18, 'F'): Clarification on Network Slice usage control timer | Huawei, HiSilicon | Rel-18 | Revision of S2-2400798r02. Approved | Agreed | |
| 9.11.2 | S2-2400909 | CR | Approval | 23.501 CR5269 (Rel-18, 'F'): Network slice usage control in case of emergency call alt1 | NTT DOCOMO | Rel-18 | Noted | George Foti (Ericsson) proposes to note this CR. 1106 is all what is needed ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Noted |
| 9.11.2 | S2-2400916 | CR | Approval | 23.501 CR5270 (Rel-18, 'F'): Network slice usage control in case of emergency call alt2 | NTT DOCOMO | Rel-18 | Noted | George Foti (Ericsson) proposes to note this CR. 1106 is all what is needed ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Noted |
| 9.11.2 | S2-2400917 | CR | Approval | 23.501 CR5271 (Rel-18, 'F'): Network slice usage control in case of emergency call alt2-1 | NTT DOCOMO | Rel-18 | Noted | George Foti (Ericsson) proposes to note this CR. 1106 is all what is needed ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Noted |
| 9.11.2 | S2-2400921 | CR | Approval | 23.501 CR5272 (Rel-18, 'F'): Default Subscribed S-NSSAIs for Network Slice usage monitoring | NTT DOCOMO | Rel-18 | Postponed | George Foti (Ericsson) proposes to note this CR. 1106 is all what is needed Jinguo(ZTE) provides comments and suggest to note. Fenqin(Huawei) agree with the view from Jinguo and George. Tsuyoshi(NTT DOCOMO) provides comments. Jinguo(ZTE) replies Tsuyoshi(NTT DOCOMO) replies and provides r01 Alessio(Nokia) asks that the FASMO issue be identified before considering approval of this CR. Jinguo(ZTE) replies to Tsuyoshi(NTT DOCOMO) George (Ericsson) responds Tsuyoshi (NTT DOCOMO) responds Myungjune (LGE) replies to Tsuyoshi (NTT DOCOMO) George (Ericsson) I am OK with a note but not more than that. Tsuyoshi (NTT DOCOMO) asks clarification. Jinguo(ZTE) replies to Tsuyoshi (NTT DOCOMO) Ashok (Samsung) responds to Tsuyoshi Tsuyoshi (NTT DOCOMO). I would like to postpone the CR. Alessio(Nokia) ok to postpone the CR. ==== Revisions Deadline ==== Tsuyoshi (NTT DOCOMO) postpones the CR. George (Ericsson) proposes to note the CR | Postponed |
| 9.11.2 | S2-2401106 | CR | Approval | 23.501 CR5291 (Rel-18, 'F'): Network Slice usage control for emergency service | ZTE | Rel-18 | r08 + clean up Agreed. Revised to S2-2401529. | Fenqin(Huawei) provides r01. Myungjune (LGE) comments. Tsuyoshi (NTT DOCOMO) comments. Jinguo(ZTE) replies Ashok (Samsung) agrees with Jinguo. George (Ericsson) provides a comment Myungjune (LGE) asks question on emergency registered UE. Tsuyoshi(NTT DOCOMO) provides comments. Jinguo(ZTE) provides r02. Myungjune (LGE) provides r03. George (Ericsson) provides comments Jinguo(ZTE) provides r04 Alessio(Nokia) thinks all revisions so fare are confusing: Tsuyoshi(NTT DOCOMO) provides r05 George (Ericsson) both revisions are not OK Jinguo(ZTE) is fine with Myungjune (LGE) proposal Myungjune (LGE) comments on r06 Jinguo(ZTE) provides r06 Jinguo(ZTE) provides r07 Tsuyoshi (NTT DOCOMO). I am OK with r07. George (Ericsson) provides r08. Linguistic improvement. Jinguo(ZTE) is ok with r08. Tsuyoshi(NTT DOCOMO) is ok with r08. ==== Revisions Deadline ==== Jinguo(ZTE) thinks the current r08 is ok, we just need to clearn up change marks when uploading the final version. Myungjune (LGE) comments that r08 shows revision mark. Genadi (Lenovo) comments that r08 doesn't have change marks - it is not clear which is the new text in the CR. We need a revision. ==== Final Comments Deadline ==== | Revised |
| 9.11.2 | S2-2401529 | CR | Approval | 23.501 CR5291R1 (Rel-18, 'F'): Network Slice usage control for emergency service | ZTE, LG Electronics, NTT DOCOMO | Rel-18 | Revision of S2-2401106r08 + clean up. Approved | Agreed | |
| 9.12.2 | - | - | - | XR (Extended Reality) and media services (XRM) | - | - | Docs:=86 | - | |
| 9.12.2 | S2-2400059 | LS In | Information | LS from RAN WG3: LS on defining new GTP-U Extension Header for PDU Set related information | RAN WG3 (R3-237845) | Rel-18 | Postponed | Chris (Vodafone) asks whether we should update the 5GC spec that describes the max GTP-U payload that avoids IP-fragmentation over typical Ethernet. Dan(China Mobile) suggest to postpond this LS to next meeting, and maybe consider to solve it in next meeting Chris (Vodafone) replies to Dan(China Mobile) and agrees to postpone this LS to next meeting, and maybe consider CRs then | Postponed |
| 9.12.2 | - | - | - | LS from SA WG4 for out of order for the end PDU | - | - | Docs:=14 | - | |
| 9.12.2 | S2-2400069 | LS In | Action | LS from SA WG4: LS on out of order reception for the end PDU of PDU Set/Data Burst | SA WG4 (S4-231955) | Rel-18 | Responses drafted in S2-2400181, S2-2400239, S2-2400593, S2-2400818, S2-2401152, S2-2401205. CC#4: CC#4: Final response in S2-2401841. | Replied to | |
| 9.12.2 | S2-2400818 | LS OUT | Approval | [DARFT] LS Reply on out of order reception for the end PDU of PDU Set/Data Burst | Huawei, HiSilicon | Rel-18 | Response to S2-2400069. Noted | Devaki (Nokia) objects to the proposed DRAFT reply LS. Hui (Huawei) : The reason of previous objection is not correct. Paul (Ericsson) : there is no need for a response LS as there is no action for SA2. The issue of PDUs being received on N6 out of order is documented in TS 23.501. Mukesh (MediaTek) suggests rephrasing the proposed draft LS to simply acknowledge PDU(s) associated to a data burst can be received after the PDU with End of Bust indication. Dario (Session chair) proposes to move the discussion for the LS out to S2-2400593 Hui (Huawei) is ok to continue the discussion in S2-2400593 ==== Revisions Deadline ==== | Noted |
| 9.12.2 | S2-2400181 | LS OUT | Approval | [DRAFT] Reply LS on out of order reception for the end PDU of PDU Set/Data Burst | vivo | Rel-18 | Response to S2-2400069. Noted | Devaki (Nokia) proposes to consider this as merged with 593. Dan(China Mobile) suggest to merge this paper into 0593 Xiaowan Ke(vivo) is ok to merge this paper into S2-2400593 and keep one email thread discussion Dario (Session chair) proposes to keep the discussion for the LS out in S2-2400593 ==== Revisions Deadline ==== | Noted |
| 9.12.2 | S2-2400239 | LS OUT | Approval | [DRAFT] LS Reply on out of order reception for the end PDU of PDU Set/Data Burst | CATT | Rel-18 | Response to S2-2400069. Noted | Devaki (Nokia) proposes to consider this as merged with 593. Chunshan (CATT) agrees to be merged into 593. Dario (Session chair): OK, let's move the discussion for the LS out to S2-2400593 ==== Revisions Deadline ==== | Noted |
| 9.12.2 | S2-2400593 | LS OUT | Approval | [DRAFT] Reply LS on out of order reception for the end PDU of PDU Set/Data Burst | China Mobile | Rel-18 | Response to S2-2400069. CC#4: r10 agreed. Revised to S2-2401841. | Devaki (Nokia) proposes to use LS out as the baseline (and merge or note all other related draft LS response). Dan (China Mobile) suggest to use this paper as baseline for the LS reply to SA4 Dario (Session chair): let's take keep the discussion for the LS out in this thread (00593) Mike (InterDigital) comments Chunshan(CATT) provides r01. Lei(Tencent) provide comments to r00 and r01. Dan(China Mobile) provide r02 to reflect the CR discussion . Lei(Tencent) appreicates Dan(China Mobile)'s update and is fine with r02. Chunshan(CATT) provide r03 to reflect the CR discussion . Mike (InterDigital) provides r05 ==== Revisions Deadline ==== Jinhua (Xiaomi) comments, r06 is prefer. Essential points are recapitulated. Dan (China Mobile) provide new version r06=r04+removing'The detailed information can be found in the attachment.'. Devaki (Nokia) can accept r00 or r01 only. R05 and other versions add unnecessary details, can live with it in the interest of progress without the attachment and the reference to the attachment. Mike (InterDigital) supports r00, r01, and r05. Comments that r06 is missing information. Proposes r05+the answer is changed to just 'Reordering is not specified in the 5GS'. Dan (China Mobile) check with Mike Mike (InterDigital) responds to Dan (China Mobile) Dan (China Mobile) provide r07=r04+removing'The detailed information can be found in the attachment.'.+'Furthermore, re-ordering may also occur on the N3/N9 interfaces.' Dan (China Mobile) provide r08=r04+removing'The detailed information can be found in the attachment.'.+'Furthermore, re-ordering may also occur on the N3/N9 interfaces.'+removing the attachement. Mike (InterDigital) supports the latest proposal from Dan (China Mobile) (r08) Chunshan(CATT) concerns the texts 'furthermore, re-ordering may also occur on the N3/N9 interfaces.' and provides r09. Mike (InterDigital) prefers r08 and can live with r09. ==== Final Comments Deadline ==== Dan(China Mobile) request to discuss this in CC#4. Dan (China Mobile) OK with r09. Dan(China Mobile) suggest to approve r09= The reply to SA4: If DL PDUs of a PDU Set are received out of sequence (including PDU dropped), the handling of re-ordering is not specified in 5GS.And without the attachment | Revised |
| 9.12.2 | S2-2401841 | LS OUT | Approval | Reply LS on out of order reception for the end PDU of PDU Set/Data Burst | SA WG2 | Rel-18 | Revision of S2-2400593r10. Approved | Approved | |
| 9.12.2 | S2-2401152 | LS OUT | Approval | [DRAFT] Reply LS on out of order reception for the end PDU of PDU Set or Data Burst | OPPO | Rel-18 | Response to S2-2400069. Noted | Devaki (Nokia) has concerns/objections to the original version of the DRAFT LS proposed. Devaki (Nokia) proposes to consider this as merged with 593. Boren (OPPO) replies to Devaki (Nokia). Dan(China Mobile) suggest to merge this paper into 0593 Boren (OPPO) is fine to merge this paper into 0593. Dario (Session chair) proposes to move the discussion for the LS out to S2-2400593 ==== Revisions Deadline ==== | Noted |
| 9.12.2 | S2-2401150 | DISCUSSION | Information | Discussion on the out of order reception for the end PDU of PDU Set/Data Burst. | OPPO | Rel-18 | Noted | Noted | |
| 9.12.2 | S2-2401205 | LS OUT | Approval | [DRAFT] LS Reply on out of order reception for the end PDU of PDU Set/Data Burst | Xiaomi | Rel-18 | Response to S2-2400069. Noted | Devaki (Nokia) proposes to consider this as merged with 593. Jinhua (Xiaomi) replies to Devaki, merged into 0818 or 0593 are both fine. Hui's clarification in 0817 is prefer. Jinhua (Xiaomi) replies to Dario, merged into 0593 for discussion is OK. Dario (Session chair) proposes to move the discussion for the LS out to S2-2400593 ==== Revisions Deadline ==== | Noted |
| 9.12.2 | S2-2400817 | CR | Approval | 23.501 CR5266 (Rel-18, 'F'): Out of order reception for the end PDU of PDU Set/Data Burst | Huawei, HiSilicon | Rel-18 | Noted | Hui (Huawei) provides r01. Paul (Ericsson) objects to S2-2400817 in r00 and r01. The issue is already documented in the existing NOTE in 5.37.8.3. The actions to address it are up to implementation choices. No additional text is needed. Chunshan (CATT) questions on the r00 and r01. Hui (Huawei) replies to Chunshan. Hui (Huawei) replies to Paul. Jari (NTT DOCOMO) comments Mukesh (MediaTek) objects to S2-2400817 r00 and r01. The additional normative text in the Note (4&X) is not necessary. Hyunsook (LGE) prefers the simple text on UPF implementation (if the new NOTE is necessary). ==== Revisions Deadline ==== Devaki (Nokia) objects to all versions of this CR. No need for a NOTE to state it is to UPF implementation as even otherwise it is. Hui (Huawei) replies. ==== Final Comments Deadline ==== | Noted |
| 9.12.2 | S2-2400184 | CR | Approval | 23.501 CR5216 (Rel-18, 'F'): Clarification and alignment on out of order receiption issue in N6 link | Tencent, Tencent Cloud | Rel-18 | Merge into S2-2400817 (Noted). Noted | Dan (China Mobile) suggest to merge this paper into 0817. Lei (Tencent) is fine to merge this paper into 0817 and think a CR is benefitical to reflect SA2 common understanding. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Noted |
| 9.12.2 | S2-2400320 | CR | Approval | 23.501 CR5227 (Rel-18, 'F'): Handling of out of order reception | Vivo | Rel-18 | Merge into S2-2400817 (Noted). Noted | Dan (China Mobile) suggest to merge this paper into 0817. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Noted |
| 9.12.2 | S2-2401151 | CR | Approval | 23.501 CR5293 (Rel-18, 'F'): Clarification on the out of order reception for the end PDU of PDU Set/Data Burst | OPPO | Rel-18 | Merge into S2-2400817 (Noted). Noted | Dan (China Mobile) suggest to merge this paper into 0817. Boren (OPPO) is fine to merge this paper into 0817. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Noted |
| 9.12.2 | S2-2401206 | CR | Approval | 23.501 CR5296 (Rel-18, 'F'): Clarification on out of order reception for the end PDU of PDU Set and Data Burst | Xiaomi | Rel-18 | Merge into S2-2400817 (Noted). Noted | Hui (Huawei) suggests to take S2-2400817 for discussion and consider this paper as merged into S2-2400817. Jinhua (Xiaomi) replies to Hui, merged 1206 into 0817 is OK. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Noted |
| 9.12.2 | - | - | - | LS from CT WG4 for packet delay measurement | - | - | Docs:=10 | - | |
| 9.12.2 | S2-2400013 | LS In | Action | LS from CT WG4: LS on packet delay measurement | CT WG4 (C4-234616) | Rel-18 | Revision of Postponed S2-2311961 from SA WG2#160. Response drafted in S2-2400368, S2-2401102. Final response in S2-2401403 | Replied to | |
| 9.12.2 | S2-2400369 | DISCUSSION | Agreement | On Questions raised by CT WG4 LS on packet delay measurement (S2-2400013 / C4-234616). | Ericsson | Rel-18 | Noted | Noted | |
| 9.12.2 | S2-2400368 | LS OUT | Approval | [DRAFT] Reply LS on packet delay measurement | Ericsson | Rel-18 | Response to S2-2400013. r02 Agreed. Revised to S2-2401403, merging S2-2401102 | Jinguo(ZTE) provides r01 Paul (Ericsson) provides r02. ==== Revisions Deadline ==== Devaki (Nokia) comments r02 is fine. Paul (Ericsson) object r01. ==== Final Comments Deadline ==== | Revised |
| 9.12.2 | S2-2401403 | LS OUT | Approval | Reply LS on packet delay measurement | SA WG2 | Rel-18 | Response to S2-2400013, merging S2-2401102. Revision of S2-2400368r02. Approved | Approved | |
| 9.12.2 | S2-2401102 | LS OUT | Approval | [DRAFT] Reply LS on packet delay measurement | ZTE | Rel-18 | Response to S2-2400013. Merged into S2-2401403 | Dan (China Mobile) suggest to merge this paper into 0368. Devaki (Nokia) agrees with Dan that this paper can be merged with 368. Dario (Session chair) proposes to move the discussion for this LS to CT4 to 0368 ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 9.12.2 | S2-2400367 | CR | Approval | 23.501 CR5082R2 (Rel-18, 'F'): Correction of UPF reporting of QoS Monitoring packet delay | Ericsson, Huawei, Nokia, Nokia Shanghai Bell | Rel-18 | Revision of (postponed) S2-2313346. r02 Agreed. Revised to S2-2401402, merging S2-2401103 | Jinguo(ZTE) comments Paul (Ericsson) provides r01. Jinguo(ZTE) is fine with r01. Hyunsook (LGE) asks clarificastions. Mirko (Huawei) responds. Hyunsook (LGE) makes a suggestion for the NOTE wording. Mirko (Huawei) responds and proposes another wording for the note. Hyunsook (LGE) can like with Mirko's rewording. Mirko (Huawei) provides r02. ==== Revisions Deadline ==== Devaki (Nokia) comments r02 is fine. ==== Final Comments Deadline ==== | Revised |
| 9.12.2 | S2-2401402 | CR | Approval | 23.501 CR5082R3 (Rel-18, 'F'): Correction of UPF reporting of QoS Monitoring packet delay | Ericsson, Huawei, Nokia, Nokia Shanghai Bell | Rel-18 | Revision of S2-2400367r02, merging S2-2401103. Approved | Agreed | |
| 9.12.2 | S2-2401103 | CR | Approval | 23.501 CR5289 (Rel-18, 'F'): Correction of UPF reporting of QoS Monitoring packet delay | ZTE | Rel-18 | Merged into S2-2401402 | Dan (China Mobile) suggest to merge this paper into 0367. Jinguo(ZTE) is ok to merge into 0367 and discuss technique issue in 0367 ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 9.12.2 | S2-2401104 | CR | Approval | 23.503 CR1261 (Rel-18, 'F'): Correction of UPF reporting of QoS Monitoring packet delay | ZTE | Rel-18 | r02 Agreed. Revised to S2-2401404. | Jinguo(ZTE) provides r01. Jinguo(ZTE) provides r02, correct the cover page ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 9.12.2 | S2-2401404 | CR | Approval | 23.503 CR1261R1 (Rel-18, 'F'): Correction of UPF reporting of QoS Monitoring packet delay | ZTE | Rel-18 | Revision of S2-2401104r02. Approved | Agreed | |
| 9.12.2 | - | - | - | LS from RAN WG2 & CT WG1 for PDU set UL handling | - | - | Docs:=6 | - | |
| 9.12.2 | S2-2400018 | LS In | Action | LS from RAN WG2: LS on XR awareness | RAN WG2 (R2-2311590) | Rel-18 | Revision of Postponed S2-2311981 from SA WG2#160. Responses drafted in S2-2400180, S2-2400813. Final response in S2-2401405 | Replied to | |
| 9.12.2 | S2-2400010 | LS In | Action | LS from CT WG1: LS on uplink PDU Set | CT WG1 (C1-237936) | Rel-18 | Revision of Postponed S2-2311953 from SA WG2#160. Responses drafted in S2-2400180, S2-2400814. Final response in S2-2401405 | Replied to | |
| 9.12.2 | S2-2400180 | LS OUT | Approval | [DRAFT] Reply LS on XR awareness and LS on uplink PDU Set | vivo | Rel-18 | Revision of (postponed) S2-2313677. Response to S2-2400010, S2-2400018. r05 + changes Agreed. Revised to S2-2401405, merging S2-2400813 and S2-2400814 | Dan (China Mobile) provide r01. Sebastian (Qualcomm) provides r02 Sudeep (Apple) also thinks that question to RAN2 is not needed. Devaki (Nokia) fine with r02. Agree that the question must be removed as in r01 as already commented. Paul (Ericsson) we are ok with r02. Xiaowan Ke(vivo) is OK with r02 Xiaowan Ke(vivo) provides r03 Mukesh (MediaTek) provides r04 Xiaowan Ke(vivo) disagree with r04 since CR has been implemented into the spec and not attached. r04 make other WG difficult to find out what has been replied by SA2 Xiaowan Ke(vivo) provides r05 ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 9.12.2 | S2-2401405 | LS OUT | Approval | Reply LS on XR awareness and LS on uplink PDU Set | SA WG2 | Rel-18 | Response to S2-2400010 and S2-2400018. Revision of S2-2400180r05 + changes, merging S2-2400813 and S2-2400814. Approved | Approved | |
| 9.12.2 | S2-2400813 | LS OUT | Approval | [DRAFT] LS Reply on XR awareness | Huawei, HiSilicon | Rel-18 | Revision of (unhandled) S2-2312955. Response to S2-2400018. Merged into S2-2401405 | Dan (China Mobile) suggest to merge this paper into 0180. Devaki (Nokia) proposes to consider this paper as the baseline for the LS response. Dan (China Mobile) suggest to reply RAN2 and CT1 in one LS, and last meeting we select vivo's LS as feedback, so it is suggest to also use the revision of S2-2400180. Xiaowan Ke(vivo) agrees with Dan (China Mobile) that a reply LS to CT and RAN is sufficient and suggests to merge S2-2400813 to 2400180. Devaki (Nokia) comments. Xiaowan Ke(vivo) replies to Devaki (Nokia) Hui (Huawei) fine with merging this into S2-2400810. Dario (Session chair): let's then merge this into 00810 Jinhua (Xiaomi) comments, 0813 should be merged into 0180, not 0810 ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 9.12.2 | S2-2400814 | LS OUT | Approval | [DRAFT] LS Reply on uplink PDU Set | Huawei, HiSilicon | Rel-18 | Revision of (unhandled) S2-2312956. Response to S2-2400010. Merged into S2-2401405 | Dan (China Mobile) suggest to merge this paper into 0180. Devaki (Nokia) proposes to consider this paper as the baseline for the LS response. Xiaowan Ke(vivo) comments that a reply LS to CT and RAN is sufficient and suggests to merge S2-2400814 to 2400180. Hui (Huawei) fine with merging. Dario (Session chair): let's then merge this one as well into 00810 Jinhua (Xiaomi) comments, 0814 should be merged into 0180, not 0810 ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 9.12.2 | - | - | - | General | - | - | Docs:=5 | - | |
| 9.12.2 | S2-2400594 | CR | Approval | 23.501 CR5245 (Rel-18, 'F'): Corrections of XRM related clauses | China Mobile | Rel-18 | CC#4: r08 agreed. Revised, merging S2-2400760, S2-2401208, S2-2401207, to S2-2401656. | Youngkyo(Samsung) requests further changes. Dan (China Mobile) provides r01 with merging 0760, 1208,1207 Dan(China Mobile) provide r02, and response for the first change proposal. Youngkyo(Samsung) replies. Dan(China Mobile) replies. Jinhua (Xiaomi) replies to Dan, merged 1208 and 1207 into 0594 is ok, and comments about the NEF exposure, Hui(Huawei) provides comments to r01 and r02. Devaki (Nokia) comments, has concerns with many changes in this paper e.g. generalizing technical feature to state XR services, removing QoS from PDU Set based handling. Sudeep (Apple) shares similar view as Devaki (Nokia). Changes in clause 6.2.2, 6.2.5.0 and 6.2.10 are not required. Youngkyo(Samsung) asks a question to Hui's comment. Mengzhen (China Telecom) comments. Dan (China Mobile) comments and provide r04 Youngkyo(Samsung) requests further clarification. Dan(China Mobile) reply Hui(Huawei) replies to Youngkyo. Hui(Huawei) provides r05 Jinhua (Xiaomi) comments with R06, and replies to mengzhen, Sudeep and Devaki, Youngkyo(Samsung) replies to Devaki.. Devaki (Nokia) objects to r06 (as it is changing congestion reporting for target RAN node) but provides r07. Dan(China Mobile) suggest to go with r07 Paul (Ericsson) proposes to postpone this CR. Dan (China Mobile) reply. Lei (Tencent) proposes to leave out the changes which still have not consensus and agree a verison. Postponing to next meeting will also occupy next meeting's slot:-) Paul (Ericsson) provides comments. Dan (China Mobile)provide r08,removing all the ECN related part. Dan(China Mobile) provides comments. ==== Revisions Deadline ==== Hui(Huawei) prefers to r07, objects to r00-r04. ==== Final Comments Deadline ==== Dan(China Mobile) suggest to approve r08. Hui(Huawei) fine with r08. | Revised |
| 9.12.2 | S2-2401656 | CR | Approval | 23.501 CR5245R1 (Rel-18, 'F'): Corrections of XRM related clauses | China Mobile,Samsung,Tencent, Tencent Cloud | Rel-18 | Revision of S2-2400594r08, merging S2-2400760, S2-2401208, S2-2401207. Approved | Agreed | |
| 9.12.2 | S2-2400760 | CR | Approval | 23.501 CR5259 (Rel-18, 'F'): Correction on XRM description | Samsung | Rel-18 | Merge into S2-2400594 (For CC#4) CC#4: Merged into S2-2401656. | Hui (Huawei) suggests to merge this paper into S2-2400594. Youngkyo(Samsung) is okay to merge this paper into S2-2400594. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 9.12.2 | S2-2401208 | CR | Approval | 23.501 CR5178R1 (Rel-18, 'F'): Update the XRM Service Supporting of SMF and AF | Xiaomi | Rel-18 | Merge into S2-2400594 (For CC#4) Revision of (unhandled) S2-2312857. CC#4: Merged into S2-2401656. | Hui (Huawei) suggests to merge this paper into S2-2400594. Jinhua (Xiaomi) replies to Hui, merged into 0594 is OK. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 9.12.2 | S2-2401207 | CR | Approval | 23.501 CR5176R1 (Rel-18, 'F'): Corrections on NEF Functionality with XRM | Xiaomi | Rel-18 | Merge into S2-2400594 (For CC#4) Revision of (unhandled) S2-2312855. CC#4: Merged into S2-2401656. | Dan(China Mobile) suggest to merge this paper into 0594 Jinhua (Xiaomi) replies to Dan, merged into 0594 is OK. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 9.12.2 | - | - | - | KI#1 & 2 Multi-modal service | - | - | Docs:=6 | - | |
| 9.12.2 | S2-2400686 | CR | Approval | 23.501 CR5255 (Rel-18, 'F'): Clarifications for multi-modal services | Huawei, HiSilicon | Rel-18 | Noted | Paul (Ericsson) objects to S2-2400686 in all revisions. This CR does not correct any errors. Dan (China Mobile) objects to S2-2400686, we do not agree to change the term . ==== Revisions Deadline ==== | Noted |
| 9.12.2 | S2-2400685 | CR | Approval | 23.502 CR4702 (Rel-18, 'F'): Clarifications for multi-modal services | Huawei, HiSilicon | Rel-18 | Postponed | Paul (Ericsson) objects to S2-2400685 in r00. Mirko (Huawei) responds to the comments. Georgios (Nokia) provides comments and does not agree with reverting previously agreed text Mengzhen (China Telecom) shares Georgios (Nokia)'s view. Dan (China Mobile) shares Georgios (Nokia)'s and Mengzhen (China Telecom)'s view. Mirko (Huawei) is ok to postpone the CR. ==== Revisions Deadline ==== | Postponed |
| 9.12.2 | S2-2401189 | CR | Approval | 23.502 CR4730 (Rel-18, 'F'): Properly define the update of the Multi-modal Service Requirements | Nokia, Nokia Shanghai Bell, [Ericsson], [Deutsche Telekom] | Rel-18 | Revised to S2-2401233 | Revised | |
| 9.12.2 | S2-2401233 | CR | Approval | 23.502 CR4730R1 (Rel-18, 'F'): Support updating Multi-modal Service Requirements | Nokia, Nokia Shanghai Bell, [Ericsson], [Deutsche Telekom] | Rel-18 | Revision of S2-2401189. Postponed | Dan (China Mobile) suggest to merge this paper into S2-2400685 Georgios (Nokia) proposes to wait for the moment Mirko (Huawei) comments and proposes to postpone the CR. Georgios (Nokia) replies to Mirko and agrees to POSTPONE both S2-2401233 and S2-2400685 ==== Revisions Deadline ==== | Postponed |
| 9.12.2 | S2-2400684 | CR | Approval | 23.503 CR1251 (Rel-18, 'F'): Clarifications for multi-modal services | Huawei, HiSilicon | Rel-18 | Noted | Jari (NTT DOCOMO) comments Dan (China Mobile) suggest to merge this paper into S2-2401188 Paul (Ericsson) objects to S2-2400684r00. Mirko (Huawei) responds to the comments and provides r01. Jari (NTT DOCOMO) proposes to merge with S2-2401188 ==== Revisions Deadline ==== Georgios (Nokia) proposes to merge with S2-2401188 Paul (Ericsson) object to all revisions. ==== Final Comments Deadline ==== | Noted |
| 9.12.2 | S2-2401188 | CR | Approval | 23.503 CR1263 (Rel-18, 'F'): Support updating Multi-modal Service Requirements | Nokia, Nokia Shanghai Bell, [Ericsson], [Deutsche Telekom] | Rel-18 | Noted | Dan (China Mobile) suggest to use this paper as baseline Paul (Ericsson) provides r01. Mirko (Huawei) provides r02. Georgios (Nokia) agrees with the changes in r02 Paul (Ericsson) we can only accept r01. We object to r02 as it simply adds changes from 0684 that we objected to (see 0684 thread for justification). Mirko (Huawei) responds to Paul and clarifies that the comments have been addressed or do not apply to these changes. ==== Revisions Deadline ==== Mirko (Huawei) objects to r00 and r01 of this CR. ==== Final Comments Deadline ==== | Noted |
| 9.12.2 | - | - | - | KI#3 Information Exposure | - | - | Docs:=10 | - | |
| 9.12.2 | S2-2400366 | CR | Approval | 23.501 CR5081R1 (Rel-18, 'F'): Correction on Congestion Information Exposure | Ericsson | Rel-18 | Revision of (unhandled) S2-2312154. r03 Agreed. Revised to S2-2401407. | Xinpeng(Huawei) comments. Paul (Ericsson) provides r01. Xinpeng(Huawei) replies to Devaki (Nokia). Devaki (Nokia) provides r02. Chunshan (CATT) provides r03 based on comments from Xinpeng(Huawei). ==== Revisions Deadline ==== Devaki (Nokia) can live with r03. Paul (Ericsson) object to r02, can accept r00, r01, and r03. ==== Final Comments Deadline ==== | Revised |
| 9.12.2 | S2-2401407 | CR | Approval | 23.501 CR5081R2 (Rel-18, 'F'): Correction on Congestion Information Exposure | Ericsson | Rel-18 | Revision of S2-2400366r03. Approved | Agreed | |
| 9.12.2 | S2-2400683 | CR | Approval | 23.501 CR4812R3 (Rel-18, 'F'): Corrections for traffic characteristics parameters in Alternative QoS Profile | Huawei, HiSilicon | Rel-18 | Revision of (unhandled) S2-2312803. Noted | Devaki (Nokia) provides r01. Paul (Ericsson) asks question for clarification. Mirko (Huawei) responds to the questions. Paul (Ericsson) asks for clarification, how does the UE communicate concerning these parameters with the application? Where is that functionality specified? Chunshan(CATT) supports this CR and asks for co-sign this CR. Mirko (Huawei) responds. Paul (Ericsson) asks for clarification what the UE uses of MDBV for and it seems not to be included in the AT commands. Why would the values from AQP be provided to the UE? Especially given RAN will probe to improve the situation, this would counteract and kept the once degraded working point. Paul (Ericsson) replies. Mirko (Huawei) provides r02. Paul (Ericsson) objects to that CR in all revisions. Mirko (Huawei) provides r03 which does no longer mention that MDBV is sent to the UE. ==== Revisions Deadline ==== Devaki (Nokia) cannot accept any version other than r01 unfortunately (as the original version and all other versions delete functionality related to MDBV). Mirko (Huawei) responds that the functionality is not deleted. The description is only moved to clause 5.7.1.2a (Alternative QoS Profile) so that all other clauses speaking of AQP can follow the logic (to consider also the MDBV if it is available) without a need to repeat the statement in every clause. Paul (Ericsson) we object to this CR in all revisions. ==== Final Comments Deadline ==== | Noted |
| 9.12.2 | S2-2400980 | CR | Approval | 23.501 CR5282 (Rel-18, 'F'): Clarifications on ECN marking for L4S | Lenovo | Rel-18 | r05 Agreed. Revised to S2-2401408. | Paul (Ericsson) provides r01. Sudeep (Apple) provides comments on r00 and r01. Haley (Lenovo) replies to Paul (Ericsson) and Sudeep(Apple). Haley (Lenovo) replies to Devaki(Nokia) Devaki (Nokia) objects to the paper and its revisions. Youngkyo(Samsung) provides the revision r02. Haley (Lenovo) replies to Youngkyo(Samsung) and provides r03. Youngkyo(Samsung) is okay with r03. Sudeep (Apple) does not think changes in r03 are correct. Haley (Lenovo) replies to Sudeep (Apple). Xinpeng(Huawei) provides r04 based on r03. Haley (Lenovo) thanks Xinpeng(Huawei) and provides r05 based on r04. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 9.12.2 | S2-2401408 | CR | Approval | 23.501 CR5282R1 (Rel-18, 'F'): Clarifications on ECN marking for L4S | Lenovo, Ericsson, Samsung | Rel-18 | Revision of S2-2400980r05. Approved | Agreed | |
| 9.12.2 | S2-2400769 | CR | Approval | 23.502 CR4707 (Rel-18, 'F'): Procedures for UPF relocation considering congestion exposure | Samsung | Rel-18 | r03 + changes Agreed. Revised to S2-2401406. | Xinpeng(Huawei) comments. Youngkyo(Samsung) replies. Youngkyo(Samsung) provides the revision r01. Dan (China Mobile) support Devaki's idea and the first change should be removed, the second part can be kept. Devaki (Nokia) objects to first change, second change is sufficient. Xinpeng(Huawei) replies to Youngkyo(Samsung). Paul (Ericsson) we don't think that the changes in 4.3.5.x are needed. Only update to 5.2.8.2.8 is needed. Youngkyo(Samsung) provides the revision r03. Youngkyo(Samsung) provides the revision r02. Xiaowan Ke(vivo) provides comments Dan(China Mobile) provides comments ==== Revisions Deadline ==== Youngkyo(Samsung) is okay to remove the first change and fix the typo as your comment(uploaded as r04) Devaki (Nokia) comments no revision is acceptable. R03 is fine with just the changes to clause 5.2.8.2.8. Xinpeng(Huawei) proposes to go with r04. ==== Final Comments Deadline ==== | Revised |
| 9.12.2 | S2-2401406 | CR | Approval | 23.502 CR4707R1 (Rel-18, 'F'): Procedures for UPF relocation considering congestion exposure | Samsung | Rel-18 | Revision of S2-2400769r03 + changes. Approved | Agreed | |
| 9.12.2 | S2-2400768 | CR | Approval | 23.502 CR4706 (Rel-18, 'F'): Procedures for 5GS congestion exposure | Samsung | Rel-18 | Noted | Xinpeng(Huawei) comments. Youngkyo(Samsung) replies and provides r01. Youngkyo(Samsung) replies and provides r02. Devaki (Nokia) objects to the CR and its revisions. Xinpeng(Huawei) still has some concerns about including 'Indication of ECN marking for L4S' in Nnef_AFsessionWithQoS_Update operation. ==== Revisions Deadline ==== Youngkyo(Samsung) replies. Xinpeng(Huawei) replies to Youngkyo(Samsung). ==== Final Comments Deadline ==== | Noted |
| 9.12.2 | S2-2400318 | CR | Approval | 23.503 CR1101R3 (Rel-18, 'F'): Update for QoS monitoring and network exposure | Vivo, Lenovo, Tencent, Tencent Cloud, China Mobile, China Telecom | Rel-18 | Revision of (unhandled) S2-2312098. r02 + changes Agreed. Revised to S2-2401410. | Xinpeng(Huawei) comments. Xiaowan Ke(vivo) replies to Xinpeng(Huawei) and provides r01 Paul (Ericsson) provides r02. ==== Revisions Deadline ==== Devaki (Nokia) is ok with r02. Devaki (Nokia) prefers r02. ==== Final Comments Deadline ==== | Revised |
| 9.12.2 | S2-2401410 | CR | Approval | 23.503 CR1101R4 (Rel-18, 'F'): Update for QoS monitoring and network exposure | Vivo, Lenovo, Tencent, Tencent Cloud, China Mobile, China Telecom | Rel-18 | Revision of S2-2400318r02 + changes. Approved | Agreed | |
| 9.12.2 | - | - | - | KI#4 & 5 PDU set handling | - | - | Docs:=18 | - | |
| 9.12.2 | S2-2400243 | LS OUT | Approval | [DRAFT] LS on Superseding the PDB and or PER with different UL and DL values for a given QoS Flow | CATT | Rel-18 | Noted | Paul (Ericsson) objects to the draft LS in S2-2400243. Chunshan (CATT) replies to Paul (Ericsson) that this LS can be considered again based on discussion of the related CR S2-2400242. Devaki (Nokia) comments that the need for LS is dependent on 242. Sebastian (Qualcomm) agrees with Paul, also objects to the LS ==== Revisions Deadline ==== Devaki (Nokia) objects to the LS at this time. ==== Final Comments Deadline ==== | Noted |
| 9.12.2 | S2-2400242 | CR | Approval | 23.501 CR5224 (Rel-18, 'F'): PSER and PSDB supersede the PER and PDB per direction | CATT | Rel-18 | Postponed | Paul (Ericsson) objects to S2-2400242 r00. Chunshan(CATT) provides clarification why this CR is needed and is very important to Paul (Ericsson) and asks to consider it again. Paul (Ericsson) replies that given PSDB&PSER are only valid for a given direction, they can't supersede another parameter in a different direction. Therefore, no additional clarification is needed. Devaki (Nokia) also has concerns with the CR, do not see the need for it. Chunshan (CATT) provides the r01. Mukesh (MediaTek) considers the r01 changes to be minor and not needed. Paul (Ericsson) we object to this CR in all revisions. Chunshan(CATT) points out that the superseding only in the NG-RAN not in the SMF or PCF. Mirko (Huawei) provides r02. Devaki (Nokia) objects to the CR and its revisions. Sorry as discussed in the other email thread, this CR makes the permutation and combination worse, we cannot have PSER and PDB for a single QoS Flow, worse in UL/DL independently. Xiaowan Ke(vivo) seek clarification from Devaki (Nokia) Chunshan(CATT) provides clarification to Devaki (Nokia) inline. Devaki (Nokia) comments Chunshan(CATT) clarifies how to handle the PSER/PSDB per direction. Chunshan (CATT) provides r03. ==== Revisions Deadline ==== Devaki (Nokia) proposes to postpone this CR, has objections to approval of any version of the CR. ==== Final Comments Deadline ==== | Postponed |
| 9.12.2 | S2-2400371 | CR | Approval | 23.501 CR5228 (Rel-18, 'F'): Protocol Descriptions for UL and DL traffic | Ericsson | Rel-18 | r03 Agreed. Revised to S2-2401411. | Hui (Huawei) questions the use cases. Sudeep (Apple) supports the intent of the CR. Dan (China Mobile) ask the question for this proposal Sebastian (Qualcomm) supports the CR Hui (Huawei) comments Devaki (Nokia) comments. Paul (Ericsson) provides response. Chunshan(CATT) provides r01 to clarify that the PD can be UL only, DL only or UL and DL. Hui(Huawei) provides comments. Chunshan(CATT) has the same comments. Paul (Ericsson) responds and provides a use case where UL and DL PD can be different, hence justification for the change introduced by CR. Chunshan(CATT) questions on the case. Hui(Huawei) provide comments. Dan(China Mobile) provide r02. Paul (Ericsson) provides r03. Dan (China Mobile) reply. ==== Revisions Deadline ==== Devaki (Nokia) comments that we support, wish to cosign r03 version of the CR. ==== Final Comments Deadline ==== | Revised |
| 9.12.2 | S2-2401411 | CR | Approval | 23.501 CR5228R1 (Rel-18, 'F'): Protocol Descriptions for UL and DL traffic | Ericsson | Rel-18 | Revision of S2-2400371r03. Approved | Agreed | |
| 9.12.2 | S2-2400611 | CR | Approval | 23.501 CR5249 (Rel-18, 'F'): Clarification on support of PDU Set based QoS | Nokia, Nokia Shanghai Bell | Rel-18 | Postponed | Hui (Huawei) objects to Alt 1 and provides comments to Alt 2. Chunshan (CATT) objects to Alt 1 and proposes to work on Alt 2. Xiaowan Ke(vivo) also requests not to make PSER and PSDB dependent with each other Jari (NTT DOCOMO) prefers Alt2 Devaki (Nokia) provides r01 to include only Alt. 2 based on preferences expected by others. Sudeep (Apple) also supports Alt 2. Paul (Ericsson) provides comments. Paul (Ericsson) clarifies that usage of QoS parameters by NG-RAN is implementation specific and asks for clarification what would be the benefits from limiting the information that is provided to NG-RAN ( aka alt.2). Devaki (Nokia) comments. Sebastian (Qualcomm) comments Chunshan (CATT) provides clarification why PSER and or PSDB to be provided to the NG-RAN and current r00 and r01 is not acceptable . Devaki (Nokia) provides r02 and r03. Devaki (Nokia) provides r04 (amends r01/Alt2). Xiaowan Ke(vivo) provides comments Hui(Huawei) still have concern on this CR Sebastian (Qualcomm) replies to Hui and Xiaowan Devaki (Nokia) provides r05, that will hopefully alleviate everyone's concerns expressed in this thread. Hui(Huawei) asks question on r05. Mirko (Huawei) comments about the stage 2 view on RAN scheduling in general. Xiaowan Ke(vivo) replies Sebastian (Qualcomm) Sebastian (Qualcomm) replies to Xiaowan Sebastian (Qualcomm) replies to Devaki Devaki (Nokia) proposes to postpone this to next meeting as proposed by Sebastian (Qualcomm). ==== Revisions Deadline ==== | Postponed |
| 9.12.2 | S2-2400766 | CR | Approval | 23.501 CR5260 (Rel-18, 'F'): Reflective QoS for UL PDU Set QoS handling | Samsung | Rel-18 | Noted | Chunshan (CATT) provides comments. Xiaowan Ke(vivo) seeks clarifications about the relationship between UE derived QoS rule and PDU Set QoS Mukesh (MediaTek) seeks to postpone this CR so that it can be thoroughly examined in Athens. Devaki (Nokia) supports the CR. Youngkyo(Samsung) provides the revision r01. Sebastian (Qualcomm) objects to the CR (r00 and revisions) Xiaowan Ke(vivo) replies Devaki (Nokia) and clarify the comment Boren (OPPO) comments on PDU Set QoS Parameters ==== Revisions Deadline ==== | Noted |
| 9.12.2 | S2-2400979 | CR | Approval | 23.501 CR5281 (Rel-18, 'F'): Clarifications on non-homogeneous support of PDU set based handling in NG-RAN | Lenovo | Rel-18 | r01 Agreed. Revised to S2-2401412. | Devaki (Nokia) comments that this CR does not really have any functional change, no strong objection but not a FASMO either. Haley(Lenovo) replies to Devaki(Nokia) and thinks the CR is necessary. Mirko (Huawei) believes that this CR is helpful and provides r01. Haley(Lenovo) is ok with r01. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 9.12.2 | S2-2401412 | CR | Approval | 23.501 CR5281R1 (Rel-18, 'F'): Clarifications on non-homogeneous support of PDU set based handling in NG-RAN | Lenovo | Rel-18 | Revision of S2-2400979r01. Approved | Agreed | |
| 9.12.2 | S2-2400815 | CR | Approval | 23.502 CR4642R3 (Rel-18, 'F'): Update on Support of UL PDU Set based QoS Handling | Huawei, HiSilicon | Rel-18 | Revision of (revised and postponed) S2-2312953. r03 + changes Agreed. Revised to S2-2401413. | Paul (Ericsson) provides r01. Mukesh (MediaTek) considers UL PDU Set handling is left to UE implementation and objects to all revisions. Dan (China Mobile) concern the objection from MTK is against with the SoH result in November meeting. Mukesh (MediaTek) responds to Dan (China Mobile) Chunshan (CATT) objects r01 since the Protocol Description is not part of the QoS rule , and is OK with r00. Xiaowan Ke(vivo) echo Protocol Description doesn't belong to QoS rule and will not impact the QoS flow mapping Hui (Huawei) replies to Mukesh on the objection and comments on r01 Dan (China Mobile) comments on r01 Paul (Ericsson) provides r02. Devaki (Nokia) comments Hui (Huawei) provides r03 ==== Revisions Deadline ==== Dan(China Mobile) support to go with r03 Devaki (Nokia) comments that we support/cosign the latest version of the CR. It does need an editorial update from UL/DL to UL and/or DL to be consistent with the 23.501 CR. Mukesh (MediaTek Inc.) objects to all revisions but can agree with r03 + removing all changes to clause 4.3.2.2.1 Hui (Huawei) have strong concerns on removing PD from PDU Session establishment. Mukesh (MediaTek Inc.) responds to Hui (Huawei), the changes do not align with 501 Hui (Huawei) responds to Mukesh and provides draft r05 Mukesh (MediaTek Inc) replies to Hui (Huawei), r05 is not acceptable Xiaowan Ke(vivo) comment: only UL Protocol Description need to provide to AMF and UE; DL doesn't Hui (Huawei) replies to Mukesh and provide draft r06 Hui (Huawei) provides r07 and ask for discussion in CC#3. r07 = r03 + 1) correct related CR number in cover page. 2) added co-signer. 3) remove changes to clause 4.3.2.2.1 Mukesh (MediaTek Inc) thanks Hui (Huawei) and agrees with r07 ==== Final Comments Deadline ==== | Revised |
| 9.12.2 | S2-2401413 | CR | Approval | 23.502 CR4642R4 (Rel-18, 'F'): Update on Support of UL PDU Set based QoS Handling | Huawei, HiSilicon, Ericsson, Nokia | Rel-18 | Revision of S2-2400815r03 + changes. Approved | Agreed | |
| 9.12.2 | S2-2400816 | CR | Approval | 23.503 CR1225R1 (Rel-18, 'F'): Update on support of UL PDU Set based QoS handling | Huawei, HiSilicon | Rel-18 | Revision of (unhandled) S2-2312954. Merged into S2-2401415 | Mukesh (MediaTek) provides r01 and objects to r00 Sebastian (Qualcomm) prefers S2-2400372 Hui (Huawei) asks question to Mukesh Hui (Huawei) prefers to keep the discussion separate. Mukesh (MediaTek) responds to Hui (Huawei) Hui (Huawei) provides r02 Mukesh (MediaTek) suggests marking this CR as merged into 2400372 or noted. Hui (Huawei) fine to merge this into 2400372. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 9.12.2 | S2-2400370 | CR | Approval | 23.502 CR4681 (Rel-18, 'F'): UPF activation of PDU Set Identification and marking for DL only | Ericsson | Rel-18 | r01 Agreed. Revised to S2-2401414. | Xiaowan Ke(vivo) provides r01 ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 9.12.2 | S2-2401414 | CR | Approval | 23.502 CR4681R1 (Rel-18, 'F'): UPF activation of PDU Set Identification and marking for DL only | Ericsson | Rel-18 | Revision of S2-2400370r01. Approved | Agreed | |
| 9.12.2 | S2-2400722 | CR | Approval | 23.502 CR4512R2 (Rel-18, 'F'): Clarification on Service Request Procedure for PDU Set based handling | Rel-18 | Revision of (unhandled) S2-2313117. Postponed | Chunshan (CATT) provides comments. Paul (Ericsson) provides r01 and objects to r00. Ellen (Google) agrees with r01 provided by Paul (Ericsson) r01 and provides feedback to Chunshan (CATT). Chunshan (CATT) provides r02 and clarify that the service request procedure is only to re-establish the UP of the established PDU Session. Paul (Ericsson) replies to Chunshan. Jari (NTT DOCOMO) comments Chunshan(CATT) replies to Paul (Ericsson). Haley(Lenovo) comments Chunshan(CATT) replies to Haley(Lenovo) that if the Source NG-RAN does not support PDU Set QoS parameter, it shall NOT include the PDU Set QoS parameters. Ellen (Google) provides r03 <https://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_160AHE_Electronic_2024-01/INBOX/Revisions/S2-2400722r03.zip> and replies to Chunshan, Haley, Paul Haley(Lenovo) replies to Chunshan (CATT). Ellen (Google) replies to Jari Devaki (Nokia) objects to all earlier versions, provides r04. Devaki (Nokia) objects to r01 as support for PDU Support handling when just a single parameter is provided. Ellen (Google) asks Devaki's clarification for r04 which is against clause 5.37.5.3 Ellen (Google) feedback to Jari ==== Revisions Deadline ==== Devaki (Nokia) comments that it is best to postpone this CR to the next meeting. Chunshan(CATT) objects any changes in Steps 18a and 21a,in such cases, only r02 is acceptable, and object r00,r01,r03,r04. Paul (Ericsson) fine to postpone as per Devaki's proposal. Paul (Ericsson) r01 is fine for us, we object to all other revisions. ==== Final Comments Deadline ==== | Postponed | |
| 9.12.2 | S2-2400726 | CR | Approval | 23.502 CR4514R2 (Rel-18, 'F'): Clarification on PDU Set based handling during UE states transition | Rel-18 | Revision of (unhandled) S2-2313119. Postponed | Chunshan (CATT) provides comments. Mukesh (MediaTek) provides comments. Paul (Ericsson) agrees with Mukesh, if there are PDU Set QoS Parameters in the UE Ctxt already, then the support indication will not trigger any SMF procedure as the state remains the same. Ellen (Google) provides feedback Devaki (Nokia) comments Sebastian (Qualcomm) provides r01 Chunshan(CATT) provides r02. Ellen (Google) provides r03 <https://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_160AHE_Electronic_2024-01/INBOX/Revisions/S2-2400726r03.zip> and feedbacks to Sebastian Devaki (Nokia) provides r04. Ellen (Google) provides r05 and comments Devaki'r04 which invented a new term PDU Set based handling parameter ==== Revisions Deadline ==== Chunshan (CATT) is OK with r02,r03 and r05. Paul (Ericsson) provides comments and questions. We object to that CR in all revisions. Ellen (Google) feedback to Paul and don't understand the objections: The way forward agreement in the Nov meeting is that we put the general requirement in TS23.501 and indicate the impacted procedure in TS23.502. Paul (Ericsson) asks question for clarification. Ellen (Google) feedback Paul ==== Final Comments Deadline ==== | Postponed | |
| 9.12.2 | S2-2401271 | CR | Approval | 23.502 CR4735 (Rel-18, 'F'): Clarification on PDU Set based handling in home routed case | Rel-18 | Postponed | Chunshan (CATT) provides comments. Ellen (Google) provides feedback to Chunshan (CATT): need other CR to provide End of Data Burst handling for roaming case Mirko (Huawei) comments that this CR should not be necessary. Ellen (Google) provide r01 <https://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_160AHE_Electronic_2024-01/INBOX/Revisions/S2-2401271r01.zip> and feedback to Mirko (Huawei) Mirko (Huawei) responds. Ellen (Google) responds Ellen (Google) provides r02 and responds to Mirko. Mirko (Huawei) responds and still believes that the issue is not strong enough to change the structure of the procedure. Ellen (Google) responds to Mirko: it is step 17/18 that RAN will send the indication and V-SMF receives it, which is also aligned with other changes in PDU Session Establish/Modification request procedures. I believe this change is important clarification because the V-SMF would need to determine whether to inform H-SMF this indication. Mirko (Huawei) responds and is not convinced (yet) that such V-SMF functionality is necessary. ==== Revisions Deadline ==== Mirko (Huawei) responds that such specific checks are better realized at H-SMF than in V-SMF. Paul (Ericsson) we propose to postpone this CR. ==== Final Comments Deadline ==== | Postponed | |
| 9.12.2 | S2-2400372 | CR | Approval | 23.503 CR1245 (Rel-18, 'F'): Protocol Description for UL and DL traffic | Ericsson | Rel-18 | r05 Agreed. Revised to S2-2401415, merging S2-2400816 | Hui (Huawei) comments: This paper depends on the outputs of S2-2400371. Chunshan(CATT) provides r01 and also update the cover page to check on the ME, RAN. Dan(China Mobile) provides comment. Mukesh (MediaTek) provides r02. Paul (Ericsson) responds. Hui (Huawei) provides r03. Mukesh (MediaTek) provides r05. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 9.12.2 | S2-2401415 | CR | Approval | 23.503 CR1245R1 (Rel-18, 'F'): Protocol Description for UL and DL traffic | Ericsson, Huawei | Rel-18 | Revision of S2-2400372r05, merging S2-2400816. Approved | Agreed | |
| 9.12.2 | - | - | - | KI#7 Packet Delay Variation | - | - | Docs:=2 | - | |
| 9.12.2 | S2-2400842 | CR | Approval | 23.501 CR5267 (Rel-18, 'F'): Modification to the Packet delay variation monitoring | ZTE | Rel-18 | r02 Agreed. Revised to S2-2401416. | Paul (Ericsson) objects to S2-2400842 r00 and provides r01. zhendong (ZTE) provides the r02 Lei (Tencent) objects r00 and can live with r01, r02. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 9.12.2 | S2-2401416 | CR | Approval | 23.501 CR5267R1 (Rel-18, 'F'): Modification to the Packet delay variation monitoring | ZTE | Rel-18 | Revision of S2-2400842r02. Approved | Agreed | |
| 9.12.2 | - | - | - | KI#8 Power Saving | - | - | Docs:=14 | - | |
| 9.12.2 | S2-2400168 | CR | Approval | 23.501 CR5215 (Rel-18, 'F'): Clarification on N6 jitter information associated periodicity from AF | Tencent,Tencent Cloud | Rel-18 | r05 Agreed. Revised to S2-2401417. | Xinpeng(Huawei) comments. Youngkyo(Samsung) comments. Lei (Tencent) replies to Xinpeng (Huawei) and Youngkyo(Samsung). Xiaowan Ke(vivo) provides r01 Xinpeng(Huawei) provides r02. Lei(Tencent) provides comments and ok the changes proposed in r01, r02. Provide r03 to accept the change in cover page. Georgios (Nokia) provides comments and proposes further updates Lei(Tencent) replies to Georgios (Nokia) and provide r04. Georgios (Nokia) thanks for r04. Still changes needed in the header Lei(Tencent) appreciated the further comments from Georgios (Nokia) on r04 and provide r05 correspondingly. Georgios (Nokia) thanks for r05 which looks OK ==== Revisions Deadline ==== Georgios (Nokia) proposes to move forward with r05, objects to all previous revisions Lei(Tencent) is fine to go with r05 ==== Final Comments Deadline ==== | Revised |
| 9.12.2 | S2-2401417 | CR | Approval | 23.501 CR5215R1 (Rel-18, 'F'): Clarification on periodicity change from AF | Tencent, Tencent Cloud | Rel-18 | Revision of S2-2400168r05. Approved | Agreed | |
| 9.12.2 | S2-2400240 | CR | Approval | 23.501 CR5222 (Rel-18, 'F'): Packet filter with DSCP and ECN | CATT | Rel-18 | r01 + changes Agreed. Revised to S2-2401418. | Chunshan (CATT) provides clarification to Devaki (Nokia) and prefers the r00. Sudeep (Apple) has question for clarification. Devaki (Nokia) objects to r00 provides r01. Mukesh (MediaTek) prefers r01 and objects r00 Chunshan(CATT) provides clarification to Sudeep (Apple) . Paul (Ericsson) objects to r00, we are ok with r01. ==== Revisions Deadline ==== Devaki (Nokia) objects to r00, accepts only r01. ==== Final Comments Deadline ==== | Revised |
| 9.12.2 | S2-2401418 | CR | Approval | 23.501 CR5222R1 (Rel-18, 'F'): Packet filter with DSCP and ECN | CATT | Rel-18 | Revision of S2-2400240r01 + changes. Approved | Agreed | |
| 9.12.2 | S2-2400241 | CR | Approval | 23.501 CR5223 (Rel-18, 'F'): UL Data Burst Handling | CATT | Rel-18 | Noted | Xinpeng(Huawei) asks for clarification. Chunshan (CATT) provides clarification to Xinpeng(Huawei). Xiaowan Ke(vivo) disagree to capture the text as it is and request to just give a reference to RAN spec if proponent want to mention UL EoDB Chunshan (CATT) provides clarification to Xiaowan Ke(vivo). Georgios (Nokia) does not agree with the UL change Sebastian (Qualcomm) objects to the CR Youngkyo(Samsung) shares the Georgios(Nokia)'s view Chunshan (CATT) provides the r01. Mukesh (MediaTek) objects to this CR for reasons given by Nokia Chunshan(CATT) comments that the r01 has been updated, please comments on the r01 version. Paul (Ericsson) objects to this CR in all revisions. ==== Revisions Deadline ==== | Noted |
| 9.12.2 | S2-2401190 | CR | Approval | 23.501 CR5295 (Rel-18, 'F'): Clarifications on applicability of Protocol Description in PDR for EoDB identification in DL | Nokia, Nokia Shanghai Bell | Rel-18 | r04 Agreed. Revised to S2-2401419. | Xinpeng(Huawei) comments. Georgios (Nokia) replies to Xinpeng Chunshan(CATT) provides r01 to remove the repeated text. Georgios (Nokia) provides r02 Xinpeng(Huawei) provides r03. Georgios (Nokia) provides r04 ==== Revisions Deadline ==== Georgios (Nokia) proposes to proceed with r04 ==== Final Comments Deadline ==== | Revised |
| 9.12.2 | S2-2401419 | CR | Approval | 23.501 CR5295R1 (Rel-18, 'F'): Clarifications on applicability of Protocol Description in PDR for EoDB identification in DL | Nokia, Nokia Shanghai Bell | Rel-18 | Revision of S2-2401190r04. Approved | Agreed | |
| 9.12.2 | S2-2400319 | CR | Approval | 23.502 CR4295R3 (Rel-18, 'F'): Update for UE power saving management | Vivo, Lenovo, China Telecom, China Mobile | Rel-18 | Revision of (unhandled) S2-2312099. r02 Agreed. Revised to S2-2401420. | Georgios (Nokia) provides r02 Paul (Ericsson) provides r01. ==== Revisions Deadline ==== Georgios (Nokia) prefers r02 and proposes it as way forward. ==== Final Comments Deadline ==== | Revised |
| 9.12.2 | S2-2401420 | CR | Approval | 23.502 CR4295R4 (Rel-18, 'F'): Update for UE power saving management | Vivo, Lenovo, China Telecom, China Mobile, Ericsson | Rel-18 | Revision of S2-2400319r02. Approved | Agreed | |
| 9.12.2 | S2-2401191 | CR | Approval | 23.502 CR4731 (Rel-18, 'F'): Clarifications on applicability of Protocol Description for EoDB identification in DL | Nokia, Nokia Shanghai Bell | Rel-18 | Approved | Agreed | |
| 9.12.2 | S2-2400843 | CR | Approval | 23.503 CR1256 (Rel-18, 'F'): Clarification on AF providing Periodicity and PCF behavoir | ZTE | Rel-18 | r04 Agreed. Revised to S2-2401421. | Xinpeng(Huawei) comments. zhendong (ZTE) provides the r01 Xiaowan Ke(vivo) provides r02 Georgios (Nokia) provides comment on r02 zhendong (ZTE) provides the r03 Georgios (Nokia) supports r03 Xinpeng(Huawei) provides r04 based on r03. zhendong (ZTE) provides the response ==== Revisions Deadline ==== Georgios (Nokia) r04 is OK ==== Final Comments Deadline ==== | Revised |
| 9.12.2 | S2-2401421 | CR | Approval | 23.503 CR1256R1 (Rel-18, 'F'): Clarification on AF providing Periodicity and PCF behavoir | ZTE | Rel-18 | Revision of S2-2400843r04. Approved | Agreed | |
| 9.12.2 | S2-2401040 | CR | Approval | 23.503 CR1258 (Rel-18, 'F'): Update for UE power saving management | Vivo, Lenovo, China Telecom | Rel-18 | r01 Agreed. Revised to S2-2401422. | Paul (Ericsson) provides r01. ==== Revisions Deadline ==== Georgios (Nokia) r01 is OK ==== Final Comments Deadline ==== | Revised |
| 9.12.2 | S2-2401422 | CR | Approval | 23.503 CR1258R1 (Rel-18, 'F'): Update for UE power saving management | Vivo, Lenovo, China Telecom, Ericsson | Rel-18 | Revision of S2-2401040r01. Approved | Agreed | |
| 9.13.2 | - | - | - | RedCap Phase 2 (NR_RedCAP_Ph2) | - | - | Docs:=18 | - | |
| 9.13.2 | - | - | - | LS related handling | - | - | Docs:=10 | - | |
| 9.13.2 | S2-2400030 | LS In | Action | LS from CT WG4: Reply LS on INACTIVE eDRX above 10.24sec and SDT | CT WG4 (C4-235535) | Rel-18 | Revision of Postponed S2-2313504 from SA WG2#160. Noted | Qian (Ericsson) proposes to NOTE the paper. | Noted |
| 9.13.2 | S2-2400004 | LS In | Action | LS from RAN WG3: Reply LS on Rel-18 RedCap enhancements to address remaining ENs in TS 23.502 | RAN WG3 (R3-234725) | Rel-18 | Revision of Postponed S2-2311938 from SA WG2#160. Response drafted in S2-2400309, S2-2400414. Final response in S2-2401530 | Qian (Ericsson) propose to NOTE, if 0309 can be agreed. | Replied to |
| 9.13.2 | S2-2400309 | LS OUT | Approval | [DRAFT] Reply LS on Rel-18 RedCap enhancements to address remaining ENs in TS 23.502 | Huawei, HiSilicon | Rel-18 | Response to S2-2400004. r05 + clean up Agreed. Revised to S2-2401530, merging S2-2400414 | Haris(Qualcomm) provides r01 Steve (Huawei) provides r02 Ellen (Google) provides r03 <https://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_160AHE_Electronic_2024-01/INBOX/Revisions/S2-2400309r03.zip> adding charging differentiation Steve (Huawei) provides r04 ==== Revisions Deadline ==== Qian (Ericsson) supports r04 Steve (Huawei) r04 is not the right version, r02 or other changes needed. Qian (Ericsson) is ok with r02. Haris(Qualcomm) agrees that is better to approve r02 and the text in it is not restrictive to other uses of the indicator which is anyway SA2 discussion Chris (Vodafone) is ok with r02 but would like to attach the CRs resulting from 1248/1249 (and align wording from '.... has approved related CRs' to '... has approved the attached CRs'). Ellen (Google) is NOT ok with r02 and proposes improvement as follows: 1. removed the second paragraph 2. the first paragraph add 'and other potential differentiation' Steve (Huawei) provides a draft r05. Wanqiang (session chair): please make an acceptable version before the comments deadline. It is LS out and we can generate a new version. ==== Final Comments Deadline ==== Ellen (Google) is Ok with r05. Chris (Vodafone) is Ok with r05. Qian (Ericsson) supports r05. | Revised |
| 9.13.2 | S2-2401530 | LS OUT | Approval | Reply LS on Rel-18 RedCap enhancements to address remaining ENs in TS 23.502 | SA WG2 | Rel-18 | Revision of S2-2400309r05 + clean up, merging S2-2400414. Approved | Approved | |
| 9.13.2 | S2-2400414 | LS OUT | Approval | [DRAFT] Reply LS on Rel-18 RedCap enhancements to address remaining ENs in TS 23.502 | Qualcomm Technologies Ireland | Rel-18 | Response to S2-2400004. Merged into S2-2401530 | Qian (Ericsson) proposes to merge this into 0309. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 9.13.2 | S2-2401249 | CR | Approval | 23.501 CR5298 (Rel-17, 'F'): Access control for users with Redcap subscriptions | Vodafone | Rel-17 | r02 + changes Agreed. Revised to S2-2401532. | Qian (Ericsson) provides comments Chris (Vodafone) replies. Yes, let's focus discussion on 1248 thread. Chris (Vodafone) provides r01 based on 1248r05 Chris (Vodafone) provides r02 to align with 1248r06. ==== Revisions Deadline ==== Qian (Ericsson) indicates that it shall be synched with agreed revision of 2148. Steve (Huawei) assumes Qian means 1248 (and not 2148). Chris (Vodafone) provides r03 in drafts to align with 1248r07. ==== Final Comments Deadline ==== | Revised |
| 9.13.2 | S2-2401532 | CR | Approval | 23.501 CR5298R1 (Rel-17, 'F'): Access control for users with Redcap subscriptions | Vodafone | Rel-17 | Revision of S2-2401249r02 + changes. Approved | Agreed | |
| 9.13.2 | S2-2401248 | CR | Approval | 23.501 CR5297 (Rel-18, 'F'): Access control for users with eRedcap/Redcap subscriptions | Vodafone | Rel-18 | r07 Agreed. Revised to S2-2401531. | Qian (Ericsson) asks questions Chris (Vodafone) answers Ericsson: Redcap UEs are NR UEs. Unlike with 'NB-IoT and WB-EUTRAN' we did not create the terms 'Redcap and WB-NR'. Chris (Vodafone) asks Huawei for further explanation. Steve (Huawei) comments. Steve (Huawei) comments on wider UE bandwidth forms of NR Chris (Vodafone) replies to Huawei and asks whether r01 is better Qian (Ericsson) provides comments and propose a way forward. Steve (Huawei) the updates help Haris(Qualcomm) comments and supports the CR Qian (Ericsson) provides responses Qian (Ericsson) provides further comments and r02 Haris(Qualcomm) comments on r02 Dongjoo (Nokia) supports r02 Chris (Vodafone) provides r03 because if we go the r02 route we need to clarify what NR is. Qian (Ericsson) provides r04 Chris (Vodafone) provides r05 Chris (Vodafone) says that he will now use r05 to update the R17 CR in 1249 Steve (Huawei) comments on mutual exclusive Qian (Ericsson) responds Chris provides r06 Haris(Qualcomm) comments that if we go with the 'mutually exclusive' text approach we need to clarify that applies only to NR as primary RAT restrictions Steve (Huawei) comments in the encoding note, provides r07. ==== Revisions Deadline ==== Dongjoo (Nokia) is fine with r07 Qian (Ericsson) supports to go with r07. Chris (Vodafone) is OK with r07 but prefers r06. Haris(Qualcomm) is ok with r06 or r07 Steve (Huawei) can live with either r06 or r07 Chris (Vodafone) says that in case we go with r07, he has uploaded the matching R17 CR in 1249r03 in drafts. ==== Final Comments Deadline ==== | Revised |
| 9.13.2 | S2-2401531 | CR | Approval | 23.501 CR5297R1 (Rel-18, 'F'): Access control for users with eRedcap/Redcap subscriptions | Vodafone | Rel-18 | Revision of S2-2401248r07. Approved | Agreed | |
| 9.13.2 | S2-2400664 | CR | Approval | 23.501 CR5254 (Rel-18, 'F'): Clarification on (e)RedCap UE | Rel-18 | Check WI Code! Postponed | Qian (Ericsson) provides comments Haris(Qualcomm) proposes to note the CR Ellen (Google) provides feedback to Qian (Qualcomm) and Haris (Ericsson) Steve (Huawei) comments. Ellen (Google) provides r01 <https://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_160AHE_Electronic_2024-01/INBOX/Revisions/S2-2400664r01.zip> that adds Editor's note for later NR eRedCap indication terminology alignment with RAN3 Steve (Huawei) comments on an EN, waiting is ok. ==== Revisions Deadline ==== Ellen (Google) agrees to postpone this paper for covering required clarification when having RAN WGs inputs and would like to support SA2 acks RAN WGs (in LSOUT) that NR (e)RedCap indication is needed for subscription control and for charging differentiation. Qian (Ericsson) supports to postpone the paper. Steve (Huawei) postponing is a reasonable at this point, thank you. ==== Final Comments Deadline ==== | Postponed | |
| 9.13.2 | - | - | - | Maintenance | - | - | Docs:=8 | - | |
| 9.13.2 | S2-2400133 | CR | Approval | 23.502 CR4671 (Rel-18, 'F'): Various fixes to RRC_INACTIVE with CN based MT communication handling | Intel | Rel-18 | r03 Agreed. Revised to S2-2401533. | Qian (Ericsson) provides comments Dongjoo (Nokia) asks questions for clarification Saso (Intel) replies to Qian and Dongjoo Qian (Ericsson) provides further responses. Saso (Intel) replies to Qian; provides r01 Steve (Huawei) comments on combination of both Saso (Intel) provides r02 Qian (Ericsson) provides r03 Saso (Intel) is OK with r03 ==== Revisions Deadline ==== Qian (Ericsson) propose to go with r03 ==== Final Comments Deadline ==== | Revised |
| 9.13.2 | S2-2401533 | CR | Approval | 23.502 CR4671R1 (Rel-18, 'F'): Various fixes to RRC_INACTIVE with CN based MT communication handling | Intel, Ericsson | Rel-18 | Revision of S2-2400133r03. Approved | Agreed | |
| 9.13.2 | S2-2400186 | CR | Approval | 23.502 CR4672 (Rel-18, 'F'): Clarification on DL data size | Intel | Rel-18 | r01 Agreed. Revised to S2-2401534. | Qian (Ericsson) provides comments Saso (Intel) replies to Qian (Ericsson) Steve (Huawei) comments. Jinguo(ZTE) comments Saso (Intel) provides r01 Haris(Qualcomm) supports the CR ==== Revisions Deadline ==== Qian (Ericsson) proposes to go with r01 ==== Final Comments Deadline ==== | Revised |
| 9.13.2 | S2-2401534 | CR | Approval | 23.502 CR4672R1 (Rel-18, 'F'): Clarification on DL data size | Intel | Rel-18 | Revision of S2-2400186r01. Approved | Agreed | |
| 9.13.2 | S2-2400436 | CR | Approval | 23.502 CR4684 (Rel-18, 'F'): Data size handling in AMF update | Ericsson | Rel-18 | Approved | Agreed | |
| 9.13.2 | S2-2401087 | CR | Approval | 23.501 CR5288 (Rel-18, 'F'): DL data size reporting for support of MT-SDT | China Mobile | Rel-18 | Noted | Qian (Ericsson) provides r01 Haris(Qualcomm) objects to the CR ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Noted |
| 9.13.2 | S2-2401088 | CR | Approval | 23.502 CR4724 (Rel-18, 'F'): MT-SDT term alignment and support of DL data size reporting configuration | China Mobile | Rel-18 | r02 Agreed. Revised to S2-2401535. | Qian (Ericsson) provides r01 Haris(Qualcomm) provides r02 ==== Revisions Deadline ==== Qian (Ericsson) is ok with r02 ==== Final Comments Deadline ==== | Revised |
| 9.13.2 | S2-2401535 | CR | Approval | 23.502 CR4724R1 (Rel-18, 'F'): MT-SDT term alignment | China Mobile | Rel-18 | Revision of S2-2401088r02. Approved | Agreed | |
| 9.14.2 | - | - | - | Evolution of IMS multimedia telephony service (NG_RTC) | - | - | Docs:=19 | - | |
| 9.14.2 | S2-2400034 | LS In | Information | LS from GSMA UPG: LS on Network Initiated IMS Data Channel | GSMA UPG (UPG08_126) | Responses drafted in S2-2400290, S2-2400543. CC#4: Postponed. | Kefeng (Qualcomm) share the same view of Yi (China Mobile). Yi (China Mobile) comments. Leo (Deutsche Telekom) agrees with Yi (China Mobile) to handle this in Re-19. | Postponed | |
| 9.14.2 | S2-2400292 | DISCUSSION | Approval | Discussion on Network initiated IMS DC. | Samsung | Rel-18 | Noted | Rainer (Nokia) proposes to note the DP DongYeon (Samsung) agrees to note the DP. ==== Revisions Deadline ==== | Noted |
| 9.14.2 | S2-2400301 | CR | Approval | 23.228 CR1378 (Rel-18, 'F'): Network initiated IMS DC | Samsung | Rel-18 | Postponed | Rainer (Nokia) objects to 301. Mu (Huawei) also objects to 301. DongYeon (Samsung) responds to Nokia & Huawei, and provides r01, and asks the group if the simple text in general section can be agreed. Mu (Huawei) comments DongYeon(Samsung) replies to Mu (Huawei). Rainer (Nokia) replies Chris (T-Mobile USA) Agrees with Nokia Ashok (Samsung) comments and propose to consider this paper as postponed ==== Revisions Deadline ==== Rainer (Nokia) ok to postpone | Postponed |
| 9.14.2 | S2-2400290 | LS OUT | Approval | [DRAFT] Reply LS on Network Initiated IMS Data Channel from GSMA UPG | Samsung | Rel-18 | Response to S2-2400034. Noted | Yi (China Mobile) comments. Propose to note this contribution and go forward with 0543. George Foti (Ericsson) proposes to postpone the LS out. The understanding is that the use case in the LS in is about UE initiating a session with an application without requesting DC. The network wants to request DC To be added. Rainer (Nokia) ok to note and use 543 as baseline. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Noted |
| 9.14.2 | S2-2400543 | LS OUT | Approval | [DRAFT] LS on Network Initiated IMS Data Channel | Qualcomm Incorporated | Rel-18 | Response to S2-2400034. CC#4: Postponed | DongYeon (Samsung) provides r02. Yi (China Mobile) comments. r01 is provided George Foti (Ericsson) proposes to postpone the LS out. The understanding is that the use case in the LS in is about UE initiating a session with an application without requesting DC. The network wants to request DC To be added. Rainer (Nokia) provides r03 George (Ericsson) provides comments. Rainer (Nokia) replies George (Ericsson) provides response Mu (Huawei) ask for clarifications George (Ericsson) provides response. I think this is a good way forward and see if the update works for GSMA Chris (T-Mobile USA) Provides comments. Kefeng (Qualcomm) is OK with the way forward and provides r04. DongYeon (Samsung) provides comments. Rainer (Nokia) provides r05 Kefeng (Qualcomm) replies DongYeon (Samsung) comments. George (Ericsson) asks if 301 is the right number .There is none. Rainer (Nokia) provides r06 Yi (China Mobile) ask question. Kefeng (Qualcomm) is OK with r06 Kefeng (Qualcomm) replies George (Ericsson) regarding 301. George (Ericsson) I missed that one. This is clearly out of scope of Release 18. Ashok (Samsung) proposes to postpone this LS OUT Rainer (Nokia) replies to Ashok (Samsung) Ashok (Samsung) insist on postponing this LS OUT to GSMA NG UPG Mu (Huawei) propose we move forward with this LS OUT in this meeting Kefeng (Qualcomm) proposes to move forward with r06 and waiting for feedback from GSMA. ==== Revisions Deadline ==== Ashok (Samsung) comments on r06 and provides r07 in draft Yi (China Mobile) is ok with r06 and aprefer to send the LS out at this meeting. George (Ericsson) Accepts R06 ONLY Wanqiang (Session Chair): we can still accept the new version of LS out. Please clearly indicate which revisions you can accept Rainer (Nokia) does not accept r07 Ashok (Samsung) request for specifics on r07 George (Ericsson) comments on r07 Rainer (Nokia) replies to Ashok. Ashok (Samsung) is not OK with r06 and provides comments on r07 ==== Final Comments Deadline ==== | Postponed |
| 9.14.2 | S2-2400047 | LS In | Action | LS from CT WG4: LS on Clarification on the AR media specification | CT WG4 (C4-235475) | Rel-18 | Response drafted in S2-2400550. Final response in S2-2401536 | Replied to | |
| 9.14.2 | S2-2400550 | LS OUT | Approval | [DRAFT] Reply LS on Clarification on the AR media specification | Qualcomm Incorporated | Rel-18 | Response to S2-2400047. r01 + clean up Agreed. Revised to S2-2401536. | George Foti (Ericsson) proposes to postpone the LS out. Yi (China Mobile) comment that sending our feedback to SA4 may help. Rainer (Nokia) comments George (Ericsson) asks a question Rainer (Nokia) replies Kefeng (Qualcomm) is OK with Rainer (Nokia) replies DongYeon (Samsung) prefers Nokia's text, but not sure on Answer to Q1. Rainer (Nokia) would be ok to combine the answers Mu (Huawei) Comments, Update the text. Kefeng (Qualcomm) provides r01 based on the comments. Rainer (Nokia) is ok with r01 ==== Revisions Deadline ==== George (Ericsson) Accepts R01 ONLY. ==== Final Comments Deadline ==== | Revised |
| 9.14.2 | S2-2401536 | LS OUT | Approval | Reply LS on Clarification on the AR media specification | SA WG2 | Rel-18 | Revision of S2-2400550r01 + clean up. Approved | Approved | |
| 9.14.2 | S2-2401216 | LS OUT | Approval | [DRAFT] LS on AR telephony service parameter | Huawei, HiSilicon | Rel-18 | Which incoming LS ? Noted | George Foti (Ericsson) proposes to postpone the LS out. Rainer (Nokia) propose to note Leo (Deutsche Telekom) propose to note DongYeon (Samsung) propose to note. ==== Revisions Deadline ==== George (Ericsson) proposes to note the CR ==== Final Comments Deadline ==== | Noted |
| 9.14.2 | S2-2400138 | CR | Approval | 23.228 CR1361R1 (Rel-18, 'F'): Clause Number Correction | Ericsson | Rel-18 | Revision of (unhandled) S2-2312136. Approved | Agreed | |
| 9.14.2 | S2-2400333 | CR | Approval | 23.228 CR1379 (Rel-18, 'F'): Clarification on SDP handling of data channel for terminating IMS network | China Mobile | Rel-18 | Noted | Kefeng (Qualcomm) provides comments, and suggests to study the case in Rel-19. George Foti (Ericsson) proposes to postpone the CR. See additional comments Rainer (Nokia) proposes to note. Yi (China Mobile) replies and provides r01. DongYeon (Samsung) provides comments, and proposes to study in Rel-19 (e.g. KI#3). Yi (China Mobile) replies to Dongyeon. Kefeng (Qualcomm) proposes to postpone the CR and provides general principes on handling the scenarios of UE without IMS DC subscription. Rainer (Nokia) comments, prefers to postpone this CR DongYeon (Samsung) ask questions. Yi (China Mobile) replies. George (Ericsson) asks a question ==== Revisions Deadline ==== George (Ericsson) proposes to note the CR. DongYeon (Samsung) proposes to note. Rainer (Nokia) agrees to not the CR Kefeng (Qualcomm) agrees to note the CR George (Ericsson) provides response to Yi Yi (China Mobile) ok to postpone. ==== Final Comments Deadline ==== | Noted |
| 9.14.2 | S2-2400334 | CR | Approval | 23.228 CR1380 (Rel-18, 'F'): Update of the downloading of data channel application and data channel application list | China Mobile | Rel-18 | Postponed | Kefeng (Qualcomm) provides comments and proposes to postpone the CR. George Foti (Ericsson) proposes to postpone the CR. See comments below Rainer (Nokia) proposes to note DongYeon (Samsung) provides comments. Yi (China Mobile) replies and provide r01. ==== Revisions Deadline ==== Yi (China Mobile) propose to agree r01. George (Ericsson) proposes to note the CR. Unclear requirement DongYeon (Samsung) provides comments on r01. DongYeon (Samsung) proposes to mark this paper as merged to 1215. Yi (China Mobile) replies to DonYeon and propose to agree r01 to align with SA6. Hao (ZTE) suggests to go with r01, it considers other WG's work and there is no conflict with current SA2 specification. Rainer (Nokia) proposes to mark this CR as postponed an add SA6 reference later Yi (China Mobile) explains why the CR is needed. Rainer (Nokia) replies ==== Final Comments Deadline ==== | Postponed |
| 9.14.2 | S2-2400868 | CR | Approval | 23.228 CR1381 (Rel-18, 'F'): KI#2_ Update AR communicate procedure | Vivo | Rel-18 | Postponed | Kefeng (Qualcomm) provide comments. Xiaowen Sun(vivo) responds to George and Yi. Yi (China Mobile) comments. George Foti (Ericsson) asks if this scenario is where UAa support AR and UEb does not support AR rendering George (Ericsson) provides comments. We share the same view that this is not needed. There are different cases, we don't need to document all of them Rainer (Nokia) proposes to note as this is not Cat F. Xiaowen Sun (vivo) replies to Rainer and George. Xiaowen Sun (vivo) provides r01. Hao (ZTE) comments on r01. Xiaowen (vivo) provides r02 Hao (ZTE) provides further comment on r02. Kefeng (Qualcomm) provide comments on r02. Xiaowen (vivo) agrees with Kenny and Hao, and provides r03. Rainer (Nokia) comments on the call flow. George (Ericsson) provides comment. Xiaowen (vivo) responds to George and Rainer. Rainer (Nokia) provides r06 Kefeng (Qualcomm) provides r07 Xiaowen (vivo) is ok for r07. Rainer (Nokia) is fine with r07 Yi (China Mobile) a minor comment to step 4 in the figure. Xiaowen (vivo) responds to Yi (China Mobile) George (Ericsson) asks a question Xiaowen (vivo) responds to George (Ericsson). George (Ericsson) responds Xiaowen (vivo) provide extra responds to George (Ericsson). Mu (Huawei) asks for clarification Xiaowen (vivo) responds to George (Ericsson) and Mu (Huawei) Mu (Huawei) comments Rainer (Nokia) provides r10 ==== Revisions Deadline ==== Xiaowen (vivo) is ok to postpone Rainer (Nokia) ok to postpone George (Ericsson) proposes to postpone the CR Xiaowen (vivo)replies to Rainer (Nokia) ==== Final Comments Deadline ==== | Postponed |
| 9.14.2 | S2-2400894 | CR | Approval | 23.228 CR1382 (Rel-18, 'F'): Update on IMS DC Capability Negotiation | ZTE | Rel-18 | Approved | Agreed | |
| 9.14.2 | S2-2400895 | CR | Approval | 23.228 CR1383 (Rel-18, 'F'): Clarification on Bootstrap Data Channel Setup Signalling procedure | ZTE | Rel-18 | r02 Agreed. Revised to S2-2401537. | Yi (China Mobile) comments. Hao (ZTE) responds and provided r01. Rainer (Nokia) comments Rainer (Nokia) adding missing info in subject line Hao (ZTE) responds and provided r02. DongYeon (Samsung) provides comments, change in Figure is not needed. Hao (ZTE) responds to DongYeon (Samsuang). ==== Revisions Deadline ==== Yi (China Mobile) is ok with r02. George (Ericsson) Accepts R02 ONLY. Rainer (Nokia) ok with r02 ==== Final Comments Deadline ==== | Revised |
| 9.14.2 | S2-2401537 | CR | Approval | 23.228 CR1383R1 (Rel-18, 'F'): Clarification on Bootstrap Data Channel Setup Signalling procedure | ZTE | Rel-18 | Revision of S2-2400895r02. Approved | Agreed | |
| 9.14.2 | S2-2400896 | CR | Approval | 23.228 CR1384 (Rel-18, 'F'): Update on UE Centric AR communication Procedure | ZTE | Rel-18 | Not Handled | Hao (ZTE) responds. George Foti (Ericsson) provides comments. Please update step 5 to read UE-B. DongYeon (Samsung) asks - should this paper unhandled or not? Rainer (Nokia) notes that 896 is marked as not handled. Hao (ZTE) confirms this paper could be marked as 'Unhandled' per the indication from rapporteur before the meeting. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | - |
| 9.14.2 | S2-2401159 | CR | Approval | 23.228 CR1385 (Rel-18, 'F'): IMS DC service subscription clarification | Samsung | Rel-18 | Postponed | Ashok (Samsung) provides clarifications. Kefeng (Qualcomm) provides comments. Yi (China Mobile) comments. George Foti (Ericsson) proposes to note the CR. SDP supports that already. There is nothing new. If DC is disabled and if originating UE anyway included DC in the SDP offer, setting DC m= line port to 0 in the returned SDP answer should be indication enough. Rainer (Nokia) does not believe this is necessary, not that this is Cat F George (Ericsson) provides response to Ashok Ashok (Samsung) provides response to Rainer (Alessio) and George (Ericsson). Mu (Huawei) Comments. Ashok (Samsung) responds to Mu (Huawei) Mu (Huawei) further comments. Ashok (Samsung) ask a question to Mu (Huawei). Rainer (Nokia) not convinced this CR is needed Mu (Huawei) replies to Ashok ==== Revisions Deadline ==== Ashok (Samsung) agrees to postpone the CR Yi (China Mobile) agree to postpone and have more discussion. George (Ericsson) proposes to note the CR. More discussion is required to assess whether there is a need to do anything or not. Rainer (Nokia) ok to postpone ==== Final Comments Deadline ==== | Postponed |
| 9.14.2 | S2-2401215 | CR | Approval | 23.228 CR1386 (Rel-18, 'F'): 23.228 Editorial change for the DC procedure | Huawei, HiSilicon | Rel-18 | Approved | Rainer (Nokia) asks for clarification Mu (Huawei) comments DongYeon (Samsung) asks question. Mu (Huawei) replies ==== Revisions Deadline ==== DongYeon (Samsung) asks if the reason for change in coversheet can be revised to add the reference of SA6 work. Rainer (Nokia) is ok with r00 Mu (Huawei) replies to DongYeon, Sorry it is after the revision deadline lets update the reference later if needed. ==== Final Comments Deadline ==== | Agreed |
| 9.15.2 | - | - | - | Access Traffic Steering, Switching and Splitting support in the 5GS; Phase 3 (ATSSS_Ph3) | - | - | Docs:=12 | - | |
| 9.15.2 | S2-2400348 | CR | Approval | 23.502 CR4678 (Rel-18, 'F'): Corrections on support for EPC IWK with MA PDU Sessions | Ericsson | Rel-18 | r01 Agreed. Revised to S2-2401538. | Rainer (Nokia) comments Stefan (Ericsson) replies and provides r01 ==== Revisions Deadline ==== Rainer (Nokia) is ok with r01 ==== Final Comments Deadline ==== | Revised |
| 9.15.2 | S2-2401538 | CR | Approval | 23.502 CR4678R1 (Rel-18, 'F'): Corrections on support for EPC IWK with MA PDU Sessions | Ericsson | Rel-18 | Revision of S2-2400348r01. Approved | Agreed | |
| 9.15.2 | S2-2400394 | CR | Approval | 23.501 CR5230 (Rel-18, 'F'): Clarify MRU handling for non-3GPP access path switching when UE has only one PDU Session | MediaTek Inc. | Rel-18 | r01 Agreed. Revised to S2-2401539. | Rainer (Nokia) comments Chia-Lin (MediaTek) provides r01 Rainer (Nokia) is ok with r01. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 9.15.2 | S2-2401539 | CR | Approval | 23.501 CR5230R1 (Rel-18, 'F'): Clarify MRU handling for non-3GPP access path switching when UE has only one PDU Session | MediaTek Inc. | Rel-18 | Revision of S2-2400394r01. Approved | Agreed | |
| 9.15.2 | S2-2400775 | CR | Approval | 23.501 CR5261 (Rel-18, 'F'): Clarifications on interworking with EPS | Huawei, HiSilicon | Rel-18 | r02 Agreed. Revised to S2-2401540. | Myungjune (LGE) comments Yishan (Huawei) answers to Stefano (Qualcomm) Stefano (Qualcomm) asks clarification Yishan (Huawei) answers to Myungjune (LGE) Myungjune (LGE) replies to Yishan (Huawei) Rainer (Nokia) asks for clarification. Ashok (Samsung) comments. Rainer (Nokia) agrees with Ashok Myungjune (LGE) replies to Ashok (Samsung) Yishan (Huawei) provides r01 Rainer (Nokia) comments Yishan (Huawei) answers to Rainer (Nokia) Yishan (Huawei) provides r02 Rainer (Nokia) is ok with r02 ==== Revisions Deadline ==== Myungjune (LGE) is ok with r02 ==== Final Comments Deadline ==== | Revised |
| 9.15.2 | S2-2401540 | CR | Approval | 23.501 CR5261R1 (Rel-18, 'F'): Clarifications on interworking with EPS | Huawei, HiSilicon | Rel-18 | Revision of S2-2400775r02. Approved | Agreed | |
| 9.15.2 | S2-2400776 | CR | Approval | 23.502 CR4708 (Rel-18, 'F'): Clarifications on interworking with EPS | Huawei, HiSilicon | Rel-18 | r02 Agreed. Revised to S2-2401541. | Stefano (Qualcomm) see comment on S2-2400775 Rainer (Nokia) comments Stefan (Ericsson) comments Yishan (Huawei) provides r01 Stefan (Ericsson) provides r02 Yishan (Huawei) is ok with r02 provided by Stefan (Ericsson) ==== Revisions Deadline ==== Rainer (Nokia) is ok with r02 ==== Final Comments Deadline ==== | Revised |
| 9.15.2 | S2-2401541 | CR | Approval | 23.502 CR4708R1 (Rel-18, 'F'): Clarifications on interworking with EPS | Huawei, HiSilicon, Ericsson | Rel-18 | Revision of S2-2400776r02. Approved | Agreed | |
| 9.15.2 | S2-2401272 | CR | Approval | 23.501 CR5299 (Rel-18, 'F'): MPQUIC support related corrections | Nokia, Nokia Shanghai Bell | Rel-18 | Approved | Stefano (Qualcomm) not FASMO, suggests noting ==== Revisions Deadline ==== Rainer (Nokia) proposes to agree ==== Final Comments Deadline ==== | Agreed |
| 9.15.2 | S2-2401273 | CR | Approval | 23.503 CR1264 (Rel-18, 'F'): ATSSS-LL supported SM related corrections | Nokia, Nokia Shanghai Bell | Rel-18 | Noted | Stefano (Qualcomm) question for clarification Rainer (Nokia) replies. Stefan (Ericsson) tries to dig in the memory and comments Rainer (Nokia) has no strong view on this. Rainer (Nokia) comments further Stefan (Ericsson) replies Stefan (Ericsson) proposes to NOTE this CR and work on a 23.501 CR for the next meeting Rainer (Nokia) is ok to note ==== Revisions Deadline ==== | Noted |
| 9.15.2 | S2-2401274 | CR | Approval | 23.502 CR4736 (Rel-18, 'F'): Error fix to MA PDU Session establishment with non-3GPP access connected to EPC | Nokia, Nokia Shanghai Bell | Rel-18 | r02 Agreed. Revised to S2-2401542. | Yishan (Huawei) provides comments Stefano (Qualcomm) comments Rainer (Nokia) provides r1. Stefan (Ericsson) comments Rainer (Nokia) replies Stefan (Ericsson) asks whether the NOTE is really correct Stefan (Ericsson) proposes to go with a version removing the NOTE Rainer (Nokia) provides r02. Stefan (Ericsson) is ok with r02 Yishan (Huawei) is ok with r02 ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 9.15.2 | S2-2401542 | CR | Approval | 23.502 CR4736R1 (Rel-18, 'F'): Error fix to MA PDU Session establishment with non-3GPP access connected to EPC | Nokia, Nokia Shanghai Bell | Rel-18 | Revision of S2-2401274r02. Approved | Agreed | |
| 9.16.2 | - | - | - | UPF enhancement for Exposure And SBA (UPEAS) | - | - | Docs:=6 | - | |
| 9.16.2 | S2-2400362 | CR | Approval | 23.502 CR4680 (Rel-18, 'F'): Correction of UPF exposure service | Ericsson | Rel-18 | Check Affected Clauses! Postponed. r07 agreed. Revised to S2-2401644. | Laurent (Nokia): provides r01 Fenqin (Huawei): provides r02 Laurent (Nokia): provides r03 Fenqin (Huawei): provides r04. Magnus H (Ericsson) comments and provides r05 and r06, but prefers r05 Fenqin (Huawei) responds to Magnus and prefer r06. Yan (China Mobile) comments Fenqin (Huawei) provides r07 Magnus H (Ericsson) objects to r07 and proposes we go with r06 ==== Revisions Deadline ==== Yan (China Mobile) suggests to go with r06 Fenqin (Huawei) insist to go with r07, i.e. without the service operation part. Fenqin (Huawei) accept only r07, i.e. without the service operation part. Laurent (Nokia): can only live with R01, R03, R07 OR can live with R05, R06 if in R05/R06 following words are added in § 5.2.26.2.3 : '( i.e.. needs to be mapped to a single N4 session)' in the added text after the words ' single UE'. objects to other versions Magnus H (Ericsson) ask Fenqin and Laurent how 'Reason for change' is solved with R07? Proposed the following way forward: Take changes of clauses 4.3.2.2.1and 4.4.1.2 from r06/r07 (which are the same) make the following update to existing clause 5.2.26.2.3, after current text in 'Input, Optional': ' If the target of the subscription (e.g. identified by traffic filtering information), corresponds to a single UE, the NF consumer needs to provide the corresponding DNN and S-NSSAI, address of the UE, and if available IP domain' Fenqin (Huawei) responds and still suggest to go with r07. ==== Final Comments Deadline ==== Magnus H (Ericsson) OK to go with r07 to start with for this meeting | Revised |
| 9.16.2 | S2-2401644 | CR | Approval | 23.502 CR4680R1 (Rel-18, 'F'): Correction of UPF exposure service | Ericsson, Nokia | Rel-18 | Revision of S2-2400362r07. Approved | Agreed | |
| 9.16.2 | S2-2400631 | CR | Approval | 23.502 CR4697 (Rel-18, 'F'): Clarification of usage of AoI | Vivo | Rel-18 | r02 Agreed. Revised to S2-2401423. | Laurent (Nokia): provides r01 Marisa (Ericsson) provides r02 and comments ==== Revisions Deadline ==== Huazhang (vivo) thanks Marisa and Laurent, prefer to go with r02 Marisa (Ericsson) can only accept r02 Fenqin (Huawei) is ok with r02 ==== Final Comments Deadline ==== | Revised |
| 9.16.2 | S2-2401423 | CR | Approval | 23.502 CR4697R1 (Rel-18, 'F'): Clarification of usage of AoI | Vivo, Nokia, Nokia Shanghai Bell, Ericsson | Rel-18 | Revision of S2-2400631r02. Approved | Agreed | |
| 9.16.2 | S2-2400689 | CR | Approval | 23.502 CR4703 (Rel-18, 'F'): Corrections for the Nupf_EventExposure Service | Huawei, HiSilicon | Rel-18 | Postponed | Marisa Mas (Ericsson) provides r01 Laurent (Nokia): provides r02 Marisa Mas (Ericsson) provides r03 and comments Laurent (Nokia): Comments: need in final version to ensure § 5.2.26.2.2, 5.2.26.2.3 don't get removed Mirko (Huawei) responds. Marisa (Ericsson) responds. Marisa (Ericsson) provides reponses Kefeng (Qualcomm) proposed correction of typo Mirko (Huawei) responds and proposes to postpone this CR. ==== Revisions Deadline ==== Laurent (Nokia): objects to R00 and R01. Can agree with R02/R03 but also to postpone. Perhaps keep track we will use R03 as basis for future work? | Postponed |
| 9.16.2 | S2-2401133 | CR | Approval | 23.502 CR4726 (Rel-18, 'F'): Nupf_EventExposure_Notify service operation subscribed implicitly or explicitly | Orange | Rel-18 | Approved | Agreed | |
| 9.17.2 | - | - | - | Edge Computing Phase 2 (EDGE_Ph2) | - | - | Docs:=43 | - | |
| 9.17.2 | - | - | - | KI#1 Generic | - | - | Docs:=4 | - | |
| 9.17.2 | S2-2400096 | CR | Approval | 23.548 CR0187R2 (Rel-18, 'F'): EASDF functional description update | China Mobile | Rel-18 | Revision of (Unhandled) S2-2312375. r01 Agreed. Revised to S2-2401424. | Hui (Huawei) provides comments. Tezcan (Nokia) asks clarifications. Dan (China Mobile) reply. Tezcan (Nokia) replies to Dan and suggests noting. Dan (China Mobile) replies to Tezcan. Tezcan (Nokia) asks further clarification Changhong (Intel) comments. Dan(China Mobile) reply Dan(China Mobile) provide r01 with only changing the 'query' to 'Query' ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 9.17.2 | S2-2401424 | CR | Approval | 23.548 CR0187R3 (Rel-18, 'F'): EASDF functional description update | China Mobile | Rel-18 | Revision of S2-2400096r01. Approved | Agreed | |
| 9.17.2 | S2-2401362 | CR | Approval | 23.503 CR1201R1 (Rel-18, 'F'): Roaming procedures with a distinction to HR-SBO scenario | Nokia, Nokia Shanghai Bell | Rel-18 | Revision of (unhandled) S2-2312179. r04 Agreed. Revised to S2-2401425. | Hui (Huawei) provides comments. Tezcan (Nokia) replies to Hui (Huawei). Magnus H (Ericsson) provides comments Tezcan (Nokia) provides r01 Hui (Huawei) provides r02 Tezcan (Nokia) responds and provides r03 Hui (Huawei) think r03 is misleading. Tezcan (Nokia) provides r04 Hui(Huawei) fine with r04 ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 9.17.2 | S2-2401425 | CR | Approval | 23.503 CR1201R2 (Rel-18, 'F'): Roaming procedures with a distinction to HR-SBO scenario | Nokia, Nokia Shanghai Bell | Rel-18 | Revision of S2-2401362r04. Approved | Agreed | |
| 9.17.2 | - | - | - | KI#1 Offload identifier/information | - | - | Docs:=11 | - | |
| 9.17.2 | S2-2400094 | CR | Approval | 23.548 CR0164R3 (Rel-18, 'F'): Enhancement on VPLMN specific offloading policy/information | China Mobile | Rel-18 | Revision of (Unhandled) S2-2312371. Noted | Hyesung (Samsung) comments. Stefano (Qualcomm) has concerns and suggests noting. Magnus (Ericsson) provides comments Tezcan (Nokia) supports suggestion from Hyesung (Samsung). Hui(Huawei) provides comments. Magnus H (Ericsson) provides comments ==== Revisions Deadline ==== Dan (China Mobile) Suggest to postpond this paper Magnus H (Ericsson) objects to this CR ==== Final Comments Deadline ==== | Noted |
| 9.17.2 | S2-2400095 | CR | Approval | 23.502 CR4382R3 (Rel-18, 'F'): Service enhancement on offload identifier delivery | China Mobile | Rel-18 | Revision of (Unhandled) S2-2312372. Merged into S2-2401427 | Hyesung (Samsung) comments. Stefano (Qualcomm) suggests a revision Magnus (Ericsson) same comment as on 0094 Hui (Huawei) suggests to consider this paper as merged into S2-2400807. Dan (China Mobile) agree to merge this into S2-2400807. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 9.17.2 | S2-2400675 | CR | Approval | 23.548 CR0188R1 (Rel-18, 'F'): Correction on Offload Identifier | Samsung | Rel-18 | Revision of (unhandled) S2-2312064. Merged into S2-2401426 | Hui (Huawei) suggests to consider this paper as merged into S2-2400675. Hyesung (Samsung) is ok to merge this paper into S2-2400675. Patrice (Huawei, rapporteur) clarifies that the proposal is to merge S2-2400675 to S2-2400806 (and not to itself). ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 9.17.2 | S2-2400806 | CR | Approval | 23.548 CR0202R1 (Rel-18, 'F'): KI#1 Corrections on Offload Identifier and misalignments in services | Huawei, HiSilicon | Rel-18 | Revision of (unhandled) S2-2312964. r08 Agreed. Revised to S2-2401426, merging S2-2400675 | Magnus (Ericsson) provided a r01 Tezcan (Nokia) provides r02. Dan(China Mobile) provides r03. Hui(Huawei) provides r04. Tezcan (Nokia) provides r05. Magnus H (Ericsson) provides r06 Hui (Huawei) asks question. Tezcan (Nokia) agrees with Hui on using single NF for offload identifier assignment Magnus H (Ericsson) provides r07 Tezcan (Nokia) provides comments to r07 Hui (Huawei) provides r08 ==== Revisions Deadline ==== Magnus H (Ericsson) provides comments are OK with r08 and wants to co-sign Tezcan (Nokia) is OK with r08 ==== Final Comments Deadline ==== | Revised |
| 9.17.2 | S2-2401426 | CR | Approval | 23.548 CR0202R2 (Rel-18, 'F'): KI#1 Corrections on Offload Identifier and misalignments in services | Huawei, HiSilicon, Ericsson | Rel-18 | Revision of S2-2400806r08, merging S2-2400675. Approved | Agreed | |
| 9.17.2 | S2-2400807 | CR | Approval | 23.502 CR4644R1 (Rel-18, 'F'): KI#1 Corrections on Offload Identifier and misalignments in services | Huawei, HiSilicon | Rel-18 | Revision of (unhandled) S2-2312965. r02 + changes Agreed. Revised to S2-2401427, merging S2-2400095 and S2-2400885 | Yuan Tao (CATT) provides comments. Tezcan (Nokia) provides comments/concerns. Hui(Huawei) replies to Tezcan. Yuan Tao (CATT) replies to Hui (Huawei) replies. Tezcan (Nokia) still has concerns on HR-SBO related updates to Namf_Communication_CreateUEContext Hui (Huawei) replies to Tezcan Yuan Tao (CATT) provides r01. Hui (Huawei) fine with r01. Tezcan (Nokia) replies to Hui Hui (Huawei) replies to Tezcan and provides r02 ==== Revisions Deadline ==== Tezcan (Nokia) is fine with r02 if the changes on 5.2.8.2.3 and 5.2.8.2.10 (regarding EAS IP replacement and target DNAI) are removed as they are covered in 01222r01. ==== Final Comments Deadline ==== | Revised |
| 9.17.2 | S2-2401427 | CR | Approval | 23.502 CR4644R2 (Rel-18, 'F'): KI#1 Corrections on Offload Identifier and misalignments in services | Huawei, HiSilicon, CATT | Rel-18 | Revision of S2-2400807r02 + changes, merging S2-2400095 and S2-2400885. Approved | Agreed | |
| 9.17.2 | S2-2400808 | CR | Approval | 23.503 CR1226R1 (Rel-18, 'F'): KI#1 Corrections on Offload Identifier and misalignments in services | Huawei, HiSilicon | Rel-18 | Revision of (unhandled) S2-2312966. r01 Agreed. Revised to S2-2401428. | Magnus (Ericsson) provides r01 Hui (Huawei) fine with r01 ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 9.17.2 | S2-2401428 | CR | Approval | 23.503 CR1226R2 (Rel-18, 'F'): KI#1 Corrections on Offload Identifier and misalignments in services | Huawei, HiSilicon | Rel-18 | Revision of S2-2400808r01. Approved | Agreed | |
| 9.17.2 | S2-2400809 | CR | Approval | 23.548 CR0205R1 (Rel-18, 'F'): KI#1 Applicability of VPLMN specific offloading information | Huawei, HiSilicon | Rel-18 | Revision of (unhandled) S2-2313112. r05 Agreed. Revised to S2-2401429. | Tianqi (China Unicom) provides r01. Magnus H (Ericsson) provides r02 based on r00 Tianqi (China Unicom) comments. Hui (Huawei) provides r04, skipped r03. Magnus H (Ericsson) provides comments Tezcan (Nokia) has concern and asks clarifications Hui (Huawei) provides r05 and responses to Tezcan Tianqi (China Unicom) is ok with r05. Tezcan (Nokia) replies to Hui ==== Revisions Deadline ==== Hui (provides) r06 and ask to confirm in CC#3 Magnus H (Ericsson) is fine with r05 and Tezcan's proposal. Want editorial update to replace 'ECS option' with 'EDNS Client Subnet (ECS) option (as defined in RFC 7871 [6])'. This to be consistent with rest of the spec Tezcan (Nokia) prefers to postpone Hui (Huawei) replies to Tezcan ==== Final Comments Deadline ==== Tezcan (Nokia) replies to Hui and asks to postpone this paper. | Revised |
| 9.17.2 | S2-2401429 | CR | Approval | 23.548 CR0205R2 (Rel-18, 'F'): KI#1 Applicability of VPLMN specific offloading information | Huawei, HiSilicon | Rel-18 | Revision of S2-2400809r05. CC#4: Postponed | Postponed | |
| 9.17.2 | - | - | - | KI#1 Session AMBR | - | - | Docs:=6 | - | |
| 9.17.2 | S2-2400262 | CR | Approval | 23.502 CR4573R1 (Rel-18, 'F'): VPLMN constraint on DL Session AMBR for Offloading | Samsung | Rel-18 | Revision of (unhandled) S2-2312245. Postponed | Magnus O (Ericsson) Questions FASMO Stefano (Qualcomm) agrees with Ericsson Hyesung (Samsung) replies and provides r01 ==== Revisions Deadline ==== Magnus (Ericsson) Propose to note/postpone 262 and 263 ==== Final Comments Deadline ==== | Postponed |
| 9.17.2 | S2-2400263 | CR | Approval | 23.501 CR5143R1 (Rel-18, 'F'): VPLMN constraint on DL Session AMBR for Offloading | Samsung | Rel-18 | Revision of (unhandled) S2-2312647. Postponed | Stefano (Qualcomm) wonders if this is FASMO at all. Magnus (Ericsson) Agrees with Stefano, adding optional information does not seem to be a FASMO Hyesung (Samsung) replies ==== Revisions Deadline ==== Magnus (Ericsson) Propose to note/postpone 262 and 263 ==== Final Comments Deadline ==== | Postponed |
| 9.17.2 | S2-2400597 | CR | Approval | 23.548 CR0193R1 (Rel-18, 'F'): Clarification on DL Session AMBR for Offloading in HR-SBO Sessions | Samsung | Rel-18 | Revision of (unhandled) S2-2312237. r02 Agreed. Revised to S2-2401409. | Hui (Huawei) provides r01 Hyesung (Samsung) provides comments on r01 Hyesung (Samsung) provides r02 Hui (Huawei) fine with r02 ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 9.17.2 | S2-2401409 | CR | Approval | 23.548 CR0193R2 (Rel-18, 'F'): Clarification on DL Session AMBR for Offloading in HR-SBO Sessions | Samsung | Rel-18 | Revision of S2-2400597r02. Approved | Agreed | |
| 9.17.2 | S2-2400598 | CR | Approval | 23.501 CR5095R1 (Rel-18, 'F'): Clarification on DL Session AMBR for Offloading in HR-SBO sessions | Samsung | Rel-18 | Revision of (unhandled) S2-2312238. r03 Agreed. Revised to S2-2401430. | Stefano (Qualcomm) seeks clarifications and wonder if this is FASMO Hyesung (Samsung) replies and provides r01 Hui (Huawei) provides r02 Hyesung (Samsung) provides comments/suggestion on r02 Hyesung (Samsung) provides r03 ==== Revisions Deadline ==== Hui (Huawei) fine with r03 ==== Final Comments Deadline ==== | Revised |
| 9.17.2 | S2-2401430 | CR | Approval | 23.501 CR5095R2 (Rel-18, 'F'): Clarification on DL Session AMBR for Offloading in HR-SBO sessions | Samsung | Rel-18 | Revision of S2-2400598r03. Approved | Agreed | |
| 9.17.2 | - | - | - | KI#1 AF influence | - | - | Docs:=6 | - | |
| 9.17.2 | S2-2400344 | CR | Approval | 23.502 CR4677 (Rel-18, 'F'): Clarifications on processing AF request for HR-SBO session | Ericsson | Rel-18 | Postponed | Stefano (Qualcomm) expresses concerns Tezcan (Nokia) provides r01 to co-sign and to expand on reason for change in the cover page. Hui (Huawei) has concern on the changes. Magnus H (Ericsson) thanks Tezcan Magnus H (Ericsson) answers Hui Hui (Huawei) replies to Magnus Hui (Huawei) provides r02 Magnus H (Ericsson) provides comments ==== Revisions Deadline ==== Hui (Huawei) proposes to postpone this CR ==== Final Comments Deadline ==== | Postponed |
| 9.17.2 | S2-2400624 | CR | Approval | 23.502 CR4570R1 (Rel-18, 'F'): Notification of serving PLMN change to AF | Vivo | Rel-18 | Revision of (unhandled) S2-2312225. r07 + changes Agreed. Revised to S2-2401431. | Stefano (Qualcomm) identifies inconsistencies and believes it is not FASMO Huazhang (vivo) provides r01 Magnus H (Ericsson) r01 needs editorial update Huazhang (vivo) provides r02 to reflect the comments from Magnus Tezcan (Nokia) has concerns. Huazhang (vivo) provides r03 to reflect the comments from Tezcan Tezcan (Nokia) provides further comments. Huazhang (vivo) provides r04 Tezcan (Nokia) provides r05. Hui(Huawei) provides comments. Huazhang (vivo) reply to Hui and provide r06 based on r05, add a wording: local 'traffic' offload Hui(Huawei) fine with r06. Tezcan (Nokia) is fine with r06 and wants to co-sign Huazhang (vivo) provides r07 based on r06, and adds Nokia and Nokia Shanghai Bell as co-sign, clean the change on change, thanks Tezcan's support ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 9.17.2 | S2-2401431 | CR | Approval | 23.502 CR4570R2 (Rel-18, 'F'): Notification of serving PLMN change to AF | Vivo, Nokia, Nokia Shanghai Bell | Rel-18 | Revision of S2-2400624r07 + changes. Approved | Agreed | |
| 9.17.2 | S2-2400810 | CR | Approval | 23.548 CR0213 (Rel-18, 'F'): KI#1 Corrections on AF traffic influence and related information transmission in HR-SBO case | Huawei, HiSilicon | Rel-18 | r03 + changes Agreed. Revised to S2-2401432. | Magnus H (Ericsson) has concerns Hui (Huawei) replies to Magnus. Magnus H (Ericsson) provides comments Tezcan (Nokia) has the similar concern raised to S2-2400811 on internal group identifier. Hui (Huawei) provides r01. Tezcan (Nokia) provides r02 Hui (Huawei) provides r03 Tezcan (Nokia) is fine with r03 ==== Revisions Deadline ==== Hui(Huawei) provides draft r04 = r03 + correct date in cover page. ==== Final Comments Deadline ==== | Revised |
| 9.17.2 | S2-2401432 | CR | Approval | 23.548 CR0213R1 (Rel-18, 'F'): KI#1 Corrections on AF traffic influence and related information transmission in HR-SBO case | Huawei, HiSilicon | Rel-18 | Revision of S2-2400810r03 + changes. Approved | Agreed | |
| 9.17.2 | S2-2400811 | CR | Approval | 23.502 CR4713 (Rel-18, 'F'): KI#1 Corrections on AF traffic influence and related information transmission in HR-SBO case | Huawei, HiSilicon | Rel-18 | Noted | Tezcan (Nokia) has some comments/concerns and proposes to merge this paper to S2-2400344. Hui(Huawei) replies to Tezcan. Magnus H (Ericsson) has comments and proposes to merge this paper to S2-2400344, Hui (Huawei) provides r01 Magnus H (Ericsson) has concerns since we have not concluded discussion on 0344, any need for this CR should be merged with 0344 once we have concluded the discussion. Hui (Huawei) clarify this is not really related to what we discussed in 0344 thread. ==== Revisions Deadline ==== Magnus H (Ericsson) objects to this CR since it overlaps with 0344. Suggest to have a merged common contribution taking 0344 and this CR into account for SA2#161 Hui (Huawei) fine to note this CR with understanding we will continue the work in 0344. | Noted |
| 9.17.2 | - | - | - | KI#1 DNS related aspects | - | - | Docs:=2 | - | |
| 9.17.2 | S2-2400622 | CR | Approval | 23.502 CR4569R1 (Rel-18, 'F'): Configuration of DNS server address delivery from HPLMN to VPLMN | Vivo | Rel-18 | Revision of (unhandled) S2-2312222. r01 Agreed. Revised to S2-2401433. | Hui (Huawei) provides r01 ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 9.17.2 | S2-2401433 | CR | Approval | 23.502 CR4569R2 (Rel-18, 'F'): Configuration of DNS server address delivery from HPLMN to VPLMN | Vivo | Rel-18 | Revision of S2-2400622r01. Approved | Agreed | |
| 9.17.2 | - | - | - | KI#1 EAS IP replatrelated | - | - | Docs:=5 | - | |
| 9.17.2 | S2-2400885 | CR | Approval | 23.502 CR4396R2 (Rel-18, 'F'): Update on SMF service operation | CATT | Rel-18 | Revision of (unhandled) S2-2312877. Merged into S2-2401427 | Tezcan (Nokia) provides comments/concerns Yuan Tao (CATT) merges this paper into S2-2400807. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 9.17.2 | S2-2401221 | CR | Approval | 23.548 CR0207R1 (Rel-18, 'F'): Clarifications on the case AF interacts with HPLMN to influence HR-SBO traffic at VPLMN | Nokia | Rel-18 | Revision of (unhandled) S2-2313203. r01 + changes Agreed. Revised to S2-2401434. | Hui (Huawei) provides r01 Tezcan (Nokia) provides comments to Hui Hui (Huawei) provides comments to Tezcan Tezcan (Nokia) replies to Hui Hui (Huawei) replies to Tezcan. Tezcan (Nokia) responds to Hui ==== Revisions Deadline ==== Hui (Huawei) can only accept r01 Tezcan (Nokia) is fine with r01 + bringing back the removed change on step 1 in 6.7.3.2 Hui (Huawei) is fine with r01 + bringing back the removed change on step 1 in 6.7.3.2 ==== Final Comments Deadline ==== | Revised |
| 9.17.2 | S2-2401434 | CR | Approval | 23.548 CR0207R2 (Rel-18, 'F'): Clarifications on the case AF interacts with HPLMN to influence HR-SBO traffic at VPLMN | Nokia | Rel-18 | Revision of S2-2401221r01 + changes. Approved | Agreed | |
| 9.17.2 | S2-2401222 | CR | Approval | 23.502 CR4732 (Rel-18, 'F'): Clarifications on the case AF interacts with HPLMN to influence HR-SBO traffic at VPLMN | Nokia, Nokia Shanghai Bell | Rel-18 | r01 + changes Agreed. Revised to S2-2401435. | Hui (Huawei) provides r01 ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 9.17.2 | S2-2401435 | CR | Approval | 23.502 CR4732R1 (Rel-18, 'F'): Clarifications on the case AF interacts with HPLMN to influence HR-SBO traffic at VPLMN | Nokia, Nokia Shanghai Bell | Rel-18 | Revision of S2-2401222r01 + changes. Approved | Agreed | |
| 9.17.2 | - | - | - | KI#1 failure scenarios | - | - | Docs:=9 | - | |
| 9.17.2 | S2-2400623 | CR | Approval | 23.548 CR0192R1 (Rel-18, 'F'): HR-SBO Authorization failure in HR-SBO | Vivo | Rel-18 | Revision of (unhandled) S2-2312223. r02 Agreed. Revised to S2-2401642. | Hyesung (Samsung) comments. Stefano (Qualcomm) expresses concerns. Huazhang (vivo) provides r01 Magnus (Ericsson) Still have some concerns on r01 Huazhang (vivo) provides r02 ==== Revisions Deadline ==== ==== Final Comments Deadline ==== Huazhang (vivo) see no objection to r02, is that possible to agree r02? | Revised |
| 9.17.2 | S2-2401642 | CR | Approval | 23.548 CR0192R2 (Rel-18, 'F'): HR-SBO Authorization failure in HR-SBO | Vivo | Rel-18 | Revision of S2-2400623r02. Approved | Agreed | |
| 9.17.2 | S2-2400625 | CR | Approval | 23.548 CR0212 (Rel-18, 'F'): Handling EAS IP address that not authorized in case of Local DNS for HR-SBO | Vivo | Rel-18 | Agree r03? (in case fix normative text in NOTE: 'may'--> 'can'). Postponed | Stefano (Qualcomm) indicates this is a corner case, suggests to note. Huazhang (vivo) reply to Tezcan and Stefano and seek more suggestion Tezcan (Nokia) provides comments for possible changes. Tezcan (Nokia) responds to Huazhang Yuan Tao (CATT) asks for clarification. Huazhang (vivo) reply to Yuan (CATT) Yuan Tao (CATT) replies. Huazhang (vivo) provides r01 and reply to Tezcan (Nokia) Tezcan (Nokia) suggests to merge this paper to S2-2400809 Huazhang (vivo) reply to Tezcan it seems hard to merge together Huazhang (vivo) reply to Tezcan, and seek whether have other way forward Magnus (Ericsson) Suggest to merge with 809 or use a note Huazhang (vivo) provides r02 and convert to a note, remove the normative text Hui (Huawei) don't' think this note is correct. Huazhang (vivo) provides r03 ==== Revisions Deadline ==== Tezcan (Nokia) prefers to postpone Huazhang (vivo) agree to postpone, thanks Tezcan, we can come back in Feb. ==== Final Comments Deadline ==== | Postponed |
| 9.17.2 | S2-2400812 | CR | Approval | 23.548 CR0214 (Rel-18, 'F'): Corrections to Neasdf_DNSContext Service and EASDF-related Description | Huawei, HiSilicon | Rel-18 | Approved | Agreed | |
| 9.17.2 | S2-2400886 | CR | Approval | 23.548 CR0215 (Rel-18, 'F'): Update on procedures for common EAS discovery and coordination | CATT | Rel-18 | Noted | Stefano (Qualcomm) expresses concerns Xinpeng(Huawei) comments. Yuan Tao replies to Stefano (Qualcomm). Yuan Tao (CATT) replies to Xinpeng(Huawei). Xinpeng(Huawei) replies to Yuan Tao (CATT). Tezcan Cogalan (Nokia) express concerns. Yuan Tao (CATT) provides r01. Magnus H (Ericsson) provides comments Yuan Tao (CATT) replies to Magnus H (Ericsson). ==== Revisions Deadline ==== Yuan Tao (CATT) asks to agree r01. Tezcan (Nokia) proposes to note this paper. ==== Final Comments Deadline ==== | Noted |
| 9.17.2 | S2-2400887 | CR | Approval | 23.548 CR0200R1 (Rel-18, 'F'): Update on general descriptions for EAS discovery | CATT | Rel-18 | Revision of (unhandled) S2-2312879. r04 Agreed. Revised to S2-2401436. | Magnus (Ericsson) has concerns with this CR Tezcan (Nokia) provides comments. Yuan Tao (CATT) provides r01. Tezcan (Nokia) provides r02 Magnus H (Ericsson) provides r03 Yuan Tao (CATT) provides r04 ==== Revisions Deadline ==== Tezcan (Nokia) is fine with r04, NOT OK with r00, r01. ==== Final Comments Deadline ==== | Revised |
| 9.17.2 | S2-2401436 | CR | Approval | 23.548 CR0200R2 (Rel-18, 'F'): Update on general descriptions for EAS discovery | CATT | Rel-18 | Revision of S2-2400887r04. Approved | Agreed | |
| 9.17.2 | S2-2401224 | CR | Approval | 23.548 CR0190R1 (Rel-18, 'F'): Clarifications on Common DNAI/EAS discovery/selection procedure and storing EAS address-DNAI mapping in UDR | Nokia, Nokia Shanghai Bell | Rel-18 | Revision of (unhandled) S2-2312177. r04 + changes Agreed. Revised to S2-2401437. | Xinpeng(Huawei) comments. Tezcan Cogalan (Nokia) replies to Xinpeng(Huawei). Magnus H (Ericsson) provides comments Xinpeng(Huawei) replies to Tezcan Cogalan (Nokia). Yuan Tao (CATT) asks for clarification. Tezcan (Nokia) replies to Xinpeng, Magnus and Yuan, and provides r01. Yuan Tao (CATT) replies to Tezcan (Nokia). Tezcan (Nokia) replies to Yuan Tao (CATT). Xinpeng(Huawei) provides r02 based on r01. Hongsuk (LGE) asks question. Tezcan (Nokia) replies to Xinpeng. Tezcan (Nokia) replies to Hongsuk Xinpeng(Huawei) replies to Tezcan (Nokia). Magnus H (Ericsson) provides r03 Xinpeng(Huawei) provides r04. Tezcan (Nokia) responds to Xinpeng and prefers r03 ==== Revisions Deadline ==== Xinpeng(Huawei) is ok with r04 and r02, not ok with r00, r01,r03. Xinpeng(Huawei) replies to Tezcan (Nokia) that the NOTE proposed is still unclear. Tezcan (Nokia) provides r05 that removes changes on 6.2.3.4.2 Xinpeng(Huawei) is fine with r05 which based on r04 + remove the change on clause 6.2.3.4.2 along with clause 2. ==== Final Comments Deadline ==== | Revised |
| 9.17.2 | S2-2401437 | CR | Approval | 23.548 CR0190R2 (Rel-18, 'F'): Clarifications on Common DNAI/EAS discovery/selection procedure and storing EAS address-DNAI mapping in UDR | Nokia, Nokia Shanghai Bell, Ericsson | Rel-18 | Revision of S2-2401224r04 + changes. Postponed | Postponed | |
| 9.18.2 | - | - | - | 5G Timing Resiliency and TSC & URLLC enhancements (TRS_URLLC) | - | - | Docs:=38 | - | |
| 9.18.2 | S2-2401337 | LS OUT | Approval | [DRAFT] Reply LS on RAN feedback during handover | Qualcomm | Rel-18 | Response to S2-2400064. Postponed | Shabnam (Ericsson) provides comments that the CRs are not acceptable for us and for that reason the LS response as stated is not aligned so we suggest to NOTE it. ==== Revisions Deadline ==== | Postponed |
| 9.18.2 | S2-2400064 | LS In | Action | LS from RAN WG3: RAN feedback during handover | RAN WG3 (R3-238038) | Rel-18 | Response drafted in S2-2401337. Postponed | Postponed | |
| 9.18.2 | S2-2400109 | CR | Approval | 23.501 CR5181R1 (Rel-18, 'F'): KI#5 Corrections on Proactive RAN Feedback and TSN enabled TN | Nokia, Nokia Shanghai Bell | Rel-18 | Revision of (unhandled) S2-2312870. r04 + changes Agreed. Revised to S2-2401438. | Srinivas Garikipati (Nokia) comments and provides r01. Haiyang (Huawei) suggests to note this paper or merge into 0274 Haiyang (Huawei) comments Srinivas Garikipati (Nokia) comments and provides r02 Srinivas Garikipati (Nokia) comments and provides r03 Haiyang (Huawei) provides r04 Srinivas Garikipati (Nokia) comments and provides r05 Haiyang (Huawei) comments to r05 Srinivas Garikipati (Nokia) comments and provides r04 ==== Revisions Deadline ==== Haiyang (Huawei) suggests to go with r04 or postpone Srinivas Garikipati (Nokia) is OK with r04 along with a re-wording of text to 'If interworking with a TSN network deployed in the transport network is supported, the SMF/CUC uses the adjusted periodicity (if provided) and BAT offset accepted by the RAN to adjust the related parameters in the Talker/Listener Group and the Talker/Listener Group is described in M.1. How the related parameters are adjusted is left to the implementation.'. Objects to rest of the revisions. Haiyang (Huawei) can live with r04 + changes proposed by Nokia for this meeting ==== Final Comments Deadline ==== | Revised |
| 9.18.2 | S2-2401438 | CR | Approval | 23.501 CR5181R2 (Rel-18, 'F'): KI#5 Corrections on Proactive RAN Feedback and TSN enabled TN | Nokia, Nokia Shanghai Bell | Rel-18 | Revision of S2-2400109r04 + changes. Approved | Agreed | |
| 9.18.2 | S2-2400196 | CR | Approval | 23.501 CR5122R1 (Rel-18, 'F'): Correction of additional parameters inside AF Request Authorization | Ericsson | Rel-18 | Revision of (unhandled) S2-2312462. Approved | Runze (Huawei) supports the CR ==== Revisions Deadline ==== | Agreed |
| 9.18.2 | S2-2400197 | CR | Approval | 23.502 CR4599R1 (Rel-18, 'F'): Correcting the ASTI procedure to enable network timing synchronization status monitoring | Ericsson | Rel-18 | Revision of (unhandled) S2-2312465. Noted | Jari (NTT DOCOMO) comments. Aleksejs (Ericsson) replies to Jari (NTT DOCOMO) Devaki (Nokia) objects to the CR as it is not FASMO, no need to provision AMF IDs/gNB IDs in the TSCTSF by AMF via PCF. Aleksejs (Ericsson) responds to Devaki (Nokia) concerns, provides r01, and asks to reconsider. Jari (NTT DOCOMO) shares the view of Nokia Aleksejs (Ericsson) responds to Jari (NTT DOCOMO) with a clarification. Jari (NTT DOCOMO) does not understand the explanation Aleksejs (Ericsson) replies to Jari (NTT DOCOMO) to clarify and provides r02 Jari (NTT DOCOMO) does not agree Aleksejs (Ericsson) replies to Jari (NTT DOCOMO) and provides r03 Jari (NTT DOCOMO) disagrees Aleksejs (Ericsson) responds. ==== Revisions Deadline ==== Jari (NTT DOCOMO) does not accept original or any revision Devaki (Nokia) comments that we also cannot accept any version of this CR at this time. ==== Final Comments Deadline ==== | Noted |
| 9.18.2 | S2-2400198 | CR | Approval | 23.502 CR4598R1 (Rel-18, 'F'): Correcting the ASTI procedure | Ericsson | Rel-18 | Revision of (unhandled) S2-2312464. r02 + changes Agreed. Revised to S2-2401439. | Jari (NTT DOCOMO) comments. Aleksejs (Ericsson) replies to Jari (NTT DOCOMO) Runze (Huawei) agreed with Devaki (Nokia) . Devaki (Nokia) comments, cannot accept changes to step 6b, some editorial changes are ok. Aleksejs (Ericsson) responds to the previous comments and provides r01. Jari (NTT DOCOMO) objects any revision where AM-PCF is discovered via Namf_EventExposure_Notify service Aleksejs (Ericsson) thanks for the discussions, accepts the comments, and provides r02. ==== Revisions Deadline ==== Devaki (Nokia) comments that r02 is fine but the figure is now totally messed up (all the lines are missing, only text remain for the most part) in r02. This SHALL be fixed. Aleksejs (Ericsson) thanks Devaki (Nokia) for heads up regarding the figure. Jari (NTT DOCOMO) can accept r02 ==== Final Comments Deadline ==== | Revised |
| 9.18.2 | S2-2401439 | CR | Approval | 23.502 CR4598R2 (Rel-18, 'F'): Correcting the ASTI procedure | Ericsson | Rel-18 | Revision of S2-2400198r02 + changes. Approved | Agreed | |
| 9.18.2 | S2-2400199 | DISCUSSION | Discussion | Discussion on the support of Network Timing Synchronization Status Reporting | Ericsson | Rel-18 | Noted | Noted | |
| 9.18.2 | S2-2400200 | CR | Approval | 23.502 CR4674 (Rel-18, 'F'): Reinstating Namf_Communication_NonUeN2MessageTransfer for TSS reporting | Ericsson | Rel-18 | Postponed | Runze (Huawei) comments to the CR. Devaki (Nokia) neutral to this approach. Jari (NTT DOCOMO) comments zhendong (ZTE) proposes this as the way forward Aleksejs (Ericsson) thanks for the feedback, replies to Jari (NTT DOCOMO), and provides r01 Jari (NTT DOCOMO) responds Devaki (Nokia) comments Jari (NTT DOCOMO) supports Nokia to postpone this. Aleksejs (Ericsson) responds to Devaki (Nokia) and Jari (NTT DOCOMO) ==== Revisions Deadline ==== Aleksejs (Ericsson) proposes to endorse the CR as Stage 3 WGs are waiting for the SA2 requirements to progress. Jari (NTT DOCOMO) asks to postpone this. Aleksejs (Ericsson) comments ==== Final Comments Deadline ==== Devaki (Nokia) comments that endorsed status would be fine for us. | Postponed |
| 9.18.2 | S2-2400273 | CR | Approval | 23.501 CR5106R1 (Rel-18, 'F'): Clarification on AoI of time synchronization service | Huawei, HiSilicon | Rel-18 | Revision of (unhandled) S2-2312292. r02 Agreed. Revised to S2-2401440. | Stefano (Qualcomm) question for clarification Rainer (Nokia) replies. Aleksejs (Ericsson) provide comments and asks for clarifications. Jari (NTT DOCOMO) provides r01 Devaki (Nokia) has concerns with r01, the newly introduced term 'updated time sync coverage area', also in original version of the CR. Haiyang (Huawei) provides r02 Devaki (Nokia) comments r02 is fine. Aleksejs (Ericsson) also thinks that r02 is okay ==== Revisions Deadline ==== Aleksejs (Ericsson) objects to r00, is OK with r01, prefers r02. ==== Final Comments Deadline ==== | Revised |
| 9.18.2 | S2-2401440 | CR | Approval | 23.501 CR5106R2 (Rel-18, 'F'): Clarification on AoI of time synchronization service | Huawei, HiSilicon | Rel-18 | Revision of S2-2400273r02. Approved | Agreed | |
| 9.18.2 | S2-2400274 | CR | Approval | 23.501 CR5225 (Rel-18, 'F'): Correction on CN PDB configured in NG-RAN | Huawei, HiSilicon | Rel-18 | r03 Agreed. Revised to S2-2401441. | Srinivas Garikipati (Nokia) Provides revision r01 Haiyang (Huawei) provides r02 with explanation Sang-Jun (Samsung) has a similar concern as Shabnam (Ericsson) provides. Why 5G-AN PDB is added is not explained. Shabnam (Ericsson) provides comments that in addition to r01, we don't agree to the changes in Annex M (why 5G-AN PDB is added) since it is not explained and not consistent with existing Annex text. Srinivas Garikipati (Nokia) comments and provides r03 Shabnam (Ericsson) provides comments that addition of 5G-AN PDB in Annex M is not acceptable still as I don't see explanation given. Haiyang (Huawei) indicates to Shabnam (Ericsson) that explanation is together with r02 Shabnam (Ericsson) provides comments that you don't describe why you simply say that 5G-AN PDB is used to derive. Please see below: Haiyang (Huawei) clarifies to Shabnam (Ericsson) ==== Revisions Deadline ==== Haiyang (Huawei) is OK with r00, r02, r03; not ok with r01; prefer r02 Srinivas Garikipati (Nokia) is OK with 03 and 01; Not ok with r00, r02; prefer r03 Shabnam (Ericsson) provides comments ok with r03, if I have any concerns can come back to it. ==== Final Comments Deadline ==== | Revised |
| 9.18.2 | S2-2401441 | CR | Approval | 23.501 CR5225R1 (Rel-18, 'F'): Correction on CN PDB configured in NG-RAN | Huawei, HiSilicon | Rel-18 | Revision of S2-2400274r03. Approved | Agreed | |
| 9.18.2 | S2-2400500 | CR | Approval | 23.501 CR5239 (Rel-18, 'F'): CQRCI check issue when there are both AF requests and subscriptions | ZTE | Rel-18 | Postponed | Sebastian (Qualcomm) comments that same comments as for S2-2400501 apply Devaki (Nokia) comments. Runze (Huawei) shared the same as view as Sebastian(Qualcomm) and Devaki (Nokia). Aleksejs (Ericsson) provides a comment sharing different understanding Sebastian (Qualcomm) objects to the CR zhendong (ZTE) provides the response ==== Revisions Deadline ==== | Postponed |
| 9.18.2 | S2-2400501 | CR | Approval | 23.502 CR4690 (Rel-18, 'F'): CQRCI check issue when there are both AF requests and subscriptions | ZTE | Rel-18 | Postponed | Aleksejs (Ericsson) provides a comment. Sebastian (Qualcomm) comments Devaki (Nokia) comments. Runze (Huawei) supports the views from Ericsson, Qualcomm and Nokia. Sebastian (Qualcomm) objects to the r00 for reasons given early zhendong (ZTE) provides the response to Sebastian (qualcomm) zhendong (ZTE) provides the response to devaki Sebastian (Qualcomm) replies Aleksejs (Ericsson) comments zhendong (ZTE) provides the response to Aleksejs ==== Revisions Deadline ==== | Postponed |
| 9.18.2 | S2-2400502 | CR | Approval | 23.501 CR5240 (Rel-18, 'F'): Clarification on the UE capability and re-connection indication | ZTE | Rel-18 | r02 Agreed. Revised to S2-2401442. | Aleksejs (Ericsson) provides r01 and asks a question to get opinions. Devaki (Nokia) provides r02 Runze (Huawei) questions on need of introducing new UE capability. Aleksejs (Ericsson) replies to Devaki (Nokia) and Runze (Huawei) zhendong (ZTE) provides the response to Aleksejs (Ericsson) zhendong (ZTE) provides the response to devaki (nokia) zhendong (ZTE) provides the response to Runze (huawei) ==== Revisions Deadline ==== Aleksejs (Ericsson) proposes to go with r02. r01 is okay, r00 is NOK. ==== Final Comments Deadline ==== | Revised |
| 9.18.2 | S2-2401442 | CR | Approval | 23.501 CR5240R1 (Rel-18, 'F'): Clarification on the UE capability and re-connection indication | ZTE | Rel-18 | Revision of S2-2400502r02. Approved | Agreed | |
| 9.18.2 | S2-2400503 | CR | Approval | 23.502 CR4691 (Rel-18, 'F'): Clarification on the on the UE Time Synchronization Subscription data for (g)PTP and TSCTSF checking | ZTE | Rel-18 | r01 Agreed. Revised to S2-2401443. | Jari (NTT DOCOMO) comments. Aleksejs (Ericsson) comments Qianghua (Huawei) asks to clarify Devaki (Nokia) comments zhendong (ZTE) provides the response to Jari (NTT DOCOMO) zhendong (ZTE) provides the response to Aleksejs (ericsson) zhendong (ZTE) provides the response to devaki zhendong (ZTE) provides the r01 Aleksejs (Ericsson) asks Zhendong (ZTE) for clarifications Aleksejs (Ericsson) replies to Zhendong (ZTE) ==== Revisions Deadline ==== Devaki (Nokia) comments r01 is ok. Aleksejs (Ericsson) also is okay to go with r01 Aleksejs (Ericsson) objects to r00 due to earlier comments, and supports r01. Jari (NTT DOCOMO) can agree r01 ==== Final Comments Deadline ==== | Revised |
| 9.18.2 | S2-2401443 | CR | Approval | 23.502 CR4691R1 (Rel-18, 'F'): Clarification on the on the UE Time Synchronization Subscription data for (g)PTP and TSCTSF checking | ZTE | Rel-18 | Revision of S2-2400503r01. Approved | Agreed | |
| 9.18.2 | S2-2400504 | CR | Approval | 23.501 CR5241 (Rel-18, 'F'): Correction on InterfaceConfiguration and InterfaceCapability | ZTE | Rel-18 | r02 Agreed. Revised to S2-2401444. | Srinivas Garikipati (Nokia) comments on the CR zhendong (ZTE) provides the response Haiyang (Huawei) seeks for clarification Srinivas Garikipati (Nokia) updates and asks for further clarification Srinivas Garikipati (Nokia) clarifies that configuration is not required Srinivas Garikipati (Nokia) provides updates to the note. zhendong (ZTE) provides the r01 Srinivas Garikipati (Nokia) comments and happy to co-sign r01 zhendong (ZTE) provides the r02 ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 9.18.2 | S2-2401444 | CR | Approval | 23.501 CR5241R1 (Rel-18, 'F'): Correction on InterfaceConfiguration and InterfaceCapability | ZTE, Nokia, Nokia Shanghai Bell | Rel-18 | Revision of S2-2400504r02. Approved | Agreed | |
| 9.18.2 | S2-2400606 | CR | Approval | 23.501 CR5246 (Rel-18, 'F'): TSCTSF subscribing to RAN TSS based on list of TAs, correction to ASTI without AF request | Nokia, Nokia Shanghai Bell | Rel-18 | r02 + changes Agreed. Revised to S2-2401445. | Jari (NTT DOCOMO) comments Sebastian (Qualcomm) objects to r00, provides r01 Devaki (Nokia) provides r02 based on r01 to fix the cover sheet. Jari (NTT DOCOMO) asks further clarification Aleksejs (Ericsson) replies to Jari (NTT DOCOMO) sharing the understanding. Jari (NTT DOCOMO) responds Jari (NTT DOCOMO) provides r03 Aleksejs (Ericsson) objects to r03 due to reasons below. Devaki (Nokia) comments Aleksejs (Ericsson) supports Devaki (Nokia) proposal and thanks Jari (NTT DOCOMO) for clarifications. ==== Revisions Deadline ==== Devaki (Nokia) proposes to consider r02 for approval. Consider r03 content as part of a separate CR in the future. Aleksejs (Ericsson) supports the way-forward proposed by Devaki (Nokia), and is okay with r02. ==== Final Comments Deadline ==== | Revised |
| 9.18.2 | S2-2401445 | CR | Approval | 23.501 CR5246R1 (Rel-18, 'F'): TSCTSF subscribing to RAN TSS based on list of TAs, correction to ASTI without AF request | Nokia, Nokia Shanghai Bell | Rel-18 | Revision of S2-2400606r02 + changes. Approved | Agreed | |
| 9.18.2 | S2-2400608 | CR | Approval | 23.501 CR5248 (Rel-18, 'F'): Updating TSCAI and TSCAC to Traffic Assistance Information | Nokia, Nokia Shanghai Bell | Rel-18 | r03 + changes Agreed. Revised to S2-2401446. | Devaki (Nokia) comments. Haiyang (Huawei) suggest to add clarification in XRM part rather than change the terms Sang-Jun (Samsung) agrees with Haiyang. Haiyang (Huawei) clarifies Haiyang (Huawei) is OK with r03 Shabnam (Ericsson) agree with previous comments, provides r03 replacing 'It' with TSCAI so that it is clear which parameter can be used. Sang-Jun (Samsung) provides r02. Devaki (Nokia) provides r01. Sang-Jun (Samsung) is also fine with r03. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 9.18.2 | S2-2401446 | CR | Approval | 23.501 CR5248R1 (Rel-18, 'F'): Updating TSCAI and TSCAC to Traffic Assistance Information | Nokia, Nokia Shanghai Bell | Rel-18 | Revision of S2-2400608r03 + changes. Approved | Agreed | |
| 9.18.2 | S2-2400609 | CR | Approval | 23.502 CR4695 (Rel-18, 'F'): Updating TSCAI and TSCAC to Traffic Assistance Information | Nokia, Nokia Shanghai Bell | Rel-18 | Noted | Haiyang (Huawei) comments Shabnam (Ericsson) based on the direction taken for 23.501 CR, the changes are not needed so the CR can be NOTED. Sang-Jun (Samsung) also thinks the CR can be NOTED. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Noted |
| 9.18.2 | S2-2400610 | CR | Approval | 23.503 CR1250 (Rel-18, 'F'): Updating TSCAI and TSCAC to Traffic Assistance Information | Nokia, Nokia Shanghai Bell | Rel-18 | Noted | Haiyang (Huawei) comments Shabnam (Ericsson) based on the direction taken for 23.501 CR, the changes are not needed so the CR can be NOTED. Sang-Jun (Samsung) also thinks the CR can be NOTED. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Noted |
| 9.18.2 | S2-2400717 | CR | Approval | 23.501 CR5256 (Rel-18, 'F'): Clock Quality Metric Report Clarification | Samsung | Rel-18 | Noted | Aleksejs (Ericsson) questions the need of the proposed changes. Sebastian (Qualcomm) objects to the CR for the same reasons commented by Aleksejs Sang-Jun (Samsung) replies to Sebastian (Qualcomm) and Aleksejs (Ericsson). Devaki (Nokia) objects to the CR. Current NOTE 2 already addresses questions from RAN folks and the proposed addition is wrong in our view, it also invalidates NOTE2. Aleksejs (Ericsson) has the same view as Devaki (Nokia). ==== Revisions Deadline ==== | Noted |
| 9.18.2 | S2-2400719 | CR | Approval | 23.501 CR5257 (Rel-18, 'F'): RAN feedback during handover | Samsung | Rel-18 | Noted | Sebastian (Qualcomm) objects to the CR Sang-Jun (Samsung) provides r01 Sebastian (Qualcomm) objects to r01 also Haiyang (Huawei) clarifies to Sebastian (Qualcomm) Sebastian (Qualcomm) replies to Haiyang ==== Revisions Deadline ==== | Noted |
| 9.18.2 | S2-2401007 | CR | Approval | 23.502 CR4719 (Rel-18, 'F'): Clock status indication from RAN to TSCTSF | NTT DOCOMO | Rel-18 | Noted | Shabnam (Ericsson) shares same view as Nokia. Devaki (Nokia) has objections to the indication proposed in this CR. Jari (NT DOCOMO) responds Devaki (Nokia) comments Jari (NTT DOCOMO) responds ==== Revisions Deadline ==== Devaki (Nokia) responds Jari (NTT DOCOMO) Devaki's response is not sufficient to solve the problem Jari (NTT DOCOMO) comments | Noted |
| 9.18.2 | S2-2401164 | CR | Approval | 23.502 CR4727 (Rel-18, 'F'): Clarification for AMF discovery and subscription by TSCTSF | Huawei, HiSilicon | Rel-18 | Postponed | Jari (NTT DOCOMO) comments Devaki (Nokia) agrees with Jari, has concerns with the CR. Runze (Huawei) replied to Jari(DOCOMO) and Devaki (Nokia) . zhendong (ZTE) provides the comments Devaki (Nokia) comments Runze (Huawei) replies to Devaki (Nokia) and Zhendong (ZTE) ==== Revisions Deadline ==== Devaki (Nokia) comments that it is better to postpone this CR to properly discuss the need for this option, also properly describe in 501/502. ==== Final Comments Deadline ==== | Postponed |
| 9.18.2 | S2-2401165 | CR | Approval | 23.502 CR4728 (Rel-18, 'F'): Add the description to aligh with conclusion of TSN charging principles | Huawei, HiSilicon | Rel-18 | Confirm Specification Number - CR states 23.501! (New CR number needed if for TS 23.501). Noted | Sebastian (Qualcomm) objects to the CR Runze (Huawei) replies to Sebastian (Qualcomm) ==== Revisions Deadline ==== | Noted |
| 9.18.2 | S2-2401256 | CR | Approval | 23.502 CR4734 (Rel-18, 'F'): Clean up and alignment for TRS monitoring and reporting, correction to ASTI without AF request | Nokia, Nokia Shanghai Bell | Rel-18 | r04 Agreed. Revised to S2-2401447. | Jari (NTT DOCOMO) comments Aleksejs (Ericsson) comments Sebastian (Qualcomm) objects to r00 and provides r01 Aleksejs (Ericsson) provides r02 and comments Devaki (Nokia) provides r03 based on r02 to fix cover sheet. Jari (NTT DOCOMO) proposes to remove 'in which case' Devaki (Nokia) provides r04 to remove 'in which case' as requested by Jari. ==== Revisions Deadline ==== Aleksejs (Ericsson) is fine with r04. ==== Final Comments Deadline ==== | Revised |
| 9.18.2 | S2-2401447 | CR | Approval | 23.502 CR4734R1 (Rel-18, 'F'): TSCTSF subscribing to RAN TSS based on list of TAs, correction to ASTI without AF request | Nokia, Nokia Shanghai Bell | Rel-18 | (Specification Number Confirmed) Revision of S2-2401256r04. Approved. Revision of S2-2401256r04. Approved | Agreed | |
| 9.18.2 | S2-2401342 | CR | Approval | 23.502 CR4737 (Rel-16, 'F'): Providing TSCAI to NG-RAN during Xn handovers | Qualcomm | Rel-16 | Postponed | Shabnam (Ericsson) provides comments that change to use Path Switch to provide TSCAI is not acceptable and objects to the CR. Sebastian (Qualcomm) responds to Shabnam Devaki (Nokia) comments Shabnam (Ericsson) comments that we need to think about this use case further but we are not ok to break the principle on which procedure triggers gNB to update the QoS and related parameters. Sebastian (Qualcomm) replies to Shabnam Haiyang (Huawei) also suggests to postpone Shabnam (Ericsson) let's postpone this topic for the next meeting, from RAN side we have concerns. ==== Revisions Deadline ==== Sebastian (Qualcomm) is fine to postpone | Postponed |
| 9.18.2 | S2-2401343 | CR | Approval | 23.502 CR4738 (Rel-17, 'A'): Providing TSCAI to NG-RAN during Xn handovers | Qualcomm | Rel-17 | Postponed | Shabnam (Ericsson) provides comments same as for doc 1342, that change to use Path Switch to provide TSCAI is not acceptable and objects to the CR. ==== Revisions Deadline ==== | Postponed |
| 9.18.2 | S2-2401344 | CR | Approval | 23.502 CR4739 (Rel-18, 'A'): Providing TSCAI to NG-RAN during Xn handovers | Qualcomm | Rel-18 | Confirm Specification Number - CR states 23.501! (New CR number needed if for TS 23.501). Postponed | Shabnam (Ericsson) provides comments same as for doc 1342, that change to use Path Switch to provide TSCAI is not acceptable and objects to the CR. ==== Revisions Deadline ==== | Postponed |
| 9.19.2 | - | - | - | Vehicle Mounted Relays (VMR) | - | - | Docs:=20 | - | |
| 9.19.2 | - | - | - | Incoming RAN WG2 LS handling | - | - | Docs:=3 | - | |
| 9.19.2 | S2-2400057 | LS In | Action | LS from RAN WG2: LS to SA2 and RAN3 on IAB or mIAB operation | RAN WG2 (R2-2313892) | Rel-18 | Noted | Noted | |
| 9.19.2 | S2-2401290 | CR | Approval | 23.501 CR5302 (Rel-18, 'F'): Clarification on mobile IAB indication when establishing RRC connection | Qualcomm Incorporated | Rel-18 | r01 Agreed. Revised to S2-2401448. | Hong (Qualcomm) provides r01. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 9.19.2 | S2-2401448 | CR | Approval | 23.501 CR5302R1 (Rel-18, 'F'): Clarification on mobile IAB indication when establishing RRC connection | Qualcomm Incorporated | Rel-18 | Revision of S2-2401290r01. Approved | Agreed | |
| 9.19.2 | - | - | - | Incoming RAN WG3 LS handling | - | - | Docs:=10 | - | |
| 9.19.2 | S2-2400065 | LS In | Action | LS from RAN WG3: LS on RAN WG3 agreements on mobile IAB | RAN WG3 (R3-238043) | Rel-18 | Response drafted in S2-2400635. Postponed | Hong (Qualcomm) suggests to POSTPONE the LS in, because the LS OUT draft was POSTPONED. | Postponed |
| 9.19.2 | S2-2400635 | LS OUT | Approval | [DRAFT] Reply LS on RAN WG3 agreements on mobile IAB | Huawei, HiSilicon | Rel-18 | Response to S2-2400065. Postponed | Qian (Ericsson) provides comments and r01 Hong (Qualcomm) comments. Qian (Ericsson) responds further. Qian (Ericsson) replies. Hong (Qualcomm) comments on r01. Alessio(Nokia) if the slice of the MBSR is subject to usage control we will have the AMF release the registration after a timer if there are no PDU sessions in the slice. Consider this also for our next steps. I recommend we have agenda for MBSR in Athens as it seems we are uncovering (late) some big topic. Qian (Ericsson) replies to Hong (Qualcomm). Alessio(Nokia) requests to not send this LS LiMeng (Huawei) responds and provides r02. ==== Revisions Deadline ==== Hong (Qualcomm) suggests to POSTPONE the LS Out, and also POSTPONE the LS IN in S2-2400065. LaeYoung (LGE) replies to LiMeng (Huawei). LiMeng (Huawei) responds. LaeYoung (LGE) comments. Alessio(Nokia) agrees to POSTPONE the LS Out, and also POSTPONE the LS IN in S2-2400065. ==== Final Comments Deadline ==== | Postponed |
| 9.19.2 | S2-2400636 | CR | Approval | 23.501 CR5250 (Rel-18, 'F'): Corrections on mobile IAB-DU s TAC provisioning | Huawei, HiSilicon | Rel-18 | r01 Agreed. Revised to S2-2401449. | Qian (Ericsson) provides comments Alessio (Nokia) provides r01 LiMeng (Huawei) agrees r01, thanks for providing the revision. ==== Revisions Deadline ==== Qian (Ericsson) is ok with r01. ==== Final Comments Deadline ==== | Revised |
| 9.19.2 | S2-2401449 | CR | Approval | 23.501 CR5250R1 (Rel-18, 'F'): Corrections on mobile IAB-DU s TAC provisioning | Huawei, HiSilicon, Nokia, Nokia shanghai Bell | Rel-18 | Revision of S2-2400636r01. Approved | Agreed | |
| 9.19.2 | S2-2401291 | CR | Approval | 23.501 CR5303 (Rel-18, 'F'): Indication to AMF for MBSR connection release | Qualcomm Incorporated | Rel-18 | r07 Agreed. Revised to S2-2401450. | LiMeng (Huawei) suggests a revision for the cause code. Alessio (Nokia) provides r02. Hong (Qualcomm) provides r01. Lalith(Samsung) provides r03 Hong (Qualcomm) comments. Qian (Ericsson) provides r04 Alessio(Nokia) provides r05 Lalith(Samsung) provides r06 Hong (Qualcomm) provides r07. ==== Revisions Deadline ==== Qian (Ericsson) is ok with r07. ==== Final Comments Deadline ==== | Revised |
| 9.19.2 | S2-2401450 | CR | Approval | 23.501 CR5303R1 (Rel-18, 'F'): Indication to AMF for MBSR connection release | Qualcomm Incorporated, Ericsson, Nokia, Nokia Shanghai Bell, Samsung | Rel-18 | Revision of S2-2401291r07. Approved | Agreed | |
| 9.19.2 | S2-2400638 | CR | Approval | 23.502 CR4698 (Rel-18, 'F'): Deregistration of MBSR based on the NGAP indication from IAB-donor | Huawei, HiSilicon | Rel-18 | Removed dependency on TS23501 CR5251 on cover page. Revised to S2-2401375. | Revised | |
| 9.19.2 | S2-2401375 | CR | Approval | 23.502 CR4698R1 (Rel-18, 'F'): Deregistration of MBSR based on the NGAP indication from IAB-donor | Huawei, HiSilicon | Rel-18 | Revision of S2-2400638. Approved | Agreed | |
| 9.19.2 | S2-2400215 | CR | Approval | 23.501 CR5220 (Rel-18, 'F'): MBSR mobility | Ericsson | Rel-18 | r08 + changes Agreed. Revised to S2-2401451. | LiMeng (Huawei) suggests to undo the second paragraph of 5.35A.3.0 for the time being. Lars (Sony) suggests a rewording in 5.35A.3.1. Qian (Ericsson) provides comments and r01. LiMeng (Huawei) provides r02. Qian (Ericsson) provides comments. Alessio (nokia) provides r03 Hong (Qualcomm) replies to LiMeng. LiMeng (Huawei) replies. Hong (Qualcomm) comments on r03. Qian (Ericsson) provides further comments on few aspects. Hong (Qualcomm) provides r04. Alessio(nokia) provides R05 Qian (Ericsson) provides comments and R06 Alessio(Nokia) provides R07 and cannot accept r06 LiMeng (Huawei) provides R08. Hong (Qualcomm) comments and fine with both r05 or r06. ==== Revisions Deadline ==== Hong (Qualcomm) is fine with r08. LiMeng (Huawei) prefers r08 than r05. Alessio(Nokia) ok with r08 with a small change. For UEs in RRC_IDLE and RRC_INACTIVE state when a MBSR goes out-of-service, procedure for cell (re-)selection as specified in TS 38.304 [50] for RRC_IDLE and RRC_INACTIVE is used between MBSR cell and fixed cell. Changed to For UEs in RRC_IDLE and RRC_INACTIVE state when a MBSR goes out-of-service, procedure for cell (re-)selection as specified in TS 38.304 [50] for RRC_IDLE and RRC_INACTIVE is used between MBSR cell and OTHER cells. Qian (Ericsson) is ok with r08. Qian (Ericsson) provides further comments. Alessio(Nokia) thanks Ericsson for pointing out we should also fix the title ?? as we can support mobility between MBSRs. In r08 before upload let's change title to 5.35A.3.1 UE mobility involving a MBSR Qian (Ericsson) is ok with the proposal form Alessio (Nokia): r08 + change 'fixed cell' to 'other cells' in the first paragraph of clause 5.35A.3.1. Alessio thanks Qian for accepting the proposal form Alessio (Nokia): r08 + change 'fixed cell' to 'other cells' in the first paragraph of clause 5.35A.3.1. Hong (Qualcomm) comments. Qian (Ericsson) provides r09 (change 'fixed cell' to 'other cells' in the first paragraph of clause 5.35A.3.1, on top of r08 which is uploaded before revision deadline) in the draft folder. ==== Final Comments Deadline ==== | Revised |
| 9.19.2 | S2-2401451 | CR | Approval | 23.501 CR5220R1 (Rel-18, 'F'): MBSR mobility | Ericsson | Rel-18 | Revision of S2-2400215r08 + changes. Approved | Agreed | |
| 9.19.2 | - | - | - | Other corrections | - | - | Docs:=4 | - | |
| 9.19.2 | S2-2400721 | CR | Approval | 23.501 CR5258 (Rel-18, 'F'): Clarification on providing the additional location and time restrictions information to the MBSR IAB-UE | Nokia, Nokia Shanghai Bell | Rel-18 | CC#3: Postponed | Qian (Ericsson) provides comments and considers it's not needed to have additional information to MBSR Alessio(Nokia) comments that unfortunately the way the text of registration is defined causes a strange loop where the AMF deregisters a UE to change authorization status to not authorized by causing the UE to register again only to get its registration attempt rejected and become deregistered. once deregistered the UE behaviour is not specified so it may attempt to register gain based on implementation and the loop begins. We want the deregistration with state changed to not authorized to not need UE to register to get deregistered. And also to then let the UE(optionally) know when/where to register again if it is deregistered but not PLMN wide or not forever. Qian (Ericsson) provides comments and indicates that there are many parameters in the reject/deregistration message can be used by AMF to control the re-registration Nassima (KPN) provides comments, supports sending additional information to MBSR LiMeng (Huawei) comments. Alessio(Nokia)comments. Qian (Ericsson) provides comments and considers approach in 0213 is the way forward. Qian (Ericsson) provides comments and indicates we shall follow the approach in 0213. ==== Revisions Deadline ==== Alessio(Nokia) thinks we should not follow approach in 0213. The whole handling of unauthorized state or change to it is not well documented. Let's work on it till Athens. Qian (Ericsson) objects to any revision of this paper. But ok to continue the discussion in next meeting. Dario (Session Chair): postponed as discussed in CC#3 | Postponed |
| 9.19.2 | S2-2400213 | CR | Approval | 23.501 CR4962R7 (Rel-18, 'F'): MBSR authorization handling update | Ericsson | Rel-18 | Revision of (postponed) S2-2313761. CC#3: Postponed | Alessio (nokia) provides comments and prefers to use the CR in 721 and 731 as basis Qian (Ericsson) comments that the addition proposed in 0721/0731 is not needed as explained in that thread. We shall proceed with this paper and remove the EN. Hong (Qualcomm) suggests deciding a direction regarding this CR together with 0721/0731. ==== Revisions Deadline ==== Qian (Ericsson) proposes to go with r00 of this paper and remove the EN. Maurice Pope (MCC) reported that this CR had already been approved at TSG SA#102 and implemented in 23.501 v18.4.0. It should therefore be noted and any further changes needed proposed in a new CR. Hong (Qualcomm) suggests NOTING the CR. Dario (Session Chair): postponed as discussed in CC#3 Alessio(Nokia) this shall be noted as revision of a CR approved previous cycle ?? | Postponed |
| 9.19.2 | S2-2400731 | CR | Approval | 23.502 CR4705 (Rel-18, 'F'): Clarification on providing the additional location and time restrictions information to the MBSR IAB-UE | Nokia, Nokia Shanghai Bell | Rel-18 | CC#3: Postponed | Qian (Ericsson) provides comments and indicates it's linked to 0721 ==== Revisions Deadline ==== Qian (Ericsson) objects this paper as linkage to 0721 Dario (Session Chair): postponed as discussed in CC#3 | Postponed |
| 9.19.2 | S2-2401303 | CR | Approval | 23.501 CR5305 (Rel-18, 'F'): Clarification on AMF selection | Samsung | Rel-18 | Approved | Agreed | |
| 9.19.2 | - | - | - | Not handled due to quota | - | - | Docs:=3 | - | |
| 9.19.2 | S2-2400214 | CR | Approval | 23.501 CR5219 (Rel-18, 'F'): MBSR authorization state change handling update | Ericsson | Rel-18 | Not Handled | - | |
| 9.19.2 | S2-2400637 | CR | Approval | 23.501 CR5251 (Rel-18, 'F'): Deregistration of MBSR based on the NGAP indication from IAB-donor | Huawei, HiSilicon | Rel-18 | Not Handled | - | |
| 9.19.2 | S2-2400944 | CR | Approval | 23.501 CR5067R3 (Rel-18, 'F'): Clarification on delay in deregistration procedure | [Samsung], Xiaomi | Rel-18 | Revision of (agreed) S2-2311471 (CR already approved at TSG SA!). Confirm CR Revision - CR states 2! Not Handled | - | |
| 9.20.2 | - | - | - | Support for 5WWC Phase 3 (5WWC_Ph2) | - | - | Docs:=14 | - | |
| 9.20.2 | S2-2400112 | CR | Approval | 23.502 CR4670 (Rel-18, 'F'): Clarification on how to obtain N3IWF information | China Telecom | Rel-18 | r01 + changes Agreed. Revised to S2-2401452. | Myungjune (LGE) comments. Jing(China Telecom) replies to Myungjune(LGE). Myungjune (LGE) provides r01 Jing(China Telecom) provides r02 and asks Myungjune(LGE) if r02 is ok. Myungjune (LGE) is NOT OK with r02 ==== Revisions Deadline ==== Myungjune (LGE) only accepts r01. Laurent (Nokia): R02, prefers R00 but can live with R01 Jing (China Telecom) prefers R00 but can live with R01 Laurent (Nokia): Objects to R02, prefers R00 but can live with R01. If R01 selected cover sheet shall be modified as shown below Marco(Huawei) prefers R00, can live with R01 and object r02 ==== Final Comments Deadline ==== | Revised |
| 9.20.2 | S2-2401452 | CR | Approval | 23.502 CR4670R1 (Rel-18, 'F'): Clarification on how to obtain N3IWF information | China Telecom | Rel-18 | Revision of S2-2400112r01 + changes. Approved | Agreed | |
| 9.20.2 | S2-2400585 | CR | Approval | 23.501 CR4929R1 (Rel-18, 'F'): Removing editor's note on Prefixed N3IWF FQDN format | LG Electronics | Rel-18 | Revision of (unhandled) S2-2310200. Approved | Agreed | |
| 9.20.2 | S2-2400701 | CR | Approval | 23.503 CR1253 (Rel-18, 'F'): AMF/PCF Policy Control Trigger for UE policy update in non-3GPP access | China Telecom | Rel-18 | r03 Agreed. Revised to S2-2401453. | Laurent (Nokia): Comments Laurent (Nokia): provides r01 Yishan (Huawei) comments Heng(China Telecom) provides r02 Stefan (Ericsson) provides r03 Heng (China Telecom) comment Laurent (Nokia): answers: AFAIK changing PCRT between table of 3GPP PCRT and table of common PCRT should not impact existing CT interfaces Laurent (Nokia): Comments I agree with keeping UE-slice6MBR in the 3GPP table Heng (China Telecom) agree r03 ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 9.20.2 | S2-2401453 | CR | Approval | 23.503 CR1253R1 (Rel-18, 'F'): AMF/PCF Policy Control Trigger for UE policy update in non-3GPP access | China Telecom, Nokia, Nokia Shanghai Bell | Rel-18 | Revision of S2-2400701r03. Approved | Agreed | |
| 9.20.2 | S2-2400745 | CR | Approval | 23.316 CR2125 (Rel-18, 'F'): AUN3 device de-registration | Nokia, Nokia Shanghai Bell | Rel-18 | Agreed. Approved | Yishan (Huawei) asks for clarification Laurent (Nokia): answers to Yishan ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Agreed |
| 9.20.2 | S2-2400746 | CR | Approval | 23.316 CR2126 (Rel-18, 'F'): Registration Management of AUN3 devices to follow TS 23.501 clause 5.5.1 | Nokia, Nokia Shanghai Bell | Rel-18 | Check Affected Clauses!. r01 Agreed. Revised to S2-2401454. | Stefan (Ericsson) provides r01 ==== Revisions Deadline ==== Laurent (Nokia): hoping that a version is agreed I need to update the clause affected Laurent (Nokia) prefers R00 that is more explicit for RG developpers Stefan (Ericsson) prefers r01 since examples are misleading ==== Final Comments Deadline ==== | Revised |
| 9.20.2 | S2-2401454 | CR | Approval | 23.316 CR2126R1 (Rel-18, 'F'): Registration Management of AUN3 devices to follow TS 23.501 clause 5.5.1 | Nokia, Nokia Shanghai Bell, Ericsson | Rel-18 | Revision of S2-2400746r01. Approved | Agreed | |
| 9.20.2 | S2-2400782 | CR | Approval | 23.316 CR2127 (Rel-18, 'F'): Clarification on NAS security for AUN3 deivces | Huawei, HiSilicon | Rel-18 | r03 Agreed. Revised to S2-2401455. | Laurent (Nokia): provides r01 Yishan (Huawei) is ok with r01 and further provides r02 Stefan (Ericsson) provides r03 ==== Revisions Deadline ==== Rahil (CableLabs) is ok with r03, not with other revisions. Marco(Huawei) ok with R03 ==== Final Comments Deadline ==== | Revised |
| 9.20.2 | S2-2401455 | CR | Approval | 23.316 CR2127R1 (Rel-18, 'F'): Clarification on NAS security for AUN3 devices | Huawei, HiSilicon, Nokia, Ericsson | Rel-18 | Revision of S2-2400782r03. Approved | Agreed | |
| 9.20.2 | S2-2401176 | CR | Approval | 23.503 CR1262 (Rel-18, 'F'): URSP for 5G-RG and FN-RG | Huawei, Hisilicon | Rel-18 | r01 Agreed. Revised to S2-2401457. | Laurent (Nokia): provides r01 Marco(Huawei) agree with Laurent (Nokia) and R01 OK ==== Revisions Deadline ==== Sebastian (Qualcomm) is ok with r01 but comments that 1176 can only be agreed if also 1177 is agreed. (If 1177 is noted/postponed, then 1176 needs to also be noted/postponed). ==== Final Comments Deadline ==== | Revised |
| 9.20.2 | S2-2401457 | CR | Approval | 23.503 CR1262R1 (Rel-18, 'F'): URSP for 5G-RG and FN-RG | Huawei, Hisilicon | Rel-18 | Revision of S2-2401176r01. Approved | Agreed | |
| 9.20.2 | S2-2401177 | CR | Approval | 23.316 CR2128 (Rel-18, 'F'): URSP for 5G-RG and FN-RG | Huawei, Hisilicon | Rel-18 | r03 Agreed. Revised to S2-2401456. | Laurent (Nokia): provides r01 Marco(Huawei) is OK with R01 Yildirim (Charter Communications) comments. Sebastian (Qualcomm) raises concerns on r00 and r01 Marco(Huawei) I'm OK with Sebastian's (QC) way out B Laurent (Nokia): provides r02 Marco(Huawei) OK with R02. Sebastian (Qualcomm) provides r03 Rahil (CableLabs) provides r04. ==== Revisions Deadline ==== Rahil (CableLabs) is ok with r04, not ok with other revisions. Laurent (Nokia): objects to R04 Marco(Huawei) OK with R03 and Object R04 since DNN, Application descriptors or connection capabilities as URSP Traffic descriptor are not know in AGF acting on behalf of FN-RG but application is FN-RG or device behind Rahil (CableLabs) is ok with r03. ==== Final Comments Deadline ==== | Revised |
| 9.20.2 | S2-2401456 | CR | Approval | 23.316 CR2128R1 (Rel-18, 'F'): URSP for 5G-RG and FN-RG | Huawei, Hisilicon, Nokia | Rel-18 | Revision of S2-2401177r03. Approved | Agreed | |
| 9.21 | - | - | - | Stage 2 of MPS_WLAN (MPS_WLAN) | - | - | Docs:=6 | - | |
| 9.21 | S2-2400415 | CR | Approval | 23.501 CR4660R3 (Rel-18, 'F'): Non-Allowed areas clarifications related to MPS | Qualcomm Incorporated | Rel-18 | Revision of (postponed) S2-2311315. Confirm Spec version used - CR states 18.3.0! CC#3: Postponed | Myungjune (LGE) provides comments and questions. Haris(Qualcomm) responds Myungjune replies to Haris(Qualcomm) Pallab (Nokia) provides comments Haris(Qualcomm) provides r03 to change CR category to A and rel.17 version in S2-2401374 (NEW TDOC) ==== Revisions Deadline ==== Pallab (Nokia) is OK to approve r06 Haris(Qualcomm) is ok with r06 | Postponed |
| 9.21 | S2-2401374 | CR | Approval | 23.501 CR5308 (Rel-17, 'F'): Non-Allowed areas clarifications related to MPS | Qualcomm Incorporated | Rel-17 | Created in CC#2. Postponed | Wanqiang (Session Chair): it is a new allocated tdoc during CC#2. Haris(Qualcomm) provides link to initial version of the CR Pallab (Nokia) comments and provides r02 based on r00. Asks for clarification on r01 Robert (Peraton Labs) provides 1374r01. Shabnam (Ericsson) provides comments about Rel-17 support of non-3GPP access and MPS, need time to ensure other features work ==== Revisions Deadline ==== Wanqiang (Session Chair): any version we can accept now, or postpone to next meeting? Haris(Qualcomm) is ok to discuss at next meeting or SA#103 depending on the agenda but is important to clarify what is supported in each release. It will also have an effect on whether 0415 will be Cat.A (as is right now) or Cat.F ==== Final Comments Deadline ==== | Postponed |
| 9.21 | S2-2400416 | CR | Approval | 23.502 CR4226R3 (Rel-18, 'F'): Indication to the UE whether MPS is supported | Qualcomm Incorporated | Rel-18 | Revision of (postponed) S2-2311316. Noted | Haris(Qualcomm) proposes to NOTE based on discussion in thread for S2-2400415 ==== Revisions Deadline ==== | Noted |
| 9.21 | S2-2400441 | CR | Approval | 23.501 CR5232 (Rel-18, 'F'): Handling of regulatory prioritized services in non-allowed areas | Peraton Labs, CISA ECD, T-Mobile USA, AT&T, Verizon | Rel-18 | TEI-18 should be TEI18! Postponed | Myungjune (LGE) provides comments on NOTE 7. Haris(Qualcomm) objects to the CR Pallab (Nokia) is fine with the proposal and provides r02 with some corrections. Would be happy to co-sign Haris(Qualcomm) provides r03 to change CR category to A and rel.17 version in S2-2401374 (NEW TDOC) ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Postponed |
| 9.21 | S2-2400442 | CR | Approval | 23.502 CR4685 (Rel-18, 'F'): Handling of regulatory prioritized services in non-allowed areas | Peraton Labs, CISA ECD, T-Mobile USA, AT&T, Verizon | Rel-18 | TEI-18 should be TEI18! Postponed | Haris(Qualcomm) objects to the CR Pallab (Nokia) comments that a revision is needed ==== Revisions Deadline ==== Pallab (Nokia) proses to POSTPONE based on the discussion in 0441 ==== Final Comments Deadline ==== | Postponed |
| 9.21 | S2-2400443 | LS OUT | Approval | [DRAFT] LS on Handling of regulatory prioritized services in non-allowed areas | Pereton Labs | Rel-18 | Postponed | Haris(Qualcomm) needs to be revised according to the discussion in the CRs threads ==== Revisions Deadline ==== Pallab (Nokia) proposes to POSTPONE as the corresponding CRs attached with the LS could not be agreed ==== Final Comments Deadline ==== | Postponed |
| 9.22.2 | - | - | - | 5G AM Policy (AMP) | - | - | Docs:=4 | - | |
| 9.22.2 | S2-2400481 | CR | Approval | 23.502 CR4688 (Rel-18, 'D'): Cleaning up the term of RFSP Index in Use Validity Time | China Telecom Corporation Ltd. | Rel-18 | r03 Agreed. Revised to S2-2401458. | Zhuoyi (China Telecom) provides r01 to correct a coversheet error. Haiyang (Huawei) provides r02. Haiyang (Huawei) provides r03. ==== Revisions Deadline ==== Zhuoyi (China Telecom) accepts r03. ==== Final Comments Deadline ==== | Revised |
| 9.22.2 | S2-2401458 | CR | Approval | 23.502 CR4688R1 (Rel-18, 'D'): Cleaning up the term of RFSP Index in Use Validity Time | China Telecom Corporation Ltd. | Rel-18 | Revision of S2-2400481r03. Approved | Agreed | |
| 9.22.2 | S2-2400482 | CR | Approval | 23.501 CR5235 (Rel-18, 'D'): Cleaning up the term of RFSP Index in Use Validity Time | China Telecom Corporation Ltd. | Rel-18 | r01 Agreed. Revised to S2-2401459. | Zhuoyi (China Telecom) provides r01 to correct a coversheet error. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 9.22.2 | S2-2401459 | CR | Approval | 23.501 CR5235R1 (Rel-18, 'D'): Cleaning up the term of RFSP Index in Use Validity Time | China Telecom Corporation Ltd. | Rel-18 | Revision of S2-2400482r01. Approved | Agreed | |
| 9.23.2 | - | - | - | Enablers for Network Automation for 5G - Phase 3 (eNA_Ph3) | - | - | Docs:=61 | - | |
| 9.23.2 | - | - | - | General | - | - | Docs:=4 | - | |
| 9.23.2 | S2-2400630 | DISCUSSION | Information | Way forward of NAT issue in UE data collection. | Vivo | Rel-18 | Noted | Noted | |
| 9.23.2 | S2-2400361 | CR | Approval | 23.288 CR0981R3 (Rel-18, 'F'): Solve NAT issue in UE data collection | [vivo], Ericsson | Rel-18 | Revision of (noted) SP-231632 from TSG SA#102. Postponed | Huazhang (vivo) provides comments, that the solution here still didn't solve the problem listed in the S2-2400630. Maybe the F2F discussion is needed in Feb. Magnus H (Ericsson) are also happy to have nothing stated related to NAT in Rel-18. Huazhang (vivo) can agree that we rediscuss this issue in R19 UPEAS_ph2 or a single TEI19, and do noting in R18. Also prefer to postpone this contribution. Some of other comments to this paper please see inline. I have to say sorry for the objection and thanks the discussion with Magnus (E///) Juan Zhang (Qualcomm) provides comment. Magnus H (Ericsson) comments. Thomas(Nokia) supports the CR. Huazhang (vivo) reply to Juan, Magnus and Thomas, that I am not insist objection this solution, but we need to solve the concerns first, after that Huazhang will compromise has no hesitation. Juan Zhang (Qualcomm) replies to Huazhang (vivo). Magnus H (Ericsson) provides comments ==== Revisions Deadline ==== Huazhang (vivo) propose to postpone this to Athen meeting, and if the concerns from discussion paper S2-2400630 are resolved, Huazhang can make compromise. Otherwise, I am not against to leave no NAT solution in R18, and we can have R19 or TEI19 to solve this, and introduce other new solution. ==== Final Comments Deadline ==== | Postponed |
| 9.23.2 | S2-2401365 | CR | Approval | 23.288 CR1050 (Rel-18, 'F'): Miscellaneous corrections | Nokia, Nokia Shanghai-Bell | Rel-18 | r02 Agreed. Revised to S2-2401543. | Zhang Fu(Huawei) provides comments and revision r01 Thomas (nokia) replies to Zhang and provides revision r02 Zhang Fu(Huawei) is OK with r02 ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 9.23.2 | S2-2401543 | CR | Approval | 23.288 CR1050R1 (Rel-18, 'F'): Miscellaneous corrections | Nokia, Nokia Shanghai-Bell, Huawei, HiSilicon | Rel-18 | Revision of S2-2401365r02. Approved | Agreed | |
| 9.23.2 | - | - | - | Key Issue #1: How to improve correctness of NWDAF analytics | - | - | Docs:=1 | - | |
| 9.23.2 | S2-2400915 | CR | Approval | 23.288 CR1045 (Rel-18, 'F'): Adding Analytics Information in the ML Model Monitoring service | China Telecom, Huawei, HiSilicon | Rel-18 | Noted | Magnus (Ericsson) as concerns. Zhang Fu(Huawei) provides comments Bahador (NTT DOCOMO) provides comments Dimitris (Lenovo) supports the proposal Jiahui (China Telecom) replys. Jiahui (China Telecom) provides r01. Bahador (NTT DOCOMO) supports r01 Magnus H (Ericsson) provides comments Zhang Fu (Huawei) provides comment Jiahui (China Telecom) replys to Thomas (Nokia) and provides r02. Thomas(Nokia) also prefers optional parameters and requests a related revision Magnus H (Ericsson) provides comments and still have concerns Zhang (Huawei) provide comments to Magnus ==== Revisions Deadline ==== Magnus H (Ericsson) objects to this CR Jiahui (China Telecom) replys to Magnus H (Ericsson) and hope Ericsson re-consider the objection. ==== Final Comments Deadline ==== | Noted |
| 9.23.2 | - | - | - | Key Issue #2: NWDAF-assisted application detection | - | - | Docs:=2 | - | |
| 9.23.2 | S2-2400688 | CR | Approval | 23.288 CR0951R6 (Rel-18, 'F'): Source of the PFD contained in PFD information retrieved from UDR | Huawei, HiSilicon | Rel-18 | Revision of (postponed) S2-2313863. r05 Agreed. Revised to S2-2401544. | Belen (Ericsson) provides comments, include r01 Aihua(CMCC) provides r02. Mirko (Huawei) responds and cannot accept r02. Aihua(CMCC) replies to comments and suggests r02 as the way forward.. Mirko (Huawei) responds. Thomas(Nokia) provides r03. Belen (Ericsson) provides r04 Mirko (Huawei) provides r05. Aihua(CMCC) provides r06, highlighted in cyan, indicating the relevant clause in 6.16.1 of TS23.502. Mirko (Huawei) is ok with r06. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 9.23.2 | S2-2401544 | CR | Approval | 23.288 CR0951R7 (Rel-18, 'F'): Source of the PFD contained in PFD information retrieved from UDR | Huawei, HiSilicon, Nokia, Nokia Shanghai Bell, Ericsson | Rel-18 | Revision of S2-2400688r05. Approved | Agreed | |
| 9.23.2 | - | - | - | Key Issue #3: Data and analytics exchange in roaming case | - | - | Docs:=2 | - | |
| 9.23.2 | S2-2401323 | CR | Approval | 23.288 CR1005R1 (Rel-18, 'F'): Clarifications to Analytics Exposure and data collection in Roaming Case | Nokia, Nokia Shanghai-Bell | Rel-18 | Revision of (unhandled) S2-2312603. r02 Agreed. Revised to S2-2401545. | Zhao (Huawei) provides comments. Thomas(Nokia) provides r01. Magnus H (Ericsson) provides comments Thomas(Nokia) provides r02. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 9.23.2 | S2-2401545 | CR | Approval | 23.288 CR1005R2 (Rel-18, 'F'): Clarifications to Analytics Exposure and data collection in Roaming Case | Nokia, Nokia Shanghai-Bell | Rel-18 | Revision of S2-2401323r02. Approved | Agreed | |
| 9.23.2 | - | - | - | Key Issue #4: How to Enhance Data collection and Storage | - | - | Docs:=8 | - | |
| 9.23.2 | S2-2400283 | CR | Approval | 23.288 CR1025 (Rel-18, 'F'): Correction on ML Model retrieval | Huawei, HiSilicon | Rel-18 | r05 Agreed. Revised to S2-2401546. | Sihan (vivo) asks for clarification. Magnus H (Ericsson) have the same concerns as Sihan (vivo) Jaewoo (LGE) provides comments. Haiyang (Huawei) provides r01 with explanation. Magnus H (Ericsson) provides comments Sihan (vivo) provides comments Haiyang (Huawei) provides r03 with explanation. (Please ignore r02) Sihan (vivo) provides r04 Haiyang (Huawei) provides r05 based on r04 ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 9.23.2 | S2-2401546 | CR | Approval | 23.288 CR1025R1 (Rel-18, 'F'): Correction on ML Model retrieval | Huawei, HiSilicon | Rel-18 | Revision of S2-2400283r05. Approved | Agreed | |
| 9.23.2 | S2-2400528 | CR | Approval | 23.288 CR1037 (Rel-18, 'F'): Alignment of unclear description of 3DA Data Management Service | ZTE | Rel-18 | Confirm CR Number - CR states 0528! Postponed | Yuang(ZTE) agrees to postpone this CR Thomas (Nokia) raises concerns that changes have nothing to do with eNA_Ph3 WI. Suggest handling them under eNA_Ph2 WI at the next meeting ==== Revisions Deadline ==== | Postponed |
| 9.23.2 | S2-2400554 | CR | Approval | 23.288 CR1015R1 (Rel-18, 'F'): Clarification for ADRF discovery | Vivo | Rel-18 | Revision of (unhandled) S2-2312653. Approved | Agreed | |
| 9.23.2 | S2-2400555 | CR | Approval | 23.501 CR5145R1 (Rel-18, 'F'): Corrections for NWDAF functionality description | Vivo | Rel-18 | Revision of (unhandled) S2-2312654. Approved | Agreed | |
| 9.23.2 | S2-2400556 | CR | Approval | 23.288 CR1013R1 (Rel-18, 'F'): Addressing EN on reference of MDA service | Vivo | Rel-18 | Revision of (unhandled) S2-2312650. Approved | Agreed | |
| 9.23.2 | S2-2400557 | CR | Approval | 23.288 CR1014R1 (Rel-17, 'F'): Addressing EN on reference of MDA service | Vivo | Rel-17 | Revision of (unhandled) S2-2312651. CC#3: r00 + WI Code correction agreed. r00 + changes Agreed. Revised to S2-2401482. | Thomas (Nokia) comments that the eNA_Ph3 WI is not possible for a Rel-17 CR. Suggest handling the CR under eNA_Ph2 and with this WI in the next meeting Vivian(vivo) responses to Thomas' (Nokia) comments, and declares it is similar to a mirror CR, so ask for handling in Rel-18 WI this e-meeting. Thomas(Nokia) comments that Rel-17 CR cannot be a mirror to a Rel-18 CR and cannot have a Rel-18 WID on the cover page. Asks SA2 chair Andy whether it would be acceptable to change WI to eNA_Ph2 and still handle this CR in this meeting under the eNA_Ph3 AI. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 9.23.2 | S2-2401482 | CR | Approval | 23.288 CR1014R2 (Rel-17, 'F'): Addressing EN on reference of MDA service | Vivo | Rel-17 | Revision of S2-2400557r00 + changes. Approved | Agreed | |
| 9.23.2 | - | - | - | Key Issue #5: Enhance trained ML Model sharing | - | - | Docs:=5 | - | |
| 9.23.2 | S2-2400360 | DISCUSSION | Discussion | Discussion on discovery aspects of ML Model Interoperability Indicator. | Ericsson | Noted | Zhang Fu(Huawei) suggest to NOTE the paper ==== Revisions Deadline ==== | Noted | |
| 9.23.2 | S2-2400409 | CR | Approval | 23.288 CR0973R3 (Rel-18, 'F'): Correction of ML Model sharing in the scenario of Analytics context transfer | Huawei, HiSilicon | Rel-18 | Revision of (agreed, but noted at TSG SA#102) S2-2313650. r04 + changes Agreed. Revised to S2-2401547. | Yuang (ZTE) provides comments below. Ulf (Ericsson) see issues with this CR and has comments Zhang Fu (Huawei) provides comments Ulf (Ericsson) respond to comments from Huawei Zhang Fu (Huawei) respond to comments from Ericsson Ulf (Ericsson) reply to comments from Huawei Zhang (Huawei) provide comments Ulf (Ericsson) reply to comments from Huawei and asks further questions Zhang Fu (huawei) provide comments and revision r01 Ulf (Ericsson) thinks r01 looks promising, but needs some additions which will be addressed mainly in the 1052 Zhang (Huawei) provide r02 Ulf (Ericsson) inform that we may need to postpone this CR depending on progress in security around the procedure Zhang (Huawei) ask for clarification Zhang (Huawei) provide r03 with a NOTE suggested by Nokia Ulf (Ericsson) explains the text and as it stands now it is hard to understand what the CR addresses Zhang (Huawei) provide r04 with suggestion from Ericsson ==== Revisions Deadline ==== Ulf (Ericsson) add new r05 try again after issues Xiaoyan (CATT) objects to r03, r04 and r05. Fine with r01/r02 + changing 'This parameter is required when the consumer requests ML Model related information.' to 'This parameter can be provided when the consumer requests ML Model related information.' in clause 6.1B.4. Wanqiang (Session Chair): no new revision after deadline is accepted. Please give a clear text change on top of r04. Zhang Fu (Huawei) pointed out that r05 is provided after deadline, we can go with r04 with the following changes: NOTE2 in clause 6.1B.4 changes to NOTE 2: Potential security considerations in the Analytics context transfer procedure, especially related to a source NWDAF sending an ML Model address which pointed to an model produced by another MTLF are up to SA WG3. Also adding ML model identifier(es) as optional parameter in clause 6.1B.4. Ulf (Ericsson) objects r00, r01, r02 and ask if text in r05 can be accepted Ulf (Ericsson) Ericsson is fine with adding Model ID, but add new r07, including clarification that we target CASE A Ulf (Ericsson) reply to Huawei and suggest how to proceed Zhang Fu (Huawei) summarize that to go with r04 with the following changes: NOTE2 in clause 6.1B.4 changes to NOTE 2: Potential security considerations in the Analytics context transfer procedure, especially related to a source NWDAF sending an ML Model address which pointed to an model produced by another MTLF are up to SA WG3. add the following bullet in clause 6.1B.4: Optionally, ML model identifier(s), which is included only when the source NWDAF itself provides the trained ML model(s) for the analytics subscription(s) for which the related analytics context is requested. Change 'The source NWDAF checks whether it can accept the Vendor ID of the consumer' to 'The source NWDAF checks the Vendor ID to decide whether it will send ML Model Information to the consumer or not ' Ulf (Ericsson) agrees to the changes proposed by Huawei using r04 with the addition of following change in cover page In reason for change in cover page: In this CR, we only focus on Case B. change to In this CR, we only focus on Case A. Xiaoyan (CATT) objects to r04 + the changes proposed by Zhang Fu (Huawei) Xiaoyan (CATT) summarized the proposed changes to r04 Zhang Fu (Huawei) put the Xiaoyan's proposal to the comment for notes: Changes to r04 1) Remove 'NOTE 2: Potential security considerations related to a source NWDAF potentially sending an ML Model address which pointed to an model produced by another MTLF are up to SA WG3.' 2) Change 'This parameter is required when the consumer requests ML Model related information.' to 'This parameter can be provided when the consumer requests ML Model related information.' 3) add a bullet 'Optionally, ML model identifier(s), which is included only when the source NWDAF itself provides the trained ML model(s) for the analytics subscription(s) for which the related analytics context is requested. 4) Change 'The source NWDAF checks whether it can accept the Vendor ID of the consumer' to 'The source NWDAF checks the Vendor ID to decide whether it will send ML Model Information to the consumer or not ' Ulf (Ericsson) is not OK to the proposal of removing the NOTE 2 as the proposed changes to r04 done by CATT and added as comment for notes in Huawei's mail Wanqiang (session chair) we need to figure out the additional change text acceptable to all . It seems still different views. ==== Final Comments Deadline ==== | Revised |
| 9.23.2 | S2-2401547 | CR | Approval | 23.288 CR0973R4 (Rel-18, 'F'): Correction of ML Model sharing in the scenario of Analytics context transfer | Huawei, HiSilicon | Rel-18 | Revision of S2-2400409r04 + changes. CC#4: Noted | Noted | |
| 9.23.2 | S2-2401053 | CR | Approval | 23.288 CR0938R3 (Rel-18, 'F'): Use of ML Model Interoperability Indicator and Vendor ID in Discovery | Ericsson | Rel-18 | Revision of S2-2400183. r02 + changes Agreed. Revised to S2-2401548. | Vivian (vivo) provides comments. Zhang Fu (Huawei) provides comments and ask for clarification Ulf (Ericsson) respond to comments from Vivo Xiaoyan (CATT) provides comments. Ulf (Ericsson) reply to comments from CATT Zhang Fu (Huawei) provide comments Ulf (Ericsson) reply to comments from Huawei Zhang (Huawei) provide comments Vivian (vivo) provide comments Ulf (Ericsson) would like to draw the attention of vivo and Huawei to Discussion paper 0360 detailing stage 3 on the discovery of NWDAF Zhang Fu (Huawei) provide response and comment Ulf (Ericsson) hope to agree that the CR is correct as is, since it aligns with definitions and implementation in stage 3 Ulf (Ericsson) again try to understand the issue and is not OK to leave TS 23.288 not aligned with implementation Vivian (vivo) doesn't agree this CR to replace the existing NF consumer information with a new name called interoperability ID Ulf (Ericsson) explains the wrong word used in mail discussion Xiaoyan (CATT) replies to Ulf (Ericsson) Ulf (Ericsson) provide r01 which removes the discussed part Zhang (Huawei) object r00 and r01 and provide r02 Vivian (vivo) can only accept r02 Ulf (Ericsson) provide revision r03 and cannot understand r02 since we do not want to change stage 3. Zhang Fu (Huawei) object r03 ==== Revisions Deadline ==== Ulf (Ericsson) add new r04 Xiaoyan (CATT) accept r02 and r04, and objects to other revisions. Vivian (vivo) is fine with r02 and r04. Wanqiang (Session Chair): No new revisions will be accepted (except for LS out) after revision deadline. Please give a clear text change on top of r02 or r03 and make sure everybody will be ok with the additional change. Zhang Fu (Huawei) suggest to go with r02, but can live with r04 which is uploaded after deadline Ulf (Ericsson) objects to r02 and notice that companies active in the discussion up to this time at least can agree to text in r04 Ulf (Ericsson) proposes to agree to following changes compared to r02 or r03. In clause 5.2 keeping both ML Model Interoperability indicator and NF consumer information and revert to existing text for all changes proposing the removal of either of them. Also reverting the changes of NOTE 5 to existing text. Zhang Fu (Huawei) propose to go with r02 with the following changes: 1, revert the changes about Model Interoperability Indicator and NF consumer information in clause 5.2 2, revert all the changes to NOTE 5 in clause 5.2 Wanqiang (Session Chair): we can not use new revisions after deadline. But can still accept additional change if you list the actual change on top of certain version of CR. Ulf (Ericsson) is OK with Huawei's suggestions and also add following changes needed in cover page which are not reflected correctly in r02. Reason for change: Some minor changes relating to discussion document S2-2400360 Changes: Minor updates including Clarify how to use ML Model Interoperability Indicator in the context of FL. Adding reference to TS 33.501 Consequences if not approved: Misunderstanding of specification leading to wrong implementations Vivian (vivo) is fine for the two changes proposed by Zhang on top of r02+ cover page alignments proposed by Ulf ==== Final Comments Deadline ==== | Revised |
| 9.23.2 | S2-2401548 | CR | Approval | 23.288 CR0938R4 (Rel-18, 'F'): Use of ML Model Interoperability Indicator and Vendor ID in Discovery | Ericsson, Huawei, HiSilicon | Rel-18 | Revision of S2-2401053r02 + changes. Approved | Agreed | |
| 9.23.2 | - | - | - | Key issue #6: NWDAF-assisted URSP | - | - | Docs:=0 | - | |
| 9.23.2 | - | - | - | Key issue #7: Enhancements on QoS Sustainability analytics | - | - | Docs:=5 | - | |
| 9.23.2 | S2-2400006 | LS In | Action | LS from SA WG5: Reply LS on OAM input data for QoS Sustainability Analytics | SA WG5 (S5-235776) | Rel-18 | Revision of Postponed S2-2311945 from SA WG2#160. Response drafted in S2-2401048. Final response in S2-2401475 | Replied to | |
| 9.23.2 | S2-2401048 | LS OUT | Approval | [DRAFT] Reply LS on LS to SA WG2 on OAM input data for QoS Sustainability Analytics | China Mobile | Rel-18 | Revision of (postponed) S2-2313653. Response to S2-2400006. r00 + Remove the draft agreed. Revised to S2-2401475. | Revised | |
| 9.23.2 | S2-2401475 | LS OUT | Approval | Reply LS on SA5 LS to SA2 on OAM input data for QoS Sustainability Analytics | SA WG2 | Rel-18 | Revision of S2-2401048r00 + Remove the draft. Approved | Approved | |
| 9.23.2 | S2-2400987 | CR | Approval | 23.288 CR1048 (Rel-18, 'F'): Qos related correction | Huawei, HiSilicon | Rel-18 | r01 Agreed. Revised to S2-2401549. | Belen (Ericsson) provides r01 Susan (Huawei) provides r02 Belen (Ericsson) comments, cannot accept r02 ==== Revisions Deadline ==== Susan (Huawei) is ok to proceed with r01 for this meeting. ==== Final Comments Deadline ==== | Revised |
| 9.23.2 | S2-2401549 | CR | Approval | 23.288 CR1048R1 (Rel-18, 'F'): Qos related correction | Huawei, HiSilicon | Rel-18 | Revision of S2-2400987r01. Approved | Agreed | |
| 9.23.2 | - | - | - | Key Issue #8: Supporting Federated Learning in 5GC | - | - | Docs:=16 | - | |
| 9.23.2 | S2-2400284 | LS OUT | Approval | [DRAFT] LS Reply on Model Sharing With MTLF | Huawei, HiSilicon, Vivo | Rel-18 | Response to S2-2400029. CC#4: Postponed | Ulf (Ericsson) asks if we can use 0363 as basis for LS out Haiyang (Huawei) comments to Ulf (Ericsson), still propose 284 as way forward Ulf (Ericsson) ask questions to Huawei on how to solve the identified issues now when stage 2 is done in SA2 and SA3 Haiyang (Huawei) provides a way forward and r01 Ulf (Ericsson) provide r02 Haiyang (Huawei) provides r03 ==== Revisions Deadline ==== Haiyang (Huawei) is OK with r00, r01, r03; objects r02 (suggests to discuss the context of r02 in 0363) Vivian (vivo) is OK with r00, r01, r03, also prefers to send a separated LS for model URL transferring to SA3 if needed. Xiaoyan (CATT) is OK with r00, r01, r03; objects to r02 Ulf (Ericsson) can only accept r02 and objects to all other revisions including r00 Xiaoyan (CATT) replies to Ulf (Ericsson) Haiyang (Huawei) comments to Ulf (Ericsson) , requests to go with r03 and discuss this in CC#4 Thomas(Nokia) is fine with r03 ==== Final Comments Deadline ==== | Postponed |
| 9.23.2 | S2-2400363 | LS OUT | Approval | [DRAFT] Reply LS on Model Sharing With MTLF | Ericsson | Rel-18 | Response to S2-2400029. Noted | Haiyang (Huawei) suggests to use 0284 as basis. Vivian (vivo) provides comments. Ulf (Ericsson) do not agree to use 0284 as basis and responds to comments Thomas(Nokia) supports 0284 as basis. Has concerns with this LS as it is taking assumptions about SA3 work organization. ==== Revisions Deadline ==== Xiaoyan (CATT) objects to r00 ==== Final Comments Deadline ==== | Noted |
| 9.23.2 | S2-2400029 | LS In | Action | LS from SA WG3: LS on Model Sharing With MTLF | SA WG3 (S3-235110) | Revision of Postponed S2-2313240 from SA WG2#160. Responses drafted in S2-2400284, S2-2400363. CC#4: Postponed | Postponed | ||
| 9.23.2 | S2-2400123 | CR | Approval | 23.288 CR0986R1 (Rel-18, 'F'): Correction of accuracy metrics in ML model monitoring service operations | NTT DOCOMO | Rel-18 | Revision of (unhandled) S2-2312333. Postponed | Thomas (Nokia) suggest postponing the issue Bahador (NTT DOCOMO) responds Thomas (Nokia) and provides r01 Thomas (Nokia) still prefers postponing this CR Bahador (NTT DOCOMO) agrees to postpone this CR ==== Revisions Deadline ==== | Postponed |
| 9.23.2 | S2-2400456 | CR | Approval | 23.288 CR1028 (Rel-18, 'F'): Clarification on the ML model metric for FL | Intel | Rel-18 | Noted | Aihua(CMCC) objects to remove the description related to ML model metric and provides r01. Zhao (Huawei) changes the AI number in the title to 'AI#9.23.2'. Megha(Intel) provides comments Aihua(CMCC) provides r02. ==== Revisions Deadline ==== Thomas(Nokia) ask questions and proposes to note this contribution. Megha(Intel) is OK to note this CR. ==== Final Comments Deadline ==== | Noted |
| 9.23.2 | S2-2400457 | CR | Approval | 23.288 CR1029 (Rel-18, 'F'): Clarification on Federated Learning between NWDAFs | Intel | Rel-18 | r02 Agreed. Revised to S2-2401550. | Zhao (Huawei) provides comments and r01. Ulf (Ericsson) has concerns with this CR Dimitris (Lenovo) shares the same view with Ulf (Ericsson) Megha(Intel) provides comments and asks a question to Ulf(Ericsson) Ulf (Ericsson) suggest some words update Megha(Intel) provides r02 and comments Zhao (Huawei) is ok with r02. Thomas(Nokia) accepts r02, objects against r00 ==== Revisions Deadline ==== Ulf (Ericsson) objects to r00 and r01, is fine with r02 ==== Final Comments Deadline ==== | Revised |
| 9.23.2 | S2-2401550 | CR | Approval | 23.288 CR1029R1 (Rel-18, 'F'): Clarification on Federated Learning between NWDAFs | Intel | Rel-18 | Revision of S2-2400457r02. Approved | Agreed | |
| 9.23.2 | S2-2400458 | CR | Approval | 23.288 CR1030 (Rel-18, 'F'): Clarification on ML Model Metric in Federated Learning | Intel | Rel-18 | r03 Agreed. Revised to S2-2401551. | Aihua(CMCC) objects to remove the description related to ML model metric and provides r01. Zhao (Huawei) changes the AI number in the title to 'AI#9.23.2' and provides r02. Ulf (Ericsson) see issues with this CR Bahador (NTT DOCOMO) provides comment and supports r02 Zhao (Huawei) provides comments and r03. Thomas(Nokia) can accept r02, objects against r00 ==== Revisions Deadline ==== Ulf (Ericsson) objects to r00 and r01, thinks R03 is fine, can live with R02 ==== Final Comments Deadline ==== | Revised |
| 9.23.2 | S2-2401551 | CR | Approval | 23.288 CR1030R1 (Rel-18, 'F'): Clarification on ML Model Metric in Federated Learning | Intel | Rel-18 | Revision of S2-2400458r03. Approved | Agreed | |
| 9.23.2 | S2-2400464 | CR | Approval | 23.288 CR1031 (Rel-18, 'F'): Corrections to ML Model Training | LG Electronics | Rel-18 | r01 Agreed. Revised to S2-2401552. | Jaewoo (LGE) is OK with r01. Thomas (Nokia) provides r01, objects against r00 ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 9.23.2 | S2-2401552 | CR | Approval | 23.288 CR1031R1 (Rel-18, 'F'): Corrections to ML Model Training | LG Electronics | Rel-18 | Revision of S2-2400464r01. Approved | Agreed | |
| 9.23.2 | S2-2400529 | CR | Approval | 23.288 CR1038 (Rel-18, 'F'): Clarification of federated learning process | ZTE | Rel-18 | Confirm CR Number - CR states 0529! Postponed | Yuang(ZTE) agrees to postpone this CR Thomas (Nokia) suggest postponing this CR ==== Revisions Deadline ==== | Postponed |
| 9.23.2 | S2-2400681 | CR | Approval | 23.288 CR0903R4 (Rel-18, 'F'): Update the consumer of ML Model Provisioning services | Qualcomm Incorporated, vivo | Rel-18 | Revision of (unhandled) S2-2313036. Approved | Agreed | |
| 9.23.2 | S2-2401046 | CR | Approval | 23.288 CR1049 (Rel-18, 'F'): Clarification on the ML Model Metric in Federated Learning | China Mobile, vivo | Rel-18 | Approved | Agreed | |
| 9.23.2 | S2-2401052 | CR | Approval | 23.288 CR0989R2 (Rel-18, 'F'): Security Corrections | Ericsson | Rel-18 | Revision of (unhandled) S2-2313213. Noted | Haiyang (Huawei) comments Xiaoyan (CATT) objects to r00. Vivian (vivo) comments Ulf (Ericsson) responds to comments and ask to re-consider objection to solve security issue Ulf (Ericsson) adds r01 and asks if it is agreeable Xiaoyan (CATT) cannot accept r01, and provides r02. Vivian (vivo) responses to Ulf (Ericsson) and provides r03 base on r01 (since there is a r02 with no announcement). Zhang Fu provides comment to the revisions Thomas(Nokia) suggest postponing the CR as it may be premature to conclude that there will be no security solution. Thomas(Nokia) could accept r02, object against r00 and r01. Ulf (Ericsson) provide r04 and have a question to Vivo and all Zhang (Huawei) provide comment Xiaoyan (CATT) cannot accept r04. Thomas(Nokia) objects against r03 Zhang (Huawei) provide comments on r04 and way forward Ulf (Ericsson) provides r05 and merge two parallel discussions, and ask questions yet again. Zhang Fu (Huawei) ask to clarification Ulf (Ericsson) reply to clarification questions from Huawei Zhang Fu (Huawei) provide further comments Thomas(Nokia) has concerns with the proposed wording Zhang (Huawei) is OK with Nokia proposal Ulf (Ericsson) reply Nokia and Huawei Ulf (Ericsson) give new r06 if 0409 will take over the NOTE on security issues with transfer procedure Zhang (Huawei) pointed out 1052 and 1052 has similar changes ==== Revisions Deadline ==== Xiaoyan (CATT) only accepts r02, and objects to other revisions. Vivian(vivo) is ok with both r02 and r06. Ulf (Ericsson) objects to r02 Zhang Fu (Huawei) is ok with r02 and r06 if the cover page is corrected with CATT suggestion. Object all other versions Ulf (Ericsson) asks if following changes can be accepted for r06 if the changes to S2-2400409 are accepted In the cover page reason for change: Remove The paragraph starting with 'Similar security issue came out from a discussion regarding the transfer of models from a source NWDAF' ==== Final Comments Deadline ==== | Noted |
| 9.23.2 | S2-2401340 | CR | Approval | 23.288 CR0996R1 (Rel-18, 'F'): Harmonoizing terminology related to Accuracy | Nokia, Nokia Shanghai-Bell | Rel-18 | Revision of (unhandled) S2-2312591. Postponed | Aihua(CMCC) objects to modify the description related to ML model metric and provides r01. Yuang (ZTE) provides comments below. Zhao (Huawei) changes the AI number in the title to 'AI#9.23.2' and provides r02. Thomas(Nokia) asks Zhao and Aihua how r01 and r02 could work. Zhao (Huawei) replies to Thomas(Nokia). Thomas(Nokia) replies to Zhao (Huawei), suggest postponing the issue Zhao (Huawei) is fine to postpone this CR. Aihua(CMCC) agrees with Thomas(Nokia) to postpone. ==== Revisions Deadline ==== | Postponed |
| 9.23.2 | - | - | - | Key Issue #9: Enhancement of NWDAF with finer granularity of location information | - | - | Docs:=7 | - | |
| 9.23.2 | S2-2400465 | CR | Approval | 23.288 CR1032 (Rel-18, 'F'): Corrections to Analytics ID and Service operation | LG Electronics | Rel-18 | r01 Agreed. Revised to S2-2401553. | Zhang Fu(Huawei) provide comments Jaewoo (LGE) replies to Zhang Fu(Huawei) and provides r01. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 9.23.2 | S2-2401553 | CR | Approval | 23.288 CR1032R1 (Rel-18, 'F'): Corrections to Analytics ID and Service operation | LG Electronics | Rel-18 | Revision of S2-2400465r01. Approved | Agreed | |
| 9.23.2 | S2-2400790 | CR | Approval | 23.288 CR1043 (Rel-18, 'F'): Clarifications on ground truth retrieval of Location Accuracy Analytics | Vivo | Rel-18 | r13 Agreed. Revised to S2-2401554, merging S2-2400856 and S2-2401354 | Xiaoyan (CATT) provides comments. Jaewoo (LGE) provides comments on r01. Thomas (Nokia) provides r01 to merge S2-2401354 Jaewoo (LGE) provides r03. Zhang Fu (Huawei) provide r04 Thomas (Nokia) provide r05 Zhang Fu (huawei) object r04 and provide r05 Amy (vivo) provides r07 based on Zhang (Huawei)'s r06 Amy (vivo) provides r08, and replies to Xiaoyan (CATT) (copy-paste xiaoyan's comments below to keep a single email thread) Thomas(Nokia) provides r09, objects against r00, r04, r06, r07, r08 Amy (vivo) objects 09 Thomas(Nokia) replies to Amy and provides r10 Zhang Fu (Huawei) object r10 and provide r11 Thomas (Nokia) provides r12 and r13 ==== Revisions Deadline ==== Xiaoyan (CATT) prefers r08, can live with r11, r12 and r13 Thomas (Nokia) prefers r12, can live with r13, has concerns about grammatical issues in r11 Zhang Fu (Huawei) is OK with r13 and r11, object all other versions. Amy (vivo) prefers r08, and is ok with r13. ==== Final Comments Deadline ==== | Revised |
| 9.23.2 | S2-2401554 | CR | Approval | 23.288 CR1043R1 (Rel-18, 'F'): Clarifications on ground truth retrieval of Location Accuracy Analytics | Vivo, Nokia, Nokia Shanghai-Bell, Huawei, HiSilicon | Rel-18 | Revision of S2-2400790r13, merging S2-2400856 and S2-2401354. Approved | Agreed | |
| 9.23.2 | S2-2400856 | CR | Approval | 23.288 CR1044 (Rel-18, 'F'): Clarification on procedures to request Location Accuracy Analytics | CATT | Rel-18 | Merged into S2-2401554 | Amy (vivo) proposes to merge this into S2-2400790 ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 9.23.2 | S2-2401354 | CR | Approval | 23.288 CR1009R2 (Rel-18, 'F'): Clarifications to Location Accuracy Analytics | Nokia, Nokia Shanghai-Bell | Rel-18 | Revision of (revised and postponed) S2-2312622. Merged into S2-2401554 | Yuang (ZTE) provides comments below. Zhang Fu(Huawei) provide comments Amy (vivo) proposes to merge this into S2-2400790 Thomas(Nokia) accepts to merge this into S2-2400790 ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 9.23.2 | S2-2401356 | CR | Approval | 23.502 CR4615R1 (Rel-18, 'F'): Data collection for Location Accuracy Analytics via AF | Nokia, Nokia Shanghai-Bell | Rel-18 | Revision of (postponed) S2-2312623. Approved | Agreed | |
| 9.23.2 | - | - | - | Key issue #10: Interactions with MDAS/MDAF | - | - | Docs:=3 | - | |
| 9.23.2 | S2-2400005 | LS In | Action | LS from SA WG5: Reply LS MDAF service discovery by NWDAF | SA WG5 (S5-235729) | Rel-17 | Revision of Postponed S2-2311942 from SA WG2#160. Postponed | Postponed | |
| 9.23.2 | S2-2400855 | CR | Approval | 23.288 CR0945R3 (Rel-18, 'F'): Clarification on analytics collection from MDAF | CATT | Rel-18 | Revision of (unhandled) S2-2312984. r03 Agreed. Revised to S2-2401555. | Haiyang (Huawei) provides r01 Dimitris (Lenovo) has concerns with r01 ok with original version Haiyang (Huawei) provides reply Dimitris (Lenovo) provides r02 Xiaoyan (CATT) provides r03 Haiyang (Huawei) asks for clarification Xiaoyan (CATT) replies to Haiyang (Huawei). Haiyang (Huawei) is OK with r03 ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 9.23.2 | S2-2401555 | CR | Approval | 23.288 CR0945R4 (Rel-18, 'F'): Clarification on analytics collection from MDAF | CATT, Huawei | Rel-18 | Revision of S2-2400855r03. Approved | Agreed | |
| 9.23.2 | - | - | - | Editorial clean-up | - | - | Docs:=8 | - | |
| 9.23.2 | S2-2400463 | CR | Approval | 23.288 CR0926R2 (Rel-18, 'D'): Editorial changes to RE-NWDAF | LG Electronics | Rel-18 | Revision of (unhandled) S2-2312641. Approved | Agreed | |
| 9.23.2 | S2-2400530 | CR | Approval | 23.288 CR1039 (Rel-18, 'F'): Clarification on output strategy in output information of analytic | ZTE | Rel-18 | Confirm CR Number - CR states 0530! r02 Agreed. Revised to S2-2401556. | Zhao (Huawei) provides comments and r02. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 9.23.2 | S2-2401556 | CR | Approval | 23.288 CR1039R1 (Rel-18, 'F'): Clarification on output strategy in output information of analytic | ZTE | Rel-18 | Revision of S2-2400530r02. Approved | Agreed | |
| 9.23.2 | S2-2400531 | CR | Approval | 23.288 CR1040 (Rel-18, 'F'): Wrong reference number of other specification | ZTE | Rel-18 | Confirm CR Number - CR states 0531! r02 Agreed. Revised to S2-2401557. | Zhao (Huawei) provides comments and r02. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 9.23.2 | S2-2401557 | CR | Approval | 23.288 CR1040R1 (Rel-18, 'F'): Wrong reference number of other specification | ZTE | Rel-18 | Revision of S2-2400531r02. Approved | Agreed | |
| 9.23.2 | S2-2400558 | CR | Approval | 23.288 CR1041 (Rel-18, 'F'): Miscellaneous corrections for TS 23.288 | Vivo, Ericsson, Orange, China Mobile, KDDI, Huawei, HiSilicon, Verizon, China Unicom, China Telecom, OPPO | Rel-18 | r07 + changes Agreed. Revised to S2-2401558. | Bahador (NTT DOCOMO) provides r01 Zhang Fu (Huawei) provides r02 Antoine (Orange) provides r03. Belen (Ericsson) provides r04 Zhang (Huawei) provide comments Thomas (Nokia) provide comments Xiaobo (vivo) provides r05 with some clean-up. Xiaobo (vivo) provides r06 with some further editorials modifications in clause 3.1. Antoine (Orange) provides r07 (editorial). ==== Revisions Deadline ==== Xiaobo (vivo) thanks Antoine for the further refinement and is ok with r07. Belen (Ericsson) objects to r07, r06,r05,r03,r02 and r01. It is okay with r04 and the initial version. It is also okay with r07 if saying that the ML Model are out of the scope. Antoine (Orange) can accept r04 but to me it doesn't make sense to have a statement on 3GPP scope in a definition. Zhang Fu(Huawei) suggest to go with r07 by removing the definition of ML model and object r04 Antoine (Orange) is OK with r07 removing the definition of ML model. Xiaobo (vivo) is also ok with r07 removing the definition of ML model . ==== Final Comments Deadline ==== | Revised |
| 9.23.2 | S2-2401558 | CR | Approval | 23.288 CR1041R1 (Rel-18, 'F'): Miscellaneous corrections for TS 23.288 | Vivo, Ericsson, Orange, China Mobile, KDDI, Huawei, HiSilicon, Verizon, China Unicom, China Telecom, OPPO, NTT DOCOMO | Rel-18 | Revision of S2-2400558r07 + changes. Approved | Agreed | |
| 9.23.2 | S2-2401047 | CR | Approval | 23.288 CR0967R2 (Rel-18, 'F'): Editorial clean-up for the description of Figures and Procedures | China Mobile | Rel-18 | Revision of (unhandled) S2-2312435. Approved | Agreed | |
| 9.24.2 | - | - | - | Enhanced support of Non-Public Networks Phase 2 (eNPN_Ph2) | - | - | Docs:=18 | - | |
| 9.24.2 | - | - | - | NSWO | - | - | Docs:=3 | - | |
| 9.24.2 | S2-2400048 | LS In | Action | LS from CT WG4: Reply LS on Decorated NAI format for 5G-NSWO for SNPN Scenarios | CT WG4 (C4-235479) | Rel-18 | Noted | Peter Hedman (Ericsson) suggests to note the LS in and, possibly, mark in the minutes that CR in 00659 addresses the LS in. Dario (Session Chair): the intention is to address this LS in in 00659 | Noted |
| 9.24.2 | S2-2400659 | CR | Approval | 23.501 CR5252 (Rel-18, 'F'): Clarification/Alignment on usage of Decorated NAI for 5G-NSWO in case of SNPNs. | Nokia, Nokia Shanghai Bell | Rel-18 | r01 Agreed. Revised to S2-2401460. | Peter Hedman (Ericsson) Changes looks good to us and we support the CR Pallab (Nokia) provides r01. Only change it to add Ericsson in the source ==== Revisions Deadline ==== Pallab (Nokia) Proposes to approve r01 ==== Final Comments Deadline ==== | Revised |
| 9.24.2 | S2-2401460 | CR | Approval | 23.501 CR5252R1 (Rel-18, 'F'): Clarification/Alignment on usage of Decorated NAI for 5G-NSWO in case of SNPNs. | Nokia, Nokia Shanghai Bell, Ericsson | Rel-18 | Revision of S2-2400659r01. Approved | Agreed | |
| 9.24.2 | - | - | - | Network Access Control | - | - | Docs:=4 | - | |
| 9.24.2 | S2-2400395 | CR | Approval | 23.501 CR5231 (Rel-18, 'F'): Clarify validity information for network access control | MediaTek Inc., Futurewei | Rel-18 | Noted | Peter Hedman (Ericsson) provides comments Pallab (Nokia) provides comments and concurs with the view from Ericsson Amanda ( Futurewei ) responses to Nokia's comment Peter Hedman (Ericsson) provides reply to Amanda Pallab (Nokia) responds to Amanda ( Futurewei ) Amanda ( Futurewei ) provides responses to Peter ( Ericsson ) ==== Revisions Deadline ==== Pallab (Nokia) proposes to NOTE this CR Peter Hedman (Ericsson) proposes to NOTE this CR ==== Final Comments Deadline ==== | Noted |
| 9.24.2 | S2-2401250 | CR | Approval | 23.502 CR4733 (Rel-18, 'F'): Clarify validity information for network access control | MediaTek Inc.,Futurewei | Rel-18 | Noted | Pallab (Nokia) provides comments. Also changed the subject line to reflect the correct Tdoc number Peter Hedman (Ericsson) provides comments Chia-Lin (MediaTek) provides comments Myungjune (LGE) comments Chia-Lin (MediaTek) responds to Myungjune (LGE) Chia-Lin (MediaTek) responds to Guanzhou(InterDigitial) Guanzhou (InterDigtial) shares the view that UDM should not perform location validity check. Pallab (Nokia) provides comments. Proposes to NOTE this CR Chia-Lin (MediaTek) responds to Pallab (Nokia) and disagreed to NOTE the CR Marco(Huawei) shares the view that UDM should not perform location validity check Chia-Lin (MediaTek) responds to Marco (Huawei) Pallab (Nokia) responds Pallab (Nokia) responds Chia-Lin (MediaTek) ==== Revisions Deadline ==== Pallab (Nokia) proposes to NOTE this CR Peter Hedman (Ericsson) proposes to NOTE this CR ==== Final Comments Deadline ==== | Noted |
| 9.24.2 | S2-2400658 | CR | Approval | 23.501 CR4766R3 (Rel-18, 'F'): Remove time validity check from UDM in the credential holder for UE registering to SNPN providing access to localised services | Nokia, Nokia Shanghai Bell, Ericsson | Rel-18 | Revision of (postponed) S2-2311531. Noted | Chia-Lin (MediaTek) disagrees this CR Peter Hedman (Ericsson) provides reply Amanda ( Futurewei ) also disagree with this CR and replies to Ericsson Peter Hedman (Ericsson) provides question to Amanda Pallab (Nokia) replies to Amanda (Futurewei) Amanda ( Futurewei ) responses to Pallab ( Nokia ) ==== Revisions Deadline ==== Chia-Lin (MediaTek) propose to note this CR ==== Final Comments Deadline ==== | Noted |
| 9.24.2 | S2-2400974 | CR | Approval | 23.501 CR5279 (Rel-18, 'F'): Network and UE enforcement of access to Localized Services | Ericsson, Nokia, Nokia Shanghai Bell | Rel-18 | Noted | Sebastian (Qualcomm) asks a question Guanzhou (InterDigtial) questions the meaning of 'If the UE is not enabled to access other services than the Localized Services in the SNPN, ...' Pallab (Nokia) responds to Sebastian (Qualcomm) Pallab (Nokia) responds to Guanzhou (InterDigtial) Chia-Lin (MediaTek) disagrees the CR Peter Hedman (Ericsson) provides comments and r01 Guanzhou (InterDigtial) OK with r01 ==== Revisions Deadline ==== Pallab (Nokia) proposes to approve r01 Chia-Lin (MediaTek) propose to note this CR Peter Hedman (Ericsson) proposes to approve r01 ==== Final Comments Deadline ==== | Noted |
| 9.24.2 | - | - | - | SNPN selection | - | - | Docs:=6 | - | |
| 9.24.2 | S2-2400586 | CR | Approval | 23.501 CR5244 (Rel-18, 'F'): Adding location validity condition to Credentials Holder controlled prioritized list of preferred SNPNs for accessing Localized Services | LG Electronics | Rel-18 | Merged into S2-2401461 | Myungjune (LGE) OK to merge into S2-2400778. Yishan (Huawei) suggests to merge S2-2400586 into S2-2400778 ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 9.24.2 | S2-2400778 | CR | Approval | 23.501 CR5263 (Rel-18, 'F'): Correction on validity information for SNPN | Huawei, HiSilicon, Ericsson, Nokia, Nokia Shanghai Bell | Rel-18 | r02 Agreed. Revised to S2-2401461, merging S2-2400586 | Myungjune (LGE) provides r01 to cosign. Yishan (Huawei) is ok with r01 Peter Hedman (Ericsson) Thanks and r01 is good to us as well Sebastian (Qualcomm) provides r02 Peter Hedman (Ericsson) provides comments and ok with r02 Pallab (Nokia) ok with r02 Yishan (Huawei) is ok with r02 ==== Revisions Deadline ==== Yishan (Huawei) responds to Myungjune (LGE) Myungjune (LGE) is ok with r02 and want to cosign Sebastian (Qualcomm) is ok with r02, objects to other versions Peter Hedman (Ericsson) ok with any revision ==== Final Comments Deadline ==== | Revised |
| 9.24.2 | S2-2401461 | CR | Approval | 23.501 CR5263R1 (Rel-18, 'F'): Correction on validity information for SNPN | Huawei, HiSilicon, Ericsson, Nokia, Nokia Shanghai Bell, LG Electronics | Rel-18 | Revision of S2-2400778r02, merging S2-2400586. Approved | Agreed | |
| 9.24.2 | S2-2400779 | CR | Approval | 23.502 CR4709 (Rel-18, 'F'): Correction on validity information for SNPN | Huawei, HiSilicon | Rel-18 | Agreed. Approved | Peter Hedman (Ericsson) provides comments Yishan (Huawei) answers to Peter Hedman (Ericsson) ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Agreed |
| 9.24.2 | S2-2400777 | CR | Approval | 23.501 CR5262 (Rel-18, 'F'): Clarifications on network re-selection for SNPN for accessing Localized Services | Huawei, HiSilicon | Rel-18 | r00 + changes Agreed. Revised to S2-2401462. | Pallab (Nokia) provides comments. Yishan (Huawei) answers to Pallab (Nokia). Pallab (Nokia) responds to Yishan (Huawei); Would prefer to go with option 2 i.e. only have reference to stage 3 spec Yishan (Huawei) provides r01 (go with option 2) according to the comments from Pallab (Nokia) Pallab (Nokia) OK with r01 Peter Hedman (Ericsson) ok with simplified r01 Yishan (Huawei) provides r02 to add Nokia, Nokia Shanghai Bell as co-signing companies based on comment from Pallab (Nokia) ==== Revisions Deadline ==== Pallab (Nokia) OK to approve r02 Sebastian (Qualcomm) objects to the revisions but can be ok with r00 if 'shall' is replaced by 'may' in the new paragraph and 'UE shall' is replaced by 'UE may' in the paragraph above. Yishan (Huawei) is ok with the proposal from Sebastian (Qualcomm) to go with r00 + 'shall' is replaced by 'may' in the new paragraph and 'UE shall' is replaced by 'UE may' in the paragraph above Peter Hedman (Ericsson) provides question whether it is a may or shall in 23.122 or whether we need to state as described in 23.122? Peter Hedman (Ericsson) ok with proposal from Sebastian to use may for SNPN seection as that is aligned with 23.122 Pallab (Nokia) is also OK with r00 + replacing 'shall' with 'may' that is aligned with TS 23.122 ==== Final Comments Deadline ==== | Revised |
| 9.24.2 | S2-2401462 | CR | Approval | 23.501 CR5262R1 (Rel-18, 'F'): Clarifications on network re-selection for SNPN for accessing Localized Services | Huawei, HiSilicon, Nokia, Nokia Shanghai Bell, Ericsson | Rel-18 | Revision of S2-2400777r00 + changes. Approved | Agreed | |
| 9.24.2 | - | - | - | CAG | - | - | Docs:=3 | - | |
| 9.24.2 | S2-2400780 | CR | Approval | 23.501 CR5264 (Rel-18, 'F'): Correction on validity information for CAG | Huawei, HiSilicon | Rel-18 | r01 Agreed. Revised to S2-2401463. | Peter Hedman (Ericsson) provides comments and support Yishan (Huawei) answers to Peter Hedman (Ericsson) Yishan (Huawei) provides r01 according to the comment from Peter Hedman (Ericsson) ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 9.24.2 | S2-2401463 | CR | Approval | 23.501 CR5264R1 (Rel-18, 'F'): Correction on validity information for CAG | Huawei, HiSilicon, Ericsson | Rel-18 | Revision of S2-2400780r01. Approved | Agreed | |
| 9.24.2 | S2-2400781 | CR | Approval | 23.502 CR4710 (Rel-18, 'F'): Correction on validity information for CAG | Huawei, HiSilicon | Rel-18 | Approved | Agreed | |
| 9.24.2 | - | - | - | Other | - | - | Docs:=2 | - | |
| 9.24.2 | S2-2400660 | CR | Approval | 23.501 CR5253 (Rel-18, 'F'): Correction on NSSAAF Selection in case of SNPN | Nokia, Nokia Shanghai Bell | Rel-18 | Approved | Agreed | |
| 9.24.2 | S2-2400975 | CR | Approval | 23.501 CR5280 (Rel-18, 'F'): Support of used underlay network | Ericsson | Rel-18 | Noted | Pallab (Nokia) provides editorial comments. Supports this CR Pallab (Nokia) provides editorial comments. Supports this CR. (Resending with correct subject line) Yishan (Huawei) comments Sebastian (Qualcomm) comments that it is not clear why this CR is FASMO given that the reason for change says 'The specifications assumes restrictions that cannot be restricted.' Dieter (Deutsche Telekom) comments that it is not clear why this CR is FASMO. Peter Hedman (Ericsson) provides replies Marco(Huawei) provides comments and express concern Sebastian (Qualcomm) provides r01 Peter Hedman (Ericsson) provides comments and fine with r01 Dieter (Deutsche Telekom) while it is still not FASMO r01 is ok for us. Yishan (Huawei) has concerns on the r01 Sebastian (Qualcomm) replies to Yishan ==== Revisions Deadline ==== Yishan (Huawei) responds to Sebastian (Qualcomm) Yishan (Huawei) proposes to note this CR since it is not FASMO and may have impacts on the existing 5G system. Peter Hedman (Ericsson) fail to understand how the proposal impacts the 5GS as it explains the relaty of not able to differentiate the cases? Yishan (Huawei) further explain the concerns to Peter Hedman (Ericsson). Omkar (CableLabs) supports r01. ==== Final Comments Deadline ==== Peter Hedman (Ericsson) provides reply to Yishan | Noted |
| 9.25.2 | - | - | - | Enhancement of 5G UE Policy (eUEPO) | - | - | Docs:=52 | - | |
| 9.25.2 | - | - | - | KI#1 | - | - | Docs:=4 | - | |
| 9.25.2 | S2-2400008 | LS In | Action | LS from CT WG1: Reply LS on provisioning list of tuples to UE | CT WG1 (C1-237896) | Rel-18 | Revision of Postponed S2-2311950 from SA WG2#160. Noted | Changhong (Intel) proposes to NOTE this LS In. | Noted |
| 9.25.2 | S2-2400189 | CR | Approval | 23.503 CR1240 (Rel-18, 'F'): KI#1 Provisioning of new, updated and removed tuples for VPS URSP Rules to the UE | Ericsson | Rel-18 | r02 Agreed. Revised to S2-2401559. | Haiyang (Huawei) provides r01 Srinivas Garikipati (Nokia) comments on r01 Haiyang (Huawei) provides comments Belen (Ericsson) can accept r01, prefer initial version Haiyang (Huawei) provides r02 as a clean version of r01 ==== Revisions Deadline ==== Belen (Ericsson) is okay with r02 ==== Final Comments Deadline ==== | Revised |
| 9.25.2 | S2-2401559 | CR | Approval | 23.503 CR1240R1 (Rel-18, 'F'): KI#1 Provisioning of new, updated and removed tuples for VPS URSP Rules to the UE | Ericsson, Huawei, HiSilicon | Rel-18 | Revision of S2-2400189r02. Approved | Agreed | |
| 9.25.2 | S2-2400357 | CR | Approval | 23.502 CR4679 (Rel-18, 'F'): Corrections in Nnef_ServiceParameter_Notify operation | Ericsson | Rel-18 | Approved | Agreed | |
| 9.25.2 | - | - | - | KI#2 | - | - | Docs:=37 | - | |
| 9.25.2 | S2-2400011 | LS In | Action | LS from CT WG1: LS on UE reporting URSP rule enforcement | CT WG1 (C1-237981) | Rel-18 | Revision of Postponed S2-2311955 from SA WG2#160. Responses drafted in S2-2400337, S2-2400474, S2-2401100, S2-2401168, S2-2401305. Final response in S2-2401560 | Replied to | |
| 9.25.2 | S2-2400337 | LS OUT | Approval | [DRAFT] Reply LS on UE reporting URSP rule enforcement | China Mobile | Rel-18 | Response to S2-2400011. r01 + clean up Agreed. Revised to S2-2401560, merging S2-2401100 | Changhong (Intel) proposes to use this paper as baseline for LS OUT. Jinguo(ZTE) provides r01, add attachment, change the source to SA2 ==== Revisions Deadline ==== Yi (China Mobile) is ok with r01. ==== Final Comments Deadline ==== | Revised |
| 9.25.2 | S2-2401560 | LS OUT | Approval | Reply LS on UE reporting URSP rule enforcement | SA WG2 | Rel-18 | Revision of S2-2400337r01 + clean up, merging S2-2401100. Approved | Approved | |
| 9.25.2 | S2-2400474 | LS OUT | Approval | [DRAFT] LS Reply to C1-237981 on UE reporting URSP rule enforcement | Intel | Rel-18 | Revision of (revised) S2-2312241. Response to S2-2400011. Noted | Changhong (Intel) proposes to NOTE it. ==== Revisions Deadline ==== | Noted |
| 9.25.2 | S2-2401100 | LS OUT | Approval | [DRAFT] Reply LS on UE reporting URSP rule enforcement | ZTE | Rel-18 | Response to S2-2400011. Merged into S2-2401560 | Changhong (Intel) proposes to merge it into S2-2400337. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 9.25.2 | S2-2401168 | LS OUT | Approval | [DRAFT] Reply LS on UE reporting URSP rule enforcement | Nokia, Nokia Shanghai Bell | Rel-18 | Revision of (unhandled) S2-2312865. Response to S2-2400011. Noted | Changhong (Intel) proposes to NOTE it. ==== Revisions Deadline ==== | Noted |
| 9.25.2 | S2-2401305 | LS OUT | Approval | [DRAFT] Reply LS on UE reporting URSP rule enforcement | Apple | Rel-18 | Revision of (unhandled) S2-2313224. Response to S2-2400011. Noted | Changhong (Intel) proposes to NOTE it. ==== Revisions Deadline ==== | Noted |
| 9.25.2 | S2-2400832 | LS OUT | Approval | [DRAFT] Reply LS on UE reporting URSP rule enforcement | OPPO | Rel-18 | Noted | Changhong (Intel) proposes to NOTE it. ==== Revisions Deadline ==== | Noted |
| 9.25.2 | S2-2400335 | CR | Approval | 23.503 CR1243 (Rel-18, 'F'): Correction on URSP rule enforcement reporting | China Mobile | Rel-18 | r09 + changes Agreed. Revised, merging S2-2401101 to S2-2401561 | Jinguo(ZTE) comments Huazhang (vivo) correct the title, because this paper should be S2-2400335, not 355 Pavan (Google) seeks clarification. Yi (China Mobile) replies and provides r01. Yi (China Mobile) replies. Jinguo(ZTE) provides r02 and add cosigner. Srinivas Garikipati (Nokia) provides r04 Changhong (Intel) provides r03 with further clarification. Yi (China Mobile) replies and provides r02. Jinguo(ZTE) response to Krisztian (Apple) Krisztian (Apple) comments. Pavan (Google) provides some comments. Haiyang (Huawei) provides r05. Belen (Ericsson) provides r06, comments and supports this revision, Changhong (Intel) provides r06. Pavan (Google) deletes Note 2a in r08. Srinivas Garikipati (Nokia) would like to co-sign Belen (Ericsson) provides r09, removing overlapping text with S2-2400192 ==== Revisions Deadline ==== Yi (China Mobile) suggest to go with r09 with or without addtional cleanup on coverpage. Hong (Qualcomm) comments that the summary of change on coverage page contains additional bullet that should be removed. Yi (China Mobile) provides r10 with cleanup on coverpage and add Nokia as co-signer, in case this can be used as agreed version. Antoine (Orange) asks why 'the UE may delay the reporting' (r06-10). Yang (OPPO) comments the CR has many parts of change over change Antoine (Orange) objects to because (r06-10) 'the UE may delay the reporting' is not in the submitted CR scope and was not even justified or disussed. Antoine (Orange) objects to r06, r07, r08, r09 and r10 because 'the UE may delay the reporting' is not in the submitted CR scope and was not even justified or disussed. ==== Final Comments Deadline ==== | Revised |
| 9.25.2 | S2-2401561 | CR | Approval | 23.503 CR1243R1 (Rel-18, 'F'): Correction on URSP rule enforcement reporting | China Mobile, ZTE, Huawei, Ericsson, Nokia | Rel-18 | Revision of S2-2400335r09 + changes, merging S2-2401101. CC#4: Approved | Agreed | |
| 9.25.2 | S2-2400336 | CR | Approval | 23.502 CR4641R1 (Rel-18, 'F'): Correction on URSP rule enforcement reporting | China Mobile | Rel-18 | Revision of (unhandled) S2-2312946. Approved | Changhong (Intel) proposes to use this paper as baseline for 23.502 CR. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Agreed |
| 9.25.2 | S2-2401101 | CR | Approval | 23.503 CR1260 (Rel-18, 'F'): Clarification on URSP rule enforcement reporting | ZTE | Rel-18 | Merged into S2-2401561 | Changhong (Intel) proposes to mark this paper as merged into S2-2400335. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 9.25.2 | S2-2400674 | DISCUSSION | Discussion | UE reporting enforced URSP rules per PDU Session. | Google, Apple | Rel-18 | Noted | Noted | |
| 9.25.2 | S2-2401298 | CR | Approval | 23.503 CR1265 (Rel-18, 'F'): Clarification on UE reporting URSP rule enforcement | Apple, Google | Rel-18 | Revised to S2-2401310 | Srinivas Garikipati (Nokia) Requesting clarification | Revised |
| 9.25.2 | S2-2401310 | CR | Approval | 23.503 CR1265R1 (Rel-18, 'F'): Clarification on UE reporting URSP rule enforcement | Apple, Google | Rel-18 | Revision of S2-2401298. Noted | Yi (China Mobile) comments the CR doesn't provide clarification. Srinivas Garikipati (Nokia) Considering the SoH in CC1, we could note this paper. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Noted |
| 9.25.2 | S2-2400805 | CR | Approval | 23.503 CR1255 (Rel-18, 'F'): Clarification on UE reporting URSP rule enforcement | OPPO, China Telecom, China Unicom, vivo | Rel-18 | r01 Agreed. Revised to S2-2401562. | Belen (Ericsson) suggest to merge into S2-2400335 Yang (OPPO) replies Yang (OPPO): we should keep the CR separate from another one. Due to the reason below Yang (OPPO): provide r01, removing the overlapped wording to latest S2-2400335 ==== Revisions Deadline ==== Belen (Ericsson) is okay with r01 ==== Final Comments Deadline ==== | Revised |
| 9.25.2 | S2-2401562 | CR | Approval | 23.503 CR1255R1 (Rel-18, 'F'): Clarification on UE reporting URSP rule enforcement | OPPO, China Telecom, China Unicom, vivo | Rel-18 | Revision of S2-2400805r01. Approved | Agreed | |
| 9.25.2 | S2-2400108 | CR | Approval | 23.503 CR1224R1 (Rel-18, 'F'): Clarification to URSP rule enforcement reporting. | Nokia, Nokia Shanghai Bell | Rel-18 | Revision of (unhandled) S2-2312864. Approved | Agreed | |
| 9.25.2 | S2-2400192 | CR | Approval | 23.503 CR1214R1 (Rel-18, 'F'): URSP Rule enforcing reporting to the PCF | Ericsson | Rel-18 | Revision of (unhandled) S2-2312535. Approved | Yi (China Mobile) comments. Belen (Ericsson) provides a response to China Mobile. Srinivas Garikipati (Nokia) comments in context to the concluded SoH in CC1 Belen (Ericsson} asks Nokia what is the relation with SoH at CC1 Srinivas Garikipati (Nokia) comments to Belen Belen (Ericsson} thanks Nokia, prefers to comment to S2-2400192 ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Agreed |
| 9.25.2 | S2-2400275 | DISCUSSION | Discussion | Discussion paper on interaction between SM-PCF and UE-PCF for PCC rule generation. | Huawei, HiSilicon | Rel-18 | Revision of (unhandled) S2-2312293. Noted | Noted | |
| 9.25.2 | S2-2400276 | CR | Approval | 23.502 CR4316R2 (Rel-18, 'F'): Interaction between SM-PCF and UE-PCF for PCC rule generation | Huawei, HiSilicon, Vivo | Rel-18 | Revision of (unhandled) S2-2312294. Postponed | Pallab (Nokia) provides comments. Has strong concerns against this proposal. Proposes to go with Nokia CR in S2-2400656 Belen (Ericsson) prefers to go with Nokia proposal in S2-2400656 Pallab (Nokia) proposes to NOTE this Haiyang (Huawei) proposes to postpone this based on offline discussion ==== Revisions Deadline ==== | Postponed |
| 9.25.2 | S2-2400277 | CR | Approval | 23.503 CR1116R2 (Rel-18, 'F'): Interaction between SM-PCF and UE-PCF for PCC rule generation | Huawei, HiSilicon, Vivo | Rel-18 | Revision of (unhandled) S2-2312295. r01 Agreed. Revised to S2-2401563. | Pallab (Nokia) has strong concerns against this CR. Proposes to go with Nokia CR in S2-2400656. Please see further comments in the thread for 0276 Belen (Ericsson) prefers to go with Nokia proposal in S2-2400656 Pallab (Nokia) proposes to NOTE this Haiyang (Huawei) provides r01 removing all stuff on PCC rule generation ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 9.25.2 | S2-2401563 | CR | Approval | 23.503 CR1116R3 (Rel-18, 'F'): Interaction between SM-PCF and UE-PCF for PCC rule generation | Huawei, HiSilicon, Vivo | Rel-18 | Revision of S2-2400277r01. Approved | Agreed | |
| 9.25.2 | S2-2400655 | DISCUSSION | Endorsement | Discussion paper on PCC rule update based on URSP rule enforcement report. | Nokia, Nokia Shanghai Bell | Rel-18 | Revision of (unhandled) S2-2312613. Noted | Noted | |
| 9.25.2 | S2-2400656 | CR | Approval | 23.503 CR1110R2 (Rel-18, 'F'): Correction to Policy control decisions based on awareness of URSP rule enforcement | Nokia, Nokia Shanghai Bell | Rel-18 | Revision of (unhandled) S2-2312614. Postponed | Haiyang (Huawei) thinks it is not sufficient to use OAM to configure per UE handling, suggests to use 0276 as basis Hong (Qualcomm) comments. Pallab (Nokia) has strong concerns to use Huawei paper 0276 as baseline. Proposes to go with this CR. Please see further details in the thread for 0276. Let us have a single thread i.e. 0276 to discuss this topic. Belen (Ericsson) is okay with this CR. Pallab (Nokia) proposes to this CR (i.e. S2-2400656r00) and NOTE the TDocs S2-2400276 and S2-2400277 (resending with correction) Pallab (Nokia) proposes to Approve this CR (i.e. S2-2400656r00) and NOTE the TDocs S2-2400276 and S2-2400277 Haiyang (Huawei) proposes to note or postpone this CR ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Postponed |
| 9.25.2 | S2-2400657 | CR | Approval | 23.502 CR4699 (Rel-18, 'F'): Correction to PDU Session Establishment and Modification procedure for URSP rule enforcement reporting | Nokia, Nokia Shanghai Bell | Rel-18 | Approved | Haiyang (Huawei) proposes to note or postpone this CR ==== Revisions Deadline ==== Pallab (Nokia) points that this CR is not related to the discussion in 0656 and 0276. This is independent and different topic. There was no comment before revision deadline. R00 can be approved Haiyang (Huawei) clarifies the previous comments from my side was for 0656, not 0657 Pallab (Nokia) thanks Haiyang (Huawei) for clarifying and proposes to approve r00 ==== Final Comments Deadline ==== | Agreed |
| 9.25.2 | S2-2400472 | CR | Approval | 23.503 CR1205R1 (Rel-18, 'F'): Add missing indication of UE capability of reporting URSP rule enforcement in Table 6.2-1 | Intel | Rel-18 | Revision of (unhandled) S2-2312239. r01 Agreed. Revised to S2-2401564. | Srinivas Garikipati (Nokia) provides r01 Srinivas Garikipati (Nokia) Resends the email ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 9.25.2 | S2-2401564 | CR | Approval | 23.503 CR1205R2 (Rel-18, 'F'): Add missing indication of UE capability of reporting URSP rule enforcement in Table 6.2-1 | Intel | Rel-18 | Revision of S2-2400472r01. Approved | Agreed | |
| 9.25.2 | S2-2400473 | CR | Approval | 23.503 CR1206R1 (Rel-18, 'D'): Clarification on UE Capability of reporting URSP rule enforcement | Intel | Rel-18 | Revision of (unhandled) S2-2312240. Approved | Belen (Ericsson) comments that there is an overlap with S2-2400578 ==== Revisions Deadline ==== Changhong (Intel) replies to Belen. Belen (Ericsson) agrees with Intel, OK with this CR, my comment was to S2-2400657. ==== Final Comments Deadline ==== | Agreed |
| 9.25.2 | S2-2400578 | CR | Approval | 23.502 CR4693 (Rel-18, 'F'): Update to the PDU Session Modification Procedure for PCC Rule Generation when Connection Capabilities are Reported | InterDigital Inc. | Rel-18 | r03 Agreed. Revised to S2-2401565. | Haiyang (Huawei) comments Mike (InterDigital) responds. Hong (Qualcomm) comments on r01. Mike (InterDigital) replies and provide r01, in r01 the only change is that the ME box is not checked. Huazhang (vivo) comments Changhong (Intel) comments. Belen (Ericsson) provides comments. Mike (InterDigital) replies and provides r02 Mike (InterDigital) replies and provides r03. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 9.25.2 | S2-2401565 | CR | Approval | 23.502 CR4693R1 (Rel-18, 'F'): Update to the PDU Session Modification Procedure for PCC Rule Generation when Connection Capabilities are Reported | InterDigital Inc. | Rel-18 | Revision of S2-2400578r03. Approved | Agreed | |
| 9.25.2 | S2-2400626 | CR | Approval | 23.502 CR4337R2 (Rel-18, 'F'): URSP rule enforcement from roaming UE | Vivo | Rel-18 | Revision of (unhandled) S2-2312230. r02 Agreed. Revised to S2-2401566. | Srinivas Garikipati (Nokia) provides comments Huazhang (vivo) provides r01 Yang (OPPO) comments it should align the term with other CR Huazhang (vivo) thanks Yang, and will follow the discussion in S2-2400336 and decides how to modify the paper. Huazhang (vivo) provides r02 to align with the term in 2400336, r01 keeps the Connection Capability, r02 changes to URSP rule enforcment ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 9.25.2 | S2-2401566 | CR | Approval | 23.502 CR4337R3 (Rel-18, 'F'): URSP rule enforcement from roaming UE | Vivo | Rel-18 | Revision of S2-2400626r02. Approved | Agreed | |
| 9.25.2 | S2-2400627 | CR | Approval | 23.502 CR4336R2 (Rel-18, 'F'): Correction of PCF for session receives PCF (PCF for UE) binding information | Vivo | Rel-18 | Revision of (unhandled) S2-2312231. Approved | Agreed | |
| 9.25.2 | S2-2400628 | CR | Approval | 23.503 CR1120R2 (Rel-18, 'F'): Not reporting URSP rule enforcement other then connection capability | Vivo, Google | Rel-18 | Revision of (unhandled) S2-2312233. r02 Agreed. Revised to S2-2401567. | Belen (Ericsson) provides comments Huazhang (vivo) provides r01, to reflect the comments Huazhang (vivo) provides r02 and reply to Krisztian Krisztian (Apple) questions the need for the CR. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 9.25.2 | S2-2401567 | CR | Approval | 23.503 CR1120R3 (Rel-18, 'F'): Not reporting URSP rule enforcement other then connection capability | Vivo, Google | Rel-18 | Revision of S2-2400628r02. Approved | Agreed | |
| 9.25.2 | S2-2400876 | CR | Approval | 23.502 CR4714 (Rel-18, 'F'): Forwarding of URSP Rule Enforcement Information for LBO roaming | Samsung | Rel-18 | Postponed | Srinivas Garikipati (Nokia) provides inputs. Changhong (Intel) comments. Jicheol (Samsung) comments. Srinivas Garikipati (Nokia) provides clarification to Jicheol ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Postponed |
| 9.25.2 | - | - | - | KI#3 | - | - | Docs:=11 | - | |
| 9.25.2 | S2-2400007 | LS In | Action | LS from CT WG1: URSP provisioning in EPS | CT WG1 (C1-237892) | Rel-18 | Revision of Postponed S2-2311949 from SA WG2#160. Noted | Changhong (Intel) proposes to NOTE this LS In. | Noted |
| 9.25.2 | S2-2400107 | CR | Approval | 23.501 CR5179R1 (Rel-18, 'F'): Clarifications related to the scenario when the PDN connection handlig the UE Policy Container is released. | Nokia, Nokia Shanghai Bell | Rel-18 | Revision of (unhandled) S2-2312861. r02 Agreed. Revised to S2-2401568. | Belen (Ericsson) provides comments, raise concerns on the current revision. Srinivas Garikipati (Nokia) provides feedback and r01 Belen (Ericsson) provides r02 Srinivas Garikipati (Nokia) comments on r02 ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 9.25.2 | S2-2401568 | CR | Approval | 23.501 CR5179R2 (Rel-18, 'F'): Clarifications related to the scenario when the PDN connection handlig the UE Policy Container is released. | Nokia, Nokia Shanghai Bell | Rel-18 | Revision of S2-2400107r02. Approved | Agreed | |
| 9.25.2 | S2-2400190 | CR | Approval | 23.501 CR5217 (Rel-18, 'F'): PDN Selection for URSP delivery in EPS | Ericsson | Rel-18 | r01 Agreed. Revised to S2-2401569. | Srinivas Garikipati (Nokia) Similar comment as that of 2400191 and asks clarification. Belen (Ericsson) replies to Nokia. Huazhang (vivo) provides r01, that only keep the indication in PDU session ACK ==== Revisions Deadline ==== Huazhang (vivo) can only accept r01, thanks. ==== Final Comments Deadline ==== | Revised |
| 9.25.2 | S2-2401569 | CR | Approval | 23.501 CR5217R1 (Rel-18, 'F'): PDN Selection for URSP delivery in EPS | Ericsson | Rel-18 | Revision of S2-2400190r01. Approved | Agreed | |
| 9.25.2 | S2-2400191 | CR | Approval | 23.502 CR4673 (Rel-18, 'F'): PDN Selection for URSP delivery in EPS | Ericsson | Rel-18 | r01 Agreed. Revised to S2-2401570. | Srinivas Garikipati (Nokia) Requests clarification on removal of step 4a Huazhang (vivo) comments and seek more clearification Belen (Ericsson) replies to comments from Nokia and vivo Belen (Ericsson) replies to comments from Nokia and vivo with more details Changhong (Intel) comments. Belen (Ericsson) replies to Intel and asks clarifications Huazhang (vivo) provides r01 to remove the ePCO ==== Revisions Deadline ==== Huazhang (vivo) can only accept r01, thanks ==== Final Comments Deadline ==== | Revised |
| 9.25.2 | S2-2401570 | CR | Approval | 23.502 CR4673R1 (Rel-18, 'F'): PDN Selection for URSP delivery in EPS | Ericsson | Rel-18 | Revision of S2-2400191r01. Approved | Agreed | |
| 9.25.2 | S2-2400447 | CR | Approval | 23.502 CR4282R3 (Rel-18, 'F'): UE-PCF stores UE indication of support of URSP delivery in EPS in UDR | Oracle, Ericsson, Verizon UK Ltd | Rel-18 | Revision of (unhandled) S2-2312062. Approved | Agreed | |
| 9.25.2 | S2-2400484 | CR | Approval | 23.501 CR5236 (Rel-18, 'F'): Clarification on 5GS to EPS mobility indication | Samsung | Rel-18 | Noted | Srinivas Garikipati (Nokia) provides inputs. DongYeon (Samsung) replies to Nokia, this paper clarifies that where the indication should be existed and the current spec text is incorrect. Changhong (Intel) proposes to NOTE this paper. ==== Revisions Deadline ==== DongYeon (Samsung) is OK to NOTE. ==== Final Comments Deadline ==== | Noted |
| 9.25.2 | S2-2400629 | CR | Approval | 23.502 CR4696 (Rel-18, 'F'): PCF discovery for URSP rule provision in EPS | Vivo | Rel-18 | r02 Agreed. Revised to S2-2401571. | Belen (Ericsson) asks question for clarification Huazhang (vivo) provides r01 and remove the UE capability Srinivas Garikipati (Nokia) provides further feedback on r01 Huazhang (vivo) provides r02 to reflect the wording alignment ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 9.25.2 | S2-2401571 | CR | Approval | 23.502 CR4696R1 (Rel-18, 'F'): PCF discovery for URSP rule provision in EPS | Vivo | Rel-18 | Revision of S2-2400629r02. Approved | Agreed | |
| 9.26.2 | - | - | - | System Enabler for Service Function Chaining (SFC) | - | - | Docs:=0 | - | |
| 9.27.2 | - | - | - | Extensions to the TSC Framework to support DetNet (DetNet) | - | - | Docs:=2 | - | |
| 9.27.2 | S2-2400892 | CR | Approval | 23.503 CR1171R3 (Rel-18, 'F'): Clarification on information transferred between TSCTSF and PCF for DetNet | CATT | Rel-18 | Revision of (noted) S2-2311695. r01 Agreed. Revised to S2-2401572. | Saubhagya (Nokia) proposes to move the CR text to a different paragraph Yuan Tao (CATT) provides r01. Saubhagya (Nokia) OK with r01 ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 9.27.2 | S2-2401572 | CR | Approval | 23.503 CR1171R4 (Rel-18, 'F'): Clarification on information transferred between TSCTSF and PCF for DetNet | CATT | Rel-18 | Revision of S2-2400892r01. Approved | Agreed | |
| 9.28.2 | - | - | - | Seamless UE context recovery (SUECR) | - | - | Docs:=0 | - | |
| 9.29 | - | - | - | Multiple location report for MT-LR Immediate Location Request for regulatory services (TEI18_MLR) | - | - | Docs:=0 | - | |
| 9.30 | - | - | - | Secondary DN Authentication and authorization in EPC IWK cases (TEI18_SDNAEPC) | - | - | Docs:=0 | - | |
| 9.31 | - | - | - | MBS support for V2X services (TEI18_MBS4V2X) | - | - | Docs:=0 | - | |
| 9.32 | - | - | - | Spending Limits for AM and UE Policies in the 5GC (TEI18_SLAMUP) | - | - | Docs:=6 | - | |
| 9.32 | S2-2400187 | CR | Approval | 23.503 CR1238 (Rel-18, 'F'): CHF discovery and selection, alignment with 23.502 | Ericsson | Rel-18 | Merged into S2-2401573 | Zhuoyi (China Telecom) suggests to merge to S2-2400384. Belen (Ericsson) is okay to merge into S2-2400384 ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 9.32 | S2-2400384 | CR | Approval | 23.503 CR1246 (Rel-18, 'F'): A fix for Spending Limits for AM and UE Policies in the 5GC | Oracle, Ericsson | Rel-18 | r02 Agreed. Revised to S2-2401573, merging S2-2400187 | Belen(ericsson) provides r01 Mirko (Huawei) comments. Uri (Oracle) replies to Mirko (Huawei) and provides S2-2400384r02 and S2-2400385r01. Mirko (Huawei) responds and is ok with r02. Wanqiang (Session Chair): please start a new email thread about 0385 handling and do not mix them together. Uri responds to Wanqiang (Session Chair) and Mirko (Huawei): a new email thread about 0385 is now opened. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 9.32 | S2-2401573 | CR | Approval | 23.503 CR1246R1 (Rel-18, 'F'): A fix for Spending Limits for AM and UE Policies in the 5GC | Oracle, Ericsson | Rel-18 | Revision of S2-2400384r02, merging S2-2400187. Approved | Agreed | |
| 9.32 | S2-2400385 | CR | Approval | 23.501 CR5229 (Rel-18, 'F'): Spending Limits for AM and UE Policies in the 5GC | Oracle, Ericsson | Rel-18 | r01 Agreed. Revised to S2-2401574. | Uri (Oracle) provides S2-2400385r01, and comments to Mirko (Huawei) and Belen (Ericsson). Uri (Oracle) fixes the CR/spec number in previous email title, provides S2-2400385r01, and comments to Mirko (Huawei) and Belen (Ericsson). ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 9.32 | S2-2401574 | CR | Approval | 23.501 CR5229R1 (Rel-18, 'F'): Spending Limits for AM and UE Policies in the 5GC | Oracle, Ericsson | Rel-18 | Revision of S2-2400385r01. Approved | Agreed | |
| 9.32 | S2-2400687 | CR | Approval | 23.503 CR1252 (Rel-18, 'F'): Corrections for spending limit information stored in UDR | Huawei, HiSilicon, Oracle | Rel-18 | Approved | Agreed | |
| 9.33 | - | - | - | Enhancement of application detection event exposure (TEI18_ADEE) | - | - | Docs:=0 | - | |
| 9.34 | - | - | - | General Support of IPv6 Prefix Delegation (TEI18_IPv6PD) | - | - | Docs:=0 | - | |
| 9.35 | - | - | - | New WID on Dynamically Changing AM Policies in the 5GC Phase 2 (TEI18_DCAMP_Ph2) | - | - | Docs:=0 | - | |
| 9.36 | - | - | - | Enhancement of NSAC for maximum number of UEs with at least one PDU session/PDN connection (eNSAC) | - | - | Docs:=3 | - | |
| 9.36 | S2-2400673 | CR | Approval | 23.502 CR4701 (Rel-18, 'F'): Clarification on the Handling of the UE number with at least one PDU Session under Hierarchical NSAC architecture | Nokia, Nokia Shanghai Bell, Samsung | Rel-18 | r01 Agreed. Revised to S2-2401775. | Fenqin (Huawei) provides r01 ==== Revisions Deadline ==== Fenqin (Huawei) accept only r01 ==== Final Comments Deadline ==== | Revised |
| 9.36 | S2-2401775 | CR | Approval | 23.502 CR4701R1 (Rel-18, 'F'): Clarification on the Handling of the UE number with at least one PDU Session under Hierarchical NSAC architecture | Nokia, Nokia Shanghai Bell, Samsung | Rel-18 | Revision of S2-2400673r01. Approved | Agreed | |
| 9.36 | S2-2401035 | CR | Approval | 23.501 CR5284 (Rel-18, 'F'): Clarifications on Option 2 NSAC for maximum number of UEs with at least one PDU SessionPDN Connection | Samsung, Nokia, Nokia Shanghai Bell | Rel-18 | Noted | George Foti (Ericsson) provides comments. Would like to postpone this CR. Option 2 is about not impacting existing SMFs and AMFs, and putting all aspects in NSACF. SO the rationale in the CR header is incorrect. Indeed there will be same requests going being sent to the NSACF for this feature. There is a clear misunderstanding of the option 2. Jinguo(ZTE) comments George (Ericsson) provides response Ashok (Samsung) replies Jinguo(ZTE) replies Ashok (Samsung) provides r01 based on the comment from Jinguo Fenqin (Huawei) comments Ashok (Samsung) agrees with Fenqin George (Ericsson) responds. Ashok (Samsung) replies to George (Ericsson) Jinguo(ZTE) is fine with r01 Ashok (Samsung) agree with Jinguo(ZTE) Ashok (Samsung) provides response to George (Ericsson) George (Ericsson) provides answer. It is. I cant make the case now in the 11th hour. ==== Revisions Deadline ==== George (Ericsson) proposes to NOTE the CR. This CR impacts the editors note in 23.502 that is yet to be addressed. ==== Final Comments Deadline ==== | Noted |
| 9.37 | - | - | - | Generic Rel-18 LSs | - | - | Docs:=0 | - | |
| 9.38 | - | - | - | Rel-18 CAT B/C alignment CR(s) due to the work led by other 3GPP Working Groups | - | - | Docs:=13 | - | |
| 9.38 | S2-2401148 | LS OUT | Approval | [DRAFT] Reply LS on PDU session capability exposure | China Mobile | Rel-18 | Revision of (withdrawn) S2-2313329. Response to S2-2400016. Postponed | Laurent (Nokia): provides r01 Hyesumg (Samsung) provide comments on r00/r01. Fenqin (Huawei) provide comments. Dan(China Mobile) suggest to postpond this LS Laurent (Nokia): let's postpone 0016 and 1148 as proposed by Dan Hyesung (Samsung) also thinks it's better to postpone. ==== Revisions Deadline ==== | Postponed |
| 9.38 | S2-2400016 | LS In | Action | LS from SA WG6: LS on PDU session capability exposure capability | SA WG6 (S6-233299) | Rel-19 | Revision of Postponed S2-2311974 from SA WG2#160. Response drafted in S2-2401148. Postponed | Postponed | |
| 9.38 | S2-2400015 | LS In | Action | LS from RAN WG3: Reply LS on MBS communication service | RAN WG3 (R3-235913) | Rel-18 | Revision of Postponed S2-2311968 from SA WG2#160. Response drafted in S2-2400142. Postponed | Hui (Huawei) proposes to note this LS reply. Thomas (Nokia) prefers to reply to the LS and if this is not agreeable in this meeting postpone this LS. Robbie (Ericsson) prefers to postpone this LS. Hui (Huawei) fine to postpone this LS. | Postponed |
| 9.38 | S2-2400143 | CR | Approval | 23.247 CR0346R2 (Rel-18, 'B'): QMC Support for MBS Multicast and Broadcast | Ericsson | Rel-18 | Revision of (postponed) S2-2313242. Postponed | Juan Zhang (Qualcomm) provides comment. Robbie (Ericsson) provides comments. Thomas (Nokia) suggest postponing this CR and instead asking RAN groups additional questions in the reply LS. Robbie (Ericsson) asks Thomas (Nokia). Thomas (Nokia).replies to Robbie Hui(Huawei) proposes to note this paper Robbie (Ericsson) replies to Hui(Huawei). Robbie (Ericsson) proposes to postpone this paper ==== Revisions Deadline ==== Hui (Huawei) fine to postpone this paper. | Postponed |
| 9.38 | S2-2400142 | LS OUT | Approval | [DRAFT] Reply LS on MBS communication Service | Ericsson | Rel-18 | Response to S2-2400015. Postponed | Thomas (Nokia) provides r01 and comments that LS depends on agreements of attached CRs Robbie (Ericsson) asks Thomas (Nokia). Thomas (Nokia).replied to Robbie. Robbie (Ericsson) replies to Thomas (Nokia). Hui (Huawei) proposes to note the LS. Thomas (Nokia) provides r02 and replies to Robbie Robbie (Ericsson) replies to Thomas (Nokia) and asks to postpone the Reply LS. ==== Revisions Deadline ==== Hui (Huawei) fine to postpone this LS. | Postponed |
| 9.38 | S2-2400692 | CR | Approval | 23.501 CR4991R2 (Rel-17, 'B'): Support of QMC configuration information | Qualcomm Incorporated, Ericsson | Rel-17 | Revision of (unhandled) S2-2312450. CC#4: Postponed | Hui (Huawei) proposes to note this paper. Juan Zhang (Qualcomm) askes Hui Ni (Huawei) to provide technical reason with your objection Robbie (Ericsson) supports Juan Zhang (Qualcomm) and replies to Hui (Huawei). ==== Revisions Deadline ==== Hui (Huawei) proposes to postpone this paper. Juan Zhang (Qualcomm) can not agree with Hui (Huawei)'s comments and askes to discuss in CC#3 or CC#4. ==== Final Comments Deadline ==== | Postponed |
| 9.38 | S2-2400696 | CR | Approval | 23.501 CR4992R2 (Rel-18, 'A'): Support of QMC configuration information | Qualcomm Incorporated, Ericsson | Rel-18 | Revision of (unhandled) S2-2312451. CC#4: Postponed | Thomas (Nokia) comments that this mirror CR can only be agreed if the CR in S2-2400692 is agreed. Dario (Sessio Chair) thanks Thomas. This depends on the Cat F CR. | Postponed |
| 9.38 | S2-2400709 | CR | Approval | 23.502 CR4495R2 (Rel-17, 'B'): Support of QMC configuration information | Qualcomm Incorporated, Ericsson | Rel-17 | Revision of (unhandled) S2-2313012. CC#4: Postponed | Hui (Huawei) proposes to note the paper. Juan Zhang (Qualcomm) askes Hui Ni (Huawei) to provide technical reason with your objection Robbie (Ericsson) supports Juan Zhang (Qualcomm). ==== Revisions Deadline ==== Hui (Huawei) proposes to postpone this paper. Juan Zhang (Qualcomm) can not agree with Hui (Huawei)'s comments and askes to discuss in CC#3 or CC#4. ==== Final Comments Deadline ==== | Postponed |
| 9.38 | S2-2400712 | CR | Approval | 23.502 CR4499R2 (Rel-18, 'A'): Support of QMC configuration information | Qualcomm Incorporated, Ericsson | Rel-18 | Revision of (unhandled) S2-2313015. CC#4: Postponed | Hui (Huawei) proposes to note the paper. Juan Zhang (Qualcomm) askes Hui Ni (Huawei) to provide technical reason with your objection Robbie (Ericsson) supports Juan Zhang (Qualcomm). ==== Revisions Deadline ==== Hui (Huawei) proposes to postpone this paper. Juan Zhang (Qualcomm) can not agree with Hui (Huawei)'s comments and askes to discuss in CC#3 or CC#4. ==== Final Comments Deadline ==== | Postponed |
| 9.38 | S2-2400939 | CR | Approval | 23.501 CR5273 (Rel-18, 'B'): Update to Support Network Controlled Repeater | ZTE | Rel-18 | r04 Agreed. Revised to S2-2401464. | Alessio(Nokia) provides r01 Haris(Qualcomm) provides r02 Hao (ZTE) comments on revisions. Alessio(nokia) provides r03 Qian (Ericsson) provides r04 Nokia OK with r04 ==== Revisions Deadline ==== Hao (ZTE) is fine with r04. ==== Final Comments Deadline ==== | Revised |
| 9.38 | S2-2401464 | CR | Approval | 23.501 CR5273R1 (Rel-18, 'B'): Update to Support Network Controlled Repeater | ZTE | Rel-18 | Revision of S2-2400939r04. Approved | Agreed | |
| 9.38 | S2-2400940 | CR | Approval | 23.502 CR4716 (Rel-18, 'B'): Update to Support Network Controlled Repeater | ZTE | Rel-18 | r01 Agreed. Revised to S2-2401465. | Haris(Qualcomm) highlights that WI should also include ',TEI18' and UE context modification procedure update is missing Hao (ZTE) responds. Hao (ZTE) provides r01 with update on cover sheet adding WI code TEI18. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 9.38 | S2-2401465 | CR | Approval | 23.502 CR4716R1 (Rel-18, 'B'): Update to Support Network Controlled Repeater | ZTE | Rel-18 | Revision of S2-2400940r01. Approved | Agreed | |
| 19 | - | - | - | Rel-19 SIDs and WIDs | - | - | Docs:=0 | - | |
| 19.1 | - | - | - | Study on Integration of satellite components in the 5G architecture Phase III (FS_5GSAT_ARCH_Ph3) | - | - | Docs:=89 | - | |
| 19.1 | - | - | - | LS in/out | - | - | Docs:=8 | - | |
| 19.1 | S2-2400036 | LS In | Action | LS from TSG RAN: LS on Robust Notification Alert for NTN-NR Rel-19 | TSG RAN (RP-234075) | Rel-19 | Responses drafted in S2-2400159, S2-2400392, S2-2400575, S2-2400792, S2-2401019, S2-2401312. Postponed | Chunhui(NEC) proposes to postpone this topic to SA2#161 meeting. Jinguo(ZTE) comments Jean Yves(Thales) proposes also to postpone this topic to SA2#161 meeting. Hanyu Ding (HONOR) proposes to postpone this topic to SA2#161 meeting. | Postponed |
| 19.1 | S2-2400159 | LS OUT | Approval | [DRAFT] Reply LS on Robust Notification Alert for NTN-NR Rel-19 | Nokia, Nokia Shanghai Bell | Rel-19 | Response to S2-2400036. Postponed | Guillaume (MediaTek Inc.) comments. Chunhui(NEC) proposes to postpone this topic to SA2#161 meeting. Jean Yves(Thales) proposes also to postpone this topic to SA2#161 meeting. Yuxin(Xiaomi) comments. Steve (Huawei) is fine to postpone. ==== Revisions Deadline ==== | Postponed |
| 19.1 | S2-2400391 | DISCUSSION | Discussion | On Robust Notification Alert for NTN-NR. | MediaTek Inc. | Noted | Noted | ||
| 19.1 | S2-2400392 | LS OUT | Approval | [DRAFT] Reply LS on Robust Notification Alert for NTN-NR Rel-19 | MediaTek Inc. | Response to S2-2400036. Postponed | Chunhui(NEC) proposes to postpone this topic to SA2#161 meeting. Amy (vivo) provides comments. Jean Yves(Thales) proposes also to postpone this topic to SA2#161 meeting. Steve (Huawei) is fine to postpone. Chris (Vodafone) is OK to postpone. However, the lack of GPS coverage should also be considered. ==== Revisions Deadline ==== | Postponed | |
| 19.1 | S2-2400575 | LS OUT | Approval | [DRAFT] Reply LS on Robust Notification Alert | OPPO | Rel-19 | Response to S2-2400036. Postponed | Guillaume (MediaTek Inc.) provides comments. Peng (OPPO) provides comments Chunhui(NEC) proposes to postpone this topic to SA2#161 meeting. Jean Yves(Thales) proposes also to postpone this topic to SA2#161 meeting. Yuxin(Xiaomi) comments. Steve (Huawei) is fine to postpone. ==== Revisions Deadline ==== | Postponed |
| 19.1 | S2-2400792 | LS OUT | Approval | [DRAFT] Reply LS to RAN and SA WG1 on Robust notification | vivo | Rel-19 | Response to S2-2400036. Postponed | Guillaume (MediaTek Inc.) provides comments. Chunhui(NEC) proposes to postpone this topic to SA2#161 meeting. Jean Yves(Thales) proposes also to postpone this topic to SA2#161 meeting. Steve (Huawei) is fine to postpone. ==== Revisions Deadline ==== | Postponed |
| 19.1 | S2-2401019 | LS OUT | Approval | [DRAFT] Reply LS on Robust Notification Alert for NTN-NR Rel-19 | Xiaomi | Rel-19 | Response to S2-2400036. Postponed | Hucheng (CATT) supports Lalith's comments. Lalith (Samsung) provides comments Guillaume (MediaTek Inc.) provides comments Saubhagya (Nokia) agrees to CATT and Samsung comments Chunhui(NEC) proposes to postpone this topic to SA2#161 meeting. Jean Yves(Thales) proposes also to postpone this topic to SA2#161 meeting. Stefan (Ericsson) comments Yuxin (Xiaomi) replies Steve (Huawei) is fine to postpone. ==== Revisions Deadline ==== | Postponed |
| 19.1 | S2-2401312 | LS OUT | Approval | [DRAFT] Reply LS on Robust Notification Alert for NTN-NR Rel-19 | Samsung | Rel-19 | Response to S2-2400036. Postponed | Guillaume (MediaTek Inc.) provides comments. Chunhui(NEC) proposes to postpone this topic to SA2#161 meeting. jean yves(Thales) comments. Jean Yves(Thales) proposes also to postpone this topic to SA2#161 meeting. Yuxin(Xiaomi) comments. Lalith(Samsung) comments that if we postpone to next meeting this topic should not be discussed in 5GSAT_ph3 agenda Steve (Huawei) is fine to postpone. ==== Revisions Deadline ==== | Postponed |
| 19.1 | - | - | - | KI#1 | - | - | Docs:=22 | - | |
| 19.1 | S2-2400354 | P-CR | Approval | 23.700-29: KI#1: New Solution for handling of S1/NG when satellite leaves an area served by a CN. | Ericsson | Rel-19 | r04 Agreed. Revised to S2-2401776. | Amy (vivo) provides comments Heng (China Telecom) provides comments Saubhagya (Nokia) provide comments. Steve (Huawei) comments. Stefan (Ericsson) replies Haris(Qualcomm) comments Chris (Vodafone) supports the concept, but would like a 'step 0' for hand over/redirection of connected mode UEs to be added. SA2 need to place the requirement on RAN 3, as RAN 3 do not deal with CN aspects. Haris(Qualcomm) provides r01 Saubhagya (Nokia) asks questions on NGAP disconnect Stefan (Ericsson) replies to Saubhagya and provides r02 Saubhagya (Nokia) further comments Hucheng (CATT) asks questions for clarification. Stefan (Ericsson) replies and provides r03 Saso (Intel) provides r04 ==== Revisions Deadline ==== Stefan (Ericsson) OK with r04 ==== Final Comments Deadline ==== | Revised |
| 19.1 | S2-2401776 | P-CR | Approval | 23.700-29: KI#1: New Solution for handling of S1/NG when satellite leaves an area served by a CN. | Ericsson | Rel-19 | Revision of S2-2400354r04. Approved | Approved | |
| 19.1 | S2-2400565 | P-CR | Approval | 23.700-29: KI#1, New Sol: Support of feeder link switchover for regenerative eNB payload. | OPPO | Rel-19 | r04 Agreed. Revised to S2-2401777, merging S2-2400566 | Hucheng (CATT) comments. Saubhagya (Nokia) provide comments. Amy (vivo) provide comments. Steve (Huawei) comments. Stefan (Ericsson) comments Haris(Qualcomm) comments Jinsook (DISH network) comments Peng (OPPO) replies to Jinsook (DISH network) comments. Peng (OPPO) replies to Haris (Qualcomm) comments. Peng (OPPO) replies to Stefan (Ericsson) comments. Peng (OPPO) replies to Steve (Huawei) comments. Peng (OPPO) replies to Amy(vivo) comments. Peng (OPPO) replies to Saubhagya (Nokia) comments. Peng (OPPO) replies to Hucheng (CATT) comments. Hyunsook (LGE) comments Yuxin (Xiaomi) comments. Jean Yves (Thales) comments. Peng (OPPO) replies to Hyunsook (LGE) comments. Peng (OPPO) replies Yuxin (Xiaomi) comments. Peng (OPPO) replies to Jean Yves (Thales) comments. Chris (Vodafone) suggests adding/referencing a satellite scenario picture; and he prefers a solution with no UE impact. Haris(Qualcomm) provides r01 Stefan (Ericsson) replies to Peng Saubhagya (Nokia) answers to Peng (OPPO) Peng (OPPO) answers Saubhagya (Nokia) questions on r02, and provides r03 Saubhagya (Nokia) seek clarification on r02 Peng (OPPO) provides r02 Peng (OPPO) replies to Chris (Vodafone) Haris(Qualcomm) comments on new text in r02 and prefers r01 Steve (Huawei) comments on UE impacts Steve (Huawei) comments on the title of the solution Haris(Qualcomm) comments that in r01 I did not try to remove UE impacts but added EN to justify on their need Stefan (Ericsson) comments on using new MME Peng (OPPO) replies comments and provides r04 Peng (OPPO) replies Stefan's comments and provides r04 ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 19.1 | S2-2401777 | P-CR | Approval | 23.700-29: KI#1, New Sol: Support of feeder link switchover for regenerative eNB payload. | OPPO | Rel-19 | Revision of S2-2400565r04, merging S2-2400566. Approved | Approved | |
| 19.1 | S2-2400566 | P-CR | Approval | 23.700-29: KI#1, New Sol: Support of Feeder Link Switchover for regenerative gNB payload in 5GS. | OPPO | Rel-19 | Merged into S2-2401777 | Amy (vivo) suggests to merge this into 2400565. Jean Yves (Thales) ok to merge this into 2400565 (but the author to decide...) ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 19.1 | S2-2400573 | P-CR | Approval | 23.700-29: KI#1, New Sol: Load re-balancing for feeder link switchover. | OPPO | Rel-19 | r02 Agreed. Revised to S2-2401778. | Amy (vivo) provides comments. Steve (Huawei) comments. Peng (OPPO) replies to address comments. Steve (Huawei) on the UE need to know. Chris (Vodafone) suggests adding a picture; describing the RAN process; and then problems may become clearer. Peng (OPPO) answers Steve (Huawei) questions Peng (OPPO) replies to Chris (Vodafone) comments. ==== Revisions Deadline ==== Steve (Huawei) there have been several unannounced revisions. objects to r00, r01 (unannounced), could live with r02 (unannounced, but even then I am not a big fan of it) Haris(Qualcomm) can live with r02 but step 1 in Figure 6.x.2.1-1 incorrectly overextends to UE which is incorrect, it should stop in eNB Peng (OPPO) would like to announce r01 and r02, which was inadvertently omitted within the previous tags. Peng (OPPO) replies to Haris (Qualcomm). ==== Final Comments Deadline ==== | Revised |
| 19.1 | S2-2401778 | P-CR | Approval | 23.700-29: KI#1, New Sol: Load re-balancing for feeder link switchover. | OPPO | Rel-19 | Revision of S2-2400573r02. Approved | Approved | |
| 19.1 | S2-2400706 | P-CR | Approval | 23.700-29: New Solution for Key Issue #1: QoS/Policy handing. | China Telecom | Rel-19 | r03 Agreed. Revised to S2-2401779. | Heng(China Telecom) provides revision to merge 0793(vivo) Hucheng(CATT) comments Amy (vivo) provides r03 and answers to Hucheng (CATT). Steve (Huawei) comments. Stefan (Ericsson) comments Heng (China Telecom) reply to Stefan Saubhagya (Nokia) provide comments Heng(China Telecom) replies to Saubhagya (Nokia) Hyunsook (LGE) asks to clarify Steve's comment Steve (Huawei) comments on RAT Type Amy (vivo) asks Stefan (Ericsson) for clarifications regarding the RAN determination of CN PDB Amy (vivo) replies to Steve (Huawei) on backhaul type Chris (Vodafone) comments that regenerative does not really change the latency from that of transparent architecture. Stefan (Ericsson) replies to Amy Haris(Qualcomm) comments that the solution may lead to a lot of spec impacts Heng (China Telecom) comment Saubhagya (Nokia) provide comments on inputs from Qualcomm ==== Revisions Deadline ==== Heng (China Telecom) is ok with r03 ==== Final Comments Deadline ==== | Revised |
| 19.1 | S2-2401779 | P-CR | Approval | 23.700-29: New Solution for Key Issue #1: QoS/Policy handing. | China Telecom, vivo | Rel-19 | Revision of S2-2400706r03. Approved | Approved | |
| 19.1 | S2-2400707 | P-CR | Approval | 23.700-29: New Solution for Key Issue #1:Feeder link switchover. | China Telecom | Rel-19 | r05 Agreed. Revised to S2-2401780. | Amy (vivo) provides comments. Heng (China Telecom) reply to Amy and provides r01. Haris(Qualcomm) comments Heng(China Telecom) reply to Haris and provides r02. Hyunsook (LGE) asks about buffering aspects. Heng (China Telecom) reply to Hyunsook. Jean Yves (Thales) comments and propose to note the doc Heng (China Telecom) replies to Jean Yves and think this doc is useful Chris (Vodafone) suggests renaming as e.g. Hard feeder link switch without AMF change Stefan (Ericsson) comments Heng(China Telecom) comment Heng (China Telecom) reply and provides r03 Saubhagya (Nokia) provide comments Steve (Huawei) comments on the title of the solution Heng (China Telecom) reply to Steve and provide r04 Haris(Qualcomm) provides r05 Heng(China Telecom) is ok with r05 ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 19.1 | S2-2401780 | P-CR | Approval | 23.700-29: New Solution for Key Issue #1:Feeder link switchover with DL data continuity. | China Telecom | Rel-19 | Revision of S2-2400707r05. Approved | Approved | |
| 19.1 | S2-2400708 | P-CR | Approval | 23.700-29: KI #1, New Sol: Regenerative architecture. | NEC | Rel-19 | r03 + changes Agreed. Revised to S2-2401781. | Hucheng (CATT) comments. Saubhagya (Nokia) provide comments. Kundan (NEC) responds to Hucheng(CATT). Amy (vivo) proposes to merge this into S2-2400794. Amy (vivo) responds to Amy. Kundan (NEC) responds to the Saubhagya (Nokia). Saubhagya (Nokia) revert to Kundan (NEC). Steve (Huawei) comments. Stefan (Ericsson) comments Kundan (NEC) responds to Saubhagya (Nokia) Kundan (NEC) acknowledges comments from Steve and Stefan. Chris (Vodafone) comments that the UE context handling is not clear.. Kundan (NEC) provides r01 addressing comments of Steven, Saubhagya and Stefan. Kundan(NEC) responds to Chris(Vodafone). Chris (Vodafone) replies to NEC. Steve (Huawei) comments on the title of the solution and resume Kundan(NEC) provides r02. Haris(Qualcomm) comments on r02 Kundan(NEC) responds to Haris (Qualcomm). Saso (Intel) comments. Kundan(NEC) provides r03. Steve (Huawei) comments on same time ==== Revisions Deadline ==== Kundan(NEC) responds to Saso. Kundan(NEC) responds to Steve Steve (Huawei) Editor's note missing? Steve (Huawei) prefers to note. Kundan(NEC) request Steve to consider this EN as place holder for his comments. His comments comes after the deadline and I couldn't add proper ENs. Kundan(NEC) proposes following EN on top of r03 to address Steve comment. Hope this will be fine to Steve. EN: The detailed step of resume procedure is FFS. Kundan(NEC) proposes following EN on top of r03 to address Steve comment. Hope this will be fine to Steve. EN: The detailed step of resume procedure is FFS. Steve (Huawei) That was the sort of EN that is missing, that would be ok. ==== Final Comments Deadline ==== | Revised |
| 19.1 | S2-2401781 | P-CR | Approval | 23.700-29: KI #1, New Sol: Regenerative architecture. | NEC | Rel-19 | Revision of S2-2400708r03 + changes. Approved | Approved | |
| 19.1 | S2-2400794 | P-CR | Approval | 23.700-29: New Solution on Context Management on AMF when RAN is onboard. | Vivo | Rel-19 | r04 Agreed. Revised to S2-2401782. | Steve (Huawei) asks questions and comments Saubhagya (Nokia) comments. Haris(Qualcomm) comments Stefan (Ericsson) comments Lalith (Samsung) seeks clarification. Amy (vivo) provides r01 and answers to Steve (HW), Saubhagya (Nokia), Haris (Qualcomm), Stefan (Ericsson) and Lalith (Samsung). Jaewoo (LGE) provides comments. Kundan (NEC) seeks clarifications. Saubhagya (Nokia) shares concerns Stefan (Ericsson) provides comments Saubhagya (Nokia) replies to Amy (vivo) Amy (vivo) replies to Stefan (Ericsson) and Saubhagya (Nokia) Peng (OPPO) asks for clarification. Amy (vivo) replies to Saubhagya (Nokia) Saubhagya (Nokia) answers to Amy (vivo) Amy (vivo) provides r02, and replies to Kundan (NEC) and Jaewoo (LGE) specially Kundan(NEC) is fine with r02. Steve (Huawei) comments in stuff like merging and others. Stefan (Ericsson) comments on r02 Jaewoo (LGE) is fine with r02. Amy (vivo) provides r03, replies to Kundan (NEC), Steve (Huawei), Stefan (Ericsson), and Jaewoo (LGE), Stefan (Ericsson) replies to Amy Amy (vivo) provides r04 replies to Stefan (Ericsson) ==== Revisions Deadline ==== Jean Yves (Thales) ok with r04 ==== Final Comments Deadline ==== | Revised |
| 19.1 | S2-2401782 | P-CR | Approval | 23.700-29: New Solution on Handling Awareness of Supported TAIs when RAN is onboard. | Vivo | Rel-19 | Revision of S2-2400794r04. Approved | Approved | |
| 19.1 | S2-2400923 | P-CR | Approval | 23.700-29: Solution for KI#1: Support of Regenerative-based satellite access. | CATT | Rel-19 | r02 Agreed. Revised to S2-2401837. | Kundan (NEC) asks questions. Steve (Huawei) comments. Hucheng(CATT) replies to Kundan (NEC). Saubhagya (Nokia) provide comments. Stefan (Ericsson) comments Peng (OPPO) asks for clarification. Hucheng (CATT) replies to all comments inline Stefan (Ericsson) replies to Hucheng Xiaoxue (CATT) provides the revision r01. Saubhagya (Nokia) repeating comments as email crossed earlier. Steve (Huawei) comments, still not really clear after the updates in r01 Hucheng(CATT) replies to all comments inline and provides r02 Steve (Huawei) comments on errors. ==== Revisions Deadline ==== Xiaoxue (CATT) replies to Steve. Steve (Huawei) has concerns on all revisions. Hucheng (CATT) replies to Steve (Huawei). ==== Final Comments Deadline ==== | Revised |
| 19.1 | S2-2401837 | P-CR | Approval | 23.700-29: Solution for KI#1: Support of Regenerative-based satellite access. | CATT | Rel-19 | Revision of S2-2400923r02. Approved | Approved | |
| 19.1 | S2-2401020 | P-CR | Approval | 23.700-29: KI #1, New Sol: Support of Regenerative-based satellite access. | Xiaomi | Rel-19 | r05 Agreed. Revised to S2-2401783. | Steve (Huawei) asks a questions Stefan (Ericsson) comments Yuxin (Xiaomi) replies to Stefan (Ericsson) and Steve (Huawei) Hyunsook (LGE) asks some clarifications Stefan (Ericsson) provides comments Saubhagya (Nokia) provide comments Peng (OPPO) provides comments. Yuxin (Xiaomi) replies to comments from Stefan(Ericsson) Yuxin (Xiaomi) replies to Peng (OPPO). Yuxin (Xiaomi) replies to Saubhagya(Nokia) Stefan (Ericsson) replies to Yuxin Chris (Vodafone) asks how this supports the 3rd and 4th scenarios in the TR annex. Peng (OPPO) to confirm his understanding of the solution. Yuxin (Xiaomi) replies and provides r03 Stefan (Ericsson) comments on r03 Yuxin (Xiaomi) provide r04 Steve (Huawei) comments Proxy RAN / RAN Agent - what does it mean to SA2? Saso (Intel) seeks clarification Yuxin (Xiaomi) replies to Steve Yuxin (Xiaomi) replies to Saso Saso (Intel) provides r05 Yuxin (Xiaomi) is OK with r05 ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 19.1 | S2-2401783 | P-CR | Approval | 23.700-29: KI #1, New Sol: Support of Regenerative-based satellite access. | Xiaomi | Rel-19 | Revision of S2-2401020r05. Approved | Approved | |
| 19.1 | S2-2401220 | P-CR | Approval | 23.700-29: KI#1, New Sol: Architecture for regenerative-based satellite access with IWF on the S1 or N2/N3 interface. | Intel | Rel-19 | r06 Agreed. Revised to S2-2401784. | Hucheng (CATT) comments. Heng (China Telecom) comments. Saubhagya (Nokia) provide comments. Steve (Huawei) comments. Saso (Intel) provides r01. Haris(Qualcomm) provides r02 Saso (Intel) is OK with r02; provides editorial fixes in r03. Hucheng (CATT) comments and questions whether this solution needs to be documented in SA2 TR. Amy (vivo) asks for clarification about the impacts of paging Yuxin(Xiaomi) comments Stefan (Ericsson) provides comments Saso (Intel) provides r04 Saso (Intel) replies to Hucheng that the solution needs to be documented. Stefan (Ericsson) replies to Saso Haris(Qualcomm) responds Saso (Intel) replies to Stefan Jean Yves (Thales) comments Chris (Vodafone) comments and requests some procedures for national-sovereignty respecting solutions to handle the 3rd and 4th scenarios in the TR's annex. Steve (Huawei) comments on gNB onboard. Saso (Intel) provides r05; replies to Chris. Chris (Vodafone) replies to Saso (Intel). Perhaps change Note 2 to 'support for scenarios 3 and 4 from the annex A is FFS'? Saso (Intel) provides r06 implementing Chris's proposal to change Note 2 to 'support for scenarios 3 and 4 from the annex A is FFS' Steve (Huawei) comments IWF function - what does it mean to SA2? Saso (Intel) replies to Steve. ==== Revisions Deadline ==== Jean Yves (Thales) OK for r06 Robert (OQ Technology) is Ok with R06. ==== Final Comments Deadline ==== | Revised |
| 19.1 | S2-2401784 | P-CR | Approval | 23.700-29: KI#1, New Sol: Architecture for regenerative-based satellite access with IWF on the S1 or N2/N3 interface. | Intel | Rel-19 | Revision of S2-2401220r06. Approved | Approved | |
| 19.1 | S2-2401304 | P-CR | Approval | 23.700-29: [KI#1] Solution X: Satellite Access Control . | Rel-19 | Noted | Amy (vivo) provides comments. Saubhagya (Nokia) comments. Ellen (Google) provides feedback to Saubhagya. Ellen (Google) provides feedback to Amy (Vivo) Jaewoo (LGE) provides comments. Saubhagya (Nokia) provide comments Lalith (Samsung) provides r02 Haris(Qualcomm) proposes to note since out of scope of the SID objectives Steve (Huawei) should be noted, not in scope. Saubhagya (Nokia) propose to note the paper Ellen (Google) provides r03 <https://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_160AHE_Electronic_2024-01/INBOX/Revisions/S2-2401304r03.zip> and thanks Lalith for acknowledge the problem statement in this paper and replied to Harris/Steven/Saubhagya Ellen (Google) provides feedback to Jasewoo Chris (Vodafone) sees this as more for Dual Steer than for this SID. So OK to Note this here. Stefan (Ericsson) also prefers to note Kundan(NEC) is fine with r03. Not all applications are allowed in S&F mode i.e. when the satellite supports S&F only. ==== Revisions Deadline ==== Steve (Huawei) objects to all revisions. Haris(Qualcomm) objects to all revisions since the solution is out of scope of the SI objectives ==== Final Comments Deadline ==== | Noted | |
| 19.1 | - | - | - | KI#2 | - | - | Docs:=40 | - | |
| 19.1 | S2-2400088 | P-CR | Approval | 23.700-29: 5GC Enhancements to Support of Store and Forward Satellite operation. | China Mobile | Rel-19 | r02 Agreed. Revised to S2-2401785. | Jean Yves (Thales) comments Saubhagya (Nokia) comments. Boren (OPPO) comments Lalith (Samsung) comments Steve (Huawei) comments. Stefan (Ericsson) comments Stephen (Qualcomm) comments Jinsook (DISH Network) seeking for clarification the needs of '5GC support for the S&F operation' Dan(China Mobile)reply Dan (China Mobile) reply. Dan(China Mobile) reply Dan (China Moble) respond Dan(China Mobile) provide r01 to reflect the comment Yuxin(Xiaomi) comments Steve (Huawei) comments on r01 Steve (Huawei) comments on the parameters Jean Yves (Thales) comments on 5GC for S&F for clarifications Jinsook (DISH Network) thanks for your clarification Jean Yves Steve (Huawei) to correct the email subject line. Kundan(NEC) comments that option 2 seems a better solution in this pCR but procedure part is missing. Jean Yves (Thales) answers to Dan. Steve (Huawei) thanks for the clarification Dan (China Mobile)reply. Dan (China Mobile) provide r02 Yuxin (Xiaomi) repeat comments . Yuxin (Xiaomi) confirms to Dan the reply is received, thanks . Dan(China Mobile) reply to Yuxin ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 19.1 | S2-2401785 | P-CR | Approval | 23.700-29: Enhancement of registration and PDU session establishment to support on-board S&F. | China Mobile | Rel-19 | Revision of S2-2400088r02. Approved | Approved | |
| 19.1 | S2-2400317 | P-CR | Approval | 23.700-29: KI #2: New Sol: MME Split Architecture for S&F. | Nokia, Nokia Shanghai Bell | Rel-19 | r05 + changes Agreed. Revised to S2-2401786, merging S2-2400341 and S2-2400343 | Stephen (Qualcomm) comments Yuxin (Xiaomi) comments Boren (OPPO) comments. Saubhagya (Nokia) provides r01. Amy (vivo) agrees with Hucheng (CATT) and proposes to merge S2-2400341, S2-2400466 into this to offer us a whole solution regarding the idea of MME split. Steve (Huawei) comments. Saubhagya (Nokia) answers to Amy (vivo) and provide some comments Kundan (NEC) provides comments. Saubhagya (Nokia) provide answers to NEC Steve (Huawei) comments on relationships Saubhagya (Nokia) fixed the relationship by merging 0343 & 0341 to 0317. Saubhagya (Nokia) addressed comments from Kundan (NEC) provided r03 Steve (Huawei) comments on the merge version. Kundan(NEC) responds to Lalith (Samsung). Lalith(Samsung) comments. Saubhagya (Nokia) agrees to comment from Lalith (Samsung) Lalith (Samsung) comments on timer part Saubhagya (Nokia) addressed comments from Kundan(NEC) provided r05 Kundan(NEC) provides comment. Saubhagya (Nokia) addressed comments from Steve (Huawei) provided r04 Lalith (Samsung) comments. Kundan(NEC) disagree with Saubhagya. How can a UE distinguish a geo stationary satellite and S&F satellite. Do we have any distinction now between these two modes? For the geo stationary satellite no need to adjust time. It is already there. Saubhagya (Nokia) provide comments Kundan (NEC) responds to Saubhagya. Steve (Huawei) comments on timers ==== Revisions Deadline ==== Lalith (Samsung) requests to co-sign Jean Yves (Thales) OK with r05 Robert (OQ Technology) Ok with r05. ==== Final Comments Deadline ==== | Revised |
| 19.1 | S2-2401786 | P-CR | Approval | 23.700-29: KI #2: New Sol: Control plane architecture and procedure for S&F. | Nokia, Nokia Shanghai Bell, Samsung | Rel-19 | Revision of S2-2400317r05 + changes, merging S2-2400341 and S2-2400343. Approved | Approved | |
| 19.1 | S2-2400341 | P-CR | Approval | 23.700-29: KI #2: New Sol: Store & Forward operation for Mobile Originated Data Transport in Control Plane CIoT EPS Optimisation. | Nokia, Nokia Shanghai Bell | Rel-19 | Merged into S2-2401786 | Stephen (Qualcomm) comments Saso (Intel) comments Steve (Huawei) comments. Saubhagya (Nokia) answers questions from QC, Intel and Huawei; provides r02 Steve (Huawei) comments in revision (whatever number it is..) Jean Yves (Thales) comments and request clarifications on the link with S2-2400317 Saubhagya (Nokia) provides clarification Amy (vivo) agrees with Jean Yves and looking forward to a merged revision, and provides suggestions on this solution Saubhagya (Nokia) 0341 is merged into 0317 ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 19.1 | S2-2400342 | P-CR | Approval | 23.700-29: KI #2: New Sol: UE Reachability estimator in S&F scenario. | Nokia, Nokia Shanghai Bell | Rel-19 | r02 Agreed. Revised to S2-2401787. | Stephen (Qualcomm) comments Saubhagya (Nokia) answers to comments and provides r01. Hucheng (CATT) comments. Saubhagya (Nokia) responds to CATT comments. Hucheng (CATT) replies to Saubhagya (Nokia). Saso (Intel) comments Jean Yves (Thales) comment and agrees on the need to try to merges solutions with same architectural assumptions Steve (Huawei) comments on reachability modes Saubhagya (Nokia) answers to Huawei and Intel and provides some generic comments. Saubhagya (Nokia) provide answers on reachability mode. jean Yves (Thales) comments Steve (Huawei) comments on parallels with Rel-18. jean yves (Huawei) comments jean yves (Thales) comments (again) Amy (vivo) provides comments Hucheng (CATT) replies to the question from the author (Nokia). Saubhagya (Nokia) answers to Amy (vivo) and provides r02. ==== Revisions Deadline ==== Jean Yves (Thales) OK with r02. ==== Final Comments Deadline ==== | Revised |
| 19.1 | S2-2401787 | P-CR | Approval | 23.700-29: KI #2: New Sol: UE Reachability estimator in S&F scenario. | Nokia, Nokia Shanghai Bell | Rel-19 | Revision of S2-2400342r02. Approved | Approved | |
| 19.1 | S2-2400343 | P-CR | Approval | 23.700-29: KI #2: New Sol: Attach Procedure in S&F scenario. | Nokia, Nokia Shanghai Bell | Rel-19 | Merged into S2-2401786 | Saubhagya (Nokia) provides r01. Stephen (Qualcomm) comments Saso (Intel) comments. Saubhagya (Nokia) agrees to Intel and provides r02 Kundan(NEC) provides comments. Saubhagya (Nokia) replies to NEC Saubhagya (Nokia) 0343 is merged to 0317, provides 0317 r02 here for reference Kundan (NEC) replies to Saubhagya (Nokia) Amy (vivo) proposes merging 1313 and 0317/0342/0343 Saubhagya (Nokia) refuse to merge and provides reason Lalith(Samsung) agrees with Saubhagya (Nokia) the solutions in 1313 and 0317/0342/0343 are different. Amy (vivo) is ok to keep them separately as 0343 assumes MME-NT maintains no UE context. Steve (Huawei) comments on (co)existence Jean Yves (Thales) comments also on (co)existence ==== Revisions Deadline ==== Lalith (Samsung) comments this tdoc should be marked merged to S2-2400317. Author please confirm Saubhagya (Nokia) confirms the S2-2400343 is merged into S2-2400317 ==== Final Comments Deadline ==== | Merged |
| 19.1 | S2-2400364 | P-CR | Approval | 23.700-29: KI#2, New Sol: Support of Store and Forward Satellite Operation via User Plane Buffering. | Tencent, Tencent Cloud | Rel-19 | Noted | Jaewoo (LGE) replies to Lei (Tencent). Lei(Tencent) provide comments. Jaewoo (LGE) comments. Saubhagya (Nokia) provide comments. Lei(Tencent) replies to Saubhagya (Nokia) and Jaewoo (LGE) and promise to provide a revsion to clarify NF location within Tuesday. Saso (Intel) proposes to note the document. Lalith(Samsung) comments. Steve (Huawei) comments. Jean Yves (Thales) requires explanations in a new revision. Stephen (Qualcomm) comments Lei(Tencent) provides r01 to merge part of S2-2400365 and propose to only focus on this thread. Also provide response and clarifications. Steve (Huawei) this does not address S&F Lei(Tencent) provides response to Steve (Huawei). Stefan (Ericsson) provides comments and questions Lei(Tencent) provides reply and also r02 to address Steve (Huawei) comments. Lei(Tencent) provides clarifications to Stefan (Ericsson) and also reflect in a new revision r02. Steve (Huawei) still lacks detail Lei(Tencent) provides comments and r03 with ENs. Jean Yves (Thales) asks question ==== Revisions Deadline ==== Lei (Tencent) provide response to Jean Yves (Thales) 's question and also add two additional ENs Lei (Tencent) provides comments and questions the correctness of comments from Stephen(Qualcomm) Stephen (Qualcomm) also prefers to note this Wanqiang (Session Chair): No new revisions will be accepted (except for LS out) after revision deadline. Please give a clear text change on top of r03 and make sure everybody will be ok with the additional change. Lei(Tencent) provide response to Wanqiang (Session Chair) confirms 'r03 + adding two ENs: Editor's Note: Whether to use new NF or reuse existing NF is FFS Editor's Note: How to detect feeder link availability is FFS ' Steve (Huawei) objects to all revisions ==== Final Comments Deadline ==== | Noted |
| 19.1 | S2-2400365 | P-CR | Approval | 23.700-29: KI#2, New Sol: Support of Store and Forward Satellite Operation via Control Plane Buffering. | Tencent, Tencent Cloud | Rel-19 | Covered into S2-2400364. Noted | Lalith(Samsung) comments. Same comments as 364 apply for this CR too. Saso (Intel) proposes to note the document. Steve (Huawei) comments. Jean Yves (Thales) requires explanations in a new revision. Lei(Tencent) provides comments, and prefer to merge this paper into S2-2400364 which includes both control plane and user plane aspect. Will provide a revision in S2-2400364 thread. ==== Revisions Deadline ==== Jean Yves(Thales) for notes, shall be noted (according the author, merged into S2-2400364) ==== Final Comments Deadline ==== | Noted |
| 19.1 | S2-2400466 | P-CR | Approval | 23.700-29: KI#2, New Sol: Store and forward control for MT data delivery based on feeder link availability information in the MME. | LG Electronics | Rel-19 | r03 Agreed. Revised to S2-2401788. | Hucheng (CATT) comments. Saso (Intel) comments; proposes to note the document. Steve (Huawei) comments. Jean Yves (Thales) comments. Jaewoo (LGE) replies to the previous comments. Stephen (Qualcomm) comments Saubhagya (Nokia) agrees with Intel view Jaewoo (LGE) provides r01. Amy (vivo) provides suggestions Kundan(NEC) Supports the contributions Jaewoo (LGE) replies to previous comments and provides r02. Amy (vivo) replies Jaewoo (LGE) replies to Amy (vivo) and Stephen (Qualcomm), and provides r03. Stephen (Qualcomm) comments again ==== Revisions Deadline ==== Stephen (Qualcomm) replies to Jaewoo (LGE) ==== Final Comments Deadline ==== | Revised |
| 19.1 | S2-2401788 | P-CR | Approval | 23.700-29: KI#2, New Sol: Solution on enabling S&F operation and data delivery with only eNB onboard. | LG Electronics | Rel-19 | Revision of S2-2400466r03. Approved | Approved | |
| 19.1 | S2-2400540 | P-CR | Approval | 23.700-29: KI#2, New Sol: Provision of Store and Forward Satellite Specific Parameters. | LG Electronics | Rel-19 | r01 Agreed. Revised to S2-2401789. | Steve (Huawei) comments Stefan (Ericsson) comments jean yves (Thales) comments Hyunsook (LGE) replies about the previous comments and asks some views. Steve (Huawei) comments in what to do Stefan (Ericsson) supports to start bottom-up Hyunsook (LGE) provides r01. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 19.1 | S2-2401789 | P-CR | Approval | 23.700-29: KI#2, New Sol: Provision of Store and Forward Satellite Specific Parameters. | LG Electronics | Rel-19 | Revision of S2-2400540r01. Approved | Approved | |
| 19.1 | S2-2400576 | P-CR | Approval | 23.700-29: KI#2, New Sol: Attach Procedure with MME and HSS on board the satellite . | OPPO | Rel-19 | r01 Agreed. Revised to S2-2401790. | Thierry (Novamint) comments Boren (OPPO) replies. Steve (Huawei) comments. Lalith(Samsung) comments Stefan (Ericsson) comments Stephen (Qualcomm) comments Boren (OPPO) replies and provides r01. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 19.1 | S2-2401790 | P-CR | Approval | 23.700-29: KI#2, New Sol: Attach Procedure with MME and HSS on board the satellite . | OPPO, NEC | Rel-19 | Revision of S2-2400576r01. Approved | Approved | |
| 19.1 | S2-2400693 | P-CR | Approval | 23.700-29: KI #2, New Sol: Support of store and forward in EPS. | NEC | Rel-19 | Revision of (unhandled) S2-2312698. Noted | Steve (Huawei) comments, seems to assume links are always available. Jean Yves (Thales) proposes to note Stephen (Qualcomm) comments Saubhagya (Nokia) same view as Huawei; propose to note it Hucheng (CATT) share similar views as Saubhagya (Nokia) and Steve Kundan(NEC) responds to Steven and Shobhagya. This pCR assumes that only for registration procedure feeder link and service link is available. It is possible that feederlink and service link is connected at some point. For data transfer it assumes that feederlink or service link is not available which is the case most of the time. Jaewoo (LGE) provides comments on the scenario. Kundan(NEC) provides r01. Amy (vivo) provides comments. Thierry (Novamint) comments Kundan (NEC) responds to Amy. Steve (Huawei) comments on the new solution Saubhagya (Nokia) provide comments, Stephen (Qualcomm) comments again Kundan(NEC) provides r02 handling Steve(Huawei) and Amy (VIVO) comments. This is single satellite coverage case . Kundan(NEC) responds to Steve that this is not new solution. Only attach procedure is merged to data transmission. Kindly compare old and new version. Kundan(NEC) answer to Saubhagya. Stefan (Ericsson) provides comments Kundan(NEC) answers to Stefan. Saso (Intel) comments. Jean Yves (Thales) proposes to note the solution in this meeting ==== Revisions Deadline ==== Steve (Huawei) for clarity, objects to all revisions ==== Final Comments Deadline ==== | Noted |
| 19.1 | S2-2400705 | P-CR | Approval | 23.700-29: New solution for Key Issue #2: Support of Store and Forward Satellite operation for SMS. | China Telecom | Rel-19 | r01 Agreed. Revised to S2-2401791. | Steve (Huawei) asks a question Stephen (Qualcomm) comments Heng (China Telecom) reply to Steve and provides r01 Heng (China Telecom) replies to Stephen. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 19.1 | S2-2401791 | P-CR | Approval | 23.700-29: New solution for Key Issue #2: Support of Store and Forward Satellite operation for SMS. | China Telecom | Rel-19 | Revision of S2-2400705r01. Approved | Approved | |
| 19.1 | S2-2400727 | P-CR | Approval | 23.700-29: TR 23.700-29 KI#2 Solution: Performance optimization for the transport of MT/MO S&F traffic. | China Mobile | Rel-19 | r02 Agreed. Revised to S2-2401792. | Steve (Huawei) asks for clarification Tianji (CMCC) replies to the comment. Saubhagya (Nokia) provide comments Tianji (CMCC) replies and provides r01 to address the comments Tianji (CMCC) provides r02 to address editorial formatting issue by following the skeleton template. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 19.1 | S2-2401792 | P-CR | Approval | 23.700-29: TR 23.700-29 KI#2 Solution: Performance optimization for the transport of MT/MO S&F traffic. | China Mobile | Rel-19 | Revision of S2-2400727r02. Approved | Approved | |
| 19.1 | S2-2400795 | P-CR | Approval | 23.700-29: New Solution on Enabling S&F operation with C-SGN onboard. | Vivo | Rel-19 | r07 Agreed. Revised to S2-2401793. | Hucheng(CATT) comments Thierry (Novamint) comments Amy (vivo) provides r01, answers to Hucheng (CATT) and thanks Thierry (Novamint)'s comments, and asks for confirmation Steve (Huawei) comments. Lalith(Samsung) seeks clarification. Stefan (Ericsson) comments Stephen (Qualcomm) comments Amy (vivo) provides r02 and replies to Stephen (Qualcomm), Stefan (Ericsson), Lalith (Samsung) Saubhagya (Nokia) provide comments Amy (vivo) provides r03 and replies to Saubhagya (Nokia) Amy (vivo) replies to Saubhagya (Nokia) and believes all S&F solutions have RAN dependency. Kundan(NEC) supports r03. Saso (Intel) supports Saubhagya; proposes to note the document. Amy (vivo) provides r04, disagrees with noting this document, AS pause/recovery can reuse the current RAN release/setup mechanism. Hucheng (CATT) comments and proposes a way forward. Lalith (Samsung) supports to document this solution in the TR. Steve (Huawei) comments on C-SGN Amy (vivo) provides r05, thanks to Lalith (Samsung)'s support, and replies to Hucheng (CATT), Steve (Huawei) Amy (vivo) provides r06 by adding NEC as a cosigner Saso (Intel) requests addition of EN on multiple satellites. Saso (Intel) provides r07 with addition of EN on multiple satellites. Amy (vivo) is ok with r07 by adding EN on multiple satellites. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 19.1 | S2-2401793 | P-CR | Approval | 23.700-29: New Solution on Enabling S&F operation with C-SGN onboard. | Vivo,NEC | Rel-19 | Revision of S2-2400795r07. Approved | Approved | |
| 19.1 | S2-2400865 | P-CR | Approval | 23.700-29: KI #2, New Sol: Support of Store and Forward Satellite operation. | IPLOOK | Rel-19 | Noted | Jaewoo (LGE) comments. Saubhagya (Nokia) provide comments. Boren (OPPO) comments. Lalith(Samsung) comments. Steve (Huawei) looks like the problem restated. Stephen (Qualcomm) comments Jean Yves (Thales) proposes to note the contribution Hucheng (CATT) share similar view as previous speakers Stefan (Ericsson) also proposes to note ==== Revisions Deadline ==== Steve (Huawei) for clarity: objects to all revisions. ==== Final Comments Deadline ==== | Noted |
| 19.1 | S2-2400924 | P-CR | Approval | 23.700-29: Solution for KI#2: Support of Store and Forward Satellite operation. | CATT | Rel-19 | r02 Agreed. Revised to S2-2401794. | Steve (Huawei) comments Stefan (Ericsson) comments Saubhagya (Nokia) provide comments Hucheng (CATT) replies to the comments. Saso (Intel) seeks clarification. Steve (Huawei) Opps, CT6 not SA6! Stephen (Qualcomm) comments Hucheng replies to Saso and Stephen Yingying (CATT) provides the revision r01. Stephen (Qualcomm) comments again Yingying (CATT) replies to Stephen and provides the revision r02. ==== Revisions Deadline ==== Jean Yves (Thales) OK with r02. ==== Final Comments Deadline ==== | Revised |
| 19.1 | S2-2401794 | P-CR | Approval | 23.700-29: Solution for KI#2: Support of Store and Forward Satellite operation. | CATT | Rel-19 | Revision of S2-2400924r02. Approved | Approved | |
| 19.1 | S2-2400985 | P-CR | Approval | 23.700-29: KI#2, New Sol: Initial Attach / Registration in 5GSAT network for S&F operation. | Intel | Rel-19 | r05 Agreed. Revised to S2-2401795. | Stephen (Qualcomm) comments Saubhagya (Nokia) provide comments. Hucheng (CATT) comments. Saso (Intel) provides r01 Hucheng(CATT) provides further comments to r01 Lalith(Samsung) seeks clarification. Saso (Intel) provides r02 Steve (Huawei) comments on CSGN. Saso (Intel) replies to Steve and Lalith. Steve (Huawei) comments on only MME in CSGN Ellen (Google) comments Saso (Intel) replies to Steve and provides r03 (with changes-on-changes) and r04 (without). Saso (Intel) replies to Ellen Kundan (NEC) asks clarification questions. Yuxin (Xiaomi) comments. Saso (Intel) replies to Kundan. Saso (Intel) replies to Yuxin. Kundan (NEC) further clarifies to Saso (Intel). Steve (Huawei) comments on coverage time Ellen (Google) thanks for clarification and replies to Saso Amy (vivo) suggests to merge this into 0795 Saso (Intel) refuses to merge with 0795. These are different solutions. Amy (vivo) agrees to not merge as you are considering eNB+MME onboard instead of C-SGN Saso (Intel) replies to Amy. Amy (vivo) helps to announce that r04 is available, and ok with r04 Saso (Intel) announces that r03 and r04 have been available since yesterday; apologies for the missing announcement. Stephen (Qualcomm) comments again Kundan(NEC) provides comment on r03/04. Saso (Intel) replies to Kundan and Stephen; provides r05 ==== Revisions Deadline ==== Jean Yves (Thales) OK with r02. Saso (Intel) point out to Jean-Yves that the latest revision is r05. Jean Yves (Thales) OK with r05. ==== Final Comments Deadline ==== | Revised |
| 19.1 | S2-2401795 | P-CR | Approval | 23.700-29: KI#2, New Sol: Initial Attach / Registration in 5GSAT network for S&F operation. | Intel | Rel-19 | Revision of S2-2400985r05. Approved | Approved | |
| 19.1 | S2-2401021 | P-CR | Approval | 23.700-29: KI #2, New Sol: Support of store and forward satellite operation in EPS. | Xiaomi | Rel-19 | r02 Agreed. Revised to S2-2401796. | Steve (Huawei) comments on what it is targeting. Yuxin (Xiaomi) replies. Steve (Huawei) it assumes simultaneously connection? Jean Yves (Thales) is sharing Steve's concern Tianji (CMCC) comments & recommends for clarification in a revision. Stephen (Qualcomm) comments Hucheng (CATT) also has concern on the assumption of the solution. Yuxin (Xiaomi) provides r01 Yuxin (Xiaomi) replies to Jean-Yves with the concern for UE attachment Steve (Huawei) comments on updates Yuxin (Xiaomi) provides r02 ==== Revisions Deadline ==== Jean Yves (Thales) comments. Yuxin (Xiaomi) replies to Jean-Yves. Jean Yves (Thales) OK with r02 ==== Final Comments Deadline ==== | Revised |
| 19.1 | S2-2401796 | P-CR | Approval | 23.700-29: KI #2, New Sol: Support of store and forward satellite operation in EPS. | Xiaomi | Rel-19 | Revision of S2-2401021r02. Approved | Approved | |
| 19.1 | S2-2401232 | P-CR | Approval | 23.700-29: KI#2: S&F solution for multi-satellite IoT NTN. | Sateliot, GateHouse, Novamint | Rel-19 | r03 Agreed. Revised to S2-2401797. | Stephen (Qualcomm) comments Steve (Huawei) comments. Saso (Intel) replies to Steve; comment to Ramon. Amy (vivo) clarifies this solution also needs C-SGN on the ground and is different with 0795 and 0985, and provides comments Saso (Intel) provides r02. Ramon (Sateliot) provides r03 and replies to Saso (Intel), Steve (Huawei) and Amy (Vivo). Relja (TNO) provides a comment. Ramon (Sateliot) replies to Relja (TNO). Relja (TNO) thanks Ramon for clarification. TNO supports the proposed solution for the KI#2. ==== Revisions Deadline ==== Jean Yves (Thales) OK with r03. ==== Final Comments Deadline ==== | Revised |
| 19.1 | S2-2401797 | P-CR | Approval | 23.700-29: KI#2: S&F solution for multi-satellite IoT NTN. | Sateliot, GateHouse, Novamint | Rel-19 | Revision of S2-2401232r03. Approved | Approved | |
| 19.1 | S2-2401313 | P-CR | Approval | 23.700-29: KI#2: S&F for multiple satellite deployment. | Samsung | Rel-19 | r02 Agreed. Revised to S2-2401798. | Stephen (Qualcomm) comments Lalith(Samsung) replies to Stephen (Qualcomm) comments Steve (Huawei) comments. Stephen (Qualcomm) provides an r01 Lalith (Samsung) is fine with r01 Amy (vivo) proposes merging 1313 and 0317/0341-0343 Lalith (Samsung) indicates solutions in 1313 and 0317/0341-0343 are different and not candidates to merge. Saubhagya (Nokia) agrees to Samsung remarks Steve (Huawei) thanks for the pointer. Lalith(Samsung) provides r02 ==== Revisions Deadline ==== Jean Yves (Thales) OK with r02 Robert (OQ Technology) We are ok with r02. ==== Final Comments Deadline ==== | Revised |
| 19.1 | S2-2401798 | P-CR | Approval | 23.700-29: KI#2: S&F for multiple satellite deployment. | Samsung | Rel-19 | Revision of S2-2401313r02. Approved | Approved | |
| 19.1 | S2-2400989 | P-CR | Approval | 23.700-29: KI#2, New Sol: Support for SMS in 5GSAT network for S&F operation. | Intel | Rel-19 | r04 Agreed. Revised to S2-2401799. | Stephen (Qualcomm) comments Saubhagya (Nokia) provide comments. Saso (Intel) provides r01 Saso (Intel) provides r02 Saso (Intel) provides r03 (with changes-on-changes) and r04 (without). Thierry (Novamint) comments Saso (Intel) replies to Thierry. ==== Revisions Deadline ==== Jean Yves (Thales) OK with r03 and r04. ==== Final Comments Deadline ==== | Revised |
| 19.1 | S2-2401799 | P-CR | Approval | 23.700-29: KI#2, New Sol: Support for SMS in 5GSAT network for S&F operation. | Intel | Rel-19 | Revision of S2-2400989r04. Approved | Approved | |
| 19.1 | S2-2401314 | P-CR | Approval | 23.700-29: KI#2: S&F for single satellite deployment. | Samsung | Rel-19 | r03 Agreed. Revised to S2-2401800. | Thierry (Novamint) comments Lalith (Samsung) comments Jean Yves (Thales) asks question on the rational for single satellite deployment Lalith(Samsung) replies Steve (Huawei) comments. jean Yves (Thales) comments and ask for a revision Lalith(Samsung) provides r01 Stephen (Qualcomm) comments Amy (vivo) suggests several ENs Lalith (Samsung) provides r02. Lalith (Samsung) provides r03. ==== Revisions Deadline ==== Jean Yves (Thales) OK with r03. Robert (OQ Technology) ok with R03. ==== Final Comments Deadline ==== | Revised |
| 19.1 | S2-2401800 | P-CR | Approval | 23.700-29: KI#2: S&F for single satellite deployment. | Samsung | Rel-19 | Revision of S2-2401314r03. Approved | Approved | |
| 19.1 | S2-2401367 | P-CR | Approval | 23.700-29: Solution to KI#2: Support of Store and Forward Satellite Operation. | Qualcomm Incorporated | Rel-19 | r02 Agreed. Revised to S2-2401801. | Hucheng (CATT) comments. Saubhagya (Nokia) provide comments. Boren (OPPO) provides comments. Lalith(Samsung) seeks clarification. Steve (Huawei) comments. Stephen (Qualcomm) replies to comments Thierry (Novamint) comments Lalith(Samsung) provides r01. jean yves (thales) ask question on solution completion Steve (Huawei) comments on complexity Stephen (Qualcomm) replies to Steve (Huawei) Stephen (Qualcomm) replies to Jean Yves (Thales) Stephen (Qualcomm) replies to Lalith (Samsung) Amy (vivo) provides suggestions. Stephen (Qualcomm) provides an r02 ==== Revisions Deadline ==== Jean Yves (Thales) OK with r02 Robert (OQ Technology) supports r02. ==== Final Comments Deadline ==== | Revised |
| 19.1 | S2-2401801 | P-CR | Approval | 23.700-29: Solution to KI#2: Support of Store and Forward Satellite Operation. | Qualcomm Incorporated | Rel-19 | Revision of S2-2401367r02. Approved | Approved | |
| 19.1 | - | - | - | KI#3 | - | - | Docs:=16 | - | |
| 19.1 | S2-2400338 | P-CR | Approval | 23.700-29: KI #3, New sol: Solution of P-CSCF offload for UE-satellite-UE communication. | China Mobile | Rel-19 | Noted | George Foti (Ericsson) provides comments Hucheng(CATT) comments Yuxin (Xiaomi) provides comments Amy (vivo) provides comments. Haris(Qualcomm) comments Saubhagya (Nokia) provide comments Yi (China Mobile) provides r01 to address multiple comments. ==== Revisions Deadline ==== Yi (China Mobile) suggest to go with r01 and replies to George. George (Ericsson) proposes to postpone the CR George (Ericsson) responds to Yi Yi (China Mobile) replies to George inline. ==== Final Comments Deadline ==== | Noted |
| 19.1 | S2-2400339 | P-CR | Approval | 23.700-29: KI #3, New sol: Solution of Satellite on board UPF and IMS Media Plane function selection for UE-satellite-UE communication. | China Mobile | Rel-19 | r01 Agreed. Revised to S2-2401802. | Steve (Huawei) comments on discontinuous coverage Stefan (Ericsson) provides comments Hanbai Wang(China Mobile) replies to Steve (Huawei) and Stefan (Ericsson) Jean Yves(Thales) request clarification Hanbai Wang(China Mobile) replies to Jean Yves(Thales) Stefan (Ericsson) replies to Hanbai Yi(China Mobile) uploads r01 Hanbai replies to Stefan (Ericsson) ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 19.1 | S2-2401802 | P-CR | Approval | 23.700-29: KI #3, New sol: Solution of Satellite on board UPF and IMS Media Plane function selection for UE-satellite-UE communication. | China Mobile | Rel-19 | Revision of S2-2400339r01. Approved | Approved | |
| 19.1 | S2-2400704 | P-CR | Approval | 23.700-29: New Solution for Key Issue #3: Support of UE-satellite-UE communication. | China Telecom | Rel-19 | r04 Agreed. Revised to S2-2401803, merging S2-2400928 | Yi (China Mobile) comments that the solution may not work. Heng (China Telecom) reply to Yi. Amy (vivo) provides comments. Stefan (Ericsson) comments Heng (China Telecom) reply to Amy. Heng(China Telecom) reply to Stefan (Ericsson) and provides r01 Baixiao (CATT) request to merge S2-2400928 into this one and provides r02. Heng (China Telecom) is ok with r02. Amy (vivo) provides r03 to address Amy's concern. Heng (China Telecom) provides r04 to change the title of r03 ==== Revisions Deadline ==== Yi (China Mobile) ask questions for clarification. Jean Yves (Thales) OK with r04 ==== Final Comments Deadline ==== | Revised |
| 19.1 | S2-2401803 | P-CR | Approval | 23.700-29: New Solution for Key Issue #3: Support of UE-satellite-UE communication with UPF/AGW inserted on satellite. | China Telecom, CATT | Rel-19 | Revision of S2-2400704r04, merging S2-2400928. Approved | Approved | |
| 19.1 | S2-2400796 | P-CR | Approval | 23.700-29: New Solution on SMF activated UE-satellite-UE Communication for IMS Service. | Vivo | Rel-19 | r02 Agreed. Revised to S2-2401804. | Hucheng(CATT) comments Yi (China Mobile) comments. Amy (vivo) suggests keeping 0796 separately as it is an SMF-activated UE-S-UE local switch solution instead of S-CSCF (0926) and provides answers to Yi (China Mobile) Stefan (Ericsson) comments Amy (vivo) provides r01 and replies to Stefan (Ericsson) Haris(Qualcomm) provides r02 Amy (vivo) is ok with Haris(Qualcomm) providing r02 ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 19.1 | S2-2401804 | P-CR | Approval | 23.700-29: New Solution on SMF activated UE-satellite-UE Communication for IMS Service. | Vivo | Rel-19 | Revision of S2-2400796r02. Approved | Approved | |
| 19.1 | S2-2400853 | P-CR | Approval | 23.700-29: KI#3: New Solution for UE-satellite-UE communication with IMS-AGW onboard . | Huawei, HiSilicon | Rel-19 | Noted | George Foti (Ericsson) provides comments Hucheng(CATT) comments George (Ericsson) provides response. Michele Zarri [Huawei] replied to the comments from Ericsson and CATT and provided r01 Saubhagya (Nokia) provide comments Michele Zarri [Huawei] commented George (Ericsson) provides comments Michele Zarri [Huawei] replied to Nokia's comments and provided revision 02 Michele Zarri [Huawei] replied to Ericsson's comments ==== Revisions Deadline ==== George (Ericsson) proposes to note the pCR ==== Final Comments Deadline ==== | Noted |
| 19.1 | S2-2400854 | P-CR | Approval | 23.700-29: KI#3: New Solution for UE-satellite-UE communication with UPF onboard . | Huawei, HiSilicon | Rel-19 | r01 Agreed. Revised to S2-2401805. | Hucheng(CATT) comments Amy (vivo) provides comments. Yi (China Mobile) comments that more details are needed for the solution. Stefan (Ericsson) comments Michele Zarri [Huawei] replied to the comments from China Mobile Michele Zarri [Huawei] comments (reply to Ericsson) Michele Zarri [Huawei] replied to the comments from CATT Stefan (Ericsson) provides r01 Hucheng(CATT) replies to Michele Zarri [Huawei] Michele Zarri [Huawei] comments (reply to Ericsson): Huawei is happy with r01 ==== Revisions Deadline ==== jean yves [Thales] OK with r01 ==== Final Comments Deadline ==== | Revised |
| 19.1 | S2-2401805 | P-CR | Approval | 23.700-29: KI#3: New Solution for UE-satellite-UE communication with UPF onboard . | Huawei, HiSilicon | Rel-19 | Revision of S2-2400854r01. Approved | Approved | |
| 19.1 | S2-2400926 | P-CR | Approval | 23.700-29: KI#3: New solution to UE-Satellite-UE Communication via UPFs onboard the satellites. | CATT | Rel-19 | r04 Agreed. Revised to S2-2401806, merging S2-2401022 | Stefan (Ericsson) comments Yuxin (Xiaomi) provides r01 to merge S2-2401022 Hucheng (CATT) replies to the comments and provides r02 based on Xiaomi version. Haris(Qualcomm) provides r03 Stefan (Ericsson) provides r04 ==== Revisions Deadline ==== Jean Yves (Thales) OK with r04 ==== Final Comments Deadline ==== | Revised |
| 19.1 | S2-2401806 | P-CR | Approval | 23.700-29: KI#3: New solution to UE-Satellite-UE Communication via UPFs onboard the satellites. | CATT, Xiaomi | Rel-19 | Revision of S2-2400926r04, merging S2-2401022. Approved | Approved | |
| 19.1 | S2-2400928 | P-CR | Approval | 23.700-29: KI#3: New solution to UE-Satellite-UE Communication via UPFs and IMS AGWs on-board the satellites. | CATT | Rel-19 | Merged into S2-2401803 | Stefan (Ericsson) comments Hucheng (CATT) replies to Stefan (Ericsson) comments Jean Yves (Thales) reproposes to merge with S2-2400853 Baixiao (CATT) merges this one into S2-2400704. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 19.1 | S2-2401022 | P-CR | Approval | 23.700-29: KI #3, New Sol: Support of UE-satellite-UE communication in 5GS. | Xiaomi | Rel-19 | Merged into S2-2401806 | Hucheng(CATT) comments Yuxin(Xiaomi) agree to merge this pCR into S2-2400926 Steve (Huawei) asks for clarification Saubhagya (Nokia) seeking clarification Stefan (Ericsson) provides comments Yuxin (Xiaomi) replies and request terminate this thread as it was merged into S2-2400926 ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 19.1 | S2-2401077 | P-CR | Approval | 23.700-29: New Solution for KI#3: Solution to determine UE-SATs-UE eligibility and enable communication setup. | Thales | Rel-19 | r02 Agreed. Revised to S2-2401807. | Saubhagya (Nokia) provide comments Steve (Huawei) comments on not matching the TR and other aspects. Jean Yves (Thales) answers Saubhagya Jean Yves (Thales) answers to comments on not matching the TR and other aspects and provides revision r01 Steve (Huawei) comments on evaluation Peng (OPPO) asks for clarification. jean yves (Thales) answers comments jean yves (Thales) provides r02 to remove 6.X.4 evaluation clause Jean Yves (Thales) responds to Peng. Peng (OPPO) replies ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 19.1 | S2-2401807 | P-CR | Approval | 23.700-29: New Solution for KI#3: Solution to determine UE-SATs-UE eligibility and enable communication setup. | Thales | Rel-19 | Revision of S2-2401077r02. Approved | Approved | |
| 19.1 | - | - | - | Discussion | - | - | Docs:=1 | - | |
| 19.1 | S2-2400446 | DISCUSSION | Discussion | QoS considerations for enhanced NTN architectures. | National Spectrum Consortium (NSC) | Noted | Elena (MITRE) comments on QoS ==== Revisions Deadline ==== | Noted | |
| 19.1 | - | - | - | Documents exceeding TU budget | - | - | Docs:=2 | - | |
| 19.1 | S2-2400793 | P-CR | Approval | 23.700-29: New Solution on the addition of new RAT types and backhaul types. | Vivo | Rel-19 | Not Handled | Ellen (Google) comments Steve (Huawei) comments this paper exceeded the TU budget so will be marked as unhandled. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Not Handled |
| 19.1 | S2-2400574 | P-CR | Approval | 23.700-29: TR 23.700-29 Updates on Terms and Annex A. | OPPO | Rel-19 | Not Handled | ==== Final Comments Deadline ==== | Not Handled |
| 19.2 | - | - | - | Study on system architecture for next generation real time communication services Phase 2 (FS_NG_RTC_Ph2) | - | - | Docs:=51 | - | |
| 19.2 | - | - | - | KI updates | - | - | Docs:=3 | - | |
| 19.2 | S2-2401130 | P-CR | Approval | 23.700-77: KI#1_Update to remove EN. | Samsung | Rel-19 | Approved | Ashok (Samsung) provides clarification George Foti (Ericsson) proposes to note this CR. This alias definition represent a group for a single subscription and not across multiple subscriptions hence it does not fulfill the real definition of group. See below George (Ericsson) provides response Ashok (Samsung) ask a question George (Ericsson) responds Ashok (Samsung) comments George (Ericsson) responds U are changing the KI now. And I find this of little use if U are restricting this to list of IMPUs belonging to the sae subscription which is what U are proposing Ashok (Samsung) clarifies to George (Ericsson) George (Ericsson) So is the pCR now to just update the KI. Ashok (Samsung) responds to George (Ericsson) and Hao (ZTE) Hao (ZTE) comments. Rainer (Nokia) proposes to keep the EN. Ashok (Samsung) clarifies to Rainer (Nokia) ==== Revisions Deadline ==== Ashok (Samsung) thanks Yi (China Mobile) for the support and replies to George Yi (China Mobile) support the idea of the CR. George (Ericsson) proposes to postpone the CR George (Ericsson) responds to Ashok Ashok (Samsung) replies to George (Ericsson) that the only change is now list is replaced by group George (Ericsson) Accepts the original. U removed the EN but that's fine. ==== Final Comments Deadline ==== | Approved |
| 19.2 | S2-2400897 | P-CR | Approval | 23.700-77: KI#8: Update on Text Transcoding. | ZTE | Rel-19 | r01 Agreed. Revised to S2-2401594. | Hao (ZTE) responds. DongYeon (Samsung) comments. Hao (ZTE) responds to Samsung. DongYeon (Samsung) provides comments. Rainer (Nokia) comments Hao (ZTE) responds and provides r01. ==== Revisions Deadline ==== George (Ericsson) Accept R01 ONLY Rainer (Nokia) r01 is ok ==== Final Comments Deadline ==== | Revised |
| 19.2 | S2-2401594 | P-CR | Approval | 23.700-77: KI#8: Update on Text Transcoding. | ZTE | Rel-19 | Revision of S2-2400897r01. Approved | Approved | |
| 19.2 | - | - | - | Solutions to KI#1 | - | - | Docs:=10 | - | |
| 19.2 | S2-2400139 | P-CR | Approval | 23.700-77: KI 1: Update to Solution 1. | Ericsson | Rel-19 | r02 Agreed. Revised to S2-2401595. | Yi (China Mobile) comments. Kefeng (Qualcomm) provides comments. Ashok (Samsung) comments. George (Ericsson) provides comments inline George (Ericsson) provides comments inline. George (Ericsson) provides r01. Just removed the additional Figure. Mu (Huawei) provides comments Rainer (Nokia) provides comments George (Ericsson) provides responses inline Mu (Huawei) provides further comments inline George (Ericsson) see inline. Mu (Huawei) comments, a EN is needed to address how HSS can distinguish between events. George (Ericsson) provides r2 added the EN for HSS to locate the producer of an event ==== Revisions Deadline ==== Rainer (Nokia) ok with r02 ==== Final Comments Deadline ==== | Revised |
| 19.2 | S2-2401595 | P-CR | Approval | 23.700-77: KI 1: Update to Solution 1. | Ericsson | Rel-19 | Revision of S2-2400139r02. Approved | Approved | |
| 19.2 | S2-2400331 | P-CR | Approval | 23.700-77: KI #1, New sol: Event subscription and notification enhancements for DC applications. | China Mobile | Rel-19 | r02 Agreed. Revised to S2-2401596. | George Foti (Ericsson) provides comments Kefeng (Qualcomm) provides comments Ashok (Samsung) comments Jari (NTT DOCOMO) comments Yi (China Mobile) replies and provide r01. Rainer (Nokia) asks for clarification Yi (China Mobile) replies to Rainer and provides r02. Ashok (Samsung) provides further comments George (Ericsson) ask a question. Yi (China Mobile) replies to Ashok. Yi (China Mobile) replies to George inline. George (Ericsson) asks Yi a question. Ashok (Samsung) provides comments. George (Ericsson) responds to Ashok ==== Revisions Deadline ==== George (Ericsson) Accepts R02 ONLY. Rainer (Nokia) ok with r02 ==== Final Comments Deadline ==== | Revised |
| 19.2 | S2-2401596 | P-CR | Approval | 23.700-77: KI #1, New sol: Event subscription and notification enhancements for DC applications. | China Mobile | Rel-19 | Revision of S2-2400331r02. Approved | Approved | |
| 19.2 | S2-2400900 | P-CR | Approval | 23.700-77: KI #1, New Sol: Subscription Operation for IMS Events. | ZTE | Rel-19 | Revision of (postponed) S2-2312668. r02 Agreed. Revised to S2-2401597. | George Foti (Ericsson) proposes to note the pCR. Additional comments below. Yi (China Mobile) comments. Kefeng (Qualcomm) comments. Hao (ZTE) responds and provides r01. Hao (ZTE) responds to George. Rainer (Nokia) comments Hao (ZTE) responds and provides r02. ==== Revisions Deadline ==== George (Ericsson) Accepts R02 ONLY. Rainer (Nokia) ok with r02 ==== Final Comments Deadline ==== | Revised |
| 19.2 | S2-2401597 | P-CR | Approval | 23.700-77: KI #1, New Sol: Subscription Operation for IMS Events. | ZTE | Rel-19 | Revision of S2-2400900r02. Approved | Approved | |
| 19.2 | S2-2401140 | P-CR | Approval | 23.700-77: KI #1, New Sol: Event subscription and notification of IMS DC for related subscribers . | Samsung | Rel-19 | Revision of (unhandled) S2-2312831. r03 Agreed. Revised to S2-2401598. | Yi (China Mobile) comments. George Foti (Ericsson) provides comments Ashok (Samsung) provides response. George (Ericsson) provides response Ashok (Samsung) provides r01 Rainer (Nokia) comments, proposes to add EN. Mu (Huawei) comments Ashok (Samsung) provides r02 and responds to Rainer (Nokia). Ashok (Samsung) responds to Mu (Huawei) Ashok (Samsung) respond to George (Ericsson) Mu (Huawei) further comments Ashok (Samsung) replies George (Ericsson) I prefer U prefer explain it later with an EN. It is too buried in the text and it is an important point. Ashok (Samsung) provides r03. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 19.2 | S2-2401598 | P-CR | Approval | 23.700-77: KI #1, New Sol: Event subscription and notification of IMS DC for related subscribers . | Samsung | Rel-19 | Revision of S2-2401140r03. Approved | Approved | |
| 19.2 | S2-2401217 | P-CR | Approval | 23.700-77: KI#1 New Sol: IMS event subscription mechanism. | Huawei, HiSilicon | Rel-19 | r01 Agreed. Revised to S2-2401599. | George Foti (Ericsson) provides comments Kefeng (Qualcomm) provides comments Mu (Huawei) replies to George and Kefeng George (Ericsson) provides responses inline Mu (Huawei) provide responses inline George (Ericsson) My questions are not addressed and each items needs an EN. See below Hao (ZTE) comments on unsubscribe procedure. Rainer (Nokia) provides comments Mu (Huawei) provide further comment inline George (Ericsson) provides comments Mu (Huawei) provide r01 based on the comment received. ==== Revisions Deadline ==== George (Ericsson) Accepts R01 ONLY Rainer (Nokia) r01 is ok ==== Final Comments Deadline ==== | Revised |
| 19.2 | S2-2401599 | P-CR | Approval | 23.700-77: KI#1 New Sol: IMS event subscription mechanism. | Huawei, HiSilicon | Rel-19 | Revision of S2-2401217r01. Approved | Approved | |
| 19.2 | - | - | - | Solutions to KI#2 | - | - | Docs:=5 | - | |
| 19.2 | S2-2401142 | P-CR | Approval | 23.700-77: 23.700-77: Solution to KI#2_ IMS NW exposing capabilities for IMS DC . | Samsung | Rel-19 | Revision of (unhandled) S2-2312833. Postponed | Ashok (Samsung) provides clarification. Hao (ZTE) comments. Yi (China Mobile) comments. George Foti (Ericsson) proposes to postpone this CR. This is mostly a conclusion. We are not at this stage yet. George (Ericsson) provides response Rainer (Nokia) comments Ashok (Samsung) provides r01 ==== Revisions Deadline ==== Ashok (Samsung) proposes to agree with r01 George (Ericsson) proposes to postpone the CR Rainer (Nokia) proposes to postpone ==== Final Comments Deadline ==== | Postponed |
| 19.2 | S2-2401218 | P-CR | Approval | 23.700-77: KI#2 New Sol: IMS capability exposure architecture. | Huawei, HiSilicon | Rel-19 | r02 Agreed. Revised to S2-2401600. | Yi (China Mobile) comments. George Foti (Ericsson) provides comments Ashok (Samsung) comments. Kefeng (Qualcomm) provide comments. Mu (Huawei) replies to previous comments Mu (Huawei) replies to Ashok Rainer (Nokia) asks for clarification Leo (Deutsche Telekom) has the same questions/comments/concerns stated below and in addition requests editorial correction Mu (Huawei) provides response Ashok (Samsung) provides further comments Mu (Huawei) provide r01 George (Ericsson) asks a question Mu (Huawei) answers the question George (Ericsson) provides comments Mu (Huawei) provide r02 and inline comment ==== Revisions Deadline ==== George (Ericsson) Accepts ONLY R02 Rainer (Nokia) ok with r02 ==== Final Comments Deadline ==== | Revised |
| 19.2 | S2-2401600 | P-CR | Approval | 23.700-77: KI#2 New Sol: IMS capability exposure architecture. | Huawei, HiSilicon | Rel-19 | Revision of S2-2401218r02. Approved | Approved | |
| 19.2 | S2-2401276 | P-CR | Approval | 23.700-77: KI#2: New solution on IMS capability exposure via DC3/DC4. | Nokia, Nokia Shanghai Bell | Rel-19 | r01 Agreed. Revised to S2-2401601. | Yi (China Mobile) comments. George Foti (Ericsson) provides comments Kefeng (Qualcomm) provides comments. George (Ericsson) provides response. Fig 1 is indeed invisible Rainer (Nokia) provides r01. ==== Revisions Deadline ==== George (Ericsson) Accepts R01 ONLY ==== Final Comments Deadline ==== | Revised |
| 19.2 | S2-2401601 | P-CR | Approval | 23.700-77: KI#2: New solution on IMS capability exposure via DC3/DC4. | Nokia, Nokia Shanghai Bell | Rel-19 | Revision of S2-2401276r01. Approved | Approved | |
| 19.2 | - | - | - | Solutions to KI#3 | - | - | Docs:=5 | - | |
| 19.2 | S2-2400329 | P-CR | Approval | 23.700-77: KI#3, New sol: Solution of Data Channel interworking. | China Mobile, Huawei, HiSilicon | Rel-19 | r01 agreed. Revised to S2-2401646. | DongYeon (Samsung) provides comments. George Foti (Ericsson) provides comments Kefeng (Qualcomm) provides comments. Rainer (Nokia) asks for clarification Yi (China Mobile) provides r01. Rainer (Nokia) comments Yi (China Mobile) replies Rainer inline. ==== Revisions Deadline ==== Yi (China Mobile) replies to George and cant agree to note the pCR. George (Ericsson) proposes to note the pCR Yi (China Mobile) replies to George. George (Ericsson) responds. Yi (China Mobile) provides r02 and add the EN. Propose to agree r02. George (Ericsson) would Accept R02 Only if allowed by the chair Rainer (Nokia) can we postpone to next meeting? ==== Final Comments Deadline ==== Rainer (Nokia) is ok to add the EN | Revised |
| 19.2 | S2-2401646 | P-CR | Approval | 23.700-77: KI#3, New sol: Solution of Data Channel interworking. | China Mobile, Huawei, HiSilicon | Rel-19 | Revision of S2-2400329r01. Approved | Approved | |
| 19.2 | S2-2400866 | P-CR | Approval | 23.700-77: New solution to Data Channel interworking with MTSI UE. | Vivo | Rel-19 | r05 Agreed. Revised to S2-2401602. | George Foti (Ericsson) provides comments James Jin (vivo) replies to questions from George Foti (Ericsson) and DongYeon (Samsung) and provide r01 DongYeon (Samsung) provides comments. Yi (China Mobile) comments. James Jin(vivo) reply comments from Yi (China Mobile) Kefeng (Qualcomm) provides comments and corrects the e-mail title. James Jin(vivo) reply comments from Kefeng (Qualcomm) George (Ericsson) provides responses inline. George (Ericsson) provides response. Yes James Jin (vivo) provides r02 Mu (Huawei) comments James Jin (vivo) provides responses to Mu (Huawei) Rainer (Nokia) provides comments Mu (Huawei) provide further comments James Jin (vivo) replies comments from Rainer (Nokia) and provide r03. Rainer (Nokia) comments George (Ericsson) asks a question on r3. James Jin (vivo) replies comments from Rainer (Nokia), George (Ericsson) and provide r04. George (Ericsson) still have a question James Jin (vivo) replies comments from George (Ericsson) and provide r05. ==== Revisions Deadline ==== George (Ericsson) Accepts R05 ONLY Rainer (Nokia) ok with r05 ==== Final Comments Deadline ==== | Revised |
| 19.2 | S2-2401602 | P-CR | Approval | 23.700-77: New solution to Data Channel interworking with MTSI UE. | Vivo | Rel-19 | Revision of S2-2400866r05. Approved | Approved | |
| 19.2 | S2-2400981 | P-CR | Approval | 23.700-77: 23.700-77: KI#3: Solution for Data channel interworking with MTSI UE . | Samsung | Rel-19 | Revision of (unhandled) S2-2312337. Postponed | George Foti (Ericsson) provides comments Yi (China Mobile) comments. Kefeng (Qualcomm) provides comments. Rainer (Nokia) asks for clarification DongYeon (Samsung) provides r01, and replies to Rainer (Nokia), Kenny (Qualcomm), Yi (China Mobile), and George (Ericsson). George (Ericsson) has questions ==== Revisions Deadline ==== Kefeng (Qualcomm) proposes to postpone the pCR George (Ericsson) proposes to note the pCR DongYeon (Samsung) agrees to postpone. ==== Final Comments Deadline ==== | Postponed |
| 19.2 | - | - | - | Solutions to KI#4 | - | - | Docs:=7 | - | |
| 19.2 | S2-2400140 | P-CR | Approval | 23.700-77: KI 4 Solution for authorization and authentication of third party identities. | Ericsson | Rel-19 | r03 Agreed. Revised to S2-2401603. | Kefeng (Qualcomm) provides comments. George (Ericsson) provides response Leo (Deutsche Telekom) provides comments. Rainer (Nokia) comments Mu (Huawei) Comments, what is the 3P ID? How it convoy in SIP? Who assign it? George (Ericsson) asks question Rainer (Nokia) replies George (Ericsson) provides a response George (Ericsson) provides r01 to update the table for the correct issue number. Kefeng (Qualcomm) has strong concern with UE carrying third party ID information in the INVITE. Kefeng (Qualcomm) replies Rainer (Nokia) Kefeng (Qualcomm) further replies Rainer (Nokia) George (Ericsson) responds to both QC and Nokia Kefeng (Qualcomm) asks George (Ericsson) for more clarification George (Ericsson) responds inline Kefeng (Qualcomm) provides comments to r02. George (Ericsson) now with the link. George (Ericsson) provides ro2. Changes are highlighted in yellow. More comments below Rainer (Nokia) comments on r02, asks for clarification George (Ericsson) provides r03 George (Ericsson) responds to Kenny inline ==== Revisions Deadline ==== Rainer (Nokia) ok with r03 ==== Final Comments Deadline ==== | Revised |
| 19.2 | S2-2401603 | P-CR | Approval | 23.700-77: KI 4 Solution for authorization and authentication of third party identities. | Ericsson | Rel-19 | Revision of S2-2400140r03. Approved | Approved | |
| 19.2 | S2-2400537 | P-CR | Approval | 23.700-77: New Solution on authorization and authentication of third party ID. | Qualcomm Incorporated | Rel-19 | Approved | George Foti (Ericsson) provides comments Kefeng (Qualcomm) replies George Foti (Ericsson) comments Rainer (Nokia) comments on the solution George (Ericsson) provides additional comments in line on points where I need some confirmation George (Ericsson) asks question Rainer (Nokia) replies Kefeng (Qualcomm) replies Rainer (Nokia) comment. Kefeng (Qualcomm) replies additional comments from George Foti (Ericsson) George (Ericsson) agrees. I had the same concern on just sending URI for reasons below ==== Revisions Deadline ==== George (Ericsson) OK with the original revision Rainer (Nokia) can accept r00 ==== Final Comments Deadline ==== | Approved |
| 19.2 | S2-2401144 | P-CR | Approval | 23.700-77: 23.700-77: Solution to KI#4_ Extensible IMS framework to support authorization and authentication of third-party identities in IMS sessions. | Samsung | Rel-19 | r01 Agreed. Revised to S2-2401604. | George Foti (Ericsson) provides comments Ashok (Samsung) provides answers Kefeng (Qualcomm) provides comments George (Ericsson) provides question to Ashok. Ashok (Samsung) responds to George (Ericsson) and Kenny (Qualcomm) Rainer (Nokia) provides comments on the solution Ashok (Samsung) replies Rainer (Nokia) Rainer (Nokia) replies to Ashok (Samsung) Ashok (Samsung) provides r01 ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 19.2 | S2-2401604 | P-CR | Approval | 23.700-77: 23.700-77: Solution to KI#4_ Extensible IMS framework to support authorization and authentication of third-party identities in IMS sessions. | Samsung | Rel-19 | Revision of S2-2401144r01. Approved | Approved | |
| 19.2 | S2-2401275 | P-CR | Approval | 23.700-77: KI#4: New solution for support of authorization and authentication of third-party identities. | Nokia, Nokia Shanghai Bell | Rel-19 | r01 Agreed. Revised to S2-2401605. | George Foti (Ericsson) provides comments Kefeng (Qualcomm) provides comments Rainer (Nokia) replies to comments Ashok (Samsung) provides comments Ashok (Samsung) comments Rainer (Nokia) replies to Ashok (Samsung). George (Ericsson) provides response George (Ericsson) provides comments Ashok (Samsung) requests for revision Rainer (Nokia) provides r01 ==== Revisions Deadline ==== George (Ericsson) Accepts R01. ==== Final Comments Deadline ==== | Revised |
| 19.2 | S2-2401605 | P-CR | Approval | 23.700-77: KI#4: New solution for support of authorization and authentication of third-party identities. | Nokia, Nokia Shanghai Bell | Rel-19 | Revision of S2-2401275r01. Approved | Approved | |
| 19.2 | - | - | - | Solutions to KI#5 | - | - | Docs:=2 | - | |
| 19.2 | S2-2400538 | P-CR | Approval | 23.700-77: Customized PS Data Off Exemption for IMS DC. | Qualcomm Incorporated | Rel-19 | Not Handled | ==== Final Comments Deadline ==== | Not Handled |
| 19.2 | S2-2401146 | P-CR | Approval | 23.700-77: 23.700-77: Solution to KI#5_ Handling of PS data off exemption for services over IMS DC . | Samsung | Rel-19 | Revision of (unhandled) S2-2312834. Not Handled | ==== Final Comments Deadline ==== | Not Handled |
| 19.2 | - | - | - | Solutions to KI#6 | - | - | Docs:=8 | - | |
| 19.2 | S2-2400332 | P-CR | Approval | 23.700-77: KI #6, New sol: Standalone data channel without extra subscription. | China Mobile | Rel-19 | r05 Agreed. Revised to S2-2401606, merging S2-2401234 | George Foti (Ericsson) provides comments Kefeng (Qualcomm) provides comments James Jin(vivo) provides comments Yi (China Mobile) replies and provides r01. Jari (NTT DOCOMO) provides r02. Rainer (Nokia) asks questions George (Ericsson) provides comments Mu (Huawei) supporting the idea of supporting standalone DC without extra subscription and would like to co-sign. Yi (China Mobile) replies. Rainer (Nokia) replies Jari (NTT DOCOMO) provides r03 George (Ericsson) asks questions. Yi (China Mobile) replies and provides r04. Jari (NTT DOCOMO) responds to George George (Ericsson) requests that EN be added for the first bullet and the complete list of sessions upgrades and/or downgrades. Yi (China Mobile) provides r05. ==== Revisions Deadline ==== George (Ericsson) Accepts R05 ONLY DongYeon (Samsung) supports r05, and would like to cosign. Yi (China Mobile) thanks to DongYeon and will add Samsung in the submission version. Rainer (Nokia) ok with r05 ==== Final Comments Deadline ==== | Revised |
| 19.2 | S2-2401606 | P-CR | Approval | 23.700-77: KI #6, New sol: Standalone data channel without extra subscription. | China Mobile, NTT DOCOMO, Huawei, Hisilicon, Samsung | Rel-19 | Revision of S2-2400332r05, merging S2-2401234. Approved | Approved | |
| 19.2 | S2-2400867 | P-CR | Approval | 23.700-77: New solution to support standalone bootstrap data channel. | Vivo | Rel-19 | r04 Agreed. Revised to S2-2401607. | George Foti (Ericsson) provides comments DongYeon (Samsung) provides comments. Yi (China Mobile) think this can be merged into 0332. James Jin (vivo) replies comments from Yi (China Mobile) James Jin(vivo) reply comments from George Foti (Ericsson) Rainer (Nokia) provides comments James Jin (vivo) replies comments from Rainer (Nokia) and provides r01 George (Ericsson) provides comments James Jin (vivo) replies comments from Yi (China Mobile) and provides r02 Yi (China Mobile) agree to merge the standalone bootstrap DC part in 0332 into this contribution. Mu (Huawei) Comments. The original title is wrong, suggesting sending the revision under the right title. Proposed an EN George (Ericsson) provides a comment James Jin (vivo) replies comments from Mu (huawei), George(Ericsson) and provides r04 Kefeng (Qualcomm) asks clarification for the use case of this paper. James Jin (vivo) replies Kefeng (Qualcomm) ==== Revisions Deadline ==== George (Ericsson) Accepts R04 ONLY. Rainer (Nokia) ok with r04 ==== Final Comments Deadline ==== | Revised |
| 19.2 | S2-2401607 | P-CR | Approval | 23.700-77: New solution to support standalone bootstrap data channel. | Vivo, China Mobile | Rel-19 | Revision of S2-2400867r04. Approved | Approved | |
| 19.2 | S2-2400899 | P-CR | Approval | 23.700-77: KI#6: Update on Standalone DC Negotiation. | ZTE | Rel-19 | Approved | George Foti (Ericsson) provides comments Hao (ZTE) responds. Rainer (Nokia) replies Hao (ZTE) responds to Rainer (Nokia). George (Ericsson) asks a question Hao (ZTE) responds to George. ==== Revisions Deadline ==== George (Ericsson) Accepts the original revision. Rainer (Nokia) ok with r00 ==== Final Comments Deadline ==== | Approved |
| 19.2 | S2-2401005 | P-CR | Approval | 23.700-77: New solution on standalone IMS DC sessions. | Qualcomm Incorporated | Rel-19 | r01 Agreed. Revised to S2-2401608. | DongYeon (Samsung) provides comments George Foti (Ericsson) provides comments Kefeng (Qualcomm) replies George Foti (Ericsson) and DongYeon (Samsung) Rainer (Nokia) comments Kefeng (Qualcomm) replies Rainer (Nokia) comments and provides r01. ==== Revisions Deadline ==== George (Ericsson) Accepts R01 ONLY. Rainer (Nokia) ok with r01 ==== Final Comments Deadline ==== | Revised |
| 19.2 | S2-2401608 | P-CR | Approval | 23.700-77: New solution on standalone IMS DC sessions. | Qualcomm Incorporated | Rel-19 | Revision of S2-2401005r01. Approved | Approved | |
| 19.2 | S2-2401234 | P-CR | Approval | 23.700-77: 23.700-77: KI#8, New Sol: Standalone Application Data Channel Setup Signalling Procedure without accompanying bootstrap data channel . | Samsung | Rel-19 | Merged into S2-2401606 | George Foti (Ericsson) provides comments James Jin(vivo) provides comments Yi (China Mobile) comments. Kefeng (Qualcomm) provides comments. Rainer (Nokia) comments George (Ericsson) provides comment. DongYeon (Samsung) replies to George (Ericsson), James (Vivo), Yi (China Mobile), Kenfeng (Qualcomm), Rainer (Nokia), and provides r01. ==== Revisions Deadline ==== George (Ericsson) proposes to merge this into pCR 332. There are too many commonalities. DongYeon (Samsung) agrees to merge this paper into S2-2400332r05. ==== Final Comments Deadline ==== | Merged |
| 19.2 | - | - | - | Solutions to KI#7 | - | - | Docs:=1 | - | |
| 19.2 | S2-2400330 | P-CR | Approval | 23.700-77: KI #7, New sol: Multiplexing a single data channel SDP media description for multiple data channels. | China Mobile | Rel-19 | Noted | DongYeon (Samsung) provides comments George Foti (Ericsson) provides comments Kefeng (Qualcomm) provides comments James Jin(vivo) provides comments Rainer (Nokia) provides comments ==== Revisions Deadline ==== George (Ericsson) proposes to note the pCR. Rainer (Nokia) agrees to note. ==== Final Comments Deadline ==== | Noted |
| 19.2 | - | - | - | Solutions to KI#8 | - | - | Docs:=10 | - | |
| 19.2 | S2-2400679 | P-CR | Approval | 23.700-77: KI#8: New solution for early capability negotiation between UEs for IMS Avatar Communication. | NTT DOCOMO | Rel-19 | Postponed | DongYeon (Samsung) provides comments George Foti (Ericsson) provides comments Kefeng (Qualcomm) provides comments Atsushi (NTT DOCOMO) provides comments Rainer (Nokia) provides comments Atsushi (NTT DOCOMO) provides second comments Atsushi (NTT DOCOMO) is fine to postpone this pCR. ==== Revisions Deadline ==== | Postponed |
| 19.2 | S2-2400869 | P-CR | Approval | 23.700-77: KI #8, New Sol Capability negotiation between UE and IMS network. | Vivo | Rel-19 | Noted | George Foti (Ericsson) provides comments DongYeon (Samsung) provides comments Kefeng (Qualcomm) corrected e-mail title and provides comments Rainer (Nokia) provides comments Xiaowen Sun (vivo) responds to George, Rainer, Kenny and Dongyeon. Rainer (Nokia) replies to Xiaowen Mu (Huawei) comments Xiaowen (vivo) replies to Rainer (Nokia) Xiaowen (vivo) responds to Mu (Huawei) ==== Revisions Deadline ==== George (Ericsson) proposes to note the CR. Rainer (Nokia) ok note or postpone ==== Final Comments Deadline ==== | Noted |
| 19.2 | S2-2400898 | P-CR | Approval | 23.700-77: Add Avatar Communication Related Definitions. | ZTE | Rel-19 | r01 Agreed. Revised to S2-2401609. | Rainer (Nokia) comments Hao (ZTE) responds and provides r01. ==== Revisions Deadline ==== George (Ericsson) Accepts R01 Rainer (Nokia) ok with r01 ==== Final Comments Deadline ==== | Revised |
| 19.2 | S2-2401609 | P-CR | Approval | 23.700-77: KI#1: Add Avatar Communication Related Definitions. | ZTE | Rel-19 | Revision of S2-2400898r01. Approved | Approved | |
| 19.2 | S2-2400901 | P-CR | Approval | 23.700-77: KI #8, New Sol: Transition Between Avatar and Audio/Video Communication. | ZTE | Rel-19 | Postponed | DongYeon (Samsung) provides comments George Foti (Ericsson) provides comments, and suggest merging between Nokia 1277 and this one Kefeng (Qualcomm) provides comments Hao (ZTE) responds and provided r01. Rainer (Nokia) provides comments Hao (ZTE) responds to Rainer (Nokia). Rainer (Nokia) replies Hao (ZTE) provides further answers and revision r02. George (Ericsson) provides additional comments Hao (ZTE) responds and provides r03. ==== Revisions Deadline ==== Kefeng (Qualcomm) proposes to postpone the solution. Hao (ZTE) responds to George (Ericsson) and proposes to approve r03. George (Ericsson) proposes to postpone the pCR Rainer (Nokia) is ok with r03 ==== Final Comments Deadline ==== | Postponed |
| 19.2 | S2-2400983 | P-CR | Approval | 23.700-77: 23.700-77: KI#8, New Sol: Support of capability negotiation between UE and IMS network for Avatar communication . | Samsung | Rel-19 | Postponed | George Foti (Ericsson) ask if there are more definitions missing and need to be added Kefeng (Qualcomm) provides comments Rainer (Nokia) asks for clarification DongYeon (Samsung) replies and provides r01. ==== Revisions Deadline ==== Kefeng (Qualcomm) proposes to postpone the pCR George (Ericsson) proposes to postpone the pCR DongYeon (Samsung) agrees to postpone. ==== Final Comments Deadline ==== | Postponed |
| 19.2 | S2-2400984 | P-CR | Approval | 23.700-77: 23.700-77: KI#8, New Sol: Support of Avatar store and access in IMS . | Samsung | Rel-19 | Postponed | George Foti (Ericsson) provides comments Kefeng (Qualcomm) provides comments DongYeon (Samsung) responds to George Foti (Ericsson), and provides r01. Mu (Huawei) ask for clarification Rainer (Nokia) asks for clarification DongYeon (Samsung) replies to Kenfeng (Qualcomm) DongYeon (Samsung) replies to Mu (Huawei) DongYeon (Samsung) provides r02, and replies to Rainer (Nokia). Mu (Huawei) further comments Hao (ZTE) comments on r02. DongYeon (Samsung) replies to Mu (Huawei), and provides r03. ==== Revisions Deadline ==== George (Ericsson) proposes to note the pCR Rainer (Nokia) proposes to postpone ==== Final Comments Deadline ==== | Postponed |
| 19.2 | S2-2401277 | P-CR | Approval | 23.700-77: KI#8: New solution on Support of IMS Avatar Communication using data channel. | Nokia, Nokia Shanghai Bell | Rel-19 | r01 Agreed. Revised to S2-2401610. | DongYeon (Samsung) provides comments George Foti (Ericsson) provides comments Kefeng (Qualcomm) provides comments Rainer (Nokia) provides r01. ==== Revisions Deadline ==== George (Ericsson) Accepts R01 ONLY ==== Final Comments Deadline ==== | Revised |
| 19.2 | S2-2401610 | P-CR | Approval | 23.700-77: KI#8: New solution on Support of IMS Avatar Communication using data channel. | Nokia, Nokia Shanghai Bell | Rel-19 | Revision of S2-2401277r01. Approved | Approved | |
| 19.2 | S2-2401278 | P-CR | Approval | 23.700-77: KI#8: New solution on Support of IMS Avatar Communication without using data channel. | Nokia, Nokia Shanghai Bell | Rel-19 | Not Handled | DongYeon (Samsung) sees it should be marked as 'Not handled' ==== Final Comments Deadline ==== | Not Handled |
| 19.3 | - | - | - | Extended Reality and Media service (XRM) Phase 2 (FS_XRM Ph2) | - | - | Docs:=103 | - | |
| 19.3 | - | - | - | New Key Issues | - | - | Docs:=5 | - | |
| 19.3 | S2-2400175 | P-CR | Approval | 23.700-70: KI#X: Enhancement for UE with the tethered devices. | Vivo, China Telecom, Lenovo, MediaTek, Tencent, Tencent Cloud, China Mobile, Meta USA, Apple, Nokia, Nokia Shanghai Bell, Samsung, Charter Communications, CableLabs, Xiaomi | Rel-19 | r02 Agreed. Revised to S2-2401466. | Hui (Huawei) provides comments. Rahil (CableLabs) provides comments and replies to Hui (Huawei). Xiaowan Ke(vivo) replies Hui (Huawei) and Rahil (CableLabs) Sebastian (Qualcomm) provides r01 Lei(Tencent) provides comments and prefer r00. Xiaowan Ke(vivo) provides r02 Georgios (Nokia) supports r02 Youngkyo(Samsung) questions to Georgios Boren (OPPO) comments. Xiaowan(vivo) replies to Boren (OPPO) comments. Xiaowan Ke(vivo) agrees Youngkyo(Samsung) and replies to Georgios (Nokia) ==== Revisions Deadline ==== Georgios (Nokia) proposes to proceed with r02 Paul R (Charter) agrees to proceed with r02 Rahil (CableLabs) is ok with r02. ==== Final Comments Deadline ==== | Revised |
| 19.3 | S2-2401466 | P-CR | Approval | 23.700-70: KI#X: Enhancement for UE with the tethered devices. | Vivo, China Telecom, Lenovo, MediaTek, Tencent, Tencent Cloud, China Mobile, Meta USA, Apple, Nokia, Nokia Shanghai Bell, Samsung, Charter Communications, CableLabs, Xiaomi | Rel-19 | Revision of S2-2400175r02. Approved | Approved | |
| 19.3 | S2-2400592 | P-CR | Approval | 23.700-70: Key issue for WT4: Enhancement for XR related network information exposure . | China Mobile, Xiaomi, Samsung, Tencent | Rel-19 | Revision of (unhandled) S2-2312645. r03 Agreed. Revised to S2-2401467. | Sebastian (Qualcomm) provides r01 Devaki (Nokia) provides r02 to remove the redundant copy/paste text, also support the KI as indicated prior to submission already. Paul (Ericsson) provides r03, rewording slightly the key issue and adding notes for further clarification. Dan (China Mobile) comment on r03 and provide r04 Hui (Huawei) support to go with r02. Mengzhen (China Telecom) shares Hui (Huawei)'s view. Tingyu (Samsung) support r04. Paul (Ericsson) provides comments. Dan (China Mobile) provides r05 Hui (Huawei) provides r06 ==== Revisions Deadline ==== Paul (Ericsson) we can only accept r03 and object to all other revisions. Dan(China Mobile) compromise to accept r03 Tingyu (Samsung) can live with r03. ==== Final Comments Deadline ==== | Revised |
| 19.3 | S2-2401467 | P-CR | Approval | 23.700-70: Key issue for WT4: Enhancement for XR related network information exposure . | China Mobile, Xiaomi, Samsung, Tencent | Rel-19 | Revision of S2-2400592r03. Approved | Approved | |
| 19.3 | S2-2400358 | P-CR | Approval | 23.700-70: New KI: WT-3, Support of PDU Set Based QoS Handling when ATSSS is Enabled and L4S when ATSSS is Enabled. | InterDigital Inc., CableLabs, Charter Communications, Lenovo | Rel-19 | Revision of (unhandled) S2-2312380. Noted | Xiaowan Ke(vivo) comments the new KI seems not in the scope of rel19 XRM_ph2 Youngkyo(Samsung) shares the view of Xiaowan Ke(vivo) Dan(China Mobile) share the view of vivo and Samsung, and think this KI is out of R19 scope. Sebastian (Qualcomm) objects to the pCR Mike (InterDigital) replies and provides r01 Rahil (CableLabs) provides comments and support this pCR. Hui (Huawei) share the view that this is not in the scope. Mike (InterDigital) comments Rahil (CableLabs) provides comments. Lei (Tencent) propose to go with r01. ==== Revisions Deadline ==== Sebastian (Qualcomm) objects also to r01 Georgios (Nokia) agrees with Sebastian Paul R (Charter) supports this pCR (r00) and can accept r01 Hui(Huawei) proposes to note or postpone this paper. Rahil (CableLabs) supports this pCR (r00) and can accept limited scope as in r01. ==== Final Comments Deadline ==== | Noted |
| 19.3 | - | - | - | Architecture requirements and assumptions | - | - | Docs:=1 | - | |
| 19.3 | S2-2400373 | P-CR | Approval | 23.700-70: TR 23.700-70: Updates to Architectural Requirements. | Ericsson | Rel-19 | Noted | Xiaowan Ke(vivo) corrects the email thread title Jari (NTT DOCOMO) the new bullet should be an evaluation criteria Youngkyo(Samsung) shares the previous view also. Mike (InterDigital) agrees with Jari (NTT Docomo) Dan(China Mobile) suggest to NOTE this paper. Sebastian (Qualcomm) shares the view expressed by others and objects to the pCR Devaki (Nokia) shares the same view as others that this is an evaluation criteria, objects to the P-CR. ==== Revisions Deadline ==== | Noted |
| 19.3 | - | - | - | Solution proposals for Key Issue #1 | - | - | Docs:=18 | - | |
| 19.3 | S2-2400340 | P-CR | Approval | 23.700-70: New solution for KI#1, Discarding of PDUs. | Sony | Rel-19 | r05 Agreed. Revised to S2-2401468. | Boren (OPPO) provides comments. Mengzhen (China Telecom) asks for clarification Lizhuo (Lenovo) asks for clarification on Sony's paper. Hyunsook (LGE) asks a question. Saso (Intel) provides comments. Svante (Sony) provides answers. Jari (NTT DOCOMO) comments Svante (Sony) provides r01 and answers. Curt (Meta) asks..how RAN knows Protocol Descriptor ... Svante (Sony) answer Curt (Meta) and Mike (InterDigital) Mike (InterDigital) asks for a clarification. Curt (Meta) questioning the RAN implementation aspect... Jinhua (Xiaomi) comments for the clarifications Mukesh (MediaTek) provides comment. Dan (China Mobile) similar comment as Xiaomi Svante (Sony) answer Dan (China Mobile), Jinhua (Xiaomi) and Curt (Meta) Youngkyo(Samsung) comments. Svante (Sony) answer Devaki (Nokia) Devaki (Nokia) comments Svante (Sony) answer Sebastian (Qualcomm) and provides r02 Sebastian (Qualcomm) comments Svante (Sony) answers Youngkyo (Samsung) and provides r03 Mukesh (MediaTek) replies to Sebastian (Qualcomm) regarding the reliability of the HARQ feedback Pau (Ericsson) for the reasons explained in the thread on S2-2400846, we have concerns also with this proposal. Paul (Ericsson) provides r05. Svante (Sony) replies to Paul (Ericsson) on r05. ==== Revisions Deadline ==== Jinhua replies to Svante, r05 is OK. Paul (Ericsson) replies, we can only accept r05 and object to all other revisions. ==== Final Comments Deadline ==== | Revised |
| 19.3 | S2-2401468 | P-CR | Approval | 23.700-70: New solution for KI#1, Discarding of PDUs. | Sony | Rel-19 | Revision of S2-2400340r05. Approved | Approved | |
| 19.3 | S2-2401037 | P-CR | Approval | 23.700-70: KI#1, New Sol: PDU Set Information marking to support RAN s other PDU Set QoS handling different from the handling for PSDB/PSER/PSIHI . | Vivo | Rel-19 | r02 Agreed. Revised to S2-2401469. | Jari (NTT DOCOMO) comments Xiaowan Ke(vivo) provides replies Jari (NTT DOCOMO) Haley(Lenovo) asks for clarification. Jari (NTT DOCOMO) further comments and questions. Xiaowan(vivo) replies to Haley(Lenovo). Haley(Lenovo) replies to Xiaowan(vivo). Xiaowan Ke(vivo) replies to Haley(Lenovo) Curt (Meta) asks - isn't this a feature control issue? Xiaowan Ke(vivo) replies Curt (Meta) and provides r01 Youngyo(Samsung) comments. Xiaowan (vivo) replies Youngyon(Samsung) Paul Ericsson) provides comments. Sebastian (Qualcomm) asks questions Xiaowan Ke(vivo) replies Youngyo(Samsung) Youngyo(Samsung) replies to Xiaowan Devaki (Nokia) comments. Jinhua (Xiaomi) comments, alternatives are proposed forward Youngkyo(Samsung) replies to Xiaowan and Jinhua. Xiaowan Ke(vivo) provides Youngkyo(Samsung) and Jinhua (Xiaomi) Xiaowan(vivo) replies to Devaki (Nokia) ,Sebastian (Qualcomm), Paul (Ericsson) and provide r02 ==== Revisions Deadline ==== Youngkyo(Samsung) replies to Xiaowan as your scenario is already considering other PDU Set QoS parameters such as PSDB and PSER other than PSIHI. My concern is not only for PSIHI but also any PDU Set QoS parameters. So my concern is not solved yet. Youngkyo(Samsung) is okay to discuss necessity of this solution later at the evaluation phase as Xiaowan mentioned before. Xiaowan(vivo) clarifies: after offline checking with Youngkyo(Samsung), what his previous email means: he is okay to live with this solution to be captured in the TR, and discuss necessity of this solution later at the evaluation phase. ==== Final Comments Deadline ==== | Revised |
| 19.3 | S2-2401469 | P-CR | Approval | 23.700-70: KI#1, New Sol: PDU Set Information marking to support RAN s other PDU Set QoS handling different from the handling for PSDB/PSER/PSIHI . | Vivo | Rel-19 | Revision of S2-2401037r02. Approved | Approved | |
| 19.3 | S2-2400097 | P-CR | Approval | 23.700-70: KI#1, New Sol: Support of Alternative QoS Profiles for PDU Set based QoS handling. | Tencent, Tencent Cloud | Rel-19 | r04 Agreed. Revised to S2-2401470, merging S2-2401209 | Lei(Tencent) provides comments to Lizhuo (Lenovo) about the question Lizhuo (Lenovo) asks a question Lei(Tencent) provides r01 considering comments received, also try to merge S2-2401209 as rapporteur suggested. Youngkyo(Samsung) questions for understanding. Hyunsook (LGE) asks a clarification on step 4. Jinhua(Xiaomi) comments for the AQPs clarification, Lei(Tencent) provides comments and propose to discuss relevant questions firstly in other paper's thread. Saso (Intel) comments on the usefulness of adding PSDB, PSER in the AQP. Jinhua(Xiaomi) replies to Lei, Lei(Tencent) replies Jinhua(Xiaomi) Lei(Tencent) provides response to Jinhua(Xiaomi), Saso (Intel), Hyunsook (LGE) and Youngkyo(Samsung). Also provide r02. Devaki (Nokia) comments. Jinhua (Xiaomi) replies to Devaki, provides r03, Lei(Tencent) thanks to Jinhua (Xiaomi) and provide r04 to make the text more clear. Jinhua (Xiaomi) replies to Lei, both r04 and r03 is OK for me. r03 is prefer. Lei(Tencent) thanks to Jinhua (Xiaomi) to confirm that both r04 and r03 are OK. Would like to go with r04 since QoS mapping is more accurate:-) ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 19.3 | S2-2401470 | P-CR | Approval | 23.700-70: KI#1, New Sol: Support of Alternative QoS Profiles for PDU Set based QoS handling. | Tencent, Tencent Cloud, Xiaomi | Rel-19 | Revision of S2-2400097r04, merging S2-2401209. Approved | Approved | |
| 19.3 | S2-2400251 | P-CR | Approval | 23.700-70: KI#1, NewSol: PDU Set FEC-based PDU Set QoS Handling. | CATT | Rel-19 | CC#4: r05 + changes agreed. Revised to S2-2401838. | Boren (OPPO) comments. Mengzhen (China Telecom) asks a question about FEC in the radio interface Chunshan(CATT) provides clarification to Mengzhen (China Telecom) . Chunshan(CATT) provides clarification to Boren (OPPO). Svante (Sony) asks questions. Haley (Lenovo) asks for clarification. Chushan(CATT) provides clarification to Haley (Lenovo) . Chunshan (CATT) provides clarification to Svante (Sony) asks questions. Svante (Sony) comment. Lei(Tencent) provides comments. Haley (Lenovo) replies. Chunhan(CATT) provides clarification to Svante (Sony). Chunshan (CATT) provides comments to Lei(Tencent). Curt (Meta) asks a question on - what is FEC scheme. Chunshan(CATT) provides clarification to Curt (Meta). Mengzhen (China Telecom) replies to chunshan (CATT). Chunshan(CATT) provides r01 to add UE impact and FEC used in satellite communication as an example in radio interface. Youngkyo(Samsung) asks a question on why AF need request a level of PDU set FEC scheme/mode than its QoS requirement . Chunshan(CATT) provides clarification to Youngkyo(Samsung) . Sebastian (Qualcomm) suggests to add Editor's notes on open aspects Chunshan(CATT) provides clarification to Sebastian (Qualcomm) . Sebastian (Qualcomm) replies to Chunshan Chunshan(CATT) provides r02. Chunshan(CATT) provide clarification inline to Devaki (Nokia). Devaki (Nokia) comments Youngkyo(Samsung) replies . Paul (Ericsson) shares same view as Devaki (Nokia) that new FEC encoding by 5GS entities is not in the scope of this study. Chunshan(CATT) provides clarification to Paul. Hui (Huawei) provides comments. Svante (Sony) provides comments and ask Chunshan(CATT) question on r02 Curt (Meta) provides comments. Chunshan(CATT) provides r03. Chunshan(CATT) provides clarification to Curt (Meta) . Chunshan(CATT) provides clarification to Svante (Sony). Chunshan(CATT) provides clarification on Hui (Huawei) . Mukesh (MediaTek) provides r04. Svante (Sony) comment and have question to Chunshan(CATT). Chunshan (CATT) provides clarification to Svante (Sony). Svante (Sony) answers Chunshan (CATT). Paul (Ericsson) asks for clarification. Chunshan(CATT) provides clarification on Paul (Ericsson). ==== Revisions Deadline ==== Paul (Ericsson) PDCP, SDAP and other RAN layers are not in scope of SA2 or this study. Hence, we can't agree to any of the revisions that contain that aspect to be included in the TR. We object to all revisions of this solution. Chunshan(CATT) provides clarification to Paul (Ericsson) that there is no technical issues on the radio-interface FEC but can put your EN to the radio-interface FEC, and the application layer FEC in this paper can also be agreed into the TR.. Sebastian (Qualcomm) comments that r04 is only ok if two Editor' notes are added: 'Editor's note: How the core network/AF can know whether a request for FEC support for PDU Sets on Uu can be supported in UL direction is FFS.' and 'Editor's note: Details of FEC scheme information are FFS.' Chunshan(CATT) provides clarification to Sebastian (Qualcomm) that new texts have been added in the revision to clarify the FEC scheme can be FEC protection ratio. And the NG-RAN can provide notification including the list of FEC shceme supported by the NG-RAN and UE. And based such clarification the two ENs are not needed. I am OK to add Paul's EN if Paul agree to go . Sebastian (Qualcomm) can only accept r05 if the following EN is added 'Editor's note: How the core network/AF can know whether a request for FEC support for PDU Sets on Uu can be supported in UL direction is FFS.' ==== Final Comments Deadline ==== | Revised |
| 19.3 | S2-2401838 | P-CR | Approval | 23.700-70: KI#1, NewSol: PDU Set FEC-based PDU Set QoS Handling. | CATT | Rel-19 | Revision of S2-2400251r05 + changes. Approved | Approved | |
| 19.3 | S2-2400459 | P-CR | Approval | 23.700-70: Solution for KI#1: FEC mechanism and PSI based PDU Set QoS Handling Enhancement. | China Telecom | Rel-19 | r07 Agreed. Revised to S2-2401471. | Mengzhen (China Telecom) replys to Lei (Tencent) Hyunsook (LGE) provides a comment. Saso (Intel) provides a comment. Mengzhen (China Telecom) replies to Saso (Intel) and Hyunsook (LGE). Xiaowan Ke(vivo) suggests to use the correct title, otherwise your comment and revision cannot be counted Mengzhen (China Telecom) replies to Mukesh (MediaTek), correct the title to 2400459 again, and provides r02 again. John (Futurewei) provides comments. Mengzhen (China Telecom) replies to John (Futurewei) Mukesh (MediaTek) asks Mengzhen (China Telecom) how RAN can detect loss when the PDUs are sent over in unacknowledged mode. John (Futurewei) replies to Mengzhen (China Telecom) re: adaptive use of FEC Jinhua (Xiaomi) comments on the mapping between FEC ratios and PSI, whether applied to FEC packets Mengzhen (China Telecom) replies to Mukesh (MediaTek) and Lizhuo (Lenovo) Youngkyo(Samsung) need to confirm from SA4 that this AL-FEC can be considered and meaningful to XRM services. Mengzhen (China Telecom) provides r03 to reflect comments received online and offline. Mukesh (MediaTek) provides r04 Devaki (Nokia) comments Mengzhen (China Telecom) replies to Devaki (Nokia). Mengzhen (China Telecom) is OK with r04. Paul (Ericsson) for the reasons explained in the thread on S2-2400846, we have concerns also with this proposal. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 19.3 | S2-2401471 | P-CR | Approval | 23.700-70: Solution for KI#1: FEC mechanism and PSI based PDU Set QoS Handling Enhancement. | China Telecom, Lenovo | Rel-19 | Revision of S2-2400459r07. Approved | Approved | |
| 19.3 | S2-2400633 | P-CR | Approval | 23.700-70: KI#1: New Solution for enhancing the alternative QoS profile with UL and/or DL PDU set QoS parameters. | Lenovo | Rel-19 | r04 + changes Agreed. Revised to S2-2401472. | Devaki (Nokia) comments. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 19.3 | S2-2401472 | P-CR | Approval | 23.700-70: KI#1: New Solution for enhancing the alternative QoS profile with UL and/or DL PDU set QoS parameters. | Lenovo, Xiaomi, Samsung | Rel-19 | Revision of S2-2400633r04 + changes. Approved | Approved | |
| 19.3 | S2-2400846 | P-CR | Approval | 23.700-70: KI#1: New solution: PDU Set content ratio awareness at RAN. | Qualcomm Incorporated | Rel-19 | r06 Agreed. Revised to S2-2401473. | Youngkyo(Samsung) supports asking SA4 Mengzhen (China Telecom) asks a question Lei(Tencent) provides comments Youngkyo(Samsung) still need to confirm from SA4 that this AL-FEC can be considered and meaningful to XRM services. Sudeep (Apple) highlights a problem with UE power consumption if proactive dropping is performed by NG-RAN. Mike (InterDigital) asks a question Lei(Tencent) respond to Youngkyo(Samsung). Sebastian (Qualcomm) replies to Mengzhen that SA4 documented that Commercial XR split rendering and cloud gaming services use Application Layer Forward Error Correction (FEC) as documented TR 26.926 clause 5.7.4. Mukesh (MediaTek) provides comment. Sebastian (Qualcomm) replies to Lei Sebastian (Qualcomm) replies to Mike Sebastian (Qualcomm) replies to Youngkyo Sebastian (Qualcomm) replies to Sudeep and provides r01 Jinhua (Xiaomi) comments, whether apply for the encrypted traffics, and one Note proposed for the RaptorQ Devaki (Nokia) comments Devaki (Nokia) comments. Jinhua (Xiaomi) replies to Sebastian, and comments on the notification of discarding Youngkyo(Samsung) replies to Lei and Sebastian. Sebastian (Qualcomm) replies to Jinhua Sebastian (Qualcomm) replies to Jinhua(Xiaomi) Sebastian (Qualcomm) replies to Devaki (Nokia) and provides r02 Paul (Ericsson) asks for clarification on the second proposal (application increases bandwidth requirement based on lost packets) and comments on the usage of FEC by unicast. Another question is raised asking to clarify the use case where delivering/using application layer redundancy (FEC) with NG-RAN for uni-cast is useful. Sebastian (Qualcomm) replies to Paul and provides r03 Jinhua (Xiaomi) replies to Sebastian, r02 is OK for me. John (Futurewei) agrees with adaptation to loss raised by Paul (Ericsson). Sebastian (Qualcomm) replies to John Mukesh (MediaTek) provides r04 Paul (Ericsson) replies to Sebastian and clarifies that same concerns as being discussed in the thread on this document are valid for all FEC proposals submitted, i.e., S2-2400340, S2-2400251, S2-2400459. Sebastian (Qualcomm) responds to Paul (Ericsson) Jari (NTT DOCOMO) comments Sebastian (Qualcomm) replies to Jari Paul (Ericsson) provides r05. Sebastian (Qualcomm) replies to Paul and provides r06 Paul (Ericsson) can accept r06. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 19.3 | S2-2401473 | P-CR | Approval | 23.700-70: KI#1: New solution: PDU Set content ratio awareness at RAN. | Qualcomm Incorporated | Rel-19 | Revision of S2-2400846r06. Approved | Approved | |
| 19.3 | S2-2401209 | P-CR | Approval | 23.700-70: KI#1_New Sol_ Enhancement of AQP with PDU Set QoS Parameters. | Xiaomi | Rel-19 | Merged into S2-2401470 | Youngkyo(Samsung) questions the status of this paper. If not merged, suggest to adding EN for HO consideration for further study. Lei(Tencent) replies to Youngkyo(Samsung) and clarifies this paper was suggested by rapporteur to merged to S2-2400097 and some of the content has been merged there. Jinhua (Xiaomi) replies to Youngkyo and Lei. It is confirmed that 1209 can be merged in 0097 for discussion. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 19.3 | S2-2401172 | P-CR | Approval | 23.700-70: KI#1 - Solution for Consistent PDU Set Handling between AF and 5GS. | Nokia, Nokia Shanghai Bell | Rel-19 | r04 Agreed. Revised to S2-2401474. | Sudeep (Apple) seeks clarification. Saso (Intel) seeks clarification. Devaki (Nokia) replies to Sudeep (Apple) and Saso (Intel). Xiaowan Ke(vivo) provides comments Youngkyo(Samsung) questions. Devaki (Nokia) provides r01 to add EN as proposed by Curt (Meta). Curt (Meta) asks to have a EN w.r.t UL direction. Devaki (Nokia) provides r02 to address comments raised. Jari (NTT DOCOMO) provides r03 Xiaowan Ke(vivo) provides comment and r04 Devaki (Nokia) can live with r04. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 19.3 | S2-2401474 | P-CR | Approval | 23.700-70: KI#1 - Solution for Consistent PDU Set Handling between AF and 5GS. | Nokia, Nokia Shanghai Bell | Rel-19 | Revision of S2-2401172r04. Approved | Approved | |
| 19.3 | S2-2400551 | P-CR | Approval | 23.700-70: KI#1, New Sol: Applying the different PDU set QoS parameters according to PDU Set Importance. | LG Electronics | Rel-19 | Noted | Hui (Huawei) provides comments. Paul (Ericsson) provides comments and has concerns with the proposal. Hyunsook (LGE) replies. ==== Revisions Deadline ==== Paul (Ericsson) object to this solution in all revisions. Hui (Huawei) proposes to note or postpone this solution. ==== Final Comments Deadline ==== | Noted |
| 19.3 | - | - | - | Solution proposals for Key Issue #2 | - | - | Docs:=8 | - | |
| 19.3 | S2-2400786 | P-CR | Approval | 23.700-70: KI#2 and KI#4: Solution for encrypted traffic detection and identification. | Huawei, HiSilicon, InterDigital Inc. | Rel-19 | r02 Agreed. Revised to S2-2401675. | Jari (NTT DOCOMO) comments Xinpeng(Huawei) replies to Jari (NTT DOCOMO). Mukesh (MediaTek) wonders whether MoQ is mature for SA2 consideration Sudeep (Apple) has question on whether MoQ Relay concept can work well in dynamic 5G UP setup. Saso (Intel) seeks clarification. Xinpeng(Huawei) replies to Saso (Intel). Xinpeng(Huawei) replies to Xiaowan Ke(vivo). Xinpeng(Huawei) provides r01. Xiaowan Ke(vivo) provides comments Xinpeng(Huawei) replies to Mukesh (MediaTek). Jari (NTT DOCOMO) provides r02. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 19.3 | S2-2401675 | P-CR | Approval | 23.700-70: KI#2 and KI#4: Solution for encrypted traffic detection and identification. | Huawei, HiSilicon, InterDigital Inc, NTT DOCOMO. | Rel-19 | Revision of S2-2400786r02. Approved | Approved | |
| 19.3 | S2-2400754 | P-CR | Approval | 23.700-70: (KI#2) Solution for e2e encrypted XRM traffic detection and identification. | Rel-19 | r02 Agreed. Revised to S2-2401676. | Dimitris (Lenovo) comments Ellen (Google) provides feedback Sudeep (Apple) provides comments. Mukesh (MediaTek) provides comment. Saso (Intel) seeks clarification. Xiaowan Ke(vivo) provides comments Ellen (Google) provides feedback to Mukesh Ellen (Google) replies to Saso and provides r01 <https://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_160AHE_Electronic_2024-01/INBOX/Revisions/S2-2400754r01.zip> Ellen (Google) provides r02 and feedback to Xiaowan Ellen (Google) replies Devaki (Nokia) Devaki (Nokia) has concerns with the UDP option as proposed in this solution. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised | |
| 19.3 | S2-2401676 | P-CR | Approval | 23.700-70: (KI#2) Solution for e2e encrypted XRM traffic detection and identification. | Rel-19 | Revision of S2-2400754r02. Approved | Approved | ||
| 19.3 | S2-2400235 | P-CR | Approval | 23.700-70: KI#2: New Sol: Encrypted XRM Traffic Handling using Obfuscated Metadata. | Futurewei, Tencent | Rel-19 | r03 Agreed. Revised to S2-2401677. | Jari (NTT DOCOMO) questions for clarification Curt (Meta) questions for clarification w.r.t UL. John (Futurewei) replies to Curt (Meta) w.r.t. UL updates in r01 John (Futurewei) replies to Jari (NTT DOCOMO) and provides r01. Saso (Intel) comments Jari (NTT DOCOMO) comments John (Futurewei) replies to Jari (NTT DOCOMO) adds text on N3 in r02 John (Futurewei) replies to Saso (Intel) clarifies about 5-tuple/mapping, uplink, EN on security, and provides r02. Lei(Tencent) share the view with John (Futurewei). John (Futurewei) clarifies to Devaki (Nokia) that this solution is technically feasible and should be captured and evaluated later. Devaki (Nokia) comments. John (Futurewei) replies to Devaki (Nokia) and provides r03. ==== Revisions Deadline ==== Spencer (Tencent) confirms that Tencent does support both the UDP options proposal and the RTP over QUIC proposal as valuable subjects for study in XRM_ph2. Spencer (Tencent) replies to Devaki (Nokia) that the understanding of IETF support for the underlying proposal described in the earlier email is incomplete. Based on a more complete understanding, Tencent thinks SA2 should document and evaluate this proposal along with other solutions for KI#2 ==== Final Comments Deadline ==== | Revised |
| 19.3 | S2-2401677 | P-CR | Approval | 23.700-70: KI#2: New Sol: Encrypted XRM Traffic Handling using Obfuscated Metadata. | Futurewei, Tencent | Rel-19 | Revision of S2-2400235r03. Approved | Approved | |
| 19.3 | S2-2400600 | P-CR | Approval | 23.700-70: New Sol for WT2: Solution for PDU Set information Identification for end-to-end encrypted traffic. | China Mobile | Rel-19 | Revision of (unhandled) S2-2312974. r03 Agreed. Revised to S2-2401678. | Saso (Intel) seeks clarification. Mukesh (MediaTek) ask how and why Connection ID is shared between UE and UPF Curt (Meta) asks few clarification questions. Dan (China Mobile) reply. Dan (China Mobile) reply and want to check further with the question Dan (China Mobile) provide r02, please ignore r01 Haley(Lenovo) asks for clarification. Dan(China Mobile)reply Dan(China Mobile) reply Devaki (Nokia) comments. Dan(China Mobile) further reply Dan (China Mobile) correct the link of r02 Dan (China Mobile) provide r03 with adding an EN ==== Revisions Deadline ==== Dan (China Mobile) suggest to go with r03 Devaki (Nokia) comments r03 is fine. ==== Final Comments Deadline ==== | Revised |
| 19.3 | S2-2401678 | P-CR | Approval | 23.700-70: New Sol for WT2: Solution for PDU Set information Identification for end-to-end encrypted traffic. | China Mobile | Rel-19 | Revision of S2-2400600r03. Approved | Approved | |
| 19.3 | - | - | - | Solution proposals for Key Issue #3 | - | - | Docs:=2 | - | |
| 19.3 | S2-2400079 | P-CR | Approval | 23.700-70: KI#3, New Sol: Multiple DSCP markings per QoS Flow. | Intel | Rel-19 | Revision of (Unhandled) S2-2312347. r07 Agreed. Revised to S2-2401679. | Saso (Intel) provides r01. Mengzhen (China Telecom) comments that the End of data burst indication may not be reflect in DSCP marking enhancement. Mengzhen (China Telecom) adds one additional comment. Saso (Intel) replies to Mengzhen (China Telecom). John (Futurewei) agrees with Mike (Interdigital) on recommending DSCP marking to only vary drop probability. Mike (InterDigital) replies and provides r02 Saso (Intel) provides r03 Mirko (Huawei) comments. Mengzhen (China Telecom) comments. Xiaowan Ke(vivo) provides comments Dan (China Mobile) provide comment Youngkyo(Samsung) provides comment. Devaki (Nokia) provides r05 (ignore r04) to merge other variants. Haley (Lenovo) comments. Saso (Intel) provides r06. Saso (Intel) replies to Youngkyo. Saso (Intel) replies to Haley. Mengzhen (China Telecom) provides r07, adding China Telecom as the cosigner. Mike (InterDigital) comments ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 19.3 | S2-2401679 | P-CR | Approval | 23.700-70: KI#3, New Sol: Multiple DSCP markings per QoS Flow. | Intel, InterDigital Inc., Nokia, Nokia Shanghai Bell, China Telecom | Rel-19 | Revision of S2-2400079r07. Approved | Approved | |
| 19.3 | - | - | - | Solution proposals for Key Issue #4 | - | - | Docs:=7 | - | |
| 19.3 | S2-2400772 | P-CR | Approval | 23.700-70: Solution for KI#3 and #4: differentiated handling for multiplexed data flows in a QoS flow. | Samsung | Rel-19 | Noted | Youngkyo(Samsung) replies. Lizhuo(Lenovo) comments: Mukesh (MediaTek) seeks clarification Curt (Meta) asks for similar clarification as MTK Sebastian (Qualcomm) comments Xiaowan Ke(vivo) comments Youngkyo(Samsung) provides the revision r01. Georgios (Nokia) provides comments Paul (Ericsson) provides comments. We have concerns with that solution as it is does not respect basic QoS Framework principles. Youngkyo(Samsung) replies to Georgios and Paul, and provides r02. Mukesh (MediaTek) agrees with Georgios (Nokia) to note this solution. ==== Revisions Deadline ==== | Noted |
| 19.3 | S2-2401193 | P-CR | Approval | 23.700-70: KI#4 Solution for separate QoS Flows for PDU Set QoS and PDU QoS. | Nokia, Nokia Shanghai Bell | Rel-19 | Postponed | Youngkyo(Samsung) questions. Jari (NTT DOCOMO) provides r01 Mukesh (MediaTek) request to postpone this pCR to Athens due to the lack of time to discuss the impact especially on UE and RAN. Georgios (Nokia) replies to Youngkyo Georgios (Nokia) provides r02 Georgios (Nokia) replies to Mukesh Paul (Ericsson) asks to postpone this CR. Jari (NTT DOCOMO) comments Georgios (Nokia) replies to Paul ==== Revisions Deadline ==== Youngkyo(Samsung) shares Paul's view. Jari (NTT DOCOMO) supports the proposal Georgios (Nokia) replies and proposes to proceed with r02 | Postponed |
| 19.3 | S2-2401154 | P-CR | Approval | 23.700-70: KI#4, New Sol: Extending Packet Filter Set to identify multiplexed traffic flows within a single transport connection. | OPPO | Rel-19 | r05 Agreed. Revised to S2-2401680. | Sebastian (Qualcomm) provides r01 Curt (Meta) requests to add the following texts/EN... Xinpeng(Huawei) asks question for clarification. Boren (OPPO) provides r02 on top of r01, capturing the texts/EN as requested by Curt (Meta). Boren (OPPO) replies to Xinpeng(Huawei), and provides r03. Boren (OPPO) replies to Paul (Ericsson), and provides r05 . ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 19.3 | S2-2401680 | P-CR | Approval | 23.700-70: KI#4, New Sol: Extending Packet Filter Set to identify multiplexed traffic flows within a single transport connection. | OPPO, Lenovo | Rel-19 | Revision of S2-2401154r05. Approved | Approved | |
| 19.3 | S2-2400264 | P-CR | Approval | 23.700-70: KI#4, New Sol: Support of Traffic Detection and QoS mapping for XR and Media services. | Tencent, Tencent Cloud | Rel-19 | r03 + changes Agreed. Revised to S2-2401681. | Hongsuk (LGE) asks for clarification. Lei(Tencent) provide reply to Hongsuk (LGE) for clarification. Sebastian (Qualcomm) comments Hongsuk (LGE) comments. Lei(Tencent) provides comments to Hongsuk (LGE) and Sebastian (Qualcomm) and provide r01 as requested. Georgios (Nokia) provides comments Lei(Tencent) agree with Georgios (Nokia) comments and provide r03 to update the pCR. Lei(Tencent) clarifies that the latest revision should be r02 instead of r03. Paul (Ericsson) asks for clarification. Lei(Tencent) provides clarification to Paul (Ericsson) and provide r03 by adding EN to address this aspect. ==== Revisions Deadline ==== Paul (Ericsson) provides comments and further questions. Paul (Ericsson) object all revisions and asks to add one more (proposed) Editor's note. Lei(Tencent is ok with Paul (Ericsson) request, fine to go with 'r03 + EN: Whether there are (e.g. RTP) fields that can be used to identify stream requirements requires further discussion and probably SA4 involvement. It is also FFS whether and how those fields can be described in PDRs to UPF and rules to UE.' Lei(Tencent) uploaded r03 + EN => r04 in the DRAFT folder. Georgios (Nokia) r03, r04 are fine by me. r04 preferred if we could take it. Lei(Tencent) clarifies actually taking r03 +EN according to procedure, 04 is just a name in DRAFT folder. ==== Final Comments Deadline ==== | Revised |
| 19.3 | S2-2401681 | P-CR | Approval | 23.700-70: KI#4, New Sol: Support of Traffic Detection and QoS mapping for XR and Media services. | Tencent, Tencent Cloud | Rel-19 | Revision of S2-2400264r03 + changes. Approved | Approved | |
| 19.3 | S2-2401080 | P-CR | Approval | 23.700-70: KI#4: New Sol: Multiplexed streams using multi-modal procedures. | NTT DOCOMO | Rel-19 | Postponed | Xiaowan Ke(vivo) provides comments Jari (NTT DOCOMO) responds to Xiaowan Paul (Ericsson) provides comments. This solution requires more discussion before it can go into the TR. ==== Revisions Deadline ==== Jari (NTT DOCOMO) thanks Paul (Ericsson) for a very late comment Georgios (Nokia) proposes to include this solution in the TR | Postponed |
| 19.3 | - | - | - | Solution proposals for Key Issue #5 | - | - | Docs:=5 | - | |
| 19.3 | S2-2400253 | P-CR | Approval | 23.700-70: KI#5, New Sol: PDU Set Bit Rate Adaptation. | CATT | Rel-19 | Noted | Sang-Jun (Samsung) asks questions for clarification. Chunshan(CATT) provides clarification to Sang-Jun (Samsung) . Sebastian (Qualcomm) comments and provides r01 Chunshan(CATT) comments to Sebastian (Qualcomm) that the r01 has wrong content. Paul (Ericsson) asks for clarification what functionality ato update bitrates of a QoS Flow (MFBR/GFBR) is missing that this solution introduces? Please note that there is no such concept as 'PDU Set bitrate'. Georgios (Nokia) provides comments Chunshan(CATT) clarifies that the acceleration is only for short time (e.g. 5 s), there is no need to PDU Session modification procedure . Sebastian (Qualcomm) provides r01 (now with correct link) Saso (Intel) seeks clarification Chunshan(CATT) provides clarification Saso (Intel); Chunshan(CATT) provides r02 and further clarification on r02. Saso (Intel) asks for the clarification to be documented. Georgios (Nokia) comments Chunshan(CATT) clarifies that if the PDU Set Bitrate > GFBR/MFBR ,it will supersede. Georgios (Nokia) replies Chunshan(CATT) provides r03. . Chunshan(CATT) replies to Georgios (Nokia) . Georgios (Nokia) provides r04 Sebastian (Qualcomm) provides r05 ==== Revisions Deadline ==== Paul (Ericsson) objects to this solution in all revisions. ==== Final Comments Deadline ==== | Noted |
| 19.3 | S2-2401350 | P-CR | Approval | 23.700-70: KI#5: New Sol: AS based trigger of Data Boost for xR payload. | Meta USA | Rel-19 | r01 Agreed. Revised to S2-2401648. | Sang-Jun (Samsung) asks questions for clarification. Sebastian (Qualcomm) asks questions and provides r01 Curt (Meta) replies to Sebastian (Qualcomm) and Sang-Jun (Samsung). ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 19.3 | S2-2401648 | P-CR | Approval | 23.700-70: KI#5: New Sol: AS based trigger of Data Boost for xR payload. | Meta USA | Rel-19 | Revision of S2-2401350r01. Approved | Approved | |
| 19.3 | S2-2400822 | P-CR | Approval | 23.700-70: KI#5: New Sol: Support of dynamic change in traffic characteristics. | Huawei, HiSilicon | Rel-19 | Revision of (unhandled) S2-2312961. Noted | Sebastian (Qualcomm) comments and provides r01 Paul (Ericsson) provides comments and expresses concerns with this proposal. Hui (Huawei) fine with r01 Paul (Ericsson) asks for clarification. Hui (Huawei) replies to Paul. Curt (Meta) asks for some clarifications... Hui (Huawei) replies to Curt. ==== Revisions Deadline ==== Paul (Ericsson) this solution provides multiple values for a single QoS parameter which is not aligned with the QoS Framework and we object all revisions. Hui (Huawei) asks for the clarification. Paul (Ericsson) it refers to a range of values for MDBV, that in my interpretation is more than one value. In the QoS Framework there is a single value for a QoS parameter. ==== Final Comments Deadline ==== | Noted |
| 19.3 | S2-2401029 | P-CR | Approval | 23.700-70: KI#5: New Solution: Configurable PSDB for handling varying PDU Set sizes . | Apple | Rel-19 | Noted | Mukesh (MediaTek) seeks to understand the merits of having multiple PSDB values Youngkyo(Samsung) ask a question. Sebastian (Qualcomm) comments and provides r01 Paul (Ericsson) we have concerns with this proposal as it is not aligned with the basic principles of the QoS Framework. Dan (China Mobile) provide comment for clarification Mukesh (MediaTek) shares concerns raised by Paul (Ericsson) ==== Revisions Deadline ==== Sudeep (Apple) responds to comments. Paul (Ericsson) objects this solution in all revisions as per concerns raised earlier. ==== Final Comments Deadline ==== | Noted |
| 19.3 | - | - | - | Solution proposals for Key Issue #6 | - | - | Docs:=2 | - | |
| 19.3 | S2-2400919 | P-CR | Approval | 23.700-70: KI#6: New Solution: L4S support in non-3GPP untrusted/trusted accesses. | Charter Communications | Rel-19 | r07 + changes Agreed. Revised to S2-2401682. | Paul (Charter) provides r01 and r02 Saso (Intel) seeks clarification; provides comments. Hui (Huawei) provides comments. Georgios (Nokia) provides comments. Lei(Tencent) provides comments to Hui (Huawei) Paul R (Charter) reply to Saso's (Intel) and Hui (Huawei) comments/questions, and agree to leverage r02. Rahil (CableLabs) replies to Hui (Huawei). Lei (Tencent) provides comments and also think 5G-RG is an intermediate node. Paul R (Charter) agrees with Rahil's (CableLabs) response to Hui (Huawei) regarding 5G-RG support of ECN marking for L4S. Xiaowan Ke(vivo) provides comments Saso (Intel) follows up on Paul R's reply. Boren (OPPO) comments Sebastian (Qualcomm) provides r03 with ENs to capture open/unclear parts Hui (Huawei) requests to add ENs into the paper. Paul R (Charter) I am OK with r06, r07 (.rar) I could not open. Hui(Huawei) replies ==== Revisions Deadline ==== Paul R (Charter) I am OK with r07. Lei (Tencent) is also OK with r07. Youngkyo(Samsung) has concern on option1 of the clause 6.X.2.4.3 (Supporting L4S in UE) but I can accept r07 for now we may bring this issue in the next meeting due to quite late comment. Georgios (Nokia) proposes to proceed with r07 Paul R (Charter) supports r07 as indicated previously, but preference is r05 Sebastian (Qualcomm) prefers r07 Rahil (CableLabs) prefers r05, and can be ok with r07 with deleting 'Alternativ1' and 'Alternative2' in impacts on wireline section. Xiaowan(vivo) is OK for r06 and r07(r07 is preferred) and disagree the other revisions. Boren (OPPO) prefers r07 Paul R (Charter) proposes to agree with the proposal from Rahil (CableLabs), r7 +removal of Alternative 1 and Alternate 2 for Wireline impacted nodes. ==== Final Comments Deadline ==== | Revised |
| 19.3 | S2-2401682 | P-CR | Approval | 23.700-70: KI#6: New Solution: L4S support in non-3GPP accesses. | Charter Communications, CableLabs, Tencent, Tencent Cloud, Nokia, Nokia Shanghai Bell | Rel-19 | Revision of S2-2400919r07 + changes. Approved | Approved | |
| 19.3 | - | - | - | Solution proposals for Key Issue #7 | - | - | Docs:=2 | - | |
| 19.3 | S2-2400405 | P-CR | Approval | 23.700-70: KI#7: New Sol: Support PDU Set QoS in wireline access. | CableLabs, Charter Communications | Rel-19 | Revision of (unhandled) S2-2312145. r02 Agreed. Revised to S2-2401683. | Georgios (Nokia) provides r01 Hui (Huawei) fine with r01 Georgios (Nokia) comments Lei(Tencent) supports this pCR and co-signed in r02. ==== Revisions Deadline ==== Georgios (Nokia) proposes to proceed with r02 Paul R (Charter) also supports r02 Rahil (CableLabs) is ok with r02 for this meeting. ==== Final Comments Deadline ==== | Revised |
| 19.3 | S2-2401683 | P-CR | Approval | 23.700-70: KI#7: New Sol: Support PDU Set QoS in wireline/wireless non-3GPP access. | CableLabs, Charter Communications, Nokia, Nokia Shanghai Bell, Tencent, Tencent Cloud | Rel-19 | Revision of S2-2400405r02. Approved | Approved | |
| 19.3 | - | - | - | Documents exceeding TU budget | - | - | Docs:=53 | - | |
| 19.3 | S2-2400172 | P-CR | Approval | 23.700-70: WT#2.3, New Sol: Support of Handling for UE with Tethered Devices for XR and Media services. | Tencent, Tencent Cloud | Rel-19 | Not Handled | Not Handled | |
| 19.3 | S2-2400544 | P-CR | Approval | 23.700-70: KI#1, New Solution: PDU Set based QoS handling based on FEC Assistance Information. | InterDigital Inc. | Rel-19 | Not Handled | Not Handled | |
| 19.3 | S2-2400771 | P-CR | Approval | 23.700-70: Solution for KI#1: Admission control of QoS flow based on PDU Set QoS parameters. | Samsung | Rel-19 | Not Handled | Not Handled | |
| 19.3 | S2-2400078 | P-CR | Approval | 23.700-70: KI#2, New Sol: N6 tunnelling and GTP-U header extension for conveyance of PDU Set-related information. | Intel | Rel-19 | Revision of (Unhandled) S2-2312346 Not Handled | Not Handled | |
| 19.3 | S2-2400098 | P-CR | Approval | 23.700-70: KI#7, New Sol: Support of PDU Set based QoS handling for non-3GPP access networks. | Tencent, Tencent Cloud | Rel-19 | Not Handled | Not Handled | |
| 19.3 | S2-2400099 | P-CR | Approval | 23.700-70: KI#6, New Sol: Support of L4S mechanism for non-3GPP access networks and intermediate 5GS nodes. | Tencent, Tencent Cloud | Rel-19 | Not Handled | Not Handled | |
| 19.3 | S2-2400167 | P-CR | Approval | 23.700-70: WT#4, New Sol: XR related network information exposure to support application layer adaptation. | Tencent, Tencent Cloud | Rel-19 | Not Handled | Not Handled | |
| 19.3 | S2-2400182 | P-CR | Approval | 23.700-70: KI#1, New Sol: Enhancement of PDU Set based QoS handling for Application Layer Redundancy. | Tencent, Tencent Cloud | Rel-19 | Not Handled | Not Handled | |
| 19.3 | S2-2400244 | P-CR | Approval | 23.700-70: Update Architectural Assumptions. | CATT | Rel-19 | Not Handled | Not Handled | |
| 19.3 | S2-2400245 | P-CR | Approval | 23.700-70: Architectural Requirements. | CATT | Rel-19 | Not Handled | Not Handled | |
| 19.3 | S2-2400249 | P-CR | Approval | 23.700-70: KI#x, NewSol: Quick Exposure of Available Data Rate. | CATT, CMCC, Lenovo | Rel-19 | Not Handled | Not Handled | |
| 19.3 | S2-2400250 | P-CR | Approval | 23.700-70: KI#1, NewSol: Alternative QoS Profile with PDU Set QoS Parameters and Notification Control. | CATT | Rel-19 | Not Handled | Not Handled | |
| 19.3 | S2-2400252 | P-CR | Approval | 23.700-70: KI#1, New Sol: New PDU Set QoS Parameters for PDU Set Bit Rate Adaptation. | CATT | Rel-19 | Not Handled | Not Handled | |
| 19.3 | S2-2400254 | P-CR | Approval | 23.700-70: New Solution for KI#4: One QoS Flow for multiplexed data flows. | CATT | Rel-19 | Not Handled | Not Handled | |
| 19.3 | S2-2400374 | P-CR | Approval | 23.700-70: KI #5, New Sol: Signalling of dynamically updated traffic periodicity. | Ericsson | Rel-19 | Not Handled | Jari (NTT DOCOMO) questions for clarification ==== Revisions Deadline ==== | Not Handled |
| 19.3 | S2-2400402 | P-CR | Approval | 23.700-70: KI#6: New Sol: Support L4S in wireline access. | CableLabs, Charter Communications | Rel-19 | Revision of (unhandled) S2-2312144 Not Handled | Not Handled | |
| 19.3 | S2-2400460 | P-CR | Approval | 23.700-70: Solution for KI#3: PSI based DSCP marking per QoS flow. | China Telecom | Rel-19 | Not Handled | Not Handled | |
| 19.3 | S2-2400545 | P-CR | Approval | 23.700-70: KI#3, New Solution, DSCP Markings based on PDU Set Information. | InterDigital Inc., Futurewei, Charter Communications | Rel-19 | Not Handled | Not Handled | |
| 19.3 | S2-2400546 | P-CR | Approval | 23.700-70: KI#1, New Solution: Per-PDU Set Integrated Handling. | InterDigital Inc. | Rel-19 | Not Handled | Not Handled | |
| 19.3 | S2-2400547 | P-CR | Approval | 23.700-70: K#5, New Solution: QoS Flow Mapping Based on Rendition ID. | InterDigital Inc. | Rel-19 | Not Handled | Not Handled | |
| 19.3 | S2-2400595 | P-CR | Approval | 23.700-70: KI #1, New Sol: Alternative PDU Set QoS to support differentiated QoS handling for PDU Set . | China Mobile | Rel-19 | Not Handled | Not Handled | |
| 19.3 | S2-2400596 | P-CR | Approval | 23.700-70: KI #5, New Sol: Dynamic Change Indication of XR traffic for enhanced QoS Handling. | China Mobile | Rel-19 | Not Handled | Not Handled | |
| 19.3 | S2-2400632 | P-CR | Approval | 23.700-70: KI#4: New Solution for traffic detection and QoS flow mapping for multiplexed data flows based on QUIC . | Lenovo | Rel-19 | Not Handled | Not Handled | |
| 19.3 | S2-2400634 | P-CR | Approval | 23.700-70: KI#1: New solution for provisioning NG-RAN with FEC ratio for PDU discarding via CP or UP. | Lenovo | Rel-19 | Revision of (unhandled) S2-2312312 Not Handled | Not Handled | |
| 19.3 | S2-2400714 | P-CR | Approval | 23.700-70: KI 3: DSCP marking values for the PDU Set. | LG Electronics | Rel-19 | Not Handled | Not Handled | |
| 19.3 | S2-2400740 | P-CR | Approval | 23.700-70: TR 23.700-70 KI#2: Solution for Supporting PDU Set information Identification for end-to-end encrypted XRM traffic. | China Mobile | Rel-19 | Not Handled | Not Handled | |
| 19.3 | S2-2400773 | P-CR | Approval | 23.700-70: New KI:<Supporting UL traffic identification and QoS handling enhancement for devices tethered to UE>. | Samsung | Rel-19 | Not Handled | Not Handled | |
| 19.3 | S2-2400819 | P-CR | Approval | 23.700-70: KI#1: New Sol: Dynamic FEC based PDU Set QoS handling. | Huawei, HiSilicon | Rel-19 | Not Handled | Not Handled | |
| 19.3 | S2-2400820 | P-CR | Approval | 23.700-70: KI#1: New Sol: Error Concealment based PDU Set QoS handling. | Huawei, HiSilicon | Rel-19 | Not Handled | Not Handled | |
| 19.3 | S2-2400821 | P-CR | Approval | 23.700-70: KI#4: New Sol: Support of traffic detection and QoS mapping for RTP multiplexing. | Huawei, HiSilicon | Rel-19 | Revision of (unhandled) S2-2312960 Not Handled | Not Handled | |
| 19.3 | S2-2400823 | P-CR | Approval | 23.700-70: WT#4: New Sol: Exposure of QoS Notification Control with Alternative QoS Profile via User Plane . | Huawei, HiSilicon | Rel-19 | Not Handled | Not Handled | |
| 19.3 | S2-2400848 | P-CR | Approval | 23.700-70: KI#1: New solution: Nominal PDU Set Delay Budget. | Qualcomm Incorporated | Rel-19 | Not Handled | Not Handled | |
| 19.3 | S2-2400893 | P-CR | Approval | 23.700-70: New Key Issue: Enhancement to 5GS capability/information exposure based on WT#4. | CATT | Rel-19 | Not Handled | Not Handled | |
| 19.3 | S2-2400929 | P-CR | Approval | 23.700-70: Solution for KI#2: New solution for supporting PDU set identification when an end-to-end XR session is fully encrypted . | Lenovo | Rel-19 | Not Handled | Not Handled | |
| 19.3 | S2-2400933 | P-CR | Approval | 23.700-70: Solution for KI#5: New solution for supporting dynamic change of traffic characteristics. | Lenovo | Rel-19 | Not Handled | Not Handled | |
| 19.3 | S2-2400962 | P-CR | Approval | 23.700-70: New solution for KI#3: map PDU Set importance to DSCP marking over N3/N9 in the transport network . | Lenovo | Rel-19 | Revision of (unhandled) S2-2312763 Not Handled | Not Handled | |
| 19.3 | S2-2400963 | P-CR | Approval | 23.700-70: New solution for KI#5: QoS Handling when Traffic Characteristics change dynamically. | Lenovo | Rel-19 | Not Handled | Not Handled | |
| 19.3 | S2-2400965 | P-CR | Approval | 23.700-70: New solution for KI#7: support for PDU set in non-3GPP access. | Lenovo | Rel-19 | Not Handled | Not Handled | |
| 19.3 | S2-2401027 | P-CR | Approval | 23.700-70: KI#2: Corrections to Key Issue wording and Encrypted Media Definition. | Apple, Futurewei, Meta USA, Google, Huawei, HiSilicon | Rel-19 | Revision of (unhandled) S2-2313104 Not Handled | Not Handled | |
| 19.3 | S2-2401038 | P-CR | Approval | 23.700-70: KI#1, New Sol: The handling of the requested PSDB . | Vivo | Rel-19 | Not Handled | Not Handled | |
| 19.3 | S2-2401039 | P-CR | Approval | 23.700-70: KI#1, New Sol: The handling and response of the QoS flow and PDU Set QoS parameters. | Vivo | Rel-19 | Not Handled | Not Handled | |
| 19.3 | S2-2401153 | P-CR | Approval | 23.700-70: KI#1, New Sol: PDU set handling enhancement to support the scenarios where FEC or error concealment is applied. | OPPO | Rel-19 | Not Handled | Not Handled | |
| 19.3 | S2-2401169 | P-CR | Approval | 23.700-70: KI#3 Solution for transport level marking over N3/N9. | Nokia, Nokia Shanghai Bell | Rel-19 | Not Handled | Not Handled | |
| 19.3 | S2-2401170 | P-CR | Approval | 23.700-70: KI#1 Solution for PDU Set Discard Buffer Management. | Nokia, Nokia Shanghai Bell | Rel-19 | Not Handled | Not Handled | |
| 19.3 | S2-2401171 | P-CR | Approval | 23.700-70: KI#5 Solution for QoS Handling when Traffic Characteristics Change Dynamically based on time to next burst. | Nokia, Nokia Shanghai Bell | Rel-19 | Not Handled | Jari (NTT DOCOMO) comments ==== Revisions Deadline ==== | Not Handled |
| 19.3 | S2-2401192 | P-CR | Approval | 23.700-70: KI#1 Solution for QoS Handling when Traffic Characteristics Change Dynamically. | Nokia, Nokia Shanghai Bell | Rel-19 | Not Handled | Not Handled | |
| 19.3 | S2-2401194 | P-CR | Approval | 23.700-70: KI#4 Support for multiplexed media traffic. | Nokia, Nokia Shanghai Bell | Rel-19 | Not Handled | Not Handled | |
| 19.3 | S2-2401195 | P-CR | Approval | 23.700-70: KI#6: Solution for L4S support in intermediate non-3GPP access nodes. | Nokia, Nokia Shanghai Bell | Rel-19 | Not Handled | Not Handled | |
| 19.3 | S2-2401196 | P-CR | Approval | 23.700-70: KI#7: Solution for PDU Set support in intermediate non-3GPP access nodes. | Nokia, Nokia Shanghai Bell | Rel-19 | Not Handled | Not Handled | |
| 19.3 | S2-2401210 | P-CR | Approval | 23.700-70: KI#4_New Sol_ QoS Flow Mapping for Multiplexed Data Flows. | Xiaomi | Rel-19 | Not Handled | Not Handled | |
| 19.3 | S2-2401347 | P-CR | Approval | 23.700-70: KI#1: New Sol: AS/AF provided PDU sets correlation information. | Meta USA | Rel-19 | Revision of (unhandled) S2-2313182 Not Handled | Not Handled | |
| 19.3 | S2-2401348 | P-CR | Approval | 23.700-70: (KI#3) Solution of Differentiated Handling for Transporting Encrypted XRM traffics. | Rel-19 | Not Handled | Not Handled | ||
| 19.3 | S2-2401352 | P-CR | Approval | 23.700-70: WT#4: New Sol: Data rate limit information to AS/AF. | Meta USA | Rel-19 | Not Handled | Not Handled | |
| 19.4 | - | - | - | Feasibility Study on 5GS Enhancement for Energy Efficiency and Energy Saving (FS_EnergySys) | - | - | Docs:=101 | - | |
| 19.4 | - | - | - | LS | - | - | Docs:=3 | - | |
| 19.4 | S2-2400072 | LS In | Action | LS from SA WG5: LS on network energy related information exposure | SA WG5 (S5-238106) | Rel-18 | Response drafted in S2-2400738. Postponed | Postponed | |
| 19.4 | S2-2400738 | LS OUT | Approval | [DRAFT] Reply LS on network energy related information exposure | Qualcomm Technologies Int | Rel-19 | Response to S2-2400072. Postponed | Tao(CMCC) do not think it is necessary to send the LS Juan Zhang (Qualcomm) replies to Tao(CMCC) and LaeYoung (LGE). LaeYoung (LGE) also proposes to NOTE this LS. Jungshin (Samsung) proposes to NOTE the LS. Manmeet (Rakuten) concurs with Samsung and others and also proposes to NOTE this LS. Yannick (Nokia) also do not see the need for a reply LS at this point. Suggest to postpone the incoming SA5 LS for a sync with SA5 later, after some progress in SA2. ==== Revisions Deadline ==== | Postponed |
| 19.4 | S2-2400296 | LS OUT | Approval | [DRAFT] LS on different energy states of network elements and network functions | vivo | Rel-19 | Postponed | Tao(CMCC) comment need some update Xiaowen (vivo) responds to LaeYoung and Tao. LaeYoung (LGE) asks a Q for clarification. LiMeng (Huawei) suggests to clarify further in the text. Jungshin (Samsung) suggest revision of the LS to focus on the question to SA1 Xiaowen (vivo) responds to Jungshin (Samsung) and Li Meng (Huawei), and provides r02 LiMeng (Huawei) asks questions. ==== Revisions Deadline ==== | Postponed |
| 19.4 | - | - | - | Key Issue - New/Update | - | - | Docs:=3 | - | |
| 19.4 | S2-2401143 | P-CR | Approval | 23.700-66: KI#1 Update. | Nokia, Nokia Shanghai Bell | Rel-19 | Revision of (unhandled) S2-2312827. Noted | Megha (Intel) asks question for clarification. Alessio(Nokia) provides r01 embedding text from S2-2400137 and S2-2400231 as per instructions from rapporteur(s) Juan (Qualcomm) asks question for clarification. Xiaowen Sun (vivo) provides corresponding requirement in SA1. Alla (OPPO) provides comments to revision r01. Genadi (Lenovo) provides comments and r02. Alessio(Nokia) provides r03 Bahador (NTT DOCOMO) asks clarification on the title of the KI Alessio(Nokia) provides a reply to Bahador (NTT DOCOMO) ==== Revisions Deadline ==== Marco(Huawei) OK for R00 and R02, NOK R01, R03 Genadi (Lenovo) can live with R03 assuming that the info provided by the AF is actually related to KI#2 and KI#3. Alessio(Nokia) agrees that the impact of the addition is on KI#2,3. Can live with r00 and r03 Megha(Intel) is OK only with r03, objects to r00,r01,r02. ==== Final Comments Deadline ==== | Noted |
| 19.4 | S2-2400729 | P-CR | Approval | 23.700-66: 23.700-66: KI#1: scope update. | Qualcomm Incorporated | Rel-19 | Postponed | Megha (Intel) supports the update in this contribution. Alla(OPPO) supports the update in this contribution. Tao(CMCC) doesn't agree to downscope the KI#1 due to the need to define the procedures. Juan Zhang (Qualcomm) replies to Genadi (Lenovo). Juan Zhang (Qualcomm) replies to Tao (CMCC). Genadi (Lenovo) has concerns with the proposal. Jungshin (Samsung) suggest further changes to clarify the scope. Alessio(Nokia) provides r01 Juan Zhang (Qualcomm) provides r02. Tao(CMCC) comments on the scope 'slices of a UE', and still request to keep the scope as it is. And response further to Juan. Juan Zhang (Qualcomm) provides r03 to add the reference num about the referred spec. Marco(Huawei) provides r04 (removed Annex X since more suitable in 1181, where is already present. Alessio(Nokia) can accept r05 we provided in this meesage with annex removed and clear text the examples are not exhaustive and not even necessarily needed to be addressed by solutions ==== Revisions Deadline ==== Juan Zhang (Qualcomm) is OK with r04 or r03 with removal of the Annex. LaeYoung (LGE) proposes to NOTE or POSTPONE this P-CR. Juan Zhang (Qualcomm) can not agree r05, but can agree r04 or r03 with removal of the Annex. Alessio(Nokia) sees r05 only acceptable. We can also postpone or leave scope as is ?? LaeYoung (LGE) cannot accept all versions including r00 in this meeting, and proposes to postpone this P-CR. ==== Final Comments Deadline ==== | Postponed |
| 19.4 | S2-2400232 | P-CR | Approval | 23.700-66: New KI UE support for energy saving and energy efficiency. | Vivo | Rel-19 | Noted | Juan Zhang (Qualcomm) objects the new KI. Xiaowen Sun (vivo) responds to Juan Bahador (NTT DOCOMO) has strong concern on this proposal. Xiaowen Sun (vivo) responds to Bahador (NTT DOCOMO). Jinsook (DISH Network) propose to defer the UE related EE for next release Xiaowen Sun (vivo) responds to Jinsook (DISH Network) Bahador (NTT DOCOMO) responds to Xiaowen (Vivo) Juan Zhang (Qualcomm) replies to Xiaowen Sun (vivo) Xiaowen Sun (vivo) provides r01 Bahador (NTT DOCOMO) comments on r01 Xiaowen (vivo) agrees with Bahador (NTT DOCOMO) and provide r02 Juan Zhang (Qualcomm) can not agree with r01 and r02. Xiaowen (vivo) responds to Juan Zhang (Qualcomm). Jinsook (DISH Network) I don't think the preference indication from UE side is needed for this release Xiaowen (vivo) responds to Jinsook (DISH Network) and provides r03. Jungshin (Samsung) provides a comment on r03. Juan Zhang (Qualcomm) provides a comment on r03. Juan Zhang (Qualcomm) replies to Xiaowen (vivo) Xiaowen (vivo) replies to Juan (Qualcomm) Jinsook (DISH Network) let's note this paper Juan Zhang (Qualcomm) replies to xiaowan (vivo) ==== Revisions Deadline ==== | Noted |
| 19.4 | - | - | - | Architecture, Definition, Scope | - | - | Docs:=7 | - | |
| 19.4 | S2-2400297 | P-CR | Approval | 23.700-66: Architecture assumption update. | Vivo | Rel-19 | Merged into S2-2401684 | Megha (Intel) provides comments. Marco(Huawei) propose to consider this document merged in S2-2401181 as proposed by rapp and discuss there Alessio(Nokia) agrees with marco(Huawei) and propose to consider this document merged in S2-2401181 as proposed by rapporteur ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 19.4 | S2-2401181 | P-CR | Approval | 23.700-66: Architectural Assumptions. | Huawei, HiSilicon | Rel-19 | r02 Agreed. Revised to S2-2401684, merging S2-2400297 | Marco(Huawei) merged with S2-2400297 with revision Alessio(Nokia) provides r02 to change drastically change the assumptions clause to just refer to the new Annex Chia-Lin (MediaTek) provides r03 Alla (OPPO) comments on r03. Marco(Huawei) disagree to r03 and comment r02 Megha(Intel) asks question for clarification on r03. Juan Zhang (Qualcomm) provides comments on r03. Chia-Lin (MediaTek) provides comments Marco(Huawei) reply to Chia-Lin (Mediatek) and express concern on 3rd party AF addition Marco(Huawei) provides R04 on top of R02 Genadi (Lenovo) provides comments to R04. Juan Zhang (Qualcomm) is OK with r04.. Alessio(Nokia) wonders why we need the editor's note in the assumption on the information specified by sA5. We prefer r02 as the EN is effectively not going to be touched unless one wants to change the assumptions. Marco(Huawei) provide r05 Alessio(nokia) still prefers r02 ==== Revisions Deadline ==== Juan Zhang (Qualcomm) is OK with r02, r04 and r05. Alessio(Nokia) can live with r02 only Megha (Intel) is OK with r02, r05 only. Marco(Huawei) OK only with R05 and R02 ==== Final Comments Deadline ==== | Revised |
| 19.4 | S2-2401684 | P-CR | Approval | 23.700-66: Architectural Assumptions. | Huawei, HiSilicon | Rel-19 | Revision of S2-2401181r02, merging S2-2400297. Approved | Approved | |
| 19.4 | S2-2401129 | P-CR | Approval | 23.700-66: Updated Scope. | Nokia, Nokia Shanghai Bell, Orange | Rel-19 | Revision of (unhandled) S2-2312828. r03 Agreed. Revised to S2-2401685. | Alessio(Nokia) provides r01 embedding text from S2-2401252 as per instructions from rapporteur(s) Marco(Huawei) provides r02 on renewable energy wording. Alessio(nokia) prefers r01 as r02 is difficult to understand. Please Marco clarify the text if you want it acceptable ?? Antoine (Orange) provides r03. Marco (Huawei) thanks Antoine (Orange) you got the point in r03. ==== Revisions Deadline ==== Marco(Huawei) agrees with R03 and R00, objects R01 and R02 ==== Final Comments Deadline ==== | Revised |
| 19.4 | S2-2401685 | P-CR | Approval | 23.700-66: Updated Scope. | Nokia, Nokia Shanghai Bell, Orange | Rel-19 | Revision of S2-2401129r03. Approved | Approved | |
| 19.4 | S2-2400835 | P-CR | Approval | 23.700-66: Adding the energy related definition. | ZTE | Rel-19 | r07 Agreed. Revised to S2-2401686. | zhendong (ZTE) provides the r01 by merging S2-2400298, S2-2401131, S2-2401180, S2-2401252 Marco (Huawei) provides r02 Alessio(Nokia) provides r03, removing editors note, improving and simplifying text, adding support Marco(Huawei) provides r05 Magnus (Ericsson) Questions the stand alone addition of the definitions Marco(Huawei) Errata Corrige : provides R04 (and not R05) Alessio(Nokia) provides r06 fixing some issues in Marco's text (using r06 as r05 is not somehow compromised ??) Chia-Lin (MediaTek) provides r07 ==== Revisions Deadline ==== Marco(Huawei) agrees R07 and R06 ==== Final Comments Deadline ==== | Revised |
| 19.4 | S2-2401686 | P-CR | Approval | 23.700-66: Adding the energy related definition. | ZTE, Vivo, Nokia, Nokia Shanghai Bell, Huawei, MediaTek Inc | Rel-19 | Revision of S2-2400835r07. Approved | Approved | |
| 19.4 | - | - | - | KI#1 | - | - | Docs:=18 | - | |
| 19.4 | S2-2400084 | P-CR | Approval | 23.700-66: New Solution: Energy related information collection and exposure. | China Mobile | Rel-19 | r08 Agreed. Revised to S2-2401687, merging S2-2400621 | Tao (CMCC) provides r01 to merge S2-240013/233/836/1069/1371. Juan Zhang (Qualcomm) provides comment on r01. Yannick (Nokia) provides comments and r02. Bahador (NTT DOCOMO) provides comments Tao(CMCC) responded to Juan, Yannick and Bahador and provided r03 based on the comments. Xiaowen Sun (vivo) provides comments. Marco(Huawei) comments on EC from NF (SMF, AMF, UPF) Juan Zhang (Qualcomm) provides comment on r03. Kenichi (KDDI) provides comments on NEF event exposure and data collection for NG-RAN. Yannick (Nokia) provides comments and r04. Tao(CMCC) response Marco to clarify the questions. Tao(CMCC) response to Bahador and Marco and provided r08 ==== Revisions Deadline ==== Tao(CMCC) thanks Costas and will add Lenovo if the revision approved with assigned tdoc number. Jinsook (DISH Network) Thanks, please include 'DISH Network' for the co-signer!! ==== Final Comments Deadline ==== Tao(CMCC) thanks Jinsook and will do | Revised |
| 19.4 | S2-2401687 | P-CR | Approval | 23.700-66: New Solution: Energy related information collection and exposure. | China Mobile, NEC, Rakuten Mobile Inc., Vvo, ZTE, Samsung, Lenovo, DISH Network | Rel-19 | Revision of S2-2400084r08, merging S2-2400621. Approved | Approved | |
| 19.4 | S2-2400111 | P-CR | Approval | 23.700-66: KI #1, New Sol: Energy Brokerage Function for energy related information processing. | OPPO | Rel-19 | CC#4: Postponed | Marco(Huawei) ask clarifications and provides comments Yannick (Nokia) provides questions. Also a kind request that, as part of this study (and not only this pCR), we do not reference PRs or CPRs from an SA1 TR but rather reference normative requirements from TS 22.261. SA1 spent significant effort rewording and merging CPRs into normative requirements, and normative specification is what we should base our work in SA2 on. Juan Zhang (Qualcomm) provides questions Alla (OPPO) provides answers to Qualcomm, Nokia and Huawei and also provides r01. Yannick (Nokia) comments on r01. Also sees some similarities with other proposals such as S2-24000621. Alla replies to Yannick and provides r02. Yannick (Nokia) comments on r02. Yannick (Nokia) sees quite some similarities between S2-2400084, S2-2400111, S2-2400322 and S2-2400621. Kindly requests proponents to check if a merge is possible into one solution proposing a new NF to collect information from OAM and/or 5GC NFs and derive energy related information. Alla (OPPO) responses to Yannick and provides r03. Yannick (Nokia) comments on r03. Juan Zhang (Qualcomm) provides comments to r03. Alla (OPPO) responses to Yannick (Nokia) and Juan (Qualcomm) and provides r04. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== Alla replies to Costas and believes his comments might be addressed by the existing ENs. Costas (Lenovo) our comments are still not addressed by doing nothing, so we still object r07. Alla provides revision which covers the comments provided by Costas r08 (for the cc#4). | Postponed |
| 19.4 | S2-2400322 | P-CR | Approval | 23.700-66: KI#1, New Sol: Energy related information exposure. | LG Electronics | Rel-19 | Revision of (unhandled) S2-2312754. r05 Agreed. Revised to S2-2401688. | Yannick (Nokia) provides comments and questions. Juan Zhang (Qualcomm) provides comments LaeYoung (LGE) provides r01 with answers to Yannick (Nokia) and Juan (Qualcomm). Yannick (Nokia) provides r02. Also asks how the solution is different from solution in e.g. S2-24000844. Yannick (Nokia) provides r02. Also asks how the solution is different from solution in e.g. S2-2400084. Yannick (Nokia) sees quite some similarities between S2-2400084, S2-2400111, S2-2400322 and S2-2400621. Kindly requests proponents to check if a merge is possible into one solution proposing a new NF to collect information from OAM and/or 5GC NFs and derive energy related information. LaeYoung (LGE) provides r03 with answers to Yannick (Nokia) and Juan (Qualcomm). Juan Zhang (Qualcomm) provides comment on r03.. LaeYoung (LGE) provides r04. Marco(Huawei) please confirm in this thread if 0322 is merged into 0084 Yannick (Nokia) comments on r04. Ok to keep this one as separate for the reasons provided by LaeYoung. LaeYoung (LGE) provides r05 and confirms that this P-CR is kept separate instead of being merged into 00084. Iskren (NEC) provides r06. Kenichi (KDDI) provides comment for location parameter. LaeYoung (LGE) also comments that AoI parameter is already there. Iskren (NEC) comments. LaeYoung (LGE) replies to Iskren (NEC) that will add NEC. ==== Revisions Deadline ==== Marco(Huawei) ok with R06 and R05 ==== Final Comments Deadline ==== | Revised |
| 19.4 | S2-2401688 | P-CR | Approval | 23.700-66: KI#1, New Sol: Energy related information exposure. | LG Electronics, NEC | Rel-19 | Revision of S2-2400322r05. Approved | Approved | |
| 19.4 | S2-2400621 | P-CR | Approval | 23.700-66: Solution on KI#1: Network energy consumption and efficiency information exposure. | Rakuten Mobile Inc. | Rel-19 | Revision of (unhandled) S2-2312550. Merged into S2-2401687 | Yannick (Nokia) provides comments. Also a kind request that, as part of this study (and not only this pCR), we do not reference PRs or CPRs from an SA1 TR but rather reference normative requirements from TS 22.261. SA1 spent significant effort rewording and merging CPRs into normative requirements, and normative specification is what we should base our work in SA2 on. Yannick (Nokia) provided r01. Manmeet (Rakuten Mobile) responds to Nokia's comment. Manmeet (Rakuten Mobile) agree with r01 provided by Yannick (Nokia). Juan Zhang (Qualcomm) provides comment. Manmeet (Rakuten Mobile) provides r02 with answers to Juan (Qualcomm) Yannick (Nokia) concurs with Juan (Qualcomm). If the solution is only to expose OAM information to AF, then we also believe this solution is out of SA2 scope and should rather be investigated in SA5. Please note that SA5 is going to work in Rel-19 on a study on Enhanced OAM for management exposure to external consumers, which would fit for current solution. Also, Nokia asks what is different between this solution and solution in e.g. S2-2400322. Manmeet (Rakuten Mobile) provides r03 with answers to Yannick (Nokia) Marco(Huawei) agrees with Yannick (Nokia) and Juan (QC) and Costas (Lenovo) Yannick (Nokia) sees quite some similarities between S2-2400084, S2-2400111, S2-2400322 and S2-2400621. Kindly requests proponents to check if a merge is possible into one solution proposing a new NF to collect information from OAM and/or 5GC NFs and derive energy related information. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 19.4 | S2-2400166 | P-CR | Approval | 23.700-66: KI#1, New Sol: Enhancement network exposure for energy saving. | Tencent, Tencent Cloud | Rel-19 | r09 Agreed. Revised to S2-2401689. | Kenichi (KDDI) provides comments. Yannick (Nokia) provides comments and questions. Jungshin (Samsung) provides comments and asks for clarification. Marco(Huawei) expresses concerns on the technical solution for RAN Magnus (Ericsson) Asks for the use case Yuhang(Tencent) replies to Costas(Lenovo). Yuhang(Tencent) replies to Yannick (Nokia) and provide r06. Kenichi (KDDI) comments for analytics exposure. ==== Revisions Deadline ==== Kenichi (KDDI) is fine with r09. ==== Final Comments Deadline ==== | Revised |
| 19.4 | S2-2401689 | P-CR | Approval | 23.700-66: KI#1&3, New Sol: Enhancement network exposure for energy saving. | Tencent, Tencent Cloud | Rel-19 | Revision of S2-2400166r09. Approved | Approved | |
| 19.4 | S2-2400736 | P-CR | Approval | 23.700-66: TR 23.700-66: KI#1 Solution about renewable energy ratio information exposure. | TOYOTA MOTOR CORPORATION, KDDI | Rel-19 | r05 Agreed. Revised to S2-2401690. | Yannick (Nokia) provides questions and r01. Also wonders if there is related stage 1. Marco(Huawei) asks clarifications Xiao (Toyota) replies to Yannick (Nokia) about related stage 1 requirement. Juan Zhang (Qualcomm) provides comment. Yannick (Nokia) replies to Xiao (Toyota). Also request again that, as part of this study (and not only this pCR), we do not reference PRs or CPRs from an SA1 TR but rather reference normative requirements from TS 22.261. SA1 spent significant effort rewording and merging CPRs into normative requirements, and normative specification is what we should base our work in SA2 on. Xiao (Toyota) replies to Yannick (Nokia). Xiao (Toyota) replies to Juan Zhang (Qualcomm). Xiao(Toyota) replies to Marco(Huawei). Yannick (Nokia) asks if this solution really target key issue #1 or does it actually address key issue #3? At least the proposal seems to be mainly about NWDAF generating analytics. Also asks which stage 1 normative requirements are addressed by this solution. Xiao (Toyota) replies to Yannick (Nokia) related to the KI and normative requirement. Yannick (Nokia) notes that related stage 1 requirements do not require exposing renewable energy information per UE. Magnus (Ericsson) Comments Xiao (Toyota) replies to Genadi (Lenovo) about the UE location retrieval. Genadi (Lenovo) provides comments. Xiao (Toyota) replies to Yannick (Nokia) and Magnus (Ericsson), and provides revision2. Genadi (Lenovo) provides further comments about the UE location and duration of activity and provides r03. Xiao (Toyota) is fine with r03 provided by Genadi (Lenovo). Marco(Huawei) comments r03 and express some concern on Per site information& cell iD Xiao (Toyota) replies to Marco(Huawei) and provides r04. Yannick (Nokia) provides r05. Xiao (Toyota) is fine with r05 provided by Yannick (Nokia). ==== Revisions Deadline ==== Marco(Huawei) OK R05 only , Not OK for R00 to R04 ==== Final Comments Deadline ==== | Revised |
| 19.4 | S2-2401690 | P-CR | Approval | 23.700-66: TR 23.700-66: KI#1 Solution about renewable energy ratio information exposure. | TOYOTA MOTOR CORPORATION, KDDI | Rel-19 | Revision of S2-2400736r05. Approved | Approved | |
| 19.4 | S2-2401336 | P-CR | Approval | 23.700-66: New Solution KI#1, Exposing energy usage information to 3rd party server. | InterDigital Inc. | Rel-19 | r04 Agreed. Revised to S2-2401691. | Kenichi (KDDI) ask for clarification. Yannick (Nokia) provides comments. Marco(Huawei) ask clarifications on info collected by NDWAF Juan Zhang (Qualcomm) provides comment. Kenichi (KDDI) provides additional comments for NEF translation. Saad (Interdigital) provides r01. Yannick (Nokia) asks if this solution really target key issue #1 only or does it also address key issue #3? Bahador (NTT DOCOMO) provides comments. Saad (Interdigital) replies to NTT DOCMO and provides r03 <https://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_160AHE_Electronic_2024-01/INBOX/Revisions/S2-2401336r03.zip> . Saad (Interdigital) replies to comments and provides r02 <https://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_160AHE_Electronic_2024-01/INBOX/Revisions/S2-2401336r02.zip> . Yannick (Nokia) comments on r03. Saad (Interdigital) provides r04 ==== Revisions Deadline ==== Marco(Huawei) OK R04 & R03 objects R00, R01 & 02 ==== Final Comments Deadline ==== | Revised |
| 19.4 | S2-2401691 | P-CR | Approval | 23.700-66: New Solution KI#1, Exposing energy usage information to 3rd party server. | InterDigital Inc. | Rel-19 | Revision of S2-2401336r04. Approved | Approved | |
| 19.4 | S2-2400720 | P-CR | Approval | 23.700-66: 23.700-66: KI#1: New solution to support NG-RAN node QoS flow PDU session and UE level energy related information report. | Qualcomm Incorporated | Rel-19 | Postponed | Yannick (Nokia) provides comments and r01. Marco(Huawei) comment on RAN collection and to Yannick (Nokia) Juan Zhang (Qualcomm) provides r02 based on r01. Yannick (Nokia) provides comments. LaeYoung (LGE) provides comments. Magnus (Ericsson) provide comments Xiaowen (vivo) provide comments Yannick (Nokia) provides r03. Genadi (Lenovo) provides comment regrading the UPF/SMF generating energy information. Juan Zhang (Qualcomm) replies to Magnus (Ericsson) Juan Zhang (Qualcomm) replies to LaeYoung (LGE). Juan Zhang (Qualcomm) provides r04. LaeYoung (LGE) answers to Juan (Qualcomm). Juan Zhang (Qualcomm) provides r05. LaeYoung (LGE) replies to Juan (Qualcomm). Marco(Huawei) provide comments Chris (Vodafone) says that the NGAP impacts are much larger, but, we can copy Rel 15 secondary data volume reporting procedures. Also 'average energy' is really not worth working on -> per UE energy is the thing that we don't know. Juan Zhang (Qualcomm) replies to Chris. Juan Zhang (Qualcomm) provides r06 Genadi (Lenovo) provides r07 to convert a NOTE to Ed. Note about the NG-RAN measurement of the energy information. Marco(Huawei) express concern and prefer to note the document Magnus (Ericsson) Agrees with Marco Juan Zhang (Qualcomm) provides r08. Yannick (Nokia) provides r09. ==== Revisions Deadline ==== Juan Zhang (Qualcomm) is OK with r09. Marco (Huawei) objects to any version and asks to postpone this contribution for further discussion in next SA2 meetings. ==== Final Comments Deadline ==== | Postponed |
| 19.4 | S2-2400837 | P-CR | Approval | 23.700-66: KI#1&2, new solution on the Energy information collection for service. | ZTE | Rel-19 | r05 Agreed. Revised to S2-2401692. | Yannick (Nokia) provides questions and r01. Juan Zhang (Qualcomm) provides comment. zhendong (ZTE) provides the response Marco(Huawei) ask clarification Marco(Huawei) answers to Zhendong (ZTE) Marco(Huawei) some EN needs to be added to address open issue zhendong (ZTE) provides the r02 zhendong (ZTE) provides the response to Juan(Qualcomm) Magnus (Ericsson) provides comments Juan Zhang (Qualcomm) replies to zhendong (ZTE) ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 19.4 | S2-2401692 | P-CR | Approval | 23.700-66: KI#1&2, new solution on the Energy information collection for service. | ZTE | Rel-19 | Revision of S2-2400837r05. Approved | Approved | |
| 19.4 | S2-2401070 | P-CR | Approval | 23.700-66: KI#1, Collection of Energy Consumption related information. | Lenovo | Rel-19 | Noted | Yannick (Nokia) provides comments. Marco(Huawei) provides comments Marco(Huawei) express concern on the report of info from RAN and on granularity Genadi (Lenovo) replies to Marco (Huawei) regarding the report of info from RAN. Genadi (Lenovo) replies to Yannick (Nokia) and provides r01. LaeYoung (LGE) asks some Qs for clarification. Genadi (Lenovo) provides replies to LaeYoung (LGE). Magnus (Ericsson) Asks for the Use Cases Yannick (Nokia) suggest to focus only on 3GPP RATs as part of this study. Genadi (Lenovo) agrees with Yannick (Nokia) and LaeYoung (LGE) to focus only on 3GPP RATs as part of this study. Genadi (Lenovo) provides replies to Magnus (Ericsson) on the use cases. Yannick (Nokia) thanks Genadi (Lenovo) and provides r03. Marco(Huawei) comments and express concerns on RAN measurement Genadi (Lenovo) is OK with r03. Genadi (Lenovo) replies to comments by Marco (Huawei) and provide r04. Yannick (Nokia) requests to capture in an editor's note that this solution needs to be reviewed by RAN. Genadi (Lenovo) replies to Yannick (Nokia). Yannick (Nokia) suggests to convert the NOTE into an editor's note. Marco(Huawei) express concern on the RAN measurement at EU/PDU session granularity and propose to note Genadi (Lenovo) provides r05 reverting a NOTE to an Editor's Note. Genadi (Lenovo) provides replies to Marco (Huawei) and refers to r05. Magnus (Ericsson) Shares Marco's concern ==== Revisions Deadline ==== Marco (Huawei) objects to any version and asks to postpone this contribution for further discussion in next SA2 meetings. Genadi (Lenovo) provides clarification to Magnus (Ericsson) that the RAN reports the energy consumed for the transmission of data/signalling for a specific UE. Genadi (Lenovo) comments that this is a solution to a study which complies with the Arch Assumption in clause 4 and the KI description. Impacts to RAN are not excluded from the study. Why shall we note solutions based on evaluation considerations by an individual company? There are Ed. Notes included for the open issues. ==== Final Comments Deadline ==== | Noted |
| 19.4 | S2-2401175 | P-CR | Approval | 23.700-66: KI#1,2 New Solution on reporting, charging and exposure of energy related information based on UP reporting from RAN. | Nokia, Nokia Shanghai Bell | Rel-19 | CC#4: Postponed | Marco(Huawei) provides comments LaeYoung (LGE) provides comments. Genadi (Lenovo) provides comments. Juan Zhang (Qualcomm) provides comments Alessio(Nokia provides r01 and replies to the good comments Marco(Huawei) comments and express concern on RAN measurement LaeYoung (LGE) comments on r01. Alessio(Nokia) replies Alessio(Nokia) provides r02. Genadi (Lenovo) suggests to add a NOTE that coordination with the RAN WGs is required. Marco(Huawei) express concern on the RAN measurement and propose to note Genadi (Lenovo) provides r03 to include an Ed. Note about the RAN measurement of the energy consumption. Alessio(nokia) believes the energy measurements in RAN cannot be a standards discussion. Same everywhere else. Cannot accept r03 Alessio(nokia) believes that then we should object to all papers and close the SID as measurement of energy consumption cannot be discussed in the standards in any node. But the proposal is also really to label the data volume according to the state of the RAN node so not sure how this can be something you can and want to prevent. Basically if RAN node has a collection of states it can say in which state a data volume was sent. We cannot see how this should be prevented from being documented. Marco (Huawei) comment to Alessio (nokia) therefore it is not in the scope to standardize in N2 or N3 as well if it can not be said that is feasible and supported.. ==== Revisions Deadline ==== Genadi (Lenovo) replies to Alessio (Nokia): it is OK to us to conclude that the energy measurement mechanism in RAN is based on implementation. This can be the resolution of the EN also in the other papers. Alessio (nokia) did not ever state it is note in the scope to standardize N3 aspects (it is written in a note be LG it is needed and involved CT4 also ?? ) . Asks Huawei to avoid inventing claims we never made. Alessio (nokia) suggests to agree r02 and Huawei can remark concerns in evaluation phase. It would be not efficient to take more meeting time in Athens on documenting this. Marco (Huawei) objects to any versions and asks to postpone this contribution for further discussion in next SA2 meetings. Alessio(Nokia) states that if Marco (Huawei) objects to anything that is not based on SA5 info , then we should reject all the CRs and close the SID. Asks to handle this in CC#3 as unacceptable behaviour. ==== Final Comments Deadline ==== | Postponed |
| 19.4 | S2-2401182 | P-CR | Approval | 23.700-66: KI#1&2&3: Sol #y Definition of network energy related information KPIs;. | Huawei, HiSilicon | Rel-19 | Postponed | Xiaoyan (CATT) provides comments. Tao (CMCC) questions whether those KPIs are all needed. Genadi (Lenovo) questions whether this solution (i.e. definition of the KPIs) is not in the scope of SA5. Xiaowen (vivo) provides comments Marco (Huawei) replies to all comments ==== Revisions Deadline ==== Xiaoyan (CATT) objects to r00, suggests postponing this paper for further discussion in next meeting. Yannick (Nokia) recommends to postpone this contribution for further discussion in next SA2 meetings. Marco(Huawei) I'm fine to resubmit revision this document ==== Final Comments Deadline ==== | Postponed |
| 19.4 | - | - | - | KI#2 | - | - | Docs:=10 | - | |
| 19.4 | S2-2400087 | P-CR | Approval | 23.700-66: New Solution: Policy control for network energy saving. | China Mobile | Rel-19 | r13 Agreed. Revised to S2-2401693. | Manmeet (Rakuten Mobile) is OK with the merge proposal and requests CMCC to provide r02 based on offline discussion to accommodate an Editor's Note regarding the name of the NF. Tao (CMCC) provides r01 to merge S2-2400930. LiMeng (Huawei) provides r02. Kenichi (KDDI) ask for clarification. Juan Zhang (Qualcomm) provides comment. Tao(CMCC) confirms the understanding of KDDI. Accept the changes from HW. Provided r03 based on the comments also from Juan and offline check with Rakuten. LaeYoung (LGE) comments on r03. Alessio(Nokia) provides r04 Xiaoyan (CATT) provides r05. Xiao(Toyota) provides comments. Tingyu (Samsung) provides comments. Magnus (Ericsson) asks for clarification and addition of a note Tao(CMCC) response to LaeYoung, Alessio, Xiao and Xiaoyan, and provides r06. Bahador (NTT DOCOMO) comments on the procedure LaeYoung (LGE) provides r07. Tao(CMCC) thanks LaeYoung's r07 and will update the Figure to include OAM as suggested by Bahador. Tao (CMCC) clarifies and response to the comments Tao(CMCC) provides r08 to include OAM in the Figure 6.x.3-1 per Bahador previous comments. Also add Toyota as supporting company Magnus (Ericsson) Comments on the assumption that lowering AMBR decrease energy consumption Alessio(Nokia) provides r09 with the editor's notes needed to understand the solution inside the procedures steps. We cannot agree without these editor's notes being documented. Tao(CMCC) clarified some text on the newly added EN and provided r10. Xiaoyan (CATT) replies to Magnus (Ericsson) LaeYoung (LGE) provides r11. Tao(CMCC) appreciate LaeYoung (LGE)' r11 and add a EN in r12 per Magnus comment Alessio provides r13 with two Ens that are important to be clarified next meeting ==== Revisions Deadline ==== LaeYoung (LGE) is fine with r13. Marco(Huawei) ok with r13 Tao(CMCC) is ok with r13, though already enough EN for next meeting homework :-) ==== Final Comments Deadline ==== | Revised |
| 19.4 | S2-2401693 | P-CR | Approval | 23.700-66: New Solution: Policy control for network energy saving. | China Mobile, Rakuten Mobile, CATT, TOYOTA MOTOR CORPORATION, LG Electronics | Rel-19 | Revision of S2-2400087r13. Approved | Approved | |
| 19.4 | S2-2400135 | P-CR | Approval | 23.700-66: KI#2, New Sol: Energy efficiency subscriptions and control. | NEC | Rel-19 | CC#4: r04 + changes agreed. Revised to S2-2401839. | Marco(Huawei) comments on EC measurements and EnergystateMode Tingyu (Samsung) provides comments. Xiaowen Sun (vivo) provides comments. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 19.4 | S2-2401839 | P-CR | Approval | 23.700-66: KI#2, New Sol: Energy efficiency subscriptions and control. | NEC, Lenovo | Rel-19 | Revision of S2-2400135r04 + changes. Approved | Approved | |
| 19.4 | S2-2400294 | P-CR | Approval | 23.700-66: KI #2, New Sol PCF based credit limit control for subscribers. | Vivo | Rel-19 | r03 Agreed. Revised to S2-2401694. | Chia-Lin (MediaTek) ask for clarification Alla (OPPO) provides comments Xiaowen Sun (vivo) replies to Chia-Lin (MediaTek). Xiaowen Sun (vivo) provides r01. Tingyu (Samsung) asks for clarification. Juan Zhang (Qualcomm) provides comments Xiaowen Sun responds to Tingyu (Samsung) and provide r02. Xiaowen (vivo) responds to Tingyu (Samsung). ==== Revisions Deadline ==== Juan Zhang (Qualcomm) is OK with r03. Tingyu (Samsung) would like to co-sign r03. ==== Final Comments Deadline ==== | Revised |
| 19.4 | S2-2401694 | P-CR | Approval | 23.700-66: KI #2, New Sol PCF based credit limit control for subscribers. | Vivo | Rel-19 | Revision of S2-2400294r03. Approved | Approved | |
| 19.4 | S2-2400462 | P-CR | Approval | 23.700-66: New solution for KI#2: Enhancement for subscription and policy control to enable network energy savings. | Intel | Rel-19 | r03 Agreed. Revised to S2-2401695. | Marco(Huawei) ask clarifications Tingyu (Samsung). Megha(Intel) provides r01 and response to Marco (Huawei) and Tingyu (Sumsung) Bahador (NTT DOCOMO) asks clarification on the assumptions and scope of the solution Megha(Intel) provides r02 and response to Bahador (NTT DOCOMO) Alessio(Nokia) request a revision to document the EECF function services and a clarification of its role before we can accept the solution in TR Megha(Intel) provides r03 and response to Alessio (Nokia) ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 19.4 | S2-2401695 | P-CR | Approval | 23.700-66: New solution for KI#2: Enhancement for subscription and policy control to enable network energy savings. | Intel | Rel-19 | Revision of S2-2400462r03. Approved | Approved | |
| 19.4 | S2-2401251 | P-CR | Approval | 23.700-66: URSP rules and slice with the validity information generation based on energy related information. | MediaTek Inc. | Rel-19 | r01 Agreed. Revised to S2-2401696. | Marco(Huawei) ask clarification on Energy info from 3rd party Chia-Lin (MediaTek) responds to Marco (Huawei) Juan Zhang (Qualcomm) provides comment. Alessio(Nokia) agrees with Juan Zhang (Qualcomm) and suggests to postpone this paper as it seems not clear. We may come back next meeting Chia-Lin (MediaTek) responds, and provides r01 ==== Revisions Deadline ==== Juan Zhang (Qualcomm) is OK with r01. ==== Final Comments Deadline ==== | Revised |
| 19.4 | S2-2401696 | P-CR | Approval | 23.700-66: URSP rules and slice with the validity information generation based on energy related information. | MediaTek Inc. | Rel-19 | Revision of S2-2401251r01. Approved | Approved | |
| 19.4 | - | - | - | KI#3 | - | - | Docs:=10 | - | |
| 19.4 | S2-2401219 | P-CR | Approval | 23.700-66: KI#3: New solution: supporting energy aware NF selection . | Huawei, HiSilicon | Rel-19 | Noted | Hyunsook (LGE) provides a comment. LiMeng (Huawei) provides r01. Xiaowen Sun (vivo) provides comments. Xiao (Toyota) provides comments. Alla (OPPO) provides comments and r02. LiMeng (Huawei) accepts r02 and provides r03. Xiaoyan (CATT) provides r04. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Noted |
| 19.4 | S2-2400389 | P-CR | Approval | 23.700-66: KI#3, New Sol: Support for NWDAF-Based Energy Analytics . | Samsung | Rel-19 | r13 Agreed. Revised to S2-2401697, merging S2-2400850 | Kenichi (KDDI) provides comments. Megha (Intel) provides comments. Jingran(OPPO) provides comments Tingyu (Samsung) provides r01 by merging major content in S2-2400126, S2-2400153, S2-2400860, S2-2400935, S2-2400947, S2-2400958, and S2-240108, per rapporteur guidance. Bahador (NTT DOCOMO) supports r01 and provides r02 Zhang Fu(Huawei) Tingyu (Samsung) provides r03, thanks Bahador (Docomo) for the support, and replies to Jingran (OPPO), Kenichi (KDDI), Zhang(Huawei), Megha (Intel). Juan Zhang (Qualcomm) provides comment. Tingyu (Samsung) replies to Juan Zhang (Qualcomm) Kenichi (KDDI) provides additional comments. Aihua(CMCC) comments. Yannick (Nokia) provides comments and r04. Tingyu (Samsung) replies and provides r05. Yannick (Nokia) provides comments on r05. Kenichi (KDDI) provides additional comments for Temporal and Spatial granularity, and KDDI and TOYOTA MOTOR CORPORATION would like to co-sign. Xiaoyan (CATT) provides r06. Zhang Fu (Huawei) provide r07 and comments LaeYoung (LGE) provides comment. Tingyu (Samsung) provides r08. LaeYoung (LGE) comments on r08. Yannick (Nokia) provides r09. Tingyu (Samsung) provides r11. Please skip r10. Kenichi (KDDI) provides r12. Zhang Fu (Huawei) is OK for r11 and co-sign Ask Zhang to check r12. Yannick (Nokia) provides r13 and co-signs. Tingyu (Samsung) supports r13. ==== Revisions Deadline ==== LaeYoung (LGE) is fine with r13. Zhang Fu (Huawei) is fine with r13. Kenichi (KDDI) is fine with r13. Tingyu (Samsung) thanks for all the support and replies to Kenichi (KDDI). ==== Final Comments Deadline ==== | Revised |
| 19.4 | S2-2401697 | P-CR | Approval | 23.700-66: KI#3, New Sol: Support for NWDAF-Based Energy Analytics . | Samsung, NTT DOCOMO, OPPO, KDDI, TOYOTA MOTOR CORPORATION, CATT, Lenovo, China Mobile, Huawei, HiSilicon, Nokia, Nokia Shanghai Bell | Rel-19 | Revision of S2-2400389r13, merging S2-2400850. Approved | Approved | |
| 19.4 | S2-2400850 | P-CR | Approval | 23.700-66: KI#3, New Sol: Area based EE/EC analytics. | KDDI, TOYOTA MOTOR CORPORATION | Rel-19 | Merged into S2-2401697 | Kenichi (KDDI) fine with merging S2-2400850 into S2-2400389. Tingyu (Samsung) suggests merging S2-2400850 into S2-2400389. Tingyu (Samsung) thanks Kenichi for the support. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 19.4 | S2-2400129 | P-CR | Approval | 23.700-66: KI#3: New Sol: 5G Core Energy Saving. | NTT DOCOMO | Rel-19 | r05 Agreed. Revised to S2-2401698. | Megha (Intel) provides comments. Bahador (NTT DOCOMO) provides clarifications and revision S2-2400129r01 LiMeng (Huawei) asks for clarification. Bahador (NTT DOCOMO) provides responses to LiMeng (Huawei) Megha (Intel) provides further comments and some questions on procedure. Bahador (NTT DOCOMO) responds Megha (Intel) and provides r03 DongYeon (Samsung) provides comments. Bahador (NTT DOCOMO) agrees with DongYeon (Samsung) and provides r04 Alessio (nokia) provides r05 Bahador (NTT DOCOMO) accepts r05 ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 19.4 | S2-2401698 | P-CR | Approval | 23.700-66: KI#3: New Sol: 5G Core Energy Saving. | NTT DOCOMO | Rel-19 | Revision of S2-2400129r05. Approved | Approved | |
| 19.4 | S2-2400136 | P-CR | Approval | 23.700-66: KI#3, New Sol: UE energy usage control. | NEC | Rel-19 | r07 Agreed. Revised to S2-2401699. | Megha (Intel) asks question for clarification. Xiaowen Sun (vivo) provides a comment. Chia-Lin (MediaTek) ask for the clarification Juan Zhang (Qualcomm) provides comment. Iskren (NEC) responds to comments from Chia-Lin (MediaTek), Xiaowen Sun (Vivo) and Megha (Intel) LiMeng (Huawei) asks for clarification. Iskren (NEC) answers questions from LiMeng (Huawei) and Juan Zhang (Qualcomm). Iskren (NEC) provides r01 with added EN. Magnus (Ericsson) asks for clarification Iskren (NEC) answers a question from Magnus (Ericsson) LiMeng (Huawei) suggests to add an EN for the credit refreshing part. Iskren (NEC) addresses comment from Bahador (NTT DOCOMO) and provides r02 Bahador (NTT DOCOMO) provides comments DongYeon (Samsung) provides comments. Bahador (NTT DOCOMO) responds Iskren (NEC) and supports LiMeng (Huawei) comment Iskren (NEC) addressed comments from Bahador (NTT DOCOMO), DongYeon (Samsung), LiMeng (Huawei) and provides r03 Genadi (Lenovo) provides comments: 1) this solution seems related to KI#2, 2) how is the energy credit updated. Iskren (NEC) answers comments from Genadi (Lenovo). Genadi (Lenovo) provides r04. Iskren (NEC) is OK with r04 provided by Genadi (Lenovo) Alessio(Nokia) requests that a CHF based solution be described. This one in this paper is not CHF based. Alessio(Nokia) provides r06 Iskren (NEC) is OK with r06 provided by Alessio(Nokia) DongYeon (Samsung) comments. Iskren (NEC) provides r07 ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 19.4 | S2-2401699 | P-CR | Approval | 23.700-66: KI#3, New Sol: UE energy usage control. | NEC | Rel-19 | Revision of S2-2400136r07. Approved | Approved | |
| 19.4 | S2-2400859 | P-CR | Approval | 23.700-66: KI#3 and #2 new solution of enhancements to existing 5GS procedures for energy saving. | CATT | Rel-19 | r06 Agreed. Revised to S2-2401700. | Megha (Intel) asks questions for clarification. Chia-Lin (MediaTek) ask for the clarification LiMeng (Huawei) asks questions. Xiaoyan (CATT) provides r01. DongYeon (Samsung) provides comments. Xiaoyan (CATT) provides r03. LaeYoung (LGE) provides comments. Xiaoyan (CATT) provides r02. Xiaoyan (CATT) provides r04. LaeYoung (LGE) provides question. Xiaoyan (CATT) replies to LaeYoung (LGE). Alessio(Nokia) provides r05 with some editor's notes Xiaoyan (CATT) provides r06. LaeYoung (LGE) replies to Xiaoyan (CATT). LaeYoung (LGE) provides comment. Xiaoyan (CATT) replies to DongYeon (Samsung). ==== Revisions Deadline ==== LaeYoung (LGE) is fine with r06. ==== Final Comments Deadline ==== | Revised |
| 19.4 | S2-2401700 | P-CR | Approval | 23.700-66: KI#3 and #2 new solution of enhancements to existing 5GS procedures for energy saving. | CATT | Rel-19 | Revision of S2-2400859r06. Approved | Approved | |
| 19.4 | - | - | - | Tdocs exceeding TU budget (max. 30 doc for 1 TU) | - | - | Docs:=50 | - | |
| 19.4 | S2-2401178 | P-CR | Discussion | 23.700-66: Discussion on the evaluation of renewable energy and Carbon related information (general). | Huawei, HiSilicon | Rel-19 | Not Handled | Not Handled | |
| 19.4 | S2-2400298 | P-CR | Approval | 23.700-66: Terms definition update. | Vivo | Rel-19 | Not Handled | Not Handled | |
| 19.4 | S2-2401131 | P-CR | Approval | 23.700-66: Definitions update. | Nokia, Nokia Shanghai Bell | Rel-19 | Revision of (unhandled) S2-2312824 Not Handled | Not Handled | |
| 19.4 | S2-2401180 | P-CR | Approval | 23.700-66: Definitions of Carbon related information. | Huawei, HiSilicon | Rel-19 | Not Handled | Not Handled | |
| 19.4 | S2-2401252 | P-CR | Approval | 23.700-66: Update to scope and definition for concept of energy saving and carbon emission. | MediaTek Inc. | Rel-19 | Not Handled | Not Handled | |
| 19.4 | S2-2401179 | P-CR | Discussion | 23.700-66: Estimating the UE level energy consumption information. | Huawei, HiSilicon | Rel-19 | Not Handled | Not Handled | |
| 19.4 | S2-2400295 | DISCUSSION | Endorsement | Discussion on different energy states of network elements and network functions. | Vivo | Rel-19 | Not Handled | Not Handled | |
| 19.4 | S2-2400137 | P-CR | Approval | 23.700-66: New KI: AF assistance for energy efficiency control in the 3GPP system. | NEC | Rel-19 | Revision of (unhandled) S2-2312432 Not Handled | Not Handled | |
| 19.4 | S2-2400231 | P-CR | Approval | 23.700-66: New KI: External interaction between communication service consumer and 5GS. | Vivo | Rel-19 | Not Handled | Not Handled | |
| 19.4 | S2-2400134 | P-CR | Approval | 23.700-66: KI#1, New Sol: Network energy related information exposure to AF. | NEC | Rel-19 | Revision of (unhandled) S2-2312434 Not Handled | Not Handled | |
| 19.4 | S2-2400233 | P-CR | Approval | 23.700-66: KI #1, New Sol PDU session level energy consumption calculation. | Vivo | Rel-19 | Not Handled | Marco(Huawei) comments the KPI Xiaowen (vivo) responds to Marco(Huawei) Alessio (nokia) reminds this is not to be handled Xiaowen (vivo) is ok to mark is as not handled. ==== Revisions Deadline ==== | Not Handled |
| 19.4 | S2-2400836 | P-CR | Approval | 23.700-66: KI#1: new solution on the Energy information collection and exposure for UE and PDU session level. | ZTE | Rel-19 | Not Handled | Not Handled | |
| 19.4 | S2-2401069 | P-CR | Approval | 23.700-66: KI#1, Exposure of Energy Consumption related information. | Lenovo | Rel-19 | Not Handled | Not Handled | |
| 19.4 | S2-2401371 | P-CR | Approval | 23.700-66: New Sol: Monitoring and exposure of Energy Consumption information. | Samsung | Rel-19 | Not Handled | Not Handled | |
| 19.4 | S2-2400124 | P-CR | Approval | 23.700-66: KI#1: New Sol: OAM-Assisted Energy-related information exposure. | NTT DOCOMO | Rel-19 | Revision of (unhandled) S2-2312343 Not Handled | Not Handled | |
| 19.4 | S2-2400110 | P-CR | Approval | 23.700-66: KI #1, New Sol: Energy related information exposure and granularity. | OPPO | Rel-19 | Not Handled | Not Handled | |
| 19.4 | S2-2400086 | P-CR | Approval | 23.700-66: New Solution: Network optimization for energy saving per S-NSSAI. | China Mobile | Rel-19 | Not Handled | Not Handled | |
| 19.4 | S2-2400930 | P-CR | Approval | 23.700-66: KI #2, New Sol Enhancement to define and enforce subscription policies for energy consumption rate for services without QoS criteria. | Rakuten Mobile | Rel-19 | Not Handled | Not Handled | |
| 19.4 | S2-2400125 | P-CR | Approval | 23.700-66: KI#2: New Sol: Energy-aware data transfer policy negotiation. | NTT DOCOMO | Rel-19 | Not Handled | Not Handled | |
| 19.4 | S2-2400388 | P-CR | Approval | 23.700-66: KI#2, New Sol: Enhancements to session related management policy control with energy aspects. | Samsung | Rel-19 | Not Handled | Not Handled | |
| 19.4 | S2-2400725 | P-CR | Approval | 23.700-66: 23.700-66 KI#2: New solution to support subscription enhancement for NG-RAN node PDU session Energy consumption related information report. | Qualcomm Incorporated | Rel-19 | Not Handled | Not Handled | |
| 19.4 | S2-2400838 | P-CR | Approval | 23.700-66: KI#2: new solution on the Subscription and policy control to support energy efficiency. | ZTE | Rel-19 | Not Handled | Not Handled | |
| 19.4 | S2-2400857 | P-CR | Approval | 23.700-66: KI#2 new solution of policy control for multiple accesses based on network energy related information. | CATT | Rel-19 | Not Handled | Not Handled | |
| 19.4 | S2-2400937 | P-CR | Approval | 23.700-66: New Solution KI#2, BDT Policy considering Energy Metrics. | Lenovo | Rel-19 | Not Handled | Not Handled | |
| 19.4 | S2-2401075 | P-CR | Approval | 23.700-66: KI#2, Policy control for Energy Consumption for a UE. | Lenovo | Rel-19 | Not Handled | Not Handled | |
| 19.4 | S2-2401214 | P-CR | Approval | 23.700-66: KI#2 New Solution on QoS Policy update based on UE Preferred Energy Setting. | Nokia, Nokia Shanghai Bell | Rel-19 | Not Handled | Not Handled | |
| 19.4 | S2-2400080 | P-CR | Approval | 23.700-66: TR 23.700-66: New Solution for KI#3. | OPPO | Rel-19 | Not Handled | Not Handled | |
| 19.4 | S2-2400085 | P-CR | Approval | 23.700-66: New Solution: Network function discovery and (re-)selection with Energy Information. | China Mobile | Rel-19 | Not Handled | Not Handled | |
| 19.4 | S2-2400234 | P-CR | Approval | 23.700-66: KI #3, New Sol Network function selection based on NF energy state. | Vivo | Rel-19 | Not Handled | Not Handled | |
| 19.4 | S2-2400541 | P-CR | Approval | 23.700-66: KI#3, New Sol: NF Selection based on NF energy states. | LG Electronics | Rel-19 | Not Handled | Not Handled | |
| 19.4 | S2-2400728 | P-CR | Approval | 23.700-66: TR 23.700-66: KI#3 Solution about NF selection/re-selection based on renewable energy information. | TOYOTA MOTOR CORPORATION, KDDI | Rel-19 | Not Handled | Not Handled | |
| 19.4 | S2-2400757 | P-CR | Approval | 23.700-66: KI#3, New Sol: NF/NF service discovery for network energy saving and efficiency. | NEC | Rel-19 | Not Handled | Not Handled | |
| 19.4 | S2-2400839 | P-CR | Approval | 23.700-66: KI#3, new solution on NF selection enhancement for Energy efficiency. | ZTE | Rel-19 | Not Handled | Not Handled | |
| 19.4 | S2-2400931 | P-CR | Approval | 23.700-66: New Solution KI#3, NF and NF service discovery considering energy criteria. | Lenovo | Rel-19 | Not Handled | Not Handled | |
| 19.4 | S2-2401174 | P-CR | Approval | 23.700-66: KI#3 New Solution on NF selection based on energy-related criteria. | Nokia, Nokia Shanghai Bell | Rel-19 | Not Handled | Not Handled | |
| 19.4 | S2-2401280 | P-CR | Approval | 23.700-66: New Sol: S-NSSAI being subject to energy control . | Samsung | Rel-19 | Not Handled | Not Handled | |
| 19.4 | S2-2400126 | P-CR | Approval | 23.700-66: KI#3: New Sol: NWDAF Energy Analytics. | NTT DOCOMO | Rel-19 | Not Handled | Not Handled | |
| 19.4 | S2-2400153 | P-CR | Approval | 23.700-66: TR 23.700-66: New Solution for KI#3 - Network energy saving and energy efficiency analytics. | OPPO | Rel-19 | Not Handled | Not Handled | |
| 19.4 | S2-2400860 | P-CR | Approval | 23.700-66: KI#3 new solution of network data analytics enhancements for energy saving . | CATT | Rel-19 | Not Handled | Not Handled | |
| 19.4 | S2-2400935 | P-CR | Approval | 23.700-66: New Solution KI#3, Energy Related Analytics . | Lenovo | Rel-19 | Not Handled | Not Handled | |
| 19.4 | S2-2400799 | P-CR | Approval | 23.700-66: KI#3, New solution: Dynamic addition or removal of AMF instance due to energy saving. | Huawei, HiSilicon | Rel-19 | Not Handled | Not Handled | |
| 19.4 | S2-2400947 | P-CR | Approval | 23.700-66: KI#3, New Sol: Energy-aware Analytics Exposure and Data Collection. | Huawei, HiSilicon | Rel-19 | Not Handled | Not Handled | |
| 19.4 | S2-2400958 | P-CR | Approval | 23.700-66: KI#3 New Solution on network analytics of network functions energy consumption. | Nokia, Nokia Shanghai Bell | Rel-19 | Not Handled | Not Handled | |
| 19.4 | S2-2401081 | P-CR | Approval | 23.700-66: New Solution on Energy consumption Analytics and exposure. | China Mobile | Rel-19 | Not Handled | Not Handled | |
| 19.4 | S2-2400185 | P-CR | Approval | 23.700-66: KI#3, New Sol: Energy usage parameters provision via NEF. | NEC | Rel-19 | Not Handled | Not Handled | |
| 19.4 | S2-2400858 | P-CR | Approval | 23.700-66: KI#3 new solution of DNAI selection based on network energy related information . | CATT | Rel-19 | Not Handled | Not Handled | |
| 19.4 | S2-2400874 | P-CR | Approval | 23.700-66: KI #3, New Sol: Enhancement on existing operations for EE and ES. | Vivo | Rel-19 | Not Handled | Not Handled | |
| 19.4 | S2-2400960 | P-CR | Approval | 23.700-66: Nokia, Nokia Shanghai Bell. | KI#3 New Solution on UE energy category analytics | Rel-19 | Not Handled | Not Handled | |
| 19.4 | S2-2401173 | P-CR | Approval | 23.700-66: KI#3 energy saving by sharing of resources across PLMNs. | Nokia, Nokia Shanghai Bell | Rel-19 | Not Handled | Not Handled | |
| 19.4 | S2-2401372 | P-CR | Approval | 23.700-66: KI#3: New Solution on session control for network energy saving. | Samsung | Rel-19 | Not Handled | Not Handled | |
| 19.5 | - | - | - | Study on MPS for IMS Messaging and SMS services (FS_MPS4msg) | - | - | Docs:=14 | - | |
| 19.5 | - | - | - | General / All key issues (1-3) | - | - | Docs:=1 | - | |
| 19.5 | S2-2401240 | P-CR | Approval | 23.700-75: Solution Overall invocation-revocation of MPS for messaging. | Nokia, Nokia Shanghai Bell | Rel-19 | Postponed | Chris (T-Mobile USA] Identifies similarities with other solutions and requests clarification be added if the text remains a separate solution Laurent (Nokia): answers to Chris. Better having these aspects separate (in 1240) than replicated in many other solutions Laurent (Nokia): provides r01 based On chris's comments Shabnam (Ericsson) provides comments and prefers to wait before UDM/HSS controlled invoke/revoke, see below: Chris (T-Mobile USA) Thanks Nokia for the revision and can accept r01 Chris (T-Mobile USA) Suggests documenting the solution and making determination of UDM/HSS controlled invoke/revoke at conclusion stage. Haris(Qualcomm) proposes to note the paper Laurent (Nokia): provides r02 Shabnam (Ericsson) proposes to postpone the invocation/revocation from AF for further discussion, we had long offline discussion and requires more work. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Postponed |
| 19.5 | - | - | - | Key Issue 1 | - | - | Docs:=1 | - | |
| 19.5 | S2-2401241 | P-CR | Approval | 23.700-75: Solution for Key Issue 1 Priority support for IMS based on MPS subscription - general. | Nokia, Nokia Shanghai Bell | Rel-19 | Noted | Chris (T-Mobile USA] provides comments and requests clarification Haris(Qualcomm) proposes to note the paper Laurent (Nokia): withdraws the paper ==== Revisions Deadline ==== | Noted |
| 19.5 | - | - | - | Key Issue 2 | - | - | Docs:=5 | - | |
| 19.5 | S2-2400428 | P-CR | Approval | 23.700-75: TR 23.700-75, SMSoIP solution for Key Issue 2 on Priority support for SMS over IP based on MPS subscription - general. | Peraton Labs, CISA ECD, Verizon, AT&T | Rel-19 | CC#3: r02 + changes Agreed. Revised to S2-2401640. | Chris (T-Mobile USA] Provides comments and requests clarification be added to the solution text Laurent (Nokia): provides r01 Haris(Qualcomm) proposes to note the paper Laurent (Nokia): answers: Haris are you discussing r00 or R01?? Shabnam (Ericsson) provides comments that there are aspects still not agreeable, see below ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 19.5 | S2-2401640 | P-CR | Approval | 23.700-75: TR 23.700-75, SMSoIP solution for Key Issue 2 on Priority support for SMS over IP based on MPS subscription - general. | Peraton Labs, CISA ECD, Verizon, AT&T | Rel-19 | Revision of S2-2400428r02 + changes. Approved | Approved | |
| 19.5 | S2-2400429 | P-CR | Approval | 23.700-75: TR 23.700-75, SMSoIP solution for Key Issue 2 on Priority support for SMS over IP based on MPS subscription - invocation. | Peraton Labs, CISA ECD, Verizon, AT&T | Rel-19 | Postponed | Haris(Qualcomm) proposes to note the paper Laurent (Nokia): We propose to postpone the discussions about invocation/revocation on per message basis (with possibly a timer). For EPS/5GS/IMS entities we at this meeting should only consider subscription data based control ==== Revisions Deadline ==== Laurent (Nokia): objects to any version (postponing the discussion) ==== Final Comments Deadline ==== | Postponed |
| 19.5 | S2-2400430 | P-CR | Approval | 23.700-75: TR 23.700-75, SMSoIP solution for Key Issue 2 on Priority support for SMS over IP based on MPS subscription - procedures. | Peraton Labs, CISA ECD, Verizon, AT&T | Rel-19 | Postponed | Laurent (Nokia): Comments, requests for change Shabnam (Ericsson) resending with correct AI#, Laurent you may want to do same for your original email. Shabnam (Ericsson) provides comments for changes Laurent (Nokia): provides r01 ==== Revisions Deadline ==== Shabnam (Ericsson) provided comments, I am not sure if Laurent addressed them in r01, so better to postpone ==== Final Comments Deadline ==== | Postponed |
| 19.5 | S2-2400431 | P-CR | Approval | 23.700-75: TR 23.700-75, SMSoIP solution for Key Issue 2 on Priority support for SMS over IP based on MPS subscription - IMS routed. | Peraton Labs, CISA ECD, Verizon, AT&T | Rel-19 | CC#3: Postponed | Shabnam (Ericsson) provides comments that it is best to postpone this paper, since other papers cover them and we have different views how to proceed. Sorry missed commenting before revision deadline. | Postponed |
| 19.5 | - | - | - | Key Issue 3 | - | - | Docs:=7 | - | |
| 19.5 | S2-2400216 | P-CR | Approval | 23.700-75: KI#3, New solution MPS support for SMS over NAS. | Ericsson | Rel-19 | r04 Agreed. Revised to S2-2401611, merging S2-2400434 and S2-2401126 | Haris(Qualcomm) provides r01 Ashok (Samsung) comments and proposes to add EN Qian (Ericsson) thanks for the comments/support from Qualcomm and Samsung and provides r02 Ashok (Samsung) proposes S2-2401126 to be considered as merged with this paper and comments on r02 Qian (Ericsson) provides comments and r03 Ashok (Samsung) comments on r03 Qian (Ericsson) responds to Ashok (Samsung) Laurent (Nokia): provides r04 ==== Revisions Deadline ==== Qian (Ericsson): is ok with r04 ==== Final Comments Deadline ==== | Revised |
| 19.5 | S2-2401611 | P-CR | Approval | 23.700-75: KI#3, New solution MPS support for SMS over NAS. | Ericsson, Samsung | Rel-19 | Revision of S2-2400216r04, merging S2-2400434 and S2-2401126. Approved | Approved | |
| 19.5 | S2-2400432 | P-CR | Approval | 23.700-75: TR 23.700-75, SMSoNAS solution for Key Issue 3 on Priority support for SMS over NAS based on MPS subscription - General. | Peraton Labs, CISA ECD, Verizon, AT&T | Rel-19 | Postponed | Chris (T-Mobile USA] Provides comments and requests clarification be added to the solution text Qian (Ericsson) Indicates it shall be treated same way as 0428 ==== Revisions Deadline ==== Qian (Ericsson) propose to postpone the paper, or need to apply the similar changes as agreed in 0428 revision Laurent (Nokia): asks to postpone this paper (any version) ==== Final Comments Deadline ==== | Postponed |
| 19.5 | S2-2400433 | P-CR | Approval | 23.700-75: TR 23.700-75, SMSoNAS solution for Key Issue 3 on Priority support for SMS over NAS based on MPS subscription - invocation. | Peraton Labs, CISA ECD, Verizon, AT&T | Rel-19 | Postponed | Laurent (Nokia): suggests to postpone this paper Qian (Ericsson) indicates that this paper promotes the same principle as in 0429 and shall be handled the same way. ==== Revisions Deadline ==== Laurent (Nokia): objects to any version (postponing the discussion) Qian (Ericsson)supports to postpone the paper ==== Final Comments Deadline ==== | Postponed |
| 19.5 | S2-2400434 | P-CR | Approval | 23.700-75: TR 23.700-75, SMSoNAS MO solution for Key Issue 3 on Priority support for SMS over NAS based on MPS subscription - procedures. | Peraton Labs, CISA ECD, Verizon, AT&T | Rel-19 | Merged into S2-2401611 | Laurent (Nokia): provides r01 Ashok (Samsung) comments Haris(Qualcomm) asks what is the difference between r01 and 0216 Haris(Qualcomm) agrees with Ashok to merge 0434r01 in 0216 Laurent (Nokia): Comments: I am not the author of 434 but I can give my opinion. I can live with merging ==== Revisions Deadline ==== Laurent (Nokia): objects to R00 ==== Final Comments Deadline ==== | Merged |
| 19.5 | S2-2401126 | P-CR | Approval | 23.700-75: 23.700-75: Solution for MPS subscription based priority support for MO SMS over NAS . | Samsung | Rel-19 | Merged into S2-2401611 | Laurent (Nokia): suggests to merge in 0434 ==== Revisions Deadline ==== Laurent (Nokia): objects to any version as the discussion takes place in 0434 (1126 merged in 0434) Ashok (Samsung) author of 1126 has already proposed to merged with 0216. So the correct no os 0216 and not 0434) ==== Final Comments Deadline ==== | Merged |
| 19.5 | S2-2401128 | P-CR | Approval | 23.700-75: 23.700-75: Solution for MPS subscription based priority support for MT SMS over NAS . | Samsung | Rel-19 | Postponed | Robert (Peraton Labs) asks for clarification. Qian (Ericsson) provides comments. Ashok (Samsung) responds to Robert. Qian (Ericsson) provides comments related to paging. Ashok (Samsung) answers to Qian (Ericsson) Qian (Ericsson) provides further comments. Laurent (Nokia): asks to postpone this paper Ashok (Samsung) provides response to Laurent (Nokia) Laurent (Nokia): answers to ashok Ashok (Samsung) respond to Laurent Qian (Ericsson) provides clarification ==== Revisions Deadline ==== Ashok (Samsung) responds to Qian (Ericsson) and Laurent (Nokia) Laurent (Nokia): objects to any version for the sake of postponing ==== Final Comments Deadline ==== | Postponed |
| 19.6 | - | - | - | Study on Architecture Enhancements for Vehicle Mounted Relays Phase 2 (FS_VMR_Ph2) | - | - | Docs:=35 | - | |
| 19.6 | - | - | - | TR skeleton & Scope | - | - | Docs:=3 | - | |
| 19.6 | S2-2400128 | P-CR | Approval | 23.700-06: Cover page for TR 23.700-06 skeleton. | Sony, Qualcomm Incorporated | Rel-19 | Approved | Approved | |
| 19.6 | S2-2401295 | P-CR | Approval | 23.700-06: Scope for TR 23.700-06 on VMR_Ph2. | Qualcomm Incorporated, Nokia, Nokia Shanghai Bell. | Rel-19 | r02 Agreed. Revised to S2-2401701. | LiMeng (Huawei) provides comments. Qian (Ericsson) provides comments and r01. Hong (Qualcomm) provides r02. ==== Revisions Deadline ==== Qian (Ericsson) is ok with r02. LiMeng (Huawei) is ok with r02. ==== Final Comments Deadline ==== | Revised |
| 19.6 | S2-2401701 | P-CR | Approval | 23.700-06: Scope for TR 23.700-06 on VMR_Ph2. | Qualcomm Incorporated, Nokia, Nokia Shanghai Bell. | Rel-19 | Revision of S2-2401295r02. Approved | Approved | |
| 19.6 | - | - | - | TR terminology, architchtural assumptions, requirements | - | - | Docs:=6 | - | |
| 19.6 | S2-2401300 | P-CR | Approval | 23.700-06: Definitions and terminologies for TR 23.700-06 on VMR_Ph2. | Qualcomm Incorporated, Nokia, Nokia Shanghai Bell | Rel-19 | r02 Agreed. Revised to S2-2401702. | Qian (Ericsson) provides r01 Alessio(Nokia) provides r02 ==== Revisions Deadline ==== Hong (Qualcomm) is fine with r02. Qian (Ericsson) is fine with r02. ==== Final Comments Deadline ==== | Revised |
| 19.6 | S2-2401702 | P-CR | Approval | 23.700-06: Definitions and terminologies for TR 23.700-06 on VMR_Ph2. | Qualcomm Incorporated, Nokia, Nokia Shanghai Bell | Rel-19 | Revision of S2-2401300r02. Approved | Approved | |
| 19.6 | S2-2400845 | P-CR | Approval | 23.700-06: Architecture assumptions and requirements for TR 23.700-06 on VMR_Ph2. | Sony, Qualcomm Incorporated, Nokia, Nokia shanghai Bell, IIT Bombay, Samsung, LG Electronics, DISH Network | Rel-19 | r04 Agreed. Revised to S2-2401703. | LiMeng (Huawei) provides comments. Fei (OPPO) comments. Qian (Ericsson) provides comments and r01. Lalith (Samsung) provides r02. Lars (Sony) answer on SNPN. Alessio(Nokia) provides r03 LaeYoung (LGE) comments. Lalith (Samsung) comments. LaeYoung (LGE) responds to Lalith (Samsung). Chris (Vodafone) suggests some alternative text. Lars (Sony) responds to Chris (Vodafone) suggestion. LaeYoung (LGE) provides comment. Chris (Vodafone) implements the alternative text in r04. ==== Revisions Deadline ==== LaeYoung (LGE) is OK with r04. Lars (Sony) is OK with r04. Qian (Ericsson) is OK with r04. ==== Final Comments Deadline ==== | Revised |
| 19.6 | S2-2401703 | P-CR | Approval | 23.700-06: Architecture assumptions and requirements for TR 23.700-06 on VMR_Ph2. | Sony, Qualcomm Incorporated, Nokia, Nokia shanghai Bell, IIT Bombay, Samsung, LG Electronics, DISH Network, Ericsson | Rel-19 | Revision of S2-2400845r04. Approved | Approved | |
| 19.6 | S2-2400323 | P-CR | Approval | 23.700-06: Architecture assumptions for FS_VMR_Ph2. | LG Electronics | Rel-19 | r06 Agreed. Revised to S2-2401704. | LiMeng (Huawei) provides suggestions to revise. LaeYoung (LGE) provides r01. Fei (OPPO) comments. LaeYoung (LGE) replies to Fei (OPPO). Qian (Ericsson) provides comments. Hong (Qualcomm) provides r02. Alessio (Nokia) supports the simple approach of R01. LaeYoung (LGE) is fine with r02 and thanks to Hong (Qualcomm). Chris (Vodafone) feels the picture misleads the reader into thinking that UE and MWAB UE are using common AMF/SMF etc. Hong (Qualcomm) comments. LaeYoung (LGE) provides r04. Pranav (IIT Bombay) has a query. LaeYoung (LGE) provides r03. Lars (Sony comments on r03 and r04. LaeYoung (LGE) provides r05. Qian (Ericsson) comments on r05. LaeYoung (LGE) provides r06. ==== Revisions Deadline ==== Qian (Ericsson) is ok with r06. Lars (Sony) is ok with r06. ==== Final Comments Deadline ==== | Revised |
| 19.6 | S2-2401704 | P-CR | Approval | 23.700-06: Architecture assumptions for FS_VMR_Ph2. | LG Electronics, IIT Bombay | Rel-19 | Revision of S2-2400323r06. Approved | Approved | |
| 19.6 | - | - | - | New Key Issues | - | - | Docs:=14 | - | |
| 19.6 | S2-2400925 | P-CR | Approval | 23.700-06: New KI: Authorization of a MWAB and Configuration of a MWAB-UE. | Nokia, Nokia shanghai Bell, Sony, LG Electronics, Samsung | Rel-19 | r06 Agreed. Revised to S2-2401705. | LiMeng (Huawei) provides r01. Qian (Ericsson) provides comments and r04 (asks to ignore r03 which is uploaded unintentionally). Hong (Qualcomm) provides r02. Alessio(Nokia) prefers calling out explicitly the two components .provides r05 improving the text a bit LaeYoung (LGE) comments on r05. LiMeng (Huawei) comments on r05. LaeYoung (LGE) provides r06. Nokia OK with r06 ==== Revisions Deadline ==== Qian (Ericsson) is OK with r06 ==== Final Comments Deadline ==== | Revised |
| 19.6 | S2-2401705 | P-CR | Approval | 23.700-06: New KI: Authorization of a MWAB and Configuration of a MWAB-UE. | Nokia, Nokia shanghai Bell, Sony, LG Electronics, Samsung | Rel-19 | Revision of S2-2400925r06. Approved | Approved | |
| 19.6 | S2-2400802 | P-CR | Approval | 23.700-06: New KI: MWAB Architecture and procedures. | Nokia, Nokia shanghai Bell, Sony | Rel-19 | r03 Agreed. Revised to S2-2401706. | LiMeng (Huawei) asks for clarification. Qian (Ericsson) provides comments and r01. Hong (Qualcomm) provides r02. Fei (OPPO) asks questions regarding N3 connectivity Alessio(nokia) provides r03 and replies to Fei (OPPO) LiMeng (Huawei) comments on r03 LaeYoung (LGE) provides r04. Alessio (nokia) objects to r04. LaeYoung (LGE) is fine to go with r03. ==== Revisions Deadline ==== Qian (Ericsson) is ok with r03. ==== Final Comments Deadline ==== | Revised |
| 19.6 | S2-2401706 | P-CR | Approval | 23.700-06: New KI: MWAB Architecture and procedures. | Nokia, Nokia shanghai Bell, Sony | Rel-19 | Revision of S2-2400802r03. Approved | Approved | |
| 19.6 | S2-2400222 | P-CR | Approval | 23.700-06: New KI RAN-CN connection handling. | Ericsson | Rel-19 | Noted | Qian (Ericsson) provides answers Lars (Sony) ask a question Hong (Qualcomm) comments. Qian (Ericsson) provides further comments Alessio(Nokia) is not considering this KI in scope of a SA2 study and should be more a RAN3 type of discussion. Objects to this KI LaeYoung (LGE) provides r01. alessio(Nokia) if you have specific solution on RAN/CN connection please use the KI on architecture. Do not create one pointing to solutions . we ask to note this paper. Alessio(Nokia) clarifies that authorization aspects have already a KI, configuration have a KI, architetutal KI exists, mobility KI exists. No need of this other KI. Qian (Ericsson) replies and indicates that current text just points out the directions of the study of the KI without intention for specific solution. We can continue the discussion on which doc can be used to document the aspects related to the CN-RAN interface. alessio(Nokia) believes this paper is too details almost at solution level in rAN3. You can bring solutions using the existing architecture KI. Sorry we object to this paper as standalone and especially as you mention protocol level topics. ==== Revisions Deadline ==== Qian (Ericsson) disagree that it's about detailed solution oriented description and indicates that we can continue the discussion in next meeting. | Noted |
| 19.6 | S2-2400830 | P-CR | Approval | 23.700-06: New KI: Handling of N2/N3 communication in 5GC for MWAB. | IIT Bombay | Rel-19 | Postponed | LiMeng (Huawei) asks for clarification. Pranav (IIT Bombay) provides response to LiMeng (Huawei) Lars (Sony) ask Pranav (IIT Bombay) for further clarification Pranav (IIT Bombay) provides response to Lars (Sony) Fei (OPPO) comments. Pranav (IIT Bombay) provides response to Fei (OPPO), Lars (Sony) and LiMeng(Huawei) and uploads a new version. Lars (Sony) comment further. Pranav (IIT Bombay) provides response to Lars (Sony) and uploads a new version. Alessio(Nokia) believes the aspect in this proposed KI can be submitted as solution to architectural KI, including how to support QoS using the existing QoS mechanisms. If you see anything is preventing you to do so in the architecture KI, please change that. ==== Revisions Deadline ==== Qian (Ericsson) propose to postpone the paper. Pranav (IIT Bombay) responds to Qian (Ericsson) and requests to consider the paper. Qian (Ericsson) provides further responses. LiMeng (Huawei) comments. Pranav (IIT Bombay) responds to LiMeng (Huawei), and Qian (Ericsson) and all ==== Final Comments Deadline ==== | Postponed |
| 19.6 | S2-2400644 | P-CR | Approval | 23.700-06: New KI: Control of UE's access to 5GS via a wireless access backhaul. | Huawei, HiSilicon | Rel-19 | r02 Agreed. Revised to S2-2401707. | Lars (Sony) ask some questions and provides r01 alessio(nokia) provides r02 further simplifying the text. LiMeng (Huawei) is fine with r01 and r02 thanks for the revision. ==== Revisions Deadline ==== Hong (Qualcomm) is fine with r02. Qian (Ericsson) is ok with r02. Lars (Sony) is ok with r02. ==== Final Comments Deadline ==== | Revised |
| 19.6 | S2-2401707 | P-CR | Approval | 23.700-06: New KI: Control of UE's access to 5GS via a wireless access backhaul. | Huawei, HiSilicon | Rel-19 | Revision of S2-2400644r02. Approved | Approved | |
| 19.6 | S2-2401317 | P-CR | Approval | 23.700-06: New key issue for VMR_Ph2 on mobility support. | Qualcomm Incorporated | Rel-19 | r02 Agreed. Revised to S2-2401708. | LiMeng (Huawei) asks for clarification. Lars (Sony) comments on the figure Hong (Qualcomm) provides r01. Lars (Sony) likes the new figure in r01. alessio(Nokia) also likes the figures of r01 but provides r02 to like also the text Qian (Ericsson) provides comments Hong (Qualcomm) comments and fine with r02. LiMeng (Huawei) comments regarding mobility. ==== Revisions Deadline ==== Hong (Qualcomm) replies to LiMeng. Qian (Ericsson) is fine with r02. ==== Final Comments Deadline ==== | Revised |
| 19.6 | S2-2401708 | P-CR | Approval | 23.700-06: New key issue for VMR_Ph2 on mobility support. | Qualcomm Incorporated | Rel-19 | Revision of S2-2401317r02. Approved | Approved | |
| 19.6 | S2-2400849 | P-CR | Approval | 23.700-06: New KI: Support of location services. | Sony, Nokia, Nokia shanghai Bell | Rel-19 | r03 Agreed. Revised to S2-2401709. | LiMeng (Huawei) comments. Lars (Sony) responds to LiMeng (Huawei) comment. Qian (Ericsson) provides comments and r01. Hong (Qualcomm) clarifies that Hong (Qualcomm) provided r02. LiMeng (Huawei) provides r03 and clarifies r02 is from Hong. Qian (Ericsson) provides comments and r02. Lars (Sony) thanks LiMeng (Huawei) for r03, it looks fine. Alessio(Nokia) provides r04 Hong (Qualcomm) comments on r04. ==== Revisions Deadline ==== Qian (Ericsson) provides comments and suggest to go with r03. Object to r04. Lars (Sony) is ok with r03. Alessio(Nokia) ok with r03 but let's write in minutes we need to cover this aspect of location of cell (ID) of MWAB (may be needed for regulations) ==== Final Comments Deadline ==== | Revised |
| 19.6 | S2-2401709 | P-CR | Approval | 23.700-06: New KI: Support of location services. | Sony, Nokia, Nokia shanghai Bell | Rel-19 | Revision of S2-2400849r03. Approved | Approved | |
| 19.6 | S2-2400851 | P-CR | Approval | 23.700-06: New KI: Support of emergency services. | Sony, Samsung, Nokia, Nokia shanghai Bell | Rel-19 | r01 + changes Agreed. Revised to S2-2401710. | LiMeng (Huawei) asks for clarification. LiMeng (Huawei) suggests a revision for the cause code. Lars (Sony) responds to LiMeng (Huawei) and asks Lalith (Samsung) to clarify 'graceful release'. LiMeng (Huawei) withdraws his previous comment. LiMeng (Huawei) comments. Lalith (Samsung) comments. Lars (Sony) thanks Lalith for the clarification and provides r01. ==== Revisions Deadline ==== Qian (Ericsson) request to add 'Whether and' in the beginning of the 2nd bullet on top of r01. Lars (Sony) is ok with the following: On top of r01 add 'Whether and' in the beginning of the 2nd bullet. Lalith(Samsung) OK with proposal of Qian (Ericsson) to add 'Whether and' in the beginning of the 2nd bullet on top of r01. ==== Final Comments Deadline ==== | Revised |
| 19.6 | S2-2401710 | P-CR | Approval | 23.700-06: New KI: Support of emergency services. | Sony, Samsung, Nokia, Nokia shanghai Bell | Rel-19 | Revision of S2-2400851r01 + changes. Approved | Approved | |
| 19.6 | - | - | - | Not handled due to quota | - | - | Docs:=12 | - | |
| 19.6 | S2-2400641 | P-CR | Approval | 23.700-06: New term of MWAB. | Huawei, HiSilicon | Rel-19 | Not Handled | Not Handled | |
| 19.6 | S2-2400220 | P-CR | Approval | 23.700-06: Architecture assumptions. | Ericsson | Rel-19 | Not Handled | Not Handled | |
| 19.6 | S2-2400639 | P-CR | Approval | 23.700-06: Architecture assumptions for FS_VMR_Ph2. | Huawei, HiSilicon | Rel-19 | Not Handled | Not Handled | |
| 19.6 | S2-2400640 | P-CR | Approval | 23.700-06: Architecture requirements for FS_VMR_Ph2. | Huawei, HiSilicon | Rel-19 | Not Handled | Not Handled | |
| 19.6 | S2-2400221 | P-CR | Approval | 23.700-06: New KI Authorization handling. | Ericsson | Rel-19 | Not Handled | Not Handled | |
| 19.6 | S2-2400642 | P-CR | Approval | 23.700-06: Key issue for authorization and configuration of MWAB. | Huawei, HiSilicon | Rel-19 | Not Handled | Not Handled | |
| 19.6 | S2-2400507 | P-CR | Approval | 23.700-06: New KT: KI on WT#1 for supporting the architecture with a gNB onboard of a relay. | OPPO | Rel-19 | Not Handled | Not Handled | |
| 19.6 | S2-2401125 | P-CR | Approval | 23.700-06: 23.700-06: New KI for FS_VMR_Ph2 WT#1. | CATT | Rel-19 | Not Handled | Not Handled | |
| 19.6 | S2-2400646 | P-CR | Approval | 23.700-06: New KI: Support of the establishment management of the N2/N3 for the onboard gNB. | Huawei, HiSilicon | Rel-19 | Not Handled | Not Handled | |
| 19.6 | S2-2401327 | P-CR | Approval | 23.700-06: New key issue for VMR_Ph2 on UE access control. | Qualcomm Incorporated | Rel-19 | Not Handled | Not Handled | |
| 19.6 | S2-2400645 | P-CR | Approval | 23.700-06: New KI: Efficient mobility and service continuity. | Huawei, HiSilicon | Rel-19 | Not Handled | Not Handled | |
| 19.6 | S2-2400643 | P-CR | Approval | 23.700-06: New KI: location services for UEs accessing via a gNB onboard of a MWAB. | Huawei, HiSilicon | Rel-19 | Not Handled | Not Handled | |
| 19.7 | - | - | - | Study on System Enhancement for Proximity-based Services in 5GS - Phase 3 (FS_5G_ProSe_Ph3) | - | - | Docs:=28 | - | |
| 19.7 | - | - | - | TR skeleton and scope | - | - | Docs:=3 | - | |
| 19.7 | S2-2401332 | P-CR | Approval | 23.700-03: 23.700-03: TR Skeleton for FS_5G_ProSe_Ph3. | KPN N.V. | Rel-19 | Approved | Approved | |
| 19.7 | S2-2401335 | P-CR | Approval | 23.700-03: Scope for FS_5G_ProSe_Ph3. | KPN, AT&T (Rapporteurs), FirstNet, MITRE | Rel-19 | Remove MITRE from source companies. Revised to S2-2401641. | Revised | |
| 19.7 | S2-2401641 | P-CR | Approval | 23.700-03: Scope for FS_5G_ProSe_Ph3. | KPN N.V., AT&T (Rapporteurs), FirstNet | Rel-19 | Revision of S2-2401335. Approved | Approved | |
| 19.7 | - | - | - | Terms and architectural requirements and assumptions | - | - | Docs:=7 | - | |
| 19.7 | S2-2400407 | P-CR | Approval | 23.700-03: Terms, Architecture Requirements and Assumptions of Multi-hop U2N/U2U Relay for 5G_ProSe_Ph3. | Huawei, HiSilicon | Rel-19 | r08 + changes Agreed. Revised to S2-2401808, merging S2-2400647 and S2-2401353 | Zhang Fu(Huawei) provide r01 Nassima (KPN) comments and provides r02 Hugh (AT&T) comments on definition of intermediate relay. Nassima (KPN) agrees with comments from AT&T and provides r03 Hong (Qualcomm) comments on r04. LaeYoung (LGE) provides comment and answer. Fei (OPPO) comments and provides r04 Deng Qiang (CATT) comments. Jianning (XIAOMI) comments. Mehrdad (MediaTek Inc.) provides comment Tingyu (Samsung) provides comments. Zhang (Huawei) provide r05 LaeYoung (LGE) thinks the EN in r05 is good to move forward. Nassima (KPN) provides comments on r05 Shabnam (Ericsson) has concern, asks clarification why we introduce new entity/role before we understand the purpose? LaeYoung (LGE) provide r06 with some answers. Shabnam (Ericsson) comments to LGE that each soln may intend to use different term because the intent is to serve different purpose, see below Hugh (AT&T) provides comments. Nassima (KPN) comments, is fine with r06 LaeYoung (LGE) provides r07 including the NOTE suggested by Shabnam (Ericsson). Jianning (XIAOMI) comments on r09. Zhang Fu (Huawei) is OK with r07, and correct that Xiaomi is commenting r07, which is the latest version Jianning (XIAOMI) is ok with r07. Thanks Zhang Fu's correction. Mehrdad (MediaTek Inc.) is ok with r07 LaeYoung (LGE) comments. Shabnam (Ericsson) provides r08 simplifying and combining the two NOTEs LaeYoung (LGE) is fine with r08 and thanks to Shabnam (Ericsson) for combining the two NOTEs. Zhang (Huawei) thanks Shabnam and OK with r08 ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 19.7 | S2-2401808 | P-CR | Approval | 23.700-03: Terms, Architecture Requirements and Assumptions of Multi-hop U2N/U2U Relay for 5G_ProSe_Ph3. | Huawei, HiSilicon, LG Electronics, KPN | Rel-19 | Revision of S2-2400407r08 + changes, merging S2-2400647 and S2-2401353. Approved | Approved | |
| 19.7 | S2-2400521 | P-CR | Approval | 23.700-03: 23.700-03: Architecture Requirement for FS_5G_ProSe_Ph3 . | CATT | Rel-19 | Merged into S2-2401809 | Nassima (KPN) suggests to merge into S2-2401334. Key points have been included in S2-2401334r01 ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 19.7 | S2-2400647 | P-CR | Approval | 23.700-03: Term and Architecture Assumptions about multi-hop U2N relaying. | LG Electronics | Rel-19 | Merged into S2-2401808 | Nassima (KPN) suggests to merge into S2-2400407 and S2-2401334. Key points have been included in S2-2400407r01 and S2-2401334r01 LaeYoung (LGE) is fine to merge this P-CR into S2-2400407 and S2-2401334. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 19.7 | S2-2401334 | P-CR | Approval | 23.700-03: Architecture requirements and assumptions for FS_5G_ProSe_Ph3. | KPN, AT&T (Rapporteurs), FirstNet, MITRE | Rel-19 | r07 + changes Agreed. Revised to S2-2401809, merging S2-2400521 | Nassima (KPN) provides r01 to merge other contributions Jungje(Interdigital) comments Fei (OPPO) provided r02. Hong (Qualcomm) comments on r01. Deng Qiang (CATT) comments on r02. Nassima (KPN) comments on r02 Mehrdad (MediaTek Inc.) provides r03. Tingyu (Samsung) provides comments. Shabnam (Ericsson) provides comments asking clarification, please see below Nassima (KPN) responds to comments, provides r05 Deng Qiang (CATT) provides r06 and co-signed. Zhang Fu (Huawei) provide r07 and co-signed. Tingyu (Samsung) supports r07 and also would like to co-sign. Jungje(Interdigital) supports r07 and would like to co-sign. ==== Revisions Deadline ==== Mehrdad (MediaTek Inc.) is OK with r07 and would like to co-source. ==== Final Comments Deadline ==== | Revised |
| 19.7 | S2-2401809 | P-CR | Approval | 23.700-03: Architecture requirements and assumptions for FS_5G_ProSe_Ph3. | KPN N.V., AT&T (Rapporteurs), FirstNet, CATT, Huawei, HiSilicon, Samsung, Interdigital, MediaTek | Rel-19 | Revision of S2-2401334r07 + changes, merging S2-2400521. Approved | Approved | |
| 19.7 | S2-2401353 | P-CR | Approval | 23.700-03: Terms and abbreviations for FS_5G_ProSe_Ph3. | KPN N.V. | Rel-19 | Merged into S2-2401808 | Nassima (KPN) proposes to merge into S2-2400407 ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 19.7 | - | - | - | WT#1.1: Multi-hop U2N Relay | - | - | Docs:=5 | - | |
| 19.7 | S2-2400508 | P-CR | Approval | 23.700-03: New KI: KI on multi-hop U2N relays. | OPPO | Rel-19 | Merged into S2-2401810 | Nassima (KPN) proposes to merge into S2-2401334. Key points have been included in S2-2401339r01 ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 19.7 | S2-2400523 | P-CR | Approval | 23.700-03: 23.700-03: New KI for FS_5G_ProSe_Ph3 WT#1.1. | CATT | Rel-19 | Merged into S2-2401810 | Nassima (KPN) proposes to merge into S2-2401334. Key points have been included in S2-2401339r01 ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 19.7 | S2-2400906 | P-CR | Approval | 23.700-03: New KI: Support Multi-hop UE-to-Network Relay. | ZTE | Rel-19 | Merged into S2-2401810 | Nassima (KPN) proposes to merge into S2-2401334. Key points have been included in S2-2401339r01 ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 19.7 | S2-2401339 | P-CR | Approval | 23.700-03: FS_5G_ProSe_Ph3 New Key Issue for Work Task #1.1. | KPN N.V., AT&T (Rapporteurs), FirstNet | Rel-19 | r10 + changes Agreed. Revised to S2-2401810, merging S2-2400508, S2-2400523 and S2-2400906 | Hao (ZTE) comments. Nassima (KPN) provides r01 to merge other contributions Hong (Qualcomm) provides r02. Fei (OPPO) provides r03. Nassima (KPN) comments on r03 Deng Qiang (CATT) comments on multi-path transmission. Jianning (XIAOMI) comments. ==== Revisions Deadline ==== Changzheng (China Telecom) is fine with r10 and would like to co-sign. ==== Final Comments Deadline ==== | Revised |
| 19.7 | S2-2401810 | P-CR | Approval | 23.700-03: FS_5G_ProSe_Ph3 New Key Issue for Work Task #1.1. | KPN N.V., AT&T (Rapporteurs), FirstNet, CATT, Xiaomi, MediaTek, Huawei, Samsung, OPPO, China Telecom | Rel-19 | Revision of S2-2401339r10 + changes, merging S2-2400508, S2-2400523 and S2-2400906. Approved | Approved | |
| 19.7 | - | - | - | WT#1.2: Multi-hop U2U Relay | - | - | Docs:=5 | - | |
| 19.7 | S2-2400437 | P-CR | Approval | 23.700-03: FS_5G_ProSe_Ph3 New Key Issue for Work Task #1.2. | AT&T, KPN, FirstNet, InterDigital, Intel, MITRE | Rel-19 | r06 + changes Agreed. Revised to S2-2401811, merging S2-2400408, S2-2400671, S2-2400961 and S2-2401157 | Changzheng (China Telecom) comments. Hugh (AT&T) provided comments and revision r01 Hong (Qualcomm) provides r02. Deng Qiang (CATT) asks question for clarifications. Mehrdad (MediaTek Inc.) thinks r02 is in the right direction with understanding that the scope of Key Issue is L3 Relay Zhang (Huawei) provides r03 Tingyu (Samsung) confirms co-signing. Hugh (AT&T) provides comments and r04 Jianning (XIAOMI) comments on r04. Hugh (AT&T) provides comments to XIAOMI. Fei (OPPO) comments and provides r05. Jianning (XIAOMI) replies to Hugh (AT&T). Zhang Fu (Huawei) object r04 and r05 Shabnam (Ericsson) provides r06 ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 19.7 | S2-2401811 | P-CR | Approval | 23.700-03: FS_5G_ProSe_Ph3 New Key Issue for Work Task #1.2. | AT&T, KPN, FirstNet, InterDigital, Intel, CATT, XIAOMI | Rel-19 | Revision of S2-2400437r06 + changes, merging S2-2400408, S2-2400671, S2-2400961 and S2-2401157. Approved | Approved | |
| 19.7 | S2-2400671 | P-CR | Approval | 23.700-03: New Key Issue on WT #1.2. | China Telecom | Rel-19 | Merged into S2-2401811 | Hugh(AT&T) proposes to merge part related to WT#1.2 into S2-2400437. Keys points are reflected in S2-2400437r01. Hugh(AT&T) proposes to merge into S2-2400437. Keys points are reflected in S2-2400437r01. ==== Revisions Deadline ==== Changzheng (China Telecom) confirm to merge this Tdoc into S2-2400437 ==== Final Comments Deadline ==== | Merged |
| 19.7 | S2-2400961 | P-CR | Approval | 23.700-03: New key issue for WT1.2 Supporting 5G ProSe U2U Relay Service with multi-hops. | Xiaomi | Rel-19 | Merged into S2-2401811 | Hugh(AT&T) proposes to merge into S2-2400437. Keys points are reflected in S2-2400437r01. Jianning (XIAOMI) is ok to merge into S2-2400437. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 19.7 | S2-2401157 | P-CR | Approval | 23.700-03: New KI: Support for multi-hop U2U Relay . | Samsung | Rel-19 | Merged into S2-2401811 | Hugh(AT&T) proposes to merge into S2-2400437. Keys points are reflected in S2-2400437r01. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 19.7 | - | - | - | WT#1.1 and WT#1.2 | - | - | Docs:=1 | - | |
| 19.7 | S2-2400408 | P-CR | Approval | 23.700-03: Key issue for WT1 of 5G ProSe multi-hop U2N/U2U Relay support. | Huawei, HiSilicon | Rel-19 | Merged into S2-2401811 | Hugh(AT&T) proposes to merge part related to WT#1.2 into S2-2400437. Keys points are reflected in S2-2400437r01. Nassima (KPN) proposes to merge the part related to WT#1.1 into S2-2401334. Key points have been included in S2-2401339r01 ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 19.7 | - | - | - | Discussion papers | - | - | Docs:=1 | - | |
| 19.7 | S2-2401269 | DISCUSSION | Endorsement | How to progress the work on FS_5G_ProSe_Ph3 | Intel | Rel-19 | Noted | Shabnam (Ericsson) provides comments and believes it is premature to endorse the proposal and as such propose to note. Nassima (KPN) shares the same view as Shabnam (Ericsson), supports noting the document Saso (Intel) is OK to note. ==== Revisions Deadline ==== | Noted |
| 19.7 | - | - | - | Documents exceeding TU budget | - | - | Docs:=6 | - | |
| 19.7 | S2-2400522 | P-CR | Approval | 23.700-03: 23.700-03: Architecture Assumption for FS_5G_ProSe_Ph3 . | CATT | Rel-19 | Not Handled | ==== Final Comments Deadline ==== | Not Handled |
| 19.7 | S2-2400524 | P-CR | Approval | 23.700-03: 23.700-03: New KI for FS_5G_ProSe_Ph3 WT#1.2. | CATT | Rel-19 | Not Handled | ==== Final Comments Deadline ==== | Not Handled |
| 19.7 | S2-2400670 | P-CR | Approval | 23.700-03: New Key Issue on WT #1.1. | China Telecom, | Rel-19 | Not Handled | ==== Final Comments Deadline ==== | Not Handled |
| 19.7 | S2-2400907 | P-CR | Approval | 23.700-03: Architecture Requirements and Assumptions. | ZTE | Rel-19 | Not Handled | ==== Final Comments Deadline ==== | Not Handled |
| 19.7 | S2-2400959 | P-CR | Approval | 23.700-03: New key issue for WT1.1 Supporting 5G ProSe U2N Relay Service with multi-hops. | Xiaomi | Rel-19 | Not Handled | ==== Final Comments Deadline ==== | Not Handled |
| 19.7 | S2-2401156 | P-CR | Approval | 23.700-03: New KI: Support for multi-hop U2N Relay . | Samsung | Rel-19 | Not Handled | ==== Final Comments Deadline ==== | Not Handled |
| 19.8 | - | - | - | Study on User Identities and Authentication Architecture (FS_UIA_ARC) | - | - | Docs:=19 | - | |
| 19.8 | - | - | - | Skeleton | - | - | Docs:=1 | - | |
| 19.8 | S2-2400422 | P-CR | Approval | 23.700-32: FS_UIA_ARC TR 23.700-32 Skeleton. | InterDigital Inc. | Rel-19 | Approved | Kefeng (Qualcomm) provides comments Jianning (XIAOMI) comments. Mike (InterDigital) replies. Peter Hedman (Ericsson) provides comments on 6.x.1 ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Approved |
| 19.8 | - | - | - | Scope | - | - | Docs:=2 | - | |
| 19.8 | S2-2400567 | P-CR | Approval | 23.700-32: FS_UIA_ARC TR Scope . | InterDigital Inc., Nokia, Nokia Shanghai Bell | Rel-19 | r04 Agreed. Revised to S2-2401612. | Peter Hedman (Ericsson) provides comments Mike (InterDigital) provides r01. Peter Hedman (Ericsson) ok with r01 Mike (InterDigital) provides r02 Peng (OPPO) is fine with r02 Mike (InterDigital) provides r03 to add a co-signer Peng (OPPO) is ok to co-sign Mike (InterDigital) provides r04 to add a co-signer ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 19.8 | S2-2401612 | P-CR | Approval | 23.700-32: FS_UIA_ARC TR Scope . | InterDigital Inc., Nokia, Nokia Shanghai Bell, Ericsson, Deutsche Telekom, OPPO, Huawei | Rel-19 | Revision of S2-2400567r04. Approved | Approved | |
| 19.8 | - | - | - | Terms | - | - | Docs:=3 | - | |
| 19.8 | S2-2400568 | P-CR | Approval | 23.700-32: FS_UIA_ARC Terms . | InterDigital Inc., Nokia, Nokia Shanghai Bell | Rel-19 | r08 Agreed. Revised to S2-2401613, merging S2-2401236 | Srinivas Garikipati (Nokia) provides comments to r02 Susan (Huawei) provides r02 Mike (InterDigital) provides r01 Susan (Huawei) replies to Srinivas. Srinivas Garikipati (Nokia) replies to Susan. Jianning (XIAOMI) comments. zhendong (ZTE) provides the comments Kefeng (Qualcomm) provides comments. Rahil (CableLabs) provides comments. Peter Hedman (Ericsson) provides comments, and draft suggested terms... Susan (Huawei) replies to Peter Hedman (Ericsson). Srinivas Garikipati (Nokia) comments on the removed terms in r02 Mike (InterDigital) replies and provides r03. Jianning (XIAOMI) comments on r03 Peter Hedman (Ericsson) provides r04 and comments Susan (Huawei) provides comments on the term 'link'. Mike (InterDigital) comments. Peter Hedman (Ericsson) Identifier Link works for now, we may realize later whether there is need to update it Naman (Samsung) comments Peng (OPPO) comments Jianning (XIAOMI) comments and provide r05 Susan (Huawei) provides r06. Peter Hedman (Ericsson) provides r07 Mike (InterDigital) provides r08 which is editorial/formatting only. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 19.8 | S2-2401613 | P-CR | Approval | 23.700-32: FS_UIA_ARC Terms . | InterDigital Inc., Nokia, Nokia Shanghai Bell, OPPO, Ericsson, Huawei, Deutsche Telekom | Rel-19 | Revision of S2-2400568r08, merging S2-2401236. Approved | Approved | |
| 19.8 | S2-2401236 | P-CR | Approval | 23.700-32: More Terms on FS_UIA_ARC . | InterDigital Inc., [OPPO] | Rel-19 | Merged into S2-2401613 | Mike (InterDigital) proposes to merge this into S2-2400568 Peng (OPPO) agreed to merge this into S2-2400568 ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 19.8 | - | - | - | Architectural Assumptions and Requirements | - | - | Docs:=3 | - | |
| 19.8 | S2-2400569 | P-CR | Approval | 23.700-32: FS_UIA_ARC Architectural Assumptions and Requirements . | InterDigital Inc., Nokia, Nokia Shanghai Bell | Rel-19 | r22 + changes Agreed. Revised to S2-2401632, merging S2-2400956 | Srinivas Garikipati (Nokia) provides comments to r02 Susan (Huawei) provides r02 Mike (InterDigital) provides r01 Jianning (XIAOMI) comments on r02. Susan (Huawei) replies Naman (Samsung) provides comments Srinivas Garikipati (Nokia) replies to Susan Kefeng (Qualcomm) provides comments Magnus (Ericsson) provides comments Huazhang (vivo) provide comments on r02 Rahil (CableLabs) provides comments Mike (InterDigital) replies and provides r03. Naman (Samsung) replies to Susan (Huawei). zhendong (ZTE) provides the response Mike (InterDigital) replies to Zhendong (ZTE) Susan (Huawei) replies and provides r04. zhendong (ZTE) provides the comments to r03 Susan (Huawei) replies to Naman (Samsung). Naman (Samsung) provides r05 Jianning (XIAOMI) comments on r04. Susan (Huawei) replies to Naman. Peter Hedman (Ericsson) provides r06 Susan (Huawei) provides r07. Naman (Samsung) replies to Susan (Huawei) and asks for clarification Jianning (XIAOMI) comments on r07 and provides r08. Naman (Samsung) replies to zhendong (ZTE) Srinivas Garikipati (Nokia) comments and provides r09. zhendong (ZTE) provides the response to Naman (Samsung) Mike (InterDigital) comments and provides r10. Rahil (CableLabs) provides r11. Mike (InterDigital) comments on r11 Rahil (CableLabs) replies to Mike (InterDigital). Mike (InterDigital) replies to Rahil (CableLabs) Rahil (CableLabs) provides r12. Naman (Samsung) adds support and provides r13 Huazhang (vivo) ask a question to Mike and Rahil about ' When the user identifier applies to a human, the services that are accessed by the user (e.g., SMS service, MO, MT, Location services) are not required to know the user identifier.' Peter Hedman (Ericsson) provides reply to Huazhang and draft proposal Jianning (XIAOMI) comments. Susan (Huawei) provides r14. Magnus H (Ericsson) provides r15 Srinivas Garikipati (Nokia) comments and also provides r16 Susan (Huawei) does not accept r16 Magnus H (Ericsson) provides comments Arun Y( Cable Labs) comments on r16 Arun Y( Cable Labs) replying to Mike (InterDigital) Mike (InterDigital) replies to Arun Y( Cable Labs) Peng (OPPO) provides r18 Mike (InterDigital) provides r17 Naman (Samsung) provides r19 and comments Jianning (XIAOMI) comments on NOTE2 of R19 Srinivas Garikipati (Nokia) asks clarification from Naman (Samsung) Dimitris (Lenovo) provides r20 Naman (Samsung) replies to Srinivas (Nokia), Jianning (Xiaomi) Srinivas Garikipati (Nokia) provides further comments to Naman Jianning (XIAOMI) replies to Naman (Samsung). Iskren (NEC) expresses concern with Note 1 Srinivas Garikipati (Nokia) provides feedback to Jianning Susan (Huawei) replies to Jianning (XIAOMI). Mike (InterDigital) provides r21 Peng (OPPO) provides r22 ==== Revisions Deadline ==== Arun Yerra(Cable Labs) provides r23 Junan (China Mobile) comments Junan (China Mobile) replies to Jianning (XIAOMI) and Mike (InterDigital) Dimitris (Lenovo) is ok with r22 - co-signs Jianning (XIAOMI) is ok with R22. Arun (Cable Labs) is not okay with R22. We will accept R22 if NOTE3 in architectural assumptions changed to 'It is assumed that the non-3GPP devices do not support 5G authentication nor NAS behavior'. Peng (OPPO) replies to Arun Arun (Cable Labs) replies to Peng (OPPO). Mike (InterDigital) proposes to agree to r22 + change NOTE 3 to 'It is assumed that the non-3GPP devices do not support 5G authentication (e.g. 5G-AKA) nor NAS behavior.' ==== Final Comments Deadline ==== | Revised |
| 19.8 | S2-2401632 | P-CR | Approval | 23.700-32: FS_UIA_ARC Architectural Assumptions and Requirements . | InterDigital Inc., Nokia, Nokia Shanghai Bell, Xiaomi, Ericsson, Samsung, NEC, OPPO, Huawei, Deutsche Telekom, Lenovo, Cable Labs, LG Electronics | Rel-19 | Revision of S2-2400569r22 + changes, merging S2-2400956. Approved | Approved | |
| 19.8 | S2-2400956 | P-CR | Approval | 23.700-32: FS_UIA_ARC Architectural Assumptions and Requirements . | Xiaomi | Rel-19 | Merged into S2-2401632 | Mike (InterDigital) proposes to merge this into S2-2400569. Jianning (XIAOMI) agrees to merge into 0569. . ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 19.8 | - | - | - | WT#1 | - | - | Docs:=4 | - | |
| 19.8 | S2-2400570 | P-CR | Approval | 23.700-32: FS_UIA_ARC New Key Issue for Work Task #1 . | InterDigital Inc., Nokia, Nokia Shanghai Bell | Rel-19 | r14 + changes Agreed. Revised to S2-2401633, merging S2-2400957 and S2-2401085 | Myungjune (LGE) provides comments. Mike (InterDigital) provides r01. Jianning (XIAOMI) is ok to merge into 0570, and provide further comments on r02. Naman (Samsung) provides comments and r03 Jianning (XIAOMI) comments Myungjune (LGE) replies to Jianning (XIAOMI) Jianning (XIAOMI) replies to Myungjune (LGE). Magnus (Ericsson) provides comments Mike (InterDigital) replies Susan (Huawei) provides r05. Mike (InterDigital) accepts Kefeng's (Qualcomm) proposal to remove the overlap between 570 and 571 Peng (OPPO) provides comments. Kefeng (Qualcomm) proposes to remove the overlap between 570 and 571 zhendong (ZTE) askes for clarification Jianning (XIAOMI) comments on r05. Peter Hedman (Ericsson) provides r06 Susan (Huawei) comments on r06 Jianning (XIAOMI) comments. Peter Hedman (Ericsson) provides comments and r07 Mike (InterDigital) comments Iskren (NEC) provides comments and r08 Myungjune (LGE) comments on r08 Srinivas Garikipati (Nokia) comments Susan (Huawei) replies to Jianning. Kefeng (Qualcomm) is not OK with r08. Susan (Huawei) replies to Peter Hedman (Ericsson). Peter Hedman (Ericsson) provides reply to Susan and comments to r08 Jianning (XIAOMI) comments on r08. Iskren (NEC) provides r09 where priority is removed.. Jianning (XIAOMI) comments and provides r10. Mike (InterDigital) comments and provides r11. Peter Hedman (Ericsson) provides r12 Peng (OPPO) is ok with r12. Jianning (XIAOMI) can live with r12. Dieter (Deutsche Telekom) asks question for clarification Peter Hedman (Ericsson) provides reply to Dieter Mike (InterDigital) replies to Dieter (Deutsche Telekom) Dieter (Deutsche Telekom) thank you for the clarification. Could you please add Deutsche Telekom as supporting company to r12? Mike (InterDigital) provides r13 to add a co-signer Peng (OPPO) provides r14 to add a co-signer ==== Revisions Deadline ==== Naman (Samsung) is fine with r14 as well Myungjune (LGE) is ok with r14 with editorial change. Dimitris (Lenovo) ok with r14 - co-signs Mike (InterDigital) agrees that 'r14+delete text with strikethrough format' is the preferred outcome. ==== Final Comments Deadline ==== | Revised |
| 19.8 | S2-2401633 | P-CR | Approval | 23.700-32: FS_UIA_ARC New Key Issue for Work Task #1 . | InterDigital Inc., Nokia, Nokia Shanghai Bell, Xiaomi, China Mobile, Ericsson, NEC, Deutsche Telekom, OPPO, Huawei, LG Electronics, Samsung, Lenovo | Rel-19 | Revision of S2-2400570r14 + changes, merging S2-2400957 and S2-2401085. Approved | Approved | |
| 19.8 | S2-2400957 | P-CR | Approval | 23.700-32: New KI related to WT1 supporting user identifier of a human in 5G system . | Xiaomi | Rel-19 | Merged into S2-2401633 | Mike (InterDigital) proposes to merge this into S2-2400570. Jianning (XIAOMI) agrees to merge into 0570. . ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 19.8 | S2-2401085 | P-CR | Approval | 23.700-32: New KI for Work Task #1 of FS_UIA_ARC. | China Mobile | Rel-19 | Merged into S2-2401633 | Mike (InterDigital) proposes to merge this into S2-2400570. Aihua(CMCCl) agrees to merge it into S2-2400570. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 19.8 | - | - | - | WT#2 | - | - | Docs:=2 | - | |
| 19.8 | S2-2400571 | P-CR | Approval | 23.700-32: FS_UIA_ARC Two New Key Issues for Work Task #2 . | InterDigital Inc., Nokia, Nokia Shanghai Bell | Rel-19 | r07 Agreed. Revised to S2-2401614. | Yan Li (China Telecom) provides comments Naman (Samsung) provides r01 Myungjune (LGE) asks question on meaning of roaming. Jianning (XIAOMI) comments. Dimitris (Lenovo) comments Mike (InterDigital) replies and provides r02 Naman (Samsung) replies Susan (Huawei) raises a question to Naman (Samsung) zhendong (ZTE) provides the comments Naman (Samsung) replies to Susan (Huawei) Peter Hedman (Ericsson) provides r03 Iskren (NEC) ask question. Srinivas Garikipati (Nokia) responds to the query of Iskren Iskren (NEC) responds to Srinivas Garikipati (Nokia) Srinivas Garikipati (Nokia) responds to the query of Iskren regarding the mapping of KI to WT. Iskren (NEC) provides r04 Sudeep (Apple) comments on r04. Srinivas Garikipati (Nokia) asks for clarification from Iskren Iskren (NEC) comments Srinivas Garikipati (Nokia) provides reasoning from the SID and KI proposals that WT1 and WT2 are for human use case and WT3 is for device use case. Iskren (NEC) comments. Srinivas Garikipati (Nokia) provides comments Peter Hedman (Ericsson) provides comments to ongoing discussion on restrictions... Mike (InterDigital) comments about the restrictions.. Mike (InterDigital) is ok with r05 Peter Hedman (Ericsson) provides r05 Jianning (XIAOMI) can live with r05. Iskren (NEC) is OK with r05. Yan Li (China Telecom) finds the previous proposed change which was adopted in r02 is missing in the latest revision, and requests to bring it back. Peter Hedman (Ericsson) provides r06 Naman (Samsung) provides r07 ==== Revisions Deadline ==== Myungjune (LGE) is ok with r07 Dimitris (Lenovo) ok with r07 - co-signs Jianning (XIAOMI) is ok with R07, happy to co-sign Peng (OPPO) is ok with r07, and as a co-signer. ==== Final Comments Deadline ==== | Revised |
| 19.8 | S2-2401614 | P-CR | Approval | 23.700-32: FS_UIA_ARC Two New Key Issues for Work Task #2 . | InterDigital Inc., Nokia, Nokia Shanghai Bell, NEC, Ericsson, Samsung, Huawei, Deutsche Telekom, Lenovo, Xiaomi, LG Electronics, OPPO | Rel-19 | Revision of S2-2400571r07. Approved | Approved | |
| 19.8 | - | - | - | WT#3 | - | - | Docs:=4 | - | |
| 19.8 | S2-2400572 | P-CR | Approval | 23.700-32: FS_UIA_ARC New Key Issue for Work Task #3 . | InterDigital Inc., Nokia, Nokia Shanghai Bell | Rel-19 | r17 + changes Agreed. Revised to S2-2401634, merging S2-2400539 and S2-2400711 | Srinivas Garikipati (Nokia) provides comment on r02 Susan (Huawei) replies. Myungjune (LGE) comments on r02. Susan (Huawei) provides r02 Mike (InterDigital) provides r01 Jianning (XIAOMI) comments on r02 Rahil (CableLabs) comments on r02. Mike (InterDigital) provides r04 Peng (OPPO) provides comments. Mike (InterDigital) comments on r05 and r06. Yildirim (Charter Communications) replies to Kefeng (Qualcomm). Kefeng (Qualcomm) provides comments to r05, r06. Peng (OPPO) comments. Rahil (CableLabs) provides r06. Yildirim (Charter Communications) comments and provides r05. Kefeng (Qualcomm) is not OK with the newly added NOTE4in r04 and r02. Susan (Huawei) provides r07. Susan (Huawei) replies to Kefeng (Qualcomm). Ashok (Samsung) comments Jianning (XIAOMI) comments on r07. Peter Hedman (Ericsson) provides comments to r07 Srinivas Garikipati (Nokia) Provides comments for various versions and provides r08 Ashok (Samsung) thanks Srinivas for the clarification Rahil (CableLabs) provides r09. Mike (InterDigital) comments and provides r10. Ashok (Samsung) responds to Myungjune (LGE) Myungjune (LGE) comments on r11. Ashok (Samsung) provides r11. Srinivas Garikipati (Nokia) Provides comments and r12 Ashok (Samsung) is not OK with r12 Myungjune responds to Ashok (Samsung) . Jianning (XIAOMI) comments. Ashok (Samsung) responds to Jianning (XIAOMI). Jianning (XIAOMI) replies to Ashok (Samsung). Magnus H (Ericsson) provides r13 iskren (NEC) provides r14 Arun Y(Cable Labs) comments Arun Y( Cable Labs) comments Ashok (Samsung) responds to Arun Y Peng (OPPO) provides comments and r15. Arun Y( Cable Labs) is Okay with r13, not okay with r14 Iskren (NEC) provides comment Iskren (NEC) r15 is not acceptable for us. Mike (InterDigital) proposes a compromise in r16 Iskren (NEC) provides comments Peng (OPPO) provides further comments. Rahil (CableLabs) provides r17. ==== Revisions Deadline ==== Peng (OPPO) comments on r17. Peng (OPPO) comments, and provides r18. Ashok (Samsung) agrees with explanation from Junan (China Mobile) and ok with r16, r17. Myungjune (LGE) is ok with r16, r17. Junan (China Mobile) comments Jianning (XIAOMI) cannot accept any versions (R16, R17) with restrictions on non-3GPP devices behind UE/5G-RG. In order for progress the SID, we can live R16/R17 with removing 'whether and how the operator restricts the number of simultaneously active non-3GPP devices per SUPI (i.e., per subscription). ', and adding Editor's Note 'Editor's Note: it is FFS to include 'whether and how the operator restricts the number of simultaneously active non-3GPP devices per SUPI (i.e., per subscription)' in this key issue.' Mike (InterDigital) is ok with the proposal from Jianning (XIAOMI) = r17+remove bullet and add EN. Peng (OPPO) cannot accept r16, r17 Arun (Cable Labs) agrees with Mike(InterDigital), okay with Jianning (XIAOMI) for r17 with bullet removed. Mike (InterDigital) responds to Peng(OPPO) Iskren (NEC) is OK with r16 Iskren (NEC) can accept r16 or r17 Peng (OPPO) replies to Mike (InterDigital). Mike (InterDigital) proposes R17 + remove 'whether and how the operator restricts the number of simultaneously active non-3GPP devices per SUPI (i.e., per subscription). ', and adding Editor's Note 'Editor's Note: it is FFS whether to include in this key issue 'whether and how the operator restricts the number of simultaneously active non-3GPP devices per SUPI (i.e., per subscription)' in this key issue.' And add '5G-AKA authentication for non-3GPP devices behind 5G-RG is not assumed in this study' to NOTE 1. Jianning (XIAOMI) supports Mike's proposal as compromised option Ashok (Samsung) comments on the proposal Srinivas Garikipati (Nokia) is fine with Mike Proposal on r17. Jianning (XIAOMI) replies. Peng (OPPO) is ok with Mike's proposal, + remove the minor wording issue in ED, i.e., the duplicated 'in this key issue' at the end of the sentence. Iskren (NEC) comments. ==== Final Comments Deadline ==== Junan (China Mobile) replied to Jianning (XiaoMi) about restricting the number of simultaneously active non-3GPP devices per SUPI Iskren (NEC) - this is marked as agreed however, it should be discussed at CC#4 as the updates to r17 are not acceptable. | Revised |
| 19.8 | S2-2401634 | P-CR | Approval | 23.700-32: FS_UIA_ARC New Key Issue for Work Task #3 . | InterDigital Inc., Nokia, Nokia Shanghai Bell, CMCC, Qualcomm Incorporated, Deutsche Telekom, Huawei, LG Electronics, Cable Labs | Rel-19 | Revision of S2-2400572r17 + changes, merging S2-2400539 and S2-2400711. Approved | Approved | |
| 19.8 | S2-2400539 | P-CR | Approval | 23.700-32: New Key Issue on identification of non-3GPP devices. | Qualcomm Incorporated | Rel-19 | Merged into S2-2401634 | Mike (InterDigital) proposes to merge this paper into S2-2400572 Kefeng (Qualcomm) is OK to merge with S2-2400572 ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 19.8 | S2-2400711 | P-CR | Approval | 23.700-32: FS_UIA_ARC New Key Issue for Work Task #3. | CMCC | Rel-19 | Merged into S2-2401634 | Mike (InterDigital) proposes to merge this paper into S2-2400572 ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 19.9 | - | - | - | Study on Enhancement of support for Edge Computing in 5G Core network - Phase 3 (FS_eEDGE_5GC_ph3) | - | - | Docs:=33 | - | |
| 19.9 | - | - | - | Rapporteur's input (TR skeleton, scope) | - | - | Docs:=3 | - | |
| 19.9 | S2-2400476 | DRAFT TR | Approval | TR 23.700-49 skeleton | Intel (Rapporteur) | Rel-19 | Add missing cover page (see S2-2400128 for example). Revised to S2-2401376. | Revised | |
| 19.9 | S2-2401376 | DRAFT TR | Approval | TR 23.700-49 skeleton | Intel (Rapporteur) | Rel-19 | Revision of S2-2400476. Approved | Approved | |
| 19.9 | S2-2400477 | P-CR | Approval | 23.700-49: Scope for TR 23.700-49. | Intel | Rel-19 | Agreed. Approved | Stefano (Qualcomm) asks clarification and for a revision to be made. Haiyang (Huawei) comments. Changhong (Intel) replies to Stefano and Haiyang comments. Tezcan Cogalan (Nokia) agrees with the rapporteur and prefers the original submission. Haiyang (Huawei) clarifies. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Approved |
| 19.9 | - | - | - | Architecture assumption and requirements | - | - | Docs:=6 | - | |
| 19.9 | S2-2400800 | P-CR | Approval | 23.700-49: Architecture assumption for EAS (re-)discovery. | Huawei, HiSilicon | Rel-19 | r05 Agreed. Revised to S2-2401711, merging S2-2400879 and S2-2401114 | Fenqin (Huawei) provides r01. Changhong (Intel) proposes to use it as baseline for Architecture Assumption. Hyesung (Samsung) comments. Stefano (Qualcomm) expresses concerns. Fenqin (Huawei) responds. Magnus (Ericsson) provides r02 Yuan Tao (CATT) agrees to merge S2-2400879 into this paper, and provides r03. Tezcan (Nokia) agrees to merge Clause 4.1 in S2-2401225 to this paper, as proposed by the rapporteur. Tezcan (Nokia) supports removal of KI specific assumptions from Clause 4.1. Changhong (Intel) provides r04 and cosigns. Fenqin (Huawei) provides r05. ==== Revisions Deadline ==== Hyesung (Samsung) suggests to go with either r05 or 04, not ok with r00, r01. Fenqin (Huawei) accept only r05, r00, r01. Tezcan (Nokia) prefers r05, OK with r02, NOT OK with r00, r01, r03. Changhong (Intel) proposes to accept r05. ==== Final Comments Deadline ==== | Revised |
| 19.9 | S2-2401711 | P-CR | Approval | 23.700-49: Architecture assumption for EAS (re-)discovery. | Huawei, HiSilicon, Intel, Nokia, Nokia Shanghai Bell | Rel-19 | Revision of S2-2400800r05, merging S2-2400879 and S2-2401114. Approved | Approved | |
| 19.9 | S2-2400879 | P-CR | Approval | 23.700-49: Architecture assumptions and principles. | CATT | Rel-19 | Merged into S2-2401711 | Fenqin (Huawei) comments. Changhong (Intel) proposes to merge into S2-2400800. Yuan Tao (CATT) is fine to merge this CR into S2-2400800 per rapporteur's suggestion . ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 19.9 | S2-2401114 | P-CR | Approval | 23.700-49: Architectural Assumptions and Requirements. | ZTE | Rel-19 | Merged into S2-2401711 | Fenqin (Huawei) comments. Changhong (Intel) proposes to merge it into S2-2401225. Hyesung (Samsung) comments. Stefano (Qualcomm) expresses concerns on being too solution oriented Jinguo(ZTE) is ok to use 0800 and 1225 as basis ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 19.9 | S2-2401225 | P-CR | Approval | 23.700-49: TR 23.700-49 Architectural Assumptions and Principles. | Nokia, Nokia Shanghai Bell | Rel-19 | r05 Agreed. Revised to S2-2401712. | Changhong (Intel) proposes to use it as Architecture Requirements. Jinguo(ZTE) agree to use 1225 as basis and request to incorporate all inputs in the next revision Fenqin(Huawei) provides r01 Tezcan Cogalan (Nokia) agrees to use two different papers on Arch Assumptions and Requirements and provides r02. Fenqin (Huawei) provides a response and r03. Hyesung (Samsung) comments on r03. Fenqin (Huawei) provides a response. Tezcan (Nokia) provides r04. Fenqin (Huawei) suggest to go r03 Tezcan (Nokia) responds to Fenqin and suggest to use r04 Changhong (Intel) comments on impacts to Application layer. Fenqin (Huawei) comments. Changhong (Intel) prefers r05. Fenqin (Huawei) responds to Tezcan and provide r05. Tezcan (Nokia) responds to Fenqin and Changhong. Tezcan (Nokia) responds to Changhong and Fenqin ==== Revisions Deadline ==== Fenqin (Huawei) accept only r05, r03, r01 Hyesung (Samsung) suggests to go with r05, but not ok with r03~r00. Tezcan (Nokia) prefers r04, OK with r05, NOT OK with r03 and 01 ==== Final Comments Deadline ==== | Revised |
| 19.9 | S2-2401712 | P-CR | Approval | 23.700-49: TR 23.700-49 Architectural Assumptions and Principles. | Nokia, Nokia Shanghai Bell | Rel-19 | Revision of S2-2401225r05. Approved | Approved | |
| 19.9 | - | - | - | WT#1.1 related key issue papers | - | - | Docs:=7 | - | |
| 19.9 | S2-2400291 | P-CR | Approval | 23.700-49: New KI for WT#1.1: Reduce impact on central NFs for Edge Computing. | Samsung | Rel-19 | Merged into S2-2401713 | Hyesung (Samsung) is ok to merge it into S2-2400325. Changhong (Intel) proposes to merge it into S2-2400325. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 19.9 | S2-2400325 | P-CR | Approval | 23.700-49: New key issue: Reducing impact on central 5GC NFs to support EAS (re)discovery and UPF (re)selection. | China Mobile | Rel-19 | r10 Agreed. Revised to S2-2401713, merging S2-2400291, S2-2400718, S2-2400801 and S2-2401226 | Dan (China Mobile) provides r01 with merging from S2-2400291,S2-2400718,S2-2400801,S2-2401226. And response to Stefano's comment Changhong (Intel) proposes to use it as baseline for the key issue related to WT#1.1. Stefano (Qualcomm) expresses concerns. Tezcan Cogalan (Nokia) provides r02. Fenqin (Huawei) provides r03. Changhong (Intel) provides r04 and cosigns. Tezcan (Nokia) provides r05 Dan(China Mobile) provides r06 to remove the change over change Fenqin (Huawei) provides r07 Hyesung (Samsung ) provides r09 with minor updates Changhong (Intel) provides r08 with rephrasing. Magnus (Ericsson) provides r10 ==== Revisions Deadline ==== Hyesung (Samsung) is ok with r10 Dan(China Mobile) is OK with r10 Fenqin (Huawei) is ok with r10 Tezcan (Nokia) is OK with r10 and would like to co-sign as Nokia and Nokia Shanghai Bell Changhong (Intel) proposes to accept r10. ==== Final Comments Deadline ==== | Revised |
| 19.9 | S2-2401713 | P-CR | Approval | 23.700-49: New key issue: Reducing impact on central 5GC NFs to support EAS (re)discovery and UPF (re)selection. | China Mobile, Intel, Huawei, HiSilicon, Samsung | Rel-19 | Revision of S2-2400325r10, merging S2-2400291, S2-2400718, S2-2400801 and S2-2401226. Revised to add Nokia in S2-2401645. | Revised | |
| 19.9 | S2-2401645 | P-CR | Approval | 23.700-49: New key issue: Enhancements for EAS (re)discovery and UPF (re)selection with reducing impact on central 5GC NFs. | China Mobile, Intel, Huawei, HiSilicon, Samsung,Nokia, Nokia Shanghai Bell | Rel-19 | Revision of S2-2401713. Approved | Approved | |
| 19.9 | S2-2400718 | P-CR | Approval | 23.700-49: New KI: Support more efficient Edge Hosting Environment information management and related EAS Discovery. | LG Electronics | Rel-19 | Merged into S2-2401713 | Changhong (Intel) proposes to merge it into S2-2400325. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 19.9 | S2-2400801 | P-CR | Approval | 23.700-49: New KI for WT1.1: Supporting efficient Edge Data Network and EAS related information management for EAS (re-)Discovery. | Huawei, HiSilicon | Rel-19 | Merged into S2-2401713 | Changhong (Intel) proposes to merge it into S2-2400325. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 19.9 | S2-2401226 | P-CR | Approval | 23.700-49: KI description for WT#1.1. | Nokia, Nokia Shanghai Bell | Rel-19 | Merged into S2-2401713 | Changhong (Intel) proposes to merge it into S2-2400325. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 19.9 | - | - | - | WT#1.2 related key issue papers | - | - | Docs:=3 | - | |
| 19.9 | S2-2400293 | P-CR | Approval | 23.700-49: New KI for WT#1.2: enhancement of EAS and local UPF (re)selection. | Samsung | Rel-19 | r12 Agreed. Revised to S2-2401714, merging S2-2400881 | Changhong (Intel) proposes to use it as the baseline for key issue related to WT#1.2. Haiyang (Huawei) provides r01 Magnus (Ericsson) provides r02 Tezcan Cogalan (Nokia) provides r03. Hyesung (Samsung) provides r04. Yuan Tao (CATT) provides r05. Changhong (Intel) provides r06 and cosigns. Haiyang (Huawei) provides r08 Tezcan (Nokia) provides r07 and cosigns Magnus (Ericsson) Prefers r07 Haiyang (Huawei) comments to Magnus (Ericsson) Haiyang (Huawei) provides r10 Dan (China Mobile) suggest to add China Mobile as supporting company Hyesung (Samsung) provides r09 Hyesung (Samsung) provides r11 Magnus O (Ericsson) not ok with r10 0r r11, provides r12 Hyesung (Samsung) is ok with r12 Tezcan (Nokia) is fine with r12 ==== Revisions Deadline ==== Hyesung (Samsung) suggests to go with r12, not ok with r10, r08, r01 Haiyang (Huawei) is OK with r12 Yuan Tao (CATT) is fine with r12. ==== Final Comments Deadline ==== | Revised |
| 19.9 | S2-2401714 | P-CR | Approval | 23.700-49: New KI for WT#1.2: enhancement of EAS and local UPF (re)selection. | Samsung, Huawei, HiSilicon, CATT, Intel, Nokia, Nokia Shanghai Bell, China Mobile | Rel-19 | Revision of S2-2400293r12, merging S2-2400881. Approved | Approved | |
| 19.9 | S2-2400881 | P-CR | Approval | 23.700-49: New Key Issue: Enhancement to EAS (re)discovery based on WT#1.2. | CATT | Rel-19 | Merged into S2-2401714 | Changhong (Intel) proposes to merge it into S2-2400293. Yuan Tao (CATT) is fine to merge this CR into S2-2400293 per rapporteur's suggestion . ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 19.9 | - | - | - | WT#2 related key issue papers | - | - | Docs:=5 | - | |
| 19.9 | S2-2400327 | P-CR | Approval | 23.700-49: New key issue: Support traffic routing between local DN and central DN. | China Mobile | Rel-19 | Merged into S2-2401715 | Changhong (Intel) proposes to merge it into S2-2400479. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 19.9 | S2-2400479 | P-CR | Approval | 23.700-49: New Key Issue: EC Traffic Routing between local DN and central DN. | Intel | Rel-19 | r07 + changes Agreed. Revised to S2-2401715, merging S2-2400327, S2-2400759 and S2-2400914 | Changhong (Intel) proposes to use it as the baseline for the key issue related to WT#2 on traffic routing between local DN and central DN. Haiyang (Huawei) provides r01 Yuan Tao (CATT) supports this paper. Changhong (Intel) provides r02 with adding some cosigners. Tezcan (Nokia) provides r03 which merges S2-2400327, S2-2400914 and S2-2400759r02 Hyesung (Samsung) asks questions Hiroshi (NEC) accepts the r03. Haiyang (Huawei) objects r03, cannot agree to merge 2-UE scenario into this KI. Changhong (Intel) comments and provides r05. Haiyang (Huawei) suggests to go with r02. Tezcan (Nokia) responds to comments and provides r04 including more co-signers and further updates Haiyang (Huawei) provides r06. Tezcan (Nokia) objects r06 and prefers r05 Changhong (Intel) provides r07. Haiyang (Huawei) provides comments. Changhong (Intel) replies to Haiyang. Jiahui (China Telecom) provides comment. Changhong (Intel) provides r08. Haiyang (Huawei) provides r09. Yuan Tao (CATT) comments. ==== Revisions Deadline ==== Tezcan (Nokia) is ok with r07 if 'server in local part of DN' is removed from the parentheses in the last bullet, and not OK with r08 or r09 Changhong (Intel) asks to put it on CC#3's agenda and propose to agree r07 with removing 'has' and 'server in local part of DN'. Tezcan (Nokia) is OK with Changhong's proposal ==== Final Comments Deadline ==== | Revised |
| 19.9 | S2-2401715 | P-CR | Approval | 23.700-49: New Key Issue: EC Traffic Routing between local DN and central DN. | Intel, Huawei, HiSilicon, CATT, China Telecom, Nokia, Nokia Shanghai Bell, NEC | Rel-19 | Revision of S2-2400479r07 + changes, merging S2-2400327, S2-2400759 and S2-2400914. Approved | Approved | |
| 19.9 | S2-2400759 | P-CR | Approval | 23.700-49: New KI: 5GS enhancements for traffic handlings between DNs. | NEC | Rel-19 | Merged into S2-2401715 | Changhong (Intel) proposes to use it as the baseline for key issue related to WT#2 on traffic routing between two local DNs. Stefano (Qualcomm) asks clarifications. Changhong (Intel) replies to Stefano's question. Haiyang (Huawei) agrees with Changhong (Intel) to have 2 KIs. Tezcan Cogalan (Nokia) has concerns with the approach. Magnus (Ericsson) Agrees with Tezcan and Stefano Changhong (Intel) replies to Tezcan on two UEs. Tezcan Cogalan (Nokia) replies to Changhong on two UEs. Changhong (Intel) further replies to Tezcan. Fenqin (Huawei) share the same view as Changhong. Tezcan (Nokia) responds to Changhong (Intel) and Fenqin (Huawei) and asks further clarifications. Changhong (Intel) provides r01. Changhong (Intel) asks Magnus to clarify the scenario on local to local. Hiroshi (NEC) responds to Changhong (Intel) and Stefano (Qualcomm). Yuan Tao (CATT) asks for clarification. Magnus (Ericsson) proposes to have one KI for WT2 and use 0479 as base. Jiahui (China Telecom) provides comment. Hiroshi (NEC) responds to Changhong (Intel), Magnus (Ericsson) and Jiahui (China Telecom) . Changhong (Intel) asks Magnus to illustrate more on the scenario. Fenqin (Huawei) also try to understand the UC of local DN<> local DN. Changhong (Intel) proposes to mark this paper as 'merged into 0479'. ==== Revisions Deadline ==== Magnus H (Ericsson) support Changhong's proposal Hiroshi (NEC) also support Changhong's proposal ==== Final Comments Deadline ==== | Merged |
| 19.9 | S2-2400914 | P-CR | Approval | 23.700-49: New KI for WT2: Support of cloud application traffic routing between the local DN and Central DN . | China Telecom | Rel-19 | Merged into S2-2401715 | Changhong (Intel) proposes to merge it into S2-2400479. Stefano (Qualcomm) conditionally objects due to being a solution in search for a key issue. Jiahui (China Telecom) agrees to merge this paper into S2-2400479. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 19.9 | - | - | - | Documents exceeding TU budget/quota | - | - | Docs:=9 | - | |
| 19.9 | S2-2400478 | P-CR | Approval | 23.700-49: Architecture assumption. | Intel | Rel-19 | Not Handled | Not Handled | |
| 19.9 | S2-2400880 | P-CR | Approval | 23.700-49: New Key Issue: Support for localized information handling based on WT#1.1. | CATT | Rel-19 | Not Handled | Not Handled | |
| 19.9 | S2-2400278 | P-CR | Approval | 23.700-49: New KI for WT1.2: Local UPF and EAS (re-)discovery considering N6 delay and EAS load. | Huawei, HiSilicon | Rel-19 | Not Handled | Not Handled | |
| 19.9 | S2-2400326 | P-CR | Approval | 23.700-49: New key issue: Local UPF and EAS (re)selection considering N6 delay. | China Mobile | Rel-19 | Not Handled | Not Handled | |
| 19.9 | S2-2401227 | P-CR | Approval | 23.700-49: KI description for WT#1.2. | Nokia, Nokia Shanghai Bell | Rel-19 | Not Handled | Not Handled | |
| 19.9 | S2-2400279 | P-CR | Approval | 23.700-49: New KI for WT#2: Support traffic routing between local DN and central DN. | Huawei, HiSilicon | Rel-19 | Not Handled | Not Handled | |
| 19.9 | S2-2400480 | P-CR | Approval | 23.700-49: New Key Issue: EC Traffic Routing between two local DNs serving two UEs. | Intel | Rel-19 | Not Handled | Not Handled | |
| 19.9 | S2-2400882 | P-CR | Approval | 23.700-49: New Key Issue: Traffic steering between different DNs based on WT#2. | CATT | Rel-19 | Not Handled | Not Handled | |
| 19.9 | S2-2401228 | P-CR | Approval | 23.700-49: KI description for WT#2. | Nokia, Nokia Shanghai Bell | Rel-19 | Not Handled | Not Handled | |
| 19.10 | - | - | - | Study on Phase 3 for UAS, UAV and UAM (FS_UAS_Ph3) | - | - | Docs:=31 | - | |
| 19.10 | - | - | - | LSs | - | - | Docs:=5 | - | |
| 19.10 | S2-2400074 | LS In | Action | LS from SA WG6: LS on Coordination of work for UAS_Ph3 | SA WG6 (S6-234027) | Rel-19 | Response drafted in S2-2400115. Final response in S2-2401812 | Replied to | |
| 19.10 | S2-2400115 | LS OUT | Approval | [DRAFT] Reply LS on Coordination of work for UAS_Ph3 | LG Electronics | Rel-19 | Response to S2-2400074. r05 + clean up Agreed. Revised to S2-2401812. | Saubhagya (Nokia) provides r02. Guanzhou (InterDigtial) supports this LS. Stefano (Qualcomm) proposes R01 Runze (Huawei) provides comment. Amanda ( Futurewei ) prefer r01 from Qualcomm Saubhagya (Nokia) prefers Ericsson proposal and responds to Amanda (Futurewei). Shabnam (Ericsson) provides comments that prefers Nokia clarification and additional questions LaeYoung (LGE) provides r03. Amanda ( Futurewei ) supports LGE's r03 Runze(Huawei) supports r03 Saubhagya (Nokia) provide comments LaeYoung (LGE) replies to Saubhagya (Nokia) and confirms that r04 in the server is from LaeYoung (LGE). Saubhagya (Nokia) asks to ignore the last comment and provides further comments Saubhagya (Nokia) provides r04 LaeYoung (LGE) provides r04. ==== Revisions Deadline ==== Amanda ( Futurewei ) is fine with r04 Guanzhou (InterDigtial) provides r05. Saubhagya (Nokia) OK with r05 LaeYoung (LGE) proposes to go with r05 instead of r04. Runze (Huawei) supports r04 and r05, but points out r05 is after revision deadline. LaeYoung (LGE) thinks that LS Out revised after revision deadline can be on the table and can be agreed if no one complains. ?? Wanqiang (Session Chair) confirm that LS Out revision is still allowed after the deadline. Amanda ( Futurewei ) supports r05 ==== Final Comments Deadline ==== | Revised |
| 19.10 | S2-2401812 | LS OUT | Approval | Reply LS on Coordination of work for UAS_Ph3 | SA WG2 | Rel-19 | Revision of S2-2400115r05 + clean up. Approved | Approved | |
| 19.10 | S2-2400102 | LS OUT | Approval | [DRAFT] LS on No-Transmit Zones according to ECC decision 22(07) | QUALCOMM Europe Inc. - Spain | Rel-19 | r07 Agreed. Revised to S2-2401813. | Ashok (Samsung) provides r02 LaeYoung (LGE) provides r01. Guanzhou (InterDigtial) provides r05 and questions Ashok(Samsung)'s removal of Q2. Guanzhou (InterDigtial) comments on r04 removal of question 'Does NTZ apply to all UAVs in the area invariably or some UAVs may be exempt'. Shabnam (Ericsson) provides comments and provides r04 (Interdigital provided r03 and not r05 as comments state) Saubhagya (Nokia) provide comments, asks for clarification and answers to question from Guanzhou (InterDigtial) Ashok (Samsung) asking clarifications from Guanzhou (InterDigtial) and Shabnam (Ericsson). Dimitris (Lenovo) comments and provides r05 Stefano (Faccin) replies to Huawei Runze (Huawei) comments on r06 Stefano (Faccin) comments and provides r06 Shabnam (Ericsson) provides additional comments and can not yet agree to some of the questions Guanzhou (InterDigtial) responds to some comments. Guanzhou (InterDigtial) corrects a typo in previous email . Stefano (Qualcomm) replies to Ericsson Stefano (Qualcomm) provides R07 Runze (Huawei) replies to Stefano (Faccin) ==== Revisions Deadline ==== Runze (Huawei) can live with R07 ==== Final Comments Deadline ==== | Revised |
| 19.10 | S2-2401813 | LS OUT | Approval | LS on No-Transmit Zones according to ECC decision 22(07) | SA WG2 | Rel-19 | Revision of S2-2400102r07. Approved | Approved | |
| 19.10 | - | - | - | Work plan, TR skeleton, Scope | - | - | Docs:=3 | - | |
| 19.10 | S2-2400321 | WORK PLAN | Information | FS_UAS_Ph3 Work plan | LG Electronics, Ericsson | Rel-19 | Noted | Noted | |
| 19.10 | S2-2400226 | P-CR | Approval | 23.700-59: 23.700-59:TR skeleton: Study on architecture enhancements of UAS, UAV and UAM; Phase 3. | Ericsson, LG Electronics | Rel-19 | Approved | Approved | |
| 19.10 | S2-2400169 | P-CR | Approval | 23.700-59: Scope for FS_UAS_Ph3. | LG Electronics, Ericsson | Rel-19 | Approved | Approved | |
| 19.10 | - | - | - | Architectural Assumptions and Requirements | - | - | Docs:=5 | - | |
| 19.10 | S2-2400313 | P-CR | Approval | 23.700-59: Architectural Assumptions for FS_UAS_Ph3. | LG Electronics, Ericsson | Rel-19 | r05 Agreed. Revised to S2-2401814. | Amanda ( Futurewei ) provides r01 Saubhagya (Nokia) has the same views as Ericsson Shabnam (Ericsson) asks how can this added assumption be fulfilled on r01? r01 it is wording is not acceptable. LaeYoung (LGE) also has the same view as Nokia and Ericsson, so cannot accept r01. Amanda ( Futurewei ) responses to the concerns and provides r02 Amanda ( Futurewei ) sends the previous email by mistake, Please ignore. Will send the correct one soon. Sorry Stefano (Faccin) recommend sticking to r00. LaeYoung (LGE) provides r03. Stefano (Qualcomm) would like to cosign r03. Guanzhou (InterDigtial) provides r04. LaeYoung is fine with r05. Runze (Huawei) provides r05, on top of r04. LaeYoung responds to Stefano (Qualcomm) and Guanzhou (InterDigtial). ==== Revisions Deadline ==== Runze supports r05 and objects to other revisions. ==== Final Comments Deadline ==== | Revised |
| 19.10 | S2-2401814 | P-CR | Approval | 23.700-59: Architectural Assumptions for FS_UAS_Ph3. | LG Electronics, Ericsson, Futurewei, Huawei, Qualcomm Incorporated | Rel-19 | Revision of S2-2400313r05. Approved | Approved | |
| 19.10 | S2-2401122 | P-CR | Approval | 23.700-59: 23.700-59: Architecture Assumption for FS_UAS_Ph3. | CATT | Rel-19 | Noted | Stefano (Qualcomm) suggest to note the paper Runze (Huawei) comments. Shabnam (Ericsson) indicates similar comments as Qualcomm, maybe better to focus on requirements doc in 0884 LaeYoung (LGE) also has similar view as Qualcomm, Huawei and Ericsson, and prefers to NOTE this paper. Yunjing(CATT) replies. Yunjing(CATT) replies to Stefano (Qualcomm). Stefano (Qualcomm) replies. Yunjing (CATT) is fine to NOTE this pCR. LaeYoung (LGE) proposes to NOTE this P-CR. Runze (Huawei) suggested Yunjing(CATT) to provide a revision ==== Revisions Deadline ==== | Noted |
| 19.10 | S2-2400884 | P-CR | Approval | 23.700-59: Architectural requirements. | CATT | Rel-19 | r03 + changes Agreed. Revised to S2-2401815. | Saubhagya (Nokia) OK with r01; provide comments. Stefano (Qualcomm) provides R01. Runze (Huawei) supports r01. Yuan Tao (CATT) is ok with R01. Shabnam (Ericsson) provides comments r01 could be ok but I think a very generic mention of exposure is too vague? Yuan Tao (CATT) replies to Shabnam (Ericsson). Stefano (Qualcomm) provides R02. Runze (Huawei) prefers R02 than R01. Yuan Tao (CATT) is fine with R02. LaeYoung (LGE) is fine with r02 and would like to co-sign. Stefano (Qualcomm) provides R03 cosigning. Yuan Tao (CATT) responds and is fine with R03. ==== Revisions Deadline ==== Amanda ( Futurewei ) supports r03 and like to co-sign Yuan Tao replies to Amanda ( Futurewei ). Runze (Huawei) supports r03 ==== Final Comments Deadline ==== | Revised |
| 19.10 | S2-2401815 | P-CR | Approval | 23.700-59: Architectural requirements. | CATT, LG Electronics, Qualcomm, Futurewei | Rel-19 | Revision of S2-2400884r03 + changes. Approved | Approved | |
| 19.10 | - | - | - | New Key Issue proposals for WT#1 | - | - | Docs:=6 | - | |
| 19.10 | S2-2400170 | P-CR | Approval | 23.700-59: New KI: KI for WT#1. | LG Electronics, Ericsson | Rel-19 | r05 + changes Agreed. Revised to S2-2401816, merging S2-2400883, S2-2401082, S2-2401083 and S2-2401239 | Saubhagya (Nokia) provides R03. Guanzhou (InterDigtial) provides r02. Stefano (Qualcomm) good basis, proposes R01. Amanda (Futurewei) provides R04. Shabnam (Ericsson) provides comments that has issues with a number of changes and would like to ask companies provide clarification so a proper revision can be made, see below: Amanda ( Futurewei ) agrees with Shabnam (Ericsson) that NOTE3 can be moved to Architecture assumption LaeYoung (LGE) provides r05. Stefano (Qualcomm) asks to cosign r03. Guanzhou (InterDigtial) asks to clarify the concern on 'change of USS' and can't accept r05. Runze (Huawei) supports r05. LaeYoung responds to Stefano (Qualcomm) and Guanzhou (InterDigtial). ==== Revisions Deadline ==== Guanzhou (InterDigtial) OK with r03/04 and objects to r05. Can live with r05 with proposed editorial change: 'supporting the scenario of multiple USS serving the different geographical areas corresponding to the UAV flight path' LaeYoung (LGE) is fine with the editorial change proposed by Guanzhou (InterDigtial). That is, on top of r05, change 'the geographical areas' to 'different geographical areas' in the very last sub-bullet. ==== Final Comments Deadline ==== | Revised |
| 19.10 | S2-2401816 | P-CR | Approval | 23.700-59: New KI: KI for WT#1. | LG Electronics, Ericsson, Futurewei, Qualcomm Incorporated | Rel-19 | Revision of S2-2400170r05 + changes, merging S2-2400883, S2-2401082, S2-2401083 and S2-2401239. Approved | Approved | |
| 19.10 | S2-2400883 | P-CR | Approval | 23.700-59: New Key Issue: Enhancement to interaction between MNO and UTM based on WT#1. | CATT | Rel-19 | Merged into S2-2401816 | Saubhagya (Nokia) provide comments. Stefano (Qualcomm) proposes to consider this merged into S2-2400170, has comments. LaeYoung (LGE) proposes to Merge this P-CR into S2-2400170 (LGE, Ericsson). Yuan Tao (CATT) replies to Stefano (Qualcomm). Yuan Tao (CATT) is fine to merge this P-CR into S2-2400170 per rapporteur's suggestion . Yuan Tao (CATT) replies to Saubhagya (Nokia). Runze (Huawei) shared the view as Shabnam (Ericsson) Shabnam (Ericsson) provides comments and does not agree with the proposed KI description, see below please ==== Revisions Deadline ==== LaeYoung (LGE) also confirms that this P-CR can be Merged into S2-2400170. Yuan Tao replies to Stefano (Qualcomm) and confirm this paper is merge into S2-2400170 per rapporteur's suggestion .. Stefano (Qualcomm) believes we got good progress in 0170, and we should consider this one noted. ==== Final Comments Deadline ==== | Merged |
| 19.10 | S2-2401082 | P-CR | Approval | 23.700-59: New KI on possible mechanisms for flight planning and monitoring. | China Mobile | Rel-19 | Merged into S2-2401816 | Saubhagya (Nokia) shares concerns/comments. Stefano (Qualcomm) expresses concerns and suggest noting this paper. LaeYoung (LGE) proposes to Merge this P-CR into S2-2400170 (LGE, Ericsson). Runze (Huawei) suggests to merge this paper into S2-2400170. Shabnam (Ericsson) supports the proposed merger, I believe the context is quite aligned. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 19.10 | S2-2401083 | P-CR | Approval | 23.700-59: New KI on improving C2 communication reliability. | China Mobile | Rel-19 | Merged into S2-2401816 | Stefano (Qualcomm) suggests rewording. LaeYoung (LGE) proposes to Merge this P-CR into S2-2400170 (LGE, Ericsson). Runze (Huawei) proposes a clarification. Runze (Huawei) proposed a comment. LaeYoung (LGE) suggests discussing new Key Issue for WT#1 under S2-2400170. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 19.10 | S2-2401239 | P-CR | Approval | 23.700-59: New KI: Enhanced NEF services for flight planning and control. | InterDigital, Inc. | Rel-19 | Merged into S2-2401816 | LaeYoung (LGE) proposes to Merge this P-CR into S2-2400170 (LGE, Ericsson). ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 19.10 | - | - | - | New Key Issue proposals for WT#2 | - | - | Docs:=4 | - | |
| 19.10 | S2-2400227 | P-CR | Approval | 23.700-59: New KI: KI for WT#2. | Ericsson, LG Electronics | Rel-19 | r06 + changes Agreed. Revised to S2-2401817, merging S2-2400103 and S2-2401245 | Saubhagya (Nokia) provides R02. Stefano (Qualcomm) provides R01 Shabnam (Ericsson) provides r03 Runze (Huawei) comments on Shabnam r03. LaeYoung (LGE) provides r04. Guanzhou (InterDigtial) provides r05 and co-signs. Runze (Huawei) comments on r05 and provides r06. Shabnam (Ericsson) fine with updates in r06 Saubhagya (Nokia) OK with r06. Ashok (Samsung) comments on the scope of this KI LaeYoung (LGE) answers to Ashok (Samsung). Stefano (Qualcomm) provides R07. Runze (Huawei) comments on R07. Stefano (Qualcomm) responds. ==== Revisions Deadline ==== LaeYoung (LGE) is fine with r07 and confirms that the Editor's Note does not intend studying/developing specific solutions for EPS. Runze (Huawei) replied to Stefano (Qualcomm) and LaeYoung (LGE) , cannot accept r07, but can accept r07 with removal of the Editor's note. LaeYoung (LGE) proposes to go with r06 in this meeting and have some time to think about EPS part further. Ashok (Samsung) finds LaeYoung (LGE) proposal is good and ok with r06. Runze (Huawei) accepts r06 and objects to other revisions. Shabnam (Ericsson) proposes to go with r06 and address the EPS aspects, if any, via solution space. Guanzhou (InterDigtial) fine with r06 and confirms co-signing. ==== Final Comments Deadline ==== | Revised |
| 19.10 | S2-2401817 | P-CR | Approval | 23.700-59: New KI: KI for WT#2. | Ericsson, LG Electronics, InterDigital | Rel-19 | Revision of S2-2400227r06 + changes, merging S2-2400103 and S2-2401245. Approved | Approved | |
| 19.10 | S2-2400103 | P-CR | Approval | 23.700-59: Key Issue for Network-based/Assisted Tactical Situational Awareness (DAA). | Qualcomm Incorporated | Rel-19 | Merged into S2-2401817 | LaeYoung (LGE) proposes to Merge this P-CR into S2-2400227 (Ericsson, LGE). ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 19.10 | S2-2401245 | P-CR | Approval | 23.700-59: New KI: Ground-based DAA. | InterDigital, Inc. | Rel-19 | Merged into S2-2401817 | Stefano (Qualcomm) suggests merging in S2-2400227. Guanzhou (InterDigital) is fine with the merge proposal. LaeYoung (LGE) proposes to Merge this P-CR into S2-2400227 (Ericsson, LGE). ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 19.10 | - | - | - | New Key Issue proposals for WT#3 | - | - | Docs:=6 | - | |
| 19.10 | S2-2400101 | P-CR | Approval | 23.700-59: New KI on No-Transmit Zones. | Qualcomm Incorporated | Rel-19 | r09 Agreed. Revised to S2-2401818, merging S2-2401084, S2-2401124 and S2-2401166 | Saubhagya (Nokia) provide comments on R01. Stefano (Qualcomm) provides R01. Dimitris (Lenovo) comments Shabnam (Ericsson) provides comments and r03 (which is based on r01) Guanzhou (InterDigtial) thinks some text belongs to Arch Assumptions and provides r02. Runze (Huawei) provides r04 based on r03. Tsuyoshi(NTT DOCOMO) asks clarification. Stefano (Qualcomm) replies to comments/questions and provides R05. LaeYoung (LGE) provides r06. Ashok (Samsung) comments. Stefano (Qualcomm) replies to Samsung. Stefano (Qualcomm) comments. Stefano (Qualcomm) provides R07. Ashok (Samsung) is satisfied with the answer from Stefano (Qualcomm), ok with r07 and ask to co-sign Guanzhou (InterDigtial) asks to co-sign r07. Shabnam (Ericsson) provides comments and r08 Ashok (Samsung) comments that r08 is not available Stefano (Qualcomm) provide comments Runze (Huawei ) comments on r08 LaeYoung (LGE) provides r09. Runze (Huawei) supports r09. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 19.10 | S2-2401818 | P-CR | Approval | 23.700-59: New KI on No-Transmit Zones. | Qualcomm Incorporated, Ericsson, LG Electronics | Rel-19 | Revision of S2-2400101r09, merging S2-2401084, S2-2401124 and S2-2401166. Approved | Approved | |
| 19.10 | S2-2400228 | P-CR | Approval | 23.700-59: New KI: KI for WT#3. | Ericsson, LG Electronics | Rel-19 | r03 Agreed. Revised to S2-2401819. | Stefano (Qualcomm) proposes to consider S2-240101 as basis and merge this one in. LaeYoung (LGE) proposes to use this P-CR only for clause 3.1. Shabnam (Ericsson) provides comments to provide r01 aligned with suggestion Guanzhou (InterDigtial) thinks the definition could be more concise and provides r02. Runze (Huawei) comments on the NTZ definition. LaeYoung (LGE) provides r03 including editorial changes. LaeYoung (LGE) responds to Runze (Huawei). Runze (Huawei) replies to LaeYoung (LGE) and supports r03. ==== Revisions Deadline ==== Runze (Huawei) supports r03. ==== Final Comments Deadline ==== | Revised |
| 19.10 | S2-2401819 | P-CR | Approval | 23.700-59: New KI: KI for WT#3. | Ericsson, LG Electronics | Rel-19 | Revision of S2-2400228r03. Approved | Approved | |
| 19.10 | S2-2401084 | P-CR | Approval | 23.700-59: New KI on possible mechanism for no-transmit zones for UAVs. | China Mobile | Rel-19 | Merged into S2-2401818 | Stefano (Qualcomm) suggests merging into S2-2400101, expresses concerns LaeYoung (LGE) proposes to Merge this P-CR into S2-2400101 (Qualcomm). ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 19.10 | S2-2401166 | P-CR | Approval | 23.700-59: New key issue: support of no-transmit zone. | Huawei, HiSilicon | Rel-19 | Merged into S2-2401818 | Stefano (Qualcomm) suggests merging in S2-2400101R01. LaeYoung (LGE) proposes to Merge this P-CR into S2-2400101 (Qualcomm) for new Key Issue and into S2-2400228 (Ericsson, LGE) for clause 3. Runze (Huawei) is fine with the suggestion of merging in S2-2400101R01. Runze (Huawei ) agrees to Merge this P-CR into S2-2400101 (Qualcomm) for new Key Issue and into S2-2400228 (Ericsson, LGE) for clause 3. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 19.10 | - | - | - | Documents exceeding TU budget/quota | - | - | Docs:=2 | - | |
| 19.10 | S2-2401123 | P-CR | Approval | 23.700-59: 23.700-59: New KI for FS_UAS_Ph3 WT#2. | CATT | Rel-19 | Not Handled | Stefano (Qualcomm) suggests merging in 0227. Yunjing(CATT) replies. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Not Handled |
| 19.10 | S2-2401124 | P-CR | Approval | 23.700-59: 23.700-59: New KI for FS_UAS_Ph3 WT#3. | CATT | Rel-19 | Merged into S2-2401818 | Stefano (Qualcomm) suggests merging in S2-2400101R01. Yunjing (CATT) agrees to merge this pCR into S2-2400101. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 19.11 | - | - | - | Study on UPF enhancement for Exposure And SBA Phase 2 (FS_UPEAS_Ph2) | - | - | Docs:=26 | - | |
| 19.11 | S2-2401109 | P-CR | Approval | 23.700-63: Skeleton for TR 23.700-63. | ZTE | Rel-19 | Approved | ==== Final Comments Deadline ==== | Approved |
| 19.11 | S2-2401110 | P-CR | Approval | 23.700-63: Scope of TR23.700-63. | ZTE | Rel-19 | Approved | ==== Final Comments Deadline ==== | Approved |
| 19.11 | S2-2400230 | P-CR | Approval | 23.700-63: Architectural assumptions and requirements . | ETRI | Rel-19 | Merged into S2-2401615 | Jinguo(ZTE) suggests to merge this paper into 1111 ==== Revisions Deadline ==== Magnus H (Ericsson) assumes this tdoc is merged into 1111, and thus object to this tdoc. ==== Final Comments Deadline ==== | Merged |
| 19.11 | S2-2401111 | P-CR | Approval | 23.700-63: Architecture assumption and requirement. | ZTE | Rel-19 | r04 Agreed. Revised to S2-2401615, merging S2-2400230 | Changki(ETRI) have a simple question to Jinguo for clarification. Jinguo(ZTE) provides r01 Jinguo(ZTE) replies to Changki(ETRI) Changki(ETRI) provides r02 with comments. Georgios (Nokia) comments on r02 Changki(ETRI) reply to Georgios. Fenqin(Huawei) provides r03. Georgios (Nokia) provides r04 and cosigns Naman (Samsung) comments on r04 Jinguo(ZTE) replies to Naman (Samsung) Naman (Samsung) provides r05 Georgios (Nokia) agrees to either of r04, r05 Dan (China Mobile) provide r06 Georgios (Nokia) objects to r06 Fenqin (Huawei) responds and provides r07 ==== Revisions Deadline ==== Naman (Samsung) is fine with r07 as well Changki(ETRI) is OK with r04, r05, r07. Georgios (Nokia) is OK with r04, r05 objects to r06, r07 Dan (China Mobile) object to r04 and r05. OK with r07. Concern about the user plane architecture. Jinguo(ZTE) suggests to go with r07 Georgios (Nokia) provides comments Dan (China Mobile) provides comments Dan (China Mobile) is OK with r04, r05 Fenqin (Huawei) is OK with r04, r05 and prefer r04. Magnus H (Ericsson) proposes to go with r04 or r05, objects to all other revisions ==== Final Comments Deadline ==== | Revised |
| 19.11 | S2-2401615 | P-CR | Approval | 23.700-63: Architecture assumption and requirement. | ZTE, ETRI, Nokia, Nokia Shanghai Bell | Rel-19 | Revision of S2-2401111r04, merging S2-2400230. Approved | Approved | |
| 19.11 | S2-2401199 | P-CR | Approval | 23.700-63: KI description for WT#1. | Nokia, Nokia Shanghai Bell, Ericsson, Huawei, HiSilicon | Rel-19 | Approved | ==== Final Comments Deadline ==== | Approved |
| 19.11 | S2-2400089 | P-CR | Approval | 23.700-63: Key issue on direct subscription of UPF event exposure service. | China Mobile | Rel-19 | r14 Agreed. Revised to S2-2401616. | Dan(China Mobile) provides r02 based on r01 Changki(ETRI) provides comments and provides r01. Jinguo(ZTE) points that r01 link is missing Changki(ETRI) provides r01 link. Fenqin(Huawei) provides r03. Georgios (Nokia) provides r04 Changki(ETRI) provides r05 with comments. Jinguo(ZTE) provides r06 to cover the indirect subscription Marisa (Ericsson) provides r07 and comments Dan (China Mobile) provides r09, please ignore r08, which I make a mistake Fenqin(Huawei) provides r11. Changki(ETRI) provides corrected link for r10. Changki(ETRI) provides r10 with comments. Dan(China Mobile) provides r12. Georgios (Nokia) provides r13 Changki(ETRI) provide comments Marisa (Ericsson) provides r14 and comments Dan (China Mobile) ok to keep the NOTE ==== Revisions Deadline ==== Dan (China Mobile) is ok with r14 Changki(ETRI) is fine with r14. Georgios (Nokia) is OK with r14 objects to r12 Fenqin (Huawei) accept only r14, r13, r11. Marisa (Ericsson) can only accept r14 ==== Final Comments Deadline ==== | Revised |
| 19.11 | S2-2401616 | P-CR | Approval | 23.700-63: Key issue on enhancements to UPF event exposure service. | China Mobile, ETRI, ZTE | Rel-19 | Revision of S2-2400089r14. Approved | Approved | |
| 19.11 | S2-2401322 | P-CR | Approval | 23.700-63: Key issue for WT2: Enhancements to UPF event exposure service. | Samsung | Rel-19 | Noted | Jinguo(ZTE) suggests that direct subscription can be merged in 0089. This key issue can focus on indirect subscription, provide r01 Georgios (Nokia) provides comments Changki(ETRI) provides comments. Jinguo(ZTE) is ok with either way and let the author decide whether to merge into 0089. Fenqin (ZTE) propose to note this paper as the indirect subscription is merged to 0089 Georgios (Nokia) also supports to Merge / NOTE this paper and only keep 0089 Marisa (Ericsson) proposes this paper is noted ==== Revisions Deadline ==== Marisa (Ericsson) objects any revision of this paper ==== Final Comments Deadline ==== | Noted |
| 19.11 | S2-2400390 | P-CR | Approval | 23.700-63: 23.700-63, Key Issue for SID WT#3. | Vodafone, ZTE | Rel-19 | r08 Agreed. Revised to S2-2401617. | Seunghan(ETRI) provides r01 with comments Marisa Mas (Ericsson) provides comments and r02 Susana (Vodafone) provides r03 and comments on Marisa changes Fenqin (Huawei) provides r04 Susana (Vodafone) replies to Fenqin. Georgios (Nokia) provides r05 Susana (Vodafone) comments and provides Rev 06. Naman (Samsung) seeks clarification from Marisa (Ericsson) Marisa (Ericsson) provides response. Jinguo(ZTE) agree with Marisa(Ericsson) Naman (Samsung) comments and provides r07 Georgios (Nokia) agrees with r07 Marisa (Ericsson) provides r08 and comments Dan (China Mobile) provides r09 and comments ==== Revisions Deadline ==== Dan (China Mobile) suggest to go with r09. Seunghan (ETRI) is OK with r08. Susana (Vodafone) prefers r07 Georgios (Nokia) is OK with either r07, r08, objects to r09 Susana (Vodafone) can live with r07or r08 and can live with R09 if a minor clarification can be included during the CC. Comments added on this. Fenqin (Huawei) is ok with r07, r08,r09. Marisa (Ericsson) is ok with r08 and r09 and objects the rest Susana (Vodafone) accepts to go for r09 and may provide the clarification in coming meeting. ==== Final Comments Deadline ==== | Revised |
| 19.11 | S2-2401617 | P-CR | Approval | 23.700-63: 23.700-63, Key Issue for SID WT#3. | Vodafone, ZTE, ETRI | Rel-19 | Revision of S2-2400390r08. Approved | Approved | |
| 19.11 | S2-2400527 | DISCUSSION | Discussion | Modification on WT#2 for UPEAS_Ph2 | Samsung Research America | Rel-19 | Noted | Noted | |
| 19.11 | - | - | - | Documents exceeding TU budget | - | - | Docs:=14 | - | |
| 19.11 | S2-2401330 | P-CR | Approval | 23.700-63: Scope for UPEAS_Ph2. | Samsung | Rel-19 | Not Handled | Georgios (Nokia) my assumption is that this is merged to 2401110 hence objecting to this one ==== Final Comments Deadline ==== | Not Handled |
| 19.11 | S2-2400091 | P-CR | Approval | 23.700-63: TR 23.700-63 FS_UPEAS_Ph2 Architectural assumptions and requirements. | China Mobile | Rel-19 | Not Handled | Georgios (Nokia) my assumption is that this is merged to 2401111 hence objecting to this one ==== Final Comments Deadline ==== | Not Handled |
| 19.11 | S2-2401197 | P-CR | Approval | 23.700-63: Architectural Assumptions for UPEAS Ph2. | Nokia, Nokia Shanghai Bell, Ericsson, Huawei, HiSilicon | Rel-19 | Not Handled | ==== Final Comments Deadline ==== | Not Handled |
| 19.11 | S2-2401198 | P-CR | Approval | 23.700-63: Architectural Requirements for UPEAS Ph2. | Nokia, Nokia Shanghai Bell, Ericsson, Huawei, HiSilicon | Rel-19 | Not Handled | ==== Final Comments Deadline ==== | Not Handled |
| 19.11 | S2-2401328 | P-CR | Approval | 23.700-63: Architectural Assumptions for UPEAS_Ph2. | Samsung | Rel-19 | Not Handled | ==== Final Comments Deadline ==== | Not Handled |
| 19.11 | S2-2400092 | P-CR | Approval | 23.700-63: Key issue on potential enhancement on UPF selection. | China Mobile | Rel-19 | Not Handled | ==== Final Comments Deadline ==== | Not Handled |
| 19.11 | S2-2401112 | P-CR | Approval | 23.700-63: Key issue for UPF Selection Enhancements. | ZTE | Rel-19 | Not Handled | ==== Final Comments Deadline ==== | Not Handled |
| 19.11 | S2-2401321 | P-CR | Approval | 23.700-63: Key issue for WT1: Enhancements for UPF selection . | Samsung | Rel-19 | Not Handled | ==== Final Comments Deadline ==== | Not Handled |
| 19.11 | S2-2400229 | P-CR | Approval | 23.700-63: Key Issue on WT#2: Direct subscription to UPF event exposure service and expose information extension . | ETRI | Rel-19 | Not Handled | ==== Final Comments Deadline ==== | Not Handled |
| 19.11 | S2-2401113 | P-CR | Approval | 23.700-63: Key issue for enhancement on UPF event exposure. | ZTE | Rel-19 | Not Handled | ==== Final Comments Deadline ==== | Not Handled |
| 19.11 | S2-2401200 | P-CR | Approval | 23.700-63: KI description for WT#2. | Nokia, Nokia Shanghai Bell, Ericsson, Huawei, HiSilicon | Rel-19 | Not Handled | ==== Final Comments Deadline ==== | Not Handled |
| 19.11 | S2-2400090 | P-CR | Approval | 23.700-63: Key issue on interface enhancement between AF and UPF for UPF event exposure. | China Mobile | Rel-19 | Not Handled | ==== Final Comments Deadline ==== | Not Handled |
| 19.11 | S2-2400158 | P-CR | Approval | 23.700-63: Key Issue on for WT#3 Enhanced Interface between AF and UPF. | ETRI | Rel-19 | Not Handled | ==== Final Comments Deadline ==== | Not Handled |
| 19.11 | S2-2401201 | P-CR | Approval | 23.700-63: KI description for WT#3. | Nokia, Nokia Shanghai Bell, Ericsson, Huawei, HiSilicon | Rel-19 | Not Handled | ==== Final Comments Deadline ==== | Not Handled |
| 19.12 | - | - | - | Study on System aspects of 5G NR Femto (FS_5G_Femto) | - | - | Docs:=28 | - | |
| 19.12 | - | - | - | TR Skeleton | - | - | Docs:=2 | - | |
| 19.12 | S2-2400871 | P-CR | Approval | 23.700-45: 23.700-45: TR skeleton: Study on System aspects of 5G NR Femto | NTT DOCOMO | Rel-19 | Add missing cover page (see S2-2400128 for example). Revised to S2-2401377. | Revised | |
| 19.12 | S2-2401377 | P-CR | Approval | 23.700-45: Cover page for TR 23.700-45 skeleton. | NTT DOCOMO | Rel-19 | Revision of S2-2400871. Approved | Approved | |
| 19.12 | - | - | - | Scope, Assumption, requirements | - | - | Docs:=6 | - | |
| 19.12 | S2-2400872 | P-CR | Approval | 23.700-45: 23.700-45: Scope, Architecture Assumption and Requirement . | NTT DOCOMO | Rel-19 | r02 Agreed. Revised to S2-2401716. | Malla (NTT DOCOMO) provides r01. Qian (Ericsson) provides comments and r02. Tezcan (Nokia) provides comments Malla (NTT DOCOMO) provides comments Tezcan (Nokia) responds to Malla Malla (NTT DOCOMO) responds to Tezcan (Nokia) ==== Revisions Deadline ==== Qian (Ericsson) provides comments and proposes to go with r02 ==== Final Comments Deadline ==== Tezcan (Nokia) comments and checks a way forward Malla (NTT DOCOMO) for CC#4, R04 + add a NOTE 'Based on RAN3 outcome, enhance the overall architecture and enable the required functional and procedural changes for supporting 5G NR Femto deployment.' Malla (NTT DOCOMO) for CC#4, r02 + add a NOTE 'Based on RAN3 outcome, enhance the overall architecture and enable the required functional and procedural changes for supporting 5G NR Femto deployment.' | Revised |
| 19.12 | S2-2401716 | P-CR | Approval | 23.700-45: 23.700-45: Scope, Architecture Assumption and Requirement . | NTT DOCOMO | Rel-19 | Revision of S2-2400872r02. Approved | Approved | |
| 19.12 | S2-2400942 | P-CR | Approval | 23.700-45: Adding Working assumption to FS_5G_Femto. | ZTE | Rel-19 | Merged into S2-2401717 | Malla (NTT DOCOMO) propose merge into S2-2401231. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 19.12 | S2-2401012 | P-CR | Approval | 23.700-45: Architectural Assumptions and Requirements for 5G Femto. | Huawei, HiSilicon | Rel-19 | Merged into S2-2401717 | Malla (NTT DOCOMO) merge into S2-2401231. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 19.12 | S2-2401231 | P-CR | Approval | 23.700-45: TR 23.700-45 Architectural Assumptions and Principles. | Nokia, Nokia Shanghai Bell | Rel-19 | r02 Agreed. Revised to S2-2401717, merging S2-2400942 and S2-2401012 | Qian (Ericsson) provides comments and r01 Tezcan (Nokia) provides r02 which merges S2-2400217, S2-2400942 and S2-2401012. ==== Revisions Deadline ==== Qian (Ericsson) is ok with r02. ==== Final Comments Deadline ==== | Revised |
| 19.12 | S2-2401717 | P-CR | Approval | 23.700-45: TR 23.700-45 Architectural Assumptions and Principles. | Nokia, Nokia Shanghai Bell, NTT DOCOMO | Rel-19 | Revision of S2-2401231r02, merging S2-2400942 and S2-2401012. Approved | Approved | |
| 19.12 | - | - | - | WT#2 (KI#1) | - | - | Docs:=6 | - | |
| 19.12 | S2-2400218 | P-CR | Approval | 23.700-45: New KI #x Support of UE move between CAG cell and CSG cell. | Ericsson | Rel-19 | r04 + changes Agreed. Revised to S2-2401718, merging S2-2400300, S2-2400715, S2-2400943 and S2-2401229 | Chia-Lin (MediaTek) ask for clarification on the three bullets in the pCR Marco(Huawei) provide r01 Qian (Ericsson) provides responses to Chia-Lin (MediaTek) Qian (Ericsson) provides comment and r02 Malla (NTT DOCOMO) replies to Marco(Huawei) Kundan (NEC) seeks clarification. Qian (Ericsson) provides responses to Kundan (NEC). Kundan(NEC) responds to Qiang(Ericsson). Marco(Huawei) answers to Kundan (NEC) Marco(Huawei) aprovide r03 with editorial revision Tezcan (Nokia) provides r04 Chia-Lin (MediaTek) responds and provides r05 Tezcan (Nokia) replies and prefers r04 Marco(Huawei) agrees with Tezcan's comment (Nokia) ==== Revisions Deadline ==== Chia-Lin (MediaTek) provides comments and cannot live with r04 unless r04 with NOTE: the mobility scenario only considers the mobility for UE in connected mode Malla (NTT DOCOMO) provided response to Chia-Lin (MediaTek). Qian (Ericsson) provides comments, supports to go with r05, but is ok with r04. Kundan(NEC) objects r05 but fine with r04. Idle mode is more important than connected mode. Without idle mode mobility UE will lose the service. Marco(Huawei) ok with R04 Malla (NTT DOCOMO) proposes to go with R04, and we can assess as part of the solution/conclusion whether there is an impact on idle mode mobility. We should not limit now at the KI level. ==== Final Comments Deadline ==== Qian (Ericsson) comments and checks the way forward. Malla (NTT DOCOMO) supports Qian's (Ericsson) way forward proposal. | Revised |
| 19.12 | S2-2401718 | P-CR | Approval | 23.700-45: New KI #x Support of UE move between CAG cell and CSG cell. | Ericsson, NTT DOCOMO | Rel-19 | Revision of S2-2400218r04 + changes, merging S2-2400300, S2-2400715, S2-2400943 and S2-2401229. Approved | Approved | |
| 19.12 | S2-2400300 | P-CR | Approval | 23.700-45: 23.700-45: New KI: 5GS support interworking between CAG and CSG cells. . | OPPO | Rel-19 | Merged into S2-2401718 | Malla (NTT DOCOMO) Merge into S2-2400218. Jingran (OPPO) agree merge into S2-2400218. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 19.12 | S2-2400715 | P-CR | Approval | 23.700-45: New KI: Interworking between CAG cells and CSG cells. | NEC | Rel-19 | Merged into S2-2401718 | Malla (NTT DOCOMO) Merge into S2-2400218. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 19.12 | S2-2400943 | P-CR | Approval | 23.700-45: New key issue on the interworking between CAG and CSG cells. | ZTE | Rel-19 | Merged into S2-2401718 | Malla (NTT DOCOMO) Merge into S2-2400218. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 19.12 | S2-2401229 | P-CR | Approval | 23.700-45: New KI: WT-2, Enabling interworking between CAG and CSG cells. | Nokia, Nokia Shanghai Bell | Rel-19 | Merged into S2-2401718 | Malla (NTT DOCOMO) Merge into S2-2400218. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 19.12 | - | - | - | WT#3 (KI#2) | - | - | Docs:=6 | - | |
| 19.12 | S2-2400219 | P-CR | Approval | 23.700-45: New KI #x Subscription data management for CAG information provisioning. | Ericsson | Rel-19 | Merged into S2-2401719 | Malla (NTT DOCOMO) Merge into S2-2401013. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 19.12 | S2-2400716 | P-CR | Approval | 23.700-45: New KI: Provisioning of CAG subscription. | NEC | Rel-19 | Merged into S2-2401719 | Malla (NTT DOCOMO) Merge into S2-2401013. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 19.12 | S2-2400770 | P-CR | Approval | 23.700-45: New KI:<Supporting CAG access management by authorized administrator>. | Samsung | Rel-19 | Merged into S2-2401719 | Malla (NTT DOCOMO) Merge into S2-2401013. Youngkyo(Samsung) is okay to merge into S2-2401013. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 19.12 | S2-2401013 | P-CR | Approval | 23.700-45: New Key Issues for 5G Femto. | Huawei, HiSilicon | Rel-19 | r10 + changes Agreed. Revised to S2-2401719, merging S2-2400219, S2-2400716, S2-2400770 and S2-2401230 | Malla (NTT DOCOMO) provides r01. Marco(Huawei) merged version of S2-2400219, s2-2400716, S2-2400770, s2-2400878 and S2-2401230 Marco(Huawei) provides r03 Hong (Qualcomm) comments on r03. Marco(Huawei) anwers to Hong (Qualcomm) and provide r04 Qian (Ericsson) provides comments and r05 Tezcan (Nokia) comments and provides r06 LaeYoung (LGE) provides r07. Marco(Huawei) provides r08 Tezcan (Nokia) provides comments to r08 Kundan (NEC) seeks clarification. Qian (Ericsson) provides comments on r08 and asks questions. Malla (NTT DOCOMO) replies Kundan (NEC). Qian (Ericsson) provides comments to the question from Kundan (NEC). Malla (NTT DOCOMO) provided comment. Marco(Huawei) answer to Kundan (NEC) Marco(Huawei) answers to comments Marco(Huawei) replies to Qian (Ericsson) LaeYoung (LGE) comments. Tezcan (Nokia) agrees with Marco Qian (Ericsson) provides comments and asks further questions Tezcan (Nokia) replies to Qian Qian (Ericsson) provides further responses Tezcan (Nokia) asks for clarification Qian (Ericsson) responds and provide r09 Chia-Lin (MediaTek) provides comments on 'Whether and how to provide the CAG information to the UE to enable the UE to access to a CAG cell of a 5G Femto where the CAG cell can be in the home or visited network' that this has been specified in 5GS, why we need this in SID? Malla (NTT DOCOMO) provided comments. Marco(Huawei) answers to Chia-Lin (mediaTek). The CAG has been provisioned for PNI-NPN which is for PLMN scenario. The 5G Femto also the customer owned and deployed scenario is part of the scope, therefore is something change in provision to the network also in provisong to the UE may be different. Tezcan (Nokia) responds and provides r04 Tezcan (Nokia) responds and provides r10 Hong (Qualcomm) comments. ==== Revisions Deadline ==== Chia-Lin (MediaTek) agrees with Hong and can only live with the revision without the bullet 'Whether and how to provide the CAG information to the UE to enable the UE to access to a CAG cell of a 5G Femto where the CAG cell can be in the home or visited network.' Qian (Ericsson) is ok with what Chia-Lin (MediaTek) proposed. Marco(Huawei) ok with R10 + removal of the bullet 'Whether and how to provide the CAG information to the UE to enable the UE to access to a CAG cell of a 5G Femto where the CAG cell can be in the home or visited network.' ==== Final Comments Deadline ==== | Revised |
| 19.12 | S2-2401719 | P-CR | Approval | 23.700-45: New Key Issues for 5G Femto. | Huawei, HiSilicon, NEC, NTT DOCOMO | Rel-19 | Revision of S2-2401013r10 + changes, merging S2-2400219, S2-2400716, S2-2400770 and S2-2401230. Approved | Approved | |
| 19.12 | S2-2401230 | P-CR | Approval | 23.700-45: New KI: WT-3, 5G NR Femto access control mechanism. | Nokia, Nokia Shanghai Bell | Rel-19 | Merged into S2-2401719 | Malla (NTT DOCOMO) provides r01. Marco(Huawei) proposes to merge into S2-2401013 Tezcan (Nokia) agrees to merge into S2-2401013 ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 19.12 | - | - | - | Other KI proposal | - | - | Docs:=2 | - | |
| 19.12 | S2-2400605 | P-CR | Approval | 23.700-45: New Key Issue: Existing gNB/5GC Architecture applicability to 5G NR Femto . | Rakuten Mobile Inc. | Rel-19 | Noted | Marco(Huawei) propose to Note this contribution Hong (Qualcomm) comments and suggests NOTE the pCR. Aoken (Rakuten Mobile) OK with Noted ==== Revisions Deadline ==== | Noted |
| 19.12 | S2-2400616 | P-CR | Approval | 23.700-45: New Key Issue: Satellite Backhaul applicability to 5G NR Femto . | Rakuten Mobile Inc. | Rel-19 | Noted | Marco(Huawei) provides comments Marco(Huawei) proposes to note this contribution based on previous email comments Aoken (Rakuten Mobile) OK with Noted ==== Revisions Deadline ==== | Noted |
| 19.12 | - | - | - | Documents exceeding TU budget | - | - | Docs:=6 | - | |
| 19.12 | S2-2400217 | P-CR | Approval | 23.700-45: Architecture assumptions. | Ericsson | Rel-19 | Not Handled | Not Handled | |
| 19.12 | S2-2400877 | P-CR | Approval | 23.700-45: New KI: Interworking between CAG and CSG cells. | NTT DOCOMO | Rel-19 | Not Handled | Not Handled | |
| 19.12 | S2-2400878 | P-CR | Approval | 23.700-45: New KI: Provisioning and managing CAG. | NTT DOCOMO | Rel-19 | Not Handled | Marco(Huawei) proposes Merge into S2-2401013. ==== Revisions Deadline ==== | Not Handled |
| 19.12 | S2-2400676 | P-CR | Approval | 23.700-45: KI#1: New solution for how to enable interworking between CAG and CSG cells. | NTT DOCOMO | Rel-19 | Not Handled | Not Handled | |
| 19.12 | S2-2400677 | P-CR | Approval | 23.700-45: KI#1: New solution for UE configuration with regards to the CAG-CSG mapping. | NTT DOCOMO | Rel-19 | Not Handled | Not Handled | |
| 19.12 | S2-2400678 | P-CR | Approval | 23.700-45: KI#2: New solution for provisioning of the CAG cell configuration. | NTT DOCOMO | Rel-19 | Not Handled | Not Handled | |
| 19.13 | - | - | - | Study on Multi-Access (DualSteer and ATSSS_Ph4) (FS_MASSS) | - | - | Docs:=79 | - | |
| 19.13 | - | - | - | Skeleton, Scope (outside of quota) | - | - | Docs:=3 | - | |
| 19.13 | S2-2401316 | P-CR | Approval | 23.700-54: FS_MASSS TR 23.700-54 Skeleton . | Apple (Primary Rapporteur), China Telecom (Secondary Rapporteur) | Rel-19 | Approved | ==== Final Comments Deadline ==== | Approved |
| 19.13 | S2-2401318 | P-CR | Approval | 23.700-54: FS_MASSS Scope . | Apple | Rel-19 | r01 Agreed. Revised to S2-2401618. | Chia-Lin (MediaTek) provides r01 Paul R (Charter) supports r01, as stated on 1288 thread the WID objectives does not state '.. does not require integrated non-3GPP access' ==== Revisions Deadline ==== Krisztian (Apple) supports r01. Chia-Lin (MediaTek) are ok r01 ==== Final Comments Deadline ==== | Revised |
| 19.13 | S2-2401618 | P-CR | Approval | 23.700-54: FS_MASSS Scope . | Apple | Rel-19 | Revision of S2-2401318r01. Approved | Approved | |
| 19.13 | - | - | - | Terms | - | - | Docs:=1 | - | |
| 19.13 | S2-2401319 | P-CR | Approval | 23.700-54: FS_MASSS Architectural Terms . | Apple, ETRI | Rel-19 | CC#4: Postponed | Zhuoyi (China Telecom) provides r01. Guanzhou (InterDigtial) questions r01 definition. Dieter (Deutsche Telekom) comments Dieter (Deutsche Telekom): If DualSteer device is based on MUSIM UE it implies support of one or more MUSIM features as per definition of 23.501. Yishan (Huawei) provides r02 and try to make the terms clear Yildirim (Charter Communications) comments on rev02, specifically on DualSteer device term definition, and shares understanding of DualSteer Device in relation to Multi-USIM UE. Zhenhua (vivo) disagree to link DualSteer Device with MUSIM UE and propose to use the data transfer capability to define the term. Provides r03 Guanzhou (InterDigtial) shares some further thoughts on DualSteer device definition. Myungjune (LGE) comments/questions on DualSteer device definition. Krisztian (Apple) does not think r01 and r02 are correct. Chunshan (CATT) provides r04 to make the definition more clear. Pallab (Nokia) comments on r04 Zhenhua (vivo) comments on r04 Stefan (Ericsson) comments Zhuoyi (China telecom) comments. Jinguo(ZTE) comments. Yishan (Huawei) provides r05 and proposes to differentiate the cases of DualSteer Device with single UE and DualSteer device with two separate UE and also proposes to make DualSteer traffic steering and switching independent with ATSSS Miguel (Qualcomm) comments that definition of 'two UEs' is not clear what it means in UE side, needs to be more specific. Provides r06. Patrice (Huawei) clarifies what wasn't the SA1 intention. Miguel (Qualcomm) replies to Patrice. Yildirim (Charter Communications) support r06. Sang-Jun (Samsung) provides comments on 1319r06 on the text 'Each UE stack registers with the corresponding 3GPP access network as a separate UE.' ==== Revisions Deadline ==== Jeounglak (ETRI) prefers r16. Yildirim (Charter Communications) is OK with revisions r16, r09, r07; can live with r12, r11. Objects to any other revisions. Proposes a compromise for the 'registered' text in r16. Omkar (CableLabs) supports r16 (with the compromise text suggested by Charter), r09, r07; can live with r12, r11. Objects to all the other revisions. ==== Final Comments Deadline ==== | Postponed |
| 19.13 | - | - | - | Architectural Assumptions and Requirements for DualSteer | - | - | Docs:=1 | - | |
| 19.13 | S2-2401320 | P-CR | Approval | 23.700-54: FS_MASSS Architectural Assumptions and Requirements for DualSteer. | Apple, ETRI | Rel-19 | CC#4: Postponed | Myungjune (LGE) provides r01. Zhuoyi (China Telecom) wants the clarification of DualSteer device of a single UE. Zhenhua (vivo) comments. Yishan (Huawei) comments. Zhenhua (vivo) replies to Yishan (Huawei). Pallab (Nokia) provides comments on DualSteer device with single UE and 2 UE Zhuoyi (China Telecom) provides r02 Yishan (Huawei) comments and provides r03 Yaxin (OPPO) provides comments. Myungjune (LGE) provides r04 Dieter (Deutsche Telekom): comments Guanzhou (InterDigtial) comments and provides r05. Dieter (Deutsche Telekom): insists on keeping 'a subscriber with two subscriptions/SUPIs, sharing one subscription profile from the same operator.', better even to capture it as an architectural requirement. Amanda ( Futurewei ) provides r06 Omkar (CableLabs) provides r10. Yildirim (Charter Communications) replies on 'sharing one subscription profile' Guanzhou (InterDigtial) has concerns on some 'architecture requirements'. CATT (Liping) also suggests to keep 'sharing one subscription profile' in the Architectural Assumptions and Requirements for DualSteer. Youngkyo(Samsung) shares the view from Myungjune (LGE) and request for clarification. Krisztian (Apple) provides r09. Please ignore r08. Myungjune (LGE) comments that 'sharing one subscription profile' should be kept. Yildirim (Charter Communications) comments and provides r07. Stefan (Ericsson) comments Jinguo(ZTE) comments on r10 Yishan (Huawei) provides r11 to address previous comments and add some missing assumptions from SID description Chia-Lin (MediaTek) provides r12 and the changes highlighted in red in revision mode Miguel (Qualcomm) provides r13 Patrice (Huawei) answers Miguel (Qualcomm)'s comments. Miguel (Qualcomm) provides r14 adding back no UICC app impacts as requirement. Krisztian (Apple) provides r16. Omkar (CableLabs) comments and provides r15. Yishan (Huawei) is not ok with r16 since it is not aligned with SID scope. Pallab (Nokia) proposes to continue using the term 'DualSteer Device' for now. Omkar (CableLabs) responds to Yishan (Huawei). Chia-Lin (MediaTek) provides r17 Myungjune (LGE) provides r18 Yaxin (OPPO) provides r19 to clarify about NTN scenario. Stefan (Ericsson) provides r20 Liping(CATT) ask Stefan (Ericsson) for clarification and provide r21. Miguel (Qualcomm) provides r22 over r21 Yishan (Huawei) provides r23 over r17 with adding some bullets from other versions. Miguel (Qualcomm) not ok with r23. Stefan (Ericsson) provides r24 Miguel (Qualcomm) provides r25 Patrice (Huawei) is puzzled that Miguel(Qualcomm) disagrees with an explicit approved SA1 requirement. ==== Revisions Deadline ==== Jeounglak (ETRI) perfers r25. Pallab (Nokia) OK to approve r24,r25 + Sang-Jun (Samsung) proposed changes Myungjune (LGE) prefer r22, can live with r25 + Sang-Jun (Samsung) proposed changes Miguel (Qualcomm) ok with r25 and Sang-Jun (Samsung) proposed changes Sang-Jun (Samsung) is also OK wih r25 with deleting 'device' and changing 'access' into 'access networks' in the 4th bullet of 4.1.1. Krisztian (Apple) is OK with either r24 or r25. There's a leftover word 'device' in the 4th bullet of 4.1.1 that should be deleted. Zhenhua (vivo) prefers r25 + Sang-Jun (Samsung) proposed changes. Chia-Lin (MediaTek) is ok with r25,r24,r23 and suggest to go with r25 Liping (CATT) prefers r23 and can live with r25. Yishan (Huawei) prefer r23, can live with r24 + changes proposed by Sang-Jun (Samsung), objects to other versions. Zhuoyi (China telecom) prefers r25 + changes proposed by Sang-Jun (Samsung), also wants to cosign this paper. Stefan (Ericsson) prefers r25, OK with r24. Also ok with Sang-Jun's proposed changes. Yaxin (OPPO) prefers r25 + Sang-Jun (Samsung) proposed changes. Krisztian (Apple) asks Yishan (Huawei) to re-consider objection to r25. Let's try to keep the DualSteer device definition discussion within S2-2401319. I hope we can progress this paper independently. Just to reiterate, the proposal is to agree r25 with deleting 'device' and changing 'access' into 'access networks' in the 4th bullet of 4.1.1. Patrice (Huawei) disagrees that we question the content of the SID at this stage. Maintains to approve r23 (or r24 + the two changes mentioned before) and keep the questioning of the SID to further contributions from the opponents of the SA1 requirements in the next meeting. Yildirim (Charter Communications) support revision r25 with addition of non-3GPP related bullet. Objects to any other revisions. Omkar (CableLabs) supports r25 but only with the addition of non-3GPP related bullet. Objects to any other revisions. Miguel ( Qualcomm) clarifies my issue with r24 is not with the simultaneous transmission but the term '2 UEs' which is Stage 1 and not clear what it means for Stage 2. Miguel (Qualcomm) asks Omkar and Yildirim can we keep the non-3GPP related bullet be included as a NOTE? I'd be ok with that as a NOTE. Krisztian (Apple) clarifies to Patrice (Huawei) the proposal to agree r25 is not due to technical reason. It is simply to limit the technical discussion to 1319 and not to impact this paper. Patrice (Huawei) clarifies that the fact that a DualSteer device is 'two separate UEs' appears in the objective of the SA2 SID, so it is stage 2. Omkar (CableLabs) responds to Miguel (Qualcomm). ==== Final Comments Deadline ==== Patrice (Huawei) says the text on impacts on 3GPP/non-3GPP is not appropriate in this section. Miguel (Qualcomm) asks Patrice (Huawei) questions Miguel (Qualcomm) asks if a NOTE for non-3GPP related text is an agreeable compromise to everyone. Yildirim (Charter Communications) replies to Miguel. Sang-Jun (Samsung) thanks to Krisztian for the way forward proposal, and can accept the way forwrd r26, which is r24+changes. Patrice (Huawei) is OK to have an editor's note for the sake of compromise, but the editor's note should then be: 'The implications of this assumption can be further discussed during the solution phase'. The current editor's note proposed in r26 is not acceptable. We are not OK with adding the NOTE on non-3GPP at this level (already covered in SM KI). Patrice (Huawei) provides r27 showing changes that we could live with, even if not happy about that. r25/r26 are not acceptable. Miguel (Qualcomm) cannot accept this 'For simultaneous transmission over two networks, the DualSteer device is assumed to include two separate UEs' due to not clear what it means for Stage 2. Saso (Intel) points out that an example of 'Device with two UEs' is already described in 23.501 Annex F. Miguel (Qualcomm) thanks Saso, but points that not clear for DualSteer we are talking about the same thing as 23.501 Annex F, hence my issue. | Postponed |
| 19.13 | - | - | - | Architectural Assumptions and Requirements for ATSSS_Ph4 | - | - | Docs:=2 | - | |
| 19.13 | S2-2401288 | P-CR | Approval | 23.700-54: WT3: Assumptions and requirements. | Qualcomm Incorporated | Rel-19 | r12 Agreed. Revised to S2-2401619. | Chia-Lin (MediaTek) provides r01 Jinguo(ZTE) provides comments. Stefan (Ericsson) provides r02 Paul R (Charter) supports r02 and agrees with ZTE that 'Non-Integrated Non-3GPP' is not defined in WID's objectives and should not be part of Architectural Assumptions or Architectural Requirements. Krisztian (Apple) provides r03. Yishan (Huawei) comments on all revisions Rahil (CableLabs) provides r04. Paul R (Charter) provides r05 Rahil (CableLabs) provides r07. Stefano (Qualcomm) provides r06 Pallab (Nokia) provides r08 Stefan (Ericsson) provides comments on r07/r08 Chia-Lin (MediaTek) provides r09 Pallab (Nokia) responds to Stefan (Ericsson) Stefan (Ericsson) provides r10 Yishan (Huawei) provides r12 with some minor change and adds an additional bullet. Please ignore r11 by mistake. Pallab (Nokia) comments on r12 Yishan (Huawei) responds to Pallab (Nokia) Pallab (Nokia) is OK with r12 Rahil (CableLabs) provides r13. ==== Revisions Deadline ==== Pallab (Nokia) proposes to apporve r12. Asks questions on r13 (NOT OK with r13) Myungjune (LGE) is OK with r13. Sang-Jun (Samsung) is OK with r12, and can live with r13. Krisztian (Apple) is OK with r13. Yishan (Huawei) proposes to approve r12 and is not ok with r13 Chia-Lin (MediaTek) is ok r12 and r13, prefers to go with r12 Dieter (Deutsche Telekom ) cannot agree to 'Current Non-3GPP InterWorking Function (N3IWF) and Trusted Non-3GPP Gateway Function (TNGF) are not used to simplify the operation over non-3GPP access.' ==== Final Comments Deadline ==== | Revised |
| 19.13 | S2-2401619 | P-CR | Approval | 23.700-54: WT3: Assumptions and requirements. | Qualcomm Incorporated, Apple, Charter Communications, Nokia, Nokia Shanghai Bell, Ericsson | Rel-19 | Revision of S2-2401288r12. Approved | Approved | |
| 19.13 | - | - | - | Key Issue for WT1.1 | - | - | Docs:=3 | - | |
| 19.13 | S2-2400532 | P-CR | Approval | 23.700-54: FS_MASSS New Key Issue for Work Task #1.1 . | China Telecom | Rel-19 | r15 Agreed. Revised to S2-2401620, merging S2-2401001 | Pallab (Nokia) provides comments and asks if a separate KI for subscription data management is really required and helpful? Krisztian (Apple) provides r02. Yubing (China Telecom) provides r01 Yubing (China Telecom) provides r03 Zhenhua (vivo) provides r04 Haiyang (Huawei) provides comments. CATT (Liping) ask for a clarification and provide comments for the KI description Yubing (China Telecom) replies Zhenhua (vivo) replies. Stefan (Ericsson) provides comments Yaxin (OPPO) provides r05. Miguel (Qualcomm) provides r06 CATT(Liping)provides r07 Zhenhua (vivo) provides r08 Zhenhua (vivo) provides r09 try to not use term of 'DualSteer UE/Device' in this KI Lalith(Samsung) provides r11 Omkar (CableLabs) provides r12. Lalith(Samsung) comments. Kundan(NEC)provides comments. Ellen (Google) provides r13 Lalith(Samsung) replies. Pallab (Nokia) provides r14 Stefan (Ericsson) provides r15 Haiyang (Huawei) provides r16 ==== Revisions Deadline ==== Pallab (Nokia) proposes to approve r15. Objects to r16 Yubing (China Telecom) prefer r15. Myungjune (LGE) prefer r15 can live with r16. Jeounglak (ETRI) prefer r16. CATT (Liping) prefers r15. Zhenhua (vivo) prefers r15. Haiyang (Huawei) prefers r16, can live with r15; object to others Yaxin (OPPO) is OK with r15. Miguel (Qualcomm) is ok with either r15 or r16 Yildirim (Charter Communications) support only r16 but can live with r15. Omkar (CableLabs) supports r16 but can live with r15, will oppose to all the other revisions. Guanzhou (InterDigital) prefers r15. ==== Final Comments Deadline ==== | Revised |
| 19.13 | S2-2401620 | P-CR | Approval | 23.700-54: FS_MASSS New Key Issue for Work Task #1.1. | China Telecom, OPPO, Apple, CATT, Nokia, Nokia Shanghai Bell, Ericsson, LG Electronics | Rel-19 | Revision of S2-2400532r15, merging S2-2401001. Approved | Approved | |
| 19.13 | S2-2401001 | P-CR | Approval | 23.700-54: 23.700-54: Key issue X: Subscription enhancement for dual steer . | OPPO | Rel-19 | Merged into S2-2401620 | Marco(Huawei) merged into S2-00532 ==== Revisions Deadline ==== Krisztian (Apple) proposes to mark this as merged into S2-2400532. ==== Final Comments Deadline ==== | Merged |
| 19.13 | - | - | - | Key Issue for WT1.2 | - | - | Docs:=9 | - | |
| 19.13 | S2-2400157 | P-CR | Approval | 23.700-54: FS_MASSS New KI for WT#1.2: Registration aspects for DualSteer. | ETRI | Rel-19 | Merged into S2-2401621 | Jeounglak (ETRI) accepts the recommendation from Rapporteur to merge this into S2-2401137. Sang-Jun (Samsung) proposes to merge this into S2-2401137 as Rapportuer recommended. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 19.13 | S2-2400533 | P-CR | Approval | 23.700-54: FS_MASSS New Key Issue for Work Task #1.2. | China Telecom | Rel-19 | Merged into S2-2401621 | Sang-Jun (Samsung) proposes to merge this into S2-2401137 as Rapportuer recommended. Patrice (Huawei) expects this contribution to be indeed merged, or to be noted otherwise. Yubing (China Telecom) agree to merge this Tdoc into S2-2401137 as Rapportuer recommended. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 19.13 | S2-2400602 | P-CR | Approval | 23.700-54: Key Issue for WT#1.2: Enhancement of Registration Procedure for DualSteer Devices. | CATT | Rel-19 | Merged into S2-2401621 | Liping (CATT) proposes to merge S2-2400602 into S2-2401137 as Rapporteur recommended. Sang-Jun (Samsung) proposes to merge this into S2-2401137 as Rapportuer recommended. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 19.13 | S2-2400743 | P-CR | Approval | 23.700-54: Key issue for WT1.2: Enhancements for DualSteer Registration aspects . | Samsung | Rel-19 | Merged into S2-2401621 | Sang-Jun (Samsung) accepts the recommendation from Rapporteur to merge this into S2-2401137. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 19.13 | S2-2401002 | P-CR | Approval | 23.700-54: 23.700-54: Key issue X: Registration enhancement for dual steer . | OPPO | Rel-19 | Merged into S2-2401621 | Sang-Jun (Samsung) proposes to merge this into S2-2401137 as Rapportuer recommended. Patrice (Huawei) expects this contribution to be indeed merged, or to be noted otherwise. ==== Revisions Deadline ==== Krisztian (Apple) proposes to mark this as merged into S2-2401137. ==== Final Comments Deadline ==== | Merged |
| 19.13 | S2-2401024 | P-CR | Approval | 23.700-54: WT#1 new Key Issue: registration aspects. | Xiaomi | Rel-19 | Merged into S2-2401621 | Sang-Jun (Samsung) proposes to merge this into S2-2401137 as Rapportuer recommended. Yuxin (Xiaomi) agrees to merge this into S2-2401137 ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 19.13 | S2-2401137 | P-CR | Approval | 23.700-54: FS_MASSS_Key Issue for WT#1.2, Registration and mobility management for SUPI/UE associated with a DualSteer device. | Nokia, Nokia Shanghai Bell, Ericsson | Rel-19 | r11 Agreed. Revised to S2-2401621, merging S2-2400157, S2-2400533, S2-2400602, S2-2400743, S2-2401002, S2-2401024 and S2-2401326 | Sang-Jun (Samsung) proposes to use this as baseline for KI for WT#1.2 as Rapportuer recommended. Zhenhua (vivo) provides r01 Pallab (Nokia) provides comments on r01 Liping(CATT) provides r03 Lalith(Samsung) provides r02 Zhenhua (vivo) comments on 'sharing one subscription profile' Pallab (Nokia) provides comments on r02 Zhenhua (vivo) provides comments on r02 about the 'NAS procedures' Zhenhua (vivo) replies Pallab (Nokia) about removing of 'SUPIs/UEs' Jeounglak (ETRI) provides missing URL for r04, based on r03, changing satellite to non-terrestrial. Jeounglak (ETRI) provides r04, based on r03, changing satellite to non-terrestrial. Yubing (China Telcom) has the same concern on 'NAS procedures' part Stefan (Ericsson) comments Myungjune (LGE) provides r05 Chia-Lin (MediaTek) provides r06 based on r05 without sub-bullet 2 since this has been included in sub-bullet 1 Lalith (Samsung) replies comments on r02 Lalith (Samsung) is OK with r05 Miguel (Qualcomm) provides r06 Krisztian (Apple) provides r08. Yuxin (Xiaomi) provides r07 Miguel (Qualcomm) clarifies r06 is indeed from Chia-Lin (MediaTek), my bad seems I was beaten to the punch and didn't realize it, but actually I'm ok with r06 which removes the text I was trying to remove. Sang-Jun (Samsung) pointed out that Miguel (Qualcomm) provided r06 later than Chia-Lin (MediaTek). Pallab (Nokia) points out that r08 file is empty Pallab (Nokia) proposes to continue using 'DualSteer device' term. OK with r07 Zhenhua (vivo) provides r09 to avoid the term of 'DualSteer UE/Device' Yildirim (Charter Communication) comments and questions why 'mobility management' aspects removed. Omkar (CableLabs) provides r10. Chunshan(CATT) provides r11. Yishan (Huawei) asks for clarifications ==== Revisions Deadline ==== Chunshan (CATT) proposes to approve r11 and asks for co-sign this paper. Pallab (Nokia) proposes to approve r11. Myungjune (LGE) is ok with r11 Miguel (Qualcomm) ok with r11 Krisztian (Apple) supports r11. Zhenhua (vivo) prefers r11 Chia-Lin (MediaTek) is ok with r11 and r10 Jeounglak (ETRI) perfers r11. Stefan (Ericsson) OK with r11 Yishan (Huawei) is ok with r09 or r11 and objects to other versions. Yaxin (OPPO) is OK with r11. Yildirim (Charter Communications) support only r11 but can live with r10. Omkar (CableLabs) supports r11 but can live with r10, will object to all other revisions. ==== Final Comments Deadline ==== | Revised |
| 19.13 | S2-2401621 | P-CR | Approval | 23.700-54: FS_MASSS_Key Issue for WT#1.2, Registration and mobility management for SUPI/UE associated with a DualSteer device. | Nokia, Nokia Shanghai Bell, Ericsson, CATT, ETRI, LG Electronics, Lenovo | Rel-19 | Revision of S2-2401137r11, merging S2-2400157, S2-2400533, S2-2400602, S2-2400743, S2-2401002, S2-2401024 and S2-2401326. Approved | Approved | |
| 19.13 | S2-2401326 | P-CR | Approval | 23.700-54: FS_MASSS DualSteer Key Issue for Registration aspects. | Apple | Rel-19 | Merged into S2-2401621 | Sang-Jun (Samsung) proposes to merge this into S2-2401137 as Rapportuer recommended. Patrice (Huawei) expects this contribution to be indeed merged, or to be noted otherwise. ==== Revisions Deadline ==== Krisztian (Apple) agrees to mark this as merged into S2-2401137. ==== Final Comments Deadline ==== | Merged |
| 19.13 | - | - | - | Key Issue for WT1.3 - Policy aspects | - | - | Docs:=8 | - | |
| 19.13 | S2-2400534 | P-CR | Approval | 23.700-54: FS_MASSS New Key Issue for policy aspect of Work Task #1.3. | China Telecom | Rel-19 | Merged into S2-2401636 | Sang-Jun (Samsung) proposes to merge this into S2-2400787 as Rapportuer recommended. Patrice (Huawei) expects this contribution to be indeed merged, or to be noted otherwise. Yubing (China Telecom) agree to merge this Tdoc into S2-2400787 ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 19.13 | S2-2400713 | P-CR | Approval | 23.700-54: FS_MASSS New KI for WT#1.3: Policy aspects for DualSteer. | ETRI | Rel-19 | Merged into S2-2401635 | Jeounglak (ETRI) accepts the recommendation from Rapporteur to merge this into S2-2400787. Sang-Jun (Samsung) proposes to merge this into S2-2400787 as Rapportuer recommended. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 19.13 | S2-2400752 | P-CR | Approval | 23.700-54: Key issue for WT1.3: Enhancements for DualSteer Policy aspects . | Samsung | Rel-19 | Merged into S2-2401635 | Sang-Jun (Samsung) accepts recommendation from Rapporteur to merge this into S2-2400787. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 19.13 | S2-2400787 | P-CR | Approval | 23.700-54: 23.700-54: New Key issue X: Policy enhancement for dual steer device . | OPPO | Rel-19 | r34 + changes Agreed. Revised to S2-2401635, merging S2-2400713, S2-2400752, S2-2401016, S2-2401139, S2-2401246 and S2-2401331 | Pallab (Nokia) provides r01 merging some text from 1139. Sang-Jun (Samsung) proposes to use this as baseline as Rapportuer recommended. Jeounglak (ETRI) provides r02 with rewording. Jeounglak (ETRI) provides r03 with rewording. Yang (OPPO) provides r04 with comprehensively incorporating all bullets from relevant companies' contributions. Suggest to use R04 to start the discussion. Pallab (Nokia) asks if 'traffic splitting' is in scope of the study? Yang (OPPO) provides r05 with correction pointed by Pallab Huazhang (vivo) comments to r05 that some of the wording and bullet is not acceptable Guanzhou (InterDigtial) responds to Huazhang (Vivo) comments. Yishan (Huawei) is not ok with any revisions so far (from r00 to r05) Amanda ( Futurewei ) supports Interdigital's view on trigger condition Krisztian (Apple) provides r06. Guanzhou (InterDigtial) comments on non-3GPP access related policy. Yildirim (Charter Communications) comments that non-3GPP access related policy impact should also be considered as part of this KI. Myungjune (LGE) provides r07. Yang (OPPO) provides r08 based on r06/07 Pallab (Nokia) provides r09 based on r08 Jeounglak (ETRI) provides r10 based on r09, adding PNI-NPN UPF. Stefan (Ericsson) provides r11 Chia-Lin (MediaTek) provides r12 and mentions that we should not impact PLMN selection here Myungjune (LGE) comments on PLMN selection aspect Lalith(Samsung) comments on r12 Yishan (Huawei) provides r13 and tries to restructure the aspects to be studied in this KI. Miguel (Qualcomm) comments and provides r14 Krisztian (Apple) provides r18. Guanzhou (InterDigtial) corrects that 22.369 in my previous email should be TS 22.261. Guanzhou (InterDigtial) responds to Myungjune (LGE) comments. Myungjune (LGE) questions whether PLMN selection is not impacted. Guanzhou (InterDigtial) provides r017. Miguel (Qualcomm) provides r16. Omkar (CableLabs) comments and provides r15. Yishan (Huawei) objects to r18 because it is not aligned with SID scope. Yildirim (Charter) comments on r16/r17/r18; and clarifies why the NOTE on non-3GPP access aspect is included as a NOTE in the SID. Huazhang (vivo) reply to Amanda(Futurewei) Patrice (Huawei) clarifies wrt the note on non-3GPP access. Pallab (Nokia) comments on r18. provides r19 Yildirim (Charter) replies to Patrice (Huawei). Sang-Jun (Samsung) supports Pallab (Nokia)'s comments and r19. Yang (OPPO) provides r20 and comments Pallab (Nokia) responds to Yang (OPPO) Yishan (Huawei) provides r21 and objects to r19 and r20 since they still include service level switching Yang (OPPO) comments to Huawei's response. Provides r22 Lalith(Samsung) provides r25 Miguel (Qualcomm) responds to Liping Wu(CATT) and Guanzhou (InterDigtial) Liping Wu(CATT) shares the same view with InterDigtial and insists on adding 'PLMN selection' in this KI Guanzhou (InterDigtial) comments on 'PLMN selection'. Miguel (Qualcomm) provides comments and r24 Omkar (CableLabs) provides r23. Pallab (Nokia) comments and provides r26 Liping (CATT) provides r27 Chia-Lin (MediaTek) responds and provides r28 based on r26 Huazhang (vivo) provide comments to Chia-Lin(MTK) that how to understand connect to an additional PLMN/NPN, may need clarification Stefan (Ericsson) provides r29 Chunshan(CATT) provides r30. Yishan (Huawei) provides r31 with editorial changes. Omkar (CableLabs) provides r32. Ellen (Google) provides r33 (based on r32): editorial changes and removes redundant texts (blue marks) Miguel (Qualcomm) responds to various comments regarding PLMN selection Miguel (Qualcomm) ok with r33 Yang (OPPO) made some clean-up and small changes based on R33 Yang (OPPO) provides r34 with some clean-up and small changes based on r33 ==== Revisions Deadline ==== Pallab (Nokia) is OK to approve r34 + changes proposed by Krisztian (Apple) Krisztian (Apple) is ok with r34. Additional changes for the final version: 1. NPN -> PNI-NPN, 2. UE policy -> UE policies, 3. remove underline from NOTE2, 4. re-number NOTE2 to NOTE1, 5. add co-signers. Myungjune (LGE) is ok with r34, r35. Guanzhou (InterDigital) provides r35 (NPN->PNI-NPN, UE policy -> UE policies) and co-signs. Jeounglak (ETRI) prefers r34 and agree to the changes proposed by Krisztian (Apple) Yang (OPPO) suggest to agree r34, the editorial change (suggested by Krisztian 1-5) will be done when uploading the final version Chunshan(CATT) agree to go with r34, the editorial change (suggested by Krisztian 1-5) needs to be handled in tonight CC. Sang-Jun (Samsung) is OK with r34 + proposed changes. Huazhang (vivo) is OK to agree r34 + the editorial change (suggested by Krisztian 1-5) Chia-Lin (MediaTek) is ok with r34 and is also ok with r34 with the changes as suggested by Krisztian (Apple) Yishan (Huawei) prefers r31 with adding a NOTE below the first bullet 'NOTE 1: If any PLMN selection enhancement is identified, SA2's role could be limited to study system level impacts and/or trigger CT1 to handle the work.', also can further accept the changes from r32 (reword NOTE 2), r34 (add 'and how' in the last bullet) and r35 (NPN->PNI-NPN, UE policy -> UE policies). Object to the changes from r33 and objects to other versions. Guanzhou (InterDigtial) OK with the Chairman's suggestion to approve r34+changes. Asks to co-sign the final version. Yildirim (Charter Communications) support only r34 with the proposed updates by Krisztian. Omkar (CableLabs) supports only r34 with the proposed updates by Krisztian, will object to all other revisions. ==== Final Comments Deadline ==== Yishan (Huawei) provides r36 and tries to make progress in this meeting. | Revised |
| 19.13 | S2-2401635 | P-CR | Approval | 23.700-54: 23.700-54: New Key issue X: Policy enhancement for dual steer device . | OPPO, Apple, ETRI, Nokia, Nokia Shanghai Bell, Google, CATT, InterDigital, LG Electronics, Lenovo | Rel-19 | Revision of S2-2400787r34 + changes, merging S2-2400713, S2-2400752, S2-2401016, S2-2401139, S2-2401246 and S2-2401331. CC#4: Postponed | Postponed | |
| 19.13 | S2-2401139 | P-CR | Approval | 23.700-54: FS_MASSS_Key Issue for policy impacts of WT#1.3. | Nokia, Nokia Shanghai Bell, Ericsson | Rel-19 | Merged into S2-2401635 | Pallab (Nokia) is OK to have the KI discussion in a single thread i.e. in tdoc S2-2400787. Sang-Jun (Samsung) proposes to merge this into S2-2400787 as Rapportuer recommended. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 19.13 | S2-2401246 | P-CR | Approval | 23.700-54: New KI: Policies in support of Establishing Connection to Second 3GPP Access Network. | InterDigital, Inc. | Rel-19 | Merged into S2-2401635 | Sang-Jun (Samsung) proposes to merge this into S2-2400787 as Rapportuer recommended. Patrice (Huawei) expects this contribution to be indeed merged, or to be noted otherwise. ==== Revisions Deadline ==== Krisztian (Apple) proposes to mark this as merged into S2-2400787. ==== Final Comments Deadline ==== | Merged |
| 19.13 | S2-2401331 | P-CR | Approval | 23.700-54: FS_MASSS DualSteer Key Issue for Network policies. | Apple | Rel-19 | Merged into S2-2401635 | Sang-Jun (Samsung) proposes to merge this into S2-2400787 as Rapportuer recommended. Patrice (Huawei) expects this contribution to be indeed merged, or to be noted otherwise. ==== Revisions Deadline ==== Krisztian (Apple) agrees to mark this as merged into S2-2400787. ==== Final Comments Deadline ==== | Merged |
| 19.13 | - | - | - | Key Issue for WT1.3 - Session management aspects | - | - | Docs:=11 | - | |
| 19.13 | S2-2400256 | P-CR | Approval | 23.700-54: KI#X for WT#1.3: Enhancement of Session Management to support steering and switching for the DualSteer Devices. | CATT | Rel-19 | Merged into S2-2401636 | Sang-Jun (Samsung) proposes to merge this intoS2-2401329 as Rapportuer recommended. Patrice (Huawei) expects this contribution to be indeed merged, or to be noted otherwise. ==== Revisions Deadline ==== Krisztian (Apple) proposes to mark this as merged into S2-2401329. ==== Final Comments Deadline ==== | Merged |
| 19.13 | S2-2400535 | P-CR | Approval | 23.700-54: FS_MASSS New Key Issue for session aspect of Work Task #1.3. | China Telecom | Rel-19 | Merged into S2-2401636 | Sang-Jun (Samsung) proposes to merge this intoS2-2401329 as Rapportuer recommended. Patrice (Huawei) expects this contribution to be indeed merged, or to be noted otherwise. Yubing (China Telecom) agree to merge this Tdoc into S2-2401329 ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 19.13 | S2-2400588 | P-CR | Approval | 23.700-54: New KI: Traffic steering and switching for a DualSteer device. | LG Electronics | Rel-19 | Merged into S2-2401636 | Sang-Jun (Samsung) proposes to merge this intoS2-2401329 as Rapportuer recommended. Patrice (Huawei) expects this contribution to be indeed merged, or to be noted otherwise. Myungjune (LGE) is ok to merge into S2-2401329 ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 19.13 | S2-2400710 | P-CR | Approval | 23.700-54: FS_MASSS New KI for WT#1.3: Session aspects for DualSteer. | ETRI | Rel-19 | Merged into S2-2401636 | Jeounglak (ETRI) accepts the recommendation from Rapporteur to merge this into S2-2401329. Sang-Jun (Samsung) proposes to merge this intoS2-2401329 as Rapportuer recommended. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 19.13 | S2-2400753 | P-CR | Approval | 23.700-54: Key issue for WT1.3: Enhancements for DualSteer Session Management Aspects . | Samsung | Rel-19 | Merged into S2-2401636 | Sang-Jun (Samsung) accepts recommendation from Rapporteur to merge this into S2-2401329. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 19.13 | S2-2401003 | P-CR | Approval | 23.700-54: 23.700-54: Key issue X: Session management enhancement for dual steer. | OPPO | Rel-19 | Merged into S2-2401636 | Sang-Jun (Samsung) proposes to merge this intoS2-2401329 as Rapportuer recommended. Patrice (Huawei) expects this contribution to be indeed merged, or to be noted otherwise. ==== Revisions Deadline ==== Krisztian (Apple) proposes to mark this as merged into S2-2401329. ==== Final Comments Deadline ==== | Merged |
| 19.13 | S2-2401025 | P-CR | Approval | 23.700-54: WT#1 new Key Issue: Session management and polices. | Xiaomi | Rel-19 | Merged into S2-2401636 | Sang-Jun (Samsung) proposes to merge this intoS2-2401329 as Rapportuer recommended. Yuxin (Xiaomi) agrees to merge this intoS2-2401329 ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 19.13 | S2-2401138 | P-CR | Approval | 23.700-54: FS_MASSS_Key Issue for Session Management impact of WT#1.3. | Nokia, Nokia Shanghai Bell, Ericsson | Rel-19 | Merged into S2-2401636 | Pallab (Nokia) is OK to have the KI discussion in a single thread i.e. in tdoc S2-2401329. However, we have concerns with some of the aspects proposed in S2-2401329, which we will comment in the respective thread. Sang-Jun (Samsung) proposes to merge this intoS2-2401329 as Rapportuer recommended. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 19.13 | S2-2401286 | P-CR | Approval | 23.700-54: WT1: New Key Issue on enhancements to session management procedures to support DualSteer. | Qualcomm Incorporated | Rel-19 | Merged into S2-2401636 | Sang-Jun (Samsung) proposes to merge this intoS2-2401329 as Rapportuer recommended. Patrice (Huawei) expects this contribution to be indeed merged, or to be noted otherwise. ==== Revisions Deadline ==== Krisztian (Apple) proposes to mark this as merged into S2-2401329. ==== Final Comments Deadline ==== | Merged |
| 19.13 | S2-2401329 | P-CR | Approval | 23.700-54: FS_MASSS DualSteer Key Issue for Session management aspects. | Apple | Rel-19 | r19 + changes Agreed. Revised to S2-2401636, merging S2-2400256, S2-2400534, S2-2400535, S2-2400588, S2-2400710, S2-2400753, S2-2401003, S2-2401025, S2-2401138 and S2-2401286 | Pallab (Nokia) provides r01 merging some text from 1138. Sang-Jun (Samsung) proposes to use this as baseline for KI for Session Management Aspects as Rapportuer recommended. Zhuoyi (China Telecom) provides comments on r01. Jeounglak (ETRI) provides r02 with a clarification. Pallab (Nokia) responds to Zhuoyi (China Telecom). Yishan (Huawei) is not ok with r01 and r02. Pallab (Nokia) requests Yishan (Huawei) to provide some alternative text proposal if current text in r01, r02 is not agreeable Huazhang (vivo) comments to r02 that there are so much details and solution specific, and not a KI. Also some parts need more clarification. Guanzhou (InterDigtial) comments and proposes not to go too much beyond WI. Krisztian (Apple) provides r03. Guanzhou (InterDigtial) provides r04. Pallab (Nokia) responds to Huazhang (vivo). Pallab (Nokia) provides comments on r04 Yang (OPPO) comments Pallab (Nokia) responds to Yang (OPPO) Yang (OPPO) replies to Pallab (Nokia) Yubing (China Telecom) provides comments on r04 Myungjune (LGE) responds to Pallab (Nokia) Chia-Lin (MediaTek) provides r05 Guanzhou (InterDigtial) comments on anchoring. Yaxin (OPPO) provides r06. Guanzhou (InterDigtial) questions r05. Patrice (Huawei) comments on Pallab(Nokia)'s assertion. Yishan (Huawei) provides r07 to restructure the KI Omkar (CableLabs) responds to Patrice (Huawei). Miguel (Qualcomm) provides r08 Omkar (CableLabs) comments and provides r09. Guanzhou (InterDigtial) questions the usage of 'UE stack' in r08+. Miguel (Qualcomm) provides r10, rewrites text added in r09 from Omkar (CableLabs) into a note. Pallab (Nokia) comments and provides r11. Cannot accept previous revisions. Liping (CATT) share the same view with Guanzhou (InterDigtial) and asks for clarifications about 'UE stack'. Huazhang (vivo) provides r12. Yishan (Huawei) is not ok with r11 and r12, which make the KI unclear. Zhenhua (vivo) replies to Yishan (Huawei) about 'DualSteer'. Yishan (Huawei) replies to the comment from Zhenhua (vivo) Huazhang (vivo) provides r13 and response to Yishan Omkar (CableLabs) provides r14. Pallab (Nokia) comments and provides r15 Chia-Lin (MediaTek) provides r16 based on r15 Pallab (Nokia) comments on r16. Why 3GPP is removed. The whole study is about steering across 2 3GPP access Chunshan(CATT) provides r17. Yishan (Huawei) provides r19 on top of r17 (please ignore r18). ==== Revisions Deadline ==== Myungjune (LGE) is ok with r19. Pallab (Nokia) is OK to approve r19 + remove underline from the NOTE text Jeounglak (ETRI) prefers r19. Chunshan(CATT) comments that the NOTE in r19 needs more clarification and may need re-words . Chia-Lin (MediaTek) is ok with r19 and suggest to go with r19 Sang-Jun (Samsung) is fine with r19 Yubing (China Telecom) is ok with r19 Stefan (Ericsson) is ok with r19 Yishan (Huawei) proposes to approve r19 and objects to other versions. Yildirim (Charter Communications) support only r17; can live with r19. Editorial (underlined text in the NOTE) can be corrected in the final version. Krisztian (Apple) is OK to approve r19 or r17 + editorial change to NOTE Omkar (CableLabs) supports r17; can live with r19 (with below suggested change). Objects to all other revisions. ==== Final Comments Deadline ==== Omkar (CableLabs) cannot accept r19 the way it is, proposes r20. | Revised |
| 19.13 | S2-2401636 | P-CR | Approval | 23.700-54: FS_MASSS DualSteer Key Issue for Session management aspects. | Apple, ETRI, Nokia, Nokia Shanghai Bell, LG Electronics | Rel-19 | Revision of S2-2401329r19 + changes, merging S2-2400256, S2-2400534, S2-2400535, S2-2400588, S2-2400710, S2-2400753, S2-2401003, S2-2401025, S2-2401138 and S2-2401286. CC#4: Postponed | Postponed | |
| 19.13 | - | - | - | Key Issue related to WT1.x | - | - | Docs:=3 | - | |
| 19.13 | S2-2401004 | P-CR | Approval | 23.700-54: 23.700-54: New KI for NTN+TN and NTN+NTN scenarios . | OPPO | Rel-19 | Noted | Stefan (Ericsson) comments Myungjune (LGE) comments Miguel (Qualcomm) agrees this proposed KI is not necessary Yishan (Huawei) also agrees this proposed KI is not needed Yaxin (OPPO) replies. Pallab (Nokia) also concurs to the previous comments that a separate KI for NTN is not needed. ==== Revisions Deadline ==== Krisztian (Apple) proposes this to be noted. ==== Final Comments Deadline ==== | Noted |
| 19.13 | S2-2401016 | P-CR | Approval | 23.700-54: Key Issue for DualSteer. | Huawei, HiSilicon | Rel-19 | Merged into S2-2401635 | Sang-Jun (Samsung) suggests to mark this as noted, as Polocy and Session Management Key Issues are being discussed separately. Pallab (Nokia) proposes to consider this as merged to S2-2400787 as all the policy aspects are covered in this. Stefan (Ericsson) agrees that this should be considered merged ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 19.13 | S2-2401136 | P-CR | Approval | 23.700-54: FS_MASSS_Key Issue for WT#1, E2E Architecture to support DualSteer device. | Nokia, Nokia Shanghai Bell, Ericsson | Rel-19 | Noted | Sang-Jun (Samsung) suggests to mark this as noted, as Key Issues for WT#1 are being discussed separately. Yishan (Huawei) agrees with suggestions from Sang-Jun (Samsung) . Pallab (Nokia) proposes to consider a separate KI for E2E architecture. Disagrees to NOTE this. Patrice (Huawei) proposes to note Miguel (Qualcomm) agrees this KI is not needed Pallab (Nokia) responds Patrice (Huawei) proposes Pallab(Nokia) to bring a revision of the SID if they wish to extend the study, and note this contribution in the meantime. ==== Revisions Deadline ==== Pallab (Nokia) OK to NOTE the paper based on multiple objections Krisztian (Apple) shares the views this KI is not necessary. The paper should be noted. ==== Final Comments Deadline ==== | Noted |
| 19.13 | - | - | - | Key Issue for WT2 | - | - | Docs:=4 | - | |
| 19.13 | S2-2400352 | P-CR | Approval | 23.700-54: New KI: MPQUIC steering functionality to steer, switch, and split non-UDP traffic (WT#2). | Ericsson, Nokia, Nokia Shanghai Bell | Rel-19 | r02 + changes Agreed. Revised to S2-2401637, merging S2-2401017 and S2-2401333 | Stefano (Qualcomm) suggests rewording. Marco(Huawei) provides r01 adding considerations on5G_RG Krisztian (Apple) provides r02. ==== Revisions Deadline ==== Myungjune (LGE) is ok with r02. Pallab (Nokia) is OK with r02. Stefan (Ericsson) is also OK with r02 Dieter (Deutsche Telekom) is OK with r02. Please add Deutsche Telekom as supporting company! Paul R (Charter) is supportive of this pCR and is OK w/ r02. Robert (OQ Technology) supports r02. Rahil (CableLabs) is ok with r02, with changing the statement on 5G-RG to be aligned with arch. assumptions. ==== Final Comments Deadline ==== | Revised |
| 19.13 | S2-2401637 | P-CR | Approval | 23.700-54: New KI: MPQUIC steering functionality to steer, switch, and split non-UDP traffic (WT#2). | Ericsson, Nokia, Nokia Shanghai Bell, Apple, Deutsche Telekom, Lenovo | Rel-19 | Revision of S2-2400352r02 + changes, merging S2-2401017 and S2-2401333. Approved | Approved | |
| 19.13 | S2-2401017 | P-CR | Approval | 23.700-54: Key Issue for WT#2 of FS_MASSS. | Huawei, HiSilicon | Rel-19 | Merged into S2-2401637 | Stefano (Qualcomm) recommends using S2-2400352 as basis. ==== Revisions Deadline ==== Krisztian (Apple) proposes to mark this as merged into S2-2400352. ==== Final Comments Deadline ==== | Merged |
| 19.13 | S2-2401333 | P-CR | Approval | 23.700-54: FS_MASSS ATSSS_Ph4 Key Issue for MPQUIC steering functionality for non-UDP traffic. | Apple | Rel-19 | Merged into S2-2401637 | Marco(Huawei) recommends using S2-2400352 as basis ==== Revisions Deadline ==== Krisztian (Apple) agrees to mark this as merged into S2-2400352. ==== Final Comments Deadline ==== | Merged |
| 19.13 | - | - | - | Key Issue for WT3 | - | - | Docs:=6 | - | |
| 19.13 | S2-2400353 | P-CR | Approval | 23.700-54: New KI: ATSSS support with simplified operation over non-3GPP access (WT#3). | Ericsson, Nokia, Nokia Shanghai Bell | Rel-19 | Merged into S2-2401638 | Myungjune (LGE) comments. Stefano (Qualcomm) recommends taking this or S2-2401289 as baseline. Recommends one common KI for the whole WT3 to ensure we don't have fragmentation of solutions due to different Kis. Marco(Huawei) WT3.1 addresses whether to keep NAS and whether to eliminate IPSec. WT3.2 how support ATSSS with N3GPP and N3GPP without NAS. Therefore in WT3.2 the NAS is not supported per definition, while in WT 3.1 needs to be study and considered. Preferable to keep sperate or in single KI as 2 set of problems to be studied. Stefano (Qualcomm) attempts to merge in 1289 and provides R01 of 1289 in other thread. Pallab (Nokia) also supports the view to have a single KI for WT 3.1, 3.2. OK to use either 0353 or 1289 as baseline Chia-Lin (MediaTek) are ok to use 00353 as baseline and provides r01 Stefan (Ericsson) ok to use 01289 as baseline, and consider this 00353 as merged. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 19.13 | S2-2400590 | P-CR | Approval | 23.700-54: New KI: ATSSS enhancement to support architecture not based on current TNGF/N3IWF. | LG Electronics | Rel-19 | Merged into S2-2401638 | Myungjune (LGE) OK to merge into other P-CR e.g. S2-2400353 or S2-2401289. Stefano (Qualcomm) recommends taking S2-2400353 or S2-2401289 as baseline and consider this merged into it. Recommends one common KI for the whole WT3 to ensure we don't have fragmentation of solutions due to different Kis. Marco(Huawei) WT3.1 addresses whether to keep NAS and whether to eliminate IPSec. WT3.2 how support ATSSS with N3GPP and N3GPP without NAS. Therefore in WT3.2 the NAS is not supported per definition, while in WT 3.1 needs to be study and considered. Preferable to keep sperate or in single KI as 2 set of problem to be studied ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 19.13 | S2-2401018 | P-CR | Approval | 23.700-54: Key Issue for WT#3 of ATSSS_Ph4. | Huawei, HiSilicon | Rel-19 | Merged into S2-2401638 | Stefano (Qualcomm) recommends taking S2-2400353 or S2-2401289 as baseline and consider this merged into it. Recommends one common KI for the whole WT3 to ensure we don't have fragmentation of solutions due to different Kis. ==== Revisions Deadline ==== Krisztian (Apple) proposes to mark this as merged into S2-2401289. ==== Final Comments Deadline ==== | Merged |
| 19.13 | S2-2401289 | P-CR | Approval | 23.700-54: WT3: New Key Issue on simplified ATSSS operation over non-3GPP access. | Qualcomm Incorporated | Rel-19 | r06 + changes Agreed. Revised to S2-2401638, merging S2-2400258, S2-2400259, S2-2400353, S2-2400590, S2-2400756, S2-2400758, S2-2401018 and S2-2401338 | Stefano (Qualcomm) recommends taking this or S2-2400353 as baseline and consider this merged into it. Recommends one common KI for the whole WT3 to ensure we don't have fragmentation of solutions due to different Kis. Stefano (Qualcomm) provides R01 merging with other papers on KI#3 Krisztian (Apple) provides r02. Stefan (Ericsson) provides r03 Marco(Huawei) we prefer 2 KIs, but if majority prefer one at least keep well organized. propose r04 Sang-Jun (Samsung) proposed to change a bullet, so that registration should be replaced with AM/SM. Pallab (Nokia) comments and provides r05 Paul R (Charter) provides r06 removing N3IWF/TNGF from KI title Saso (Intel) seeks clarification Marco(Huawei) agree with Saso and provide r07 Paul R (Charter) provides r08 removing N3IWF/TNGF from KI title Pallab (Nokia) objects to r07, r08 ==== Revisions Deadline ==== Pallab (Nokia) OK to approve r06. Maintains objection to r07, r08 Krisztian (Apple) proposes to agree r06. Myungjune (LGE) corrects that previous comment is from LGE. I'm ok with r06. Stefano (Qualcomm) is OK with r06. Sang-Jun (Samsung) is OK with r06. Stefano (Qualcomm) OK with r06 if r07, r08 are not acceptable. Stefan (Ericsson) supports approving r06 Chia-Lin (MediaTek) is ok with r06 and if possible a minor editorial change to r06 in 'non-3GPP access without 5G NAS over non-3GPP ' to add with 'access' to become 'non-3GPP access without 5G NAS over non-3GPP access' Paul R (Charter) supports approving r06 ==== Final Comments Deadline ==== | Revised |
| 19.13 | S2-2401638 | P-CR | Approval | 23.700-54: WT3: New Key Issue on simplified ATSSS operation over non-3GPP access. | Qualcomm Incorporated, Apple, Ericsson, Nokia, Nokia Shanghai Bell, Charter Communications | Rel-19 | Revision of S2-2401289r06 + changes, merging S2-2400258, S2-2400259, S2-2400353, S2-2400590, S2-2400756, S2-2400758, S2-2401018 and S2-2401338. Approved | Approved | |
| 19.13 | S2-2401338 | P-CR | Approval | 23.700-54: FS_MASSS ATSSS_Ph4 Key Issue for Non-TNGF/N3IWF based non-3GPP access. | Apple | Rel-19 | Merged into S2-2401638 | Stefano (Qualcomm) recommends taking S2-2400353 or S2-2401289 as baseline and consider this merged into it. Recommends one common KI for the whole WT3 to ensure we don't have fragmentation of solutions due to different Kis. Marco(Huawei) WT3.1 addresses whether to keep NAS and whether to eliminate IPSec. WT3.2 how support ATSSS with N3GPP and N3GPP without NAS. Therefore in WT3.2 the NAS is not supported per definition, while in WT 3.1 needs to be study and considered. Preferable to keep sperate or in single KI as 2 set of problem to be studied ==== Revisions Deadline ==== Krisztian (Apple) agrees to mark this as merged into S2-2401289. ==== Final Comments Deadline ==== | Merged |
| 19.13 | - | - | - | Key Issue specific for WT3.1 | - | - | Docs:=2 | - | |
| 19.13 | S2-2400258 | P-CR | Approval | 23.700-54: KI#X for WT#3.1: Control Plane and User plane of Non-3GPP access without NAS as an access of ATSSS. | CATT | Rel-19 | Merged into S2-2401638 | Stefano (Qualcomm) recommends taking S2-2400353 or S2-2401289 as baseline and consider this merged into it. Recommends one common KI for the whole WT3 to ensure we don't have fragmentation of solutions due to different Kis. Marco(Huawei) WT3.1 addresses whether to keep NAS and whether to eliminate IPSec. WT3.2 how support ATSSS with N3GPP and N3GPP without NAS. Therefore in WT3.2 the NAS is not supported per definition, while in WT 3.1 needs to be study and considered. Preferable to keep sperate or in single KI as 2 set of problem to be studied Stefano (Qualcomm) question for clarification: since the text in this document is pretty much rolled into revisions of 1289, is this document considered merged into 1289? If not, why are we duplicating text in different KIs? We would be forced to object to duplicated KIs ==== Revisions Deadline ==== Krisztian (Apple) proposes to mark this as merged into S2-2401289. Stefano (Qualcomm) is merged into 1289 ==== Final Comments Deadline ==== | Merged |
| 19.13 | S2-2400756 | P-CR | Approval | 23.700-54: Key issue for WT3.1: Enhancements for ATSSS elimination of IPSec tunnel encapsulation. | Samsung | Rel-19 | Merged into S2-2401638 | Stefano (Qualcomm) recommends taking S2-2400353 or S2-2401289 as baseline and consider this merged into it. Recommends one common KI for the whole WT3 to ensure we don't have fragmentation of solutions due to different Kis. Stefano (Qualcomm) question for clarification: since the text in this document is pretty much rolled into revisions of 1289, is this document considered merged into 1289? If not, why are we duplicating text in different KIs? We would be forced to object to duplicated KIs ==== Revisions Deadline ==== Sang-Jun (Samsung) is OK with merging this into 1289 Stefano (Qualcomm) is merged into 1289 ==== Final Comments Deadline ==== | Merged |
| 19.13 | - | - | - | Key Issue specific for WT3.2 | - | - | Docs:=2 | - | |
| 19.13 | S2-2400259 | P-CR | Approval | 23.700-54: KI#X for WT#3.2: ATSSS with non-3GPP access without NAS. | CATT | Rel-19 | Merged into S2-2401638 | Stefano (Qualcomm) recommends taking S2-2400353 or S2-2401289 as baseline and consider this merged into it. Recommends one common KI for the whole WT3 to ensure we don't have fragmentation of solutions due to different Kis. Marco(Huawei) WT3.1 addresses whether to keep NAS and whether to eliminate IPSec. WT3.2 how support ATSSS with N3GPP and N3GPP without NAS. Therefore in WT3.2 the NAS is not supported per definition, while in WT 3.1 needs to be study and considered. Preferable to keep sperate or in single KI as 2 set of problem to be studied Stefano (Qualcomm) question for clarification: since the text in this document is pretty much rolled into revisions of 1289, is this document considered merged into 1289? If not, why are we duplicating text in different KIs? We would be forced to object to duplicated KIs ==== Revisions Deadline ==== Krisztian (Apple) proposes to mark this as merged into S2-2401289. Stefano (Qualcomm) is merged into 1289 ==== Final Comments Deadline ==== | Merged |
| 19.13 | S2-2400758 | P-CR | Approval | 23.700-54: Key issue for WT3.2: Enhancements for ATSSS non-3GPP access without 5G NAS. | Samsung | Rel-19 | Merged into S2-2401638 | Stefano (Qualcomm) recommends taking S2-2400353 or S2-2401289 as baseline and consider this merged into it. Recommends one common KI for the whole WT3 to ensure we don't have fragmentation of solutions due to different Kis. Marco(Huawei) WT3.1 addresses whether to keep NAS and whether to eliminate IPSec. WT3.2 how support ATSSS with N3GPP and N3GPP without NAS. Therefore in WT3.2 the NAS is not supported per definition, while in WT 3.1 needs to be study and considered. Preferable to keep sperate or in single KI as 2 set of problem to be studied Stefano (Qualcomm) question for clarification: since the text in this document is pretty much rolled into revisions of 1289, is this document considered merged into 1289? If not, why are we duplicating text in different KIs? We would be forced to object to duplicated KIs ==== Revisions Deadline ==== Sang-Jun (Samsung) is OK with merging this into 1289 Stefano (Qualcomm) is merged into 1289 ==== Final Comments Deadline ==== | Merged |
| 19.13 | - | - | - | Documents exceeding TU budget | - | - | Docs:=24 | - | |
| 19.13 | S2-2400603 | P-CR | Approval | 23.700-54: Terms for FS_MASSS. | CATT | Rel-19 | Not Handled | ==== Final Comments Deadline ==== | Not Handled |
| 19.13 | S2-2400723 | P-CR | Approval | 23.700-54: FS_MASSS_TR23700-54_Clarification of the term of DualSteer Device. | China Telecom | Rel-19 | Not Handled | ==== Final Comments Deadline ==== | Not Handled |
| 19.13 | S2-2400587 | P-CR | Approval | 23.700-54: Assumption and requirements on DualSteer. | LG Electronics | Rel-19 | Not Handled | ==== Final Comments Deadline ==== | Not Handled |
| 19.13 | S2-2400604 | P-CR | Approval | 23.700-54: Architectural Assumptions and Requirements for DualSteer. | CATT | Rel-19 | Not Handled | ==== Final Comments Deadline ==== | Not Handled |
| 19.13 | S2-2400774 | P-CR | Approval | 23.700-54: Architectural assumption for DualSteer Work Tasks. | Samsung | Rel-19 | Not Handled | ==== Final Comments Deadline ==== | Not Handled |
| 19.13 | S2-2401000 | P-CR | Approval | 23.700-54: 23.700-54: Architectural assumptions and requirements for DualSteer . | OPPO | Rel-19 | Not Handled | ==== Final Comments Deadline ==== | Not Handled |
| 19.13 | S2-2401014 | P-CR | Approval | 23.700-54: Architectural Assumptions and Requirements for DualSteer. | Huawei, HiSilicon | Rel-19 | Not Handled | ==== Final Comments Deadline ==== | Not Handled |
| 19.13 | S2-2401023 | P-CR | Approval | 23.700-54: WT#1 DualSteer architecture assumptions. | Xiaomi | Rel-19 | Not Handled | ==== Final Comments Deadline ==== | Not Handled |
| 19.13 | S2-2401135 | P-CR | Approval | 23.700-54: FS_MASSS_Architectural Assumptions and Architectural Requirements. | Nokia, Nokia Shanghai Bell | Rel-19 | Not Handled | ==== Final Comments Deadline ==== | Not Handled |
| 19.13 | S2-2401283 | P-CR | Approval | 23.700-54: WT1: Assumptions and definitions. | Qualcomm Incorporated | Rel-19 | Not Handled | ==== Final Comments Deadline ==== | Not Handled |
| 19.13 | S2-2401015 | P-CR | Approval | 23.700-54: Architectural assumptions and requirements for ATSSS_Ph4. | Huawei, HiSilicon | Rel-19 | Not Handled | ==== Final Comments Deadline ==== | Not Handled |
| 19.13 | S2-2401324 | P-CR | Approval | 23.700-54: FS_MASSS Architectural Assumptions and Requirements for ATSSS_Ph4. | Apple | Rel-19 | Not Handled | ==== Final Comments Deadline ==== | Not Handled |
| 19.13 | S2-2401115 | P-CR | Approval | 23.700-54: Architectural Assumptions and Requirements. | ZTE | Rel-19 | Not Handled | ==== Final Comments Deadline ==== | Not Handled |
| 19.13 | S2-2400601 | P-CR | Approval | 23.700-54: Key Issue for WT#1.1: Enhancement of subscription for DualSteer Devices. | CATT | Rel-19 | Not Handled | ==== Final Comments Deadline ==== | Not Handled |
| 19.13 | S2-2400742 | P-CR | Approval | 23.700-54: Key issue for WT1.1: Enhancements for DualSteer in subscription aspects. | Samsung | Rel-19 | Not Handled | ==== Final Comments Deadline ==== | Not Handled |
| 19.13 | S2-2401284 | P-CR | Approval | 23.700-54: WT1: New Key Issue on enhancements to registration procedures to support DualSteer. | Qualcomm Incorporated | Rel-19 | Not Handled | ==== Final Comments Deadline ==== | Not Handled |
| 19.13 | S2-2401285 | P-CR | Approval | 23.700-54: WT1: New Key Issue on enhancements to subscription aspects to support DualSteer. | Qualcomm Incorporated | Rel-19 | Not Handled | ==== Final Comments Deadline ==== | Not Handled |
| 19.13 | S2-2401325 | P-CR | Approval | 23.700-54: FS_MASSS DualSteer Key Issue for Subscription aspects. | Apple | Rel-19 | Not Handled | ==== Final Comments Deadline ==== | Not Handled |
| 19.13 | S2-2400255 | P-CR | Approval | 23.700-54: KI#X for WT#1.3: Enhancement of Policies to support steering and switching for the DualSteer Devices. | CATT | Rel-19 | Not Handled | ==== Final Comments Deadline ==== | Not Handled |
| 19.13 | S2-2401287 | P-CR | Approval | 23.700-54: WT1: New Key Issue on enhancements to policies to support DualSteer. | Qualcomm Incorporated | Rel-19 | Not Handled | ==== Final Comments Deadline ==== | Not Handled |
| 19.13 | S2-2400257 | P-CR | Approval | 23.700-54: KI#X for WT#2: Enhancement of MPQUIC steering functionality and steering mode to steer, switch, and split non-UDP traffic . | CATT | Rel-19 | Not Handled | ==== Final Comments Deadline ==== | Not Handled |
| 19.13 | S2-2400589 | P-CR | Approval | 23.700-54: New KI: Non-UDP traffic support with extension of MPQUIC steering functionality. | LG Electronics | Rel-19 | Not Handled | ==== Final Comments Deadline ==== | Not Handled |
| 19.13 | S2-2400755 | P-CR | Approval | 23.700-54: Key issue for WT2: Enhancements for ATSSS MPQUIC steering non-UDP traffic . | Samsung | Rel-19 | Not Handled | ==== Final Comments Deadline ==== | Not Handled |
| 19.13 | S2-2401026 | P-CR | Approval | 23.700-54: WT#2 ATSSS_Ph4: MPQUIC steering functionality enhancement. | Xiaomi | Rel-19 | Not Handled | ==== Final Comments Deadline ==== | Not Handled |
| 19.14 | - | - | - | Study on Architecture support of Ambient power-enabled Internet of Things (FS_AmbientIoT) | - | - | Docs:=47 | - | |
| 19.14 | - | - | - | Skeleton and Scope | - | - | Docs:=3 | - | |
| 19.14 | S2-2400509 | P-CR | Approval | 23.700-13: Skeleton for TR 23.700-13 | OPPO | Rel-19 | Approved | Runze (Huawei) supports the proposal. Peter Hedman (Ericsson) proposal looks good and follows normal TR structure ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Approved |
| 19.14 | S2-2400510 | P-CR | Approval | 23.700-13: Scope for Ambient IoT. | OPPO, Huawei, Hisilicon | Rel-19 | r12 + changes Agreed. Revised to S2-2401820. | Runze (Huawei) provides reply to Robbie (Ericsson). Fei (OPPO) comments. Guanzhou (InterDigtial) provides r02. Sang-Jun (Samsung) provides comments. Robbie (Ericsson) provides comments. Runze (Huawei) provides re-wording and provides r01. Runze (Huawei) comments on r02. Runze replies to Fei (OPPO). Guanzhou (InterDigtial) responds to Runze(Huawei) question. Peter Hedman (Ericsson) provides r03, re-sending as server didn't accept the mail Deng Qiang (CATT) comments on Ambient IoT services. Runze (Huawei) replies to Deng Qiang (CATT)'s comments on Ambient IoT services. Runze (Huawei) replies to Guanzhou (InterDigtial) and provides r04, on top of r02. Robbie (Ericsson) shares the same view as Deng Qiang (CATT), and comments. Mehrdad (MediaTek Inc.) provides comment on all revisions of the scope clause so far Changhong (Intel) comments and provides r05. Runze (Huawei) can live with r05. Runze (Huawei) replies to Mehrdad (MediaTek Inc.) . Peter Hedman (Ericsson) provides comments Fei (OPPO) provides responses and r07 to remove the duplication (please ignore r06 which was wrongly uploaded). Dongjoo (Nokia) comments on r07. Fei (OPPO) responds to Runze (Huawei). Fei (OPPO) provides responses to Dongjoo (Nokia) and provides r08. Sebastian (Qualcomm) comments Sebastian (Qualcomm) provides r09 Mehrdad (MediaTek Inc.) thinks r09 is in the right direction Penny (Wiliot) support r09 changes Runze (Huawei) cannot accept version from 06-09 and suggest to use r05 for further discussion. Runze(Huawei) replied to Sebastian, Mehrdad, and Penny. Mehrdad (MediaTek Inc.) replies to Huawei. Fei (OPPO) provides r11 and also indicates that Deng Qiang (CATT) has provided r10 Deng Qiang (CATT) also thinks RAN scope needs to be considered as SA1 requirement is superset. Robbie (Ericsson) provides r12. Mehrdad (MediaTek Inc.) is generally ok with r12. The only issue is the Terms clause now appears in two PCRs, this one and also S2-2400375 Fei (OPPO) responds to Mehrdad (MediaTek) on the terms Runze (Huawei) provides r13, on top of r12. ==== Revisions Deadline ==== Fei (OPPO) is fine with r13. Deng Qiang (CATT) is fine with r13. Sang-Jun (Samsung) is OK with r13. Runze (Huawei) proposed to agree r13. Xiaowan (vivo) request to agree r13 with remove of 'traffic' in device terminated traffic in 3.1 or agree r12 Fei (OPPO): Xiaowan's proposal is ok to us. Steve (Huawei) comments on 'traffic' and reading of it. Fei (OPPO) made a proposal Penny (Wiliot) supports Fei's proposal Xiaowan Ke(vivo) replies and also give proposal Fei (OPPO) suggests to use intermediate node. Xiaowan(vivo) is OK for Fei's proposal Runze (Huawei) suggests to agree r12 for this meeting, as suggested by Xiaowan (vivo). Robbie (Ericsson) agrees with Runze (Huawei) to move forward with r12. Fei (OPPO) let's go with r12. Sebastian (Qualcomm) is ok with r12, r13 or r09; objects to other versions; is not ok with further changes as proposed by Fei Xiaowan Ke(vivo) is OK with r12 and ask to cosign; and disagree with r13 ==== Final Comments Deadline ==== | Revised |
| 19.14 | S2-2401820 | P-CR | Approval | 23.700-13: Scope for Ambient IoT. | OPPO, Huawei, HiSilicon, vivo | Rel-19 | Revision of S2-2400510r12 + changes. Approved | Approved | |
| 19.14 | - | - | - | Architectural Assumptions and Requirements | - | - | Docs:=9 | - | |
| 19.14 | S2-2400179 | P-CR | Approval | 23.700-13: Architecture Assumption and Architecture Requirement. | Vivo, OPPO | Rel-19 | r25 + changes Agreed. Revised to S2-2401821, merging S2-2400289, S2-2400376, S2-2400518, S2-2401063, S2-2401072, S2-2401202 and S2-2401235 | Xiaowan Ke(vivo) provides r01 Dongjoo (Nokia) provides comments Hao (ZTE) comments. Peter Hedman (Ericsson) provides comments Xiaowan Ke(vivo) replies to Dongjoo (Nokia) Xiaowan Ke(vivo) replies to Hao (ZTE) Xiaowan Ke(vivo) replies to Peter Hedman (Ericsson) Fei (OPPO) comments. Robbie (Ericsson) provides r02, merging S2-2400376 into this pCR. Runze (Huawei) comments on r02. Runze (Huawei) comments on 'architectural requirement' part in r02. Robbie (Ericsson) provides r04 and replies to Runze (Huawei). Guanzhou (InterDigtial) provides r03 merging proposals from S2-2301235. Deng Qiang (CATT) provides r05 and comments on some bullets. Fei (OPPO) comments and provides r06. Xiaowan Ke(vivo) provides r07 Lufeng Han(Spreadtrum) provides r08 Nassima (KPN) supports r08 Aihua(CMCC) suggests to use 'Mobility management is not supported' rather than 'Handover is not supported' Runze (Huawei) replies to Peter Hedman (Ericsson). Aihua(CMCC) suggests to use 'Mobility management is not supported' via providing r09 Runze (Huawei) provides r10. Fei (OPPO) comments on r09. Changhong (Intel) comments. Fei (OPPO) responds to Changhong (Intel) Penny (Wiliot) provides r03, merging S2-2400289r01 assumptions into this pCR. Penny (Wiliot) provides r11, merging S2-2400289r01 assumptions into this pCR. Guanzhou (InterDigtial) provides r12. Runze (Huawei) comments on r11. Qianghua (Huawei) provides comments on CM and MM Penny (Wiliot) response to Runze for clarification Peter Hedman (Ericsson) provides replies to Runze Fei (OPPO) provides r14. Peter Hedman (Ericsson) provides r13 Deng Qiang (CATT) comments on r14. Xiaowan Ke(vivo) provides r15 Peter Hedman (Ericsson) provides r16 Sebastian (Qualcomm) provides r17 Mehrdad (MediaTek Inc.) provides r18 Runze (Huawei) provides r19. Antoine (Orange) comments. Mehrdad (MediaTek Inc.) replies to Huawei and Orange. Sang-Jun (Samsung) comments on scope and Architecture Assumptions. Changhong (Intel) provides r20. Guanzhou (InterDigtial) questions r19 on 'The use of the AIoT radio interface is subject to network control' Deng Qiang (CATT) comments on r19. Xiaowan Ke(vivo) provides r21 Fei (OPPO) also thinks wording under network control more clear. Peter Hedman (Ericsson) provides r22 Aihua(CMCC) provides r23. Xiaowan Ke(vivo) provides r24 Xiaowan Ke(vivo) provides r25 ==== Revisions Deadline ==== Guanzhou (InterDigtial) is OK with r25 and asks to co-sign. Deng Qiang (CATT) is ok with r25 and would like to co-sign. Fei (OPPO) is ok with r25. Sang-Jun (Samsung) is OK with r25 Runze (Huawei) supports r25. Lufeng Han(Spreadtrum) is ok with r25 and would like to co-sign. Aihua(CMCC) is fine with r25 and would like to co-sign. Robbie (Ericsson) is fine with r25. Mehrdad (MediaTek Inc.) is OK with 25 and would like to co-sign. Penny (Wiliot) is OK with r25 Sebastian (Qualcomm) is ok with r25, objects to other version ==== Final Comments Deadline ==== | Revised |
| 19.14 | S2-2401821 | P-CR | Approval | 23.700-13: Architecture Assumption and Architecture Requirement. | Vivo, OPPO, Ericsson, Huawei, Wiliot, CATT, InterDigtial, Spreadtrum, China Mobile, MediaTek | Rel-19 | Revision of S2-2400179r25 + changes, merging S2-2400289, S2-2400376, S2-2400518, S2-2401063, S2-2401072, S2-2401202 and S2-2401235. Approved | Approved | |
| 19.14 | S2-2400289 | P-CR | Approval | 23.700-13: FS_AmbientIoT architectural assumptions and requirements. | Wiliot | Rel-19 | Merged into S2-2401821 | Mehrdad (MediaTek Inc.) suggests to mark this PCR as merged in S2-2400179 or noted. Penny Efraim-Sagi (Wiliot) provides r01 Fei (OPPO) suggests to use S2-2400375 thread for the term discussion and S2-2400179 thread for the assumption discussion Penny (Wiliot) I'll add our suggested our and assumption to S2-2400375 and S2-2400179 threads. Peter Hedman (Ericsson) agrees with Merhdad that we should consider this as merged with 00179 Penny (Wiliot) agrees with Merhdad and Peter that we should consider this as merged with 00179 ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 19.14 | S2-2400376 | P-CR | Approval | 23.700-13: Architectural Assumptions and Principles for Ambient IoT. | Ericsson | Rel-19 | Merged into S2-2401821 | Robbie (Ericsson) provides r01 taking the comments received from CC into account. Robbie (Ericsson) merges it into S2-2400179. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 19.14 | S2-2400518 | P-CR | Approval | 23.700-13: 23.700-13: Architecture Requirement for FS_AmbientIoT . | CATT | Rel-19 | Merged into S2-2401821 | Mehrdad (MediaTek Inc.) suggests to mark this PCR as merged in S2-2400179 or noted. Runze (Huawei) suggests to mark this PCR as merged in S2-2400179. Deng Qiang (CATT) agrees to mark this PCR as merged in S2-2400179. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 19.14 | S2-2401063 | P-CR | Approval | 23.700-13: Architectural Assumption for Ambient IoT. | Huawei, HiSilicon | Rel-19 | Merged into S2-2401821 | Runze (Huawei) provides r01. Saso (Intel) seeks clarification on the DT trigger. Sang-Jun (Samsung) supports comments from Peter Hedman (Ericsson). Hao (ZTE) comments on r01. Peter Hedman (Ericsson) provides comments and concerns with the provided assumptions and proposes to move forward with 00179 Dongjoo (Nokia) shares the same view as Peter Hedman (Ericsson) and Sang-Jun (Samsung). Nassima (KPN) supports moving forward with 00179 Mehrdad (MediaTek Inc.) also suggests to mark this PCR as either merged in S2-2400179 or noted. Runze (Huawei) is fine to mark this PCR merged in S2-2400179. Runze (Huawei) replies to Saso (Intel). ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 19.14 | S2-2401072 | P-CR | Approval | 23.700-13: Architectural assumptions and requirements. | China Mobile | Rel-19 | Merged into S2-2401821 | Mehrdad (MediaTek Inc.) suggests to mark this PCR as merged in S2-2400179 ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 19.14 | S2-2401202 | P-CR | Approval | 23.700-13: Architectural Assumptions. | Xiaomi | Rel-19 | Merged into S2-2401821 | Peter Hedman (Ericsson) suggests to mark the paper merged with 00179 Jinhua (Xiaomi) replies to Peter, merged with 00179 is OK. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 19.14 | S2-2401235 | P-CR | Approval | 23.700-13: FS_AmbientIoT: Architecture Assumptions and Requirements. | InterDigital, Inc. | Rel-19 | Merged into S2-2401821 | Peter Hedman (Ericsson) suggests to mark the paper merged with 00179 Runze (Huawei) agrees with Peter Hedman (Ericsson) to mark the paper merged with 00179 ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 19.14 | - | - | - | Key issue 1 | - | - | Docs:=2 | - | |
| 19.14 | S2-2400511 | P-CR | Approval | 23.700-13: New KI: KI corresponding to WT#1 for architecture support. | OPPO, Huawei, Hisilicon | Rel-19 | r11 + changes Agreed. Revised to S2-2401822. | Fei (OPPO) provides r01. Dongjoo (Nokia) provides comments. Fei (OPPO) responds to Dongjoo (Nokia). Xiaowan Ke(vivo) provides r02 Mehrdad (MediaTek Inc.) provides comment on r02 Changhong (Intel) comments and expresses concerns on this key issue. Guanzhou (InterDigtial) provides r03. Deng Qiang (CATT) asks questions and comments. Changhong (Intel) provides r04. Fei (OPPO) provides responses and r05. Dongjoo (Nokia) co-signs and provides r06. Jinhua (Xiaomi) comments, whether overlap with SA3 SID objective Fei (OPPO) replies to Jinhua (Xiaomi) and provides the link of r06. Robbie (Ericsson) asks Fei (OPPO) Fei (OPPO) replied to Robbie (Ericsson) Robbie (Ericsson) replies to Fei (OPPO) Amanda ( Futurewei ) co-signs and provides r07 Steve (Huawei) comments on SA2/SA3 split. Jinhua (Xiaomi) replies to Fei, Peter Hedman (Ericsson) provides r08 Runze (Huawei) provides r09, based on r08 from Peter (Ericsson). Fei (OPPO) provides r10. Robbie (Ericsson) asks Fei (OPPO). Fei (OPPO) provides replies to Robbie (Ericsson). Steve (Huawei) comments in the notes. Fei (OPPO) replied to Steve (Huawei) Robbie (Ericsson) replies to Fei (OPPO). Steve (Huawei) provides a new note Fei (OPPO) provides r11 based on Steve's suggestion. ==== Revisions Deadline ==== Guanzhou (InterDigtial) OK with r11 and asks to co-sign. Fei (OPPO) thanks for Deng Qiang (CATT)'s cosigning Sang-Jun (Samsung) comments r11 seems fine. Deng Qiang (CATT) is fine with r11 and would like to co-sign. Dongjoo ( Nokia ) is fine with r11. Amanda ( Futurewei ) is fine with r11. Runze (Huawei) supports r11. Robbie (Ericsson) is fine with r11. Mehrdad (MediaTek Inc.) is OK with r11 Penny (Wiliot) is OK with r11 Changhong (Intel) is OK with r11 and ask to cosign. Sebastian (Qualcomm) is ok with r11 and objects to other versions Xiaowan Ke(vivo) is OK with r11 and ask to cosign ==== Final Comments Deadline ==== | Revised |
| 19.14 | S2-2401822 | P-CR | Approval | 23.700-13: New KI: KI corresponding to WT#1 for architecture support. | OPPO, Huawei, HiSilicon, Nokia, Nokia Shanghi Bell, Futurewei, Ericsson, CATT, InterDigtial, Intel, vivo | Rel-19 | Revision of S2-2400511r11 + changes. Approved | Approved | |
| 19.14 | - | - | - | Key issue 2 | - | - | Docs:=2 | - | |
| 19.14 | S2-2401061 | P-CR | Approval | 23.700-13: New Key Issue: Key Issue proposal for WT#2. | Huawei, HiSilicon, OPPO | Rel-19 | r07 + changes Agreed. Revised to S2-2401823. | Runze (Huawei) summarizes the proposals to Key issue/WT#2. Dongjoo (Nokia) provides comments. Robbie (Ericsson) provides r01 to include group of Ambient IoT devices aspect. Other comments may come later. Fei (OPPO) asks questions on r01. Robbie (Ericsson) replies to Fei (OPPO). Changhong (Intel) comments on connection management aspects. Runze (Huawei) replied to Changhong (Intel). Runze (Huawei) replies to Robbie (Ericsson). Runze (Huawei) replies to Dongjoo (Nokia) and provides r02. Changhong (Intel) replies to Runze. Robbie (Ericsson) provides r03 to reinstate management aspect of a group of Ambient IoT devices. Deng Qiang (CATT) prefers r02 and comments. Runze (Huawei) replies to Robbie, Changhong and Dengqiang and provides r04. Robbie (Ericsson) replies to Runze (Huawei). Sebastian (Qualcomm) provides r05 Jinhua (xiaomi) replies to Runze, Dongjoo (Nokia) is fine with both r04 and r05, and would like to co-sign. Runze (Huawei) asks questions to Sebastian (Qualcomm). Runze (Huawei) replies to Jinhua (xiaomi). Runze (Huawei) thanks Dongjoo (Nokia) for the support. Amanda ( Futurewei ) prefer r04, but can live with r05, and like to co-sign Runze (Huawei) provides r06, based on r04. Fei (OPPO) comments Peter Hedman (Ericsson) provides comments to FEI and ok with r06 Fei (OPPO) replied to Peter (Ericsson) and provides r07. Runze (Huawei) supports r07. ==== Revisions Deadline ==== Deng Qiang (CATT) is fine with r07 and would like to co-sign. Sang-Jun (Samsung) comments r07 is fine. Hao (ZTE) supports r07. Dongjoo ( Nokia ) is fine with r07. Amanda ( Futurewei ) is fine with r07 Robbie (Ericsson) is fine with r07. Lufeng Han(Spreadtrum) is fine with r07 and would like to co-sign. Penny (Wiliot) is fine with r07. Changhong (Intel) is fine with r07 and ask to cosign. Sebastian (Qualcomm) is ok with r07 and objects to other versions Guanzhou (InterDigtial) is OK with r07 and asks to co-sign. Xiaowan Ke(vivo) is OK for r07 and would like to cosign ==== Final Comments Deadline ==== | Revised |
| 19.14 | S2-2401823 | P-CR | Approval | 23.700-13: New Key Issue: Key Issue proposal for WT#2. | Huawei, HiSilicon, OPPO, Nokia, Nokia Shanghai Bell, Futurewei, Ericsson, CATT, InterDigtial, Spreadtrum, Intel, vivo | Rel-19 | Revision of S2-2401061r07 + changes. Approved | Approved | |
| 19.14 | - | - | - | Key issue 3 | - | - | Docs:=2 | - | |
| 19.14 | S2-2401060 | P-CR | Approval | 23.700-13: New Key Issue: Key issue proposal for WT#3. | Huawei, HiSilicon, OPPO | Rel-19 | r07 + changes Agreed. Revised to S2-2401824. | Runze (Huawei) summarize the proposals to WT/key issue 3. Dongjoo (Nokia) provides comments. Robbie (Ericsson) provides r01 to include group of Ambient IoT devices aspect. Other comments may come later. Runze (Huawei) replied to Dongjoo (Nokia) and provides r02. Runze (Huawei) cannot accept r01 unless the requirements are justified. Robbie (Ericsson) objects to r00/r02 and provides r03. Robbie (Ericsson) clarifies to Runze (Huawei) the requirements are in TS 22.369. Runze (Huawei) replies to Robbie (Ericsson) and objects to r03, provides r04. Robbie (Ericsson) provides comments on r04. Sebastian (Qualcomm) provides r05 Jinhua (Xiaomi) provides comments, Dongjoo (Nokia) would like to co-sign this paper. Runze (Huawei) provides r06, based on r05. Runze (Huawei) replies to Robbie (Ericsson) . Runze (Huawei) sent mail to wrong thread, please ignore. Amanda ( Futurewei ) provides r06 and co-sign Runze (Huawei) supports r06. Robbie (Ericsson) is fine with r06 and asks to co-sign. Guanzhou (InterDigtial) provides r07. Runze (Huawei) replies to Guanzhou. ==== Revisions Deadline ==== Fei (OPPO) is fine with r07 and r08 Sang-Jun (Samsung) comments r07 is OK. Deng Qiang (CATT) is fine with r07 or r08, and would like to co-sign. Dongjoo ( Nokia ) is fine with r07, but provide 08 just to add Nokia as co-signer. Hao (ZTE) supports r07. Amanda ( Futurewei ) is fine with r07 Dongjoo (Nokia) requests agreement on r07, as r08 was provided after the revision deadline by a mistake, and requests to include Nokia and Nokia Shanghai Bell as co-sources in the final version. Robbie (Ericsson) is fine with r07 (+ co-signer) and would like to co-sign. Penny (Wiliot) is fine with r07/r08 Changhong (Intel) is fine with r07 and r08, Intel can cosign. Guanzhou (InterDigtial) OK with r07 or r08 and asks to co-sign. Objects to other versions. Sebastian (Qualcomm) can only accept r07 if 'for AIoT Device operation' is removed (as this is not defined at this stage) and objects to all other versions Runze (Huawei) replies to Sebastian (Qualcomm) and proposes for CC#4. Sebastian (Qualcomm) replies to Runze ==== Final Comments Deadline ==== | Revised |
| 19.14 | S2-2401824 | P-CR | Approval | 23.700-13: New Key Issue: Key issue proposal for WT#3. | Huawei, HiSilicon, OPPO, Futurewei, CATT, Nokia, Nokia Shanghai Bell, Ericsson, InterDigtial, Intel | Rel-19 | Revision of S2-2401060r07 + changes. Approved | Approved | |
| 19.14 | - | - | - | Terms and definitions | - | - | Docs:=5 | - | |
| 19.14 | S2-2400375 | P-CR | Approval | 23.700-13: Terms and abbreviation for Ambient IoT. | Ericsson | Rel-19 | r10 Agreed. Revised to S2-2401825, merging S2-2401062 | Robbie (Ericsson) replies to Runze (Huawei). Dongjoo (Nokia) provides comments Runze (Huawei) replies to Robbie (Ericsson) on the scope of traffic types Fei (OPPO) comments and provides r02. Robbie (Ericsson) provides r01 taking the comments received from CC into account. Robbie (Ericsson) replies to Dongjoo (Nokia) and Fei (OPPO) and asks to ignore r03. LaeYoung (LGE) comments. Runze (Huawei) replies to Robbie (Ericsson). Xiaowan Ke(vivo) provides r04 on top of r02 Nassima (KPN) provides comments, is OK with r02 and r04 Fei (OPPO) responds to Robbie (Ericsson) Robbie (Ericsson) replies to Fei (OPPO). Fei (OPPO) provides responses. Penny (Wiliot) replies to Robbie (Ericsson) on the scope of Ambient IoT term Runze (Huawei) provides r05. Robbie (Ericsson) can live with r05. Robbie (Ericsson) replies to Penny (Wiliot) Dongjoo (Nokia) is fine with r05 Fei (OPPO) provides r06. Penny (Wiliot) relipes to Robbie (Ericsson) Runze (Huawei) thanks Robbie (Ericsson) can live with r05. Robbie (Ericsson) provides r07/r08 and replies to Lufeng Han(Spreadtrum). Lufeng Han(Spreadtrum) comment for clarification. Lufeng Han(Spreadtrum) reply to Robbie that r07/08 can resolve the previous confusion. Antoine (Orange) provides r09 'with limited or no energy storage capability'. Robbie (Ericsson) provides comments to Antoine (Orange). Steve (Huawei) comments on batteries are not the only energy storage. Xiaowan Ke(vivo) provides r10 Penny (Wiliot) Supportive of r10 definition ==== Revisions Deadline ==== LaeYoung (LGE) also supports r10. Fei (OPPO) agrees with Doogjoo's explanation and supports r10. Dongjoo ( Nokia ) supports r10. Amanda ( Futurewei ) supports r09, don't agree with r10 Runze (Huawei) supports r10. Robbie (Ericsson) supports r10. Antoine (Orange) withdraws r09 and supports r10. Lufeng Han(Spreadtrum) is fine with r10. Amanda ( Futurewei ) withdraws objection and support r10. Sebastian (Qualcomm) is ok with r10 and objects to other versions ==== Final Comments Deadline ==== | Revised |
| 19.14 | S2-2401825 | P-CR | Approval | 23.700-13: Terms and abbreviation for Ambient IoT. | Ericsson, LG Electronics, vivo | Rel-19 | Revision of S2-2400375r10, merging S2-2401062. Approved | Approved | |
| 19.14 | S2-2401062 | P-CR | Approval | 23.700-13: New Term proposal: Ambient IoT Device. | Huawei, HiSilicon | Rel-19 | Merged into S2-2401825 | Peter Hedman (Ericsson) can we consider this merged with 00375? Jinhua (Xiaomi) comments, the Ambient IoT device is already discussed in 0375, prefer to merged there. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 19.14 | S2-2401213 | P-CR | Approval | 23.700-13: Terms for Ambient IoT Services. | Vivo | Rel-19 | CC#4: r05 agreed. Revised to S2-2401840. | Runze(Huawei) replies to Robbie (Ericsson). Robbie (Ericsson) asks questions. Robbie (Ericsson) replies to Runze(Huawei). Deng Qiang (CATT) comments AIoT Service as part of KI in 1060. Hao (ZTE) comments. Robbie (Ericsson) agrees with Deng Qiang (CATT). Xiaowan Ke(vivo) replies and provides r01 Dongjoo (Nokia) provides comments. Chunhui (NEC) comments. Fei (OPPO) comments. Deng Qiang (CATT) comments to avoid using service. Changhong (Intel) comments. Runze (Huawei) replies to Robbie (Ericsson) Runze(Huawei) replies to Dengqiang (CATT) and provides r02. Runze (Huawei) replies to Changhong (Intel) comments. Guanzhou (InterDigtial) can't accept existing definitions and propose to use SA1 definiton. R03 provided Changhong (Intel) prefers r03 provided by Guanzhou. Peter Hedman (Ericsson) provides comments on r03 Xiaowan Ke(vivo) provides r04 Dongjoo (Nokia) provides comments on r03. Xiaowan Ke(vivo) replies to Dongjoo (Nokia) Dongjoo (Nokia) is fine with r04. Sebastian (Qualcomm) comments and provides r05 Jinhua (xiaomi) comments, with r04, Runze (Huawei) provides r06, based on r05. Jinhua (Xiaomi) replies to Runze, Changhong (Intel) replies to Hao. Hao (ZTE) comments on r06. Deng Qiang (CATT) proposed to keep the Term short or leave it to be studied in KI#3. Jinhua (xiaomi) replies to Runze, can live with r07, Deng Qiang (CATT) is fine with r07 provided by Runze. Hao (ZTE) is fine with r07. Runze (Huawei) provides r08. Hao (ZTE) comments on r08. Peter Hedman (Ericsson) provides r09 Sebastian (Qualcomm) comments that this discussion on terms is not useful and a waste of timel at this stage and suggests to note the pCR Changhong (Intel) provides r10 Chris (Vodafone) provides r11 Runze (Huawei) replies to Sebastian (Qualcomm) and hope r11 is acceptable to you. Xiaowan Ke(vivo) provides r12 Sebastian (Qualcomm) replies to Runze Guanzhou (InterDigtial) also suggests to note the pCR. Runze (Huawei) replies to Guanzhou (InterDigtial), and explains why the definition is important. Runze (Huawei) replies to Sebastian (Qualcomm) and removes definition of Ambient IoT service in r13 provided. ==== Revisions Deadline ==== Fei (OPPO) supports r13. Deng Qiang (CATT) is ok with the comprised r13. Hao (ZTE) proposes to go with r13. Aihua(CMCC) is fine with r13. Sebastian (Qualcomm) objects to r13 (and other versions) Runze (Huawei) replies to Sebastian (Qualcomm) and propose an EN 'the term needs update based on the outcome of key issues' as way forward, propose it for CC#4. Sebastian (Qualcomm) comments that it does not make sense to add terms and then mark those as for further study; not ok to agree half-baked terms with Editor's notes Runze (Huawei) replies to Sebastian (Qualcomm). ==== Final Comments Deadline ==== | Revised |
| 19.14 | S2-2401840 | P-CR | Approval | 23.700-13: Terms for Ambient IoT Services. | Vivo | Rel-19 | Revision of S2-2401213r05. Approved | Approved | |
| 19.14 | - | - | - | Annex | - | - | Docs:=1 | - | |
| 19.14 | S2-2401059 | P-CR | Approval | 23.700-13: Background Information for Ambient IoT Service. | Huawei, HiSilicon | Rel-19 | Noted | Peter Hedman (Ericsson) provides comments Steve (Huawei) comments. Fei (OPPO) comments. Peter Hedman (Ericsson) provides comments as the annex should not be used to steer the scope of the work Steve (Huawei) thanks for the feedback, provides r01. Sebastian (Qualcomm) objects to the pCR (original and revisions) Genadi (Lenovo) agrees with Sebastian (Qualcomm) that the proposed Annex is a possible solution. Steve (Huawei) comments on trying to provide a general overview Peter Hedman (Ericsson) agrees with Genadi and Sebastian to note the pCR ==== Revisions Deadline ==== Guanzhou (InterDigital) shares the opinion that this is not needed. Fei (OPPO) is fine to note this PCR. ==== Final Comments Deadline ==== | Noted |
| 19.14 | - | - | - | Discussion paper | - | - | Docs:=1 | - | |
| 19.14 | S2-2400081 | DISCUSSION | Discussion | Considerations for Ambient IoT Devices | Wiliot Ltd. | Noted | Noted | ||
| 19.14 | - | - | - | Documents exceeding TU budget/quota | - | - | Docs:=22 | - | |
| 19.14 | S2-2401244 | P-CR | Approval | 23.700-13: Definition of Ambient IoT Device. | OPPO | Rel-19 | Not Handled | ==== Final Comments Deadline ==== | Not Handled |
| 19.14 | S2-2400517 | P-CR | Approval | 23.700-13: 23.700-13: Architecture Assumption for FS_AmbientIoT . | CATT | Rel-19 | Not Handled | ==== Final Comments Deadline ==== | Not Handled |
| 19.14 | S2-2400377 | P-CR | Approval | 23.700-13: New KI: Group of Ambient IoT Devices. | Ericsson | Rel-19 | Not Handled | ==== Final Comments Deadline ==== | Not Handled |
| 19.14 | S2-2400512 | P-CR | Approval | 23.700-13: New KI: KI corresponding to WT#2 . | OPPO | Rel-19 | Not Handled | ==== Final Comments Deadline ==== | Not Handled |
| 19.14 | S2-2400519 | P-CR | Approval | 23.700-13: 23.700-13: New KI for FS_AmbientIoT WT#2. | CATT | Rel-19 | Not Handled | ==== Final Comments Deadline ==== | Not Handled |
| 19.14 | S2-2400520 | P-CR | Approval | 23.700-13: 23.700-13: New KI for FS_AmbientIoT WT#3. | CATT | Rel-19 | Not Handled | ==== Final Comments Deadline ==== | Not Handled |
| 19.14 | S2-2400682 | P-CR | Approval | 23.700-13: KI for Ambient IOT Services WT#3.1. | CMCC | Rel-19 | Not Handled | ==== Final Comments Deadline ==== | Not Handled |
| 19.14 | S2-2400730 | P-CR | Approval | 23.700-13: Key issue for WT#1: Architecture to support Ambient IoT. | Samsung | Rel-19 | Not Handled | ==== Final Comments Deadline ==== | Not Handled |
| 19.14 | S2-2400735 | P-CR | Approval | 23.700-13: Key issue for WT#2: Identification, Subscription, Registration and Connection management to support Ambient IoT devices. | Samsung | Rel-19 | Not Handled | ==== Final Comments Deadline ==== | Not Handled |
| 19.14 | S2-2400737 | P-CR | Approval | 23.700-13: Key issue for WT#3: Enhancements for Ambient IoT Services. | Samsung | Rel-19 | Not Handled | ==== Final Comments Deadline ==== | Not Handled |
| 19.14 | S2-2400904 | P-CR | Approval | 23.700-13: New KI: Support Ambient IoT Services and Exposure. | ZTE | Rel-19 | Not Handled | ==== Final Comments Deadline ==== | Not Handled |
| 19.14 | S2-2400905 | P-CR | Approval | 23.700-13: New KI: Identification of Ambient IoT Device. | ZTE | Rel-19 | Not Handled | ==== Final Comments Deadline ==== | Not Handled |
| 19.14 | S2-2401032 | P-CR | Approval | 23.700-13: Key Issue for WT#2: Enhancement to support the Identifier related functionalities for Ambient IoT Device. | Spreadtrum Communications | Rel-19 | Not Handled | ==== Final Comments Deadline ==== | Not Handled |
| 19.14 | S2-2401073 | P-CR | Approval | 23.700-13: New KI for Architecture Enhancements to Support Ambient IoT (WT#1). | CMCC | Rel-19 | Not Handled | ==== Final Comments Deadline ==== | Not Handled |
| 19.14 | S2-2401074 | P-CR | Approval | 23.700-13: New KI for Identification, Subscription, Registration and Connection to Support Ambient IoT (WT#2). | China Mobile | Rel-19 | Not Handled | ==== Final Comments Deadline ==== | Not Handled |
| 19.14 | S2-2401203 | P-CR | Approval | 23.700-13: WT2_New KIs on ISRC management to support Ambient IoT device. | Xiaomi | Rel-19 | Not Handled | ==== Final Comments Deadline ==== | Not Handled |
| 19.14 | S2-2401204 | P-CR | Approval | 23.700-13: WT3_New KIs on Ambient IoT Services. | Xiaomi | Rel-19 | Not Handled | ==== Final Comments Deadline ==== | Not Handled |
| 19.14 | S2-2401211 | P-CR | Approval | 23.700-13: KI for WT#1: Service architecture support for Ambient IoT Services and Ambient IoT devices. | Vivo | Rel-19 | Not Handled | ==== Final Comments Deadline ==== | Not Handled |
| 19.14 | S2-2401212 | P-CR | Approval | 23.700-13: KI for WT#1: Security architecture support for Ambient IoT Services and Ambient IoT devices. | Vivo | Rel-19 | Not Handled | ==== Final Comments Deadline ==== | Not Handled |
| 19.14 | S2-2401237 | P-CR | Approval | 23.700-13: FS_AmbientIoT: KI#3: Ambient IoT Services. | InterDigital, Inc. | Rel-19 | Not Handled | ==== Final Comments Deadline ==== | Not Handled |
| 19.14 | S2-2401057 | P-CR | Approval | 23.700-13: New solution: Enable Ambient IoT Management within 5GC to support AIoT services. | Huawei, HiSilicon | Rel-19 | Not Handled | ==== Final Comments Deadline ==== | Not Handled |
| 19.14 | S2-2401058 | P-CR | Approval | 23.700-13: New Solution: AIoT Device Function and Services. | Huawei, HiSilicon | Rel-19 | Not Handled | ==== Final Comments Deadline ==== | Not Handled |
| 19.15 | - | - | - | Core Network Enhanced Support for Artificial Intelligence (AI)/Machine Learning (ML) (FS_AIML_CN) | - | - | Docs:=73 | - | |
| 19.15 | - | - | - | General | - | - | Docs:=9 | - | |
| 19.15 | S2-2400058 | LS In | Action | LS from RAN WG3: Reply to LS on AI/ML Core Network enhancements | RAN WG3 (R3-237745) | Rel-19 | Response drafted in S2-2400287. Noted | Thomas (Nokia) proposes to note this LS Alla (OPPO) supports Nokia's view. | Noted |
| 19.15 | S2-2400287 | LS OUT | Approval | [DRAFT] Reply LS on AI/ML Core Network enhancements | Huawei, HiSilicon | Rel-19 | Response to S2-2400058. Noted | Vivian (vivo) provides comments Alla Goldner (OPPO) provides comments. Dimitris (Lenovo) proposes to NOTE ==== Revisions Deadline ==== Haiyang (Huawei) is OK to NOTE Alla (OPPO) is OK to NOTE. ==== Final Comments Deadline ==== | Noted |
| 19.15 | S2-2400100 | DISCUSSION | Discussion | Beyond 5G AI-Enabled Security and Resilience (BASIL) Framework | Dell Technologies | Rel-19 | Noted | Thomas (Nokia) suggest noting this contribution and asks to which agreed objective in the SID this discussion paper relates and whether this could be a topic for SA3. Belen (Ericsson) agrees with Nokia´s comments. This is a SA3 topic Haiyang (Huawei) agrees with previous comments. This is a SA3 topic Alla (OPPO) agrees with the comments this is not in scope of SA2 R19. ==== Revisions Deadline ==== | Noted |
| 19.15 | S2-2401253 | P-CR | Approval | 23.700-84: FS_AIML_CN TR 23.700-84 Skeleton . | MediaTek Inc. (Rapporteur), vivo (Rapporteur) | Rel-19 | r07 Agreed. Revised to S2-2401826. | Belen (Ericsson) provides comments Alla Goldner (OPPO) cosigns S2-2401253. David (Samsung) provides comments Mehrdad (MediaTek Inc.) provides r01 addressing the comments raised so far Mehrdad (MediaTek Inc.) replies to Ericsson Mehrdad (MediaTek Inc.) replies to Samsung. Mehrdad (MediaTek Inc.) provides r02 and r03 addressing Ericsson comment. Please ignore r02 due to typo. Belen (Ericsson) is okay with r03 Thomas(Nokia) provides r04 Mehrdad (MediaTek Inc.) can not agree with r04 and requests Chair to comment Xiaobo(vivo) support to proceed with r03 based on offline feedback since last two week David (Samsung) comments, provides r05 Mehrdad (MediaTek Inc.) is fine with either r05 or r03 Thomas(Nokia) replies to Mehrdad, still has concerns with r00, r01, r02, r03 and r05. Thomas(Nokia) provides r06, prefers r04 but can live with r06. Has concerns with r00, r01, r02, r03 and r05. Mehrdad (MediaTek Inc.) thanks Thomas/ Nokia and can live with r06 David (Samsung) is OK with r06 Alla (OPPO) is OK with r06 Mehrdad (MediaTek Inc.) provides r07 with minor editorial change versus r06 Alla (OPPO) supports r07. David (Samsung) supports r07 ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 19.15 | S2-2401826 | P-CR | Approval | 23.700-84: FS_AIML_CN TR 23.700-84 Skeleton . | MediaTek Inc. (Rapporteur), vivo (Rapporteur), OPPO, Samsung | Rel-19 | Revision of S2-2401253r07. Approved | Approved | |
| 19.15 | S2-2400563 | P-CR | Approval | 23.700-84: Scope for FS_AIML_CN . | Vivo, MediaTek Inc, OPPO | Rel-19 | r14 Agreed. Revised to S2-2401827. | David (Samsung) provides comments. Haiyang (Huawei) provides r01. Vivian (vivo) provides r02. Xiaobo (vivo) thanks for suggestion and comments and r02 looks good. Thomas (Nokia) provides r03. David (Samsung) provides r04. Belen (ericsson) provides r05 David (Samsung) provides r06 Alla (OPPO) provides r07 Thomas (Nokia) provides r08. Xiaobo (vivo) do some clean-up and provides r09. Alla (OPPO) does some additional clean-ups and provides r10. Thomas(Nokia) provides r11 with additional editorials. David (Samsung) provides r12 and objects to revisions not containing WT2 scope as agreed in the SID. Belen (Ericsson) objects to r12, and any revision that mentions that VFL applies to 5GC/NWDAF and/or AF as the number of options are open, we need to be able to be more specific on what to study Provides r13 as a compromise and a proposal David (Samsung) cannot agree to r13, provides r14 as another compromise attempt. Belen (Ericsson) is okay with r14 Abbas (Futurewei) comments on r14 wording ==== Revisions Deadline ==== Haiyang (Huawei) suggests to go with r14 and changing the second bullet to 'Whether and what 5GC enhancements are needed to enable 5G system to assist in collaborative AI/ML operations for Vertical Federated Learning (VFL) performed between NWDAF and/or AF.' Alla (OPPO) suggests to proceed with r14. Belen(Ericsson) also suggests to approve r14 ==== Final Comments Deadline ==== | Revised |
| 19.15 | S2-2401827 | P-CR | Approval | 23.700-84: Scope for FS_AIML_CN . | Vivo, MediaTek Inc, OPPO. Nokia, Nokia Shanghai-Bell, Ericsson, Samsung, Tencent, Tencent Cloud | Rel-19 | Revision of S2-2400563r14. Approved | Approved | |
| 19.15 | S2-2401255 | P-CR | Approval | 23.700-84: 23.700-84: Architecture Assumptions for FS_AIML_CN . | MediaTek Inc. (Rapporteur), vivo (Rapporteur), OPPO, Samsung, Orange, Futurewei | Rel-19 | r16 + changes Agreed. Revised, merging S2-2400316, to S2-2401828. | Mehrdad (MediaTek Inc.) provides r01, also bringing the Architecture requirements into this thread and revision. Haiyang (Huawei) provides comments. Jianning (XIAOMI) comments on r01. Mehrdad (MediaTek Inc.) provides r02 Belen (Ericsson) objects to all revisions provided so far. Security aspects are SA3 responsibility Mehrdad (MediaTek Inc.) provides r03 addressing Ericsson concern. Belen (Ericsson) thanks Mehrdad, asks a question for clarification Mehrdad (MediaTek Inc.) replies to Ericsson and requests clarification from other parties Dimitris (Lenovo) comments Mehrdad (MediaTek Inc.) replies to Lenovo and request feedback from all parties. David (Samsung) comments, objects to Lenovo's proposal. Zhao (Huawei) suggests to merge S2-2400316 into S2-2401255 as guided by rapporteur, and provides r04. Alla (OPPO) replies to Lenovo and to Mediatek. David (Samsung) provides r05. Mehrdad (MediaTek Inc.) gives further update to Lenovo and OPPO in light of Samsung concern on removal of text versus r03+. Antoine (Orange) provides r06, improving the definition of Signalling Storm and removing the EN. Bahador (NTT DOCOMO) provides comments on the definitions Xiaobo(vivo) support to have the definition of Signalling Storm Belen (Ericsson) provides comments on the definitions Alla (OPPO) provides comments on the definitions Abbas (Futurewei) provides comments on the definitions Thomas(Nokia) provides r07, replies to Abbas Abbas (Futurewei) provides updated VFL/HFL definitions Yuang provides updated VFL/HFL definitions Xiaoyan (CATT) provides r09 Yuang(ZTE) comments r09 Jianning (XIAOMI) comments and provide r09 Jianning (XIAOMI) comments on r10. David (Samsung) provides r12. Alla (OPPO) provides r13. Mehrdad (MediaTek Inc.) has concern on new changes in r10, r11,12,r13. David (Samsung) is OK with Mediatek's proposal Thomas (Nokia) comments on r10. Alla (OPPO) is OK with Mediatek's proposal Mehrdad (MediaTek Inc.) thanks Samsung and OPPO and provides r14 Magnus H (Ericsson) provides r15 Mehrdad (MediaTek Inc.) provides r16 with minor editorial changes over r15 ==== Revisions Deadline ==== Haiyang (Huawei) is OK with r16, hope to cosign Alla (OPPO) is OK with r16. Jianning (XIAOMI) is ok with r16. ==== Final Comments Deadline ==== | Revised |
| 19.15 | S2-2401828 | P-CR | Approval | 23.700-84: 23.700-84: Architecture Assumptions and Requirements for FS_AIML_CN . | MediaTek Inc. (Rapporteur), vivo (Rapporteur), OPPO, Samsung, Orange, Futurewei, Nokia, Nokia Shanghai-Bell, ZTE, CATT, Huawei | Rel-19 | Revision of S2-2401255r16 + changes, merging S2-2400316. Approved | Approved | |
| 19.15 | - | - | - | WT#1.4 (AI/ML based positioning) | - | - | Docs:=2 | - | |
| 19.15 | S2-2400559 | P-CR | Approval | 23.700-84: New key issue for LCS enhancements to support AI/ML based Positioning. | Vivo, MediaTek Inc, ZT, Lenovo? | Rel-19 | Confirm Sources! r22 + changes Agreed. Revised to S2-2401829. | Megha (Intel) provides comments. Tao (Sony) tries to clarify the LMF-sided model to Antonie (Orange) and Feng (Huawei) and provides further comment. Yuang(ZTE) replies and provides further comments. Zhao (Huawei) replies and provides further comments. Antoine (Orange) asks why assume that the ML Model is used by the LMF. Jingran(OPPO) provides comments. Yuang(ZTE) provides comments. Xiaoyan (CATT) provides r01. Dimitris (Lenovo) suggests avoiding solution specific terminology. Provides comments. Jianning (XIAOMI) comments Jianning (XIAOMI) comments. AIhua (CMCC) comments. Juan Zhang (Qualcomm) provides comment. Vivian (vivo) replies to comments and provides r01. Belen (Ericsson) objects to r01 and initial version, provides r02 Vivian (vivo) provides r03 to ask for belen(E) comments, sorry for providing the wrong previous r01. Jianning (XIAOMI) comments on r03. Yuang(ZTE) comments on r03. David (Samsung) comments, provides r04. AIhua (CMCC) provides r05. Vivian (vivo) provides comments to David(Samsung) and r06. Juan Zhang (Qualcomm) provides r06. Yuang(ZTE) response Juan's comment. Zhao (Huawei) provides comments and r07. Vivian (vivo) responses to comments and provides r08. Xiaobo (vivo) do some clean-up and provide r09. David (Samsung) provides r10. Belen (ericsson) cannot accept r06 Belen (Ericsson) objects to r10 and previous revisions, provides r11 Dimitris (Lenovo) comments Thomas(Nokia) provides r12 Xiaoyan (CATT) provides comments and r13 Jianning (XIAOMI) comments on r11 Xiaobo (vivo) provide r14 based on further comments. Jingran (OPPO) supports r14 and ask for co-sign. Yuang(ZTE) comments r14. AIhua (CMCC) provides comments. Belen (ericsson) objects to r14, provides r15. Juan Zhang (Qualcomm) provides comments Zhao (Huawei) provides comments. Thomas(Nokia) provides r16. Yuang(ZTE) accept r16. Vivian (vivo) responses to comments and provides r17. Belen (Ericsson) objects to conclude already that LMF does model training and inference. Provides r17 Zhao (Huawei) reminds Belen (Ericsson) that the revision link is wrong, and provide comments. Xiaobo (vivo) provide r18 to address Belen's comment. Belen (Ericsson thanks Zhao, provides r19 and replies Xiaobo (vivo) thanks Belen for providing r19 and propose to go with r19. Mehrdad (MediaTek Inc.) comments Xiaoyan (CATT) provides r20. Dimitris (Lenovo) provides r21 Mehrdad (MediaTek Inc.) provides r22. Only editorial change to fix the note numbering order of r21. ==== Revisions Deadline ==== Juan Zhang (Qualcomm) proposes to further update r22 to remove the bullet 'How the Model consumer uses the trained model to perform inference and/or derive UE position;' Xiaobo (vivo) ) thank Juan for the comments and ask whether Juan whether she can live with r22 and I will update KI to remove the bullet next meeting. Mehrdad (MediaTek Inc.) is ok with r22 + adding Title: Enhancements to LCS to support Direct AI/ML based Positioning as suggested by Lenovo Juan Zhang (Qualcomm) is OK with Mehrdad (MediaTek Inc.)'s proposal to go with r22 + adding Title: Enhancements to LCS to support Direct AI/ML based Positioning as suggested by Lenovo, but we need to further consider the referred bullet in next meeting. Jianning (XIAOMI) is ok with R22, and happy to co-sign. David (Samsung) would like to co-sign. Xiaobo(vivo) thanks all for the contribution and especially Juan's kindness. Belen (Ericsson) asks to change on top of r22 - Which entity trains the model for Direct AI/ML positioning and how the Model consumer gets the trained AI/ML model; By - Which entity trains the model for Direct AI/ML positioning and if the entity that train the model and the consumer are different, how the Model consumer gets the trained AI/ML model; Antoine (Orange): How can this be incoporated into the TR without a clause heading?? Mehrdad (MediaTek Inc.) clarifies to Orange that the WF was r22 + adding Title: Enhancements to LCS to support Direct AI/ML based Positioning as suggested by Lenovo Mehrdad (MediaTek Inc.) requests session Chair to capture WF as r22 + adding Title of clause: Enhancements to LCS to support Direct AI/ML based Positioning as suggested by Lenovo + Replace: Which entity trains the model for Direct AI/ML positioning and how the Model consumer gets the trained AI/ML model With: Which entity trains the model for Direct AI/ML positioning and if the entity that train the model and the consumer are different, how the Model consumer gets the trained AI/ML model; Megha(Intel) is OK with r22, asks a question on the change proposed to be captured in addition to what exists in r22. ==== Final Comments Deadline ==== | Revised |
| 19.15 | S2-2401829 | P-CR | Approval | 23.700-84: New key issue for LCS enhancements to support AI/ML based Positioning. | Vivo, MediaTek Inc, ZTE, Nokia, Nokia Shanghai Bell, Lenovo, Ericsson, OPPO, Xiaomi, Samsung, Intel,CATT | Rel-19 | Revision of S2-2400559r22 + changes. Approved | Approved | |
| 19.15 | - | - | - | WT#2 (VFL) | - | - | Docs:=7 | - | |
| 19.15 | S2-2400560 | P-CR | Approval | 23.700-84: New key issue for Vertical Federated Learning between 5GC and AF for cross-domain AI/ML coordination. . | Vivo (rapporteur), MediaTek Inc. (rapporteur), China Mobile, KDDI, NTT DoCoMo, Futurewei?, Samsung? Orange, ZTE?, Ericsson? | Rel-19 | Confirm Sources! r36 + changes Agreed. Revised to S2-2401830. | Sohei (KDDI) reply Megha. Megha (Intel) provides comments. Jiahui (China Telecom) comments. Yuang(ZTE) provides comments. Jingran (OPPO) provides comments. Sohei (KDDI) provides comments and provides r08. Vivian (vivo) provides comments and answers the question from Megha Jihoon (ETRI) provides comments. Sohei (KDDI) provides comments and provides r9 Dimitris (Lenovo) comments Vivian (vivo) comments Sohei (KDDI) comments and provide r02 Antoine (Orange) comments on co-existence with HFL. David (Samsung) provides r03. Dimitris (Lenovo) comments to r03 Jihoon (ETRI) provides r04. Sohei (KDDI) agree with r03 Vivian (vivo) provides comments and r05. Haiyang (Huawei) comments and r10 Jingran (OPPO) provides r06 Sohei (KDDI) comments on r05. Bahador (NTT DOCOMO) provides r11 Antoine (Orange) provides r12. David (Samsung) provides r13. David (Samsung) provides r14. Abbas (Futurewei) provides r14 Belen (Ericsson) and not David (Samsung) provides r14 Megha (Intel) provides r15 and comments Thomas (Nokia) provides r16 and comments Thomas(Nokia) asks Belen and Abbas to clarify who is the real source of the uploaded r14 Abbas (Futurewei) replies Thomas (Nokia) and confirms Futurewei is the source of the uploaded r14 Yuang(ZTE) conmments r17 Bahador (NTT DOCOMO) provides r17 Tao (Sony) provides r18. Jiahui (China Telecom) comments on r17 and r18. Jingran (OPPO) comments on the r18. David (Samsung) provides r19. Dimitris (Lenovo) provides r20 - cosigns Belen (Ericsson) objects to any revision that states that ML model sharing applies in VFL. Belen (Ericsson) asks Sony to clarify. Tao (Sony) replies to Belen (Ericsson) with regards to model sharing further clarification. Thomas (Nokia) provides r21. Chi (China Unicom) supports this paper and would like to co-sign it. Yuang(ZTE) comments r23. Vivian(vivo) provides r24 based on r23. Haiyang (Huawei) provides r23. Ulises (InterDigital Inc.) provides r22. Jingran(OPPO)provides r25. Xiaobo (vivo) provides r26 with some clean-up. Tao (Sony) agrees with Jingran (Oppo) on the clarification of model sharing and the corresponding note. David (Samsung) provides r27 Aihua(CMCC) provides r28 for model parameter sharing. Belen (Ericsson) objects to any reference to model sharing as in r28, r27 and more, replies to OPPO and Sony, provides r29 David (Samsung) raises concerns on r29, requests clarifications from Ericsson Jingran (OPPO) is ok for the model sharing part wording updated by Ericsson David (Samsung) provides r30 Thomas(nokia) provides r31 Thomas (Nokia) provides r32 David (Samsung) objects to r31 and r32 Thomas(Nokia) replies to David Belen (Ericsson) replies to Samsung that the WT is a first step and objects to copy and paste in this case. Belen (Ericsson) objects to r30, r31 and any revision that says that VFL can be performed between any entity, that is what 5GC/NWDAF and/or AF means to us Xiaobo (vivo) provide r33 to make compromise and hopefully it is acceptable. Haiyang (Huawei) suggests to use 'NWDAF and/or AF' instead of '5GC/NWDAF and/or AF' in the sentence. David (Samsung) thanks Xiaobo/vivo for the compromise, is OK with r33. Belen (Ericsson) is okay with Huawei proposal Thomas(Nokia) raises concerns against r29 Vivian (vivo) keeps open but provides r33 based on Huawei's suggestion for further discussion. Haiyang (Huawei) indicates that it is r34 that Vivian (vivo) uploaded. Vivian (vivo) announces she provided r34 in last email not r33, sorry for the mistake. David (Samsung) thinks Vivian (vivo) provided r34 (not r33), is OK with r34. Mehrdad (MediaTek Inc.) is OK with r34. Minor editorial, Note W4 should change to NOTE 4 Haiyang (Huawei) provides r35. Thomas (Nokia) provides r36. ==== Revisions Deadline ==== Tao (Sony) provides r37. Vivian (vivo) can accept r36. Although r37 is also OK for us, but since it is a revision after deadline and the modification is not that fatal, so we suggest to go with r36. Tao (Sony) is fine with r36. Mehrdad (MediaTek Inc.) is OK with r36 Yuang(ZTE) agree with r36 Antoine (Orange) comments that '?' in Source need the be removed and the styles of the bullet list need to be fixed. Belen (Ericsson) objects to r36. It can accept r36 if '5GC/NWDAF and/or AF' is removed or replaced by 'NWDAF and/or AF' Belen (Ericsson) replies to Nokia, I don't think we need to copy and paste the text in the SID is subject of misunderstandings. Xiaobo (vivo) thank Belen for the comments and ask whether Belen can live with r36 as it is common understanding by group here that '5GC/NWDAF and/or AF' should be replaced by 'NWDAF and/or AF'. Rapporteur will bring a miscellaneous paper to update them next meeting. Belen (Ericsson) can live with Xiaobo proposal to fix it next meeting, with the understanding that there are no objections from any company. Abbas (Futurewei) is OK with r36 Megha(Intel) is OK with r36 Thomas(Nokia) suggest agreeing r36 + Replace 'involving 5GC/NWDAF and/or AF' by 'involving NWDAF and/or AF' ==== Final Comments Deadline ==== | Revised |
| 19.15 | S2-2401830 | P-CR | Approval | 23.700-84: New key issue for Vertical Federated Learning between 5GC and AF for cross-domain AI/ML coordination. . | Vivo (rapporteur), MediaTek Inc. (rapporteur), China Mobile, KDDI, NTT DoCoMo, ETRI, Futurewei, Samsung, Orange, ZTE, Ericsson OPPO, Nokia, Nokia Shanghai-Bell, Sony, Lenovo, InterDigital Inc., Huawei,China Unicom,CATT | Rel-19 | Revision of S2-2400560r36 + changes. Approved | Approved | |
| 19.15 | S2-2400285 | P-CR | Approval | 23.700-84: New use case for WT2: VFL between AFs with assistance of 5GC. | Huawei, HiSilicon | Rel-19 | Noted | Bahador (NTT DOCOMO) shares concerns and requests further clarification Haiyang (Huawei) responds to Bahador (NTT DOCOMO) Bahador (NTT DOCOMO) responds to Haiyang (Huawei) Yuang(ZTE) comments to Haiyang (Huawei) Haiyang (Huawei) provides r01 David (Samsung) shares concerns about this use case. Belen (ericsson) asks for some more concrete assistance info Jiahui (China Telecom) provides comment. Haiyang (Huawei) provides r02 Thomas (Nokia) comments that use case does not fit well to key issue description Haiyang (Huawei) provides reply to Thomas (Nokia) Bahador (NTT DOCOMO) suggest removing the Figure Haiyang (Huawei) provides r03 to remove the figure Thomas(Nokia) prefers that we start with a use case about coordination between AF and NWDAF, considering limited TUs for this key issues ==== Revisions Deadline ==== Thomas(Nokia) suggest to Note this contribution Haiyang (Huawei) thinks it is improper to object a valid use case at the beginning. Belen(Ericsson) thinks that the use case is not part of the SID. Thomas(Nokia) replies that a discussion of use cases has been requested in SID and key issue, and this means not every conceivable use case needs to be agreed. We have not enough TUs to study any conceivable use case. If desired, we could do a show of hand at the next meeting to determine use cases with most support ==== Final Comments Deadline ==== | Noted |
| 19.15 | S2-2400804 | P-CR | Approval | 23.700-84: New Use Case for WT#2: VFL between NWDAFs. | Huawei, HiSilicon | Rel-19 | Noted | Vivian (vivo) provides comments David (Samsung) comments, asks question for clarification Haiyang (Huawei) provides feedback. Belen (Ericsson) proposes to NOTE this paper. Thomas (Nokia) provides feedback. Jingran (OPPO) suggest we are not consider roaming in this release. Dimitris (Lenovo) comments Haiyang (Huawei) provides r01. Thomas(Nokia) raises concerns. Haiyang (Huawei) provides response to Thomas(Nokia) Jingran(OPPO) raise some comments Haiyang (Huawei) provides response to Jingran(OPPO) David (Samsung) provides r02 but still unsure about the use case Jingran(OPPO) raise concerns Belen (Ericsson) raise concerns ==== Revisions Deadline ==== Haiyang (Huawei) suggests to go with r02 Thomas (Nokia) suggests to note ==== Final Comments Deadline ==== | Noted |
| 19.15 | S2-2400312 | P-CR | Approval | 23.700-84: WT2: New Use Case for Vertical Federated Learning. | Samsung | Rel-19 | CC#4: Postponed | Jingran (OPPO) provides comments. Antoine (Orange) comments. Vivian (vivo) provides comments. Bahador (NTT DOCOMO) provides comments Yuang (ZTE) provides comments David (Samsung) replies to comments, provides r01. Sohei (KDDI) comments on r01 David (Samsung) replies to KDDI Belen (Ericsson) asks questions for clarification. David (Samsung) replies to Ericsson. Thomas (Nokia) comments that use case is still unclear. Sohei (KDDI) replies to David and comments on r02 Haiyang (Huawei) comments and provides r02. Jingran(OPPO) comments that this use case still need update. Bahador (NTT DOCOMO) provides further comments on top of the OPPO's comment Belen (Ericsson) replies to Samsung Dimitris (Lenovo) comments Haiyang (Huawei) clarifies to Sohei (KDDI). David (Samsung) replies to all comments, provides r03 David (Samsung) replies to Lenovo Abbas (Futurewei) comments and supports this UC David (Samsung) thanks Futurewei, provides r04 Abbas (Futurewei) co-signs r04 Thomas(Nokia) reminds that his previous questions were not addressed and questions if slice load analytics are a good example for VFL. Sohei (KDDI) replies to Haiyang and David and coments. David (Samsung) clarifies to Nokia that answers were indeed provided; provides further replies to Nokia and KDDI Belen (Ericsson) thinks that this use case covers some more complex scenarios, and as such it should not be prioritized in this release. Thomas(Nokia) agrees that the benefits of this use case compared to the existing HFL are questionable, in particular considering slice load analytics. Suggest postponing the issue to see if we can agree any use case for VFL within the 5GC with more compelling justification. David (Samsung) replies to Nokia and Ericsson, believes the technical observations for the suitability of this UC are perfectly valid and compliant with the SID, and rejects the argument that this UC expands the scope as most of the required work to enable VFL in the 5GC is common across use cases Haiyang (Huawei) provides r05 based on Sohei's suggestion. David (Samsung) is OK with r05, hopes KDDI can live with r05. Thomas(Nokia) finds use case to use VFL for different geographical areas in 5GC not convincing. David (Samsung) thinks Thomas is not really commenting on the scope of this use case, the motivation is not different geographical areas but rather aggregating models for same samples and different features. This can be the case for many analytics Thomas replies to David that wording is still very confusing and suggest postponing the contribution ==== Revisions Deadline ==== Sohei (KDDI) is OK with r05 but considers that r05 is possible but quite rare. Thomas(Nokia) request to postpone this contribution. David (Samsung) thanks KDDI for their acceptance of r05, offers an EN on top of r05 as a compromise for companies who aren't satisfied with the UC wording. David (Samsung) requests this paper to be opened at CC3/CC4. ==== Final Comments Deadline ==== | Postponed |
| 19.15 | S2-2400379 | P-CR | Approval | 23.700-84: New use case for KI#1 Vertical Federated Learning (VFL). | Futurewei | Rel-19 | Noted | Bahador (NTT DOCOMO) requests further clarification Belen (Ericsson) proposes to NOTE this paper. Abbas (Futurewei) replies to Bahador (NTT DOCOMO) Abbas (Futurewei) replies to Belen (Ericsson) Abbas (Futurewei) provides r01 to address Bahador (NTT DOCOMO) comment and Belen (Ericsson) concern Bahador (NTT DOCOMO) responds to Abbas (Futurewei) Belen (Ericsson) asks questions for clarification on r01 Abbas (Futurewei) provides r02 Abbas (Futurewei) replies to Thomas (Nokia) that VFL between NWDAF/5GC is indeed in the scope of the approved SID Thomas(Nokia) shares concern that use case is quite exotic ==== Revisions Deadline ==== Thomas (Nokia) requests to Note this contribution Reminds chair that there is a similar request of Belen(Ericsson) Abbas (Futurewei) requests to capture this UC in TR and evaluate later as this UC is technically feasible for VFL among NWDAFs ==== Final Comments Deadline ==== | Noted |
| 19.15 | S2-2401068 | P-CR | Approval | 23.700-84: Use case for user experience evaluation based on VFL. | China Mobile | Rel-19 | CC#4: Postponed. S2-2401068r14 should be taken as the baseline for further discussions in SA WG2#161. | Megha (Intel) provides comments. Aihua (CMCC) provides r01 as merged version based on rapportuer suggestion during the TDoc ording. Sohei (KDDI) co-signs r01. Jingran (OPPO) comments. Aihua(CMCC) replies to Jingran (OPPO) comment. David (Samsung) provides comments. Belen (Ericsson) provides r02 David (Samsung) cannot agree to r02. Bahador (NTT DOCOMO) provides a comment Sohei (KDDI) replies to David and Bahador Jihoon (ETRI) provides comments. Aihua(CMCC) provides r03. Jingran(OPPO) comments on the r03. Dimitris (Lenovo) provides r04 and cosigns Bahador (NTT DOCOMO) supports r04 Vivian (vivo) provides r05 and supports this paper Belen (Ericsson) asks a question to Jinhoon and Aihua Belen (Ericsson) provide comments to r05. Sudeep (Apple) provides comments on r05. Jingran (OPPO) provides r07. Jihoon (ETRI) provides comments and replies to Belen (Ericsson). Thomas (Nokia) provides r06 Aihua(CMCC) provides r08. David (Samsung) provides comments, asks question for clarification Thomas(Nokia) comments. Haiyang (Huawei) provides r11 to merge r09 and r10 Haiyang (Huawei) provides r10. Sohei (KDDI) provides r09 and support this paper Jingran (OPPO) is ok with r11 David (Samsung) provides further comments to Sohei Dimitris (Lenovo) comments David (Samsung) replies to Lenovo David (Samsung) provides r12 Belen (Ericsson) provides r13, given that the questions I raised after r05 were not responded. I cannot accept previous versions David (Samsung) provides r14 with an EN on NWDAF labels ==== Revisions Deadline ==== Dimitris (Lenovo) is ok with r14 with some changes Aihua(CMCC) replies to David(Samsung) and Belen (Ericsson), but can live with r14. Sohei (KDDI) replies to David(Samsung), and is OK with r14. Belen (Ericsson) replies to Samsung. Jingran (OPPO) provides comments and can live with R14. Vivian (vivo) can live with R14. David (Samsung) provides clarifications on the EN in r14. David (Samsung) cannot agree to this UC yet, requests to keep this UC open for CC3/CC4. We have concerns regarding how VFL UCs are being treated in this meeting without knowledge of work plan for next meeting. To decide our disposition for this UC we need to understand what can and can't be discussed in next meeting. Thomas(Nokia) asks David to clarify his position after the CC#3 discussion, where rapporteurs indicated that they want to continue use case discussions at the next meeting. Reminds that he requested that 'Nokia, Nokia Shanghai-Bell' is added as supporting company ==== Final Comments Deadline ==== | Postponed |
| 19.15 | - | - | - | WT#3.1 (NWDAF-assisted policy control and QoS enhancement) | - | - | Docs:=7 | - | |
| 19.15 | S2-2400561 | P-CR | Approval | 23.700-84: New KI for NWDAF-assisted policy control and QoS enhancement. | Vivo (rapporteur), MediaTek Inc. (rapporteur), China Mobile, OPPO?, Ericsson? Samsung? Orange? NTT DoCoMo | Rel-19 | Confirm Sources! r21 Agreed. Revised to S2-2401831. | Alla Goldner (OPPO) provides rev2. Bahador (NTT DOCOMO) provides r03. Tingyu (Samsung) provides r04. Alla (OPPO) comments on r04. Vivian (vivo) provides r05. Alla (OPPO) supports r05. Tingyu (Samsung) confirms co-sourcing. Magnus H (Ericsson) provides comments Zhao (Huawei) can accept r06 and object all other revisions. Jihoon (ETRI) provides r08. Lei(Tencent) thanks to the discussions and add one change to be consistent and provide r07. Also ask to co-sign the pCR. Thomas(Nokia) provides r06, objects against all previoius revisions. Lei(Tencent) is also ok with r08 ask for clarification about objection to r07 and r08. Tingyu (Samsung) can accept r06 but objects all later revisions. Magnus H (Ericsson) provides r09 based on r06, objects to all revisions prior to r09 Alla (OPPO) provides r10. Tingyu (Samsung) provides r11. Alla (OPPO) supports r11. Thomas(Nokia) provides r12. Xiaobo (vivo) do some clean-up and provides r13. Lei(Tencent) appreciates Xiaobo (vivo)'s great effort and also provide the revision and is ok with r13. Also would like to co-sign the pCR. Zhao (Huawei) provides r14. Lei(Tencent) prefers rapporteur provided version r13 instead of r14. Alla (OPPO) provides r15. Tingyu (Samsung) supports r15. Zhao (Huawei) provides comments and only accepts r14, objects to r13 and r15. Lei(Tencent) share the same view with Xiaobo(vivo)/rapporteur, Alla(OPPO) and Tingyu(Samsung). Also fine with r15 (in addition to r13) and object r14. Tingyu (Samsung) provides r16 on top of r14 with adding 'AF information' to another bullet point. Alla provides r17 on top of r15 by incorporating r16 key modifications. Tingyu (Samsung) is OK with r17. Xiaobo (vivo) provide some examples regarding assistance information from AF in TS 23.501 and request Zhao(Huawei) to re-consider his objection to avoid blocking the progress. Thomas(Nokia) provides r18. Alla (OPPO) is OK with r18. Zhao (Huawei) provides r19 on top of r17, and r20 without NOTE2 on top of r19. Xiaobo (vivo) provide further clarification regarding assistance information from AF to Zhao(Huawei). Lei(Tencent) objects r19 and r20. Still shares the same view with Xiaobo(vivo)/rapporteur, Alla(OPPO) and Tingyu(Samsung). Propose to focus on r18 from Thomas(Nokia) technically. Thomas(Nokia) replies to Tei Zhao (Huawei) only accepts r19 and r20, objects to all revisions that includes the collection of assistance information from AF. Tingyu (Samsung) provides r21 on top of r20. ==== Revisions Deadline ==== Zhao (Huawei) is ok with r21. Alla (OPPO) is ok with r21. Lei(Tencent) can live with r20. Lei(Tencent) can live with r21,not r20. Sincerely sorry for the typo, Jihoon (ETRI) is also ok with r21 and would like to co-sign this paper. Magnus H (Ericsson) are OK with r21 but want to change the following in first paragraph: from: '...making PCC decisions...', To: '...making policy decisions...' Antoine (Orange) agrees with Magnus but can also live with r21. ==== Final Comments Deadline ==== | Revised |
| 19.15 | S2-2401831 | P-CR | Approval | 23.700-84: New KI for NWDAF-assisted policy control and QoS enhancement. | Vivo (rapporteur), MediaTek Inc. (rapporteur), China Mobile, OPPO, Ericsson Samsung, Orange, NTT DoCoMo, Nokia, Nokia Shanghai-Bell, ETRI,CATT | Rel-19 | Revision of S2-2400561r21. Approved | Approved | |
| 19.15 | S2-2400615 | P-CR | Approval | 23.700-84: Use case for NWDAF-assisted policy control and QoS. | Huawei, HiSilicon | Rel-19 | r11 + changes Agreed. Revised to S2-2401832. | Alla Goldner (OPPO) provides comments. Zhao (Huawei) replies to Alla(OPPO) and provides r01. Alla (OPPO) provides comments on r01. Tingyu (Samsung) asks for clarification. Zhao (Huawei) provides replies and r02. Magnus H (Ericsson) provides r03 Zhao (Huawei) provides replies and r05. Lei(Tencent) provides comments on r04 and think it is still more like a solution instead of a use case. Thomas (Nokia) provides r04 Lei(Tencent) provides comments on r05 and still have concerns on the use case. Zhao (Huawei) replies to Lei (Tencent) and provides r06. Dimitris (Lenovo) comments Tingyu (Samsung) provides r07. Thomas(Nokia) raises concerns. Zhao (Huawei) provides response and r08. Alla OPPO) raises concerns for r08. Tingyu (Samsung) provides comments. Dimitris (Lenovo) provides additional comments Zhao (Huawei) provides response and r09. Thomas(Nokia) raises further concerns. Zhao (Huawei) provides response. Lei(Tencent) also have further concerns. Tingyu (Samsung) provides r10. Zhao (Huawei) provides response and r11. Alla (OPPO) provides response to r11. ==== Revisions Deadline ==== Tingyu (Samsung) replies. Alla (OPPO) replies. Lei(Tencent) comments and express concerns Dimitris (Lenovo) ok to proceed with r11 Zhao (Huawei) provides comments. Lei(Tencent) is fine to NOTE the pCR. Zhao (Huawei) provides response and asks for further clarification why this use case is associated with signalling storm. Xiaobo (vivo) thanks all for the contribution and we do need progress for use case this meeting and I strongly encourage companies to bring new reversion as we still have time to compromise. Zhao (Huawei) suggests to go with r11 with the removal of 'Those iterations will increase the workload the 5GS significantly and lower the service quality.' to avoid confusion with signalling storm scenario. Tingyu (Samsung) is ok with r11, but prefer to keep this. Zhao (Huawei) provides r12 that removes the sentence 'Those iterations will increase the workload the 5GS significantly and lower the service quality.' on top of r11. Tingyu (Samsung) can live with r12 based on the understanding that we will revisit the UC during Athens meeting. ==== Final Comments Deadline ==== | Revised |
| 19.15 | S2-2401832 | P-CR | Approval | 23.700-84: Use case for NWDAF-assisted policy control and QoS. | Huawei, HiSilicon | Rel-19 | Revision of S2-2400615r11 + changes. Approved | Approved | |
| 19.15 | S2-2401049 | P-CR | Approval | 23.700-84: New use case for WT#3.1: NWDAF-assisted handover strategy optimization for specific services. | Tencent, Tencent Cloud | Rel-19 | CC#4: Postponed | Lei (Tencent) provides comments to Antoine (Orange) and provide r02. Antoine (Orange) does not think this is a relevant UC for NWDAF. Tao (Sony) provides comments on the HO use case. Lei(Tencent) provide comments to Tao (Sony) for clarification. Tingyu (Samsung) provides comments. Bahador (NTT DOCOMO) provide comments Magnus H (Ericsson) has same view as Tingyu (Samsung) and Antoine (Orange) Lei (Tencent) provides comments and r03 to reflect the benefits, cost and complexity consdieration as Bahador suggested. Thomas(Nokia) also questions whether this proposed UC is really in scope of WT#3.1. Zhao (Huawei) provides comments, has concerns on this UC. Lei (Tencent) provides response and comments and also provide r04. Magnus H (Ericsson) has similar concerns as Zhao, Thomas and Tingyu Lei (Tencent) provides comments and ask if Magnus see the lastest e-mail with further clarification and lastest revision. Seems not so... Also would like to question whether all use case should be reviewed with common criteria on cost and complexity assessment. ==== Revisions Deadline ==== Zhao (Huawei) is fine to NOTE this pCR. Lei (Tencent) want to check if still concerns (as not sure if some e-mails are read/received), if so fine to Note the pCR. Xiaobo (vivo) thanks all for the contribution and we do need progress for use case this meeting and I strongly encourage companies to bring new reversion as we still have time to compromise. Lei(Tencent) replies and propose to go with 'r04+ removing the last two paragraphs + removing the last sentence of first paragraph' Tingyu (Samsung) replies to Lei(Tencent). Lei(Tencent) replies to Tingyu (Samsung). Tingyu (Samsung) requires an EN: 'Editor's Note: more clarification and justification on the relevance between the UC and policy control are required'. Lei(Tencent) agree with Tingyu (Samsung) request, fine to go with 'r04+ removing the last two paragraphs + removing the last sentence of first paragraph + Editor's Note: more clarification and justification on the relevance between the UC and policy control are required' Lei(Tencent) uploaded 'r04+ removing the last two paragraphs + removing the last sentence of first paragraph + Editor's Note: more clarification and justification on the relevance between the UC and policy control are required' => r05 in the DRAFT folder. Thomas(Nokia) prefers to postpone this use case. Lei(Tencent) hope to discuss this in CC#4 ==== Final Comments Deadline ==== | Postponed |
| 19.15 | S2-2401078 | P-CR | Approval | 23.700-84: New Use Case on Enhancements to QoS Determination with NWDAF Assistance . | Samsung | Rel-19 | r03 Agreed. Revised to S2-2401833. | Magnus (Ericsson) provides comments Tingyu (Samsung) asks Magnus (Ericsson) for providing comments. Lei(Tencent) provides comments and think an EN is needed on relationship with application for QoS determination Zhao (Huawei) asks for clarification. Tingyu (Samsung) provides r01 and replies. Magnus H (Ericsson) provides comments Tingyu (Samsung) provides r02 and replies to Magnus H (Ericsson). Lei (Tencent) is not ok with r02 with EN added as commented already. Lei (Tencent) is not ok with r02 withOUT EN added as commented already. Sorry that I have to correct this. Tingyu (Samsung) asks Lei (Tencent) for providing clear technical justification of the required EN, pointing out what issues should be solved by the EN, and why the current statement cannot address Tencent's concerns without adding the EN. Lei (Tencent) replies and is happy to see another revision without the EN but with some clarifcations Tingyu suggested. Tingyu (Samsung) provides r03 and replies to Lei (Tencent). Lei (Tencent) thanks for the updates provided in r03. Tingyu (Samsung) thanks Lei (Tencent) for the support. Xiaobo (vivo) thanks Lei(Tencent) and Tingyu(Samsung) for the contribution. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 19.15 | S2-2401833 | P-CR | Approval | 23.700-84: New Use Case on Enhancements to QoS Determination with NWDAF Assistance . | Samsung | Rel-19 | Revision of S2-2401078r03. Approved | Approved | |
| 19.15 | - | - | - | WT#3.2 (network abnormal behaviours) | - | - | Docs:=5 | - | |
| 19.15 | S2-2400562 | P-CR | Approval | 23.700-84: New key issue for NWDAF enhancements to support network abnormal behaviours (i.e. Signalling storm) mitigation . | Vivo (rapporteur), MediaTek Inc. (rapporteur), China Mobile, KPN, ZTE, ETRI, Tencent, Tencent Cloud | Rel-19 | r21 + changes Agreed. Revised, merging S2-2400132, to S2-2401834. | Sohei (KDDI) asks what the root cause means. Sohei (KDDI) Replies to Peretz Jiahui (China Telecom) provides comment. Yuang(ZTE) reponses to the comment. Huli (vivo) provides r02 according to the received comments. Alla (OPPO) provides r03 according to the received comments. Dimitris (Lenovo) provides r04 Alla (OPPO) comments on r04. Zhang Fu (Huawei) provide comments Alla (OPPO) provide comments Juan Zhang (Qualcomm) can not agree r05. Dimitris (Lenovo) comments Alla (OPPO) provides r15 Li Hu (vivo) provides r16 Thomas (Nokia) has concerns with r16 Jiahui (China Telecom) replys to Thomas (Nokia) and comments. Li Hu (vivo) provides r17. Xiaobo (vivo) provides r18 with some clean-up. Zhang Fu (Huawei) object r18 Nassima (KPN) supports r18, can live with removing the examples Li Hu (vivo) provides r19 Thomas (Nokia) provides r20 Alla (OPPO) provides r21 Xiaobo (vivo) propose go with r20 (preferred)or r19 to make progress. Zhang Fu is OK with r20 and co-sign ==== Revisions Deadline ==== Lei (Tencnet) is ok with r20 Dimitris (Lenovo) is ok with r20 and cosign Alla (OPPO) is ok with r21, not OK to proceed with r20. Li Hu (vivo) provide clarification to Alla (OPPO) Alla (OPPO) answers Li Hu (vivo) Magnus H (Ericsson) prefers r21 are ok with r20, want to change bullet 2 from: '...assist detection and prediction...' to: '...assist detection and/or prediction...' Bahador (NTT DOCOMO) prefers r20 and suggests (if agreeable) adding 'to prevent/mitigate signalling storm' at the end of third bullet to address OPPO's concern. OPPO answers and proposes to move forward with r21. Bahador (NTT DOCOMO) proposes to limit the 'prevention/mitigation' actions in r21 to the scope of the SID Zhang Fu (Huawei) support DOCOMO's suggestion, we can go with r21 with the following changes Change 'Whether and how signalling storm can be prevented and mitigated.' to 'Whether and how signalling storm can be prevented or mitigated based on the inputs provided by NWDAF.' Alla (OPPO) answers to Bahador (NTT Docomo) ==== Final Comments Deadline ==== | Revised |
| 19.15 | S2-2401834 | P-CR | Approval | 23.700-84: New key issue for NWDAF enhancements to support network abnormal behaviours (i.e. Signalling storm) mitigation . | Vivo (rapporteur), MediaTek Inc. (rapporteur), China Mobile, KPN, ZTE, ETRI, Tencent, Tencent Cloud, Nokia, Nokia Shanghai-Bell,China Telecom, OPPO, Verizon, Huawei, HiSilicon, Lenovo | Rel-19 | Revision of S2-2400562r21 + changes, merging S2-2400132. Approved | Approved | |
| 19.15 | S2-2400912 | P-CR | Approval | 23.700-84: New UC and KI for WT3.2: NWDAF assisted in prevention and mitigation of signalling storm . | China Telecom | Rel-19 | r09 Agreed. Revised to S2-2401835, merging S2-2401185 | Jiahui (China Telecom) replys and provides r01. Antoine (Orange): What is described is not a sigaling storm. Yuang(ZTE) comments Jiahui (China Telecom) replies to Sohei (KDDI) and Yuang (ZTE) Sohei (KDDI) replies to Jiahui and provide r04 AIhua (CMCC) provides comments. Li Hu (vivo) provide r05 to address Juan (Qualcomm)'s concern. Juan Zhang (Qualcomm) is OK with r05. Lei(Tencent) responds to Juan Zhang (Qualcomm) and is ok to consider S2-2401185 as merged into this one. Provide r06 to co-sign the pCR. Thomas(Nokia) requests further improvements. Li Hu (vivo) is OK with r07, and please add vivo as cosigner. Jiahui (China Telecom) provides r07. Alla (OPPO) comments on the use case. Alla (OPPO) provides r08, adds OPPO and vivo as a cosigners. Zhang (Huawei) provides r09 and confuse on the NOTE added in r08 ==== Revisions Deadline ==== Alla (OPPO) supports r09. Juan Zhang (Qualcomm) is OK with r09. Thomas(Nokia) is OK with r09 but has request for PCR implementation by rapporteurs as this PCR(and also some others) are not fully aligned with skeleton. ==== Final Comments Deadline ==== | Revised |
| 19.15 | S2-2401835 | P-CR | Approval | 23.700-84: New UC and KI for WT3.2: NWDAF assisted in prevention and mitigation of signalling storm . | China Telecom, Tencent, Tencent Cloud, OPPO, vivo | Rel-19 | Revision of S2-2400912r09, merging S2-2401185. Approved | Approved | |
| 19.15 | S2-2401185 | P-CR | Approval | 23.700-84: New use case for WT#3.2: NWDAF enhancements to mitigate abnormal behaviours in the 5GS. | Tencent, Tencent Cloud | Rel-19 | Revision of S2-2401055. Merged into S2-2401835 | Zhang Fu(Huawei) Jungshin (Samsung) provides comments Lei (Tencent) replies to Juan Zhang (Qualcomm) and is also fine to mark this as merged to S2-2400912. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 19.15 | - | - | - | Documents exceeding TU budget/quota | - | - | Docs:=43 | - | |
| 19.15 | S2-2401254 | P-CR | Approval | 23.700-84: 23.700-84: Architecture Requirements for FS_AIML_CN . | MediaTek Inc. (Rapporteur), vivo (Rapporteur), OPPO, Samsung, Orange | Rel-19 | Not Handled | Xiaoyan (CATT) provides comments. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Not Handled |
| 19.15 | S2-2400146 | P-CR | Approval | 23.700-84: Architecture requirement and assumption. | ZTE | Rel-19 | Not Handled | ==== Final Comments Deadline ==== | Not Handled |
| 19.15 | S2-2400316 | P-CR | Approval | 23.700-84: Terminology alignment for FS_AIML_CN. | Huawei, HiSilicon | Rel-19 | Merged into S2-2401828 | Peretz (Veizon) clarifies that the network may be congested and might also be under attack. Changes are provided in r01. Zhao (Huawei) replies to Peretz (Veizon) and provides r02. Belen (Ericsson) provides r03. Bahador (NTT DOCOMO) provides r04 Mehrdad (MediaTek Inc.) clarifies that this thread is related to a PCR exceeding TU budget and not to be treated and kindly requests all to avoid making threads for such items Belen (Ericsson) can accept r04 Zhao (Huawei) provides replies, suggests to merge this pCR into S2-2401255 as guided by rapporteur and discuss it in S2-2401255 thread. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 19.15 | S2-2401238 | P-CR | Approval | 23.700-84: 23.700-84: Architectural Assumptions. | Nokia, Nokia Shanghai-Bell | Rel-19 | Not Handled | ==== Final Comments Deadline ==== | Not Handled |
| 19.15 | S2-2400148 | P-CR | Approval | 23.700-84: Key issue on enhancement of LMF direct AI/ML positioning. | ZTE | Rel-19 | Not Handled | ==== Final Comments Deadline ==== | Not Handled |
| 19.15 | S2-2400149 | P-CR | Approval | 23.700-84: Key issue on enhancement of UE direct or assisted AI/ML positioning. | ZTE | Rel-19 | Not Handled | Antoine (Orange) asks why does the LMF send location assistance parameters to UE in case 1. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Not Handled |
| 19.15 | S2-2400150 | P-CR | Approval | 23.700-84: Key issue on enhancement of NG-RAN assisted positioning. | ZTE | Rel-19 | Not Handled | ==== Final Comments Deadline ==== | Not Handled |
| 19.15 | S2-2400154 | P-CR | Approval | 23.700-84: 23.700-84: New KI: 5GS supports AI/ML based positioning with the UE-side model. . | OPPO | Rel-19 | Not Handled | ==== Final Comments Deadline ==== | Not Handled |
| 19.15 | S2-2400378 | P-CR | Approval | 23.700-84: WT1.4: New Key Issue on 5GC Support for AI/ML-based Positioning. | Samsung | Rel-19 | Not Handled | ==== Final Comments Deadline ==== | Not Handled |
| 19.15 | S2-2400744 | P-CR | Approval | 23.700-84: 23.700-84 New KI for WT1.4: Enhancement to support AI/ML based positioning. | Qualcomm Incorporated | Rel-19 | Not Handled | ==== Final Comments Deadline ==== | Not Handled |
| 19.15 | S2-2400861 | P-CR | Approval | 23.700-84: Key issue for WT#1.4 LCS enhancements to support AI/ML based Positioning. | CATT | Rel-19 | Not Handled | ==== Final Comments Deadline ==== | Not Handled |
| 19.15 | S2-2400913 | P-CR | Approval | 23.700-84: New KI for WT1.4: Support of LMF direct AI/ML based positioning . | China Telecom | Rel-19 | Not Handled | ==== Final Comments Deadline ==== | Not Handled |
| 19.15 | S2-2400918 | P-CR | Approval | 23.700-84: New KI for WT1.4: Enhacements to LCS to support AI/ML based positioning. | Lenovo | Rel-19 | Not Handled | ==== Final Comments Deadline ==== | Not Handled |
| 19.15 | S2-2400955 | P-CR | Approval | 23.700-84: New KI for WT#1.4: LCS enhancements to support AI/ML based Positioning. | Xiaomi | Rel-19 | Not Handled | ==== Final Comments Deadline ==== | Not Handled |
| 19.15 | S2-2401065 | P-CR | Approval | 23.700-84: New KI on Enhancement of LCS to support AI/ML-based positioning (WT1.4). | CMCC | Rel-19 | Not Handled | ==== Final Comments Deadline ==== | Not Handled |
| 19.15 | S2-2401297 | P-CR | Approval | 23.700-84: New key issue for WT 1.4. | Nokia, Nokia Shanghai-Bell | Rel-19 | Revision of S2-2401279. Not Handled | ==== Final Comments Deadline ==== | Not Handled |
| 19.15 | S2-2400130 | P-CR | Approval | 23.700-84: KI#1: Vertical Federated Learning. | NTT DOCOMO | Rel-19 | Not Handled | Ulises Olvera (InterDigital Inc.) provides comments/proposed text ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Not Handled |
| 19.15 | S2-2400147 | P-CR | Approval | 23.700-84: Key issue on enhancement of Federated Learning. | ZTE | Rel-19 | Not Handled | ==== Final Comments Deadline ==== | Not Handled |
| 19.15 | S2-2400155 | P-CR | Approval | 23.700-84: 23.700-84: New KI: 5GS assists in collaborative AI/ML operation involving 5GC and/or AF for Vertical Federated Learning. . | OPPO | Rel-19 | Not Handled | ==== Final Comments Deadline ==== | Not Handled |
| 19.15 | S2-2400311 | P-CR | Approval | 23.700-84: WT2: New Key Issue on 5GC Support for Vertical Federated Learning. | Samsung | Rel-19 | Not Handled | ==== Final Comments Deadline ==== | Not Handled |
| 19.15 | S2-2400418 | P-CR | Approval | 23.700-84: New KI for WT#2: Vertical Federated Learning . | Futurewei | Rel-19 | Not Handled | ==== Final Comments Deadline ==== | Not Handled |
| 19.15 | S2-2400862 | P-CR | Approval | 23.700-84: Key issue for WT#2 5GC enhancements for Vertical Federated Learning. | CATT | Rel-19 | Not Handled | ==== Final Comments Deadline ==== | Not Handled |
| 19.15 | S2-2400911 | P-CR | Approval | 23.700-84: New KI for WT2: 5GS support of collaborative AI/ML operation for VFL . | China Telecom | Rel-19 | Not Handled | ==== Final Comments Deadline ==== | Not Handled |
| 19.15 | S2-2400920 | P-CR | Approval | 23.700-84: New KI for WT2: Supporting Vertical Federated Learning in 5GS. | Lenovo | Rel-19 | Not Handled | ==== Final Comments Deadline ==== | Not Handled |
| 19.15 | S2-2401067 | P-CR | Approval | 23.700-84: KI for VFL support between NWDAF and AF (WT#2). | China Mobile | Rel-19 | Not Handled | ==== Final Comments Deadline ==== | Not Handled |
| 19.15 | S2-2401299 | P-CR | Approval | 23.700-84: 23.700-84: Key Issue for Work Task 2. | Nokia, Nokia Shanghai-Bell | Rel-19 | Not Handled | ==== Final Comments Deadline ==== | Not Handled |
| 19.15 | S2-2400286 | P-CR | Approval | 23.700-84: New use case for WT2: VFL between AF and NWDAF . | Huawei, HiSilicon | Rel-19 | Not Handled | ==== Final Comments Deadline ==== | Not Handled |
| 19.15 | S2-2400564 | P-CR | Approval | 23.700-84: New use case for Vertical Federated Leaning. | Vivo | Rel-19 | Not Handled | ==== Final Comments Deadline ==== | Not Handled |
| 19.15 | S2-2400669 | P-CR | Approval | 23.700-84: Use case on FS_AIML_CN WT#2. | KDDI | Rel-19 | Not Handled | ==== Final Comments Deadline ==== | Not Handled |
| 19.15 | S2-2400982 | P-CR | Approval | 23.700-84: Scenarios for VFL between 3rd party AF and NWDAF. | Lenovo | Rel-19 | Not Handled | ==== Final Comments Deadline ==== | Not Handled |
| 19.15 | S2-2400131 | P-CR | Approval | 23.700-84: KI#2: Policy control and QoS assistance by NWDAF. | NTT DOCOMO | Rel-19 | Not Handled | ==== Final Comments Deadline ==== | Not Handled |
| 19.15 | S2-2400151 | P-CR | Approval | 23.700-84: Key issue on policy enhancement assisted by NWDAF . | ZTE | Rel-19 | Not Handled | ==== Final Comments Deadline ==== | Not Handled |
| 19.15 | S2-2401301 | P-CR | Approval | 23.700-84: Key issue for WT 3.1: NWDAF-assisted policy control and QoS enhancements. | Nokia, Nokia Shanghai-Bell | Rel-19 | Not Handled | ==== Final Comments Deadline ==== | Not Handled |
| 19.15 | S2-2400863 | P-CR | Approval | 23.700-84: Key issue for WT#3.1 NWDAF-assisted policy control and QoS enhancements. | CATT | Rel-19 | Not Handled | ==== Final Comments Deadline ==== | Not Handled |
| 19.15 | S2-2400922 | P-CR | Approval | 23.700-84: New KI for WT3.1: Supporting PCF decisions for dynamic policy control and QoS decisions assisted by NWDAF. | Lenovo | Rel-19 | Not Handled | ==== Final Comments Deadline ==== | Not Handled |
| 19.15 | S2-2400083 | P-CR | Approval | 23.700-84: 23.700-84: Key issue X: Signalling storm detection, prediction and mitigation . | OPPO | Rel-19 | Not Handled | ==== Final Comments Deadline ==== | Not Handled |
| 19.15 | S2-2400127 | P-CR | Approval | 23.700-84: New Key Issue on NWDAF-assisted enhanced mechanisms to address network abnormal behaviours. | SK Telecom | Rel-19 | Not Handled | ==== Final Comments Deadline ==== | Not Handled |
| 19.15 | S2-2400132 | P-CR | Approval | 23.700-84: KI#3: NF Abnormality analytics. | NTT DOCOMO | Rel-19 | Merged into S2-2401834 | Peretz (Veizon) incorporates a few additions and provides r01. Huli (vivo) ask to close the E-mail thread since the contribution is already merged into S2-2400562. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Merged |
| 19.15 | S2-2400152 | P-CR | Approval | 23.700-84: Key issue on solving signnaling storm . | ZTE | Rel-19 | Not Handled | ==== Final Comments Deadline ==== | Not Handled |
| 19.15 | S2-2400927 | P-CR | Approval | 23.700-84: New KI for WT3.2: Signalling storm detection, prediction and mitigation. | Lenovo | Rel-19 | Not Handled | ==== Final Comments Deadline ==== | Not Handled |
| 19.15 | S2-2401066 | P-CR | Approval | 23.700-84: New KI on Network abnormal behaviours handling with the assistance of NWDAF (WT3.2). | China mobile | Rel-19 | Not Handled | ==== Final Comments Deadline ==== | Not Handled |
| 19.15 | S2-2401311 | P-CR | Approval | 23.700-84: Key issue for WT 3.1: NWDAF-assisted network abnormal behaviours prevention and mitigation. | Nokia, Nokia Shanghai-Bell | Rel-19 | Not Handled | ==== Final Comments Deadline ==== | Not Handled |
| 19.15 | S2-2401370 | P-CR | Approval | 23.700-84: New Key Issue on NWDAF-assisted mechanisms to control network abnormal behaviours. | Samsung | Rel-19 | Not Handled | ==== Final Comments Deadline ==== | Not Handled |
| 30 | - | - | - | Project Planning and Management | - | - | Docs:=0 | - | |
| 30.1 | - | - | - | New and Revised Study/Work Items | - | - | Docs:=15 | - | |
| 30.1 | S2-2400176 | DISCUSSION | Information | Discussion on WT#2.3 for the UE with the tethered devices in FS_XRM Ph2. | Vivo, China Telecom, Lenovo, Meta USA, Tencent, Tencent Cloud, MediaTek | Noted | Noted | ||
| 30.1 | S2-2400177 | SID REVISED | Approval | Revised SID on 5GS XRM Ph2 . | Vivo, China Telecom, Lenovo, Meta USA, Tencent, Tencent Cloud MediaTek | Rel-19 | Noted | Devaki (Nokia) objects to the SID update as this kind of increases the scope of the SID (immediately after Rel-19 package approval). Mehrdad (MediaTek Inc.) suggests to NOTE this but to go with Alt2 in S2-2400178 ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Noted |
| 30.1 | S2-2400178 | SID REVISED | Approval | Revised SID on 5GS XRM Ph2 . | Vivo, China Telecom, Lenovo | Rel-19 | r01 Agreed. Revised to S2-2401622. | Devaki (Nokia) has strong concerns with the SID update. Xiaowan Ke(vivo) replies to Devaki (Nokia) Mehrdad (MediaTek Inc.) is OK with this change in the SID. ==== Revisions Deadline ==== Devaki (Nokia) comments Devaki (Nokia) can live with 178, if it is ok for others. Xiaowan Ke(vivo) replies to Devaki (Nokia) and suggest to agree the original version ==== Final Comments Deadline ==== | Revised |
| 30.1 | S2-2401622 | SID REVISED | Approval | Revised SID on 5GS XRM Ph2 . | Vivo, China Telecom, Lenovo | Rel-19 | Revision of S2-2400178r01. Approved | Approved | |
| 30.1 | S2-2400246 | DISCUSSION | Decision | Discussion Paper: Update WT#2.3 of R19 FS_XRM Ph2 SID. | CATT | Rel-19 | Noted | Noted | |
| 30.1 | S2-2400247 | DISCUSSION | Decision | Discussion Paper: Update WT#2.2 of R19 FS_XRM_Ph2 SID. | CATT | Rel-19 | Noted | Noted | |
| 30.1 | S2-2400248 | SID REVISED | Approval | Update New SID on 5GS XRM Ph2 . | CATT | Rel-19 | CC#3: Noted | Shabnam (Ericsson) the updates change the scope and increases the work and this aspect was discussed extensively during SA plenary approval of the SI. We object to the changes. Chunshan (CATT) provides r01 without change the scope. Mehrdad (MediaTek Inc.) objects to original version but can live with r01 Shabnam (Ericsson) can not agree with r01 either, provides explanation & welcomes others view from SA discussion ==== Revisions Deadline ==== Chunshan (CATT) proposes to go with r01, otherwise the WT#2.2 cannot work. Devaki (Nokia) comments. | Noted |
| 30.1 | S2-2400440 | SID REVISED | Approval | New SID on Proximity-based Services in 5GS - Phase 3. | AT&T, KPN (Rapporteurs) | Rel-19 | Revision of SP-231798. Approved | ==== Final Comments Deadline ==== | Approved |
| 30.1 | S2-2400475 | SID REVISED | Approval | Revised SID: Study on Enhancement of support for Edge Computing in 5G Core network - Phase 3. | Intel | Rel-19 | r03 Agreed. Revised to S2-2401623. | Hyesumg (Samsung) provides minor comments. Changhong (Intel) replies to Hyesung. Changhong (Intel) provides r01. Tezcan (Nokia) has concerns on adding text to the agreed WTs and prefers original submission. Magnus (Ericsson) provides r02 Fenqin (Huawei) comments. Changhong (Intel) provides r03. ==== Revisions Deadline ==== Fenqin (Huawei) is ok with r03. Hyesung (Samsung) is ok with r03. Tezcan (Nokia) is ok with r03. Jinguo(ZTE) is fine with r03 ==== Final Comments Deadline ==== | Revised |
| 30.1 | S2-2401623 | SID REVISED | Approval | Revised SID: Study on Enhancement of support for Edge Computing in 5G Core network - Phase 3. | Intel | Rel-19 | Revision of S2-2400475r03. Approved | Approved | |
| 30.1 | S2-2400991 | SID REVISED | Approval | New SID on Core Network Enhanced Support for Artificial Intelligence (AI)/Machine Learning (ML). | Vivo, MediaTek Inc | Rel-19 | r03 Agreed. Revised to S2-2401624. | Belen (Ericsson) asks to add Ericsson as supporting company. Belen (Ericsson) provides r01. Mehrdad (MediaTek Inc.) provides r02 Mehrdad (MediaTek Inc.) provides r03 ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 30.1 | S2-2401624 | SID REVISED | Approval | New SID on Core Network Enhanced Support for Artificial Intelligence (AI)/Machine Learning (ML). | Vivo, MediaTek Inc | Rel-19 | Revision of S2-2400991r03. Approved | Approved | |
| 30.1 | S2-2401315 | SID REVISED | Approval | Revised SID on Multi-Access (DualSteer and ATSSS_Ph4). | Apple (Primary Rapporteur) | Rel-19 | Revision of SP-231802. Approved | ==== Final Comments Deadline ==== | Approved |
| 30.1 | S2-2401345 | SID REVISED | Approval | Updated SID on Vehicle Mounted Relays (VMR) Phase 2. | Qualcomm Incorporated, Sony | Rel-19 | r01 Agreed. Revised to S2-2401625. | Qian (Ericsson) provides r01 adding Ericsson as supporting company ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 30.1 | S2-2401625 | SID REVISED | Approval | Updated SID on Vehicle Mounted Relays (VMR) Phase 2. | Qualcomm Incorporated, Sony | Rel-19 | Revision of S2-2401345r01. Approved | Approved | |
| 30.2 | - | - | - | Proposals for TEI19 | - | - | Docs:=128 | - | |
| 30.2 | S2-2400161 | WID NEW | Approval | New WID on enhancement of TSC&URLLC_FRER. | China Mobile | Rel-19 | Not handled | Not Handled | |
| 30.2 | S2-2400162 | DISCUSSION | Information | Remote UE accessing services provided by PIN | Huawei, HiSilicon | Rel-19 | Noted | Noted | |
| 30.2 | S2-2400163 | WID NEW | Approval | Remote UE accessing services provided by PIN. | Huawei, HiSilicon | Rel-19 | CC#4: Postponed | Jicheol (Samsung) shares the similar view as Qualcomm, Nokia and Ericsson (i.e propose to note). Susan (Huawei) replies to Qian (Ericsson). Susan (Huawei) replies to Jicheol (Samsung) and clarifies that the existing NRF based mechanism does not work for PIN. Qian (Ericsson) replies to Susan (Huawei). Kefeng (Qualcomm) is not convinced with the clarification of 'per subscriber level DNN and S-NSSAI'. Susan (Huawei) replies to Kefeng (Qualcomm) to clarify that: 1) PIN is SUPI/Consumer/Person level (each person/SUPI can subscribe one or more PINs), resulting in the DNN and S-NSSAI for each PIN is SUPI/Consumer/Person level, see 23.501 'For each PIN, a dedicated DNN/S-NSSAI shall be configured.'. The DNN/S-NSSAI for PIN is actually used as a PIN identifier. 2) For others, such as 5G VN Group, DNN and S-NSSAI is per enterprise configuration, not per each person level. Pallab (Nokia) is not convinced with the justification. Once a DNN, S-NSSAI is assigned, why cannot an SMF be selected based on that DNN, S-NSSAI? Susan (Huawei) replies to Pallab (Nokia) to clarify that the PEGC or UEs belonging to a PIN (Personal IoT network) is used by a person, and asks for clarification how it is possible to configure per each person/consumer (identified by one or two SUPIs) information in the NRF? ==== Revisions Deadline ==== Pallab (Nokia) proposes to NOTE and responds to Susan (Huawei) Qian (Ericsson) proposes to NOTE the paper and replies further to Susan (Huawei) . Kefeng (Qualcomm) proposes to NOTE the paper. Susan (Huawei) replies to Pallab (Nokia) and proposes to postpone this TEI19, and askes whether the same arguments from Pallab, i.e. 'let us wait for actual PIN deployments', can be used to object other topics Nokia is proposing. Susan (Huawei) cannot accept the proposal from Kefeng (Qualcomm) to NOTE the paper, without technical explanation. Susan (Huawei) asks for CC#3 or CC#4 discussion on this paper. ==== Final Comments Deadline ==== | Postponed |
| 30.2 | S2-2400164 | DRAFTCR | Information | SMF selection for PIN Group | Huawei, HiSilicon | Rel-19 | Noted | Noted | |
| 30.2 | S2-2400165 | DRAFTCR | Information | SMF and UPF selection for PIN Group | Huawei, HiSilicon | Rel-19 | Noted | Noted | |
| 30.2 | S2-2400171 | DRAFTCR | Information | Support of Replication and elimination for redundancy transmission for FRER | China Mobile | Rel-19 | Not handled | Not Handled | |
| 30.2 | S2-2400173 | WID NEW | Discussion | New WID on Network Controlled Network Slice Selection . | KDDI | Rel-19 | Postponed | Myungjune (LGE) proposes to postpone. Stefano (Qualcomm) suggests noting. Koji (KDDI) responds to LG's comment and QC's comment. Alessio(Nokia) provides comments Belen (Ericsson) provides comments. Koji (KDDI) provides comments. Fenqin (Huawei) provides comments. Dan(China Mobile) support of this TEI19 Alessio(Nokia) thanks KDDI for their polite reply and would like to be part of offline discussions going forward. Ashok (Samsung) provides comments Jinguo(ZTE) supports this WID Ulises (InterDigital Inc.) provides comments. Koji (KDDI) responds to Samsung's comment and ZTE's comment. Peter Hedman (Ericsson) provides comments Xiao (Toyota) supports this work for TEI19. Yasuo (SHARP) provides comments. Krisztian (Apple) provides comments. Koji (KDDI) confirms supporting companies. Fenqin (Huawei) comments. Yuying (China Telecom) comments. Susana (Vodafone) comments Koji (KDDI) confirms supporting companies, and provides comments. Koji (KDDI) proposes to postpone this WID. ==== Revisions Deadline ==== Nassima (KPN) comments Ouerdia (Orange) comments | Postponed |
| 30.2 | S2-2400174 | DISCUSSION | Discussion | Discussion on Network Controlled Slice Selection | KDDI Corporation | Rel-19 | Noted | Belen (Ericsson) provides comments. Koji (KDDI) responds to Ericsson's comments. Belen (Ericsson) replies to KDDI ==== Revisions Deadline ==== | Noted |
| 30.2 | S2-2400193 | WID NEW | Approval | Minimize the number of Policy Associations . | Ericsson, AT&T, Verizon, Oracle, Huawei | Rel-19 | Revision of (unhandled) S2-2312524. r03 Agreed. Revised to S2-2401626. | Srinivas Garikipati (Nokia) support this SID and wish to co-sign. Jinsook (DISH Network) we also support this TEI19. Belen (Ericsson) provides r02 (no r01 was stored). Ashok (Samsung) comments. Belen (Ericsson) replies to comments Ashok (Samsung) provides further comments. Dimitris (Lenovo) has a question on the scenario where the AF influences URSP rules Hyunsook (LGE) asks clarifications. Belen (Ericsson) replies to Samsung comments Belen (Ericsson) replies to Lenovo. Belen (Ericsson) provides r03 Dimitris (Lenovo) responds to Belen Ashok (Samsung) responds to Belen (Ericsson) Belen(Ericsson) replies to Lenovo Belen (Ericsson) responds to Samsung Ashok (Samsung) responds to Ericsson Dimitris (Lenovo) further responds Changhong (Intel) asks to add Intel as cosigner for this TEI19 WID. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 30.2 | S2-2401626 | WID NEW | Approval | Minimize the number of Policy Associations . | Ericsson, AT&T, Verizon, Oracle, Huawei | Rel-19 | Revision of S2-2400193r03. Endorsed | Endorsed | |
| 30.2 | S2-2400194 | OTHER | Information | TEI19 draft CRs - Minimize the Number of Policy Associations | Ericsson, AT&T, Verizon, Oracle | Rel-19 | Revision of (unhandled) S2-2312524. Noted | Belen (Ericsson) provides r01, aligned with r02 of the WID Hong (Qualcomm) comments on r01. Belen (Ericsson) provides r02 Belen (Ericsson) provides r03 including comments from QC ==== Revisions Deadline ==== | Noted |
| 30.2 | S2-2400195 | DISCUSSION | Discussion | Minimize the number of UE and AM Policy Associations. | Ericsson, AT&T, Verizon, Oracle, Huawei | Rel-19 | Revision of (unhandled) S2-2312524. Noted | Noted | |
| 30.2 | S2-2400209 | WID NEW | Approval | New WID: Deferred 5GC-MT-LR Procedure for Periodic Location Events based NRPPa Periodic Measurement Reports. | Ericsson | Rel-19 | CC#4: Postponed | Yunjing(CATT) provides comment. Richard (Ericsson) responses to Yunjing(CATT) Yunjing (CATT) replies to Richard (Ericsson). Richard (Ericsson) replies to Yunjing (CATT) Richard (Ericsson) provides r01, adding T-Mobile USA and Huawei as supporter company Yunjing (CATT) concerns the need of this TEI proposal since SA2 already has UE based solution. Richard (Ericsson) provides r02, adding China Mobile as supporting company Richard (Ericsson) UE based approach does not always satisfy operators needs and one can see many functions in 3GPP that has both options includes like Location Services. ==== Revisions Deadline ==== Yunjing (CATT) suggests to postpone the TEI since the mobility issue raised earlier this week has not been addressed, and coordination with RAN WG is possible needed. Runze (Huawei) supports the TEI work and clarifies the motivation. Richard (Ericsson) addresses questions from Yunjing (CATT), and suggest to endorse the TEI item Yunjing(CATT) don't think Richard (Ericsson) addressed her questions, and don't agree to endorse the TEI item this meeting in a rush. Yunjing(CATT) replies to Runze (Huawei), the procedure proposed in corresponding CR is actually a new end to end procedure. Richard (Ericsson) disagrees the questions have not been answered. Item was shared in the Chicago meeting which happened 2 and half months ago. ==== Final Comments Deadline ==== | Postponed |
| 30.2 | S2-2400210 | DISCUSSION | Discussion | Deferred 5GC-MT-LR Procedure for Periodic Location Events based NRPPa Periodic Measurement Reports. | Ericsson | Rel-19 | Noted | Noted | |
| 30.2 | S2-2400211 | OTHER | Information | Deferred 5GC-MT-LR Procedure for Periodic Location Events based NRPPa Periodic Measurement Reports | Ericsson | Rel-19 | Noted | Noted | |
| 30.2 | S2-2400223 | WID NEW | Approval | New WID on Architecture support of Roaming Value-Added Services. | Ericsson, Nokia, Deutsche Telekom, AT&T | Rel-19 | r01 endorsed. Revised to S2-2401647. | Haris(Qualcomm) provides comment re the TU allocation Qian (Ericsson) provides comments Qian (Ericsson) provides r01 to reduce the TU ==== Revisions Deadline ==== Qian (Ericsson) proposes to endorse/agree r01 Srinivas Garikipati (Nokia) proposes to endorse/agree r01 Dieter (Deutsche Telekom) asks to postpone the WID. Haris(Qualcomm) is ok with r01. Minor comment: Qian's email is mispelled in rapporteur section Qian (Ericsson) indicates that we have worked on this for long time before this meeting. And we have limited time to the Feb meetings. It will be good know the reason to postpone. Fenqin (Huawei) is ok with r01. Hugh (AT&T) proposes to endorse/agree r01 ==== Final Comments Deadline ==== Laurent (Nokia): it would be fair to have ASAP an explanation on why we need to postpone (the CR may of course be subject of changes) Jicheol (Samsung) prefers endorsing this version and requests to add Samsung as supporting companies when uploading the final version. Dieter (Deutsche Telekom) is ok to endorse the WID. | Revised |
| 30.2 | S2-2401647 | WID NEW | Approval | New WID on Architecture support of Roaming Value-Added Services. | Ericsson, Nokia, Deutsche Telekom, AT&T | Rel-19 | Revision of S2-2400223r01. Endorsed | Endorsed | |
| 30.2 | S2-2400224 | OTHER | Information | RVAS with target NF selection enhancement. | Ericsson | Rel-19 | Noted | Haris(Qualcomm) provides r01 in DRAFTS folder Fenqin (Huawei) ask a question for clarification Qian (Ericsson) provides answers to Fenqin (Huawei) Fenqin (Huawei) comments Qian (Ericsson) provides further responses and r02 in draft folder. Saso (Intel) wonders if 'target PLMN' is appropriate term. Fenqin (Huawei) provides further responses. Qian (Ericsson) responds to Fenqin (Huawei) and Saso (Intel) related to the terminology. Fenqin (Huawei) provides responds to Qian (Ericsson) ==== Revisions Deadline ==== | Noted |
| 30.2 | S2-2400265 | WID NEW | Approval | New WID on Roaming traffic offloading via home-session breakout. | SK Telecom, Samsung | Not handled | Not Handled | ||
| 30.2 | S2-2400266 | DISCUSSION | Information | TEI19_Discussion on roaming traffic offloading via home-session breakout | SK Telecom | Rel-19 | Not handled | Not Handled | |
| 30.2 | S2-2400267 | DRAFTCR | Information | HR-HSBO: HR session breakout in HPLMN | Samsung, SK Telecom | Rel-19 | Not handled | Not Handled | |
| 30.2 | S2-2400268 | DRAFTCR | Information | HR-HSBO: H-UPF selection and user plane management | SK Telecom, Samsung | Rel-19 | Not handled | Not Handled | |
| 30.2 | S2-2400288 | DRAFTCR | Information | HR-HSBO: User Plane management | Samsung, SK Telecom | Rel-19 | Not handled | Not Handled | |
| 30.2 | S2-2400299 | WID NEW | Approval | New WID on Indirect Network Sharing . | China Unicom | Rel-19 | Revision of (noted) S2-2312441. CC#4: r07 + changes endorsed. Revised to S2-2401652. | Laurent (Nokia): supports the WID and is happy to cosign Tianqi (China Unicom) provides r01 to remove the 'charging part' in the objective clause. Tianqi (China Unicom) provides r02 to add the supporting company. Haris(Qualcomm) proposes to reduce the TUs to 0.5 Tianqi (China Unicom) suggests to reduce the TUs to 1. Tianqi (China Unicom) provides r03 to reduce the TU to 1. Saso (Intel) seeks clarifications. Tianqi (China Unicom) replies to Saso. Tianqi (China Unicom) provides r04. Haris(Qualcomm) asks question for clarification on new text in r04 and proposes alternative text Tianqi (China Unicom) provides r05. Shabnam (Ericsson) would support Haris approach, describe the scenario and not number of SMFs ?? Tianqi (China Unicom) gives a clarification and suggestion. Fenqin (Huawei) suggest some wording. Tianqi (China Unicom) provides r06 to refine the wording. Jicheol (Samsung) comments. Tianqi (China Unicom) gives a clarification. Saso (Intel) is OK with r06. Tianqi (China Unicom) provides r07. ==== Revisions Deadline ==== Tianqi (China Unicom) is fine for r07. Tianqi (China Unicom) suggests to endorse r07. Jicheol (Samsung) is okay to endorse r07. Fenqin (Huawei) is ok with r07. Haris(Qualcomm) is ok with r07 Chris(Vodafone) objects to r07 and all other revisions that ignore roaming. Tianqi (China Unicom) replies to Chris. Fenqin (Huawei) comments that roaming is still supported but just with some restriction. Shabnam (Ericsson) Chris, I think one can describe consequence, which is what agreement was if I recollect. Tianqi (China Unicom) proposes to endorse r07 and add the NOTE to clarify 'in the case of Indirect Network Sharing, tthe roaming users of participating operator can access the 4G network of participating operator as usual in the shared area' in the formal CR. Haris(Qualcomm) comments Laurent (Nokia): yes we have discussed this thoroughly and got consensus about what Tianqi and Shabnam Tianqi (China Unicom) replies further. Chris (Vodafone) suggests to add text to the WID to explain how roaming will not be supported (sending PLMN not allowed would be the normal reaction of an AMF but would be incorrect in this situation). ==== Final Comments Deadline ==== Lei(Tencent) share the view that this TEI WID has been discussed this thoroughly and TEI WID already endorsed in last meeting. The DraftCR by Ericsson and other companies are already in good shape. Hope this TEI WID can be agreed in this meeting and CR can be refined in future meetings. Saso (Intel) proposes to replace NOTE2 in r07 with a new bullet. Andy (SA2 Chair): No TEI19 WIDs were endorsed in the last meeting. Tianqi (China Unicom) suggests to endorse r09 in DRAFTS folder. Chris (Vodafone) says he is OK with r09. Tianqi (China Unicom) refine the wording based on r08, and provides updated ' NOTE 2: The scenario where the participating operator is different from the home network operator of the UE is not supported in this release. As part of this TEI19 WID, it will be documented how to handle the inbound roaming UE of the participating operator in the shared area of Indirect Network Sharing based on roaming agreement (e.g. redirect UE to 4G network of the participating operator to receive services using currently available mechanism). ', r09 in Drafts and remove Vodafone from supporting company based on Chris's request. Chris (Vodafone) replies. Chris (Vodafone) says r08 (or r07 with Laurent-Nokia's note) will be OK if you remove Vodafone as a supporting company. Tianqi (China Unicom) refines the wording of the NOTE. Shabnam (Ericsson) provides updated 'NOTE 2: The scenario where the participating operator is different from the home network operator of the UE is not supported in this release. As part of this work item it will be documented how to handle the inbound roaming UE of the participating network in the shared area based on roaming agreement (e.g. redirect UE to 4G network of the participating network to receive services using currently available mechanism).', r08 in Drafts. Laurent (Nokia): proposes to replace NOTE2 in r07 with a new bullet slightly different from Saso's | Revised |
| 30.2 | S2-2401652 | WID NEW | Approval | New WID on Indirect Network Sharing . | China Unicom | Rel-19 | Revision of S2-2400299r07 + changes. Endorsed | Endorsed | |
| 30.2 | S2-2400225 | OTHER | Information | Draft CRs: Indirect Network Sharing. | Ericsson, China Unicom | Rel-19 | Noted | Tianqi (China Unicom) provides r01 for your information. Zhenhua (vivo) is happy to co-sign the CR. Tianqi (China Unicom) provides r02 to add source company. ==== Revisions Deadline ==== | Noted |
| 30.2 | S2-2400553 | DRAFTCR | Information | The clarifications of mobility procedure for Indirect Network Sharing | China Unicom, Ericsson | Rel-19 | Noted | Tianqi (China Unicom) provides r01 for your information. Zhenhua (vivo) is happy to co-sign the CR. Tianqi (China Unicom) provides r02 to add source company. ==== Revisions Deadline ==== | Noted |
| 30.2 | S2-2400347 | WID NEW | Information | New WID on Emergency Short Message Service over IMS. | Orange, Telecom Italia, BT plc, Thales, Minist re Economie et Finances, Google, Ericsson | Rel-19 | Revision of (unhandled) S2-2312007. r03 Agreed. Revised to S2-2401627. | Rainer (Nokia) supporting this WID. Antoine (Orange) provides r01 and indicates that draft CRs are available in S2-2400141. Chris (Vodafone) expects that this work is probably needed, but it looks a large TEI. How does it interact/complement ETSI-EMTEL-AML? Antoine (Orange) replies to Chris. Chris (Vodafone) replies to Antoine (Orange). Antoine (Orange) replies to Chris (Vodafone). Haris(Qualcomm) provides comments Rainer (Nokia) replies Chris (Vodafone) replies to Orange about AML use of +CC112 Haris(Qualcomm) replies Rainer (Nokia) replies to Haris (QC). Antoine (Orange) replies to Haris and Chris. Jinsook (DISH Network) asking for clarification for the scope Shabnam (Ericsson) provides comments that the draft CRs were produced if we went with full scope of the potential work and to indicate the potential impacts to consider, see below: Rainer (Nokia) comments on the scope Antoine (Orange) replies on the scope. Rainer (Nokia) replies on the WID scope Jinsook (DISH Network) comment on the scope Ashok (Samsung) comments Antoine (Orange) replies to Ashok. Ashok (Samsung) provides further comments Krisztian (Apple) supports this TEI19 WID. Jinsook (DISH Network) we also support this TEI19 and want to be involved in the solution preparation ! Antoine (Orange) provides r02. Rainer (Nokia) is ok with r02 Ashok (Samsung) is ok with r02 Antoine (Orange) provides r03 (adding Samsung). ==== Revisions Deadline ==== Jinsook (DISH Network) Thanks for the update, question for the UE impact Antoine (Orange) replies. Rainer (Nokia) proposes to endorse r03 Antoine (Orange) also proposes to endorse r03 as the discussion seems to has converged. Haris(Qualcomm) is ok to endorse r03 of the WI. More work is needed in the CRs Jinsook (DISH Network) yes agree to endorse v03 ==== Final Comments Deadline ==== | Revised |
| 30.2 | S2-2401627 | WID NEW | Information | New WID on Emergency Short Message Service over IMS. | Orange, Telecom Italia, BT plc, Thales, Minist re Economie et Finances, Google, Ericsson | Rel-19 | Revision of S2-2400347r03. Endorsed | Endorsed | |
| 30.2 | S2-2400141 | OTHER | Information | Support for Emeregency SMS over IMS | Ericsson | Rel-19 | Noted | Haris(Qualcomm) comments Antoine (Orange) replies to Haris. Rainer (Nokia) comments on the CRs George (Ericsson) provides responses and hopefully we can agree. Please see inline George (Ericsson) provides responses inline Haris(Qualcomm) provides further comments inline Rainer (Nokia) replies George (Ericsson) ask a question George (Ericsson) asks a question Haris(Qualcomm) responds to George Ashok (Samsung) request for clarification from George George (Ericsson) provides comment on SIB George (Ericsson) responds George (Ericsson) provides answer George (Ericsson) provides an updated set. Rainer (Nokia) proposes too keep CRs open until next meeting George (Ericsson) is Ok with that. ==== Revisions Deadline ==== | Noted |
| 30.2 | S2-2400355 | WID NEW | Approval | New WID on providing per-subscriber VLAN instructions from UDM. | Ericsson | Rel-19 | Postponed | Qianghua (Huawei) comments and proposes to generalize the objective to allow considering other options Stefan (Ericsson) replies and provides r01 Pavan (Google) seeks clarification. Hyunsook (LGE) asks a clarification on handling per subscriber. Laurent (Nokia): Comments asking for clarifications Qianghua (Huawei) replies Stefan (Ericsson) replies to Laurent Stefan (Ericsson) replies to Qianghua Stefan (Ericsson) provides r02 Laurent (Nokia): Comments on r02 Stefan (Ericsson) provides r03 and r04 ==== Revisions Deadline ==== Ling (Siemens) is concerned about the justification of the study and solutions. Stefan (Ericsson) replies to Ling Laurent (Nokia): Suggests to go ahead with R04 (endorsed) that he cosigns (together with the CR(s)) BUT correct the WID title (adding 'and DN-AAA') Ling (Siemens) remains concerns and suggests more offline discussions and postpone the WID at this meeting ==== Final Comments Deadline ==== | Postponed |
| 30.2 | S2-2400356 | WID NEW | Approval | New WID on enhancing NEF Parameter Provisioning procedure with static UE IP address and UP security policy . | Ericsson | Rel-19 | r00 + changes Agreed. Revised to S2-2401639. | Qianghua (Huawei) comments Stefan (Ericsson) replies Marco(Huawei) replies to Stefan (Ericsson) Stefan (Ericsson) replies to Marco Laurent (Nokia): Comments. Having the AF able to allocate a proper UE IP address for a UE is a MUST to be considered before discussing NEF API Dieter (Deutsche Telekom): We are supportive of this TEI WID. Please add Deutsche Telekom as supporting company. ==== Revisions Deadline ==== Laurent (Nokia): Suggests to endorse this TEI19, cosigns the CR(s) Ling (Siemens) supports this WID Stefan (Ericsson) proposes to endorse the WID/CRs but reword in the 23.502 CR from 'The AF may provide static IP address/prefix for multiple GPSIs using the external parameter provision procedure.' to 'The AF may provide a list of GPSIs and for each GPSI include the static IP address/prefix as described in Table 4.15.6.3x-1' ==== Final Comments Deadline ==== | Revised |
| 30.2 | S2-2401639 | WID NEW | Approval | New WID on enhancing NEF Parameter Provisioning procedure with static UE IP address and UP security policy . | Ericsson, Nokia, Nokia Shanghai Bell, Deutsche Telekom, Siemens AG | Rel-19 | Revision of S2-2400356r00 + changes. Endorsed | Endorsed | |
| 30.2 | S2-2400380 | WID NEW | Agreement | Draft TEI19 WID on support of Access Traffic Steering, Switching, Splitting and Aggregation of all Traffic Types by single MPDCCP based Steering functionality. | Vodafone, Deutsche Telekom, BT, Huawei, Xiaomi, InterDigital, Broadcom | Rel-19 | Revision of (unhandled) S2-2309402. Noted | Haris(Qualcomm) comments Rainer (Nokia) comments, questioning the need of another steering function option Stefan (Ericsson) comments, also questions the need for another steering functionality Myungjune (LGE) agrees comments from Qualcomm, Nokia and Ericsson Dieter (Deutsche Telekom) MPDCCP is needed to avoid double encryption, to support all kind of traffic in a simple manner, and is the only protocol that comes with sequencing numbers which is needed for reordering in particular for the RG case. Susana (Vodafone) comments that from RGs market perspective, MPDCCP is taking prevalence and support in the core is needed. Krisztian (Apple) agrees with the comments from Qualcomm, Nokia, Ericsson and LGE. Existing Rel-18 MPQUIC steering functionality and work-in-progress R19 extensions serve the same need as MPDCCP, hence there is no need for a competing solution. Conclusion of R18 ATSSS study was not to progress MPDCCP. Susan (Huawei) supports this TEI19 proposal. Ellen (Google) comments, SA2 has made the choice to support MPQUIC in R18 and continue to enhance it in R19. The alternative option is not needed. The MPDCCP proposal would require a study for more TUs to resolve potential coexistence issues. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Noted |
| 30.2 | S2-2400381 | DRAFTCR | Agreement | Introduction of the MPDCCP Steering Functionality | Deutsche Telekom, Vodafone | Rel-19 | Noted | Haris(Qualcomm) comments Guanzhou (InterDigtial) provides r01 for inner header compression support. Susan (Huawei) provides r02. ==== Revisions Deadline ==== | Noted |
| 30.2 | S2-2400382 | DRAFTCR | Agreement | Introduction of the MPDCCP Steering Functionality | Vodafone, Deutsche Telekom | Rel-19 | Noted | Haris(Qualcomm) comments Guanzhou (InterDigtial) provides r01 for inner header compression support. Guanzhou (InterDigtial) provides r02. ==== Revisions Deadline ==== | Noted |
| 30.2 | S2-2400383 | DRAFTCR | Agreement | Introduction of the MPDCCP Steering Functionality | Deutsche Telekom, Vodafone | Rel-19 | Noted | Susan (Huawei) provides r01. ==== Revisions Deadline ==== | Noted |
| 30.2 | S2-2400406 | WID NEW | Discussion | New WID on DNN insertion for Alternative Network Slice. | Lenovo | Rel-19 | Not handled | Not Handled | |
| 30.2 | S2-2400410 | DRAFTCR | Discussion | DNN selection for Alternative S-NSSAI | Lenovo | Rel-18 | Not handled | Not Handled | |
| 30.2 | S2-2400411 | DRAFTCR | Discussion | DNN insertion for Alternative S-NSSAI | Lenovo | Rel-18 | Not handled | Not Handled | |
| 30.2 | S2-2400412 | DRAFTCR | Discussion | DNN insertion for Alternative S-NSSAI | Lenovo | Rel-18 | Not handled | Not Handled | |
| 30.2 | S2-2400413 | DRAFTCR | Information | Spending Limits for UE Policies in Roaming scenario | Oracle | Rel-19 | Noted | Noted | |
| 30.2 | S2-2400423 | WID NEW | Discussion | New WID: TEI19_5MBS_Roam; Adding support for Roaming UEs to receive 5MBS. | Nokia, Nokia Shanghai Bell (Rapporteur) | Rel-19 | Revision of (unhandled) S2-2312582. Postponed | Robbie (Ericsson) comments. Haris(Qualcomm) questions the value of the WI, provides comments and asks questions Thomas(Nokia) replies to Haris(Qualcomm) LiMeng (Huawei) comments. Robbie (Ericsson) shares the similar view as Haris (Qualcomm) and provide further comments. Thomas(Nokia) replies to Robbie and provides r01 to address the comment of Limeng. ==== Revisions Deadline ==== Robbie (Ericsson) objects to the approval of this WI. Haris(Qualcomm) objects to the endorsement or approval Thomas(Nokia) suggest to postpone this WID ==== Final Comments Deadline ==== | Postponed |
| 30.2 | S2-2400424 | DRAFTCR | Discussion | MBS Roaming | Nokia, Nokia Shanghai-Bell | Rel-19 | Revision of (unhandled) S2-2312583. Noted | Robbie (Ericsson) comments. Thomas (Nokia) replies to Robbie. Thomas (Nokia) provides r01 to address comments of Robbie. ==== Revisions Deadline ==== | Noted |
| 30.2 | S2-2400435 | DRAFTCR | Discussion | MBS Roaming | Nokia, Nokia Shanghai-Bell | Rel-19 | Noted | Noted | |
| 30.2 | S2-2400403 | WID NEW | Approval | WID: TEI19_SLUPiR Spending Limits for UE Policies in Roaming scenario . | Oracle | Rel-19 | Revision of (unhandled) S2-2313202. r02 Agreed. Revised to S2-2401628. | Srinivas Garikipati (Nokia) comments about the TU Uri (Oracle) provides r01 of the TEI 19 proposal. Belen (Ericsson) provides comments Uri (Oracle) replies to Srinivas Garikipati (Nokia) with a question. Uri (Oracle) addresses Belen's concerns and provides r01 of both 23.501 and 23.503 draft CRs. Hong (Qualcomm) asks for clarifications of the use case. Hong (Qualcomm) comments on r02. Uri (Oracle) provides r02 of the WID to address use case questions of Hong (Qualcomm) and to accommodate a request from Susana (Vodafone). Uri (Oracle) provides r02 of the 23.503 draftCR (S2-2400445) to address Hong's (Qualcomm) comments. Hong (Qualcomm) comments. Uri (Oracle) responds to yet another Hong's (Qualcomm) good comment. Uri (Oracle) replies to Hong (Qualcomm). Hong (Qualcomm) replies to Uri. Uri (Oracle) provides additional clarifications to address Hong's (Qualcomm) last comment. Belen (Ericsson) comments. Uri (Oracle) replies to a new question from Hong (Qualcomm). Uri (Oracle) provides new revisions of the 23.501 and 23.503 draftCRs to align with adjustment in SLAMUP CR 0384. ==== Revisions Deadline ==== ==== Final Comments Deadline ==== | Revised |
| 30.2 | S2-2401628 | WID NEW | Approval | WID: TEI19_SLUPiR Spending Limits for UE Policies in Roaming scenario . | Oracle | Rel-19 | Revision of S2-2400403r02. Endorsed | Endorsed | |
| 30.2 | S2-2400444 | DRAFTCR | Information | Spending Limits for UE Policies in Roaming scenario | Oracle | Rel-19 | Noted | Noted | |
| 30.2 | S2-2400445 | DRAFTCR | Information | Spending Limits for UE Policies in Roaming scenario | Oracle | Rel-19 | Noted | Noted | |
| 30.2 | S2-2400448 | WID NEW | Approval | New WID on Robust Paging Notification for NR-NTN. | Xiaomi | Rel-19 | Not handled | Chris (Vodafone) thinks the LS discussion means we should postpone this WID. Leo (Deutsche Telekom) asks to stop commenting on documents marked as postponed and not on the agenda for this meeting ==== Revisions Deadline ==== | Not Handled |
| 30.2 | S2-2400449 | DRAFTCR | Information | 23.501 draft CR for robust paging notification | Xiaomi | Rel-19 | Not handled | Not Handled | |
| 30.2 | S2-2400450 | DRAFTCR | Information | 23.502 draft CR for robust paging notification | Xiaomi | Rel-19 | Not handled | Not Handled | |
| 30.2 | S2-2400452 | WID NEW | Approval | New WID on Emergency Services over NB-IoT NTN. | Rel-19 | Not handled | Chris (Vodafone) says we need F2F chat on this with the IMS SMS emergency folks/operators. Jinsook (DISH Network ) agree with Vodafone, and also need to see the outcome of 'emergency SMS over IMS' Leo (Deutsche Telekom) asks to stop commenting on documents marked as postponed and not on the agenda for this meeting ==== Revisions Deadline ==== | Not Handled | |
| 30.2 | S2-2400612 | WID NEW | Approval | New WID: DSCP Marking in the UL. | Nokia, Nokia Shanghai Bell | Rel-19 | Postponed | Mengzhen (China Telecom) comments that this TEI is not needed. Mengzhen (China Telecom) shares the same view with Hongsuk (LGE). Hongsuk (LGE) asks question for DSCP marking in the UL for regular QoS Flows. Devaki (Nokia) replies. Hui (Huawei) supports China Telecom's concern. Mukesh (MediaTek) asks why this TEI needed when it contradicts the solution in S2-2400612 (Nokia) Paul (Ericsson) shares similar view and concern as Hui (Huawei), there is already a working solution to configure DSCP marking for UL in place. Devaki (Nokia) comments Devaki (Nokia) comments. Hong (Qualcomm) comments. Mengzhen (China Telecom) comments. Paul (Ericsson) replies to Devaki that there is today no support for taking PSI into consideration when performing DSCP marking, hence we have concerns to include it in the TEI work. Using PSI for UL DSCP marking has mainly RAN impacts and should in our view not be driven in SA2. Moreover, PSI information is not included in the UL user data, hence such functionality would require major impact to the radio interface/UE and would be again outside SA2 scope. Finally, it would add overhead for a functionality with unknown benefits. Xiaowan Ke(vivo) provides comments Ellen (Google) comments Hui (Huawei) replies to Hong. Devaki (Nokia) provides r01 to limit this to DSCP marking per QoS Flow for UL. ==== Revisions Deadline ==== Hui (Huawei) asks for postpone this TEI. Paul (Ericsson) we object to this WID because there already exists solution to the task that works. ==== Final Comments Deadline ==== | Postponed |
| 30.2 | S2-2400613 | DRAFTCR | Information | Introducing DSCP marking support for UL transport | Nokia, Nokia Shanghai Bell | Rel-19 | Noted | Noted | |
| 30.2 | S2-2400614 | DRAFTCR | Information | Introducing DSCP marking support for UL transport | Nokia, Nokia Shanghai Bell | Rel-19 | Noted | Noted | |
| 30.2 | S2-2400648 | WID NEW | Agreement | New WID: TEI19_NetFailTol; Enhancing Network Failure Tolerance . | China Telecom | Postponed | Juan Zhang (Qualcomm) provides comments Qian (Ericsson) provides comments. Laurent (Nokia): asks questions on WT1 and WT2 Yinglin (China Telecom) replies to comments and clarifies that WT1 and WT2 are 2 independent solutions addressing 2 different failure scenarios. Fei (OPPO) asks clarification. Yinglin (China Telecom) replies to Juan Zhang (Qualcomm). Yinglin (China Telecom) replies to Hyunsook (LGE) and copies the reply to Fei (OPPO) from another thread. Hyunsook (LGE) asks clarification. Yinglin (China Telecom) replies to Fei (OPPO). Antoine (Orange) proposes to remove WT2. Yinglin (China Telecom) provides WID_r01 and draftCR_r03. Yinglin (China Telecom) replies to Antoine (Orange). Antoine (Orange) replies to Yinglin (China Telecom). Hyunsook (LGE)seeks for further clarification. Juan Zhang (Qualcomm) replies to Yinglin (China Telecom). Yinglin (China Telecom) replies to Hyunsook (LGE). Hyunsook (LGE) hopes it doesn't affect the existing MINT. Yinglin (China Telecom) replies to Hyunsook (LGE) and provides draft CR r04 . Laurent (Nokia): Comments: WT2 shall be removed and Home-routed PDU session is required for IMS Voice Yinglin (China Telecom) replies to Laurent (Nokia). Juan Zhang (Qualcomm) replies to Yinglin. Antoine (Orange) provides r02, updating WT2 according to the discussion. Antoine (Orange) provides r03 = r02 without Word access restriction label. Yinglin (China Telecom) provides WID r04. ==== Revisions Deadline ==== Yinglin (China Telecom) replies to Jicheol (Samsung), clarifies that changes on WID are down-scoping and making the WID more clear. Jicheol (Samsung) proposes to postpone this. Yinglin (China Telecom) replies to Qian (Ericsson), clarifies that the controversial part on AUSF failure is removed and WT2 with UDM/UDR failure is not related to roaming. Qian (Ericsson) provides technical comments and also indicates the content of the WID seems changed intensively. Better to have more time to discussion this further and postpone the discussion to offline and next meeting. Juan Zhang (Qualcomm) proposes to postpone the WID. Laurent (Nokia): objects to endorsement of the WID at this meeting. Need to be postponed ==== Final Comments Deadline ==== | Postponed | |
| 30.2 | S2-2400650 | DRAFTCR | Agreement | Bypassing UE authentication and subscription data retrieval in the case of UDM/UDR/AUSF failure (WT2 of TEI19_NetFailTol) | China Telecom | Rel-19 | Noted | Noted | |
| 30.2 | S2-2400651 | DRAFTCR | Agreement | Enhancing Disaster Condition notification and determination procedures in the case of core network failure with 5G MOCN (WT1 of TEI19_NetFailTol) | China Telecom | Rel-19 | Noted | Noted | |
| 30.2 | S2-2400661 | DISCUSSION | Discussion | Discussion paper on TEI19 for SMSF Service Deactivation during inter-RAT Mobility. | Nokia, Nokia Shanghai Bell | Rel-19 | Not handled | Not Handled | |
| 30.2 | S2-2400662 | WID NEW | Approval | New WID: TEI19_SSDRM; SMSF Service Deactivation in case of inter-RAT Mobility. | Nokia, Nokia Shanghai Bell (Rapporteur) | Rel-19 | Not handled | Qian (Ericsson) provides comments and asks questions ==== Revisions Deadline ==== | Not Handled |
| 30.2 | S2-2400663 | DRAFTCR | Information | Addition of Deactivation cause to SMS service deactivation | Nokia, Nokia Shanghai Bell, T-Mobile | Rel-19 | Not handled | Not Handled | |
| 30.2 | S2-2400690 | DISCUSSION | Discussion | Discussion for TEI19 WID proposal on UE requested URSP provisioning. | LG Electronics | Rel-19 | Noted | Belen (Ericsson) provides comments ==== Revisions Deadline ==== | Noted |
| 30.2 | S2-2400691 | WID NEW | Endorsement | New WID: UE requested URSP provisioning (TEI19_URSPreq). | LG Electronics | Rel-19 | Noted | Susan (Huawei) suggests to note this proposal. Srinivas Garikipati (Nokia) provides views and comments on the TEI LaeYoung (LGE) provides r01 with answers to Susan (Huawei) and Srinivas (Nokia). Srinivas Garikipati (Nokia) provides updates to LaeYoung (LGE) Belen (Ericsson) provides comments Dimitris (Lenovo) has a question for the UE behaviour Changhong (Intel) comments. Jicheol (Samsung) proposes to note this WID. ==== Revisions Deadline ==== Srinivas Garikipati (Nokia) accordingly proposes to NOTE this WID. ==== Final Comments Deadline ==== | Noted |
| 30.2 | S2-2400694 | DRAFTCR | Information | UE requested URSP provisioning | LG Electronics | Rel-19 | Noted | Noted | |
| 30.2 | S2-2400695 | DRAFTCR | Information | UE requested URSP provisioning | LG Electronics | Rel-19 | Noted | Noted | |
| 30.2 | S2-2400697 | WID NEW | Approval | New WID on 5GC support for IoT NTN. | China Telecom, Vivo, CATT, Spreadtrum, Xiaomi, ZTE, Hughes/EchoStar, Inmarsat, Viasat, Oppo, TCL | Rel-19 | Revision of (unhandled) S2-2312210. CC#4: Noted | Haris(Qualcomm) comments Jinsook (DISH Network) We're interested in this proposal but seems more clarification is needed Heng(China Telecom) reply to Haris Stefan (Ericsson) comments Steve (Huawei) comments. Heng (China Telecom) reply to Jinsook Jinsook (DISH Network) thanks to Heng and ask further questions Heng (China Telecom) replies to Jinsook Heng (China Telecom) replies to Stefan Heng(China Telecom) replies to Steve. Saubhagya (Nokia) provide comments Antoine (Orange) asks if option 5 will be implemented and deployed. Heng (China Telecom) replies to Saubhagya Heng (China Telecom) reply. Jinsook (DISH Network) comments Chris (Vodafone) says he expects RAN and CT (and SA5) impacts - is this a TEI? Heng(China Telecom) explain: Within SA2 it is alignment work so this is a TEI Amy (vivo) replies to Andy and confirms that the work content is SA2 is limited as analyzed in S2-2400791 Heng (China Telecom) replies to Andy Jean Yves (Thales) is OK in principle to study this 5GC support for IoT NTN. but has some questions... ==== Revisions Deadline ==== Heng(China Telecom) replies to Jean Yves Munira Jaffar (Hughes/EchoStar) - The 5GC support of IoT is highly needed for operators deploying 3GPP NTN. Stefan (Ericsson) comments that this is not alignment work Haris(Qualcomm) observes that the WI and CRs have not been updated to reflect the comments made and the current version (r0) does not provide accurately the full scope Saubhagya (Nokia) has the same view as Stefan (Ericsson) it will have an impact on CT and RAN, not suitable for TEI19 Heng (China Telecom) replies and provide revision in the email Amy (vivo) proposes to postpone this TEI and bring it back by considering NB-IoT coarse location reporting and CT1 and SA5 impacts Robert (OQ Technology) we agree with Munira's comments regarding the rationale to introduce this feature is shared by several companies including ourselves. It is important that 5GC support be completed by including IoT NTN support. Please add OQ Technology as a supporting company. ==== Final Comments Deadline ==== Laurent (Nokia): clarifies we have sustained objection to any version of this TEI19 that should at least be a SID. Asks this document to be NOTED Heng (China Telecom) replies to Laurent: We support the conclusion marked by Chairman in CC#3. Laurent (Nokia): Answers and confirms his objection Stefan (Ericsson) has same view as Nokia and objects to any version of this TEI19. It is not suitable as TEI19. Asks this document to be NOTED Munira (Hughes/EchoStar) replies to Laurent Robert (OQ Technology) relies to Munira and Laurent. | Noted |
| 30.2 | S2-2400698 | DRAFTCR | Information | 23501 draft CR for 5GC support of IoT NTN | China Telecom, Vivo | Rel-19 | Revision of (unhandled) S2-2312211. Noted | Noted | |
| 30.2 | S2-2400699 | DRAFTCR | Information | 23.502 draft CR for 5GC support of IoT NTN | China Telecom, Vivo | Rel-19 | Revision of (unhandled) S2-2312212. Noted | Noted | |
| 30.2 | S2-2400700 | DRAFTCR | Information | 23.503 draft CR for 5GC support of IoT NTN | China Telecom | Rel-19 | Revision of (revised) S2-2311213. Noted | Noted | |
| 30.2 | S2-2400732 | CR | Approval | 23.401 CR3765 (Rel-19, 'B'): Enable emergency service support for NB-IoT UE over satellite access | Rel-19 | Incorrect WI Code on CR. Not handled | - | ||
| 30.2 | S2-2400733 | WID NEW | Approval | New WID: URSP rules with extended time window (TEI19_URSP_eTW). | LG Electronics | Rel-19 | Postponed | Hongsuk (LGE) provides r01 of the TEI 19 proposal. Yang (OPPO) has concern to r01 Srinivas Garikipati (Nokia) provides comment on the TEI Chia-Lin (MediaTek) provides comments and shares same view with previous emails Hongsuk (LGE) provides answers to Yang (OPPO) and Srinivas (Nokia). Antoine (Orange) replies to Chia-Lin and Srinivas Garikipati. Hongsuk (LGE) shares the same view with Antoine(Orange). Hong (Qualcomm) comments and thinks it is a useful enhancement. Jinsook (DISH Network) agree that the enhancement looks useful Srinivas Garikipati (Nokia) responds to Antoine Antoine (Orange) replies to Srinivas Garikipati that the earlier is the better. Krisztian (Apple) shares the concern raised by Oppo and thinks UE capability for this URSP feature would be against URSP design principles. Hongsuk (LGE) provides answers to Krisztian (Apple). Belen (Ericsson) see benefits to reduce signalling and configuration to the UE. Belen (Ericsson) comments Chia-Lin (MediaTek) still thinks the existing mechanism can achieve this feature Jicheol (Samsung) share the concern from OPPO and Apple. Changhong (Intel) sees the value of this TEI19 WID. ==== Revisions Deadline ==== Hongsuk (LGE) suggests to endorse(r01) and further discuss for the detail. ==== Final Comments Deadline ==== | Postponed |
| 30.2 | S2-2400734 | DISCUSSION | Discussion | Discussion for TEI19 WID proposal on URSP rules with extended time window . | LG Electronics | Rel-19 | Noted | Noted | |
| 30.2 | S2-2400739 | DRAFTCR | Information | URSP rules with extended time window | LG Electronics | Rel-18 | Noted | Noted | |
| 30.2 | S2-2400741 | DRAFTCR | Information | URSP rules with extended time window | LG Electronics | Rel-19 | Noted | Noted | |
| 30.2 | S2-2400748 | WID NEW | Approval | New WID on Edge Computing for EPC Interworking. | Nokia, Nokia Shanghai Bell | Rel-19 | Not handled | Magnus (Ericsson) cannot accept this TEI Laurent (Nokia): where is stated it is forbidden as TEI19. The point is whether this is useful feature (BTw this topic is not at the agenda) ==== Revisions Deadline ==== Magnus H (Ericsson) object to this WID since it is not on the agenda | Not Handled |
| 30.2 | S2-2400749 | DRAFTCR | Approval | Support of Edge Computing for EPC Interworking | Nokia, Nokia Shanghai Bell | Rel-19 | Not handled | Not Handled | |
| 30.2 | S2-2400750 | DRAFTCR | Approval | Support of Edge Computing for EPC Interworking | Nokia, Nokia Shanghai Bell | Rel-19 | Not handled | Not Handled | |
| 30.2 | S2-2400751 | DRAFTCR | Approval | Support of Edge Computing for EPC Interworking | Nokia, Nokia Shanghai Bell | Rel-19 | Not handled | Not Handled | |
| 30.2 | S2-2400762 | WID NEW | Approval | New WID: Access Stratum based time synchronization enhancements. | Nokia, Nokia Shanghai Bell | Rel-19 | Not handled | Jari (NTT DOCOMO) comments Srinivas Garikipati (Nokia) provides clarification to Jari. ==== Revisions Deadline ==== | Not Handled |
| 30.2 | S2-2400763 | DRAFTCR | Information | Assistance information for access stratum reference time distribution | Nokia, Nokia Shanghai Bell | Rel-19 | Not handled | Not Handled | |
| 30.2 | S2-2400764 | DRAFTCR | Information | RVAS - Support of Welcome SMS | Nokia, Nokia Shanghai Bell, Ericsson | Rel-19 | Noted | Fenqin (Huawei) comments Srinivas Garikipati (Nokia) Comments to Fenqin and provides r01 ==== Revisions Deadline ==== | Noted |
| 30.2 | S2-2400765 | DRAFTCR | Information | Introduction to 5GS support of Roaming value Added Services (RVAS) | Nokia, Nokia Shanghai Bell | Rel-19 | Noted | Haris(Qualcomm) provides comment Srinivas Garikipati (Nokia) provides clarification and uploads a revision r01 Fenqin (Huawei) ask a question for clarification Srinivas Garikipati (Nokia) responds to Fenqin Qian (Ericsson) indicates that this draft CR is high level introduction/description of the feature. we may need some further work on this to reduce the context. The other 3 draft CRs, included in 0224, 0764, cover already the needed actual changes needed for the work. ==== Revisions Deadline ==== | Noted |
| 30.2 | S2-2400791 | DISCUSSION | Discussion | Discussion Paper: 5GC Support of IoT NTN. | Vivo, China Telecom | Rel-19 | Noted | Haris(Qualcomm) comments Amy (vivo) replies to Haris (Qualcomm) and considers this TEI should be led by SA2. ==== Revisions Deadline ==== | Noted |
| 30.2 | S2-2400831 | DISCUSSION | Discussion | Discussion on introducing the indication of handover support between 3GPP and non-3GPP access . | China Telecom | Rel-19 | Noted | Noted | |
| 30.2 | S2-2400833 | DISCUSSION | Discussion | Subscription control for reference time distribution in EPS | Qualcomm, Vodafone | Rel-19 | Revision of (unhandled) S2-2312366. Noted | Noted | |
| 30.2 | S2-2400834 | WID NEW | Discussion | New WID on subscription control for reference time distribution in EPS. | Qualcomm | Rel-19 | Revision of (unhandled) S2-2312368. Postponed | Runze (Huawei) provides comments to the TEI-19 proposal. Sebastian (Qualcomm) replies Shabnam (Ericsson) provides comments Runze (Huawei) replies to Sebastian (Qualcomm) Yuan Tao (CATT) provides comments. Sebastian (Qualcomm) replies to Runze Sebastian (Qualcomm) replies to Shabnam Sebastian (Qualcomm) replies to Yuan Tao Runze (Huawei) replies to Sebastian (Qualcomm). ==== Revisions Deadline ==== Shabnam (Ericsson) provides comments that the WI is not ready for endorsement, need to resolve RAN aspects raised and document consequences. Yuan Tao (CATT) suggests postpone this TEI. The issues for legacy UE and RAN can be foreseen, so the coordination with RAN WG is possible needed to evaluate the reasonability. There are only two supporting companies in WID r00 (it is less than 4 companies). Chris (Vodafone) responds that broadcast of the existing SIB is optional so there cannot be legacy UE impact. While RAN implementation needs to decide between 'broadcast to all' and 'unicast to selected UEs', this is not RAN specification related (beyond S1AP codepoint). Runze (Huawei) replies to Chris (Vodafone). ==== Final Comments Deadline ==== | Postponed |
| 30.2 | S2-2400844 | DRAFTCR | Discussion | Subscription control for reference time delivery in EPS | Qualcomm Incorporated, Vodafone | Rel-19 | Revision of (unhandled) S2-2312370. Noted | Noted | |
| 30.2 | S2-2400847 | WID NEW | Approval | New TEI19-WID: Indication of Handover Support between 3GPP and non-3GPP access . | China Telecom | Rel-19 | Revision of (unhandled) S2-2311141. Postponed | Laurent (Nokia): Comments on the real benefits. Haris(Qualcomm) objects to the approval of this WI Yan Li (China Telecom) replies to Laurent (Nokia) Yan Li (China Telecom) replies to Haris (Qualcomm) Yan Li (China Telecom) combined another thread on the same topic to avoid forking, and provides r01 Laurent (Nokia): Comments: sorry new justification is unclear to me Haris(Qualcomm) disagrees with the justification and continues to object Yan Li (China Telecom) further clarifies, and replies to Laurent (Nokia) and Haris (Qualcomm) Mehrdad (MediaTek Inc.) thinks this TEI-19 WI needs more time for analyses and suggests to postpone. Leo (Deutsche Telekom) comments and suggests to postpone the proposal. ==== Revisions Deadline ==== Laurent (Nokia): cannot endorse or agree this proposal Yan Li (China Telecom) replies to Laurent (Nokia), Leo (Deutsche Telekom), and Mehrdad (MediaTek Inc.) Leo (Deutsche Telekom) thanks for feedback and proposes to POSTPONE the WID to the next SA2 meeting. ==== Final Comments Deadline ==== | Postponed |
| 30.2 | S2-2400864 | DRAFTCR | Information | Indication to the UE whether 3GPP and non-3GPP handover is supported | China Telecom | Rel-19 | Noted | Noted | |
| 30.2 | S2-2400870 | DRAFTCR | Information | Indication to the UE whether 3GPP and non-3GPP handover is supported | China Telecom | Rel-19 | Noted | Noted | |
| 30.2 | S2-2400873 | DRAFTCR | Information | Adding HO support indication between 3GPP and non-3GPP accesses | China Telecom | Rel-19 | Noted | Noted | |
| 30.2 | S2-2400888 | WID NEW | Information | New WID: Common EAS discovery and common DNAI determination for roaming UE (TEI19_CEaDRoam). | CATT (Rapporteur) | Rel-19 | Revision of (unhandled) S2-2312880. Noted | Yuan Tao (CATT) replies to Stefano (Qualcomm). Stefano (Qualcomm) suggests noting. Magnus (Ericsson) cannot accept this TEI Stefano (Qualcomm) responds with further questions. Magnus H (Ericsson) provides more comments Yuan Tao (CATT) replies to Magnus H (Ericsson). Yuan Tao (CATT) can't accept the reason of objection. This is not an official rule. We need unified rules to evaluate all the TEI. Yuan Tao (CATT) further replies to Stefano (Qualcomm). Stefano (Qualcomm) support Ericsson comment that the problem is not so realistic and there are more realistic scenarios that require a SID, and remain unconvinced. ==== Revisions Deadline ==== Yuan Tao (CATT) responds to Stefano (Qualcomm) this TEI intends to support an application available worldwide can be used by roaming UE. It is a very realistic scenario. ==== Final Comments Deadline ==== | Noted |
| 30.2 | S2-2400889 | DISCUSSION | Information | Common EAS discovery and common DNAI determination for roaming UE. | CATT | Rel-19 | Revision of (unhandled) S2-2312881. Noted | Noted | |
| 30.2 | S2-2400890 | DRAFTCR | Information | Common EAS discovery and common DNAI determination for roaming UE | CATT | Rel-19 | Revision of (unhandled) S2-2312882. Noted | Noted | |
| 30.2 | S2-2400891 | DRAFTCR | Information | Common EAS discovery and common DNAI determination for roaming UE | CATT | Rel-19 | Revision of (unhandled) S2-2312883. Noted | Noted | |
| 30.2 | S2-2400908 | WID NEW | Information | New TEI WID: URSP rule enhancements for advanced WLAN access selection (TEI19_URSP_WLAN). | Lenovo, InterDigital | Rel-19 | Not handled | Marco(Huawei) ask clarifications Yang (OPPO) has concern to the WID Laurent (Nokia): Comments: basically supporting Marco's point Belen (Ericsson) provides comments ==== Revisions Deadline ==== | Not Handled |
| 30.2 | S2-2400910 | DRAFTCR | Information | Draft CR: URSP rule enhancements for advanced WLAN access selection | Lenovo, InterDigital | Rel-19 | Not handled | Not Handled | |
| 30.2 | S2-2400932 | DISCUSSION | Information | Discussion on TEI19 WID proposal on UE Policy PCRT support in EPS (TEI19_UEPCRT_EPS). | Samsung | Rel-19 | Not handled | Not Handled | |
| 30.2 | S2-2400934 | WID NEW | Approval | New WID: UE Policy Control Trigger Request (PCRT) support in EPS (TEI19_UEPCRT_EPS). | Samsung | Rel-19 | Not handled | Not handled | |
| 30.2 | S2-2400936 | DRAFTCR | Information | UE Policy PCRT support in EPS | Samsung | Rel-19 | Not handled | Not Handled | |
| 30.2 | S2-2400938 | DRAFTCR | Information | UE Policy PCRT support in EPS | Samsung | Rel-19 | Not handled | Not Handled | |
| 30.2 | S2-2400950 | DRAFTCR | Information | Integration with Ethernet LAN via enhancements of 5G VN group data | Huawei, Hisilicon | Rel-19 | Not handled | Not Handled | |
| 30.2 | S2-2400951 | DRAFTCR | Information | Integration with Ethernet LAN via enhancements of 5G VN group data | Huawei, HiSilicon | Rel-19 | Not handled | Not Handled | |
| 30.2 | S2-2401096 | WID NEW | Approval | 5GS enhancement on On-demand broadcast of GNSS assistance data. | China Mobile | Rel-19 | r05 Agreed. Revised to S2-2401629. | Richard (Ericsson) provides comments and r01 Hong (Qualcomm) comments. Guanglei (Huawei) raise concerns on r01. Guanglei (Huawei) replies to Hong. Richard (Ericsson) provides additional comments Guanglei (Huawei) replies to Richard.. Aihua(CMCC) replies to the comments. Richard (Ericsson) responses to Aihua(CMCC) and Guanglei (Huawei) Aihua(CMCC) replies to the comment from Richard (Ericsson). Richard (Ericsson) answers to Aihua(CMCC) related to r01 Aihua(CMCC) replies to the comment from Richard (Ericsson) and provides r03. Richard (Ericsson) replies to Aihua(CMCC) Aihua(CMCC) replies to Richard (Ericsson) . Richard (Ericsson) providing r04 and Ericsson is added as Supporting company Aihua(CMCC) is fine with r04 provided by Richard (Ericsson). Hong (Qualcomm) provides r05. ==== Revisions Deadline ==== Aihua(CMCC) can live with r05 provided by Hong (Qualcomm). Guanglei (Huawei) supports r05 Richard (Ericsson) accepts r05 or r04 ==== Final Comments Deadline ==== | Revised |
| 30.2 | S2-2401629 | WID NEW | Approval | 5GS enhancement on On-demand broadcast of GNSS assistance data. | China Mobile | Rel-19 | Revision of S2-2401096r05. Endorsed | Endorsed | |
| 30.2 | S2-2401097 | WID NEW | Approval | 5GS enhancement on QoS monitoring enhancement. | China Mobile | Rel-19 | Revision of (unhandled) S2-2312442. CC#3: Postponed | Mengzhen (China Telecom) comments that the QoS monitoring capability negotiation and per packet monitoring are two different aspects. zhendong (ZTE) provides the clarification Laurent (Nokia): aks questions on the usefulness of WT1 and on scalability of WT2 Haiyang (Huawei) seeks for clarification Juan Zhang (Qualcomm) provides comments Lei (Tencent) provides clarification to Juan Zhang (Qualcomm) on QoS monitoring part of the TEI WID Aihua(CMCC) supports the view from Lei (Tencent) and provides further clarification to Juan Zhang (Qualcomm) on QoS monitoring part. zhendong (ZTE) provides the response Haiyang (Huawei) comments Juan Zhang (Qualcomm) provides comment. Aihua (CMCC) provides the clarifications to Laurent (Nokia). Hyunsook (LGE) asks clarifications on NF re-selection by QoS monitoring capability negotiation. Antoine (Orange) supports the 2nd objective. zhendong (ZTE) provides the r01 zhendong (ZTE) provides the response to juan(Qualcomm) zhendong (ZTE) provides the response to haiyang (huawei) Antoine (Orange) requests to add Orange and EDF as supporting compnies. zhendong (ZTE) provides the r02 Mengzhen (China Telecom) is OK with r02. Haiyang (Huawei) further comments Juan Zhang (Qualcomm) replies to Zhendong (ZTE) Ling (Siemens) asks for clarifications on justification part Paul (Ericsson) provides comments. Laurent (Nokia): in short the WT on per packet delay measurement requires a SID and not a TEI19 zhendong (ZTE) provides the r03 Aihua (CMCC) provides the response to Paul (Ericsson) . zhendong (ZTE) provides the response to laurent Hyunsook (LGE) provides some comments. Laurent (Nokia): Comments: this 'The CN needs to know the QoS monitoring capability of RAN' needs RAN3 blessing Xiaowan Ke(vivo) support 'QoS monitoring capability negotiation mechanism between RAN, UPF and SMF' and suggest to remove the 'QoS monitoring per data packet granularity' and postpone related CR Aihua (CMCC) responses to Hyunsook (LGE) , Laurent (Nokia) and Xiaowan(vivo), providing r04 . zhendong (ZTE) provides the r05 Paul (Ericsson) replies to Aihua. Lei(Tencent) provides comments Aihua (CMCC) provides the response to Juan Zhang (Qualcomm). Aihua (CMCC) provides r06 only with QoS Monitoring capability negotiation. Juan Zhang (Qualcomm) replies to Aihua (CMCC). Lei(Tencent) provides comments. Paul (Ericsson) we don't see need for this WID as WT1 is not needed due to selection of a RAN nodes is not possible and there is no need for the CN to be aware of RAN capabilities (CN learns by reception/lack of measurements) while WT2 lacks support by the UEs. Jinguo(ZTE) replies to Paul (Ericsson) that it is benefit that the SMF can know the RAN capability ==== Revisions Deadline ==== Aihua (CMCC) responses to Paul (Ericsson). Juan Zhang (Qualcomm) proposes to postpone the WID Lei (Tencent) provides comments to further explain the QoS monitoring capability negotiation iwithin 5GC and also between 5GC and NG-RAN. Aihua (CMCC) responses to Juan Zhang (Qualcomm). Aihua(CMCC) reponds to Juan(Qualcomm) and suggest to discuss this on CC#3 or CC#4 Laurent (Nokia): objects to this WID, Lei(Tencent) replies to Laurent (Nokia) that the r06 from Aihua has deleted the concerned part, i.e., only keep the remaining part, please double check Aihua(CMCC) reponds to Laurent (Nokia). Xiaowan Ke(vivo) replies to Laurent (Nokia). Paul (Ericsson) we object to this WID in all revisions based on comments provided earlier. Antoine (Orange): Orange does not support r06 because the 2nd objective is removed. | Postponed |
| 30.2 | S2-2401098 | WID NEW | Approval | TEI19 WID on Enhancement on NSSF service. | ZTE | Rel-19 | Postponed | Peter Hedman (Ericsson) provides question Myungjune (LGE) comments Alessio(Nokia) has similar comments as LG. proposes to note this TEI-19 proposal as it is not strictly necessary nor urgent Jinguo(ZTE) replies and think this TEI19 proposal is necessary. Myungjune (LGE) replies to Jinguo(ZTE). Jinguo(ZTE) replies to Myungjune(LGE) Peter Hedman (Ericsson) provides comments Jinguo(ZTE) replies to Peter Hedman (Ericsson) Alessio(Nokia) comments that given the amount of discussion there is no way we agree this at this meeting so we propose to note or postpone the paper and related CR at this meeting. Jinguo(ZTE) suggest to continue the discussion on technique aspect Myungjune (LGE) responds to Jinguo(ZTE) Jinguo(ZTE) replies to Myungjune (LGE) Jinguo(ZTE) replies to Myungjune (LGE) and Peter (Ericsson), provides r01 Myungjune (LGE) replies to Jinguo (ZTE) . Peter Hedman (Ericsson) provides question again what is the problem caused Myungjune (LGE) asks question Peter Hedman (Ericsson) provides comments and propose to postpone Myungjune(LGE) replies to Jinguo(ZTE) Myungjune(LGE) replies to Jinguo (ZTE) . ==== Revisions Deadline ==== Jinguo(ZTE) is ok to postpone. ==== Final Comments Deadline ==== | Postponed |
| 30.2 | S2-2401099 | DRAFTCR | Decision | Support of Slice mapping information notification from NSSF | ZTE | Rel-19 | Noted | Noted | |
| 30.2 | S2-2401134 | WID NEW | Approval | New WID on 5G VN integration with Ethernet LAN. | Huawei, HiSilicon | Rel-19 | Not handled | Not Handled | |
| 30.2 | S2-2401161 | WID NEW | Approval | New WID on Source Traffic Descriptors for URSP. | Siemens AG | Rel-19 | Not handled | Marco(Huawei) asks clarifications Yang (OPPO) comments ==== Revisions Deadline ==== Ling (Siemens) replied to the comments and provides r01 | Not Handled |
| 30.2 | S2-2401167 | DRAFTCR | Agreement | URSP Rule Traffic descriptor components for differentiating the 5G traffic | Siemens AG | Rel-19 | Not handled | Not Handled | |
| 30.2 | S2-2401183 | WID NEW | Approval | New WID: Generic Use of Service Level Authorization and Authentication Procedure (TEI19_GUSLAP). | Qualcomm (Rapporteur) | Rel-19 | Not handled | Not Handled | |
| 30.2 | S2-2401184 | DISCUSSION | Discussion | Generic use of service-level-AA procedure | QUALCOMM Europe Inc. - Spain | Rel-19 | Not handled | Not Handled | |
| 30.2 | S2-2401186 | CR | Approval | 23.501 CR5294 (Rel-19, 'B'): Support of generic service level AA procedure | Qualcomm Incorporated | Rel-19 | Check WI Code (TEI19GUSLAP)! Not handled | - | |
| 30.2 | S2-2401187 | CR | Approval | 23.502 CR4729 (Rel-19, 'B'): Support of generic service level AA procedure | Qualcomm Incorporated | Rel-19 | Not handled | - | |
| 30.2 | S2-2401267 | WID NEW | Approval | TEI19 on enabling Multiple Location Procedure for Emergency LCS Routing . | Nokia, Nokia Shanghai Bell | Rel-19 | Not handled | Not Handled | |
| 30.2 | S2-2401268 | DISCUSSION | Discussion | Multiple location procedure for Next Generation Emergency Routing. | Nokia, Nokia Shanghai Bell | Rel-19 | Not handled | Not Handled | |
| 30.2 | S2-2401293 | CR | Approval | 23.273 CR0502 (Rel-19, 'B'): Multiple Location Report for Next Generation Emergency Routing | Nokia, Nokia Shanghai Bell | Rel-19 | Not handled | Stephen (Qualcomm) comments ==== Revisions Deadline ==== | - |
| 30.2 | S2-2401306 | WID NEW | Approval | TEI19 WID on support for ProSe services in NPNs. | Philips International B.V. | Rel-19 | Not handled | Not Handled | |
| 30.2 | S2-2401307 | DISCUSSION | Information | Discussion on TEI19 support for ProSe in NPNs. | Philips International B.V. | Rel-19 | Not handled | Not Handled | |
| 30.2 | S2-2401308 | DRAFTCR | Information | TS 23.501 draft CR for ProSe support for NPNs | Philips International B.V. | Rel-19 | Not handled | Not Handled | |
| 30.2 | S2-2401309 | DRAFTCR | Information | TS 23.304 draft CR for ProSe support for NPNs | Philips International B.V. | Rel-19 | Not handled | Not Handled | |
| 30.2 | S2-2401358 | WID NEW | Discussion | Draft New WID: TEI19_TPlmnNfSel; NF discovery and selection by target PLMN. | Nokia, Nokia Shanghai Bell (Rapporteur) | Rel-19 | Revision of (unhandled) S2-2312584. Postponed | Juan Zhang (Qualcomm) provides comments ==== Revisions Deadline ==== Juan Zhang (Qualcomm) proposes to postpone the WID. Thomas(Nokia) agrees to postpone the WID. ==== Final Comments Deadline ==== | Postponed |
| 30.2 | S2-2401360 | DRAFTCR | Information | NF discovery and selection by target PLMN | Nokia, Nokia Shanghai-Bell | Rel-19 | Revision of (unhandled) S2-2312585. Noted | Magnus (Ericsson) cannot accept the solution Thomas (Nokia) suggest focusing on the WID. The draft CR is only for information Fenqin (Huawei) ask a question for clarification Magnus H (Ericsson) provides comments Thomas(Nokia) replies to Fenqin and Magnus Jicheol (Samsung) proposes to postpone this WID. ==== Revisions Deadline ==== Magnus H (Ericsson) Objects to the this draft-CR | Noted |
| 30.2 | S2-2401361 | DRAFTCR | Information | NF discovery and selection by target PLMN | Nokia, Nokia Shanghai-Bell | Rel-19 | Revision of (unhandled) S2-2312586. Noted | Magnus (Ericsson) same comment as on 1360 Thomas (Nokia) suggest focusing on the WID. The draft CR is only for information Fenqin (Huawei) same question as in 1360 Thomas(Nokia) points Fenqin to his reply in the 1360 thread and suggest continuing only in one PCR thread and mainly in the WID thread ==== Revisions Deadline ==== Magnus H (Ericsson) objects to this draft-CR | Noted |
| 30.2 | S2-2401363 | WID NEW | Approval | New WID: TEI19 UE assisted Enforceable URSP Rules Provisioning. | Apple | Rel-19 | Source should be Google! Not handled | Antoine (Orange) comments that the problem description is incorrect. Srinivas Garikipati (Nokia) proposes to note this WID. Susana (Vodafone) agrees with Antoine and proposes to note Yang (OPPO) supports the idea of the WID proposal and comments Antoine (Orange) replies to Yang. Yang (OPPO) replies to Antoine ==== Revisions Deadline ==== | Not Handled |
| 30.2 | S2-2401364 | CR | Approval | 23.502 CR4740 (Rel-19, 'B'): UE assisted for Enforceable URSP rules provisioning | Rel-19 | Check WI Code! Not handled | - | ||
| 30.3 | - | - | - | Rel-19 TR and TS Cover sheets | - | - | Docs:=0 | - | |
| 30.4 | - | - | - | Rel-18 WID Status Reports | - | - | Docs:=0 | - | |
| 30.5 | - | - | - | Rel-19 WID Status Reports | - | - | Docs:=15 | - | |
| 30.5 | S2-2401660 | WI STATUS REPORT | Information | WI Status Report for Study on Energy Efficiency and Energy Saving (FS_EnergySys) | FS_EnergySys Rapporteur (Samsung) | Rel-19 | Noted | Noted | |
| 30.5 | S2-2401661 | WI STATUS REPORT | Information | WI Status Report for Study on Core Network Enhanced Support for Artificial Intelligence (AI)/Machine Learning (ML) (FS_AIML_CN) | FS_AIML_CN Rapporteur (vivo) | Rel-19 | Noted | Noted | |
| 30.5 | S2-2401662 | WI STATUS REPORT | Information | WI Status Report for Study on Architecture support of Ambient power-enabled Internet of Things (FS_AmbientIoT) | FS_AmbientIoT Rapporteur (Huawei) | Rel-19 | Noted | Noted | |
| 30.5 | S2-2401663 | WI STATUS REPORT | Information | WI Status Report for Study on Integration of satellite components in the 5G architecture Phase 3 (FS_5GSAT_Ph3_ARCH) | FS_5GSAT_Ph3_ARCH Rapporteur (Thales) | Rel-19 | Noted | Noted | |
| 30.5 | S2-2401664 | WI STATUS REPORT | Information | WI Status Report for Study on Extended Reality and Media service (XRM) Phase 2 (FS_XRM_Ph2) | FS_XRM_Ph2 Rapporteur (Nokia) | Rel-19 | Noted | Noted | |
| 30.5 | S2-2401665 | WI STATUS REPORT | Information | WI Status Report for Study on (Stage 2 of) Phase 3 for UAS, UAV and UAM (FS_UAS_Ph3) | FS_UAS_Ph3 Rapporteur (LG Electronics) | Rel-19 | Noted | Noted | |
| 30.5 | S2-2401666 | WI STATUS REPORT | Information | WI Status Report for Study on Multi-Access (DualSteer and ATSSS_Ph4) (FS_MASSS) | FS_MASSS Rapporteur (Apple) | Rel-19 | Noted | Noted | |
| 30.5 | S2-2401667 | WI STATUS REPORT | Information | WI Status Report for Study on Enhancement of support for Edge Computing in 5G Core network - Phase 3 (FS_eEDGE_5GC_Ph3) | FS_eEDGE_5GC_Ph3 Rapporteur (Intel) | Rel-19 | Noted | Noted | |
| 30.5 | S2-2401668 | WI STATUS REPORT | Information | WI Status Report for Study on System aspects of 5G NR Femto (FS_5G_Femto) | FS_5G_Femto Rapporteur (NTT DOCOMO) | Rel-19 | Noted | Noted | |
| 30.5 | S2-2401669 | WI STATUS REPORT | Information | WI Status Report for Study on Proximity-based Services in 5GS Phase 3 (FS_5G_ProSe_Ph3) | FS_5G_ProSe_Ph3 Rapporteur (AT&T) | Rel-19 | Noted | Noted | |
| 30.5 | S2-2401670 | WI STATUS REPORT | Information | WI Status Report for Study on Vehicle Mounted Relays Phase 2 (FS_VMR_Ph2) | FS_VMR_Ph2 Rapporteur (Qualcomm) | Rel-19 | Noted | Noted | |
| 30.5 | S2-2401671 | WI STATUS REPORT | Information | WI Status Report for Study on User Identities and Authentication Architecture (FS_UIA_ARC) | FS_UIA_ARC Rapporteur (nterdigital) | Rel-19 | Noted | Noted | |
| 30.5 | S2-2401672 | WI STATUS REPORT | Information | WI Status Report for Study on UPF enhancement for Exposure And SBA Phase 2 (FS_UPEAS_Ph2) | FS_UPEAS_Ph2 Rapporteur (ZTE) | Rel-19 | Noted | Noted | |
| 30.5 | S2-2401673 | WI STATUS REPORT | Information | WI Status Report for Study on system architecture for next generation real time communication services phase 2 (FS_NG_RTC_Ph2) | FS_NG_RTC_Ph2 Rapporteur (China Mobile) | Rel-19 | Noted | Noted | |
| 30.5 | S2-2401674 | WI STATUS REPORT | Information | WI Status Report for Study on MPS for IMS Messaging and SMS services (FS_MPS4msg) | FS_MPS4msg Rapporteur (Peraton Labs) | Rel-19 | Noted | Noted | |
| 30.6 | - | - | - | Review of the Work Plan | - | - | Docs:=2 | - | |
| 30.6 | S2-2400761 | WORK PLAN | Endorsement | SA WG2 Work Planning | SA WG2 Chair | Noted | ==== Final Comments Deadline ==== | Noted | |
| 30.6 | S2-2400767 | WORK PLAN | Endorsement | SA WG2 Work Plan - TU planning | SA WG2 Chair | Noted | ==== Final Comments Deadline ==== | Noted | |
| 30.7 | - | - | - | Planning future meetings | - | - | Docs:=0 | - | |
| 31 | - | - | - | Close of meeting | - | - | Docs:=0 | - | |
| 99 | - | - | - | Withdrawn and Reserved documents | - | - | Docs:=123 | - | |
| 99 | S2-2401242 | WID NEW | Approval | New WID on immediate EIR reporting of PEI status change. | Nokia, Nokia Shanghai Bell | Rel-19 | WITHDRAWN | Withdrawn | |
| 99 | S2-2401243 | DRAFTCR | Agreement | Immediate EIR reporting of PEI status change | Nokia, Nokia Shanghai Bell | Rel-19 | WITHDRAWN | Withdrawn | |
| 99 | S2-2400076 | CR | Approval | 23.304 CR0408 (Rel-18, 'F'): Clarification on Cell Reporting in multi-path L2 U2N case | Nokia, Nokia Shanghai Bell | Rel-18 | WITHDRAWN | Withdrawn | |
| 99 | S2-2400082 | DISCUSSION | Discussion | Considerations for AIoT NW Architecture | Wiliot Ltd. | WITHDRAWN | Withdrawn | ||
| 99 | S2-2400104 | CR | Approval | 23.501 CR5212 (Rel-18, 'F'): KI#3 Clarifications related to the scenario when the PDN connection handlig the UE Policy Container is released | Nokia, Nokia Shanghai Bell | Rel-18 | WITHDRAWN | Withdrawn | |
| 99 | S2-2400105 | CR | Approval | 23.503 CR1237 (Rel-18, 'F'): KI#2 Clarification to URSP rule enforcement reporting. | Nokia, Nokia Shanghai Bell | Rel-18 | WITHDRAWN | Withdrawn | |
| 99 | S2-2400106 | CR | Approval | 23.501 CR5213 (Rel-18, 'F'): KI#5 Corrections on Proactive RAN Feedback and TSN enabled TN | Nokia, Nokia Shanghai Bell | Rel-18 | WITHDRAWN | Withdrawn | |
| 99 | S2-2400183 | CR | Approval | 23.288 CR0938R1 (Rel-18, 'F'): Use of ML Model Interoperability Indicator and Vendor ID in Discovery | Ericsson | Rel-18 | Revision of (unhandled) S2-2310373. Revised to S2-2401053. WITHDRAWN | Withdrawn | |
| 99 | S2-2400212 | CR | Approval | 23.501 CR5218 (Rel-18, 'B'): Data size handling in AMF update | Ericsson | Rel-18 | WITHDRAWN | Withdrawn | |
| 99 | S2-2400238 | WID NEW | Approval | TEI19_Roaming traffic offloading via home-session breakout | SK Telecom | Rel-19 | WITHDRAWN | Withdrawn | |
| 99 | S2-2400260 | DRAFTCR | Information | TEI19_draftCR_23501_HR-HSBO_H-UPF selection | SK Telecom | Rel-19 | WITHDRAWN | Withdrawn | |
| 99 | S2-2400261 | DISCUSSION | Information | TEI19_Discussion on roaming traffic offloading via home-session breakout | SK Telecom | Rel-19 | WITHDRAWN | Withdrawn | |
| 99 | S2-2400324 | P-CR | Approval | 23.700-66: KI#3, New Sol: Location based EE/EC analytics | KDDI, TOYOTA MOTOR CORPORATION | Rel-19 | WITHDRAWN | Withdrawn | |
| 99 | S2-2400328 | P-CR | Approval | 23.700-49: Architecture assumption and requirement | China Mobile | Rel-19 | WITHDRAWN | Withdrawn | |
| 99 | S2-2400359 | CR | Approval | 23.288 CR0938R2 (Rel-18, 'F'): Security Corrections | Ericsson | Rel-18 | WITHDRAWN | Withdrawn | |
| 99 | S2-2400393 | CR | Approval | 23.401 CR3763 (Rel-18, 'F'): CR 23.401-3761 rev 1: NB-IoT NTN: UE Coarse Location Information Reporting | MediaTek Inc., Airbus, CEWiT, Deutsche Telekom, Echostar, ESA, Gatehouse, Inmarsat/Viasat, JSAT, Ligado, Lockheed Martin, Novamint, OQ Technology, Reliance Jio, Sateliot, Skylo, Thales, TNO, vivo | Rel-18 | WITHDRAWN | Withdrawn | |
| 99 | S2-2400396 | CR | Approval | 23.502 CR4683 (Rel-18, 'F'): Clarify validity information for network access control | MediaTek Inc., Futurewei | Rel-18 | WITHDRAWN | Withdrawn | |
| 99 | S2-2400397 | P-CR | Approval | 23.700-66: URSP rules and slice with the validity information generation based on energy related information | MediaTek Inc. | Rel-19 | WITHDRAWN | Withdrawn | |
| 99 | S2-2400398 | P-CR | Approval | 23.700-66: Update to scope and definition for concept of energy saving and carbon emission | MediaTek Inc. | Rel-19 | WITHDRAWN | Withdrawn | |
| 99 | S2-2400399 | P-CR | Approval | 23.700-84: FS_AIML_CN TR 23.700-84 Skeleton | MediaTek Inc. (Rapporteur), vivo (Rapporteur) | Rel-19 | WITHDRAWN | Withdrawn | |
| 99 | S2-2400400 | P-CR | Approval | 23.700-84: 23.700-84: Architecture Requirements for FS_AIML_CN | MediaTek Inc. (Rapporteur), vivo (Rapporteur) | Rel-19 | WITHDRAWN | Withdrawn | |
| 99 | S2-2400401 | P-CR | Approval | 23.700-84: 23.700-84: Architecture Assumptions for FS_AIML_CN | MediaTek Inc. (Rapporteur), vivo (Rapporteur) | Rel-19 | WITHDRAWN | Withdrawn | |
| 99 | S2-2400425 | P-CR | Approval | 23.700-75: Solution for IMS for MPS for messaging - General | Peraton Labs, CISA ECD | Rel-19 | WITHDRAWN | Withdrawn | |
| 99 | S2-2400426 | P-CR | Approval | 23.700-75: Solution for IMS for MPS for messaging - Invocation | Peraton Labs, CISA ECD | Rel-19 | WITHDRAWN | Withdrawn | |
| 99 | S2-2400427 | P-CR | Approval | 23.700-75: Solution for IMS for MPS for messaging - Procedures | Peraton Labs, CISA ECD | Rel-19 | WITHDRAWN | Withdrawn | |
| 99 | S2-2400439 | SID REVISED | Approval | New SID on Proximity-based Services in 5GS - Phase 3 | AT&T | Rel-19 | WITHDRAWN | Withdrawn | |
| 99 | S2-2400467 | CR | Approval | 23.501 CR5234 (Rel-18, 'D'): Cleaning up the term of RFSP Index in Use Validity Time | China Telecom Corporation Ltd. | Rel-18 | WITHDRAWN | Withdrawn | |
| 99 | S2-2400468 | CR | Approval | 23.288 CR1033 (Rel-18, 'F'): Alignment of unclear description of 3DA Data Management Service | ZTE | Rel-18 | WITHDRAWN | Withdrawn | |
| 99 | S2-2400469 | CR | Approval | 23.288 CR1034 (Rel-18, 'F'): Clarification of federated learning process | ZTE | Rel-18 | WITHDRAWN | Withdrawn | |
| 99 | S2-2400470 | CR | Approval | 23.288 CR1035 (Rel-18, 'F'): Clarification on output strategy in output information of analytic | ZTE | Rel-18 | WITHDRAWN | Withdrawn | |
| 99 | S2-2400471 | CR | Approval | 23.288 CR1036 (Rel-18, 'F'): Wrong reference number of other specification | ZTE | Rel-18 | WITHDRAWN | Withdrawn | |
| 99 | S2-2400536 | P-CR | Approval | 23.700-77: New solution on standalone IMS DC sessions | Qualcomm Incorporated | Rel-19 | WITHDRAWN | Withdrawn | |
| 99 | S2-2400552 | P-CR | Approval | 23.700-54: FS_MASSS_TR23700-54_Term | China Telecom Corporation Ltd. | Rel-19 | WITHDRAWN | Withdrawn | |
| 99 | S2-2400577 | P-CR | Approval | 23.700-29: KI#2, New Sol: on S&F architecture support in 5GS | OPPO | Rel-19 | WITHDRAWN | Withdrawn | |
| 99 | S2-2400607 | CR | Approval | 23.501 CR5247 (Rel-18, 'F'): Clean up and alignment for TRS monitoring and reporting, correction to ASTI without AF request | Nokia, Nokia Shanghai Bell | Rel-18 | WITHDRAWN | Withdrawn | |
| 99 | S2-2400827 | CR | Approval | 23.586 CR0104 (Rel-18, 'F'): Updates to SL-MO-LR and SL-MT-LR | vivo | Rel-18 | WITHDRAWN | Withdrawn | |
| 99 | S2-2400875 | P-CR | Approval | 23.700-66: TR 23.700-66, New Solution for KI#1: Network energy related information exposure | IPLOOK | Rel-19 | WITHDRAWN | Withdrawn | |
| 99 | S2-2400902 | CR | Approval | 23.501 CR5268 (Rel-18, 'B'): Update to Support Network Controlled Repeater | ZTE | Rel-18 | WITHDRAWN | Withdrawn | |
| 99 | S2-2400903 | CR | Approval | 23.502 CR4715 (Rel-18, 'B'): Update to Support Network Controlled Repeater | ZTE | Rel-18 | WITHDRAWN | Withdrawn | |
| 99 | S2-2400949 | WID NEW | Discussion | WID on 5G VN integration with Ethernet LAN | Huawei, HiSilicon | Rel-19 | WITHDRAWN | Withdrawn | |
| 99 | S2-2400952 | CR | Approval | 23.501 CR5274 (Rel-18, 'F'): Default Subscribed S-NSSAIs for Network Slice usage monitoring | NTT DOCOMO | Rel-18 | WITHDRAWN | Withdrawn | |
| 99 | S2-2400953 | CR | Approval | 23.501 CR5275 (Rel-18, 'F'): Network slice usage control in case of emergency call alt1 | NTT DOCOMO | Rel-18 | WITHDRAWN | Withdrawn | |
| 99 | S2-2400954 | CR | Approval | 23.501 CR5276 (Rel-18, 'F'): Network slice usage control in case of emergency call alt2 | NTT DOCOMO | Rel-18 | WITHDRAWN | Withdrawn | |
| 99 | S2-2401031 | CR | Approval | 23.502 CR4720 (Rel-18, 'F'): Removal of the option to use TSCTSF | NTT DOCOMO | Rel-18 | WITHDRAWN | Withdrawn | |
| 99 | S2-2401055 | P-CR | Approval | 23.700-84: New use case for WT#3.2: NWDAF enhancements to support network abnormal behaviours. | Tencent, Tencent Cloud | Rel-19 | Revised to S2-2401185. WITHDRAWN | Withdrawn | |
| 99 | S2-2401089 | WID NEW | Approval | TEI19 on 5GS enhancement on On-demand broadcast of GNSS assistance data | CMDI | WITHDRAWN | Withdrawn | ||
| 99 | S2-2401090 | WID NEW | Approval | TEI19 on 5GS enhancement on On-demand broadcast of GNSS assistance data | CMDI | WITHDRAWN | Withdrawn | ||
| 99 | S2-2401091 | WID NEW | Approval | TEI19 on 5GS enhancement on On-demand broadcast of GNSS assistance data | CMDI | Rel-19 | WITHDRAWN | Withdrawn | |
| 99 | S2-2401092 | WID NEW | Approval | TEI19 on 5GS enhancement on On-demand broadcast of GNSS assistance data | CMDI | Rel-19 | WITHDRAWN | Withdrawn | |
| 99 | S2-2401093 | WID NEW | Approval | TEI19 on 5GS enhancement on On-demand broadcast of GNSS assistance data | CMDI | Rel-19 | WITHDRAWN | Withdrawn | |
| 99 | S2-2401094 | WID NEW | Approval | TEI19 on 5GS enhancement on On-demand broadcast of GNSS assistance data | CMDI | Rel-19 | WITHDRAWN | Withdrawn | |
| 99 | S2-2401095 | WID NEW | Approval | TEI19 on 5GS enhancement on On-demand broadcast of GNSS assistance data | CMDI | Rel-19 | WITHDRAWN | Withdrawn | |
| 99 | S2-2401223 | CR | Approval | 23.502 CR4667R3 (Rel-18, 'F'): Clarifications on processing AF request for HR-SBO session | Nokia, Nokia Shanghai Bell | Rel-18 | WITHDRAWN | Withdrawn | |
| 99 | S2-2401261 | CR | Approval | 23.586 CR0115 (Rel-18, 'F'): Update to Ranging/SL Positioning service exposure through control plane | Xiaomi | Rel-18 | WITHDRAWN | Withdrawn | |
| 99 | S2-2401266 | CR | Approval | 23.273 CR0500 (Rel-19, 'B'): MLR for NG emergency routing | Nokia, Nokia Shanghai Bell | Rel-19 | WITHDRAWN | Withdrawn | |
| 99 | S2-2401279 | P-CR | Approval | 23.700-84: Proposed key issue for WT#1.4 | Nokia, Nokia Shanghai Bell | Rel-19 | Revised to S2-2401297. WITHDRAWN | Withdrawn | |
| 99 | S2-2401292 | CR | Approval | 23.273 CR0501 (Rel-19, 'B'): MLR for NG emergency routing | Nokia, Nokia Shanghai Bell | Rel-19 | WITHDRAWN | Withdrawn | |
| 99 | S2-2401294 | CR | Approval | 23.503 CR1236R3 (Rel-18, 'F'): Clarification on UE reporting URSP rule enforcement | Apple, Google | Rel-18 | WITHDRAWN | Withdrawn | |
| 99 | S2-2401296 | P-CR | Approval | 23.700-84: Proposed key issue for WT#2 | Nokia, Nokia Shanghai Bell | Rel-19 | WITHDRAWN | Withdrawn | |
| 99 | S2-2401341 | CR | Approval | 23.501 CR5306 (Rel-16, 'F'): Providing TSCAI to NG-RAN during Xn handovers | Qualcomm | Rel-16 | WITHDRAWN | Withdrawn | |
| 99 | S2-2401357 | CR | Approval | 23.501 CR5307 (Rel-18, 'F'): Corrections to SNPN selection procedure for Localized Services | Samsung | Rel-18 | WITHDRAWN | Withdrawn |