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-2200001 | AGENDA | Approval | SA WG2 #149E Meeting Agenda | SA WG2 Chair | Approved | Approved | ||
| 2.1 | - | - | - | IPR Call and Antitrust Reminder | - | - | Docs:=0 | - | |
| 3 | - | - | - | SA2#148E Meeting report | - | - | Docs:=1 | - | |
| 3 | S2-2200002 | REPORT | Approval | Auto-Generated Report of SA WG2 meeting #148E | SA WG2 Secretary | Approved | Approved | ||
| 4 | - | - | - | General | - | - | Docs:=0 | - | |
| 4.1 | - | - | - | Common issues and Incoming LSs | - | - | Docs:=51 | - | |
| 4.1 | S2-2200008 | LS In | Action | LS from CT WG3: LS on PDU Session ID assignment for the Interworking scenario | CT WG3 (C3-214527) | Rel-17 | Revision of Postponed S2-2108267 from S2#148E. Responses drafted in S2-2200113 and S2-2200311. Final response in S2-2201271 | ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Replied to |
| 4.1 | S2-2200113 | LS OUT | Approval | [DRAFT] LS on PDU Session ID assignment for the Interworking scenario | Nokia, Nokia Shanghai Bell | Rel-17 | Response to S2-2200008. r00 agreed. Revised to S2-2201271, merging S2-2200311 | Judy (Ericsson) is OK to take 0113 as the baseline for the LS out as proposed by Laurent, assuming that 0310 is taken as baseline for CR. Laurent (Nokia): Suggests to take 0113 as the baseline for the LS out, merging 0311 in 0113 Fabio Giust (Nokia): Nokia provides r01 ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Revised |
| 4.1 | S2-2201271 | LS OUT | Approval | LS on PDU Session ID assignment for the Interworking scenario | SA WG2 | Rel-17 | Revision of S2-2200113r00, merging S2-2200311. Approved | Approved | |
| 4.1 | S2-2200311 | LS OUT | Approval | [DRAFT] Rely to LS on PDU Session ID assignment for the Interworking scenario | Ericsson | Rel-17 | Response to S2-2200008. Merged into S2-2201271 | Laurent (Nokia): Suggests to take 0113 as the baseline for the LS out, merging 0311 in 0113 ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Merged |
| 4.1 | S2-2200023 | LS In | Action | LS from RAN WG3: Reply to Reply LS On ACL support for Indirect Data Forwarding | RAN WG3 (R3-216140) | Rel-16 | Revision of Postponed S2-2109007 from S2#148E. Response drafted in S2-2200340. Final response in S2-2201272 | ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Replied to |
| 4.1 | S2-2200340 | LS OUT | Approval | [DRAFT] Reply LS on ACLIndirectForwarding | Ericsson | Rel-16 | Response to S2-2200023. r06 agreed. Revised to S2-2201272. | Fenqin (Huawei) comment and provides r01. Laurent (Nokia): provides r02 Qian (Ericsson) provides comments and r03. Juan Zhang (Qualcomm) provides comment and r04. Fenqin (Huawei) comment and provides r05. Laurent (Nokia): provides r06 Qian (Ericsson) provides comments on r06. Fenqin (Huawei) comment. Laurent (Nokia): answers Fenqin (Huawei) provides r07. Qian (Ericsson) provides r08. ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== Qian (Ericsson) proposes to go with r08, can live with r06 as well. Juan Zhang (Qualcomm) is OK with r06 and r08.. Laurent (Nokia): objects to R08, can live with R06 or R07 ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Revised |
| 4.1 | S2-2201272 | LS OUT | Approval | Reply LS On ACL support for Indirect Data Forwarding | SA WG2 | Rel-16 | Revision of S2-2200340r06. Approved | Approved | |
| 4.1 | S2-2200035 | LS In | Information | LS from GSMA ESTF: LS informing partner groups of ESTF creation | GSMA ESTF (ESTF 02_102) | Noted | Leo (Deutsche Telekom) proposes to note the LS from GSMA ESTF. ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Noted | |
| 4.1 | S2-2200036 | LS In | Information | LS from BBF: Alignment concerning 5G RG requirements and its remote management | Broadband Forum (LIAISE-483) | Noted | Dieter (Deutsche Telekom) Do we need to send an answer to this LS? ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== Tao (VC) check views whether we need to answer. Otherwise, suggest to Note it. ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Noted | |
| 4.1 | S2-2200037 | LS In | Information | LS from IEEE 802.1 Working Group: Liaison response to work items related to deterministic communication in ITU-T SG13 | IEEE 802.1 Working Group (liaison-response-itu-t-SG13-LS217-determcommunics-) | Noted | Shabnam (Ericsson) LS can be noted as for information about work that has been and being done in IEEE and 3GPP. ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Noted | |
| 4.1 | S2-2200053 | LS In | Action | LS from CT WG4: Reply LS on ACL support for Indirect Data Forwarding | CT WG4 (C4-216377) | Noted | Fenqin (Huawei) suggest to reply this LS in 0340. ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== Qian (Ericsson) proposes to NOTE this since 0340 replied to this. ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Noted | |
| 4.1 | S2-2200054 | LS In | Action | LS from CT WG4: Reply LS on Support of Asynchronous Type Communication in N1N2MessageTransfer | CT WG4 (C4-216381) | Rel-17 | Responses drafted in S2-2200282 and S2-2201011. CC#2: This LS was postponed. | ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Postponed |
| 4.1 | S2-2200282 | LS OUT | Approval | [DRAFT] Reply LS on Support of Asynchronous Type Communication in N1N2MessageTransfer | Huawei, HiSilicon | Rel-17 | Response to S2-2200054. CC#2: This LS was noted | Hannu (Nokia) proposes to use S2-2201011 instead of this draft LS as the basis for SA2 reply. Qian (Ericsson) provides comments. Haris(Qualcomm) comments that the justification for ATC used in PMIC is not correct and configuration to use/not use ATC based on DNN/S-NSSAI is rudimentary and not so practical Haiyang (Huawei) responds to Haris (Qualcomm) Hannu (Nokia) supports the views of Haris and Qian and replies to Haiyang (Huawei). Saso (Intel) supports the LS reply in 1011 and the removal of the ATC functionality from the specification. Sang-Jun (Samsung) supports the LS reply in 0282 and objects to the removal of the ATC functionality from the specification. Qian (Ericsson) asks a question. Hannu (Nokia) provides r01 to reduce the SA2 reply to what can be decided in the meeting. Can agree either S2-2201011 or S2-2200282r01 but not the original version of S2-2200282. Haiyang (Huawei) comments that r01 brings no valuable info to CT4. And provide r02 as comprimise. Hannu (Nokia) can't agree that r02 represents a compromise as it fails to consider the feedback that has been given in this meeting on the proposed responses to CT4. Provides r03, can live with also r01 but r02 is not acceptable. Haiyang (Huawei) provides r04. Haris(Qualcomm) comments that r02 is incorrect Hannu (Nokia) shares the view of Haris(Qualcomm) that r02 is not accurate representation of SA2 opinion or SA2 specifications. Proposes r03 instead. Hannu (Nokia) can't accept r04 as it fails to reflect SA2 specifications and the technical discussion in the meeting. Proposes to agree r03. Haiyang (Huawei) comments. ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== Haiyang (Huawei) is OK with r00, r01, and r04. Cannot accept r01 and r03. Tao (VC) guess haiyang means ok with r00, r02 and r04 Haiyang (Huawei) confirm OK with r00, r02, and r04 Haris(Qualcomm) comments that only r01 reflects reality based on existing specifications, therefore objects to all other versions Hannu (Nokia) replies to Haiyang (Huawei). Nokia can support only r01 and r03. Sang-Jun (Samsung) supports r04, and objects to r03. Tao(VC) it reads no agreeable version so far. Qian (Ericsson) comments that it is meaningless to send back a LS response to CT4 without any conclusion. We can NOTE this paper and go back to 1011. If we don't have a valid use case, we removed it which is not really a proper/workable feature. ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Noted |
| 4.1 | S2-2201011 | LS OUT | Approval | [DRAFT] Reply LS on support of Asynchronous Type Communication in N1N2MEssageTransfer | Nokia, Nokia Shanghai Bell | Rel-17 | Response to S2-2200054. Noted | Haiyang (Huawei) comments and suggests to go with 0282. Hannu (Nokia) points out that SA2 and CT4 haven't found any valid use case for ATC procedure and provides r02 proposing to use this LS version and the related CRs. Qian (Ericsson) supports the view from Nokia that no use case has been found for the usage of ATC and also indicates that the current ATC function is not workable. Haiyang (Huawei) comments. Hannu (Nokia) replies to Haiyang (Huawei) pointing out that no valid use case has been identified for ATC in SA2 or CT4. Haiyang (Huawei) replies to Hannu (Nokia) Chunshan (CATT) points out there are use cases in S2-2106421 proposed by nokia. Sang-Jun (Samsung) supports the LS reply in 0282 and objects to the removal of the ATC functionality from the specification. Haris(Qualcomm) comments Hannu (Nokia) thanks for good observation on Nokia proposal that sadly wasn't agreed but points out the requirement is different and ATC does not apply even if the former Nokia CR was agreed. Haiyang (Huawei) suggest to note this LS and discuss in 0282 thread as revisions already provided in that thread ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== Hannu (Nokia) agrees to note this LS and to focus the discussion on S2-2200282. But Nokia can't agree with the original contents of 282, so revision r01 or r03 of 282 is needed. Qian (Ericsson) propose to go with r01 since the 0282 r01/r03 does not provide any conclusion which can help CT4. If we don't have a valid use case, we remove the feature which is not really a proper/workable feature. Qian (Ericsson) asks this to be discussed in CC#2, if the author, Hannu (Nokia), agrees. ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== Hannu (Nokia) agrees to discuss this LS out as it is still in my view technically the most correct. I only provided S2-2200282r03 as possible Plan B in case no other LS can be sent. | Noted |
| 4.1 | S2-2200055 | LS In | Information | LS from CT WG4: Reply LS On Source IP address clarifications | CT WG4 (C4-216388) | Rel-16 | Noted | ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Noted |
| 4.1 | S2-2200063 | LS In | Information | LS from SA WG1: LS on Emergency Communication Improvement | SA WG1 (S1-214240) | Noted | Leo (Deutsche Telekom) proposes to note the contribution. ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Noted | |
| 4.1 | S2-2200411 | LS In | Action | LS from GSMA NRG: LS reply from NRG to 3GPP on IMS emergency communication improvement - SMS | GSMA NRG (NRG_012_204) | Noted | Leo (Deutsche Telekom) proposes to postpone the LS from GSMA NRG. Thomas (Nokia) agrees to postpone the LS and wait for SA1 requirements. Shabnam (Ericsson) should SA2 NOTE the LS and take action based on SA1 response, instead of postpone? Leo (Deutsche Telekom) can agree to NOTE the LS. Thomas (Nokia) can also agree to NOTE the LS. ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Noted | |
| 4.1 | S2-2200074 | LS In | Information | LS from SA WG5: LS on the mapping between service types and slice at application | SA WG5 (S5-216414) | Rel-17 | Noted | Paul (Ericsson) proposes to NOTE this LS as for Information only/no action to SA2 included. ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Noted |
| 4.1 | S2-2200076 | LS In | Information | LS from SA WG5: LS Reply on model deployment and update from OAM to NG-RAN | SA WG5 (S5-216423) | Rel-17 | Noted | Leo (Deutsche Telekom) proposes to note the contribution. ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Noted |
| 4.1 | S2-2200077 | LS In | Action | LS from TSG SA: LS on Energy Efficiency as guiding principle for new solutions | TSG SA (SP-211621) | Noted | Leo (Deutsche Telekom) proposes to note the LS from TSG SA. ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Noted | |
| 4.1 | S2-2200112 | CR | Approval | 23.502 CR3135R2 (Rel-17, 'F'): SMF+PGW-C assigned PDU Session ID | Nokia, Nokia Shanghai Bell, ZTE, Cisco, Qualcomm | Rel-17 | Revision of (Noted) S2-2108386 from S2#148E. Merged into S2-2201675 | Judy (Ericsson) comment 0112 and 0310 are revisions to the same CR in previous meeting. 0310 gives operator choice of avoiding UDM impact, keeps the original order of source companies and keeps source companies' update visible, thus propose to use 0310 as basis for revision. Laurent (Nokia): OK to take 0310 as a baseline, merging 0112 in it, while we take 0113 (LS) as the baseline for the Ls out ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Merged |
| 4.1 | S2-2200309 | CR | Approval | 23.501 CR3488 (Rel-17, 'F'): Documentation handling for description of NF profile | Ericsson | Rel-17 | Merged into S2-2201273 | Josep (DT) prefers the approach in S2-2201189. Proposes to merge with S2-2201189. Devaki (Nokia) agrees with Josep (DT) and proposes to merge this CR to S2-2201189. Judy (Ericsson) reponds to Devaki (Nokia) and can live with the proposal to merge 0309 to 1189 which seems more preferred. ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Merged |
| 4.1 | S2-2200310 | CR | Approval | 23.502 CR3135R3 (Rel-17, 'F'): SMF+PGW-C assigned PDU Session ID | Ericsson, [Cisco, Nokia, Nokia Shanghai Bell, ZTE] | Rel-17 | Revision of (Noted) S2-2108386 from S2#148E. CC#2: r10 agreed. Revised, merging S2-2200112, to S2-2201675. | Laurent (Nokia): provides r01, OK to take 0310 as a baseline, merging 0112 in it, while we take 0113 (LS) as the baseline for the Ls out Judy (Ericsson) is OK with r01 Josep (DT) co-signs, provides r03, please disregard wrongly-uploaded r02. Zhendong (ZTE): provides r04 Susan (Huawei) raises objection to the UDM based solution and provides r05. Sebastian (Qualcomm) supports the CR and would like to cosign Judy (Ericsson) thanks Josep (DT), Zhendong (ZTE) and Sebastian (Qualcomm) for support of UDM approach, responds to Susan (Huawei) that the statement 'it requires the HSS to be upgraded to an UDM' is not really correct and has major concern on the new proposal of PCF storing PDU Session ID(s) in UDR Laurent (Nokia): Supports Judy Antoine (Orange) supports r04 and would like to co-sign. Judy (Ericsson) thanks Antoine (Orange) for your support. Susan (Huawei) replies to Judy and keeps objection to UDM based solution, i.e. r00, r01, r02, r03, r04. Susan (Huawei) replies to Laurent (Nokia). Sebastian (Qualcomm) replies Judy (Ericsson) responds to Susan (Huawei) and provide r07 based on r04, only change is that Qualcomm and Orange are added in Source. Laurent (Nokia): Supports Sebastian Judy (Ericsson) share the view from Sebastian and Laurent, and provides r08 adding Telecom Italia and Verizon as co-source. Zhendong (ZTE):similar view with sebastian (qualcomm) Irfan (Cisco) also supports the CR and continues to co-sign r09 Susana (Vodafone) supports this version of the CR Judy (Ericsson) thanks Susana (Vodafone) for support and provides r10 adding Vodafone as co-source. ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== Susan (Huawei) replies and keeps objection to all versions of this CR, except r05, r06. Serge (T-Mobile USA) supports this CR and is willing to cosign r10. Farooq (AT&T) also supports R10. Judy (Ericsson) thanks Farooq and Serge's support, objects to r5/r06, points out that Huawei's objection lacks of technical ground (explained below) thus request to withdraw their objection, otherwise propose SOH at CC#2. Susan (Huawei) replies to Judy (Ericsson) what she said that Huawei's objection lacks of technical ground is not true. Sebastian (Qualcomm) replies to Susan Laurent (Nokia): objects to R05/R06 Susan (Huawei) replies to Sebastian (Qualcomm) Susan (Huawei) replies to Laurent (Nokia) and keeps objection to all versions except r05/r06. Josep (DT) comments. Susan (Huawei) replies to Josep (DT) and propose to either postpone this CR to next meeting. Sebastian (Qualcomm) supports the comments made by DT (Josep) Judy (Ericsson) supports the comments from Josep (DT) and responds to Susan (Huawei). Susan (Huawei) keeps objection to all versions except r05/r06, but could accept to postpone this CR to next meeting for further check. Susan (Huawei) replies to Judy (Ericsson). ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Revised |
| 4.1 | S2-2201675 | CR | Approval | 23.502 CR3135R4 (Rel-17, 'F'): SMF+PGW-C assigned PDU Session ID | Ericsson, Nokia, Nokia Shanghai Bell, ZTE, Deutsche Telekom, Qualcomm, Orange, Telecom Italia, Verizon, Cisco, Vodafone, T-Mobile USA, AT&T | Rel-17 | Revision of S2-2200310r10, merging S2-2200112. This CR was agreed, subject to a Working Agreement | Agreed | |
| 4.1 | S2-2200422 | LS In | Action | Reply LS On Source IP address clarifications | RAN WG3 (R3-221474) | Rel-16 | Noted | Fenqin (Huawei) suggest to reply this LS in 0340. ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== Qian (Ericsson) proposes to NOTE the paper since 0340 replied this. ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Noted |
| 4.1 | S2-2200423 | LS In | Action | LS from RAN WG3: LS on NAS PDU delivery during PDU Session modification procedure | RAN WG3 (R3-221475) | Rel-16 | Response drafted in S2-2201026. CC#2: Final response in S2-2201676 | ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Replied to |
| 4.1 | S2-2201026 | LS OUT | Approval | [DRAFT] Response LS on NAS PDU delivery during PDU Session modification procedure | CATT | Rel-16 | Response to S2-2200423. CC#2: r06 agreed. Revised to S2-2201676. | LiMeng (Huawei) comments S2-2201025 and S2-2201026 shall be discussed together and provides r01. Yunjing (CATT) provides r02 to correct the Work Item based on r00. Yunjing (CATT) comments r01. LiMeng (Huawei) thanks the reminder from Yunjing (CATT) and provides r03 based on r01. Stefan (Ericsson) comments and provides r04 ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== Yunjing (CATT) comments on r04 and provides r05 in draft folder. LiMeng (Huawei) is fine with r05. LiMeng (Huawei) objects to r01-r04, and r00(original version) suggests to check r05 in CC#2. Stefan (Ericsson) provides r06 in DRAFTS LiMeng (Huawei) is fine with r06. ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== Hannu (Nokia) supports r05 and r06. | Revised |
| 4.1 | S2-2201676 | LS OUT | Approval | Response LS on NAS PDU delivery during PDU Session modification procedure | SA WG2 | Rel-16 | Revision of S2-2201026r06. Approved | Approved | |
| 4.1 | S2-2200442 | LS OUT | Approval | Reply LS on mandatory SSC modes supported by UE | Ericsson | Rel-15 | Response to S2-2108269 (already replied to at S2#148E in S2-2109345). r00 Revised to S2-2201274. | Hui(Huawei) comments: this LS reply should not be approved before S2-2200443. ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Revised |
| 4.1 | S2-2201274 | LS OUT | Approval | Reply LS on mandatory SSC modes supported by UE | SA WG2 | Rel-15 | Revision of S2-2200442r00. CC#2: Approved | Approved | |
| 4.1 | S2-2200443 | CR | Approval | 23.501 CR3503 (Rel-15, 'F'): SSC mode support by the UEs | Ericsson | Rel-15 | CC#2. r03 agreed. Revised to S2-2201677. | Antoine (Orange) provides r01. Saso (Intel) comments on r01. Magnus H (Ericsson) provides r02 Fenqin (Huawei) ask one question Magnus H (Ericsson) comments Hui (Huawei) provides r03. Chris (Vodafone) asks for clarification on SSC mode2. Dan (China Mobile) comments ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== Leo (Deutsche Telekom) comments, and can accept r03, but proposes some changes (latest at the next SA2 meeting). Hui (Huawei) can only accept r03, or r03 with changes proposed by Leo (Deutsche Telekom). Magnus H (Ericsson) accepts r03 with the changes proposed by Leo (Deutsche Telekom) ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== Hui (Huawei) uploaded r04 and ask to discuss in CC#2. | Revised |
| 4.1 | S2-2201677 | CR | Approval | 23.501 CR3503R1 (Rel-15, 'F'): SSC mode support by the UEs | Ericsson | Rel-15 | Revision of S2-2200443r03. This CR was agreed | Agreed | |
| 4.1 | S2-2200444 | CR | Approval | 23.501 CR3504 (Rel-16, 'A'): SSC mode support by the UEs | Ericsson | Rel-16 | r00 Revised to S2-2201275. | Hui(Huawei) comments: the contents of this CR should align with the approved version of S2-2200443. ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Revised |
| 4.1 | S2-2201275 | CR | Approval | 23.501 CR3504R1 (Rel-16, 'A'): SSC mode support by the UEs | Ericsson | Rel-16 | Revision of S2-2200444r00. CC#2: This CR was agreed | Agreed | |
| 4.1 | S2-2200445 | CR | Approval | 23.501 CR3505 (Rel-17, 'A'): SSC mode support by the UEs | Ericsson | Rel-17 | r00 Revised to S2-2201276. | Hui(Huawei) comments: the contents of this CR should align with the approved version of S2-2200443. ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Revised |
| 4.1 | S2-2201276 | CR | Approval | 23.501 CR3505R1 (Rel-17, 'A'): SSC mode support by the UEs | Ericsson | Rel-17 | Revision of S2-2200445r00. CC#2: This CR was agreed | Agreed | |
| 4.1 | S2-2200446 | DISCUSSION | Agreement | Handling of SSC modes being mandatory or optional . | Ericsson | Noted | ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Noted | |
| 4.1 | S2-2200510 | CR | Approval | 23.501 CR2866R1 (Rel-15, 'F'): Removal of ATC | Ericsson, Nokia, Nokia Shanghai Bell | Rel-15 | Revision of (Noted) S2-2103896 from S2#145E. Noted | Haiyang (Huawei) comments. Sang-Jun (Samsung) has similar views as Haiyang (Huawei). Hannu (Nokia) agrees with the proposal on Nokia part of co-signed CR and offers Cat F revision of the corresponding Rel-17 CRs. Haiyang (Huawei) suggest to note this paper as per discussion in 0282 thread ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Noted |
| 4.1 | S2-2200511 | CR | Approval | 23.501 CR2867R1 (Rel-16, 'A'): Removal of ATC | Ericsson, Nokia, Nokia Shanghai Bell | Rel-16 | Revision of (Noted) S2-2103897 from S2#145E. Noted | Haiyang (Huawei) suggest to note this paper as per discussion in 0282 thread ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Noted |
| 4.1 | S2-2200512 | CR | Approval | 23.501 CR2868R1 (Rel-17, 'A'): Removal of ATC | Ericsson, Nokia, Nokia Shanghai Bell | Rel-17 | Revision of (Noted) S2-2103898 from S2#145E. Noted | Hannu (Nokia) provides r01 to address the request to avoid changing old releases. The only change is on the cover page from 'Cat A' to 'Cat F'. Haiyang (Huawei) suggest to note this paper as per discussion in 0282 thread Hannu (Nokia) points out that the only technically valid argument against this document has been to avoid changing Rel-15. ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Noted |
| 4.1 | S2-2200513 | CR | Approval | 23.502 CR2746R1 (Rel-15, 'F'): Removal of ATC | Ericsson, Nokia, Nokia Shanghai Bell | Rel-15 | Revision of (Noted) S2-2103899 from S2#145E. Noted | Haiyang (Huawei) comments. Sang-Jun (Samsung) has similar views as Haiyang (Huawei). Hannu (Nokia) agrees with the proposal for Nokia part of co-signed CR and volunteers to provide Cat F revision of the corresponding Rel-17 CRs. Haiyang (Huawei) suggest to note this paper as per discussion in 0282 thread ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Noted |
| 4.1 | S2-2200514 | CR | Approval | 23.502 CR2747R1 (Rel-16, 'A'): Removal of ATC | Ericsson, Nokia, Nokia Shanghai Bell | Rel-16 | Revision of (Noted) S2-2103900 from S2#145E. Noted | Haiyang (Huawei) suggest to note this paper as per discussion in 0282 thread ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Noted |
| 4.1 | S2-2200515 | CR | Approval | 23.502 CR2748R1 (Rel-17, 'A'): Removal of ATC | Ericsson, Nokia, Nokia Shanghai Bell | Rel-17 | Revision of (Noted) S2-2103901 from S2#145E. Noted | Hannu (Nokia) provides r01 to address the request to avoid changing old releases. The only change is on the cover page from 'Cat A' to 'Cat F'. Haiyang (Huawei) suggest to note this paper as per discussion in 0282 thread Hannu (Nokia) points out that the only technically valid argument against this document has been to avoid changing Rel-15. ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Noted |
| 4.1 | S2-2200811 | LS In | Information | LS from RAN WG2: LS on User consent Updating | RAN WG2 (R3-221210) | Rel-17 | Noted | ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Noted |
| 4.1 | S2-2201024 | DISCUSSION | Discussion | Discussion on NAS PDU delivery during PDU Session modification procedure. | CATT | Rel-16 | Noted | ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Noted |
| 4.1 | S2-2201025 | CR | Approval | 23.502 CR3404 (Rel-16, 'F'): NAS PDU delivery during PDU Session modification | CATT | Rel-16 | Noted | Juan Zhang (Qualcomm) provides comment. Hannu (Nokia) supports Juan Zhang (Qualcomm) in suggesting Option 1. Yunjing (CATT) provides r01. Yunjing (CATT) provides r02. Myungjune (LGE) asks question on r02. Yunjing (CATT) provides r03. LiMeng (Huawei) comments on option 1, and prefers option 2. Yunjing(CATT) replies to LiMeng (Huawei). Hannu (Nokia) has concerns on all revisions r01, r02, r03 and prefers the original version. Yunjing (CATT) replies to Hannu (Nokia) and provides r04. Stefan (Ericsson) comments LiMeng (Huawei) comments on the principle of option 1 and provides r05. LiMeng (Huawei) replies. Yunjing (CATT) replies to LiMeng (Huawei). Stefan (Ericsson) provides comments ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== Yunjing (CATT) replies to Stefan (Ericsson). LiMeng (Huawei) objects to all versions of this document including the original one. ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Noted |
| 4.1 | S2-2201189 | CR | Approval | 23.501 CR3577 (Rel-17, 'F'): Completing description of NF profile | Nokia, Nokia Shanghai Bell | Rel-17 | r01 agreed. Revised to S2-2201273, merging S2-2200309 | Judy (Ericsson) proposes to merge this paper (1189) to 0309, explained below. Devaki (Nokia) comments that 309 should be considered merged to this CR. Judy (Ericsson) reponds to Devaki (Nokia), can live with the proposal to merge 0309 to 1189 and provide r01 ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Revised |
| 4.1 | S2-2201273 | CR | Approval | 23.501 CR3577R1 (Rel-17, 'F'): Completing description of NF profile | Nokia, Nokia Shanghai Bell, Ericsson | Rel-17 | Revision of S2-2201189r01, merging S2-2200309. Approved | Agreed | |
| 4.1 | S2-2201251 | LS In | Information | LS from GSMA 5GMRR: LS to 3GPP CT WG4 on Identification of source PLMN-ID in SBA | GSMA 5GMRR (5GMRR Doc 27_06r3) | Noted | Thomas (Nokia) suggests to note the LS ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Noted | |
| 4.1 | S2-2201261 | LS In | Information | LS from SA WG5: Reply LS on energy efficiency as guiding principle for new solutions | SA WG5 (S5-221501) | Rel-18 | Noted | Leo (Deutsche Telekom) proposes to note the LS from SA5. ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Noted |
| 4.1 | S2-2201264 | LS In | Information | LS from SA WG5: LS on 3GPP SA5 work on 5G network energy efficiency and energy saving | SA WG5 (S5-221680) | Rel-18 | Noted | Leo (Deutsche Telekom) proposes to note the LS from SA5. ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Noted |
| 4.2 | - | - | - | P-CRs/CRs related to use of inclusive language in 3GPP | - | - | Docs:=1 | - | |
| 4.2 | S2-2201265 | LS In | Information | LS from IEEE 1588 WG: RE: Liaison Statement on inclusive terminology received 2021-10-28 | IEEE 1588 WG (Reply to 3GPP liaison of 2021-10-28) | Noted | Shabnam (Ericsson) proposes to NOTE the LS and wait for further input from IEEE once they have reached a decision on their choice of terminology. ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Noted | |
| 5 | - | - | - | Pre-Rel-17 Maintenance (excluding all 5G topics) | - | - | Docs:=0 | - | |
| 5.1 | - | - | - | 3GPP Packet Access Maintenance | - | - | Docs:=6 | - | |
| 5.1 | S2-2200384 | CR | Approval | 23.401 CR3681 (Rel-17, 'F'): Correction for Restriction of use of Enhanced Coverage | Qualcomm Incorporated | Rel-17 | r03 agreed. Revised to S2-2201471. | Antoine (Orange): this CR should be applied from Rel-14 to avoid interoperability issues. Qian (Ericsson) provides comments and r01. Hannu (Nokia) agrees the principle but proposes r02 to add binding between what the network sends and what the UE receives by adding the parameter name also in clause 4.3.28. Steve (Huawei) principle is fine, provides r03. Hannu (Nokia) replies to Steve (Huawei) and provides r04. Steve (Huawei) comments Haris(Qualcomm) comments that r04 is incorrect Hannu (Nokia) agrees with Haris(Qualcomm) that r04 is not correct. Asks if the UE condition to determine EC Restriction can be clarified based on r03? Haris(Qualcomm) comments that r03 is technically correct and can be approved ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== Qian (Ericsson) supports to go with r03 Hannu (Nokia) supports r03 ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Revised |
| 5.1 | S2-2201471 | CR | Approval | 23.401 CR3681R1 (Rel-17, 'F'): Correction for Restriction of use of Enhanced Coverage | Qualcomm Incorporated | Rel-17 | Revision of S2-2200384r03. Approved | Agreed | |
| 5.1 | S2-2200385 | CR | Approval | 23.501 CR3495 (Rel-17, 'F'): Correction for Restriction of use of Enhanced Coverage | Qualcomm Incorporated | Rel-17 | r03 agreed. Revised to S2-2201472. | Antoine (Orange): this CR should be applied from Rel-16 to avoid interoperability issues. Qian (Ericsson) provides comments and r01. Hannu (Nokia) proposes to bind the network sending the parameter to UE receiving the same parameter by mentioning the parameter name explicitly in r02. Haris(Qualcomm) responds that would like to hear views from other companies whether it is essential to do the CR in much older releases Steve (Huawei) principle is fine, provides r03. Hannu (Nokia) thanks Steve (Huawei) for explanation and supports r03. ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== Qian (Ericsson) supports r03. ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Revised |
| 5.1 | S2-2201472 | CR | Approval | 23.501 CR3495R1 (Rel-17, 'F'): Correction for Restriction of use of Enhanced Coverage | Qualcomm Incorporated | Rel-17 | Revision of S2-2200385r03. Approved | Agreed | |
| 5.1 | S2-2200957 | CR | Approval | 23.401 CR3687 (Rel-17, 'F'): Clarification on handling of UE radio capability for paging when MME changes | Nokia, Nokia Shanghai Bell | Rel-17 | CC#2: r03 + changes agreed. Revised to S2-2201678. | Steve (Huawei) asks for clarification Qian (Ericsson) provides comments and consider no clarification is needed Alessio(Nokia) explains and replies to Steven: stage 3 only allows one UE radio capability for paging to be transferred, not both. Alessio(Nokia) replies to Qian Qian (Ericsson) provides further comments. Haris(Qualcomm) comments and provides r01 Qian (Ericsson) asks questions on r01 Haris(Qualcomm) responds Qian(Ericsson) asks further questions Qian(Ericsson) provides comments alessio(Nokia) provides r02 Qian (Ericsson) comments and provides r03 Steve (Huawei) comments Haris(Qualcomm) asks question Qian (Ericsson) replies Alessio(Nokia) comments (and states r03 is not acceptable) Steve (Huawei) provides r04 alessio(Nokia) still prefer r02. ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== Qian (Ericsson) provides further comments and supports r04 or r03 Steve (Huawei) prefers r04, objects to r00, r01, r02. Alessio(Nokia) can only accept r02 Haris(Qualcomm) comments that r04 creates more confusion, r03 could be better. R02 is technically correct alessio(Nokia) proposes the way forward to be discussed at CC#2 Chris (Vodafone) supports discussion at CC#2. R04 seems to miss critical information. ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== Qian (Ericsson) responds Chris (Vodafone) replies to a question from ZTE and tries to explain the situation. Alessio(Nokia) proposes then to agree with r02 as it requires no update (r03 does require an update due to syntax ) and it is technically correct. Steve (Huawei) could live with r03 or, still prefers simplified version in r04 | Revised |
| 5.1 | S2-2201678 | CR | Approval | 23.401 CR3687R1 (Rel-17, 'F'): Clarification on handling of UE radio capability for paging when MME changes | Nokia, Nokia Shanghai Bell | Rel-17 | CC#2: Revision of S2-2200957r03 + changes. This CR was agreed | Agreed | |
| 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:=1 | - | |
| 6.1 | S2-2200341 | CR | Approval | 23.501 CR3492 (Rel-17, 'F'): Reference architecture editorial correction | Ericsson | Rel-17 | Approved | ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Agreed |
| 6.2 | - | - | - | Common Access Control, RM and CM functions and procedure flows | - | - | Docs:=18 | - | |
| 6.2 | - | - | - | AMF re-allocation in connected state | - | - | Docs:=11 | - | |
| 6.2 | S2-2200509 | CR | Approval | 23.501 CR3516 (Rel-17, 'F'): Change of network slices in CM-CONNECTED | Ericsson | Rel-17 | Noted | Kundan (NEC) comments Susan (Huawei) asks questions for clarification. Peter Hedman (Ericsson) provides reply. alessio(Nokia) proposes to note this CR Jinguo(ZTE) supports this CR Alessio(Nokia) proposes to note this CR. Peter Hedman (Ericsson) provides r01 and comments Alessio(nokia) comments that the documentation of this 'no support' should then be for rel-16 and the documentation of support in rel-17. Dongeun (Samsung) comments and provides r02. Alessio(Nokia) proposes to note this CR as we are documenting how the relocation works in CM-CONNECTED. Peter Hedman (Ericsson) provides r03 Alessio(Nokia) cannot accept a y of the revisions so far (up to r03) and provides r04 Peter Hedman (Ericsson) provides r05 Alessio(nokia) objects to r05 Peter Hedman (Ericsson) provides r06 Peter Hedman (Ericsson) provides additional clarification ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== Jinguo(ZTE) suggest to go with r06 Alessio(nokia) objects to r06 Peter Hedman (Ericsson) provides reply and asks the same question again on the technical reasoning Dongeun (Samsung) asks questions alessio(Nokia) replies Dongeun (Samsung) has concern on the option 1 and suggest to go with r02 Peter Hedman (Ericsson) ok with r02 ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== Alessio(Nokia) then proposes this CR is noted. r02 does not read well at all and in fact wrong | Noted |
| 6.2 | S2-2200850 | DISCUSSION | Decision | Discussion on Registration with AMF re-allocation in connected state. | Huawei, HiSilicon | Rel-17 | Noted | ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Noted |
| 6.2 | S2-2200851 | CR | Approval | 23.501 CR3540 (Rel-17, 'F'): Registration with AMF re-allocation in connected state | Huawei, HiSilicon | Rel-17 | r04 agreed. Revised to S2-2201473. | Peter (Ericsson) provides comments and suggests to note the CR or to focus on explaining that RAN can decide to use existing mechanisms Alessio(Nokia) comments Peter Hedman (Ericsson) provides comments Susan (Huawei) replies to Peter (Ericsson) and Alessio(Nokia) comments, and provides r01. Peter Hedman (Ericsson) provides r02 Susan (Huawei) is ok with r02. alessio(Nokia) asks a question for clarification Genadi (Lenovo) provides r03. Alessio(nokia) provides r04 Kundan(NEC) is fine with r04. Susan (Huawei) is fine with r04, but provides r05 to address Alessio's comment. ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== Alessio(Nokia) is ok with r05. Peter Hedman (Ericsson) provides reply and ok with r05 Genadi (Lenovo) is fine with r05 but the requests to remove 'In this case, the NSSF does not provide the target AMF(s).' in the clause 5.15.5.2.1. Susan (Huawei) replies to Genadi (Lenovo). Peter Hedman (Ericsson) provides comments and support comment from Genadi Alessio(Nokia) ok with r04. Peter Hedman (Ericsson) ok with r04, but would have preferred to remove changes to the note. Genadi (Lenovo) replies to Susan (Huawei). ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== Susan (Huawei) replies to Genadi. | Revised |
| 6.2 | S2-2201473 | CR | Approval | 23.501 CR3540R1 (Rel-17, 'F'): Registration with AMF re-allocation in connected state | Huawei, HiSilicon, Ericsson, Nokia, Nokia Shanghai Bell, NEC | Rel-17 | Revision of S2-2200851r04. Approved | Agreed | |
| 6.2 | S2-2200852 | CR | Approval | 23.502 CR3382 (Rel-17, 'F'): Registration with AMF re-allocation in connected state | Huawei, HiSilicon | Rel-17 | Noted | Alessio(Nokia) proposes to note this CR as we are documenting how the relocation works in CM-CONNECTED in 1165 ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== Susan (Huawei) is ok to either note this paper or marked it as merged to 1165. ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Noted |
| 6.2 | S2-2200853 | LS OUT | Approval | [DRAFT] LS on handover triggered by Target NSSAI | Huawei, HiSilicon | Rel-17 | Noted | Peter (Ericsson) provides comments and suggest there is no need for any LS Susan (Huawei) is ok with no LS to RAN. alessio(Nokia) agrees there is no need of Ls at this meeting. we need to conclude on this at next meeting. ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Noted |
| 6.2 | S2-2200979 | CR | Approval | 23.502 CR3395 (Rel-17, 'F'): Registration with AMF reallocation in connected mode | Nokia, Nokia Shanghai Bell | Rel-17 | Merged into S2-2201474 | Peter (Ericsson) provides comments that changes to existing procedure is not inline with working stage 3 alessio(Nokia) proposes this is merged in 1165 ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Merged |
| 6.2 | S2-2201103 | CR | Approval | 23.501 CR3561 (Rel-16, 'F'): AMF re-allocation in CM connected state | ZTE | Rel-16 | Noted | Peter (Ericsson) provides comments, and proposes it is enough with Rel-17 CR Alessio(Nokia) provides r01 ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== Peter Hedman (Ericsson) provides comments and objects to the CR, any revision, as r01 always directly push UE to idle ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Noted |
| 6.2 | S2-2201104 | CR | Approval | 23.501 CR3562 (Rel-17, 'A'): AMF re-allocation in CM connected state | ZTE | Rel-17 | Covered by (noted) S2-2200509. Noted | Peter (Ericsson) provides comments, and proposes a merge Jinguo(ZTE) agree to merge into 509 Alessio(Nokia) comments in rel-17 we should define the support of relocation in CM-Connected not document how it is not supported. proposed to note ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Noted |
| 6.2 | S2-2201165 | CR | Approval | 23.502 CR3102R1 (Rel-17, 'F'): AMF relocation in connected state | NEC | Rel-17 | Revision of (Postponed) S2-2106411 from S2#146E. r03 agreed. Revised to S2-2201474, merging S2-2200979 | Peter (Ericsson) provides comments, and proposes a merge Peter Hedman (Ericsson) provides comments Kundan(NEC) provides response. Alessio(Nokia) the S2-2200979 CR addresses the case of relocation with connected mode in separate clause as to us we want to highlight this requires N14 . There cannot be the case of keeping the UE connected without N14, is it? we would like to hear comments on this. at least we thought the N14-less case is hard to address and not well justified as if there are no sessions to continue then placing in idle of course can be an option. Kundan(NEC) clarifies further with Alessio(Nokia). Alessio(Nokia) provides r01 based on offline discussion with Kundan Kundan(NEC) is fine with revision 1. Kundan(NEC) provides r02. Peter Hedman (Ericsson) provides r03 ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Revised |
| 6.2 | S2-2201474 | CR | Approval | 23.502 CR3102R2 (Rel-17, 'F'): AMF relocation in connected state | NEC, Nokia, Nokia Shanghai Bell, ZTE, Ericsson, Huawei, HiSilicon | Rel-17 | Revision of S2-2201165r03, merging S2-2200979. Approved | Agreed | |
| 6.2 | - | - | - | Other | - | - | Docs:=7 | - | |
| 6.2 | S2-2200875 | CR | Approval | 23.502 CR3271R1 (Rel-17, 'F'): Inter PLMN Handover procedure | Huawei, HiSilicon | Rel-17 | Revision of (Noted) S2-2108676 from S2#148E. r02 agreed. Revised to S2-2201475. | Haris(Qualcomm) provides comments and suggests alternative documentation Qian (Ericsson) provides comments and asks question Fenqin (Huawei) provides r01 Qian (Ericsson) comments and provides r02 Fenqin (Huawei) is fine with r02 ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Revised |
| 6.2 | S2-2201475 | CR | Approval | 23.502 CR3271R2 (Rel-17, 'F'): Inter PLMN Handover procedure | Huawei, HiSilicon, Ericsson | Rel-17 | Revision of S2-2200875r02. Approved | Agreed | |
| 6.2 | S2-2201005 | CR | Approval | 23.502 CR3403 (Rel-17, 'F'): Inter-AMF Xn handover | Nokia, Nokia Shanghai Bell | Rel-17 | CC#2: Postponed | LiMeng (Huawei) comments. Hannu (Nokia) replies to LiMeng. Hannu (Nokia) replies to LiMeng and points out why the existing text is incorrect and it causes handovers to fail. Qian (Ericsson) provides comments and ask question. Hannu (Nokia) supports the interpretation from Qian (Ericsson) and asks for acceptable way to solve the conflict in the specs? Haris(Qualcomm) comments that he does not understand the problem this CR tries to solve Jinguo(ZTE) comments that the changes are not necessary. Hannu (Nokia) replies to Jinguo(ZTE) and Haris(Qualcomm) and shares r01. Hannu (Nokia) responds to Haris(Qualcomm). Hannu (Nokia) provides the other half of the response to Haris(Qualcomm). Haris(Qualcomm) responds LiMeng (Huawei) provides r02 Hannu (Nokia) thanks LiMeng (Huawei) for help and provides r03. Jinguo(ZTE) comments on r03. Hannu (Nokia) responds to comment from Jinguo(ZTE) in r04. Haris(Qualcomm) provides r05 Hannu (Nokia) thanks Haris(Qualcomm) for r05. Nokia can agree either r04 or r05. ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== Jinguo(ZTE) don't agree both r04 and r05 since both of them are incorrect Qian (Ericsson) supports Jinguo's (ZTE) understanding Haris(Qualcomm) comments that r03 does not reflect the explanation from Qian and Jinguo Qian (Ericsson) responds to Haris (Qualcomm) Haris(Qualcomm) comments that r05+change suggested by Qian is correct Hannu (Nokia) agrees with the discussion so far and proposes r03 as the way forward. Jinguo(ZTE) suggest a new revision Hannu (Nokia) agrees the concept does not object to late revision as has been discussed, but points out that note cannot change normative requirement. ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Postponed |
| 6.2 | S2-2201006 | CR | Approval | 23.501 CR3554 (Rel-17, 'F'): Inter-system configuration transfer | Nokia, Nokia Shanghai Bell | Rel-17 | r01 agreed. Revised to S2-2201476. | Haris(Qualcomm) comments that the reason for change is wrong and the CR is not needed Hannu (Nokia) addresses the comments from Haris(Qualcomm) in r01. ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Revised |
| 6.2 | S2-2201476 | CR | Approval | 23.501 CR3554R1 (Rel-17, 'F'): Inter-system configuration transfer | Nokia, Nokia Shanghai Bell | Rel-17 | Revision of S2-2201006r01. Approved | Agreed | |
| 6.2 | S2-2200342 | CR | Approval | 23.502 CR3346 (Rel-17, 'F'): Updating AMF with new Routing Indicator Data if re-registration is not triggered | Ericsson | Rel-17 | r01 agreed. Revised to S2-2201478. | Josep (DT) comments, provides r01. Hannu (Nokia) asks why the condition to request the UE to re-register must be synchronous with updating the data? Peter Hedman (Ericsson) provides comments ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== Josep (DT) clarifies. Hannu (Nokia) thanks Josep for explanation. Nokia prefers the original version but can also live with r01 if that's what the others want. Josep (DT) is also fine with r00. Peter Hedman (Ericsson) prefers r00, but are ok with r01 as well ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Revised |
| 6.2 | S2-2201478 | CR | Approval | 23.502 CR3346R1 (Rel-17, 'F'): Updating AMF with new Routing Indicator Data if re-registration is not triggered | Ericsson | Rel-17 | Revision of S2-2200342r01. Approved | Agreed | |
| 6.3 | - | - | - | Session management and continuity functions and flows | - | - | Docs:=15 | - | |
| 6.3 | - | - | - | Service request and PCF interaction | - | - | Docs:=6 | - | |
| 6.3 | S2-2200312 | DISCUSSION | Agreement | Service Request and PCF interaction. | Ericsson | Rel-16 | Noted | ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Noted |
| 6.3 | S2-2200313 | CR | Approval | 23.502 CR3230R1 (Rel-16, 'F'): Service Request and PCF interaction | Ericsson | Rel-16 | Revision of (Postponed S2-2108389 from S2#148E. r09 agreed. Revised to S2-2201479, merging S2-2200876 | Judy (Ericsson) provides r01 merging 0876 into this paper based on offline discussion Laurent (Nokia): provides r02 Judy (Ericsson) thanks Laurent (Nokia) for the revision and provides further update in r03 . Judy (Ericsson) comments on r04 Judy (Ericsson) uploaded r04 provided by Fenqin (Huawei). Fenqin (Huawei) provides comments and provide r04 Fenqin(Huawei) provides comments Judy (Ericsson) responds. Fenqin (Huawei) responds. Judy (Ericsson) provides r05. Jinguo(ZTE) provides r06 Jinguo(ZTE) provides r07 Jinguo(ZTE) provides r08 Fenqin (Huawei) provides r09 ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== Jinguo(ZTE) is ok with r09 but think more change is needed at next meeting. Laurent (Nokia): has a strong preference for R09 Judy (Ericsson) responds to Laurent (Nokia). ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Revised |
| 6.3 | S2-2201479 | CR | Approval | 23.502 CR3230R2 (Rel-16, 'F'): Service Request and PCF interaction | Ericsson, Huawei, HiSilicon, Nokia, Nokia Shanghai Bell, ZTE | Rel-16 | Revision of S2-2200313r09, merging S2-2200876. Approved | Agreed | |
| 6.3 | S2-2200314 | CR | Approval | 23.502 CR3231R1 (Rel-17, 'A'): Service Request and PCF interaction | Ericsson | Rel-17 | Revision of (Postponed) S2-2108390 from S2#148E. r00 agreed. Revised to S2-2201480. | Jinguo(ZTE) comment this mirror CR should be aliged with 313. ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Revised |
| 6.3 | S2-2201480 | CR | Approval | 23.502 CR3231R3 (Rel-17, 'A'): Service Request and PCF interaction | Ericsson, Huawei, HiSilicon, Nokia, Nokia Shanghai Bell, ZTE | Rel-17 | Revision of S2-2200314r00. Approved | Agreed | |
| 6.3 | S2-2200876 | CR | Approval | 23.502 CR3231R2 (Rel-17, 'F'): Service Request and PCF interaction | Huawei, HiSilicon | Rel-17 | Revision of (Postponed) S2-2108390 from S2#148E. Merged into S2-2201479 | Judy (Ericsson) proposes to merge this paper to 0313 based on offline discussion. Judy (Ericsson) comment that the Rel-17 version is a mirror of 0313 but 0876 has Cat F thus propose to use 0313 (Rel-16)/0314 (mirror) to simplify handling. Fenqin (Huawei) proposes to use this version for R17. Laurent (Nokia): we need first to decide whether this requires a R16 or a R17 baseline CR. Judy (Ericsson) believes that Rel-16 correction is needed, otherwise the PCC for ETSUN scenario does not work. Fenqin (Huawei) comment. Judy (Ericsson) comments. Laurent (Nokia): suggests we take 313 as the basis (to have a R16 CR) ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== Fenqin (Huawei) we are ok to merge this paper to 0314, i.e. the Rel-17 version. ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Merged |
| 6.3 | - | - | - | Other | - | - | Docs:=9 | - | |
| 6.3 | S2-2200448 | CR | Approval | 23.501 CR3507 (Rel-17, 'F'): Handling of VPLMN QoS constraints during mobility | Ericsson | Rel-17 | r04 + changes agreed. Revised to S2-2201671. Editorial change NG-RAN -> 5G AN | Laurent (Nokia): provides r01 Stefan (Ericsson) provides r02 Laurent (Nokia): answers: why would 5QI, ARP in QoS constraints be restricted to the default QoS rule? what if the H-SMF provides multiple Qos Flows in the PDU Session Establishment procedure Fenqin (Huawei) comments. Stefan (Ericsson) replies Stefan (Ericsson) provides r03 Stefan (Ericsson) replies to Laurent Mirko (Huawei) provides r04. Stefan (Ericsson) is ok with r04 ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== Laurent (Nokia): OK with R04 but asking a small change ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Revised |
| 6.3 | S2-2201671 | CR | Approval | 23.501 CR3507R1 (Rel-17, 'F'): Handling of VPLMN QoS constraints during mobility | Ericsson | Rel-17 | Revision of S2-2200448r04 + changes. Approved | Agreed | |
| 6.3 | S2-2200449 | CR | Approval | 23.502 CR3353 (Rel-17, 'F'): Handling of VPLMN QoS constraints during mobility | Ericsson | Rel-17 | r02 agreed. Revised to S2-2201481. | Fenqin (Huawei) comments and provides r01 Stefan (Ericsson) provides comments Fenqin (Huawei) provides r02 Laurent (Nokia): Comments Stefan (Ericsson) replies to Laurent ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Revised |
| 6.3 | S2-2201481 | CR | Approval | 23.502 CR3353R1 (Rel-17, 'F'): Handling of VPLMN QoS constraints during mobility | Ericsson | Rel-17 | Revision of S2-2200449r02. Approved | Agreed | |
| 6.3 | S2-2200991 | CR | Approval | 23.502 CR3400 (Rel-17, 'F'): Enforcement of VPLMN QoS policies | Ericsson | Rel-17 | r01 agreed. Revised to S2-2201482. | Laurent (Nokia): provides r01 Stefan (Ericsson) is OK with r01 ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Revised |
| 6.3 | S2-2201482 | CR | Approval | 23.502 CR3400R1 (Rel-17, 'F'): Enforcement of VPLMN QoS policies | Ericsson, Nokia, Nokia Shanghai Bell | Rel-17 | Revision of S2-2200991r01. Approved | Agreed | |
| 6.3 | S2-2200545 | CR | Approval | 23.502 CR3360 (Rel-16, 'F'): Secondary reauthentication | Samsung | Rel-16 | Noted | Laurent (Nokia): Suggests to have this CR only in R17 for this clarification (0547 is transformed into Cat F). Comments Myungjune (LGE) comments. Ashok (Samsung) replies to Laurent (Nokia) and to Myungjune (LGE) Myungjune (LGE) questions on overall procedure Ashok (Samsung) replies to Myungjune (LGE) Saso (Intel) proposes to NOTE the CR. Ashok ( Samsung) does not agree with Saso (Intel) and clarifies the difference about the reauth failure and reauth not executed in case of UE unreachability Saso (Intel) comments. Ashok (Samsung) responds to Saso (Intel) Haris(Qualcomm) shares the same view as Saso (Intel) Ashok (Samsung) responds to Haris (Qualcomm) Myungjune (LGE) responds to Ashok (Samsung) Ashok (Samsung) clarifies to Myungjune (LGE) Myungjune (LGE) replies to Ashok (Samsung) Ashok (Samsung) responds to Myungjune (LGE) Fenqin (Huawei) share the same view as Myungjune Ashok (Samsung) provides r02 after discussing in offline Ashok (Samsung) responds to Jinguo(ZTE) Jinguo(ZTE) comments on r02 Ashok (Samsung) responds to Fenqin (Huawei) Fenqin (Huawei) provides comment Stefan (Ericsson) comments Laurent (Nokia): We have the same view as Stefan, Jinguo and Fenqin. ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Noted |
| 6.3 | S2-2200547 | CR | Approval | 23.502 CR3362 (Rel-17, 'A'): Secondary reauthentication | Samsung | Rel-17 | r03 agreed. Revised to S2-2201483. | Laurent (Nokia): Suggests to have this CR only in R17 for this clarification (0547 is transformed into Cat F). Comments Ashok (Samsung) provides r01 Fenqin (Huawei) provides r02 Stefan (Ericsson) provides r03 Ashok (Samsung) comments Ashok (Samsung) provides r04 and r05 ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== Fenqin (Huawei) suggest to go with r03 Myungjune (LGE) prefer r03, can live with r04/r05 Ashok (Samsung) propose to go with either r04 or r05 Kundan(NEC) is fine with either r04 or r05. Jinguo(ZTE) prefers to r03, has concerns on r04 and r05 Ashok (Samsung) responds to Jinguo(ZTE) and request not to raise concern on a revision for editorial issue Laurent (Nokia): objects to R00, R01, R04, R05. suggest to go with R03 Haris(Qualcomm) suggests to go with r03 Ashok (Samsung) agrees with r03 keeping in line with majority view Stefan (Ericsson) also agrees to go with r03. objects to R00, R01, R04, R05 ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Revised |
| 6.3 | S2-2201483 | CR | Approval | 23.502 CR3362R1 (Rel-17, 'F'): Secondary reauthentication | Samsung | Rel-17 | Revision of S2-2200547r03. Approved | Agreed | |
| 6.4 | - | - | - | Security related functions and flows | - | - | Docs:=2 | - | |
| 6.4 | S2-2200117 | CR | Approval | 23.501 CR3465 (Rel-17, 'F'): Adding NSWO NF in the architecture | Nokia, Nokia Shanghai Bell | Rel-17 | r16 agreed. Revised to S2-2201672. | Antoine (Orange) provides r01. Stefan (Ericsson) provides r02 Laurent (Nokia): provides r03 Marco (Huawei): we have concern in the CR due to uncomplete description of this new kind of doing NSWO from SA2 point of view Haris(Qualcomm) provides r04 Laurent (Nokia): supports R04 improvements and agrees with Haris Marco (Huawei) disagree with all proposed revision and comments Haris(Qualcomm) asks Marco question for clarification Marco (huawei) answer to Haris (Qualcomm) Marco (huawei) would enforce that we have concern with any of current revisions. Beside the architecture figure, the relevant text addressing the aspects discussed should be in clause 5.5 (or I new clause) Laurent (Nokia): provides r05 Haris(Qualcomm) comments that documenting anything related to NSWO in clause 5.5 is not appropriate Laurent (Nokia): provides r06 Robert (Peraton Labs) comments. Apostolis (Lenovo) supports the CR but believe more changes are needed. marco (Huawei) agree with Apostolis (Lenovo) and propose R07. Haris(Qualcomm) asks questions for r07 Florin (Broadcom) supports the comments from Apostolis and Marco and provides new update r08 with few changes on top of r07 provided by Marco. Haris(Qualcomm) provides r09 Macro (Huawei) answers to Haris(Qualcomm) Stefan (Ericsson) provides r10 Apostolis (Lenovo) provides r11 Marco(Huawei) comments Marco (Huawei) provides r12 Marco (Huawei) would be nice to generate a LS to SA3 Apostolis (Lenovo) comments on r12. Marco (Huawei) provides r13. Laurent (Nokia): provides r14 Saso (Intel) proposes an EN. Haris(Qualcomm) supports Saso's suggestion to add EN Marco (Huawei) is OK with Saso's suggestion to add EN Laurent (Nokia): provides r15 =R14 + Saso's EN Robert (Peraton Labs) asks question on Trusted WLAN without TNFG Marco (Huawei) answer to Robert (Peraton Labs) Antoine (Orange) provides r16. Robert (Peraton Labs) responds ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== Florin (Broadcom) provides r17 which includes some editorial updates on top of r16.. Laurent (Nokia): proposes text for the draft LS. happy with R16 Marco (Huawei): we are ok with only R16 Florin (Broadcom): is ok with R16. However, R16 may also need some editorial corrections which were previously submitted in R17. ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Revised |
| 6.4 | S2-2201672 | CR | Approval | 23.501 CR3465R1 (Rel-17, 'F'): Adding NSWO NF in the architecture | Nokia, Nokia Shanghai Bell | Rel-17 | Revision of S2-2200117r16. CC#2: This CR was agreed | Agreed | |
| 6.5 | - | - | - | QoS concept and functionality | - | - | Docs:=0 | - | |
| 6.6 | - | - | - | Policy and charging control | - | - | Docs:=15 | - | |
| 6.6 | - | - | - | PCF selection when SSC mode 3 applies | - | - | Docs:=4 | - | |
| 6.6 | S2-2200343 | CR | Approval | 23.502 CR3305R1 (Rel-16, 'F'): Selecting the same PCF for all UE PDU Sessions to a DNN, S-NSSAI when SSC mode 3 applies | Ericsson | Rel-16 | Revision of (Noted) S2-2108902 from S2#148E. Postponed | Pallab (Nokia) comments and requests for clarification Susan (Huawei) asks questions for clarification. Jari (NTT DOCOMO) comments Belen (Ericsson) responds to comments Jinguo(ZTE) agree with Susan Belen (Ericsson) asks for clarifications. Belen (Ericsson) provides r02 addressing Nokia and DoCoMo comments. Pallab (Nokia) provides r03. Belen (Ericsson) is okay with r03 Pallab (Nokia) responds to Belen (Ericsson). Jinguo(ZTE) comments Belen (Ericsson) replies to ZTE comments Belen (Ericsson) provides r04 to consider if S2-2200409 Pallab (Nokia) provides r05 as r04 missed to update clause 5.2.8.2.5. Belen (Ericsson) is okay with r05. Susan (Huawei) replies to Belen and asks questions for clarification. ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== Belen (Ericsson) replies to Susan Susan (Huawei) replies to Belen. Susan (Huawei) replies to Belen and asks further questions. Pallab (Nokia) tries to clarify Susan (Huawei) Susan (Huawei) replies to Pallab (Nokia). Belen (Ericsson) replies to Susan. Susan (Huawei) replies to Belen (Ericsson) and propose to postpone this CR to next meeting for further discussion. Susan (Huawei) replies to Jari (NTT DOCOMO) ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Postponed |
| 6.6 | S2-2200344 | CR | Approval | 23.502 CR3306R1 (Rel-17, 'A'): Selecting the same PCF for all UE PDU Sessions to a DNN, S-NSSAI when SSC mode 3 applies | Ericsson | Rel-17 | Revision of (Noted) S2-2108903 from S2#148E. Postponed | ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Postponed |
| 6.6 | S2-2200409 | CR | Approval | 23.502 CR3351 (Rel-17, 'F'): Selecting the same PCF when usage monitoring and SSC mode 3 applies | NTT DOCOMO | Rel-17 | Confirm Spec version used - CR states 17.10.0! Noted | Susan (Huawei) raises comments Jari (NTT DOCOMO) responds to Susan Susan (Huawei) replies to Jari. Jinguo(ZTE) agree with Susan (Huawei). Jari (NTT DOCOMO) responds to Jinguo and Susan Pallab(Nokia) proposes to go with 0343 for same PCF selection and consider this CR as NOTED or merge to 0343 Jari (NTT DOCOMO) responds to Pallab Pallab(Nokia) responds to Jari (NTT DOCOMO) Belen (Ericsson) is okay with the proposal to merge this CR into 0343. It is also okay to merge 0343 into this one if needed. Jari (NTT DOCOMO) comments Jinguo(ZTE) comments Belen (Ericsson) prefers to merge this CR into 0343 ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== Pallab(Nokia) responds to Jari (NTT DOCOMO) and maintains objection to this CR. ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Noted |
| 6.6 | S2-2200424 | CR | Approval | 23.503 CR0693 (Rel-17, 'F'): Selecting the same PCF when usage monitoring and SSC mode 3 applies | NTT DOCOMO | Rel-17 | Noted | Pallab (Nokia) asks for clarification and thinks that the changes proposed may not be needed. Jari (NTT DOCOMO) responds to Pallab Belen (Ericsson) provides comments. Jari (NTT DOCOMO) provides r01 Pallab (Nokia) thinks the changes proposed are not needed and proposes to NOTE the CR Belen (Ericsson) is okay with r01 Pallab (Nokia) responds to Jari (NTT DOCOMO) ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== Susan (Huawei) shares same view as Pallab (Nokia). Pallab (Nokia) removes objection based on offline discussion. r01 can be agreed if the corresponding CR to 23.502 i.e. tdoc number S2-2200343r05 is agreed. Susan (Huawei) objects all versions of the CR, including the original one. Jari (NTT DOCOMO) explains to Susan why this CR is required Susan (Huawei) replies to Jari (NTT DOCOMO) and is not convinced that the CR is needed. Jari (NTT DOCOMO) responds to Susan Susan (Huawei) replies to Jari (NTT DOCOMO). ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Noted |
| 6.6 | - | - | - | Other | - | - | Docs:=11 | - | |
| 6.6 | S2-2200315 | CR | Approval | 23.502 CR3341 (Rel-17, 'F'): Correction to UE Configuration Update procedure for transparent UE Policy delivery | Ericsson | Rel-17 | r02 + changes agreed. Revised to S2-2201673. Replace step 00 by step 0a in the figure 4.2.4.3-1 in r02 | Josep (DT) comments, provides r01. Belen (Ericsson) provides comments. Mirko (Huawei) comments and provides r02. ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== Belen (Ericsson) asks to add to chairman notes to replace step 00 by step 0a in the figure 4.2.4.3-1 in r02 ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Revised |
| 6.6 | S2-2201673 | CR | Approval | 23.502 CR3341R1 (Rel-17, 'F'): Correction to UE Configuration Update procedure for transparent UE Policy delivery | Ericsson | Rel-17 | Revision of S2-2200315r02 + changes. This CR was agreed | Agreed | |
| 6.6 | S2-2200682 | CR | Approval | 23.502 CR3373 (Rel-17, 'F'): Alignment of PCC input parameter documentation | Huawei, HiSilicon | Rel-17 | r01 agreed. Revised to S2-2201484, merging S2-2201096 and S2-2200898 | Belen (Ericsson) asks a question for clarification. Mirko (Huawei) responds. Belen (Ericsson) is okay with this contribution Mirko (Huawei) provides r01. ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Revised |
| 6.6 | S2-2201484 | CR | Approval | 23.502 CR3373R1 (Rel-17, 'F'): Alignment of PCC input parameter documentation | Huawei, HiSilicon | Rel-17 | Revision of S2-2200682r01, merging S2-2201096, merging S2-2201096 and S2-2200898. Approved | Agreed | |
| 6.6 | S2-2200683 | CR | Approval | 23.503 CR0697 (Rel-17, 'F'): Clarification of PCC input parameter AF application identifier | Huawei, HiSilicon | Rel-17 | Postponed | Belen (Ericsson) provides comments Belen (Ericsson) object to this contribution and ask to postpone the discussion. ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== Mirko (Huawei) responds and is ok with postponing. ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Postponed |
| 6.6 | S2-2200736 | CR | Approval | 23.502 CR3375 (Rel-16, 'F'): UP path change notification to the AF | NTT DOCOMO | Rel-16 | r03 agreed. Revised to S2-2201485. | Pallab (Nokia) comments and provides r01 Haiyang (Huawei) comments Jari (NTT DOCOMO) comments Jari (NTT DOCOMO) responds Pallab (Nokia) responds to Haiyang (Huawei) and Jari (NTT DOCOMO) Haiyang (Huawei) further comments Belen (Ericsson) provides comments Jari (NTT DOCOMO) responds to Haiyang Jari (NTT DOCOMO) provides r02, responds to Belen Pallab (Nokia) asks for clarification on r02 to Jari (NTT DOCOMO) Jari (NTT DOCOMO) provides r03, responds to Pallab Belen (Ericsson) asks about r03 Jari (NTT DOCOMO) responds to Belen Belen (Ericsson) is okay with r03 Pallab (Nokia) OK with r03 Haiyang (Huawei) is also OK with r03. Objects to r00, r01 and r02 (just in case). ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Revised |
| 6.6 | S2-2201485 | CR | Approval | 23.502 CR3375R1 (Rel-16, 'F'): UP path change notification to the AF | NTT DOCOMO | Rel-16 | Revision of S2-2200736r03. Approved | Agreed | |
| 6.6 | S2-2200756 | CR | Approval | 23.502 CR3376 (Rel-17, 'A'): UP path change notification to the AF | NTT DOCOMO | Rel-17 | r00 agreed. Revised to S2-2201486. | ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Revised |
| 6.6 | S2-2201486 | CR | Approval | 23.502 CR3376R1 (Rel-17, 'A'): UP path change notification to the AF | NTT DOCOMO | Rel-17 | Revision of S2-2200756r00. Approved | Agreed | |
| 6.6 | S2-2200842 | CR | Approval | 23.503 CR0673R1 (Rel-17, 'F'): BSF service update for session binding information update | China Mobile | Rel-17 | Revision of (Noted) S2-2108421 from S2#148E. Postponed | Belen (Ericsson) provides comments Dan (China Mobile) provides r01 Belen (Ericsson) provides comments to r01 Dan (China Mobile) provides response Belen (Ericsson) provides comments, proposes to postpone this CR. ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== Dan (China Mobile) reply Dan (China Mobile) ok to postpond to next meeting ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Postponed |
| 6.6 | S2-2200844 | CR | Approval | 23.502 CR3234R1 (Rel-17, 'F'): BSF service update for session binding information update | China Mobile | Rel-17 | Revision of (Noted) S2-2108420 from S2#148E. Postponed | Belen (Ericsson) provides comments Dan (China Mobile) reply Dan (China Mobile) provide r01 Belen (Ericsson) comments on r01 Haiyang (Huawei) comments that a new related procedure (not only the service) will be more helpful. Dan (China Mobile) provide r02 ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== Dan (China Mobile) suggest maybe we can approve r02 for this emeeting? Belen (Ericsson) asks to postpone this discussion for next meeting Dan (China Mobile) ok to postpone this discussion for next meeting ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Postponed |
| 6.7 | - | - | - | 3GPP access specific functionality and flows | - | - | Docs:=8 | - | |
| 6.7 | S2-2200052 | LS In | Information | LS from CT WG4: Reply LS on Insufficient UE Capabilities Cause Value | CT WG4 (C4-216371) | Rel-16 | Noted | Hannu (Nokia) proposes to note this LS. It is only CC to us and there is no action for SA2. ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Noted |
| 6.7 | S2-2200024 | LS In | Action | LS on indication of direct data forwarding availability | RAN WG3 (R3-216176) | Rel-16 | Revision of Postponed S2-2109008 from S2#148E. Noted | Fenqin (Huawei) comments Hannu (Nokia) supports Fenqin's view and proposes that if the CRs can be agreed the SA2 need not reply to this LS. Otherwise, the LS can be left open for future actions. ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Noted |
| 6.7 | S2-2200336 | CR | Approval | 23.502 CR3344 (Rel-16, 'F'): Data forwarding indication during HO | Ericsson | Rel-16 | r04 agreed. Revised to S2-2201487, merging S2-2200237 | Juan Zhang (Qualcomm) proposes to merge S2-2200237 into this one and provides r01. Hannu (Nokia) supports the merged r01 and comments. Qian (Ericsson) thanks Juan Zhang (Qualcomm) for the merge and provide r02. Qian (Ericsson) comments and provides r03. Chris (Vodafone) comments. Juan Zhang (Qualcomm) is OK with r03. Qian (Ericsson) comments and provides r04. ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== Juan Zhang (Qualcomm) is OK with r04. ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Revised |
| 6.7 | S2-2201487 | CR | Approval | 23.502 CR3344R1 (Rel-16, 'F'): Data forwarding indication during HO | Ericsson, Qualcomm Incorporated | Rel-16 | Revision of S2-2200336r04, merging S2-2200237. Approved | Agreed | |
| 6.7 | S2-2200337 | CR | Approval | 23.502 CR3345 (Rel-17, 'A'): Data forwarding indication during HO | Ericsson | Rel-17 | r00 agreed. Revised to S2-2201488, merging S2-2200238 | Juan Zhang (Qualcomm) proposes to merge S2-2200238 into this one and provides r01. Qian (Ericsson) thanks Juan Zhang (Qualcomm) for the merge and provides r02. Qian (Ericsson) comments and provides r03. Juan Zhang (Qualcomm) is OK with r03. Qian (Ericsson) provides r04 to synch with 0336. ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== Juan Zhang (Qualcomm) is OK with r04. ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Revised |
| 6.7 | S2-2201488 | CR | Approval | 23.502 CR3345R1 (Rel-17, 'A'): Data forwarding indication during HO | Ericsson, Qualcomm Incorporated | Rel-17 | Revision of S2-2200337r00, merging S2-2200238. Approved | Agreed | |
| 6.7 | S2-2200237 | CR | Approval | 23.502 CR3328 (Rel-16, 'F'): Direct Forwarding Path Availability in the Handover Required message | Qualcomm Incorporated | Rel-16 | Merged into S2-2201487 | Juan Zhang (Qualcomm) proposes to merge this paper to S2-2200336. ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Merged |
| 6.7 | S2-2200238 | CR | Approval | 23.502 CR3329 (Rel-17, 'A'): Direct Forwarding Path Availability in the Handover Required message | Qualcomm Incorporated | Rel-17 | Merged into S2-2201488 | Juan Zhang (Qualcomm) proposes to merge this CR into S2-2200337. Qian (Ericsson) thanks Juan Zhang (Qualcomm) for the merge and provides r02. Qian (Ericsson) indicates that the previous comment is for 0377. ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Merged |
| 6.8 | - | - | - | Specific services support | - | - | Docs:=2 | - | |
| 6.8 | S2-2200222 | CR | Approval | 23.501 CR3473 (Rel-17, 'F'): 5G-EIR clarification | Ericsson | Rel-17 | r03 agreed. Revised to S2-2201489. | Hannu (Nokia) can't agree to prohibit shared EIR and proposes r01. Shabnam (Ericsson) agrees with Hannu's understanding, revises the wording to reflect the intent more clearly in r02. Fenqin (Huawei) proposes r03. Shabnam (Ericsson) thanks, I am good with r03. Hannu (Nokia) supports r03. ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Revised |
| 6.8 | S2-2201489 | CR | Approval | 23.501 CR3473R1 (Rel-17, 'F'): 5G-EIR clarification | Ericsson | Rel-17 | Revision of S2-2200222r03. Approved | Agreed | |
| 6.9 | - | - | - | Interworking and Migration | - | - | Docs:=3 | - | |
| 6.9 | S2-2200206 | CR | Approval | 23.502 CR3325 (Rel-17, 'F'): Correction related to EPS to 5GC HO. | Ericsson | Rel-17 | r01 agreed. Revised to S2-2201490. | Fenqin(Huawei) comment and provides r01. Magnus H (Ericsson) comments ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== Magnus H (Ericsson) accepts r01 ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Revised |
| 6.9 | S2-2201490 | CR | Approval | 23.502 CR3325R1 (Rel-17, 'F'): Correction related to EPS to 5GC HO. | Ericsson | Rel-17 | Revision of S2-2200206r01. Approved | Agreed | |
| 6.9 | S2-2200959 | CR | Approval | 23.501 CR3355R1 (Rel-17, 'F'): Clarification on mobility from NG-RAN to GERAN/UTRAN | Nokia, Nokia Shanghai Bell | Rel-17 | Revision of (Postponed) S2-2108303 from S2#148E. CC#2: Postponed | Qian (Ericsson) provides comments Alessio(Nokia) asks Ericsson to disclose the good practices so they become part of the standard. Qian (Ericsson) responds and provides r01. Zhendong (ZTE):ask question for clarification Zhendong (ZTE): provides response Alessio(Nokia) replies Qian (Ericsson) comments. Alessio(Nokia) comments. Qian (Ericsson) responds. ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== alessio(Nokia) provides r02 based on comments. Qian (Ericsson) comments and provides r03. Fenqin (Huawei) ask a question Fenqin (Huawei) responds alessio(Nokia) provides the small update of r03 in CC#2 subfolder on 2-3G IWK Qian (Ericsson) proposes to go with r01. It can be discussed if r03(which is uploaded after revision deadline) can be agreed in CC#2. Qian (Ericsson) objects to the removal of the text on top of r03. Fenqin (Huawei) we can go r01 alessio(Nokia) r01 is not really moving us anywhere forward as everyone knows where to find T-ADS. so we cannot live with R01. alessio(Nokia) cannot go with R01 Fenqin (Huawei) comments. Alessio (Nokia) comments that this is R0. so we are really happy to go with R0 if this is ok. Qian (Ericsson) comments what Fenqin(Huawei) proposed is different from R0. There are extra text need to be removed from r0 ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Postponed |
| 6.10 | - | - | - | Non-3GPP access specific functionality and flows | - | - | Docs:=4 | - | |
| 6.10 | S2-2200782 | CR | Approval | 23.501 CR3536 (Rel-16, 'F'): Corrections to combined N3IWF/ePDG Selection | Lenovo, Motorola Mobility | Rel-16 | r01 agreed. Revised to S2-2201491. | Josep (DT) asks questions for clarification. ePDG or N3IWF is now ePDG AND N3IWF Stefan (Ericsson) asks questions for clarification Apostolis (Lenovo) responds to Stefan's (Ericsson) questions for clarification Apostolis (Lenovo) responds to Josep's (DT) questions for clarification. Myungjune (LGE) comments. Apostolis (Lenovo) responds to Myungjune's (LGE) question. Myungjune (LGE) replies to Apostolis (Lenovo) Apostolis (Lenovo) provides further comments to Myungjune (LGE). Stefan (Ericsson) provides further comments Apostolis (Lenovo) responds to Stefan's (Ericsson) suggestion. Stefan (Ericsson) replies to Apostolis Apostolis (Lenovo) provides r01 with the requested clarifications. ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Revised |
| 6.10 | S2-2201491 | CR | Approval | 23.501 CR3536R1 (Rel-16, 'F'): Corrections to combined N3IWF/ePDG Selection | Lenovo, Motorola Mobility | Rel-16 | Revision of S2-2200782r01. Approved | Agreed | |
| 6.10 | S2-2200793 | CR | Approval | 23.501 CR3538 (Rel-17, 'A'): Corrections to combined N3IWF/ePDG Selection | Lenovo, Motorola Mobility | Rel-17 | r00 agreed. Revised to S2-2201492. | ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Revised |
| 6.10 | S2-2201492 | CR | Approval | 23.501 CR3538R1 (Rel-17, 'A'): Corrections to combined N3IWF/ePDG Selection | Lenovo, Motorola Mobility | Rel-17 | Revision of S2-2200793r00. Approved | Agreed | |
| 6.11 | - | - | - | Framework functions | - | - | Docs:=2 | - | |
| 6.11 | S2-2200290 | CR | Approval | 23.502 CR3335 (Rel-17, 'F'): Internal 23.502 alignment on UE addressing information that an AF can provide | Nokia, Nokia Shanghai Bell | Rel-17 | r01 agreed. Revised to S2-2201493. | Laurent (Nokia): provides r01 ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Revised |
| 6.11 | S2-2201493 | CR | Approval | 23.502 CR3335R1 (Rel-17, 'F'): Internal 23.502 alignment on UE addressing information that an AF can provide | Nokia, Nokia Shanghai Bell | Rel-17 | Revision of S2-2200290r01. Approved | Agreed | |
| 7 | - | - | - | Rel-16 Maintenance for 5G (excluding 5GS_Ph1) | - | - | Docs:=0 | - | |
| 7.1 | - | - | - | Architecture enhancements for 3GPP support of advanced V2X services (eV2XARC) | - | - | Docs:=1 | - | |
| 7.1 | S2-2200218 | CR | Approval | 23.287 CR0170R1 (Rel-17, 'F'): V2X Policy provisioning request | Ericsson, Huawei | Rel-17 | Revision of (Noted) S2-2108340 from S2#148E. Noted | LaeYoung (LGE) comments that this CR needs to be discussed with the papers for the same issue in AI#8.8. Cai Simon (Nokia) agrees with the comments from LaeYoung (LGE) and suggest postponing the paper Hong (Qualcomm) propose to NOTE. LaeYoung (LGE) also proposes to NOTE this CR. Cai Simon(Nokia) also support to note the paper ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== Scott(Inspur) support the paper and object to note it. Leo (Deutsche Telekom) also supports to note the CR. ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== Changhong (Intel) objects to this paper. | Noted |
| 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:=1 | - | |
| 7.4 | S2-2201164 | CR | Approval | 23.501 CR3572 (Rel-17, 'F'): UE Radio Capability change between Category M and E-UTRA | Qualcomm Incorporated | Rel-17 | Noted | Steve (Huawei) Asks what is different to the existing procedures? Hannu (Nokia) replies to Steve (Huawei) and proposes r01. Qian (Ericsson) provides comments Miguel (Qualcomm) answers the questions from Steve, Qian and Hannu and provides r02 Hannu (Nokia) replies to Qian (Ericsson) that generalization to any RAT Type in r01 was intentional. Hannu (Nokia) provides r03 and explains why. Guillaume (MediaTek Inc.) comments and objects to this CR as well. Guillaume (MediaTek Inc.) objects to r03. Hannu (Nokia) objects to the proposal that UE capability change would be a topic for RAN2 to decide. Guillaume (MediaTek Inc.) objects to Hannu's statement. Steve (Huawei) This needs and requires RAN2 work to complete, which RAN2 have already minuted they won't discuss further. Miguel (Qualcomm) clarifies this has nothing to do with RAN2 'fallback' discussions, provides r03. Hannu (Nokia) comments. ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== Miguel (Qualcomm) comments on Steve's understanding Miguel (Qualcomm) provides r04 (clarifies previous claim to provide r03 was wrong as r03 already existed). Steve (Huawei) comments Miguel (Qualcomm) answers Steve's question Steve (Huawei) the CR does not change anything, not needed. Hannu (Nokia) supports the analysis from Steve(Huawei) that only the first CN related change in the CR is needed (as the proposed UE behaviour is specified already). Leo (Deutsche Telekom) proposes to NOTE the CR. ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== Guillaume (MediaTek Inc.) repeats that no CR is needed in view of the current requirement that a Cat M UE is a Cat M UE and signals itself as such. | Noted |
| 7.5 | - | - | - | Enablers for Network Automation for 5G (eNA) | - | - | Docs:=0 | - | |
| 7.6 | - | - | - | Enhancement to the 5GC Location Services (5G_eLCS) | - | - | Docs:=1 | - | |
| 7.6 | S2-2200047 | LS In | Information | Reply LS on LCS MO-LR Procedure in 5G | CT WG1 (C1-217277) | Rel-16 | Noted | Yunjing (CATT) proposes to note the LS. Runze (Huawei) proposes to note the paper. ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Noted |
| 7.7 | - | - | - | 5GS Enhanced support of Vertical and LAN Services (Vertical_LAN) | - | - | Docs:=30 | - | |
| 7.7 | S2-2200302 | CR | Approval | 23.501 CR3486 (Rel-16, 'F'): Scheduled Traffic not used for TSCAI | Ericsson | Rel-16 | r03 agreed. Revised to S2-2201494. | Haiyang (Huawei) comments. Jari (NTT DOCOMO) comments. Shabnam (Ericsson) the intention was to remove only PSFP related info but DoCoMo suggestion works well, so I provide r01 with your suggestion. Zhendong (ZTE): provides the r02 Haiyang (Huawei) is OK with such approach, provides r03 with editorial changes. ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Revised |
| 7.7 | S2-2201494 | CR | Approval | 23.501 CR3486R1 (Rel-16, 'F'): Scheduled Traffic not used for TSCAI | Ericsson | Rel-16 | Revision of S2-2200302r03. Approved | Agreed | |
| 7.7 | S2-2200303 | CR | Approval | 23.501 CR3487 (Rel-17, 'A'): Scheduled Traffic not used for TSCAI | Ericsson | Rel-17 | r00 agreed. Revised to S2-2201495. | ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Revised |
| 7.7 | S2-2201495 | CR | Approval | 23.501 CR3487R1 (Rel-17, 'A'): Scheduled Traffic not used for TSCAI | Ericsson | Rel-17 | Revision of S2-2200303r00. Approved | Agreed | |
| 7.7 | S2-2200386 | CR | Approval | 23.501 CR3496 (Rel-16, 'F'): Requirement for signalling separate IMEI for each network subscription | Qualcomm Incorporated | Rel-16 | CC#2: Postponed | Qianghua (Huawei) provides r01 Devaki (Nokia) comments. ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== Xiaowan (vivo) disagree r01 and request to revoke the removal of 'when it registers to the network' Devaki (Nokia) proposes to postpone the paper (seems authors have not had time to answer to the comments prior to the deadline, I assume it was not so important to resolve during this meeting). Qianghua (Huawei) OK to postpone and questions the rational for disagreement from vivo Xiaowan(vivo) replies to Qianghua (Huawei) and can accept r01 if 'uses different network subscriptions to' is added, i.e. the whole sentence is 'When a UE uses different network subscriptions to register simultaneously to a PLMN and a SNPN, the UE shall use a separate PEI for each network subscription.' Qianghua (Huawei) OK with your proposal Haris(Qualcomm) responds Haris(Qualcomm) provides post-deadline r02 in DRAFTS based on text from Qianghua Devaki (Nokia) ok with the technical updates in r02, still prefer the updates for both Rel-16/Rel-17 in the right section (5.30.2.3) but can live with r02 for now. ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Postponed |
| 7.7 | S2-2200390 | CR | Approval | 23.501 CR3360R1 (Rel-16, 'F'): Mapping TSCAI between TSN GM clock and 5GS clock | NTT DOCOMO, Qualcomm | Rel-16 | Revision of (Noted) S2-2108319 from S2#148E. Approved | Qianghua (Huawei) raises strong concerns Jari (NTT DOCOMO) responds to Qianghua Qianghua (Huawei) replies Jari (NTT DOCOMO) responds to Qianghua (Huawei) György (Ericsson) comments. Jari (NTT DOCOMO) comments Qianghua (Huawei) provides comments Jari (NTT DOCOMO) responds Qianghua Zhendong (ZTE): provides comments ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== Qianghua (Huawei) OK for r00 with the approval of r02 of 0391 ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Agreed |
| 7.7 | S2-2200391 | CR | Approval | 23.502 CR3224R1 (Rel-16, 'F'): Mapping TSCAI between TSN GM clock and 5GS clock | NTT DOCOMO, Qualcomm | Rel-16 | Revision of (Noted) S2-2108321 from S2#148E. r02 agreed. Revised to S2-2201496. | Qianghua (Huawei) raises strong concerns György (Ericsson) comments. Jari (NTT DOCOMO) provides r01 Qianghua (Huawei) provides r02 Jari ()NTT DOCOMO) disagrees with r02, comments Qianghua (Huawei) replies Qianghua (Huawei) cannot accept r00, r01. And replies again Jari (NTT DOCOMO) responds to Qianghua Qianghua (Huawei) replies to Jari ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== Qianghua (Huawei) OK to go with r02 ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Revised |
| 7.7 | S2-2201496 | CR | Approval | 23.502 CR3224R2 (Rel-16, 'F'): Mapping TSCAI between TSN GM clock and 5GS clock | NTT DOCOMO, Qualcomm | Rel-16 | Revision of S2-2200391r02. Approved | Agreed | |
| 7.7 | S2-2200392 | CR | Approval | 23.501 CR3414R1 (Rel-17, 'F'): Mapping TSCAI between TSN GM clock and 5GS clock | NTT DOCOMO, Qualcomm | Rel-17 | Revision of (Noted) S2-2108695 from S2#148E. r02 agreed. Revised to S2-2201497. | Qianghua (Huawei) raises strong concerns György (Ericsson) comments. Jari (NTT DOCOMO) responds to György Devaki (Nokia) has concerns with the paper, believes that the paper is not needed at all (proposed approach does not fit Vertical_LAN as TSCTSF is not applicable for Rel-16). Jari (NTT DOCOMO) responds to Devaki Jari (NTT DOCOMO) provides r01 Qianghua (Huawei) provides comments Jari (NTT DOCOMO) responds to Qianghua Devaki (Nokia) comments. Devaki (Nokia) provides r02. ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== Jari (NTT DOCOMO) prefers r01, can agree r02 as well Qianghua (Huawei) OK with r01 and r02 ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== Devaki (Nokia) comments that we cannot agree to r01 to be clear. Devaki (Nokia) prefers r02. Chunshan (CATT) provides comments. Jari (NTT DOCOMO) responds to Chunshan | Revised |
| 7.7 | S2-2201497 | CR | Approval | 23.501 CR3414R2 (Rel-17, 'F'): Mapping TSCAI between TSN GM clock and 5GS clock | NTT DOCOMO, Qualcomm | Rel-17 | Revision of S2-2200392r02. Approved | Agreed | |
| 7.7 | S2-2200393 | CR | Approval | 23.502 CR3225R1 (Rel-17, 'A'): Mapping TSCAI between TSN GM clock and 5GS clock | NTT DOCOMO, Qualcomm | Rel-17 | Revision of (Noted) S2-2108323 from S2#148E. r00 agreed. Revised to S2-2201498. | ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Revised |
| 7.7 | S2-2201498 | CR | Approval | 23.502 CR3225R2 (Rel-17, 'A'): Mapping TSCAI between TSN GM clock and 5GS clock | NTT DOCOMO, Qualcomm | Rel-17 | Revision of S2-2200393r00. Approved | Agreed | |
| 7.7 | S2-2200633 | CR | Approval | 23.501 CR3521 (Rel-16, 'F'): Clarification for Routing Indicator on SNPN-enabled UE | Huawei, HiSilicon | Rel-16 | r03 agreed. Revised to S2-2201499. | Josep (DT) questions the need for this CR. Qianghua (Huawei) provides r01 Peter Hedman (Ericsson) provides r02 and comments Devaki (Nokia) comments R02 is not available in SA2#149E/revisions folder. Seems it was uploaded to a wrong folder. Qianghua (Huawei) provides r03 ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Revised |
| 7.7 | S2-2201499 | CR | Approval | 23.501 CR3521R1 (Rel-16, 'F'): Clarification for Routing Indicator on SNPN-enabled UE | Huawei, HiSilicon, Ericsson | Rel-16 | Revision of S2-2200633r03. Approved | Agreed | |
| 7.7 | S2-2200634 | CR | Approval | 23.501 CR3522 (Rel-17, 'F'): Clarification for Routing Indicator on SNPN-enabled UE | Huawei, HiSilicon | Rel-17 | r02 agreed. Revised to S2-2201500. | Josep (DT) asks why this CR (R17) is not a pure mirror of S2-2200633 (R16). Qianghua (Huawei) replies Peter (Ericsson) provides comments Qianghua (Huawei) provides r01 Peter Hedman (Ericsson) provides r02 ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Revised |
| 7.7 | S2-2201500 | CR | Approval | 23.501 CR3522R1 (Rel-17, 'F'): Clarification for Routing Indicator on SNPN-enabled UE | Huawei, HiSilicon, Ericsson, Nokia, Nokia Shanghai Bell | Rel-17 | Revision of S2-2200634r02. Approved | Agreed | |
| 7.7 | S2-2201050 | CR | Approval | 23.501 CR3557 (Rel-16, 'F'): LLDP neighbor discovery information fixes | Nokia, Nokia Shanghai Bell | Rel-16 | r02 agreed. Revised to S2-2201501. | Qianghua (Huawei) provides r01 Zhendong (ZTE): provides r02 Devaki (Nokia) fine with r01. ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Revised |
| 7.7 | S2-2201501 | CR | Approval | 23.501 CR3557R1 (Rel-16, 'F'): LLDP neighbor discovery information fixes | Nokia, Nokia Shanghai Bell | Rel-16 | Revision of S2-2201050r02. Approved | Agreed | |
| 7.7 | S2-2201051 | CR | Approval | 23.501 CR3558 (Rel-17, 'F'): LLDP neighbor discovery information fixes | Nokia, Nokia Shanghai Bell | Rel-17 | r00 agreed. Revised to S2-2201502. | Qianghua (Huawei) questions the CR category F Devaki (Nokia) fine with r01. ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Revised |
| 7.7 | S2-2201502 | CR | Approval | 23.501 CR3558R1 (Rel-17, 'A'): LLDP neighbor discovery information fixes | Nokia, Nokia Shanghai Bell | Rel-17 | Revision of S2-2201051r00. Approved | Agreed | |
| 7.7 | S2-2201154 | CR | Approval | 23.501 CR3566 (Rel-16, 'F'): Handling of untagged frames in TSN scenarios | Qualcomm Incorporated | Rel-16 | r03 agreed. Revised to S2-2201503. | Haiyang (Huawei) comments. Sebastian (Qualcomm) replies to Huawei Saso (Intel) asks a question Sebastian (Qualcomm) replies to Saso Zhendong (ZTE): provides comments Devaki (Nokia) comments. Zhendong (ZTE): provides r01 Sang-Jun (Samsung) also prefers option 2. Haiyang (Huawei) also prefers Option 2 and provides r02. Sebastian (Qualcomm) provides r03 ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== Haiyang (Huawei) can accept r03. ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Revised |
| 7.7 | S2-2201503 | CR | Approval | 23.501 CR3566R1 (Rel-16, 'F'): Handling of untagged frames in TSN scenarios | Qualcomm Incorporated | Rel-16 | Revision of S2-2201154r03. Approved | Agreed | |
| 7.7 | S2-2201157 | CR | Approval | 23.501 CR3568 (Rel-17, 'A'): Handling of untagged frames in TSN scenarios | Qualcomm Incorporated | Rel-17 | r00 agreed. Revised to S2-2201504. | ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Revised |
| 7.7 | S2-2201504 | CR | Approval | 23.501 CR3568R1 (Rel-17, 'A'): Handling of untagged frames in TSN scenarios | Qualcomm Incorporated | Rel-17 | Revision of S2-2201157r00. Approved | Agreed | |
| 7.7 | S2-2201159 | CR | Approval | 23.501 CR3569 (Rel-16, 'F'): Add missing SupportedListMax for gate control information in PMIC and BMIC | Qualcomm Incorporated | Rel-16 | r01 agreed. Revised to S2-2201505. | Zhendong (ZTE): provides comments Devaki (Nokia) provides r01. Sebastian (Qualcomm) replies Sang-Jun (Samsung) comments. ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Revised |
| 7.7 | S2-2201505 | CR | Approval | 23.501 CR3569R1 (Rel-16, 'F'): Add missing SupportedListMax for gate control information in PMIC and BMIC | Qualcomm Incorporated | Rel-16 | Revision of S2-2201159r01. Approved | Agreed | |
| 7.7 | S2-2201161 | CR | Approval | 23.501 CR3570 (Rel-17, 'A'): Add missing SupportedListMax for gate control information in PMIC and UMIC | Qualcomm Incorporated | Rel-17 | r00 agreed. Revised to S2-2201506. | Sang-Jun (Samsung) proposes to revise 1161 according to 1159 revisions. Sebastian (Qualcomm) clarifies that mirrors are typically only revised once the related CR has been agreed ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Revised |
| 7.7 | S2-2201506 | CR | Approval | 23.501 CR3570R1 (Rel-17, 'A'): Add missing SupportedListMax for gate control information in PMIC and UMIC | Qualcomm Incorporated | Rel-17 | Revision of S2-2201161r00. Approved | Agreed | |
| 7.7 | S2-2201167 | CR | Approval | 23.501 CR3574 (Rel-16, 'F'): Addressing open issues for time synchronization | Qualcomm Incorporated | Rel-16 | r03 agreed. Revised to S2-2201507. | Shabnam (Ericsson) provides r01, as our understanding of Issue#4 and Issue#5 means no changes to Rel-16. Sebastian (Qualcomm) replies Shabnam (Ericsson) provides response. Sebastian (Qualcomm) replies to Ericsson and provides r02 Shabnam (Ericsson) provides response in line and asks if we can have a revision if we have agreement. Sebastian (Qualcomm) replies to Shabnam and provides r03 ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Revised |
| 7.7 | S2-2201507 | CR | Approval | 23.501 CR3574R1 (Rel-16, 'F'): Addressing open issues for time synchronization | Qualcomm Incorporated | Rel-16 | Revision of S2-2201167r03. Approved | Agreed | |
| 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:=2 | - | |
| 7.10 | S2-2201095 | CR | Approval | 23.502 CR3409 (Rel-16, 'F'): Missing QoS Monitoring report in the Npcf_SMPolicyControl_Update service | Lenovo, Motorola Mobility | Rel-16 | Approved | ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Agreed |
| 7.10 | S2-2201096 | CR | Approval | 23.502 CR3410 (Rel-17, 'A'): Missing QoS Monitoring report in the Npcf_SMPolicyControl_Update service | Lenovo, Motorola Mobility | Rel-17 | Merged into S2-2201484 | Mirko (Huawei) suggests to note the Rel-17 version of this CR (or to consider it merged) due to a conflict with the update done by S2-2200682. Genadi (Lenovo) is fine to merge this CR into S2-2200682. ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Merged |
| 7.11 | - | - | - | Enhancement of Network Slicing (eNS) | - | - | Docs:=2 | - | |
| 7.11 | S2-2201262 | LS In | Information | LS from SA WG5: Reply LS on slicing management aspects in relation to SEAL | SA WG5 (S5-221548) | Rel-17 | Noted | ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Noted |
| 7.11 | S2-2201263 | LS In | Information | LS from SA WG5: Reply LS on network slice management service consumption | SA WG5 (S5-221560) | Rel-17 | Noted | ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Noted |
| 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:=11 | - | |
| 7.15 | S2-2200288 | DISCUSSION | Agreement | Handover of a PDU Session from 3GPP to untrusted non-3GPP access (I-SMF case). | Nokia, Nokia Shanghai Bell | Rel-16 | Noted | ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Noted |
| 7.15 | S2-2200293 | CR | Approval | 23.502 CR3336 (Rel-16, 'F'): Handover of a PDU Session from 3GPP to untrusted non-3GPP access (I-SMF case) | Nokia, Nokia Shanghai Bell | Rel-16 | CC#2: r00 + changes agreed. Revised to S2-2201679. | Fenqin (Huawei) provides r01 Jinguo (ZTE) comments Laurent (Nokia): Comments Jinguo (ZTE) response to Laurent and provide r02 Laurent (Nokia): potential concerns with r02 Jinguo(ZTE) replies ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== Fenqin (ZTE) comments. Jinguo(ZTE) response. Stefan (Ericsson) comments Laurent (Nokia): Same point as Stefan about R02. can only live with R00 Fenqin (Huawei) comments Fenqin (Huawei) comments and provides r03 Jinguo(ZTE) response to Stefan(Ericsson) Fenqin(Huawei) response to Laurent(Nokia) and suggest to go r03 and bring to CC#2. Stefan (Ericsson) replies to Jinguo Jinguo(ZTE) comments Laurent (Nokia): answers Jinguo(ZTE) response and can live with r03 Laurent (Nokia): proposes R00 with following modification: '4) Figure 4.9.2.4.2-1 step 3 involving I-SMF instead of V-SMF, starting from step 5c of clause 4.3.4.3'; + have this handled at CC2 ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== Laurent (Nokia): proposes R00 with following modification: '4) Figure 4.9.2.4.2-1 step 3 involving I-SMF instead of V-SMF starting from step 5c of Figure 4.3.4.3-1 and up to step 15 of Figure 4.3.4.3-1 Fenqin (Huawei) still prefer to go to R03 | Revised |
| 7.15 | S2-2201679 | CR | Approval | 23.502 CR3336R1 (Rel-16, 'F'): Handover of a PDU Session from 3GPP to untrusted non-3GPP access (I-SMF case) | Nokia, Nokia Shanghai Bell | Rel-16 | Revision of S2-2200293r00 + changes. CC#2: This CR was agreed | Agreed | |
| 7.15 | S2-2200294 | CR | Approval | 23.502 CR3337 (Rel-17, 'A'): Handover of a PDU Session from 3GPP to untrusted non-3GPP access (I-SMF case) | Nokia, Nokia Shanghai Bell | Rel-17 | CC#2: Revised to S2-2201680. | ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Revised |
| 7.15 | S2-2201680 | CR | Approval | 23.502 CR3337R1 (Rel-17, 'A'): Handover of a PDU Session from 3GPP to untrusted non-3GPP access (I-SMF case) | Nokia, Nokia Shanghai Bell | Rel-17 | Revision of S2-2200294. CC#2: This CR was agreed | Agreed | |
| 7.15 | S2-2200877 | CR | Approval | 23.502 CR3386 (Rel-16, 'F'): Mobiltiy between HPLMN and VPLMN | Huawei, HiSilicon | Rel-16 | r05 agreed. Revised to S2-2201508. | Laurent (Nokia): this clarification does not justify a R16 CR. thus we have concerns with this non FASMO CR. OK for the R17 clarification Fenqin (Huawei): give a response on the reason why it is proposed back to Rel-16. Stefan (Ericsson) has similar understanding as Fenqin Laurent (Nokia): provides r01 Fenqin (Huawei) provides r02 Stefan (Ericsson) provides r03 Fenqin (Huawei) is fine with r03 Chris (Vodafone) raises a question on r03. Stefan (Ericsson) provides r04 Fenqin (Huawei) provides response and r05. Either r04 or r05 work for me. ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Revised |
| 7.15 | S2-2201508 | CR | Approval | 23.502 CR3386R1 (Rel-16, 'F'): Mobiltiy between HPLMN and VPLMN | Huawei, HiSilicon, Ericsson | Rel-16 | Revision of S2-2200877r05. Approved | Agreed | |
| 7.15 | S2-2200878 | CR | Approval | 23.502 CR3387 (Rel-17, 'A'): Mobiltiy between HPLMN and VPLMN | Huawei, HiSilicon | Rel-17 | r00 agreed. Revised to S2-2201509. | ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Revised |
| 7.15 | S2-2201509 | CR | Approval | 23.502 CR3387R1 (Rel-17, 'A'): Mobiltiy between HPLMN and VPLMN | Huawei, HiSilicon | Rel-17 | Revision of S2-2200878r00. Approved | Agreed | |
| 7.15 | S2-2200879 | CR | Approval | 23.502 CR3273R1 (Rel-17, 'F'): N9 forwarding tunnel between ULCLs controlled by I-SMF | Huawei, HiSilicon | Rel-17 | Revision of (Postponed) S2-2108678 from S2#148E. r03 agreed. Revised to S2-2201510. | Laurent (Nokia): provides r01 Fenqin (Huawei): provides r02 Stefan (Ericsson) comments Stefan (Ericsson) changes Subject to AI#7.15 Fenqin (Huawei) provides r03 ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Revised |
| 7.15 | S2-2201510 | CR | Approval | 23.502 CR3273R2 (Rel-17, 'F'): N9 forwarding tunnel between ULCLs controlled by I-SMF | Huawei, HiSilicon, Nokia, Nokia Shanghai Bell | Rel-17 | Revision of S2-2200879r03. Approved | Agreed | |
| 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:=6 | - | |
| 7.17 | S2-2200108 | CR | Approval | 23.216 CR0371 (Rel-16, 'F'): MSC Server performing a TMSI reallocation and a MAP Update Location at 5G-SRVCC | Nokia, Nokia Shanghai Bell | Rel-16 | Approved | ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Agreed |
| 7.17 | S2-2200109 | CR | Approval | 23.216 CR0372 (Rel-16, 'F'): AMF interaction with GMLC at SRVCC for an Emergency session | Nokia, Nokia Shanghai Bell | Rel-16 | Postponed | George Foti (Ericsson) proposes to postpone the CR. There is an agreed upon CR in CT4 C4-211668 that should work. Please shows that there is a deployment model where the CT4 CR would not work. Laurent (Nokia): answers George (Ericsson) provides responds George (Ericsson) provides comments ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== Laurent (Nokia): as it seems this is 1-1 discussion, we can also POSTPONE 109 + 110 + 111 ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Postponed |
| 7.17 | S2-2200110 | CR | Approval | 23.502 CR3319 (Rel-16, 'F'): AMF interaction with GMLC at SRVCC for an Emergency session | Nokia, Nokia Shanghai Bell | Rel-16 | Postponed | ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Postponed |
| 7.17 | S2-2200111 | CR | Approval | 23.502 CR3320 (Rel-17, 'A'): AMF interaction with GMLC at SRVCC for an Emergency session | Nokia, Nokia Shanghai Bell | Rel-17 | Postponed | George Foti (Ericsson) proposes to postpone the CR. There is an agreed upon CR in CT4 C4-211668 that should work. Please shows that there is a deployment model where the CT4 CR would not work. Laurent (Nokia): answers George (Ericsson) responds. Please see document 109. Laurent (Nokia): same answer as for Tdoc 109 George (Ericsson) provides comment. ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== Laurent (Nokia): as it seems this is 1-1 discussion, we can also POSTPONE 109 + 110 + 111 ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Postponed |
| 7.17 | S2-2200285 | CR | Approval | 23.216 CR0373 (Rel-16, 'F'): Failure cases for SRVCC from NR to UTRAN | Nokia, Nokia Shanghai Bell | Rel-16 | r01 + changes agreed. Revised to S2-2201674. Tick ME box. Update (When as defined in clause 8.1.2, there is a Failure after UE receives HO command, the UE attempts to return to NG-RAN, ...) | George Foti (Ericsson) provides comments. Zhendong (ZTE): similar comments with ericsson Laurent (Nokia): answers George (Ericsson) provides a comment. So how is a failure message conveyed than in case of MME or SGSN. This has to be a general problem. Zhendong (ZTE): provides response George (Ericsson) provides response. This looks like a general problem than. George (Ericsson) provides additional comment. While this is an error case, we should not implement it for Release 16. For Release 17 this is OK. So we propose to note the CR. Juan Zhang (Qualcomm) supports Ericsson's comments that we should avoid the change for Rel-16. Laurent (Nokia): OK to transform this into a R17 CR Laurent (Nokia): provides r01 ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== George (Ericsson) provides comments. Will that create confusion during implementation with the current subject: 23.216 CR0373 (Rel-16, 'F'): Failure cases for SRVCC from NR to UTRAN Juan Zhang (Qualcomm) provides r02 in draft folder Laurent (Nokia): I think you comment George is on a wrong thread Laurent (Nokia): Juan, your R02 looks good: based on R01: tick ME box and update (When as defined in clause 8.1.2, there is a Failure after UE receives HO command, the UE attempts to return to NG-RAN, ....) ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Revised |
| 7.17 | S2-2201674 | CR | Approval | 23.216 CR0373R1 (Rel-17, 'F'): Failure cases for SRVCC from NR to UTRAN | Nokia, Nokia Shanghai Bell | Rel-17 | Revision of S2-2200285r01 + changes. Approved | Agreed | |
| 8 | - | - | - | Rel-17 WIDs | - | - | Docs:=0 | - | |
| 8.1 | - | - | - | Enablers for Network Automation for 5G - phase 2 (eNA_Ph2) | - | - | Docs:=49 | - | |
| 8.1 | - | - | - | General | - | - | Docs:=4 | - | |
| 8.1 | S2-2200318 | CR | Approval | 23.288 CR0499 (Rel-17, 'F'): Clarification on identifiers used as Target of Analytics Reporting | Ericsson | Rel-17 | r02 agreed. Revised to S2-2201520. | Wang Yuan (Huawei) asks for clarification. Zhang (Ericsson) provides comments Wang Yuan (Huawei) provides r01. Wang Yuan (Huawei) thanks for the clarification and can live with r00. Yannick (Nokia): Nokia requests for clarification. Suggest to postpone the CR to allow further discussion on this issue. Zhang (Ericsson) provides comments to Nokia Yannick (Nokia): Nokia clarifies that r00 is almost ok. Provide r02 based on r00. Zhang (Ericsson) is Ok with r02 ==== 8.X, 9.X, 10.X Revisions Deadline ==== Wang Yuan (Huawei) is OK with r02. ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.1 | S2-2201520 | CR | Approval | 23.288 CR0499R1 (Rel-17, 'F'): Clarification on identifiers used as Target of Analytics Reporting | Ericsson | Rel-17 | Revision of S2-2200318r02. Approved | Agreed | |
| 8.1 | S2-2200845 | CR | Approval | 23.288 CR0508 (Rel-17, 'F'): Clarification on UE related analytics | CATT | Rel-17 | r03 agreed. Revised to S2-2201521. | Wang Yuan (Huawei) comments. Zhang (Ericsson) provides comments Yannick (Nokia): Nokia objects to the proposal. This CR is not a clarification, it introduces functionality that has not been fully studied. This cannot be a correction at this stage of Rel-17. Yingying(CATT) replies to Yuan (Huawei), Zhang (Ericsson), and Yannick (Nokia). Yingying(CATT) provides the r01 in the previous email. Yingying(CATT) provides r02 to update the format and wording. Yannick (Nokia): Nokia object to r01 and r02. Yingying(CATT) is OK with removing 'any UE', provides r03. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Zhang (Ericsson) is OK with r03 Yannick (Nokia): Nokia thanks CATT. Nokia is fine with r03. ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.1 | S2-2201521 | CR | Approval | 23.288 CR0508R1 (Rel-17, 'F'): Clarification on UE related analytics | CATT | Rel-17 | Revision of S2-2200845r03. Approved | Agreed | |
| 8.1 | - | - | - | KI#2 | - | - | Docs:=7 | - | |
| 8.1 | S2-2200317 | CR | Approval | 23.288 CR0498 (Rel-17, 'F'): Clarification on Analytics Transfer for Group of UEs | Ericsson | Rel-17 | Noted | Yannick (Nokia): Nokia cannot accept this proposal. Zhang (Ericsson) provides comments Jungshin (Samsung): ask for clarification Yannick (Nokia): Nokia replies to Ericsson (Zhang). Yingying(CATT) asks for clarification. Zhang (Ericsson) reply to YingYing (CATT) ==== 8.X, 9.X, 10.X Revisions Deadline ==== Zhang (Ericsson) ask if the r0 is OK Yannick (Nokia): Nokia maintain concerns about the proposal. Zhang (Ericsson) response to Yannick (Nokia) Zhang (Ericsson) provides and r01 and ask if it is Ok to be agreed in CC#4 Yannick (Nokia): Nokia maintain concerns about the proposal. Object to r00 and r01. Zhang (Ericsson) provides r02 and ask if it is OK to be discussed in CC#4 Yannick (Nokia): Nokia objects to r02. We have same comments as for r01. Also, no revision was provided for this CR until revision deadline, we are concerned that now we start for the last two hours discussing two revisions r01 and r02, with significant changes. Zhang (Ericsson) suggest to postpone the paper ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 8.1 | S2-2200533 | CR | Approval | 23.288 CR0504 (Rel-17, 'F'): Clarification for Analytics Aggregation without Provision of Area of Interest | China Unicom | Rel-17 | r04 agreed. Revised to S2-2201522. | Mehrdad (Samsung) provides r01 and co-signs this CR. Yannick (Nokia): Nokia provides r02. Mehrdad (Samsung) asks for clarification as r02 is not based on r01 already provided by Samsung. Chi (China Unicom) replies to Mehrdad (Samsung). Mehrdad (Samsung) cannot agree with original revision and r02 Yannick (Nokia): Nokia provides r03, based on r02 and incorporating some changes from r01. Mehrdad (Samsung) provides r04 based on minor changes in r03 and co-signs this. Chi (China Unicom) is fine with r04. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.1 | S2-2201522 | CR | Approval | 23.288 CR0504R1 (Rel-17, 'F'): Clarification for Analytics Aggregation without Provision of Area of Interest | China Unicom, Nokia, Samsung | Rel-17 | Revision of S2-2200533r04. Approved | Agreed | |
| 8.1 | S2-2200534 | CR | Approval | 23.501 CR3517 (Rel-17, 'F'): Clarifications for NWDAF profile and NWDAF discovery | China Unicom | Rel-17 | r02 agreed. Revised to S2-2201523. | Yannick (Nokia): Nokia provides r01. Mehrdad (Samsung) provides r02 and co-signs this CR. Yannick (Nokia): Nokia is fine with r02. Chi (China Unicom) is fine with r02. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.1 | S2-2201523 | CR | Approval | 23.501 CR3517R1 (Rel-17, 'F'): Clarifications for NWDAF profile and NWDAF discovery | China Unicom, Nokia, Samsung | Rel-17 | Revision of S2-2200534r02. Approved | Agreed | |
| 8.1 | S2-2200694 | CR | Approval | 23.288 CR0448R2 (Rel-17, 'F'): CR to resolve conflicts in ML model transferring | ETRI | Rel-17 | Revision of (Postponed) S2-2108436 from S2#148E. Merged into S2-2201363 | Xiaoyan (CATT) provides comments and considers the CR is not needed. Soohwan (ETRI) proposes a way forward. Mall (NTT DOCOMO) propose to merge this CR into S2-2200808. Yannick (Nokia): Nokia agrees with NTT DOCOMO. And encryption of ML models is not under SA2 remit. Soohwan (ETRI) okay with to merge this CR into S2-2200808. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 8.1 | S2-2200808 | CR | Approval | 23.288 CR0488R1 (Rel-17, 'F'): Clarification of transferring ML model during analytics transfer | Lenovo, Motorola Mobility, Nokia, Nokia Shanghai Bell | Rel-17 | Revision of (Postponed) S2-2108713 from S2#148E. CC#4: Postponed | Soohwan (ETRI) asks to add ETRI as a co-signer and provide r01. Xiaoyan (CATT) provides r02 and objects to r00, r01. Soohwan (ETRI) objects r02. Dimitris (Lenovo) objects to r02 Malla (NTT DOCOMO) provides r03 on top of r01. Xiaoyan (CATT) replies to Dimitris (Lenovo). Dimitris (Lenovo) responds to Xiaoyan (CATT) Yannick (Nokia): Nokia objects to r02. Provides r04. Xiaoyan (CATT) objects to r03 and r04, and asks for clarification. Soohwan (ETRI) replies to Xiaoyan (CATT). Yannick (Nokia): Nokia agree with ETRI. Dimitris (Lenovo) agrees with Yannick (Nokia) and Soohwan (ETRI) comments. Asks if Xiaoyan (CATT) can remove their objections Xiaoyan (CATT) replies to Soohwan (ETRI), Yannick (Nokia) and Dimitris (Lenovo). Yannick (Nokia): Nokia maintain objection to r02. Xiaoyan (CATT) replies to Yannick (Nokia). Yannick (Nokia): Nokia maintain objection to r02. ML model sharing can be enhanced in Rel-18. Xiaoyan (CATT) ask for clarification from Yannick (Nokia). Yannick (Nokia): Nokia replies to CATT. Xiaoyan (CATT) requests further clarification from Yannick (Nokia). Malla (NTT DOCOMO) replies to Xiaoyan (CATT). Xiaoyan (CATT) replies to Yannick (Nokia) and Malla (NTT DOCOMO). ==== 8.X, 9.X, 10.X Revisions Deadline ==== Dimitris (Lenovo) proposes to go with r04 Yannick (Nokia): Nokia also supports going with r04 and close an issue that has been discussed for a couple of meetings now. Xiaoyan (CATT) maintains objection to r04 and requests again on considering r02. Soohwan (ETRI) supports to go with r04. Yannick (Nokia): Nokia replies to CATT. Still objects to r02. ==== 8.X, 9.X, 10.X Final Deadline ==== | Postponed |
| 8.1 | - | - | - | KI#4 | - | - | Docs:=10 | - | |
| 8.1 | S2-2200075 | LS In | Action | Reply LS on Network slice information from OAM | SA WG5 (S5-216416) | Rel-17 | Noted | Yannick (Nokia): Nokia believes this LS from SA5 can be noted, no specific action was requested from SA2. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 8.1 | S2-2200586 | CR | Approval | 23.288 CR0507 (Rel-17, 'F'): Remove the statistics value or expected value for load level | Huawei, HiSilicon | Rel-17 | Approved | Zhang (Ericsson) ask for clarification Wang Yuan (Huawei) replies to Zhang. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Agreed |
| 8.1 | S2-2200849 | CR | Approval | 23.288 CR0425R1 (Rel-17, 'F'): Update of Data collection from OAM | Huawei, HiSilicon | Rel-17 | Revision of (Postponed) S2-2105938 from S2#146E. r03 agreed. Revised to S2-2201524. | Yannick (Nokia): Nokia requests for clarification. Susan (Huawei) replies to Yannick (Nokia). Yannick (Nokia): Nokia thank Huawei for the explanation and provides r02. Susan (Huawei) replies to Yannick (Nokia) and provides r03. Yannick (Nokia): Nokia is fine with r03. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.1 | S2-2201524 | CR | Approval | 23.288 CR0425R2 (Rel-17, 'F'): Update of Data collection from OAM | Huawei, HiSilicon | Rel-17 | Revision of S2-2200849r03. Approved | Agreed | |
| 8.1 | S2-2200981 | CR | Approval | 23.501 CR3552 (Rel-17, 'F'): Removal of Nnssf_NSRestriction service | Orange, Samsung | Rel-17 | r01 agreed. Revised to S2-2201525. | Yannick (Nokia): Nokia provides r01. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.1 | S2-2201525 | CR | Approval | 23.501 CR3552R1 (Rel-17, 'F'): Removal of Nnssf_NSRestriction service | Orange, Samsung | Rel-17 | Revision of S2-2200981r01. Approved | Agreed | |
| 8.1 | S2-2200982 | CR | Approval | 23.502 CR3397 (Rel-17, 'F'): Removal of Nnssf_NSRestriction service | Orange, Samsung | Rel-17 | r01 agreed. Revised to S2-2201526. | Yannick (Nokia): Nokia provides r01. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.1 | S2-2201526 | CR | Approval | 23.502 CR3397R1 (Rel-17, 'F'): Removal of Nnssf_NSRestriction service | Orange, Samsung | Rel-17 | Revision of S2-2200982r01. Approved | Agreed | |
| 8.1 | S2-2201045 | CR | Approval | 23.288 CR0509 (Rel-17, 'F'): Correction on service operation to retreive the number of UE and number of PDU session | ZTE | Rel-17 | r04 agreed. Revised to S2-2201527. | Wang Yuan (Huawei) has concerns on original version and provide r01. David (Samsung) agrees with Huawei, provides one further comment. Jinguo (ZTE) asks question for clarification. Yannick (Nokia): Nokia agrees with Huawei and Samsung, and provides r02. Belen (Ericsson) supports r02 Jinguo (ZTE) provides r03 Yannick (Nokia): Nokia provides r04. Malla (NTT DOCOMO) asks question for clarification. Yannick (Nokia): Nokia replies to NTT DOCOMO (Malla). Malla (NTT DOCOMO) replies to Yannick (Nokia) and fine with r04 Jinguo(ZTE) is fine with r04 Wang Yuan (Huawei) is also fine with r04. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.1 | S2-2201527 | CR | Approval | 23.288 CR0509R1 (Rel-17, 'F'): Correction on service operation to retreive the number of UE and number of PDU session | ZTE | Rel-17 | Revision of S2-2201045r04. Approved | Agreed | |
| 8.1 | - | - | - | KI#8 | - | - | Docs:=4 | - | |
| 8.1 | S2-2200030 | LS In | Information | LS from SA WG4: Reply LS to CT3 Questions and Feedback on EVEX | SA WG4 (S4-211647) | Rel-17 | Revision of Postponed S2-2109022 from S2#148E. Noted | Yannick (Nokia): Nokia believes this LS from SA4 can be noted, no specific action was requested from SA2, and there is another LS from SA4 in S2-2200031 on UE data collection and reporting for which we are discussing a proposed reply already. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 8.1 | S2-2200031 | LS In | Action | LS from SA WG4: Reply LS to SA WG2 on UE Data Collection and Reporting | SA WG4 (S4-211648) | Rel-17 | Revision of Postponed S2-2109023 from S2#148E. Response drafted in S2-2200995. Final response in S2-2201528 | ==== 8.X, 9.X, 10.X Final Deadline ==== | Replied to |
| 8.1 | S2-2200995 | LS OUT | Action | [DRAFT] Reply LS on UE data collection and reporting | Samsung | Rel-17 | Response to S2-2200031. r02 agreed. Revised to S2-2201528. | Juan Zhang (Qualcomm) provides comment. Mehrdad (Samsung) replies to Qualcomm. Juan Zhang (Qualcomm) is fine with the proposed rewording. Mehrdad (Samsung) provides r01 with the proposed rewording. Yannick (Nokia): Nokia provides r02. Mehrdad (Samsung) thanks Nokia. We are fine with r02. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Juan Zhang (Qualcomm) is OK with r02. ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.1 | S2-2201528 | LS OUT | Action | Reply LS on UE data collection and reporting | SA WG2 | Rel-17 | Revision of S2-2200995r02. Approved | Approved | |
| 8.1 | - | - | - | KI#9 | - | - | Docs:=2 | - | |
| 8.1 | S2-2200316 | CR | Approval | 23.288 CR0497 (Rel-17, 'F'): Clarification on Dispersion Analytic for identification of Top-Heavy UEs in a location | Ericsson | Rel-17 | r09 agreed. Revised to S2-2201529. | Zhuoyi (China Telecom) asks for clarification. Wang Yuan (Huawei) provides r01 and co-signs this CR. Yannick (Nokia): Nokia provides comments. Wang Yuan (Huawei) replies to Yannick and provide r02. David Weiss (Spirent) addresses and replies to various comments by providing r03. Zhuoyi (China Telecom) provides r04. Yannick (Nokia): Nokia provides r05. Belen (Ericsson) provides r06 David Weiss (Spirent) provides r07 to better align with a recent CT4 CR. Yannick (Nokia): Nokia comments on r07. David Weiss (Spirent) replies to Yannic and provides r08 Yannick (Nokia): Nokia provides r09. ==== 8.X, 9.X, 10.X Revisions Deadline ==== David Weiss (Spirent) replies to Yannic's version r09 Wang Yuan (Huawei) is OK with r09. Yannick (Nokia): Nokia replies to Spirent. ==== 8.X, 9.X, 10.X Final Deadline ==== Manuel (Sandvine) is oka with r09. | Revised |
| 8.1 | S2-2201529 | CR | Approval | 23.288 CR0497R1 (Rel-17, 'F'): Clarification on Dispersion Analytic for identification of Top-Heavy UEs in a location | Ericsson, Huawei, Spirent, Sandvine, China Mobile | Rel-17 | Revision of S2-2200316r09. Approved | Agreed | |
| 8.1 | - | - | - | KI#10 | - | - | Docs:=1 | - | |
| 8.1 | S2-2200971 | CR | Approval | 23.288 CR0462R2 (Rel-17, 'F'): Clarify the Redundant Transmission Experience related analytics | China Mobile, Huawei | Rel-17 | Revision of (Postponed) S2-2108665 from S2#148E. CC#5: Postponed | Zhang (Ericsson) provides comments Susan (Huawei) replies to Zhang (Ericsson) and provides r01. Yannick (Nokia): Nokia provides r02. Susan (Huawei) replies to Yannick (Nokia) and is ok with r02. Hyunsook (LGE) has a concern on r02 and provides r03. Yannick (Nokia): Nokia objects to r03. Zhuoyi (China Telecom): ask for clarification. Yannick (Nokia): Nokia replies to Ericsson (Zhang). Zhang (Ericsson) reply to Yannick (Nokia) Hyunsook (LGE) provides comments ==== 8.X, 9.X, 10.X Revisions Deadline ==== Yannick (Nokia): Nokia suggest to go with r02 in this meeting. Objected to r03 already for the reason that 'value' has no meaning and is not interoperable between the analytics consumer and the NWDAF. Hyunsook (LGE) objects to r02. Yannick (Nokia): Nokia then suggests to note the document. R02 is the only revision we can accept, we object to all other revisions. Zhang (Ericsson) suggest to go with r03 Susan (Huawei) provides r04 as way forward. Zhang (Ericsson) is OK with r04 Hyunsook (LGE) proposes to keep both existing 'Redundant Transmission Experience' text and new editor's note as way forward. Yannick (Nokia): Nokia can live with r04 as proposed by Huawei (Susan). Will not accept adding or keeping text regarding redundant transmission experience value. Hyunsook (LGE) cannot accept r04 and proposes to note it. Susan (Huawei) provides r05 and requests discussion at CC#4. ==== 8.X, 9.X, 10.X Final Deadline ==== | Postponed |
| 8.1 | - | - | - | KI#11 | - | - | Docs:=9 | - | |
| 8.1 | S2-2200179 | CR | Approval | 23.288 CR0494 (Rel-17, 'F'): ADRF ID in the analytics context between NWDAFs | Nokia, Nokia Shanghai Bell | Rel-17 | r03 agreed. Revised to S2-2201530, merging S2-2200532 | Wang Yuan (Huawei) provide r01. Yannick (Nokia): Nokia prefers r00. Wang Yuan (Huawei) asks for further clarifications for r00. Yannick (Nokia): Nokia replies to Huawei. Wang Yuan (Huawei) provide r02. Yannick (Nokia): Nokia is fine with the proposal from Huawei. Provide r03. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Xiaoyan (CATT) is fine with r03 and would like to cosign. Wang Yuan (Huawei) is fine with r03. ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.1 | S2-2201530 | CR | Approval | 23.288 CR0494R1 (Rel-17, 'F'): ADRF ID in the analytics context between NWDAFs | Nokia, Nokia Shanghai Bell, CATT | Rel-17 | Revision of S2-2200179r03, merging S2-2200532. Approved | Agreed | |
| 8.1 | S2-2200182 | CR | Approval | 23.501 CR3471 (Rel-17, 'F'): Cleanup for NWDAF, DCCF, MFAF and ADRF services | Nokia, Nokia Shanghai Bell | Rel-17 | Approved | ==== 8.X, 9.X, 10.X Final Deadline ==== | Agreed |
| 8.1 | S2-2200186 | CR | Approval | 23.502 CR3324 (Rel-17, 'F'): Cleanup for NRF service operations usage for analytics | Nokia, Nokia Shanghai Bell | Rel-17 | r01 agreed. Revised to S2-2201531. | Wang Yuan (Huawei) provide r01 and co-signs this paper. Yannick (Nokia): Nokia is fine with r01. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Yannick (Nokia): Nokia suggests to approve r01. ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.1 | S2-2201531 | CR | Approval | 23.502 CR3324R1 (Rel-17, 'F'): Cleanup for NRF service operations usage for analytics | Nokia, Nokia Shanghai Bell, Huawei | Rel-17 | Revision of S2-2200186r01. Approved | Agreed | |
| 8.1 | S2-2200436 | CR | Approval | 23.288 CR0502 (Rel-17, 'F'): Cleanup for consumers of NWDAF services | Nokia, Nokia Shanghai Bell | Rel-17 | Postponed | Aihua(CMCC) provides r01. Yannick (Nokia): Nokia objects r01. Mehrdad (Samsung) comments Yannick (Nokia): Nokia replies to Samsung. Belen (Ericsson) objects to r01, support initial version. Aihua(CMCC) can't accept r00 since it will destroy the feature that already exists in R16 and R17. Yannick (Nokia): Nokia replies to CMCC. This CR does not 'destroy' any feature because the behaviour described by CMCC is simply not specified in Rel-16 and Rel-17. Aihua(CMCC) suggests to draft an LS to CT3 to ask for clarification. Yannick (Nokia): Nokia replies to China Mobile (Aihua). Aihua(CMCC) agrees with Yannick that SA2 can send LS to CT3 to check with CT3 if such removal occurs. Yannick (Nokia): Nokia provided draft LS out proposal in S2-2201685. Aihua(CMCC) is fine with LS out proposal in S2-2201685 provided by Nokia. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Yannick (Nokia): Nokia suggest to postpone this CR, and wait for CT3 feedback as requested in draft LS out proposal in S2-2201685. ==== 8.X, 9.X, 10.X Final Deadline ==== | Postponed |
| 8.1 | S2-2201685 | LS OUT | Approval | [DRAFT] LS on removing UDM as consumer of expected UE behavioural parameters analytics | Nokia | Created at CC#3. Revised to S2-2201532. | Yannick (Nokia): Nokia provides initial version for draft LS out to CT3 on UDM as consumer for expected UE behaviour analytics. This is related to discussion on CR in S2-2200436. Mehrdad (Samsung) comments Yannick (Nokia): Nokia replies to Samsung. Mehrdad (Samsung) can live with current wording with the assumption that the CR will be postponed until CT3 feedback. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised | |
| 8.1 | S2-2201532 | LS OUT | Approval | LS on removing UDM as consumer of expected UE behavioural parameters analytics | SA WG2 | - | Revision of S2-2201685 | Approved | |
| 8.1 | S2-2200532 | CR | Approval | 23.288 CR0503 (Rel-17, 'F'): ADRF related parameters in Nnwdaf_AnalyticsInfo_ContextTransfer | CATT | Rel-17 | Merged into S2-2201530 | Yannick (Nokia): Nokia asks if this proposal can be merged with S2-2200179. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Xiaoyan (CATT) confirms that S2-2200532 is merged into S2-2200179. ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 8.1 | - | - | - | KI#12 | - | - | Docs:=4 | - | |
| 8.1 | S2-2200319 | CR | Approval | 23.288 CR0500 (Rel-17, 'F'): Correction on Analytics ID on Service Experience | Ericsson | Rel-17 | r09 agreed. Revised to S2-2201533. | Juan Zhang (Qualcomm) provides comments to both r00 and r01. Zhuoyi (China Telecom) comments and provides r01. Belen (Ericsson) replies to QC. David (Samsung) provides r02. Belen (Ericsson) provides r03. David (Samsung) confirms r03 is OK. Yannick (Nokia): Nokia provides comments and r04. Zhuoyi (China Telecom): China Telecom is ok with r03 and r04, and would like to co-sign this paper. Juan Zhang (Qualcomm) provides r05 Leo (Deutsche Telekom) provides comments Yannick (Nokia): Nokia provides r06. Wang Yuan (Huawei) provides r07 and co-signs this paper. Yannick (Nokia): Nokia comments on r07. Wang Yuan (Huawei) asks to ignore r07 and provides r08. Belen (Ericsson) objects to r07 and r08. Ask Huawei Wang Yuan (Huawei) replies to Belen (Ericsson) and provides r09. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.1 | S2-2201533 | CR | Approval | 23.288 CR0500R1 (Rel-17, 'F'): Correction on Analytics ID on Service Experience | Ericsson, Huawei, China Telecom | Rel-17 | Revision of S2-2200319r09. Approved | Agreed | |
| 8.1 | S2-2200320 | CR | Approval | 23.503 CR0692 (Rel-17, 'F'): Correction on Analytics ID on Service Experience | Ericsson | Rel-17 | r03 agreed. Revised to S2-2201534. | Juan Zhang (Qualcomm) provides comments on both r00 and r01. Zhuoyi (China Telecom) comments and provides r01. Belen (Ericsson) asks a question on what a threshold means in the context of RAT or Frequency. Zhuoyi (China Telecom) replies to Ericsson on reporting threshold. Yannick (Nokia): Nokia provides comments. Belen (Ericsson) replies to Nokia comments Zhuoyi (China Telecom) provides r02 and would like to co-sign this paper. Yannick (Nokia): Nokia provides r03. Cannot accept r00, r01 nor r02. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.1 | S2-2201534 | CR | Approval | 23.503 CR0692R1 (Rel-17, 'F'): Correction on Analytics ID on Service Experience | Ericsson, China Telecom | Rel-17 | Revision of S2-2200320r03. Approved | Agreed | |
| 8.1 | - | - | - | KI#15 | - | - | Docs:=5 | - | |
| 8.1 | S2-2200583 | DISCUSSION | Approval | Discussion on who should check the user consent. | Huawei, HiSilicon | Rel-17 | Noted | Yannick (Nokia): Nokia disagree with the proposal in this discussion paper. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 8.1 | S2-2200584 | CR | Approval | 23.288 CR0505 (Rel-17, 'F'): Update for the user consent checking | Huawei, HiSilicon | Rel-17 | r05 agreed. Revised to S2-2201535. | Juan Zhang (Qualcomm) provides comment Yannick (Nokia): Nokia objects to this proposal. Wang Yuan (Huawei) replies and provides r01. Juan Zhang (Qualcomm) objects both r00 and r01. Wang Yuan (Huawei) replies Juan (Qualcomm). Aihua(CMCC) provides comments. Yannick (Nokia): Nokia provides r02. Wang Yuan (Huawei) still has concerns on r02. Belen (Ericsson) provides comments Yannick (Nokia): Nokia provides r03. Wang Yuan (Huawei) is OK with r03 and further provides r04. Yannick (Nokia): Nokia provides r05 and co-signs. Juan Zhang (Qualcomm) is OK with r05. Wang Yuan (Huawei) is OK with r05. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.1 | S2-2201535 | CR | Approval | 23.288 CR0505R1 (Rel-17, 'F'): Update for the user consent checking | Huawei, HiSilicon, Nokia | Rel-17 | Revision of S2-2200584r05. Approved | Agreed | |
| 8.1 | S2-2200733 | CR | Approval | 23.288 CR0489R1 (Rel-17, 'F'): Clarification on including location information for OSE analytics | Lenovo, Motorola Mobility | Rel-17 | Revision of (Postponed) S2-2108716 from S2#148E. r03 agreed. Revised to S2-2201536. | Zhuoyi (China Telecom) ask for clarification. Dimitris (Lenovo) provides r01 Belen (Ericsson) provides comments. Dimitris (Lenovo) provides r02 Yannick (Nokia): Nokia provides r03. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.1 | S2-2201536 | CR | Approval | 23.288 CR0489R2 (Rel-17, 'F'): Clarification on including location information for OSE analytics | Lenovo, Motorola Mobility | Rel-17 | Revision of S2-2200733r03. Approved | Agreed | |
| 8.1 | - | - | - | KI#16 | - | - | Docs:=3 | - | |
| 8.1 | S2-2200241 | CR | Approval | 23.288 CR0496 (Rel-17, 'F'): Correction for the figure of DN Performance Analytics | KDDI | Rel-17 | Approved | ==== 8.X, 9.X, 10.X Final Deadline ==== | Agreed |
| 8.1 | S2-2200585 | CR | Approval | 23.288 CR0506 (Rel-17, 'F'): Remove the redundant content of performance data collected from SMF | Huawei, HiSilicon | Rel-17 | r01 agreed. Revised to S2-2201537. | Yannick (Nokia): Nokia provides r01. Wang Yuan (Huawei) is fine with r01. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.1 | S2-2201537 | CR | Approval | 23.288 CR0506R1 (Rel-17, 'F'): Remove the redundant content of performance data collected from SMF | Huawei, HiSilicon | Rel-17 | Revision of S2-2200585r01. Approved | Agreed | |
| 8.2 | - | - | - | Enhanced support of Non-Public Networks (eNPN) | - | - | Docs:=71 | - | |
| 8.2 | - | - | - | LS on the scope of applying Network Slicing feature in Rel-17 and Rel-16 | - | - | Docs:=7 | - | |
| 8.2 | S2-2200007 | LS In | Action | LS from CT WG1: LS on the scope of applying Network Slicing feature in Rel-17 and Rel-16 | CT WG1 (C1-215137) | Rel-16 | Revision of Postponed S2-2108264 from S2#148E. Responses drafted in S2-2200478 and S2-2200558. Postponed | ==== 8.X, 9.X, 10.X Final Deadline ==== | Postponed |
| 8.2 | S2-2200061 | LS In | Action | LS from SA WG1: LS on the scope of applying Network Slicing feature in Rel-17 and Rel-16 | SA WG1 (S1-214234) | Rel-16 | Postponed | ==== 8.X, 9.X, 10.X Final Deadline ==== | Postponed |
| 8.2 | S2-2200478 | LS OUT | Approval | [DRAFT] Reply LS on the scope of applying Network Slicing feature in Rel-17 and Rel-16 | Ericsson | Rel-17 | Response to S2-2200007. Noted | Antoine (Orange) doesn't agree with r00 but provides r01. Jianning (Xiaomi) asks question for clarification from Antonie (Orange) Antoine (Orange) replies. Josep (DT) comments, supports Antoine (Orange). Objects to r00 Peter Hedman (Ericsson) provides comments that the proposal of no slice support deviates from basic principle of 5GS Josep (DT) clarifies. Antoine (Orange) replies to Peter. Patrice (Huawei) asks Antoine (Orange) a question for clarification. Peter Hedman (Ericsson) provides questions to Orange Peter Hedman (Ericsson) provides reply Josep (DT) comments, provides r02. Haris(Qualcomm) comments on r02 Peter Hedman (Ericsson) provides comments on r02 Josep (DT) replies. Peter Hedman (Ericsson) provides r03 Ashok (Samsung) comments Peter Hedman (Ericsson) provides r04 Ashok (Samsung) responds to Peter Hedman (Ericsson) ==== 8.X, 9.X, 10.X Revisions Deadline ==== Josep (DT) is OK with r04, objects to r00, r01. Peter Hedman (Ericsson) ok with r04, r00, r03, and objects to r01 and r02 Marco (Huawei) ok with r04 & r03, and objects r00, r01, r02 Haris(Qualcomm) objects to r04, r03 Antoine (Orange) proposes to Note this reply LS and decide at the next meeting if we remove the architecture option where CH hosts AUSF+UDM. ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 8.2 | S2-2200558 | LS OUT | Approval | [DRAFT] ] Reply LS on the scope of applying Network Slicing feature in Rel-17 and Rel-16 | MediaTek Inc. | Rel-17 | Response to S2-2200007. Noted | Peter (Ericsson) proposes to use S2-2200478 for the reply Rainer (Nokia) replies and prefers 558. Peter Hedman (Ericsson) provides reply to Rainer Josep (DT) also prefers to use 558 as basis, provides r01. Rainer (Nokia) comments. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Peter Hedman (Ericsson) propose to use 00478 as basis again as we cannot send two replies Haris(Qualcomm) objects to r01, agrees to concentrate the discussion on 0478 Josep (DT) objects to r00. ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 8.2 | S2-2200479 | DISCUSSION | Agreement | Network Slice-Specific Authentication and Authorization procedure when involving an SNPN. | Ericsson | Rel-17 | Noted | Antoine (Orange) objects. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 8.2 | S2-2200480 | CR | Approval | 23.501 CR3511 (Rel-17, 'F'): CH architecture update | Ericsson | Rel-17 | r01 agreed. Revised to S2-2201691. | Antoine (Orange) objects. Josep (DT) objects to this CR. Peter Hedman (Ericsson) provides replies and ask how the NSSAA can be applied locally as argued. Josep (DT) replies. Peter Hedman (Ericsson) provides reply to Josep. Josep (DT) comments. Peter Hedman (Ericsson) provides r01 Josep (DT) can live with r01. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.2 | S2-2201691 | CR | Approval | 23.501 CR3511R1 (Rel-17, 'F'): CH architecture update | Ericsson | Rel-17 | Revision of S2-2200480r01. Approved | Agreed | |
| 8.2 | - | - | - | LS on PCF in case of SNPN with CH using AUSF/UDM for primary auth | - | - | Docs:=5 | - | |
| 8.2 | S2-2200013 | LS In | Action | LS from CT WG1: LS on PCF in case of SNPN with CH using AUSF/UDM for primary auth | CT WG1 (C1-216294) | Rel-17 | Revision of Postponed S2-2108282 from S2#148E. Responses drafted in S2-2200402 S2-2200640 and S2-2201168. Final response in S2-2201692 | ==== 8.X, 9.X, 10.X Final Deadline ==== | Replied to |
| 8.2 | S2-2200402 | LS OUT | Approval | [DRAFT] Reply LS on PCF in case of SNPN with CH using AUSF/UDM for primary auth. | MediaTek Inc. | Rel-17 | Response to S2-2200013. r04 agreed. Revised to S2-2201692, merging S2-2200640 and S2-2201168 | Antoine (Orange) comments and proposes to use S2-2200640 as the baseline. Sebastian (Qualcomm) objects to the LS Guillaume (MediaTek Inc.) provides r02 Antoine (Orange) objects. Sebastian (Qualcomm) asks a question to Orange (Antoine) Antoine (Orange) replies. Sebastian (Qualcomm) provides r03 Guillaume (MediaTek Inc.) provides r04 (adding the next meeting's dates). ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.2 | S2-2201692 | LS OUT | Approval | Reply LS on PCF in case of SNPN with CH using AUSF/UDM for primary auth. | SA WG2 | Rel-17 | Revision of S2-2200402r04, merging S2-2200640 and S2-2201168. Approved | Approved | |
| 8.2 | S2-2200640 | LS OUT | Approval | Reply LS on PCF in case of SNPN with CH using AUSF/UDM for primary auth | Huawei, HiSilicon | Rel-17 | Response to S2-2200013. Merged into S2-2201692 | Sebastian (Qualcomm) objects to the LS Belen (Ericsson) objects to this LS. Qianghua (Huawei) agrees to mark this merged into S2-2201168 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 8.2 | S2-2201168 | LS OUT | Approval | [DRAFT] Reply LS on PCF in case of SNPN with CH using AUSF/UDM for primary auth | Qualcomm Incorporated | Rel-17 | Response to S2-2200013. Merged into S2-2201692 | Antoine (Orange) doesn't agree with the proposed answers; proposes to use S2-2200640 as the baseline. Josep (DT) sees the option with two URSPs less restrictive. Genadi (Lenovo) provides r01. Josep (DT) asks question for clarification. Qianghua (Huawei) provides comments and agrees to go with S2-2200640 Belen (Ericsson) supports this LS reply, prefers r01. Genadi (Lenovo) provides responses to Josep (DT). Josep (DT) comments, provides r03, please disregard r02. Genadi (Lenovo) provides comments to Qianghua (Huawei). Guillaume (MediaTek Inc.) objects to r03 - it cannot be left open-ended as suggested. Qianghua (Huawei) replies Antoine (Orange) objects to r00 and r01. Josep (DT) comments. Sebastian (Qualcomm) objects to r02 and r03 Sebastian (Qualcomm) replies to Josep Guillaume (MediaTek Inc.) comments. Sebastian (Qualcomm) comments that this LS can be marked as merged into S2-2200402 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 8.2 | - | - | - | LS on conclusions of authentication methods for initial access for onboarding | - | - | Docs:=2 | - | |
| 8.2 | S2-2200029 | LS In | Action | LS from SA WG3: LS on conclusions of authentication methods for initial access for onboarding. | SA WG3 (S3-214334) | Rel-17 | Revision of Postponed S2-2109020 from S2#148E. Postponed | ==== 8.X, 9.X, 10.X Final Deadline ==== | Postponed |
| 8.2 | S2-2200175 | LS OUT | Approval | Reply LS on conclusions of authentication methods for initial access for onboarding | Intel | Rel-17 | Response to S2-2200029. Noted | Rainer (Nokia) proposes to note S2-2200175. Saso (Intel) replies to Rainer (Nokia); provides r01. Qianghua (Huawei) provides comments for the NOTE Saso (Intel) replies to Qianghua. Jianning (Xiaomi) provides comment and provide r02 Saso (Intel) provides r03. Haris(Qualcomm) asks to put this LS on hold due to discussions in SA3 and until SA3 corresponding CRs are resolved objects to any revision Saso (Intel) replies to Haris. Rainer (Nokia) comments. Saso (Intel) replies to Haris and Rainer. Peter Hedman (Ericsson) provides comments Haris(Qualcomm) proposes to note Saso (Intel) is OK to note Peter Hedman (Ericsson) ok to note the LS ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 8.2 | - | - | - | LS on network slice admission control for SNPN onboarding | - | - | Docs:=1 | - | |
| 8.2 | S2-2200195 | LS In | Action | LS from CT WG1: Reply LS on network slice admission control for SNPN onboarding | CT WG1 (C1-220831) | Rel-17 | Noted | Qianghua (Huawei) considers this to be noted. Ashok (Samsung) comments Peter Hedman (Ericsson) provides comments Ashok (Samsung) responds to Peter Hedman (Ericsson) Peter Hedman (Ericsson) provides reply Ashok (Samsung) agrees with Peter Hedman (Ericsson) and thinks that CT1 is the best place to trigger this discussion ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 8.2 | - | - | - | LS on Clarification on UE Onboarding aspects for SNPN | - | - | Docs:=11 | - | |
| 8.2 | S2-2200200 | LS In | Action | LS from CT WG4: LS on Clarification on UE Onboarding aspects for SNPN | CT WG4 (C4-220313) | Rel-17 | Responses drafted in S2-2200494 and S2-2201169. Final response in S2-2201693 | ==== 8.X, 9.X, 10.X Final Deadline ==== | Replied to |
| 8.2 | S2-2200494 | LS OUT | Approval | [DRAFT] Reply LS on Clarification on UE Onboarding aspects for SNPN | Ericsson | Rel-17 | Response to S2-2200200. Noted | Rainer (Nokia) proposes to note and go with S2-2201169. Peter Hedman (Ericsson) ok to use 1169 for basis of the discussions for the reply, i.e. LS can be noted as merged. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 8.2 | S2-2201169 | LS OUT | Approval | [DRAFT] Reply LS on Clarification on UE Onboarding aspects for SNPN | Qualcomm Incorporated | Rel-17 | Response to S2-2200200. Revised to S2-2201693. | Qianghua (Huawei) provides comments Sebastian (Qualcomm) replies ==== 8.X, 9.X, 10.X Revisions Deadline ==== Qianghua (Huawei) objects r00, and suggest to modify the second answer Rainer (Nokia) replies. Sebastian (Qualcomm) replies to Qianghua Qianghua (Huawei) OK with Sebastian Proposal Sebastian (Qualcomm) proposes to approve r00 with the following change: Replace the answer to the second question by 'SA2 response: SA2's expectation is that DCS can provide multiple FQDNs or multiple IP addresses (or both FQDNs and IP addresses) for different PVS servers to the ON-SNPN's AMF, where each FQDN identifies a different PVS. How the UE uses PVS IP addresses and/or PVS FQDNs is up to UE implementation.' Qianghua (Huawei) OK with Sebastian Proposal: r00+modification of the second SA2 answer ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.2 | S2-2201693 | LS OUT | Approval | Reply LS on Clarification on UE Onboarding aspects for SNPN | SA WG2 | Rel-17 | Revision of S2-2201169. Approved | Approved | |
| 8.2 | S2-2201214 | CR | Approval | 23.501 CR3579 (Rel-17, 'F'): Clarification on the FQDN(s) and IP address(es) of PVS for remote provisionning | ZTE | Rel-17 | CC#2: This LS was noted. | Josep (DT) this this CR as making the issue even worse. Objects to this CR. Sees the approach in S2-2200477 much more feasible Zhendong (ZTE): provides response xiaowan (vivo) provides comment and changes proposal Josep (DT) replies. Peter Hedman (Ericsson) provides comments Zhendong (ZTE): provides the response Sebastian (Qualcomm) comments Rainer (Nokia) is ok with 1214. Josep (DT) retracts his objection. Provides r01 Jihoon (ETRI) provides r02. Qianghua (Huawei) provides comments Josep (DT) replies to Zhendont (ZTE) that he still does not like the approach. Sebastian (Qualcomm) provides r03 Qianghua (Huawei) provides r04 Zhendong (ZTE): provides comments Rainer (Nokia) objects to r04, prefers r03. Sebastian (Qualcomm) objects to r04 in line with comments provided for S2-2201169 Peter Hedman (Ericsson) ok with r03, but provides a question Qianghua (Huawei) objects r00-r03. Can only accept r04. Rainer (Nokia) asks for clarification. Qianghua (Huawei) replies to Rainer Zhendong (ZTE): provides comments. Peter Hedman (Ericsson) provides reply Zhendong (ZTE): confirm peter clarification, DCS know SO-SNPN of UE. | Noted |
| 8.2 | S2-2201215 | CR | Approval | 23.502 CR3418 (Rel-17, 'F'): Clarification on the FQDN(s) and IP address(es) of PVS for remote provisionning | ZTE | Rel-17 | Noted | Josep (DT) objects to this CR. Same reasons as in S2-2201214. Sebastian (Qualcomm) asks a question Josep (DT) retracs his objection if a revision mirroring the changes in S2-2201214 is provided. Qianghua (Huawei) provides r01 Rainer (Nokia) objects to r01. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Qianghua (Huawei) can only accept r01 Josep (DT) retracts his objection. Peter Hedman (Ericsson) any rev needs to be aligned with what is agreed for 01214, if approved Sebastian (Qualcomm) objects to r01 ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 8.2 | S2-2200432 | CR | Approval | 23.503 CR0694 (Rel-17, 'F'): Correction for remote provisioning | Ericsson | Rel-17 | CC#4: r05 agreed. Revised, merging S2-2200644, to S2-2201839. | Antoine (Orange) asks justification for removals of 'SNPN'. Zhendong (ZTE): similar comments with orange Huan (vivo): ask for clarification Xiaowan (vivo) provides comments and term suggestions Qianghua (Huawei) provides comments Peter Hedman (Ericsson) provides replies to the questions Josep (DT) comments on the removal of 'SNPN'. Provides r02, please disregard r01 Peter Hedman (Ericsson) provides reply and asks how to handel the CR overlap Belen (Ericsson) provides r03 Rainer (Nokia) prefers r02. Peter Hedman (Ericsson) provides reply and also prefer r02, but then 0644 need to be changed Qianghua (Huawei) provides r04 Rainer (Nokia) is ok with r04. Peter Hedman (Ericsson) provides r05 Qianghua (Huawei) provides r06 fixing one overlook ==== 8.X, 9.X, 10.X Revisions Deadline ==== Rainer (Nokia) comments. Peter Hedman (Ericsson) provides reply to Rainer Josep (DT) is OK with r02, r03, objects to other revisions includign original. Peter Hedman (Ericsson) propose to agree r05, and if there are objections ok to agree r03 Qianghua (Huawei) OK with r05/r06, object r03, prefer postpone if r05/r06 is not acceptable Rainer (Nokia) is ok to go with r05. ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.2 | S2-2201839 | CR | Approval | 23.503 CR0694R1 (Rel-17, 'F'): Correction for remote provisioning | Ericsson, Huawei | Rel-17 | Revision of S2-2200432r05, merging S2-2200644. Approved | Agreed | |
| 8.2 | S2-2200476 | CR | Approval | 23.501 CR3510 (Rel-17, 'F'): Correction for remote provisioning | Ericsson | Rel-17 | r08 agreed. Revised to S2-2201694. | Antoine (Orange) provides r01 removing change 4. Zhendong (ZTE): provides the comments Xiaowan (vivo) provides comments and r02 Qianghua (Huawei) provides r04, please ignore r03 Peter Hedman (Ericsson) provides r05 and comments Antoine (Orange) provides r06, re-instating change 4. Qianghua (Huawei) provides r07 Peter Hedman (Ericsson) provides comments Qianghua (Huawei) replies Peter Hedman (Ericsson) provides r08 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.2 | S2-2201694 | CR | Approval | 23.501 CR3510R1 (Rel-17, 'F'): Correction for remote provisioning | Ericsson | Rel-17 | Revision of S2-2200476r08. Approved | Agreed | |
| 8.2 | S2-2200477 | CR | Approval | 23.502 CR3356 (Rel-17, 'F'): Correction for remote provisioning | Ericsson | Rel-17 | Noted | Qianghua (Huawei) comments Peter Hedman (Ericsson) ok to note the CR and take the discussion in 01215 covering same subject ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 8.2 | - | - | - | Other LSs | - | - | Docs:=3 | - | |
| 8.2 | S2-2200040 | LS In | Information | LS from GSMA: Reply LS on IMEI for Non-Public Networks/Private Networks without using USIM | GSMA (TSG46_028) | Postponed | ==== 8.X, 9.X, 10.X Final Deadline ==== | Postponed | |
| 8.2 | S2-2200060 | LS In | Information | LS from SA WG1: Reply to LS on support of PWS over SNPN | SA WG1 (S1-214049) | Rel-17 | Noted | Qianghua (Huawei) proposes to note this LS, which is for information ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 8.2 | S2-2200068 | LS In | Action | Reply LS on UE capabilities indication in UPU | SA WG3 (S3-214447) | Rel-17 | Noted | Qianghua (Huawei) proposes to note this LS, no need for SA2 reply LS and the all CRs seem aligned ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 8.2 | - | - | - | Maintenance CRs – CP based remote provisioning | - | - | Docs:=8 | - | |
| 8.2 | S2-2200141 | CR | Approval | 23.501 CR3466 (Rel-17, 'F'): Remove the CP based remote provisioning | vivo | Rel-17 | r02 agreed. Revised to S2-2201695, merging S2-2200406 and S2-2200483 | Xiaowan (vivo) provides r01 to merge 0406 and 0408 Haris(Qualcomm) ok with the suggestion to merge and r01 Peter Hedman (Ericsson) provides comments Xiaowan (vivo) provides r02 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.2 | S2-2201695 | CR | Approval | 23.501 CR3466R1 (Rel-17, 'F'): Remove the CP based remote provisioning | Vivo, Ericsson, Qualcomm | Rel-17 | Revision of S2-2200141r02, merging S2-2200406 and S2-2200483. Approved | Agreed | |
| 8.2 | S2-2200142 | CR | Approval | 23.502 CR3321 (Rel-17, 'F'): Remove the CP based remote provisioning | vivo | Rel-17 | Confirm Specification Number - CR states 23.501! Confirmed should be 23.502. r02 agreed. Revised to S2-2201696, merging S2-2200484 and S2-2200407 | Xiaowan (vivo) provides r01 Peter Hedman (Ericsson) provides r02 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.2 | S2-2201696 | CR | Approval | 23.502 CR3321R1 (Rel-17, 'F'): Remove the CP based remote provisioning | Vivo, Ericsson, Qualcomm | Rel-17 | Revision of S2-2200142r02, merging S2-2200484 and S2-2200407. Approved | Agreed | |
| 8.2 | S2-2200406 | CR | Approval | 23.501 CR3500 (Rel-17, 'F'): Removal of CP provisioning | Qualcomm Incorporated | Rel-17 | Merged into S2-2201695 | Xiaowan (vivo) proposes to merge the CR into S2-2200141 and use 0141 as the baseline for further discussion. Haris(Qualcomm) is ok to merge in S2-2200141 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 8.2 | S2-2200407 | CR | Approval | 23.502 CR3350 (Rel-17, 'F'): Removal of CP provisioning | Qualcomm Incorporated | Rel-17 | Merged into S2-2201696 | Xiaowan (vivo) proposes to merge the CR into S2-2200142 and use 0142 as the baseline for further discussion. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 8.2 | S2-2200483 | CR | Approval | 23.501 CR3513 (Rel-17, 'F'): CP Remote Provision of credentials for NSSAA or secondary authentication/authorization | Ericsson | Rel-17 | Merged into S2-2201695 | Xiaowan (vivo) proposes to merge the CR into S2-2200141 and use 0141 as the baseline for further discussion. Peter Hedman (Ericsson) ok to note as merged into 0141 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 8.2 | S2-2200484 | CR | Approval | 23.502 CR3357 (Rel-17, 'F'): CP Remote Provision of credentials for NSSAA or secondary authentication/authorization | Ericsson | Rel-17 | Merged into S2-2201696 | Xiaowan (vivo) proposes to merge the CR into S2-2200142 and use 0142 as the baseline for further discussion. Peter Hedman (Ericsson) ok to note as merged into 0142 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 8.2 | - | - | - | Maintenance CRs – Onboarding | - | - | Docs:=13 | - | |
| 8.2 | S2-2200176 | CR | Approval | 23.501 CR3470 (Rel-17, 'F'): DN-AAA server selection when the DCS is not involved during primary authentication | Intel, Ericsson | Rel-17 | r06 agreed. Revised to S2-2201697. | Peter (Ericsson) provides comments and r01 Rainer (Nokia) cannot accept r01 and r00. Huan (vivo) asks for clarification Saso (Intel) replies to Rainer (Nokia). Saso (Intel) replies to Huan (vivo). Rainer (Nokia) replies to Saso (Intel). Yishan (Huawei) asks for clarification Saso (Intel) replies to Yishan (Huawei) Yishan (Huawei) replies to Saso (Intel) Ashok (Samsung) need clarification from Saso (Intel) Peter Hedman (Ericsson) provides comments Rainer (Nokia) replies. Haris(Qualcomm) comments Ashok (Samsung) comments Saso (Intel) comments Josep (DT) comments on NOTE X. Saso (Intel) provides r02 Haris(Qualcomm) provides r03 Rainer (Nokia) is ok with r03. Saso (Intel) provides r04. Antoine (Orange) withdraws r05. Antoine (Orange) provides r05 (removing 'v' from 'vPCF' also in the first 2 figures). Peter Hedman (Ericsson) provides r06 Saso (intel) is OK with r06 and replies to Peter Hedman (Ericsson). Peter Hedman (Ericsson) provides r07 Saso (Intel) prefers r07 over r06. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Haris(Qualcomm) comments on r07 Yishan (Huawei) prefers r07 and objects any versions from r00 to r04. Haris(Qualcomm) r07 not acceptable as is, r06 is ok ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.2 | S2-2201697 | CR | Approval | 23.501 CR3470R1 (Rel-17, 'F'): DN-AAA server selection when the DCS is not involved during primary authentication | Intel, Ericsson | Rel-17 | Revision of S2-2200176r06. Approved | Agreed | |
| 8.2 | S2-2200177 | CR | Approval | 23.502 CR3323 (Rel-17, 'F'): DN-AAA server selection when the DCS is not involved during primary authentication | Intel | Rel-17 | CC#4: r01 + changes agreed. Revised to S2-2201835. | Rainer (Nokia) comments. Peter Hedman (Ericsson) provides comments and proposes to note the CR as 23.501 CR is enough. Qianghua (Huawei) provides comments Rainer (Nokia) is ok to note the CR. Saso (Intel) replies to Qianghua Haris(Qualcomm) comments and proposes to NOTE Saso (Intel) replies to Haris Myungjune (LGE) comments Saso (Intel) replies to Myungjune (LGE) Myungjune (LGE) replies to Saso (Intel) Peter Hedman (Ericsson) provides comments and suggest enough with same change done in 23.501 CR Saso (Intel) replies to Peter Hedman (Ericsson). Provides r01 Saso (Intel) follows up on Peter's question. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Haris(Qualcomm) does not see the need for the CR Yishan (Huawei) proposes to object this CR. Saso (Intel) seeks clarification from Haris and Yishan. Haris(Qualcomm) comments that Saso's suggested text modification is acceptable Saso (Intel) proposes to handle 0505 in CC#4 or CC#5; the proposed change is addition of 'can be' and 'only' in r01. ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.2 | S2-2201835 | CR | Approval | 23.502 CR3323R1 (Rel-17, 'F'): DN-AAA server selection when the DCS is not involved during primary authentication | Intel | Rel-17 | Revision of S2-2200177r01 + changes. Approved | Agreed | |
| 8.2 | S2-2200481 | CR | Approval | 23.501 CR3512 (Rel-17, 'F'): Correction for UE onboarding | Ericsson | Rel-17 | r03 agreed. Revised to S2-2201698. | Xiaowan (vivo) question for clarification how a UE provide IMSI when onboarding registration Haris(Qualcomm) provides comments Saso (Intel) comments Yishan (Huawei) comments Peter Hedman (Ericsson) provides r02 Yishan (Huawei) answers to Peter (Ericsson) and provide r03. Rainer (Nokia) asks for clarification. Peter Hedman (Ericsson) provides reply ==== 8.X, 9.X, 10.X Revisions Deadline ==== Peter Hedman (Ericsson) ok with r03 (and previous revisions) Yishan (Huawei) prefers r03, can live with r02 and r01, object to r00. ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.2 | S2-2201698 | CR | Approval | 23.501 CR3512R1 (Rel-17, 'F'): Correction for UE onboarding | Ericsson | Rel-17 | Revision of S2-2200481r03. Approved | Agreed | |
| 8.2 | S2-2200551 | CR | Approval | 23.501 CR3519 (Rel-17, 'F'): SNPN Onboarding resource unavailability | Samsung | Rel-17 | Merged into S2-2201556 | Antoine (Orange) requests to align the change in the CR with the summary of change. Huan (vivo) comments and think the current proposal does not align with CT1's suggestion Ashok (Samsung) replies to Antoine (Orange) and Huan (vivo) Fei (OPPO) comments Haris(Qualcomm) comments Ashok (Samsung) provides r01 Rainer (Nokia) comments. Josep (DT) comments, provides r02. Qianghua (Huawei) provides comments and proposes to merge this into S2-2200639 Ashok (Samsung) replies to Qianghua (Huawei) Qianghua (Huawei) replies Ashok (Samsung) responds to Qianghua (Huawei) Peter Hedman (Ericsson) provides comments and r03 Ashok (Samsung) agrees to merge with 0639 and responds to Peter Qianghua (Huawei) proposes to merge this into 0639 Ashok (Samsung) comments that this paper can be marked as merged to S2-2200639 CR ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 8.2 | S2-2200639 | CR | Approval | 23.501 CR3525 (Rel-17, 'F'): Clarifications for SNPN onboarding service | Huawei, HiSilicon | Rel-17 | r10 agreed. Revised to S2-2201699, merging S2-2201130 | Antoine (Orange) asks questions. Xiaowan (vivo) provides comments and r01 Qianghua (Huawei) provides r02 Rainer (Nokia) asks for clarification. Qianghua (Huawei) replies Qianghua (Huawei) provides r03, merging S2-2200551 Antoine (Orange) provides r04. Qianghua (Huawei) provides r05 Josep (DT) questions the change in r05. Ashok (Samsung) responds to Josep (DT) Josep (DT) objects to r05 Peter Hedman (Ericsson) provides r06 Ashok (Samsung) responds to Peter Hedman (Ericsson) and provides r07 adding the NOTE again Rainer (Nokia) comments. Ashok (Samsung ) agrees with Rainer (Nokia) Ashok (Samsung ) provides r08 Rainer (Nokia) provides r09. Peter Hedman (Ericsson) provides r10 Rainer (Nokia) replies. Ashok (Samsung) fine with r10 and replies to Peter (Ericsson) and Rainer (Nokia) ==== 8.X, 9.X, 10.X Revisions Deadline ==== Josep (DT) additionally objects to r07, r08, r09, r10. Proposes to just remove 'or SNPN' from NOTE 2. Ashok (Samsung) agrees with Josep (DT) to remove 'or the SNPN' from NOTE 2 on top of the r10 and mark for CC#4 Qianghua (Huawei) OK with Proposal from Ashok and Josep: namely, on top of r10, remove 'or the SNPN' from NOTE 2 in the 3rd change Peter Hedman (Ericsson) ok with r10 + remove 'or the SNPN' from NOTE 2 in the 3rd change ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.2 | S2-2201699 | CR | Approval | 23.501 CR3525R1 (Rel-17, 'F'): Clarifications for SNPN onboarding service | Huawei, HiSilicon, Ericsson, Samsung, Nokia, Nokia Shanghai Bell | Rel-17 | Revision of S2-2200639r10, merging S2-2201130. Approved | Agreed | |
| 8.2 | S2-2200745 | CR | Approval | 23.501 CR3533 (Rel-17, 'F'): Clarification on Onboarding PLMN selection | Huawei, HiSilicon | Rel-17 | Noted | Rainer (Nokia) proposes to note as this is not FASMO and not needed. Yishan (Huawei) replies to the comments from Rainer (Nokia) Rainer (Nokia) replies, believes the CR is not needed. Genadi (Lenovo) has concerns with this proposal. Josep (DT) has also concerns. Does not agree that this is FASMO. Yishan (Huawei) replies to Lenovo and DT. Josep (DT) replies. Haris(Qualcomm) objects to the CR Yishan (Huawei) answers to DT and Qualcomm Peter Hedman (Ericsson) provides comments Yishan (Huawei) replies to Peter (Ericsson) Peter Hedman (Ericsson) provides reply ==== 8.X, 9.X, 10.X Revisions Deadline ==== Josep (DT) objects to this CR. Rainer (Nokia) repeats to note the CR. ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 8.2 | S2-2200746 | DISCUSSION | Discussion | Discussion on Onboarding PLMN Selection. | Huawei, HiSilicon | Rel-17 | Noted | ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 8.2 | S2-2201156 | CR | Approval | 23.501 CR3567 (Rel-17, 'F'): Clean-up the clause on UP onboarding via ON-SNPN | Lenovo, Motorola Mobility | Rel-17 | r01 agreed. Revised to S2-2201700. | Qianghua (Huawei) provides comments and asks whether can merge with S2-2200642 Peter (Ericsson) provides comments and r01 Genadi (Lenovo) provides r02. Rainer (Nokia) provides r03. Genadi (Lenovo) is fine with r03. Peter Hedman (Ericsson) provides support of the CR but comments about a clash with 00642 ==== 8.X, 9.X, 10.X Revisions Deadline ==== Qianghua (Huawei) proposes to go r01, object r02/r03 that introduces clashes with 00642 Rainer (Nokia) replies. Qianghua (Huawei) FASMO criterion is not applicable for AI#8.x. Please check S2-2200001 if you need Genadi (Lenovo) proposes a way forward on the overlap with S2-2200642. Qianghua (Huawei) comments that S2-2200642r01/r02 has no conflicts with 2201156r01 Peter Hedman (Ericsson) provides comments Genadi (Lenovo) is OK with r01. ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.2 | S2-2201700 | CR | Approval | 23.501 CR3567R1 (Rel-17, 'F'): Clean-up the clause on UP onboarding via ON-SNPN | Lenovo, Motorola Mobility | Rel-17 | Revision of S2-2201156r01. Approved | Agreed | |
| 8.2 | - | - | - | Other Maintenance CRs | - | - | Docs:=21 | - | |
| 8.2 | S2-2200400 | DISCUSSION | Agreement | URSP provisioning when UE accesses an SNPN using CH credentials. | MediaTek Inc. | Rel-17 | Noted | Guillaume (MediaTek Inc.) proposes to note this discussion paper. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 8.2 | S2-2200401 | CR | Approval | 23.501 CR3499 (Rel-17, 'F'): ENPN: URSP provisioning when UE accesses an SNPN using CH credentials | MediaTek Inc. | Rel-17 | Confirm Specification Number - CR states 23.503! Confirmed should be 23.503. To be revised as 23.503 CR0707. r28 agreed. Revised to S2-2201701. | Antoine (Orange) proposes to note this CR and use S2-2200641 as the way forward. Josep (DT) wonders if such a complex (and also incomplete) solution is really needed. Guillaume (MediaTek Inc.) provides r01 Guillaume (MediaTek Inc.) responds. Guillaume (MediaTek Inc.) responds to Antoine Josep (DT) comments, also supports S2-2200641 as way forward. Antoine (Orange) replies to Guillaume. Sebastian (Qualcomm) comments and objects to the CR Guillaume (MediaTek Inc.) responds to Josep (DTAG) Guillaume (MediaTek Inc.) replies to Antoine (Orange). Sebastian (Qualcomm) replies to Josep Josep (DT) replies to Sebastian. Antoine (Orange) replies to Guillaume (MediaTek Inc.). Genadi (Lenovo) looks for clarifications how the URSP rules from the SNPN are used in the UE. Josep (DT) replies to Sebastian (Qualcomm). Devaki (Nokia) proposes to consider this paper merged with 641. Guillaume (MediaTek Inc.) responds to Devaki (Nokia) Guillaume (MediaTek Inc.) responds to Genadi Guillaume (MediaTek Inc.) provides r02 Guillaume (MediaTek Inc.) provides r03 Antoine (Orange) objects to r03 and previous versions. Guillaume (MediaTek): responds to Antoine (Orange): then CH credentials scenario must be removed from Rel-17 Antoine (Orange) responds. Qianghua (Huawei) provides comments Guillaume (MediaTek Inc.) responds to Antoine (Orange) Antoine (Orange) is OK to remove CH from R17. Guillaume (MediaTek Inc.) responds to Qianghua (Huawei) Sebastian (Qualcomm) provides r04 Guillaume (MediaTek Inc.) thanks Sebastian (Qualcomm) for r04. Ok with r04. Josep (DT) asks a question for clarification, comments. Antoine (Orange) provides r05. Apostolis (Lenovo) asks question on r05. Qianghua (Huawei) comments Antoine (Orange) withdraws r05 and provides r06. Guillaume (MediaTek Inc.) comments on r05 (not ok) Antoine (Orange) provides r07 (the only difference from r06 is the removal of 'Orange restricted' footer). Guillaume (MediaTek Inc.) asks clarification on r07 Josep (DT) comments, provides r08, r10, please disregard r09. Antoine (Orange) provides clarification. Antoine (Orange) comments on r08 and r10. Josep (DT) agrees with Antoine (Orange), retracts r08, r10, provides replacement r12, r13. Qianghua (Huawei) provides r14 (on top of r13) Josep (DT) comments, provides r15. Guillaume (MediaTek Inc.) provides r16. Josep (DT) comments. Sebastian (Qualcomm) provides r17 Josep (DT) provides r18 correcting 'CH network'. Antoine (Orange) provides r19. Devaki (Nokia) provides r11. Belen (Ericsson) provides comments, ask a question for clarification. Sebastian (Qualcomm) replies to Belen Josep (DT) is fine with the clarification in r19. Belen (Ericsson) provides r20. Guillaume (MediaTek Inc.) provides r21. Sebastian (Qualcomm) asks a question to Belen Belen (Ericsson) replies to QC Antoine (Orange) comments on r20/r21. Josep (DT) has the same view as Antoine (Orange) and Sebastian (Qualcomm). Belen (Ericsson) replies to QC, Orange and DT. Guillaume (MediaTek Inc.) recommends to move forward with r19 approach Antoine (Orange) replies to Belen that there is no HPLMN and no HR. Belen (Ericsson) asks Orange for clarification Josep (DT) tries to clarify. Belen (Ericsson) asks Josep Josep (DT) replies to Belén (Ericsson). Belen (Ericsson) replies to Josep Josep (DT) is also fine with r22. Antoine (Orange): r22 is fine. Sebastian (Qualcomm) replies to Belen and provides r22 Belen (Ericsson) provides r23, states that furhter updates are needed. Provides comments to r22/r23 Josep (DT) comments on r23, does not understand the addition. Sebastian (Qualcomm) replies and provides r24 Belen (Ericsson) replies to Josep. Belen (Ericsson) asks QC Belen (Ericsson) replies to QC, and ask for clarifications- marco (Huawei) comments r23 & r24 Marco (Huawei): for all versions- the text for SNPN should be moved at the end of clause for better readability & consistency of the whole clause. Guillaume (MediaTek Inc.) provides r25 Sebastian (Qualcomm) is ok with r25 Antoine (Orange) provides r26. Josep (DT) provides r27. Guillaume (MediaTek Inc.) objects to r26 and r27. marco (Huawei) comments to Guillaume. Antoine (Orange) provides r28. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Josep (DT) is OK with revisions r24 to r28. Objects to r20, r23 Belen (Ericsson) is okay with r27, r28. Ask to remove 'TS 23.503 [45]' before uploading Devaki (Nokia) asks question for clarification regarding r28. Guillaume (MediaTek Inc.) replies to Devaki (Nokia) Guillaume (MediaTek Inc.) ok with r28 and agrees with Belen (Ericsson) on the removal of 'TS 23.503 [45]'. Sebastian (Qualcomm) is ok with r28 and removal of the TS reference in the text ('TS 23.503 [45]') Peter Hedman (Ericsson) provides comments Marco (Huawei) is okay with r25, r26 , r27, r28 and objects to all from r00 to r21 Antoine (Orange) replies to Devaki. ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.2 | S2-2201701 | CR | Approval | 23.503 CR0707 (Rel-17, 'F'): ENPN: URSP provisioning when UE accesses an SNPN using CH credentials | MediaTek Inc. | Rel-17 | Revision of S2-2200401r28. Approved | Agreed | |
| 8.2 | S2-2200482 | DISCUSSION | Agreement | CP remote provisioning of credentials for NSSAA or secondary authentication/authorization. | Ericsson | Noted | ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted | |
| 8.2 | S2-2200497 | CR | Approval | 23.501 CR3514 (Rel-17, 'F'): Correction in AAA selection procedure | Qualcomm Incorporated | Rel-17 | r02 agreed. Revised to S2-2201702. | Peter (Ericsson) provides comments and question the assumptions made and the CR as such Qianghua (Huawei) provides comments Haris(Qualcomm) provides r01 Saso (Intel) comments Peter Hedman (Ericsson) provides r02 ==== 8.X, 9.X, 10.X Revisions Deadline ==== Haris(Qualcomm) indicates that is fine with r02 and responds Qianghua (Huawei) prefers r02+removal of the new EN, but can live with r02 Saso (Intel) prefers to keep the new EN; OK with r02 Peter Hedman (Ericsson) ok with r02 Rainer (Nokia) comments. ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.2 | S2-2201702 | CR | Approval | 23.501 CR3514R1 (Rel-17, 'F'): Correction in AAA selection procedure | Qualcomm Incorporated | Rel-17 | Revision of S2-2200497r02. Approved | Agreed | |
| 8.2 | S2-2200498 | CR | Approval | 23.501 CR3515 (Rel-17, 'F'): Support for emergency calls when no PLMN acceptable cell is available | Qualcomm Incorporated, Deutsche Telekom, Ericsson, Nokia, Nokia Shanghai Bell, Xiaomi | Rel-17 | Approved | ==== 8.X, 9.X, 10.X Final Deadline ==== | Agreed |
| 8.2 | S2-2200535 | CR | Approval | 23.502 CR3359 (Rel-17, 'F'): UE SM context fetch in registration procedure during inter-network mobility | Samsung, Ericsson, LGE | Rel-17 | r01 agreed. Revised to S2-2201703. | Antoine (Orange) comments. Youngkyo(Samsung) replies to Antoine (Orange). Antoine (Orange) has concerns. Youngkyo(Samsung) replies. Josep (DT) comments, provides r01. Youngkyo(Samsung) is okay with the revision r01. Peter Hedman (Ericsson) ok with r01 Antoine (Orange): r01 solves my concerns . ==== 8.X, 9.X, 10.X Revisions Deadline ==== Devaki (Nokia) is ok with r01, indeed it is an improvement overall to differentiate the scenarios clearly. Minor improvement request would be to add 'session' in front of 'continuity' to avoid ambiguity. Youngkyo(Samsung) replies to Devaki . ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.2 | S2-2201703 | CR | Approval | 23.502 CR3359R1 (Rel-17, 'F'): UE SM context fetch in registration procedure during inter-network mobility | Samsung, Ericsson, LGE | Rel-17 | Revision of S2-2200535r01. Approved | Agreed | |
| 8.2 | S2-2200641 | CR | Approval | 23.501 CR3526 (Rel-17, 'F'): Corrections for UE access with CH credentials | Huawei, HiSilicon | Rel-17 | CC#4: r12 + changes agreed. Revised to S2-2201836. | Antoine (Orange) supports and provide r01. Josep (DT) supports this approach, provides r02. Youngkyo(Samsung) provides a comment. Josep (DT) agrees with Youngkyo (Samsung), provides r03. Huan (vivo) asks for clarifications and provides comments. Qianghua (Huawei) replies Sebastian (Qualcomm) provides r04, objects to all other versions Antoine (Orange) previously provided r01; comments on ProSe+PNI-NPN. Devaki (Nokia) provides r05 to remove the change related to ProSe that overlaps with 1052 and its revisions. Qianghua (Huawei) asks clarification from Sebastian Guillaume (MediaTek inc.) comments Belen (Ericsson) supports r04, and r05, objects to previous revisions Saso (Intel) provides r06 Qianghua (Huawei) replies to Saso and provides r07 Saso (Intel) provides r08 Haris(Qualcomm) comments on r08 Saso (Intel) provides r09 Qianghua (Huawei) provides r10 Peter Hedman (Ericsson) provides r11 Qianghua (Huawei) replies to Peter Saso (Intel) replies to Peter Peter Hedman (Ericsson) provides replies Qianghua (Huawei) provides r12 ==== 8.X, 9.X, 10.X Revisions Deadline ==== Devaki (Nokia) comments that the added text '(e.g. MCC reserved for use by private networks) is wrong. OK with r12 only without ''(e.g. MCC reserved for use by private networks)' Qianghua (Huawei) suggests to go with r12 Saso (Intel) is OK with both r11 and r12 Peter Hedman (Ericsson) is OK with both r11 and r12 Devaki (Nokia) objects to r12 as-is. Can accept r12 minus (e.g. MCC reserved for use by private networks) as when an MCC is reserved for private network, it could be unique thus it is a wrong example to illustrate 'when MCC+MNC is not unique'. Haris(Qualcomm) comments that GIN definition in r012 and other revisions in incorrect Devaki (Nokia) is fine with r11 (r12 minus the text) or ok with r12 if we replace (e.g. MCC reserved for use by private networks) with (e.g. MCC =999 is used and MNC is not coordinated amongst the SNPNs). Qianghua (Huawei) suggests to go with r12 for CC#4, with the following updates: 1. change definition of GIN to: Group ID for Network Selection (GIN): An identifier used during SNPN selection to enhance the likelihood of selecting a preferred SNPN that supports a Default Credentials Server or a Credentials Holder. 2. replace (e.g. MCC reserved for use by private networks) with (e.g. MCC =999 is used and MNC is not coordinated amongst the SNPNs) Antoine (Orange) doesn't understand Devaki's concerns because 'MCC reserved for use by private networks' means the same as MCC=999. Devaki (Nokia) replies to Antoine. How about MCC + MNC reserved for an SNPN? How about enterprises obtaining their own MCC+MNC values? Devaki (Nokia) comments. Antoine (Orange) replies to Devaki. Devaki (Nokia) replies. ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.2 | S2-2201836 | CR | Approval | 23.501 CR3526R1 (Rel-17, 'F'): Corrections for UE access with CH credentials | Huawei, HiSilicon, Deutsche Telekom, Ericsson | Rel-17 | Revision of S2-2200641r12 + changes. Approved | Agreed | |
| 8.2 | S2-2200642 | CR | Approval | 23.501 CR3527 (Rel-17, 'D'): Terms alignments and clean-ups for eNPN | Huawei, HiSilicon | Rel-17 | r02 agreed. Revised to S2-2201704. | Rainer (Nokia) questions the need of this CR. Qianghua (Huawei) replies to Rainer Peter Hedman (Ericsson) provides comments and question whether we should move forward with the CR as then CR needs a cleanup for consistency. Qianghua (Huawei) provides r01 Peter Hedman (Ericsson) provides r02 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.2 | S2-2201704 | CR | Approval | 23.501 CR3527R1 (Rel-17, 'D'): Terms alignments and clean-ups for eNPN | Huawei, HiSilicon | Rel-17 | Revision of S2-2200642r02. Approved | Agreed | |
| 8.2 | S2-2200643 | CR | Approval | 23.502 CR3371 (Rel-17, 'F'): Terms alignments and clean-ups for eNPN | Huawei, HiSilicon | Rel-17 | r04 agreed. Revised to S2-2201705. | Rainer (Nokia) provides r01. Qianghua (Huawei) OK with r01 and asks further Rainer (Nokia) replies to Qianghua (Huawei). Qianghua (Huawei) provides r02 Saso (Intel) comments on r02 Rainer (Nokia) is ok with r02. Qianghua (Huawei) provides r03 Peter Hedman (Ericsson) provides r04 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.2 | S2-2201705 | CR | Approval | 23.502 CR3371R1 (Rel-17, 'F'): Terms alignments and clean-ups for eNPN | Huawei, HiSilicon | Rel-17 | Revision of S2-2200643r04. Approved | Agreed | |
| 8.2 | S2-2200644 | CR | Approval | 23.503 CR0696 (Rel-17, 'D'): Terms alignments and clean-ups for eNPN | Huawei, HiSilicon | Rel-17 | Merged into S2-2201839 | Josep (DT) aks questions for clarification, does not agree that addign a definition is editorial. Qianghua (Huawei) provides r01 Josep (DT) comments. Is OK with r01 Rainer (Nokia) questions the need of this CR. Haris(Qualcomm) proposes r02 Qianghua (Huawei) provides r03 Peter Hedman (Ericsson) provides comments Peter Hedman (Ericsson) provides r04 Qianghua (Huawei) this CR can be marked merged if S2-2200432r04 is agreeable. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Qianghua (Huawei) if S2-2200432r04~r06 is not agreed, then I suggest to go with r03 for this CR ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 8.2 | S2-2201052 | CR | Approval | 23.501 CR3559 (Rel-17, 'F'): Clarification of ProSe support in SNPN | Nokia, Nokia Shanghai Bell | Rel-17 | r05 agreed. Revised to S2-2201706. | Peter (Ericsson) provides comments and r01 Qianghua (Huawei) provides comments and proposes to merge into S2-2200641 Fei (OPPO) comments. Josep (DT) co-signs, provides r02, r03. Haris(Qualcomm) provides r04 Qianghua (Huawei) provides r05 Steve (Huawei) comments on ProSe, CAGs the ability to bypass the CAGs by a Remote UE Josep (DT) comments. Proposes to leaved the issue raised by Steve (Huawei) for another CR. Haris(Qualcomm) comments Steve (Huawei) comments on the tools Devaki (Nokia) comments and is fine with r05. Fei (OPPO) comments and is fine with r05. Steve (Huawei) provides r06 Fei (OPPO) comments on r06 Antoine (Orange) comments on r06. Josep (DT) . Devaki (Nokia) provides r07, prefers r05 however. Josep (DT) comments, provides r08. Devaki (Nokia) comments. Josep (DT) comments. Would very much prefer r05. Steve (Huawei) is ok with r07 Josep (DT) retracts r08, provides r09. Walter Dees (Philips) prefers r05 or r08 Peter Hedman (Ericsson) provides preference for r05 Steve (Huawei) is ok with r09 Devaki (Nokia) proposes to go with r05 (from Huawei) for this meeting and reconsider the note for a future meeting. Devaki (Nokia) replies to Steven. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Steve (Huawei) replies Josep (DT) can live with r09, much prefers r05. Peter Hedman (Ericsson) prefers r05 Steve (Huawei) prefers r09, can live with r05 Fei (OPPO) prefers r05. ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.2 | S2-2201706 | CR | Approval | 23.501 CR3559R1 (Rel-17, 'F'): Clarification of ProSe support in SNPN | Nokia, Nokia Shanghai Bell, Ericsson, Deutsche Telekom, Huawei, HiSilicon | Rel-17 | Revision of S2-2201052r05. Approved | Agreed | |
| 8.2 | S2-2201053 | CR | Approval | 23.501 CR3560 (Rel-17, 'F'): SNPN with CH Subscription profile prohibits HR | Nokia, Nokia Shanghai Bell | Rel-17 | Noted | Antoine (Orange) questions/comments. Huan (vivo) questions/comments. Peter Hedman (Ericsson) provides comments and suggest that the CR is not needed Qianghua (Huawei) comments. Antoine (Orange) replies to Qianghua. Sebastian (Qualcomm) objects to the CR Devaki (Nokia) replies and provides r02 (please ignore r01). Qianghua (Huawei) replies Antoine (Orange) provides r03; objects to r00, r01 and r02. Devaki (Nokia) is ok with r03 although it is not explicit. Antoine (Orange) replies. Peter Hedman (Ericsson) proposes to note the CR Devaki (Nokia) replies to Peter and provides r04. Peter Hedman (Ericsson) proposes to go with the 23.502 CR only and note this CR ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 8.2 | S2-2201054 | CR | Approval | 23.502 CR3408 (Rel-17, 'F'): SNPN with CH Subscription profile prohibits HR | Nokia, Nokia Shanghai Bell | Rel-17 | r03 agreed. Revised to S2-2201707. | Antoine (Orange) questions/comments. Josep (DT) objects to r00. Peter Hedman (Ericsson) provides comments and suggest that the CR is not needed Qianghua (Huawei) same comments with S2-2201053 Sebastian (Qualcomm) objects to the CR Devaki (Nokia) provides r01. Antoine (Orange) questions. Devaki (Nokia) provides r02. Antoine (Orange) provides r03. Devaki (Nokia) is happy with r03. Peter Hedman (Ericsson) provides reply and ok with r03 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.2 | S2-2201707 | CR | Approval | 23.502 CR3408R1 (Rel-17, 'F'): SNPN with CH Subscription profile prohibits HR | Nokia, Nokia Shanghai Bell | Rel-17 | Revision of S2-2201054r03. Approved | Agreed | |
| 8.3 | - | - | - | Enhancement of support for Edge Computing in 5GC (eEDGE_5GC) | - | - | Docs:=40 | - | |
| 8.3 | S2-2200038 | LS In | Action | LS from GSMA OPAG: Reply LS from GSMA Operator Platform API Group to 3GPP SA, SA2, SA5, SA6 and ETSI ISG MEC on edge computing definition and integration | GSMA OPAG (OPAG_04_Doc_02) | Response from TSG SA in S2-2200078. Noted | Hui (Huawei) proposes to note this LS. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted | |
| 8.3 | S2-2200039 | LS In | Action | LS from GSMA OPG: Reply LS from GSMA Operator Platform Group to 3GPP SA, SA2, SA5, SA6 and ETSI ISG MEC on edge computing definition and integration | GSMA OPG (OPG_72_Doc_04) | Response from TSG SA in S2-2200078. Noted | Hui (Huawei) proposes to note this LS. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted | |
| 8.3 | S2-2200078 | LS In | Information | LS from TSG SA: Reply LS to GSMA Operator Platform Group on edge computing definition and integration | TSG SA (SP-220003) | TSG SA response to S2-2200039 and S2-2200038. Noted | Hui (Huawei) proposes to note this LS. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted | |
| 8.3 | S2-2200071 | LS In | Information | LS from SA WG4: LS on follow-up on EAS definition | SA WG4 (S4-211658) | Rel-17 | Noted | Hui (Huawei) proposes to note this LS. Dario (Qualcomm) shares the rapporteur's view. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 8.3 | S2-2200073 | LS In | Information | LS from SA WG5: Reply LS on Prioritized Vehicle to Cloud Technical Solutions (Automotive Edge Computing Consortium (AECC)) | SA WG5 (S5-216412) | Rel-17 | Noted | Hui (Huawei) proposes to note this LS. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 8.3 | S2-2200114 | CR | Approval | 23.501 CR3464 (Rel-17, 'F'): Aligning 23.501 and 23.548 wording about the DN accessed via a L-UPF | Nokia, Nokia Shanghai Bell | Rel-17 | r04 agreed. Revised to S2-2201708. | Hui (Huawei) provides comments. Magnus H (Ericsson) comments Laurent (Nokia): provides r01 Hui (Huawei) provides r02. Hui (Huawei) provides r03. Hui (Huawei) provides r04. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Laurent (Nokia): Ok with the versions of Hui ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.3 | S2-2201708 | CR | Approval | 23.501 CR3464R1 (Rel-17, 'F'): Aligning 23.501 and 23.548 wording about the DN accessed via a L-UPF | Nokia, Nokia Shanghai Bell | Rel-17 | Revision of S2-2200114r04. Approved | Agreed | |
| 8.3 | S2-2200159 | CR | Approval | 23.548 CR0043 (Rel-17, 'F'): Corrections on enabling EAS IP Replacement procedure by AF | China Unicom | Rel-17 | r02 agreed. Revised to S2-2201709. | Hui (Huawei) provides comments. Tianqi (China Unicom) replies to Hui (Huawei) and provides r01. Shubhranshu (Nokia) comments Tianqi (ChinaUnicom) replies to Shubhranshu (Nokia). Shubhranshu (Nokia) responds Changhong (Intel) agrees with Nokia and propose to keep the original text in the 1st change. Tianqi (China Unicom) replies to Shubhranshu (Nokia) and Changhong (Intel). Shubhranshu (Nokia) comments and provides r02 Tianqi (China Unicom) is fine with S2-2200159r02. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.3 | S2-2201709 | CR | Approval | 23.548 CR0043R1 (Rel-17, 'F'): Corrections on enabling EAS IP Replacement procedure by AF | China Unicom | Rel-17 | Revision of S2-2200159r02. Approved | Agreed | |
| 8.3 | S2-2200160 | CR | Approval | 23.502 CR3322 (Rel-17, 'F'): Corrections on notification of user plane management event procedure | China Unicom | Rel-17 | Approved | Huazhang (vivo) provides comments. Tianqi (China Unicom) replies to Huazhang (vivo). Hui(Huawei) agree with Tianqi. Huazhang(vivo) responses to Tianqi and Hui. Shubhranshu (Nokia) comments ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Agreed |
| 8.3 | S2-2200207 | CR | Approval | 23.501 CR3472 (Rel-17, 'F'): Clarify FQDN in Traffic Influence | Ericsson | Rel-17 | r04 agreed. Revised to S2-2201711. | Hui (Huawei) provides comments. Magnus H (Ericsson) ask question and comments Tugce (NTT DOCOMO) provides comments. Tingfang (Lenovo) comments. Tingfang (Lenovo) provides r01. Magnus H (Ericsson) comments Tingfang (Lenovo) comments . Magnus (Ericsson) provides r02 Hui (Huawei) prefer to r01 Tingfang (Lenovo) is OK with r02 . Hui (Huawei) provides r03. Hui (Huawei) provides r04. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.3 | S2-2201711 | CR | Approval | 23.501 CR3472R1 (Rel-17, 'F'): Clarify FQDN in Traffic Influence | Ericsson | Rel-17 | Revision of S2-2200207r04. Approved | Agreed | |
| 8.3 | S2-2200208 | CR | Approval | 23.548 CR0044 (Rel-17, 'F'): Local NEF discovery via CAPIF | Ericsson | Rel-17 | Noted | Laurent (Nokia): expresses doubts Dan (China Mobile) comments Hyesung (Samsung) asks clarification Magnus H (Ericsson) comments Laurent (Nokia): answers Magnus (Ericsson) provides r01 Magnus H (Ericsson) provides correct link to CR ==== 8.X, 9.X, 10.X Revisions Deadline ==== Laurent (Nokia): objects to any version of this CR ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 8.3 | S2-2200210 | CR | Approval | 23.548 CR0045 (Rel-17, 'F'): Correction related to EDI | Ericsson | Rel-17 | Noted | Xinpeng(Huawei) provides r01. Magnus H (Ericsson) comments Xinpeng(Huawei) Replies. Xinpeng(Huawei) The previous mail is post by Xinpeng(Huawei) not Magnus H (Ericsson), sorry about that... Laurent (Nokia): provides r02 Dario (Qualcomm) asks why new parameters are needed since it seems the issue can be solved with configuration. Xinpeng(Huawei) provides r03. Tingfang (Lenovo) commnets. Laurent (Nokia): Comments Magnus H (Ericsson) replies Magnus H (Ericsson) answers Dario Magnus H (Ericsson) provides r04 Laurent (Nokia): provides r05; we need to support 'Each of DNN and S-NSSAI may be wildcarded' Xinpeng(Huawei) replies to Laurent (Nokia) ==== 8.X, 9.X, 10.X Revisions Deadline ==== Magnus H (Ericsson) objects to r01,r02,r03,r05. Can only accept r00 and r04 Laurent (Nokia): Can only live with R02 and R05. suggest to POSTPONE as we have not settled the *Possibility* of wildcarding of DNN/S-NNSAI which I claim we need to support. Magnus H (Ericsson) withdraws previous objection and objects to all revisions except r03 where r03 is modified as follows: Table 6.2.3.4-1 the 'per DNAI' row is moved to be under the 'FQDN(s)' row, i.e. directly above the 'DNS Server Information' row Tingfang (Lenovo) is OK with r00, r04, prefers r04, objects others. ==== 8.X, 9.X, 10.X Final Deadline ==== Magnus H (Ericsson) ask if Tingfang can re-consider Xingpeng(Huawei) prefer r03. | Noted |
| 8.3 | S2-2200211 | CR | Approval | 23.502 CR3327 (Rel-17, 'F'): Correction related to EDI | Ericsson | Rel-17 | CC#4: r00 + changes agreed. Revised to S2-2201847. | Xinpeng(Huawei) provides r01. Laurent (Nokia): provides r02 Dario (Qualcomm) asks why new parameters are needed since it seems the issue can be solved with configuration. Xinpeng(Huawei) provides r03. Tingfang (Lenovo) commnets. Laurent (Nokia): Comments Xinpeng(Huawei) replies. Magnus H (Ericsson) replies. Magnus H (Ericsson) ask question regarding Event ID. Magnus H (Ericsson) provides r04 Xinpeng(Huawei) comments. Magnus H (Ericsson) comments Xinpeng(Huawei) replies to Magnus H (Ericsson). Magnus (Ericsson) provides r05 Tingfang (Lenovo) comments . Tingfang (Lenovo) provides r06 . Magnus H (Ericsson) comments no need for transaction id Tingfang (Lenovo) replies. Laurent (Nokia): answers asking other folks to give their opinion Xinpeng(Huawei) replies to Laurent (Nokia). Tingfang (Lenovo) comments. Magnus H (Ericsson) comment to Laurent. Tingfang (Lenovo) provides r07 based on r05. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Magnus H (Ericsson) can only accept r05, and objects to all other revisions. Magnus H (Ericsson) withdraws previous objection and objects to all version except r05 and r07 Tingfang (Lenovo) is OK with r06, r07, prefers r06, objects others. Xinpeng(Huawei) suggests take r07. Laurent (Nokia): Can only live with R02 and R06. Otherwise suggests to POSTPONE as we have not settled the *Possibility* of wildcarding of DNN/S-NNSAI which I claim we need to support. ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.3 | S2-2201847 | CR | Approval | 23.502 CR3327R1 (Rel-17, 'F'): Correction related to EDI | Ericsson, Nokia, Nokia Shanghai Bell | Rel-17 | Revision of S2-2200211r00 + changes. Approved | Agreed | |
| 8.3 | S2-2200283 | CR | Approval | 23.548 CR0046 (Rel-17, 'F'): Correction related EHE in EC architecture | Ericsson | Rel-17 | r01 agreed. Revised to S2-2201712. | Hui(Huawei) provides r01. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Magnus H (Ericsson) accepts r01 ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.3 | S2-2201712 | CR | Approval | 23.548 CR0046R1 (Rel-17, 'F'): Correction related EHE in EC architecture | Ericsson | Rel-17 | Revision of S2-2200283r01. Approved | Agreed | |
| 8.3 | S2-2200433 | DISCUSSION | Agreement | Feature control for eEDGE_5GC functionality | Ericsson | Rel-17 | Noted | Magnus Olsson (Ericsson) propose to note 433 (Ericsson doc) Hui (Huawei) agree with previous comments. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 8.3 | S2-2200524 | CR | Approval | 23.502 CR3358 (Rel-17, 'F'): Correction on notification on the outcome of UE Policies delivery due to service specific parameter provisioning | Orange | Rel-17 | Approved | Shubhranshu (Nokia) comments Antoine (Orange) replies. Shubhranshu (Nokia) responds ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Agreed |
| 8.3 | S2-2200609 | CR | Approval | 23.502 CR3254R1 (Rel-17, 'B'): UE indicates the EDC capability in PCO | vivo | Rel-17 | Revision of (Noted) S2-2108548 from S2#148E. Merged into S2-2201720 | Tugce (NTT DOCOMO) comments that S2-2200609 should be merged into S2-2201245. Dario (Qualcomm) shares NTT's view and proposes to merge this into 1245. Huazhang (vivo) is ok merge this into 1245, but object to not add the capability in 502 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 8.3 | S2-2200610 | CR | Approval | 23.502 CR3366 (Rel-17, 'F'): Add UE capability to SMF decision for ECS address delivery | vivo | Rel-17 | r03 agreed. Revised to S2-2201713. | Hui (Huawei) provides r01. Tingfang (Lenovo) comments. Huazhang (vivo) reply to Tingfang(Lenovo) Tugce (NTT DOCOMO) provides comments. Huazhang (vivo) reply to Tugce(NTT DOCOMO). Dario (Qualcomm) provides r02 to shorten change and remove normative wording from note. Shubhranshu (Nokia) comments and provides r03 Dario (Qualcomm) is fine with r03. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Huazhang (vivo) is fine with r03, thanks for your help Shubhranshu(Nokia) ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.3 | S2-2201713 | CR | Approval | 23.502 CR3366R1 (Rel-17, 'F'): Add UE capability to SMF decision for ECS address delivery | Vivo | Rel-17 | Revision of S2-2200610r03. Approved | Agreed | |
| 8.3 | S2-2200611 | CR | Approval | 23.502 CR3367 (Rel-17, 'F'): Add UPF capability that supports QoS monitoring event exposure in registration procedure to NRF | vivo | Rel-17 | r04 agreed. Revised to S2-2201714. | Magnus (Ericsson) provides r01 Huazhang (vivo) change the title to AI 8.3, and ask Magnus that r01 can't be open Tugce (NTT DOCOMO) provides comments. Magnus H (Ericsson) provides a correct link to r01 Huazhang (vivo) replys to Tugce Fenqin (Huawei) provides comments. Huazhang (vivo) provides r02 and reply to Fenqin (Huawei) Huazhang (vivo) provides r03 and reply to Fenqin (Huawei) Huazhang (vivo) thanks for Fenqin (Huawei)'s suggestions and provide r04 to modify the coversheet of CR and editorial changes ==== 8.X, 9.X, 10.X Revisions Deadline ==== Huazhang (vivo) thanks for Fenqin (Huawei)'s suggestions and supports to go with r04 ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.3 | S2-2201714 | CR | Approval | 23.502 CR3367R1 (Rel-17, 'F'): Add UPF event exposure that supports direct QoS monitoring | Vivo | Rel-17 | Revision of S2-2200611r04. Approved | Agreed | |
| 8.3 | S2-2200612 | CR | Approval | 23.503 CR0695 (Rel-17, 'F'): AF guides URSP policy determination via Npcf | vivo | Rel-17 | r01 agreed. Revised to S2-2201715. | Hui (Huawei) provides r01. Shubhranshu (Nokia) asks for clarification Huazhang(vivo) reply to Shubhranshu (Nokia) Shubhranshu (Nokia) comments Huazhang (vivo) replies to Shubhranshu ==== 8.X, 9.X, 10.X Revisions Deadline ==== Huazhang (vivo) is ok with r01 ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.3 | S2-2201715 | CR | Approval | 23.503 CR0695R1 (Rel-17, 'F'): AF guides URSP policy determination via Npcf | Vivo | Rel-17 | Revision of S2-2200612r01. Approved | Agreed | |
| 8.3 | S2-2200734 | CR | Approval | 23.548 CR0047 (Rel-17, 'F'): Update of EAS discovery procedure and BaselineDNSPattern management in EASDF | Tencent, Tencent Cloud | Rel-17 | r03 agreed. Revised to S2-2201716. | Hui (Huawei) provides r01. Zhuoyun (Tencent) comments. Hui (Huawei) replies to Zhuoyun. Zhuoyun (Tencent) is fine with r01. Laurent (Nokia): provides r02 Zhuoyun (Tencent) is ok with r02. Magnus (Ericsson) provides r03 Zhuoyun (Tencent) is ok with r03. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Laurent (Nokia): objects to R00 and R01, happy with R03 ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.3 | S2-2201716 | CR | Approval | 23.548 CR0047R1 (Rel-17, 'F'): Update of EAS discovery procedure and BaselineDNSPattern management in EASDF | Tencent, Tencent Cloud | Rel-17 | Revision of S2-2200734r03. Approved | Agreed | |
| 8.3 | S2-2200914 | CR | Approval | 23.501 CR3548 (Rel-17, 'F'): Add missing EASDF descriptions | Huawei, HiSilicon | Rel-17 | r02 agreed. Revised to S2-2201717. | Laurent (Nokia): provides r01 Hui (Huawei) provides r02 Magnus H (Ericsson) comments ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.3 | S2-2201717 | CR | Approval | 23.501 CR3548R1 (Rel-17, 'F'): Add missing EASDF descriptions | Huawei, HiSilicon, Nokia, Nokia Shanghai Bell | Rel-17 | Revision of S2-2200914r02. Approved | Agreed | |
| 8.3 | S2-2201087 | CR | Approval | 23.548 CR0049 (Rel-17, 'F'): Editorial update for EDC functionality | Lenovo, Motorola Mobility | Rel-17 | Merged into S2-2201719 | Dario (Qualcomm) proposes to merge this CR into 1244 Tingfang (Lenovo) replies it is OK to merge this CR into 1244. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 8.3 | S2-2201188 | CR | Approval | 23.503 CR0706 (Rel-17, 'F'): Correction to the UE Policies delivery notification | Nokia, Nokia Shanghai Bell | Rel-17 | Approved | Dario S. Tonesi (Qualcomm) asks question for clarification. Shubhranshu (Nokia) responds Dario (Qualcomm) thanks Shubhranshu Changhong (Intel) comments ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Agreed |
| 8.3 | S2-2201244 | CR | Approval | 23.548 CR0051 (Rel-17, 'F'): Corrections of EDC functionality description | Qualcomm Incorporated | Rel-17 | r03 agreed. Revised to S2-2201719, merging S2-2201087 | Tugce (NTT DOCOMO) provides comments. Sudeep (Apple) provides r01 and comments on the CR. Dario (Qualcomm) is OK with Apple's and NTT's proposals. Provides r02 including further changes. Hui (Huawei) provides comments. Sudeep (Apple) agrees with Hui's comment. Zhuoyun (Tencent) provides r03. Dario (Qualcomm) thanks and he is fine with r03. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Huazhang (vivo) is fine with r03. ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.3 | S2-2201719 | CR | Approval | 23.548 CR0051R1 (Rel-17, 'F'): Corrections of EDC functionality description | Qualcomm Incorporated | Rel-17 | Revision of S2-2201244r03, merging S2-2201087. Approved | Agreed | |
| 8.3 | S2-2201245 | CR | Approval | 23.502 CR3419 (Rel-17, 'F'): Corrections of EDC functionality description | Qualcomm Incorporated | Rel-17 | r03 agreed. Revised to S2-2201720, merging S2-2200609 | Tugce (NTT DOCOMO) provides comments. Dario (Qualcomm) thanks Tugce and provides r01 Huazhang (vivo) provides r02 (r01 has already in folder) Dario (Qualcomm) provides r03 which rewords r02 Magnus H (Ericsson) comments and makes suggestion Dario (Qualcomm) replies to Magnus. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Huazhang (vivo) is OK with r03 ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.3 | S2-2201720 | CR | Approval | 23.502 CR3419R1 (Rel-17, 'F'): Corrections of EDC functionality description | Qualcomm Incorporated | Rel-17 | Revision of S2-2201245r03, merging S2-2200609. Approved | Agreed | |
| 8.3 | S2-2201266 | LS In | Action | LS from GSMA OPAG: Further Operator Platform Group questions following SDO Workshop | GSMA OPAG (OPAG_09_Doc_04) | Response to TSG SA drafted in S2-2201682. Final LS in S2-2201721 | Hui(Huawei) provides a draft LS reply. Jicheol (Samsung) supports drafring the LS reply. Dario (Qualcomm) proposes to move the discussion to the S2-2201682 email thread. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Magnus O (Ericsson) this is an incoming LS and should be marked as replied to in 1628 ==== 8.X, 9.X, 10.X Final Deadline ==== | Replied to | |
| 8.3 | S2-2201682 | LS OUT | Approval | [DRAFT] LS on Further GSMA OPG questions following SDO Workshop | SA WG2 | Created at CC#2. LS related to S2-2201266 for TSG SA collation.. r05 agreed. Revised to S2-2201721. | Dario (Qualcomm) provides r01 Dario (Qualcomm) provides link to original version by Hui Hui(Huawei) provides r02 Magnus (Ericsson) provides r03 Hui (Huawei) fine with r03 Jicheol (Samsung) provides r04. Hui (Huawei) provides r05. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised | |
| 8.3 | S2-2201721 | LS OUT | Approval | Reply LS on Further GSMA OPAG questions following SDO Workshop | SA WG2 | Rel-17 | Revision of S2-2201682r05. Approved | Approved | |
| 8.4 | - | - | - | Enhancement of Network Slicing Phase 2 (eNS_Ph2) | - | - | Docs:=47 | - | |
| 8.4 | - | - | - | NSAC general | - | - | Docs:=12 | - | |
| 8.4 | S2-2200201 | LS In | Action | LS from CT WG4: LS on a single operation for updating both number of UE and number of PDU in EPS | CT WG4 (C4-220331) | Rel-17 | Responses drafted in S2-2200893 and S2-2201178. Final response in S2-2201855 | ==== 8.X, 9.X, 10.X Final Deadline ==== | Replied to |
| 8.4 | S2-2200893 | LS OUT | Approval | [DRAFT] Reply LS on a single operation for updating both number of UE and number of PDU in EPS | Nokia, Nokia Shanghai Bell | Rel-17 | Response to S2-2200201. Merged into S2-2201855 | Jinguo(ZTE) suggests to merge this LS in 1178 to use single thread for discussion ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 8.4 | S2-2201178 | LS OUT | Approval | [DRAFT] Reply to LS on a single operation for updating both number of UE and number of PDU in EPS | NEC | Rel-17 | Response to S2-2200201. CC#4: Postponed to CC#5. CC#5: r04 agreed. Revised to S2-2201855, merging S2-2200893. | Srisakul (NTT DOCOMO) comments. George (Ericsson) provides comments. This LS and all other LSs related to this issue to be noted. alessio(Nokia) proposes to note this and use 893 instead. Kundan(NEC) disagrees with Alessio: 893 includes a CR which is addressing scenarios other than mentioned in the LS. alessio(Nokia) does not mind which CR (if any) is eventually attached but creating a new operation is not acceptable. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Tao(VC) I don't see converge on the response LS OUT. Neither 893 nor 1178. Jinguo(ZTE) suggest to keep 1178 open George (Ericsson) We need to tell then that there was no agreement Jinguo(ZTE) asks to discuss it at CC#4 ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.4 | S2-2201855 | LS OUT | Approval | Reply to LS on a single operation for updating both number of UE and number of PDU in EPS | SA WG2 | Rel-17 | Revision of S2-2201178r04, merging S2-2200893. Approved | Approved | |
| 8.4 | S2-2201176 | CR | Approval | 23.501 CR3575 (Rel-17, 'F'): Combined update number of UE and number of UE update NSAC procedure in EPS | NEC, Samsung | Rel-17 | Noted | George Foti (Ericsson) proposes to note the CR. Additional comments Kundan (NEC) provides response to George. Jinguo(ZTE) propose to note this CR Kundan(NEC) responds to Jinguo(ZTE). Jinguo(ZTE) disagree with Kundan(NEC) George (Ericsson) provides comments. We are still NOT Ok with this approach. Kundan (NEC) further responds to George(Ericsson) comment. Srisakul (NTT DOCOMO) agrees with George (Ericsson) and Jinguo (ZTE). George (Ericsson) provides additional comment. Alessio(Nokia) agrees adding a third service makes no sense. so we should rather use a single service: the PDU session update like proposed. in our papers. proposes to note. Kundan (NEC) clarifies further with Srisakul . ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 8.4 | S2-2200325 | CR | Approval | 23.501 CR3489 (Rel-17, 'F'): Clarifications on NSAC for Emergency and Priority Services | Peraton Labs, CISA ECD, Verizon, AT&T, T-Mobile USA | Rel-17 | r02 agreed. Revised to S2-2201277. | Dongeun (Samsung) provides r01. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.4 | S2-2201277 | CR | Approval | 23.501 CR3489R1 (Rel-17, 'F'): Clarifications on NSAC for Emergency and Priority Services | Peraton Labs, CISA ECD, Verizon, AT&T, T-Mobile USA | Rel-17 | Revision of S2-2200325r02. Approved | Agreed | |
| 8.4 | S2-2200347 | CR | Approval | 23.502 CR3347 (Rel-17, 'F'): Clarification on EAC notification for unsubscription | China Telecom | Rel-17 | Noted | George Foti (Ericsson) proposes to note the CR. Please see additional comments Heng(China Telecom) reply George (Ericsson) this is a wrong link Ashok (Samsung) need clarification from Heng (China Telecom) Heng(China Telecom) corrects the link Heng(China Telecom) offer clarification to Ashok (Samsung) George (Ericsson) provides comment. Ouerdia (Orange) provides comment. Heng (China Telecom) reply to Ouerdia. Heng (China Telecom) reply to George. George (Ericsson) provides comment. Please describe what situation cannot be handled. Alessio(Nokia) asks a question. do you know if this is already done in CT4? I mean it is an alignment or a new work we are starting? Heng(China Telecom) reply. do you know if this is already done in CT4? I mean it is an alignment or a new work we are starting? George (Ericsson) provides reply Heng (China Telecom) reply to George (Ericsson) ==== 8.X, 9.X, 10.X Revisions Deadline ==== TAO(VC) check whether r00 agreeable with the clarification by Heng George (Ericsson) Ericsson objects to the CR and all its revisions. ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 8.4 | S2-2200630 | CR | Approval | 23.502 CR3368 (Rel-17, 'F'): NSAC clarification | Samsung | Rel-17 | Noted | Fenqin (Huawei) comment Ashok (Samsung) responds to Fenqin (Huawei) Fenqin (Huawei) give a response Ashok (Samsung) ask a question to Fenqin (Huawei) Fenqin (Huawei) provides a response Srisakul (NTT DOCOMO) comments. Fenqin (Huawei) comments and provide r01. Fenqin (Huawei) comments. Ashok (Samsung) thanks Fenqin (Huawei) for the revised text proposal Fenqin (Huawei) provides r02 George (Ericsson) OK only with the original. This is the type of CR s that is completely not needed. It is not a stage 2 type of detail that is required here. Fenqin (Ericsson) We object r00 as it is incorrect to use the OR operation. R01/R02 remove that problem. Alessio(Nokia) proposes to postpone this CR to think more about this (especially if it has no stage 3 impact we should see if this can be solved by implementations or requires standards to provide behavior guidance Ashok (Samsung) responds to Alessio(Nokia) Fenqin (Huawei) We support the view from Ashok that this is a necessary correction. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Tao(VC) check whether Ashok clarified enough and r02 agreeable or not. George (Ericsson) provides comment. Ericsson accepts only the original. Jinhua(Xiaomi) provides comment, r00 is prefer, can live with r02. Genadi (Lenovo) prefers r00. Fenqin (Huawei) keep the same position as before, i.e. object R00 and either R01 or R02 is ok. Tao(VC) can we agree r00? Jinhua(Xiaomi) replies to Fenqin, propose r02 for approval. Jinhua(Xiaomi) replies to Tao(VC), propose r02 for approval. ==== 8.X, 9.X, 10.X Final Deadline ==== George (Ericsson) Ericsson re-iterates only r00 is OK. Jinhua(Xiaomi) can live with r00, for the progress. Genadi (Lenovo) after re-reading the emails, I agrees that r02 is preferrable. George (Ericsson) provides comments. Frankly speaking this whole CR is not needed. It is a stage 3 type of CR at best. So much implementation related. The removal of UE context is an internal action not verifiable. So enough for now. Ashok (Samsung) responds to George (Ericsson) : How come the context removal is internal things and not verifiable? We have clearly written some triggers in 502 spec like some timer, UDM sending dereg notification etc for AMF to remove UE context. Also this removal has impact on NSACF counting the UE reg quota. But after all the clarification if you are not convinced it's better to NOTE it. | Noted |
| 8.4 | S2-2200720 | CR | Approval | 23.501 CR3532 (Rel-17, 'F'): NSAC for maximum number of PDU Sessions for EPC IWK | Lenovo, Motorola Mobility, NTT DOCOMO, NEC, ZTE | Rel-17 | Postponed | Heng(China Telecom) comment: Some of the description seems inaccurate Genadi (Lenovo) replies to Heng Nie (China Telecom). Heng (China Telecom) thanks for the reply. Fenqin (Huawei) provides r01. George (Ericsson) provides comments. These details really are not required. It is obvious. All these revisions for what is obvious is just consuming endless times with hardly any value added. Ashok (Samsung) comments and provides r02 alessio(Nokia) comments that this is just one example of what is not working and our CRs resolve at the root by implementing the GSMA requirements correctly . we ask to posptopne this topic and mark the whole NSAC as work in progress in rel-17 if the nokia CRs fixing the feature are not implemented. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Postponed |
| 8.4 | S2-2201101 | CR | Approval | 23.502 CR3411 (Rel-17, 'F'): NSAC for maximum number of PDU Sessions and MA PDU Session | Lenovo, Motorola Mobility | Rel-17 | r11 agreed. Revised, merging S2-2200874, to S2-2201278. | Jinguo(ZTE) provides r01 DongEun (Samsung) asks for clarification. Myungjune (LGE) supports r01. Genadi (Lenovo) asks for clarifications to r01. Genadi (Lenovo) replies to comments from Myungjune (LGE) and Dongeun (Samsung). Myungjune (LGE) replies to Genadi (Lenovo) Dario (Qualcomm) comments and provides r02 Genadi (Lenovo) replies to Myungjune (LGE). Genadi (Lenovo) replies to Dario (Qualcomm). Genadi (Lenovo) provides r03. Krisztian (Apple) supports r03. Providing the backoff timer to the UE at the time of NSAC rejection is the correct way. Myungjune (LGE) comments on r03 and proposes to approve r01. Genadi (Lenovo) replies to Myungjune (LGE) and proposes to approve r03. George (Ericsson) Ericsson supports r03. I find r01 vague. What is current access type. The SMF knows whether the UE is registered in one access, and which one, or both. So 'current access type' does not mean anything. George (Ericsson) provides comment. I though r03 was pretty clear as U describe below. The UE knows that one AT is OK, so it has to apply the BOT to the other one if it gets one. We need no more text please. Genadi (Lenovo) comments to George (Ericsson). Jinguo(ZTE) comments Jinguo(ZTE) provides r04 Genadi (Lenovo) provides r05. Jinguo(ZTE) is fine with r05 Ashok (Samsung) comments Myungjune (LGE) provides r06 Myungjune (LGE) comments on r07 Jinguo(ZTE) provides r07 Jinguo(ZTE) replies to Myungjune (LGE) Myungjune (LGE) replies to Jinguo(ZTE) Myungjune (LGE) replies to Jinguo(ZTE) and proposes to agree r06. Dongeun (Samsung) asks for clarifications Jinguo(ZTE) replies to Myungjune (LGE) and still prefer r04, r05 and r07, object r06 and revisions before r04. Jinguo(ZTE) replies to Dongeun (Samsung) Myungjune (LGE) replies to Jinguo (ZTE) Dongeun (Samsung) asks clarifications again Myungjune (LGE) questions on reuse of NAS congestion control back off timer Genadi (Lenovo) comments on the reuse of NAS congestion control BOT for NSAC George (Ericsson) Ericsson supports only r06. R07 is incorrect Genadi (Lenovo) replies to Myungjune (LGE) regarding MA PDU Session in roaming. Genadi (Lenovo) provides r08. George (Ericsson) Is Ok only with r06. The BOT is sent with the rejected message and is applicable to the Access over which the request is received. So what is the ambiguity that we are trying to address. Genadi (Lenovo) replies to George (Ericsson). George (Ericsson) provides response in line below. Alessio(NOKIA) Is Ok only with r08 Dario (Qualcomm) is OK with r08 Myungjune (LGE) provides r10 George (Ericsson) asks a question Myungjune (LGE) provides r09 and objects all previous revisions including original version Jinguo(ZTE) prefers r09, but can live with r07, r08, and r10. Genadi (Lenovo) provides r11 for editorial and clean-up changes. Fenqin (Huawei) provides r12 George (Ericsson) Ericsson NOT OK with r12. I have a question on r11 though. Why is this last Note a note. It should be a bullet as well. It is a missing case. I prefer to see it as a bullet. Fenqin (Huawei) ask a question George (Ericsson) provides comments. Not clear. We need a bullet form that U removed Fenqin (Huawei) it do cover the scenario below. You can check on it. ==== 8.X, 9.X, 10.X Revisions Deadline ==== George (Ericsson) Ericsson accepts r11only. Bullet form text leaves no ambiguity, and make sure we cover all cases clearly. I would prefer the Note to be converted to a bullet as well. But Ok for now Myungjune (LGE) responds to George (Ericsson) and Fenqin (Huawei) Dongeun (Samsung) agrees with Ericsson and ok with r11 ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.4 | S2-2201278 | CR | Approval | 23.502 CR3411R1 (Rel-17, 'F'): NSAC for maximum number of PDU Sessions and MA PDU Session | Lenovo, Motorola Mobility | Rel-17 | Revision of S2-2201101r11, merging S2-2200874. Approved | Agreed | |
| 8.4 | - | - | - | NSAC - Access Type | - | - | Docs:=4 | - | |
| 8.4 | S2-2200554 | CR | Approval | 23.502 CR3364 (Rel-17, 'F'): NSAC notification per Access Type | Samsung, NTT DOCOMO | Rel-17 | Postponed | George Foti (Ericsson) provides r01 Iskren (NEC) provides r02 Ashok (Samsung) comments Iskren (NEC) answers Ashok (Samsung) Srisakul (NTT DOCOMO) ok with r02 Fenqin (Huawei) comment Ashok (Samsung) explains to Fenqin (Huawei) Fenqin (Huawei) provides comment Ashok (Samsung) responds to Fenqin (Huawei) Jinhua(Xiaomi) provides comments, Iskren (NEC) provides comments, Ashok (Samsung) responds to Iskren (NEC) and Jinhua (Xiaomi) Iskren (NEC) provides r03 Ashok (Samsung) need clarification from Iskren (NEC) Iskren (NEC) answers question from Ashok (Samsung) Fenqin (Huawei) provides comments Ashok (Samsung) responds to Fenqin (Huawei) and Iskren (NEC) Genadi (Lenovo) comments that the quota may be per AT. Genadi (Lenovo) comments that AT is associated with S-NSSAI. Prefer r01. Iskren (NEC) provide comments. r00 and r01 are not acceptable. Jinhua(Xiaomi) replies to Ashok, Jinhua (Xiaomi) replies to Genadi(Lenovo) Jinhua (Xiaomi) provides comments, propose to merge 0946r01 into 0554, George (Ericsson) provides comment. This is link for a separate CR nit aligned with the subject. So please use the proper subject George (Ericsson) provides comment. Ericsson accepts only r02. The Access Type has to be part of the Event Filter. The whole purpose of the filter is to limit what the NOTIFY is all about. Jinhua replies to George, Iskren(NEC) answers to Ashok (Samsung) Srisakul (NTT DOCOMO) comments. Not ok with r03. Fine with r02. Iskren (NEC) answers question from Jinhua (Xiaomi) Jinhua(Xiaomi) provides comments, the overlapped Clauses (clarification of AT related to SliceEventExposure) will be removed from 0946, George (Ericsson) provides comments Iskren (NEC) provides comments. Ashok (Samsung) explains to Iskren (NEC) and gave spec reference from SA2, CT1, CT4 to justify that NSAC quota per AT is present in all stage 2 and stage 3 specifications and there should not be any confusion about it Fenqin (Huawei) ask a question Iskren (NEC) comments George (Ericsson) provides additional comment George (Ericsson) provides comments. Iskren (NEC) answers Ashok (Samsung). Jinguo(ZTE) mention that nothing is broken. Iskren (NEC) disagrees with Jinguo(ZTE) Srisakul (NTT DOCOMO) comments and agrees with Jinguo. Ashok (Samsung) comments George (Ericsson) Genadi (Lenovo) provides comments. Jinhua(Xiaomi) provides comments, 0554r02 is prefer, George (Ericsson) Ericsson objects to all revisions including the original Ashok (Samsung) request George (Ericsson) to update the reason for objections within these tags so that it can be captured in chairman's report. George (Ericsson) provides comments . This is an optimization CR, nothing is broken; a similar optimization was not accepted last meeting addressing same functionality; and indeed was better than the new proposed one in this CR. Additionally, this optimization requires the AMF to support this feature, and given that the new parameter is optional, it is not mandatory for the AMF to support it. This is also not a cat F CR. Ashok (Samsung) comments to George (Ericsson): It seems you are giving reasons for 0555 CR here. This CR you wanted to object because in your view SA2 does not support 'Quota per AT'. Hence please clarify Iskren (NEC) also object this CR as it does not fit with the rest of the feature agreements in SA2, see comments below. George (Ericsson) provides comments. Ericsson objects to all revisions including the original. Indeed we have only a single global quota and no quota per AT. Hence this CR is not aligned with the existing functionality alessio(Nokia) proposes to postpone these CRs this we figure out better the per AT topic. To us there is also no need for this... the quota is one in NG.116 for now. This is not CAT F however to us as there is no mis operation that can happen with a global exposure of the total number. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Postponed |
| 8.4 | S2-2200555 | CR | Approval | 23.502 CR3365 (Rel-17, 'F'): EAC notification per Access Type | Samsung, NTT DOCOMO | Rel-17 | Postponed | George Foti (Ericsson) proposes to note the CR. Please see additional comments Ashok (Samsung) replies to George (Ericsson) George (Ericsson) provides answer Ashok (Samsung) responds to George (Ericsson) George (Ericsson) Please change the CAT F Jinhua(Xiaomi) provides comments and r01, Ashok (Samsung) thanks Jinhua(Xiaomi) for providing the r01 and fine with it. George (Ericsson) Ericsson NOT OK with either revisions. Additional comments below Ashok (Samsung) agrees with George (Ericsson) and provides r02 by making Access Type optional George (Ericsson) provides comments. I think U need to move this text 'The optional Access Type input parameter indicates whether the EAC mode is applicable for 3gpp, non-3gpp or both'. o the input optional section to align with the spec. as a whole. Ashok (Samsung) provides r03 Jinhua(Xiaomi) provides r04, Ashok (Samsung) comments Srisakul (NTT DOCOMO) ok with r04 Iskren (NEC) provides r05, Jinhua(Xiaomi) replies to Iskren, OK with r05, George (Ericsson) provides comment. Ericsson NOT OK with r05, or any other revisions including the original. Ashok (Samsung) explains to George (Ericsson) George (Ericsson) provides response inline Genadi (Lenovo) seeks clarification from Ashok (Samsung) and George (Ericsson) Iskren (NEC) comments George (Ericsson) My responses in line to Ashok asked the same question. Ashok (Samsung) responds to George (Ericsson) provides response inline Ashok (Samsung) responds to Iskren (NEC) and Genadi (Lenovo) . Iskren (NEC) answers Ashok Ashok (Samsung) comments. I am simply saying that with this CR , AMF will be able to set the EAC mode correctly for 3GPP access if NSACF responds with 3GPP AT in EAC notification. Also for AMF there will no ambiguity as it will never set EAC mode for N3GPP access George (Ericsson) provides comments So this clearly an optimization to avoid configuration in the AMF of this information in the AMF that U tried before and did not progress. U should have stated that in the coversheet that this is an optimization and we could have saved 100 emails. Ashok (Samsung) comments. It is setting correct EAC mode as per the functionalities we have specified in our spec. I would request you to provide revision and lets close it. Ashok (Samsung) comments need answers from George (Ericsson): EAC feature itself is introduced to handle the latency and bring optimization. Now anything wrong to address on EAC feature will be obviously fall into optimization category. Does that mean we will not correct the issues wrt EAC feature. Setting the wrong EAC mode is a fault which should be handled as part of cat F CR. Ashok (Samsung) provides r06 Jinhua(Xiaomi) is OK with r06, new clarification of EAC scenario is persuasive, Iskren (NEC) object this CR as it does not fit with the current SA2 NSAC feature agreements alessio(Nokia) proposes to postpone these CRs this we figure out better the per AT topic. To us there is also no need for this... EAC should be invoked when needed. Using a single policy for all the ATs. This is not CAT F to us as there is no mis operation that can happen with a universal EAC (AT independent). ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Postponed |
| 8.4 | S2-2200945 | CR | Approval | 23.501 CR3550 (Rel-17, 'F'): Clarification of NSAC about the Access Type | Xiaomi, | Rel-17 | Noted | George Foti (Ericsson) proposes to consider this merged in 0554. Please see additional Jinhua(Xiaomi) replies to George, Jinhua(Xiaomi) provides r01, with comments, Srisakul (NTT DOCOMO) would consider this CR is not necessarily needed. Provide r02. George (Ericsson) is OK ONLY with r02. Jinhua(Xiaomi) replies to George and Srisakul, r02 is OK, George (Ericsson) Ericsson objects to all revisions including the original. This is an optimization; not a cat F CR alessio(Nokia) also objects to all revisions. the per AT feature is outside GSMA NG.116 requirements. while we can support MORE than GSMA requires, we need to check now SA5 has enabled the configuration of this per AT behaviour as they follow NG.116 and this per AT behavior is not there in NG.116. once we find SA5 has done their part we can certainly retain this and fix what needs fixing. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 8.4 | S2-2200946 | CR | Approval | 23.502 CR3391 (Rel-17, 'F'): Clarification of NSAC about the Access Type | Xiaomi, | Rel-17 | Noted | George Foti (Ericsson) provides comments Jinhua(Xiaomi) replies to George, and provides 0946r01, Iskren (NEC) comments Jinhua(Xiaomi) replies to Iskren, Jinhua (Xiaomi) provides comments, propose to merge 0946r01 into 0554, George (Ericsson) provides comment. Srisakul (NTT DOCOMO) comments and provides r02. Iskren (NEC) suggests this CR is considered merged to S2-2200554 r02. Jinhua (Xiaomi) replies to Srisakul(NTT DOCOMO), and provides r03, Ashok (Samsung) is OK with r03 Srisakul (NTT DOCOMO) ok with r03 George (Ericsson) NOT OK with any revision including the original. Iskren (NEC) this CR is not acceptable in any variation. It should be noted. Jinhua (Xiaomi) replies to George and Iskren, provides r04, alessio request to postpone this topic till we know SA5 can support NSAC per AT configuration. then we will need to update NG.116 also I gather... Jinhua (Xiaomi) replies to Alessio, please see the clarification of r04, Iskren (NEC) - This CR is not acceptable in any revision, ==== 8.X, 9.X, 10.X Revisions Deadline ==== Jinhua(Xiaomi) replies to Iskren, more clarification is provided, please double check, ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 8.4 | - | - | - | NSAC – multiple NSACFs | - | - | Docs:=13 | - | |
| 8.4 | S2-2200864 | CR | Approval | 23.501 CR3434R1 (Rel-17, 'F'): Clarification of NSAC | Nokia, Nokia Shanghai Bell | Rel-17 | Revision of (Noted) S2-2108817 from S2#148E. Noted | Iskren (NEC) suggests to note this CR, see the comments bellow. George Foti (Ericsson) proposes to note the CR. alessio(Nokia) replies that this CR aligns with the latest GSMA requirements. the only one that is still ambiguous is EPS counting enabled and we believe the CR in here addresses adequately. the CR does not rewrite the text for fun, it does that to fix what is not working now and not aligned with the GSMA requirements. if these CRs are not approved the whole NSAC text should be marked as work in progress in the TS and not to be implemented as written. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 8.4 | S2-2200895 | CR | Approval | 23.502 CR3293R1 (Rel-17, 'F'): Clarification of NSAC | Nokia, Nokia Shanghai Bell | Rel-17 | Revision of (Noted) S2-2108831 from S2#148E. Confirm Spec version used - CR states 17.2.1! Noted | Iskren (NEC) suggests to note this CR, see the comments bellow. George Foti (Ericsson) proposes to note the CR. Please see additional comments alessio(Nokia) replies that this CR aligns with the latest GSMA requirements. the only one that is still ambiguous is EPS counting enabled and we believe the CR in here addresses adequately. the CR does not rewrite the text for fun, it does that to fix what is not working now and not aligned with the GSMA requirements. if these CRs are not approved the whole NSAC text should be marked as work in progress in the TS and not to be implemented as written. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 8.4 | S2-2200091 | CR | Approval | 23.501 CR3239R2 (Rel-17, 'F'): Support for Session Continuity for EPC 5GC IWK, and inter-AMF Mobility. | Ericsson, NEC | Rel-17 | Revision of (Noted) S2-2108331 from S2#148E. Noted | Alessio(Nokia) proposes to note this paper ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 8.4 | S2-2200092 | CR | Approval | 23.502 CR3126R2 (Rel-17, 'F'): Support for Session Continuity for EPC 5GC IWK, and inter-AMF Mobility. | Ericsson, NEC | Rel-17 | Revision of (Noted) S2-2108332 from S2#148E. Noted | Alessio(Nokia) proposes to note this paper ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 8.4 | S2-2200089 | CR | Approval | 23.501 CR3463 (Rel-17, 'F'): Support for NSAC for Roaming subscribers. | Ericsson | Rel-17 | Noted | Dan (China Mobile) comments and suggest to udpate the paper or NOTE it. Fenqin (Huawei) support the view from Dan Fenqin (Huawei) propose to note this paper Alessio(Nokia) also propose to note this paper George (Ericsson) provides comments. This is a Release 18 issue, so U can provide a detailed solution, that can be evaluated against others. Iskren (NEC) support this CR. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 8.4 | S2-2200090 | CR | Approval | 23.502 CR3317 (Rel-17, 'F'): Support for NSACF for Roaming Subscribers | Ericsson | Rel-17 | Noted | Alessio(Nokia) proposes to note this paper Iskren (NEC) supports this CR ==== 8.X, 9.X, 10.X Revisions Deadline ==== George (Ericsson) provides comments. Tao(VC) can Alessio convinced by the response? Fenqin (Huawei) propose to note this paper. ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 8.4 | S2-2200880 | CR | Approval | 23.501 CR3545 (Rel-17, 'F'): Multi NSACF support for roaming and multi service area | Huawei, HiSilicon, China Mobile, China Telecom, China Unicom | Rel-17 | Noted | Fenqin (Huawei) provides r01. George (Ericsson) proposes to note the CR. Fenqin (Huawei) ask the reason? George (Ericsson) I don't know how many times I need to repeat this. Additional comments below. George (Ericsson) provides comments. What was discussed was a PCF solution. Is that what U have in mind by saying it is being discussed in the TR. Fenqin (Huawei) provides comments. George Foti (Ericsson) proposes to note the CR. Additional comments below Alessio(nokia) supports r01 Iskren (NEC) object any revision of this CR. We can not start a new interface between NSACFs with a lot of impact to an already agreed NSAC in the frozen Rel-17. This is a potential discussion for Rel-18. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 8.4 | S2-2200881 | CR | Approval | 23.502 CR3388 (Rel-17, 'F'): Multi NSACF support for roaming and multi service area | Huawei, HiSilicon, China Mobile, China Telecom, China Unicom | Rel-17 | Noted | George Foti (Ericsson) proposes to note the CR. Please see additional comments alessio(nokia) supports r01 Iskren (NEC) object any revision of this CR. We can not start a new interface between NSACFs with a lot of impact to an already agreed NSAC in the frozen Rel-17. This is a potential discussion for Rel-18. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 8.4 | S2-2200947 | CR | Approval | 23.502 CR3392 (Rel-17, 'F'): Remove the Editor's Note about Multiple NSACFs | Xiaomi, | Rel-17 | CC#4: Approved | Fenqin (Huawei) provides r01 George (Ericsson) Ericsson OK only with the original The added note is incorrect specially if U have a single service area. If U want to add a note than say in this release we only support a single service area. That would be OK. Iskren (NEC) comments. R01 is not acceptable. Fenqin (Huawei) provides r02 Jinhua(Xiaomi) replies to Fenqin, George and Iskren, provide r03 with comments, George (Ericsson) Ericsson Objects to r02. Again U make coorindation as the only way to solve this. This is a roadmap for a solution. Let solutions of any sort be submitted than we can discuss. I don't U don't give up but so am I ??. We are willing to have an open mind. George (Ericsson) provides comments. We object to this revision. Any hint on needing coordination is solution centric. Fenqin (Huawei) comments ==== 8.X, 9.X, 10.X Revisions Deadline ==== George (Ericsson) Ericsson objects to r03. Jinhua(Xiaomi) replies to George and Fenqin, propose r0 for progress, Dogneun (Samsung) suggest to go with r00 Jinhua(Xiaomi) replies to Jinguo, Jinguo(ZTE) corrects the title and agree with r00, Iskren (NEC) suggests to agree the initial version r00 Alessio(Nokia) prefers to note this paper .... we can come back next quarter with general cleanups and see what works or not of this feature and add notes to says so. unfortunately this feature has too many unstable parts. we will need also to report to GSMA the inability to deliver some of the expectations. Jinguo(ZTE) suggests to approve with r00 Jinguo(ZTE) asks to discuss it at CC#4 ==== 8.X, 9.X, 10.X Final Deadline ==== | Agreed |
| 8.4 | S2-2201162 | CR | Approval | 23.501 CR3571 (Rel-17, 'F'): Clarification on support of multiple NSACFs | ZTE | Rel-17 | r06 agreed. Revised to S2-2201279. | Dongeun (Samsung]) asks for clarfiication. Jinguo(ZTE) provides r01 Srisakul (NTT DOCOMO) provides r02 George (Ericsson) provides r03. We should allow for implementation specific means to support SC. alessio(Nokia) disagrees with all revisions of this CR. also there is no need to include implementation specific things in a CR to discuss SC topic when the quota is fractioned as there is no provision in GSMA NG.116 for split quotas among zones of a slice so the only interoperable and working way to achieve a single quota in roaming and multi-SA is to use interaction with a central NSACF for the slice. Jinguo(ZTE) sugges to agree r03, or r02 George (Ericsson) Ericsson Ok with r02, or r03. We will study the topic properly in Rel-18, so solutions can be clear, complete and written down. Then we can perform the proper evaluation.. Genadi (Lenovo) provides r04 to insert the NOTE in clause '5.15.11.0 General'. Jinguo(ZTE) provides r05 George (Ericsson) Ericsson OK with r05 Fenqin (Huawei) provides r06 George (Ericsson) OK with r06 ==== 8.X, 9.X, 10.X Revisions Deadline ==== DongEun (Samsung) is OK with r06 ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.4 | S2-2201279 | CR | Approval | 23.501 CR3571R1 (Rel-17, 'F'): Clarification on support of multiple NSACFs | ZTE | Rel-17 | Revision of S2-2201162r06. Approved | Agreed | |
| 8.4 | S2-2201163 | CR | Approval | 23.502 CR3416 (Rel-17, 'F'): Clarication on support of roaming for NSAC | ZTE | Rel-17 | CC#4: r02 agreed. Revised to S2-2201840. | George Foti (Ericsson) objects to the CR. Please see additional comments George (Ericsson) provides response. Jinguo(ZTE) replies to George (Ericsson) Jinguo(ZTE )further reply to George (Ericsson) Fenqin (Huawei ) comments George (Ericsson) provides additional comment Fenqin (Huawei) provides comment George (Ericsson) provides comments George (Ericsson) provides comments. Then we wait for Release 18 to resolve this. What is being proposed is not acceptable. It is a one use case design without usability; does not have any means for informing the VPLMN realtime of any changes. What I proposed is not on the fly. We intended to bring it. It is based on what exists already and reuses notification framework, and does not have any gaps. Jinguo(ZTE) provides r01 George (Ericsson) Ericsson NO OK with all revisions. We should just remove the Editors Note. The note prejudges that such interaction is needed. There is no interaction with the HPLMN at all in this release for any admission. Any note should simply state: 'There is no admission with the HPLMN in this Release', and remove the Editors note. Jinguo(ZTE) provides r02 George (Ericsson) Ericsson OK with r02 Alessio(Nokia) cannot agree to the proposed CR. proposes to note all revisions. Jinguo(ZTE) suggests to agree r02. We can discuss the topic further in r18. It doesn't make sence to keep an open issue in Rel-17 anymore. Fenqin(Huawei) provides r03 Iskren (NEC) object all revision of this CR. The normative spec is not a place for study requirements. George (Ericsson) Ericsson Objects to r03. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Jinguo(ZTE) suggest to agree r02 Tao(VC) further check r02 agreeable or not. Dongeun (Samsung) is ok with r02 and objects to r03 Jinhua(Xiaomi) provides comments, supports r02, Iskren (NEC) agrees with r02 George (Ericsson) Ericsson supports r02 Alessio(Nokia) requests to note this paper .... we can come back next quarter with general cleanups and see what works or not of this feature and add notes to says so. unfortunately this feature has too many unstable parts. we will need also to report to GSMA the inability to deliver some of the expectations. Jinguo(ZTE) proposes to approve r02 Jinguo(ZTE) asks to discuss at CC#4. ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.4 | S2-2201840 | CR | Approval | 23.502 CR3416R1 (Rel-17, 'F'): Clarification on support of roaming for NSAC | ZTE | Rel-17 | Revision of S2-2201163r02. Approved | Agreed | |
| 8.4 | - | - | - | Key issue#3 | - | - | Docs:=5 | - | |
| 8.4 | S2-2201260 | LS In | Action | LS from CT WG3: LS on handling of UE-Slice-MBR(s) change related to Allowed NSSAI change | CT WG3 (C3-220400) | Rel-17 | Response drafted in S2-2200890. Final response in S2-2201280 | ==== 8.X, 9.X, 10.X Final Deadline ==== | Replied to |
| 8.4 | S2-2200890 | LS OUT | Approval | [DRAFT] Reply LS on handling of UE-Slice-MBR(s) change related to Allowed NSSAI change | Nokia, Nokia Shanghai Bell | Rel-17 | Response to S2-2201260. r02 agreed. Revised to S2-2201280. | Belen (Ericsson) provides r01. Jinguo(ZTE) suggests to discuss the CR first in 1044. Alessio(Nokia)believes r0 is ok based on 1044 Belen (Ericsson) provides r02, objects to r00 Alessio(Nokia) can live with r02 Jinguo(ZTE) is also ok with r02 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.4 | S2-2201280 | LS OUT | Approval | Reply LS on handling of UE-Slice-MBR(s) change related to Allowed NSSAI change | SA WG2 | Rel-17 | Revision of S2-2200890r02. Approved | Approved | |
| 8.4 | S2-2201044 | CR | Approval | 23.503 CR0703 (Rel-17, 'F'): Clarification on UE-Slice-MBR | ZTE, Nokia, Nokia Shanghai Bell | Rel-17 | r06 agreed. Revised to S2-2201281. | Belen (Ericsson) provides r01 Jinguo(ZTE) provides r02 Belen (Ericsson) asks a question on r02 to Jinguo Haiyang (Huawei) comments, an update is needed Jinguo(ZTE) response to Belen and Haiyang Belen (Ericsson) replies to ZTE and ask for clarifications again Belen (Ericsson) provides r03 based on offline discussion triggered by ZTE alessio (Nokia) provides r05 Belen (Ericsson) prefers r04 but can accept r05 with some rewording. Belen (Ericsson) asks Alessio if he can explain his solution Jinguo(ZTE) provides r06 Belen (Ericsson) can accept r06 Alessio (nokia) can accept r06 and suggest that for this feature we do not support strange roaming set ups with strange mappings of slices... 1:1 is the assumption in this feature Belen (Ericsson) is okay with r06, but don't want to restrict the mapping of slices 1:1 but leave it as 1:n as in 23.501 alessio(Nokia) believes it is stated that for this feature it is recommended to keep 1:1 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.4 | S2-2201281 | CR | Approval | 23.503 CR0703R1 (Rel-17, 'B'): Clarification on UE-Slice-MBR | ZTE, Nokia, Nokia Shanghai Bell, Ericsson | Rel-17 | Revision of S2-2201044r06. Approved | Agreed | |
| 8.4 | - | - | - | Key issue #4 | - | - | Docs:=3 | - | |
| 8.4 | S2-2200180 | CR | Approval | 23.503 CR0691 (Rel-17, 'F'): Reporting utilized data rate in network slice to the AF | Ericsson | Rel-17 | Noted | Alessio(Nokia) asks to note this CR that is a category B and not working in multiple PCF case at least. also it replicates info available by other means. Belen (Ericsson) responds to Nokia. Ashok (Samsung) agrees with Alessio(Nokia) and propose to NOTE the CR Alessio(NOKIA) We simply do not think this CR is needed. this was not considered necessary to be exposed by PCF for KI#4 in TR so this is a late feature addition. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 8.4 | S2-2200348 | CR | Approval | 23.501 CR3493 (Rel-17, 'F'): Clarification on Network Slice status notifications for unsubscription | China Telecom | Rel-17 | Noted | George Foti (Ericsson) proposes to note the CR. Please see additional comments Heng(China Telecom) reply: Please see my reply in thread of S2-2200347 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 8.4 | S2-2201043 | CR | Approval | 23.502 CR3405 (Rel-17, 'F'): Correction on NSACF exposure | ZTE | Rel-17 | Postponed | George Foti (Ericsson) provides comments Jinguo(ZTE) response Fenqin(Huawei) provides r01 Jinguo(ZTE) provides r02 Jinguo(ZTE) provides r03 Fenqin(Huawei) provides r04 Srisakul(Thakolsri) comments. Fenqin(Huawei) comments. George (Ericsson) provides r08. I jumped by mistake to this number. But it used r04 as a base. We have to stop trying to let CT influence what we have in here.This repeated statement about immediate reporting is not needed here.It is sufficient to be captured in stage 3. Srisakul(NTT DOCOMO) comments. Fenqin(Huawei) comments and provides r09 George (Ericsson) provides comments. U can't have an EN. CT groups should send an LS if they have a question. ==== 8.X, 9.X, 10.X Revisions Deadline ==== George (Ericsson) provides comments. R09 has an Editors note which is NOT OK Tao(VC)we check r08 agreeable or not Fenqin(Huawei) only accept r09 or postpone this paper to next meeting Iskren (NEC) objects to r08. It is better to postpone this CR. Jinguo(ZTE) asks question and suggests to go with r08 or r09 and removes the change in step 4. Iskren (NEC) objects to all versions of this CR as there are multiple technically incorrect updates. Jinguo(ZTE) asks Iskren (NEC) to reconsider the objection Iskren (NEC) sustains objection to all revisions of this CR. Jinguo(ZTE) ask Iskren (NEC) to point which steps he has concern Iskren (NEC) responds ==== 8.X, 9.X, 10.X Final Deadline ==== | Postponed |
| 8.4 | - | - | - | Key issue #5 | - | - | Docs:=2 | - | |
| 8.4 | S2-2200684 | CR | Approval | 23.503 CR0663R2 (Rel-17, 'F'): Correction for PCF based monitoring of the data rate per network slice | Huawei, HiSilicon, Ericsson | Rel-17 | Revision of (Noted) S2-2108737 from S2#148E. Noted | Alessio(Nokia) objects to this paper Mirko (Huawei) responds. Alessio(Nokia) we are sorry wee cannot agree to this new feature. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 8.4 | S2-2201027 | CR | Approval | 23.503 CR0702 (Rel-17, 'F'): SM Policy association establishment rejected due to NW slice monitoring | Ericsson | Rel-17 | Approved | ==== 8.X, 9.X, 10.X Final Deadline ==== | Agreed |
| 8.4 | - | - | - | Key issue #6 | - | - | Docs:=2 | - | |
| 8.4 | S2-2200093 | CR | Approval | 23.502 CR3318 (Rel-17, 'F'): Clarification on indication of NSSRG support | InterDigital Inc., Nokia, Nokia Shanghai Bell, Telecom Italia | Rel-17 | r02 agreed. Revised to S2-2201282. | Peter (Ericsson) provides comments and r01 Mike (InterDigital) supports the change in r01 Alessio(Nokia) ok with R01 Jinguo(ZTE) provides r02 with small update Alessio(Nokia) ok with R02 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.4 | S2-2201282 | CR | Approval | 23.502 CR3318R1 (Rel-17, 'F'): Clarification on indication of NSSRG support | InterDigital Inc., Nokia, Nokia Shanghai Bell, Telecom Italia, Ericsson | Rel-17 | Revision of S2-2200093r02. Approved | Agreed | |
| 8.4 | - | - | - | Key issue#7 | - | - | Docs:=6 | - | |
| 8.4 | S2-2200051 | LS In | Action | LS from CT WG3: LS on Clarification on the change of Target NSSAI | CT WG3 (C3-216445) | Rel-17 | Response drafted in S2-2200255. Final response in S2-2201856 | ==== 8.X, 9.X, 10.X Final Deadline ==== | Replied to |
| 8.4 | S2-2200255 | LS OUT | Approval | [DRAFT] Reply LS on clarification on the change of Target NSSAI | Huawei, HiSilicon | Rel-17 | Response to S2-2200051. Await CR in S2-2200256. CC#4: Postponed to CC#5. CC#5: r08 agreed. Revised to S2-2201856. | Peter (Ericsson) provides comments and r01 alessio(Nokia) provides comments and r02 Peter Hedman (Ericsson) provides replies and r02 does not refloect what is possible with current SA2 specs alessio(Nokia) comments Jinguo(ZTE) provides r03 alessio(NOKIA) provides r04 Peter Hedman (Ericsson) provides r05 Alessio(Nokia) cannot agree r05 ==== 8.X, 9.X, 10.X Revisions Deadline ==== Peter Hedman (Ericsson) objects to r04, r03, r02 and r00 supports r05 and r01 Tao(CMCC) let's check r01 agreeable or not Jinguo(ZTE) suggest to keep it open alessio(Nokia) complains Ericsson wants to write LSs not based on text in the specs. there is nowhere in the specs that the target NSSAI is stored in the AMF and we do not change the specifications to add features after freeze just to please some people. moreover r04 responds to the LS while r05 seems to be some discussion not related to the LS that ericsson wants to write in this Ls to then use it for other purposes. This is not good behaviour. ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.4 | S2-2201856 | LS OUT | Approval | Reply LS on Clarification on the change of Target NSSAI | SA WG2 | Rel-17 | Revision of S2-2200255r08. Approved | Approved | |
| 8.4 | S2-2200256 | CR | Approval | 23.501 CR3477 (Rel-17, 'F'): Clarification on the Target NSSAI | Huawei, HiSilicon | Rel-17 | CC#4: Noted | Peter (Ericsson) provides comments and r01 Jinguo(ZTE) asks question to Peter(Ericsson) Genadi (Lenovo) provides r02 and comments. Peter Hedman (Ericsson) provides comments Haiyang (Huawei) asks questions to Peter(Ericsson) and Genadi (Lenovo) Peter Hedman (Ericsson) provides r03 Jinguo(ZTE) ask question for clarification Peter Hedman (Ericsson) provides reply Haiyang (Huawei) responds to Peter Hedman (Ericsson) Ashok (Samsung) comments Alessio(Nokia) believes this CR is not needed. we request to note it. Yunjing (CATT) asks a question for clarification. Peter Hedman (Ericsson) provides replies alessio(Nokia) objects to any revision of this non FASMO CR. Ashok (Samsung) responds to Peter Hedman (Ericsson) Peter Hedman (Ericsson) provides r04 Dieter Gludovacz (Deutsche Telekom) comments. Haiyang (Huawei) provides questions to Ashok (Samsung) Ashok (Samsung) responds to Haiyang (Huawei) Alessio(Nokia) objects to r04 Peter Hedman (Ericsson) provides r05 Jinguo(ZTE) asks clarification Iskren (NEC) provides comments alessio(Nokia) comments that this is a misleading use case and we request to postpone this CR till we better understand the issue and whether it is FASMO. for now we think it has implication that need further study Iskren (NEC) supports this CR and provides r06 where the text from the Note is move to the normative text. Ouerdia (Orange) supports this CR version r06. Dieter (Deutsche Telekom) also supports r06.. Alessio(Nokia) objects to any revision of this CR as there is no FASMO and it may actually introduce FASMO. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Peter Hedman (Ericsson) supports approving r06, asks for CR to be taken at CC#4 Nokia provides additional information on objection to approval of this CR Alessio(Nokia) believes the feature as is is very clear to reply to CT3. any changes like proposed is category B/C and needs consensus in a frozen release. we do not do category B/C in frozen release unless there is consensus. this is not about FASMO, it is about the concept of a frozen release. and this category B/C would introduce the FASMO of some ongoing session in allowed NSSAI being dropped. ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 8.4 | S2-2200458 | CR | Approval | 23.501 CR3508 (Rel-17, 'F'): Clarification on the Registration area when Target NSSAI is indicated | InterDigital Inc., Nokia, Nokia Shanghai Bell | Rel-17 | r01 agreed. Revised to S2-2201283. | Peter (Ericsson) provides comments and r01 Mike (InterDigital) is ok with r01 Haiyang (Huawei) provides r02 Nokia objects to r02 as it does not solve the issue we have by introducing a 'may' Haiyang (Huawei) provides r03 to change the may back to shall alessio(Nokia) (can live with r03. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Peter Hedman (Ericsson) objects to r02 and r03 and proposes to approve r01 Haiyang (Huawei) clarifies to Peter Hedman (Ericsson) alessio(Nokia) for sake of progress we can go with r01 at this meeting and add the other clause aspects at the next meeting if this is too late to discuss. but we can also live with r03. Peter Hedman (Ericsson) provides reply and again proposes to go with r01 Mike (InterDigital) is fine to go with r01 ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.4 | S2-2201283 | CR | Approval | 23.501 CR3508R1 (Rel-17, 'F'): Clarification on the Registration area when Target NSSAI is indicated | InterDigital Inc., Nokia, Nokia Shanghai Bell, Ericsson, Huawei, HiSilicon | Rel-17 | Revision of S2-2200458r01. Approved | Agreed | |
| 8.5 | - | - | - | Enhanced support of Industrial IoT - TSC/URLLC enhancements (IIoT) | - | - | Docs:=43 | - | |
| 8.5 | S2-2200011 | LS In | Action | Reply LS on more efficient PMIC/UMIC signalling exchange for time synchronization | CT WG1 (C1-216069) | Rel-17 | Revision of Postponed S2-2108276 from S2#148E. Noted | Zhendong (ZTE): proposes to Note this LS response Sang-Jun (Samsung) also proposes to Note this LS response ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 8.5 | S2-2200041 | LS In | Action | LS from ITU-T SG15: LS/r on Time Synchronization support in 3GPP specification | ITU-T SG15 (SG15-LS348) | Postponed | ==== 8.X, 9.X, 10.X Final Deadline ==== | Postponed | |
| 8.5 | S2-2200268 | CR | Approval | 23.501 CR3480 (Rel-17, 'F'): Correction on 5G access stratum time distribution | Huawei, HiSilicon | Rel-17 | CC#4: r01 + changes agreed. Revised to S2-2201837. | Shabnam (Ericsson) objects to the proposed change as this is not FASMO, the original focus was as specified without these changes. Internal system clock functions as understood before and independent of the intro of the access stratum time distribution control. Devaki (Nokia) comments that there is no need for radical changes as proposed, sees no need for the CR. Sebastian (Qualcomm) objects to the CR Haiyang (Huawei) clarifies. Devaki (Nokia) comments. Haiyang (Huawei) provides r01, but prefer r00. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Shabnam (Ericsson) provides late revision in Drafts folder to undo r01 change and replace with changes in clause 5.27.1.9, to take it to CC#4 ==== 8.X, 9.X, 10.X Final Deadline ==== Haiyang (Huawei) is OK with the draft provided by Shabnam (Ericsson). Devaki (Nokia) provides r03 in CC#4 folder. Devaki (Nokia) provides updates on top of r02 in Draft folder as r03 in CC#1 folder. | Revised |
| 8.5 | S2-2201837 | CR | Approval | 23.501 CR3480R1 (Rel-17, 'F'): Correction on 5G access stratum time distribution | Huawei, HiSilicon, Ericsson, Nokia, Nokia Shanghai Bell | Rel-17 | Revision of S2-2200268r01 + changes. Approved | Agreed | |
| 8.5 | S2-2200269 | CR | Approval | 23.502 CR3333 (Rel-17, 'F'): Correction on 5G access stratum time distribution | Huawei, HiSilicon | Rel-17 | r03 agreed. Revised to S2-2201723. | Shabnam (Ericsson) there are issues to correct for this CR and not really same as the 23.501 CR with same title, see comments. Devaki (Nokia) agrees with Ericsson that this CR is unrelated to 0268 although it uses the same title. Provides r01. Zhendong (ZTE): provides r02 Haiyang (Huawei) clarifies and provides r03. Sebastian (Qualcomm) asks a question Haiyang (Huawei) clarifies. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.5 | S2-2201723 | CR | Approval | 23.502 CR3333R1 (Rel-17, 'F'): Correction on 5G access stratum time distribution | Huawei, HiSilicon | Rel-17 | Revision of S2-2200269r03. Approved | Agreed | |
| 8.5 | S2-2200298 | CR | Approval | 23.502 CR3338 (Rel-17, 'F'): Alignment of the 5G AS time distribution management procedure | Ericsson | Rel-17 | r11 agreed. Revised to S2-2201724, merging S2-2200158 | Yuan Tao (CATT) comments. György (Ericsson) responds. Jari (NTT DOCOMO) comments. Jari (NTT DOCOMO) responds. Zhendong (ZTE): provides comments Qianghua (Huawei) comments, prefers the proposal in this CR György (Ericsson) comments Jari (NTT DOCOMO) responds to György Qianghua (Huawei) provides r04 Devaki (Nokia) provides r03. Zhendong (ZTE): provides response Devaki (Nokia) provides r02 (merging the call flow updates needed from 1046) and cosigns. Jari (NTT DOCOMO) responds to Zhendong György (Ericsson) provides r06 Jari (NTT DOCOMO) provides r05 György (Ericsson) provides r07. Zhendong (ZTE): provides r08 Jari (NTT DOCOMO) provides r09, partial merge from S2-2200980 Jari (NTT DOCOMO) provides r10, partial merge from S2-2200638 György (Ericsson) provides r11 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.5 | S2-2201724 | CR | Approval | 23.502 CR3338R1 (Rel-17, 'F'): Alignment of the 5G AS time distribution management procedure | Ericsson, Nokia, Nokia Shanghai Bell, Huawei, HiSilicon, ZTE, NTT DOCOMO | Rel-17 | Revision of S2-2200298r11, merging S2-2200158. Approved | Agreed | |
| 8.5 | S2-2200299 | CR | Approval | 23.501 CR3485 (Rel-17, 'F'): Alignment of the 5G AS time distribution management procedure | Ericsson | Rel-17 | Noted | Jari (NTT DOCOMO) comments. György (Ericsson) comments. Qianghua (Huawei) provides comments György (Ericsson) provides r01. Devaki (Nokia) provides r02. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Jari (NTT DOCOMO) objects the original and all revisions ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 8.5 | S2-2200300 | CR | Approval | 23.502 CR3339 (Rel-17, 'F'): Clarifying the 5G AS time distribution parameter delivery to NG-RAN | Ericsson | Rel-17 | Approved | ==== 8.X, 9.X, 10.X Final Deadline ==== | Agreed |
| 8.5 | S2-2200301 | CR | Approval | 23.502 CR3340 (Rel-17, 'F'): Correcting the naming and/or description of some BSF service operations | Ericsson | Rel-17 | Approved | Zhendong (ZTE): ask for clarification Shabnam (Ericsson) what you ask is existing in the spec, this CR just corrects/aligns, provides additional comments. Zhendong (ZTE): clarify this CR depend on the conclusion for CR 2200298 Shabnam (Ericsson) please note that the current specification (see existing table) before this CR already has TSCTSF operation using BSF. Zhendong (ZTE): withdraw the comments ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Agreed |
| 8.5 | S2-2200635 | CR | Approval | 23.501 CR3523 (Rel-17, 'F'): Multiple NW-TTs associated with a single UPF | Huawei, HiSilicon | Rel-17 | r03 agreed. Revised to S2-2201725. | Devaki (Nokia) comments. Qianghua (Huawei) replies Zhendong (ZTE): provides r01 Devaki (Nokia) believes r01 goes in the right direction. Qianghua (Huawei) provides r02 Devaki (Nokia) proposes to note this CR as the intention is anyhow covered in 636 (23.502 CR). Devaki (Nokia) replies to Qianghua Qianghua (Huawei) questions Qianghua (Huawei) replies to Devaki Devaki (Nokia) replies. Qianghua (Huawei) replies to Devaki and provide r03 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.5 | S2-2201725 | CR | Approval | 23.501 CR3523R1 (Rel-17, 'F'): Multiple NW-TTs associated with a single UPF | Huawei, HiSilicon | Rel-17 | Revision of S2-2200635r03. Approved | Agreed | |
| 8.5 | S2-2200636 | CR | Approval | 23.502 CR3369 (Rel-17, 'F'): Multiple NW-TTs associated with a single UPF | Huawei, HiSilicon | Rel-17 | r01 agreed. Revised to S2-2201726. | Zhendong (ZTE): provides comments Qianghua (Huawei) comments Zhendong (ZTE): provides response Qianghua (Huawei) provides r01 Zhendong (ZTE): is fine with this wording ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.5 | S2-2201726 | CR | Approval | 23.502 CR3369R1 (Rel-17, 'F'): Multiple NW-TTs associated with a single UPF | Huawei, HiSilicon | Rel-17 | Revision of S2-2200636r01. Approved | Agreed | |
| 8.5 | S2-2200637 | CR | Approval | 23.501 CR3524 (Rel-17, 'F'): Clarifications and clean-ups for TSC | Huawei, HiSilicon | Rel-17 | r02 agreed. Revised to S2-2201727, merging S2-2200767 | György (Ericsson) comments. Sebastian (Qualcomm) provides r01 Devaki (Nokia) comments that the changes remaining in r01 are purely editorial - not really FASMO. Furthermore, 638 (even though it uses the same title) is completely unrelated to 637. Qianghua (Huawei) replies GYörgy (Ericsson) responds Sebastian (Qualcomm) comments Zhendong (ZTE): provides comments Devaki (Nokia) comments. Qianghua (Huawei) provides r02 Devaki (Nokia) comments that the revision should remove the sections that are not modified by the CR (otherwise it appears deleted which is wrong). ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.5 | S2-2201727 | CR | Approval | 23.501 CR3524R1 (Rel-17, 'F'): Clarifications and clean-ups for TSC | Huawei, HiSilicon | Rel-17 | Revision of S2-2200637r02, merging S2-2200767. Approved | Agreed | |
| 8.5 | S2-2200638 | CR | Approval | 23.502 CR3370 (Rel-17, 'F'): Clarifications and clean-ups for TSC | Huawei, HiSilicon | Rel-17 | r05 agreed. Revised to S2-2201728. | György (Ericsson) comments. Devaki (Nokia) comments. Qianghua (Huawei) replies and provides r01 György (Ericsson) responds Qianghua (Huawei) provides r02 Jari (NTT DOCOMO) provides r03 Qianghua (Huawei) provides r04, fixing cover page Jari (NTT DOCOMO) provides r05 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.5 | S2-2201728 | CR | Approval | 23.502 CR3370R1 (Rel-17, 'F'): Clarifications and clean-ups for TSC | Huawei, HiSilicon | Rel-17 | Revision of S2-2200638r05. Approved | Agreed | |
| 8.5 | S2-2200685 | CR | Approval | 23.503 CR0686R1 (Rel-17, 'F'): QoS parameter handling for TSC | Huawei, HiSilicon | Rel-17 | Revision of (Merged) S2-2108740 from S2#148E. Merged into S2-2201734 | Devaki (Nokia) provides r01. György (Ericsson) responds. Mirko (Huawei) responds and provides r02. Devaki (Nokia) proposes to merge this CR with 1047, also responds to Mirko's comments. I will provide this merged version as a revision of 1047. Devaki (Nokia) comments that this should be merged with 1048 (sorry 1047 is the 23.502 CR). Mirko (Huawei) comments and agrees to merge with 1048. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 8.5 | S2-2200686 | CR | Approval | 23.501 CR3528 (Rel-17, 'F'): 23.501 PMIC exchange with UE(s) in idle mode | Samsung | Rel-17 | Noted | Devaki (Nokia) proposes to note this CR, one could do this in an implementation anyhow. Sebastian (Qualcomm) objects to the CR Chunshan (CATT) supports this CR, it uses the ATC which is defined from R15. Shabnam (Ericsson) objects to this CR, we have discussed this many times now, there is no need for this change. Sang-Jun (Samsung) provides response. Shabnam (Ericsson) as being discussed under agenda 4.1, ATC procedure does not work nor has it been specified in stage 3 and it does not work for this case. Sebastian (Qualcomm) confirms objection and comments that the ATC procedure as-is cannot be used for PMIC Devaki (Nokia) also confirms objection of this CR. (if companies want to use ATC, it could be used in an implementation specific manner but we don't believe it needs to be stated in the spec). ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 8.5 | S2-2200687 | CR | Approval | 23.502 CR3374 (Rel-17, 'F'): 23.502 PMIC exchange with UE(s) in idle mode | Samsung | Rel-17 | Noted | Devaki (Nokia) proposes to note this CR, one could do this in an implementation anyhow. Sebastian (Qualcomm) objects to the CR Chunshan (CATT) supports this CR, it uses the ATC which is defined from R15. Shabnam (Ericsson) objects to the CR, no reason for this update as discussed in previous meetings. Sang-Jun (Samsung) provides response. Shabnam (Ericsson) sustains objection and reiterates what is written does not work and nor is it needed. Devaki (Nokia) also confirms objection of this CR. (if companies want to use ATC, it could be used in an implementation specific manner but we don't believe it needs to be stated in the spec). ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 8.5 | S2-2200688 | CR | Approval | 23.503 CR0698 (Rel-17, 'F'): Clafication on Application Function | CATT, Huawei | Rel-17 | r01 agreed. Revised to S2-2201729. | Sang-Jun (Samsung) provides r01. Zhendong (ZTE): provides r02 Devaki (Nokia) supports r02. Yuan Tao (CATT) responds. Sang-Jun (Samsung) also supports r02. Mirko (Huawei) responds and suggests to move forward with r01. Shabnam (Ericsson) also prefers r02, since the text removed from the spec in r01 is not related to IIoT I believe but rather for general AF interaction? Yuan Tao (CATT) replies to Shabnam (Ericsson), and prefers r01. Mirko (Huawei) responds and clarifies that there is nothing removed from the spec in r00/r01. Shabnam (Ericsson) sorry Mirko you are right, I missed the top part completely. I now see that and agree r01 is better as provides generic description of AF role which I was also thinking would be needed. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.5 | S2-2201729 | CR | Approval | 23.503 CR0698R1 (Rel-17, 'F'): Clarification on Application Function | CATT, Huawei | Rel-17 | Revision of S2-2200688r01. Approved | Agreed | |
| 8.5 | S2-2200775 | CR | Approval | 23.501 CR3534 (Rel-17, 'F'): Time Synchronization of the 5GS as IEEE 1588 Boundary Clock | CATT | Rel-17 | r02 agreed. Revised to S2-2201730. | Sang-Jun (Samsung) provides r01. Jari (NTT DOCOMO) provides r02. Chunshan (CATT) provides r03. Sang-Jun (Samsung) thinks r03 is fine and r02 is also fine. Shabnam (Ericsson) prefers r02 over r03. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.5 | S2-2201730 | CR | Approval | 23.501 CR3534R1 (Rel-17, 'F'): Time Synchronization of the 5GS as IEEE 1588 Boundary Clock | CATT | Rel-17 | Revision of S2-2200775r02. Approved | Agreed | |
| 8.5 | S2-2200776 | CR | Approval | 23.501 CR3535 (Rel-17, 'F'): Correction for the end-to-end Transparent Clock | CATT | Rel-17 | r02 agreed. Revised to S2-2201731. | Shabnam (Ericsson) provides r01, removing misleading new note. Devaki (Nokia) provides r02. Chunshan (CATT) cannot find new change in r02. Devaki (Nokia) replies to Chunshan (CATT). Chunshan (CATT) points out that r01 is right and r02 is wrong. Devaki (Nokia) cannot agree to r01 or r00. Shabnam (Ericsson) explains that r01 does not change the concept due to text preceding the changed part, comments. Chunshan (CATT) can accept r02 as a compromise and bring paper in next meeting. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.5 | S2-2201731 | CR | Approval | 23.501 CR3535R1 (Rel-17, 'F'): Correction for the end-to-end Transparent Clock | CATT | Rel-17 | Revision of S2-2200776r02. Approved | Agreed | |
| 8.5 | S2-2200978 | CR | Approval | 23.502 CR3394 (Rel-17, 'F'): Clean up of the AF-session with required QoS procedures. | NTT DOCOMO | Rel-17 | Merged into S2-2201734 | Qianghua (Huawei) provides comments Jari (NTT DOCOMO) responds to Qianghua Devaki (Nokia) proposes to consider this paper as merged with 1047 (as agreed with Jari, 1047 cosigned by NTT Docomo). ==== 8.X, 9.X, 10.X Revisions Deadline ==== Jari (NTT DOCOMO) agrees to merge with 1047 ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 8.5 | S2-2200980 | CR | Approval | 23.502 CR3396 (Rel-17, 'F'): Clean up of the time synchronization procedures. | NTT DOCOMO | Rel-17 | r04 agreed. Revised to S2-2201732. | Sebastian (Qualcomm) asks a question Chunshan (CATT) concerns the changes for the TSCTF/NEF to discover the DNN/S-NSAAI from the BSF. Jari (NTT DOCOMO) responds to Sebastian Sebastian (Qualcomm) replies to Jari Zhendong (ZTE): provides comments Devaki (Nokia) comments. Sang-Jun (Samsung) asks for clarification whether exposure of PTP port states are for BMCA report or initialization? Jari (NTT DOCOMO) responds to Sebastian and Zhendong Qianghua (Huawei) provides comments Jari (NTT DOCOMO) responds to Devaki Jari (NTT DOCOMO) provides r01 Jari (NTT DOCOMO) provides r02, partial merge with S2-2200292r09 Qianghua (Huawei) provides r03 Jari (NTT DOCOMO) responds to Qianghua Qianghua (Huawei) replies Qianghua (Huawei) replies to Jari Jari (NTT DOCOMO) provides r04 Jari (NTT DOCOMO) provides r05 Jari (NTT DOCOMO) responds to Zhendong ==== 8.X, 9.X, 10.X Revisions Deadline ==== Zhendong (ZTE): provides response Qianghua (Huawei) suggests to go with r04, objects r05 Jari (NTT DOCOMO) prefers r05 Sang-Jun (Samsung) also prefers r05 Zhendong (ZTE): accept r04, Sang-Jun (Samsung) can accept r04. ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.5 | S2-2201732 | CR | Approval | 23.502 CR3396R1 (Rel-17, 'F'): Clean up of the time synchronization procedures. | NTT DOCOMO | Rel-17 | Revision of S2-2200980r04. Approved | Agreed | |
| 8.5 | S2-2201046 | CR | Approval | 23.502 CR3406 (Rel-17, 'F'): Update to time synchronization procedures | Nokia, Nokia Shanghai Bell | Rel-17 | Merged into S2-2201362 and S2-2201131 | Jari (NTT DOCOMO) comments Jari (NTT DOCOMO) proposes to merge with S2-2200298 Devaki (Nokia) requests to ignore the last comment, r03 was meant to be posted for 298 thread. Sorry for the error. Zhendong (ZTE): provides comments Devaki (Nokia) provides r03. Devaki (Nokia) comments that 298 does not cover all the changes proposed in 1046. It can only be partly merged, provides r01 removing the overlapping parts. Qianghua (Huawei) asks this to be merged into 0638 Jari (NTT DOCOMO) proposes to note the CR Devaki (Nokia) comments. Jari (NTT DOCOMO) responds to Devaki Devaki (Nokia) replies to Jari. Devaki (Nokia) provides r02. Jari (NTT DOCOMO) proposes merge with S2-2201131 ==== 8.X, 9.X, 10.X Revisions Deadline ==== Qianghua (Huawei) is fine with r02. But also agrees that the change is covered in 1131r01 and can be merged with 1131. Jari (NTT DOCOMO) proposes to NOTE or merge with 1131 Devaki (Nokia) comments that main part of the CR was actually merged with 298 (not 1131). Remaining change to first section merged with 1131. In any case, it can be marked as merged with 298 and 1141 It can be marked as merged with 298 and 1131. ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 8.5 | S2-2201047 | CR | Approval | 23.502 CR3407 (Rel-17, 'F'): Update to AF session with required QoS procedures | Nokia, Nokia Shanghai Bell, Ericsson | Rel-17 | r03 agreed. Revised to S2-2201733, merging S2-2200257 | Devaki (Nokia) provides r01 - merging 978 with this paper as they are updating the same call flow. Qianghua (Huawei) provides comments for r01 Jari (NTT DOCOMO) responds to Qianghua Qianghua (Huawei) replies Devaki (Nokia) replies to Qianghua. Qianghua (Huawei) provides r02 Devaki (Nokia) comments. György (Ericsson) provides r03 ==== 8.X, 9.X, 10.X Revisions Deadline ==== Qianghua (Huawei) can live with r03 ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.5 | S2-2201733 | CR | Approval | 23.502 CR3407R1 (Rel-17, 'F'): Update to AF session with required QoS procedures | Nokia, Nokia Shanghai Bell, Ericsson, NTT DOCOMO | Rel-17 | Revision of S2-2201047r03, merging S2-2200257. Approved | Agreed | |
| 8.5 | S2-2201048 | CR | Approval | 23.503 CR0704 (Rel-17, 'F'): Fixes for AF session with required QoS update procedure | Nokia, Nokia Shanghai Bell, Ericsson | Rel-17 | r07 agreed. Revised to S2-2201734, merging S2-2200978 and S2-2200685 | Devaki (Nokia) provides r01, merges 685 with 1048. Mirko (Huawei) provides r02. Devaki (Nokia) comments. Mirko (Huawei) responds and provides r04. György (Ericsson) provides r05. Mirko (Huawei) responds. Devaki (Nokia) replies and provides r06 as a compromise. Mirko (Huawei) responds and provides r07. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.5 | S2-2201734 | CR | Approval | 23.503 CR0704R1 (Rel-17, 'F'): Fixes for AF session with required QoS update procedure | Nokia, Nokia Shanghai Bell, Ericsson, Huawei | Rel-17 | Revision of S2-2201048r07, merging S2-2200978 and S2-2200685. Approved | Agreed | |
| 8.5 | S2-2201049 | CR | Approval | 23.503 CR0705 (Rel-17, 'F'): Updates for TSCTSF functionality within 23.503 specification | Nokia, Nokia Shanghai Bell | Rel-17 | r02 agreed. Revised to S2-2201735. | Shabnam (Ericsson) provides r01, removing UDR. Devaki (Nokia) fine with r01 (although keeping UDR or removing UDR perhaps depends on other discussions as well) Mirko (Huawei) provides r02. Devaki (Nokia) comments. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.5 | S2-2201735 | CR | Approval | 23.503 CR0705R1 (Rel-17, 'F'): Updates for TSCTSF functionality within 23.503 specification | Nokia, Nokia Shanghai Bell | Rel-17 | Revision of S2-2201049r02. Approved | Agreed | |
| 8.5 | S2-2201128 | CR | Approval | 23.502 CR3413 (Rel-17, 'F'): Clarification on the survival time and Configuration ID. | ZTE | Rel-17 | Merged into S2-2201556 | Shabnam (Ericsson) NOTE the CR since first change is covered in another CR and other clauses have no changes that are change marked. Devaki (Nokia) comments that the reason for change is not aligned with the actual changes, cover sheet needs to be fixed. Zhendong (ZTE): provides response Devaki (Nokia) proposes to consider this CR merged with 648 (as also agreed by ZTE in an earlier email). Qianghua (Huawei) corrects that this should be considered merging with 0638 (not 648) ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 8.5 | S2-2201129 | CR | Approval | 23.501 CR3564 (Rel-17, 'F'): Clarification on how the TSFTSF assign the NW-TT port to PPT instance | ZTE | Rel-17 | Noted | Devaki (Nokia) objects to the CR. Devaki (Nokia) comments. Zhendong (ZTE): provides response Qianghua (Huawei) provides comments ==== 8.X, 9.X, 10.X Revisions Deadline ==== Devaki (Nokia) continues to have concerns with the CR, ok to discuss if there is any problem offline and consider for next meeting. ==== 8.X, 9.X, 10.X Final Deadline ==== Devaki (Nokia) prefers per NW-TT PTP instance assignment (your option 2). | Noted |
| 8.5 | S2-2201130 | CR | Approval | 23.501 CR3565 (Rel-17, 'F'): Clarification on the TSCTSF discovery | ZTE | Rel-17 | Merged into S2-2201699 | Qianghua (Huawei) proposes to mark this merged into S2-2200637 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 8.5 | S2-2201131 | CR | Approval | 23.502 CR3414 (Rel-17, 'F'): Clarification on the TSCTSF discovery | ZTE | Rel-17 | r02 agreed. Revised to S2-2201736, merging S2-2200579 and S2-2201046 | Jari (NTT DOCOMO) comments Devaki (Nokia) comments that the changes to the figures in this CR and 1046 are complimentary. Do not see a need for the merge. Jari (NTT DOCOMO) comments that both CRs replace the Figure 4.15.9.2-1 Devaki (Nokia) comments that both the CRs are modifying different steps of the figure. Jari (NTT DOCOMO) comments that both the CRs are implementing the same change for Step 4 in the figure, except this CR has a typo in the message name. Jari (NTT DOCOMO) provides r01 Zhendong (ZTE): provides r02 Qianghua (Huawei) thinks that S2-2201046 can be merged here ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.5 | S2-2201736 | CR | Approval | 23.502 CR3414R1 (Rel-17, 'F'): Clarification on the TSCTSF discovery | ZTE | Rel-17 | Revision of S2-2201131r02, merging S2-2200579 and S2-2201046. Approved | Agreed | |
| 8.6 | - | - | - | Access Traffic Steering, Switch and Splitting support in the 5G system architecture Phase 2 (ATSSS_Ph2) | - | - | Docs:=5 | - | |
| 8.6 | S2-2200045 | LS In | Action | LS on UE assistance data provisioning procedure | CT WG1 (C1-217218) | Rel-17 | Noted | ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 8.6 | S2-2200437 | CR | Approval | 23.501 CR3501 (Rel-17, 'F'): MA PDU sessions with connectivity over E-UTRAN/EPC and non-3GPP access to 5GC | Ericsson | Rel-17 | r02 agreed. Revised to S2-2201538. | Myungjune (LGE) comments and provides r01. Stefan (Ericsson) is OK with r01 Apostolis (Lenovo) provides r02 Stefan (Ericsson) is OK with r02 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.6 | S2-2201538 | CR | Approval | 23.501 CR3501R1 (Rel-17, 'F'): MA PDU sessions with connectivity over E-UTRAN/EPC and non-3GPP access to 5GC | Ericsson, Deutsche Telekom | Rel-17 | Revision of S2-2200437r02. Approved | Agreed | |
| 8.6 | S2-2200794 | CR | Approval | 23.502 CR3378 (Rel-17, 'F'): User-plane restriction due to network slice admission control | Lenovo, Motorola Mobility | Rel-17 | Noted | Jinguo(ZTE) propose to use 1101 as basis for discussion Rainer (Nokia) asks for clarification. Apostolis (Lenovo) responds to Rainer's (Nokia) question. Apostolis (Lenovo) accepts to use the email thread of 1101 for discussing this issue, as proposed by Jinguo (ZTE). Rainer (Nokia) replies. Apostolis (Lenovo) provides further comments. Marco (huawei) ask clarification. Myungjune (LGE) comments Dario (Qualcomm) comments and provides r01 Apostolis (Lenovo) responds to Myungjune's (LGE) comments Rainer (Nokia) is ok with r01. Marco (Huawei) proposes to note this paper and to discuss and solve in S2-2201101 under NS AI, since more appropriate to address as a whole. Myungjune (Lenovo) replies to Apostolis (Lenovo) Apostolis (Lenovo) responds to Dario's (Qualcomm) comments and proposes again to use the email thread for 1101 for discussing this topic. Stefan (Ericsson) yes please use the 1101 thread Krisztian (Apple) provides r02. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Dario (Qualcomm) is OK with r02 Jinguo(ZTE) proposes to NOTE this CR Myungjune (LGE) proposes to NOTE this CR Rainer (Nokia) agrees to note 794. Stefan (Ericsson) also support to NOTE ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 8.6 | S2-2200854 | CR | Approval | 23.501 CR3541 (Rel-17, 'F'): Clarification on PMF reply message | Huawei, HiSilicon | Rel-17 | Noted | Stefan (Ericsson) asks a question for clarification Rainer (Nokia) provides r01. Myungjune (LGE) supports r01. Dario (Qualcomm) express concerns and asks questions for clarification. Susan (Huawei) replies to Stefan, Rainer, Myungjune. Susan (Huawei) replies to Dario. Myungjune (LGE) replies to Susan (Huawei). Susan (Huawei) replies to Myungjune. Rainer (Nokia) comments. Stefan (Ericsson) provides additional comments Dario (Qualcomm) thinks this CR is not necessary Apostolis (Lenovo) is fine with r01 and provides further comments. Dario (Qualcomm) replies Apostolis (Lenovo) is also fine to note this CR. Stefan (Ericsson) also OK to note the CR Rainer (Nokia) ok to note the CR. Myungjune (LGE) also OK to note the CR Susan (Huawei) replies to Rainer (Nokia) and is ok with r01. Dario (Qualcomm) replies to Susan Susan (Huawei) replies to Dario (Qualcomm). Stefan (Ericsson) replies to Susan Susan (Huawei) is ok to note this CR. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 8.7 | - | - | - | Support of Aerial Systems Connectivity, Identification, and Tracking (ID_UAS) | - | - | Docs:=29 | - | |
| 8.7 | S2-2200056 | LS In | Information | LS from CT WG4: Reply LS on GTP-C cause value used for UAS services | CT WG4 (C4-216390) | Rel-17 | Noted | ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 8.7 | S2-2200062 | LS In | Action | Reply LS on 3GPP SA1 clarifications on problematic UAV | SA WG1 (S1-214238) | Rel-17 | Postponed | ==== 8.X, 9.X, 10.X Final Deadline ==== | Postponed |
| 8.7 | S2-2201259 | LS In | Action | LS on Issues on ID_UAS | CT WG3 (C3-220363) | Rel-17 | CC#1: Response drafted in S2-2201268. Final response in S2-2201284 | ==== 8.X, 9.X, 10.X Final Deadline ==== | Replied to |
| 8.7 | S2-2201268 | LS OUT | Approval | [DRAFT] Reply LS on Issues on ID_UAS | SA WG2 | Rel-17 | Created at CC#1. Response to S2-2201259.. r04 agreed. Revised to S2-2201284. | Guanglei (Huawei) provides r01 Jaewoo (LGE) provides comments. Guanglei (Huawei) replies Pallab (Nokia) provides comments. Pallab (Nokia) provides further comments. Guanglei (Huawei) replies to Pallab (Nokia) and provides r02 Pallab (Nokia) responds to Guanglei (Huawei) and comments on r02 . Shabnam (Ericsson) comments on r02 and asks clarification. Guanglei (Huawei) responses to Shabnam (Ericsson) Guanglei (Huawei) responses to Pallab (Nokia) and provides r03 Guanglei (Huawei) provides r04 to reflect both the opinion from Nokia and E/// ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.7 | S2-2201284 | LS OUT | Approval | LS Reply on Issues on ID_UAS | SA WG2 | Rel-17 | Revision of S2-2201268r04. Approved | Approved | |
| 8.7 | S2-2200556 | CR | Approval | 23.256 CR0049 (Rel-17, 'F'): UUAA context management | Samsung | Rel-17 | r03 agreed. Revised to S2-2201285. | Shabnam (Ericsson) provides r01 cleaning up the wording and removing stage 3 level details. Stefano (Qualcomm) provides R02 and questions. Jaewoo (LGE) provides comment. Ashok (Samsung) responds to Jaewoo (LGE) Pallab (Nokia) provides r03. Stefano (Qualcomm) replies to Samsung. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Ashok (Samsung) OK with r03. ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.7 | S2-2201285 | CR | Approval | 23.256 CR0049R1 (Rel-17, 'F'): UUAA context management | Samsung | Rel-17 | Revision of S2-2200556r03. Approved | Agreed | |
| 8.7 | S2-2200557 | CR | Approval | 23.256 CR0050 (Rel-17, 'F'): UUAA-SM in case of multiple PDU session for USS operation | Samsung | Rel-17 | Postponed | Shabnam (Ericsson) objects to the CR as we do not see any reason to specify such condition or restriction. Jaewoo (LGE) asks for clarification. Guanglei (Huawei) also has concern on this CR Ashok (Samsung) replies to Shabnam (Ericsson) , Guanglei (Huawei), Jaewoo (LGE) asks for clarification. Pallab (Nokia) asks for clarification and has same concerns as raised by others. Proposes to NOTE the CR. Ashok (Samsung) clarifies Pallab (Nokia) Shabnam (Ericsson) responds and again repeats that optimisation is not FASMO and as such do not see the need for the CR, comments. Guanglei (Huawei) provides comments and share the view form E/// about multiple PDU sessions Ashok (Samsung) responds to Shabnam (Ericsson) & Guanglei (Huawei) Shabnam (Ericsson) responds, no change in position regarding the view on the validity of this CR. Stefano (Qualcomm) also believes this CR should be noted. Ashok (Samsung) thanks Shabnam (Ericsson) and Stefano (Qualcomm) for good comments. Pallab (Nokia) responds to Ashok (Samsung). Maintains position to NOTE the CR Jaewoo (LGE) provides comments. Ashok (Samsung) responds to Pallab (Nokia) Stefano (Qualcomm) responds and now absolutely is sure the CR should be noted because the use case does not exist. Stefano (Qualcomm) responds to Ashok and Jaewoo and supports Pallab, and the CR can be safely noted without loss of functionality Ashok (Samsung) need clarification Stefano (Qualcomm) and Pallab (Nokia) Shabnam (Ericsson) responds that such note is not needed since the information you copied seem to already indicate per DNN? Stefano (Qualcomm) disagrees with the need for any changes. Ashok (Samsung) comments Stefano (Qualcomm) replies to Ashok. Ashok (Samsung) responds to Stafano (Qualcomm) Pallab (Nokia) responds to Ashok. Ashok (Samsung) propose to POSTPONE the paper Stefano (Qualcomm) insists on noting the paper. Ashok (Samsung) OK to NOTE the paper ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Postponed |
| 8.7 | S2-2200525 | CR | Approval | 23.256 CR0048 (Rel-17, 'F'): Clarification on cause of revocation | Qualcomm Incorporated | Rel-17 | Approved | Guanglei (Huawei) objects this CR Guanglei (Huawei) withdraws objection after discussion with Dimitios(Lenovo) ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Agreed |
| 8.7 | S2-2200761 | CR | Approval | 23.256 CR0054 (Rel-17, 'F'): Revocation of C2 authorisation | Lenovo, Motorola Mobility, | Rel-17 | r03 agreed. Revised to S2-2201286. | Guanzhou (InterDigital) provides comments. Stefano (Qualcomm) 761 and 788 address the same issue with similar but distinct approaches, and we cannot have both papers proceed. We recommend noting 788 and use 761 as a basis for further updates. Dimitris (Lenovo) provides r01 Shabnam (Ericsson) provides r02, cosigns and comments. Dimitris (Lenovo) provides r03 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.7 | S2-2201286 | CR | Approval | 23.256 CR0054R1 (Rel-17, 'F'): Revocation of C2 authorisation | Lenovo, Motorola Mobility, Ericsson | Rel-17 | Revision of S2-2200761r03. Approved | Agreed | |
| 8.7 | S2-2200788 | CR | Approval | 23.256 CR0056 (Rel-17, 'F'): Clarification on C2 authorization revocation | Huawei, HiSilicon | Rel-17 | Confirm CR Revision - CR states 1!. r12 agreed. Revised to S2-2201287. | Dimitris (Lenovo) indicates additional proposal in S2-2200761. Provides comments Stefano (Qualcomm) 761 and 788 address the same issue with similar but distinct approaches, and we cannot have both papers proceed. We recommend noting 788 and use 761 as a basis for further updates. Shabnam (Ericsson) proposes to note this CR and use 2200761 as a basis for further updates. Guanglei (Huawei) replies and provides r01 Pallab (Nokia) comments on r02 and asks for clarification. Dimitris (Lenovo) comments Guanglei (Huawei) replies and provides r03 Jaewoo (LGE) provides comments. Guanglei (Huawei) replies and provides r04 Pallab (Nokia) feels that it is getting confusing due mixing multiple things in this CR (C2 authorization and LS response to CT3). Let us discuss one thing in this CR please. Guanzhou (InterDigital) comments. Dimitris (Lenovo) has a comment on r04 Guanglei (Huawei) replies to Guanzhou (InterDigital) and provides r05 Guanglei (Huawei) replies Dimitrios(Lenovo) Dimitris (Lenovo) provides r06 and cosigns Guanglei (Huawei) replies to Dimitris (Lenovo) and provides r07 Guanzhou (InterDigital) questions the need of 'flight authorization revocation indication'. Pallab (Nokia) comments on r07 and provides r08 Guanglei (Huawei) responses to Pallab(Nokia) and Guanzhou Wang(InterDigital) and provides r09 and r10 for further discussion Pallab (Nokia) OK with r09 Dimitris (Lenovo) provides r11 based on r09 Guanglei (Huawei) is fine with r11 Shabnam (Ericsson) supports the CR, provides r12 and proposes to focus on the CT4 LS aspects on the SBI part only in this CR, gives explanation. Guanzhou (InterDigital) is OK with r12 and thinks other revisions(r09/r11, r10) may not be correct. Guanglei (Huawei) is fine with r12 Pallab (Nokia) is fine with r12 and co-signs ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.7 | S2-2201287 | CR | Approval | 23.256 CR0056R1 (Rel-17, 'F'): Clarification on re-authorization | Huawei, HiSilicon, Lenovo, Nokia, Nokia Shanghai Bell, Ericsson | Rel-17 | Revision of S2-2200788r12. Approved | Agreed | |
| 8.7 | S2-2200560 | CR | Approval | 23.256 CR0051 (Rel-17, 'F'): Clarification on PDU Session Status Event | LG Electronics | Rel-17 | r03 agreed. Revised to S2-2201288. | Pallab (Nokia) asks for clarification. Jaewoo (LGE) responds to Pallab(Nokia). Tricci (OPPO) supports comments from Pallab (Nokia). Tricci (OPPO) ask Jaewoo (LGE) for further clarifications. Jaewoo (LGE) responds to Tricci (OPPO). Pallab (Nokia) asks for further clarification. Jaewoo (LGE) responds to Pallab (Nokia) and provides r01. Shabnam (Ericsson) do not see why the changes are needed, if anything left of the content, we propose to provide a clean version with only remaining clauses that are being proposed to change. Stefano (Qualcomm) prefers r01 and does not support removing DNN/S-NSSAI. Jaewoo (LGE) responds to Shabnam (Ericsson) and provides r03. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.7 | S2-2201288 | CR | Approval | 23.256 CR0051R1 (Rel-17, 'F'): Clarification on PDU Session Status Event | LG Electronics | Rel-17 | Revision of S2-2200560r03. Approved | Agreed | |
| 8.7 | S2-2200561 | CR | Approval | 23.256 CR0052 (Rel-17, 'F'): Clarification on UAV Re-authorization procedure | LG Electronics | Rel-17 | r05 agreed. Revised to S2-2201289. | Tricci (OPPO) asks for clarification. Jaewoo (LGE) responds to Tricci (OPPO) and provides r01. Shabnam (Ericsson) comments that some of the changes are not needed, see details below. Jaewoo (LGE) responds to Shabnam (Ericsson). Guanglei (Huawei) provides comments and proposes to discuss the LS from CT3 first Jaewoo (LGE) provides comments. Jaewoo (LGE) provides r02. Jaewoo (LGE) replies to Guanglei (Huawei). Shabnam (Ericsson) our view is that the details you explain is not really stage 2 level, all stage 2 needs to add is that there are two distinct associations which we know from two different connectivity? Jaewoo (LGE) replies to Shabnam (Ericsson) and provides r03. Guanglei (Huawei) provides r04 Jaewoo (LGE) responds to Guanglei (Huawei) and provides r05. Guanglei (Huawei) is fine with r05 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.7 | S2-2201289 | CR | Approval | 23.256 CR0052R1 (Rel-17, 'F'): Clarification on UAV Re-authorization procedure | LG Electronics | Rel-17 | Revision of S2-2200561r05. Approved | Agreed | |
| 8.7 | S2-2201090 | CR | Approval | 23.256 CR0058 (Rel-17, 'F'): Removal of AMF determined re-authentication | China Mobile | Rel-17 | Noted | Guanzhou (InterDigital) questions the reason for change. Pallab (Nokia) has similar comments as raised by Guanzhou (InterDigital) and would request the author to clarify. Ashok (Samsung) comments Pallab (Nokia) responds to Ashok (Samsung). Stefano (Faccin) asks to see a revision with a corrected reason for change, point 1 is not correct. Yi (China Mobile) responds and provides r01. Guanzhou (InterDigital) can't accept this CR. Yi (China Mobile) responds to Guanzhou. Stefano (Qualcomm) responds to Yi. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Tao(VC) check whether r01 agreeable with clarification by Yi. Yi (China Mobile) responds to Stefano. ==== 8.X, 9.X, 10.X Final Deadline ==== Guanzhou (InterDigital) reiterates that we object to any version of this CR. | Noted |
| 8.7 | S2-2200826 | CR | Approval | 23.256 CR0057 (Rel-17, 'F'): Corrections to Nnef_Authentication_AuthenticateAuthorize service operation | Nokia, Nokia Shanghai Bell | Rel-17 | r03 agreed. Revised to S2-2201290. | Guanglei (Huawei) provides r01 Pallab (Nokia) OK with r01 Jaewoo (LGE) provides comment. Pallab (Nokia) responds to Jaewoo (LGE) and provides r02 Guanglei (Huawei) provides comments on r02 Pallab (Nokia) responds to Guanglei (Huawei) Jaewoo (LGE) is OK with r02. Guanglei (Huawei) further provides comments on r02 Pallab (Nokia) provides r03 Guanglei (Huawei) is fine with r03 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.7 | S2-2201290 | CR | Approval | 23.256 CR0057R1 (Rel-17, 'F'): Corrections to Nnef_Authentication_AuthenticateAuthorize service operation | Nokia, Nokia Shanghai Bell | Rel-17 | Revision of S2-2200826r03. Approved | Agreed | |
| 8.7 | S2-2200759 | CR | Approval | 23.256 CR0053 (Rel-17, 'F'): UAV attaching in EPS with no aerial subscription | Lenovo, Motorola Mobility, | Rel-17 | Noted | Pallab (Nokia) comments and asks for clarification. Dimitris (Lenovo) responds. Pallab (Nokia) asks further questions and thinks that the proposed changes are not needed. Pallab (Nokia) asks for further clarification. Ashok (Samsung) shares the same view as Pallab (Nokia) Dimitris (Lenovo) provides additional responses Ashok ( Samsung) replies to Dimitris (Lenovo) Pallab (Nokia) responds to Dimitris (Lenovo). Dimitris (Lenovo) provides r01 and responds to Pallab (Nokia) Ashok (Samsung) need clarification from Dimitris (Lenovo) Dimitris (Lenovo) responds to Ashok (Samsung) Pallab (Nokia) proposes to NOTE the paper. Stefano (Qualcomm) we share the view that the content left is not UAS specific, thus noting the paper is the best way forward. Shabnam (Ericsson) shares the same view, what is left in the r01 to me is not specific to UAS but any feature with DNN/APN association? ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 8.7 | S2-2200769 | CR | Approval | 23.256 CR0055 (Rel-17, 'F'): Correction on handling the authorized CAA-Level UAV ID provided by a USS | Lenovo, Motorola Mobility, | Rel-17 | r02 agreed. Revised to S2-2201291. | Pallab (Nokia) provides comments. Dimitris (Lenovo) provides r01 Pallab (Nokia) ok with r01. Guanzhou (InterDigital) provides r02 with some editorial changes on top of r01. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.7 | S2-2201291 | CR | Approval | 23.256 CR0055R1 (Rel-17, 'F'): Correction on handling the authorized CAA-Level UAV ID provided by a USS | Lenovo, Motorola Mobility, | Rel-17 | Revision of S2-2200769r02. Approved | Agreed | |
| 8.7 | S2-2200789 | CR | Approval | 23.501 CR3537 (Rel-17, 'F'): Correction on UAS NF discovery | Huawei, HiSilicon | Rel-17 | Confirm CR Revision - CR states 1!. r02 agreed. Revised to S2-2201292. | Tricci (OPPPO) objects this PCR to remove FQDN. This PCR should be NOTED. Guanglei (Huawei) replies and provides r01 Shabnam (Ericsson) the content of r01, the new addition of text is already there in current text so I believe there is nothing in this CR left, so propose to NOTE. Tricci (OPPO) thanks Guanglei (Huawei) response and is okay with r01. Pallab (Nokia) shares the same view and Shabnam (Ericsson) . Stefano (Qualcomm) shares Nokia's and Ericsson's view and proposes to note the paper. Pallab (Nokia) has same comment as in S2-2200790 Guanglei (Huawei) responses to Pallab (Nokia) and prefers the option 2 to remove the NOTE Pallab (Nokia) is OK to remove the NOTE. i.e. to approve 0790r00, 0789r00 and to NOTE 0827. Guanglei (Huawei) provides r02 based on r00 to correct the CR revision number ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.7 | S2-2201292 | CR | Approval | 23.501 CR3537R1 (Rel-17, 'F'): Correction on UAS NF discovery | Huawei, HiSilicon | Rel-17 | Revision of S2-2200789r02. Approved | Agreed | |
| 8.7 | S2-2200790 | CR | Approval | 23.502 CR3377 (Rel-17, 'F'): Correction on UAS NF discovery | Huawei, HiSilicon | Rel-17 | Confirm CR Revision - CR states 1!. r03 agreed. Revised to S2-2201293. | Pallab (Nokia) provides comments and also indicates that the fate of the CR depends on S2-2200789 as both the CRs are related. Guanglei (Huawei) replies and provides r01 Guanglei (Huawei) provides r02 Pallab (Nokia) comments and proposes NOTE the CR. Guanglei (Huawei) provides replies and asks whether we make this NOTE complete or just remove it Stefano (Qualcomm) also proposes to note the paper. Guanglei (Huawei) asks for clarification Pallab (Nokia) responds to Guanglei (Huawei). Guanglei (Huawei) responses to Pallab (Nokia) and prefers the option 2 to remove the NOTE Pallab (Nokia) is OK to remove the NOTE. i.e. to approve 0790r00, 0789r00 and to NOTE 0827. Guanglei (Huawei) provides r03 based on r00 to correct the CR revision number ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.7 | S2-2201293 | CR | Approval | 23.502 CR3377R1 (Rel-17, 'F'): Correction on UAS NF discovery | Huawei, HiSilicon | Rel-17 | Revision of S2-2200790r03. Approved | Agreed | |
| 8.7 | S2-2200827 | CR | Approval | 23.502 CR3381 (Rel-17, 'F'): NEF discovery using AF FQDN | Nokia, Nokia Shanghai Bell | Rel-17 | Noted | Guanglei (Huawei) provides comments and proposes to merge this paper to 0790r02 Pallab (Nokia) comments and proposes to go with r00. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 8.7 | S2-2201270 | LS In | Action | LS from CT WG4: LS on SMF initiated reauthorization | CT WG4 (C4-221445) | Rel-17 | Postponed | Postponed | |
| 8.8 | - | - | - | System enhancement for Proximity based Services in 5GS (5G_ProSe) | - | - | Docs:=82 | - | |
| 8.8 | - | - | - | LS for information | - | - | Docs:=2 | - | |
| 8.8 | S2-2200044 | LS In | Information | LS on the indication of discovery message and PC5-S signalling to ProSe layer | CT WG1 (C1-217167) | Rel-17 | Noted | Deng Qiang (CATT) proposed to note this incoming LS. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 8.8 | S2-2201255 | LS In | Information | LS from RAN WG2: LS reply on the indication of discovery message and PC5-S signalling to ProSe layer | RAN WG2 (R2-2201781) | Rel-17 | Noted | Deng Qiang (CATT) proposed to note this incoming LS. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 8.8 | - | - | - | UE POLICY PROVISIONING REQUEST message | - | - | Docs:=7 | - | |
| 8.8 | S2-2200014 | LS In | Action | LS from CT WG1: LS on UE POLICY PROVISIONING REQUEST message | CT WG1 (C1-216298) | Rel-17 | Revision of Postponed S2-2108284 from S2#148E. Responses drafted in S2-2200220 and S2-2200659. Final response in S2-2201294 | Deng Qiang (CATT) this LS can be marked as noted. ==== 8.X, 9.X, 10.X Final Deadline ==== | Replied to |
| 8.8 | S2-2200220 | LS OUT | Approval | [DRAFT] Reply LS on UE POLICY PROVISIONING REQUEST message | Ericsson | Rel-17 | Response to S2-2200014. Noted | Deng Qiang (CATT) proposed to note this reply LS and focus on S2-2200659. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 8.8 | S2-2200659 | LS OUT | Approval | Reply LS on UE POLICY PROVISIONING REQUEST message | Intel | Response to S2-2200014. r07 agreed. Revised to S2-2201294. | Belen (Ericsson) provides r02. Changhong (Intel) is OK with r02. Changhong (Intel) replies to Susan and propose to agree on a version for the LS reply. Susan (Huawei) objects to this LS, all versions. Hannu (Nokia) provides r03. Changhong (Intel) provides r04 based on r03. Deng Qiang (CATT) proposes to follow CC#1 way-forward, and agreed one reply to CT1. Belen (Ericsson) provides r05. Susan (Huawei) provides r07. Belen (Ericsson) is okay with r07 for this meeting. We think we need to define how the Rel16 PCF will behave at Initial Registration (next meeting) Sherry (Xiaomi) comments. Belen (Ericsson) replies to Sherry Hong (Qualcomm) comments. ==== 8.X, 9.X, 10.X Revisions Deadline ==== LaeYoung (LGE) is fine with r07. Tao(VC) thanks. Let's check r07 agreeable or not Deng Qiang (CATT) clarifies to Tao (VC) r07 is target for approval, not r06. Hong (Qualcomm) accepts r07. Changhong (Intel) is OK with r07. ==== 8.X, 9.X, 10.X Final Deadline ==== Sherry (Xiaomi) is fine with r07. | Revised | |
| 8.8 | S2-2201294 | LS OUT | Approval | Reply LS on UE POLICY PROVISIONING REQUEST message | SA WG2 | Rel-17 | Revision of S2-2200659r07. Approved | Approved | |
| 8.8 | S2-2200217 | CR | Approval | 23.503 CR0668R1 (Rel-17, 'F'): Removal of the V2X or ProSe policy request at Registration | Ericsson, Huawei | Rel-17 | Revision of (Noted) S2-2108342 from S2#148E. Noted | Deng Qiang (CATT) proposed to note this CR per CC#1 outcome. Hannu (Nokia) supports the proposal from Deng Qiang (CATT) to note this CR per CC#1 outcome. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 8.8 | S2-2200660 | CR | Approval | 23.502 CR3372 (Rel-17, 'F'): Correction for UE Policy Container | Intel, Qualcomm Incorporated | Rel-17 | Source to WG incorrect! Noted | Belen (Ericsson) thinks that this CR is not needed as attachment to S2-2200659, objects to this CR Susan (Huawei) objects to this CR. Changhong (Intel) replies to Susan. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 8.8 | S2-2200219 | CR | Approval | 23.304 CR0042R1 (Rel-17, 'F'): ProSe policy provisioning request | Ericsson, Huawei | Rel-17 | Revision of (Noted) S2-2108341 from S2#148E. Noted | Deng Qiang (CATT) proposed to note this CR per CC#1 outcome. Hannu (Nokia) supports the proposal from Deng Qiang (CATT) to note this CR per CC#1 outcome. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 8.8 | - | - | - | PC5 DRX for ProSe | - | - | Docs:=3 | - | |
| 8.8 | S2-2200034 | LS In | Action | LS response on PC5 DRX for ProSe | RAN WG2 (R2-2111433) | Rel-17 | Revision of Postponed S2-2109373 from S2#148E. Noted | Fei (OPPO) proposed to note this incoming LS. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 8.8 | S2-2200087 | CR | Approval | 23.304 CR0024R1 (Rel-17, 'B'): DRX support for direct discovery and communication and L3 relay | OPPO, LG Electronics | Rel-17 | Revision of (Postponed) S2-2107422 from S2#147E. r04 agreed. Revised to S2-2201295. | Walter Dees (Philips) comments. LaeYoung (LGE) provides r01. Steve (Huawei) comments Hong (Qualcomm) comments. Fei (OPPO) responds to Hong (Qualcomm) and Steve(Huawei) and provides r02 LaeYoung (LGE) comments and provides r03. Mehrdad (Samsung) comments Fei (OPPO) responds to Mehrdad (Samsung) LaeYoung (LGE) responds to Fei (OPPO) and Mehrdad (Samsung). Mehrdad (Samsung)replies to OPPO and LGE. Zhang (Ericsson) provides comments Fei (OPPO) provides responses to Hao (ZTE). Fei (OPPO) provides responses. LaeYoung (LGE) replies to Hao Dong (ZTE). LaeYoung (LGE) provides r04. LaeYoung (LGE) provides comment. Hao Dong (ZTE) responds to Fei (OPPO). Fei (OPPO) responds to Hao (ZTE). Hao Dong (ZTE) comments. Fei (OPPO) replies Deng Qiang (CATT) agree with LaeYoung (LGE) to stick to RAN2 conclusion. Mehrdad (Samsung) thanks LGE for the revision and comments ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.8 | S2-2201295 | CR | Approval | 23.304 CR0024R2 (Rel-17, 'B'): DRX support for direct discovery and communication and L3 relay | OPPO, LG Electronics | Rel-17 | Revision of S2-2200087r04. Approved | Agreed | |
| 8.8 | - | - | - | RSC determination in Layer-3 Remote UE | - | - | Docs:=10 | - | |
| 8.8 | S2-2200050 | LS In | Action | LS from CT WG1: LS on RSC determination in the remote UE for 5G ProSe Layer-3 UE-to-network relay scenario | CT WG1 (C1-217452) | Rel-17 | Response drafted in S2-2200721, S2-2200926 and S2-2201127. Final response in S2-2201842 | Deng Qiang (CATT) this LS can be marked as noted. ==== 8.X, 9.X, 10.X Final Deadline ==== | Replied to |
| 8.8 | S2-2200721 | LS OUT | Approval | Reply LS on RSC determination in the remote UE for 5G ProSe Layer-3 UE-to-network relay scenario | OPPO | Rel-17 | Response to S2-2200050. Noted | Judy (Ericsson) comments the related discussion is in S2-2200928 Deng Qiang (CATT) proposes to note this LS out and focused on either S2-2201137 or S2-2200926. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Fei (OPPO) it can be noted. ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 8.8 | S2-2200926 | LS OUT | Approval | [DRAFT] LS reply on RSC determination in the remote UE for 5G ProSe Layer-3 UE-to-network relay scenario | Huawei, HiSilicon | Rel-17 | Response to S2-2200050. CC#4: r02 agreed. Revised to S2-2201842. | Guanglei (Huawei) provides r01 to reflect the 0928r02 and proposes to use this one if we can go with 0928 Judy (Ericsson) comments this paper is related to discussion in S2-2200928 Deng Qiang (CATT) provides r02 to shorten the answer. Guanglei (Huawei) is fine with r02 ==== 8.X, 9.X, 10.X Revisions Deadline ==== Deng Qiang (CATT) this reply LS needs to be discussed at CC#4 as the attachment CR needs to be discussed at CC#4. ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.8 | S2-2201842 | LS OUT | Approval | LS reply on RSC determination in the remote UE for 5G ProSe Layer-3 UE-to-network relay scenario | SA WG2 | Rel-17 | Revision of S2-2200926r02. Approved | Approved | |
| 8.8 | S2-2201137 | LS OUT | Approval | [DRAFT] Relay LS on RSC determination in the remote UE for 5G ProSe Layer-3 UE-to-network relay scenario | Qualcomm Incorporated | Rel-17 | Response to S2-2200050. Noted | Judy (Ericsson) comments this paper is related to discussion in S2-2200928 ==== 8.X, 9.X, 10.X Revisions Deadline ==== Deng Qiang (CATT) this reply LS can be noted as we move forward with S2-2200926. ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 8.8 | S2-2200929 | DISCUSSION | Approval | Discussion on RSC determination by remote UE in L3 U2N relay scenario. | Huawei, HiSilicon | Rel-17 | Noted | Deng Qiang (CATT) proposed to note this DP. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 8.8 | S2-2200737 | CR | Approval | 23.304 CR0076 (Rel-17, 'F'): RSC determination by Layer-3 remote UE | OPPO | Rel-17 | Noted | Deng Qiang (CATT) proposed to note this CR. Judy (Ericsson) supports Deng Qiang's proposal to note this paper. Guanglei (Huawei) proposes to consider the alternative b) Fei (OPPO) responds to Deng Qiang (CATT) and Judy (Ericsson). Wen (vivo) comments and shares the same concerns from CT1. Hannu (Nokia) supports the proposal from Deng Qiang and Judy to note this document. Hong (Qualcomm) comments and agrees that Application Layer does not control RSC. Xiaoyan Shi (Interdigital) supports to note this CR. Guanglei (Huawei) provides comments Fei (OPPO) responds to Hong (Qualcomm) ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 8.8 | S2-2200928 | CR | Approval | 23.304 CR0080 (Rel-17, 'F'): RSC Determination by a Layer-3 Remote UE | Huawei, HiSilicon | Rel-17 | CC#4: r05 + changes agreed. Revised to S2-2201841. | Deng Qiang (CATT) proposed to note this CR and stick to current conclusion. Guanglei (Huawei) replies and kindly reminds that the question is how UE can determine suitable RSC. Hong (Qualcomm) comments. Deng Qiang (CATT) comments. Mehrdad (Samsung) also thinks this CR goes against the past agreements and the Spec and prefers S2-2201137 as the baseline for LS reply. Guanglei (Huawei) provides r02 Hong (Qualcomm) comments on r01. Fei (OPPO) comments on r01. Guanglei (Huawei) re-provides the right link of 0928 r01 Guanglei (Huawei) provides r01 to reflect option#2 of 0929 Judy (Ericsson) ask questions. Guanglei (Huawei) responses to Judy (Ericsson) Guanglei (Huawei) responds to Deng Qiang (CATT) Judy (Ericsson) comments. Guanglei (Huawei) replies to Deng Qiang (CATT) Deng Qiang (CATT) replies to Guanglei (Huawei). Hong (Qualcomm) comments on r02. Guanglei (Huawei) provides r03 Deng Qiang (CATT) provides r04. Guanglei (Huawei) provides r05 based on r04 ==== 8.X, 9.X, 10.X Revisions Deadline ==== Deng Qiang (CATT) prefers r04 but can live with r05 if UE implementation is made as a NOTE, and CR category needs to be fixed. Mehrdad (Samsung) agrees with Ericsson. We think we need a revision to be discussed over CC#4 or CC#5 Guanglei (Huawei) is fine to fix the CR category based on r05, also to make the UE implementation as a NOTE, revise the word based on comments from Judy, and ask for CC#4 Guanglei (Huawei) responds to Mehrdad (Samsung) Deng Qiang (CATT) this CR request to be discussed at CC#4. Guanglei (Huawei) responds and is fine to remove the second change of r05 during the CC#4 ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.8 | S2-2201841 | CR | Approval | 23.304 CR0080R1 (Rel-17, 'B'): RSC Determination by a Layer-3 Remote UE | Huawei, HiSilicon | Rel-17 | Revision of S2-2200928r05 + changes. Approved | Agreed | |
| 8.8 | S2-2200927 | CR | Approval | 23.503 CR0701 (Rel-17, 'F'): RSC Determination by a Layer-3 Remote UE | Huawei, HiSilicon | Rel-17 | Noted | Deng Qiang (CATT) proposed to note this CR, same comment as 0928. Guanglei (Huawei) replies and provides r01 Xiaoyan Shi (Interdigital) proposes to note this CR. Hong (Qualcomm) comments on r01. Guanglei (Huawei) replies to Wen(vivo), Xiaoyan Shi (Interdigital), Deng Qiang(CATT), Hong (Qualcomm) Wen (vivo) comments. Deng Qiang (CATT) comments on r01. Fei (OPPO) comments on r01. Hong (Qualcomm) replies to Guanglei. Deng Qiang (CATT) replies to Guanglei. Guanglei (Huawei) responses to Deng qiang (CATT) and Hong (Qualcomm) Mehrdad (Samsung) thinks this CR goes against the past agreements and the Spec and prefers S2-2201137 as the baseline for LS reply. Guanglei (Huawei) replies to Mehrdad (Samsung), if we can live with r01 of 0928, then 0927 can be noted Guanglei (Huawei) responses to Hong (Qualcomm) Deng Qiang (CATT) proposes to note this CR as extending URSP is not agreeable. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Mehrdad (Samsung) also proposes to NOTE this CR. Guanglei (Huawei) agrees to note 0927, as we are focusing on the other direction based on 0928 ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 8.8 | - | - | - | RAN sharing and discovery signalling | - | - | Docs:=5 | - | |
| 8.8 | S2-2201256 | LS In | Action | LS from RAN WG2: LS on support of RAN sharing and discovery signalling | RAN WG2 (R2-2201810) | Rel-17 | Response drafted in S2-2200930. Final response in S2-2201296 | Deng Qiang (CATT) this LS can be marked as noted. ==== 8.X, 9.X, 10.X Final Deadline ==== | Replied to |
| 8.8 | S2-2200930 | LS OUT | Approval | [DRAFT] LS reply on support of RAN sharing and discovery signalling | Huawei, HiSilicon | Rel-17 | Response to S2-2201256. r01 agreed. Revised to S2-2201296. | Fei (OPPO) provides r01. Steve (Huawei) r01 is fine for me. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.8 | S2-2201296 | LS OUT | Approval | LS reply on support of RAN sharing and discovery signalling | SA WG2 | Rel-17 | Revision of S2-2200930r01. Approved | Approved | |
| 8.8 | S2-2200924 | CR | Approval | 23.304 CR0079 (Rel-17, 'F'): Support of RAN Sharing for L2 Relay | Huawei, HiSilicon | Rel-17 | r05 agreed. Revised, merging S2-2200379, to S2-2201297. | Deng Qiang (CATT) provides r01. Steve (Huawei) comments Hannu (Nokia) asks a question. Fei (OPPO) provides comments. Deng Qiang (CATT) replies and comments on NCGI. Fei (OPPO) responds to Deng Qiang (CATT) Hong (Qualcomm) comments. Walter Dees (Philips) prefers to keep NCGI. Steve (Huawei) comments on linking the descriptions Fei (OPPO) responds to Steve (Huawei) and provides r02. Changhong (Intel) comments and prefers to keep NCGI for now. Deng Qiang (CATT) think NCGI is still useful after further check. Deng Qiang (CATT) responds to Steve (Huawei). Hannu (Nokia) thanks Deng Qiang (CATT) for reply and confirms his original intention. Deng Qiang (CATT) replies to Hannu (Nokia) and provides r03. Steve (Huawei) provides r04 Fei (OPPO) comments and provides r05. Steve (Huawei) wording in r05 is ok ==== 8.X, 9.X, 10.X Revisions Deadline ==== Deng Qiang (CATT) r05 is ok. ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.8 | S2-2201297 | CR | Approval | 23.304 CR0079R1 (Rel-17, 'F'): Support of RAN Sharing for L2 Relay | Huawei, HiSilicon | Rel-17 | Revision of S2-2200924r05, merging S2-2200379 and S2-2200378. Approved | Agreed | |
| 8.8 | - | - | - | Discovery and data associated to different L2 IDs | - | - | Docs:=9 | - | |
| 8.8 | S2-2201254 | LS In | Action | LS from RAN WG2: LS to SA2 on discovery and data associated to different L2 IDs | RAN WG2 (R2-2201780) | Rel-17 | Responses drafted in S2-2200701 and S2-2201222. Final response in S2-2201298 | Deng Qiang (CATT) this LS can be marked as noted. ==== 8.X, 9.X, 10.X Final Deadline ==== | Replied to |
| 8.8 | S2-2200701 | LS OUT | Approval | LS response on discovery and data associated to different L2 IDs | vivo | Rel-17 | Response to S2-2201254. r01 agreed. Revised to S2-2201298, merging S2-2201061 | Wen (vivo) provides r01 based on the progress on S2-2200702. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.8 | S2-2201298 | LS OUT | Approval | Reply LS on discovery and data associated to different L2 IDs | SA WG2 | Rel-17 | Revision of S2-2200701r01, merging S2-2201061. Approved | Approved | |
| 8.8 | S2-2201222 | LS OUT | Approval | [DRAFT] Reply LS on Discovery and data associated to different L2 IDs | Philips International B.V. | Rel-17 | Response to S2-2201254. Merged into S2-2201615 | Mehrdad (Samsung) suggests to mark this as noted or merged into S2-2200701 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 8.8 | S2-2201240 | DISCUSSION | Agreement | Discussion on multiplexing direct discovery and direct communication messages . | Apple | Rel-17 | Noted | Deng Qiang (CATT) this DP can be noted as we made good progress in actual CR S2-2200702. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 8.8 | S2-2200700 | DISCUSSION | Approval | Discussion and proposal on discovery and data associated to different L2 ID in RAN WG2 LS R2-2201780. | vivo | Rel-17 | Noted | Deng Qiang (CATT) this DP can be noted as we made good progress in actual CR S2-2200702. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 8.8 | S2-2200702 | CR | Approval | 23.304 CR0075 (Rel-17, 'F'): Handling on discovery and data associated to different L2 IDs | vivo | Rel-17 | r13 agreed. Revised to S2-2201299. | Wen (vivo) provides r01 based on discussion before. Deng Qiang (CATT) comments. Fei (OPPO) comments r01 Wen (vivo) replies and provides r02 Zhang (Ericsson) provides comments for r02 Fei (OPPO) provides comments Steve (Huawei) comments Sudeep (Apple) comments on r02. Hong (Qualcomm) comments. Wen (vivo) replies and provides r03 Fei (OPPO) comments on r03 Wen (vivo) provides r04 Wen (vivo) replies. Deng Qiang (CATT) comments on r04. Mehrdad (Samsung) provides r06. Wen (vivo) replies and provides r07. Deng Qiang (CATT) also prefers a NOTE. Mehrdad (Samsung) thinks NOTE Y is not needed and cannot agree with r07. Wen (vivo) removed NOTE Y and provides r08. Mehrdad (Samsung) is OK with r08. Walter (Philips) provides r09 Zhang (Ericsson) is OK with r08 Wen (vivo) is ok with r09 Steve (Huawei) provides r10, editorial. Fei (OPPO) comments on r10. Wen (vivo) provides r11. Fei (OPPO) r11 is good. Mehrdad (Samsung) is OK with r11 and co-signs the CR. Wen (vivo) , thanks for Mehrdad (Samsung) support and will add Samsung in the cleaned version. Steve (Huawei) provides r12 Wen (vivo) provides r13 Steve (Huawei) thanks Wen (vivo) to copying the changes, r13 is ok for me. Hannu (Nokia) reminds that we can't make requirements in informative notes. Provides r14. Wen (vivo) comments on r14. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Mehrdad (Samsung) is OK with both r14 and r13 but we object to original revision, r01, r02,r03, r04 , r05 and r07. Deng Qiang (CATT) prefers r13. Wen (vivo) also prefers r13. Fei (OPPO) is ok with r14 and r13. Zhang (Ericsson) is Ok with r13 and r14 ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.8 | S2-2201299 | CR | Approval | 23.304 CR0075R1 (Rel-17, 'F'): Handling on discovery and data associated to different L2 IDs | Vivo, Philips International B.V, Apple, Samsung | Rel-17 | Revision of S2-2200702r13. Approved | Agreed | |
| 8.8 | S2-2201223 | CR | Approval | 23.304 CR0085 (Rel-17, 'F'): Clarification on L2 identifiers used for discovery and communication | Philips International B.V. | Rel-17 | Merged into S2-2201615 | Deng Qiang (CATT) proposes to be merged into S2-2200702. Walter Dees (Philips) agrees with the merge into S2-2200702. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 8.8 | - | - | - | LS on non-relay discovery | - | - | Docs:=3 | - | |
| 8.8 | S2-2200059 | LS In | Action | LS from RAN WG2: LS on non-relay discovery | RAN WG2 (R2-2111397) | Rel-17 | Noted | Fei (OPPO) proposed to note this incoming LS. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 8.8 | S2-2200570 | CR | Approval | 23.304 CR0070 (Rel-17, 'F'): Removal of discovery range | LG Electronics | Rel-17 | Approved | ==== 8.X, 9.X, 10.X Final Deadline ==== | Agreed |
| 8.8 | S2-2200738 | CR | Approval | 23.304 CR0077 (Rel-17, 'F'): Range and RRC container to align with RAN WG2 agreement | OPPO | Rel-17 | Merged into S2-2201795 and S2-2201297 | Deng Qiang (CATT) proposes to be merged into S2-2200570 and S2-2200924. Fei (OPPO) responds to Deng Qiang (CATT). Steve (Huawei) comments splitting the discussion Xiaoyan Shi (Huawei) proposes to merge this CR to 0570 and 0924. Fei (OPPO) is fine to merge this CR to 0570 and 0924. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 8.8 | - | - | - | Layer-3 Relay authentication and authorization | - | - | Docs:=7 | - | |
| 8.8 | S2-2200067 | LS In | Action | LS from SA WG3: Reply LS on Layer-3 UE-to-Network Relay authentication and authorization | SA WG3 (S3-214443) | Rel-17 | Responsesdrafted in S2-2201127. Noted | Deng Qiang (CATT) this LS can be marked as noted. ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 8.8 | S2-2201127 | LS OUT | Approval | [DRAFT] Reply LS on Layer-3 UE-to-Network Relay authentication and authorization | Qualcomm Incorporated | Rel-17 | Response to S2-2200067. Noted | Fei (OPPO) asks questions. Myungjune (LGE) comments Hong (Qualcomm) replies to Fei. Zhang (Ericsson) provides comments Fei (OPPO) replies to Zhang (Ericsson) and Hong (Qualcomm) Xiaoyan Shi (Interdigital) proposes to NOTE this LS. Deng Qiang (CATT) thinks it is valuable to ask feedback from SA3 if any architecture impact is identified by SA2. Steve (Huawei) comments ==== 8.X, 9.X, 10.X Revisions Deadline ==== Deng Qiang (CATT) proposes to note this reply LS. Steve (Huawei) should be noted ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 8.8 | S2-2201117 | CR | Approval | 23.304 CR0083 (Rel-17, 'B'): Add reference points for UE-PKMF and PKMF-PKMF | Qualcomm Incorporated | Rel-17 | Merged into S2-2201300 | Zhang (Ericsson) suggest merge S2-2201117 into S2-2200214 Deng Qiang (CATT) this CR can be merged into S2-2200214. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 8.8 | S2-2200214 | CR | Approval | 23.304 CR0063 (Rel-17, 'F'): Capture the reference point of PKMF | Ericsson | Rel-17 | r03 agreed. Revised to S2-2201300, merging S2-2201117 | Deng Qiang (CATT) proposes to be merged into S2-2201117. Fei (OPPO) comments. Zhang (Ericsson) suggest merge S2-2201117 into S2-2200214 Steve (Huawei) comments, not all the interfaces are correct Zhang (Ericsson) provides comments Steve (Huawei) withdraws comment about Npc9 Zhang (Ericsson) provides r01 Xiaoyan Shi (Interdigtial) share same view with CATT and Huawei on Npc10 (UDM and 5G PKMF). Provides r02 by removing Npc10 Deng Qiang (CATT) provides r03 on top of r02. Deng Qiang (CATT) responds to Zhang (Ericsson). ==== 8.X, 9.X, 10.X Revisions Deadline ==== Steve (Huawei) is ok with r03. Xiaoyan Shi (Interdigital) is fine with r03. ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.8 | S2-2201300 | CR | Approval | 23.304 CR0063R1 (Rel-17, 'F'): Capture the reference point of PKMF | Ericsson, Qualcomm Incorporated | Rel-17 | Revision of S2-2200214r03, merging S2-2201117. Approved | Agreed | |
| 8.8 | S2-2201001 | CR | Approval | 23.304 CR0081 (Rel-17, 'B'): Security procedures for L3 relaying | Nokia, Nokia Shanghai Bell, Interdigital Inc., LG Electronics | Rel-17 | r07 agreed. Revised to S2-2201301. | Zhang (Ericsson) provides comments Hannu (Nokia) replies to Zhang (Ericsson) and provides r01. Hong (Qualcomm) comments on r01. Deng Qiang (CATT) comments. Fei (OPPO) commets. Hannu (Nokia) agrees with the feedback from Hong, Fei, Deng Qiang and Zhang and provides r02 Fei (OPPO) comments on r02. Zhang (Ericsson) provides comments on r02 Deng Qiang (CATT) provides r03. Steve (Huawei) provides r04 Zhang (Ericsson) prefer r04 Fei (OPPO) is ok with r04. Xiaoyan Shi (Interdigital) provides r05. Hong (Qualcomm) comments on r05. Hannu (Nokia) responds to Hong and provides r06. Hong (Qualcomm) is fine with r06. Steve (Huawei) provides r07 Xiaoyan Shi (Interdigital) provides r08 Zhang (Ericsson) prefer r07 Hong (Qualcomm) comments. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Hannu (Nokia) prefers r08, can also live with r07 and shares his thoughts. Deng Qiang (CATT) would suggest to move forward with r07. Xiaoyan Shi (Interdigital) would suggest to move forward with r08 and possible update can be made in next meeting. Hannu (Nokia) still prefers r08 and asks Deng Qiang what which part of the additional bullet point is not already specified by SA3? Fei (OPPO) proposed the rewording. Steve (Huawei) prefers r07. Let's come back to the wording. Hannu (Nokia) can live with r07 but asks again what's wrong with r08, if anything? Deng Qiang (CATT) replies to Hannu (Nokia). Fei (OPPO) Replied to Hannu (Nokia). Hannu (Nokia) replies to Fei Hannu (Nokia) replies to Deng Qiang Fei (OPPO) replied to Hannu, Hannu (Nokia) can live with r07 if the others are not willing to accept r08. ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.8 | S2-2201301 | CR | Approval | 23.304 CR0081R1 (Rel-17, 'B'): Security procedures for L3 relaying | Nokia, Nokia Shanghai Bell, Interdigital Inc., LG Electronics | Rel-17 | Revision of S2-2201001r07. Approved | Agreed | |
| 8.8 | - | - | - | LS on Layer-3 Remote UE authorization | - | - | Docs:=1 | - | |
| 8.8 | S2-2200414 | LS In | Action | LS from RAN WG3: Reply LS for authorization information for 5G ProSe Layer-3 Remote UE | RAN WG3 (R3-221202) | Rel-17 | Noted | Deng Qiang (CATT) proposes to note this LS. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 8.8 | - | - | - | Mobility Restriction | - | - | Docs:=6 | - | |
| 8.8 | S2-2200925 | DISCUSSION | Approval | Discussion on ProSe Mobility Restrictions. | Huawei, HiSilicon | Rel-17 | Noted | ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 8.8 | S2-2200134 | CR | Approval | 23.304 CR0061 (Rel-17, 'F'): Resolve EN for Mobility Restriction | CATT | Rel-17 | CC#4: r04 + changes agreed. Revised to S2-2201843, merging S2-2200216, S2-2201122 and S2-2200504 | Judy (Ericsson) checks if this paper could be used as baseline for discussion and revisions Mehrdad (Samsung) is OK to use S2-2200134 as the baseline for the discussion. However, wording needs improvement. Judy (Ericsson) responds to Mehrdad (Samsung) LaeYoung (LGE) is fine to use this CR as baseline for discussion and revisions. Wen (vivo) comments: Steve (Huawei) is ok to use this thread for discussion and CR to update Hannu (Nokia) thought S2-2200504 was better structured to work as the basis but agrees to discuss the topic under this thread. But revision of S2-2200134 is needed. Mehrdad (Samsung) clarifies to Nokia that S2-2200134 is only used as the thread for the discussions but we agree with Nokia that S2-2200504 wording is better. Xiaoyan Shi (Interdigital) is ok to use 0134 thread for further discussion, but the original text of this contribution is not acceptable for us. Judy (Ericsson) comments. Hong (Qualcomm) agrees with Judy's summary. Fei (OPPO) provides comments. Mehrdad (Samsung) replies to Ericsson Judy (Ericsson) responds to Mehrdad (Samsung). Steve (Huawei) comments Hannu (Nokia) asks for conclusion on this paper and proposes to mention emergency and other regulatory priority services explicitly to avoid misunderstanding. Mehrdad (Samsung) agrees with Nokia that both emergency service and other regulatory prioritized services should be clarified together and replies to Ericsson. Judy (Ericsson) comments and provides r01. Judy (Ericsson) responds to Fei (OPPO). Fei (OPPO) asks questionts on NOTE1 in r01 Wen (vivo) replies Judy (Ericsson) responds to Wen (vivo) Wen (vivo) comments. Mehrdad (Samsung) provides r02 Judy (Ericsson) responds to Wen (vivo) and Mehrdad (Samsung), provides r04 (please ignore r03) Xiaoyan Shi (Interdigital) objects all versions of 0134. All these versions proposes the L2 NW relay cannot be used in Non-allowed area without clear justification. Xiaoyan Shi (Interdigital) replies to Samsung. Mehrdad (Samsung) replies to InterDigital. Judy (Ericsson) comments that SOH is probably the only way forward if objection is not withdrawn. Deng Qiang (CATT) asks whether SoH is required. Xiaoyan Shi (Interdigital) replies. Judy (Ericsson) responds to Xiaoyan Shi. Xiaoyan Shi (interdigital) replies to Judy. Fei (OPPO) supports SoH. Mehrdad (Samsung) is not clear what is exactly to be put in SoH until the Rel-18 KI is agreed. Hannu (Nokia) points out another technical problem in r04. Mehrdad (Samsung) replies to Nokia Shabnam (Ericsson) proposes companies remain professional during discussions where there is disagreement, see comments. Mehrdad (Samsung) replies to Ericsson and clarifies it is all professional discussions. Steve (Huawei) provides r05 Xiaoyan Shi (Interdigital) only accepts r05 and objects all previous version. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Mehrdad (Samsung) objects to r05. Shabnam (Ericsson) thanks, I am glad we cleared the misunderstanding so all is fine ??. Mehrdad, please note that for Rel-17 there was no requirement in WI for emergency support & for Rel-18 no Priority services but we are open to inclusion if wanted by the main drivers of this feature. Mehrdad (Samsung) thanks Ericsson for their constructive feedback and glad that we clarified the matter. We are also open to clarify the Rel-18 SID scope for WT#10. Judy (Ericsson) has had the view from the beginning, i.e. 5G ProSe enabled UE in Non-Allowed Area should have the same behavior regarding whether such UE can act as Relay, regardless of L3 or L2, and supports SOH in CC#4 to move forward. Wen (vivo) provides views. Deng Qiang (CATT) thanks all for the good discussion and proposed way-forward proposals for Layer-2 Relay in Non-Allowed Area. Hannu (Nokia) supports Judy's proposal that ProSe UE behaves in Non-Allowed Area the same way irrespective of whether such UE can act as Relay and this applies equally on L2 and L3 relaying. Supports r04 (with tiny edit to remove the words 'of its serving PLMN') Mehrdad (Samsung) agrees we need to go for a SoH. We also prefer r04. Steve (Huawei) has also had the same view the start and is unchanged. L2 relay is ok. Hannu (Nokia) proposes to mark up this document for decision in CC. Deng Qiang (CATT) request to discuss this CR at CC#4. Hong (Qualcomm) comments. ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.8 | S2-2201843 | CR | Approval | 23.304 CR0061R1 (Rel-17, 'F'): Resolve EN for Mobility Restriction | CATT, Ericsson, Samsung | Rel-17 | Revision of S2-2200134r04 + changes, merging S2-2200216, S2-2201122 and S2-2200504. Approved | Agreed | |
| 8.8 | S2-2200216 | CR | Approval | 23.304 CR0027R6 (Rel-17, 'F'): EN resolve for mobility restriction | [vivo, Samsung, Nokia, Nokia Shanghai Bell,] Ericsson | Rel-17 | Revision of (Noted) S2-2108382 from S2#148E. Merged into S2-2201843 | Judy (Ericsson) comments (as author) this paper is merged to S2-2200134 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 8.8 | S2-2200504 | CR | Approval | 23.304 CR0068 (Rel-17, 'F'): EN resolve for mobility restriction | Samsung | Rel-17 | Merged into S2-2201843 | Judy (Ericsson) comments that the related discussion is in S2-2200134 thread. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Steve (Huawei) should be noted or merged to S2-2200134, as discussions/CRs are in 0134. Mehrdad (Samsung) is OK to mark this CR as merged into S2-2200134. ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 8.8 | S2-2201122 | CR | Approval | 23.304 CR0084 (Rel-17, 'F'): EN resolve for mobility restriction | Interdigital Inc | Rel-17 | Merged into S2-2201843 | Judy (Ericsson) comments that the related discussion is in S2-2200134 thread. Xiaoyan Shi (Interdigital) confirms this CR could be marked as 'merged to S2-2200134'. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 8.8 | - | - | - | Miscellaneous corrections | - | - | Docs:=29 | - | |
| 8.8 | S2-2200133 | CR | Approval | 23.304 CR0060 (Rel-17, 'F'): Clarification on QoS handling for Layer-3 Relay with N3IWF | CATT | Rel-17 | r02 agreed. Revised to S2-2201302. | Zhang (Ericsson) asks for clarification Yali (OPPO) provides comments Myungjune (LGE) comments Steve (Huawei) comments Hong (Qualcomm) comments. Steve (Huawei) clarifies the question Yali (OPPO) comments. Deng Qiang (CATT) provides r01. Yali (OPPO) provides r02. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Deng Qiang (CATT) is fine with r02. Zhang (Ericsson) is OK with r02 ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.8 | S2-2201302 | CR | Approval | 23.304 CR0060R1 (Rel-17, 'F'): Clarification on QoS handling for Layer-3 Relay with N3IWF | CATT | Rel-17 | Revision of S2-2200133r02. Approved | Agreed | |
| 8.8 | S2-2200593 | CR | Approval | 23.304 CR0071 (Rel-17, 'F'): Clarification of QoS handling for L3 U2N with N3IWF | OPPO | Rel-17 | Noted | Zhang (Ericsson) provides comments Yali (OPPO) replies to Zhang (Ericsson) Myungjune (LGE) comments Yali (OPPO) replies to Myungjune (LGE) Myungjune (LGE) replies to Yali (OPPO) Hong (Qualcomm) comments. Yali (OPPO) comments. Yali (OPPO) replies to Hong (Qualcomm). Yali (OPPO) replies to Zhang (Ericsson) and Hong (Qualcomm). Hong (Qualcomm) replies to Yali. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Hong (Qualcomm) cannot agree r0. Yali (OPPO) confirms this CR can be noted. ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 8.8 | S2-2200135 | CR | Approval | 23.304 CR0062 (Rel-17, 'F'): Remove ENs on security aspects | CATT | Rel-17 | Merged into S2-2201303 | Deng Qiang (CATT) this paper can be marked as merged into S2-2200215r01. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 8.8 | S2-2200215 | CR | Approval | 23.304 CR0064 (Rel-17, 'F'): Resolve ENs for Security Parameters Provisioning | Ericsson | Rel-17 | r04 agreed. Revised to S2-2201303, merging S2-2200135 and S2-2200922 | Deng Qiang (CATT) provides r01 that merged S2-2200135 and S2-2200922. Zhang (Ericsson) provides comments Fei (OPPO) comments on r00 and r01. Hannu (Nokia) provides r02 to remove normative language from informative notes. Xiaoyan Shi (Interdigital) proposes to postpone this CR. Deng Qiang (CATT) replies and provides r03. Deng Qiang (CATT) responds. Zhang (Ericsson) is OK with r03 Steve (Huawei) provides r04 Zhang (Ericsson) reply to Steve (Huawei) Steve (Huawei) comments Deng Qiang (CATT) proposed to go with r04 which accurately reflect SA3 spec. Fei (OPPO) provides comments and prefers r03. Steve (Huawei) agrees with r04 Hannu (Nokia) supports r04 Fei (OPPO) prefers r03 and can accept r04. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Zhang (Ericsson) prefer r03, can live with r04 ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.8 | S2-2201303 | CR | Approval | 23.304 CR0064R1 (Rel-17, 'F'): Resolve ENs for Security Parameters Provisioning | Ericsson, CATT, Huawei, HiSilicon | Rel-17 | Revision of S2-2200215r04, merging S2-2200135, merging S2-2200135 and S2-2200922. Approved | Agreed | |
| 8.8 | S2-2200922 | CR | Approval | 23.304 CR0078 (Rel-17, 'F'): SA WG3 Editor's notes Alignment | Huawei, HiSilicon | Rel-17 | Merged into S2-2201303 | Deng Qiang (CATT) proposed this paper merged into S2-2200215r01. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 8.8 | S2-2200370 | CR | Approval | 23.304 CR0065 (Rel-17, 'F'): High-level description of UE-to-Network Relay discovery | LG Electronics | Rel-17 | Approved | ==== 8.X, 9.X, 10.X Final Deadline ==== | Agreed |
| 8.8 | S2-2200371 | CR | Approval | 23.304 CR0066 (Rel-17, 'D'): Editorial fixes related to referred clauses | LG Electronics | Rel-17 | r02 agreed. Revised to S2-2201304. | Judy (Ericsson) provides r01 LaeYoung (LGE) is OK with r01. Hannu (Nokia) agrees with r01 but no earlier versions. Judy (Ericsson) thanks LaeYoung and Hannu for accepting the proposal, and provide r02 with the only change to add Ericsson as co-source. LaeYoung (LGE) is OK with r02. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.8 | S2-2201304 | CR | Approval | 23.304 CR0066R1 (Rel-17, 'F'): Editorial fixes related to referred clauses | LG Electronics, Ericsson | Rel-17 | Revision of S2-2200371r02. Approved | Agreed | |
| 8.8 | S2-2200503 | CR | Approval | 23.304 CR0067 (Rel-17, 'F'): Update to metadata in PC5 Direct Discovery message | Samsung, LG Electronics, Interdigital Inc., Nokia, Nokia Shanghai Bell | Rel-17 | r01 agreed. Revised to S2-2201305. | Judy (Ericsson) ask a question Mehrdad (Samsung) comments Judy (Ericsson) responds to Mehrdad (Samsung) Mehrdad (Samsung) replies to Ericsson and provides r01, only updating the coversheet. Judy (Ericsson) responds to Mehrdad (Samsung). Hannu (Nokia) supports r01. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Mehrdad (Samsung) clarifies to VC that r01 is under approval and seems OK with all parties. LaeYoung (LGE) is fine with r01. Tao(VC) Thanks Mehrdad. Let's check r01 agreeable or not ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.8 | S2-2201305 | CR | Approval | 23.304 CR0067R1 (Rel-17, 'F'): Update to metadata in PC5 Direct Discovery message | Samsung, LG Electronics, Interdigital Inc., Nokia, Nokia Shanghai Bell | Rel-17 | Revision of S2-2200503r01. Approved | Agreed | |
| 8.8 | S2-2200506 | CR | Approval | 23.304 CR0069 (Rel-17, 'F'): Clarification on conflict avoidance between Source Layer-2 IDs | Samsung | Rel-17 | Postponed | Zhang (Ericsson) provides comments Wen (vivo) provides comments Fei (OPPO) asks questions Mehrdad (Samsung) replies to Ericsson and Vivo. Mehrdad (Samsung) replies to OPPO Hong (Qualcomm) comments. Mehrdad (Samsung) replies to Qualcomm. Hong (Qualcomm) replies to Mehrdad. Mehrdad (Samsung) asks for further clarification from Qualcomm Steve (Huawei) comments Sudeep (Apple) has a question to Mehrdad. Mehrdad (Samsung) replies to Qualcomm, Huawei, Apple. Xiaoyan Shi(Interdigital) comments. Sudeep (Apple) responds to Mehrdad. Mehrdad (Samsung) further replies to Qualcomm, InterDigital, Apple. Xiaoyan Shi (Interdigital) replies. Walter (Philips) asks question if this one is going ahead. If so it requires changes. Mehrdad (Samsung) requests to mark this CR as postponed. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Postponed |
| 8.8 | S2-2200697 | CR | Approval | 23.304 CR0072 (Rel-17, 'F'): NAS message type determination | vivo | Rel-17 | r07 agreed. Revised to S2-2201306. | Judy (Ericsson) comments Fei (OPPO) comments and provides r01. Wen (vivo) replies and provides r02. Hannu (Nokia) provides r03 and asks a question. Judy (Ericsson) comments. Fei (OPPO) provides response Fei (OPPO) replies to Judy (Ericsson). Judy (Ericsson) responds to Fei (OPPO). Fei (OPPO) replied to Judy (Ericsson) Deng Qiang (CATT) provides r04. Fei (OPPO) comments on r04. Wen (vivo) tries to provide r05. Steve (Huawei) provides r06 Xiaoyan Shi (Interdigital) provides r07 ==== 8.X, 9.X, 10.X Revisions Deadline ==== Steve (Huawei) is ok with r07. We (vivo) is ok with r07 as well. ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.8 | S2-2201306 | CR | Approval | 23.304 CR0072R1 (Rel-17, 'F'): NAS message type determination | vivo | Rel-17 | Revision of S2-2200697r07. Approved | Agreed | |
| 8.8 | S2-2200698 | CR | Approval | 23.304 CR0073 (Rel-17, 'F'): PC5 QoS rules determination | vivo | Rel-17 | Noted | Yali (OPPO) provides r01. Wen (vivo) is ok with r01. Hong (Qualcomm) comments and does not believe the CR is needed. Hong (Qualcomm) replies to Wen. Wen (vivo) replies. Wen (vivo) replies to Hong. Hannu (Nokia) supports the view of Hong (Qualcomm) that the CR is not needed. Wen (vivo) replies and agree with that this paper is no needed. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 8.8 | S2-2201235 | CR | Approval | 23.304 CR0087 (Rel-17, 'F'): Clarification on Remote UE providing QoS Info | Philips International B.V. | Rel-17 | r01 agreed. Revised to S2-2201307. | Yali (OPPO) comments. Walter (Philips) provides r01 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.8 | S2-2201307 | CR | Approval | 23.304 CR0087R1 (Rel-17, 'F'): Clarification on Remote UE providing QoS Info | Philips International B.V. | Rel-17 | Revision of S2-2201235r01. Approved | Agreed | |
| 8.8 | S2-2200699 | CR | Approval | 23.304 CR0074 (Rel-17, 'F'): User info in discovery message | vivo | Rel-17 | r06 agreed. Revised to S2-2201308. | Zhang (Ericsson) provides comments Wen (vivo) replies Steve (Huawei) comments Xiaoyan Shi (Interdigital) provides comments Hong (Qualcomm) comments. Deng Qiang (CATT) comments. Wen (vivo) replies and provides r01. Wen (vivo) responses to Deng Qiang (CATT). Fei (OPPO) comments. Wen (vivo) replies. Wen (vivo) replies and provides r02 Deng Qiang (CATT) comments on r02 and proposes to stick to current discovery models. Deng Qiang (CATT) replies to Wen (vivo). Wen (vivo) replies to Deng Qiang (CATT). Fei (OPPO) replies to Zhana (Ericsson) Fei (OPPO) clarified Wen (vivo) replies and provides r03 Xiaoyan Shi (Interdigital) comments. Wen (vivo) replies and provides r04. Deng Qiang (CATT) r03 is not acceptable to us. Fei (OPPO) asks question on target info Wen (vivo) replies to Fei (OPPO) Walter (Philips) provides r05 Deng Qiang (CATT) can't accept r04 and r05, and object adding any new parameters in discovery message. Fei (OPPO) asks clarification. Walter (Philips) supports the CR Xiaoyan Shi (Interdigital) supports the CR and is fine with r05. Wen (vivo) :Thanks for Xiaoyan and Walter support. Deng Qiang (CATT) provides r06. Wen (vivo) is ok with r06. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.8 | S2-2201308 | CR | Approval | 23.304 CR0074R1 (Rel-17, 'F'): User info in discovery message | vivo | Rel-17 | Revision of S2-2200699r06. Approved | Agreed | |
| 8.8 | S2-2200923 | CR | Approval | 23.502 CR3389 (Rel-17, 'F'): Corrections for 5G ProSe | Huawei, HiSilicon | Rel-17 | Approved | ==== 8.X, 9.X, 10.X Final Deadline ==== | Agreed |
| 8.8 | S2-2201003 | CR | Approval | 23.304 CR0082 (Rel-17, 'F'): Use of discovery Model A and Model B | Nokia, Nokia Shanghai Bell | Rel-17 | r04 agreed. Revised to S2-2201309. | Zhang (Ericsson) provides comments Fei (OPPO) has the same understanding with Zhang (Ericsson) and also proposed to note this CR Hannu (Nokia) comments while I agree with the interpretation, I was not able to find any normative text on this UE option. Fei (OPPO) comments. Deng Qiang (CATT) share the views of Zhang (Ericsson) and Fei (OPPO) and proposed to note this CR. Hannu (Nokia) accepts the comments made so far and proposes to document the outcome of this discussion in r01. Fei (OPPO) indicates r01 is not acceptable. Steve (Huawei) comments Fei (OPPO) comments on r02. Fei (OPPO) clarified. Steve (Huawei) provides r03 Fei (OPPO) provides r04. Mehrdad (Samsung) is OK to reword the NOTEs based on the wording in r03 but still thinks we should keep them both as notes. Mehrdad (Samsung) is OK with r04 Steve (Huawei) is ok with r04 Zhang (Ericsson) is OK with r04 Hannu (Nokia) prefers r03 as more correct but can also live with r04 even though it misuses informative note. Fei (OPPO) responds to Hannu (Nokia) and sugguests to go with r04. Hannu (Nokia) replies to Fei and gives justification on why r03 is more correct than r04. Fei (OPPO) provides further response. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Hannu (Nokia) asks for clarification from Fei. Mehrdad (Samsung) is OK with r04 but we object to other revisions of the CR. ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.8 | S2-2201309 | CR | Approval | 23.304 CR0082R1 (Rel-17, 'F'): Use of discovery Model A and Model B | Nokia, Nokia Shanghai Bell | Rel-17 | Revision of S2-2201003r04. Approved | Agreed | |
| 8.8 | S2-2201225 | CR | Approval | 23.304 CR0086 (Rel-17, 'F'): Clarification on privacy timer | Philips International B.V. | Rel-17 | r02 agreed. Revised to S2-2201310. | Xiaoyan Shi (Interdigital) comments and provides r01. Deng Qiang (CATT) comments. Mehrdad (Samsung) provides r02. Fei (OPPO) comments and is ok with r02. Walter (Philips) responds to the comments received and provides r03. Deng Qiang (CATT) comments on r03 and prefers r02. Xiaoyan Shi (Interdigital) prefers r02. Fei (OPPO) comments additional change in r03 not needed and r03 is not acceptable to us. Walter (Philips) ok to go with r02 ==== 8.X, 9.X, 10.X Revisions Deadline ==== Mehrdad (Samsung) is OK with r02 but we object to other revisions of the CR. Hannu (Nokia) has concerns on other versions but can also live with r02. ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.8 | S2-2201310 | CR | Approval | 23.304 CR0086R1 (Rel-17, 'F'): Clarification on privacy timer | Philips International B.V. | Rel-17 | Revision of S2-2201225r02. Approved | Agreed | |
| 8.8 | S2-2200541 | DISCUSSION | Agreement | RSC for Remote UE paging via a 5G ProSe Layer-2 U2N relay. | ASUSTeK | Rel-17 | Noted | Zhang (Ericsson) provides comments Xiaoyan Shi (Interdigital) proposes to NOTE this CR. Hong (Qualcomm) comments that this is not a CR, and it can only be NOTED. Wen (vivo) share same comments. Fei (OPPO) comments. Lider (ASUSTeK) comments. Xiaoyan Shi (interdigital) comments. Lider (ASUSTeK) replies to Xiaoyan . Steve (Huawei) this is not a CR ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 8.8 | S2-2200542 | DISCUSSION | Agreement | New cause for Layer-2 link release due to RRC connection establishment failure. | ASUSTeK | Rel-17 | Noted | Zhang (Ericsson) provides comments Hong (Qualcomm) comments. Fei (OPPO) comments. Lider (ASUSTeK) comments. Steve (Huawei) this is not a CR ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 8.8 | S2-2200543 | DISCUSSION | Agreement | Separating source L2IDs for layer-2 links for relaying Unstructured type traffic. | ASUSTeK | Rel-17 | Noted | Mehrdad (Samsung) thinks being a discussion paper this should be NOTED. Lider (ASUSTeK) reply to Mehrdad, and seeks for other comment. Fei (OPPO) comments Mehrdad (Samsung) replies to ASUSTeK. Lider (ASUSTeK) comments on Mehrdad's NOTE. Steve (Huawei) this is not a CR Zhang (Ericsson) provides comments Hannu (Nokia) agrees to note and proposes an answer to Steve ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 8.8 | S2-2200544 | DISCUSSION | Agreement | Correction on condition for layer-2 link release. | ASUSTeK | Rel-17 | Noted | Lider (ASUSTeK) clarifies that the changes are proposed for alignment with CT1 spec. Steve (Huawei) this is not a CR ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 8.9 | - | - | - | Architectural enhancements for 5G multicast-broadcast services (5MBS) | - | - | Docs:=61 | - | |
| 8.9 | - | - | - | LSs and replies | - | - | Docs:=22 | - | |
| 8.9 | S2-2200021 | LS In | Action | LS from RAN WG3: Reply LS on MBS broadcast service continuity and MBS session identification | RAN WG3 (R3-215977) | Rel-17 | Revision of Postponed S2-2109002 from S2#148E. Noted | LiMeng (Huawei) suggests to mark this LS as noted. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 8.9 | S2-2200025 | LS In | Action | LS from RAN WG3: LS on Feedback on data forwarding solutions for MBS | RAN WG3 (R3-216195) | Rel-17 | Revision of Postponed S2-2109009 from S2#148E. Noted | LiMeng (Huawei) proposes to note this LS ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 8.9 | S2-2200057 | LS In | Action | LS from CT WG4: Reply LS on User plane management in UPF for MBS service | CT WG4 (C4-216598) | Rel-17 | Noted | Robbie (Ericsson) suggests to mark this LS as noted ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 8.9 | S2-2200069 | LS In | Action | LS from SA WG3: LS to SA2 on secondary authentication for multicast PDU session | SA WG3 (S3-214538) | Rel-17 | Responses drafted in S2-2200465 and S2-2200596. Final response in S2-2201311 | ==== 8.X, 9.X, 10.X Final Deadline ==== | Replied to |
| 8.9 | S2-2200465 | LS OUT | Approval | [Draft] Reply LS on secondary authentication for multicast PDU session | Ericsson | Rel-17 | Response to S2-2200069. r03 agreed. Revised to S2-2201311. | LiMeng (Huawei) provides r01. Robbie (Ericsson) provides r02. Robbie (Ericsson) provides r03 to update 'Date of Next TSG SA WG2 Meetings' ==== 8.X, 9.X, 10.X Revisions Deadline ==== Robbie (Ericsson) objects to r01. ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.9 | S2-2201311 | LS OUT | Approval | Reply LS on secondary authentication for multicast PDU session | SA WG2 | Rel-17 | Revision of S2-2200465r03. Approved | Approved | |
| 8.9 | S2-2200596 | LS OUT | Approval | [Draft] Reply to SA WG3 on Secondary Authorization | Huawei, HiSilicon | Rel-17 | Response to S2-2200069. Noted | Thomas (Nokia) comments that S2-2200465 is an alternative reply and only one can be agreed. Thomas prefers the reply in S2-2200465 Zhendong (ZTE): similar view with thomas(nokia) LaeYoung (LGE) has same view with Zhendong (ZTE) and Thomas (Nokia), so proposes to NOTE or MERGE this reply LS into S2-2200465 (Ericsson). ==== 8.X, 9.X, 10.X Revisions Deadline ==== LiMeng (Huawei) proposes to mark this document as NOTED. ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 8.9 | S2-2200072 | LS In | Information | LS from SA WG4: Reply LS on 5MBS preparation of stage 3 work split between SA WG4 and CT WG3 | SA WG4 (S4-211665) | Rel-17 | Noted | LiMeng (Huawei) suggests to mark this LS as noted Thomas (Nokia) suggest to note this incoming LS ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 8.9 | S2-2200198 | LS In | Information | LS from CT WG4: Reply LS on 5MBS preparation of stage 3 work split between SA WG4 and CT WG3 | CT WG4 (C4-220307) | Rel-17 | Noted | LiMeng (Huawei) suggests to mark this LS as noted Thomas (Nokia) suggest to note this incoming LS ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 8.9 | S2-2200199 | LS In | Action | LS from CT WG4: LS on MBS session restoration for NG-RAN failure with or without restart | CT WG4 (C4-220308) | Rel-17 | Response drafted in S2-2200466. Final response in S2-2201312 | ==== 8.X, 9.X, 10.X Final Deadline ==== | Replied to |
| 8.9 | S2-2200466 | LS OUT | Approval | [Draft] Reply LS on MBS session restoration for NG-RAN failure with or without restart | Ericsson | Rel-17 | Response to S2-2200199. r09 agreed. Revised to S2-2201312. | Thomas (Nokia) provides r01 Robbie (Ericsson) raises questions on r01 Thomas(Nokia) answers to Robbie (Ericsson) Fenqin (Huawei) comments Zhendong (ZTE): provides r02 Robbie (Ericsson) shares the similar view with Fenqin (Huawei) Thomas(Nokia) replies to Fenqin Thomas (Nokia) provides r03 and objects against r00 and r02 Robbie (Ericsson) comments Thomas (Nokia) replies to Fenqin Robbie (Ericsson) asks. Thomas provides r04 to address the comments of Fenqin Thomas(Nokia) provides r05 to address Robbie´s comment Robbie (Ericsson) provides r06. Thomas (Nokia) prefers r05. Robbie (Ericsson) comments it is Fenqin (Huawei) who provides r07. Thomas (Nokia) comment and provides r07 Robbie (Ericsson) prefers r06 and comments Fenqin (Huawei) correct that it is me provide r07 Thomas (Nokia) comments that in fact Fenqin (Huawei) provided r07 Robbie (Ericsson) provides r08. Robbie (Ericsson) provides r09 to update 'Date of Next TSG SA WG2 Meetings' ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.9 | S2-2201312 | LS OUT | Approval | Reply LS on MBS session restoration for NG-RAN failure with or without restart | SA WG2 | Rel-17 | Revision of S2-2200466r09. Approved | Approved | |
| 8.9 | S2-2200203 | LS In | Action | LS from CT WG4: LS on Location dependent MBS session | CT WG4 (C4-220333) | Rel-17 | Response drafted in S2-2200428. Final response in S2-2201313 | ==== 8.X, 9.X, 10.X Final Deadline ==== | Replied to |
| 8.9 | S2-2200428 | LS OUT | Approval | Reply LS on Location dependent MBS session | Nokia, Nokia Shanghai-Bell | Rel-17 | Response to S2-2200203. r09 agreed. Revised to S2-2201313. | Thomas (Nokia) provides r01 to reflect conclusion of offline discussions Fenqin (Huawei) provides r03 Zhendong (ZTE): provides r02 Judy (Ericsson) comments Fenqin (Huawei) responds Thomas(Nokia) comments against r02 Thomas (Nokia) responds Provides r04. Judy (Ericsson) provides r06. Fenqin (Huawei) provides r05 Thomas(Nokia) comments against r06 that answer to Q6 is insufficient because 'simple solution' is undefined. Fenqin (Huawei) comments. Judy (Ericsson) provides r07. Judy (Ericsson) responds to Fenqin (Huawei). Thomas (Nokia) provides r08. Fenqin (Huawei) provides r09. Fenqin (Huawei) ask a question. Judy (Ericsson) provides r10. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Judy (Ericsson) prefer r10, can accept r09. Fenqin (Huawei) suggest to go with r09. Thomas (Nokia) prefers r09, can accept r10 ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.9 | S2-2201313 | LS OUT | Approval | Reply LS on Location dependent MBS session | SA WG2 | Rel-17 | Revision of S2-2200428r09. Approved | Approved | |
| 8.9 | S2-2200372 | CR | Approval | 23.247 CR0075 (Rel-17, 'F'): Clarification on MBS Session Update procedures | LG Electronics | Rel-17 | r02 agreed. Revised to S2-2201314. | LaeYoung (LGE) provides r01. Judy (Ericsson) asks question Judy (Ericsson) provides r02. LaeYoung (LGE) is OK with r02. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.9 | S2-2201314 | CR | Approval | 23.247 CR0075R1 (Rel-17, 'F'): Clarification on MBS Session Update procedures | LG Electronics, Ericsson | Rel-17 | Revision of S2-2200372r02. Approved | Agreed | |
| 8.9 | S2-2200419 | LS In | Action | LS from RAN WG3: LS on MBS Session Management aspects | RAN WG3 (R3-221468) | Rel-17 | Response drafted in S2-2200885. Final response in S2-2201315 | ==== 8.X, 9.X, 10.X Final Deadline ==== | Replied to |
| 8.9 | S2-2200885 | LS OUT | Approval | [DRAFT] Reply LS on MBS Session Management aspects | Huawei,HiSilicon | Response to S2-2200419. r02 agreed. Revised to S2-2201315. | Judy (Ericsson) provides r01 Zhendong (ZTE): provides comments Judy (Ericsson) responds to Zhendong (ZTE). Zhendong (ZTE): provides response Thomas (Nokia): provides r02 Fenqin (Huawei) is fine with r02 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised | |
| 8.9 | S2-2201315 | LS OUT | Approval | LS Response LS on MBS Session Management aspects | SA WG2 | - | Revision of S2-2200885r02. Approved | Approved | |
| 8.9 | S2-2200420 | LS In | Information | LS from RAN WG3: Reply LS on paging for multicast session activation notification | RAN WG3 (R3-221470) | Rel-17 | Noted | LiMeng (Huawei) suggests to mark this LS as noted. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 8.9 | S2-2201269 | LS In | Action | LS from CT WG4: LS on Clarifications on Namf_MBSCommunication N2MessageTransfer service operation | CT WG4 (C4-221427) | Rel-17 | Postponed | Postponed | |
| 8.9 | - | - | - | Mega CR | - | - | Docs:=2 | - | |
| 8.9 | S2-2200800 | CR | Approval | 23.247 CR0089 (Rel-17, 'F'): Miscellaneous corrections on TS 23.247 | Huawei, HiSilicon | Rel-17 | r05 agreed. Revised to S2-2201316. | Robbie (Ericsson) wonders whether it is mega CR Zhendong (ZTE): proposes to only keep the editoriall part. LiMeng (Huawei) is Okay to remove the controversial parts LiMeng (Huawei) provides r02. LaeYoung (LGE) clarifies that LiMeng (Huawei) provided r01 and provides editorial comment. Robbie (Ericsson) provides r03. LiMeng (Huawei) provides r04. Robbie (Ericsson) provides r05. ==== 8.X, 9.X, 10.X Revisions Deadline ==== LiMeng (Huawei) is fine with r05. ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.9 | S2-2201316 | CR | Approval | 23.247 CR0089R1 (Rel-17, 'F'): Miscellaneous corrections on TS 23.247 | Huawei, HiSilicon, Ericsson | Rel-17 | Revision of S2-2200800r05. Approved | Agreed | |
| 8.9 | - | - | - | General | - | - | Docs:=6 | - | |
| 8.9 | S2-2200470 | CR | Approval | 23.247 CR0081 (Rel-17, 'F'): Resolving ENs, cleanup and corrections | Ericsson | Rel-17 | r02 agreed. Revised to S2-2201317. | Judy (Ericsson) provide r01 to remove the update overlapping with 0374. Thomas (Nokia) provide r02 to remove location dependent service changes. Proposes to focus related discussions in S2-2200425 thread Judy (Ericsson) is fine to discuss the changes related to location dependent and local MBS service in 00425. Judy (Ericsson) responds to Fenqin (Huawei) that there is non-overlapping part thus not merged to 00425, and proposes to proceed the non-overlapping part in this paper. Fenqin (Huawei) propose to merge this paper to 00425. Fenqin (Huawei) agree with Judy and not need merged to 0425 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.9 | S2-2201317 | CR | Approval | 23.247 CR0081R1 (Rel-17, 'F'): Resolving ENs, cleanup and corrections | Ericsson | Rel-17 | Revision of S2-2200470r02. Approved | Agreed | |
| 8.9 | S2-2200374 | CR | Approval | 23.247 CR0077 (Rel-17, 'D'): Adding a heading of clause 5 | LG Electronics | Rel-17 | r01 agreed. Revised to S2-2201318. | LaeYoung (LGE) is OK with r01. Judy (Ericsson) provides r01 to add Ericsson in co-source as a result of merging the update from 0470 to this paper. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.9 | S2-2201318 | CR | Approval | 23.247 CR0077R1 (Rel-17, 'D'): Adding a heading of clause 5 | LG Electronics, Ericsson | Rel-17 | Revision of S2-2200374r01. Approved | Agreed | |
| 8.9 | S2-2200546 | CR | Approval | 23.502 CR3361 (Rel-17, 'F'): NRF service operations for MBS | SAMSUNG | Rel-17 | r07 agreed. Revised to S2-2201319. | Judy (Ericsson) provides r01 Thomas(Nokia) suggests to note the CR Youngkyo(Samsung) replies and objects noting it. Fenqin(Huawei) comments and provides r03 Judy (Ericsson) comments. Thomas(Nokia) replies to Youngkyo. Thomas(Nokia) maintains that CR is not required and existing text is sufficient Youngkyo(Samsung) provides r05. Youngkyo(Samsung) replies to Thomas(Nokia) and provides r04. Youngkyo(Samsung) provides r06 Thomas(Nokia) comments against r04 Thomas(Nokia) comments that CR is not required and cover page is still incorrect Youngkyo(Samsung) provides r07 Thomas(Nokia) can live with r07 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.9 | S2-2201319 | CR | Approval | 23.502 CR3361R1 (Rel-17, 'F'): NRF service operations for MBS | Samsung, Ericsson | Rel-17 | Revision of S2-2200546r07. Approved | Agreed | |
| 8.9 | - | - | - | Local and Location dependent MBS | - | - | Docs:=6 | - | |
| 8.9 | S2-2200373 | CR | Approval | 23.247 CR0076 (Rel-17, 'F'): EN resolution on ULI to SMF for local multicast | LG Electronics | Rel-17 | Merged into S2-2201320 | Thomas (Nokia) suggest to merge this contribution into S2-2200425 LaeYoung (LGE) is fine to merge this CR into S2-2200425 (Nokia). ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 8.9 | S2-2200425 | CR | Approval | 23.247 CR0078 (Rel-17, 'F'): Corrections for Location dependent MBS session | Nokia, Nokia Shanghai-Bell | Rel-17 | r08 agreed. Revised to S2-2201320, merging S2-2200373, S2-2200884 and S2-2201135 | Thomas (Nokia) provides r01 to reflect the result of offline discussions and merge contents from overlapping CRs S2-2200884, S2-2200373, S2-2200470 and S2-2201135 Fenqin (Huawei) provides r02 Thomas(Nokia) comments against r02 Fenqin (Huawei) responds. Thomas (Nokia) responds and provides r03 Judy (Ericsson) provides r05, please ignore r04. Thomas(Nokia) provides r06 based on offline discussion, objects against r05. Judy (Ericsson) comments provides r08. Fenqin (Huawei) provides r07. Thomas accepts r08 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.9 | S2-2201320 | CR | Approval | 23.247 CR0078R1 (Rel-17, 'F'): Corrections for Location dependent MBS session | Nokia, Nokia Shanghai-Bell, Ericsson, LG Electronics, Huawei, HiSilicon, ZTE | Rel-17 | Revision of S2-2200425r08, merging S2-2200373, merging S2-2200373 and S2-2200884, merging S2-2200373, S2-2200884 and S2-2201135. Approved | Agreed | |
| 8.9 | S2-2200883 | DISCUSSION | Approval | Clarification of the left issue on local MBS service. | Huawei, HiSilicon | Noted | Thomas (Nokia) comments on proposals Fenqin (Huawei) provides feedback Thomas (Nokia) replies to Fenqin LaeYoung (LGE) provides comment. Fenqin (Huawei) comments. Judy (Ericsson) comments. Judy (Ericsson) responds to Fenqin (Huawei). Fenqin (Huawei) responds to Judy(Ericsson) ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted | |
| 8.9 | S2-2200884 | CR | Approval | 23.247 CR0091 (Rel-17, 'F'): Clarification of the left issue on local MBS service | Huawei, HiSilicon | Rel-17 | Merged into S2-2201320 | Thomas (Nokia) suggest to merge this contribution into S2-2200425 and continue discussion in that thread. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 8.9 | S2-2201135 | CR | Approval | 23.247 CR0097 (Rel-17, 'F'): Resolving the EN in the location dependent service procedure | ZTE | Rel-17 | Merged into S2-2201320 | Thomas (Nokia) suggest to merge this contribution into S2-2200425 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 8.9 | - | - | - | MBMS SAI-like | - | - | Docs:=6 | - | |
| 8.9 | S2-2200468 | CR | Approval | 23.247 CR0080 (Rel-17, 'F'): MBS FAI | Ericsson | Rel-17 | Merged into S2-2201321 | Thomas (Nokia) suggest to merge this contribution into S2-2200958 Robbie (Ericsson) confirms it is merged into S2-2200958 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 8.9 | S2-2200527 | CR | Approval | 23.247 CR0082 (Rel-17, 'F'): MBS identifier for broadcast MBS session | CATT | Rel-17 | Merged into S2-2201321 | Thomas (Nokia) suggest to merge this contribution into S2-2200958 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 8.9 | S2-2200595 | CR | Approval | 23.247 CR0087 (Rel-17, 'F'): Discussion and proposals for MBS SAI | Huawei, HiSilicon | Rel-17 | Merged into S2-2201321 | LiMeng (Huawei) is OK with the merging proposal. Thomas (Nokia) suggest to merge this contribution into S2-2200958 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 8.9 | S2-2200958 | CR | 23.247 CR0092 (Rel-17, 'F'): MBS Broadcast Frequency area Identifier | Nokia, Nokia Shanghai-Bell | Rel-17 | r08 agreed. Revised to S2-2201321, merging S2-2200468, S2-2200527, S2-2200595 and S2-2201132 | Thomas (Nokia) provides r01 to reflect the conclusions of offline discussions LiMeng (Huawei) suggests to use this document as the basis for further discussion for MBS FSA issue. Robbie (Ericsson) provides r03. Thomas(Nokia) comments on r03 and provides r04. Robbie (Ericsson) comments. LiMeng (Huawei) replies. Robbie (Ericsson) comments on r05. Robbie (Ericsson) prefers r03 and comments. LiMeng (Huawei) provides r05 and add Huawei as co-source. LiMeng (Huawei) considers the delta between r03 and r04 can be kept with removing the 'optional' and 'may' of r03. Robbie (Ericsson) provides r07. Thomas(Nokia) provides r06. Zhendong (ZTE): provides r08 Thomas (Nokia) provides r09 Robbie (Ericsson) replies to Thomas (Nokia). ==== 8.X, 9.X, 10.X Revisions Deadline ==== LiMeng (Huawei) prefers r08, is fine with r09, r06 and r05. Robbie (Ericsson) prefers r08. Thomas (Nokia) can accept r08. ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised | |
| 8.9 | S2-2201321 | CR | - | 23.247 CR0092R1 (Rel-17, 'F'): MBS Frequency Selection Area Identifier | Nokia, Nokia Shanghai-Bell, Ericsson, Huawei, HiSilicon, ZTE, CATT | Rel-17 | Revision of S2-2200958r08, merging S2-2200468, merging S2-2200468 and S2-2200527, merging S2-2200468, S2-2200527 and S2-2200595, merging S2-2200468, S2-2200527, S2-2200595 and S2-2201132. Approved | Agreed | |
| 8.9 | S2-2201132 | CR | Approval | 23.247 CR0094 (Rel-17, 'F'): Clarification on the MBS SAI | ZTE | Rel-17 | Merged into S2-2201321 | Thomas (Nokia) suggest to merge this contribution into S2-2200958 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 8.9 | - | - | - | MBS PCC | - | - | Docs:=3 | - | |
| 8.9 | S2-2200469 | CR | Approval | 23.247 CR0004R2 (Rel-17, 'F'): Policy Control for MBS Session | Ericsson, Huawei, HiSilicon | Rel-17 | Revision of (Noted) S2-2108396 from S2#148E. Noted | Thomas (Nokia) raises concern that this CR is an unnecessary late redesign and not a necessary correction. Judy (Ericsson) believes the correction in this paper is essential to resolve ENs, avoid unnecessary MBS radio bearer setup and security risk, see more in 1133 thread. Thomas (Nokia) replies to Judy(Ericsson) Judy (Ericsson) asks questions. Thomas (Nokia) replies to Judy. Zhendong (ZTE): provides comments Mirko (Huawei) comments. Thomas (Nokia) replies to Mirko. Judy (Ericsson) fully supports Mirko's comments and believes that the principles of the functionality/procedures that is needed should be the main input to SA2 design ==== 8.X, 9.X, 10.X Revisions Deadline ==== Judy (Ericsson) agrees with LiMeng (Huawei) that this paper should be NOTED. Tao(VC) let's check merged to 1133 is ok or not LiMeng (Huawei) corrects that this document should be NOTED LiMeng (Huawei) asks if this document can be marked as 'merged into S2-2201133' ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 8.9 | S2-2201133 | CR | Approval | 23.247 CR0095 (Rel-17, 'F'): Resolving the PCC related EN and issue | ZTE | Rel-17 | r02 agreed. Revised to S2-2201322. | Judy (Ericsson) comments that the proposal may require to set up additional MBS QoS Flow (thus additional MBS radio bearer) for no purpose, and may have security risk that any DL traffic will be allowed in MB-UPF. Thomas(Nokia) replies to Judy that her concerns are incorrect. Judy (Ericsson) comments Thomas(Nokia) seems to misunderstand how PCC framework works Thomas(Nokia) comments that Judy (Ericsson) seems to misunderstand how PCC framework works Judy (Ericsson) responds to Thomas(Nokia). Zhendong (ZTE): provides response Zhendong (ZTE): provides clarification Judy (Ericsson) responds to Zhendong (ZTE). Zhendong (ZTE): provides rersponse Judy (Ericsson) responds. Zhendong (ZTE): provides r01 Thomas (Nokia): provides r02 Judy (Ericsson) comments. Thomas(Nokia) replies to Judy (Ericsson). ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.9 | S2-2201322 | CR | Approval | 23.247 CR0095R1 (Rel-17, 'F'): Resolving the PCC related EN and issue | ZTE, Nokia, Nokia Shanghai-Bell | Rel-17 | Revision of S2-2201133r02. Approved | Agreed | |
| 8.9 | - | - | - | Other MBS procedures | - | - | Docs:=16 | - | |
| 8.9 | S2-2200467 | CR | Approval | 23.247 CR0079 (Rel-17, 'F'): Removing UE from Multicast MBS Session | Ericsson, Nokia, Nokia Shanghai Bell | Rel-17 | Approved | ==== 8.X, 9.X, 10.X Final Deadline ==== | Agreed |
| 8.9 | S2-2200528 | CR | Approval | 23.247 CR0083 (Rel-17, 'F'): Corrections to MBS procedures for broadcast Session | CATT | Rel-17 | r06 agreed. Revised to S2-2201323. | Xiaoyan (CATT) provides r01. LiMeng (Huawei) provides r02. Robbie (Ericsson) provides r05 and add Ericsson as co-source. LiMeng (Huawei) provides r04. Ericsson (Robbie) provides r03. Xiaoyan (CATT) provides r06. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.9 | S2-2201323 | CR | Approval | 23.247 CR0083R1 (Rel-17, 'F'): Corrections to MBS procedures for broadcast Session | CATT, Ericsson | Rel-17 | Revision of S2-2200528r06. Approved | Agreed | |
| 8.9 | S2-2200537 | CR | Approval | 23.247 CR0084 (Rel-17, 'F'): Usage of NAS message for UE joining procedure | SAMSUNG | Rel-17 | Postponed | Judy (Ericsson) comments Youngkyo(Samsung) replies. Zhenhua (vivo) comments LiMeng (Huawei) further clarifies. Zhenhua (vivo) clarifies. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Judy (Ericsson) comments. Youngkyo(Samsung) replies to Judy (Ericsson) . Judy (Ericsson) responds to Youngkyo(Samsung). LiMeng (Huawei) replies to Youngkyo (Samsung) . Youngkyo(Samsung) replies to LiMeng (Huawei). Thomas(Nokia) replies Youngkyo(Samsung) replies to Judy. Judy (Ericsson) propose to postpone this paper as the proposed text does not seem to clarify but bring more unclarity. Youngkyo(Samsung) accepts proposal from Judy and let's postpone to the next meeting ==== 8.X, 9.X, 10.X Final Deadline ==== | Postponed |
| 8.9 | S2-2200538 | CR | Approval | 23.247 CR0085 (Rel-17, 'F'): Paging strategy handling for multicast MBS session | SAMSUNG | Rel-17 | r08 agreed. Revised to S2-2201324. | Thomas (Nokia) provides comments Youngkyo(Samsung) replies. Judy (Ericsson) provides r01 LiMeng (Huawei) considers the exact AMF behavior can be based on implementation. Thomas (Nokia) raises concerns against r01 and the original version Youngkyo(Samsung) provides r02. LiMeng (Huawei) asks questions. Judy (Ericsson) comments. Youngkyo(Samsung) replies and provide a revision r03. LiMeng (Huawei) comments. Thomas (Nokia) comments and provides r04 Judy (Ericsson) provide r05. Youngkyo(Samsung) replies to Judy (Ericsson) and provide r06. Judy (Ericsson) responds to Youngkyo(Samsung) and cannot accept the note to delay per-UE paging in non-supporting RAN Youngkyo(Samsung) replies to Judy and provide r07 Judy (Ericsson) provides r08. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Youngkyo(Samsung) would accept r08 in this meeting and provide a comment. Judy (Ericsson) accepts r01, r05, r08, objects to other revisions including r00 ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.9 | S2-2201324 | CR | Approval | 23.247 CR0085R1 (Rel-17, 'F'): Paging strategy handling for multicast MBS session | Samsung, Ericsson | Rel-17 | Revision of S2-2200538r08. Approved | Agreed | |
| 8.9 | S2-2200539 | CR | Approval | 23.247 CR0086 (Rel-17, 'F'): Restoration of multicast MBS session following AN release | SAMSUNG | Rel-17 | r06 agreed. Revised to S2-2201325. | Thomas (Nokia) objects against this CR Youngkyo(Samsung) replies. LiMeng (Huawei) asks question. Judy (Ericsson) comments. Thomas(Nokia) replies to Youngkyo(Samsung). Zhendong (ZTE): similar view with thomas, limeng and judy Youngkyo (Samsung) replies to LiMeng. Youngkyo(Samsung) replies to Judy(Ericsson) and provide r01. Zhendong (ZTE): provides response LiMeng (Huawei) replies to Youngkyo (Samsung). Judy (Ericsson) responds to Youngkyo(Samsung) Youngkyo(Samsung) replies . Judy (Ericsson) comments that AN release is valid use case, but the proposal does not address the use case properly. Thomas(Nokia) comments that his concerns are not resolved by r01. Youngkyo(Samsung) replies to Thomas. Youngkyo(Samsung) replies to LiMeng and Judy Youngkyo(Samsung) replies and provide r02. Judy (Ericsson) provides r03. LiMeng (Huawei) provides r04. Youngkyo(Samsung) provides r05. Thomas(Nokia) provides r06. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Youngkyo(Samsung) is okay with r06. LiMeng (Huawei) prefers r06. Judy (Ericsson) is OK with r06. ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.9 | S2-2201325 | CR | Approval | 23.247 CR0086R1 (Rel-17, 'F'): Restoration of multicast MBS session following AN release | Samsung, Ericsson | Rel-17 | Revision of S2-2200539r06. Approved | Agreed | |
| 8.9 | S2-2200597 | CR | Approval | 23.247 CR0088 (Rel-17, 'F'): Secondary authorization | Huawei, HiSilicon | Rel-17 | Noted | Robbie (Ericsson) asks a question LiMeng (Huawei) replies Robbie (Ericsson) asks LiMeng (Huawei) LaeYoung (LGE) asks a Q. Zhenhua (vivo) replies further Zhenhua (vivo) replies to Laeyoung (LGE). LaeYoung (LGE) provides comments. Robbie (Ericsson) further comments. Zhendong (ZTE): provides comments Zhenhua (vivo) replies to Zhendong (ZTE) Zhenhua (vivo) replies to Robbie (Ericsson). Robbie (Ericsson) asks Zhenhua (vivo). Thomas (Nokia) comments and questions need for the CR Zhenhua (vivo) replies to Thomas (Nokia) and Robbie (Ericsson) Robbie (Ericsson) replies to Zhenhua (vivo) LiMeng (Huawei) further clarifies Youngkyo(Samsung) comments to Zhenhua (vivo) Zhenhua (vivo) replies to Robbie (Ericsson) further Thomas (Nokia) replies to Zhenhua (vivo) Zhenhua (vivo) replies to Youngkyo(Samsung) Zhendong (ZTE): propsoes to Note this CR Robbie (Ericsson) proposes to note this CR ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 8.9 | S2-2201102 | CR | 23.247 CR0093 (Rel-17, 'F'): Indication whether MBS session is active | Nokia, Nokia Shanghai-Bell | Rel-17 | r01 agreed. Revised to S2-2201326. | Robbie (Ericsson) provides r01. Thomas (Nokia) prefers r00, comments on r01. Robbie (Ericsson) prefers r01 and comments on r00. Thomas(Nokia) replies to Robbie Fenqin(Huawei) ask one question for clarification Thomas replies to Fenqin Thomas replies to Robbie Robbie (Ericsson) comments. Robbie (Ericsson) replies to Thomas (Nokia). Robbie (Ericsson) answers to Thomas (Nokia). ==== 8.X, 9.X, 10.X Revisions Deadline ==== Robbie (Ericsson) objects to r00. ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised | |
| 8.9 | S2-2201326 | CR | - | 23.247 CR0093R1 (Rel-17, 'F'): Indication whether MBS session is active | Nokia, Nokia Shanghai-Bell | Rel-17 | Revision of S2-2201102r01. Approved | Agreed | |
| 8.9 | S2-2201134 | CR | Approval | 23.247 CR0096 (Rel-17, 'F'): Calrification on the MBS session Create and update procedure. | ZTE | Rel-17 | r01 agreed. Revised to S2-2201327. | LiMeng (Huawei) comments the relationship with MBS PCC documents (S2-2200469, S2-2201133). Zhendong (ZTE): provides r01 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.9 | S2-2201327 | CR | Approval | 23.247 CR0096R1 (Rel-17, 'F'): Calrification on the MBS session Create and update procedure. | ZTE | Rel-17 | Revision of S2-2201134r01. Approved | Agreed | |
| 8.9 | S2-2200882 | CR | Approval | 23.247 CR0090 (Rel-17, 'F'): Clarification of MBS data forwarding | Huawei, HiSilicon | Rel-17 | CC#4: Postponed to CC#5. CC#5: Postponed | Paul (Ericsson) provides comments and r01. Zhendong (ZTE): provides comments Fenqin (Huawei): provides comments Paul (Ericsson) replies to Fenqin (Huawei) and Zhendong (ZTE). The mechanism in 882 describes how to detect duplicates and is based on a RAN3 agreement for minimization of data loss between supporting gNBs: synchronization of PDCP SN between neighboring gNBs will be achieved in Rel-17 by the following two means: 1) SN added to MBS user data on N3mb (with 'SN' to be converted into a PDCP SN at the gNB) and 2) support of a shared gNB NG-U termination (i.e. a central entity to assign PDCP SN for multiple gNBs). If 882 aims to describe how 1) is applied to HO from non-supporting to supporting RAN nodes, we are of the opinion, that both RAN3 agreed mechanisms as mentioned above need to be described first. Current RAN3 status is that only the agreement exists, but no stage 3 work was performed so far, however, we are fine to progress in SA2 in parallel. Paul (Ericsson) replies to Fenqin (Huawei). Fenqin (Huawei) replies to Paul (Ericsson). Thomas(Nokia) provides r02 to merge S2-2201250. Objects against r01 Zhenhua (vivo) ask Q Fenqin (Huawei) responds Zhenhua (vivo) ask further to Fenqin (Huawei) Fenqin (Huawei) responds to Zhenhua(Vivo) Thomas(Nokia) replies to Zhenhua (vivo) Zhenhua (vivo) replies to Fenqin (Huawei) Fenqin (Huawei) provides r03 As alignment with RAN3 progress, we are supportive to introduce both solutions agreed by RAN3 in stage 2 at this meeting. However, we can't agree to have only one solution described. Hence, prior to an alignment, we propose to wait for RAN3 to progress that topic first. Paul (Ericsson) object to r03, r02 and r00. Fenqin (Huawei) provides response Thomas (Nokia) suggest bringing this to a conference call to try to establish a working assumption Adding sequence numbers to MBS data was proposed by multiple companies for many meetings, and it was always only one company that objected. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Postponed |
| 8.9 | S2-2201152 | CR | Approval | 23.247 CR0098 (Rel-17, 'F'): Minimizing data loss for handover from non-supporting to supporting node | Nokia, Nokia Shanghai-Bell | Rel-17 | Revised to S2-2201250 | Revised | |
| 8.9 | S2-2201250 | CR | Approval | 23.247 CR0098R1 (Rel-17, 'F'): Minimizing data loss for handover from non-supporting to supporting node | Nokia, Nokia Shanghai-Bell | Rel-17 | Revision of S2-2201152. Merged into S2-2201766 | Paul (Ericsson) provides comments and r01. Zhenhua (vivo) ask clarification to Paul (Ericsson). Paul (Ericsson) replies that it is not feasible to ensure in general that the same UP entity in the target NG-RAN handles UP resources for both, PDU Sessions and MBS Sessions. Hence it is up to the UE to detect duplications and request re-transmissions. However, if the understanding is that the UE is in general not able to provide the requested functions, then we suggest to remove this particular optimization altogether. Zhenhua (vivo) replies to Paul (Ericsson) and provides r02. Paul (Ericsson) comments that the new r02 in 7.2.3.5 includes a non-working proposal and objects to it. Fenqin (Huawei) suggest to merge this paper 0882 Thomas(Nokia) agrees to merge this paper into 0882 ==== 8.X, 9.X, 10.X Revisions Deadline ==== Paul (Ericsson) provides comments and objects to all revisions, i.e. r00, r01, r02. This contribution is not agreeable without progress in 0882. ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 8.10 | - | - | - | System enablers for multi-USIM devices (MUSIM) | - | - | Docs:=17 | - | |
| 8.10 | S2-2200019 | LS In | Action | LS from RAN WG2: LS on RAN2 agreements for paging with service indication | RAN WG2 (R2-2111330) | Rel-17 | Revision of Postponed S2-2108998 from S2#148E. Response drafted in S2-2200147. Final response in S2-2201838 | ==== 8.X, 9.X, 10.X Final Deadline ==== | Replied to |
| 8.10 | S2-2200147 | LS OUT | Approval | [DRAFT] LS reply on RAN WG2 agreements for paging with service indication | vivo | Rel-17 | Response to S2-2200019. CC#5: r05 agreed. Revised to S2-2201838. | Lars (Sony) provides r01 Saso (Intel) provides r02 Steve (Huawei) does not think r02 addition is correct Juan Zhang (Qualcomm) prefers r01. Saso (Intel) withdraws r02 Xiaowan (vivo) provides r03 Alessio(Nokia) asks a question: is r03 a duplicate of r01? Nokia is ok with r01. Xiaowan(vivo) confirms r03 is same as r01 Steve (Huawei) r01 and r03 look the same to me ==== 8.X, 9.X, 10.X Revisions Deadline ==== Juan Zhang (Qualcomm) is OK with r03. Lars (Sony) is OK with r03. Saso (Intel) is OK with r03. Steve (Huawei) comments, needs small update to align with the CR. Xiaowan(vivo) proposes to agree r03 with the changes of 1) 'network' -> 'RAN' and 2) attached CR number, in order to fix the comment from Steve (Huawei). R04 is provided to reflect this Steve (Huawei) provides r05 Xiaowan(vivo) is OK with r05 ==== 8.X, 9.X, 10.X Final Deadline ==== Xiaowan(vivo) will propose r05 in CC#4. | Revised |
| 8.10 | S2-2201838 | LS OUT | Approval | LS reply on RAN WG2 agreements for paging with service indication | SA WG2 | Rel-17 | Revision of S2-2200147r05. Approved | Approved | |
| 8.10 | S2-2200143 | CR | Approval | 23.501 CR3467 (Rel-17, 'F'): Correct the MUSIM Connection Release feature | vivo | Rel-17 | r05 agreed. Revised to S2-2201737. | Steve (Huawei) is this needed? Xiaowan(vivo) replies to Steve (Huawei) Steve (Huawei) comments Xiaowan (vivo) replies to Steve (Huawei) and provides r01 Juan Zhang (Qualcomm) provides comments Xiaowan (vivo) replies to Juan (Qualcomm) Juan Zhang (Qualcomm) replies to Xiaowan (vivo) Xiaowan (vivo) replies to Juan Zhang (Qualcomm) Qian (Ericsson) comments and asks a question Saso (Intel) provides r02 Myungjune (LGE) comments Juan Zhang (Qualcomm) provides r03. Xiaowan(vivo) replies Myungjune (LGE) and Qian (Ericsson) , provide r04 Saso (Intel) comments that there 5 occurrences of 'normally registered' in 23..501. Alessio(Nokia) objects to this Cr as it is not resolving a FASMO issue but enhancing the text to taste of the source company. at this point of the release these CRs cannot be approved. Xiaowan (vivo) replies to Alessio(Nokia) what you said is unfair to people have contributed. I try to clarify the technical reason again. Xiaowan(vivo) provides r06 Steve (Huawei) provides r05 Steve (Huawei) comments on r06 Xiaowan(vivo) replies to Steve (Huawei) and Juan(Qualcomm) Juan Zhang (Qualcomm) comments. Xiaowan(vivo) seek clarification from Steve (Huawei) alessio(Nokia) could live with r05 but this is the last revisions we are ready to consider. Xiaowan (vivo) proposes to agree r05 ==== 8.X, 9.X, 10.X Revisions Deadline ==== Juan Zhang (Qualcomm) is OK with r05. Saso (Intel) is OK with r05. Qian (Ericsson) supports r05. Steve (Huawei) is ok with r05. ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.10 | S2-2201737 | CR | Approval | 23.501 CR3467R1 (Rel-17, 'F'): Correct the MUSIM Connection Release feature | vivo | Rel-17 | Revision of S2-2200143r05. Approved | Agreed | |
| 8.10 | S2-2200144 | CR | Approval | 23.501 CR3468 (Rel-17, 'F'): Correction on MUSIM Paging Cause feature | vivo | Rel-17 | r09 agreed. Revised to S2-2201738, merging S2-2200967 | Steve (Huawei) provides r01 Steve (Huawei) provides the correct link to r01. Guillaume (MediaTek Inc.) provides comments and r02. Saso (Intel) comments; ok with r02. Steve (Huawei) comments Xiaowan (vivo) replies and provides r03 Steve (Huawei) comments on r03 Juan Zhang (Qualcomm) can agree r02 or note the CR. Saso (Intel) proposes to agree r02. Lalith (Samsung) proposes r04 Xiaowan (vivo) provides r05 Steve (Huawei) comments on 5GC Xiaowan(vivo) replies Steve (Huawei) Qian (Ericsson) comments and provides r06 Steve (Huawei) comments on r06 Qian (Ericsson) responds Saso (Intel) proposes r07 Steve (Huawei) provides r08 Xiaowan(vivo) is OK for r08 and seconds the view of Steve (Huawei) that RAN can only indicate RAN support. Alessio(Nokia) asks to note this paper as this is not an issue Xiaowan (vivo) clarifies the issue to Alessio(Nokia) Xiaowan (vivo) provides r09 Steve (Huawei) Thanks, r09 is fine for me. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Juan Zhang (Qualcomm) is OK with r09. Alessio(Nokia) as an exception can live with r09 but requests that in the next meetings we stop with non FASMO CRs. Saso (Intel) is OK with r09. Qian (Ericsson) is OK with r09. ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.10 | S2-2201738 | CR | Approval | 23.501 CR3468R1 (Rel-17, 'F'): Correction on MUSIM Paging Cause feature | Vivo, Samsung | Rel-17 | Revision of S2-2200144r09, merging S2-2200967. Approved | Agreed | |
| 8.10 | S2-2200145 | CR | Approval | 23.501 CR3469 (Rel-17, 'F'): Correct PEI used for MUSIM and network subscriptions | vivo | Rel-17 | r06 agreed. Revised to S2-2201739. | Juan Zhang (Qualcomm) provides r01. Steve (Huawei) provides r02 Juan Zhang (Qualcomm) provides r03. Steve (Huawei) comments Xiaowan (vivo) provides comments Juan Zhang (Qualcomm) replies to Steve (Huawei) Juan Zhang (Qualcomm) provides comments Qian (Ericsson) comments Juan Zhang (Qualcomm) replies to Qian (Ericsson) Steve (Huawei) provides r04 Xiaowan (vivo) provides r05 Alessio(Nokia) asks what is the FASMO text that is in the specifications we are correcting that is specific to the MUSIM FEATURE. asks to note as PEI is IMEI and is working for the past few decades in the field. Xiaowan (vivo) encourages to Alessio(Nokia) to review the latest version, it is about 'while the UE in the registered state, the UE shall keep the PEI used for the network authentication????' Xiaowan (vivo) provides r06, to fix the typo 'or' to 'and' ==== 8.X, 9.X, 10.X Revisions Deadline ==== Juan Zhang (Qualcomm) is OK with r06. Alessio(Nokia) as an exception can live with r06 but requests that in the next meetings we stop with non FASMO CRs. Saso (Intel) is OK with r06. Qian (Ericsson) is OK with r06. ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.10 | S2-2201739 | CR | Approval | 23.501 CR3469R1 (Rel-17, 'F'): Correct PEI used for MUSIM and network subscriptions | vivo | Rel-17 | Revision of S2-2200145r06. Approved | Agreed | |
| 8.10 | S2-2200178 | CR | Approval | 23.401 CR3679 (Rel-17, 'F'): MUSIM capabilities in TAU for Emergency attached UE | Intel | Rel-17 | r01 agreed. Revised to S2-2201740. | Qian (Ericsson) comments and provides r01 Saso (Intel) is ok with r01 ==== 8.X, 9.X, 10.X Revisions Deadline ==== Qian (Ericsson) comments and supports to go with r01 ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.10 | S2-2201740 | CR | Approval | 23.401 CR3679R1 (Rel-17, 'F'): MUSIM capabilities in TAU for Emergency attached UE | Intel, Ericsson | Rel-17 | Revision of S2-2200178r01. Approved | Agreed | |
| 8.10 | S2-2200565 | CR | Approval | 23.401 CR3684 (Rel-17, 'F'): Removing 'Registration Area' | MediaTek Inc. | Rel-17 | Approved | ==== 8.X, 9.X, 10.X Final Deadline ==== | Agreed |
| 8.10 | S2-2200967 | CR | 23.501 CR3551 (Rel-17, 'F'): Clarification on paging cause | Samsung | Rel-17 | Merged into S2-2201738 | Steve (Huawei) CR repeats text in previous paragraph, should be noted. Xiaowan (vivo) provides comments and propose to merge the CR into S2-2200144 Lalith(Samsung) replies to Steve (Huawei) Yang (OPPO) has similar concern that the new paragraph is not FASMO. It should be noted. Yang (OPPO) comments Lalith(Samsung) replies to Yang (OPPO) Yang (OPPO) replies Steve (Huawei) comments Laith(Samsung) OK to partially merge into S2-2200144 Lalith(Samsung) comments Juan Zhang (Qualcomm) provides comment. Lalith(Samsung) proposes to merge this into S2-2200144 Lalith(Samsung) replies to Juan Zhang (Qualcomm) and Yang (OPPO) Alessio(Nokia) also agrees this CR is not needed. Lalith(Samsung) indicates this needs to be marked merged into S2-2200144 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged | |
| 8.10 | S2-2200970 | CR | 23.401 CR3688 (Rel-17, 'F'): Clarification on paging cause | Samsung | Rel-17 | Merged into S2-2201800 | Steve (Huawei) CR Repeats text in previous paragraph, should be noted. Xiaowan (vivo) provides comments and propose to merge the CR into S2-2201119 Juan Zhang (Qualcomm) supports HW's comment and proposed to note the CR. Alessio(Nokia)) supports HW's and QCOM comment and proposed to note the CR. Lalith(Samsung) indicates this needs to be marked merged into S2-2201119 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged | |
| 8.10 | S2-2201098 | CR | Approval | 23.401 CR3691 (Rel-17, 'F'): Correction on calculation algorithm of Alternative IMSI to align with RAN WG2 latest agreements | vivo | Rel-17 | Noted | Steve (Huawei) provides r01, so we don't repeat ourselves. Lars (Sony) There is no need for alignment CR. Steve (Huawei) comments alessio(Nokia) comments and objects to this CR as this is a incorrect CR and unhelpful, beyond not being FASMO. Xiaowan (vivo) clarifies the changes is FASMO because it is required by RAN2 LS S2-2201252 Lars (Sony) comments Qian (Ericsson) provides comments Guillaume (MediaTek Inc.) proposes to note the CR for it is incorrect. Xiaowan(vivo) replies Lars (Sony) ok with r01 Juan Zhang (Qualcomm) provides comments Guillaume (MediaTek Inc.) objects to all versions of this CR. Alessio(Nokia) proposes to note the CR for it is incorrect. Xiaowan (vivo) replies the CR reflects RAN2 WA and nothing wrong. But we are OK to note the paper, since we agree a LS S2-2101267 to ask RAN to change their WA and follow SA2 specification. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 8.10 | S2-2201119 | CR | Approval | 23.401 CR3692 (Rel-17, 'F'): Correction on MUSIM Paging Cause feature | vivo | Rel-17 | r04 agreed. Revised to S2-2201741, merging S2-2200968 | Steve (Huawei) provides r01 Steve (Huawei) provides the correct link to r01. Guillaume (MediaTek Inc.) comments and provides r02. Xiaowan (vivo) provides r03 Alessio(Nokia) requests to note this paper. Xiaowan (vivo) clarifies the issue to Alessio(Nokia) Xiaowan (vivo) provides r04 Steve (Huawei) Thanks, r04 is fine for me. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Juan Zhang (Qualcomm) is OK with r04. Alessio(Nokia) as an exception can live with r04 but requests that in the next meetings we stop with non FASMO CRs. Qian (Ericsson) is OK with r04. ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.10 | S2-2201741 | CR | Approval | 23.401 CR3692R1 (Rel-17, 'F'): Correction on MUSIM Paging Cause feature | Vivo, Samsung | Rel-17 | Revision of S2-2201119r04, merging S2-2200968. Approved | Agreed | |
| 8.11 | - | - | - | Architecture aspects for using satellite access in 5G (5GSAT_ARCH) | - | - | Docs:=55 | - | |
| 8.11 | - | - | - | UE location aspects in NTN | - | - | Docs:=32 | - | |
| 8.11 | S2-2200004 | LS In | Action | LS from SA WG3: Reply LS on UE location aspects in NTN | SA WG3 (S3-212306) | Rel-17 | Revision of Postponed S2-2108255 from S2#148E. Final response in S2-2201539 | ==== 8.X, 9.X, 10.X Final Deadline ==== | Replied to |
| 8.11 | S2-2200020 | LS In | Action | LS from RAN WG2: Reply LS on UE location aspects in NTN | RAN WG2 (R2-2111547) | Rel-17 | Revision of Postponed S2-2109000 from S2#148E. Response drafted in S2-2200939. Final response in S2-2201834 | ==== 8.X, 9.X, 10.X Final Deadline ==== | Replied to |
| 8.11 | S2-2200022 | LS In | Action | LS from RAN WG3: Reply LS on UE Location Aspects in NTN | RAN WG3 (R3-216067) | Rel-17 | Revision of Postponed S2-2109005 from S2#148E. Response drafted in S2-2200441. Final response in S2-2201539 | ==== 8.X, 9.X, 10.X Final Deadline ==== | Replied to |
| 8.11 | S2-2200027 | LS In | Action | LS from SA WG3: Reply LS on UE location aspects in NTN | SA WG3 (S3-214394) | Rel-17 | Revision of Postponed S2-2109018 from S2#148E. Final response in S2-2201539 | ==== 8.X, 9.X, 10.X Final Deadline ==== | Replied to |
| 8.11 | S2-2200939 | LS OUT | Approval | [DRAFT] Reply LS on UE location aspects in NTN | Huawei, HiSilicon | Rel-17 | Response to S2-2200020. r04 agreed. Revised to S2-2201834, merging S2-2201038 | Stephen (Qualcomm) points out some limitations and suggests to merge this into S2-2201239 Jingran (OPPO) comments on the TACs for all PLMNs as broadcast TACs in ULI Stefan (Ericsson) provides comments Jingran (OPPO) replies to Stefan. Wanqiang (Huawei) feedback. Hucheng (CATT) comments. Stephen (Qualcomm) comments Hannu (Nokia) proposes r01 along with revision of the attached CR (in separate document) Stephen (Qualcomm) can agree the r02 and agrees to merge in S2-2201239 into this LS Jingran (OPPO) provides r02 Wanqiang (Huawei) is ok with r02 to simplify. Jean Yves (Thales) comments on r02 , that partially answers RAN2 LS Yuxin (Xiaomi) provides r03 with attachment is removed since based on the r02 attachment is not needed Guillaume (MediaTek Inc.): ok with r03 Jean Yves (Thales): provides r04 that completely answer RAN2 questions Wanqiang (Huawei): ok with r04 Hannu (Nokia) also supports r04 Yuxin (Xiaomi) also supports r04 ==== 8.X, 9.X, 10.X Revisions Deadline ==== Leo (Deutsche Telekom) can accept r04, but for the final version of the LS 'RAN3' has to be moved from CC to TO, as there is action on RAN3. Stephen (Qualcomm) agrees the r04 Stefan (Ericsson) OK with r04 ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.11 | S2-2201834 | LS OUT | Approval | LS on Reply LS on UE location aspects in NTN | SA WG2 | Rel-17 | Revision of S2-2200939r04, merging S2-2201038. Approved | Approved | |
| 8.11 | S2-2201239 | LS OUT | Approval | [DRAFT] LS Response to Reply LS on UE location aspects in NTN | Qualcomm Incorporated | Rel-17 | Response to S2-2200020. Merged into S2-2201542 | Wanqiang (Huawei) comments and proposes to shrink the text. Hucheng (CATT) has concerns on the text and proposes to remove unnecessary sentences or use another LS reply as the baseline. Stefan (Ericsson) comments Yuxin (Xiaomi) has the similar comments with Hucheng (CATT) . Hannu (Nokia) proposes to consider this document merged to S2-2200939 Stephen (Qualcomm) agrees to merge S2-2201239 into S2-2200939 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 8.11 | S2-2200441 | LS OUT | Approval | Reply LS on UE Location Aspects in NTN | Ericsson | Rel-17 | Response to S2-2200022. Revised to S2-2201539. | ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.11 | S2-2201539 | LS OUT | Approval | Reply LS on UE Location Aspects in NTN | SA WG2 | Rel-17 | Revision of S2-2200441. Approved | Approved | |
| 8.11 | S2-2200043 | LS In | Action | Use, if any, of network provided 'Indication of country of UE location' | CT WG1 (C1-217150) | Rel-17 | Responses drafted in S2-2200394, S2-2200440, S2-2200567, S2-2200869 and S2-2200936. Final response in S2-2201844 | Hannu (Nokia) proposes to look at the motivation behind sending the country indication to the UE along with reject cause #78. Jean Yves (Thales) rapporteur comments on several LS response proposals and suggest a way forward. Guillaume (MediaTek) repeats comments on this thread (sorry I did miss it earlier) Jean Yves (Thales) answers to Guillaume and repeats rapporteur proposal to keep 2 LS proposal for discussion. Stefan (Ericsson) provides comments Hannu (Nokia) thanks Jean Yves (Thales) for identifying two draft LSs to represent the different views and points out that the network enforcement of UE's PLMN selection was introduced to ensure the legal requirements on roaming and regulatory services (LI, emergency) can be met. Hannu (Nokia) asks how is the UE expected to select the PLMN without knowing the country? Guillaume (MediaTek Inc.) responds to Jean-Yves (Thales) Scott (Inspur) answers Hannu, Jean Yves, Guillaume on the correct way forward for the LS. Scott (Inspur) comments on several LS response proposals and suggest a way forward. Jingran (OPPO) comments on how to reply this LS. Wanqiang (Huawei) comments and proposes to make a decision ASAP. Scott (Inspur) comments on Stepan and Hannu's reply. Yuxin (Xiaomi) comments on discussing the LS reply. Guillaume (MediaTek Inc.) responds to Jingran (OPPO) Jingran (OPPO) replies to Guillaume (MediaTek Inc.). Jean-Yves (Thales) provides answers to Yuxin and promotes consensus. Stefan (Ericsson) replies to Jingran Stefan (Ericsson) replies to Hannu Hannu (Nokia) replies to Guillaume (MediaTek Inc.) Guillaume (MediaTek Inc.): for CC#3 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Replied to |
| 8.11 | S2-2200394 | LS OUT | Approval | [DRAFT] Reply LS on Indication of country of UE location and its use in PLMN selection | MediaTek Inc. | Rel-17 | Response to S2-2200043. Merge into S2-2201844 | Hannu (Nokia) proposes to note draft LS out S2-2200394, 440, 869 and 936 and to use S2-2200567 as the basis for SA2 reply LS. Jean Yves (Thales) proposes to merge this draft LS out with S2-2200869. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 8.11 | S2-2200440 | LS OUT | Approval | Reply LS on Use, if any, of network provided 'Indication of country of UE location' | Ericsson | Rel-17 | Response to S2-2200043. Merge into S2-2201844 | Hannu (Nokia) proposes to note draft LS out S2-2200394, 440, 869 and 936 and to use S2-2200567 as the basis for SA2 reply LS. Jean Yves (Thales) proposes to merge this draft LS out with S2-2200869. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 8.11 | S2-2200567 | LS OUT | Approval | [DRAFT] Reply LS on Use, if any, of network provided 'Indication of country of UE location' | OPPO | Rel-17 | Response to S2-2200043. Merge into S2-2201844 | Hannu (Nokia) proposes to take this LS as the basis for SA2 answer to CT1 (S2-2200043) and provides r01. Guillaume (MediaTek Inc.) proposes to note 567 and take one of 394/440/869/936 as baseline instead Jean Yves (Thales) answers to Guillaume and repeats rapporteur proposal to keep 2 LS proposal for discussion. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Jingran (OPPO) confirms to merge this LS to 869. Hannu (Nokia) confirms the merge of 567 to 869. I only provided S2-2200567r01 as I was not sure whether this LS would be needed, but now the discussion has moved to 869 so this one can be either noted or merged. ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 8.11 | S2-2200869 | LS OUT | Approval | [DRAFT] Reply LS on Use, if any, of network provided Indication of country of UE location | Xiaomi | Rel-17 | Response to S2-2200043. CC#4: r15 agreed. Revised to S2-2201844, merging S2-2200394, S2-2200440, S2-2200567, S2-2200571, S2-2200936 and S2-2200871 | Hannu (Nokia) proposes to note draft LS out S2-2200394, 440, 869 and 936 and to use S2-2200567 as the basis for SA2 reply LS. After discussion on LS in S2-2200043, Hannu (Nokia) proposes r01. Can accept either S2-2200567r01 or S2-2200869r01 with these principles. Guillaume (MediaTek Inc.) provides r02. Hannu (Nokia) agrees with Guillaume (MediaTek Inc.) on the main points, but provides still r03 for reasons below. Guillaume (MediaTek Inc.) provides r04 Guillaume (MediaTek) responds to Hannu (Nokia) Stefan (Ericsson) comments Steve (Huawei) comments Yuxin (Xiaomi) comments Guillaume (MediaTek Inc.): for CC#3 Hannu (Nokia) agrees with the main substance of the LS but adds a clear question for CT1 in order to get decisive conclusion after one round trip. Stefan (Ericsson) comments and provides r06 Hannu (Nokia) agrees with Stefan's text updates but proposes to still ask the question from CT1 in r07. Jean Yves (Thales) comments on r07 Guillaume (MediaTek Inc.) cannot accept r05 or r07, provides r08. Guillaume (MediaTek Inc.) provides r09 Hannu (Nokia) cannot agree r08 as it fails to represent SA2 discussions in this meeting. Provides r09. Hannu (Nokia) warns Guillaume that uploading of r09 failed. Proposes to continue from the simplified r10. Hannu (Nokia) updates his comment to provide r10 with the same contents his earlier revision (r09) as the document upload failed on r09. Guillaume (MediaTek Inc.) objects r10. Provides r11 Steve (Huawei) supports r11. Stefan (Ericsson) supports r11 Yuxin (Xiaomi) also supports r11. Hannu (Nokia) provides r12 ==== 8.X, 9.X, 10.X Revisions Deadline ==== Leo (Deutsche Telekom) proposes to correct a sentence for the final version of the LS Hannu (Nokia) agrees with Leo that the proposed correction is needed. Guillaume (MediaTek Inc.) cannot agree r12. We support r11 or a very simple answer to CT1's question: see r13 Hannu (Nokia) can't agree r13, but completes the answer in r14. Steve (Huawei) r11 or the draft r13 is good. Hannu (Nokia) proposes to mark up this document for CC#4 Hannu (Nokia) asks question and asks Steve to consider r14. Guillaume (MediaTek Inc.) cannot agree with r14 Hannu (Nokia) asks question from Guillaume and provides r15. Hannu (Nokia) replies to Steve Guillaume (MediaTek Inc.) is ok with r15- Steve (Huawei) can live with r15. Stefan (Ericsson) OK with r15 ==== 8.X, 9.X, 10.X Final Deadline ==== Jean Yves (Thales) OK with r15 Scott (Inspur) can live with r15. Hannu (Nokia) replies to Jean Yves and asks for verification of r15 approval in CC#4 but does not expect any discussion on the contents. | Revised |
| 8.11 | S2-2201844 | LS OUT | Approval | Reply LS on Use, if any, of network provided 'Indication of country of UE location' | SA WG2 | Rel-17 | Revision of S2-2200869r15, merging S2-2200394, S2-2200440, S2-2200567, S2-2200571, S2-2200936 and S2-2200871. Approved | Approved | |
| 8.11 | S2-2200936 | LS OUT | Approval | [DRAFT] Reply LS on Use, if any, of network provided 'Indication of country of UE location' | Huawei, HiSilicon | Rel-17 | Response to S2-2200043. Merge into S2-2201844 | Hannu (Nokia) proposes to note draft LS out S2-2200394, 440, 869 and 936 and to use S2-2200567 as the basis for SA2 reply LS. Jean Yves (Thales) proposes to merge this draft LS out with S2-2200869. Wanqiang (Huawei) try to understand the reason to be merged. Jean Yves (Thales) answers to Wanqiang Wanqiang (Huawei) answers to Jean Yves Hannu (Nokia) objects to this LS. I am happy to talk the contents of the LS, but let's use the one in 869 instead. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 8.11 | S2-2200065 | LS In | Action | Reply LS on UE location aspects in NTN | SA WG3 (S3-214360) | Rel-17 | Postponed | ==== 8.X, 9.X, 10.X Final Deadline ==== | Postponed |
| 8.11 | S2-2200079 | LS In | Action | LS from RAN WG2: LS on UE location during initial access in NTN | RAN WG2 (R2-2201881) | Rel-17 | Response drafted in S2-2200408. Final response in S2-2201540 | ==== 8.X, 9.X, 10.X Final Deadline ==== | Replied to |
| 8.11 | S2-2200408 | LS OUT | Approval | [DRAFT] Reply to LS on UE location during initial access in NTN | THALES | Rel-17 | Response to S2-2200079. Merged into S2-2201540 | Stephen (Qualcomm) points out some limitations and suggests to merge this into S2-2201241 Lalith(Samsung) share view with Stephen (Qualcomm) and suggests to merge this into S2-2201241 Jean-Yves (Thales) comments and asks questions on further NGAP CGI determination. Stephen (Qualcomm) provides answers to Jean-Yves (Thales) Wanqiang (Huawei) comments Stefan (Ericsson) support to use S2-2201241 as basis for LS reply Jean Yves (Thales) agrees to merge into S2-2201241 and provides r01 to recap SA2 hypothesis for RAN2/3 Jean Yves (Thales) correct previous mistake: rev1 is to be provided for merged document, so to be considered in S2-2201241 thread ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 8.11 | S2-2201241 | LS OUT | Approval | [DRAFT] LS Response to LS on UE location during initial access in NTN | Qualcomm Incorporated | Rel-17 | Response to S2-2200079. r04 agreed. Revised to S2-2201540, merging S2-2200408 | Jean Yves (Thales) agrees to merge S2-2200408 into S2-2201241 and provides r01 of S2-2201241 to recap SA2 hypothesis for RAN2/3 Chris (Vodafone) provides r02 and disagrees with r00 and r01. Stephen (Qualcomm) provides an r03 Chris (Vodafone) comments that r03 is OK BUT implies some SA2 changes are needed for the AMF redesign. Also add SA3-LI in cc? Yuxin (Xiaomi) also supports r03 Jean Yves (Thales) provides r04 ==== 8.X, 9.X, 10.X Revisions Deadline ==== Stephen (Qualcomm) can agree the r04 Yuxin (Xiaomi) can agree the r04 ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.11 | S2-2201540 | LS OUT | Approval | LS Response to LS on UE location during initial access in NTN | SA WG2 | Rel-17 | Revision of S2-2201241r04, merging S2-2200408. Approved | Approved | |
| 8.11 | S2-2200937 | CR | Approval | 23.501 CR3549 (Rel-17, 'F'): Remove indication of country of UE location for NR satellite access | Huawei, HiSilicon | Rel-17 | r04 agreed. Revised to S2-2201541. | Hannu (Nokia) provides r01 proposing to limit this CR to only TAI indication. Jingran (OPPO) objects r00 and r01. Stefan (Ericsson) provides r02 Jingran (OPPO) can agree the r02 Guillaume (MediaTek Inc.) recommends a new CR number Wanqiang (Huawei) is OK with r02, and request a new CR number Hannu (Nokia) supports the contents of r02 and the proposal to get new CR number and requests to change the title as well. Wanqiang (Huawei) provides r03 with updating the CR title to match the actual change. Stefan (Ericsson) provides r04 adding a missing 'in' Hannu (Nokia) supports r04. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Stephen (Qualcomm) agrees the r04 ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.11 | S2-2201541 | CR | Approval | 23.501 CR3549R1 (Rel-17, 'F'): TAIs reporting corresponding to the Selected PLMN | Huawei, HiSilicon, Ericsson | Rel-17 | Revision of S2-2200937r04. Approved | Agreed | |
| 8.11 | S2-2200938 | CR | Approval | 23.502 CR3390 (Rel-17, 'F'): Remove indication of country of UE location | Huawei, HiSilicon | Rel-17 | Postponed | Hannu (Nokia) requests to postpone this CR and all other removal of country indication CRs until we receive CT1 response to LS out (assumed to be S2-2200869r03). ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Postponed |
| 8.11 | S2-2200438 | CR | Approval | 23.501 CR3502 (Rel-17, 'F'): Removal of indication of country of UE location | Ericsson | Rel-17 | Postponed | Hannu (Nokia) requests to postpone this CR and all other removal of country indication CRs until we receive CT1 response to LS out (assumed to be S2-2200869r03). Guillaume (MediaTek Inc.): for CC#3 Guillaume (MediaTek Inc.): as per CC#3, this should be postponed. Hannu (Nokia) agrees that this should be postponed. Let's focus on the LS. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Postponed |
| 8.11 | S2-2200439 | CR | Approval | 23.502 CR3352 (Rel-17, 'F'): Removal of indication of country of UE location | Ericsson | Rel-17 | Postponed | Hannu (Nokia) requests to postpone this CR and all other removal of country indication CRs until we receive CT1 response to LS out (assumed to be S2-2200869r03). Guillaume (MediaTek Inc.): for CC#3 Guillaume (MediaTek Inc.): as per CC#3, this should be postponed. Hannu (Nokia) agrees that this should be postponed. Let's focus on the LS. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Postponed |
| 8.11 | S2-2200569 | CR | Approval | 23.501 CR3520 (Rel-17, 'F'): The requirement of the indication of the UE location | OPPO | Rel-17 | Postponed | Hannu (Nokia) proposes to consider this merged to S2-220869. Guillaume (MediaTek Inc.): as per CC#3, this should be postponed. Hannu (Nokia) agrees that this should be postponed. Let's focus on the LS. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Postponed |
| 8.11 | S2-2200866 | DISCUSSION | Approval | Discussion on indication of country of UE location. | Xiaomi | Rel-17 | Noted | Hannu (Nokia) proposes to note the discussion paper without conclusion ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 8.11 | S2-2200867 | CR | Approval | 23.501 CR3544 (Rel-17, 'C'): Remove indicaiton of country of UE location from TS23.501 | Xiaomi | Rel-17 | Postponed | Hannu (Nokia) requests to postpone this CR and all other removal of country indication CRs until we receive CT1 response to LS out (assumed to be S2-2200869r03). Guillaume (MediaTek Inc.) disagrees with Hannu (Nokia). It is SA2 responsibility to decide now: it is SA2 that had decided to introduce initially. SA1 responded 'please stop!', CT1 asked 'why is this needed?'. The situation is clear now. Guillaume (MediaTek Inc.): for CC#3 Guillaume (MediaTek Inc.): as per CC#3, this should be postponed. Hannu (Nokia) agrees that this should be postponed. Let's focus on the LS. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Postponed |
| 8.11 | S2-2200868 | CR | Approval | 23.502 CR3384 (Rel-17, 'C'): Remove indicaiton of country of UE location from TS23.502 | Xiaomi | Rel-17 | Postponed | Hannu (Nokia) requests to postpone this CR and all other removal of country indication CRs until we receive CT1 response to LS out (assumed to be S2-2200869r03). Guillaume (MediaTek Inc.) disagrees with Hannu (Nokia). It is SA2 responsibility to decide now: it is SA2 that had decided to introduce initially. SA1 responded 'please stop!', CT1 asked 'why is this needed?'. The situation is clear now.- Guillaume (MediaTek Inc.): for CC#3 Hannu (Nokia) proposes that as per CC#3 discussions, this should be postponed. Let's focus on the LS. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Postponed |
| 8.11 | S2-2200395 | CR | Approval | 23.501 CR3497 (Rel-17, 'F'): NR NTN: Removal of Country of UE Location | MediaTek Inc. | Rel-17 | Postponed | Hannu (Nokia) requests to postpone this CR and all other removal of country indication CRs until we receive CT1 response to LS out (assumed to be S2-2200869r03). Guillaume (MediaTek Inc.): for CC#3 Guillaume (MediaTek Inc.): as per CC#3, this should be postponed. Hannu (Nokia) agrees that this should be postponed. Let's focus on the LS. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Postponed |
| 8.11 | S2-2200396 | CR | Approval | 23.502 CR3349 (Rel-17, 'F'): NR NTN: Removal of Country of UE Location | MediaTek Inc. | Rel-17 | Postponed | Hannu (Nokia) requests to postpone this CR and all other removal of country indication CRs until we receive CT1 response to LS out (assumed to be S2-2200869r03). Guillaume (MediaTek Inc.): for CC#3 Guillaume (MediaTek Inc.): as per CC#3, this should be postponed. Hannu (Nokia) agrees that this should be postponed. Let's focus on the LS. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Postponed |
| 8.11 | - | - | - | Validity of CV #78 | - | - | Docs:=5 | - | |
| 8.11 | S2-2200049 | LS In | Action | LS from CT WG1: LS on validity of cause value #78 | CT WG1 (C1-217451) | Rel-17 | Responses drafted in S2-2200462, S2-2201002 and S2-2201100. Final response in S2-2201845 | ==== 8.X, 9.X, 10.X Final Deadline ==== | Replied to |
| 8.11 | S2-2200462 | LS OUT | Approval | Reply LS on LS on validity of cause value #78 | Ericsson | Rel-17 | Response to S2-2200049. Noted | Haris(Qualcomm) comments and objects to the suggestion for UE to calculate the minimum distance Scott(Inspur) comments on clarification and objection to the suggestion for UE to calculate the timer and minimum distance Lalith (Samsung) comments. Lalith(Samsung) replies to Scott(Inspur) Scott(Inspur)replies to Lalith(Samsung) Lalith(Samsung) comments. Stefan (Ericsson) comments and replies to Haris Hannu (Nokia) shares the view of Scott(Inspur) and comments. Hannu (Nokia) objects to this LS and replies to Stefan Scott(Inspur) shares the view of and comments. Steve (Huawei) comments Hannu (Nokia) shares the concerns of Steve and Scott and proposes to note this LS ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 8.11 | S2-2201002 | LS OUT | Approval | [DRAFT] LS on validity of vause value #78 | Nokia, Nokia Shanghai Bell | Rel-17 | Response to S2-2200049. Merged into S2-2201845 | Hannu (Nokia) proposes to merge this to S2-2201100 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 8.11 | S2-2201100 | LS OUT | Approval | [DRAFT] Reply LS on validity of cause value #78 | Qualcomm | Rel-17 | Response to S2-2200049. CC#4: r07 agreed. Revised to S2-2201845, merging S2-2201002. | Stefan (Ericsson) comments Hannu (Nokia) replies to Stefan (Ericsson) and provides r01. Stefan (Ericsson) replies to Hannu Haris(Qualcomm) provides answers to Stefan (Ericsson) Jean Yves (Thales) comments that CT1 question in LS in only to know if SA2 wants to provides time and distance lower bounds or shall it be left for implementation Stefan (Ericsson) provides r02 Jean Yves (Thales) is OK with r02 Hannu (Nokia) objects to r02. Prefers r01 and can also live with the original version. Stefan (Ericsson) replies to Hannu. Objects to r00 and r01. Steve (Huawei) r02 is ok Stefan (Ericsson) provides r03 without 2nd paragraph Jean Yves (Thales) ok for r03 Steve (Huawei) provides r04 Haris(Qualcomm) provides r05 Steve (Huawei) comments, r05 is not factually correct. Hucheng (CATT) comments and provides r06 Haris(Qualcomm) comments that we can note the LS response Hannu (Nokia) can't agree r06. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Krisztian (Apple) suggests to move forward with r04 or r03. We think comments/questions/concerns about the usefulness of the backoff mechanism should be raised directly in CT1. CT1 did not ask feedback about it, the asked feedback about the optional network signalling of lower bound values. Hannu (Nokia) cannot agree with r03 or r04 as they fail to answer the question. Stefan (Ericsson) prefers r03, r04. Can live with r02, r06. Objects to all other revisions. Steve (Huawei) is ok with r02, r03 & r04 and objects to r05 to r06. Hannu (Nokia) can only agree r05 or r06. Earlier versions r03 and r04 are not acceptable Hannu (Nokia) sees that also r02 has been brought back in the discussion, but that's not agreeable either. Steve (Huawei) asks Hannu a question Hannu (Nokia) replies to Steve ==== 8.X, 9.X, 10.X Final Deadline ==== Jean Yves (Thales) is in line with Stefan comment Haris(Qualcomm) proposes post deadline revision with the following text: 'SA2 would like to thank CT1 for the LS on validity of cause value #78. During the stage-2 design and the preceding study, SA2 did not consider a backoff mechanism where the UE may retry access to the same PLMN based on expiry of a minimum time or the UE moved to a position at a minimum distance away from the location where the cause value #78 was received. SA2 has discussed the topic and there was no consensus on whether the backoff mechanism with values signaled from the network (either for time or distance) is useful or not.' To be discussed/agreed in CC#4 Hannu (Nokia) supports the revision proposed by Haris. Steve (Huawei) is ok with the text proposed. | Revised |
| 8.11 | S2-2201845 | LS OUT | Approval | Reply LS on validity of cause value #78 | SA WG2 | Rel-17 | Revision of S2-2201100r07, merging S2-2201002. Approved | Approved | |
| 8.11 | - | - | - | TAC reporting in ULI | - | - | Docs:=4 | - | |
| 8.11 | S2-2200416 | LS In | Action | LS from RAN WG3: Reply LS on LS on TAC reporting in ULI and support of SAs and FAs for NR Satellite Access (R3-220121/S2-2109337) | RAN WG3 (R3-221370) | Rel-17 | Responses drafted in S2-2200940 and S2-2201243. Final response in S2-2201542 | ==== 8.X, 9.X, 10.X Final Deadline ==== | Replied to |
| 8.11 | S2-2200940 | LS OUT | Approval | [DRAFT] Reply LS on LS on TAC reporting in ULI and support of SAs and FAs for NR Satellite Access | Huawei, HiSilicon | Rel-17 | Response to S2-2200416. r04 agreed. Revised to S2-2201542, merging S2-2201239 | Stephen (Qualcomm) points out some ambiguity and suggests to merge this into S2-2201243 Wanqiang (Huawei) provides reply and propose to use 940 as the basis for the LS out. Stephen (Qualcomm) provides a response to Wanqiang (Huawei) Stefan (Ericsson) provides comments Yuxin (Xiaomi) provides comments Hucheng (CATT) comments Hannu (Nokia) is not sure which LS is being discussed and provides r01 just in case someone wants to agree this one. Stephen (Qualcomm) provides an r02 Wanqiang (Huawei) is ok with r02 Stefan (Ericsson) provides r03 Stephen (Qualcomm) can agree the r03 Yuxin (Xiaomi) can agree the r03 Jean Yves (Thales) can agree the r03 Chris (Vodafone) believes r03 is technically wrong and provides r04. Wanqiang (Huawei) comments on r04 and provides r05. Jingran (OPPO) prefers r05. Chris (Vodafone) thinks r05 is also wrong. Wanqiang (Huawei) provides feedback and also r06. Chris (Vodafone) thinks r06 is still wrong and that R04 is correct. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Stephen (Qualcomm) prefers the r06 followed by r05 and followed by r04 (as a least preferred rev) Wanqiang (Huawei) prefer r06 but ok with r04. ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.11 | S2-2201542 | LS OUT | Approval | LS on Reply LS on LS on TAC reporting in ULI and support of SAs and FAs for NR Satellite Access | SA WG2 | Rel-17 | Revision of S2-2200940r04, merging S2-2201239. Approved | Approved | |
| 8.11 | S2-2201243 | LS OUT | Approval | [DRAFT] LS Response to Reply LS on LS on TAC reporting in ULI and support of SAs and FAs for NR Satellite Access | Qualcomm Incorporated | Rel-17 | Response to S2-2200416. Merged into S2-2201630 | Hucheng (CATT) asks for a clarification. Wanqiang (Huawei) raises some issues and suggests to merge this into S2-2200940 Stephen (Qualcomm) provides responses to the comments from Wanqiang (Huawei) and Hucheng (CATT) Yuxin (Xiaomi) provides comments Hucheng (CATT) provides further comments to Stephen (Qualcomm)'s response. Hannu (Nokia) supports the proposal to merge this into S2-2200940 Stephen (Qualcomm) agrees to merge S2-2201243 into S2-2200940 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 8.11 | - | - | - | EPS support for IoT NTN | - | - | Docs:=0 | - | |
| 8.11 | - | - | - | Other | - | - | Docs:=14 | - | |
| 8.11 | S2-2200417 | LS In | Action | LS from RAN WG3: LS on RAN Initiated Release due to out-of-PLMN area condition | RAN WG3 (R3-221379) | Rel-17 | Postponed | ==== 8.X, 9.X, 10.X Final Deadline ==== | Postponed |
| 8.11 | S2-2200460 | CR | Approval | 23.501 CR3509 (Rel-17, 'F'): Providing lower bound values to UE for backoff mechanism when AMF is not able to serve UE location. | Ericsson | Rel-17 | Noted | Haris(Qualcomm) objects to the CR Hannu (Nokia) shares the comment from Haris(Qualcomm) objects to the CR. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 8.11 | S2-2200461 | CR | Approval | 23.502 CR3354 (Rel-17, 'F'): Providing lower bound values to UE for backoff mechanism when AMF is not able to serve UE location | Ericsson | Rel-17 | Noted | Haris(Qualcomm) objects to the CR Hannu (Nokia) shares the concern of Haris(Qualcomm) and objects to the CR ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 8.11 | S2-2200889 | CR | Approval | 23.501 CR3546 (Rel-17, 'F'): Correction on PLMN selection for satellite access | China Mobile | Rel-17 | Noted | Haris(Qualcomm) objects to the CR ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 8.11 | S2-2200891 | CR | Approval | 23.501 CR3547 (Rel-17, 'B'): Network providing timer and distance information during rejection to registration via satellite access | China Mobile | Rel-17 | Noted | Haris(Qualcomm) objects to the CR ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 8.11 | S2-2200993 | CR | Approval | 23.502 CR3401 (Rel-17, 'B'): UE behavior of handling network provided timer and distance information during rejection to registration via satellite access | China Mobile | Rel-17 | Noted | Haris(Qualcomm) objects to the CR ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 8.11 | S2-2201009 | CR | Approval | 23.501 CR3555 (Rel-17, 'F'): Correction of Mobility Restrictions handling for emergency calls | Nokia, Nokia Shanghai Bell, MediaTek Inc. | Rel-17 | r04 agreed. Revised to S2-2201543. | Stephen (Qualcomm) comments that the CR title and reason for change do not match the CR changes Hannu (Nokia) replies to Stephen (Qualcomm) and provides r01 with updated cover sheet. Steve (Huawei) comments on the change Hannu (Nokia) replies to Steve (Huawei) and explains. Stephen (Qualcomm) provides an r03 Hannu (Nokia) agrees with Stephen and Steve and provides r04. Steve (Huawei) r04 is ok. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Stephen (Qualcomm) agrees the r04 Jean Yves (Thales) is OK with the r04 ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.11 | S2-2201543 | CR | Approval | 23.501 CR3555R1 (Rel-17, 'F'): Correction of Mobility Restrictions handling for emergency calls | Nokia, Nokia Shanghai Bell, MediaTek Inc. | Rel-17 | Revision of S2-2201009r04. Approved | Agreed | |
| 8.11 | S2-2200003 | LS In | Action | LS from CT WG1: LS reply on multiple TACs per PLMN | CT WG1 (C1-213965) | Rel-17 | Revision of Postponed S2-2108252 from S2#148E. Noted | Stefan (Ericsson) proposes to NOTE the LS ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 8.11 | S2-2200006 | LS In | Action | LS from RAN WG2: Response LS on Multiple TACs per PLMN | RAN WG2 (R2-2108888) | Rel-17 | Revision of Postponed S2-2108260 from S2#148E. Noted | Stefan (Ericsson) propsoes to NOTE this LS ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 8.11 | S2-2200398 | CR | Approval | 23.501 CR3498 (Rel-17, 'F'): NR NTN: Correction to TA Handling | MediaTek Inc. | Rel-17 | r02 agreed. Revised to S2-2201544. | Hannu (Nokia) provides r01 to avoid collision with S2-2201009. Guillaume (MediaTek Inc.) ok with r01 Chris (Vodafone) suggest small cover sheet update. Hannu (Nokia) agrees with Chris and provides r02 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.11 | S2-2201544 | CR | Approval | 23.501 CR3498R1 (Rel-17, 'F'): NR NTN: Correction to TA Handling | MediaTek Inc. | Rel-17 | Revision of S2-2200398r02. Approved | Agreed | |
| 8.11 | S2-2200064 | LS In | Information | LS from SA WG3: Reply LS on NTN specific User Consent | SA WG3 (S3-214349) | Rel-17 | Already handled and noted at S2#148E (S2-2108995). Noted | ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 8.11 | S2-2201253 | LS In | Information | LS from RAN WG2: Reply LS on NTN specific User Consent | RAN WG2 (R2-2201754) | Rel-17 | Noted | ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 8.12 | - | - | - | Architecture enhancements for 3GPP support of advanced V2X services - Phase 2 (eV2XARC_Ph2) | - | - | Docs:=1 | - | |
| 8.12 | S2-2200033 | LS In | Action | Reply LS on Tx Profile | RAN WG2 (R2-2111432) | Rel-17 | Revision of Postponed S2-2109372 from S2#148E. Noted | LaeYoung (LGE) proposes to get this LS Noted because no reply is needed. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 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:=13 | - | |
| 8.14 | - | - | - | Incoming LS’s and related | - | - | Docs:=10 | - | |
| 8.14 | S2-2200009 | LS In | Action | LS from RAN WG2: Reply LS on determination of location estimates in local co-ordinates | RAN WG2 (R2-2108957) | Rel-17 | Revision of Postponed S2-2108270 from S2#148E. Response drafted in S2-2200212. Final response in S2-2201545 | ==== 8.X, 9.X, 10.X Final Deadline ==== | Replied to |
| 8.14 | S2-2200212 | LS OUT | Approval | [DRAFT] Response LS on determination of location estimates in local co-ordinates | Ericsson | Rel-17 | Revision of (Noted) S2-2108358 from S2#148E. Response to S2-2200009. r03 agreed. Revised to S2-2201545. | Stephen (Qualcomm) provides an r01 Runze (Huawei) provides r02. Leo (Deutsche Telekom) provides r03. Runze (Huawei) supports r03. Richard (Ericsson) accepts r03 Cai Simon(Nokia) also supports r03 Stephen (Qualcomm) can also agree the r03 Yunjing (CATT) can also agree the r03 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.14 | S2-2201545 | LS OUT | Approval | Response LS on determination of location estimates in local co-ordinates | SA WG2 | Rel-17 | Revision of S2-2200212r03. Approved | Approved | |
| 8.14 | S2-2200197 | LS In | Action | LS from CT WG4: LS on Clarification on Scheduled Location Time | CT WG4 (C4-220306) | Rel-17 | Response drafted in S2-2201023. Final response in S2-2201546 | ==== 8.X, 9.X, 10.X Final Deadline ==== | Replied to |
| 8.14 | S2-2201023 | LS OUT | Approval | [DRAFT] Response LS on Clarification on Scheduled Location Time | CATT | Rel-17 | Response to S2-2200197. r01 agreed. Revised to S2-2201546. | Runze (Huawei) provides suggestion. Cai Simon (Nokia) agrees with the suggestion Yunjing (CATT) replies to Runze (Huawei) and Cai Simon (Nokia). Runze (Huawei) proposes an idea for update the LS. Yunjing (CATT) provides r01. Runze (Huawei) supports R01 and comments the attachment number needs update. Yunjing(CATT) will update the attachment number. Stephen (Qualcomm) can also agree the r01 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.14 | S2-2201546 | LS OUT | Approval | Response LS on Clarification on Scheduled Location Time | SA WG2 | Rel-17 | Revision of S2-2201023r01. Approved | Approved | |
| 8.14 | S2-2201020 | DISCUSSION | Discussion | Discussion on Solutions for HTTP Timeout Issue when Scheduled Location Time Applied. | CATT | Rel-17 | Noted | Richard (Ericsson ) DP is missing a proposal to limit how far in future MT-LR can be scheduled. Yunjing (CATT) also prefers to use 'Proposal#2: without introducing acknowledge message' for all cases. Stephen (Qualcomm) agrees with Richard (Ericsson) and proposes to use 'Proposal#2: without introducing acknowledge message' for all cases ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 8.14 | S2-2201021 | CR | Approval | 23.273 CR0224 (Rel-17, 'F'): Add acknowlege message in scheduled location time mechanism | CATT | Rel-17 | Noted | Richard (Ericsson ) CR is not needed Stephen (Qualcomm) agrees with Richard (Ericsson) that the CR is not needed Runze (Huawei) agrees with Richard and Ake. Yunjing (CATT) is fine to note the CR. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 8.14 | S2-2201022 | CR | Approval | 23.273 CR0225 (Rel-17, 'F'): Update to Scheduled Location Time | CATT | Rel-17 | r03 agreed. Revised to S2-2201547. | Richard (Ericsson ) r01 is provided Yunjing (CATT) asks a question on r01. Runze (Huawei ) comments on r01. Richard (Ericsson ) replies to Runze (Huawei ) and Yunjing (CATT) Runze (Huawei) replies to Richard. Stephen (Qualcomm) comments on the r01 Runze (Huawei) supports the original version. Yunjing (CATT) replies to Stephen (Qualcomm). Yunjing (CATT) prefers r0 based on compare between r0 and r1. Cai Simon(Nokia) comments on the r01, comments from Yunjing (CATT) and Stephen (Qualcomm) Runze (Huawei) supports CATT and Nokia on timeout configuration that 3GPP should leave it to implementation. Cai Simon(Nokia) provides r02 based on r01, Stephen and Yunjing's comments and co-signs Yunjing (CATT) provides r03. Richard (Ericsson ) accepts r03 Stephen (Qualcomm) can also agree the r03 Runze (Huawei) agrees the r03 Cai Simon(Nokia) accepts r03 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.14 | S2-2201547 | CR | Approval | 23.273 CR0225R1 (Rel-17, 'F'): Update to Scheduled Location Time | CATT, Ericsson, Nokia | Rel-17 | Revision of S2-2201022r03. Approved | Agreed | |
| 8.14 | - | - | - | Other | - | - | Docs:=3 | - | |
| 8.14 | S2-2200777 | CR | Approval | 23.273 CR0221 (Rel-17, 'F'): Clarification on location determination for satellite access UE | Huawei, HiSilicon | Rel-17 | Noted | Yunjing (CATT) thinks the CR is already covered by the existing parameter. Runze (Huawei) replies to Yunjing (CATT) Richard (Ericsson) agrees that the CR is not needed ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 8.14 | S2-2201018 | CR | Approval | 23.273 CR0222 (Rel-17, 'F'): Multiple QoS Class applicable procedure | CATT, Samsung | Rel-17 | Approved | ==== 8.X, 9.X, 10.X Final Deadline ==== | Agreed |
| 8.14 | S2-2201019 | CR | Approval | 23.273 CR0223 (Rel-17, 'F'): PLMN Operator Class applicable to SNPN | CATT | Rel-17 | Approved | ==== 8.X, 9.X, 10.X Final Deadline ==== | Agreed |
| 8.15 | - | - | - | Multimedia Priority Service (MPS) Phase 2 (MPS2) | - | - | Docs:=6 | - | |
| 8.15 | S2-2200987 | CR | Approval | 23.502 CR3398 (Rel-17, 'F'): SBI Message Priority for MPS | Peraton Labs, CISA ECD, Verizon, AT&T, T-Mobile USA | Rel-17 | CC#4: Postponed to CC#5. CC#5: Postponed | Shabnam (Ericsson) comments that first change is placed in wrong place since AMF does not yet have the subscription information, until step 14. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Postponed |
| 8.15 | S2-2200988 | CR | Approval | 23.501 CR3553 (Rel-17, 'F'): Correction of Subscription-related Priority Mechanism | Peraton Labs, CISA ECD, AT&T, Verizon, T-Mobile USA | Rel-17 | r06 agreed. Revised to S2-2201742. | Dongeun (Samsung) comments. Shabnam (Ericsson) provides additional comments. Robert (Peraton Labs) provides r01. Dongeun (Samsung) provides r02. Dongeun (Samsung) provides r05. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.15 | S2-2201742 | CR | Approval | 23.501 CR3553R1 (Rel-17, 'F'): Correction of Subscription-related Priority Mechanism | Peraton Labs, CISA ECD, AT&T, Verizon, T-Mobile USA | Rel-17 | Revision of S2-2200988r06. Approved | Agreed | |
| 8.15 | S2-2200989 | CR | Approval | 23.502 CR3399 (Rel-17, 'F'): UE Configuration Update support for MPS. | Peraton Labs, CISA ECD, AT&T, Verizon, T-Mobile USA | Rel-17 | r02 agreed. Revised to S2-2201743. | Shabnam (Ericsson) has concerns with this change, as the other two CRs at subscription check can mitigate the issue. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.15 | S2-2201743 | CR | Approval | 23.502 CR3399R1 (Rel-17, 'F'): UE Configuration Update support for MPS. | Peraton Labs, CISA ECD, AT&T, Verizon, T-Mobile USA | Rel-17 | Revision of S2-2200989r02. Approved | Agreed | |
| 8.15 | S2-2200990 | CR | Approval | 23.401 CR3689 (Rel-17, 'F'): Paging priority correction for MPS | Peraton Labs, CISA ECD, AT&T, Verizon, T-Mobile USA | Rel-17 | Approved | ==== 8.X, 9.X, 10.X Final Deadline ==== | Agreed |
| 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:=5 | - | |
| 8.21 | S2-2200475 | CR | Approval | 23.502 CR3355 (Rel-17, 'F'): Correction to Nnef_AMInfluence_Create | Ericsson | Rel-17 | Approved | ==== 8.X, 9.X, 10.X Final Deadline ==== | Agreed |
| 8.21 | S2-2200824 | CR | Approval | 23.502 CR3379 (Rel-17, 'F'): Correction to Management of AM Policies at SM policy association establishment and termination | Nokia, Nokia Shanghai Bell | Rel-17 | Approved | ==== 8.X, 9.X, 10.X Final Deadline ==== | Agreed |
| 8.21 | S2-2200825 | CR | Approval | 23.502 CR3380 (Rel-17, 'F'): Correction to Processing AF requests to influence AM policies | Nokia, Nokia Shanghai Bell | Rel-17 | r03 agreed. Revised to S2-2201744. | Pallab (Nokia) provides r01 Belen (Ericsson) provides r02. Zhuoyi (China Telecom) provides r03 based on r02. Pallab (Nokia) comments. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Pallab (Nokia) is OK with r03 and proposes to approve r03. ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.21 | S2-2201744 | CR | Approval | 23.502 CR3380R1 (Rel-17, 'F'): Correction to Processing AF requests to influence AM policies | Nokia, Nokia Shanghai Bell | Rel-17 | Revision of S2-2200825r03. Approved | Agreed | |
| 8.21 | S2-2200894 | CR | Approval | 23.503 CR0662R3 (Rel-17, 'F'): Correction to AF-triggered dynamically changing AM policies | Huawei, HiSilicon | Rel-17 | Revision of (Noted) S2-2108587 from S2#148E. Approved | ==== 8.X, 9.X, 10.X Final Deadline ==== | Agreed |
| 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:=7 | - | |
| 8.24 | S2-2200083 | LS In | Action | LS from CT WG1: LS on lists of 5GS forbidden tracking area for non-3GPP access | CT WG1 (C1-220810) | Rel-17 | Response drafted in S2-2201028. Final response in S2-2201745 | ==== 8.X, 9.X, 10.X Final Deadline ==== | Replied to |
| 8.24 | S2-2201028 | LS OUT | Approval | [DRAFT] Reply LS on lists of 5GS forbidden tracking area for non-3GPP access | ZTE | Rel-17 | Response to S2-2200083. r05 agreed. Revised to S2-2201745. | Laurent (Nokia): provides r01 Marco (Huawei): ask clarification Jinguo(ZTE) replies Stefan (Ericsson) comments Myungjune (LGE) comments Laurent (Nokia): answers Myungjune (LGE) comments. Marco (Huawei) comments. Jinguo(ZTE) suggest to discuss the CR in 1029 first . Laurent (Nokia): objects to R00 Jinguo(ZTE) provides r02 Jinguo(ZTE) provides r03 and asks to ignore r02 since it is empty. Marco (Huawei) comments r03. Myungjune (LGE) provides r04 Stefan (Ericsson) provides r05 ==== 8.X, 9.X, 10.X Revisions Deadline ==== Laurent (Nokia): objects to R00, R02. R05 the best Marco (Huawei): OK with r05 ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.24 | S2-2201745 | LS OUT | Approval | Reply LS on lists of 5GS forbidden tracking area for non-3GPP access | SA WG2 | Rel-17 | Revision of S2-2201028r05. Approved | Approved | |
| 8.24 | S2-2200548 | CR | Approval | 23.501 CR3518 (Rel-17, 'F'): Clarification on non-3gpp AN selection | Samsung | Rel-17 | Approved | ==== 8.X, 9.X, 10.X Final Deadline ==== | Agreed |
| 8.24 | S2-2200549 | CR | Approval | 23.502 CR3363 (Rel-17, 'F'): Clarification on non-3gpp AN selection | Samsung | Rel-17 | Approved | ==== 8.X, 9.X, 10.X Final Deadline ==== | Agreed |
| 8.24 | S2-2201029 | CR | Approval | 23.501 CR3556 (Rel-17, 'F'): Clarification on TAI configured for Non 3GPP access | ZTE | Rel-17 | r10 agreed. Revised to S2-2201746. | Laurent (Nokia): provides r01 Jinguo(ZTE) comments and prefer original version. Marco (Huawei) provides comments. Laurent (Nokia): answers Jinguo(ZTE) replies Stefan (Ericsson) comments Marco (Huawei) comments Jinguo(ZTE) reply to Myungjune comment in 1028 Laurent (Nokia): provides r02 Myungjune (LGE) replies to Jinguo (ZTE) Myungjune (LGE) provides r04 Jinguo(ZTE) provides r03 Apostolis (Lenovo) provides questions and comments on r04. Myungjune (LGE) replies to Apostolis (Lenovo) Jinguo(ZTE) comments on r05 provided by Laurent(Nokia) Myungjune (LGE) comments on r05 Laurent (Nokia): provides r06 Laurent (Nokia): provides r05 Marco (Huawei) propose r07 on top of r05 Myungjune (LGE) provides r08 Laurent (Nokia): objects to R00, R03 much prefer R06. strong concern with R04 and R07. I am OK with the change of 'or' to 'and' proposed in NoTE1 by R08 Jinguo(ZTE) is fine with r08 Myungjune (LGE) provides r09 Marco (Huawei) support 08, I can survive to 06 and objects to any others including 00 Laurent (Nokia): explains his future position: R06 is the best Myungjune (LGE) provides r10 Marco (Huawei) is ok with r10 ==== 8.X, 9.X, 10.X Revisions Deadline ==== Jinguo(ZTE) is ok with r10 Laurent (Nokia): objects to R00, R03, R04, R07, R08, R09 Marco (Huawei): ok with r10 , r08, objects from r00 to r06, r09 ==== 8.X, 9.X, 10.X Final Deadline ==== Apostolis (Lenovo) is ok with r10 | Revised |
| 8.24 | S2-2201746 | CR | Approval | 23.501 CR3556R1 (Rel-17, 'F'): Clarification on TAI configured for Non 3GPP access | ZTE, Nokia, Nokia Shanghai Bell, LG Electronics | Rel-17 | Revision of S2-2201029r10. Approved | Agreed | |
| 8.25 | - | - | - | Minimization of Service Interruption (MINT) | - | - | Docs:=28 | - | |
| 8.25 | S2-2200028 | LS In | Action | Reply LS on LS on MINT functionality for Disaster Roaming | SA WG3 (S3-214342) | Rel-17 | Revision of Postponed S2-2109019 from S2#148E. Noted | Hyunsook (LGE) proposes to mark this as NOTE. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 8.25 | S2-2200066 | LS In | Action | Reply LS on LS on MINT functionality for Disaster Roaming | SA WG3 (S3-214416) | Rel-17 | Responses drafted in S2-2200244 and S2-2200261. Final response in S2-2201514 | Hyunsook (LGE) proposes to NOTE this since S2-2201514 replied to this. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Replied to |
| 8.25 | S2-2200048 | LS In | Action | LS on Disaster Roaming Enabled Indication | CT WG1 (C1-217427) | Rel-17 | Noted | Lalith (Samsung) proposes to NOTE this LS Hyunsook (LGE) agrees to NOTE this LS ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 8.25 | S2-2200084 | LS In | Information | LS from CT WG1: Reply LS on UE capabilities indication in UPU | CT WG1 (C1-220811) | Rel-17 | Noted | Lalith (Samsung) proposes to NOTE this LS Hyunsook (LGE) agrees to NOTE this LS ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 8.25 | S2-2201871 | LS In | Information | LS from SA WG3: Reply LS on protection of UE capabilities indication in UPU | SA WG3 (S3-220469) (S3-220469) | Rel-17 | Noted | Tao(VC) add the LS in to the NOTES and ask whether we can NOTE this. Hyunsook (LGE) suggests to mark it as 'NOTED'. Lalith(Samsung) also suggests to mark this LS NOTED ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 8.25 | S2-2200247 | CR | Approval | 23.501 CR3475 (Rel-17, 'F'): Clarification on UE configuration | LG Electronics | Rel-17 | Approved | ==== 8.X, 9.X, 10.X Final Deadline ==== | Agreed |
| 8.25 | S2-2200248 | CR | Approval | 23.501 CR3476 (Rel-17, 'F'): Clarification on UE 5GMM Capability | LG Electronics | Rel-17 | Merged into S2-2201330 | Hyunsook (LGE) proposes to mark this as 'merged into 1105'. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 8.25 | S2-2200264 | CR | Approval | 23.502 CR3332 (Rel-17, 'F'): Delete the EN on disaster roaming revoking | Huawei, HiSilicon | Rel-17 | r05 agreed. Revised to S2-2201328. | Hyunsook (LGE) asks for the clarification. Haiyang (Huawei) responds to Hyunsook (LGE) Lalith(Samsung) comments Haiyang (Huawei) provides r01 Hyunsook (LGE) comments. Chris (Vodafone) provides rev2. Rev 0 and rev 1 are dangerous and hence I object to them. Clause 5.40.5 of TS 23.501 makes it clear that an orderly return is mandatory, not optional. Separately the CR title is dangerously misleading. Lalith(Samsung) comments on r02 Chris (Vodafone) disagrees with Samsung. Hyunsook (LGE) provide a comment. Lalith(Samsung) replies to Chris (Vodafone) Haiyang (Huawei) provides r03 Lalith(Samsung) is OK with r03 Qian (Ericsson) comments and provide r04 Lalith(Samsung) comments on r04 and suggest to go with r03. Chris (Vodafone) provides r05 Haiyang (Huawei) is OK with r05 ==== 8.X, 9.X, 10.X Revisions Deadline ==== Hyunsook (LGE) is OK with r05 Lalith(Samsung) prefers r03 but can live with r05 Qian (Ericsson) comments and proposes to go with r05. ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.25 | S2-2201328 | CR | Approval | 23.502 CR3332R1 (Rel-17, 'F'): Delete the EN on disaster roaming revoking | Huawei, HiSilicon | Rel-17 | Revision of S2-2200264r05. Approved | Agreed | |
| 8.25 | S2-2200265 | CR | Approval | 23.501 CR3479 (Rel-17, 'F'): Delete the EN on disaster roaming revoking | Huawei, HiSilicon | Rel-17 | Approved | ==== 8.X, 9.X, 10.X Final Deadline ==== | Agreed |
| 8.25 | S2-2200332 | CR | Approval | 23.501 CR3490 (Rel-17, 'F'): Disaster Roaming support updates | Ericsson | Rel-17 | Merged into S2-2201330 | Hyunsook (LGE) comments. Qian (Ericsson) propose to mark this as merged into 1105. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 8.25 | S2-2200333 | CR | Approval | 23.502 CR3343 (Rel-17, 'F'): Disaster roaming service indication | Ericsson | Rel-17 | This should be a CR to 23.501. To be revised as 23.501 CR 3580. r02 agreed. Revised to S2-2201832. | Qian (Ericsson) provides r01 Hyunsook (LGE) checks this CR indicates incorrect spec#. Qian (Ericsson) comments. Qian (Ericsson) provides r02 to update the TS and CR number. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Lalith(Samsung) comments based on discussion in S2-2200335 this CR also should be marked postponed. Qian (Ericsson) comments and propose to technically endorse this CR Tao(VC) Lalith and all, can we endorse r02 or not Lalith(Samsung) replies to Tao(VC) and confirm OK to endorse r02 Hyunsook (LGE) thinks we can technically endorse r02 in this meeting. ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.25 | S2-2201832 | CR | Approval | 23.501 CR3580 (Rel-17, 'F'): Disaster roaming service indication | Ericsson | Rel-17 | Revision of S2-2200333r02. Endorsed | Endorsed | |
| 8.25 | S2-2200703 | CR | Approval | 23.501 CR3529 (Rel-17, 'F'): Condition update for disaster roaming | vivo | Rel-17 | Merged into S2-2201330 | Hyunsook (LGE) proposes to mark this as 'merged into 1105'. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Wen (vivo) confirms that this paper is merged into 1105. ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 8.25 | S2-2200704 | CR | Approval | 23.501 CR3530 (Rel-17, 'F'): Disaster roaming disable handling | vivo | Rel-17 | r01 agreed. Revised to S2-2201329. | Hyunsook (LGE) comments. Wen (vivo) provides r01. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Hyunsook (LGE) is OK with r01 Qian (Ericsson) comments Wen(vivo) replies Qian (Ericsson) provides further comments and proposes to add ',registered for Disaster Roaming service,' on top of r01 Wen (vivo) replies Qian (Ericsson) responds Wen (vivo) is ok with Qian (Ericsson)'s proposal of adding ',registered for Disaster Roaming service,' on top of r01 ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.25 | S2-2201329 | CR | Approval | 23.501 CR3530R1 (Rel-17, 'F'): Disaster roaming disable handling | vivo | Rel-17 | Revision of S2-2200704r01. Approved | Agreed | |
| 8.25 | S2-2200865 | CR | 23.501 CR3543 (Rel-17, 'F'): Disaster roaming registration type | Samsung | Rel-17 | Approved | ==== 8.X, 9.X, 10.X Final Deadline ==== | Agreed | |
| 8.25 | S2-2200873 | CR | 23.502 CR3385 (Rel-17, 'F'): Disaster roaming registration type | Samsung | Rel-17 | Approved | ==== 8.X, 9.X, 10.X Final Deadline ==== | Agreed | |
| 8.25 | S2-2201105 | CR | Approval | 23.501 CR3563 (Rel-17, 'F'): Alignment with use of Disaster Roaming Enabled Configuration | Qualcomm Incorporated | Rel-17 | r03 agreed. Revised to S2-2201330, merging S2-2200248, S2-2200332 and S2-2200703 | Haris(Qualcomm) provides r01 Hyunsook (LGE) provides r02 Chris (Vodafone) provides r03 ==== 8.X, 9.X, 10.X Revisions Deadline ==== Hyunsook (LGE) is OK with r03 Qian (Ericsson) supports r03 ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.25 | S2-2201330 | CR | Approval | 23.501 CR3563R1 (Rel-17, 'F'): Alignment with use of Disaster Roaming Enabled Configuration | Qualcomm Incorporated, Ericsson, Samsung, LG Electronics | Rel-17 | Revision of S2-2201105r03, merging S2-2200248, S2-2200332 and S2-2200703. Approved | Agreed | |
| 8.25 | S2-2201116 | CR | Approval | 23.502 CR3412 (Rel-17, 'F'): Alignment with use of Disaster Roaming Enabled Indication | Qualcomm Incorporated | Rel-17 | Merged into S2-2201331 | Hyunsook proposes to mark this as 'merged into 0863'. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 8.25 | S2-2200334 | CR | Approval | 23.502 CR3146R3 (Rel-17, 'F'): Registration procedure improvement for MINT | Ericsson | Rel-17 | Revision of S2-2107253 from S2#147E (Revised and approved in S2-2109313 at S2#148E). Merged into S2-2201515 | Hyunsook (LGE) proposes to mark this as NOTE. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Qian (Ericsson) consider this paper shall be marked as merged into 0245(1515) which is agreed under 8.29. ?? ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 8.25 | S2-2200335 | CR | Approval | 23.502 CR3147R1 (Rel-17, 'F'): Session procedure improvement for MINT | Ericsson | Rel-17 | Revision of (Noted) S2-2107254 from S2#147E. r03 agreed. Revised to S2-2201833. | Lalith(Samsung) comments. Haiyang (Huawei) shares similar view with Lalith (Samsung). Haris(Qualcomm) comments and asks question Qian (Ericsson) comments provides r01 Hyunsook (LGE) comments. Haiyang (Huawei) comments. Qian (Ericsson) comments and provide r02. Chris (Vodafone) supports the need for the H-SMF to get the DR indication. R02 looks OK. Hyunsook (LGE) provides r03. Lalith(Samsung) request to Postpone this CR till we get SA5 LS response. Haris(Qualcomm) comments on SA5 response Haiyang (Huawei) seeks clarification from Chris (Vodafone) Qian (Ericsson) provides some comments Qian (Ericsson) provides comments Qian (Ericsson) provides further comments Lalith (Samsung) comments Chris (Vodafone) comments ==== 8.X, 9.X, 10.X Revisions Deadline ==== Qian (Ericsson) comments and propose to technically endorse the CR Haiyang (Huawei) provides questions to Chris (Vodafone) TAO(VC) can we endorse r03 then Lalith(Samsung) replies to TAO(VC) OK to endorse r03 Chris (Vodafone) replies to Haiyang (Huawei) ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.25 | S2-2201833 | CR | Approval | 23.502 CR3147R2 (Rel-17, 'F'): Session procedure improvement for MINT | Ericsson | Rel-17 | Revision of S2-2200335r03. Endorsed | Endorsed | |
| 8.25 | S2-2200705 | CR | Approval | 23.501 CR3531 (Rel-17, 'F'): Handling of Prevention of signalling overload | vivo | Rel-17 | Noted | Lalith (Samsung) seeks clarification Wen (vivo) replies to Lalith (Samsung) Lalith(Samsung) replies to Wen (vivo) Wen(vivo) replies to Lalith(Samsung) Lalith(Samsung) replies to Wen(vivo) Hyunsook (LGE) asks for the clarification on NG-RAN behavior. Wen (vivo) replies and provides r01. Lalith(Samsung) is OK with r01. Haris(Qualcomm) asks for the requirement to justify the CR Hyunsook (LGE) comments. Wen(vivo) replies and is ok to NOTED in this stage Qian (Ericsson) comments. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 8.25 | S2-2200861 | CR | 23.501 CR3542 (Rel-17, 'F'): Applicability of lists provided by VPLMN | Samsung | Rel-17 | Merged into S2-2201820 | Hyunsook (LGE) proposes to mark this as 'merged into 1105'. Lalith(Samsung) agrees to merge this CR into 1105 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged | |
| 8.25 | S2-2200863 | CR | 23.502 CR3383 (Rel-17, 'F'): Applicability of lists provided by VPLMN | Samsung | Rel-17 | r01 agreed. Revised to S2-2201331, merging S2-2201192 and S2-2201116 | Lalith (Samsung) provides r01. Hyunsook (LGE) comments. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Hyunsook (LGE) is OK with r01 Qian (Ericsson) is OK with r01 ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised | |
| 8.25 | S2-2201331 | CR | - | 23.502 CR3383R1 (Rel-17, 'F'): Applicability of lists provided by VPLMN | Samsung | Rel-17 | Revision of S2-2200863r01, merging S2-2201192 and S2-2201116. Approved | Agreed | |
| 8.26 | - | - | - | Architecture Enhancement for NR Reduced Capability Devices (ARCH_NR_REDCAP) | - | - | Docs:=1 | - | |
| 8.26 | S2-2201166 | CR | Approval | 23.501 CR3573 (Rel-17, 'C'): UE Radio Capability change between RedCap and non-RedCap | Qualcomm Incorporated | Rel-17 | Postponed | Guillaume (MediaTek Inc.) objects to this CR Hannu (Nokia) is also against the present CR version but asks for guidance pointing out that 'do nothing' is bad choice and we should aim at revision of the CR. Guillaume (MediaTek) responds to Hannu Hannu (Nokia) asks to see the proposal from Guillaume (MediaTek) in CR revision, please? Qian (Ericsson) provides comments Miguel (Qualcomm) answers the questions from Steve, Qian and Hannu and provides r01 Guillaume (MediaTek Inc.) objects to r01 and provides r02. Miguel (Qualcomm) objects to r02 clarifies that the UE changing capabilities is always possible, insists on r01. Guillaume (MediaTek Inc.) responds to Miguel (Qualcomm) Steve (Huawei) This needs and requires RAN2 work to complete, which RAN2 have already minuted they won't discuss further. Miguel (Qualcomm) responds to Guillaume that RAN2 discussed 'fallback' issues, this CR has nothing to do with any 'fallback', it is about change of UE radio capabilities, which is allowed and exists today. Provides r02. Guillaume (MediaTek) disagrees with Miguel (Qualcomm) - this is indeed a fallback where a RedCap UE is allowed to fallback to being non-RedCap UE in specific conditions. Of course this implies a change of radio capabilities. Hannu (Nokia) does not want to take any side in whether NR RedCap UE can change its capabilities or not and provides a neutral revision r03 leaving all UE radio capa changes Guillaume (MediaTek Inc.) responds to Hannu Leo (Deutsche Telekom) objects to original version, r01, r02 and r03. Hannu (Nokia) agrees to note this CR now and promises to bring smaller CR to add the missing SR procedure next time. Miguel (Qualcomm) ok to postpone, but believes there's clearly an issue to resolve ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Postponed |
| 8.27 | - | - | - | Architecture support for NB-IoT/eMTC Non-Terrestrial Networks in EPS (IoT_SAT_ARCH_EPS) | - | - | Docs:=17 | - | |
| 8.27 | S2-2201257 | LS In | Information | LS from RAN WG2: Reply LS on IoT NTN extended NAS supervision timers at satellite access | RAN WG2 (R2-2201951) | Rel-17 | Noted | ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 8.27 | S2-2200010 | LS In | Action | LS from RAN WG2: LS on supporting discontinuous coverage in IoT NTN | RAN WG2 (R2-2109213) | Rel-17 | Revision of Postponed S2-2108271 from S2#148E. Noted | Stefan (Ericsson) proposes to note the LS ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 8.27 | S2-2200397 | CR | Approval | 23.401 CR3682 (Rel-17, 'F'): IoT NTN: Removal of Indication of country of UE location | MediaTek Inc. | Rel-17 | Postponed | Hannu (Nokia) requests to postpone this CR and all other removal of country indication CRs until we receive CT1 response to LS out (assumed to be S2-2200869r03). Guillaume (MediaTek Inc.) responds that this was introduced *by SA2* so SA2 holds the responsibility to remove such indication Guillaume (MediaTek Inc.): as per CC#3, this should be postponed. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Postponed |
| 8.27 | S2-2200399 | CR | Approval | 23.401 CR3683 (Rel-17, 'F'): IoT NTN: Alignment of TA Handling for moving cells with NR NTN | MediaTek Inc., Nokia, Nokia Shanghai Bell, Huawei, HiSilicon | Rel-17 | r01 agreed. Revised to S2-2201332. | Chris (Vodafone) provides r01. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Stefan (Ericsson) comments Chris (Vodafone) replies to Stefan (Ericsson) Stefan (Ericsson) replies to Chris Stefan (Ericsson) can accept r01 Chris replies to Stefan's (Ericsson) question ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.27 | S2-2201332 | CR | Approval | 23.401 CR3683R1 (Rel-17, 'F'): IoT NTN: Alignment of TA Handling for moving cells with NR NTN | MediaTek Inc., Nokia, Nokia Shanghai Bell, Huawei, HiSilicon | Rel-17 | Revision of S2-2200399r01. Approved | Agreed | |
| 8.27 | S2-2200418 | LS In | Action | LS from RAN WG3: LS on opens issues for NB-IoT and eMTC support for NTN | RAN WG3 (R3-221406) | Rel-17 | Postponed | ==== 8.X, 9.X, 10.X Final Deadline ==== | Postponed |
| 8.27 | S2-2200572 | CR | Approval | 23.401 CR3685 (Rel-17, 'F'): IoT NTN: The requirement of the indication of the UE location | OPPO | Rel-17 | Postponed | Chris (Vodafone) comments that we should not agree this CR if other CRs are going to remove the indication. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Jingran (OPPO) confirms that this CR should be postpone. Steve (Huawei) suggests noting or postponing, as this is about 'Indication of country of UE location' ==== 8.X, 9.X, 10.X Final Deadline ==== | Postponed |
| 8.27 | S2-2200870 | CR | Approval | 23.401 CR3686 (Rel-17, 'C'): Remove indicaiton of country of UE location from TS23.401 | Xiaomi | Rel-17 | Postponed | Hannu (Nokia) objects to treating the individual CRs on this aspect before the principle has been handled along with LS in S2-22000043. Hannu (Nokia) requests to postpone this CR and all other removal of country indication CRs until we receive CT1 response to LS out (assumed to be S2-2200869r03). Guillaume (MediaTek Inc.) responds that this was introduced *by SA2* so SA2 holds the responsibility to remove such indication ==== 8.X, 9.X, 10.X Revisions Deadline ==== Guillaume (MediaTek) confirms this should be postponed ==== 8.X, 9.X, 10.X Final Deadline ==== | Postponed |
| 8.27 | S2-2201004 | CR | Approval | 23.401 CR3690 (Rel-17, 'F'): Limited service emergency call over satellite | Nokia, Nokia Shanghai Bell | Rel-17 | Approved | ==== 8.X, 9.X, 10.X Final Deadline ==== | Agreed |
| 8.27 | S2-2200080 | LS In | Action | LS from CT WG1: Reply LS on EPS support for IoT NTN in Rel-17 | CT WG1 (C1-220532) | Rel-17 | Responses drafted in S2-2200571 and S2-2200871. Final response in S2-2201844 | ==== 8.X, 9.X, 10.X Final Deadline ==== | Replied to |
| 8.27 | S2-2200571 | LS OUT | Approval | [DRAFT]Reply LS on EPS support for IoT NTN in Rel-17 | OPPO | Rel-17 | Response to S2-2200080. Merged into S2-2201844 | Chris (Vodafone) comments that we should not agree this outgoing LS if CRs are going to remove the indication. Guillaume (MediaTek Inc.) proposes to merge with 869 ==== 8.X, 9.X, 10.X Revisions Deadline ==== Jingran (OPPO) agrees to merge with 869 ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 8.27 | S2-2200871 | LS OUT | Approval | [DRAFT] Reply LS on EPS support for IoT NTN in Rel-17 | Xiaomi | Rel-17 | Response to S2-2200080. Merged into S2-2201844 | Hannu (Nokia) proposes either postponing this LS or at least a revision along the same principle as in 5GSAT_ARCH (related with S2-2200869r03 or later) Stefan (Ericsson) provides r02 Guillaume (MediaTek Inc.) proposes merger with 869 to keep things easier. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 8.27 | S2-2200046 | LS In | Information | Reply LS on EPS support for IoT NTN in Rel-17 | CT WG1 (C1-217258) | Rel-17 | Noted | Guillaume (MediaTek Inc.) proposes to note this LS ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 8.27 | S2-2200412 | LS In | Action | LS from RAN WG2: LS on UE providing Location Information for NB-IoT | RAN WG2 (R2-2201957) | Rel-17 | Response drafted in S2-2201242. Final response in S2-2201333 | ==== 8.X, 9.X, 10.X Final Deadline ==== | Replied to |
| 8.27 | S2-2201242 | LS OUT | Approval | [DRAFT] LS Response to LS on UE providing Location Information for NB-IoT | Qualcomm Incorporated | Rel-17 | Response to S2-2200412. r02 agreed. Revised to S2-2201333. | Chris (Vodafone) objects to r0 and provides r01. Stefan (Ericsson) provides r02 ==== 8.X, 9.X, 10.X Revisions Deadline ==== Guillaume (MediaTek Inc.) supports r02 Jean Yves (Thales) is OK with r02 ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.27 | S2-2201333 | LS OUT | Approval | LS Response to LS on UE providing Location Information for NB-IoT | SA WG2 | Rel-17 | Revision of S2-2201242r02. Approved | Approved | |
| 8.27 | S2-2200413 | LS In | Information | LS from RAN WG2: LS on security concerns for UE providing Location Information for NB-IoT | RAN WG2 (R2-2201958) | Rel-17 | Noted | ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 8.28 | - | - | - | Rel-17 CAT B/C alignment CR(s) due to the work led by other 3GPP Working Groups | - | - | Docs:=51 | - | |
| 8.28 | - | - | - | IMS | - | - | Docs:=9 | - | |
| 8.28 | S2-2200042 | LS In | Action | LS on access to multiple IMS networks via a 5GC network slice | CT WG1 (C1-216839) | Rel-17 | Response drafted in S2-2200129. Postponed | Haris(Qualcomm) This LS can be noted ==== 8.X, 9.X, 10.X Final Deadline ==== | Postponed |
| 8.28 | S2-2200129 | LS OUT | Approval | [DRAFT] Reply LS on access to multiple IMS networks via a 5GC network slice | China Mobile | Response to S2-2200042. Noted | Ashok (Samsung) comments Yi (China Mobile) responds to Ashok. Haris(Qualcomm) comments that the original LS is outdated Yi (China Mobile) is OK to not reply the LS if there is no problem with the conclsion of 00082 . Ashok (Samsung) responds to Yi (China Mobile) Yi (China Mobile) replies to Ashok. Rainer (Nokia) comments. Yi (China Mobile) replies to Ashok and Rainer. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted | |
| 8.28 | S2-2200082 | LS In | Action | LS from CT WG1: LS on progress of FS_eIMS5G2 | CT WG1 (C1-220734) | Rel-17 | Postponed | Haris(Qualcomm) this LS can be noted if LS response in S2-2200324 is agreed Thomas(Nokia) replies to Haris(Qualcomm) that LS response in S2-2200324 is unrelated and not a reply to S2-2200082. That LS is about a different key issue in the FS_eIMS5G2 study ==== 8.X, 9.X, 10.X Final Deadline ==== | Postponed |
| 8.28 | S2-2200204 | LS In | Action | LS from CT WG4: LS on progress of FS_eIMS5G2 | CT WG4 (C4-220445) | Rel-17 | Response drafted in S2-2200324. Final response in S2-2201548 | Haris(Qualcomm) this LS can be noted if LS response in S2-2200324 is agreed ==== 8.X, 9.X, 10.X Final Deadline ==== | Replied to |
| 8.28 | S2-2200324 | LS OUT | Approval | [DRAFT] Reply LS on progress of FS_eIMS5G2 | Nokia, Nokia Shanghai-Bell | Rel-17 | Response to S2-2200204. r02 agreed. Revised to S2-2201548. | Mirko (Huawei) comments and asks about the possibility for an alternative solution. Thomas (Nokia) replies to Shabnam and Mirko Shabnam (Ericsson) the LS response, if to be sent, needs to be updated reflecting the discussion outcome on the CRs. Ericsson position is to do any work in Rel-18. Thomas (Nokia) provides r01 to address Shabnam`s comment. Haris(Qualcomm) comments on r01 Thomas (Nokia) provides r02 to address the comments of Harris ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.28 | S2-2201548 | LS OUT | Approval | Reply LS on progress of FS_eIMS5G2 | SA WG2 | Rel-17 | Revision of S2-2200324r02. Approved | Approved | |
| 8.28 | S2-2200906 | CR | Approval | 23.503 CR0700 (Rel-17, 'B'): Providing IMS home network domain name information in URSP | China Mobile | Rel-17 | Postponed | Josep (DT) comments (editorial). Haris(Qualcomm) objects to the CR George (Ericsson) objects to the CR. This CR is not needed. Ashok (Samsung) comments Rainer (Nokia) asks for clarification. George (Ericsson) provides response Yi (China Mobile) replies to George. Yi (China Mobile) responds and propose to postpone the CR. George (Ericsson) provides comments ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Postponed |
| 8.28 | S2-2200321 | CR | Approval | 23.502 CR3342 (Rel-17, 'F'): Conveying UPF FQDN to IMS nodes | Nokia, Nokia Shanghai-Bell | Rel-17 | Noted | Shabnam (Ericsson) objects to this CR, 3 CT WGs working on studying different pieces of information, SA2 needs to have overall evaluation so propose to postpone to Rel-18. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 8.28 | S2-2200323 | CR | Approval | 23.228 CR1256 (Rel-17, 'F'): Routing of IMS traffic via localized IMS media plane functions | Nokia, Nokia Shanghai-Bell | Rel-17 | Noted | Ashok (Samsung) comments Thomas (Nokia) replies to Ashok Shabnam (Ericsson) same as for 0321, objects to this CR, 3 CT WGs working on studying different pieces of information, SA2 needs to have overall evaluation so propose to postpone to Rel-18. Thomas (Nokia) replies to Shabnam (Ericsson) Shabnam (Ericsson) responds to Thomas. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 8.28 | - | - | - | SCG outside RA for slicing | - | - | Docs:=6 | - | |
| 8.28 | S2-2200026 | LS In | Action | LS from RAN WG3: LS on Clarification of SCG outside RA for slicing | RAN WG3 (R3-216237) | Rel-17 | Revision of Postponed S2-2109012 from S2#148E. Responses drafted in S2-2200507, S2-2200523 and S2-2200846. Final response in S2-2201549 | ==== 8.X, 9.X, 10.X Final Deadline ==== | Replied to |
| 8.28 | S2-2200507 | LS OUT | Approval | [DRAFT] Reply LS on Clarification of SCG outside RA for slicing | Ericsson | Rel-17 | Response to S2-2200026. r02 agreed. Revised to S2-2201549, merging S2-2200771 and S2-2200523 | Alessio (Nokia) provides comments and suggests to go with S2-2200846 Peter Hedman (Ericsson) provides r0x Alessio(Nokia) cannot find r0x provided by Ericsson. Peter Hedman (Ericsson) provides reply Dongeun (Samsung) provides r01 Haiyang (Huawei) agrees with Dongeun (Samsung) Stefano (Qualcomm) provides r02 Peter Hedman (Ericsson) ok with the wording in r02. Alessio(Nokia) provides r03 Dongeun (Samsung) is ok with r02 Haiyang (Huawei) has questions on r03 Peter Hedman (Ericsson) provides comments and ok with r02, r01 and r00, but objects to r03. Alessio(Nokia) replies alessio(Nokia) provides answer. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.28 | S2-2201549 | LS OUT | Approval | Reply LS on Clarification of SCG outside RA for slicing | SA WG2 | Rel-17 | Revision of S2-2200507r02, merging S2-2200771, merging S2-2200771 and S2-2200523. Approved | Approved | |
| 8.28 | S2-2200523 | LS OUT | Approval | [Draft] LS reply on Clarification of SCG outside RA for slicing | QUALCOMM Europe Inc. - Italy | Response to S2-2200026. Merged into S2-2201549 | Peter (Ericsson) provides comments Stefano (Qualcomm) OK to merge into 507. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged | |
| 8.28 | S2-2200846 | LS OUT | Approval | [DRAFT] Reply LS on Clarification of SCG outside RA for slicing | Nokia, Nokia Shanghai Bell | Rel-17 | Response to S2-2200026. Merged into S2-2201335 | Peter (Ericsson) provides comments and suggests to go with S2-2200507 Alessio(Nokia) suggest we keep this LS based on the rationale in the paper in S2-2201085 Stefano (Qualcomm) suggest we proceed with a revision of 507. Peter Hedman (Ericsson) objects to r00 Miguel (Qualcomm) provides r01 to correct Cover sheet (Clauses affected) Miguel (Qualcomm) : wrong Tdoc please disregard previous comment ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 8.28 | S2-2201085 | DISCUSSION | Agreement | Discussion paper related to draft reply LS in S2-2200846. | Nokia, Nokia Shanghai-Bell | Rel-17 | Noted | ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 8.28 | - | - | - | Slice group for cell re-selection | - | - | Docs:=14 | - | |
| 8.28 | S2-2200378 | CR | Approval | 23.501 CR3494 (Rel-17, 'B'): Support slice group for cell re-selection | Samsung | Rel-17 | Merged intoS2-2200847 Postponed). Postponed | Peter (Ericsson) provides comments Jinguo(ZTE) suggest to merge this CR into 508 or 847. Dogneun (Samsung) is ok to merge this CR to 847 ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Postponed |
| 8.28 | S2-2200379 | CR | Approval | 23.502 CR3348 (Rel-17, 'B'): Support slice group for cell re-selection | Samsung | Rel-17 | Merged into S2-2201297 | Peter (Ericsson) provides comments Jinguo(ZTE) suggest to merge this CR into 719 or 918. Dogneun (Samsung) is ok to merge this CR to 0918 ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Merged |
| 8.28 | S2-2201075 | DISCUSSION | Agreement | Discussion on Slice list and priority information for cell reselection | Ericsson | Rel-17 | Noted | ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Noted |
| 8.28 | S2-2200279 | DISCUSSION | Agreement | Discussion on Slice Group and slice priority. | Huawei, HiSilicon | Rel-17 | Noted | ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Noted |
| 8.28 | S2-2200719 | CR | Approval | 23.502 CR3194R2 (Rel-17, 'B'): Support of slice priority and slice group information for cell (re)selection | China Mobile, Ericsson | Rel-17 | Revision of (Noted) S2-2108798 from S2#148E. Merged into S2-2201372 | Jinguo(ZTE) comment that this CR needs to be revised or merged into 918 based on outcome of discussion ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Merged |
| 8.28 | S2-2200012 | LS In | Action | LS on Slice list and priority information for cell reselection | CT WG1 (C1-216256) | Rel-17 | Revision of Postponed S2-2108280 from S2#148E. Response drafted in S2-2201030. CC#2: Moved back to Agenda item 8.28. CC#5: Final response in S2-2201859 | ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Replied to |
| 8.28 | S2-2200017 | LS In | Action | Reply LS on Slice list and priority information for cell reselection | RAN WG2 (R2-2111310) | Rel-17 | Revision of Postponed S2-2108996 from S2#148E. Response drafted in S2-2201030. CC#2: Moved back to Agenda item 8.28. CC#5: Final response in S2-2201859 | ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Replied to |
| 8.28 | S2-2201030 | LS OUT | Approval | [DRAFT] Reply LS on Slice list and priority information for cell reselection | ZTE | Rel-17 | Response to S2-2200017 and S2-2200012. CC#2: Moved back to Agenda item 8.28 for further discussion. CC#4: postponed for further discussion for CC#5. CC#5: r17 agreed. Revised to S2-2201859. | Haiyang (Huawei) provides r01 for per PLMN granularity. Peter Hedman (Ericsson) provides r02 Alessio(Nokia) provides r03 Peter Hedman (Ericsson) provides r03 Haiyang (Huawei) comments DongEun (Samsung) provides r05 Alessio(Nokia) comments Jinguo(ZTE) provide r06 ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== alessio(nokia) cannot live with any revision after r03. Peter Hedman (Ericsson) ok with r06 Dan (China Mobile) ok with r06 alessio(nokia) still retains r03 is what we can agree with. Jinguo(ZTE) asks to discuss this LS at CC#2 Dongeun (Samsung) can only live with r05 and r06 ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== Peter Hedman (Ericsson) provides r07 Alessio(Nokia) provides r08 Jinguo(ZTE) provides r09 Peter Hedman (Ericsson) provides comments Dan(China Mobile) support the LS Jinguo(ZTE)provides r10 Alessio(Nokia) provides r11 alessio(Nokia) informs of a r11 as already advertised on AI#8.29 alessio(Nokia) believes that per PLMN level does not work as it imposes limitations on PLMNs that want to serve a sizeable enterprise/ industrial IOT market. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Haiyang (Huawei) comments to r11 Peter Hedman (Ericsson) objects to r11, proposes that revision depend on outcome of the CRs e.g. r10 can be ok if 00508 is noted and per PLMN granularity CRs are agreed Alessio(Nokia) objects to any LS revision except r11 (or a similar revision) where we allow RAN2 to pick among per PLMN (280) and per PLMN or TA solutions( -847) Haiyang (Huawei) provides clarifications to Alessio (Nokia) ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.28 | S2-2201859 | LS OUT | Approval | Reply LS on Slice list and priority information for cell reselection | SA WG2 | Rel-17 | Revision of S2-2201030r17. Approved | Approved | |
| 8.28 | S2-2200508 | CR | Approval | 23.501 CR3317R2 (Rel-17, 'B'): Enabling slice priority and slice groups for RRM purposes | Ericsson, China Mobile | Rel-17 | Revision of (Noted) S2-2108471 from S2#148E. CC#2: Moved back to Agenda item 8.28 for further discussion. CC#4: This CR was postponed | DongEun(Samsung) ask for clarifications. Peter Hedman (Ericsson) provides reply Peter (Ericsson) provides comments and r01 DongEun(Samsung) comments. Peter Hedman (Ericsson) provides r02 Haiyang (Huawei) comments and provides r03 only focusing on priority Jinguo(ZTE) suggest to discuss whether to send TA list in NSAC information in 2200847 Alessio(Nokia) proposes to merge this in S2-2200847 Jinguo(ZTE) suggests that 0508 can focus on the priority part and 847 can focus on other aspects. Peter Hedman (Ericsson) provides r04 Alessio(Nokia) provides r05 Patrice (Huawei) comments Haiyang(Huawei) provides r06 alessio(nokia) provides r07 ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== Peter Hedman (Ericsson) objects to wording in r05, r06 and 07 with the reasoning as explained below that has not been countered with technical arguments. Peter Hedman (Ericsson) suggests to bring CR up at CC#2 Jinguo(ZTE) comments Haiyang(Huawei) comments and suggests to go with r03 alessio(Nokia) is ok to note the CR since we cannot reach agreement on the way forward on priority. it's a pity as r07 was receiving good support based on the idea the priority is left to the UE. your statement that a slice cannot be prioritized unless the UE immediately establishes a PDU session on it is a bit vague as the cell selection has happened, the UE registers, the UE may even attempt a PDU session establishment and this fails so now what. Note also all slices are first requested without a PDU session. in general this s one arbitrary statement that can be valid in many cases but why forbid a case there this is not valid. we do not understand your logic. Jinguo(ZTE) asks to discuss this LS at CC#2 Dongeun (Samsung) cannot agree with all the revisions Haiyang (Huawei) indicates to Dongeun (Samsung) that r03 is only related to priority, nothing related to the RA Dongeun (Samsung) provides reason to disagree with r03 Haiyang (Huawei) responds to Dongeun (Samsung) Peter Hedman (Ericsson) provides clarifications Dongeun (Samsung) can live with r03 if either 0847 or 0280 are agreed Peter Hedman (Ericsson) Can accept r00, r01, r02, or with slice prioritization aspects only the r04, i.e. objects to r03, r05, r06, r07. ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== Haiyang (Huawei) comments to r04 Peter Hedman (Ericsson) provides replies to Haiyang once more Haiyang (Huawei) responds to Peter Hedman (Ericsson) Haiyang (Huawei) clarifies to Peter Hedman (Ericsson) Haiyang (Huawei) provides r08 for compromise Alessio(Nokia) provides what Nokia could agree with in r09. we are not ok with r08. Peter Hedman (Ericsson) provides r10 alessio(Nokia) cannot live with r10 as some soft descriptions are quite hard. provides r11 ==== 8.X, 9.X, 10.X Revisions Deadline ==== Peter Hedman (Ericsson) objects to r11, is ok with r10 Alessio(Nokia) objects to r10 as it is technically incorrect for the PDU session part. ==== 8.X, 9.X, 10.X Final Deadline ==== | Postponed |
| 8.28 | S2-2200847 | CR | Approval | 23.501 CR3539 (Rel-17, 'B'): Enabling configuration of Network Slice AS Groups | Nokia, Nokia Shanghai Bell | Rel-17 | CC#2: Moved back to Agenda item 8.28 for further discussion. CC#4: This CR was postponed | Peter (Ericsson) provides comments Alessio(nokia) comments that this should be the basis for the documentation Peter Hedman (Ericsson) provides comments Alessio(Nokia) replies Alessio (nokia) comments that RAN2 should not decide that the way the RA is formed changes if this feature is deployed. It is simply not in their remit to make this call. Alessio(Nokia) proposes the way forward Dongeun (Samsung) provides r01 and comments alessio(Nokia) believes the option to allow indication of reused group semantics shall be there (as this is associated to per TA granularity) what slices the UE registers with is up to the UE and the UE should be able to then reselect a cell based on the need to register with a certain slice (and with a priority that it determines). alessio(Nokia) provides r02 Patrice (Huawei) comments Dongeun (Samsung) provides r04 (please ignore r03 which is a mistake) alessio(Nokia) cannot accept r02 and believes we need at least to let the groups for RACH and reselection independent. also a flexible mechanism defined in sA2 to allow more association to groups is not in conflict with any decision in rAN2 to be more restrictive. our mechanism is not per se limited to this release and may support forward compatibility .... so the RAN2 view can remain as is or change without impacting what we define here. Patrice (Huawei) reads the contributions he comments and has concerns when he reads 0847. alessio (nokia) comments that 0847 is based on the current RAN2 view in their meeting minuted and decisions reord (and LSs to us) and also on the majority view on Monday SoH. ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== Peter Hedman (Ericsson) objects to the CR, all revisions alessio(Nokia) this CR is supporting the current RAN2 view and the complexity is not really there... there is no additional complexity at all. alessio(Nokia) asks this to be discussed in CC#2 as this CR aligns with rAN2 agreement so far and the WF in SoH so it should actually be the main cR output... Dongeun (Samsung) can only agree with r02 and r04 and disagree to all other revisions. ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== Jinguo(ZTE) provides r05 to propose a compromise alessio(nokia) provides r06 to propose a compromise (meaning it is called out a certain deployment can offer per PLMN validity only of NSAG but we cannot mandate it.) Dongeun (Samsung) supports r06 as a compromise ==== 8.X, 9.X, 10.X Revisions Deadline ==== Peter Hedman (Ericsson) proposal seems not to be a compromise as keeps the per TA list logic alessio(Nokia) confirms this keep the TA logic and this should be the alternative compliant with current RAN2 assumption we send to rAN2. this and the other CR can only be endorsed at this meeting and RAN2 will decide. Peter Hedman (Ericsson) objects to r00, r01, r02, r03, r04, r05, r06 Guillaume (MediaTek) objects to all revisions of this CR. Dieter (Deutsche Telekom) objects to all revisions of this CR ==== 8.X, 9.X, 10.X Final Deadline ==== | Postponed |
| 8.28 | S2-2200918 | CR | Approval | 23.502 CR3300R1 (Rel-17, 'B'): Enabling configuration of Network Slice AS Groups | Nokia, Nokia Shanghai Bell | Rel-17 | Revision of (Noted) S2-2108866 from S2#148E. CC#2: Moved back to Agenda item 8.28 for further discussion. CC#4: This CR was postponed | Peter (Ericsson) provides comments Dongeun (Samsung) provides r01 and comments ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== Peter Hedman (Ericsson) objects to r00 and cannot find r01 alessio(Nokia) also cannot find r01. since r0 is anyhow aligned with 847 we should keep r0 AND we REQUEST to discuss this at CC#2 together with 847. ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== Jinguo(ZTE) provides r02 alessio(Nokia) comments that this is NOT to say the NSAG is provided in reg complete. it says reg complete is sent if the reg accept includes NSAG. Objects to r02 as it is tech incorrect. so we still are using r00 for this CR. Alessio(Nokia) as already stated ibn 8.29 this is incorrect reading of the text. objects to r02. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Alessio(Nokia) proposes to go to CC#4 unless Jinguo ACK that his revision is wrong technically (he misunderstood the 'complete message' provides the NSAG while the text says the COMPLETE message is sent if the ACCEPT includes NSAG) so we go with r00. Jinguo can you ACK you misread the CR text and this generated R02 needlessly? Jinguo(ZTE) agree with Alessio(Nokia) and withdraw r02 Alessio(Nokia) suggest then to agree r0 Peter Hedman (Ericsson) objects to r00, r01, r02 Guillaume (MediaTek Inc.) objects to all revs of this CR ==== 8.X, 9.X, 10.X Final Deadline ==== | Postponed |
| 8.28 | S2-2200280 | CR | Approval | 23.501 CR3482 (Rel-17, 'F'): Enabling Network Slice Access Stratum groups | Huawei, HiSilicon | Rel-17 | WI Code should be NR_slice-Core. CC#2: Moved back to Agenda item 8.28 for further discussion. CC#4: This CR was postponed | Haiyang (Huawei) provides r01 (as baseline for per PLMN granularity). Peter Hedman (Ericsson) provides comments alessio (Nokia) comments that per TA granularity is assumed in RAN WGs because of the size of the NSAGs Guillaume (MediaTek Inc.) supports the view expressed by Haiyang (Huawei) on granularity. Haiyang (Huawei) responds. Jinguo(ZTE) agrees with Alessio (Nokia), let's focus on per TA granularity according to SoH@CC#1 Jinguo(ZTE) response to Haiyang and Guillaume. Jinguo(ZTE) provides r02 Peter Hedman (Ericsson) provides r03 ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== Peter Hedman (Ericsson) ok with r03 as a compromise if we also can solve the slice prioritization aspects Haiyang (Huawei) is OK with r03. alessio(Nokia) objects to any revision of this document as it is not in line with RAN2 assumption and Monday SoH. proposes this and 847 are technically endorsed and included in a LS to rAN2 which then decides which way to go. there is no technical justification to prefer this until RAN2 says they can live with per PLMN NSAGs. proposes this goes to CC#2 as objected to by nokia. Jinguo(ZTE) asks to discuss at CC#2 Dongeun (Samsung) can only live with r02 and r03 (if this is a way forward) ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== Guillaume (MediaTek Inc.) provides r04 Alessio(Nokia) objects to this CR. in particular as it seems missing the core of the proposal ( is NSAG it per PLMN or not) nor how many groups a slice can be in... Jinguo(ZTE) provides r05 Haiyang (Huawei) agrees with Jinguo (ZTE), provides r06. Haiyang (Huawei) clarifies to Alessio (Nokia). Alessio (nokia) comments r06 is not a solution with per PLMN granularity. saying a value is valid in a PLMN DOES NOT MEAN IT IS UNIQUE in it. Jinguo (ZTE) provides r07 Haiyang (Huawei) provides r08 ==== 8.X, 9.X, 10.X Revisions Deadline ==== Peter Hedman (Ericsson) ok with r08 alessio(Nokia) is ok to technically endorse r08 as the per-PLMN option. we are not ready to assume the per PLMN option is the way to go and RAN2 has to decide as they are the leading group for this feature and for now they assume per TA granularity. they did not ask us to change this assumption. so we can certainly offer this alternative as an option but ultimately they are to pick as the work item is led by RAN2 on this matter. Nokia is also concerned that the association to S-NSSAI of each per PLMN group will be deterministic in PLMN and will disclose the S-NSSAI (or S-NSSAI group). if we remember well NSSAI on RRC is something people did not want to disclose ... Alessio(Nokia) since we are not sure which AI is the discussion on we repeat here we can only accept endorsing r08. alessio(Nokia) if other companies object then we also need to object to this while we were happy to endorse two set of CRs to let RAN2 choose from ==== 8.X, 9.X, 10.X Final Deadline ==== | Postponed |
| 8.28 | S2-2200281 | CR | Approval | 23.502 CR3334 (Rel-17, 'F'): Enabling Network Slice Acess stratum group | Huawei, HiSilicon | Rel-17 | CC#2: Moved back to Agenda item 8.28 for further discussion. CC#4: This CR was postponed | Jinguo(ZTE) provides r01 Peter Hedman (Ericsson) provides r02 ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== Haiyang (Huawei) is OK with r02 Jinguo(ZTE) asks to discuss at CC#2 ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== Guillaume (MediaTek Inc.) provides r03 ==== 8.X, 9.X, 10.X Revisions Deadline ==== Peter Hedman (Ericsson) ok with r03 Alessio(Nokia) objects to this CR (and all its revisions) as it is technically wrong as the configuration of UE with NSASGs must be ACKED by the UE (like when it is configured with NSSRGs). ==== 8.X, 9.X, 10.X Final Deadline ==== | Postponed |
| 8.28 | - | - | - | UPIP | - | - | Docs:=4 | - | |
| 8.28 | S2-2200277 | CR | Approval | 23.401 CR3680 (Rel-17, 'F'): Remove the EN on UPIP for EPS | Huawei, HiSilicon | Rel-17 | WI Code should be UPIP_SEC_LTE. r01 agreed. Revised to S2-2201550. | Haiyang (Huawei) provides r01 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.28 | S2-2201550 | CR | Approval | 23.401 CR3680R1 (Rel-17, 'F'): Remove the EN on UPIP for EPS | Huawei, HiSilicon | Rel-17 | Revision of S2-2200277r01. Approved | Agreed | |
| 8.28 | S2-2200278 | CR | Approval | 23.501 CR3481 (Rel-17, 'F'): Correction on the MME handling for UPIP during interworking | Huawei, HiSilicon | Rel-17 | r03 agreed. Revised to S2-2201551. | Stefan (Ericsson) provides r01 Laurent (Nokia): Supports R01 from Stefan which much clearer Haiyang (Huawei) seeks for clarification Stefan (Ericsson) comments Laurent (Nokia): objects to R00, happy with R01 Haiyang (Huawei) provides r02 Laurent (Nokia): provides r03 Haiyang (Huawei) is OK with r03 ==== 8.X, 9.X, 10.X Revisions Deadline ==== Stefan (Ericsson) OK with r03 ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.28 | S2-2201551 | CR | Approval | 23.501 CR3481R1 (Rel-17, 'F'): Correction on the MME handling for UPIP during interworking | Huawei, HiSilicon | Rel-17 | Revision of S2-2200278r03. Approved | Agreed | |
| 8.28 | - | - | - | Paging subgrouping and PEI | - | - | Docs:=6 | - | |
| 8.28 | S2-2200032 | LS In | Action | LS from RAN WG2: LS on paging subgrouping and PEI | RAN WG2 (R2-2111415) | Rel-17 | Revision of Postponed S2-2109371 from S2#148E. Postponed | ==== 8.X, 9.X, 10.X Final Deadline ==== | Postponed |
| 8.28 | S2-2201187 | CR | Approval | 23.501 CR3576 (Rel-17, 'F'): UE assistance information in NAS needed to avoid PEI increasing power consumption of OTHER UEs | VODAFONE | Rel-17 | Merged into S2-2201345 | Miguel (Qualcomm) has comments and prefers to move forward with S2-2201204 instead Hannu (Nokia) supports the proposal from Miguel (Qualcomm) to move forward with S2-2201204 instead ==== 8.X, 9.X, 10.X Revisions Deadline ==== Qian (Ericsson) supports the previous proposals to go with 1204. ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 8.28 | S2-2201204 | CR | Approval | 23.501 CR3578 (Rel-17, 'F'): Paging Early Indication: Removal of Editor's notes | Qualcomm Incorporated | Rel-17 | CC#4: r07 + changes agreed. Revised to S2-2201846. | Hannu (Nokia) provides r01. Miguel (Qualcomm) OK with r01 Steve (Huawei) comments Miguel (Qualcomm) OK with Steve's suggestion, provides r02 Hannu (Nokia) supports r02 Chris (Vodafone) provides r03. Hannu (Nokia) updates the style in r04 Qian (Ericsson) provides comment on r04 Chris (Vodafone) replies to Ericsson. Hannu (Nokia) comments. Qian (Ericsson) provides further comments Steve (Huawei) provides r05 Miguel (Qualcomm) provides r06 Chris (Vodafone) disagrees with r06 - this is at least a 'should' not a 'may'. Chris (Vodafone) provides r07 ==== 8.X, 9.X, 10.X Revisions Deadline ==== Hannu (Nokia) replies to Qian (Ericsson) and supports r07 Miguel (Qualcomm) is ok with r07 Qian (Ericsson) proposes a way forward. Chris ( Vodafone) is OK with Qian (Ericsson)'s suggestion. Steve (Huawei) comments on the suggestion Qian (Ericsson) comments and propose to add '(See clause 5.4.3)' on top of r07 Steve (Huawei) (resends) comments on the suggestion Hannu (Nokia) supports the proposal from Steve. Steve (Huawei) provides an r08 in drafts with the small addition. Hannu (Nokia) supports r08 and proposes this document for CC#4 hoping to have the document approved in this meeting. ==== 8.X, 9.X, 10.X Final Deadline ==== Miguel (Qualcomm) ok with r07 + adding '(see clause 5.4.3)' and moving 'Paging messages sent to that gNB can increase UE power consumption for other UEs that support Paging Subgrouping based on the UE's temporary ID.' to a NOTE | Revised |
| 8.28 | S2-2201846 | CR | Approval | 23.501 CR3578R1 (Rel-17, 'F'): Paging Early Indication: Removal of Editor's notes | Qualcomm Incorporated | Rel-17 | Revision of S2-2201204r07 + changes. Approved | Agreed | |
| 8.28 | S2-2201208 | CR | Approval | 23.502 CR3417 (Rel-17, 'F'): Paging Early Indication: Removal of Editor's note | Qualcomm Incorporated | Rel-17 | r01 agreed. Revised to S2-2201552. | Miguel (Qualcomm) provides r01 to correct Cover sheet (Clauses affected) ==== 8.X, 9.X, 10.X Revisions Deadline ==== Qian (Ericsson) is ok with r01 ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.28 | S2-2201552 | CR | Approval | 23.502 CR3417R1 (Rel-17, 'F'): Paging Early Indication: Removal of Editor's note | Qualcomm Incorporated | Rel-17 | Revision of S2-2201208r01. Approved | Agreed | |
| 8.28 | - | - | - | eCPSOR_CON | - | - | Docs:=8 | - | |
| 8.28 | S2-2200081 | LS In | Action | LS from CT WG1: LS on Deletion of ME support of SOR-CMCI indicator during Nudm_SDM_Get | CT WG1 (C1-220559) | Rel-17 | Responses drafted in S2-2201013 and S2-2201143. Final response in S2-2201553 | ==== 8.X, 9.X, 10.X Final Deadline ==== | Replied to |
| 8.28 | S2-2201143 | LS OUT | Approval | [DRAFT] Reply LS on Deletion of 'ME support of SOR-CMCI' indicator during Nudm_SDM_Get | Samsung | Response to S2-2200081 and S2-2200058. Merged into S2-2201588 | Lalith (Samsung) proposes to merge this LS OUT in the S2-2201013(or its revisions) as discussed offline. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged | |
| 8.28 | S2-2201138 | CR | Approval | 23.502 CR3415 (Rel-17, 'F'): Nudm_UECM_Registration to delete the 'ME support of SOR-CMCI' indicator | Samsung | Rel-17 | Merged into S2-2201803 | Lalith (Samsung) proposes to merge this CR with the revisions of S2-2200998 as discussed offline. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 8.28 | S2-2200058 | LS In | Action | LS from CT WG4: LS on Deletion of ME support of SOR-CMCI indicator during Nudm_SDM_Get | CT WG4 (C4-216607) | Rel-17 | Responses drafted in S2-2201013 and S2-2201143. Final response in S2-2201553 | ==== 8.X, 9.X, 10.X Final Deadline ==== | Replied to |
| 8.28 | S2-2201013 | LS OUT | Approval | [DRAFT] LS Reply on Deletion of ME support of SOR-CMCI indicator during Nudm_SDM_Get | NTT DOCOMO | Rel-17 | Response to S2-2200081 and S2-2200058. r01 agreed. Revised to S2-2201553, merging S2-2201249 | Malla (NTT DOCOMO) provides r01. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.28 | S2-2201553 | LS OUT | Approval | LS Reply on Deletion of ME support of SOR-CMCI indicator during Nudm_SDM_Get | SA WG2 | Rel-17 | Revision of S2-2201013r01, merging S2-2201249. Approved | Approved | |
| 8.28 | S2-2200998 | CR | Approval | 23.502 CR3402 (Rel-17, 'F'): Registration type to the UDM for SoR | NTT DOCOMO | Rel-17 | Source to WG incorrect!. r02 agreed. Revised to S2-2201554, merging S2-2200999 | Malla (NTT DOCOMO) provides r01 Haris(Qualcomm) considers the CR unecessary Peter Hedman (Ericsson) provides comments Haris(Qualcomm) provides r02 Malla (NTT DOCOMO) fine with r02 Peter Hedman (Ericsson) ok with r02 Fenqin (Huawei) ok with r02 Lalith (Samsung) is also fine with r02 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 8.28 | S2-2201554 | CR | Approval | 23.502 CR3402R1 (Rel-17, 'F'): Registration type to the UDM for SoR | NTT DOCOMO, Ericsson, Samsung | Rel-17 | Revision of S2-2200998r02, merging S2-2200999. Approved | Agreed | |
| 8.28 | - | - | - | Other | - | - | Docs:=4 | - | |
| 8.28 | S2-2200338 | CR | Approval | 23.501 CR3491 (Rel-17, 'F'): Number of CN paging subgroups | Ericsson | Rel-17 | Approved | ==== 8.X, 9.X, 10.X Final Deadline ==== | Agreed |
| 8.28 | S2-2201519 | LS In | Action | LS from SA WG3: LS on full Registration Request upon AMF re-allocation | SA WG3 (S3-220453) | Rel-17 | Postponed | ==== 8.X, 9.X, 10.X Final Deadline ==== | Postponed |
| 8.28 | S2-2200339 | CR | Approval | 23.502 CR3150R3 (Rel-17, 'F'): Clarification on rerouted Registration Request message | Ericsson, Huawei, HiSilicon, NEC | Rel-17 | Revision of (Technically endorsed) S2-2108374 from S2#148E. r02 agreed. Revised to S2-2201477. CC#2: Moved to 8.28. r02 agreed | Alessio(Nokia) proposes to note/postpone this CR till we get reply from SA3 Fenqin (Huawei) comments Qian (Ericsson) comments and provides r01 Alessio(Nokia) is ok to technically endorse r01 and then approve at the earliest possible SA2 meeting if SA3 replies Qian (Ericsson) comments and provides r02 ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Revised |
| 8.28 | S2-2201477 | CR | Approval | 23.502 CR3150R4 (Rel-17, 'F'): Clarification on rerouted Registration Request message | Ericsson, Huawei, HiSilicon, NEC | Rel-17 | Revision of S2-2200339r02. CC#2: Moved to 8.28. Approved | Agreed | |
| 8.29 | - | - | - | Items moved for decision by Deadline #1 | - | - | Docs:=33 | - | |
| 8.29 | - | - | - | Slice group for cell re-selection (from 8.28) | - | - | Docs:=0 | - | |
| 8.29 | - | - | - | UPIP (from 8.28) | - | - | Docs:=3 | - | |
| 8.29 | S2-2200421 | LS In | Action | LS from RAN WG3: Reply LS on LTE User Plane Integrity Protection | RAN WG3 (R3-221473) | Rel-17 | Response drafted in S2-2200631. Final response in S2-2201518 | ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Replied to |
| 8.29 | S2-2200631 | LS OUT | Approval | Reply LS on LTE User Plane Integrity Protection | Huawei, HiSilicon | Rel-17 | Response to S2-2200421. r00 Revised to remove 'draft' in S2-2201518 | ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Revised |
| 8.29 | S2-2201518 | LS OUT | Approval | Reply LS on LTE User Plane Integrity Protection | SA WG2 | Rel-17 | Revision of S2-2200631r00. Approved | Approved | |
| 8.29 | - | - | - | Moved from 8.3 | - | - | Docs:=12 | - | |
| 8.29 | S2-2200196 | LS In | Information | LS from CT WG1: LS on ECS provider identification in ECS address provisioning | CT WG1 (C1-220854) | Rel-17 | Response drafted in S2-2201197. Postponed | ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Postponed |
| 8.29 | S2-2201197 | LS OUT | Approval | [DRAFT] Reply LS on ECS provider identification in ECS address provisioning | Nokia, Nokia Shanghai Bell | Rel-17 | Response to S2-2200196. Postponed | Hui (Huawei) provides comments. Shubhranshu (Nokia) responds Tugce (NTT DOCOMO) provides comments. Dario (Qualcomm) comments and asks q uestion to Shubhranshu. Hui (Huawei) provides further comments. Tingfang (Lenovo) comments. Dan (China Mobile) comments. Magnus O (Ericsson) provides comments Dario (Qualcomm) proposes to postpone this LS. Huazhang (vivo) provides some comments. Shubhranshu (Nokia) comments Hui (Huawei) provides r01 Shubhranshu (Nokia) comments and not agrees to r01 ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== Hui(Huawei) proposes to postpone the LS reply. Shubhranshu (Nokia) replies ( ok to postpone) ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Postponed |
| 8.29 | S2-2201190 | CR | Approval | 23.548 CR0050 (Rel-17, 'F'): Removing inconsistency in the definition of ECS Address Configuration Information | Nokia, Nokia Shanghai Bell | Rel-17 | r01 agreed. Revised to S2-2201511 | Hui (Huawei) provides comments. Shubhranshu (Nokia) provides r01 Tugce (NTT DOCOMO) provides comments. Shubhranshu (Nokia) responds Dario (Qualcomm) comments. Tingfang (Lenovo) comments. Tugce (NTT DOCOMO) responds. Hui (Huawei) provides r02 Shubhranshu (Nokia) responds, and objects to r02 Magnus O (Ericsson) proposes to postpone the CR to next meeting ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== Shubhranshu (Nokia) proposes to agree r01 Magnus O (Ericsson) can live with r01 Dario (Qualcomm) can accpet r01 (as long as next meeting we aling with SA6 on the optionality of ECS Provider ID). ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Revised |
| 8.29 | S2-2201511 | CR | Approval | 23.548 CR0050R1 (Rel-17, 'F'): Removing inconsistency in the definition of ECS Address Configuration Information | Nokia, Nokia Shanghai Bell | Rel-17 | Revision of S2-2201190r01. Approved | Agreed | |
| 8.29 | S2-2200202 | LS In | Action | LS from CT WG4: LS on NAT between the PSA UPF and the EASDF | CT WG4 (C4-220332) | Rel-17 | Responses drafted in S2-2200628, S2-2200874 and S2-2201081. Final response in S2-2201512 | ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Replied to |
| 8.29 | S2-2200628 | LS OUT | Approval | Reply to LS on NAT between the PSA UPF and the EASDF | Huawei, HiSilicon | Rel-17 | Response to S2-2200202. r04 agreed. Revised to S2-2201512, merging S2-2200874, S2-2201081 and S2-2200231 | Xinpeng(Huawei) provides r01. Laurent (Nokia): Comments and suggests to take 1080/1081 as baseline Dario (Qualcomm) comments and asks questions to Laurent and Xinpeng Dan (China Mobile) provide some comments Xinpeng(Huawei) suggest use 0628 as baseline for LS OUT. Magnus (Ericsson) provides r02 Laurent (Nokia): provides r03 Dario (Qualcomm) comments and provides r04. ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== Dario (Qualcomm) proposes to go w/ r04. ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Revised |
| 8.29 | S2-2201512 | LS OUT | Approval | Reply to LS on NAT between the PSA UPF and the EASDF | SA WG2 | Rel-17 | Revision of S2-2200628r04, merging S2-2200874, merging S2-2200874 and S2-2201081, merging S2-2200874, S2-2201081 and S2-2200231. Approved | Approved | |
| 8.29 | S2-2200874 | LS OUT | Approval | [DRAFT] Reply LS on NAT between the PSA UPF and the EASDF | China Mobile | Rel-17 | Response to S2-2200202. Merged into S2-2201512 and S2-2201728 | Dario S. Tonesi (Qualcomm) suggests to take Huawei's 0628 as baseline for discussion. Dan (China Mobile) OK to merge this LS into S2-2200628 as baseline for discussion. ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Merged |
| 8.29 | S2-2201081 | LS OUT | Approval | [DRAFT] LS on NAT between the PSA UPF and the EASDF | Nokia, Nokia Shanghai Bell | Rel-17 | Response to S2-2200202. Merged into S2-2201512 | Dario S. Tonesi (Qualcomm) suggests to take Huawei's 0628 as baseline Magnus H (Ericsson) proposes to use 0628 as base for LS Laurent (Nokia): OK to merge 1081 into 0628 (reducing the Nr of threads) ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Merged |
| 8.29 | S2-2201080 | CR | Approval | 23.548 CR0048 (Rel-17, 'F'): On NAT between PSA UPF and EASDF | Nokia, Nokia Shanghai Bell | Rel-17 | r04 agreed. Revised to S2-2201513 | Laurent (Nokia): provides r01 Magnus (Ericsson) provides r02 Dario (Qualcomm) provides r04 (= r03 + fix in cover page) Dario (Qualcomm) provides r03 ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== Dario (Qualcomm) proposes to go w/ r04. ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Revised |
| 8.29 | S2-2201513 | CR | Approval | 23.548 CR0048R1 (Rel-17, 'F'): On NAT between PSA UPF and EASDF | Nokia, Nokia Shanghai Bell | Rel-17 | Revision of S2-2201080r04. Approved | Agreed | |
| 8.29 | S2-2200434 | LS OUT | Approval | LS on 3GPP Edge Computing Feature Control | Ericsson [3GPP TSG SA WG2] | Rel-17 | Noted | Hui (Huawei) asks whether this LS is needed. Magnus O (Ericsson) provides an answer to Hui Laurent (Nokia): we support the LS Laurent (Nokia): provides r01 Dario (Qualcomm) thinks the LS should not be sent because CT3 did not ask for any input. Hui (Huawei) share the view of Dario (Qualcomm) . Magnus O (Ericsson) is happy with r01 Dario (Qualcomm) comments. Magnus O (Ericsson) comments further Laurent (Nokia): answers (support Magnus) Susana (Vodafone) supports the proposal to clarify to CT3 ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== Hui (Huawei) objects to r0 and r1 but would be fine to remove some 'feature control' related words, and no need to include CT1/4 since they are not relevant to the issue. Hui (Huawei) provides draft r02 and asks to discuss in CC#2. Magnus O (Ericsson) is ok with r02 and propose to discuss it at CC#2 Laurent (Nokia): is ok with r02 and propose to discuss it at CC#2 (but removing CT4, not CT3) Dario (Qualcomm) objects this LS. ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Noted |
| 8.29 | - | - | - | Moved from 8.25 | - | - | Docs:=9 | - | |
| 8.29 | S2-2200244 | LS OUT | Approval | [DRAFT] Reply LS on MINT functionality for Disaster Roaming | LG Electronics | Rel-17 | Response to S2-2200066. r01 agreed. Revised to S2-2201514. | Hyunsook (LGE) provides r01. Haiyang (Huawei) provides r02. ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== Hyunsook (LGE) suggests to go with r01, and objects to r02. Qian (Ericsson) supports Hyunsook (LGE) to go with r01. ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Revised |
| 8.29 | S2-2201514 | LS OUT | Approval | Reply LS on MINT functionality for Disaster Roaming | SA WG2 | Rel-17 | Revision of S2-2200244r01. Approved | Approved | |
| 8.29 | S2-2200261 | LS OUT | Approval | [DRAFT] Reply LS on MINT functionality for Disaster Roaming | Huawei, HiSilicon | Rel-17 | Response to S2-2200066. Noted | Based on the way forward during CC#1, Hyunsook (LGE) proposes to note this draft LS. ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Noted |
| 8.29 | S2-2200245 | CR | Approval | 23.501 CR3474 (Rel-17, 'F'): Clarification on Authentication and Subscription information checking | LG Electronics, KT Corp., LG Uplus, SK Telecom, Ericsson | Rel-17 | r03 agreed. Revised to S2-2201515, merging S2-2200956 and S2-2200334 | Qian (Ericsson) provides r01 Hyunsook (LGE) proposes to use AI#8.29 (of Andy's chair note) for this CR. [FYI] Qian(Ericsson) provides r01 in AI#8.25. Hyunsook (LGE) provides r02. Haiyang (Huawei) provides comments. [For the chair's note] Haiyang (Huawei) provides comments. Hyunsook (LGE) responses to Haiyang (Huawei). Haiyang (Huawei) provides further comments. Qian (Ericsson) responds. Lalith(Samsung) comments Qian (Ericsson) provides further responses. Lalith(Samsung) comments. Qian (Ericsson) responds to Lalith (Samsung). Lalith(Samsung) replies to Qian (Ericsson) Sudeep (Apple) provides comments and indicates support for this CR. Qian (Ericsson) provides further comments. Haiyang (Huawei) comments. Hyunsook (LGE) provides r03 adding co-signer. Haiyang (Huawei) provides r04. Haiyang (Huawei) further comments. ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== Hyunsook (LGE) suggests to go with r03, and objects to r04. Haiyang (Huawei) can accept r03. Qian (Ericsson) supports r03. Haris(Qualcomm) supports r03. R04 is not correct for reasons explained from Qian ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Revised |
| 8.29 | S2-2201515 | CR | Approval | 23.501 CR3474R1 (Rel-17, 'F'): Clarification on Authentication and Subscription information checking | LG Electronics, KT Corp., LG Uplus, SK Telecom, Ericsson, Apple | Rel-17 | Revision of S2-2200245r03, merging S2-2200956 and S2-2200334. Approved | Agreed | |
| 8.29 | S2-2200246 | CR | Approval | 23.502 CR3330 (Rel-17, 'B'): Authentication and Subscription information checking for Disaster Roaming service | LG Electronics, KT Corp., LG Uplus, SK Telecom, Ericsson | Rel-17 | r03 agreed. Revised to S2-2201516. | Qian (Ericsson) provides r01 and 0334 can be considered as merged Hyunsook (LGE) proposes to use AI#8.29 (of Andy's chair note) for this CR. [FYI] Qian(Ericsson) provides r01 in AI#8.25. Hyunsook (LGE) provides r02. Sudeep (Apple) supports this CR. Hyunsook (LGE) provides r03 adding co-signers. Haiyang (Huawei) provides r04. ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== Qian (Ericsson) comments and provides r05 on top of r03. Hyunsook (LGE) suggests to go with r03, and objects to r04. Haiyang (Huawei) can live with r03, and cannot accept r05. Qian (Ericsson) comments and prefers to added the 'indication of Disaster Roaming'on top of R03, but can live with r03 as well. ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Revised |
| 8.29 | S2-2201516 | CR | Approval | 23.502 CR3330R1 (Rel-17, 'B'): Authentication and Subscription information checking for Disaster Roaming service | LG Electronics, KT Corp., LG Uplus, SK Telecom, Ericsson, CATT, Apple | Rel-17 | Revision of S2-2200246r03. Approved | Agreed | |
| 8.29 | S2-2200262 | CR | Approval | 23.502 CR3331 (Rel-17, 'F'): Delete the EN related to disaster roaming indication for authentication | Huawei, HiSilicon | Rel-17 | Noted | Based on the way forward during CC#1, Hyunsook (LGE) proposes to note this CR. Haris(Qualcomm) asks questions for clarification Haiyang (Huawei) responds to Haris(Qualcomm) Haris(Qualcomm) comments Haiyang (Huawei) further responds to Haris(Qualcomm) Haris(Qualcomm) comments further Qian (Ericsson) comments Haiyang (Huawei) comments to Qian (Ericsson) Haiyang (Huawei) provides r01 Haiyang (Huawei) provides r02 as an Alt ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== Hyunsook (LGE) objects to r00 and all revisions. ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Noted |
| 8.29 | S2-2200263 | CR | Approval | 23.501 CR3478 (Rel-17, 'F'): Delete the EN on disaster roaming indication for authentication | Huawei, HiSilicon | Rel-17 | Noted | Based on the way forward during CC#1, Hyunsook (LGE) proposes to note this CR. ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Noted |
| 8.29 | - | - | - | Moved from 8.9 | - | - | Docs:=4 | - | |
| 8.29 | S2-2200415 | LS In | Action | LS from RAN WG3: LS on MBS Service Area Identity and start procedure for broadcast service | RAN WG3 (R3-221302) | Rel-17 | Response drafted in S2-2200996. Final response in S2-2201517 | ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Replied to |
| 8.29 | S2-2200526 | LS OUT | Approval | [Draft] Reply LS on MBS Service Area Identity and start procedure for broadcast service | CATT | Rel-17 | r06 agreed. Revised to S2-2201517, merging S2-2200996 | Robbie (Ericsson) provides r01 Xiaoyan (CATT) provides r02 and r03. Zhenhua (vivo) ask for clarification Robbie (Ericsson) replies to Zhenhua (vivo) Zhendong (ZTE): provides r05 Xiaoyan (CATT) is fine with r05. Robbie (Ericsson) provides r06. LiMeng (Huawei) replies. Robbie (Ericsson) comments. Xiaoyan (CATT) replies to LiMeng (Huawei). LiMeng (Huawei) is fine with r06. Thomas (Nokia) confirms that he provided r04. Can also accept r05 or r06 ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Revised |
| 8.29 | S2-2201517 | LS OUT | Approval | Reply LS on MBS Service Area Identity and start procedure for broadcast service | SA WG2 | Rel-17 | Revision of S2-2200526r06, merging S2-2200996. Approved | Approved | |
| 8.29 | S2-2200996 | LS OUT | Approval | [DRAFT] Reply LS on MBS Service Area Identity and start procedure for broadcast service | Ericsson Inc. | Rel-17 | Response to S2-2200415. Merged into S2-2201517 | Robbie (Ericsson) merges it to 0526 ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Merged |
| 8.29 | - | - | - | Moved from 8.10 | - | - | Docs:=5 | - | |
| 8.29 | S2-2201252 | LS In | Action | LS from RAN WG2: LS to SA2 and CT1 on alternative IMSI for MUSIM | RAN WG2 (R2-2201718) | Rel-17 | CC#1: Response drafted in S2-2201267. CC#2: Final response in S2-2201681 | ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Replied to |
| 8.29 | S2-2201267 | LS OUT | Approval | [DRAFT] Reply LS on alternative IMSI for MUSIM | SA WG2 | Rel-17 | Created at CC#1. Response to S2-2201252. CC#2: r10 agreed. Revised, merging S2-2200146, to S2-2201681. | Lars (Sony) provides original version for the new tdoc number received during CC#1 Steve (Huawei) provides r01 Lars (Sony) provides r02 Alessio(Nokia)) provides r03 Steve (Huawei) comments Lars (Sony) provides r04 Steve (Huawei) provides r05 Lars (Sony) provides r06 alessio(Nokia) prefers r03 alessio(Nokia) cannot accept any version than r03. Steve (Huawei) r03 does not provide the whole picture and unnecessarily constrains RAN2 - it becomes pointless. ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== Saso (Intel) proposes to agree r06 and to consider 0146 merged into 1267. Lars (Sony) proposes to agree r06. Steve (Huawei) can live with r06 Xiaowan(vivo) comment r06 since it doesn't reply RAN2's request in the LS in S2-2201252 Alessio(Nokia) proposes the way forward based on a small change to r06. Xiaowan(vivo) disagrees r06. If we cannot make decision this meeting to choose 1) ask RAN2 to follow SA2(23.401) or 2) SA2 follow RAN2(36.304); I request to postpone LS reply and continue the discussion next meeting. Steve (Huawei) comments. Lars (Sony) comments. Guillaume (MediaTek Inc.) comments. Lars (Sony) provides a draft of an r07 in the drafts folder, let's see if we can agree on an updated revision of the LS in CC#2. alessio(Nokia) supports the brief but effective summary by Guillaume on where we are We are ok with r07 . Guillaume (MediaTek Inc.) provides r07. Lars (Sony) provides r08 and ask to discuss in CC2. ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== Steve (Huawei) provides r09 Saso (Intel) provides r10 Lars (Sony) is ok with r10 Alessio (Nokia) is ok with r10 Xiaowan (vivo) is OK with r10 Guillaume (MediaTek Inc.): r10 is ok. | Revised |
| 8.29 | S2-2201681 | LS OUT | Approval | Reply LS on alternative IMSI for MUSIM | SA WG2 | Rel-17 | Revision of S2-2201267r10, merging S2-2200146. CC#2: Approved | Approved | |
| 8.29 | S2-2200018 | LS In | Action | LS from RAN WG2: Reply LS on RAN2 agreements for MUSIM | RAN WG2 (R2-2111329) | Rel-17 | Revision of Postponed S2-2108997 from S2#148E. Response drafted in S2-2200146. CC#2: Final response in S2-2201681 | ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== | Replied to |
| 8.29 | S2-2200146 | LS OUT | Approval | [DRAFT] LS reply on Reply LS on RAN WG2 agreements for MUSIM | vivo | Rel-17 | Response to S2-2200018. CC#2: merged into S2-2101681 | Lars (Sony) ask whether we can consider this MERGED into S2-2201267 ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== Saso (Intel) agrees with Lars (Sony) that 0146 can be merged into S2-2201267 Xiaowan(vivo) replies S2-2200146(reply to S2-2200018) and S2-2201267( reply to S2-2201252) are the different LS reply to different RAN2 LS. hence, 0146 cannot be merged into S2-2201267. Lars (Sony) not sure way it is not possible to reply with one LS to more than one LSin. Lars (Sony) this LSout can only be Approved if the LSout in S2-2201267 is Approved. Else this LSout should be postponed. ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Final Deadline ==== Saso (Intel) points there is no rule prohibiting the use of one LS reply for two incoming LSs. | Merged |
| 9 | - | - | - | Rel-18 SIDs | - | - | Docs:=0 | - | |
| 9.1 | - | - | - | Study on System Enabler for Service Function Chaining (FS_SFC) | - | - | Docs:=11 | - | |
| 9.1 | S2-2201079 | P-CR | Approval | 23.700-18: FS_SFC TR Skeleton | Intel | Rel-18 | 23.700-18 TR Skeleton. Approved | ==== 8.X, 9.X, 10.X Final Deadline ==== | Approved |
| 9.1 | S2-2201086 | P-CR | Approval | 23.700-18: FS_SFC TR Scope. | Intel | Rel-18 | Approved | ==== 8.X, 9.X, 10.X Final Deadline ==== | Approved |
| 9.1 | S2-2201089 | P-CR | Approval | 23.700-18: FS_SFC architectural assumptions and Principles. | Intel | Rel-18 | CC#4: Postponed for CC#5. CC#5: r15 + changes agreed. Revised to S2-2201848, merging S2-2201228. | Laurent (Nokia): provides r01 merging in 1228 Stefan (Ericsson) provides r02 Ellen (Intel) provides r03 Xinpeng(Huawei) provides r04. Stefan (Ericsson) provides r05 Ellen (Intel) provides r06 Xinpeng(Huawei) comments. Curt (Charter) comments. Ellen (Intel) provides r07 Jaewook(ETRI) asks a question about r07. Laurent (Nokia): provides r08 Ellen (intel) answers ETRI's questions Xinpeng(Huawei) commets. Jaewook (ETRI) provides comments. Xinpeng(Huawei) replies to Jaewook (ETRI). Ellen (Intel): provides r09 Laurent (Nokia): provides r10 Ellen (Intel) provides r11 to use the same wording as SID Xinpeng(Huawei) provides r12. Laurent (Nokia): provides r13 Stefan (Ericsson) provides r14 Ellen (Intel) provides r15 ==== 8.X, 9.X, 10.X Revisions Deadline ==== Laurent (Nokia): can happily live with R10, R13, R14, R15 (the best). objects to any other version including R00 Xinpeng(Huawei) is ok with r15 with the following changes: ' - The study assumes a Home Routed roaming PDU Session does not have an offloading point for SFC in a VPLMN. This does not prevent offloading in the VPLMN for other purpose.', and objects to all other versions. Xinpeng(Huawei) could be ok with r15 with one of the following optional changes: Option1: ' - Currently The study assumes a Home Routed roaming PDU Session does not have an offloading point for SFC in a VPLMN. This does not prevent offloading in the VPLMN for other purpose.'; Option2: replace 'The study assumes a Home Routed roaming PDU Session does not have an offloading point in a VPLMN' to ''This study will not study SFC in VPLMN for a HR PDU Session'. and objects to all other versions. ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.1 | S2-2201848 | P-CR | Approval | 23.700-18: FS_SFC architectural assumptions and Principles. | Intel, Sandvine | Rel-18 | Revision of S2-2201089r15 + change, merging S2-2201228. Approved | Approved | |
| 9.1 | S2-2201091 | P-CR | Approval | 23.700-18: FS_SFC: New KI related with WT2 v1. | Intel (rapporteur) | Rel-18 | CC#5: r13 + changes agreed. Revised to S2-2201849. | Laurent (Nokia): provides r01 Ellen (Intel) provides r02 Stefan (Ericsson) asks why we need both Key Issues Ellen (Intel) proposed 1091r03 with merged Key Issues Manuel (Sandvine), we agree with what 1091r03 intel is proposing. Xinpeng(Huawei) provides r04. Stefan (Ericsson) provides r05 Ellen (Intel) provides r06 Xinpeng(Huawei) comments. Ellen (Intel) answers Xinpeng (HW) question Xinpeng(Huawei) provides r07. Ellen (Intel) provides r08 to clarify home-routed cases Laurent (Nokia): provides r09 Stefan (Ericsson) provides r10 Ellen (Intel) provides r11 Xinpeng(Huawei) provides r11 Ellen (Intel) provides r13 ==== 8.X, 9.X, 10.X Revisions Deadline ==== Laurent (Nokia): can happily live with r13 (best), R11, R10, R09; objects to any other version Xinpeng(Huawei) is ok with r13 with the following changes: ' NOTE1: Home Routed roaming PDU Sessions do not have an offloading point for SFC in a VPLMN. This does not prevent offloading in the VPLMN for other purpose.', and objects to all other versions. Xinpeng(Huawei) could be ok with r13 with one of following options: Opt1: ' NOTE1: Currently Home Routed roaming PDU Sessions do not have an offloading point for SFC in a VPLMN. This does not prevent offloading in the VPLMN for other purpose.'; Opt2: Replace NOTE1 with: This study will not study SFC in VPLMN for a HR PDU Session . And objects to all other versions. ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.1 | S2-2201849 | P-CR | Approval | 23.700-18: FS_SFC KI related with WT2. | Intel, Nokia, Nokia Shanghai Bell, Sandvine | Rel-18 | Revision of S2-2201091r13 + changes. Approved | Approved | |
| 9.1 | S2-2201094 | P-CR | Approval | 23.700-18: FS_SFC KI related with WT3. | Intel | Rel-18 | r11 agreed. Revised to S2-2201747. | Laurent (Nokia): provides r01 Xinpeng(Huawei) provides r03. Stefan (Ericsson) provides r04 Ellen (Intel) provides r05 Xinpeng(Huawei) replies. Curt (Charter) comments... Ellen (Intel) provides feedback to HW's question about NOTE Stefan (Ericsson) provides r08 Curt (Charter) prefers to skip the NOTE for now. Xinpeng(Huawei) provides r09. Laurent (Nokia): provides r10 Ellen (Intel) is fine with r08 provided by Ericsson Ellen (Intel): provides r11 ==== 8.X, 9.X, 10.X Revisions Deadline ==== Laurent (Nokia): R11/R10 are the best. objects to R00, R06, R07, R09. I can live with the others Xinpeng(Huawei) is ok with r11, r09, and objects to all other versions. ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.1 | S2-2201747 | P-CR | Approval | 23.700-18: FS_SFC KI related with WT3. | Intel, Nokia, Nokia Shanghai Bell, Sandvine | Rel-18 | Revision of S2-2201094r11. Approved | Approved | |
| 9.1 | S2-2201097 | P-CR | Approval | 23.700-18: FS_SFC: Annex for Pre-R18 Traffic Steering Control. | Intel | Rel-18 | r01 agreed. Revised to S2-2201748. | Stefan (Ericsson) provides r01 Ellen (Intel) is fine with r01 provided by Stefan (Ericsson) ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.1 | S2-2201748 | P-CR | Approval | 23.700-18: FS_SFC: Annex for Pre-R18 Traffic Steering Control. | Intel | Rel-18 | Revision of S2-2201097r01. Approved | Approved | |
| 9.1 | S2-2201228 | P-CR | Approval | 23.700-18: FS_SFC architectural assumptions. | Nokia, Nokia Shanghai Bell | Rel-18 | Merged into S2-2201848 | Laurent (Nokia): OK with merging 1228 into 1089 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.2 | - | - | - | Study on Generic group management, exposure and communication enhancements (FS_GMEC) | - | - | Docs:=38 | - | |
| 9.2 | - | - | - | TR Skeleton and Scope | - | - | Docs:=2 | - | |
| 9.2 | S2-2200646 | P-CR | Approval | 23.700-74: FS_GMEC TR 23.700-74 Skeleton. | Huawei, HiSilicon, Samsung (Rapporteur) | Rel-18 | 23.700-74 TR Skeleton. Approved | ==== 8.X, 9.X, 10.X Final Deadline ==== | Approved |
| 9.2 | S2-2200647 | P-CR | Approval | 23.700-74: FS_GMEC TR 23.700-74 Scope. | Huawei, HiSilicon, Samsung (Rapporteur) | Rel-18 | Approved | ==== 8.X, 9.X, 10.X Final Deadline ==== | Approved |
| 9.2 | - | - | - | Definitions of terms and abbreviations | - | - | Docs:=2 | - | |
| 9.2 | S2-2200649 | P-CR | Approval | 23.700-74: FS_GMEC TR 23.700-74 Definitions of terms and abbreviations. | Huawei, HiSilicon | Rel-18 | r03 agreed. Revised to S2-2201555. | Stefan (Ericsson) provides r01 Qianghua (Huawei) replies to Stefan Shubhranshu (Nokia) comments Zhendong (ZTE): provides r02 Zhendong (ZTE): provides response Sebastian (Qualcomm) supports Stefan's comments; suggests to remove Group definition Stefan (Ericsson) comments Shubhranshu (Nokia) provides r03 Qianghua (Huawei) provides comments Shubhranshu (Nokia) responds Stefan (Ericsson) replies ==== 8.X, 9.X, 10.X Revisions Deadline ==== Qianghua (Huawei) OK with either r03 or r03+EN Sang-Jun (Samsung) proposes to adding an EN on top of r03.. Shubhranshu (Nokia) also OK with r03 Sang-Jun (Samsung) is OK with r03 if adding an EN is not possible. Stefan (Ericsson) OK with r03 Zhendong (ZTE): is fine with r03 ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.2 | S2-2201555 | P-CR | Approval | 23.700-74: FS_GMEC TR 23.700-74 Definitions of terms and abbreviations. | Huawei, HiSilicon | Rel-18 | Revision of S2-2200649r03. Approved | Approved | |
| 9.2 | - | - | - | Architectural Assumptions | - | - | Docs:=4 | - | |
| 9.2 | S2-2200289 | P-CR | Approval | 23.700-74: FS_GMEC Architectural Assumptions and Requirements. | Nokia, Nokia Shanghai Bell | Rel-18 | Merged into S2-2201557 | Laurent (Nokia): OK to merge 0289 in 0648 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.2 | S2-2200359 | P-CR | Approval | 23.700-74: Adding architecture assumption and requirement to FS_GMEC. | ZTE | Rel-18 | Merged into S2-2201557 | Laurent (Nokia): objects to this Tdoc (for the sake of merging in 0648) Zhendong (ZTE): is fine merge this pCR into 2200648 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.2 | S2-2200648 | P-CR | Approval | 23.700-74: FS_GMEC TR 23.700-74 Architectural Assumptions and Requirements. | Huawei, HiSilicon, Samsung | Rel-18 | r07 agreed. Revised to S2-2201556, merging S2-2201128 and S2-2200551 | Laurent (Nokia): provides r01 that merges in 0289 Qianghua (Huawei) provides r02 Laurent (Nokia): provides r03 Qianghua (Huawei) provides r04 Zhendong (ZTE): provides r05 Laurent (Nokia): provides r06 Qianghua (Huawei) provides r07 Qianghua (Huawei) provides r08 Laurent (Nokia): provides r09 Qianghua (Huawei) provides comments for r09 Stefan (Ericsson) comments r08 and r09 Qianghua (Huawei) replies ==== 8.X, 9.X, 10.X Revisions Deadline ==== Laurent (Nokia): objects to R02, R04, R05, R08; As R09 is verbatim the SID it should be the best Qianghua (Huawei) suggests to go with r07 or r08. Object r09, r06, r03, r01 Sang-Jun (Samsung) can accept r07, r08, and objects to r09 as the architectural requirements are not fully discussed/agreed. Stefan (Ericsson) proposes to go with r07. Object to r08, r05, r04, r02, r00 Sebastian (Qualcomm) is fine with r07 and r09; objects to other versions Zhendong (ZTE): proposes move with r07 ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.2 | S2-2201556 | P-CR | Approval | 23.700-74: FS_GMEC TR 23.700-74 Architectural Assumptions and Requirements. | Huawei, HiSilicon, Samsung, ZTE | Rel-18 | Revision of S2-2200648r07, merging S2-2201128, merging S2-2201128 and S2-2200551. Approved | Approved | |
| 9.2 | - | - | - | Key Issue Proposal for WT#1.1 | - | - | Docs:=4 | - | |
| 9.2 | S2-2200650 | P-CR | Approval | 23.700-74: Key Issue Proposal for FS_GMEC WT#1.1. | Huawei, HiSilicon | Rel-18 | r13 agreed. Revised to S2-2201557, merging S2-2200289, S2-2200359, S2-2200667 and S2-2200404 | Josep (DT) comments, requests clarification on what other 'group types' are. Qianghua (Huawei) provides 0650r01, merging 0667 and 1237 Shubhranshu (Nokia) comments and provides r02 Qianghua (Huawei) provides 0650r03 Stefan (Ericsson) provides r04 Shubhranshu (Nokia) comments and provides r05 Zhendong (ZTE): provides r06 Qianghua (Huawei) provides r07, merging concept of S2-2200404 Shubhranshu (Nokia) provides r08 Tugce (NTT DOCOMO) is ok with r08. Sebastian (Qualcomm) provides r09 Sang-Jun (Samsug) provides comments on r09. Qianghua (Huawei) provides r10 Stefan (Ericsson) provides r11 Shubhranshu (Nokia) provides r12 Sebastian (Qualcomm) provides r13 ==== 8.X, 9.X, 10.X Revisions Deadline ==== Sebastian (Qualcomm) prefers r13, is also ok with r09 and objects to other revisions ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.2 | S2-2201557 | P-CR | Approval | 23.700-74: Key Issue Proposal for FS_GMEC WT#1.1. | Huawei, HiSilicon, Nokia, Nokia Shanghai Bell, NTT DOCOMO | Rel-18 | Revision of S2-2200650r13, merging S2-2200289, S2-2200359, S2-2200667 and S2-2200404. Approved | Approved | |
| 9.2 | S2-2200667 | P-CR | Approval | 23.700-74: New KI related with FS_GMEC WT1.1. | Samsung | Rel-18 | Merged into S2-2201557 | Qianghua (Huawei) proposes to merge this into S2-2200650 Sang-Jun (Samsung) agrees to merge this into S2-2200650 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.2 | S2-2201237 | P-CR | Approval | 23.700-74: KIs related with WT#1.1. | Nokia, Nokia Shanghai Bell | Rel-18 | Merged into S2-2201364 | Josep (DT) requests clarification on requirements. Qianghua (Huawei) proposes to merge this into S2-2200650 Shubhranshu (Nokia) responds Shubhranshu (Nokia) ok to merge to S2-2200650 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.2 | - | - | - | Key Issue Proposal for WT#1.2 | - | - | Docs:=4 | - | |
| 9.2 | S2-2200651 | P-CR | Approval | 23.700-74: Key Issue Proposal for FS_GMEC WT#1.2. | Huawei, HiSilicon | Rel-18 | Merged into S2-2201558 | Shubhranshu (Nokia) proposes to merge this into S2-2201238 Qianghua (Huawei) confirms to merge this into S2-2201238 Sebastian (Qualcomm) suggests to consider merged into 1238. (Authors please confirm!) ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.2 | S2-2200668 | P-CR | Approval | 23.700-74: New KI related with FS_GMEC WT1.2. | Samsung | Rel-18 | Merged into S2-2201558 | Shubhranshu (Nokia) proposes to merge into S2-2201238 Sang-Jun (Samsung) agrees to merge this into S2-2201238. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.2 | S2-2201238 | P-CR | Approval | 23.700-74: KI related with WT1.2. | Nokia, Nokia Shanghai Bell | Rel-18 | r05 agreed. Revised to S2-2201558, merging S2-2200651 and S2-2200668 | Shubhranshu (Nokia) provides r01, merging S2-2200651 & S2-2200668 Qianghua (Huawei) provides comments on r01 and provides r02 Shubhranshu (Nokia) responds and provides r03 Qianghua (Huawei) replies Zhendong (ZTE): proposes to add 'group' description in general clause. Stefan (Ericsson) provides r04 Sebastian (Qualcomm) provides r05 Sang-Jun (Samsung) comments ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.2 | S2-2201558 | P-CR | Approval | 23.700-74: KI related with WT1.2. | Nokia, Nokia Shanghai Bell, Huawei, HiSilicon, Samsung | Rel-18 | Revision of S2-2201238r05, merging S2-2200651, merging S2-2200651 and S2-2200668. Approved | Approved | |
| 9.2 | - | - | - | Key Issue Proposal for WT#2.1 | - | - | Docs:=4 | - | |
| 9.2 | S2-2200360 | P-CR | Approval | 23.700-74: Adding Key Issue on Multiple SMFs for VN group communication. | ZTE | Rel-18 | r06 agreed. Revised to S2-2201559, merging S2-2200652 and S2-2200669 | Laurent (Nokia): provides r01 Qianghua (Huawei) provides r02, merging S2-2200652 Ashok (Samsung) need clarifications Qianghua (Huawei) replies to Ashok Zhendong (ZTE): provides response Stefan (Ericsson) provides r03 Sang-Jun (Samsung) provides r04 Laurent (Nokia): provides r05 Sang-Jun (Samsung) provides r06 ==== 8.X, 9.X, 10.X Revisions Deadline ==== Laurent (Nokia): prefers R05, can live with R06, objects to R04, R03, R02, R00 ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.2 | S2-2201559 | P-CR | Approval | 23.700-74: Adding Key Issue on Multiple SMFs for VN group communication. | ZTE, Huawei, HiSilicon, Samsung | Rel-18 | Revision of S2-2200360r06, merging S2-2200652, merging S2-2200652 and S2-2200669. Approved | Approved | |
| 9.2 | S2-2200652 | P-CR | Approval | 23.700-74: Key Issue Proposal for FS_GMEC WT#2.1. | Huawei, HiSilicon | Rel-18 | Merged into S2-2201559 | Laurent (Nokia): objects to this Tdoc (for the sake of merging in 0360 per the rapporteur proposal) Qianghua (Huawei) confirms this is merged into S2-2200360 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.2 | S2-2200669 | P-CR | Approval | 23.700-74: New KI related with FS_GMEC WT2.1. | Samsung | Rel-18 | Merged into S2-2201559 | Laurent (Nokia): objects to this Tdoc (for the sake of merging in 0360 per the rapporteur proposal) Sang-Jun (Samsung) proposes to consider this paper as merged with 0360. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.2 | - | - | - | Key Issue Proposal for WT#3 | - | - | Docs:=3 | - | |
| 9.2 | S2-2200361 | P-CR | Approval | 23.700-74: Adding Key Issue on simultaneously send data to different groups. | ZTE | Rel-18 | Merged into S2-2201768 | Josep (DT) questions the 'via one PDU session' statement. Proposes to merge with 2200670. Zhendong (ZTE): is fine to merge this paper to S2-2200670 Laurent (Nokia): objects to this Tdoc (for the sake of merging in 0670 per the rapporteur proposal) Zhendong (ZTE): confirm this pCR is merged to S2-2200670 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.2 | S2-2200670 | P-CR | Approval | 23.700-74: New KI related with FS_GMEC WT3. | Samsung, Huawei | Rel-18 | r10 agreed. Revised to S2-2201560, merging S2-2201170 | Sang-Jun (Samsung) provides r01 merging S2-2200670 and S2-2200361, using S2-2200670 as a baseline. Zhendong (ZTE): provides the r02 Josep (DT) asks for clarification regarding existing functionality. Sees only addressing a whole group as missing. Sang-Jun (Samsung) provides r01 merging S2-2200670 and S2-2200361, using S2-2200670 as a baseline, and appolgoizes for the missing '#' in the previous email header. Sang-Jun (Samsung) is fine with r02 and appolgizes for the missing '#' in the email header when r01 was provided. Sang-Jun (Samsung) reponds to Josep (DT). Laurent (Nokia): provides r03 Qianghua (Huawei) provides comments Stefan (Ericsson) provides r04 Sang-Jun (Samsung) comments on r04. Sang-Jun (Samsung) is fine with r03. Josep (DT) comments, provides r05. Marco (Huawei) comments, provides r06. Zhendong (ZTE): provides comments Laurent (Nokia): provides r07 Sebastian (Qualcomm) provides r08 Sang-Jun (Samsung) provides comments on r05~r08. Qianghua (Huawei) prefers r07 and suggests to go with r07 Laurent (Nokia): prefers R08 that avoids telling twice the same thing Josep (DT) likes the shorter approach in r08, proposes r09. Qianghua (Huawei) provides r10, and still prefer r07 ==== 8.X, 9.X, 10.X Revisions Deadline ==== Sang-Jun (Samsung) prefers r07 and suggests to go with r07. Laurent (Nokia): equally happy with R08, R09, R10 which are the best; objects to R00, R01, R02, R03, R04, R05, R06 Sebastian (Qualcomm) is ok with r08/r09/r10, objects to other versions Stefan (Ericsson) OK with r08-r10. Objects to other revisions. ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.2 | S2-2201560 | P-CR | Approval | 23.700-74: New KI related with FS_GMEC WT3. | Samsung, Huawei, ZTE | Rel-18 | Revision of S2-2200670r10, merging S2-2201170. Approved | Approved | |
| 9.2 | - | - | - | Solution Proposal for WT#1.1 | - | - | Docs:=3 | - | |
| 9.2 | S2-2200404 | P-CR | Approval | 23.700-74: New Solution to Key Issue for FS_GMEC WT#1.1. | NTT DOCOMO | Rel-18 | Merged into S2-2201557 | Qianghua (Huawei) asks questions Tugce (NTT DOCOMO) responds. Zhendong (ZTE): proposes this can be put into annex Shubhranshu (Nokia) comments Qianghua (Huawei) proposes a way forward Tugce (NTT DOCOMO) agrees on the way forward with minor changes. Sebastian (Qualcomm) suggests to consider the paper merged into S2-2200650 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.2 | S2-2200653 | P-CR | Approval | 23.700-74: New Solution to Key Issue for FS_GMEC WT#1.1. | Huawei, HiSilicon | Rel-18 | r03 agreed. Revised to S2-2201561. | Shubhranshu (Nokia) asks for clarification Qianghua (Huawei) replies to Shubhranshu Stefan (Ericsson) provides questions for clarification Qianghua (Huawei) replies to Stefan and provides r01 Stefan (Ericsson) replies to Qianghua Sebastian (Qualcomm) comments Qianghua (Huawei) provides r02 and replies Shubhranshu (Nokia) provides r03 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.2 | S2-2201561 | P-CR | Approval | 23.700-74: New Solution to Key Issue for FS_GMEC WT#1.1. | Huawei, HiSilicon | Rel-18 | Revision of S2-2200653r03. Approved | Approved | |
| 9.2 | - | - | - | Solution Proposal for WT#1.2 | - | - | Docs:=2 | - | |
| 9.2 | S2-2200654 | P-CR | Approval | 23.700-74: New Solution to Key Issue for FS_GMEC WT#1.2. | Huawei, HiSilicon | Rel-18 | r06 agreed. Revised to S2-2201562. | Shubhranshu (Nokia) asks for clarification Qianghua (Huawei) replies to Shubhranshu György (Ericsson) comments Zhendong (ZTE): provides comments Qianghua (Huawei) provides r01 Stefan (Ericsson) provides questions Sebastian (Qualcomm) provides r02 Qianghua (Huawei) replies and provides r03 Stefan (Ericsson) provides r04 Shubhranshu (Nokia) provides r05 Stefan (Ericsson) provides r06 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.2 | S2-2201562 | P-CR | Approval | 23.700-74: New Solution to Key Issue for FS_GMEC WT#1.2. | Huawei, HiSilicon | Rel-18 | Revision of S2-2200654r06. Approved | Approved | |
| 9.2 | - | - | - | Solution Proposal for WT#2.1 | - | - | Docs:=6 | - | |
| 9.2 | S2-2200115 | P-CR | Approval | 23.700-74: New solution for WT2 | Nokia, Nokia Shanghai Bell | Rel-18 | r03 agreed. Revised to S2-2201563. | Qianghua (Huawei) asks questions Stefan (Ericsson) comments Laurent (Nokia): provides r01 Sang-Jun (Samsung) comments Qianghua (Huawei) repeats comments Qianghua (Huawei) provides r02 Qianghua (Huawei) provides r02, with the correct link Laurent (Nokia): provides r03 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.2 | S2-2201563 | P-CR | Approval | 23.700-74: New solution for WT2. | Nokia, Nokia Shanghai Bell | Rel-18 | Revision of S2-2200115r03. Approved | Approved | |
| 9.2 | S2-2200362 | P-CR | Approval | 23.700-74: A new Solution for KI#x on multiple SMFs for the VN . | ZTE | Rel-18 | r02 agreed. Revised to S2-2201564. | Stefan (Ericsson) asks questions for clarifications Zhendong (ZTE): provides response and r01 Laurent (Nokia): provides r02 ==== 8.X, 9.X, 10.X Revisions Deadline ==== Laurent (Nokia): can only live with r02; objects to any other version Zhendong (ZTE): is fine with r02 ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.2 | S2-2201564 | P-CR | Approval | 23.700-74: A new Solution for KI#x on multiple SMFs for the VN . | ZTE | Rel-18 | Revision of S2-2200362r02. Approved | Approved | |
| 9.2 | S2-2200655 | P-CR | Approval | 23.700-74: New Solution to Key Issue for FS_GMEC WT#2.1. | Huawei, HiSilicon | Rel-18 | r01 agreed. Revised to S2-2201565. | Laurent (Nokia): provides r01 ==== 8.X, 9.X, 10.X Revisions Deadline ==== Laurent (Nokia): can only live with r01; objects to any other version ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.2 | S2-2201565 | P-CR | Approval | 23.700-74: New Solution to Key Issue for FS_GMEC WT#2.1. | Huawei, HiSilicon | Rel-18 | Revision of S2-2200655r01. Approved | Approved | |
| 9.2 | - | - | - | Solution Proposal for WT#3 | - | - | Docs:=4 | - | |
| 9.2 | S2-2200116 | P-CR | Approval | 23.700-74: New solution for FS_GMEC WT3 | Nokia, Nokia Shanghai Bell | Rel-18 | r02 agreed. Revised to S2-2201566. | Qianghua (Huawei) asks questions Laurent (Nokia): provides r01 Sang-Jun (Samsung) comments. Zhendong (ZTE): provides comments Laurent (Nokia): answers on top of my previous sending (R01) Qianghua (Huawei) repeats comments Qianghua (Huawei) provides r02 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.2 | S2-2201566 | P-CR | Approval | 23.700-74: New solution for FS_GMEC WT3. | Nokia, Nokia Shanghai Bell | Rel-18 | Revision of S2-2200116r02. Approved | Approved | |
| 9.2 | S2-2200672 | P-CR | Approval | 23.700-74: New solution to Key Issue on Support for 5G Smart Energy and Infrastructure. | Samsung | Rel-18 | r04 agreed. Revised to S2-2201567. | Qianghua (Huawei) asks questions Sang-Jun (Samsung) provides response, and provides r01. Stefan (Ericsson) provides questions for clarification Sang-Jun (Samsung) provides responses, and provides r02. Zhendong (ZTE): ask question for clarification. Sebastian (Qualcomm) provides r03 Sang-Jun provides response to Zhendong and accepts EN in r03 provided by Sebastian. Laurent (Nokia): Many of Stefan's questions have not been answered. Do you plan to add corresponding EN? Stefan (Ericsson) provides r04 ==== 8.X, 9.X, 10.X Revisions Deadline ==== Sang-Jun (Samsung) accepts r04 ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.2 | S2-2201567 | P-CR | Approval | 23.700-74: New solution to Key Issue on Support for 5G Smart Energy and Infrastructure. | Samsung | Rel-18 | Revision of S2-2200672r04. Approved | Approved | |
| 9.3 | - | - | - | Study on Access Traffic Steering, Switching and Splitting support in the 5GS; Phase 3 (FS_ATSSS_Ph3) | - | - | Docs:=22 | - | |
| 9.3 | S2-2200755 | P-CR | Approval | 23.700-53: Technical Report | Lenovo, Motorola Mobility | Rel-18 | Approved | ==== 8.X, 9.X, 10.X Final Deadline ==== | Approved |
| 9.3 | S2-2200757 | P-CR | Approval | 23.700-53: Scope of TR 23.700-53. | Lenovo, Motorola Mobility | Rel-18 | Approved | ==== 8.X, 9.X, 10.X Final Deadline ==== | Approved |
| 9.3 | S2-2200758 | P-CR | Approval | 23.700-53: Architectural assumptions for ATSSS_Ph3. | Lenovo, Motorola Mobility | Rel-18 | r10 agreed. Revised to S2-2201334, merging S2-2201186 | Marco (huawei) proposes r01 following indication to merge with S2-2200753 Rainer (Nokia) provides r02. Curt (Charter) comments... Rainer (Nokia) provides r03. Apostolis (Lenovo) supports r03 and provides minor comments. Dieter (Deutsche Telekom) comments. Rainer (Nokia) replies. Apostolis (Lenovo) is fine with the proposed wording on steering functionalities. Dieter (Deutsche Telekom) is fine with the proposed wording by Rainer. Rainer (Nokia) provides r04. Marco (Huawei) comments. Curt (Charter) replies to Marco. Apostolis (Lenovo) provides r07 with more co-signing companies. Marco (Huawei) provides r09. Apostolis (Lenovo) is fine with r09. Florin (Broadcom) provides r10. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Stefan (Ericsson) OK with r10 ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.3 | S2-2201334 | P-CR | Approval | 23.700-53: Architectural assumptions for ATSSS_Ph3. | Lenovo, Motorola Mobility, Nokia, Nokia Shanghai Bell, Apple, Deutsche Telekom, Tencent, Broadcom | Rel-18 | Revision of S2-2200758r10, merging S2-2201186. Approved | Approved | |
| 9.3 | S2-2200753 | P-CR | Approval | 23.700-53: FS_ATSSS_Ph3 architecture requirements and assumptions. | Huawei, HiSilicon | Rel-18 | Merged into S2-2201809 | Dario S. Tonesi (Qualcomm) provides r01. Dieter (Deutsche Telekom) provides comments. Curt (Charter) proposes to merge this with S2-2200758 as they are (~100%) overlapping. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.3 | S2-2200516 | P-CR | Approval | 23.700-53: KI for WT#5.1. | Charter Communications, Lenovo, Motorola Mobility, CableLabs | Rel-18 | r11 agreed. Revised to S2-2201335, merging S2-2200846 | Guanzhou (InterDigital) asks a question for clarification. Curt (Charter) replies... Rainer (Nokia) provides r01. Curt (Charter) - thx Rainer...I m fine with r01. Marco (Huawei) proposes r02 for merging S2-220752. Krisztian (Apple) provides r03. Sebastian (MediaTek Inc.) provides r04. Stefan (Ericsson) comments and provides r05 Marco (Huawei) comments and provides r06 Marco (Huawei) provides r07 considering merging from S2-220752 Guanzhou (InterDigital) provides r08. Marco (Huawei) answer to Dario (Qualcomm) Dario (Qualcomm) asks questions Marco (Huawei) provide r09 Apostolis (Lenovo) provides r10. Apostolis (Lenovo) has concerns on r09 and provides comments. Sebastian (MediaTek Inc.) is fine with r10. No service continuity enhancement will be studied or defined. R16 baseline will be reused. Marco (Huawei) provide R11. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Marco (Huawei) OK r11 and objects from 00 to r10 Apostolis (Lenovo) prefers r10. The additional Note in r11 is not clear. ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.3 | S2-2201335 | P-CR | Approval | 23.700-53: KI for WT#5.1. | Charter Communications, Lenovo, Motorola Mobility, CableLabs, Nokia, Nokia Shanghai Bell, Apple | Rel-18 | Revision of S2-2200516r11, merging S2-2200846. Approved | Approved | |
| 9.3 | S2-2200517 | P-CR | Approval | 23.700-53: Key Issue #X: Support for Redundant Traffic Steering. | InterDigital Inc | Rel-18 | Merged into S2-2201750 | Dario S. Tonesi (Qualcomm) proposes to merge this paper into 0715 and take 0715 as baseline. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.3 | S2-2200715 | P-CR | Approval | 23.700-53: Key Issue for supporting redundant traffic steering with intelligent traffic duplication . | Nokia, Nokia Shanghai Bell | Rel-18 | r10 agreed. Revised to S2-2201336, merging S2-2200966 | Guanzhou (InterDigital) proposes merging S2-2200517 to S2-2200715 and provides r01. Myungjune (LGE) comments Rainer (Nokia) is ok with r01. Rainer (Nokia) replies to Myungjune (LGE). Yishan (Huawei) provides comments Stefan (Ericsson) comments Guanzhou (InterDigital) comments. Myungjune (LGE) comments. Dario (Qualcomm) provides r02 Myungjune (LGE) comments on r02 Yishan (Huawei) comments and provides r03 Rainer (Nokia) is ok with r03. Markus (Deutsche Telekom) provides r04. Rainer (Nokia) provides r05. Myungjune (LGE) questions on new bullet - how to treat duplicated packets. Markus (Deutsche Telekom) answers questions on new bullet - how to treat duplicated packets. Rainer (Nokia) replies. Markus (Deutsche Telekom) replies. Markus (Deutsche Telekom) replies to Rainer from Nokia. Myungjune (LGE) replies to Markus (Deutsche Telekom). Stefan (Ericsson) provides r05 Yishan (Huawei) provides r06 Markus (Deutsche Telekom) replies to Myungjune (LGE). Rainer (Nokia) provides r07. Guanzhou (InterDigital) comments on r07. Guanzhou (InterDigital) responds to Rainer(Nokia) comments. Myungjune (LGE) provides r08 Markus (Deutsche Telekom) comment to r08 Myungjune (LGE) responds to Markus (Deutsche Telekom) Stefan (Ericsson) provides r09 Dario (Qualcomm) provides r10 ==== 8.X, 9.X, 10.X Revisions Deadline ==== Marco (huawei) we are ok only with r10 Apostolis (Lenovo) is fine with r10. Dieter (Deutsche Telekom): we are also fine with r10. Please add Deutsche Telekom as supporting company. Dario (Qualcomm) asks to co-sign. ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.3 | S2-2201336 | P-CR | Approval | 23.700-53: Key Issue for supporting redundant traffic steering . | Nokia, Nokia Shanghai Bell, InterDigital, Deutsche Telekom, Qualcomm Incorporated | Rel-18 | Revision of S2-2200715r10, merging S2-2200966. Approved | Approved | |
| 9.3 | S2-2200751 | P-CR | Approval | 23.700-53: FS_ATSSS_Ph3 Key Issue of new steering functionalities. | Huawei, HiSilicon | Rel-18 | Merged into S2-2201809 | Dario S. Tonesi (Qualcomm) proposes to take 0760 as baseline for the discussion on this KI. Dieter (Deutsche Telekom) proposes to work on a single doc for that KI, i.e. to take 0760 as basis and consider this doc merged into 0760. Apostolis (Lenovo) agrees to merge this document into 0760. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.3 | S2-2200760 | P-CR | Approval | 23.700-53: KI on 'New steering functionalities for non-TCP traffic'. | Lenovo, Motorola Mobility, Apple, Broadcom | Rel-18 | r07 agreed. Revised to S2-2201337, merging S2-2200578 | Dario S. Tonesi (Qualcomm) comments Rainer (Nokia) provides r01. Markus (Deutsche Telekom) provides r02. Myungjune (LGE) questions on switching, splitting of Ethernet traffic. Markus (Deutsche Telekom) replies to Myungjune from LGE. Myungjune (LGE) replies to Markus (Deutsche Telekom) Stefan (Ericsson) provides r03 Apostolis (Lenovo) provides r04. Markus (Deutsche Telekom) replies to Myungjune (LGE). Dieter (Deutsche Telekom) comments. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.3 | S2-2201337 | P-CR | Approval | 23.700-53: KI on 'New steering functionalities for non-TCP traffic'. | Lenovo, Motorola Mobility, Apple, Broadcom, Deutsche Telekom | Rel-18 | Revision of S2-2200760r07, merging S2-2200578. Approved | Approved | |
| 9.3 | S2-2200752 | P-CR | Approval | 23.700-53: Key Issue of Supporting Traffic Switching between two Non-3GPP Access Paths. | Huawei, HiSilicon | Rel-18 | Merged into S2-2201359 | Curt (Charter) proposes to merge this with S2-2200516 as they both are describing the same KI. I propose that S2-2200516 is used as basis (due to more co-sourcing companies). Myungjune (LGE) comments Marco (Huawei) answer to Myungjune (LGE) ==== 8.X, 9.X, 10.X Revisions Deadline ==== Marco (Huawei) confirmed merged in 0516 ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.3 | S2-2200762 | P-CR | Approval | 23.700-53: KI for WT#6. | Lenovo, Motorola Mobility | Rel-18 | r01 agreed. Revised to S2-2201338. | Myungjune (LGE) comments Apostolis (Lenovo) answers Myungjune's (LGE) questions. Myungjune (LGE) replies to Apostolis (Lenovo) Apostolis (Lenovo) responds to Myungjune (LGE). Myungjune (LGE) responds to Apostolis (Lenovo). Myungjune (LGE) provides r01. Apostolis (Lenovo) is fine with r01. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.3 | S2-2201338 | P-CR | Approval | 23.700-53: KI for WT#6. | Lenovo, Motorola Mobility | Rel-18 | Revision of S2-2200762r01. Approved | Approved | |
| 9.3 | S2-2200856 | P-CR | Approval | 23.700-53: KI and solution for support of redundant traffic steering. | Huawei, HiSilicon | Rel-18 | r05 agreed. Revised to S2-2201339. | Apostolis (Lenovo) proposes to remove the KI from this document and consider only the solution. The KI for redundant traffic steering is captured in 0715. Rainer (Nokia) asks for clarification. Susan (Huawei) replies to Apostolis (Lenovo) and Rainer (Nokia). Stefan (Ericsson) provides questions Dario (Qualcomm) asks questions. Susan (Huawei) replies to Stefan and Dario, and provides r01. Rainer (Nokia) provides r02. Susan (Huawei) is ok with r02. Guanzhou(InterDigital) provides r03. Dario (Qualcomm) provides r04 Rainer (Nokia) is ok with r04. Curt (Charter) provides r05 Susan (Huawei) replies to Guanzhou, Dario and Curt. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Dario (Qualcomm) is OK with r05 Apostolis (Lenovo) is OK with r05 but makes a question. Rainer (Nokia) replies. ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.3 | S2-2201339 | P-CR | Approval | 23.700-53: KI and solution for support of redundant traffic steering. | Huawei, HiSilicon | Rel-18 | Revision of S2-2200856r05. Approved | Approved | |
| 9.3 | S2-2200857 | P-CR | Approval | 23.700-53: Solution for Multi-access between EPC and 5GC . | Huawei, HiSilicon | Rel-18 | r01 agreed. Revised to S2-2201340. | Stefan (Ericsson) provides comments Myungjune (LGE) provides comments Rainer (Nokia) comments. Susan (Huawei) replies to Rainer, Myungjune and Stefan, and provides r01. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.3 | S2-2201340 | P-CR | Approval | 23.700-53: Solution for Multi-access between EPC and 5GC . | Huawei, HiSilicon | Rel-18 | Revision of S2-2200857r01. Approved | Approved | |
| 9.3 | S2-2200983 | P-CR | Approval | 23.700-53: New Solution: MP-DCCP-LL based ATSSS steering functionality for Non-TCP traffic. | Deutsche Telekom AG, Vodafone, BT, Xiaomi | Rel-18 | r04 agreed. Revised to S2-2201341. | Rainer (Nokia) proposes to add ATSSS and MA rules impacts. Stefan (Ericsson) provides comments and questions Dario (Qualcomm) provides comments and suggests changes. Dieter (Deutsche Telekom) replies and provides r01. Rainer (Nokia) replies. Dario (Qualcomm) replies to Dieter and provides r02. Dario (Qualcomm) replies to Dieter. Dieter (Deutsche Telekom) replies to Dario. Florin (Broadcom) requests clarifications from authors Susan (Huawei) raises comments. Dieter (Deutsche Telekom) replies to Florin. Dieter (Deutsche Telekom) replies to Susan and provides r03. Dieter (Deutsche Telekom) provides r03. Florin (Broadcom) replies to Dieter (Deutsche Telekom) and provides r04 on top of r03. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Dario (Qualcomm) is OK with r04 Dieter (Deutsche Telekom) we are ok with r04. ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.3 | S2-2201341 | P-CR | Approval | 23.700-53: New Solution: MP-DCCP-LL based ATSSS steering functionality for Non-TCP traffic. | Deutsche Telekom AG, Vodafone, BT, Xiaomi, Huawei | Rel-18 | Revision of S2-2200983r04. Approved | Approved | |
| 9.4 | - | - | - | Study on enhanced support of Non-Public Networks phase 2 (FS_eNPN_Ph2) | - | - | Docs:=37 | - | |
| 9.4 | - | - | - | General (skeleton, scope) | - | - | Docs:=2 | - | |
| 9.4 | S2-2200487 | P-CR | Approval | 23.700-08: TR 23.700-08 skeleton | Ericsson (rapporteur) | Rel-18 | 23.700-08 TR Skeleton. Approved | ==== 8.X, 9.X, 10.X Final Deadline ==== | Approved |
| 9.4 | S2-2200488 | P-CR | Approval | 23.700-08: FS_eNPN_Ph2: Scope. | Ericsson | Rel-18 | Approved | ==== 8.X, 9.X, 10.X Final Deadline ==== | Approved |
| 9.4 | - | - | - | Terminology and definitions | - | - | Docs:=1 | - | |
| 9.4 | S2-2201182 | P-CR | Approval | 23.700-08: FS_eNPN_Ph2: terminology and definitions. | Xiaomi | Rel-18 | Noted | Peter (Ericsson) provides comments and asks why there is a need to define PALS as not used in stage 1? Jianning (Xiaomi) response to Peter (Ericsson) Josep (DT) proposes to NOTE. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== Jianning (Xiaomi) propose to accept this doc, since 'PALS' is used in the approved Key Issue (0723r08) | Noted |
| 9.4 | - | - | - | Architectural Assumptions and Requirements | - | - | Docs:=4 | - | |
| 9.4 | S2-2200489 | P-CR | Approval | 23.700-08: FS_eNPN_Ph2: Architectural Assumptions and Requirements. | Ericsson | Rel-18 | Approved | ==== 8.X, 9.X, 10.X Final Deadline ==== | Approved |
| 9.4 | S2-2200835 | P-CR | Approval | 23.700-08: 23.700-08: Architectural assumptions proposal . | Nokia, Nokia Shanghai Bell | Rel-18 | Noted | Antoine (Orange) comments. Peter Hedman (Ericsson) provides comments ==== 8.X, 9.X, 10.X Revisions Deadline ==== Antoine (Orange) objects. ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 9.4 | S2-2201181 | P-CR | Approval | 23.700-08: FS_eNPN_Ph2: Architectural Assumptions and Requirements. | Xiaomi | Rel-18 | r03 agreed. Revised to S2-2201749. | Antoine (Orange) provides r01. Jianning (Xiaomi) provide r02 Antoine (Orange) provides r03. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.4 | S2-2201749 | P-CR | Approval | 23.700-08: FS_eNPN_Ph2: Architectural Assumptions and Requirements. | Xiaomi | Rel-18 | Revision of S2-2201181r03. Approved | Approved | |
| 9.4 | - | - | - | Key Issue related to WT#1 | - | - | Docs:=6 | - | |
| 9.4 | S2-2200490 | P-CR | Approval | 23.700-08: Key issue (WT#1): Enhanced mobility between SNPNs. | Ericsson | Rel-18 | Merged into S2-2201750 | Peter (Ericsson) ok to note and consider merged into 00726 ==== 8.X, 9.X, 10.X Revisions Deadline ==== Josep (DT) objects to this pCR. ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.4 | S2-2200726 | P-CR | Approval | 23.700-08: Key Issue to enable optimized support for SNPN mobility in idle and connected mode. | Nokia, Nokia Shanghai Bell | Rel-18 | r09 agreed. Revised to S2-2201750, merging S2-2200517, S2-2200490 and S2-2200743 | Rainer (Nokia) provides r01. Ashok (Samsung) need clarification Jihoon (ETRI) provides r02. Fei (OPPO) asks clarification and provides comments on r02. Rainer (Nokia) replies. Josep (DT) comments, provides r03. Rainer (Nokia) provide r04. Jihoon (ETRI) replies to Rainer (Nokia). Fei (OPPO) provides r05. Rainer (Nokia) is ok with r05. Peter Hedman (Ericsson) provides r06 Rainer (Nokia) is ok with r06. Amanda Xiang ( Futurewei ) provides r07. Jianning (Xiaomi) provide view Yishan (Huawei) provides r08. Antoine (Orange) provides r09. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Peter Hedman (Ericsson) ok with r09 ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.4 | S2-2201750 | P-CR | Approval | 23.700-08: Key Issue to enable optimized support for SNPN mobility in idle and connected mode. | Nokia, Nokia Shanghai Bell, ETRI, OPPO, Ericsson, Futurewei | Rel-18 | Revision of S2-2200726r09, merging S2-2200517, S2-2200490 and S2-2200743. Approved | Approved | |
| 9.4 | S2-2200743 | P-CR | Approval | 23.700-08: Key issue on equivalent SNPNs. | OPPO | Rel-18 | Merged into S2-2201750 | Rainer (Nokia) asks whether this KI is needed and proposes to note 743. Peter Hedman (Ericsson) suggests to note and mark it as merged into 00726, I hope author can confirm Fei (OPPO) confirmed it can be noted and mark it as merged into basis. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.4 | S2-2200748 | P-CR | Approval | 23.700-08: FS_eNPN_Ph2 Key Issue for Objective: 1. | Huawei, HiSilicon | Rel-18 | Merged into S2-2201366 | Peter Hedman (Ericsson) suggests to note and mark it as merged into 00726, I hope author can confirm ==== 8.X, 9.X, 10.X Revisions Deadline ==== Josep (DT) objects to this pCR. ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.4 | S2-2200841 | P-CR | Approval | 23.700-08: New KI related with FS_eNPN_ph2 WT1. | Samsung | Rel-18 | Merged into S2-2201777 | Peter Hedman (Ericsson) suggests to note and mark it as merged into 00726, I hope author can confirm Kisuk (Samsung) agrees to merge into 00726. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.4 | - | - | - | Key Issue related to WT#2 | - | - | Docs:=5 | - | |
| 9.4 | S2-2200459 | P-CR | Approval | 23.700-08: Key issue on Support of non-3GPP accesses for SNPN services. | Lenovo, Motorola Mobility, Broadcom, Charter Communications, CableLabs, Intel, Ericsson | Rel-18 | Noted | Josep (DT) comments, provides r01. Rainer (Nokia) asks for clarification. Josep (DT) comments, suggests to bring more precise use cases in the KI scope. Rainer (Nokia) provides r02. Saso (Intel) seeks clarification on r02. Kisuk (Samsung) is ok with r02. Myungjune (LGE) questions on r01 Rainer (Nokia) replies. Huan (vivo) comments on r02 and provides r03 Genadi (Lenovo) has similar concerns as Myungjune (LGE) to r01. Genadi (Lenovo) replies to Rainer (Nokia). Yishan (Huawei) provides r04 Rainer (Nokia) comments. Haris(Qualcomm) provides r04 Rainer (Nokia) asks. Josep (DT) comments on r04's additions. Josep (DT) re-asks his comments. R04 is from Yishan(Huawei). Rainer (Nokia) is ok with this revised wording. Marco (Huawei) reply to Josep (DT) on r04. Yishan (Huawei) provides r05 Myungjune (LGE) comments Josep (DT) comments, questions the use case of WWC for SNPN. Yishan (Huawei) replies to Myungjune (LGE) Yishan (Huawei) answers to Josep (DT) Haris(Qualcomm) provides r06 Curt (Charter) comments... Saso (Intel) comments on r06 and objects to r06. Josep (DT) is not convinced that including Wireline 5G Access is useful for SNPNs, objects to r06. Marco (Huawei) object to r06. Curt (Charter) objects to r07. R05 is fine for us. Ashok (Samsung) need clarification on 4th scenario Myungjune (LGE) provides r08 based on r05 Omkar (CableLabs) objects to r07. CLs is also ok with R05. Josep (DT) comments, provides r09 based on r05. Haris(Qualcomm) accepts only r06, objects to all other revisions Myungjune (LGE) replies to Josep (DT) Saso (Intel) points to Haris that that the KI in 0459 follows closely the existing definition of this KI in 23.700-07; provides r10. Haris(Qualcomm) asks question to Myungjune (LGE) Myungjune (LGE) replies to Haris (Qualcomm) Josep (DT) comments, provides r11. Myungjune (LGE) comments, provides r12. Genadi (Lenovo) replies to Haris (Qualcomm) and proposes to agree r11. marco (Huawei) comments and provides r13. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Josep (DT) objects to revision r00-r06, r08, r10, r12. Very much prefers r13 Rainer (Nokia) is ok with r13. Saso (Intel) can accept any revision in the r07-r13 range; prefers r13 Ashok (Samsung) comments Peter Hedman (Ericsson) ok with r13 Genadi (Lenovo) is OK with r13. Haris(Qualcomm) only r06 is acceptable, objects to all other revisions Marco(Huawei) ok R13, r08 objects to r06 Haris(Qualcomm) comments Marco (huawei) answers to Ashok (Samsung) Saso (Intel) comments that 0459r13 does not restrict the solution space; the solutions on this WT submitted for this meeting are being progressed. ==== 8.X, 9.X, 10.X Final Deadline ==== Genadi (Lenovo) comments to Haris(Qualcomm). Josep (DT) replies to Marco (Huawei). Curt (Charter) just to say that r13 is fine too. | Noted |
| 9.4 | S2-2200722 | P-CR | Approval | 23.700-08: FS_eNPN_Ph2 KI proposal - WT2. | vivo | Rel-18 | Merge into revision of S2-2200459 (Noted). Noted | Peter Hedman (Ericsson) suggests to note and mark it as merged into 00459, I hope author can confirm Huan (vivo) confirm to merged 00722 into 00459 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 9.4 | S2-2200727 | P-CR | Approval | 23.700-08: Key Issue for support of non-3GPP access to SNPN. | Nokia, Nokia Shanghai Bell | Rel-18 | Merge into revision of S2-2200459 (Noted). Noted | Peter Hedman (Ericsson) suggests to note and mark it as merged into 00459, I hope author can confirm ==== 8.X, 9.X, 10.X Revisions Deadline ==== Josep (DT) objects to this pCR. ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 9.4 | S2-2200749 | P-CR | Approval | 23.700-08: FS_eNPN_Ph2 Key Issue for Objective: 2. | Huawei, HiSilicon | Rel-18 | Merged into S2-2201357 | Peter Hedman (Ericsson) suggests to note and mark it as merged into 00459, I hope author can confirm ==== 8.X, 9.X, 10.X Revisions Deadline ==== Josep (DT) objects to this pCR. ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.4 | S2-2200862 | P-CR | Approval | 23.700-08: KI related with FS_eNPN_ph2 WT2. | Samsung | Rel-18 | Merge into revision of S2-2200459 (Noted). Noted | Peter Hedman (Ericsson) suggests to note and mark it as merged into 00459, I hope author can confirm Kisuk (Samsung) agrees to merge into 00459. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 9.4 | - | - | - | Key Issue related to WT#5 | - | - | Docs:=12 | - | |
| 9.4 | S2-2200491 | P-CR | Approval | 23.700-08: Key issue (WT#5): NPN supports of providing access to localized services. | Ericsson, Futurewei | Rel-18 | CC#5: r22 + changes agreed. Revised to S2-2201860, merging S2-2200903, S2-2200520, S2-2200521, S2-2200750, S2-2200834 and S2-2200839 | Peter (Ericsson) provides comments and r01 merging in related tdocs Ashok (Samsung) comments Guanzhou (InterDigital) proposes to keep 0522/0723 as separate KI . Huan (vivo) proposes to keep 0522/0723 as separate KI . Pallab (Nokia) comments on r01 and provides r02 Jinsook (DISH) provides comments. Ellen (Intel) comments on r02 and provides r03 Guanzhou (InterDigital) provides r04 and co-signs. Huan (vivo) provides r05 and co-signs. Guanzhou (InterDigital) responds to Ashok (Samsung)'s comment. Genadi (Lenovo) provides r06. Ashok (Samsung) responds to Genadi (Lenovo) Genadi (Lenovo) replies to Ashok (Samsung). Peter Hedman (Ericsson) provides r07 Guanzhou (InterDigital) responds to Genadi. Miguel (Qualcomm) provides r08 Jianning (Xiaomi) provide comment Josep (DT) proposes major rewriting of the text, provides r09. Guanzhou (InterDigital) responds to Jiannning (Xiaomi). Guanzhou (InterDigital) comments on r09. Josep (DT) comments, provices r10. Josep (DT) further clarifies charging, provides r11. Walter Dees (Philips) provides r12. Antoine (Orange) provides r13. Antoine (Orange) provides r15. Curt (Charter) provides r14. Walter Dees (Philips) provides clarification on service operator term Peter Hedman (Ericsson) provides r16 Antoine (Orange) provides r17. Miguel (Qualcomm) comments, provides r18 Walter Dees (Philips) provides r19 Josep (DT) provides r20 based on r18, disagrees with r19. Antoine (Orange) provides r21. Peter Hedman (Ericsson) provides r22 Walter Dees (Philips) cannot agree r20 and r21 and provides r23 Guanzhou(InterDigital) comments on automatic selection of hosting network . ==== 8.X, 9.X, 10.X Revisions Deadline ==== Peter Hedman (Ericsson) provides reply Walter Dees (Philips) replies to Guanzhou (Interdigital) Guanzhou(InterDigital) responds to Walter Dees (Philips). Josep (DT) additionally objects to r23, r19. Jianning (Xiaomi) shares the view with Ashok (Samsung), can not agree any version mandating the prior subscription with hosting network Josep (DT) comments, points out to the eMeeting rules. Pallab (Nokia) proposes to go with r22 after changing 'would be triggered' to 'would be triggered or controlled' in bullet 5 of 5.Y.1 Josep (DT) would be fine to go with r22 + 'is triggered or controlled'. Walter Dees (Philips) can only agree to r19 or r23 regarding the bullet on manual selection and suggests way forward Josep (DT) comments. Peter Hedman (Ericsson) ok with r23 (with or without additional EN) Guanzhou(InterDigital) prefers to go with r23. Walter (Philips) clarifies to Peter (Ericsson) and Josep (DT) Antoine (Orange) prefers r21, can accept as a compromise r22 with 'would be triggered' replaced by 'is triggered or controlled', objects other versions. Miguel (Qualcomm) objects to r21, r22, r23 ok with r20 Yishan (Huawei) prefers r23, can live with r22 and r21 ==== 8.X, 9.X, 10.X Final Deadline ==== Genadi (Lenovo) prefers r23 with additions to be agreed during CC#4. Josep (DT) replies to Miguel (Qualcomm). Miguel (Qualcomm) responds to Josep (DT). Josep (DT) replies. Comments that the case highlighted by Miguel is by definition a 'no service requirements exist in TS 22.261' case. Miguel (Qualcomm) points to the service requirements in TS 22.261 | Revised |
| 9.4 | S2-2201751 | P-CR | Approval | 23.700-08: Key issue (WT#5): NPN supports of providing access to localized services. | Ericsson, Futurewei | Rel-18 | CC#2: WITHDRAWN | Withdrawn | |
| 9.4 | S2-2201860 | P-CR | Approval | : Key issue (WT#5): NPN supports of providing access to localized services. | Ericsson, Futurewei, Nokia, Nokia Shanghai Bell, Intel, InterDigital, vivo, Lenovo, Motorola Mobility, Qualcomm Inc. | Rel-18 | CC#5: Revision of S2-2200491r22 + changes, merging S2-2200903, S2-2200520, S2-2200521, S2-2200750 and S2-2200839. Approved | Approved | |
| 9.4 | S2-2200520 | P-CR | Approval | 23.700-08: New Key Issue: Discovery, selection and access of hosting network | InterDigital | Rel-18 | Merged into S2-2201860 | Peter Hedman (Ericsson) suggests to note and mark it as merged into 00491, I hope author can confirm Guanzhou (InterDigital) confirms that this is merged into 00491. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.4 | S2-2200521 | P-CR | Approval | 23.700-08: Key Issue: Network steering between local hosting network and home network . | InterDigital, FutureWei | Rel-18 | Merged into S2-2201860 | Peter Hedman (Ericsson) suggests to note and mark it as merged into 00491, I hope author can confirm Guanzhou (InterDigital) confirms this is merged into 00491. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.4 | S2-2200522 | P-CR | Approval | 23.700-08: Key Issue: Overload control when returning to Home Network . | InterDigital | Rel-18 | Merged into S2-2201752 | Peter Hedman (Ericsson) suggests to note and mark it as merged into 00723, I hope author can confirm Guanzhou (InterDigital) confirms this is merged into 00723. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.4 | S2-2200723 | P-CR | Approval | 23.700-08: FS_eNPN_Ph2 KI proposal of Returning to Home Network. | vivo | Rel-18 | r08 agreed. Revised to S2-2201752, merging S2-2201115 and S2-2200522 | Huan (vivo) provides r01 of merge with 2200522 and 2200723 Kisuk(Samsung) is fine with r01. Guanzhou (InterDigital) provides r02 for some minor editorial change. Pallab (Nokia) asks questions on r02. Pallab (Nokia) provides r03. Huan (vivo) provides r04. Pallab (Nokia) provides r05. Josep (DT) has the same view as Pallab (Nokia). Yishan (Huawei) suggests that the KI shall be part of the KI#Z in 0491 Marco (Huawei) provide r06 for technical part (valid even if it is merged in 0491) Huan (vivo) provide r07 and provides feedback Huan (vivo) provide r08 Yishan (Huawei) is fine with r08 Josep (DT) thinks that it is too early to agree on solutions given that the KI is not yet agreed. Huan (vivo) asks for clarification ==== 8.X, 9.X, 10.X Revisions Deadline ==== Josep (DT) apologizes. He may have sent the email to the wrong thread... Huan (vivo) thanks DT for clarifications Pallab (Nokia) is fine with r08 Peter Hedman (Ericsson) ok with r08 ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.4 | S2-2201752 | P-CR | Approval | 23.700-08: FS_eNPN_Ph2 KI proposal of Returning to Home Network. | Vivo, InterDigital | Rel-18 | Revision of S2-2200723r08, merging S2-2201115 and S2-2200522. Approved | Approved | |
| 9.4 | S2-2200750 | P-CR | Approval | 23.700-08: FS_eNPN_Ph2 Key Issue for Objective: 3. | Huawei, HiSilicon | Rel-18 | Merged into S2-2201860 | Peter Hedman (Ericsson) suggests to note and mark it as merged into 00491, I hope author can confirm ==== 8.X, 9.X, 10.X Revisions Deadline ==== Josep (DT) objects to this pCR. ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.4 | S2-2200834 | P-CR | Approval | 23.700-08: Key Issues for supporting UE to discover, select, access services offered by SNPN. | Nokia, Nokia Shanghai Bell | Rel-18 | Merged into S2-2201860 | Peter Hedman (Ericsson) suggests to note and mark it as merged into 00491, I hope author can confirm ==== 8.X, 9.X, 10.X Revisions Deadline ==== Josep (DT) objects to this pCR. ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.4 | S2-2200839 | P-CR | Approval | 23.700-08: KI related with FS_eNPN_ph2 WT5. | Samsung | Rel-18 | Merged into S2-2201860 | Peter Hedman (Ericsson) suggests to note and mark it as merged into 00491, I hope author can confirm Kisuk (Samsung) agrees to merge into 00491. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.4 | S2-2201183 | P-CR | Approval | 23.700-08: FS_eNPN_Ph2: KI support for PALS. | Xiaomi | Rel-18 | Merged into S2-2201753 | Peter Hedman (Ericsson) suggests to note and mark it as merged into 00491, I hope author can confirm Jianning (Xiaomi) is ok to merge into 00491 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.4 | - | - | - | Solutions related to WT#1 | - | - | Docs:=3 | - | |
| 9.4 | S2-2200492 | P-CR | Approval | 23.700-08: Solution (WT#1): Enable efficient mobility via equivalent SNPNs. | Ericsson | Rel-18 | r04 agreed. Revised to S2-2201753, merging S2-2201183 and S2-2200744 | Rainer (Nokia) asks for clarification. Josep (DT) asks for clarification, similary questions as Rainer (Nokia). Huan (vivo) asks for clarification Peter Hedman (Ericsson) provides r01 Fei (OPPO) provides r02 which merges difference of S2-2200744 Peter Hedman (Ericsson) provides r03 Huan (vivo) provides feedback to Peter Huan (vivo) provides r04 link ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.4 | S2-2201753 | P-CR | Approval | 23.700-08: Solution (WT#1): Enable efficient mobility via equivalent SNPNs. | Ericsson, OPPO | Rel-18 | Revision of S2-2200492r04, merging S2-2201183 and S2-2200744. Approved | Approved | |
| 9.4 | S2-2200744 | P-CR | Approval | 23.700-08: Solution for equivalent SNPNs. | OPPO | Rel-18 | Merged into S2-2201753 | Rainer (Nokia) proposes to merge 744 in 492. Fei (OPPO) provides r01. Yishan (Huawei) asks for clarification. Fei (OPPO) responds to Yishan (Huawei) ==== 8.X, 9.X, 10.X Revisions Deadline ==== Fei (OPPO) it can be merged into S2-2200492 Peter Hedman (Ericsson) propose to note the P-CR as merged into S2-2200492 ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.4 | - | - | - | Solutions related to WT#2 | - | - | Docs:=4 | - | |
| 9.4 | S2-2200493 | P-CR | Approval | 23.700-08: Solution (WT#2): Providing selected SNPN ID over NGAP to AMF for non-3GPP access. | Ericsson | Rel-18 | Noted | Rainer (Nokia) asks for clarification. Josep (DT) also feels that this is an incomplete solution. Yishan (Huawei) share the same concern as Josep (DT) Peter Hedman (Ericsson) provides r01 and comments Josep (DT) comments that then it should not be called 'solution'. Peter Hedman (Ericsson) provides reply ==== 8.X, 9.X, 10.X Revisions Deadline ==== Josep (DT) comments. Rainer (Nokia) objects to 493. Peter Hedman (Ericsson) provides reply to Nokia Rainer (Nokia) replies. Yishan (Huawei) agrees with Nokia and proposes to object S2-2200493 ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 9.4 | S2-2201146 | P-CR | Approval | 23.700-08: Solutions for access to SNPN services via Untrusted and Trusted non-3GPP access network. | Intel | Rel-18 | Noted. CC#5: r03 + changes agreed. Revised to S2-2201850. | Rainer (Nokia) comments. Yishan (Huawei) comments. Apostolis (Lenovo) provides r01 and comments. Saso (Intel) replies and provides r02. Curt (Charters) asks question about the NWt aspect. Rainer (Nokia) provides r03. Saso (Intel) is OK with r03. Saso (Intel) replies to Curt (Charters). ==== 8.X, 9.X, 10.X Revisions Deadline ==== Apostolis (Lenovo) is also OK with r03. Rainer (Nokia) replies. Peter Hedman (Ericsson) unfortunately we need some common grounds, object to r00, r01, r02, r03 as solutions are not complete as per conditions expressed by others ==== 8.X, 9.X, 10.X Final Deadline ==== Saso (Intel) considers this objection from Peter Hedman (Ericsson) completely unjustified. Intel did not even make any comment on 0493! There is no reason for Ericsson to object to 1146 just because someone objected to Ericsson's solution in 0493. And Ericsson did not comment on 1146 before the revision deadline. Peter Hedman (Ericsson) provides reply | Revised |
| 9.4 | S2-2201850 | P-CR | Approval | 23.700-08: Solutions for access to SNPN services via Untrusted and Trusted non-3GPP access network. | Intel, Nokia, Nokia Shanghai Bell, Ericsson | Rel-18 | Revision of S2-2201146r03 + changes. Approved | Approved | |
| 9.4 | S2-2201193 | P-CR | Approval | 23.700-08: Solution for lightweight architecture for support of WLAN in SNPN . | Qualcomm Incorporated | Rel-18 | Noted | Josep (DT) asks question for clarification. Haris(Qualcomm) provides responses Josep (DT) comments. Rainer (Nokia) asks for clarification. Genadi (Lenovo) provides questions for clarification. Saso (Intel) comments. Haris(Qualcomm) provides responses to comments received and provides r01 Saso (Intel) provides r02. Josep (DT) find the solution quite incomplete, provides r03. Marco (Huawei) provides r04 Haris(Qualcomm) provides r05 Saso(Intel) provides r06 Florin (Broadcom) requests further clarifications regarding the mobility aspects of the proposed solution. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Haris(Qualcomm) responds Josep (DT) objects to this pCR. ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 9.5 | - | - | - | Study on Phase 2 for UAS, UAV and UAM (FS_UAS_Ph2) | - | - | Docs:=21 | - | |
| 9.5 | S2-2201196 | P-CR | Approval | 23.700-58: TR Skeleton | QUALCOMM Europe Inc. - Italy | Rel-18 | 23.700-58 TR Skeleton. Approved | ==== 8.X, 9.X, 10.X Final Deadline ==== | Approved |
| 9.5 | S2-2201198 | P-CR | Approval | 23.700-58: TR 23.700-58: Scope . | Qualcomm Incorporated | Rel-18 | Approved | Shabnam (Ericsson) comments that first case should be further clarified to expand on Rel-18 scope, provides further details. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Approved |
| 9.5 | S2-2201199 | P-CR | Approval | 23.700-58: TR 23.700-58: References and Abbreviations . | Qualcomm Incorporated | Rel-18 | r01 agreed. Revised to S2-2201342. | LaeYoung (LGE) provides r01. Stefano (Qualcomm) is of course OK with r01 and thanks LaeYoung. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.5 | S2-2201342 | P-CR | Approval | 23.700-58: TR 23.700-58: References and Abbreviations . | Qualcomm Incorporated | Rel-18 | Revision of S2-2201199r01. Approved | Approved | |
| 9.5 | S2-2201200 | P-CR | Approval | 23.700-58: TR 23.700-58 FS_UAS_Ph2 Architectural Assumptions Requirements. | Qualcomm Incorporated | Rel-18 | r01 agreed. Revised to S2-2201343. | Runze (Huawei) comments. Stefano (Qualcomm) provide R01. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.5 | S2-2201343 | P-CR | Approval | 23.700-58: TR 23.700-58 FS_UAS_Ph2 Architectural Assumptions Requirements. | Qualcomm Incorporated | Rel-18 | Revision of S2-2201200r01. Approved | Approved | |
| 9.5 | S2-2200518 | P-CR | Approval | 23.700-58: Architectural requirements and assumptions. | InterDigital, Oppo | Rel-18 | r11 agreed. Revised to S2-2201344. | Stefano (Qualcomm) provides r01. Runze (Huawei) comments. Shabnam (Ericsson) asks clarifications and comments. Stefano (Qualcomm) comments. Guanzhou (InterDigital) responds to Shabnam(Ericsson)'s comments. Runze (Huawei) replies. Guanzhou(InterDigital) provides r03 based on r01 and can't accept r02. Runze (Huawei) can only accept r02. Stefano (Qualcomm) re-iterate concerns about mentioning MBS and support Ericsson, cannot accept R05. Shabnam (Ericsson) Ericsson would have a problem including MBS directly into the discussion without actual input paper showing how it would work, so I suggest either rephrase as example or remove MBS. Amanda (Futurewei) provides r05 regarding the MBS issue. Tricci (OPPO) shares the same concern as Qualcomm, Ericsson, InterDigital, LG and MITRE. However, in order to find a possible way forward given the tight timeline that we have without stalling the progress, OPPO proposes r06 with a note as a compromise suggestion. LaeYoung (LGE) has similar view with Qualcomm, Ericsson and MITRE and does not prefer to capture MBS related Architectural Requirement at this stage. We can discuss how MBS can be used as solution. Tricci (OPPO) apologizes for forgetting to include r06 reference in previous email. Please see below for the server link for r06. Stefano (Qualcomm) thanks Tricci and provides R07. Tricci (OPPO) thanks Stefano (Qualcomm) acceptance of the compromise and to provide better revision R07. OPPO supports r07. Antoine (Orange) provides r08. Runze (Huawei) replies to Stefano (Qualcomm) and objects to all the revisions only with 'PC5 based solution'. Antoine (Orange) asks a clarification on MBS requirement in r02. Runze (Huawei) provides r09 and r10. Stefano (Qualcomm) provides r11. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Guanzhou(InterDigital) OK with r11 and comments. LaeYoung (LGE) is fine with r11. Runze (Huawei) replies to Antoine (Orange). Tricci (OPPO) is okay with r11. Thanks. ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.5 | S2-2201344 | P-CR | Approval | 23.700-58: Architectural requirements and assumptions. | InterDigital, Oppo, Qualcomm | Rel-18 | Revision of S2-2200518r11. Approved | Approved | |
| 9.5 | S2-2200519 | P-CR | Approval | 23.700-58: New Key Issue: Support for direct C2 communication . | InterDigital | Rel-18 | Merged into S2-2201345 | Tricci (OPPO) asks for clarifications. Guanzhou (InterDigital) responds to Tricci (Oppo)'s questions. Tricci (OPPO) thanks Guanzhou (InterDigital) feedback and provides further comments. Guanzhou (InterDigital) further comments. Stefano (Qualcomm) provides comments and expresses concerns. Tricci (OPPO) thanks both Stefano (Qualcomm) and Guanzhou (InterDigital) clarifications. Guanzhou (InterDigital) responds to Stefano(Qualcomm) comments. Stefano (Qualcomm) replies to comments and points to a revision of 1210 for a merger. Runze (Huawei) proposes to merge this paper into 2201210. Guanzhou (InterDigital) confirms this is merged into S2-2201210. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.5 | S2-2200892 | P-CR | Approval | 23.700-58: KI for WT#2.1 for transporting Broadcast Remote Id and C2 Communication. | OPPO | Rel-18 | Merged into S2-2201346 | Stefano (Qualcomm) recommends considering this merged for the first key issue with 1201, and for the second issue with 1210. Tricci (OPPO) thanks Stefano (Qualcomm) for the suggestion of the merge. OPPO agrees with your suggestion. Thanks. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.5 | S2-2201093 | P-CR | Agreement | 23.700-58: 23.700-58: KI on C2 communications via the 3GPP system. | Nokia, Nokia Shanghai Bell | Rel-18 | Merged into S2-2201345 | Stefano (Qualcomm) proposes to note because the KI has no justification wrt the SID and the requirements. Pallab (Nokia) responds to Stefano (Qualcomm). Stefano (Qualcomm) after seeing some explanation has more reasons to ask for this to be noted being out of scope of the current SID. Guanzhou (InterDigital) shares the view that the KI proposal is not aligned with the SID objective . Shabnam (Ericsson) believes we can focus on 1210 for this KI, together with the architectural assumptions/requirements this pCR goals can be considered covered. Pallab (Nokia) OK to NOTE or merge to 1210 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.5 | S2-2201210 | P-CR | Approval | 23.700-58: 23.700-58: KI on C2 over PC5 for WT#2.1. | Qualcomm Incorporated | Rel-18 | r05 agreed. Revised to S2-2201345, merging S2-2201187, S2-2200519 and S2-2201093 | Stefano (Qualcomm) provides r01. Guanzhou (InterDigital) is OK with r01 and confirms co-signing. Antoine (Orange) asks clarification on radio resources not belonging to the MNO. Stefano (Qualcomm) provides r02 and responds to Antoine. Shabnam (Ericsson) proposes to add references to V2X and ProSe specs where out of coverage etc. are defined. Tricci (OPPO) confirms merging 2nd KI from 0892 into 1210 and provides r03. LaeYoung (LGE) provides r04. Antoine (Orange) provides r05. Stefano (Qualcomm) answers to Shabnam. Shabnam (Ericsson) asks clarification. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Tricci (OPPO) is okay with r05. ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.5 | S2-2201345 | P-CR | Approval | 23.700-58: 23.700-58: KI on C2 over PC5 for WT#2.1. | Qualcomm Incorporated, Oppo, Interdigital, LG Electronics | Rel-18 | Revision of S2-2201210r05, merging S2-2201187, merging S2-2201187 and S2-2200519, merging S2-2201187, S2-2200519 and S2-2201093. Approved | Approved | |
| 9.5 | S2-2200778 | P-CR | Approval | 23.700-58: Key Issue Proposal on Support of Broadcast Remote Identification Transport. | Huawei, HiSilicon | Rel-18 | Merged into S2-2201346 | Stefano (Qualcomm) provides a suggested way forward and R01. LaeYoung (LGE) asks a Q for clarification. Pallab (Nokia) asks for clarification. Shabnam (Ericsson) support previous speakers that this pCR can be considered merged into 1201, also this is a bit too soln specific and prefer KIs to be more agnostic to solns. LaeYoung (LGE) also proposes to merge this paper into 1201. Runze (Huawei) is fine to merge this paper into 1201. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.5 | S2-2200831 | P-CR | Approval | 23.700-58: 23.700-58: KI on loss of UAV control due to network-initiated events. | Nokia, Nokia Shanghai Bell, InterDigital | Rel-18 | Noted | Stefano (Qualcomm) requests the document to be noted. Pallab (Nokia) agrees to NOTE this paper based on offline discussion. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 9.5 | S2-2200921 | P-CR | Approval | 23.700-58: KI for WT#2.2 for supporting DAA using enhanced existing mechanism. | OPPO | Rel-18 | Merged into S2-2201347 | Shabnam (Ericsson) can we consider this document merged into 1211? There is no reason to have two pCRs for same KI. Tricci (OPPO) thanks Shabnam (Ericsson) reminder. OPPO agrees 0921 to be merged into 1211. Thanks. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.5 | S2-2201092 | P-CR | Approval | 23.700-58: New KI on how to supporting aviation applications. | China Mobile | Rel-18 | Merged into S2-2201347 | Stefano (Qualcomm) proposes to merge the document into 1211. Aihua(CMCC) is fine to merge this paperinto 1211. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.5 | S2-2201201 | P-CR | Approval | 23.700-58: 23.700-58: KI on BRID for WT#2.1. | Qualcomm Incorporated | Rel-18 | r03 agreed. Revised to S2-2201346, merging S2-2200778 and S2-2200892 | Tricci (OPPO) asks for clarification. Stefano (Qualcomm) replies to Oppo. LaeYoung (LGE) provides r01. Tricci (OPPO) thanks LaeYoung (LGE) help to explain my questions to Qualcomm. It is all good and understood now. Stefano (Qualcomm) provides r02. Runze (Huawei) comments. Stefano (Qualcomm) provides r03. Runze (Huawei) accepts r03. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.5 | S2-2201346 | P-CR | Approval | 23.700-58: 23.700-58: KI on BRID for WT#2.1. | Qualcomm Incorporated | Rel-18 | Revision of S2-2201201r03, merging S2-2200778, merging S2-2200778 and S2-2200892. Approved | Approved | |
| 9.5 | S2-2201211 | P-CR | Approval | 23.700-58: 23.700-58: KI#1 on DAA for WT#2.2. | Qualcomm Incorporated | Rel-18 | r04 agreed. Revised to S2-2201347, merging S2-2200921 and S2-2201092 | Tricci (OPPO) asks for clarifications. Stefano (Qualcomm) replies to Oppo. Guanzhou (InterDigital) provides r01 and co-signs. Stefano (Qualcomm) is OK with R01 and replies to Oppo. Pallab (Nokia) asks for clarification. Tricci (OPPO) merges 0921 and first KI from 0892 into 1211 and provides r02. Pallab (Nokia) responds to Stefano. Stefano (Qualcomm) responds to Pallab and provides R. Pallab (Nokia) responds to Stefano. OK with r03 Guanzhou (InterDigital) is OK with r03. Amanda ( Futurewei ) provides r04 ==== 8.X, 9.X, 10.X Revisions Deadline ==== Tricci (OPPO) also prefers r03 and not sure about r04 because the reading of the 2nd bullet is a bit awkward. Amanda ( Futurewei) can not accept r03, but only r04 ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.5 | S2-2201347 | P-CR | Approval | 23.700-58: 23.700-58: KI#1 on DAA for WT#2.2. | Qualcomm Incorporated, InterDigital, OPPO, Futurewei | Rel-18 | Revision of S2-2201211r04, merging S2-2200921, merging S2-2200921 and S2-2201092. Approved | Approved | |
| 9.6 | - | - | - | Study on Extensions to the TSC Framework to support DetNet (FS_DetNet) | - | - | Docs:=19 | - | |
| 9.6 | - | - | - | General (skeleton, scope) | - | - | Docs:=3 | - | |
| 9.6 | S2-2200304 | P-CR | Approval | 23.700-46: TR 23.700-46: Study on 5GS DetNet interworking | Ericsson | 23.700-46 TR Skeleton. Approved | ==== 8.X, 9.X, 10.X Final Deadline ==== | Approved | |
| 9.6 | S2-2200305 | P-CR | Approval | 23.700-46: Scope and Assumptions for the DetNet study. | Ericsson | Rel-18 | r01 agreed. Revised to S2-2201754. | Laurent (Nokia): provides r01 Laurent (Nokia): proposes to merge all architectural assumptions in one single Tdoc (0291) György (Ericsson) comments. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.6 | S2-2201754 | P-CR | Approval | 23.700-46: Scope and Assumptions for the DetNet study. | Ericsson | Rel-18 | Revision of S2-2200305r01. Approved | Approved | |
| 9.6 | - | - | - | Architecture Assumption | - | - | Docs:=4 | - | |
| 9.6 | S2-2200307 | P-CR | Approval | 23.700-46: Clarifying assumptions for the DetNet study. | Ericsson | Rel-18 | r01 agreed. Revised to S2-2201755. | György (Ericsson) provides r01. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.6 | S2-2201755 | P-CR | Approval | 23.700-46: Clarifying assumptions for the DetNet study. | Ericsson | Rel-18 | Revision of S2-2200307r01. Approved | Approved | |
| 9.6 | S2-2200291 | P-CR | Approval | 23.700-46: Architecture assumption for DetNet . | Nokia, Nokia Shanghai Bell | Rel-18 | r06 + remove figure agreed. Revised to S2-2201756. | György (Ericsson) comments. Laurent (Nokia): provides r01 Laurent (Nokia): provides r02 that adds Ericsson as co-source (merge) Zhendong (ZTE): provides comments Saso (Intel) comments György (Ericsson) provides r03. Laurent (Nokia): provides r04 Sebastian (Qualcomm) provides r05 Haiyang (Huawei) comments György (Ericsson) provides r06 György (Ericsson) provides r07 Laurent (Nokia): provides r08 ==== 8.X, 9.X, 10.X Revisions Deadline ==== György (Ericsson) responds to Laurent and proposes to go with r07, or 06 as a fallback. Laurent (Nokia): objects to R07, R06, R03, R00. Can live with R05 (looks the best) , R08. R08 is already a strong compromise effort as it has It is FFS whether the NEF Sebastian (Qualcomm) suggests to move ahead with r05; objects to r00-r04 and r08 Haiyang (Huawei) comments that we should not change IETF protocols in 3GPP György (Ericsson) proposes to go with r09: based on r06 and an additional Editor's note: The protocol interactions between TSCTSF and the DetNet controller are FFS. Sebastian (Qualcomm) is ok with the proposal by György Zhendong (ZTE): provides the response Zhendong (ZTE): is fine with György proposal ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.6 | S2-2201756 | P-CR | Approval | 23.700-46: Architecture assumption for DetNet . | Nokia, Nokia Shanghai Bell, Ericsson | Rel-18 | Revision of S2-2200291r06 + remove figure. Approved | Approved | |
| 9.6 | - | - | - | Key Issues | - | - | Docs:=7 | - | |
| 9.6 | S2-2200267 | P-CR | Approval | 23.700-46: New Key Issue: Parameter mapping between DetNet controller and 5G system. | Huawei, HiSilicon | Rel-18 | r08 agreed. Revised to S2-2201757, merging S2-2200620, S2-2200731, S2-2200829 and S2-2200962 | Laurent (Nokia): provides r01 Laurent (Nokia): provides r02, as R01 had a mistake. Plesae disregard R01 Laurent (Nokia): please see the mail carrying 292 R02 to see how a merge 267+292+357+962+956 (non OAM part) could be made György (Ericsson) provides r03. Jari (NTT DOCOMO) provides r04. György (Ericsson) provides r05. Laurent (Nokia): provides r06 Laurent (Nokia): provides r07 György (Ericsson): provides r08 Jari (NTT DOCOMO) provides r09 György (Ericsson) proposes to go with r08. Jari (NTT DOCOMO) prefers r09. György (Ericsson) responds and proposes to go with r08. Laurent (Nokia): provides r10 ==== 8.X, 9.X, 10.X Revisions Deadline ==== György (Ericsson) responds to Laurent and proposes to go with r08 Laurent (Nokia): objects to R09, R08, R05, R04, R03, R00. Can live with a wording that allows solutions with an optional NEF even if the interface relies heavily on IETF work; we discuss the northbound 5GS interface Zhendong (ZTE): do you mean you agree with r10? György (Ericsson) proposes to go with r11, which is based on r08, plus the added sentence in the key issue text: The solution should clarify whether the NEF could be deployed between the TSCTSF and the DetNet controller. Zhendong (ZTE): is fine with György proposal ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.6 | S2-2201757 | P-CR | Approval | 23.700-46: New Key Issue: Parameter mapping between DetNet controller and 5G system. | Huawei, HiSilicon | Rel-18 | Revision of S2-2200267r08, merging S2-2200620, S2-2200731, S2-2200829, S2-2200292 and S2-2200962. Approved | Approved | |
| 9.6 | S2-2200292 | P-CR | Approval | 23.700-46: Key Issue for DetNet controller to 5GS interface. | Nokia, Nokia Shanghai Bell | Rel-18 | Merged into S2-2201819 and S2-2201757 | György (Ericsson) comments. Laurent (Nokia): provides r01 Laurent (Nokia): provides r02 György (Ericsson) comments and suggests to use 0357 and 0267 for the Key Issues as originally proposed. Jari (NTT DOCOMO) provides r03 Laurent (Nokia): OK to merge György (Ericsson): This document is considered merged into 357 and 267. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.6 | S2-2200357 | P-CR | Approval | 23.700-46: Adding Key issue on DetNet node capability reporting. | ZTE | Rel-18 | r03 agreed. Revised to S2-2201758, merging S2-2200962 | Jari (NTT DOCOMO) comments. György (Ericsson) responds and provides r01 Laurent (Nokia): provides r02 Laurent (Nokia): please see the mail carrying 292 R02 to see how a merge 267+292+357+962+956 (non OAM part) could be made György (Ericsson): provides r03, and proposes to use 0357 and 0267 to collect key issue text as originally discussed. Zhendong (ZTE): provides response Jari (NTT DOCOMO) provides r02 György (Ericsson) indicates to Jari that the revision was not uploaded. Jari (NTT DOCOMO) provides r04 György (Ericsson) proposes to go with r03. Haiyang (Huawei) is ok to go with r03 but prefer to keep the original note . Laurent (Nokia): provides r05 Laurent (Nokia): provides r06 György (Ericsson) comments ==== 8.X, 9.X, 10.X Revisions Deadline ==== György (Ericsson): proposes to go with r03. Jari (NTT DOCOMO) responds Laurent (Nokia): objects to R00, R01, R03, R04; Can live with a wording that allows solutions with an optional NEF even if the interface relies heavily on IETF work; we discuss the northbound 5GS interface; same comment as 0267 Zhendong (ZTE): ask Laurent which revision you agree? György (Ericsson) proposes to go with r07, which is based on r03 plus the following added text in the key issue: The solution should clarify whether the NEF could be deployed between the TSCTSF and the DetNet controller. Zhendong (ZTE): is fine with György proposal ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.6 | S2-2201758 | P-CR | Approval | 23.700-46: Adding Key issue on DetNet node capability reporting. | ZTE | Rel-18 | Revision of S2-2200357r03, merging S2-2200962. Approved | Approved | |
| 9.6 | S2-2200956 | P-CR | Approval | 23.700-46: New key issues for DetNet traffic management. | ETRI | Rel-18 | Merged into S2-2201515 | György (Ericsson) comments. Laurent (Nokia): support Györgi: key issue X is to be merged in 0267, key issue Y about OAM functions is out of our scope Laurent (Nokia): please see the mail carrying 292 R02 to see how a merge 267+292+357+962+956 (non OAM part) could be made Yoohwa (ETRI) responds to Laurent and György. György (Ericsson) responds to ETRI. Yoohwa (ETRI) is okay with key issue X being merged into 0267. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.6 | S2-2200962 | P-CR | Approval | 23.700-46: Key issues for the DetNet study. | NTT DOCOMO | Rel-18 | Merged into S2-2201758 and S2-2201757 | György (Ericsson) comments. Jari (NTT DOCOMO) responds to György Laurent (Nokia): Comments: György I'd suggest you select a baseline between 0267 + 0292 +357+962 Laurent (Nokia): please see the mail carrying 292 R02 to see how a merge 267+292+357+962+956 (non OAM part) could be made Yoohwa (ETRI) asks a question for my clarification. György (Ericsson) responds to Jari. György (Ericsson) responds to Yoohwa Jari (NTT DOCOMO) comments Zhendong (ZTE): provides comments and proposes merge this paper into 0267 and 0357 Jari (NTT DOCOMO) comments. György (Ericsson) responds. Laurent (Nokia): Can I assume that 0962 is merged in 0267 + 0357 Zhendong (ZTE): i think it has been merged into 0267 and 0357 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.6 | - | - | - | Documents exceeding quota | - | - | Docs:=5 | - | |
| 9.6 | S2-2200356 | P-CR | Approval | 23.700-46: Adding architecture assumption and reference architecture. | ZTE | Rel-18 | Not Handled | ==== 8.X, 9.X, 10.X Final Deadline ==== | - |
| 9.6 | S2-2200358 | P-CR | Approval | 23.700-46: Adding Key issue on DetNet configuration mapping. | ZTE | Rel-18 | Not Handled | ==== 8.X, 9.X, 10.X Final Deadline ==== | - |
| 9.6 | S2-2200266 | P-CR | Approval | 23.700-46: New Key Issue: Network Information exposure from 5G system to DetNet controller. | Huawei, HiSilicon | Rel-18 | Not Handled | ==== 8.X, 9.X, 10.X Final Deadline ==== | - |
| 9.6 | S2-2200306 | P-CR | Approval | 23.700-46: Key issues for the DetNet study. | Ericsson | Rel-18 | Not Handled | ==== 8.X, 9.X, 10.X Final Deadline ==== | - |
| 9.6 | S2-2200948 | P-CR | Approval | 23.700-46: New Key Issue on Exposure of QoS Information to the DetNet Controller. | Xiaomi, | Rel-18 | Not Handled | ==== 8.X, 9.X, 10.X Final Deadline ==== | - |
| 9.7 | - | - | - | Study on 5G Timing Resiliency and TSC & URLLC enhancements (FS_5TRS_URLLC) | - | - | Docs:=40 | - | |
| 9.7 | - | - | - | General (skeleton, scope) | - | - | Docs:=3 | - | |
| 9.7 | S2-2201055 | P-CR | Approval | 23.700-18: ToC for TR 23.700-18 | Nokia, Nokia Shanghai Bell | Rel-18 | Approved | Qianghua (Huawei) points out the TR number for 5RTS_URLLC should be 23.700-25, not 23.700-18. Devaki (Nokia) agrees that the TR# should be fixed and that this can be fixed as part of Editing by the Editor. Thanks for pointing it out. Sorry for the oversight .18 and .25 were next to each other in the table. ==== 8.X, 9.X, 10.X Final Deadline ==== | Approved |
| 9.7 | S2-2201056 | P-CR | Approval | 23.700-18: Scope for TR 23.700-18. | Nokia, Nokia Shanghai Bell | Rel-18 | r01 agreed. Revised to S2-2201759. | Sebastian (Qualcomm) provides r01 ==== 8.X, 9.X, 10.X Revisions Deadline ==== Qianghua (Huawei) points out the TR number for 5RTS_URLLC should be 23.700-25, not 23.700-18. ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.7 | S2-2201759 | P-CR | Approval | 23.700-18: Scope for TR 23.700-25. | Nokia, Nokia Shanghai Bell | Rel-18 | Revision of S2-2201056r01. Approved | Approved | |
| 9.7 | - | - | - | Architecture Assumptions and requirements | - | - | Docs:=5 | - | |
| 9.7 | S2-2200205 | P-CR | Approval | 23.700-25: Architectural assumption for WT#3.1. | Intel | Rel-18 | Merged into S2-2201766 | Devaki (Nokia) comments. Haiyang (Huawei) comments. Chunshan (CATT) comments. Saso (Intel) replies that a merge with 0897 is possible. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Saso (Intel) confirms that 0205 is MERGED into 0897. ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.7 | S2-2200896 | P-CR | Approval | 23.700-25: Adding architecture assumption and requirement to 5TRS_URLLC. | ZTE | Rel-18 | r03 agreed. Revised to S2-2201760. | Devaki (Nokia) comments. Qianghua (Huawei) provides comments Sebastian (Qualcomm) provides r01 Zhendong (ZTE): provides response Zhendong (ZTE): provides r02 György (Ericsson): provides r03 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.7 | S2-2201760 | P-CR | Approval | 23.700-25: Adding architecture assumption and requirement to 5TRS_URLLC. | ZTE | Rel-18 | Revision of S2-2200896r03. Approved | Approved | |
| 9.7 | S2-2201057 | P-CR | Approval | 23.700-18: Architectural assumptions for Timing Resiliency. | Nokia, Nokia Shanghai Bell | Rel-18 | r03 agreed. Revised to S2-2201761. | Sebastian (Qualcomm) provides r01 Devaki (Nokia) is fine with r01 as a starting point for arch. assumption. Shabnam (Ericsson) provides r02. Sebastian (Qualcomm) provides r03 ==== 8.X, 9.X, 10.X Revisions Deadline ==== Devaki (Nokia) provides r04, objects to r02/r03. Shabnam (Ericsson) agrees the intent was as stated in r04, so ok going with r04. Qianghua (Huawei) points out the TR number for FS_5TRS_URLLC should be 23.700-25, not 23.700-18. Devaki (Nokia) agrees that the TR# should be fixed and that this can be fixed as part of Editing by the Editor. Thanks for pointing it out. Sorry for the oversight .18 and .25 were next to each other in the table. Devaki (Nokia) requests Chair to ask approval of r04 (if needed, re-confirm this during CC). Devaki (Nokia) highlights the changes in r04 on top of r03 for Chair record, bullet 2 in section 4.1 updated as follows: * How the 5GS network is time synchronized is assumed to be deployment specific thus outside the scope of this study (e.g., 5GS may use local GNSS server, may be time synchronized with an external clock using transport network synchronization protocols, etc.). Qianghua (Huawei) prefers r04 or Devaki's proposed changes on top of r03 Sebastian (Qualcomm) is ok with changes as proposed by Devaki on top of r03 ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.7 | S2-2201761 | P-CR | Approval | 23.700-18: Architectural assumptions for Timing Resiliency. | Nokia, Nokia Shanghai Bell, Ericsson | Rel-18 | Revision of S2-2201057r03. Approved | Approved | |
| 9.7 | - | - | - | Key Issue for WT#1.1 | - | - | Docs:=5 | - | |
| 9.7 | S2-2200675 | P-CR | Approval | 23.700-25: New KI related with FS_5TRS_URLLC WT1.1. | Samsung | Rel-18 | Merged to S2-2201762 | Devaki (Nokia) proposes to consider this paper as merged with 1058. Sang-Jun (Samsung) agrees to consider this paper as merged with 1058. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.7 | S2-2200645 | P-CR | Approval | 23.700-25: New key issue for management of 5GS network timing resiliency. | Huawei, HiSilicon, Nokia, Nokia Shanghai Bell | Rel-18 | Noted | Shabnam (Ericsson) can not agree to this KI as it goes beyond what is in scope for the SI, as shown in the discussion part, comments. Qianghua (Huawei) replies to Shabnam Sebastian (Qualcomm) objects to the pCR Qianghua (Huawei) replies and provides r01 Shabnam (Ericsson) provides r02. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Sebastian (Qualcomm) objects to r01 and r02 (and r00) ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 9.7 | S2-2200900 | P-CR | Approval | 23.700-25: Adding a new KI on 5GS timing synchronization status reporting. | ZTE | Rel-18 | Merged into S2-2201763 | Devaki (Nokia) proposes to consider this paper as merged with 1058. Zhendong (ZTE): is fine to merge this paper into 1058 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.7 | S2-2201058 | P-CR | Approval | 23.700-18: Key issue: Timing resiliency monitoring and reporting. | Nokia, Nokia Shanghai Bell, Huawei | Rel-18 | Revised to S2-2201762, merging S2-2200675. | Devaki (Nokia) comments. Shabnam (Ericsson) asks for some clarification on the role of UE vs. application. Shabnam (Ericsson) prefers that the KI description removes ambiguity to focus on the work and at a minimum add clarity as we encountered for TSN. So I think we should clarify that it is the devices/apps in the UE. Devaki (Nokia) provides r01 to clarify device/apps within the UE as requested. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Qianghua (Huawei) points out the TR number for 5RTS_URLLC should be 23.700-25, not 23.700-18. Sebastian (Qualcomm) objects to r01 Devaki (Nokia) asks if we can agree r00 (in the interest of progress) and clarify the end point on the device side next meeting or as part of the solution? Qianghua (Huawei) OK with r00 that uses the same terms from SID Devaki (Nokia) proposes to go with r00 plus '(e.g. application running in the UE), devices attached to the UE (i.e. that receive time information from 5GS)' to the two bullets for KI. ==== 8.X, 9.X, 10.X Final Deadline ==== Jari (NTT DOCOMO) the proposal from Devaki is not clear on 'devices behind the DS-TT' Sebastian (Qualcomm) replies to Jari Runze (Huawei) supports Sebastian's proposal. | Revised |
| 9.7 | S2-2201762 | P-CR | Approval | 23.700-18: Key issue: Timing resiliency monitoring and reporting. | Nokia, Nokia Shanghai Bell, Huawei, Ericsson | Rel-18 | Revision of S2-2201058, merging S2-2200675. Approved | Approved | |
| 9.7 | - | - | - | Key Issue for WT#1.2 | - | - | Docs:=4 | - | |
| 9.7 | S2-2200676 | P-CR | Approval | 23.700-25: New KI related with FS_5TRS_URLLC WT1.2. | Samsung | Rel-18 | Merged into S2-2201763 | Devaki (Nokia) proposes to consider this paper as merged with 1059. Sang-Jun (Samsung) agrees to consider this paper as merged with 1059. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.7 | S2-2200899 | P-CR | Approval | 23.700-25: Adding a new KI on how to provide time synchronization service in a specific coverage area. | ZTE | Rel-18 | Merged into S2-2201765 | Devaki (Nokia) proposes to consider this paper as merged with 1059. Zhendong (ZTE): is fine with the merge proposal ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.7 | S2-2201059 | P-CR | Approval | 23.700-18: Key issue: Time synchronization service extensions. | Nokia, Nokia Shanghai Bell, Huawei | Rel-18 | r02 agreed. Revised to S2-2201763, merging S2-2200900 and S2-2200676 | Shabnam (Ericsson) provides r01, simplifying the text and removing solution assumptions. Sebastian (Qualcomm) provides r02 ==== 8.X, 9.X, 10.X Revisions Deadline ==== Sebastian (Qualcomm) objects to r00, prefers r02 ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.7 | S2-2201763 | P-CR | Approval | 23.700-18: Key issue: Time synchronization service extensions. | Nokia, Nokia Shanghai Bell, Huawei | Rel-18 | Revision of S2-2201059r02, merging S2-2200900 and S2-2200676. Approved | Approved | |
| 9.7 | - | - | - | Key Issue for WT#1.3 | - | - | Docs:=3 | - | |
| 9.7 | S2-2200678 | P-CR | Approval | 23.700-25: New KI related with FS_5TRS_URLLC WT1.3. | Samsung | Rel-18 | Merged into S2-2201764 | Devaki (Nokia) proposes to consider this paper as merged with 232. Sang-Jun (Samsung) agrees to consider this paper as merged with 232. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.7 | S2-2200232 | P-CR | Approval | 23.700-25: Key Issue for controlling 5G time synchronization service based on subscription. | Huawei, HiSilicon, Nokia, Nokia Shanghai Bell | Rel-18 | r03 agreed. Revised to S2-2201764, merging S2-2200678 | Devaki (Nokia) comments. Shabnam (Ericsson) provides r01, focusing on the specific KI aspects. Jari (NTT DOCOMO) provides r02 Sebastian (Qualcomm) provides r03 Runze (Huawei) provides r04. Shabnam (Ericsson) cannot accept revisions with inclusion of 'with or without AF request', as the KI is for subscription and this is going into soln for enforcement. Devaki (Nokia) replies, fine with r03. Runze (Huawei) is fine with r03. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.7 | S2-2201764 | P-CR | Approval | 23.700-25: Key Issue for controlling 5G time synchronization service based on subscription. | Huawei, HiSilicon, Nokia, Nokia Shanghai Bell | Rel-18 | Revision of S2-2200232r03, merging S2-2200678. Approved | Approved | |
| 9.7 | - | - | - | Key Issue for WT#2 | - | - | Docs:=3 | - | |
| 9.7 | S2-2200679 | P-CR | Approval | 23.700-25: KI related with FS_5TRS_URLLC WT2. | Samsung | Rel-18 | Merged into S2-2201812 | Devaki (Nokia) proposes to consider this paper as merged with 1060. Yan (China Mobile) proposes to merge this S2-2200798 into S2-2200099 Sang-Jun (Samsung) agrees to consider this paper as merged with 1060. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.7 | S2-2201060 | P-CR | Approval | 23.700-18: Key Issue for explicitly providing PER to NEF/PCF. | Nokia, Nokia Shanghai Bell | Rel-18 | r01 agreed. Revised to S2-2201765, merging S2-2200899 | Sebastian (Qualcomm) provides r01 György (Ericsson) agrees with r01 Devaki (Nokia) replies. György (Ericsson) replies. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.7 | S2-2201765 | P-CR | Approval | 23.700-18: Key Issue for explicitly providing PER to NEF/PCF. | Nokia, Nokia Shanghai Bell | Rel-18 | Revision of S2-2201060r01, merging S2-2200899. Approved | Approved | |
| 9.7 | - | - | - | Key Issue for WT#3.1 | - | - | Docs:=5 | - | |
| 9.7 | S2-2200680 | P-CR | Approval | 23.700-25: New KI related with FS_5TRS_URLLC WT3.1. | Samsung | Rel-18 | Merged into S2-2201766 | Devaki (Nokia) proposes to consider this paper as merged with 897. Sebastian (Qualcomm) provides r01 Sang-Jun (Samsung) agrees to consider this paper as merged with 897. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.7 | S2-2200274 | P-CR | Approval | 23.700-25: New KI for WT3.1 on interworking with TSN transport network. | Huawei, HiSilicon | Rel-18 | Merged into S2-2201766 | Devaki (Nokia) proposes to consider this paper as merged with 897. Sebastian (Qualcomm) objects to r00 and also suggests to merge with 897 Haiyang (Huawei) clarifies but OK to merge with 897 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.7 | S2-2200689 | P-CR | Approval | 23.700-18: New KI: Support for deterministic N3 transmission. | CATT | Rel-18 | Merged into S2-2201360 | Devaki (Nokia) proposes to consider this paper as merged with 897. Yuan Tao (CATT) agrees this paper is merged with 2200897. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.7 | S2-2200897 | P-CR | Approval | 23.700-25: Adding a new KI on how to interworking with the TSN in the transport network. | ZTE | Rel-18 | r11 agreed. Revised to S2-2201766, merging S2-2201250, S2-2200377, S2-2200205, S2-2200680 and S2-2200274 | Haiyang (Huawei) supports r01. Devaki (Nokia) provides r01. Yuan Tao (CATT) confirms 2200689 is merged into this paper and provides r02. Saso (Intel) proposes r03 merging content from S2-2200505. Sebastian (Qualcomm) provides r04 Devaki (Nokia) comments. Haiyang (Huawei) comments to r04 Sebastian (Qualcomm) replies to Devaki Sebastian (Qualcomm) provides r05 Jari (NTT DOCOMO) provides r06 Haiyang (Huawei) provides r07 Sebastian (Qualcomm) provides r08 Yuan Tao (CATT) agrees with r08 Haiyang (Huawei) is OK with r09. Please add Huawei as a co-signer Devaki (Nokia) provides r09. Zhendong (ZTE): provides r10 Jari (NTT DOCOMO) provides r10 Zhendong (ZTE): Jari (NTT Docomo) provides r11 ==== 8.X, 9.X, 10.X Revisions Deadline ==== Saso (Intel) is OK with r11 ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.7 | S2-2201766 | P-CR | Approval | 23.700-25: Adding a new KI on how to interworking with the TSN in the transport network. | ZTE, Intel, Huawei, NTT DOCOMO | Rel-18 | Revision of S2-2200897r11, merging S2-2201250, S2-2200377, S2-2200205, S2-2200680 and S2-2200274. Approved | Approved | |
| 9.7 | - | - | - | Key Issue for WT#3.2 | - | - | Docs:=8 | - | |
| 9.7 | S2-2200273 | LS OUT | Approval | [DRAFT] LS on RAN feedback for low latency | Huawei, HiSilicon | Rel-18 | r10 agreed. Revised to S2-2201767, merging S2-2200157 | Haiyang (Huawei) provides r01 as merger of 273 and 405 Sang-Jun (Samsung) provides r02. György (Ericsson) provides r03. Saso (Intel) comments and seeks clarifications. Haiyang (Huawei) provides r04 Sebastian (Qualcomm) provides r05 György (Ericsson) provides r06 Haiyang (Huawei) provides r07 Sebastian (Qualcomm) objects to r06 and provides r09 (please ignore r08) Saso (Intel) comments that the third question is difficult to understand. Haiyang (Huawei) clarifies to Saso (Intel). György (Ericsson) provides r10. Saso (Intel) is OK with r10. Devaki (Nokia) comments. Haiyang (Huawei) clarifies to Devaki (Nokia). Saso (Intel) replies to Devaki (Nokia). Devaki (Nokia) thanks Haiyang, Saso for the clarification. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.7 | S2-2201767 | LS OUT | Approval | LS on RAN feedback for low latency | SA WG2 | Rel-18 | Revision of S2-2200273r10, merging S2-2200157. Approved | Approved | |
| 9.7 | S2-2200275 | P-CR | Approval | 23.700-25: New KI for WT3.2 on RAN feedback to meet low latency. | Huawei, HiSilicon | Rel-18 | Merged into S2-2201768 | Devaki (Nokia) proposes to consider this paper as merged with 681. Haiyang (Huawei) is OK to merged with 681 and discuss in that thread. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.7 | S2-2200405 | LS OUT | Approval | [DRAFT] LS on TDD and FDD impact to Low Latency Communications | Intel | Merged into S2-2201362 | Haiyang (Huawei) suggests to merge 273 and 405 Saso (Intel) is OK to merge 0405 into 0273. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged | |
| 9.7 | S2-2200681 | P-CR | Approval | 23.700-25: New KI related with FS_5TRS_URLLC WT3.2. | Samsung | Rel-18 | r09 agreed. Revised to S2-2201768, merging S2-2200187, S2-2200361 and S2-2200275 | Sang-Jun (Samsung) provides r01 merging 0275, 0681, 0898, and 1061. Sang-Jun (Samsung) provides r01 merging 0275, 0681, 0898, and 1061, and appolgoizes for the missing '#' in the previous email header. Devaki (Nokia) ok to use this paper as the baseline for WT#3.2. Sang-Jun (Samsung) provdes r02. Saso (Intel) seeks clarifications. Devaki (Nokia) replies to Saso (Intel). Saso (Intel) replies to Devaki (Nokia). Chunshan (CATT) provides clarification on the UL case. Sang-Jun (Samsung) thanks to Saso, Devaki and Chunshan, and provides r03. Saso (Intel) replies to Chunshan (CATT) on the UL case. Devaki (Nokia) provides r06. Haiyang (Huawei) provides r04. GYörgy (Ericsson) provides r07. Sebastian (Qualcomm) provides r08 György (Ericsson) responds Haiyang (Huawei) comments to György (Ericsson) Sang-Jun (Samsung) has a similar question to György (Ericsson) as sunhaiyang and Sebastian. Devaki (Nokia) comments. Zhendong (ZTE): agree with György and provides comments Jari (NTT DOCOMO) provides r09 ==== 8.X, 9.X, 10.X Revisions Deadline ==== Sang-Jun (Samsung) can accept r05~r09. Haiyang (Huawei) can accept r09. Please add Huawei as a co-signer. Saso (Intel) supports r09 and would like to co-sign ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.7 | S2-2201768 | P-CR | Approval | 23.700-25: New KI related with FS_5TRS_URLLC WT3.2. | Samsung, Nokia, Nokia Shanghai Bell, Intel, Huawei | Rel-18 | Revision of S2-2200681r09, merging S2-2200187, S2-2200361 and S2-2200275. Approved | Approved | |
| 9.7 | S2-2200898 | P-CR | Approval | 23.700-25: Adding new Key issue on how to adapt downstream scheduling. | ZTE | Rel-18 | Merged into S2-2201484 | Devaki (Nokia) proposes to consider this paper as merged with 681. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.7 | S2-2201061 | P-CR | Approval | 23.700-18: Key Issue for 5GS to provide feedback to application traffic transmission schedules. | Nokia, Nokia Shanghai Bell | Rel-18 | Merged into S2-2201298 | Devaki (Nokia) proposes to consider this paper as merged with 681. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.7 | - | - | - | Solutions | - | - | Docs:=4 | - | |
| 9.7 | S2-2201177 | P-CR | Approval | 23.700-25: Inform UE and AF about network timing synchronization status. | Qualcomm Incorporated | Rel-18 | r04 agreed. Revised to S2-2201769. | Devaki (Nokia) comments. Jari (NTT DOCOMO) provider r01 Shabnam (Ericsson) asks some questions for clarification Sebastian (Qualcomm) replies to Ericsson, Nokia, and Docomo and provides r02 Shabnam (Ericsson) thanks for the responses, we are moving in the right formulation, see comments. Sebastian (Qualcomm) responds to Shabnam (Ericsson) and provides r03 Jari (NTT DOCOMO) provides r04 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.7 | S2-2201769 | P-CR | Approval | 23.700-25: Inform UE and AF about network timing synchronization status. | Qualcomm Incorporated | Rel-18 | Revision of S2-2201177r04. Approved | Approved | |
| 9.7 | S2-2201179 | P-CR | Approval | 23.700-25: Burst arrival time adaptation. | Qualcomm Incorporated | Rel-18 | r05 agreed. Revised to S2-2201770. | Devaki (Nokia) comments. Sebastian (Qualcomm) replies Qianghua (Huawei) asks whether new solution proposal is in agenda of this SID Qianghua (Huawei) provides additional technical comments Sebastian (Qualcomm) asks a question György (Ericsson) comments Qianghua (Huawei) provides r01 Sebastian (Qualcomm) replies to György Jari (NTT DOCOMO) comments Sebastian (Qualcomm) replies to Jari and provides r02 Jari (NTT DOCOMO) provides r03 György (Ericsson) provides r04 Saso (Intel) provides r05 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.7 | S2-2201770 | P-CR | Approval | 23.700-25: Burst arrival time adaptation. | Qualcomm Incorporated | Rel-18 | Revision of S2-2201179r05. Approved | Approved | |
| 9.8 | - | - | - | Study on RedCap Phase 2 (FS_RedCAP_Ph2) | - | - | Docs:=17 | - | |
| 9.8 | - | - | - | Skeleton, scope and architectural assumptions | - | - | Docs:=4 | - | |
| 9.8 | S2-2200326 | P-CR | Approval | 23.700-68: FS_RedCap_Ph2 TR Skeleton | Ericsson (Rapporteur) | 23.700-68 TR Skeleton. Approved | Steve (Huawei) comments on mapping table. Qian (Ericsson) provides comments to Steve (Huawei). Hannu (Nokia) comments that there is just one KI in this study. Qian (Ericsson) comments. Hannu (Nokia) thanks Qian for his comment and proposes to roll back r01 and agree the initial version of S2-2200326 instead. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Qian (Ericsson) propose to go with original version of the paper. Steve (Huawei) is ok with r00 (original) ==== 8.X, 9.X, 10.X Final Deadline ==== | Approved | |
| 9.8 | S2-2200327 | P-CR | Approval | 23.700-68: RedCap ph2 study scope, reference, architectural assumptions . | Ericsson | Rel-18 | r02 agreed. Revised to S2-2201568. | Steve (Huawei) question for clarification Qian (Ericsson) provides comments and r01 Miguel (Qualcomm) comments provides r02 Qian (Ericsson) comments ==== 8.X, 9.X, 10.X Revisions Deadline ==== Qian (Ericsson) proposes to go with r02. ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.8 | S2-2201568 | P-CR | Approval | 23.700-68: RedCap ph2 study scope, reference, architectural assumptions . | Ericsson | Rel-18 | Revision of S2-2200327r02. Approved | Approved | |
| 9.8 | S2-2200673 | P-CR | Approval | 23.700-68: HLcom Notification features for RedCap devices. | Sony | Rel-18 | Noted | Steve (Huawei) comments Qian (Ericsson) provides comments Miguel (Qualcomm) proposes to note this document, disagrees with its content Lars (Sony) It is a discussion paper and it will be NOTED anyway. Lars (Sony) Please ignore my previous comment, as this is NOT a discussion paper. Lars (Sony) Provides r01. Lars (Sony) comments Qian (Ericsson) provides further comments on r01 Lars (Sony) responds to Qian (Ericsson) Hannu (Nokia) comments and provides r02. Hannu (Nokia) provides r03 to follow the recommendation to remove TS 23.503 dependency. Lars (Sony) responds to Hannu (Nokia). Qian (Ericsson) comments and provide r04 Lars (Sony) comments on r04 Qian (Ericsson) responds Lars (Sony) ask as the author to NOTE this paper. Hannu (Nokia) agrees to note the paper and asks for contacts for further discussion? ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 9.8 | - | - | - | Key issues | - | - | Docs:=5 | - | |
| 9.8 | S2-2200328 | P-CR | Approval | 23.700-68: RedCap ph2 study key issues . | Ericsson | Rel-18 | r06 agreed. Revised to S2-2201569, merging S2-2200960, S2-2200843 and S2-2200168 | Steve (Huawei) comments Qian (Ericsson) provides comments and r01 Xiaowan (vivo) provides r02 Lars (Sony) provides r03 Xiaowan (vivo) provides r04 Hannu (Nokia) proposes cleanup of the wording in r05 and comments. Steve (Huawei) provides r06 for editorials and cosign. Hannu (Nokia) supports r06. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Qian (Ericsson) thanks all for the merges/updates and supports to go with r06. Lars (Sony) supports to go with r06. Leo (Deutsche Telekom) supports r06. ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.8 | S2-2201569 | P-CR | Approval | 23.700-68: RedCap ph2 study key issues . | Ericsson, vivo, Huawei, HiSilicon | Rel-18 | Revision of S2-2200328r06, merging S2-2200960, merging S2-2200960 and S2-2200843, merging S2-2200960, S2-2200843 and S2-2200168. Approved | Approved | |
| 9.8 | S2-2200157 | P-CR | Approval | 23.700-68: KI#X: Enhancement with eDRX cycle longer than 10.24s | vivo | Rel-18 | Merged into S2-2201767 | Qian (Ericsson) proposes to use 0328 as base and mark this paper as merged Xiaowan (vivo) is ok to merge 0157 into 0328 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.8 | S2-2200158 | P-CR | Approval | 23.700-68: KI#X: MT handling for UE with long eDRX cycle in RRC_INACTIVE state | vivo | Rel-18 | Merged into S2-2201724 | Qian (Ericsson) proposes to use 0328 as base and mark this paper as merged Xiaowan (vivo) is ok to merge 0157 into 0328 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.8 | S2-2200960 | P-CR | Approval | 23.700-68: Key Issue: Support of long eDRX cycles in RRC_Inactive. | Huawei, HiSilicon | Rel-18 | Merged into S2-2201569 | Qian (Ericsson) proposes to use 0328 as base and mark this paper as merged ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.8 | - | - | - | Solutions | - | - | Docs:=8 | - | |
| 9.8 | S2-2200329 | P-CR | Approval | 23.700-68: Solution for RedCap Ph2 KI . | Ericsson | Rel-18 | r03 agreed. Revised to S2-2201570. | Lars (Sony) asks a question for clarification. Miguel (Qualcomm) has a concern for section 6.1.3.2, and other comments Qian (Ericsson) responds and provides r01 Lars (Sony) responds to Qian on r01 Qian (Ericsson) responds to Lars (Sony) Lars (Sony) responds to Qian (Ericsson) Qian (Ericsson) comments and provides r02 Lars (Sony) comments on r02 Qian (Ericsson) responds and provides r03 Lars (Sony) is ok with r03 ==== 8.X, 9.X, 10.X Revisions Deadline ==== Qian (Ericsson) thanks all for the good comments and proposes to go with r03 ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.8 | S2-2201570 | P-CR | Approval | 23.700-68: Solution for RedCap Ph2 KI . | Ericsson | Rel-18 | Revision of S2-2200329r03. Approved | Approved | |
| 9.8 | S2-2200671 | P-CR | Approval | 23.700-68: Solution proposal long eDRX for RedCap devices. | Sony | Rel-18 | r04 agreed. Revised to S2-2201571. CC#4: Noted | Miguel (Qualcomm) provides comments to procedures Lars (Sony) responds to Miguel Xiaowan (vivo) seek clarification if lack of Xn interface, how AF1044 | Noted |
| 9.8 | S2-2201571 | P-CR | Approval | 23.700-68: Solution proposal long eDRX for RedCap devices. | Sony, Nokia, Nokia Shanghai Bell | Rel-18 | Revision of S2-2200671r04. Approved | Approved | |
| 9.8 | S2-2200961 | P-CR | Approval | 23.700-68: Solution: MT signalling and data handling for UE with long eDRX cycle in RRC_Inactive state and UPF buffering. | Huawei, HiSilicon | Rel-18 | r02 agreed. Revised to S2-2201572. | Lars (Sony) asks a question for clarification Steve (Huawei) provides r01 Lars (Sony) propose to add clarification. Steve (Huawei) provides r02 ==== 8.X, 9.X, 10.X Revisions Deadline ==== Qian (Ericsson) supports to go with r02 Lars (Sony) supports to go with r02 Steve (Huawei) thank you everyone, I am good with r02. ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.8 | S2-2201572 | P-CR | Approval | 23.700-68: Solution: MT signalling and data handling for UE with long eDRX cycle in RRC_Inactive state and UPF buffering. | Huawei, HiSilicon | Rel-18 | Revision of S2-2200961r02. Approved | Approved | |
| 9.8 | S2-2201209 | P-CR | Approval | 23.700-68: Solution: RRC inactive with CM IDLE and eDRX longer than 10.24s. | Qualcomm Inc | Rel-18 | r03 agreed. Revised to S2-2201573. | Lars (Sony) Request a revision that follows the SA2 format on solution descriptions. Steve (Huawei) supports Lars (Sony) request. Qian (Ericsson) share the similar view from Lars(Sony) and Steve(Huawei). Xiaowan (vivo) provides comment Miguel (Qualcomm) provides r01 Lars (Sony) comments on r01 Qian (Ericsson) comments on r01 Miguel (Qualcomm) provides r02 Lars (Sony) ask for an EN Miguel (Qualcomm) provides some thoughts and creates r03 Lars (Sony) is ok with r03. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Qian (Ericsson) supports to go with r03 ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.8 | S2-2201573 | P-CR | Approval | 23.700-68: Solution: RRC inactive with CM IDLE and eDRX longer than 10.24s. | Qualcomm Inc | Rel-18 | Revision of S2-2201209r03. Approved | Approved | |
| 9.9 | - | - | - | Study on Vehicle Mounted Relays (FS_VMR) | - | - | Docs:=20 | - | |
| 9.9 | S2-2201142 | P-CR | Approval | 23.700-05: Cover page for TR 23.700-05 skeleton. | Qualcomm Incorporated | Rel-18 | 23.700-05 TR Skeleton. r01 agreed. Revised to S2-2201574. | LaeYoung (LGE) provides comment. Hong (Qualcomm) provides r01. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.9 | S2-2201574 | P-CR | Approval | 23.700-05: Cover page for TR 23.700-05 skeleton. | Qualcomm Incorporated | Rel-18 | Revision of S2-2201142r01. Approved | Approved | |
| 9.9 | S2-2201145 | P-CR | Approval | 23.700-05: TR 23.700-05: Scope for FS_VMR. | Qualcomm Incorporated | Rel-18 | r05 agreed. Revised to S2-2201575. | Qian (Ericsson) asks a question Lars (Sony) comments and provides r01 Lars (Sony) ask a question and provides r01 Hong (Qualcomm) replies to Qian. Qian (Ericsson) comments Qian (Ericsson) comments and provide r02 Hong (Qualcomm) provides r03. Alessio(Nokia) OK with r03. LiMeng (Huawei) provides r04 with removing 'possibly' from r03. Lars (Sony) provides r05 ==== 8.X, 9.X, 10.X Revisions Deadline ==== Hong (Qualcomm) is fine with r05. Lars (Sony) supports r05. Qian (Ericsson) supports r05. ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.9 | S2-2201575 | P-CR | Approval | 23.700-05: TR 23.700-05: Scope for FS_VMR. | Qualcomm Incorporated | Rel-18 | Revision of S2-2201145r05. Approved | Approved | |
| 9.9 | S2-2201148 | P-CR | Approval | 23.700-05: TR 23.700-05: Architecture assumptions and requirements for FS_VMR. | Qualcomm Incorporated | Rel-18 | r05 agreed. Revised to S2-2201576. | LaeYoung (LGE) fixes Tdoc# in the email subject and clarifies that Lars (Sony) provided r01 of 1148. Lars (Sony) thanks LaeYoung for answer. I also resend the r01 link here with the correct email subject. Steve (Huawei) comments alessio(Nokia) provides r02 Hong (Qualcomm) comments. LiMeng (Huawei) comments. Hong (Qualcomm) comments and provide r03. LiMeng (Huawei) comments and provide r04. Hong (Qualcomm) provide r05. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Lars (Sony) supports r05. Qian (Ericsson) is ok with r05. ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.9 | S2-2201576 | P-CR | Approval | 23.700-05: TR 23.700-05: Architecture assumptions and requirements for FS_VMR. | Qualcomm Incorporated | Rel-18 | Revision of S2-2201148r05. Approved | Approved | |
| 9.9 | S2-2200297 | P-CR | Approval | 23.700-05: Key Issue: Configuration of Vehicle Mounted Relay . | Futurewei | Rel-18 | r04 agreed. Revised to S2-2201577. | Steve (Huawei) comments John (Futurewei) provides r01. Qian (Ericsson) comments and provides r02. Hong (Qualcomm) provides r03. Qian (Ericsson) comments. Hong (Qualcomm) replies to Qian. Qian (Ericsson) comments and provide r04. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Qian (Ericsson) proposes to go with r04. John (Futurewei) is fine to go with r04. Hong (Qualcomm) is fine with r04. ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.9 | S2-2201577 | P-CR | Approval | 23.700-05: Key Issue: Configuration of Vehicle Mounted Relay . | Futurewei | Rel-18 | Revision of S2-2200297r04. Approved | Approved | |
| 9.9 | S2-2200559 | P-CR | Approval | 23.700-05: Key Issue: VMR applicability to NR satellite access . | Rakuten Mobile | Rel-18 | Postponed | Saad (InterDigital) comments Hong (Qualcomm) comments. LaeYoung (LGE) is fine to check with RAN by sending an LS as suggested by Hong (Qualcomm) and prefers to postpone this pCR. Saad (Interdigital) agrees to postpone the pCR Qian (Ericsson) also agrees to postpone the pCR Aoken (Rakuten Mobile) agrees to the proposed way forward. Hong (Qualcomm) comments and would like to know if all are fine with sending an LS to RAN on this topic. LaeYoung (LGE) replies to Hong (Qualcomm). Wanqiang (Huawei) comments Aoken (Rakuten Mobile) comments fine with sending an LS to RAN Aoken (Rakuten Mobile) provide the draft LS to RAN Alessio(Nokia) also ok to postpone Alessio(Nokia) asks a question Aoken(Rakuten) comments. Hong (Qualcomm) replies to Saad. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Postponed |
| 9.9 | S2-2201686 | LS OUT | Approval | [DRAFT] LS on VMR applicability to NR satellite access | Qualcomm | Created at CC#3. r03 agreed. Revised to S2-2201578. | Aoken(Rakuten) provides the draft LS. Hong (Qualcomm) provides r01. LaeYoung (LGE) provides r02. Wanqiang (Huawei) provides r03. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Qian (Ericsson) supports to go with r03. ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised | |
| 9.9 | S2-2201578 | LS OUT | Approval | LS on IAB support of NR satellite access | SA WG2 | Rel-18 | Revision of S2-2101686r03. Approved | Approved | |
| 9.9 | S2-2200591 | DISCUSSION | Discussion | Discussion on the mobility scenarios for WT#1. | Huawei, HiSilicon | Rel-18 | Noted | ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 9.9 | S2-2200582 | P-CR | Approval | 23.700-05: Key Issue: 5GC supports efficient mobility. | vivo | Rel-18 | r06 agreed. Revised to S2-2201579. | LaeYoung (LGE) provides comments. Ming (CATT) asks questions. Steve (Huawei) comments, should be merged with 0592? Zhenhua (vivo) propose merge 0592 into 0582 Hong (Qualcomm) comments. Zhenhua (vivo) provides r01 Qian (Ericsson) comments. Zhenhua (vivo) is OK to separate KI according to scenarios described in S2-2200591, i.e. this contribution addresses scenario #1 and #2, r02 is provided Hong (Qualcomm) comments on r02 and suggest to use a more descriptive title for the KI. Zhenhua (vivo) agrees to Hong (Qualcomm) and provides r03. Qian (Ericsson) comments and provides r04. Zhenhua (vivo) can accept r04. Walter Dees (Philips) provides r05 LiMeng (Huawei) provides r06 based on r05. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Qian (Ericsson) comments and is ok with r06. Hong (Qualcomm) is fine with r06. ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.9 | S2-2201579 | P-CR | Approval | 23.700-05: Key Issue: 5GC supports efficient mobility. | vivo | Rel-18 | Revision of S2-2200582r06. Approved | Approved | |
| 9.9 | S2-2200592 | P-CR | Approval | 23.700-05: Key Issue: efficient mobility and service continuity . | Huawei, HiSilicon | Rel-18 | r04 agreed. Revised to S2-2201580. | Hong (Qualcomm) provides r01. Zhenhua (vivo) asks whether we can have two KIs as Hong (Qualcomm) indicated? LiMeng (Huawei) asks whether we need to enhance the . LiMeng (Huawei) asks whether we need to enhance the procedure for scenario #1 and #2, and is fine to separate the KI description. Qian (Ericsson) ask question and provide proposals. LiMeng (Huawei) thanks for the proposal and provides r02. Hong (Qualcomm) comments on r02 and suggest to use a more descriptive title for the KI. LiMeng (Huawei) agrees and provides r02. Qian (Ericsson) comments and provides r04. LiMeng (Huawei) can accepts r04. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Qian (Ericsson) proposes to go with r04. ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.9 | S2-2201580 | P-CR | Approval | 23.700-05: Key Issue: efficient mobility and service continuity . | Huawei, HiSilicon | Rel-18 | Revision of S2-2200592r04. Approved | Approved | |
| 9.9 | S2-2201150 | P-CR | Approval | 23.700-05: TR 23.700-05: new Key Issue on roaming support for FS_VMR. | Qualcomm Incorporated | Rel-18 | r02 agreed. Revised to S2-2201581. | Qian (Ericsson) provides comments Hong (Qualcomm) comments. LiMeng (Huawei) comments and provides r01. Qian (Ericsson) comments and provides r02. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Qian (Ericsson) proposes to go with r02. LiMeng (Huawei) is fine with r02. Hong (Qualcomm) is fine with r02. ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.9 | S2-2201581 | P-CR | Approval | 23.700-05: TR 23.700-05: new Key Issue on roaming support for FS_VMR. | Qualcomm Incorporated | Rel-18 | Revision of S2-2201150r02. Approved | Approved | |
| 9.9 | S2-2201153 | P-CR | Approval | 23.700-05: TR 23.700-05: new Key Issue on location and regulatory services support for FS_VMR. | Qualcomm Incorporated | Rel-18 | r05 agreed. Revised to S2-2201582. | Ming (CATT) asks questions and makes suggestions. Hong (Qualcomm) replies to Ming. Ming (CATT) replies to Hong. Steve (Huawei) comments Ming (CATT) comments and provides r01. Hong (Qualcomm) provides r02. Zhenhua (vivo) comments r01. Qian (Ericsson) comments and provides r03. Hong (Qualcomm) provides r04. Ming (CATT) provides r05. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Qian (Ericsson) asks a question on r05. Ming (CATT) responses to Qian (Ericsson) Qian (Ericsson) provides further comments Hong (Qualcomm) comments. ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.9 | S2-2201582 | P-CR | Approval | 23.700-05: TR 23.700-05: new Key Issue on location and regulatory services support for FS_VMR. | Qualcomm Incorporated, CATT | Rel-18 | Revision of S2-2201153r05. Approved | Approved | |
| 9.10 | - | - | - | Study on 5GC LoCation Services Phase 3 (FS_eLCS_Ph3) | - | - | Docs:=34 | - | |
| 9.10 | - | - | - | TR skeleton, scope, etc | - | - | Docs:=5 | - | |
| 9.10 | S2-2200349 | P-CR | Approval | 23.700-71: TR 23.700-71 Skeleton | CATT | Rel-18 | 23.700-71 TR Skeleton. r02 agreed. Revised to S2-2201583. | Runze (Huawei) points out a minor error. Ming (CATT) thanks Runze and will correct this during TR editing. Stephen (Qualcomm) comments Ming (CATT) responses. Stephen (Qualcomm) replies to Ming (CATT) Ming (CATT) responses and provides r01. Runze (Huawei) supports r01. Stephen (Qualcomm) does not agree the r00 or r01 Ming (CATT) replies to Stephen (Qualcomm) and provides r02 ==== 8.X, 9.X, 10.X Revisions Deadline ==== Stephen (Qualcomm) can accept the r02 Runze (Huawei) can accept the r02 ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.10 | S2-2201583 | P-CR | Approval | 23.700-71: Cover page for TR 23.700-71 skeleton. | CATT | Rel-18 | Revision of S2-2200349r02. Approved | Approved | |
| 9.10 | S2-2200350 | P-CR | Approval | 23.700-71: FS_eLCS_Ph3: TR Scope. | CATT | Rel-18 | Approved | ==== 8.X, 9.X, 10.X Final Deadline ==== | Approved |
| 9.10 | S2-2200351 | P-CR | Approval | 23.700-71: FS_eLCS_Ph3: Architectural Assumptions and Requirements. | CATT | Rel-18 | r02 agreed. Revised to S2-2201584. | Hank(vivo) points out some minor error. Stephen (Qualcomm) provides an r01 David (Samsung) provides r02. Runze (Huawei) supprots r02. Stephen (Qualcomm) can also agree the r02 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.10 | S2-2201584 | P-CR | Approval | 23.700-71: FS_eLCS_Ph3: Architectural Assumptions and Requirements. | CATT | Rel-18 | Revision of S2-2200351r02. Approved | Approved | |
| 9.10 | - | - | - | Key issues for WT#1.1 | - | - | Docs:=4 | - | |
| 9.10 | S2-2200213 | P-CR | Approval | 23.700-71: Key issues for LPP transport via user plane. | Ericsson | Rel-18 | Merged into S2-2201585 | Hank (vivo) provides some comments. Stephen (Qualcomm) provides more comments Runze (Huawei) replies to Stephen. Richard (Ericsson) provide response and r01 Runze (Huawei) proposes to merge this paper into S2-2201140 Yunjing (CATT) proposes to merge this paper into S2-2201140 Richard (Ericsson) accepts to merge S2-2200213 into S2-2201140 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.10 | S2-2201140 | P-CR | Approval | 23.700-71: FS_eLCS_Ph3 TR KI related with WT1.1. | Nokia, Nokia Shanghai Bell | Rel-18 | r04 agreed. Revised to S2-2201585, merging S2-2200213 and S2-2200791 | Richard (Ericsson ) Comments KI is outside objective of SID and also seems more of a solution. Cai Simon (Nokia) clarifies to Richard (Ericsson) Runze (Huawei) supports Simon (Nokia). Richard (Ericsson ) answer to Simon (Nokia) and to Runze (Huawei) Yunjing(CATT) propose to take S2-2201140 as the baseline for WT#1.1. Stephen (Qualcomm) provides an r01 Cai Simon(Nokia) provides r02 Richard (Ericsson ) provides r03. Cai Simon(Nokia) accepts r03 Runze (Huawei) comments on r03. Cai Simon(Nokia) clarifies to Runze (Huawei) Stephen (Qualcomm) provides an r04 Runze (Huawei) comments on r04 Stephen (Qualcomm) replies to Runze (Huawei) Hank (vivo) comments on r04. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Stephen (Qualcomm) can agree the r04 but cannot agree any other version Runze (Huawei) accepts r04. Hank (vivo) replies to Stephen (Qualcomm) and can accept r04. ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.10 | S2-2201585 | P-CR | Approval | 23.700-71: FS_eLCS_Ph3 TR KI related with WT1.1. | Nokia, Nokia Shanghai Bell | Rel-18 | Revision of S2-2201140r04, merging S2-2200213, merging S2-2200213 and S2-2200791. Approved | Approved | |
| 9.10 | S2-2200791 | P-CR | Approval | 23.700-71: Key Issue for supporting user plane location service . | Huawei, HiSilicon | Rel-18 | Merged into S2-2201585 | Cai Simon (Nokia) suggests removing the solution concepts in the KI Hank (vivo) asks for clarifications. Richard (Ericsson ) Comments KI is outside objective of SID Guanglei (Huawei) provides r01 to solve the concerns from Richard (Ericsson ), Hank (vivo) and Cai Simon (Nokia) Stephen (Qualcomm) provides comments Guanglei (Huawei) replies to Stephen (Qualcomm) Stephen (Qualcomm) proposes to merge this KI into S2-2201140 Guanglei (Huawei) is fine to merge 0791 to 1140 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.10 | - | - | - | Key issues for WT#1.2 | - | - | Docs:=5 | - | |
| 9.10 | S2-2200781 | P-CR | Approval | 23.700-71: Key issue proposal on enhanced positioning architecture for vertical use case. | Huawei, HiSilicon | Rel-18 | r02 agreed. Revised to S2-2201586, merging S2-2201016 | Stephen (Qualcomm) provides comments David (Samsung) agrees with Qualcomm, provides r01. Runze (Huawei) asks clarification to David (Samsung). Runze (Huawei) replies to Stephen. David (Samsung) replies to Runze. Runze (Huawei) replies to David (Samsung) David (Samsung) replies to Runze (Huawei) Runze (Huawei) replies to David (Samsung) . Stephen (Qualcomm) provides an r02 Runze (Huawei) supports r02 ==== 8.X, 9.X, 10.X Revisions Deadline ==== David (Samsung) supports r02. ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.10 | S2-2201586 | P-CR | Approval | 23.700-71: Key issue proposal on enhanced positioning architecture for vertical use case. | Huawei, HiSilicon | Rel-18 | Revision of S2-2200781r02, merging S2-2201016. Approved | Approved | |
| 9.10 | S2-2201039 | P-CR | Approval | 23.700-71: New Key issue for WT#1.2 enhancement of LMF selection. | ZTE, Huawei | Rel-18 | r04 agreed. Revised to S2-2201587. | Stephen (Qualcomm) provides an r01 Jinguo(ZTE) provides an r02 Stephen (Qualcomm) asks for clarification from Jinguo (ZTE) Jinguo(ZTE) response to Stephen(Qualcomm) Runze (Huawei) supports to have a separate key issue proposed in this paper. Stephen (Qualcomm) provides an r03 Jinguo(ZTE) provides an r04 to correct a typo ==== 8.X, 9.X, 10.X Revisions Deadline ==== Stephen (Qualcomm) agrees the r04 ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.10 | S2-2201587 | P-CR | Approval | 23.700-71: New Key issue for WT#1.2 enhancement of LMF selection. | ZTE, Huawei | Rel-18 | Revision of S2-2201039r04. Approved | Approved | |
| 9.10 | S2-2201040 | P-CR | Approval | 23.700-71: New Key issue for WT#1.2 Support of location service latency reduction. | ZTE | Rel-18 | Merged into S2-2201629 | Yunjing(CATT) propose to merge this pCR into S2-2200781. Jinguo(ZTE ) is ok to merge into S2-2200781. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.10 | - | - | - | Key issues for WT#2 | - | - | Docs:=6 | - | |
| 9.10 | S2-2200695 | DISCUSSION | Information | Discussion on the Interaction between NWDAF and location service. | vivo, CATT, China Telecom, NTT DOCOMO | Rel-18 | Noted | ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 9.10 | S2-2200242 | P-CR | Approval | 23.700-71: New Key Issue on location services and NWDAF analytics (WT#2). | Samsung | Rel-18 | Merged into S2-2201588 | Yunjing (CATT) propose to merge this pCR into S2-2201014. David (Samsung) confirms the merger into S2-2201014. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.10 | S2-2200696 | P-CR | Approval | 23.700-71: New KI #X: The enhancement of location service with the benefit from NWDAF. | vivo | Rel-18 | Merged into S2-2201588 | Runze (Huawei) provides comment. Hank (vivo) replies to Runze(Huawei). Yunjing (CATT) propose to merge this pCR into S2-2201014. Runze (Hank) replies to Hank (vivo). Hank(vivo) replies to Runze(Huawei) and is fine to take S2-2201014 as the baseline for further discussion suggested by Yunjing(CATT). Runze (Huawei) replies to Hank (vivo) Hank(vivo) confirms the merge into S2-2201014. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.10 | S2-2201014 | P-CR | Approval | 23.700-71: New KI #X: Interaction between Location Service and NWDAF. | CATT, vivo, NTT DOCOMO | Rel-18 | r17 agreed. Revised to S2-2201588, merging S2-2201143, S2-2200242, S2-2201141 and S2-2200696 | Yunjing (CATT) provides r01 based on offline discussion. David (Samsung) provides r02, co-signs the merger. Cai Simon(Nokia) comments r02 Hank(vivo) comments r02. Runze (Huawei) comments on r02. Runze (Huawei) propose to reword bullet 1. Yunjing (CATT) provides r03. David (Samsung) comments on r03. Runze (Huawei) comments on r03. Cai Simon(Nokia) clarifies to David (Samsung) about r03 Yunjing (CATT) provides r04. Cai Simon(Nokia) supports r04 David (Samsung) supports r05. Yunjing(CATT) provides r05. Dimitris (Lenovo) requests clarification on r05 Cai Simon(Nokia) accepts r05 Stephen (Qualcomm) provides an r06 Yunjing (CATT) replies to Dimitris (Lenovo). Yunjing (CATT) can accept r06. Runze (Huawei) comments on r06 and propose r07. Dimitris (Lenovo) provides r08 (based on r07) Cai Simon (Nokia) agree with the reason and provides wording in r09 David (Samsung) provides r10. Cai Simon (Nokia) accepts r10 Runze (Huawei) comments on r10. Hank(vivo) provides r11. Cai Simon (Nokia) provides r12 Runze (Huawei) provides a general comment on all revisions with 'regulatory and SA1 requirements'. Runze (Huawei) provides r13 Hank(vivo) accepts r13. Dimitris (Lenovo) cannot accept r13 Runze (Huawei) provides r14. Runze (Huawei) replies to Dimitris Cai Simon (Nokia) supports r13 Dimitris (Lenovo) responds to Runze (Huawei) provides a proposal Runze (Huawei) can live with the proposal and provides r15. Dimitris (Lenovo) is ok with r15 Hank(vivo) provides r16. Runze (Huawei) accepts r16. David (Samsung) is OK with r16. Cai Simon provides r17 to avoid misunderstanding ==== 8.X, 9.X, 10.X Revisions Deadline ==== Stephen (Qualcomm) prefers the r16 (due to clearer wording) but the r17 is acceptable Cai Simon (Nokia) accepts r17 and r13, not versions in between Dimitris (Lenovo) is ok with r17 Yunjing (CATT) is ok with r17. David (Samsung) can live with r17. Hank (vivo) can live with r17. Runze (Huawei) is ok with r17. ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.10 | S2-2201588 | P-CR | Approval | 23.700-71: New KI #X: Interaction between Location Service and NWDAF. | CATT, vivo, NTT DOCOMO, Samsung | Rel-18 | Revision of S2-2201014r17, merging S2-2201143, S2-2200242, S2-2201141 and S2-2200696. Approved | Approved | |
| 9.10 | S2-2201141 | P-CR | Approval | 23.700-71: FS_eLCS_Ph3: Key Issue and Technical Requirements . | Nokia, Nokia Shanghai Bell | Rel-18 | Merged into S2-2201588 | Yunjing (CATT) propose to merge this pCR into S2-2201014. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.10 | - | - | - | Key issues for WT#3.1 | - | - | Docs:=2 | - | |
| 9.10 | S2-2200792 | P-CR | Approval | 23.700-71: Key Issue for supporting low power high accuracy positioning of GNSS. | Huawei, HiSilicon | Rel-18 | r05 agreed. Revised to S2-2201589. | Richard (Ericsson) Comments KI is not needed Guanglei (Huawei) replies to Richard (Ericsson) and provides r01 Stephen (Qualcomm) provides an r02 Guanglei (Huawei) is fine with r02 Richard (Ericsson) provides r03 Cai Simon(Nokia) ask questions about r03 Richard (Ericsson) provides comments Cai Simon(Nokia) further comments about r03 Guanglei (Huawei) comments on r03 Guanglei (Huawei) provides r06 based on r04 (sorry to waste r05, as I received the email from Ming after I uploaded r05) Ming (CATT) comments and provides r04. Ming (CATT) thanks Guanglei (Huawei), and likes r06. Cai Simon(Nokia) supports r05 Stephen (Qualcomm) comments on the r05 versus r06 Richard (Ericsson) agrees to r05 Guanglei (Huawei) also prefers r05 and provides the link of it Ming (CATT) comments, and can live with r05. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Leo (Deutsche Telekom) suggest to approve r05. ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.10 | S2-2201589 | P-CR | Approval | 23.700-71: Key Issue for supporting low power high accuracy positioning of GNSS. | Huawei, HiSilicon | Rel-18 | Revision of S2-2200792r05. Approved | Approved | |
| 9.10 | - | - | - | Key issues for WT#3.2 | - | - | Docs:=1 | - | |
| 9.10 | S2-2201015 | P-CR | Approval | 23.700-71: New KI #X: UE Positioning without UE/User Awareness. | CATT | Rel-18 | Approved | Runze (Huawei) supports the original version. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Approved |
| 9.10 | - | - | - | Key issues for WT#5 | - | - | Docs:=4 | - | |
| 9.10 | S2-2200240 | P-CR | Approval | 23.700-71: New Key Issue on 5GS Support for Reference UE (WT#5). | Samsung | Rel-18 | Merged into S2-2201591 | Stephen (Qualcomm) suggests to merge this into S2-2200779 which seems more comprehensive David (Samsung) confirms merger into S2-2200779 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.10 | S2-2200779 | P-CR | Approval | 23.700-71: Key Issue: Supporting Positioning Reference Units . | Huawei, HiSilicon | Rel-18 | r08 agreed. Revised to S2-2201590, merging S2-2200368 and S2-2200911 | Stephen (Qualcomm) provides an r01 Runze (Huawei) provides r02. Stephen (Qualcomm) provides an r03 Yunjing(CATT) provides r04. Cai Simon (Nokia) comments the r03/r04 and provides r05 David (Samsung) is OK with r05. Runze (Huawei) provides r06. Stephen (Qualcomm) provides an r07 David (Samsung) provides r08. Runze (Huawei) supports r08. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Stephen (Qualcomm) agrees the r08 ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.10 | S2-2201590 | P-CR | Approval | 23.700-71: Key Issue: Supporting Positioning Reference Units . | Huawei, HiSilicon, Samsung, CATT | Rel-18 | Revision of S2-2200779r08, merging S2-2200368, merging S2-2200368 and S2-2200911. Approved | Approved | |
| 9.10 | S2-2201016 | P-CR | Approval | 23.700-71: New KI #X: Support of Positioning Reference Units. | CATT | Rel-18 | Merged into S2-2201586 | Stephen (Qualcomm) suggests to merge this into S2-2200779 which seems more comprehensive Yunjing (CATT) is fine to merge this into S2-2200779. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.10 | - | - | - | Key issues for WT#6 | - | - | Docs:=3 | - | |
| 9.10 | S2-2200780 | P-CR | Approval | 23.700-71: Key issue proposal on support of location service continuity in case of UE mobility. | Huawei, HiSilicon | Rel-18 | r01 agreed. Revised to S2-2201591, merging S2-2200240 and S2-2201017 | Stephen (Qualcomm) provides an r01 Runze (Huawei) supports r01 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.10 | S2-2201591 | P-CR | Approval | 23.700-71: Key issue proposal on support of location service continuity in case of UE mobility. | Huawei, HiSilicon | Rel-18 | Revision of S2-2200780r01, merging S2-2200240 and S2-2201017. Approved | Approved | |
| 9.10 | S2-2201017 | P-CR | Approval | 23.700-71: New KI #X: Support of Location Service Continuity. | CATT | Rel-18 | Merged into S2-2201591 | Yunjing (CATT) propose to merge this pCR into S2-2200780. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.10 | - | - | - | Key issues for WT#7 | - | - | Docs:=3 | - | |
| 9.10 | S2-2200562 | P-CR | 23.700-71: New KI #X: Support of Network Verified UE Location for UEs using NR Satellite Access. | CATT, Thales | Rel-18 | r06 agreed. Revised to S2-2201592. | Stephen (Qualcomm) provides an r01 Richard (Ericsson) Provide Comments Ming (CATT) Provides r02. Jingran(OPPO) comments on the r02. Yuxin (Xiaomi) Provides r03. Yuxin(Xiaomi) replies to Jingran(OPPO) Ming (CATT) comments on r03. Yuxin (Xiaomi) provides r04 and replies to Ming (CATT). Stephen (Qualcomm) provides an r05 Ming (CATT) replies to Yuxin (Xiaomi) and provides r05. Ming (CATT) provides r06. Ming (CATT) replies to Yuxin (Xiaomi), and clarify the 'study of network based positioning..' itself has been deleted since RP-213522. Yuxin (Xiaomi) replies to Ming (CATT) and requests to double check whether network based positioning is needed. Yuxin (Xiaomi) replies to Ming (CATT). Stephen (Qualcomm) can agree the r06 Yuxin (Xiaomi)also supports r06 ==== 8.X, 9.X, 10.X Revisions Deadline ==== Jean Yves (Thales) is OK with r06 Runze (Huawei) supports r06 ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised | |
| 9.10 | S2-2201592 | P-CR | - | 23.700-71: New KI #X: Support of Network Verified UE Location for UEs using NR Satellite Access. | CATT, Thales, Xiaomi | Rel-18 | Revision of S2-2200562r06. Approved | Approved | |
| 9.10 | S2-2200872 | P-CR | Approval | 23.700-71: New Key Issue #X: supporting network verified UE location in NR satellite access. | Xiaomi | Rel-18 | Merged into S2-2201353 | Richard (Ericsson) Ask for clarification Stephen (Qualcomm) suggests this might be merged into S2-2200562 Ming (CAT) provides a merged version based on S2-2200562 Yuxin (Xiaomi) agrees to merge this pCR into S2-2200562 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.10 | - | - | - | Work plan | - | - | Docs:=1 | - | |
| 9.10 | S2-2200369 | DISCUSSION | Discussion | Work Plan for eLCS_Ph3 | CATT | Noted | Stephen (Qualcomm) comments Ming (CATT) responses. Stephen (Qualcomm) thanks Ming (CATT) for the clarification ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted | |
| 9.11 | - | - | - | Study on Edge Computing Phase 2 (FS_EDGE_Ph2) | - | - | Docs:=49 | - | |
| 9.11 | - | - | - | General (skeleton, scope) | - | - | Docs:=3 | - | |
| 9.11 | S2-2200763 | P-CR | Approval | 23.700-48: TR 23.700-48 skeleton. | Huawei (Rapporteur) | Rel-18 | 23.700-48 TR Skeleton. r01 agreed. Revised to S2-2201771. | Patrice (Huawei) agrees with Shubhranshu (Nokia). Shubhranshu (Nokia) comments ==== 8.X, 9.X, 10.X Revisions Deadline ==== Dario (Qualcomm) clarifies: r01 (which Patrice provided before deadline) should be approved. ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.11 | S2-2201771 | P-CR | Approval | 23.700-48: TR 23.700-48 skeleton. | Huawei (rapporteur) | Rel-18 | Revision of S2-2200763r01. Approved | Approved | |
| 9.11 | S2-2200764 | P-CR | Approval | 23.700-48: Baseline for scope and architectural assumption. | Huawei (Rapporteur) | Rel-18 | Approved | ==== 8.X, 9.X, 10.X Final Deadline ==== | Approved |
| 9.11 | - | - | - | Architecture Assumptions and requirements | - | - | Docs:=2 | - | |
| 9.11 | S2-2200690 | P-CR | Approval | 23.700-48: Architecture assumptions and principles. | CATT | Rel-18 | r14 agreed. Revised to S2-2201772. | Yuan Tao (CATT) provides r01, which merges 2200353 and S2- 2200729. Dario (Qualcomm) provides r02 Mike (InterDigital) provides r03 Mike (InterDigital) indicates support for r05 Dan (China Mobile) provides r05 based on r04 Dan (China Mobile) provides r04 and object r02 and r03 Shubhranshu (Nokia) comments and provides r06 Dan (China Mobile) response Patrice (Huawei) provides an update r07 and comments Dario (Qualcomm) supports r07 Yuan Tao (CATT) responds and provides r08. Magnus (Ericsson) provides r09 Dan(CHina Mobile) provides r10 Huazhang (vivo) provides r11 based on r10 Patrice (Huawei, rapporteur) proposes, as discussed offline, to take formally S2-2200690 as baseline for architectural assumptions, and merge S2-2200353 and S2-2200729 into it. Patrice (Huawei) provides r12, comments. Dario (Qualcomm) comments and provide r13 Dan (China Mobile) comments and provide r14 Yuan Tao responses to Dan (China Mobile). Zhuoyun (Tencent) comments. Patrice (Huawei) comments further in support of Dan's (China Mobile) r14. Yuan Tao (CATT) is fine with r14. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Dario (Qualcomm) is OK with r14 Zhuoyun (Tencent) is ok with r14. Dan (China Mobile) suggest to go with r14 Magnus O (Ericsson) is also ok with r14 ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.11 | S2-2201772 | P-CR | Approval | 23.700-48: Architecture assumptions and principles. | CATT, China Mobile, Tencent, Ericsson, Huawei | Rel-18 | Revision of S2-2200690r14. Approved | Approved | |
| 9.11 | - | - | - | Key Issues | - | - | Docs:=34 | - | |
| 9.11 | S2-2200101 | P-CR | Approval | 23.700-48: Key Issue: support UE access EHE in a VPLMN in roaming scenario | China Mobile | Rel-18 | r17 agreed. Revised to S2-2201773, merging S2-2200615, S2-2200691, S2-2200728 and S2-2200919 | Laurent (Nokia): Comments (concerns) and proposes text for compromise and merging Mike (InterDigital) provides r02 Dan(China Mobile) OK with Laurent's suggestion and provide r01. S2-2200691 is merged into this paper. Dan (China Mobile) OK with r02 Changhong (Intel) provides r03 Svante (Sony) supports the updated proposal so we would like to co-sign this contribution and treat S2-2200919 as merged into this one. Xinpeng(Huawei) comments. Patrice (Huawei) provides an update r04 and comments. Yuan Tao (CATT) provides r07. Jicheol (Samsung) provides r06. Dario (Qualcomm) comments and provides r05 Magnus (Ericsson) provides r08 Huazhang (vivo) provides r09 based on R08 Dan (China Mobile) is OK with r09 Patrice (Huawei, rapporteur) proposes, as discussed offline, to formally take S2-2200101 as the baseline for KI#1 content, and merging S2-2200691, S2-2200615, S2-2200728, S2-2200919 and S2-2200915 into it. Patrice (Huawei) provides r10. Laurent (Nokia): provides r11 Mike (InterDigital) asks a question Jicheol (Samsung) confirmed Mike(Interdigital)'s understanding. Changhong (Intel) clarifies on NOTE 2 in r04 and provides r12. Dan (China Mobile) provide r13 with some clean Patrice (Huawei) comments on r12 Mike (InterDigital) provides r14 Svante (Sony) provides r15 Dan (China Mobile) is OK with r15 Patrice (Huawei) provides r16, finally clarifying the puzzling note. Laurent (Nokia): provides r17 ==== 8.X, 9.X, 10.X Revisions Deadline ==== Changhong (Intel) replies to Patrice. Patrice (Huawei) further comments. Dan(China Mobile) is OK for r17,16,15, prefer 17 Mike (InterDigital) prefers r17 Changhong (Intel) is OK with r15, r16 and r17. Laurent (Nokia): Strongly prefers R17. objects to any version between r00 and R10 both included Svante (Sony) prefers r17 and accept any version from r15. ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.11 | S2-2201773 | P-CR | Approval | 23.700-48: Key Issue: support UE access EHE in a VPLMN in roaming scenario. | China Mobile, Samsung, CATT, Ericsson, vivo, InterDigital Inc., Sony | Rel-18 | Revision of S2-2200101r17, merging S2-2200615, S2-2200691, S2-2200728 and S2-2200919. Approved | Approved | |
| 9.11 | S2-2200691 | P-CR | Approval | 23.700-48: New KI: Accessing EHE in a VPLMN when roaming. | CATT | Rel-18 | Merged into S2-2201773 | Laurent (Nokia): Comments (concerns) and proposes text for compromise and merging Dan (China Mobile) suggest to merge this paper into S2-2200101 Yuan Tao (CATT) replies to Laurent (Nokia). Yuan Tao (CATT) agrees to merge this paper into S2-2200101. Patrice (Huawei) indicates that this paper is merged to S2-2200101. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.11 | S2-2200916 | P-CR | Approval | 23.700-48: New KI: Fast and efficient network exposure improvements. | Huawei, HiSilicon | Rel-18 | r14 agreed. Revised to S2-2201774, merging S2-2200997 and S2-2200666 | Jinsook (DISH) Comment for asking a clarification Hui (Huawei) responses. Jinsook (DISH) Thanks for the clarification Dan (China Mobile) suggest to merge RAN related part of S2-2200229 into this paper. Changhong (Intel) provides r01 and cosigns. Hui (Huawei) fine with r01. Hui (Huawei) confirms that S2-2200229 can be considered as merged into this paper. Shubhranshu (Nokia) comments Shubhranshu (Nokia) comments and provides r02 Hui(Huawei) objects r02 and provides r03. Patrice (Huawei, rapporteur) indicates that it has been discussed offline to take S2-2200916 as the basis for KI#2 content, merging S2-2200666, S2-2200614, S2-2200229 and S2-2201236. Magnus (Ericsson) provides r04 Dario (Qualcomm) provides r05. Hui (Huawei) provides r07, please ignore r06. Magnus (Ericsson) provides r08 Shubhranshu (Nokia) provides r09 Magnus O (Ericsson) comments Hui (Huawei) provides r11 Magnus O (Ericsson) comments further Hui (Huawei) provides r12 and replies to Magnus. Magnus (Ericsson) provides r13 Hui (Huawei) disagree with r13. Hui (Huawei) provides r14 as a compromise. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.11 | S2-2201774 | P-CR | Approval | 23.700-48: New KI: Fast and efficient network exposure improvements. | Huawei, HiSilicon, Intel, Nokia, Nokia Shanghai Bell, China Mobile | Rel-18 | Revision of S2-2200916r14, merging S2-2200997 and S2-2200666. Approved | Approved | |
| 9.11 | S2-2200231 | P-CR | Approval | 23.700-48: Key Issue: DNAI determined by 5GC based on AF information. | China Mobile | Rel-18 | Merged into S2-2201512 | Dan(China Mobile) agree to merge this paper into S2-2200613 Patrice (Huawei, rapporteur) confirms that it has been discussed offline to merge KI#7 papers to S2-2200613. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.11 | S2-2200376 | P-CR | Approval | 23.700-48: KI#4: Influencing UPF and EAS (re)location for collections of UEs. | NTT DOCOMO | Rel-18 | Merged into S2-2201778 | Dario (Qualcomm) asks if this paper is merged into 0627. Tugce (NTT DOCOMO) agrees to merge into 0627. Patrice (Huawei, rapporteur) indicates, as discussed offline, that S2-2201232 should be the host for KI#4 discussions, and therefore S2-2200376 should be merged rather in S2-2201232. Tugce (NTT DOCOMO) agrees to merge into 1232. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.11 | S2-2201088 | P-CR | Approval | 23.700-48: KI#4: Influencing UPF and EAS (re)location for collections of UEs. | Lenovo, Motorola Mobility | Rel-18 | Merged into S2-2201778 | Dario (Qualcomm) asks if this paper is merged into 0627. Patrice (Huawei, rapporteur) indicates that it has been proposed offline to use S2-2201232 as the basis for KI#4, and therefore S2-2201088 would be merged to S2-2201232. Tingfang (Lenovo) is OK to merge 1088 into 1232 . ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.11 | S2-2200435 | P-CR | Approval | 23.700-48: Clarification of KI#6: Avoiding UE to switch away from PDU Session used for Edge Computing. | Ericsson | Rel-18 | r16 agreed. Revised to S2-2201775, merging S2-2200617, S2-2200658, S2-2200693, S2-2200766 and S2-2200920 | Mike (InterDigital) proposes that we use this paper as a baseline for Key Issue #6 / Work Task #8, proposes to mark the other 6 papers for this KI as merged into this paper, and provides r01. Sudeep (Apple) provides comments. Huazhang (vivo) provides comments. Mike (InterDigital) replies to Huazhang (vivo) and Sudeep (Apple) and provides r02 Yuan Tao (CATT) comments. Svante (Sony) comments and reply to questions and provides r03 Mike (InterDigital) replies to Svante (Sony) and Yuan Tao (CATT) Dario (Qualcomm) provides r04 Magnus (Ericsson) provides r05 Huazhang (vivo) provides r06 based on r05, Huazhang add a precondition of this KI that The user's preference and choices should be taken into consideration. The pre-condition of whether the EC traffic will be switched or not is that should be approved by user first. Patrice (Huawei, rapporteur) indicates, as discussed offline, that this S2-2200435 has been proposed to host KI#6 content, and that S2-2200617, S2-2200658, S2-2200693, S2-2200766, S2-2200920 and S2-2201012 would be merged into it. Magnus (Ericsson) provides r07 Patrice (Huawei) provides r08. Mike (InterDigital) provides r09 Sudeep (Apple) provides r10. Dario (Qualcomm) provides r11. Dario (Qualcomm) replies to Huazhang and cannot accept r06 to 10. Huazhang (vivo) comments on r11, and don't agree in r11 to delete such user preference Huazhang (vivo) replies to Dario and cannot accept r11 if no user preference is considered, but provide r12 as compromise that user preference needs to be considered during study phase when defining solutions. Patrice (Huawei) comments, OK with r12 Changhong (Intel) provides r13. Svante (Sony) provides r14. Patrice (Huawei) comments on Changhong's (Intel's) change. Magnus (Ericsson) provides r15 Mike (InterDigital) comments to Patrice (Huawei) and Changhong (Intel) Yuan Tao (CATT) replies to Magnus (Ericsson). Hyesung (Samsung) replies to Magnus (Ericsson) Patrice (Huawei) provides r16. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Dario (Qualcomm) can only accept r11 and objects all other revisions (unless the NOTE in r12-r16 is removed). Huazhang (vivo) prefers r16, objects r11 that without this note. The note is already our compromise to live with the KI. I don't understand why Dario thinks this note is correct, but afraid to add it Magnus O (Ericsson) is ok with r11, r16 and r16 without the Note in 5.6.1. Proposes to go with the r16 without the Note. Svante (Sony) prefers r16. We also accept r16 without the note. Patrice (Huawei) proposes to go with r16 with the note. Without the note is also OK, but the note should be acceptable by all (cf comment). Mike (InterDigital) is ok with R11, R16, and R16 with no note Sudeep (Apple) agrees with Patrice's (Huawei) suggestion to go with r16. Dario (Qualcomm) confirms objection unless in r16 last sentence in 6.5.2 is removed and note in 6.5.1 is reworded to 'User preference may or may not be considered depending on the solution' Magnus O (Ericsson) asks if we can go with r16 with rephrased note and removal the last sentence in 6.5.2 Changhong (Intel) supports Qualcomm's proposal and proposes to go with r16 with rephrased note and removal of the last sentence in 6.5.2. Patrice (Huawei, rapporteur) proposes to then confirm for CC#4 or for CC#5 the approval of r16 with the note in 5.6.1 saying 'User preference may be considered depending on solutions.' and the removal of the last sentence in 5.6.2: 'User preference of whether the EC traffic of 5GS should be kept or switched to non-integrated access should be considered during the study phase when designing solutions.' Huazhang (vivo) can compromise to go with r16 with removal of the last sentence in 6.5.2, and rephrase the note as: NOTE: User preference needs to be considered. Huazhang (vivo) can compromise to go with r16 with removal of the last sentence in 6.5.2, and rephrase the note as: NOTE: User preference needs to be considered. Magnus O (Ericsson) proposes an editor's note to resolve the deadlock Huazhang (vivo) agree with Magnus of this editor's note Editor's note: If and how to address user preferences is FFS Huazhang (vivo) can compromise to go with r16 with removal of the last sentence in 6.5.2, and add Editor's note: If and how to address user preferences is FFS Patrice (Huawei) supports Magnus O's (Ericsson) proposal as a way to resolve the deadlock. The proposal would now be: r16 + note in 5.6.1 replaced with editor's note: 'If and how to address user preferences is FFS', and remove last sentence of 5.6.2: 'User preference of whether the EC traffic of 5GS should be kept or switched to non-integrated access should be considered during the study phase when designing solutions.' (for CC#4 or for CC#5) ==== 8.X, 9.X, 10.X Final Deadline ==== Dario (Qualcomm) accepts r16 with removal of the last sentence in 6.5.2, and EN proposed by Ericsson. | Revised |
| 9.11 | S2-2201775 | P-CR | Approval | 23.700-48: Clarification of KI#6: Avoiding UE to switch away from PDU Session used for Edge Computing. | Ericsson, CATT, Huawei, HiSilicon, Sony, InterDigital Inc. | Rel-18 | Revision of S2-2200435r16, merging S2-2200617, S2-2200658, S2-2200693, S2-2200766 and S2-22009. Approved | Approved | |
| 9.11 | S2-2200613 | P-CR | Approval | 23.700-48: Key Issue on mapping relationship between DNAI and IP range. | vivo | Rel-18 | r05 agreed. Revised to S2-2201776, merging S2-2200529 and S2-2200902 | Huazhang (vivo): merge S2-2200231 and S2-2200767 to S2-2200613, and use S2-2200613 as baseline as WT#7 in FS_EDGE_Ph2, and provides r01 Dario (Qualcomm) provides r02 Magnus (Ericsson) provides r03 Xinpeng(Huawei) ask for clarification. Shubhranshu (Nokia) provides r04 Patrice (Huawei) confirms that it has been discussed offline that S2-2200613 is the host for KI#7 content, and that S2-2200231 and S2-2200767 should be merged to S2-2200613. Magnus H (Ericsson) comments Patrice (Huawei) provides r05. Xinpeng(Huawei) comments Huazhang (vivo) is ok with r05. Magnus (Ericsson) provides r06 Patrice (Huawei) disagrees with r06. Huazhang (vivo) provides r08, please ignore the r07 Patrice (Huawei) further comments, still with the same concern towards r08. Huazhang (vivo) provide r09, that to have an agreement now, and turn back at next meeting if we have any modification on KI Patrice (Huawei) has an issue with r09 similar to r06. Huazhang (vivo) can confirm that r09 nearly the same as r05 that I forget to refresh the words in section 2:proposal. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Huazhang (vivo) suggests we go ahead with r05, this is the only way forward. And Magnus would you mind co-sign this version? And some of the details we still have time next meeting Dan(China Mobile) suggests to go with r05, Patrice (Huawei) proposes to go with r05 as well, other revisions not OK. Shubhranshu (Nokia) r05 is OK Dario (Qualcomm) is also OK w/ r05 Magnus H (Ericsson) accepts r05 Changhong (Intel) comments Patrice (Huawei) replies to Changhong (Intel). Relja (KPN) accepts r05 ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.11 | S2-2201776 | P-CR | Approval | 23.700-48: Key Issue on mapping relationship between DNAI and IP range. | Vivo, CMCC, Huawei | Rel-18 | Revision of S2-2200613r05, merging S2-2200529 and S2-2200902. Approved | Approved | |
| 9.11 | S2-2200615 | P-CR | Approval | 23.700-48: Key Issue on edge computing in roaming scenarios. | vivo | Rel-18 | Merged into S2-2201773 | Changhong (Intel) proposes to merge it into S2-2200101. Patrice (Huawei, rapporteur) would like to confirm that it's been discussed offline to merge into S2-220101. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.11 | S2-2200616 | P-CR | Approval | 23.700-48: Key Issue on provision the same edge services to group of UE. | vivo | Rel-18 | Merged into S2-2201778 | Dario (Qualcomm) asks if this paper is merged into 0627. Patrice (Huawei, rapporteur) proposes to merge to S2-2201232 as discussed offline for KI#4, rather than S2-2200627. Huazhang (vivo) is ok to merge this paper to S2-2201232. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.11 | S2-2200617 | P-CR | Approval | 23.700-48: Key Issue on maintenance the edge-traffic when switch from 3GPP to non-3GPP access. | vivo | Rel-18 | Merged into S2-2201775 | Patrice (Huawei, rapporteur) indicates that S2-2200435 has been discussed to be the host for KI#6 content, and therefore S2-2200617 should be merged to S2-2200435. Huazhang (vivo) agree to merge this paper to S2-2200435. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.11 | S2-2200626 | P-CR | Approval | 23.700-48: Key Issue for FS_EDGE_Ph2 WT#5. | Huawei, HiSilicon | Rel-18 | Merged into S2-2201798 | Dario (Qualcomm) asks if 0626 is merged into 0732 Patrice (Huawei, rapporteur) indicates that based on the offline discussion, this contribution is merged into S2-2200732. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.11 | S2-2200627 | P-CR | Approval | 23.700-48: Key Issue for FS_EDGE_Ph2 WT#6 . | Huawei, HiSilicon | Rel-18 | Merged into S2-2201778 | Magnus H (Ericsson) provides r01 Xinpeng(Huawei) comments. Patrice (Huawei, rapporteur) proposes, based on the offline discussion, that KI#4 content is being addressed in S2-2201232, therefore S2-2200627 would be merged to S2-2201232. Magnus H (Ericsson) answers Xinpeng Xinpeng(Huawei) replies to Magnus H (Ericsson). ==== 8.X, 9.X, 10.X Revisions Deadline ==== Patrice (Huawei) confirms that S2-2200627 is merged to S2-2201232. ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.11 | S2-2200658 | P-CR | Approval | 23.700-48: Key issue on avoidance of EC traffic switching. | Samsung | Rel-18 | Merged into S2-2201775 | Patrice (Huawei, rapporteur) indicates that S2-2200435 has been discussed offline to be the host for KI#6 content, and therefore S2-2200658 should be merged to S2-2200435. Hyesung (Samsung) agrees to merge this pCR into S2-2200435. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.11 | S2-2200666 | P-CR | Approval | 23.700-48: KI on network exposure of UE traffic related information for EC. | Samsung | Rel-18 | Merged into S2-2201774 | Hui (Huawei) suggests to merge this paper into S2-2200916. Hyesung (Samsung) is ok to merge this paper into S2-2200916. Patrice (Huawei, rapporteur) confirms the merge to S2-2200916. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.11 | S2-2200693 | P-CR | Approval | 23.700-48: New KI: Avoiding UE to switch away from EC PDU Session. | CATT | Rel-18 | Merged into S2-2201775 | Patrice (Huawei, rapporteur) indicates that S2-2200435 has been discussed offline to be the host for KI#6 content, and therefore S2-2200693 should be merged to S2-2200435. Yuan Tao (CATT) confirms that S2-2200693 is merged into S2-2200435. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.11 | S2-2200728 | P-CR | Approval | 23.700-48: A scenario for KI#1 Accessing EHE in a VPLMN when roaming. | Samsung | Rel-18 | Merged into S2-2201773 | Laurent (Nokia): Comments (concerns) Dan (China Mobile): Comments and suggest to add this paper's general scenario consideration/idea in to S2-2200101 Patrice (Huawei,rapporteur) indicates that it's been discussed offline to merge to S2-2200101. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Jicheol (Samsung) confirms this paper has been merged into the S2-2200101 ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.11 | S2-2200732 | P-CR | Approval | 23.700-48: New Key Issue: Policies for finer granular sets of UEs. | Tencent, Tencent Cloud | Rel-18 | r07 agreed. Revised to S2-2201777, merging S2-2200841 | Zhuoyun (Tencent) corrects the Tdoc number in the email title and provides r03. Xinpeng(Huawei) provides r04. Patrice (Huawei, rapporteur) indicates that, based on the offline discussion, S2-2200732 is to be used for KI#3 content, merging S2-2200626. Laurent (Nokia): provides r05 Zhuoyun (Tencent) provides r06. Xinpeng(Huawei) provides r07. Laurent (Nokia): provides r08 Xinpeng(Huawei) comments. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Zhuoyun (Tencent) comments. Laurent (Nokia): can only live with r05/R08; objects to any other version: R05/R08 last sentence is incomplete and I propose adding 2 words to this last sentence Xinpeng(Huawei) asks Laurent (Nokia) for what 'policy does not belong to the 5GC operator' means. Laurent (Nokia): answers: it is the *AF* providing the policies that does not belong to the 5GC operator Zhuoyun (Tencent) asks for clarification. Magnus H (Ericsson) ask for clarification and makes suggestion Zhuoyun (Tencent) thanks for the clarification. Patrice (Huawei) proposes to go with r07 + text to support Nokia's intention to be defined in the next few hours. Magnus H (Ericsson) is fine with proposal from Patrice (Huawei) Magnus H (Ericsson) prefers r03 but can live with all other revisions >r03 Patrice (Huawei) proposes to go with r07 + the following text (r08 not OK): Solutions for this KI will identify their support for the following: - AF under operator control - AF under 3rd party control Zhuoyun (Tencent) is ok with the proposal from Patrice, and could also accept other revisions >r02. Patrice (Huawei, rapporteur) proposes to confirm for CC#4 or for CC#5 the approval of r07 + the text proposed in my previous comment. ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.11 | S2-2201777 | P-CR | Approval | 23.700-48: New Key Issue: Policies for finer granular sets of UEs. | Tencent, Tencent Cloud, Nokia, Nokia Shanghai Bell, Charter, Huawei, HiSilicon | Rel-18 | Revision of S2-2200732r07, merging S2-2200841. Approved | Approved | |
| 9.11 | S2-2200766 | P-CR | Approval | 23.700-48: KI#6 scenario. | Huawei, HiSilicon | Rel-18 | Merged into S2-2201775 | Patrice (Huawei, rapporteur) indicates that S2-2200435 has been discussed offline to be the host for KI#6 content, and therefore S2-2200766 should be merged to S2-2200435. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.11 | S2-2200767 | P-CR | Approval | 23.700-48: KI#7 scenario and assumption. | Huawei, HiSilicon | Rel-18 | Merged into S2-2201727 | Magnus H (Ericsson) suggest as been already proposed that this is merged into 0613 Patrice (Huawei, rapporteur) confirms that this has been discussed that S2-2200613 hosts the KI#7 content, and that S2-2200767 is merged to S2-2200613. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.11 | S2-2200919 | P-CR | Approval | 23.700-48: KI#1 Improvements to roaming, to support access to EHE in a VPLMN. | Sony | Rel-18 | Merged into S2-2201773 | Dan (China Mobile) suggest this paper merged into S2-2200101 Patrice (Huawei, rapporteur) indicates that this is merged to S2-2200101, as confirmed by Svante (Sony). ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.11 | S2-2200920 | P-CR | Approval | 23.700-48: KI#6 Proposal for Avoiding UE to switch away from EC PDU Session. | Sony | Rel-18 | Merged into S2-2201775 | Patrice (Huawei, rapporteur) indicates that S2-2200435 has been discussed offline to be the host for KI#6 content, and therefore S2-2200920 should be merged to S2-2200435. Svante (Sony) confirms that S2-2200920 is merged into S2-2200435. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.11 | S2-2201012 | P-CR | Approval | 23.700-48: WT#8: New Key Issue on Conflicting Connectivity Preferences. | InterDigital Inc. | Rel-18 | Merged into S2-2201785 | Patrice (Huawei, rapporteur) confirmed that S2-2200435 has been discussed offline to be the host for KI#6 content, and therefore S2-2201012 should be merged to S2-2200435. Mike (InterDigital) confirms that S2-2201012 is merged into S2-2200435. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.11 | S2-2201084 | P-CR | Approval | 23.700-48: New solution (WT5) for supporting offload policies to match more granular sets of UE(s). | Nokia, Nokia Shanghai Bell | Rel-18 | Postponed | Patrice (Huawei) proposes to postpone the solution to the next meeting. Laurent (Nokia): yes let's postpone all solutions. I agree with postponing ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Postponed |
| 9.11 | S2-2201232 | P-CR | Approval | 23.700-48: WT#6 Key Issue Description and Scenario. | Nokia, Nokia Shanghai Bell | Rel-18 | r12 agreed. Revised to S2-2201778, merging S2-2200376, S2-2200616, S2-2200627 and S2-2201088 | Dario (Qualcomm) asks if this paper is merged into 0627. Patrice (Huawei, rapporteur) indicates that it has been discussed offline to use this document S2-2201232 as the basis for KI#4, merging S2-2200376, S2201088, S2-2200616, S2-2200627, and S2-2200692. Shubhranshu (Nokia) provides r01 Tugce (NTT DOCOMO) have comments. Magnus (Ericsson) provides r02 Tugce (NTT DOCOMO) is not ok with r02 and has comments. Dario (Qualcomm) asks question and proposed r03 Xinpeng(Huawei) provides r04. Tingfang (Lenovo) provides r05. Magnus (Ericsson) provides r06 Shubhranshu (Nokia) provides r07 Magnus H (Ericsson) comments to justify EN Tingfang (Lenovo) provides r08. Tugce (NTT DOCOMO) provides r09. Patrice (Huawei) provides r10 with editorial clean up. Shubhranshu (Nokia) provides r11 Magnus H (Ericsson) provides r12 Patrice (Huawei) further comments. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Huazhang (vivo) don't object to r12, but have some comments to r12, that some of the bullets a little bit repetition. We need simplification Xinpeng(Huawei) is ok with r12,r10, r09,r08,r07,r06 and objects to all other version. Tingfang (Lenovo) is OK with r08-r12, objects others. ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.11 | S2-2201778 | P-CR | Approval | 23.700-48: WT#6 Key Issue Description and Scenario. | Nokia, Nokia Shanghai Bell, NTT DOCOMO, Lenovo, Motorola Mobility, Huawei, HiSilicon, Vivo, CATT, Ericsson | Rel-18 | Revision of S2-2201232r12, merging S2-2200376, S2-2200616, S2-2200627 and S2-2201088. Approved | Approved | |
| 9.11 | S2-2201234 | P-CR | Approval | 23.700-48: WT#7: Key Issue Description and Scenario . | Nokia, Nokia Shanghai Bell | Rel-18 | Merged into S2-2201779 | Dario (Qualcomm) asks questions for clarification and proposes to merge this into 1246. Shubhranshu (Nokia) responds Patrice (Huawei, rapporteur) indicates, that, as discussed offline, it is proposed to use S2-2201246 as the basis for KI#5 content. Therefore, S2-2201234 would be merged to S2-2201246. Shubhranshu (Nokia) OK to merge into S2-2201246 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.11 | S2-2201246 | P-CR | Approval | 23.700-48: KI#5: GSMA OPG impacts and improvements for EHE operated by separate party. | Qualcomm Incorporated | Rel-18 | r09 agreed. Revised to S2-2201779, merging S2-2201234 | Dan (China Mobile) provides r02 with some question, also suggest to merge S2-2200230 into this paper Dario (Qualcomm) provides r01 Magnus O (Ericsson) comments Magnus (Ericsson) provides r03 Shubhranshu (Nokia) responds Shubhranshu (Nokia) asks for clarification Xinpeng(Huawei) comments. Patrice (Huawei, rapporteur) indicates that it has been discussed and agreed to use S2-2201246 as the host for KI#5 content. Therefore, S2-2201232 and S2-2200230 can be marked as merged to S2-2201246. Dan (China Mobile) responds Magnus O (Ericsson) Answers to earlier question from Shubhranshu Shubhranshu (Nokia) provides r04 Shubhranshu (Nokia) comments Shubhranshu (Nokia) clarifies that S2-2201234 (and not S2-2201232 ) is merged to S2-2201246 Dan (China Mobile) confirm something Dario (Qualcomm) provides r06, asks to ignore r05 and replies. Magnus O (Ericsson) comments again Hyesung (Samsung) comments. Patrice (Huawei) comments. Dan (China Mobile) reply Changhong (Intel) comments and is not convinced with this key issue. Magnus O (Ericsson) provides comment Magnus O (Ericsson) comments more Magnus (Ericsson) provides r07 Xinpeng(Huawei) replies to Magnus O (Ericsson). Xinpeng(Huawei) provides r08. Magnus (Ericsson) provides r09 Dario (Qualcomm) provides r10 and r11 ==== 8.X, 9.X, 10.X Revisions Deadline ==== Magnus O (Ericsson) propose to go with r09, object to r10, r11, r08, r00-r02, r04-r06 Xinpeng(Huawei) is fine to go with r09. Shubhranshu (Nokia) OK with r09 Dario (Qualcomm) can live w/ r09 ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.11 | S2-2201779 | P-CR | Approval | 23.700-48: KI#5: GSMA OPG impacts and improvements for EHE operated by separate party. | Qualcomm Incorporated, Nokia, Nokia Shanghai Bell | Rel-18 | Revision of S2-2201246r09, merging S2-2201234. Approved | Approved | |
| 9.11 | - | - | - | Solutions | - | - | Docs:=2 | - | |
| 9.11 | S2-2201247 | P-CR | Approval | 23.700-48: KI#5: solutions for supporting federated Operator Platforms . | Qualcomm Incorporated | Rel-18 | Noted | Dan (China Mobile)comments and would like to see other's opinion of whether solution can be accepted for this meeting Dario (Qualcomm) replies to Dan Magnus O (Ericsson) comments Dario (Qualcomm) replies to Magnus. Dan (China Mobile) comments Magnus O (Ericsson) proposes to note 1247 Patrice (Huawei) proposes to note the proposed solution at this meeting, as we are trying to converge on the KI itself. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Shubhranshu (Nokia) agrees to note this paper Patrice (Huawei) confirms that this document should be noted. ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 9.11 | S2-2201083 | P-CR | Approval | 23.700-48: New solution for WT1: URSP solution to support roamers access to EHE in a VPLMN. | Nokia, Nokia Shanghai Bell | Rel-18 | Postponed | Mike (InterDigital) asks a question Changhong (Intel) proposed to note this paper. Patrice (Huawei) proposes to postpone the solution. Dario (Qualcomm) supports postposing this paper. Jicheol (Samsung) also supports postponing this solution paper and suggests to discuss any enhancement of URSP related (VPLMN and any enhancement of URSP guidance) should be discuss in the agenda 9.22 (UEPo) not here. Laurent (Nokia): yes let's postpone all solutions. I agree with postponing ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Postponed |
| 9.11 | - | - | - | Documents exceeding quota | - | - | Docs:=8 | - | |
| 9.11 | S2-2200353 | P-CR | Approval | 23.700-48: The architecture assumptions and requirements for FS_EDGE_Ph2. | China Mobile | Rel-18 | Not Handled | ==== 8.X, 9.X, 10.X Final Deadline ==== | - |
| 9.11 | S2-2200729 | P-CR | Approval | 23.700-48: Architectural assumptions and principles. | Tencent, Tencent Cloud | Rel-18 | Not Handled | ==== 8.X, 9.X, 10.X Final Deadline ==== | - |
| 9.11 | S2-2200230 | P-CR | Approval | 23.700-48: Key issue: GSMA OPG impacts and improvements for EHE operated by separate party. | China Mobile | Rel-18 | Not Handled | ==== 8.X, 9.X, 10.X Final Deadline ==== | - |
| 9.11 | S2-2200614 | P-CR | Approval | 23.700-48: Key Issue on enhancement of local network event exposure. | vivo | Rel-18 | Not Handled | ==== 8.X, 9.X, 10.X Final Deadline ==== | - |
| 9.11 | S2-2200229 | P-CR | Approval | 23.700-48: Key Issue: Fast and efficient network exposure improvements. | China Mobile | Rel-18 | Not Handled | ==== 8.X, 9.X, 10.X Final Deadline ==== | - |
| 9.11 | S2-2201236 | P-CR | Approval | 23.700-48: WT#3 Key Issue Description and Scenario . | Nokia, Nokia Shanghai Bell | Rel-18 | Not Handled | ==== 8.X, 9.X, 10.X Final Deadline ==== | - |
| 9.11 | S2-2200692 | P-CR | Approval | 23.700-48: New KI: Influencing UPF and EAS relocation for collections of UEs. | CATT | Rel-18 | Not Handled | ==== 8.X, 9.X, 10.X Final Deadline ==== | - |
| 9.11 | S2-2200915 | P-CR | Approval | 23.700-48: KI#1: Accessing EHE in a VPLMN when roaming. | Huawei, HiSilicon | Rel-18 | Not Handled | ==== 8.X, 9.X, 10.X Final Deadline ==== | - |
| 9.12 | - | - | - | Study on 5G System with Satellite Backhaul (FS_5GSATB) | - | - | Docs:=12 | - | |
| 9.12 | S2-2200380 | P-CR | Approval | 23.700-27: FS_5GSATB TR Skeleton. | CATT (rapporteur) | Rel-18 | 23.700-27 TR Skeleton. Approved | ==== 8.X, 9.X, 10.X Final Deadline ==== | Approved |
| 9.12 | S2-2200381 | P-CR | Approval | 23.700-27: FS_5GSATB TR Scope. | CATT (rapporteur) | Rel-18 | r01 agreed. Revised to S2-2201593. | Hannu (Nokia) provides r01. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.12 | S2-2201593 | P-CR | Approval | 23.700-27: FS_5GSATB TR Scope. | CATT (rapporteur) | Rel-18 | Revision of S2-2200381r01. Approved | Approved | |
| 9.12 | S2-2200382 | P-CR | Approval | 23.700-27: FS_5GSATB TR Architectural assumptions. | CATT | Rel-18 | r02 agreed. Revised to S2-2201594. | Hannu (Nokia) provides r01. Hucheng (CATT) comments. Stefan (Ericsson) provides r02 Hannu (Nokia) supports r02 Hucheng (CATT) supports r02. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.12 | S2-2201594 | P-CR | Approval | 23.700-27: FS_5GSATB TR Architectural assumptions. | CATT | Rel-18 | Revision of S2-2200382r02. Approved | Approved | |
| 9.12 | S2-2200383 | P-CR | Approval | 23.700-27: Key issues for WT#2. | CATT, Huawei | Rel-18 | r06 agreed. Revised to S2-2201595, merging S2-2200785 | Haris(Qualcomm) proposes r01 Hucheng responds to Haris, and provides r02 Stefan (Ericsson) provides r03 Hucheng (CATT) responds to Stefan (Ericsson). Hannu (Nokia) comments. Haris(Qualcomm) comments that 'UPF on board' is the term used in the WT of the approved SID Hucheng (CATT) clarifies. Stefan (Ericsson) replies to Hucheng Guanglei (Huawei) provides comments Hucheng (CATT) replies to Haris(Qualcomm) and Stefan (Ericsson) Stefan (Ericsson) provides r04 Hucheng (CATT) responds to Stefan (Ericsson) and provides r05. Guanglei (Huawei) comments on r04 and r05 and provides r06 ==== 8.X, 9.X, 10.X Revisions Deadline ==== Guanglei (Huawei) proposes to approve r06 ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.12 | S2-2201595 | P-CR | Approval | 23.700-27: Key issues for WT#2. | CATT, Huawei | Rel-18 | Revision of S2-2200383r06, merging S2-2200785. Approved | Approved | |
| 9.12 | S2-2200785 | P-CR | Approval | 23.700-27: Key Issue on enable edge computing services via UPF deployed on satellite. | vivo | Rel-18 | Merged into S2-2201595 | Hucheng (CATT) proposes to merge this paper into S2-2200383. Huazhang (vivo) response to Hucheng(CATT) Hucheng (CATT) comments. Leo (Deutsche Telekom) suggests to merge S2-2200785 into S2-2200383. Stefan (Ericsson) support to merge ==== 8.X, 9.X, 10.X Revisions Deadline ==== Huazhang (vivo) is ok to merge ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.12 | S2-2200917 | P-CR | Approval | 23.700-27: New Key Issue: PCC/QoS control enhancement considering dynamic satellite backhaul. | Huawei, HiSilicon, CATT | Rel-18 | r05 agreed. Revised to S2-2201596. | Haris(Qualcomm) provides r01 Hui(Huawei) provides r02 Stefan (Ericsson) comments Hannu (Nokia) provides r03. Stefan (Ericsson) provides r04 Hui (Huawei) provides r05 Hucheng (CATT) supports r05. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.12 | S2-2201596 | P-CR | Approval | 23.700-27: New Key Issue: PCC/QoS control enhancement considering dynamic satellite backhaul. | Huawei, Hisilicon, CATT | Rel-18 | Revision of S2-2200917r05. Approved | Approved | |
| 9.12 | S2-2201008 | P-CR | Approval | 23.700-27: Solution for dynamic backhaul delay. | Nokia, Nokia Shanghai Bell | Rel-18 | r04 agreed. Revised to S2-2201597. | Hucheng (CATT) comments. Hannu (Nokia) answers to Hucheng (CATT). Hucheng (CATT) asks for further clarifications. Haris(Qualcomm) comments inline and point that wrong reference to TS 23.501 clause is used in the solution Guanglei (Huawei) asks questions to Hucheng (CATT) Hucheng (CATT) responds to Guanglei (Huawei) Hannu (Nokia) responds to comments and provides r02. Hucheng (CATT) comments, and proposes ways forward. Stefan (Ericsson) provides question Hucheng (CATT) replies to Stefan (Ericsson). Hucheng (CATT) provides r03. Jaewoo (LGE) provides r04. Hannu (Nokia) supports r04. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.12 | S2-2201597 | P-CR | Approval | 23.700-27: Solution for dynamic backhaul delay. | Nokia, Nokia Shanghai Bell | Rel-18 | Revision of S2-2201008r04. Approved | Approved | |
| 9.13 | - | - | - | Study on the support for 5WWC Phase 3 (FS_5WWC_Ph3) | - | - | Docs:=30 | - | |
| 9.13 | - | - | - | General (skeleton, scope) | - | - | Docs:=2 | - | |
| 9.13 | S2-2200102 | P-CR | Approval | 23.700-17: TR 23.700-17 Skeleton | Nokia, Nokia Shanghai Bell (rapporteur) | Rel-18 | 23.700-17 TR Skeleton. Approved | ==== 8.X, 9.X, 10.X Final Deadline ==== | Approved |
| 9.13 | S2-2200104 | P-CR | Approval | 23.700-17: FS_5WWC_Phx TR Scope | Nokia, Nokia Shanghai Bell (rapporteur) | Rel-18 | Approved | ==== 8.X, 9.X, 10.X Final Deadline ==== | Approved |
| 9.13 | - | - | - | Architecture Assumptions and requirements | - | - | Docs:=2 | - | |
| 9.13 | S2-2200747 | P-CR | Approval | 23.700-17: FS_5WWC_Ph2 Architectural Assumptions and Principles. | Huawei, HiSilicon | Rel-18 | r02 agreed. Revised to S2-2201780. | Laurent (Nokia): provides r01 (merging in 0103) Marco (Huawei) ok with provides r01 Laurent (Nokia): provides r02 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.13 | S2-2201780 | P-CR | Approval | 23.700-17: FS_5WWC_Ph2 Architectural Assumptions and Principles. | Huawei, HiSilicon, Nokia, Nokia Shanghai Bell | Rel-18 | Revision of S2-2200747r02. Approved | Approved | |
| 9.13 | - | - | - | Key Issues | - | - | Docs:=5 | - | |
| 9.13 | S2-2200105 | P-CR | Approval | 23.700-17: FS_5WWC_Phx TR KI related with WT2 | Nokia, Nokia Shanghai Bell (rapporteur) | Rel-18 | r07 agreed. Revised to S2-2201781. | Marco (Huawei) proposed R01 with merging KI description from 0858 and ask clairifcations Myungjune (LGE) comments on r01 Heng (China Telecom) comments Curt (Charter) comments... Marco (Huawei) comments... Laurent (Nokia): provides r02 Marco (Huawei): provides r03 Huan (vivo): comments and provides r04 Sriram (CableLabs): comments marco (Huawei): ok with r04 Curt (Charter): provides r05. Sriram(CableLabs) comments. Laurent (Nokia): provides r06 Dieter (Deutsche Telekom): provides comments. Dieter (Deutsche Telekom): provides r07. ==== 8.X, 9.X, 10.X Revisions Deadline ==== marco (Huawei) OK with r07 & r06. Laurent (Nokia): objects to R01; Dieter (Deutsche Telekom): objects to all versions but r07. ==== 8.X, 9.X, 10.X Final Deadline ==== Sriram (CableLabs) objects to all versions but r07. | Revised |
| 9.13 | S2-2201781 | P-CR | Approval | 23.700-17: FS_5WWC_Ph2 TR KI related with WT2. | Nokia, Nokia Shanghai Bell (rapporteur), Deutsche Telekom | Rel-18 | Revision of S2-2200105r07. Approved | Approved | |
| 9.13 | S2-2200106 | P-CR | Approval | 23.700-17: FS_5WWC_Phx TR KI related with WT3 | Nokia, Nokia Shanghai Bell (rapporteur) | Rel-18 | Approved | ==== 8.X, 9.X, 10.X Final Deadline ==== | Approved |
| 9.13 | S2-2200858 | P-CR | Approval | 23.700-17: KI and solution for remote UE accessing 5GC. | Huawei, HiSilicon | Rel-18 | r04 agreed. Revised to S2-2201782. | Laurent (Nokia): as rapporteur proposes to merge in the KI part of this Tdoc 0858 into 0105 and to keep only the solution part within Tdoc 0858 Marco (Huawei): agree with Laurent (Nokia) and proposed r01 Myungjune (LGE) questions whether this solution is in the scope of study Heng (China Telecom) agree with Myungjune (LGE) Curt (Charter) comments... Suresh Srinivasan (Intel) comments Laurent (Nokia): asks questions for clarification on the solution Marco (Huawei) answers to Laurent (Nokia) Marco (Huawei) answers to Suresh Srinivasan (Intel) Marco (Huawei) answers to Curt (Charter) Marco (Huawei) answers to Heng (China Telecom) Marco (Huawei) answers to Myungjune (LGE) Laurent (Nokia): Comments Sebastian (Qualcomm) comments Marco (Huawei) provide r02 Marco (Huawei) provide r03 and answer to Sebastian Laurent (Nokia): provides r04 ==== 8.X, 9.X, 10.X Revisions Deadline ==== marco (Huawei) OK with r04 Laurent (Nokia): objects to R00 ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.13 | S2-2201782 | P-CR | Approval | 23.700-17: KI and solution for remote UE accessing 5GC. | Huawei, HiSilicon | Rel-18 | Revision of S2-2200858r04. Approved | Approved | |
| 9.13 | - | - | - | Solutions | - | - | Docs:=20 | - | |
| 9.13 | S2-2200410 | P-CR | Approval | 23.700-17: FS_5WWC_Ph2 Solution related with WT#2. | China Telecom | Rel-18 | r04 agreed. Revised to S2-2201783. | Suresh Srinivasan (Intel) comments Marco (Huawei) ask questions and comments Laurent (Nokia): Comments Stefan (Ericsson) provides comments and questions Yubing (China Telecom) replies to Suresh Srinivasan (Intel), Marco (Huawei) and Laurent (Nokia) Yubing (China Telecom) replies to Stefan (Ericsson) Yubing (China Telecom) provides r01 Laurent (Nokia): please provide a r01, not a r1!! Yubing (China Telecom): provides r01 Sriram (CableLabs): comments Yubing (China Telecom): replies to Sriram (CableLabs) and provides r02 Sriram(CableLabs): replies to Yubing. Marco (Huawei): comments r02 Yubing (China Telecom): replies to Sriram (CableLabs) and Marco (Huawei) and provides r03. ==== 8.X, 9.X, 10.X Revisions Deadline ==== marco (Huawei) OK with r03 Laurent (Nokia): provides r04 Laurent (Nokia): asks R04 sent yesterday *before the deadline* and rejected by Altospam to be considered. Otherwise can only live with R03 + 2 added EN Yubing (China Telecom) is ok with r04, if acceptable marco (huawei): R04 is even better, if acceptable ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.13 | S2-2201783 | P-CR | Approval | 23.700-17: FS_5WWC_Ph2 Solution related with WT#2. | China Telecom | Rel-18 | Revision of S2-2200410r04. Approved | Approved | |
| 9.13 | S2-2200450 | P-CR | Approval | 23.700-17: New solution for providing differentiated service for non-3GPP devices behind a 5G RG. | Ericsson | Rel-18 | r04 agreed. Revised to S2-2201784. | Laurent (Nokia): as rapporteur: could author of 0450 and of § 6.X.1.3 of 0505 consider merging their solutions in one Tdoc Stefan (Ericsson) comments on differences between 0450 and § 6.X.1.3 of 0505 Suresh (Intel) Reply to comments on differences between 0450 and § 6.X.1.3 of 0505 Curt (Charter) comments ... Marco (Huawei) provides comments Suresh Srinivasan (Intel) Reply to Curt (Charter) comments ... Suresh Srinivasan (Intel) is OK to merge 0450 with § 6.X.1.3 of 0505 Myungjune (LGE) asks question Huan (vivo) asks question Suresh (Intel) provides 0450r1 (§ 6.X.1.3 of 0505 merged with 0450) Curt (Charter) comments... Sriram(CableLabs) comments... Stefan (Ericsson) replies to questions and provides r02 Stefan (Ericsson) replies to Huan, Myungjune, Marco, Suresh Srinivasan (Ericsson) replies to questions Suresh Srinivasan (Intel) replies to questions Suresh Srinivasan (Intel) Further Clarifies Curt's question on distinct PDU session Susan (Huawei) raises comments. Laurent (Nokia): Comments Stefan (Ericsson) replies to Susan, Laurent and provides r03 Suresh Srinivasan (Intel) provides 0450r04 Marco (Huawei) asks clarification Stefan (Ericsson) replies to Marco Marco (Huawei) replies to Stefan (Ericsson) ==== 8.X, 9.X, 10.X Revisions Deadline ==== marco (Huawei) OK with r04 ==== 8.X, 9.X, 10.X Final Deadline ==== Sriram(CableLabs) objects. | Revised |
| 9.13 | S2-2201784 | P-CR | Approval | 23.700-17: New solution for providing differentiated service for non-3GPP devices behind a 5G RG. | Ericsson, Intel | Rel-18 | Revision of S2-2200450r04. Approved | Approved | |
| 9.13 | S2-2200451 | P-CR | Approval | 23.700-17: New solution for providing differentiated service for UE connected behind a 5G RG. | Ericsson | Rel-18 | r06 agreed. Revised to S2-2201785, merging S2-2201012 and S2-2200725 | Laurent (Nokia): As a rapporteur suggests to merge 0451, 0725 and the corresponding subset (6.X.1.1 ) of 0505 into 0451 Stefan (Ericsson) provides r01 merging aspects from 0505 Huan (vivo) asks questions for clarifications Stefan (Ericsson) provides r02 based on Huan's comments Huan (vivo) asks a question for clarification and would like to cosign Susan (Huawei) raises questions. Laurent (Nokia): comments Stefan (Ericsson) replies to Huan Stefan (Ericsson) replies to Susan Stefan (Ericsson) provides r03 Stefan (Ericsson) provides r04 Suresh Srinivasan (Intel) agrees to co-sign 0451r04 Curt (Charter) provides r05 Stefan (Ericsson) is OK with r05 Susan (Huawei) replies to Stefan. Suresh Srinivasan (Intel) co-signs 0451 and provides r06 ==== 8.X, 9.X, 10.X Revisions Deadline ==== Susan (Huawei) replies to Stefan and ok with the proposal. ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.13 | S2-2201785 | P-CR | Approval | 23.700-17: New solution for providing differentiated service for UE connected behind a 5G RG. | Ericsson, Intel, Vivo | Rel-18 | Revision of S2-2200451r06, merging S2-2201012 and S2-2200725. Approved | Approved | |
| 9.13 | S2-2200505 | P-CR | Approval | 23.700-17: Solution for differentiated QoS for devices behind 5G-RG. | Intel | Rel-18 | r06 agreed. Revised to S2-2201786. | Laurent (Nokia): as rapporteur: could author of 0450 and of § 6.X.1.3 of 0505 consider merging their solutions in one Tdoc Laurent (Nokia): As a rapporteur suggests to merge 0451, 0725 and the corresponding subset (6.X.1.1 ) of 0505 into 0451 Sriram(CableLabs): we provide revision of S2-2200505r01 Stefan (Ericsson) comments Sriram(CableLabs) comments. Suresh (Intel) is Ok to merge 6.X.1.1 of 0505 to 0451 Huan (vivo) asks questions and comments. Curt (Charter) provides r02 Sriram(CableLabs) responds. Suresh Srinivasan (Intel) provides 0505r03 (6.X.1.2 of 0505 as a standalone solution) Stefan (Ericsson) provides comments Suresh Srinivasan (Intel) Reply to Stefan comments Curt (Charter) asks why the proposed EN is removed? Suresh Srinivasan (Intel) replies to 'why the proposed EN is removed?' Curt (Charter) replies to Suresh/Intel Laurent (Nokia): provides r04 Yishan (Huawei) shares concerns on the solution Suresh Srinivasan (Intel) replies to Yishan's (Huawei) concerns Suresh Srinivasan (Intel) replies to Laurent and provides r05 Suresh Srinivasan (Intel) provides r06 with some corrections ==== 8.X, 9.X, 10.X Revisions Deadline ==== Laurent (Nokia): objects to R00, R01, R02 (keep an unique solution) Marco (huawei): ok R06 and objects to r00, r01, r02, r03. Curt (Charter) proposes to postpone this tdoc Suresh Srinivasan (Intel) propose to handle this document on CC#4 with the addition of the following Editor's note ==== 8.X, 9.X, 10.X Final Deadline ==== Sriram(CableLabs) objects. | Revised |
| 9.13 | S2-2201786 | P-CR | Approval | 23.700-17: Solution for differentiated QoS for devices behind 5G-RG. | Intel | Rel-18 | Revision of S2-2200505r06. Approved | Approved | |
| 9.13 | S2-2200724 | P-CR | Approval | 23.700-17: FS_5WWC_Ph2 Solution for providing differentiated service for Non-3GPP devices connected behind a 5G-RG. | vivo | Rel-18 | r03 agreed. Revised to S2-2201787. | Marco (Huawei) provides comments Suresh Srinivasan (Intel) comments Myungjune (LGE) asks question Huan (vivo) provides feedback Stefan (Ericsson) provides questions Huan (vivo) provides r01 Stefan (Ericsson) provides comments Huan (vivo) provides feedback and upload r02 Laurent (Nokia): Comments Sriram( CableLabs) provides comments. Suresh Srinivasan (Intel) provides 0450r04 Marco (Huawei) comment (I apologize for wrong tag) Huan (vivo) provides r03 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== Sriram(CableLabs) objects to all revisions. Huan (vivo) asks Sriram for clarification Sriram (CableLabs) replies. | Revised |
| 9.13 | S2-2201787 | P-CR | Approval | 23.700-17: FS_5WWC_Ph2 Solution for providing differentiated service for Non-3GPP devices connected behind a 5G-RG. | Vivo | Rel-18 | Revision of S2-2200724r03. Approved | Approved | |
| 9.13 | S2-2200725 | P-CR | Approval | 23.700-17: FS_5WWC_Ph2 Solution for providing differentiated service for UE connected behind a 5G-RG. | vivo | Rel-18 | Merged into S2-2201785 | Laurent (Nokia): As a rapporteur suggests to merge 0451, 0725 and the corresponding subset (6.X.1.1 ) of 0505 into 0451 Laurent (Nokia): Comments: li huan, is it ok to merge in 0451? Huan (vivo) confirms merge 00725 in 0451 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.13 | S2-2200796 | P-CR | Approval | 23.700-17: Solution on WT#3 based on TNGF relocation. | Lenovo, Motorola Mobility | Rel-18 | r03 agreed. Revised to S2-2201788. | Ashok (Samsung) needs clarification Apostolis (Lenovo) responds to Ashok's (Samsung) questions. marco (Huawei) asks clarifications Apostolis (Lenovo) responds to Marco's (Huawei) questions. Heng(China Telecom) asks questions. Marco (Huawei) comment to Apostolis (Lenovo) Apostolis (Lenovo) responds to Marco's (Huawei) comments. Apostolis (Lenovo) responds to Heng's (China Telecom) comment. Apostolis (Lenovo) provides r01. Marco (huawei) r01 requires an EN that whether and how the NSSF has knowledge of TAI supported by TNGF for selecting AMF is FFS. Apostolis (Lenovo) provides r02 including the EN requested by Marco (huawei). Laurent (Nokia): provides r03 Apostolis (Lenovo) is fine with r03. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.13 | S2-2201788 | P-CR | Approval | 23.700-17: Solution on WT#3 based on TNGF relocation. | Lenovo, Motorola Mobility | Rel-18 | Revision of S2-2200796r03. Approved | Approved | |
| 9.13 | S2-2200802 | P-CR | Approval | 23.700-17: Solution on WT#3 based on N3IWF relocation. | Lenovo, Motorola Mobility | Rel-18 | r04 agreed. Revised to S2-2201789. | Ashok (Samsung) needs clarification Apostolis (Lenovo) responds to Ashok's (Samsung) questions. Marco (Huawei) asks questions. Apostolis (Lenovo) responds to Marco's (Huawei) questions. Heng(China Telecom) asks questions. Apostolis (Lenovo) responds to Heng's (China Telecom) questions. Stefan (Ericsson) provides comments Laurent (Nokia): Comments Apostolis (Lenovo) provides r01 Marco (huawei) ask EN that whether and how the NSSF has knowledge of TAI supported by N3IWF for selecting AMF is FFS. Apostolis (Lenovo) provides r02 including the EN requested by Marco (huawei). Laurent (Nokia): provides r03 Apostolis (Lenovo) is fine with r03. Florin (Broadcom): provides small editorial update in r04 on top of r03 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.13 | S2-2201789 | P-CR | Approval | 23.700-17: Solution on WT#3 based on N3IWF relocation. | Lenovo, Motorola Mobility | Rel-18 | Revision of S2-2200802r04. Approved | Approved | |
| 9.13 | S2-2201082 | P-CR | Approval | 23.700-17: Solution for WT3: slice related TNGF selection. | Nokia, Nokia Shanghai Bell | Rel-18 | r01 agreed. Revised to S2-2201790. | Marco (Huawei) asks questions and comments Laurent (Nokia): provides r01 Marco (huawei): further comments r01 Laurent (Nokia): answers ==== 8.X, 9.X, 10.X Revisions Deadline ==== Apostolis (Lenovo) is fine with r01 and comments. ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.13 | S2-2201790 | P-CR | Approval | 23.700-17: Solution for WT3: slice related TNGF selection. | Nokia, Nokia Shanghai Bell | Rel-18 | Revision of S2-2201082r01. Approved | Approved | |
| 9.13 | S2-2201213 | P-CR | Approval | 23.700-17: Differentiated QoS for non-3GPP devices behind 5G-RG. | Qualcomm Incorporated | Rel-18 | r06 agreed. Revised to S2-2201791. | Suresh Srinivasan (Intel) comments Myungjune (LGE) asks question Marco (Huawei) asks questions and comments Huan (vivo) asks questions for clarification Sebastian (Qualcomm) replies to comments from vivo, Huawei, LGE and Intel and provides r01 Susan (Huawei) raises comment. Laurent (Nokia): Comments Sebastian (Qualcomm) replies to Susan Sebastian (Qualcomm) replies and provides r03 (please ignore r02) Marco (Huawei) provides r04 Sebastian (Qualcomm) replies to Marco Marco (huawei) replies to Sebastian Susan (Huawei) replies to Sebastian (Qualcomm) and provides r05. Marco (Huawei) replies to Sebastian (Qualcomm) Sebastian (Qualcomm) provides r06 Sriram(CableLabs) seeks clarification. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Sebastian (Qualcomm) replies to Sriram Laurent (Nokia): objects to any version between R00 and R03 both included. R06 is the best ==== 8.X, 9.X, 10.X Final Deadline ==== Sriram(CableLabs) objects | Revised |
| 9.13 | S2-2201791 | P-CR | Approval | 23.700-17: Differentiated QoS for non-3GPP devices behind 5G-RG. | Qualcomm Incorporated | Rel-18 | Revision of S2-2201213r06. Approved | Approved | |
| 9.13 | S2-2201216 | P-CR | Approval | 23.700-17: N3IWF selection taking supported slices into account. | Qualcomm Incorporated | Rel-18 | Noted | Marco (Huawei) express doubts and ask questions Ashok (Samsung) shares same view as Marco (Huawei) Sebastian (Qualcomm) replies to Marco Sebastian (Qualcomm) replies to Ashok Susan (Huawei) provides comments. Sebastian (Qualcomm) replies to Susan Apostolis (Lenovo) asks more questions. Laurent (Nokia): Comments Sebastian (Qualcomm) replies to Apostolis Sebastian (Qualcomm) replies to Laurent and provides r02 Ashok (Samsung) ask for clarification from Sebastian (Qualcomm) Susan (Huawei) replies to Sebastian (Qualcomm). Marco (Huawei) comments Sebastian (Qualcomm) replies to Susan and provides r03 Laurent (Nokia): provides r04 Sebastian (Qualcomm) provides r05 ==== 8.X, 9.X, 10.X Revisions Deadline ==== Susan (Huawei) raises further question to Sebastian (Qualcomm). Laurent (Nokia): objects to Any version except R04. Can ONLY live with R04; Patrice (Huawei) objects to the proposal as it is conflicting severely with the existing NSSRG feature and impacts 3GPP access functionality. Major issues need to be addressed before it can be accepted. ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 9.13 | - | - | - | Documents exceeding quota | - | - | Docs:=1 | - | |
| 9.13 | S2-2200103 | P-CR | Approval | 23.700-17: FS_5WWC_Phx TR architectural assumptions | Nokia, Nokia Shanghai Bell (rapporteur) | Rel-18 | Not Handled | ==== 8.X, 9.X, 10.X Final Deadline ==== | - |
| 9.14 | - | - | - | Study on Network Slicing Phase 3 (FS_eNS_Ph3) | - | - | Docs:=31 | - | |
| 9.14 | - | - | - | General | - | - | Docs:=2 | - | |
| 9.14 | S2-2200563 | P-CR | Approval | 23.700-41: Skeleton of FS_eNS_Ph3 TR 23.700-41 | LG Electronics, ZTE | Rel-18 | 23.700-41 TR Skeleton. Approved | ==== 8.X, 9.X, 10.X Final Deadline ==== | Approved |
| 9.14 | S2-2201033 | P-CR | Approval | 23.700-41: FS_eNS_Ph3: Scope. | ZTE, LG Electronics | Rel-18 | Approved | ==== 8.X, 9.X, 10.X Final Deadline ==== | Approved |
| 9.14 | - | - | - | Architecture Assumption | - | - | Docs:=2 | - | |
| 9.14 | S2-2201034 | P-CR | Approval | 23.700-41: FS_eNS_Ph3: Architecture assumption. | ZTE, LG Electronics | Rel-18 | r01 agreed. Revised to S2-2201348. | Alessio(Nokia) provides r01 ==== 8.X, 9.X, 10.X Revisions Deadline ==== Jinguo(ZTE) is ok with r01 ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.14 | S2-2201348 | P-CR | Approval | 23.700-41: FS_eNS_Ph3: Architecture assumption. | ZTE, LG Electronics | Rel-18 | Revision of S2-2201034r01. Approved | Approved | |
| 9.14 | - | - | - | Key issue #1 | - | - | Docs:=6 | - | |
| 9.14 | S2-2201035 | P-CR | Approval | 23.700-41: New key issue: KI for objective #1 - Support of network slice service continuity. | ZTE, LG Electronics, Nokia, Nokia Shanghai Bell, NTT DOCOMO, NEC. | Rel-18 | CC#5: r10 + changes agreed. Revised to S2-2201857. | Jinsook (DISH) Provided comments Haiyang (Huawei) comments ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.14 | S2-2201857 | P-CR | Approval | 23.700-41: New key issue: KI for objective #1 - Support of network slice service continuity. | ZTE, LG Electronics, Nokia, Nokia Shanghai Bell, NTT DOCOMO, NEC, MITRE | Rel-18 | Revision of S2-2201035r10 + changes. Approved | Approved | |
| 9.14 | S2-2200717 | P-CR | Approval | 23.700-41: New KI: Abrupt PDU Session release due to a removal of network slice . | NTT DOCOMO, Samsung, OPPO | Rel-18 | r04 agreed. Revised to S2-2201349 (withdrawn). CC#5: Merged into S2-2201352 | George Foti (Ericsson) Ericsson provides r01 alessio(Nokia) proposes to merge in 1035 George (Ericsson) including r01. The link was missing before. I don't know if this is n=so much related to 1035. But I would let the authors decide. DongEun (Samsung) provides r02 Srisakul (NTT DOCOMO) comments. Ok for both r01 and r02. Prefer to keep it separate rather than to merge into 1045. Patrice (Huawei) comments. George (Ericsson) requests clarification. Srisakul (NTT DOCOMO) provides r04. Alessio(Nokia) comments on the rationale provided by Srisakul (NTT DOCOMO) alessio(Nokia) let's note all revisions of this and work on updating 1035 if necessary. Jinguo(ZTE) suggest to keep it separated key issue alessio Nokia) suggest we merge it objective 5 (1069) KI as now it seems this is something people want to address as part of slice termination (which also applies to temporary slices) Patrice (Huawei) comments, is OK with r04. George (Ericsson) asks question Srisakul (NTT DOCOMO) prefers to keep this tdoc open and not merged, if 1035(r05 or r09) and 1069 (r05) cannot be agreed. George (Ericsson) provides response George (Ericsson) provides comments. I am OK with this being separate. But I responded on ES and MC in separate email. Hope this clarifies the point. ==== 8.X, 9.X, 10.X Revisions Deadline ==== alessio(Nokia) is expecting this to be addressed by solutions in WT#5 KI so it is naturally belonging there. I thought we had agreed text you were ok wit. so this should be merged in 1069 DongEun (Samsung) suggest to go with r04 TAO(VC) let's further check r04 which many prefers to go with Alessio(Nokia) requests that we consider this part of 1069r05 as it seems there is consensus on it. is Docomo ok? Patrice (Huawei) confirms that r04 is OK. Patrice (Huawei) further replies to George (Ericsson). Srisakul (NTT DOCOMO) r04 is OK. But also see possibility to merge this into both 1069r05 or 1035 (either r05, r09 or r10). If both 1069r05 and 1035 (r05, r09 or r10) cannot be agreed in this meeting, we suggest to go ahead with r04. Note that 717 has two aspects, one is about service continuity and another is to avoid abrupt service termination due to the network slice termination. ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.14 | S2-2201349 | P-CR | Approval | 23.700-41: New KI: Abrupt PDU Session release due to a removal of network slice | NTT DOCOMO, Samsung, OPPO | Rel-18 | Revision of S2-2200717r04. Approved. WITHDRAWN | Withdrawn | |
| 9.14 | S2-2200257 | P-CR | Approval | 23.700-41: New key issue on the service continuity in case of Network Slice instance resource shortage. | Huawei, HiSilicon | Rel-18 | Merged into S2-2201733 | Haiyang (Huawei) prefers to keep them separately. Jinguo(ZTE) points that the two new bullets are solution specific. Haiyang (Huawei) responds. Haiyang (Huawei) further responds. Jinguo(ZTE) comments. Jinguo(ZTE) response to Haiyang (Huawei) Haiyang (Huawei) comments to Jinguo(ZTE). Jinguo(ZTE) suggest to merge into 1035 Dongeun (Samsung) also suggest to merge into 1035 Haiyang (Huawei) indicates that we do not agree with some other aspects in 1035. Besides, slice instance is not in 1035 any longer. ==== 8.X, 9.X, 10.X Revisions Deadline ==== alessio(Nokia) also believes it is sufficient to go wit 1035. Companies can provide NSI considerations in their solutions in KI 1035 ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.14 | S2-2200258 | DISCUSSION | Approval | Discussion on the service continuity for WT#1. | Huawei, HiSilicon | Rel-18 | Noted | ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 9.14 | - | - | - | Key issue #2 | - | - | Docs:=5 | - | |
| 9.14 | S2-2200190 | P-CR | Approval | 23.700-41: Key issue for Handling Rejected S-NSSAIs in some TAs of RA . | Ericsson, Samsung, OPPO | Rel-18 | Noted | Jinsook (DISH) Provided comments Peter Hedman (Ericsson) provides reply and r01 Mike (InterDigital) provides r02 Jinsook (DISH) comments and provides r03, I added DISH as a supporting company and deleted Note 2. Alessio(Nokia) objects to all revisions except rev4 that nokia is providing as the wording by Ericsson is not in line with the study objective 'Study whether and how to initiate a registration for a rejected S-NSSAI that was rejected in a first TA of the RA but may be available in another TA of the RA' Peter Hedman (Ericsson) provides reply and r04 is not acceptable alessio(Nokia) comments that peter has not understood the objective of the WI Alessio(Nokia) proposes to merge in 992 Haiyang (Huawei) comments, suggests to reuse the wording of WT Peter Hedman (Ericsson) provides r05 Kundan(NEC) thinks that KI wording of r04 is not very clear and seeking clarifications on wording. Kundan (NEC) is fine with r05. Stefano (Qualcomm) asks status of this paper wrt 1067: merged into this one, two distinct KIs both going to the TR, or only one selected and which one? Alessio(Nokia) replies to Kundan and Stefano. Kundan: 1067 just compiles with the study objective. what you (and ericsson) propose is not an objective of the study. Stefano this is to me the only KI we can agree to (as nokia) the other one is not part of the study objective (the Ericsson paper)Stefano (Qualcomm) asks status of this paper wrt 1067: merged into this one, two distinct KIs both going to the TR, or only one selected and which one? alessio(Nokia) objects to 190 and all its revisions. Alessio(Nokia) objects to r05 as it departs from support of allowed NSSAI in all TAs of the RA. Jinguo(ZTE) suggests to use 190 as basis, but agree with Alessio that the current description is solution space and needs to be improved. alessio(Nokia) comments that NEC can provide any solution they wish but not for a KI worded like this in 190 that departs from assuming the allowed NSSAI works in RA. 190 is not acceptable. alessio(Nokia) corrects a typo in r04 identified by Kundan(NEC) and provides r06 Haiyang (Huawei) also suggests to go with 1067r01 Peter Hedman (Ericsson) provides r07 Kundan (NEC) provides r08 fixing minor editorial errors. NEC is fine with r07 or r08. alessio objects to r07. alessio(Nokia) objects to r08 also as it is outside the WT objective to do what described in here. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Peter Hedman (Ericsson) suggests to go with r08 or do a SoH Alessio(Nokia) does not accept a SoH on this as procedurally the KIs shall be aligned to the objectives and the objective is clear... we cannot change the Study scope and objectives in the KIs. Objects to 190 and all revisions (except those we said we can live with) on a sustained basis and will bring this us to SA plenary if a SI objective is not respected and Ericsson wants to do just what they wish . Jinguo(ZTE) comments on r07 and r08 Ashok (Samsung) replies to Jinguo(ZTE) and ask clarification from Alessio (Nokia) Ashok (Samsung) need clarification from Peter (Ericsson) Alessipon Understand that 'Jinguo(ZTE) comments on r07 and r08' meant 'Jinguo(ZTE) comments on r06 and r08' and so rellies and confirm objection to 190 and requests to use 1067 instead. Krisztian (Apple) comments: why don't we use the exact same wording as in the SID: Study whether and how to initiate a registration for a rejected S-NSSAI that was rejected in a first TA of the RA but may be available in another TA of the RA. Jinguo(ZTE) further comments Peter Hedman (Ericsson) provides reply to Apple Peter Hedman (Ericsson) provides comments Peter Hedman (Ericsson) supports going with r08 (or e.g. r07, or r05, r03) objects to r06, r04 alessio also agree tha using the SID objective is a MUST.: why don't we use the exact same wording as in the SID: Study whether and how to initiate a registration for a rejected S-NSSAI that was rejected in a first TA of the RA but may be available in another TA of the RA. objects to 190 if Ericsson wants to extend the work to areas not agreed at SA approval of SID. alessio(Nokia) objects to r08 and all the revisions that do not exactly stick to the approved WID. (i.e. r07, r05, r03). requests 1067 is used as basis as already agreed during the call we had before the meeting and also based on the fact that this is sticking to the WID objective text. ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 9.14 | S2-2200260 | P-CR | Approval | 23.700-41: New key issue: Re-initiate registration for rejected S-NSSAI. | Huawei, HiSilicon | Rel-18 | Merged into S2-2201352 | Peter (Ericsson) suggests to use 00190 as basis, see r01 for some of the merged in content Alessio(nokia) is ok with the text on the KI which is very similar to what is in 1067 and so we propose to merge in 1067. Haiyang (Huawei) is OK to merge in 1067 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.14 | S2-2200985 | P-CR | Approval | 23.700-41: New key issue for objective #5 - Support for network slices with partial TA coverage and limited lifetime. | NEC | Rel-18 | Merged into S2-2201622 | Jinguo(ZTE) suggests to merge this into 1069 Alessio(Nokia) supports ZTE(Jinguo) Iskren (NEC) - please mark this pCR as merged to S2-2201069 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.14 | S2-2201067 | P-CR | Approval | 23.700-41: New key issue: KI for objective #2 - Improved support of RAs including TAs supporting Rejected S-NSSAIs . | Nokia, Nokia Shanghai Bell. | Rel-18 | Noted | Peter (Ericsson) suggests to use 00190 as basis, see r01 for some of the merged in content alessio(nokia) rather contends that 00190 is not aligned with the objectives of the study which is '2. Study whether and how to initiate a registration for a rejected S-NSSAI that was rejected in a first TA of the RA but may be available in another TA of the RA.' Haiyang (Huawei) comments Stefano (Qualcomm) asks status of this paper wrt 0190: merged, two distinct KIs both going to the TR, or only one selected and which one? alessio(Nokia) can only agree with the formulation like in the study objective like in 1067. Jinguo(ZTE) suggests to merge this into 190 Haiyang (Huawei) provides r01 alessio(Nokia) we are ok with r01. Kundan(NEC) proposes to use 0190 as baseline. Peter Hedman (Ericsson) provides comments and suggest again to use 0190 ==== 8.X, 9.X, 10.X Revisions Deadline ==== Peter Hedman (Ericsson) objexts to r00, r01 Alessio(Nia) asks the motivation of objection and anyhow to take to CC#4 Kundan (NEC) does not accept r00 and r01 and proposes to use 0190 as baseline as 1067 is very restrictive and does not allow improvements in AMF behavior to handle this case. alessio(Nokia) we repeat our view that 1067 is just repeating the WT text. if you think the WT text is restrictive start from updating the SID and getting the update agreed. ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 9.14 | S2-2201151 | P-CR | Approval | 23.700-41: WT#2: New Key Issue on Non-homogeneous Support of an S-NSSAI in a Registration Area. | InterDigital Inc. | Rel-18 | Merge into revision of S2-2200190 (Noted). Noted | Peter (Ericsson) suggests to use 00190 as basis, see r01 for some of the merged in content Mike (InterDigital) is ok with marking this document as merged into 00190 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 9.14 | - | - | - | Key issue #3 | - | - | Docs:=6 | - | |
| 9.14 | S2-2200189 | P-CR | Approval | 23.700-41: Key issue for enhancing network slice information while roaming. | Ericsson | Rel-18 | Merged into S2-2201350 | Myungjune proposes to merge this CR into S2-220564 George (Ericsson) provides comments. We are OK with that. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.14 | S2-2200259 | P-CR | Approval | 23.700-41: New KI for WT#3 on VPLMN Selection. | Huawei, HiSilicon | Rel-18 | Merged into S2-2201350 | George Foti (Ericsson) To be noted. This is merged in 564r01 alessio(Nokia) supports George. Haiyang (Huawei) is OK to merge this paper into 564. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.14 | S2-2200564 | P-CR | Approval | 23.700-41: New key issue: KI for objective #3 - providing VPLMN network slice info to roaming UE. | LG Electronics, Nokia, Nokia shanghai Bell, NEC, ZTE, Qualcomm Incorporated, Apple, Samsung, OPPO, Lenovo, Motorola Mobility | Rel-18 | r06 agreed. Revised to S2-2201350, merging S2-2200933, S2-2200189, S2-2200259, S2-2201149 and S2-2201126 | George Foti (Ericsson) provides r01 Genadi (Lenovo) looks for clarifications regarding non-3GPP access and proposes to merge S2-2201126 into S2-2200564. George (Ericsson) provides comments Myungjune (LGE) responds to Genadi (Lenovo) Genadi (Lenovo) provides r05 to add clarification that this issue is applicable to 3GPP access type. Myungjune (LGE) is ok with r05 Haiyang (Huawei) provides r06 Kundan (NEC) provides r07 clarifying what does mean by network slice not offered. George (Ericsson) Ericsson Ok with r06 George (Ericsson) provides comments. We don't need this additional statement. R06 is fine ==== 8.X, 9.X, 10.X Revisions Deadline ==== alessio(Nokia) objects to r07 as the slice support only in in the PLMN selection. its availability in a particular area of the network is orthogonal issue. Alessio(Nokia) Ok with r06 Kundan (NEC) responds to Myungjune (LGE) Myungjune (LGE) responds to Kundan (NEC) Myungjune (LGE) suggests to remove 'supported but not allowed' from r07. Krisztian (Apple) suggests to move forward with r06. 'not offered' is a synonym of 'not supported'. Kundan (NEC) is fine with removing 'supported but not allowed' from r07. Myungjune (LGE) responds to Krisztian (Apple) and clarifies key issue scope Alessio(Nokia) we are ok with r06 or r07 with removal of the text as proposed by Myungjune (LGE) ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.14 | S2-2201350 | P-CR | Approval | 23.700-41: New key issue: KI for objective #3 - providing VPLMN network slice info to roaming UE. | LG Electronics, Nokia, Nokia shanghai Bell, NEC, ZTE, Qualcomm Incorporated, Apple, Samsung, OPPO, Lenovo, Motorola Mobility, Ericsson, InterDigital Inc., MITRE, Huawei, HiSilicon | Rel-18 | Revision of S2-2200564r06, merging S2-2200933, S2-2200189, S2-2200259, S2-2201149 and S2-2201126. Approved | Approved | |
| 9.14 | S2-2201126 | P-CR | Approval | 23.700-41: New KI for WT#3 - Providing the UE with information for VPLMN selection when using non-3GPP access. | Lenovo, Motorola Mobility | Rel-18 | Merged into S2-2201350 | George Foti (Ericsson) proposes to note this pCR. Non-3GPP access is not specified in SA1 requirements. But given that this is already covered in FS_5WWC_Ph2 states for WT #3, then it seems appropriate that it should be studied there. Genadi (Lenovo) replies to George (Ericsson). George (Ericsson) provides comments alessio(Nokia) indeed prefers the KI remains in WWC2 ... we can explore synergies as both studies progress (and hopefully intra and intercompany coordination will help). Genadi (Lenovo) proposes to merge this paper in S2-2200564 r05. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.14 | S2-2201149 | P-CR | Approval | 23.700-41: WT#3: New Key Issue on enabling roaming UEs to register to available network slices in the surrounding area. | InterDigital Inc. | Rel-18 | Merged into S2-2201350 | George Foti (Ericsson) proposes to note the pCR. It is merged in 564rev01 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.14 | - | - | - | Key issue #4 | - | - | Docs:=5 | - | |
| 9.14 | S2-2200191 | P-CR | Approval | 23.700-41: Key issue for Enhanced Network control of Slice Usage. | Ericsson | Rel-18 | Merged into S2-2201351 (withdrawn). CC#5: Postponed | Alessio(Nokia) proposes to merge in 992 George (Ericsson) Ericsson Ok ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Postponed |
| 9.14 | S2-2200887 | P-CR | Approval | 23.700-41: New Key issue for WT#4: Network controlled behavior of network slice usage . | Huawei, HiSilicon | Rel-18 | Noted | George Foti (Ericsson) This can be noted as it is merged into 992r01 Alessio(Nokia) supports George Foti (Ericsson) Fenqin (Huawei) ask this paper to be separated from paper 0992 ==== 8.X, 9.X, 10.X Revisions Deadline ==== Fenqin (Huawei) ask this paper to be separated. Tao(VC) let's check can we agree r00 or not. Alessi(Nokia) cannot understand the rationale of this paper so we request to note it as it seems that this defines a UE behavior control that is not at all using the UE . we request to note this. Fenqin (Huawei) provides a response Alessio replies Fenqin (Huawei) suggest that two direction can be considered in parallel and go forward with R00. Alessio(Nokia) objects and proposes to use 992 as all classes of solutions will be allowed to be documented under the KI. we do not create separate KI's to allow separate types of solutions and ensure a type of solution is adopted. ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 9.14 | S2-2200992 | P-CR | Approval | 23.700-41: New key issue: KI for objective #4 -Improved Network control of the UE behaviour control. | Nokia, Nokia Shanghai Bell. | Rel-18 | r06 agreed. Revised to S2-2201351, merging S2-2200984 and S2-2200191. CC#5: Postponed | George Foti (Ericsson) provides r01 Fenqin (Huawei) provides r02 Nokia is OK with r01 alessio(Nokia) cannot accept r02 Ashok (Samsung) need clarification alessio(nokia) provides r04 addressing Samsung's comment and adding Samsung as supporting company. George (Ericsson) provides r05. Just adding Ericsson as co-signer. Fenqin (Huawei) comments. Fenqin (Huawei) provides r06 George (Ericsson) Not OK with r06 and r02. U are basically creating a solution in the KI with these 2 new revisions. Iskren (NEC) ask to co-sign. Krisztian (Apple) shares the concern raised by George (Ericsson) and objects to r06 and r02. alessio(Nokia) cannot accept revision 06 Fenqin (Huawei) comment and provide r07 alessio(Nokia) believes that r04 is the way to proceed alessio (nokia) cannot live with r07 Fenqin (Huawei) comment and provide r08 George (Ericsson) provides comment. Please explain what do U mean by accommodate. This is vague. Alessio(Nokia) comments that controlling the UE behavior of pre-rel-18 UEs which cannot be controlled hence the KI seems odd... so we do not see this as a text in scope of this KI (so we do not think r08 can be accepted) Fenqin (Huawei) provides a response. George (Ericsson) provides comments. The majority of Ur updates are solution focused. These are KI. U can contribute whatever U want. Don't provide the road map for a solution in the KI. George (Ericsson) provides comments. This issue will be addressed any way by some solutions or may be by none. We may not solve it either. Putting it in the KI implies that we wont have acceptable solutions if we cant handle legacy UEs in an acceptable way, whatever that means. It is not reasonable to even allude to any outcome as it may be not acceptable if this issue cant be addressed in satisfactory manner. Let the solutions drive the outcome. ==== 8.X, 9.X, 10.X Revisions Deadline ==== alessio(Nokia) ok with r05. we should use this as basis for approval. Alessio (Nokia) replies to Fenqin that document in 1034 says that if you find a solution that can use legacy methods to provide the KI solution this is evaluated. So really I see no issue if you want to support also legacy UEs. but this is true for all the features. No need to indicate it here. proposes r05 is ok as basis. it is also true that we do not want to force all solutions to show how legacy is supported. George (Ericsson) provides comments. Ericson OK only with r02 or r06 Fenqin (Huawei) Huawei OK only with r06, r07, r08 Tao(VC) check whether any revision can be agreed. alessio(Nokia) is ok with R08 with the understanding that pre-18 UE support is not a requirement for a solution to be valid. this shall be minuted. Fenqin (Huawei) ask to postpone this paper to give some more time on checking how to merge the KI proposal if the intention is merge the proposal. Alessio(Nokia) asks whether Fenqin can live with r08 which he himself has provided. Alessio(Nokia) is ready to approve r08 by Huawei. I hope Huawei is ok with their own revisions. George (Ericsson) Ericsson supports only r06. alessio(nokia) fine by me... seems r06 works also for fenqin. is this a compromise then? Fenqin (Huawei) accept r06 as way forward ==== 8.X, 9.X, 10.X Final Deadline ==== | Postponed |
| 9.14 | S2-2201351 | P-CR | Approval | 23.700-41: New key issue: KI for objective #4 -Improved Network control of the UE behaviour control. | Nokia, Nokia Shanghai Bell. | Rel-18 | Revision of S2-2200992r06, merging S2-2200984, merging S2-2200984 and S2-2200191. CC#5: WITHDRAWN | Withdrawn | |
| 9.14 | S2-2200999 | P-CR | Approval | 23.700-41: New key issue: KI for objective #4 - Requested Slice controlled by network. | Samsung | Rel-18 | Merged into S2-2201554 | George Foti (Ericsson) This can be noted as it is merged into 992r01. George Foti (Ericsson) provides r01 Ashok (Samsung) need clarification George (Ericsson) provides response I would let Alessio respond. Alessio(Nokia) is ok with r01 alessio(Nokia) proposes to note this paper and move the discussion to 992 paper that should be basis for this KI. Ashok (Samsung) agrees to merge this paper to 0992 but request alessio(Nokia) to respond the question ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.14 | - | - | - | Key issue #5 | - | - | Docs:=2 | - | |
| 9.14 | S2-2201069 | P-CR | Approval | 23.700-41: New key issue: KI for objective #5 - Network Slice Area of Service not mapping to existing TAs boundaries, and Temporary network slices. | Nokia, Nokia Shanghai Bell. | Rel-18 | r05 agreed. Revised to S2-2201352, merging S2-2200260 and S2-2200717 | Ashok (Samsung) comments Iskren (NEC) asks to co-sign Patrice (Huawei) provides his changes in r03 on top of Ericsson's r02. Patrice (Huawei) provides r02. Peter Hedman (Ericsson) provides r02 alessio(Nokia) is ok with r01 Srisakul (NTT DOCOMO) supports r03 provided by Patrice (Huawei). alessio(Nokia) is ok with r03 Srisakul (NTT DOCOMO) asks Alessio for clarification. alessio(Nokia) clarifies he meant to say ok with r02 (not r03) but also proposes r04 to add the topic of the KI by docomo if this is acceptable. Srisakul (NTT DOCOMO) comments. Provide r05 and indicate . Alessio(Nokia) can live with r05 (if other can) but still prefer r04 as we do not need to explain WHY the KI is done. therere may well be other reasons. so we take r05 as an example ... Srisakul (NTT DOCOMO) prefer r05. Peter Hedman (Ericsson) provides question ==== 8.X, 9.X, 10.X Revisions Deadline ==== Peter Hedman (Ericsson) ok with r05 but KI needs more work at the next meeting Patrice (Huawei) is OK with r03, r04, r05. ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.14 | S2-2201352 | P-CR | Approval | 23.700-41: New key issue: KI for objective #5 - Network Slice Area of Service not mapping to existing TAs boundaries, and Temporary network slices. | Nokia, Nokia Shanghai Bell, NEC, Ericsson, Huawei, NTT DOCOMO, Samsung, Deutsche Telekom. | Rel-18 | Revision of S2-2201069r05, merging S2-2200260 and S2-2200717. Approved | Approved | |
| 9.14 | - | - | - | Key issue #6 | - | - | Docs:=3 | - | |
| 9.14 | S2-2200377 | P-CR | Approval | 23.700-41: New Key Issue: NSAC enhancement to support multiple NSACFs shared maximum allowed number of UEs or PDU sessions. | China Mobile | Rel-18 | Merged into S2-2201766 | George Foti (Ericsson) provides comments Dan (China Mobile) provides reply George (Ericsson) provides response Dan (China Mobile) OK to merge this paper to S2-2200886 Alessio(Nokia) suggests postponing this KI discussion to next meeting after we see the outcome of rel-17 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.14 | S2-2200886 | P-CR | Approval | 23.700-41: New Key issue for WTI#7: support of NSAC involved multi NSACF. | Huawei, HiSilicon | Rel-18 | r07 agreed. Revised to S2-2201353, merging S2-2200872 | George Foti (Ericsson) provides comments Fenqin (Huawei) provides feedback George (Ericsson) provides response. 'Support of Multi Service areas' is a more generic and neutral title. Fenqin (Huawei) provides r01 George (Ericsson) provides r02. Simplified revision. Jinguo(ZTE) comments Fenqin (Huawei) provides r03 George (Ericsson) Not OK with r03. Additional comments below Fenqin (Huawei) comments George (Ericsson) provides comments Fenqin (Huawei) provides r04 George (Ericsson) provides r05. Minor editorial updates. Alessio(Nokia) suggests postponing this KI discussion to next meeting after we see the outcome of rel-17 Fenqin (Huawei) ask question for clarification Fenqin (Huawei) provides r06 Dongeun (Samsung) adds Samsung as a cosigner in r07 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.14 | S2-2201353 | P-CR | Approval | 23.700-41: New Key issue for WTI#7: support of NSAC involved multi NSACF. | Huawei, HiSilicon, Ericsson, Samsung | Rel-18 | Revision of S2-2200886r07, merging S2-2200872. Approved | Approved | |
| 9.15 | - | - | - | Study on 5G AM Policy (FS_AMP) | - | - | Docs:=7 | - | |
| 9.15 | S2-2200161 | P-CR | Approval | 23.700-89: FS_AMP TR Skeleton. | China Telecom (rapporteur) | Rel-18 | 23.700-89 TR Skeleton. Approved | ==== 8.X, 9.X, 10.X Final Deadline ==== | Approved |
| 9.15 | S2-2200162 | P-CR | Approval | 23.700-89: FS_AMP TR23.700-89 Scope. | China Telecom (rapporteur) | Rel-18 | Approved | ==== 8.X, 9.X, 10.X Final Deadline ==== | Approved |
| 9.15 | S2-2200163 | P-CR | Approval | 23.700-89: FS_AMP TR23700-89 architectural assumptions. | China Telecom (rapporteur) | Rel-18 | Approved | ==== 8.X, 9.X, 10.X Final Deadline ==== | Approved |
| 9.15 | S2-2200164 | P-CR | Approval | 23.700-89: FS_AMP TR23700-89 KI related with WT1. | China Telecom (rapporteur) | Rel-18 | Approved | Belen (Ericsson) ask a question for clarification Zhuoyi (China Telecom) replies to Ericsson. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Approved |
| 9.15 | S2-2200165 | P-CR | Approval | 23.700-89: New solution for FS_AMP WT#1. | China Telecom | Rel-18 | r03 agreed. Revised to S2-2201598. | Juan Zhang (Qualcomm) provides comment Zhuoyi (China Telecom) provides r01. Ashok (Samsung) comments Zhuoyi (China Telecom) replies. Ashok (Samsung) responds to Zhuoyi Zhuoyi (China Telecom) replies to Ashok. Belen (Ericsson) provides comments. Zhuoyi (China Telecom) replies to Ericsson and provides r02. Belen (Ericsson) provides r03. Zhuoyi (China Telecom) is OK with r03. Ashok (Samsung) fine with r03 ==== 8.X, 9.X, 10.X Revisions Deadline ==== Juan Zhang (Qualcomm) is fine with r03. ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.15 | S2-2201598 | P-CR | Approval | 23.700-89: New solution for FS_AMP WT#1. | China Telecom | Rel-18 | Revision of S2-2200165r03. Approved | Approved | |
| 9.15 | S2-2200833 | P-CR | Approval | 23.700-89: 23.700-89: Solution to KI#1, Provide Authorized RFSP in EPC via UDM/HSS . | Nokia, Nokia Shanghai Bell | Rel-18 | Approved | Ashok (Samsung) need some clarification Pallab (Nokia) responds to Ashok (Samsung) Belen (Ericsson) provides comments. Pallab (Nokia) responds to Belen Belen (Ericsson) asks a question again and thinks the contribution needs updates. Ashok (Samsung) replies to Pallab (Nokia) Ashok (Samsung) explains to Pallab (Nokia) Pallab (Nokia) responds to Ashok (Samsung) and requests to read the solution Ashok (Samsung) provides feedback on the solution to Pallab (Nokia) Pallab (Nokia) responds to Ashok (Samsung) and requests to read the solution again Belen (Ericsson) comments. Belen (Ericsson) is okay with the contribution ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Approved |
| 9.16 | - | - | - | Study on Personal IoT Networks (5G_PIN) | - | - | Docs:=29 | - | |
| 9.16 | - | - | - | General (skeleton, scope) | - | - | Docs:=4 | - | |
| 9.16 | S2-2200573 | P-CR | Approval | 23.700-88: TR 23.700-88 v0.0.0 - skeleton | vivo | Rel-18 | r01 agreed. Revised to S2-2201792. | Zhenhua (vivo) provides r01 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.16 | S2-2201792 | P-CR | Approval | 23.700-88: FS_PIN TR 23.700-88 Skeleton. | Vivo (Rapporteur) | Rel-18 | Revision of S2-2200573r01. Approved | Approved | |
| 9.16 | S2-2200574 | P-CR | Approval | 23.700-88: Scope of PIN study. | vivo | Rel-18 | r03 agreed. Revised to S2-2201793. | Lars (Sony) provides r01. Kefeng Zhang (Qualcomm) comments to r01 and provides r02. Lars (Sony) responds to Kefeng Zhang. LaeYoung (LGE) comments. Zhenhua (vivo) provides r03. Kefeng (Qualcomm) responds to Lars (Sony). Lars (Sony) responds to Kefeng. Kefeng Zhang (Qualcomm) is fine with r03 from Zhenhua. Pallab (Nokia) comments. Zhenhua (vivo) replies to Pallab (Nokia). Pallab (Nokia) replies to Zhenhua (vivo). ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.16 | S2-2201793 | P-CR | Approval | 23.700-88: Scope of PIN study. | vivo | Rel-18 | Revision of S2-2200574r03. Approved | Approved | |
| 9.16 | - | - | - | Terminology and definitions | - | - | Docs:=2 | - | |
| 9.16 | S2-2201184 | P-CR | Approval | 23.700-88: Definitions of terms and abbreviations. | Xiaomi | Rel-18 | r07 agreed. Revised to S2-2201794. | Marco (huawei) provides r01. Zhenhua (vivo) comments on r01. Lars (Sony) comments Zhenhua (vivo) agrees proposal from Lars (Sony) and provides r02 Xiaoyan Shi (Interdigital) is fine with r02 Marco (Huawei) provides r03 Jianning (Xiaomi) provide comment and r04 Zhenhua (vivo) comments on r04 Marco (Huawei) object r04 since per SID scope the PEGC is restricted to a UE Jianning (Xiaomi) provides r05 to stick with SID Zhenhua (vivo) provides r06 Zhenhua (vivo) replies to Qian (Ericsson) Pallab (Nokia) has same comments as Ericsson. Qian (Ericsson) asks a questions Walter (Philips) provides r07 Lars (Sony) ask Walter (Philips) on r07 Walter (Philips) responds to Lars (Sony) Lars (Sony) responds to Walter (Philips) Jianning (Xiaomi) replies to Qian (Ericsson) and Pallab (Nokia) Jianning (Xiaomi) provide comments Jianning (Xiaomi) provide views Zhenhua (vivo) share the view of Jianning (Xiaomi) and Walter (Philips) Marco (Huawei) replies to Qian (Ericsson) ==== 8.X, 9.X, 10.X Revisions Deadline ==== Marco (Huawei) ok with r07, r06 objects r00, r02, r04 Lars (Sony) prefers and is ok with r06, can live with r07. Qian (Ericsson) is ok with r07 or r06. ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.16 | S2-2201794 | P-CR | Approval | 23.700-88: Definitions of terms and abbreviations. | Xiaomi | Rel-18 | Revision of S2-2201184r07. Approved | Approved | |
| 9.16 | - | - | - | Architectural Assumption and requirements | - | - | Docs:=4 | - | |
| 9.16 | S2-2200575 | P-CR | Approval | 23.700-88: Architectural assumptions and principles. | vivo | Rel-18 | r27 agreed. Revised to S2-2201795, merging S2-2200738 | Zhenhua (vivo) proposes to merge S2-2200836 and S2-2200975 into S2-2200575, and provides r01. Xiaoyan Shi (Interdigital) provides r02 and adds Interdigital as cosign company. Marco (Huawei) comments and express disagree with R02. Zhenhua (vivo) replies to Marco (Huawei). Sudeep (Apple) comments on r02. Zhenhua (vivo) replies to Sudeep (Apple). LaeYoung (LGE) comments. Kefeng Zhang (Qualcomm) share the same concern as Sudeep (Apple), provides r03. Lars (Sony) have strong concern that text goes outside the SIB. LaeYoung (LGE) shares same concern with Lars (Sony). Zhenhua (vivo) replies to LaeYoung (LGE). Zhenhua (vivo) provides r04. Lars (Sony) comments on r04. LaeYoung (LGE) comments on r04. Zhenhua (vivo) provides r05. Lars (Sony) r05 looks good. Marco (Huawei) provides r06. Deng Qiang (CATT) asks questions for clarification. Lars (Sony) responds to Deng Qiang (CATT). Pallab (Nokia) provides comments and asks for opinion Lars (Sony) responds to Pallab (Nokia) Zhenhua (vivo) replies to Pallab (Nokia) Marco (Huawei) provides r07 and comment to Pallab (Nokia) Xiaoyan Shi (Interdigital) comments on r07 Jianning (Xiaomi) provide r08 Amanda Xiang ( Futurewei ) asked for clarification on r07 Pallab (Nokia) responds to Lars (Sony) Zhenhua (vivo) replies to Amanda Xiang ( Futurewei ) Zhenhua (vivo) provide r09 Pallab (Nokia) responds to Zhenhua (vivo) Zhenhua (vivo) comments to r10 Pallab (Nokia) provides r10 Jianning (Xiaomi) provide comment on r09 Pallab (Nokia) responds to Zhenhua (vivo). Walter Dees (Philips) provides r11 Zhenhua (vivo) provides r12 because r11 is based on an unagreeable version Kefeng Zhang (Qualcomm) comments to r12 Kefeng Zhang (Qualcomm) comments to r11 on replacing of 5G ProSe with NR SideLink Marco (Huawei) comment on identification of device and 5WWC Marco (Huawei) objects to r11 & R12 (and any possible future version) on replacing of 5G ProSe with NR SideLink Marco (Huawei) ask comments on '1 PEMC vs more PEMC' Walter (Philips) responds to Kenny (Qualcomm) and Marco (Huawei) Kefeng Zhang (Qualcomm) asks questions for clarification Zhenhua (vivo) replies to Kefeng Zhang (Qualcomm) Jianning (Xiaomi) provide view Kefeng Zhang (Qualcomm) replies to Walter (Philips) Pallab (Nokia) asks for clarification and provides r13, r14 Zhenhua (vivo) provides r15 based on r09, and comments on r13 and r14 LaeYoung (LGE) asks a Q for clarification. Zhenhua (vivo) comments on r15 and asks for clarification. Cannot accept r15 Jianning (Xiaomi) share the view with LaeYoung (LGE) and provide r16 Zhenhua (vivo) replies to Jianning (Xiaomi) Zhenhua (vivo) clarifies and provide r17 Pallab (Nokia) responds to Zhenhua (vivo) and provides r18 (based on r17) Zhenhua (vivo) replies to Pallab (Nokia) and provides r19 Jianning (Xiaomi) replies to Zhenhua (vivo) Pallab (Nokia) responds to Zhenhua (vivo) and provides r20 Zhenhua (vivo) provides r20 and replies to Pallab (Nokia) Jianning (Xiaomi) provide clarification to Zhenhua (vivo) Zhenhua (vivo) provides r22 Marco (Huawei) requests to remove the bullet on 5G-RG to consider any version from 20 onwards OK Pallab (Nokia) responds to Marco (Huawei) Walter (Philips) disagrees with r21 and suggests revision of r20. Prefers r19. Qian (Ericsson) provides r023 Zhenhua (vivo) provides r24 Xiaoyan Shi (Interdigital) ask question for clarification. Marco (Huawei) proposes: 'NOTE In this release the 5G-RG is considered outside the scope of the study and consequently not part of PIN' Zhenhua (vivo) replies to Xiaoyan Shi (Interdigital). Qian (Ericsson) comments. Dieter (Deutsche Telekom) comments. Xiaoyan Shi (Interdigital) provides r26. Zhenhua (vivo) replies to Qian (Ericsson). Qian (Ericsson) responds. Xiaoyan Shi (Interdigital) proposes to postpone CP/UP assumption discussion to next meeting. Zhenhua (vivo) provides r27. Zhenhua (vivo) propose another way forward to add an EN related to CP/UP. Xiaoyan Shi (Interdigital) is fine with both r27 and r26. ==== 8.X, 9.X, 10.X Revisions Deadline ==== LaeYoung (LGE) is fine with r27. Jianning (Xiaomi) is fine with r27 Pallab (Nokia) is OK with r27. Marco (Huawei) ok with r26, r27 Ericsson (Ericsson) proposes to go with r27 ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.16 | S2-2201795 | P-CR | Approval | 23.700-88: 23.700-88: Architectural assumptions and principles. | Vivo, Nokia, Nokia Shanghai Bell, Huawei, HiSilicon, Interdigital Inc. | Rel-18 | Revision of S2-2200575r27, merging S2-2200738. Approved | Approved | |
| 9.16 | S2-2200836 | P-CR | Approval | 23.700-88: 23.700-88: Architectural assumptions proposal . | Nokia, Nokia Shanghai Bell | Rel-18 | Merged into S2-2201355 | Zhenhua (Rapporteur) proposes to merge into S2-2200575. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.16 | S2-2200975 | P-CR | Approval | 23.700-88: PIN architecture assumptions. | Huawei, HiSilicon | Rel-18 | Merged into S2-2201355 | Zhenhua (Rapporteur) proposes to merge into S2-2200575. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.16 | - | - | - | Key Issues | - | - | Docs:=16 | - | |
| 9.16 | S2-2200576 | P-CR | Approval | 23.700-88: Key Issue: 5GC architecture enhancements to support PIN. | vivo | Rel-18 | r04 agreed. Revised to S2-2201796. | Zhenhua (vivo) provides r01. Lars (Sony) provides r02. Xiaoyan Shi (Interdigital) asks question for clarification. marco (Huawei) provides r03. Zhenhua (vivo) replies to Xiaoyan Shi (Interdigital). Lars (Sony) comments on r03. Suresh Srinivasan (Intel) agrees to merge 5.X.1 (points 5 &6) with 0576 Kefeng Zhang(Qualcomm) comments on r03. Zhenhua (vivo) replies to Kefeng Zhang(Qualcomm). Marco (Huawei) comments Zhenhua (vivo) is fine with the proposal from Marco (Huawei) and is fine with r03 Kefeng Zhang (Qualcomm) is fine with the proposal from Marco (Huawei). Pallab (Nokia) provides comments on r03 Zhenhua (vivo) comments on r04 Pallab (Nokia) provides r04 based on comments provided earlier Pallab (Nokia) responds to Zhenhua (vivo) Zhenhua (vivo) is fine with r04 Qian (Ericsson) provides comments Zhenhua (vivo) replies to Qian (Ericsson) ==== 8.X, 9.X, 10.X Revisions Deadline ==== Marco (Huawei) ok with r04, r03 Qian (Ericsson) is also ok with r04. Xiaoyan Shi (Interdigital) is fine with r04 ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.16 | S2-2201796 | P-CR | Approval | 23.700-88: Key Issue: 5GC architecture enhancements to support PIN. | Vivo, Intel, Nokia, Nokia Shanghai Bell | Rel-18 | Revision of S2-2200576r04. Approved | Approved | |
| 9.16 | S2-2200578 | P-CR | Approval | 23.700-88: Key Issue: 5GC supports management of PIN. | vivo | Rel-18 | Merged into S2-2201337 | Zhenhua (Rapporteur) proposes to merge S2-2200578 into S2-2200754. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.16 | S2-2200579 | P-CR | Approval | 23.700-88: Key Issue: 5GC supports communication of PIN. | vivo | Rel-18 | Merged into S2-2201736 | Zhenhua (Rapporteur) proposes to merge into S2-2201125. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.16 | S2-2200580 | P-CR | Approval | 23.700-88: Key Issue: 5GC supports authorization in PIN. | vivo | Rel-18 | r08 agreed. Revised to S2-2201797. | Zhenhua (Rapporteur) proposes to merge 'authorization' part of S2-2200754, S2-2200837, and S2-2201125 into S2-2200580, and provides r01. Lars (Sony) have several questions and provides r02. Zhenhua (vivo) ask Q for r02. Pallab (Nokia) ask for clarification on r02. Qian (Ericsson) provides comments and r03. Suresh Srinivasan (Intel) agrees to merge 1192 with 580 Marco (Huawei) provides r04 Dieter (Deutsche Telekom) asks question for clarification and comments. Zhenhua (vivo) replies to Dieter (Deutsche Telekom). Zhenhua (vivo) provides r05 to remove the restriction on '5GC'. Dieter (Deutsche Telekom) comments. Qian (Ericsson) comments and provide r07 (please ignore r06 which has an error). Suresh Srinivasan (Intel) co-signs 580 (1192 merged with 580) and provide r08 ==== 8.X, 9.X, 10.X Revisions Deadline ==== Marco (Huawei) ok with r08 (NOT OK to r00 - r05) Qian (Ericsson) is ok with r08. Pallab (Nokia) is ok with r08. Objects to r00 through r05 ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.16 | S2-2201797 | P-CR | Approval | 23.700-88: Key Issue: 5GC supports authorization in PIN. | Vivo, China Telecom, Nokia, Interdigital Inc, Intel. | Rel-18 | Revision of S2-2200580r08. Approved | Approved | |
| 9.16 | S2-2200754 | P-CR | Approval | 23.700-88: Key Issue of support for management of the PIN and its elements. | China Telecom | Rel-18 | r16 agreed. Revised to S2-2201798, merging S2-2200626 | Yuying (China Telecom) proposes to merge S2-2201124 and S2-2200578 into S2-2200754, and provides S2-2200754r01. Lars (Sony) provides r02. Xiaoyan Shi (Interdigital) provides r03. Lars (Sony) comments on r03. Xiaoyan Shi (Interdigital) replies to Lars. Marco (Huawei) provides r04. Yuying (China Telecom) replies to Marco and asks for clarification. Zhenhua (vivo) clarifies on r04. Yishan (Huawei) asks for clarification Yuying (China Telecom) replies to Huawei. Zhenhua (vivo) replies to Yishan (Huawei) LaeYoung (LGE) asks a Q. Zhenhua (vivo) replies to Lars (Sony) and comments. Lars (Sony) responds to Zhenhua (vivo) Xiaoyan Shi (Interdigital) comments Zhenhua (vivo) provides r05 Kefeng Zhang (Qualcomm) asks question to r05 LaeYoung (LGE) asks a Q to r05. Zhenhua (vivo) replies to LaeYoung (LGE). LaeYoung (LGE) replies to Zhenhua (vivo). Xiaoyan Shi (Interdigital) comments on '5GC' in this KI and suggests to replace it by '5GS' Kefeng Zhang (Qualcomm) replies Zhenhua (vivo) Pallab (Nokia) ask questions and provides r06 Jianning (Xiaomi) provides comment Zhenhua (vivo) replies to Pallab (Nokia) Zhenhua (vivo) replies to Jianning (Xiaomi) Jianning (Xiaomi) replies to Zhenhua (vivo) and provide r07 Zhenhua (vivo) replies to Kenny (Qualcomm) Zhenhua (vivo) agrees Xiaoyan Shi (Interdigital) Zhenhua (vivo) provide r08 LaeYoung (LGE) provides r09. Kefeng Zhang (Qualcomm) provides r10. Qian (Ericsson) comments and provides r11. Zhenhua (vivo) provides r12 to remove reference to 22.261 Yuying (China Telecom) provides r13 to remove the third bullet Marco (Huawei) provides r14 to re-add bullet and move text from authorization KI Jianning (Xiaomi) provide comment on r14 Qian (Ericsson) provides comments Zhenhua (vivo) provide r15 Sudeep (Apple) provides r16. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Marco (Huawei) ok with r16 Qian (Ericsson) is ok with r16 Pallab (Nokia) is ok with r16 ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.16 | S2-2201798 | P-CR | Approval | 23.700-88: Key Issue of support for management of the PIN and its elements. | China Telecom, vivo, Interdigital Inc. | Rel-18 | Revision of S2-2200754r16, merging S2-2200626. Approved | Approved | |
| 9.16 | S2-2200837 | P-CR | Approval | 23.700-88: 23.700-88: KI on Identification of PIN and PIN elements. | Nokia, Nokia Shanghai Bell | Rel-18 | Noted | Zhenhua (vivo) proposes to merge 'Identification' related part of S2-2200578 and S2-2201192 into S2-2200837, and provides r01. Marco (Huawei) confused with the proposal for 1192 & 0837. Pallab (Nokia) provides r03 based on r01. Also for chairs note, r02 was provided by Intel in the discussion for 1192 Zhenhua (vivo) provides r04 Kefeng Zhang (Qualcomm) provides r05 Qian (Ericsson) asks a question. Walter (Philips) provides r06. Zhenhua (vivo) provides r07 and replies to Qian (Ericsson). Marco (Huawei ) provides r08. Suresh Srinivasan (Intel) provides 0837r09 (merged with 1192) Xiaoyan Shi (interdigital) prefers r07. Pallab (Nokia) objects to r09. Prefers r07 over r08 ==== 8.X, 9.X, 10.X Revisions Deadline ==== Suresh Srinivasan (Intel) clarifies to Pallab's objection to r09 Pallab (Nokia) responds to Suresh Srinivasan (Intel). No change in position. Marco (Huawei) ok with r07, r08, and object r09 and from r00 to r05 Suresh Srinivasan (Intel) Objects with r07, r08 Qian (Ericsson) provides comments and supports r08 Xiaoyan Shi (Interdigital) prefers r07, but can also live with r08. Xiaoyan Shi (Interdigital) would ask which parts of r07/08 is objected by Intel. Suresh Srinivasan (Intel) replies to Xiaoyan comments ==== 8.X, 9.X, 10.X Final Deadline ==== Zhenhua (rapporteur) propose to go CC#4 Suresh Srinivasan (Intel) replies to Zhenhua's proposition to go to CC#4 | Noted |
| 9.16 | S2-2201123 | P-CR | Approval | 23.700-88: New KI: PIN discovery and selection. | Interdigital | Rel-18 | r08 agreed. Revised to S2-2201799. | Zhenhua (vivo) proposes to merge part of S2-2200577 into S2-2201123, and provides r01. Xiaoyan Shi (Interdigital) comments. Zhenhua (vivo) replies to Xiaoyan Shi (Interdigital). Xiaoyan Shi (Interdigital) replies to Zhenhua Yishan (Huawei) provides comments and asks for clarification Zhenhua (vivo) replies to Yishan (Huawei) Hong (Qualcomm) comments on r01. Xiaoyan Shi (Interdigital) provides r02. Zhenhua (vivo) replies to Hong (Qualcomm) LaeYoung (LGE) comments. Marco (Huawei) comments. Xiaoyan Shi (Interdigital) is fine with r03. Zhenhua (vivo) also is fine with r03 and replies. Deng Qiang (CATT) asks questions for clarification. Zhenhua (vivo) replies. LaeYoung (LGE) asks a Q to Zhenhua (vivo). Zhenhua (vivo) replies to LaeYoung (LGE). LaeYoung (LGE) provides r04. Pallab (Nokia) requests for clarification. Zhenhua (vivo) replies to Pallab (Nokia). Walter (Philips) provides r05 Amanda ( Futurewei ) provides r06 Jianning (Xiaomi) provide r07 Pallab (Nokia) asks Amanda ( Futurewei ) for clarification Qian (Ericsson) provides comments Zhenhua (vivo) provides r08 Amanda ( Futurewei ) provides response to Nokia Pallab (Nokia) responds to Amanda ( Futurewei ) ==== 8.X, 9.X, 10.X Revisions Deadline ==== LaeYoung (LGE) is fine with r08 and asks a Q. Zhenhua (vivo) also suggest to go with r08. Xiaoyan Shi (Interdigital) replies to Kefeng and proposes to move forward with r08. Kefeng Zhang (Qualcomm) asks questions to r08 Jianning (Xiaomi) replies to Kenny (Qaulcomm) and Xiaoyan (interdigital), and fine to go with r08 LaeYoung (LGE) replies to Zhenhua (vivo). Kefeng Zhang (Qualcomm) is OK with r08 and replies to LaeYoung and Jianning. Qian (Ericsson) is OK with r08. Pallab (Nokia) supports r08. ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.16 | S2-2201799 | P-CR | Approval | 23.700-88: New KI: PIN discovery and selection. | Interdigital, vivo, Futurewei, Xiaomi | Rel-18 | Revision of S2-2201123r08. Approved | Approved | |
| 9.16 | S2-2201125 | P-CR | Approval | 23.700-88: New KI: PIN connectivity . | Interdigital | Rel-18 | r07 agreed. Revised to S2-2201800, merging S2-2200970 | Zhenhua (Rapporteur) proposes to merge S2-2200579 into S2-2201125, and merge 'authorization' part of S2-2201125 into S2-2200580, and provides r01. LaeYoung (LGE) provides r02. Xiaoyan Shi (Interdigital) provides r03. Pallab (Nokia) provides r04. Walter (Philips) asks clarification on r04. Prefers r03. LaeYoung (LGE) provides comment. Kefeng Zhang (Qualcomm) asks clarification. Pallab (Nokia) responds to Walter (Philips) and prefers r04 over r03 Zhenhua (vivo) replies to Kefeng Zhang (Qualcomm). Xiaoyan Shi (Interdigital) replies to Pallab and provides r05. Dieter (Deutsche Telekom) asks question for clarification and comments. Zhenhua (vivo) replies to Dieter (Deutsche Telekom). Zhenhua (vivo) provides r06, only make the title simple Jianning (Xiaomi) ask questions for clarification on r06 Zhenhua (vivo) replies to Jianning (Xiaomi) Jianning (Xiaomi) provide comments Dieter (Deutsche Telekom) asks question for clarification. Dieter (Deutsche Telekom) comments. Zhenhua (vivo) provides r07 ==== 8.X, 9.X, 10.X Revisions Deadline ==== Pallab (Nokia) is OK to go with r07. Qian (Ericsson) is fine to go with r07. ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.16 | S2-2201800 | P-CR | Approval | 23.700-88: New KI: PIN connectivity . | Interdigital, vivo, Xiaomi | Rel-18 | Revision of S2-2201125r07, merging S2-2200970. Approved | Approved | |
| 9.16 | S2-2201185 | P-CR | Approval | 23.700-88: Key Issue: Authorization and policy/parameters provisioning for PIN. | Xiaomi | Rel-18 | r09 agreed. Revised to S2-2201801. | Zhenhua (vivo) proposes to merge 'policy/parameters provisioning' part of S2-2200577 into S2-2201185, and provides r01. Xiaoyan Shi (Interdigital) provides r02. Jianning (Xiaomi) provides comment and provide r03 Xiaoyan Shi (Interdigital) provide r04 Kefeng Zhang (Qualcomm) provides r05 Pallab (Nokia) provides r06 and asks questions Jianning (Xiaomi) response Pallab (Nokia), and fine with r06 Marco (Huawei) express concern on this KI and propose R07 Suresh Srinivasan (Intel) provides 1185r08 Jianning (Xiaomi) is fine with r08 Zhenhua (vivo) provides r09, only editorial modification Zhenhua (vivo) provides r10 to add configuration example that removed from 754r15 ==== 8.X, 9.X, 10.X Revisions Deadline ==== Marco (Huawei) ok with r07, r08, r09 and object r10 and from r00 to r06 Qian (Ericsson) supports to go with r09 Pallab (Nokia) also supports r09. Objects to r10 ==== 8.X, 9.X, 10.X Final Deadline ==== Kefeng Zhang (Qualcomm) prefers r09. | Revised |
| 9.16 | S2-2201801 | P-CR | Approval | 23.700-88: Key Issue: Policy/parameters provisioning for PIN. | Xiaomi, vivo, Interdigital Inc, Intel | Rel-18 | Revision of S2-2201185r09. Approved | Approved | |
| 9.16 | S2-2201192 | P-CR | Approval | 23.700-88: New KI of PIN and PIN Element Identification for WT#1.2 and WT2.1. | Intel | Rel-18 | Merged into S2-2201331 | Zhenhua (vivo) proposes to merge 'arch enhancements' in 5.Y into S2-2200576, merge others in 5.Y into S2-2200837, merge 'Identify PIN Elements' in 5.X.1 into S2-2200837, merge 'Potential arch enhancements' in 5.X.1 into S2-2200576, and provides r01. Xiaoyan Shi (Interdigital) asks question for clarification and proposes to merge this contribution to 0837 and 0580. Marco (Huawei) confused with the proposal for 1192 & 0837. Suresh Srinivasan (Intel) agrees with S2-2201192r01 Zhenhua (vivo) comments. Suresh Srinivasan (Intel) Clarification on the proposal of 1192 & 0837 merger Suresh Srinivasan (Intel) agree to merge 5.Y of 1192 with 0837 Marco (Huawei) answer to Suresh Srinivasan (Intel) Zhenhua (vivo) suggest to first refine the text of the contribution Xiaoyan Shi (Interdigital) comments on 'linkage'. Suresh Srinivasan (Intel) Provides S2-2200837r02 (5.Y of 1192 merged with 0837) Pallab (Nokia) comments. Suresh Srinivasan (Intel) replies to Pallab's (Nokia) comments. Suresh Srinivasan (Intel) replies to Xiaoyan Shi's comments on 'linkage'. Pallab (Nokia) responds to Suresh Srinivasan (Intel) and asks questions on r01. Feels that content of this KI can be merged to multiple KIs related to Identification, Discovery and authentication/authorization. Marco (Huawei) propose Object this pCR. So propose to Note and discuss only S2-220837 as KI on Authentication/Authorization Qian (Ericsson) provides comments Suresh Srinivasan (Intel) reply to Pallab, Marco, Qian comments Zhenhua (vivo) proposes merge into S2-2200837 as Suresh Srinivasan (Intel) indicated ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.16 | - | - | - | Solutions | - | - | Docs:=1 | - | |
| 9.16 | S2-2200976 | P-CR | Approval | 23.700-88: Solution for PIN network. | Huawei, HiSilicon | Rel-18 | Postponed | Zhenhua (vivo) proposes to not include this solution in the TR now considering there's no call flows to support and help understand the architecture. But still want to see others opinion on this solution. Provides r01 in case we want further discussion. Xiaoyan Shi (Interdigital) also suggests to postpone this solution to next meeting. The corresponding KI is not stable and there is not clear description on PEF. Hong (Qualcomm) supports postponing the solution proposal. LaeYoung (LGE) also prefers to POSTPONE this paper. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Postponed |
| 9.16 | - | - | - | Documents exceeding quota | - | - | Docs:=2 | - | |
| 9.16 | S2-2200577 | P-CR | Approval | 23.700-88: Key Issue: 5GC supports discovery and access of PIN. | vivo | Rel-18 | Not Handled | Zhenhua (Rapporteur) proposes to merge S2-2200577 into S2-2201123. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | - |
| 9.16 | S2-2201124 | P-CR | Approval | 23.700-88: New KI: PIN Management. | Interdigital | Rel-18 | Not Handled | Zhenhua (Rapporteur) proposes to merge into S2-2200754. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | - |
| 9.17 | - | - | - | Study on evolution of IMS multimedia telephony service (FS_NG_RTC) | - | - | Docs:=24 | - | |
| 9.17 | S2-2200015 | LS In | Action | LS from GSMA 5GJA: LS to 3GPP on IMS Data Channel Architecture | GSMA 5GJA (5GJA18_109r1) | Revision of Postponed S2-2108297 from S2#148E. Response drafted in S2-2200130. Final response in S2-2201599 | ==== 8.X, 9.X, 10.X Final Deadline ==== | Replied to | |
| 9.17 | S2-2200130 | LS OUT | Approval | [DRAFT] Reply LS on IMS Data Channel Architecture | China Mobile | Response to S2-2200015. r06 agreed. Revised to S2-2201599. | George Foti (Ericsson) provides r01. UPG group has taken over the GSMA work SO corrected the committee name. Yi (China Mobile) provides r02 Rainer (Nokia) provides r03. Rainer (Nokia) comments. Leo (Deutsche Telekom) provides r04. Hao Dong (ZTE) comments on r04. Yi (China Mobile) clarifies the SA2 SID name is FS_NG_RTC. Rainer (Nokia) replies. Yi (China Mobile) replies and provides r05. Leo (Deutsche Telekom) provides r06. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised | |
| 9.17 | S2-2201599 | LS OUT | Approval | Reply LS on IMS Data Channel Architecture | SA WG2 | Rel-18 | Revision of S2-2200130r06. Approved | Approved | |
| 9.17 | S2-2200123 | P-CR | Approval | 23.700-87: Skeleton of TR 23.700-87 | China Mobile | Rel-18 | 23.700-87 TR Skeleton. Approved | ==== 8.X, 9.X, 10.X Final Deadline ==== | Approved |
| 9.17 | S2-2200124 | P-CR | Approval | 23.700-87: Scope of TR 23.700-87 | China Mobile | Rel-18 | r01 agreed. Revised to S2-2201600. | Leo (Deutsche Telekom) provides r01 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.17 | S2-2201600 | P-CR | Approval | 23.700-87: Scope of TR 23.700-87. | China Mobile | Rel-18 | Revision of S2-2200124r01. Approved | Approved | |
| 9.17 | S2-2200125 | P-CR | Approval | 23.700-87: Architectural assumptions and principles of TR 23.700-87 | China Mobile | Rel-18 | r04 agreed. Revised to S2-2201601. | Hao Dong (ZTE) comments. Kefeng Zhang (Qualcomm) comments on access agnostic. George Foti (Ericsson) provides r01 Kefeng Zhang (Qualcomm) further comments on access agnostic. Yi (China Mobile) responds to Kefeng. Rainer (Nokia) asks for clarification. Yi (China Mobile) responds to Rainer. Rainer (Nokia) proposes to merge 125 into 192. Rainer (Nokia) replies. George (Ericsson) provides comments. Let the editor do that. I prefer it this way Yi (China Mobile) provides r02. George (Ericsson) provides comments. I also think the first bullet is not needed. Too broad. I want it removed. The other key issues capture that aspect and it is more pertinent there. Kefeng Zhang (Qualcomm) provides comments. George (Ericsson) provides r03. Removed the first bullet. It does not belong there. Kefeng Zhang (Qualcomm) provides r04 to reflect the previous editorial comment. Yi (China Mobile) is OK with r03 or r04. ==== 8.X, 9.X, 10.X Revisions Deadline ==== George (Ericsson) Ericsson supports r04 Rainer (Nokia) is also ok with r04. Mu (Huawei) is ok with r04. ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.17 | S2-2201601 | P-CR | Approval | 23.700-87: Architectural assumptions and principles of TR 23.700-87. | China Mobile | Rel-18 | Revision of S2-2200125r04. Approved | Approved | |
| 9.17 | S2-2200192 | P-CR | Approval | 23.700-78: Architectural Requirements. | Ericsson | Rel-18 | r03 agreed. Revised to S2-2201602. | George (Ericsson) Ericsson Ok with r01 Yi (China Mobile) provides r01 Rainer (Nokia) provides r02. Rainer (Nokia) replies. George (Ericsson) Ericsson NOT OK with r02. Anything related to Key issues and the solutions cannot be part of any architectural requirement. This prejudges solutions. Rainer (Nokia) provides r03. George (Ericsson) responds. I dont see the need for the second bullet which is already covered by a KI. ==== 8.X, 9.X, 10.X Revisions Deadline ==== George (Ericsson) Ericsson OK with r03 Mu (Huawei) is ok with r03. ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.17 | S2-2201602 | P-CR | Approval | 23.700-78: Architectural Requirements. | Ericsson | Rel-18 | Revision of S2-2200192r03. Approved | Approved | |
| 9.17 | S2-2200126 | P-CR | Approval | 23.700-87: TR 23.700-87: KI on service based architecture for IMS media control | China Mobile | Rel-18 | r06 agreed. Revised to S2-2201603, merging S2-2201233. CC#4: Noted | George Foti (Ericsson) provides r01. Merged in 389 aspects in this revision. Mu(Huawei) comments that this KI should not only limit to new services. George (Ericsson) provides response. We have already an IMS architecture that we want to apply 5G service based principles to it. Service based architecture is not an appropriate term. The second bullet does cover what U want. Also this is CMCC pCR. There is everything that U want in there. Yi (China Mobile) do not accept r01 and provides r03. Rainer (Nokia) provides r04. Ashok (Samsung) agrees with Rainer (Nokia) George (Ericsson) provides r05. Minor editorial changes Chris Joul (T-Mobile USA) Provides Comments Yi (China Mobile) provides r06. Hao Dong (ZTE) provides r07. George (Ericsson) provides r08 Rainer (Nokia) objects to r08. George (Ericsson) provides comments. This was only intended for service discovery, etc... we are not proposing to change SIP for example or impacting legacy interfaces. Would adding such a clarification help. Rainer (Nokia) replies. Ashok (Samsung) comments George (Ericsson) provides comment. Yes, I thought U would be OK with that, and not just limit it to the IMS Media. In other words we should allow solutions to present what they want. We have an evaluation phase that will take place. Ashok (Samsung) responds to George (Ericsson) ==== 8.X, 9.X, 10.X Revisions Deadline ==== George (Ericsson) Ericsson support r08. George (Ericsson) Ericsson not OK with r07 as it restricts solutions. We propose r08 which is broader Rainer (Nokia) is ok with r07 and objects to r08. Yi (China Mobile) suggest to go with r07 and discuss further if the consensus can be made for extending the scope. Hao Dong (ZTE) comments. Hao Dong (ZTE) is ok with r07. George (Ericsson) Ericsson Objects to r07; on the one hand the Key issues is broad in the scope of impacts to IMS media and control, and on the other hand it limits discovery, etc to IMS media nodes only knowing that other IMS nodes, eg. IMS AS may need to be discovered in support of the DC feature. This limits solutions and as such its NOT OK. R08 attempted to broaden the scope. ==== 8.X, 9.X, 10.X Final Deadline ==== Yi (China Mobile) clarifies I am not objecting r08. George (Ericsson) provides comments. The rev 08 was out since Friday, i.e. 4 days before the deadline including the weekend. Not a single comment received; certainly not for a lack of time. I believe, people can submit solutions We can work on the KI offline with all people concerned to clarify the scope and leave no loose ends, and then it will progress the next meeting. I believe I can say that in the name of progress you can also accept r08. Yi (China Mobile) comments. | Noted |
| 9.17 | S2-2201603 | P-CR | Approval | 23.700-87: TR 23.700-87: KI on service based architecture for IMS media control | China Mobile | Rel-18 | Revision of S2-2200126r06, merging S2-2201233. CC#4: WITHDRAWN | Withdrawn | |
| 9.17 | S2-2200194 | P-CR | Approval | 23.700-78: Key issue for interaction IMS and webserver for media handling. | Ericsson | Rel-18 | Merged into S2-2201604 | Yi (China Mobile) ask question for clarification. George (Ericsson) provides response. Are U sure this is 194. There is none here. We will consider this merged as well in 126 and 128 Yi (China Mobile) propose to note it. Rainer (Nokia) agrees that 194 should be marked as merged into 128. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.17 | S2-2200127 | P-CR | Approval | 23.700-87: TR 23.700-87: KI on enhancement to support third party identity management and usage in IMS network | China Mobile | Rel-18 | Merged into S2-2201604 | George Foti (Ericsson) Merged in 388 r01. To be noted. Rainer (Nokia) agrees that 127 should be marked as merged into 388. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.17 | S2-2200128 | P-CR | Approval | 23.700-87: TR 23.700-87: KI on support of Data Channel usage in IMS network | China Mobile | Rel-18 | r16 agreed. Revised to S2-2201604, merging S2-2200127, S2-2200193, S2-2200194, S2-2200389 and S2-2200730 | Kefeng Zhang (Qualcomm) comments on DC impacts to Emergency Call. George Foti (Ericsson) provides r01. Merged in applicable aspects from 389 Hao Dong (ZTE) agrees to take this pCR as baseline for DC KI and provides r02 with two additional bullets. Yi (China Mobile) replies to Kefeng. Yi (China Mobile) comments on r02. Hao Dong (ZTE) responds to Yi (China Mobile) and provides r03. Rainer (Nokia) comments. Mu(Huawei) agrees to merge 0389 into 0128, and provide r04 based on r03, with one additional point. George (Ericsson) provides r05. Please see comments below Rainer (Nokia) provides r06. Yi (China Mobile) provides r07. George (Ericsson)asks a question. Rainer (Nokia) provides r08. Yi (China Mobile) responds on interworking scenario. Hao Dong (ZTE) comments. Kefeng Zhang (Qualcomm) comments on DCMTSI and MTSI interworking, provides r09. Hao Dong (ZTE) responds to Yi (China Mobile). Mu(Huawei) adds on a point about interworking scenario. Mu(Huawei) responds to Rainer (Nokia). George (Ericsson) provides r10. Enhanced readability of second bullet Leo (Deutsche Telekom) supports this KI and provides r11. Yi (China Mobile) clarifies and provides r12. Rainer (Nokia) prefers the original wording. Yi (China Mobile) is fine with the original wording. George (Ericsson) provides r13. Sorry now correct link George (Ericsson) provides r13. I converted the last bullet to a Note. See comments below Yi (China Mobile) comments. Rainer (Nokia) provides r14. Mu(Huawei) comments. We should not use lack of solution as a reason to deprioritize KI. George (Ericsson) provides comments. Xiaobo (vivo) comments and would like to study interworking between DCMTSI and MTSI client. Rainer (Nokia) replies. George (Ericsson) provides comment. Mu(Huawei) comments. I don't see why we need to put the issue as low priority. Mu(Huawei) provides r15 to reflect recent discussion. George (Ericsson) provides r16. Please consider other views on the email thread and not just Urs. Patrice (Huawei) comments. Rainer (Nokia) is ok with r16. Patrice (Huawei) comments further. George (Ericsson) then U should be fine with lower priority or something that says that this bullet depends on the other 3. I am fine if U have some alternative text. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Yi (China Mobile) provides r17. Mu (Huawei) is ok with the note change in r17. Hao Dong (ZTE) supports r17. Yi (China Mobile) suggests to go forward with r15 and change the NOTE at the next meeting if people are fine with it. Mu (Huawei) agrees to approve r15 in this meeting and change the NOTE at the next meeting. George (Ericsson) provides comment. Ericsson OK with r16 only and also with r17 if the note is slightly changed as follows: NOTE: This last bullet might hasve dependency on progress of other bullets. Coordination with SA4 might be needed. If this is agreeable we can bring it in the CC Rainer (Nokia) is ok with r17 and changing the Note as proposed by George. Leo (Deutsche Telekom) prefers r15 and can live with r16. r17 was provided after the Revisions Deadline. Mu (Huawei) is ok with r17 and changing the Note as proposed be George, I propose to bring the topic to CC#4. Mu (Huawei) is OK with r16 as a compromise, and propose to change the note proposed by George in next meeting. Hao Dong (ZTE) can live with r16 to make some progress for this KI. Rainer (Nokia) also ok with r16. ==== 8.X, 9.X, 10.X Final Deadline ==== Yi (China Mobile) in light of making progress, I can live with r16 and changing the note at next meeting. | Revised |
| 9.17 | S2-2201604 | P-CR | Approval | 23.700-87: TR 23.700-87: KI on support of Data Channel usage in IMS network. | China Mobile, ZTE, Huawei, HiSilicon, Ericsson, Nokia, Nokia Shanghai Bell, Qualcomm, Deutsche Telekom | Rel-18 | Revision of S2-2200128r16, merging S2-2200127, merging S2-2200127 and S2-2200193, merging S2-2200127, S2-2200193 and S2-2200194, merging S2-2200127, S2-2200193, S2-2200194 and S2-2200389, merging S2-2200127, S2-2200193, S2-2200194, S2-2200389 and S2-22007 | Approved | |
| 9.17 | S2-2200389 | P-CR | Approval | 23.700-87: Key issue: the impact of IMS architecture and procedures to support Data Channel usage in IMS network. | Huawei, HiSilicon | Rel-18 | Merged into S2-2201604 | George Foti (Ericsson) proposes to merge this into 126 r01, and 128 r01 Kefeng Zhang (Qualcomm) comments: 1) remove the interactive communication between the DCMTSI client and the MTSI client. 2) remove DC in IMS emergence session Mu(Huawei) responses to Kefeng Zhang (Qualcomm). ==== 8.X, 9.X, 10.X Revisions Deadline ==== Mu (Huawei) comments. Please mark this as merged into 0128. ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.17 | S2-2200730 | P-CR | Approval | 23.700-87: New Key Issue on Support of Data Channel in IMS Architecture. | ZTE | Rel-18 | Merged into S2-2201604 | George Foti (Ericsson) proposes to merge this into 126 r01 and 128 r01 Kefeng Zhang (Qualcomm) comments on the reference of NG.129. Hao Dong (ZTE) responds to Kefeng Zhang (Qualcomm). George (Ericsson) provides comments. As stated we have the CMCC 126 and 128 containing the same info. SO we can note that one. Rainer (Nokia) proposes to merge 730 into 128. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Hao Dong (ZTE) confirms this paper is merged into S2-2200128. ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.17 | S2-2200193 | P-CR | Approval | 23.700-78: Key issue for interaction IMS AS - Web Server . | Ericsson | Rel-18 | Merged into S2-2201604 | George (Ericsson) Ericsson provide 128r01. We are OK to consider this merged in there. Yi (China Mobile) propose to merge it into 128 or 389. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.17 | S2-2200387 | P-CR | Approval | 23.700-87: Key Issue: Supporting AR Communication. | Huawei, HiSilicon | Rel-18 | r03 agreed. Revised to S2-2201605. | George Foti (Ericsson) provides r01 Mu(Huawei) we are OK with r01. Rainer (Nokia) provides r02. Mu(Huawei) provides r03. Rainer (Nokia) is ok with r03. ==== 8.X, 9.X, 10.X Revisions Deadline ==== George (Ericsson) Ericsson OK with r03 ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.17 | S2-2201605 | P-CR | Approval | 23.700-87: Key Issue: Supporting AR Communication. | Huawei, HiSilicon | Rel-18 | Revision of S2-2200387r03. Approved | Approved | |
| 9.17 | S2-2200388 | P-CR | Approval | 23.700-87: Key Issue: Support Third Party ID Access in IMS. | Huawei, HiSilicon | Rel-18 | r14 agreed. Revised to S2-2201606. | George Foti (Ericsson) provided r01. Incudes also 127 which is merged in this revision. Kefeng Zhang (Qualcomm) comments to remove IMS access for non-UICC based UE. Mu(Huawei) comments, and provides r02 based on r01. George (Ericsson) Ericsson NOT OK with r02. Please see comments Rainer (Nokia) provided r03. Ashok (Samsung) comments Rainer (Nokia) replies. Mu(Huawei) replies and provides r04. Rainer (Nokia) replies, proposes two changes. George (Ericsson) provides comments. Not OK with r04 Kefeng Zhang (Qualcomm) comments on r04 for call-back procedure. Yi (China Mobile) comments on r04 and ask question. Mu(Huawei) replies to some of the previous questions and comments. Rainer (Nokia) provides r05. George (Ericsson) provides r06. I added missing things to cover what I mentioned in my notes below. Rainer (Nokia) is ok with r06. Mu(Huawei) asks a question Mu(Huawei) provides r07, adding one note to reflect the dynamic process. Ashok (Samsung) provides r08 Mu(Huawei) asks a questions. Ashok (Samsung) responds to Mu(Huawei) Yi (China Mobile) provides r09. Ashok (Samsung) would like to co-sign. Forgot while uploading r08 George (Ericsson) OK with r08 ONLY. Additional comments below. Kefeng Zhang (Qualcomm) is OK with r08 and would like to cosign. Mu(Huawei) provides r10 based on previous discussion. Rainer (Nokia) comments. George (Ericsson) provides r11 Mu(Huawei) replies to Rainer(Nokia) George (Ericsson) provides comments. There is nothing touching IMS Registration. A UE is authenticated at IMS Registration as is today. We can add a note if U are concerned. The added aspects of checking third party identities etc, will only happen during a call, and that's what the bullets are about./ George (Ericsson) provides comments. That's what I said basically I don't know what HWA is concerned about. Mu (Huawei) comments. I don't see why the auth must happen during the call setup phase. It could happen during registration phase. Yi (China Mobile)comments on r10 and r11 and ask for further clarification. Mu(Huawei) replies. Yi (China Mobile) replies. George (Ericsson) provides comments. What is really the difference between what was written before and now. Mu(Huawei) provides r13 to reflect recent discussion George (Ericsson) provides r14. We would like to keep the statements aligned. Rainer (Nokia) is ok with r14. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Mu (Huawei) replies. Hao Dong (ZTE) comments. Yi (China Mobile) is ok with r14. Mu (Huawei) is ok with r14. Hao Dong (ZTE) is OK with r14. Ashok (Samsung) Ok with r14 and request to add Samsung while uploading the final tdoc ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.17 | S2-2201606 | P-CR | Approval | 23.700-87: Key Issue: Support Third Party ID Access in IMS. | Huawei, HiSilicon, Nokia, Nokia Shanghai Bell, Ericsson, China Mobile, Samsung | Rel-18 | Revision of S2-2200388r14. Approved | Approved | |
| 9.17 | S2-2201233 | P-CR | Approval | 23.700-87: Key Issue for WT#5, Discovery and Selection of other IMS nodes. | T-Mobile USA | Rel-18 | Merged into S2-2201603 (Withdrawn) | Yi (China Mobile) ask question for clarification. Chris Joul (T-Mobile USA) answers Yi (China Mobile) questions Ashok (Samsung) need clarification from Chris Joul (T-Mobile USA) Chris Joul (T-Mobile USA) answers Ashok (Samsung) question Ashok (Samsung) comments Rainer (Nokia) proposes to merge with S2-2200126. Yi (China Mobile) comments. George (Ericsson) provides comments. I prefer we agree on a scope for this before any merge to the r01 that I uploaded. Rainer (Nokia) comments. Chris Joul (T-Mobile USA) provides comments and proposes way forward George (Ericsson) provides response I would prefer to keep S-CSCF out for now. Once we have a handle on the discovery aspects for media than we can come back to it. Chris Joul (T-Mobile USA) recommends marking this as merged into S2-2000126 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 9.18 | - | - | - | Study on 5G multicast-broadcast services Phase 2 (FS_5MBS_Ph2) | - | - | Docs:=36 | - | |
| 9.18 | - | - | - | Administrative documents | - | - | Docs:=4 | - | |
| 9.18 | S2-2200602 | P-CR | Approval | 23.700-47: TR 23.700-47 scope. | Huawei (rapporteur) | Rel-18 | Approved | ==== 8.X, 9.X, 10.X Final Deadline ==== | Approved |
| 9.18 | S2-2200603 | P-CR | Approval | 23.700-47: Cover page of TR skeleton. | Huawei (rapporteur) | Rel-18 | r02 agreed. Revised to S2-2201354. | LaeYoung (LGE) provides r01. Thomas (Nokia) provides r02, comments that TR name needs to be aligned with proposed SID update in S2-2200608. LaeYoung (LGE) comments on the TR title. LiMeng (Huawei) replies LaeYoung and Thomas, and is fine with r02. LaeYoung (LGE) replies to LiMeng (Huawei). ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.18 | S2-2201354 | P-CR | Approval | 23.700-47: Cover page of TR skeleton. | Huawei (rapporteur) | Rel-18 | Revision of S2-2200603r02. Approved | Approved | |
| 9.18 | S2-2200605 | WORK PLAN | Information | Work plan of TR 23.700-47 | Huawei | Rel-18 | Noted | Judy (Ericsson) assumes that this paper can be noted ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 9.18 | - | - | - | Architectural assumptions | - | - | Docs:=2 | - | |
| 9.18 | S2-2200604 | P-CR | Approval | 23.700-47: FS_5MBS_Ph2 architectural assumptions. | Huawei (rapporteur) | Rel-18 | Merged into S2-2201360 | LiMeng (Huawei) provides r01, with merging S2-2200901. Zhendong (ZTE): proposes merging this pCR into S2-2200901 LiMeng (Huawei) is OK with Zhendong (ZTE)'s proposal. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.18 | S2-2200901 | P-CR | Approval | 23.700-47: Adding Architectural Assumption and Principle to MBS ph2. | ZTE | Rel-18 | Approved | LiMeng (Huawei) suggests to merge this document to S2-2200604. Zhendong (ZTE): proposes merging this 2200604 into this pCR LiMeng (Huawei) is fine with Zhendong (ZTE)'s proposal. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Approved |
| 9.18 | - | - | - | WT#1.1 (RRC Inactive) | - | - | Docs:=7 | - | |
| 9.18 | S2-2200473 | P-CR | Approval | 23.700-47: New Key Issue on Multicast MBS Session data reception in RRC Inactive . | Ericsson | Rel-18 | Merged into S2-2201355 | LiMeng (Huawei) suggests to merge this document into S2-2200600. Judy (Ericsson) confirms this paper is merged to 00600. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.18 | S2-2200529 | P-CR | Approval | 23.700-47: Key issue for multicast reception in RRC INACTIVE state. | CATT | Rel-18 | Merged into S2-2201776 | LiMeng (Huawei) suggests to merge this document into S2-2200600. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Xiaoyan (CATT) confirms that S2-2200529 is merged into S2-2200600. ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.18 | S2-2200600 | P-CR | Approval | 23.700-47: Key Issue: MBS data reception in RRC Inactive mode. | Huawei, HiSilicon | Rel-18 | r07 agreed. Revised to S2-2201355, merging S2-2200836, S2-2200975 and S2-2200473 | LiMeng (Huawei) provides r01. Thomas (Nokia) provides r02. Haris(Qualcomm) provides r03 LiMeng (Huawei) provides r05. Judy (Ericsson) provides r04. Xiaoyan (CATT) provides r06. Judy (Ericsson) provide r07. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Zhendong (ZTE): is fine with r07 LiMeng (Huawei) is OK with r07. Thomas (Nokia) is fine with r07. ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.18 | S2-2201355 | P-CR | Approval | 23.700-47: Key Issue: MBS data reception in RRC Inactive mode. | Huawei, HiSilicon, Nokia, Nokia Shanghai Bell, CATT, Ericsson, ZTE | Rel-18 | Revision of S2-2200600r07, merging S2-2200836, merging S2-2200836 and S2-2200975, merging S2-2200836, S2-2200975 and S2-2200473. Approved | Approved | |
| 9.18 | S2-2200902 | P-CR | Approval | 23.700-47: New Key issue: receiving Multicast MBS data in RRC Inactive state. | ZTE | Rel-18 | Merged into S2-2201776 | LiMeng (Huawei) suggests to merge this document into S2-2200600. Zhendong (ZTE): is fine to merge this paper into 2200600 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.18 | S2-2200599 | P-CR | Approval | 23.700-47: Discussion and proposal of RRC Inactive multicast MBS reception. | Huawei, HiSilicon | Rel-18 | r02 agreed. Revised to S2-2201356. | Judy (Ericsson) provides r01 Thomas (Nokia) provides r02 Judy (Ericsson) comments. Thomas(Nokia) replies to Judy (Ericsson) ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.18 | S2-2201356 | P-CR | Approval | 23.700-47: Discussion and proposal of RRC Inactive multicast MBS reception. | Huawei, HiSilicon | Rel-18 | Revision of S2-2200599r02. Approved | Approved | |
| 9.18 | - | - | - | WT#1.2 (MOCN broadcast) | - | - | Docs:=6 | - | |
| 9.18 | S2-2200471 | P-CR | Approval | 23.700-47: New Key Issue: Efficient Resource Utilization for 5MBS Broadcast in MOCN Network Sharing. | Ericsson | Rel-18 | r05 agreed. Revised to S2-2201357, merging S2-2200749 and S2-2200607 | Haris(Qualcomm) provides r01 Robbie (Ericsson) provides r02. Thomas (Nokia) provides r03. Thomas(Nokia) comments against r01 Haris(Qualcomm) comments Thomas(Nokia) replies to Haris LiMeng (Huawei) replies to Haris (Qualcomm) and provides r04. Zhendong (ZTE): provides r05 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.18 | S2-2201357 | P-CR | Approval | 23.700-47: New Key Issue: Efficient Resource Utilization for 5MBS Broadcast in MOCN Network Sharing. | Ericsson, ZTE | Rel-18 | Revision of S2-2200471r05, merging S2-2200749, merging S2-2200749 and S2-2200607. Approved | Approved | |
| 9.18 | S2-2200607 | P-CR | Approval | 23.700-47: Key Issue: 5MBS MOCN network sharing. | Huawei, HiSilicon, CBN | Rel-18 | Merged into S2-2201357 | Robbie (Ericsson) proposes to merge it in S2-2200471. LiMeng (Huawei) agrees to merge into S2-2200471. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.18 | S2-2200903 | P-CR | Approval | 23.700-47: New Key issue: The same Broadcast content over MOCN network sharing. | ZTE | Rel-18 | Merged into S2-2201860 | Robbie (Ericsson) proposes to merge it in S2-2200471. Zhendong (ZTE): is fine to merge this paper into 2200471 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.18 | S2-2200601 | P-CR | Approval | 23.700-47: Discussion and proposal on the solution of MOCN network sharing. | Huawei, HiSilicon, CBN | Rel-18 | r04 agreed. Revised to S2-2201358. | Haris(Qualcomm) provides comments LiMeng (Huawei) provides r02. LaeYoung (LGE) comments. LiMeng (Huawei) replies to Haris (Qualcomm) and provides r01. Robbie (Ericsson) provides r03. LiMeng (Huawei) is fine with r04. Thomas (Nokia) provides r04. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.18 | S2-2201358 | P-CR | Approval | 23.700-47: Discussion and proposal on the solution of MOCN network sharing. | Huawei, HiSilicon, CBN | Rel-18 | Revision of S2-2200601r04. Approved | Approved | |
| 9.18 | - | - | - | WT#2 (AF-triggered join and unicast/multicast selection) | - | - | Docs:=6 | - | |
| 9.18 | S2-2200530 | P-CR | Approval | 23.700-47: Key issue for on demand multicast MBS session triggered by AF. | CATT | Rel-18 | r08 agreed. Revised to S2-2201359, merging S2-2200752, S2-2200531, S2-2200581 and S2-2200888 | Robbie (Ericsson) asks for clarification Zhenhua (vivo) replies to Robbie (Ericsson) Thomas (Nokia) comments that there are five competing key issue proposals for WT#2 and request that only one related key issue is agreed Ask source companies to suggest a baseline to work upon in time before the revision deadline. Thomas(Nokia) replies to Zhenhua and raises concerns that the proposed key issue is rather a solution Xiaoyan (CATT) provides r01, merging other pCRs for WT#2. Robbie (Ericsson) comments. LiMeng (Huawei) provides r02. LaeYoung (LGE) comments. Robbie (Ericsson) asks for clarification. Xiaoyan (CATT) provides r03 to address comments from Robbie (Ericsson) LaeYoung (LGE) provides r04. Robbie (Ericsson) provides r05. Thomas (Nokia) provides r06. Aihua (CMCC) is fine with r06, and suggests S2-2200977 merged into 0530, since both of them address the same issue. Zhenhua (vivo) is fine with r06, and please add 'vivo' as co-source. Fenqin (Huawei) provides r07 Zhenhua (vivo) comments on r07 Thomas (Nokia) provides r08 Fenqin (Huawei) provides response Xiaoyan (CATT) provides r09 Xiaoyan (CATT) provides r10 Thomas (Nokia) prefers r08 Thomas (Nokia) prefers r08 over r10 and suggest to base possible additional revisions on that version Zhenhua (vivo) share the same view with Xiaoyan (CATT) Xiaoyan (CATT) provides r11. ==== 8.X, 9.X, 10.X Revisions Deadline ==== LaeYoung (LGE) is fine with r11. Fenqin (Huawei) can live with r11. Aihua (CMCC) is fine with r11. Thomas(Nokia) still prefers r08, objects against later revisions ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.18 | S2-2201359 | P-CR | Approval | 23.700-47: Key issue for on demand multicast MBS session triggered by AF. | CATT, vivo, China Mobile, Huawei, HiSilicon | Rel-18 | Revision of S2-2200530r08, merging S2-2200752, merging S2-2200752 and S2-2200531, merging S2-2200752, S2-2200531 and S2-2200581, merging S2-2200752, S2-2200531, S2-2200581 and S2-2200888. Approved | Approved | |
| 9.18 | S2-2200531 | P-CR | Approval | 23.700-47: Key issue for selection between multicast and unicast delivery for a service. | CATT | Rel-18 | Merged into S2-2201359 | Thomas (Nokia) comments that there are five competing key issue proposals for WT#2 and request that only one related key issue is agreed Ask source companies to suggest a baseline to work upon in time before the revision deadline. LiMeng (Huawei) suggests to merge this document into S2-2200530. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Xiaoyan (CATT) confirms that S2-2200531 is merged into S2-2200530. ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.18 | S2-2200581 | P-CR | Approval | 23.700-47: Key Issue: On-demand AF triggered MBS session management. | vivo | Rel-18 | Merged into S2-2201359 | Robbie (Ericsson) asks for clarification Zhenhua (vivo) replies to Robbie (Ericsson) Robbie (Ericsson) asks Zhenhua (vivo) Zhenhua (vivo) replise Thomas (Nokia) comments that there are five competing key issue proposals for WT#2 and request that only one related key issue is agreed Ask source companies to suggest a baseline to work upon in time before the revision deadline. Thomas (Nokia) shares the concerns of Robbie LiMeng (Huawei) suggests to merge this document into S2-2200530. Zhenhua (vivo) is OK to merge this document into S2-2200530. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.18 | S2-2200888 | P-CR | Approval | 23.700-47: Key Issue: AF triggered MBS session . | Huawei, HiSilicon | Rel-18 | Merged into S2-2201359 | Robbie (Ericsson) asks for clarification Zhenhua (vivo) propose to merge into S2-2200581 although 888 is a good number Fenqin (Huawei) comments Fenqin (Huawei) Provides feedback Robbie (Ericsson) comments Thomas (Nokia) raises concerns that the key issue is far too solution oriented with respect to the wording of AF triggered join Asks Thomas (Nokia) comments that there are five competing key issue proposals for WT#2 and request that only one related key issue is agreed Ask source companies to suggest a baseline to work upon in time before the revision deadline. LiMeng (Huawei) suggests to merge this document into S2-2200530. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.18 | S2-2200977 | P-CR | Approval | 23.700-47: New KI on AF Triggered MBS Session Management. | China Mobile | Rel-18 | Merged into S2-2201370 | Thomas (Nokia) comments that there are five competing key issue proposals for WT#2 and request that only one related key issue is agreed Ask source companies to suggest a baseline to work upon in time before the revision deadline. LiMeng (Huawei) suggests to merge this document into S2-2200530. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.18 | - | - | - | WT#3 (Group message delivery) | - | - | Docs:=6 | - | |
| 9.18 | S2-2200472 | P-CR | Approval | 23.700-47: New Key Issue: Group Message Delivery via MBS. | Ericsson | Rel-18 | Merged into S2-2201360 | Haris(Qualcomm) provides comments Robbie (Ericson) asks Haris(Qualcomm). Robbie (Ericson) merges it to S2-2200904 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.18 | S2-2200606 | P-CR | Approval | 23.700-47: New KI: Group message delivery of 5MBS. | Huawei, HiSilicon | Rel-18 | Merged into S2-2201360 | Robbie (Ericsson) proposes to merge it in S2-2200904 LiMeng (Huawei) confirms the merging proposal from Robbie (Ericsson). ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.18 | S2-2200904 | P-CR | Approval | 23.700-47: New Key issue: Group message delivery. | ZTE | Rel-18 | r03 agreed. Revised to S2-2201360, merging S2-2200689, S2-2200472, S2-2200606 and S2-2200604 | Robbie (Ericsson) provides r01 which merges S2-2200606 and S2-2200472 Thomas (Nokia) provides r02 LiMeng (Huawei) asks questions and prefers r01. Robbie (Ericsson) provides r03 Thomas (Nokia) can accept r03 Zhendong (ZTE): proposes to move with r03 ==== 8.X, 9.X, 10.X Revisions Deadline ==== Relja (KPN) supports r03 ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.18 | S2-2201360 | P-CR | Approval | 23.700-47: New Key issue: Group message delivery. | ZTE, Ericsson | Rel-18 | Revision of S2-2200904r03, merging S2-2200689, S2-2200472, S2-2200606 and S2-2200604. Approved | Approved | |
| 9.18 | S2-2201207 | P-CR | Approval | 23.700-47: New key issue on coexistance with existing power saving mechanisms for capability-limited devices. | Nokia, Nokia Shanghai-Bell | Rel-18 | r06 agreed. Revised to S2-2201361. | LaeYoung (LGE) provides r01. Thomas (Nokia) provides r02. LaeYoung (LGE) provides r03. Judy (Ericsson) provides r04. LiMeng (Huawei) provides r05. Thomas(Nokia) accepts r03. Judy (Ericsson) provides r07, adding Ericsson as co-source. Thomas (Nokia) accepts r05. Judy (Ericsson) corrects that r06 (instead of r07) is provided. ==== 8.X, 9.X, 10.X Revisions Deadline ==== LaeYoung (LGE) is fine with r06. Haris(Qualcomm) is fine with r06 but there is a typo in the title 'coexistance' instead of 'coexistence'. It can be corrected in final version ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.18 | S2-2201361 | P-CR | Approval | 23.700-47: New key issue on coexistence with existing power saving mechanisms for capability-limited devices. | Nokia, Nokia Shanghai-Bell, LG Electronics, Ericsson | Rel-18 | Revision of S2-2201207r06. Approved | Approved | |
| 9.18 | - | - | - | WT#5 (Large number of UEs in case of Public safety) | - | - | Docs:=5 | - | |
| 9.18 | S2-2200474 | P-CR | Approval | 23.700-47: New Key Issue: Improving multicast performance aspects. | Ericsson | Rel-18 | Merged into S2-2201808 | Thomas (Nokia) questions whether this key issue is really related to WT#5 of the SID and required Judy (Ericsson) believes aspect related to call setup time for public safety with large no. of UEs belongs to WT#5, and asks if Thomas (Nokia) thinks otherwise Judy (Ericsson) corrects the AI to 9.18 in the title. Thomas (Nokia) questions whether this key issue is really related to WT#5 of the SID and required (resending with correct AI) Also answers to Judy Fenqin (Huawei) share similar view as Thomas Judy (Ericsson) responds. Fenqin (Huawei) provides response Judy (Ericsson) provides r01. Judy (Ericsson) ask question Thomas(Nokia) replies to Judy Judy (Ericsson) responds to Thomas(Nokia). Fenqin (Huawei) propose to merge to 0905 Judy (Ericsson) is OK with the merging proposal to move forward, although there is no techncial reason provided during offline discussion. Fenqin (Huawei) responds that it is unclear on the scenario to be solved. Thomas(Nokia) responds to Judy (Ericsson). ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.18 | S2-2200550 | P-CR | Approval | 23.700-47: Key Issue on performance issue for public safety UE (WT #5). | SAMSUNG | Rel-18 | Noted | Robbie (Ericsson) asks for clarification Youngkyo(Samsung) replies Thomas (Nokia) believes that the proposed key issue is not in scope of WT#5 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 9.18 | S2-2200905 | P-CR | Approval | 23.700-47: New Key issue: performance issues for high number of public safety UE. | ZTE | Rel-18 | CC#5: Postponed | Thomas (Nokia) provides r01 Judy (Ericsson) ask if r01 is uploaded. LiMeng (Huawei) suggests to use the email of S2-2201212 as the thread for further discussion. Thomas (Nokia) provides r02 Judy (Ericsson) propose to merge this paper to 0474. Thomas(Nokia) proposes to maintain this contribution and remove key issue from 0474, because 074 also contains a solution proposal Thomas(Nokia) asks to ignore previous comment but suggest to use S2-2200905 as basis instead of S2-2200474 Fenqin (Huawei) provides r03 Judy (Ericsson) provides r04. Fenqin (Huawei) comments and provides r05. Haris(Qualcomm) provides r06 Haris(Qualcomm) corrects typo on email that changed its meaning Thomas(Nokia) provides r07 Haris(Qualcomm) r07 not acceptable since it is focusing on multicast Thomas(Nokia) comments that r07 does not intend to focus on multicast only and provides r08 to further clarify that Judy (Ericsson) provides r09. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Zhendong (ZTE): is fine with r09 Fenqin (Huawei) can accept r09. Haris(Qualcomm) prefers r06, can accept r09 but some small corrections are needed possibly at next meeting Thomas (Nokia) objects against r09, asks to consider r08. Judy (Ericsson) accepts r04, r05 & r09, can live with r06, and objects to other revisions. Thomas (Nokia) objects against r00, r01(empty file), r04, r05, r06, & r09 Suggest postponing and have offline discussions including public safety experts before the next meeting to identify salient points Tao(VC) will use r06 as the agreeable target for further check Fenqin (Huawei) accepts r06. Thomas (Nokia) maintains objection against r06. Suggest postponing issue and offline work with public safety experts before next meeting Judy (Ericsson) asks Thomas (Nokia) once again what is the relevance of unicast signaling in 5MBS in SA2. Judy (Ericsson) propose to bring the discussion to CC#4 or CC#5. ==== 8.X, 9.X, 10.X Final Deadline ==== Ihab Guirguis (FirstNet) accepts r04, r05, or r09 | Postponed |
| 9.18 | S2-2201212 | P-CR | Approval | 23.700-47: WT5: Key Issue and Solution for handling large number of devices in a specific area for public safety. | Qualcomm Inc. | Rel-18 | CC#5: Postponed | Robbie (Ericsson) asks for clarification Thomas(Nokia) suggest to remove key issue proposal from this contribution and only retain solution Has concern that key issue formulation is very focused on the proposed solution. LiMeng (Huawei) provides r01, and considers another way around that we keep the KI description and remove the proposal parts. Robbie (Ericsson) proposes to merge the KI in this paper to 0474. Robbie (Ericsson) comments on the solution in this paper. Haris(Qualcomm) comments Haris(Qualcomm) provides r02 and responds to comments Robbie (Ericsson) comments that he cannot understand the use of GCS AS. Robbie (Ericsson) replies to Haris (Qualcomm). Thomas(Nokia) replies to Robbie (Ericsson) Haris(Qualcomm) provides r03 LiMeng (Huawei) provides r04 Robbie (Ericsson) provides r05 to correct the wording in the EN and points out this solution is dependent on the agreement of KI for WT#5 ==== 8.X, 9.X, 10.X Revisions Deadline ==== LiMeng (Huawei) is fine with r05, and agrees with Robbie that if the KI S2-2200905 cannot be get agreed, this pCR has to be postponed. Haris(Qualcomm) is ok with r05, and agrees w LiMeng and Robbie re the dependency on KI approval Robbie (Ericsson) points out that unfortunately all revisions of this pCR cannot be agreed until agreement reached on associated KI, suggest to discuss in CC#4 or CC#5 together with S2-2200905 ==== 8.X, 9.X, 10.X Final Deadline ==== | Postponed |
| 9.18 | S2-2201221 | P-CR | Approval | 23.700-47: Key Issue: New key issue on improved performance for public safety UEs. | Nokia, Nokia Shanghai-Bell | Rel-18 | Merged into S2-2201808 | Robbie (Ericsson) asks for clarification Robbie (Ericsson) raises concerns against this pCR Haris(Qualcomm) comments Fenqin (Huawei) comments James (AT&T) provides a comment to confirm Nokia's statement in that improving performance for high number of public safety UEs is a very important issue for deployment. Thomas (Nokia) replies to Robbie Robbie (Ericsson) has the same questions as Fenqin (Huawei) and comments Thomas(Nokia) provides r01 to address the comments of Robbie and Fenqin and thanks James for the support Robbie (Ericsson) comments on r01 Fenqin (Huawei) propose to merge to 0905 Thomas (Nokia) replies to Robbie Accepts to merge into 905 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.19 | - | - | - | Study on XR (Extended Reality) and media services (FS_XRM) | - | - | Docs:=78 | - | |
| 9.19 | - | - | - | General (skeleton, scope) | - | - | Docs:=6 | - | |
| 9.19 | S2-2200096 | P-CR | Approval | 23.700-60: FS_XRM TR 23.700-60 skeleton | China Mobile, Huawei | Rel-18 | 23.700-60 TR Skeleton. Approved | ==== 8.X, 9.X, 10.X Final Deadline ==== | Approved |
| 9.19 | S2-2200097 | P-CR | Approval | 23.700-60: Scope of FS_XRM TR | China Mobile,huawei, Tencent | Rel-18 | r07 agreed. Revised to S2-2201802. | Dario (Qualcomm) provides r01 Dan(China Mobile) suggest to update this paper when the 1041 or some definition is stable, and if not stable before the revision deadline, the r00 is suggested to be approved Saso (Intel) comments on r01; prefers r00 Xiaowan (vivo) share the comment with Saso(Intel) and Dan(China Mobile) on r01, prefer r00 Dario (Qualcomm) provides r02 Dan (China Mobile) provides r03 Hui (Huawei) provides comments Dan (China Mobile) provides r04 Dan (China Mobile) provides r05 Dan (China Mobile) provides r06, please ignore r05(some mistake) Dan (China Mobile) provides r07, based on r00 with only replace media units with PDU Set ==== 8.X, 9.X, 10.X Revisions Deadline ==== Dario (Qualcomm) is OK w/ r07 ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.19 | S2-2201802 | P-CR | Approval | 23.700-60: Scope of FS_XRM TR. | China Mobile, Huawei, Tencent | Rel-18 | Revision of S2-2200097r07. Approved | Approved | |
| 9.19 | S2-2201000 | LS OUT | Approval | [DRAFT] LS on QoS support with Media Unit granularity | Intel | Rel-18 | r11 agreed. Revised to S2-2201803, merging S2-2201138 | Xiaowan (vivo) would like to remind XRM fans that there are two LSs unhandled yet Saso (Intel) replies to Xiaowan (vivo) Devaki (Nokia) comments. Hui (Huawei) provides r01. Guillaume (MediaTek Inc.) comments and provides r02. Saso (Intel) replies to Guillaume, Hui, Devaki. Hui (Huawei) provides r04, but prefers to r02 from Guillaume. Dario (Qualcomm) provides r02 Chunshan (CATT) provides r05. Saso (Intel) provides r06. Hui (Huawei) provides r07. Paul (Ericsson) provides comments and r08. Guillaume (MediaTek Inc.) provides r09 Hui (Huawei) provides r10 Saso (Intel) provides r11 ==== 8.X, 9.X, 10.X Revisions Deadline ==== Dario (Qualcomm) OK w/ r11, but attachment 0234 has issues ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.19 | S2-2201803 | LS OUT | Approval | LS on QoS support with PDU Set granularity | SA WG2 | Rel-18 | Revision of S2-2201000r11, merging S2-2201138. Approved | Approved | |
| 9.19 | S2-2201249 | LS OUT | Approval | [DRAFT] LS on Application Data Units | Qualcomm Incorporated | Rel-18 | Merged into S2-2201553 | Xiaowan (vivo) proposes to postpone the LS Dario (Qualcomm) provides r01 Hui (Huawei) suggest to take S2-2201000 as baseline for LS to SA4. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.19 | - | - | - | Architectural Assumption and requirements | - | - | Docs:=4 | - | |
| 9.19 | S2-2201042 | P-CR | Approval | 23.700-60: FS_XRM: Architecture assumption . | ZTE | Rel-18 | Merged into S2-2201804 | Dan (China Mobile) propose to merge this S2-2201042 into S2-2201231 Jinguo(ZTE) agree with the merge ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.19 | S2-2201231 | P-CR | Approval | 23.700-60: Adding architecture assumption and requirement. | T-Mobile USA | Rel-18 | r23 agreed. Revised to S2-2201804, merging S2-2201042 and S2-2201248 | Chris Joul (T-Mobile USA) - provides r01 merging in parts of S2-2200295 and S2-2200426 Jinguo(ZTE) provides r01 with the merge of S2-2201042 Jinguo (ZTE) propose r02 Chris Joul (T-Mobile) - Comments and Thanks Jinguo for correcting an Email error Chris Joul (T-Mobile USA) - provides comments Hui(Huawei) provides r03. Youngkyo(Samsung) questions to Hui(Huawei). Chris Joul (T-Mobile) replies to Youngkyo(Samsung) Hui(Huawei) replies to Youngkyo(Samsung). Chunshan (CATT) provides r04. Jinhua(Xiaomi) provides 1231r05,with comments Boren (OPPO) provides comments. Lei (Tencent) provides r06. John (Futurewei) replies to Boren (OPPO). Dario (Qualcomm) provides r07 James (AT&T) provides comments Huarui (Apple) provides r08. Saso (Intel) seeks clarification on r08. John (Futurewei) comments. Dario (Qualcomm) provides r09 Chris Joul (T-Mobile USA) asks question to Huarui (Apple) Hui(Huawei) provides r10 John (Futurewei) replies to Dario (Qualcomm) Devaki (Nokia) provides r11. Saso (Intel) provides r12. Dan (China Mobile) provides r13 and merge the S2-2200426 into this paper. Jinguo (ZTE) provides r14. Curt (Charter) provides r15. Huarui (Apple) asks a question to Saso (Intel) Xiaowan (vivo) provides r16 Devaki (Nokia) replies to Dario Dario (Qualcomm) provides r20 Sriram (CableLabs) provides r19 Dan (China Mobile) provide r21 to reflect some Shabnam's offline comment Xiaowan (vivo) provides r22 Sriram(CableLabs) provides r23 ==== 8.X, 9.X, 10.X Revisions Deadline ==== Dario (Qualcomm) is OK with r20-23 Jinhua(Xiaomi) replies, r23 is prefer, can live with r20,r21 and r22. Dan (China Mobile) suggest to go with r23 Saso (Intel) is OK with r21, r22 and r23; slight preference for r21. ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.19 | S2-2201804 | P-CR | Approval | 23.700-60: Adding architecture assumption and requirement. | T-Mobile USA, Futurewei, China Mobile, Huawei, Hisilicon, Xiaomi, Tencent, Tencent Cloud, Nokia, Nokia Shanghai Bell, ZTE, Deutsche Telekom | Rel-18 | Revision of S2-2201231r23, merging S2-2201042 and S2-2201248. Approved | Approved | |
| 9.19 | S2-2201248 | P-CR | Approval | 23.700-60: Application Data Unit: architectural assumptions and definition. | Qualcomm Incorporated | Rel-18 | Merged into S2-2201804 | Dan (China Mobile) propose to merge this S2-2201248 into S2-2201231 Mike (InterDigital) comments Dario (Qualcomm) replies to Mike and provides r01 Saso (Intel) comments and proposes to NOTE the paper. Devaki (Nokia) proposes to consider this paper noted or merged with 1231 that is being revised and progressed at the moment. Dario (Qualcomm) OK to merge into 1231. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.19 | - | - | - | Terminology and definitions | - | - | Docs:=2 | - | |
| 9.19 | S2-2201041 | P-CR | Approval | 23.700-60: FS_XRM: Media Unit definition. | ZTE | Rel-18 | CC#5: r29 + changes agreed. Revised to S2-2201851. | Dan (China Mobile) propose to use this paper as baseline version for term definition Dan (China Mobile) agree some part of S2-2200235 would like to give a definition of media unit,but draft as a key issue Xiaowan (vivo) provides comments Mike (InterDigital) asks questions Saso (Intel) proposes a definition for Media Unit; question the need for a 'Group of Media Units' Jinguo(ZTE) replies and provides r01 to add ADU definition. Guillaume (MediaTek Inc.) comments and provides r02. Chunshan (CATT) provides r03 and clarification. Dario (Qualcomm) provides r04 Devaki (Nokia) comments. Mike (InterDigital) comments Hui (Huawei) provides r05. Boren (OPPO) provides r06. Saso (Intel) seeks clarification on r05 and r06. Paul (Ericsson) provides comments and r07. Devaki (Nokia) provides r08 with some refinements on top of r07. Sudeep (Apple) provides r10. Mike (InterDigital) provides r09 Devaki (Nokia) prefers to use r09 as the basis for future revisions. R10 definition is not needed as this is status quo (with PER). Dario (Qualcomm) provides r11. Hui (Huawei) replies to Saso. Hui (Huawei) provides r12. Boren (OPPO) relies to Saso (Intel) and provides comments on r12 Saso (Intel) comments on r12 Saso (Intel) replies to Hui (Huawei). Sudeep (Apple) responds to Devaki (Nokia) and Dario (Qualcomm). Provides r13. Guillaume (MediaTek Inc.) comments. Guillaume (MediaTek Inc.) provides r15 Guillaume (MediaTek) objects to r14 Devaki (Nokia) supports r14. Yali(OPPO) comments on r15 and provides r16. Guillaume (MediaTek Inc.) replies to Yali (OPPO) and provides r17 Yali(OPPO) replies to Guillaume (MediaTek Inc.) . Paul (Ericsson) objects to r17 and provides r18, comments and a question for clarification. Xiaowan (vivo) provides comments on rel18, and provides r19 Saso (Intel) provides r20 Dario (Qualcomm) comments and provide r21 Jinguo(ZTE) provides r21 Hui(Huawei) comments and provide r23. Saso (Intel) replies to Devaki. Paul (Ericsson) provides comments. Guillaume (MediaTek Inc.) agrees with Saso (Intel) wrt importance information. Hui (Huawei) replies. Chris (Vodafone) comments on R23 and proposes a (hopefully) simple definition. Dario (Qualcomm) provides r24. Hui (Huawei) provides r25. Guillaume (MediaTek Inc.) provides r26. Guillaume (MediaTek Inc.) provides the link to r26 Paul (Ericsson) provides comments and r27. Hui (Huawei) asks for clarification on r26 Boren (OPPO) provides r28. Saso (Intel) seeks clarification. Guillaume (MediaTek Inc.) provides r29 Dario (Qualcomm) provides r30 Hui (Huawei) prefers to r29 ==== 8.X, 9.X, 10.X Revisions Deadline ==== Dario (Qualcomm) is not OK with r25-r29; proposes to go with r30. Hui(Huawei) provides comments. Guillaume (MediaTek Inc.) supports r29 only. Devaki (Nokia) prefers to go with r29. Saso (Intel) proposes to go with r29 with addition of an EN providing a pointer to the Wikipedia reference; provides r31 in the DRAFTS folder. Paul (Ericsson) provides comments and proposal. Hui (Huawei) provides proposal. Saso (Intel) provides r33 in DRAFTS Dario (Qualcomm) is not OK w/ r31-33 and provides r34 in DRAFTS. Jinguo(ZTE) is fine with r33 Dario (Qualcomm), for clarity: objects to r31-33, r25-29; Proposes to go with r34 or r30 Guillaume (MediaTek Inc.) is not ok with r34 ==== 8.X, 9.X, 10.X Final Deadline ==== Jinguo(ZTE) asks to discuss at CC#4 | Revised |
| 9.19 | S2-2201851 | P-CR | Approval | 23.700-60: FS_XRM: Media Unit definition. | ZTE, Nokia, Nokia Shanghai Bell, Intel, Huawei, Hisilicon, OPPO, Qualcomm, VIVO, MediaTek Inc. Ericsson | Rel-18 | Revision of S2-2201041r29 + changes.Approved | Approved | |
| 9.19 | - | - | - | WT #1&2.1:multi-modility | - | - | Docs:=8 | - | |
| 9.19 | S2-2200427 | P-CR | Approval | 23.700-60: Key issue for coordination transmission for multi-modality traffic with single UE related with WT1&WT2.1 . | China Mobile | Rel-18 | r17 agreed. Revised to S2-2201805, merging S2-2200552 | Dan (China Mobile) propose to use this paper as baseline version for WT1&2.1 of single UE case LaeYoung (LGE) asks a Q for clarification on r01. Dan (China Mobile) provide r01 for WT1&2.1 of single UE case Hao Dong (ZTE) comments. Dan (China Mobile) provide r03 Jinhua(Xiaomi) provides 0427r02,with comments Mike (InterDigital) provides comments and questions Youngkyo(Samsung) replies to Mike (InterDigital) Dan(China Mobile) replies to Mike (InterDigital) and provide r04 Dario (Qualcomm) provides r05 based on WT1/2.1 wording of the SID. Xiaowan(vivo) comment on r05 Dan(China Mobile) provide r06 Dario (Qualcomm) comments and provides r07 Jinhua(Xiaomi) provides r08, with comments, Mike (InterDigital) provides r09 and comments Devaki (Nokia) provides r12. Dario (Qualcomm) asks to ignore r10 and provides r11 Dario (Qualcomm) provides r10 Youngkyo(Samsung) comments. Jinhua(Xiaomi) replies to Youngkyo, Dan(China Mobile) reply and provide r13 and r14 Hui(Huawei) provides r15 Dario (Qualcomm) provides r16 Devaki (Nokia) comments that r16 is fine, requests to remove ? from Nokia in the subsequent revisions. Dan (China Mobile) provide r17 with only remove the ?in the supporting company ==== 8.X, 9.X, 10.X Revisions Deadline ==== Jinhua(Xiaomi) fine with r17, ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.19 | S2-2201805 | P-CR | Approval | 23.700-60: Key issue for coordination transmission for multi-modality traffic with single UE related with WT1&WT2.1 . | China Mobile, China Telecom, Huawei, Hisilicon, Nokia, Samsung,vivo, Xiaomi, Interdigital Inc, ZTE | Rel-18 | Revision of S2-2200427r17, merging S2-2200552. Approved | Approved | |
| 9.19 | S2-2200429 | P-CR | Approval | 23.700-60: Key issue for coordination transmission for multi-modality traffic among multiple UEs related with WT1&WT2.1 . | China Mobile | Rel-18 | Merged into S2-2201806 | Dan (China Mobile) propose to merge this paper into S2-2200949 for WT1&2.1 of multiple UEs case ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.19 | S2-2200552 | P-CR | Approval | 23.700-60: Key Issue on policy enhancements for supporting multi-modality (WT #1 & 2.1) . | SAMSUNG | Rel-18 | Merged into S2-2201805 and S2-2201806 | Dan (China Mobile) propose to merge this paper into S2-2200427(singel UE)&S2-2200949(multiple UEs) for WT1&2.1 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.19 | S2-2200566 | P-CR | Approval | 23.700-60: TR 23.700-60: Key Issue on policy enhancements for supporting multi-modality synchronization. | China Telecom | Rel-18 | Merged into S2-2201806 | Dan (China Mobile) propose to merge this paper into S2-2200949(multiple UEs) for WT1&2.1 Mengzhen (China Telecom) agree with the merge. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.19 | S2-2200949 | P-CR | Approval | 23.700-60: New Key Issue on Interaction between AF and 5GS for application synchronization and QoS policy coordination among multiple UEs _WT2.1. | Xiaomi, | Rel-18 | r13 agreed. Revised to S2-2201806, merging S2-2200787, S2-2200429, S2-2200566, S2-2200552 and S2-2201070 | Dan (China Mobile) propose to use this paper as baseline for multiple UEs of WT1&2.1 Jinhua(Xiaomi) provides 0949r01,with comments Youngkyo(Samsung) provides r02. Jinhua(Xiaomi) replies to Youngkyo and provides r03, Dario (Qualcomm) provides r04 based on WT1/2.1 wording from the SID. Xiaowan(vivo) comments on r04. Youngkyo(Samsung) comments.. Dario (Qualcomm) provides r05 to address Xiaowan's comments Jinhua(Xiaomi) provides r06, with comments, Dan(China Mobile) provides r08, with comments, please ignore r07 Mengzhen(China Telecom) provides r09, with comments. Mike (InterDigital) provides r10 and comments Devaki (Nokia) provides r12. Dario (Qualcomm) provides r11 Jinhua(Xiaomi) replies to Devaki (Nokia), provides r13 with comments, Jinhua(Xiaomi) replies to Dario, provides r14 with comments, ==== 8.X, 9.X, 10.X Revisions Deadline ==== Jinhua(Xiaomi) agree with r13, and propose r13 for approval, Devaki (Nokia) can accept r13 but objects to r14 (also believes that last bullet is not in scope of the SID). Dan (China Mobile) OK with r13. Dario (Qualcomm) objects to r14 and is OK with r13/12/11. LaeYoung (LGE) thinks that r13 should be checked instead of r14. Xiaowan (vivo) is OK to proceed with r13 Jinhua(Xiaomi) replies to Xiaowan, ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.19 | S2-2201806 | P-CR | Approval | 23.700-60: New Key Issue on Coordinate Transmission for Multi-modal Traffic among multiple UEs _WT1&WT2.1. | Xiaomi, China Mobile, Samsung, China Telecom, InterDigital Inc. ZTE, Huawei, HiSilicon, Nokia, Nokia Shanghai Bell, vivo | Rel-18 | Revision of S2-2200949r13, merging S2-2200787, S2-2200429, S2-2200566, S2-2200552 and S2-2201070. Approved | Approved | |
| 9.19 | S2-2201070 | P-CR | Approval | 23.700-60: WT#1 and WT#2.1: New Key Issue on Identification and Synchronization of Multi-Modal Data. | InterDigital Inc. | Rel-18 | Merged into S2-2201806 | Dan (China Mobile) propose to merge this paper into S2-2200949(multiple UEs) for WT1&2.1 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== Mike (InterDigital) confirms the merge to S2-2200949 | Merged |
| 9.19 | - | - | - | WT #2.2: Exposure | - | - | Docs:=5 | - | |
| 9.19 | S2-2200150 | P-CR | Approval | 23.700-60: KI#X: Exposure of 5GS information/event to the Application to enable the coordination between traffic throughput and network resource usage | vivo | Rel-18 | Merged into S2-2201852 | Dan (China Mobile) propose to merge this paper into S2-2200496 for WT#2.2 Xiaowan (vivo) is OK to merge the pCR into S2-2200496 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.19 | S2-2200496 | P-CR | Approval | 23.700-60: Key Issue on 5GS information exposure for application codec/rate adaptation . | Ericsson | Rel-18 | CC#5: r20 + changes agreed. Revised to S2-2201852, merging S2-2200150 and S2-2200629. | Dan (China Mobile) propose to use this paper as baseline for WT#2.2 Mike (InterDigital) provides r01 Xinpeng(Huawei) provides r02. Paul (Ericsson) replies to Lei (Tencent) and asks questions to Chunshan (CATT). Xiaowan(vivo) comments and provide r06 Xiaowan(vivo) share the view with Lei (Tencent) and provide r05 Xinpeng(Huawei) replies. Xinpeng(Huawei) provides r07. Paul (Ericsson) provides r08 correcting the information direction flow, i.e. from 5GS to application aligned with the WT2.2 that this KI addresses, the description of the KI is abstracted from possible solutions & repeat content removed. Xinpeng(Huawei) objects r08 and provides r09. Saso (Intel) proposes to use r08 as a basis for further updates; objects to r09. Devaki (Nokia) provides r12. Dario (Qualcomm) provides r11 Xinpeng(Huawei) provides r13, and objects to r01, r03, r04, r11. Paul (Ericsson) provides comments and r14 that is based on r13. Xinpeng(Huawei) replies to Paul (Ericsson). Chunshan (CATT) provides r15. Paul (Ericsson) objects to r15. Xiaowan (vivo) provide r16 based on r14 Paul (Ericsson) object to r16. Lei (Tencent) provides r18. Xiaowan(vivo) seek clarification from Paul (Ericsson) Xinpeng(Huawei) is ok for r16 and r18. Paul (Ericsson) replies to Xiaowan(vivo). Kenichi (KDDI) provides r19. Paul (Ericsson) provides r20. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Xinpeng(Huawei) is ok with r14 and r19 (prefer), objects to all other versions. Paul (Ericsson) asks Xinpeng (Huawei) question for clarification. Devaki (Nokia) is fine with r20, wishes to support/cosign the CR as our CR on exposure was also proposed to be merged with this one. Dario (Qualcomm) supports r20 because SA4 needs to be involved. Xinpeng (Huawei) replies to Paul(Ericsson). ==== 8.X, 9.X, 10.X Final Deadline ==== Paul (Ericsson) provides r21, to be finalized in CC#4. Dieter (Deutsche Telekom): we support r20 therefore if we can converge on r21 in CC#4 would be fine. Devaki (Nokia) comments that the Note to coordinate with other WGs cannot be a show stopper to progress the KI. Devaki (Nokia) is fine with r21. Dan (China Mobile) for CC#4, we suggest to go with r21 Xinpeng(Huawei) is not ok with r20, and agree with Devaki (Nokia) removing the NOTE is a good suggestion, we don't need waste time to discuss it here, or we can discuss it next meeting if people would like to spend time on it. | Revised |
| 9.19 | S2-2201852 | P-CR | Approval | 23.700-60: Key Issue on 5GS information exposure for application codec/rate adaptation . | Ericsson, Deutsche Telekom, Huawei, HiSilicon, Tencent, Tencent Cloud, KDDI, CATT, Nokia | Rel-18 | Revision of S2-2200496r20 + changes, merging S2-2200150 and S2-2200629. Approved | Approved | |
| 9.19 | S2-2200629 | P-CR | Approval | 23.700-60: New Key Issue: Enhancements to the Exposure Framework for XR/media Service. | Huawei, HiSilicon | Rel-18 | Merged into S2-2201852 | Dan (China Mobile) propose to merge this paper into S2-2200496 for WT#2.2 Xinpeng(Huawei) agrees to merge 0629 into S2-2200496 for WT#2.2 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.19 | S2-2200771 | P-CR | Approval | 23.700-60: New Key Issue: Exposure of 5GS QoS information and network conditions to the AF. | CATT | Rel-18 | Merged into S2-2201549 | Dan (China Mobile) propose to merge this paper into S2-2200496 for WT#2.2 Chunshan(CATT) agrees to merge this paper into S2-2200496 for WT#2.2 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.19 | - | - | - | WT #3.1-3.3: MU handling | - | - | Docs:=14 | - | |
| 9.19 | S2-2200234 | P-CR | Approval | 23.700-60: Key issue on traffic characteristics of XR and media service . | Lenovo, Motorola Mobility | Rel-18 | CC#5: r05 + changes agreed. Revised to S2-2201807, merging S2-2200908 | Hui (Huawei) proposes to take this paper to discuss how to draft a KI for WT 3.1. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.19 | S2-2201807 | P-CR | Approval | 23.700-60: Key issue on traffic characteristics of XR and media service . | Lenovo, Motorola Mobility, Huawei, HiSilicon, Vivo, CATT | Rel-18 | Revision of S2-2200234r05 + changes, merging S2-2200908. Approved | Approved | |
| 9.19 | S2-2200908 | P-CR | Approval | 23.700-60: Architecture assumptions about media traffic characteristics. | Huawei, HiSilicon | Rel-18 | Merged into S2-2201807 | Hui (Huawei) provides r01. Hui (Huawei) confirms this paper has been merged into S2-2200234. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.19 | S2-2200997 | P-CR | Approval | 23.700-60: Key Issue for WT#3.1, WT#3.2, WT#3.3. | Intel | Rel-18 | Merged into S2-2201774 | Hui (Huawei) proposes to consider this paper as merged. Saso (Intel) comments that a common KI for 3.2 and 3.3 is preferable, but fine to go with the majority view. Lei(Tencent) comments agree with rapporteur and prefer to have separate KIs for 3.2 and 3.3. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Hui(Huawei) confirms that this paper has been merged in S2-2200910. ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.19 | S2-2200235 | P-CR | Approval | 23.700-60: Key issue on QoS enhancement to support media unit granularity . | Lenovo, Motorola Mobility | Rel-18 | Merged into S2-2201808 | Hui (Huawei) proposes to consider this paper as merged into S2-2200910. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.19 | S2-2200910 | P-CR | Approval | 23.700-60: New Key Issue: Media unit integrated packet handling. | Huawei, HiSilicon, KDDI | Rel-18 | r26 agreed. Revised to S2-2201808, merging S2-2200474, S2-2201221, S2-2200235, S2-2201065 and S2-2200296 | Hui (Huawei) take this paper as baseline to discuss KI for WT 3.2. Hui (Huawei) provides r01. Boren (oppo) provides r02. Mike (InterDigital) provides r03 John (Futurewei) requests clarification. Mike (InterDigital) provides r04 and replies to John (Futurewei) Chunshan (CATT) provides r05. Saso (Intel) provides r06. Kenichi (KDDI) provides comments for r06. Mike (InterDigital) provides r07 and replies to Chunshan (CATT) Lei (Tencent) provide r16 on top of r15. John (Futurewei) is fine with r16. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.19 | S2-2201808 | P-CR | Approval | 23.700-60: New Key Issue: PDU Set integrated packet handling. | Huawei, HiSilicon, KDDI, CATT, Ericsson, Futurewei, Intel, InterDigital, Lenovo, Motorola Mobility, Nokia, Nokia Shanghai Bell, OPPO, Tencent, Tencent Cloud, vivo, Deutsche Telekom, China Mobile | Rel-18 | Revision of S2-2200910r26, merging S2-2200474, S2-2201221, S2-2200235, S2-2201065 and S2-2200296. Approved | Approved | |
| 9.19 | S2-2201065 | P-CR | Approval | 23.700-60: Key Issue for QoS framework enhancement based on media unit. | Nokia, Nokia Shanghai Bell | Rel-18 | Merged into S2-2201808 | Hui (Huawei) proposes to consider this paper as merged. Devaki (Nokia) is fine with the merge proposal. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.19 | S2-2200296 | P-CR | Approval | 23.700-60: Key Issue for WT#3 - Differentiated QoS . | Futurewei | Rel-18 | Merged into S2-2201808 | Hui (Huawei) proposes to consider this paper as merged. John (Futurewei) is ok to merge and consider S2-2200774, S2-2200234/S2-2200910 as baselines. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.19 | S2-2200364 | DISCUSSION | Agreement | KI#X: Differentiated QoS handling considering importance of media units . | Tencent, Tencent Cloud | Rel-18 | This should be a P-CR. Merged into S2-2201809 | Hui (Huawei) proposes to consider this paper as merged into S2-2200774. Lei (Tencent) is fine to consider this paper as merged into S2-2200774. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.19 | S2-2200368 | P-CR | Approval | 23.700-60: New KI for differentiated QoS handling. | OPPO | Rel-18 | Merged into S2-2201590 | Hui (Huawei) proposes to consider this paper as merged into S2-2200774. Boren (OPPO) is ok to take S2-2200774 as a baseline for further discussion. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.19 | S2-2200774 | P-CR | Approval | 23.700-60: New Key Issue: The differentiated QoS handling considering different importance of media units. | CATT | Rel-18 | r25 agreed. Revised to S2-2201809, merging S2-2200753, S2-2200751 and S2-2200364 | Hui (Huawei) take this paper as baseline to discuss a KI for WT 3.3. Chunshan (CATT) provides r01. Boren (OPPO) asks for clarification and provides r02. Paul (Ericsson) provides comments in a draft revision in DRAFTS folder. Chunshan (CATT) provides r02 and clarification. Boren (OPPO) provides comments. Chunshan (CATT) provides clarification to Boren (OPPO). Paul (Ericsson) provides comments and r04. John (Futurewei) asks a question to Paul (Ericsson). Chunshan (CATT) provides comments and r05. Saso (Intel) comments on r05. Chunshan (CATT) provides clarification to Saso. Mike (InterDigital) provides r06 Chunshan (CATT) provides r11. Yali (OPPO) replies to Paul (Ericsson) and provides r12. Saso (Intel) provides r13. Dario (Qualcomm) comments and provides r15 Devaki (Nokia) provides r14. Paul (Ericsson) provides comments and r16, we object to r15, r14, r13. Hui (Huawei) provides r17. Paul (Ericsson) asks question for clarification. Hui (Huawei) replies to Paul. John (Futurewei) prefers Media Unit but is ok with PDU group in r17. Chunshan (CATT) provides r18. Paul (Ericsson) replies to Hui (Huawei) and provides r19. Saso (Intel) provides r20. Hui (Huawei) replies to Paul (Ericsson) . Chunshan (CATT) provides r21. Hui (Huawei) provides r22. Chris (Vodafone) provides r23. John (Futurewei) provides r24. Paul (Ericsson) provides comments and r25. John (Futurewei) comments. Paul (Ericsson) replies. John (Futurewei) agrees. Paul (Ericsson) replies to Hui (Huawei). Hui (Huawei) replies to Paul (Ericsson). Devaki (Nokia) comments. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Dario (Qualcomm) comments. Hui(Huawei) suggests go with r25. Lei(Tencent) is fine with r25 and confirm can co-sign. Saso (Intel) agrees with Dario (Qualcomm) that the two KIs (WT#3.2 and WT#3.3) can be merged, but for this meeting is OK with r25. Dario (Qualcomm) for this meeting is OK w/ r25 but thinks that the two KIs should be merged. ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.19 | S2-2201809 | P-CR | Approval | 23.700-60: New Key Issue: The differentiated QoS handling considering different importance of media units. | CATT, Huawei, Hisilicon, Nokia, OPPO, Futurewei, Intel, Tencent, Lenovo, vivo, Ericsson, Interdigital Inc. | Rel-18 | Revision of S2-2200774r25, merging S2-2200753, S2-2200751 and S2-2200364. Approved | Approved | |
| 9.19 | S2-2200911 | P-CR | Approval | 23.700-60: New Key Issue: Media unit differentiated packet handling. | Huawei, HiSilicon | Rel-18 | Merged into S2-2201590 | Hui (Huawei) proposes to consider this paper as merged into S2-2200774. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.19 | - | - | - | WT #3.4: RTT | - | - | Docs:=2 | - | |
| 9.19 | S2-2200153 | P-CR | Approval | 23.700-60: KI#X: Uplink-downlink transmission coordination to meet Round-Trip latency requirements | vivo | Rel-18 | r02 agreed. Revised to S2-2201810. | Xiaowan (vivo) provides r01 Dan (China Mobile) ok to merge S2-2200430 into this paper Dario (Qualcomm) provides r02 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.19 | S2-2201810 | P-CR | Approval | 23.700-60: KI#X: Uplink-downlink transmission coordination to meet Round-Trip latency requirements. | Vivo, China Mobile, Huawei, Tencent | Rel-18 | Revision of S2-2200153r02. Approved | Approved | |
| 9.19 | - | - | - | WT #3.5:Jitter | - | - | Docs:=2 | - | |
| 9.19 | S2-2200366 | P-CR | Approval | 23.700-60: KI#X: Policy enhancement to minimize jitter. | Tencent, Tencent Cloud | Rel-18 | CC#5: r13 + note agreed. Revised to S2-2201853. | Lei (China Mobile) provide r01 to merge 0431 and 0154. Lei (Tencent) provide r01 to merge 0431 and 0154. Dan (China Mobile) confirm to merge S2-2200431 into this paper. Paul (Ericsson) provides comments, r02 and objects to r01. Boren (OPPO) provides comments on r02. Paul (Ericsson) replies. Lei (Tencent) comments and provide r03. Boren (OPPO) comments. Devaki (Nokia) replies to Lei. Lei (Tencent) replies to Devaki(Nokia) clarifies that r04, r05, r06 is inline with WT description. Also provide r08 for further discussion with 'jitter measurement and report to AF' included. Devaki (Nokia) provides r07. Dario (Qualcomm) comments and provide r04 Saso (Intel) comments that jitter measurement is not in scope of WT#3.5; provides r09. Hui(Huawei) withdraws the previous comments and provides r10. Shabnam (Ericsson) provides r11, as we believe we need to first establish the need for this. Lei(Tencent) provide comments and provides r12. Dan(China Mobile) provide r13. Lei(Tencent) provide comments and provides r14. Mike (InterDigital) provides r15 Devaki (Nokia) corrects earlier comment, prefers r15 from Mike. Devaki (Nokia) prefers 14. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Devaki (Nokia) comments. Lei(Tencent) provides comments. Devaki (Nokia) questions the value of the KI without the addition in r15. Dario (Qualcomm) onjects to r15 Dan(China Mobile) reply and suggest to go with r13 Hui (Huawei) prefers r14 but ok with r13. Devaki (Nokia) prefers r15 but ok with r13 in the interest of progress. Dan(China Mobile) Thanks Devaki and reply Xiaowan (vivo) prefers r14 and is also OK to go with r13. Shabnam (Ericsson) Ericsson can only accept r11 or r13 with the last NOTE reinstated on SA4 coordination. Dan(China Mobile) reply to Shabnam Mike (InterDigital) prefers r15. Can live with r13. Suggests a change in r15 in an attempt to make r15 acceptable. Lei(Tencent) provides comments and propose to discuss in CC#4 (r13 as base). Dario (Qualcomm) supports E///'s proposal (r11 or r13 + NOTE) ==== 8.X, 9.X, 10.X Final Deadline ==== Dan (China Mobile) propose to use r13+NOTE in CC4 Dan (China Mobile) suggest to use r13+NOTE for CC#4 discussion Lei (Tencent) agree with the way forward proposed by Dan(China Mobile) and provide r16 which equals r13+NOTE. Request to check before CC#4 to save our online discussion time. Mike (InterDigital) is ok with r16 (r13+note) | Revised |
| 9.19 | S2-2201853 | P-CR | Approval | 23.700-60: KI#X: Jitter minimization. | Tencent, Tencent Cloud, China Mobile, vivo, Huawei, HiSilicon, CATT | Rel-18 | Revision of S2-2200366r13 + note. Approved | Approved | |
| 9.19 | - | - | - | WT #4: Power saving | - | - | Docs:=5 | - | |
| 9.19 | S2-2200155 | P-CR | Approval | 23.700-60: KI#X: Trade-off of QoE and Power Saving Requirements | vivo | Rel-18 | r02 agreed. Revised to S2-2201811. | Hui (Huawei) proposes to take this paper as baseline to discuss the trade-off issue of WT 4. Dario (Qualcomm) is not OK w/ r0 and proposes to take 1064 as baseline. Xiaowan (vivo) provides r01, and propose keep 1)0155 Trade-off of QoE and Power Saving Requirements and 2) 1064 Power Saving separate, since they are different objective. Hui (Huawei) supports r01 Boren (OPPO) provides r02. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.19 | S2-2201811 | P-CR | Approval | 23.700-60: KI#X: Trade-off of QoE and Power Saving Requirements. | vivo | Rel-18 | Revision of S2-2200155r02. Approved | Approved | |
| 9.19 | S2-2200950 | P-CR | Approval | 23.700-60: New Key Issue on Power Management Considering Traffic Pattern of XRM services _WT4. | Xiaomi, | Rel-18 | Merged into S2-2201812 | Hui (Huawei) proposes to merge this paper into S2-2201064. Jinhua(Xiaomi) replies to Hui, merge 0950 into 1064 for further discussion together is OK. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.19 | S2-2201064 | P-CR | Approval | 23.700-60: Enhancements to power savings for XR services. | Nokia, Nokia Shanghai Bell | Rel-18 | r04 agreed. Revised to S2-2201812, merging S2-2200679 and S2-2200950 | Hui (Huawei) proposes to take this paper as baseline to discuss KI for power saving. Jinhua(Xiaomi) replies to Hui, and provides 1064r01 with 0950 merged into. Dario (Qualcomm) comments and provides r02 Devaki (Nokia) is fine with r02. Paul (Ericsson) provides comments and a new r03. Devaki (Nokia) provides r04. Paul (Ericsson) replies. Jinhua(Xiaomi) provides r05, with comments, ==== 8.X, 9.X, 10.X Revisions Deadline ==== Dario (Qualcomm) is OK with r05 Paul (Ericsson) replies to Jinhua (Xiaomi) and indicates preference for r04, objects r05. Devaki (Nokia) requests if we can go with r04 in the interest of progress? Addition proposed in r05 can be discussed for next meeting or as part of solution discussion directly. Dario (Qualcomm) is fine with r04. ==== 8.X, 9.X, 10.X Final Deadline ==== Jinhua(Xiaomi) replies to Devaki, can go with r04 for progress as you suggested | Revised |
| 9.19 | S2-2201812 | P-CR | Approval | 23.700-60: Enhancements to power savings for XR services. | Nokia, Nokia Shanghai Bell, Xiaomi | Rel-18 | Revision of S2-2201064r04, merging S2-2200679 and S2-2200950. Approved | Approved | |
| 9.19 | - | - | - | Documents exceeding quota | - | - | Docs:=30 | - | |
| 9.19 | S2-2200149 | P-CR | Approval | 23.700-60: KI#X: QoS coordination among multiple UEs and multiple QoS flows | vivo | Rel-18 | Not Handled | ==== 8.X, 9.X, 10.X Final Deadline ==== | - |
| 9.19 | S2-2200151 | P-CR | Approval | 23.700-60: KI#X: Enhancement with traffic characteristics of media service enabling improved network resources usage and QoE | vivo | Rel-18 | Not Handled | ==== 8.X, 9.X, 10.X Final Deadline ==== | - |
| 9.19 | S2-2200152 | P-CR | Approval | 23.700-60: KI#X: Media units granularity based QoS | vivo | Rel-18 | Not Handled | ==== 8.X, 9.X, 10.X Final Deadline ==== | - |
| 9.19 | S2-2200154 | P-CR | Approval | 23.700-60: KI#X: Jitter minimization | vivo | Rel-18 | Not Handled | ==== 8.X, 9.X, 10.X Final Deadline ==== | - |
| 9.19 | S2-2200156 | P-CR | Approval | 23.700-60: KI#X: Power Saving Enhancement | vivo | Rel-18 | Not Handled | ==== 8.X, 9.X, 10.X Final Deadline ==== | - |
| 9.19 | S2-2200236 | P-CR | Approval | 23.700-60: Key issue on differentiated QoS handling for XR and media service. | Lenovo, Motorola Mobility | Rel-18 | Not Handled | ==== 8.X, 9.X, 10.X Final Deadline ==== | - |
| 9.19 | S2-2200295 | P-CR | Approval | 23.700-60: Architectural Assumptions and Principles. | Futurewei | Rel-18 | Not Handled | ==== 8.X, 9.X, 10.X Final Deadline ==== | - |
| 9.19 | S2-2200363 | DISCUSSION | Agreement | KI# | Tencent, Tencent Cloud | Rel-18 | Not Handled | ==== 8.X, 9.X, 10.X Final Deadline ==== | - |
| 9.19 | S2-2200365 | DISCUSSION | Agreement | KI#X: Support of UL-DL Coordination to Meet RTT Latency Requirements . | Tencent, Tencent Cloud | Rel-18 | Not Handled | ==== 8.X, 9.X, 10.X Final Deadline ==== | - |
| 9.19 | S2-2200367 | P-CR | Approval | 23.700-60: New KI for media unit granularity QoS. | OPPO | Rel-18 | Not Handled | ==== 8.X, 9.X, 10.X Final Deadline ==== | - |
| 9.19 | S2-2200426 | P-CR | Approval | 23.700-60: Architecture assumptions and requirements of FS_XRM. | China Mobile, Huawei, Tencent | Rel-18 | Not Handled | ==== 8.X, 9.X, 10.X Final Deadline ==== | - |
| 9.19 | S2-2200430 | P-CR | Approval | 23.700-60: Key issue: Support uplink-downlink transmission coordination to meet RTT latency requirement. | China Mobile | Rel-18 | Not Handled | ==== 8.X, 9.X, 10.X Final Deadline ==== | - |
| 9.19 | S2-2200431 | P-CR | Approval | 23.700-60: Key issue: Policy enhancement to minimize the jitter . | China Mobile | Rel-18 | Not Handled | ==== 8.X, 9.X, 10.X Final Deadline ==== | - |
| 9.19 | S2-2200495 | P-CR | Approval | 23.700-60: Key Issue on Application QoS and traffic characteristics awareness in 5GS. | Ericsson | Rel-18 | Not Handled | ==== 8.X, 9.X, 10.X Final Deadline ==== | - |
| 9.19 | S2-2200553 | P-CR | Approval | 23.700-60: Key Issue on Application-aware QoS for XR services (WT #3) . | SAMSUNG | Rel-18 | Not Handled | ==== 8.X, 9.X, 10.X Final Deadline ==== | - |
| 9.19 | S2-2200568 | P-CR | 23.700-60: TR 23.700-60: Key Issue on optimized CDRX for XR and media services. | China Telecom | Rel-18 | Not Handled | ==== 8.X, 9.X, 10.X Final Deadline ==== | - | |
| 9.19 | S2-2200735 | P-CR | Approval | 23.700-60: New Key Issue on Support of Multi-Modality Service. | ZTE | Rel-18 | Not Handled | ==== 8.X, 9.X, 10.X Final Deadline ==== | - |
| 9.19 | S2-2200772 | P-CR | Approval | 23.700-60: New Key Issue: Study the traffic characteristics of media service enabling improved network resources usage and QoE. | CATT | Rel-18 | Not Handled | ==== 8.X, 9.X, 10.X Final Deadline ==== | - |
| 9.19 | S2-2200773 | P-CR | Approval | 23.700-60: New Key Issue: Enhance QoS framework to support media unit granularity. | CATT | Rel-18 | Not Handled | ==== 8.X, 9.X, 10.X Final Deadline ==== | - |
| 9.19 | S2-2200907 | P-CR | Approval | 23.700-60: Definition of Media Unit and video slice. | Huawei, HiSilicon | Rel-18 | Not Handled | ==== 8.X, 9.X, 10.X Final Deadline ==== | - |
| 9.19 | S2-2200909 | P-CR | Approval | 23.700-60: New Key Issue: Supporting QoS handling of multiple QoS Flows serving an application. | Huawei, HiSilicon | Rel-18 | Not Handled | ==== 8.X, 9.X, 10.X Final Deadline ==== | - |
| 9.19 | S2-2200912 | P-CR | Approval | 23.700-60: New Key Issue: Uplink-downlink transmission coordination for RTT latency optimization. | Huawei, HiSilicon | Rel-18 | Not Handled | ==== 8.X, 9.X, 10.X Final Deadline ==== | - |
| 9.19 | S2-2200913 | P-CR | Approval | 23.700-60: New Key Issue on CDRX enhancement with media traffic awareness. | Huawei, HiSilicon | Rel-18 | Not Handled | ==== 8.X, 9.X, 10.X Final Deadline ==== | - |
| 9.19 | S2-2200951 | P-CR | Approval | 23.700-60: New Key Issue on QoS policy coordination among multiple UEs for delivery of related tactile and multi-modal data_WT1. | Xiaomi, | Rel-18 | Not Handled | ==== 8.X, 9.X, 10.X Final Deadline ==== | - |
| 9.19 | S2-2200952 | P-CR | Approval | 23.700-60: New Key Issue on support for delivery of related tactile and multi-modal data. | Xiaomi, | Rel-18 | Not Handled | ==== 8.X, 9.X, 10.X Final Deadline ==== | - |
| 9.19 | S2-2200954 | P-CR | Approval | 23.700-60: New Key Issue on Time Synchronization for Delivery of Related Tactile and Multi-modal Data_WT1. | Xiaomi, | Rel-18 | Not Handled | ==== 8.X, 9.X, 10.X Final Deadline ==== | - |
| 9.19 | S2-2200953 | P-CR | Approval | 23.700-60: New Key Issue on support for exposure of 5GS QoS information and network conditions to the XRM Application_WT2.2. | Xiaomi, | Rel-18 | Not Handled | ==== 8.X, 9.X, 10.X Final Deadline ==== | - |
| 9.19 | S2-2201062 | P-CR | Approval | 23.700-60: Key Issue for Multi-modality service and policy enhancements. | Nokia, Nokia Shanghai Bell | Rel-18 | Not Handled | ==== 8.X, 9.X, 10.X Final Deadline ==== | - |
| 9.19 | S2-2201063 | P-CR | Approval | 23.700-60: Exposure of 5GS QoS capabilities and network conditions. | Nokia, Nokia Shanghai Bell | Rel-18 | Not Handled | ==== 8.X, 9.X, 10.X Final Deadline ==== | - |
| 9.19 | S2-2201074 | P-CR | Approval | 23.700-60: WT#3.2 and WT#3.3: New Key Issue on Improved QoS Granularity. | InterDigital Inc. | Rel-18 | Not Handled | ==== 8.X, 9.X, 10.X Final Deadline ==== | - |
| 9.20 | - | - | - | Study on Ranging based services and sidelink positioning (FS_Ranging_SL) | - | - | Docs:=30 | - | |
| 9.20 | - | - | - | Work plan | - | - | Docs:=1 | - | |
| 9.20 | S2-2201106 | DISCUSSION | Information | FS_Ranging_SL Work Plan | Xiaomi | Rel-18 | Noted | ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 9.20 | - | - | - | TR skeleton, scope,etc | - | - | Docs:=7 | - | |
| 9.20 | S2-2201108 | P-CR | Approval | 23.700-86: FS_Ranging_SL TR skeleton | Xiaomi | Rel-18 | 23.700-86 TR Skeleton. r01 agreed. Revised to S2-2201607. | LaeYoung (LGE) provides comment. Sherry (Xiaomi) provides r01. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.20 | S2-2201607 | P-CR | Approval | 23.700-86: Skeleton of FS_Ranging_SL TR. | Xiaomi | Rel-18 | Revision of S2-2201108r01. Approved | Approved | |
| 9.20 | S2-2201109 | P-CR | Approval | 23.700-86: Proposed TR Scope. | Xiaomi | Rel-18 | Approved | ==== 8.X, 9.X, 10.X Final Deadline ==== | Approved |
| 9.20 | S2-2201110 | P-CR | Approval | 23.700-86: Proposal on Definition and Abbreviations. | Xiaomi | Rel-18 | r07 agreed. Revised to S2-2201608. | LaeYoung (LGE) provides comments. Sherry (Xiaomi) provides r01 and replies to LaeYoung. LaeYoung (LGE) replies to Sherry (Xiaomi). Hong (Qualcomm) replies to Laeyoung. LaeYoung (LGE) replies to Hong (Qualcomm) and LiMeng (Huawei). LiMeng (Huawei) wonders if SL positioning should be aligned with RAN. Sherry (Xiaomi) provides r02. Walter Dees (Philips) suggests improvements to the definitions Sherry (Xiaomi) provides r03. LaeYoung (LGE) comments. Sherry (Xiaomi) provides r04. Walter (Philips) comments on r04 that it removed all edits made in r03, and provides r05 Hong (Qualcomm) comments. Sherry (Xiaomi) comments and provides r06. Walter (Philips) provides r07. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Sherry (Xiaomi) is fine with r07. ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.20 | S2-2201608 | P-CR | Approval | 23.700-86: Proposal on Definition and Abbreviations. | Xiaomi | Rel-18 | Revision of S2-2201110r07. Approved | Approved | |
| 9.20 | S2-2201111 | P-CR | Approval | 23.700-86: Proposed Architecture Assumptions and Requirements. | Xiaomi | Rel-18 | r07 agreed. Revised to S2-2201609. | Lars (Sony) comments. LaeYoung (LGE) comments. Sherry (Xiaomi) provides r01. Saad (Interdigital) comments on r01. Sherry (Xiaomi) provides r02. Hong (Qualcomm) provides r03. Yunjing (CATT) asks questions for clarification. Sherry (Xiaomi) replies to Yunjing. Hong (Qualcomm) comments on r04. Sherry (Xiaomi) provides r05. Walter (Philips) provides r06. Saad (Interdigital) comments on r06 Sherry (Xiaomi) provides r07. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.20 | S2-2201609 | P-CR | Approval | 23.700-86: Proposed Architecture Assumptions and Requirements. | Xiaomi | Rel-18 | Revision of S2-2201111r07. Approved | Approved | |
| 9.20 | - | - | - | WT#1.1 Authorization and Policy/Parameter provisioning | - | - | Docs:=3 | - | |
| 9.20 | S2-2200710 | P-CR | Approval | 23.700-86: KI#X: Authorization and Policy/Parameters Provisioning to UE for Ranging and sidelink positioning. | vivo | Rel-18 | Merged into S2-2201610 | Sherry (Xiaomi) proposes to merge this paper into 00965. Wen (vivo) is ok to merge this paper into 00965. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.20 | S2-2200965 | P-CR | Approval | 23.700-86: Key Issue: Support of authorisation, policy and parameter provisioning for ranging services. | Huawei, HiSilicon | Rel-18 | r05 agreed. Revised to S2-2201610, merging S2-2200710 | Sherry (Xiaomi) provides r01 Sherry (Xiaomi) provides r02 LiMeng (Huawei) replies. Wen (vivo) comments and provides r03. Fei (OPPO) asks questions and comments on r03. Lars (Sony) asks questions. Hong (Qualcomm) comments. LiMeng (Huawei) provides r04. LaeYoung (LGE) provides comment. Wen (vivo) replies to LiMeng (Huawei). Sherry (Xiaomi) provides r05. Wen (vivo) is ok with r05. Fei (OPPO) is ok with r05. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.20 | S2-2201610 | P-CR | Approval | 23.700-86: Key Issue: Support of authorisation, policy and parameter provisioning for ranging services. | Huawei, HiSilicon, Xiaomi, vivo | Rel-18 | Revision of S2-2200965r05, merging S2-2200710. Approved | Approved | |
| 9.20 | - | - | - | WT#1.3 discovery and service operation procedures | - | - | Docs:=9 | - | |
| 9.20 | S2-2200711 | P-CR | Approval | 23.700-86: KI#X: Ranging devices discovery. | vivo | Rel-18 | Merged into S2-2201612 | Sherry (Xiaomi) comments. Wen (vivo) replies. Sherry (Xiaomi) replies. Walter Dees (Philips) requests if S2-2201139 and S2-2200711 could be merged Wen(vivo) is ok to merge these 2 papers LaeYoung (LGE) also proposes to merge this paper into S2-2201139. Cai Simon (Nokia) suggests merging this paper to S2-2201139 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.20 | S2-2200963 | P-CR | Approval | 23.700-86: Key Issue: Ranging service procedure between two UEs. | Huawei, HiSilicon | Rel-18 | Merged into S2-2201613 | Sherry (Xiaomi) comments. LiMeng (Huawei) replies. Hong (Qualcomm) comments. Sherry (Xiaomi) proposes to merge this paper into 1158. ==== 8.X, 9.X, 10.X Revisions Deadline ==== LiMeng (Huawei) confirms it will be merged into 1158. ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.20 | S2-2200964 | P-CR | Approval | 23.700-86: Key Issue: Ranging service procedure with the assistance of another UE. | Huawei, HiSilicon | Rel-18 | r03 agreed. Revised to S2-2201611. | Sherry (Xiaomi) provides r01. Hong (Qualcomm) comments on r01. LiMeng (Huawei) provides r02. Sherry (Xiaomi) provides r03. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.20 | S2-2201611 | P-CR | Approval | 23.700-86: Key Issue: Ranging service procedure with the assistance of another UE. | Huawei, HiSilicon | Rel-18 | Revision of S2-2200964r03. Approved | Approved | |
| 9.20 | S2-2201114 | P-CR | Approval | 23.700-86: Proposed new KI on Service Operation. | Xiaomi | Rel-18 | Merged into S2-2201613 | Saad (InterDigital) comments and asks a clarification question Sherry(Xiaomi) replies to Saad. Saad (Interdigital) is ok to merge this paper to 1158 LaeYoung (LGE) also proposes to merge this paper into other paper, e.g. S2-2201158. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Sherry (Xiaomi) is ok to merge this paper to 1158 ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.20 | S2-2201139 | P-CR | Approval | 23.700-86: New KI on Ranging device discovery . | Nokia, Nokia Shanghai Bell | Rel-18 | r05 agreed. Revised to S2-2201612, merging S2-2200711 | Sherry (Xiaomi) provides r01 Cai Simon (Nokia) objects to the revision Sherry (Xiaomi) replies. Cai Simon (Nokia) replies to Sherry (Xiaomi) Walter Dees (Philips) requests if S2-2201139 and S2-2200711 could be merged Sherry (Xiaomi) comments. Sherry (Xiaomi) provides r02. Yunjing(CATT) provides comment. Cai Simon (Nokia) further clarifies and provides r03 Cai Simon (Nokia) clarifies to Yunjing (CATT) and provides r03 Wen (vivo) comments on r03 Cai Simon (Nokia) accepts the comment and provides r04 Sherry (Xiaomi) provides r05. Cai Simon (Nokia) accepts r05 Wen (vivo) is ok with r05 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.20 | S2-2201612 | P-CR | Approval | 23.700-86: New KI on Ranging device discovery . | Nokia, Nokia Shanghai Bell, Xiaomi | Rel-18 | Revision of S2-2201139r05, merging S2-2200711. Approved | Approved | |
| 9.20 | S2-2201158 | P-CR | Approval | 23.700-86: TR 23.700-86: New key issue on RAT independent control signalling . | Qualcomm Incorporated | Rel-18 | r11 agreed. Revised to S2-2201613, merging S2-2200963 and S2-2201114 | Sherry (Xiaomi) provides r01 and askes some questions. Hong (Qualcomm) replies to Sherry. LiMeng (Huawei) asks whether the KI has RAN impact. Hong (Qualcomm) replies to Li Meng. Sherry (Xiaomi) comments. LiMeng (Huawei) asks questions. Hong (Qualcomm) replies to LiMeng. Yunjing(CATT) provides comments. Sherry (Xiaomi) provides r02 and proposes to merge 1114 and 0968 into this paper. Walter (Philips) has concerns on this KI. Hong (Qualcomm) replies to Yunjing. Hong (Qualcomm) comments. LiMeng (Huawei) provides r02 follows the suggestion by Rapporteur, and remove the parts that people may have concern. Sherry (Xiaomi) provides r03. Sherry (Xiaomi) comments that r02 was already provided by Xiaomi. Hong (Qualcomm) comments and is fine with the r03 provided by Xiaomi. LiMeng (Huawei) provides r04, and confirms r02 was provided by Xiaomi. Cai Simon (Nokia) provides comments Cai Simon (Nokia) provides r06 based on comments Hong (Qualcomm) provides r05. Hong (Qualcomm) provides r07. Walter (Philips) prefers r06 over r05. LiMeng (Huawei) comments on r07. Cai Simon (Nokia) provides r08 Hong (Qualcomm) replies to Walter. Sherry (Xiaomi) provides r09. LiMeng (Huawei) comments. Sherry (Xiaomi) provides r10. LiMeng (Huawei) provides r11. Hong (Qualcomm) is fine with r11. Cai Simon provides r12 ==== 8.X, 9.X, 10.X Revisions Deadline ==== Sherry (Xiaomi) is fine with both r11 and r12. LiMeng (Huawei) prefers r11 and comments against to r10. LiMeng (Huawei) corrects the previous comment: prefers r11 and comments against to r12. LiMeng (Huawei) replies to Sherry, corrects that the comment is to r12, and is Okay with r11. Hong (Qualcomm) is fine with r10, r11, and r12. Cai Simon agrees with Hong (Qualcomm) ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.20 | S2-2201613 | P-CR | Approval | 23.700-86: TR 23.700-86: New key issue on RAT independent control signalling . | Qualcomm Incorporated, Xiaomi, Huawei, HiSilicon | Rel-18 | Revision of S2-2201158r11, merging S2-2200963, merging S2-2200963 and S2-2201114. Approved | Approved | |
| 9.20 | - | - | - | WT#1.5 service exposure | - | - | Docs:=8 | - | |
| 9.20 | S2-2200674 | P-CR | Approval | 23.700-86: KI for Sidelink positioning for Partial Network Coverage. . | Sony | Rel-18 | r15 agreed. Revised to S2-2201614. | Sherry (Xiaomi) comments. Hong (Qualcomm) comments. Lars (Sony) provides r01. Sherry (Xiaomi) provides r02. Lars (Sony)comments on r02. Sherry (Xiaomi) replies to Lars. Lars (Sony) replies to Sherry Lars (Sony) provides r03 Sherry (Xiaomi) provides r04. Lars (Sony) provides r05. Hong (Qualcomm) provides r07, as there is already r06 provided. Hong (Qualcomm) provides r06. Saad (Interdigital) provides r06. Wen (vivo) seeks clarifications. Lars (Sony) responds. Lars (Sony) responds to Yunjing (CATT). Yunjing (CATT) provides comments. Sherry (Xiaomi) further comments. Wen (vivo) replies. Lars (Sony) responds to Wen (vivo). Sherry (Xiaomi) provides r08. Lars (Sony) provides r09. Ming (CATT) provides r10 and ask for clarifications. Lars (Sony) comments. R10 looks ok Sherry (Xiaomi) provides r11. Runze (Huawei) provides R12. Sherry (Xiaomi) provides r13. Runze (Huawei) accepts r13. Lars (Sony) provides r14. Runze (Huawei) comments on r14. Lars (Sony) responds to Runze (Huawei) Ming (CATTS) provides r15. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Sherry (Xiaomi) is fine with r15. Lars (Sony) is fine with r15. Runze (Huawei) clarifies the question to Lars (Sony). ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.20 | S2-2201614 | P-CR | Approval | 23.700-86: KI for Sidelink positioning for Partial Network Coverage. . | Sony, Xiaomi | Rel-18 | Revision of S2-2200674r15. Approved | Approved | |
| 9.20 | S2-2200712 | P-CR | Approval | 23.700-86: KI#X: Ranging and sidelink positioning service exposure to a UE. | vivo | Rel-18 | r04 agreed. Revised to S2-2201615, merging S2-2201222 and S2-2201223 | Sherry (Xiaomi) comments. Hong (Qualcomm) comments. Wen (vivo) replies and provides r01. Sherry (Xiaomi) provides r02. Leo (Deutsche Telekom) has concerns with supporting deferred and periodic requests. Wen (vivo) replies and provides r03. Leo (Deutsche Telekom) comments on r03. Sherry (Xiaomi) provides r03. Sherry (Xiaomi) provides r04. Leo (Deutsche Telekom) is fine with r04. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Sherry (Xiaomi) prefers r02 and can live with r04. Wen (vivo) is ok with both r02 and r04. Leo (Deutsche Telekom) prefers r04, and suggests to improve the wording at SA2#150. ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.20 | S2-2201615 | P-CR | Approval | 23.700-86: KI#X: Ranging and sidelink positioning service exposure to a UE. | Vivo, Xiaomi | Rel-18 | Revision of S2-2200712r04, merging S2-2201222, merging S2-2201222 and S2-2201223. Approved | Approved | |
| 9.20 | S2-2200713 | P-CR | Approval | 23.700-86: KI#X: Ranging and sidelink positioning service exposure to application server. | vivo | Rel-18 | r03 agreed. Revised to S2-2201616. | Sherry (Xiaomi) comments. Lars (Sony) comments. Hong (Qualcomm) comments. Wen (vivo) replies and tries to provide r01. Sherry (Xiaomi) replies to Hong. Wen (vivo) has a question. Lars (Sony) responds to Wen (vivo). Wen (vivo) replies. Sherry (Xiaomi) replies to Wen. Sherry (Xiaomi) provides r02. Leo (Deutsche Telekom) provides comments. Wen (vivo) replies and provides r03. Leo (Deutsche Telekom) is fine with S2-2200713r03. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Sherry (Xiaomi) prefers r02 and can live with r03. ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.20 | S2-2201616 | P-CR | Approval | 23.700-86: KI#X: Ranging/Sidelink Positioning service exposure for network assisted measurement management. | Vivo, Xiaomi | Rel-18 | Revision of S2-2200713r03. Approved | Approved | |
| 9.20 | S2-2200966 | P-CR | Approval | 23.700-86: Key Issue: Ranging and sidelink positioning service exposure. | Huawei, HiSilicon | Rel-18 | Merged into S2-2201336 | Sherry (Xiaomi) comments. Lars (Sony) comments. Hong (Qualcomm) comments. LiMeng (Huawei) replies. LaeYoung (LGE) clarifies that Lars (Sony) provided r01 with incorrect zip file name, i.e. S2-2200996r01.zip instead of S2-2200966r01.zip. Anyhow the included docx file is correct (i.e. S2-2200966r01...docx). So, just zipped the docx file from Lars (Sony) to S2-2200966r01.zip and uploaded it to the server. Sherry (Xiaomi) proposes to merge this paper into either 0712 or 0713. LiMeng (Huawei) is fine with Rapporteur's merging proposal, proposes to merge into 0712. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.20 | S2-2201115 | P-CR | Approval | 23.700-86: Proposed new KI on Service Exposure. | Xiaomi | Rel-18 | Merged into S2-2201752 | Sherry (Xiaomi) proposes to merge this paper into either 0712 or 0713. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Sherry (Xiaomi) confirms to merge it into 0712. ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.20 | - | - | - | Not handled | - | - | Docs:=2 | - | |
| 9.20 | S2-2201112 | P-CR | Approval | 23.700-86: Proposed new KI on Authorization and policy/parameter provisioning. | Xiaomi | Rel-18 | Not Handled | ==== 8.X, 9.X, 10.X Final Deadline ==== | - |
| 9.20 | S2-2201113 | P-CR | Approval | 23.700-86: Proposed new KI on Observer UE and Target UE discovery. | Xiaomi | Rel-18 | Not Handled | ==== 8.X, 9.X, 10.X Final Deadline ==== | - |
| 9.21 | - | - | - | Study on System Support for AI/ML-based Services (5G_AIMLsys) | - | - | Docs:=50 | - | |
| 9.21 | - | - | - | General (skeleton, scope) | - | - | Docs:=4 | - | |
| 9.21 | S2-2200172 | P-CR | Approval | 23.700-80: FS_AIMLsys TR 23.700-80 Skeleton | Samsung, OPPO | Rel-18 | 23.700-80 TR Skeleton. r03 agreed. Revised to S2-2201813. | Yannick (Nokia): Nokia provides suggestions for revision. David (Samsung) provides r01, replies to Nokia's comments. LaeYoung (LGE) comments on the TR title. David (Samsung) thanks LaeYoung for the comment, replies. Yannick (Nokia): Nokia would like that TR 23.700-80 title clearly indicates this is about 5G system support for AI/ML-based services and provide r02. LaeYoung (LGE) provides comment to David (Samsung) that currently '5G' exists in the SID title in the workplan sheet/3GU as well as the TR title in the 3GPP portal. David (Samsung) replies to LGE. David (Samsung) provides r03. Yannick (Nokia): Nokia is fine with r03. Malla (NTT DOCOMO) asks question on r03 from David (Samsung). Malla (NTT DOCOMO) withdraws an earlier comment on r03 to David (Samsung). ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.21 | S2-2201813 | P-CR | Approval | 23.700-80: FS_AIMLsys TR 23.700-80 Skeleton | Samsung, OPPO | Rel-18 | Revision of S2-2200172r03. Approved | Approved | |
| 9.21 | S2-2200118 | P-CR | Approval | 23.700-80: Scope for FS_AIMLsys | OPPO, Samsung | Rel-18 | r03 agreed. Revised to S2-2201814. | Antoine (Orange) can't parse the first 2 §. Tricci (OPPO) thanks Antoine (Orange) comment and provides feedback. Yannick (Nokia): Nokia provides r01. Antoine (Orange) prefers r01. Tricci (OPPO) thanks Yannick (Nokia) to provide r01 and is okay with r01. Yannick (Nokia): Nokia provides r02. Tricci (OPPO) thanks Yannick (Nokia) to provide r02 and it is okay with r02. Zhang (Ericsson) provides r03 and co-sign Tricci (OPPO) thanks Zhang (Ericsson) kind support. The changes look good... ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.21 | S2-2201814 | P-CR | Approval | 23.700-80: Scope for FS_AIMLsys. | OPPO, Samsung, Ericsson | Rel-18 | Revision of S2-2200118r03. Approved | Approved | |
| 9.21 | - | - | - | Architectural Assumption and requirements | - | - | Docs:=2 | - | |
| 9.21 | S2-2200166 | P-CR | Approval | 23.700-80: Architectural assumptions. | CATT | Rel-18 | r18 agreed. Revised to S2-2201815. | Megha(Intel) provides r01 and comments. Tricci (OPPO) provides r02 Xiaoyan (CATT) disagrees with r01 and asks for clarifications from Megha(Intel). Xiaoyan (CATT) provides comments to r02. Tricci (OPPO) thanks Xiaoyan (CATT) for feedback and would like to ask for clarifications. Zhang (Ericsson) provides comments on r02 Tricci (OPPO) thanks Zhang (Ericsson) comments and provides feedback. David (Samsung) provides r03 and comments Tricci (OPPO) thanks David (Samsung) comments and provides r04 Yannick (Nokia): Nokia provides r05. Malla (NTT DOCOMO) asks clarifications. David (Samsung) provides r06 and comments. Tricci (OPPO) thanks Yannick (Nokia) and David (Samsung) for proposing a way forward. As a compromise, a revision r07 is proposed by OPPO. Yannick (Nokia): Nokia comments on the new text in r07 which is going too far into solution space. Malla (NTT DOCOMO) provided r08. David (Samsung) agrees with Nokia's proposal David (Samsung) provides r09. Tricci (OPPO) cannot agree with Yannick's suggestion as this does not add anything to address OPPO's concern. OPPO proposes another way forward. Chien-Sheng (MediaTek) provides r10. Tricci (OPPO) continues to raise the concern for lacking of a well defined scope on how to allow 5GC to be aware of the Application Layer AI/ML operation. David (Samsung) comments on Tricci's proposal. Yannick (Nokia): Nokia prefers to just put an editor's note. Tricci (OPPO) thanks David (Samsung) for his suggestion and provide OPPO's feedback. David (Samsung) comments. Tricci (OPPO) thanks David (Samsung) for his further feedback. Tricci (OPPO) provides r11 to capture the interim agreed proposed text to discuss further on the 5GC awareness of the Application layer AI/ML operation. Yannick (Nokia): Nokia prefers to just put an editor's note. Provide r12. Zhang (Ericsson) prefer r12 David (Samsung) can live with r12 Megha(Intel) prefers r12 and provides comments. Tricci (OPPO) thanks Megha(Intel) comments and provides feedback. David (Samsung) supports the view from Tricci (OPPO). Tricci (OPPO) thanks Malla (NTT DoCoMo) suggestion, however, OPPO cannot agree with such Architecture assumption. Malla (NTT DOCOMO) pointed out that based on S2-2200167 discussion, I suggest adding this text 'Neither Uu nor any AN impacts are in the scope of this study' to the assumption. David (Samsung) provides feedback to Megha (Intel). Tricci (OPPO) provides r13 to correct the typo highlighted in blue as shown. Yannick (Nokia): Nokia provides r14. Xiaoyan (CATT) provides r15. Tricci (OPPO) cannot accept Xiaoyan (CATT) r15 revision as CATT's argument is incorrect and the integrity of 5G system is fundamental to enable any service. Antoine (Orange) agrees with Tricci and provides r16. Yannick (Nokia): Nokia provides r17. David (Samsung) provides r18. Tricci (OPPO) proposes r19 and r20 revisions to address the UE member terminology as the general assumptions. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Tricci (OPPO) would like to clarify that r20 was uploaded by mistake and would like to withdraw r20. Chien-Sheng (MediaTek) needs the clarification on type added by Nokia. We also think this EN is not needed since anyway the work is contribution-driven. Thanks. Yannick (Nokia): Nokia suggests going forward with r18. Objects to r19. Yannick (Nokia): Nokia replies to MediaTek. David (Samsung) supports keeping the EN and approving r18. Tricci (OPPO) suggests to go forward with r19 or moves this into the 'Terms' clause as kindly suggested by Ericsson. OPPO asks Yannick (Nokia) for further clarifications for his concerns. David (Samsung) provides comments to Tricci. Tricci (OPPO) considers David (Samsung) suggestion and can live with r18 as a way forward. Yannick (Nokia): Nokia replies to Oppo (Tricci). Yannick (Nokia): Nokia is fine with Samsung (David) suggestion, and thanks Oppo (Tricci) for willingness to compromise and live with r18. Megha (Intel) is ok with r18. ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.21 | S2-2201815 | P-CR | Approval | 23.700-80: Architectural assumptions. | CATT, OPPO, Samsung, Nokia, Nokia Shanghai Bell, Ericsson, MediaTek, Intel | Rel-18 | Revision of S2-2200166r18. Approved | Approved | |
| 9.21 | - | - | - | Generic Key Issue | - | - | Docs:=1 | - | |
| 9.21 | S2-2200119 | P-CR | Approval | 23.700-80: New Generic Key Issue: 5GS Assistance for Member Selection for Application AI/ML Training | OPPO | Rel-18 | Postponed | Megha(Intel) provides a few comments and asks questions for clarification. Tricci (OPPO) thanks Megha(Intel) comments and provides inline feedback below. Zhang (Ericsson) ask for clarification Chien-Sheng (MediaTek) provides r01 and comments. Chien-Sheng (MediaTek) corrects the link for r01. David (Samsung) asks Chien-Sheng (MediaTek) for r01 in ZIP format David (Samsung) provides r02 Tricci (OPPO) would like to provide Zhang (Ericsson) further clarifications. Zhang (Ericsson) provides comments Tricci (OPPO) thanks Zhang (Ericsson) with more specific comments and provides feedback. Megha(Intel) provides further comments.. Chien-Sheng (MediaTek) thanks David and provides r04. Malla (NTT DOCOMO) asks for clarification. Yannick (Nokia): Nokia do not understand why we need this key issue. Tricci (OPPO) thanks comments from Malla (NTT DOCOMO) and Yannick (Nokia) and provides some feedback. Tricci (OPPO) provides r05 to address comments from Malla (NTT DOCOMO) and from Zhang (Ericsson ). David (Samsung) thanks Tricci for the new revision, provides r06. Tricci (OPPO) thanks Chien-Sheng (MediaTek) clarification and provides further feedback. Chien-Sheng (MediaTek) thanks Tricci and provides clarification. Chien-Sheng (MediaTek) thanks Tricci's clarification and is ok now. Yingying(CATT) provides comments. Tricci (OPPO) thanks Yingying(CATT) comments and provides r07 that address some of the comments. David (Samsung) objects to r07 and comments. Tricci (OPPO) respectfully disagrees with David (Samsung) comments and would like to suggest a way forward. Zhang (Ericsson) provides r08 Tricci (OPPO) thanks Zhang (Ericsson) comments and revision, unfortunately, r06 is NOT acceptable. David (Samsung) does not think the proposed way forward helps. Yannick (Nokia): Nokia requests for clarification. Megha(Intel) provides few comments.. Tricci (OPPO) responds to Zhang (Ericsson) question. Tricci (OPPO) responds to Yannick (Nokia) questions. Please see responses inline below. Tricci (OPPO) thanks Megha(Intel) comments and provides feedback. Juan Zhang (Qualcomm) provides comments. Yingying(CATT) asks for clarification, provides and co-sign r09 which is on top of r07. Zhang (Ericsson) object r09 and ask for clarification Yannick (Nokia): Nokia comments on second bullet. Tricci (OPPO) responds to Zhang (Ericsson) for his questions. Tricci (OPPO) thanks Juan Zhang (Qualcomm) comments and provides feedback. Tricci (OPPO) provides feedback to Yannick (Nokia) question on second bullet. Tricci (OPPO) thanks Antoine (Orange) comments and provides responses as well r10 version. Antoine (Orange) asks what the 2nd bullet adds compared to the 1st one. Tricci (OPPO) provides r11 to remove the level 3 clause header '5.X.1 Description' and also some old inserted comments which are not needed. Tricci (OPPO) thanks Zhang (Ericsson) provides kind feedback. Hoping that the latest updated version is acceptable to Zhang. Yannick (Nokia): Nokia comments on r11, does not understand the difference between second bullet and what is going to be studied in key issue related to objective 1.b. Zhang (Ericsson) provides r12 David (Samsung) provides r13. Tricci (OPPO) thanks Zhang (Ericsson) provides r12 and is okay with r12. Malla (NTT DOCOMO) provides r14. Yannick (Nokia): Nokia is concerned about the lack of clarity for this key issue description, as well as about potential overlap with other key issues. Tricci (OPPO) provides feedback to Yannick (Nokia) to address his comments. Juan Zhang (Qualcomm) provides r15. Tricci (OPPO) thanks Malla (DoCoMo) and Juan Zhang (Qualcomm) proposed revisions. OPPO provides r16 to correct the first change. Tricci (OPPO) provides further comment on r16. Yannick (Nokia): Nokia replies to Oppo (Tricci). Tricci (OPPO) thanks Yannick (Nokia) for further responses and OPPO would like to provide further clarifications. Chien-Sheng (MediaTek): provides r17 and comments. Tricci (OPPO) cannot accept r17 from Chien-Sheng (MediaTek) because the examples are not solution-oriented and there are the requirements described in 22.261. OPPO proposes r18 to make the examples in the KI to be 100% aligned with SA1 requirements. Yannick (Nokia): Nokia still has concerns about the proposal. Guillaume (MediaTek Inc.): this KI seems out of scope of the work. Provides r19. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Zhang (Ericsson) is OK with r12, 13, 14, 17 and object all other revisions Tricci (OPPO) prefers r12, 13, 14 David (Samsung) prefers r17 or r15, objects to r12 and earlier revisions, can live with the rest Yingying(CATT) prefers r12, r13, r14. Yannick (Nokia): Nokia prefers to postpone this to next meeting. Cannot find a version that either does not overlap with key issue for work task 1.1b being discussed in the context of S2-2200243, or that clearly illustrate what first bullet really tries to address, i.e. is this a user consent related issue or not at all. Guillaume (MediaTek Inc.) supports r19. Ok to postpone as suggested by Yannick (Nokia) Tricci (OPPO) could not understand Yannick (Nokia) argument and obviously, we definitely have different inference minds. OPPO asks further justification from Nokia below. Tricci (OPPO) responds to Yannick (Nokia) for his question. ==== 8.X, 9.X, 10.X Final Deadline ==== | Postponed |
| 9.21 | - | - | - | Key Issue: Monitoring Network Resource Utilization | - | - | Docs:=3 | - | |
| 9.21 | S2-2200167 | P-CR | Approval | 23.700-80: Key issue for monitoring of network resource utilization. | CATT | Rel-18 | r20 agreed. Revised to S2-2201816, merging S2-2201144 | Xiaoyan (CATT) provides r01 and r02. Tricci (OPPO) thanks Xiaoyan (CATT) updates and provide r03 for some wording clarifications. Ulises Olvera (InterDigital Inc.) provides r04 Xiaoyan (CATT) provides r05. Zhang (Ericsson) provides comments Malla (NTT DOCOMO) asks KI distinction between SA2 and SA5. Chien-Sheng (MediaTek) provides r06 and comments. Chien-Sheng (MediaTek) reuploads zip for r06. David (Samsung) provides r07. Juan Zhang (Qualcomm) provides comments Tricci (OPPO) provides r08. Malla (NTT DOCOMO) raised a concern that the KI proposal is overlapped with the SA5 aspect. Yannick (Nokia): Nokia requests for clarification. David (Samsung) agrees with previous comment by Nokia, provides r09 Malla (NTT DOCOMO) provides r10, object to initial and earlier revisions. Ulises (InterDigital Inc.) provides r11 to emphasize specific support for Application AI/ML operations as indicated in the SID, not all traffic. Chien-Sheng (MediaTek) provides r12 and comments. David (Samsung) requests clarifications on r12. Yannick (Nokia): Nokia comments on UE performance measurements. David (Samsung) provides comments Guillaume (MediaTek Inc.) replies. Tricci (OPPO) fully agree with Guillaume (MediaTek Inc.) understanding for scope of this study of the UE performance measurement, i.e.no performance measurement should be implemented at the UE. Yannick (Nokia): Nokia shares MediaTek and Oppo's understanding, no performance measurements at UE are needed. David (Samsung) provides r13 . Ulises (InterDigital Inc.) provides r14 Zhang (Ericsson) provides r15 and co-sign Malla (NTT DOCOMO) provides r17 and co-sign Xiaoyan (CATT) provides r19 Chien-Sheng (MediaTek) provides r20. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Zhang (Ericsson) is OK with r20 Yannick (Nokia): Nokia is ok with r20. Wang Yuan (Huawei) is also with r20. Tricci (OPPO) is okay with r20. ==== 8.X, 9.X, 10.X Final Deadline ==== Ulises (InterDigital Inc.) also supports r20. | Revised |
| 9.21 | S2-2201816 | P-CR | Approval | 23.700-80: Key issue for monitoring of network resource utilization. | CATT, InterDigital Inc, Samsung, OPPO, Ericsson, NTT DOCOMO, Huawei, HiSilicon, Qualcomm | Rel-18 | Revision of S2-2200167r20, merging S2-2201144. Approved | Approved | |
| 9.21 | S2-2201144 | P-CR | Approval | 23.700-80: New Key Issue on Enhanced 5GC to provide monitoring of System resource utilization relevant to specific AI/ML Operations (Objective: 1a, 1c, 2). | InterDigital Inc | Rel-18 | Merged into S2-2201816 | Zhang (Ericsson) thinks this CR is merged into S2-2200167 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.21 | - | - | - | Key Issue: Exposure Extensions Towards UE | - | - | Docs:=6 | - | |
| 9.21 | S2-2200969 | P-CR | Approval | 23.700-80: FS_AIMLsys Key Issue: 5GC information exposure to the UE. | China Mobile | Rel-18 | r14 agreed. Revised to S2-2201817, merging S2-2200804, S2-2200132 and S2-2200239 | Aihua (CMCC) provides r01 based on the rapporteur merged version and the further comments raised. David (Samsung) provides r02. Chien-Sheng (MediaTek) provides r03 and comments. Juan Zhang (Qualcomm) provides r04 and comments Megha(Intel) requests for clarification. Tricci (OPPO) thanks Juan (Qualcomm) KI update and provides r05 for further clarifications on the KI. Yannick (Nokia): Nokia provides comments and r06. Chien-Sheng (MediaTek) provides r07 and comments. Tricci (OPPO) thanks Yannick (Nokia) to provide r06 and is okay with r06. Thanks. Huazhang (vivo) provides r08 based on r07 and comments. Chien-Sheng (MediaTek) provides comments. Tricci (OPPO) would like to clarify with Chien-Sheng (MediaTek)'s comments. Yannick (Nokia): Nokia suggests a way forward to address MediaTek's question. Yannick (Nokia): Nokia provides r09. Tricci (OPPO) thanks Yannick (Nokia) revision but not sure if the construct of the sentence looks and sounds strange. Yannick (Nokia): Nokia answers to Tricci (Oppo). Juan Zhang (Qualcomm) provides r10. Zhang (Ericsson) provides r11 Tricci (OPPO) provides r12 for some editorial clean up which are highlighted in grey below. Huazhang (vivo) is ok with r12 and co-sign. Wang Yuan (Huawei) has concern on r12 and provides r13, and would like to co-sign. Tricci (OPPO) thanks Wang Yuan (Huawei) revision but would like to ask for technical reason for changes. Wang Yuan (Huawei) maintains the comments on r12 and clarify the technical reason. Wang Yuan (Huawei) replies to Zhang (Ericsson) and asks for clarification. Yannick (Nokia): Nokia believes that what is needed in the study phase is to understand the purpose of exposing some information to the UE. Whether this will require standardization is a different issue. Provides r14. Zhang (Ericsson) is OK with r14 ==== 8.X, 9.X, 10.X Revisions Deadline ==== Chien-Sheng (MediaTek) is OK with r14 and provides comments. ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.21 | S2-2201817 | P-CR | Approval | 23.700-80: FS_AIMLsys Key Issue: 5GC information exposure to the UE. | China Mobile, vivo, OPPO, Huawei, HiSilicon, Ericsson | Rel-18 | Revision of S2-2200969r14, merging S2-2200804, S2-2200132 and S2-2200239. Approved | Approved | |
| 9.21 | S2-2200132 | P-CR | Approval | 23.700-80: FS_AIMLsys KI (WT#1.1b): Extensions of information exposure for 5G NF(s) | China Telecom | Rel-18 | Merged into S2-2201817 | Zhang (Ericsson) thinks this paper is merged in to S2-2200969 Jiahui (China Telecom) agrees to merge into S2-2200969 and S2-2200243 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.21 | S2-2200239 | P-CR | Approval | 23.700-80: New KI: 5GS information exposure to UE for application layer AI/ML operation. | Qualcomm Incorporated | Rel-18 | Merged into S2-2201817 | Zhang (Ericsson) thinks this paper is merged in to S2-2200969 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.21 | S2-2200589 | P-CR | Approval | 23.700-80: New KI: Efficient Network analytics notification to UE. | Huawei, HiSilicon | Rel-18 | Merged into S2-2201624 | Zhang (Ericsson) thinks this paper is merged in to S2-2200969 Wang Yuan (Huawei) confirms this paper is merged in to S2-2200969. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.21 | S2-2200804 | P-CR | Approval | 23.700-80: Key Issue on 5GS predictions and analytics exposure to UE. | vivo | Rel-18 | Merged into S2-2201817 | Zhang (Ericsson) thinks this paper is merged in to S2-2200969 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.21 | - | - | - | Key Issue: Exposure Extensions Towards Authorized 3rd Party AF | - | - | Docs:=6 | - | |
| 9.21 | S2-2200243 | P-CR | Approval | 23.700-80: New KI: 5GS information exposure to application for application layer AI/ML operation. | Qualcomm Incorporated, China Telecom, KDDI, Samsung, OPPO, InterDigital Inc | Rel-18 | CC#5: r22 + replacement note agreed. Revised to S2-2201854, merging S2-2200120, S2-2200223, S2-2200227 and S2-2200233. | Tricci (OPPO): On behalf of the FS_AIMLsys colleagues, submitting the r01 rapporteur merged version of the PCR for WT#1.1b to be used as the baseline to discuss 5GC Exposure Enhancement to support authorized 3rd party for Application Layer AI / ML Operation. It is proposed to merge S2-2200120, S2-2200223, S2-2200233 and S2-2200227 into this S2-2200243. Tricci (OPPO) provides r02 for further comments on KI related WT#1.1b for exposure extensions to authorized 3rd party to support application AI/ML operation. David (Samsung) corrects link to r01. Tricci (OPPO) thanks David (Samsung) for providing the corrected link to r01. Chien-Sheng (MediaTek) comments on S2-2200243. Tricci (OPPO) thanks Chien-Sheng (MediaTek) comments on S2-2200243. Juan Zhang (Qualcomm) provides r03 Tricci (OPPO) thanks Juan Zhang (Qualcomm) to provide a revision. OPPO provides revision r04 to restore an aspect in the KI based on SA1 requirement and was not captured in any other KI. Yannick (Nokia): Nokia requests for clarification on r04. Tricci (OPPO) thanks Yannick (Nokia) comments. Please see my responses inline with you below in orange. Yannick (Nokia): Nokia relies to Oppo (Tricci). Tricci (OPPO) thanks Yannick (Nokia) feedback. OPPO has no strong opinion to whether to consolidate all three bullets into the merged bullet. Hence, OPPO provide r05 to consolidate the three bullets. Please check. Chien-Sheng (MediaTek) provides comments. Chien-Sheng (MediaTek) thanks Tricci and provides r06. Zhang (Ericsson) asks for clarification Yannick (Nokia): Nokia provides r07. Guillaume (MediaTek) comments and provide r08 with a rewording. Zhang (Ericsson) provides comments Tricci (OPPO) welcomes Guillaume to join the discussions and would like to provide further comments on this topic. Megha(Intel) provides r09 with some comments Yannick (Nokia): Nokia comments on user consent. Tricci (OPPO) responds to Yannick (Nokia) question. Guillaume (MediaTek Inc.) responds to Zhang (Ericsson) Juan Zhang (Qualcomm) provides a cleanup version in R10. Zhang (Ericsson) is fine with r10 and co-sign Chien-Sheng (MediaTek) provides r11. Malla (NTT DOCOMO) provides r12 and object to initial and earlier revisions. Tricci (OPPO) provides r13 based on r12 for some editorial clean up and to add the reference to TS 22.261. Chien-Sheng (MediaTek) provides comments on r13. Malla (NTT DOCOMO) replies to Chien-Sheng (MediaTek). Zhang (Ericsson) provides r14 and co-sign David (Samsung) provides r15 and co-signs Wang Yuan (Huawei) provides r16 and co-sign. Megha(Intel) provides r017 Xiaoyan (CATT) provides r19 and cosign. Wang Yuan (Huawei) has concerns on r19. Tricci (OPPO) thanks Xiaoyan (CATT) for revision r19, unfortunately, OPPO can NOT accept r19. Tricci (OPPO) thanks and supports Wang Yuan (Huawei) comments and agrees with Huawei and proposes to keep r18 with CATT remains as the supporting company. Juan Zhang (Qualcomm) provides comments on r18 and r19. Tricci (OPPO) thanks Juan Zhang (Qualcomm) due diligent to catch the mistake. Indeed, OPPO prefers r17 and not r18. Thanks again. Chien-Sheng (MediaTek) provides r20 and comments. David (Samsung) agrees with Qualcomm and OPPO, cannot accept r18/r19, prefers the bullet in r17. Malla (NTT DOCOMO) objects r20, prefers the bullet in r17. Chien-Sheng (MediaTek) objects r17 or other earlier revisions, and provides r20 and comments. Tricci (OPPO) does not understand what exactly is 'explicit' consent and also what is 'UE's subscriber'? Chien-Sheng (MediaTek) replies to Malla (NTT DOCOMO). Yannick (Nokia): Nokia would like to keep 'predictions' in the scope for this key issue. Also, any aspect related to user consent should be addressed by SA3, so suggest to put some text related to MediaTek point into a note for SA3 to review. Malla (NTT DOCOMO) provides r21 on top of r20. Yannick (Nokia): Nokia provides r22, based on r17, with some rewording for the note as proposed by NTT DOCOMO. Malla (NTT DOCOMO) fine with r22. Chien-Sheng (MediaTek) thanks for Yannick' comments. Provides r23 (based on r20) and comments. Xiaoyan (CATT) provides r24, based on r22. Chien-Sheng (MediaTek) asks Xiaoyan (CATT) for clarification: Why Note 1 in r23 is incomplete? Guillaume (MediaTek Inc.) objects r24 given it is incorrect. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Xiaoyan (CATT) asks clarifications from Yuan (Huawei). Wang Yuan (Huawei) provides comments on r23 and r24, prefer r22. Xiaoyan (CATT) clarifies to Chien-Sheng (MediaTek) and Guillaume (MediaTek). Wang Yuan (Huawei) withdraws the comments on r24, can accept r24. Juan Zhang (Qualcomm) provides r25 in the draft folder. Chien-Sheng (MediaTek) is not ok with r24 and r22, thus provides r25 in drafts as a merge between r22 and r23. Juan Zhang (Qualcomm) provides r26 in the draft folder. Yannick (Nokia): only looking at latest versions, Nokia is fine with r22, r24 and r25. Zhang (Ericsson) is Ok with r22, 24, 25, 26 Yannick (Nokia): Nokia highlights there are two r25 provided. Suggest to use same folder for all drafts. Nokia is fine with r25 as provided by Mediatek. Nokia is not ok with r25 as provided by Qualcomm. Juan Zhang (Qualcomm) is OK with r22, r25, r26, and proposes to agree r25. Tricci (OPPO) can live with r22, 24, 25, 26 David (Samsung) supports agreeing r25 (provided by Mediatek). Since it was provided after revisions deadline we may need to confirm it in CC#4/5 Megha(Intel) is ok with r22, r24, r25, r26. Chien-Sheng (MediaTek) confirms that r25 is as a merge between r22 and r23. David (Samsung) thanks Chien-Sheng (MediaTek), confirms for CC#4 the basis pre-deadline revision is r22 where the full NOTE has been updated in r25 Xiaoyan (CATT) proposes one small modification on top of r25. ==== 8.X, 9.X, 10.X Final Deadline ==== Ulises (InterDigital) also supports agreeing r25 as is without further modifications, and request removing the '?' after our company's name. KDDI also supports agreeing r25, and request removing the '?' from KDDI. Jihoon (ETRI) also supports agreeing r25 and requests removing the '?' from ETRI. Jiahui (China Telecom) also supports agreeing r25 and requests removing the '?' from China Telecom. | Revised |
| 9.21 | S2-2201854 | P-CR | Approval | 23.700-80: New KI: 5GS information exposure to application for application layer AI/ML operation. | Qualcomm Incorporated, China Telecom, KDDI, Samsung, Intel, ETRI, InterDigital Inc, OPPO, Ericsson, Huawei, Nokia | Rel-18 | Revision of S2-2200243r22 + replacement note, merging S2-2200120, S2-2200223, S2-2200227 and S2-2200233. Approved | Approved | |
| 9.21 | S2-2200223 | P-CR | Approval | 23.700-80: KI, WT 1b: 5GC information exposure to authorized 3rd party to assist Application AIML operation. | Intel | Rel-18 | Merged into S2-2201854 | Megha(Intel): This pCR can be marked as merged with S2-2200243. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.21 | S2-2200233 | P-CR | Approval | 23.700-80: Key issue on 5GS information exposure extensions for AI/ML service. | Lenovo, Motorola Mobility | Rel-18 | Merged into S2-2201854 | Yannick (Nokia): Nokia suggests to mark S2-2200233 as merged into S2-2200243. ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.21 | S2-2200227 | P-CR | Approval | 23.700-80: New Key Issue on NF exposure services for application AI/ML operation (WT#1.1b). | Samsung | Rel-18 | Merged into S2-2201854 | David (Samsung) confirms this paper is merged into S2-2200243. ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.21 | S2-2200120 | P-CR | Approval | 23.700-80: FS_AIMLsys Proposed KI: Related to WT#1.1.b for Info Exposure Extension to assist Application AI/ML operation | OPPO | Rel-18 | Merged into S2-2201854 | Tricci (OPPO) confirms this PCR S2-220012 is merged into S2-2200243. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.21 | - | - | - | Key Issue: Enhancements of external parameter provisioning | - | - | Docs:=2 | - | |
| 9.21 | S2-2200170 | P-CR | Approval | 23.700-80: New Key Issue on Enhancing External Parameter Provisioning (WT#1.1c). | Samsung, InterDigital Inc., OPPO | Rel-18 | r14 agreed. Revised to S2-2201818. | Juan Zhang (Qualcomm) provides comments Yannick (Nokia): Nokia provides r01. Tricci (OPPO) thanks Yannick (Nokia) provides r01 update. OPPO provides r02 for further clarifications. Malla (NTT DOCOMO) provides r03 with further clarification. Yannick (Nokia): Nokia provides r04. Mehrdad (Samsung) provides r05 and answers to Qualcomm. Chien-Sheng (MediaTek) provides r06. Yannick (Nokia): Nokia comments on r06. Mehrdad (Samsung) provides r07. Zhang (Ericsson) provides comments Mehrdad (Samsung) provides r08. Yannick (Nokia): Nokia prefers r08 which clearly indicates that privacy aspects are for SA3. Vivian (vivo) provides r09 and would like to co-sign. Mehrdad (Samsung) can not agree with r09 Yannick (Nokia): Nokia provides r10. Mehrdad (Samsung) is OK with r10 and thanks Nokia for the support. Zhang (Ericsson) provides r11 and co-sign Vivian(vivo) is fine with r10 and r11, and confirms to co-sign Mehrdad (Samsung) provides r12, adding vivo as a co-signer Megha (Intel) provides r13 Mehrdad (Samsung) replies to Intel Megha(Intel) provides comments. Mehrdad (Samsung) provides r14. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Chien-Sheng (MediaTek) is ok with r14. Thanks. Yannick (Nokia): Nokia also supports r14. Tricci (OPPO) supports r14. Zhang (Ericsson) prefer r14 Megha(Intel) is ok with r13, r14. ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.21 | S2-2201818 | P-CR | Approval | 23.700-80: New Key Issue on Enhancing External Parameter Provisioning (WT#1.1c). | Samsung, InterDigital Inc., OPPO, Nokia, Ericsson, vivo, Intel | Rel-18 | Revision of S2-2200170r14. Approved | Approved | |
| 9.21 | - | - | - | Key Issue: Enhancements of 5GC to assist Application AIML operation | - | - | Docs:=5 | - | |
| 9.21 | S2-2200352 | P-CR | Approval | 23.700-80: New Key Issues for supporting AI/ML training/inference/splitting/sharing operation. | ETRI, OPPO | Rel-18 | CC#5: r22 agreed. Revised to S2-2201819, merging S2-2200292 and S2-2200171 | Tricci (OPPO): On behalf of the FS_AIMLsys colleagues, submitting the r01 rapporteur merged version of the PCR for WT#1.1d to be used as the baseline to discuss data transfer and traffic steering extensions in 5GC, and cooperation of 5GS and AI/ML application to enable AI/ML training/inference/splitting/sharing operation. It is proposed to merge S2-2200171, S2-2200168 and S2-2200843 into this S2-2200352. Tricci (OPPO) provides r02 for further comments on KI for WT#1.1d. Mehrdad (Samsung) corrects the thread subject. Mehrdad (Samsung) provides r03 Farooq (AT&T) provides r04 with a bullet to capture charging aspects for AIML training traffic Tricci (OPPO) provides r05 with the list of updates. Chien-Sheng (MediaTek) provides r09. Mehrdad (Samsung) clarifies to MediaTek that in r08, the bullet under change by MediaTek is already removed. Please use r08 to generate another revision. Tricci (OPPO) thanks Mehrdad (Samsung) to provide an update and Chien-Sheng (MediaTek) to provide his comment. OPPO provides revision r12. Soohwan (ETRI) provides r12 on top of r11. Chien-Sheng (MediaTek) thanks Mehrdad and provides r11. Tricci (OPPO) informs Soohwan (ETRI) regarding the clashes of OPPO's r12 vs. ETRI's r012. Hence, OPPO prepares r13 to incorporate ETRI's changes. Please abandon r012. Soohwan (ETRI) confirmed r13 and asks to abandon r012. Yannick (Nokia): Nokia provides comments and r14. Mehrdad (Samsung) replies to Nokia and provides r15. Yannick (Nokia): Nokia provides r16. Tricci (OPPO) thanks Mehrdad (Samsung) and Yannick (Nokia) provide previous revisions. OPPO provides r17 to remove the not needed background text. Mehrdad (Samsung) cannot agree with r017. Mehrdad (Samsung) cannot agree with r17. Mehrdad (Samsung) provides r18. Tricci (OPPO) thanks Mehrdad (Samsung) provides r18. OPPO is okay with r18. Yannick (Nokia): Nokia request clarification on privacy aspects. Mehrdad (Samsung) replies to Nokia. Yannick (Nokia): Nokia provides r19, removing privacy aspects that fall under SA3 remit. Zhang (Ericsson) provides comments Mehrdad (Samsung) provides r20. Zhang (Ericsson) is OK with r20 and co-sign Mehrdad (Samsung) confirms merging S2-2200171 into S2-2200352r20 and co-signs this PCR. Wang Yuan (Huawei) is fine with r20 and would like to co-sign. Juan Zhang (Qualcomm) is OK with r20 and would like to co-sign the proposal. Vivian (vivo) likes this r20 and would like to co-sign. Tricci (OPPO) apologizes to break the lucky number 20 and provides r21 to clean up the level 3 header '5.X.1 Description) to be consistent with TR skeleton and also to reword 'traffic steering' to 'traffic routing' highlighted in 'grey' to be more accurate to the bullet since UE is not involved in steering the traffic. Mehrdad (Samsung) provides r22 adding new co-signers Tricci (OPPO) thanks Mehrdad (Samsung) to provide r22 and is okay with r22. Hoping 22 is the new lucky number ?? Yingying(CATT) provides r23 and confirms to co-sign it. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Chien-Sheng(MediaTek) is ok with r22 and r23. Thanks. Mehrdad (Samsung) is ok with both r22 and r23. Yannick (Nokia): Nokia prefers r22. Tricci (OPPO) is ok with either r22 or r23. Yingying(CATT) just asks Yannick (Nokia) for clarifications. Yannick (Nokia): Nokia replies to CATT. Juan Zhang (Qualcomm) suggests to go with r22. Yingying(CATT) replies to Yannick (Nokia). Yingying(CATT) is OK with r22. ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.21 | S2-2201819 | P-CR | Approval | 23.700-80: New Key Issues for supporting AI/ML training/inference/splitting/sharing operation . | ETRI, CATT, Samsung, OPPO, AT&T, Huawei, Qualcomm Incorporated, vivo, Ericsson | Rel-18 | CC#5: Revision of S2-2200352r22, merging S2-2200292 and S2-2200171. Approved | Approved | |
| 9.21 | S2-2200171 | P-CR | Approval | 23.700-80: New Key Issue on Enhanced 5GC to Assist AIML Operation (WT#1.1d). | Samsung | Rel-18 | Merged into S2-2201819 | Mehrdad (Samsung) suggests to mark S2-2200171 as merged into S2-2200352r20. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.21 | S2-2200168 | P-CR | Approval | 23.700-80: Key issue for assistance to Application AI/ML operation splitting. | CATT | Rel-18 | Merged into S2-2201569 | Zhang (Ericsson) thinks this paper is merged into S2-2200352 Mehrdad (Samsung) also suggests to mark this paper as merged into S2-2200352 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.21 | S2-2200843 | P-CR | Approval | 23.700-80: FS_AIMLsys - proposed KI for WT#1.1d. | OPPO | Rel-18 | Merged into S2-2201569 | Zhang (Ericsson) thinks this paper is merged into S2-2200352 Mehrdad (Samsung) also suggests to mark this paper as merged into S2-2200352 Tricci (OPPO) confirms this PCR S2-2200843 is merged into S2-2200352. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.21 | - | - | - | Key Issue: QoS and Policy Enhancement | - | - | Docs:=7 | - | |
| 9.21 | S2-2201118 | P-CR | Approval | 23.700-80: KI (WT#1.2): QoS and Policy enhancements. | NTT DOCOMO, InterDigital, Samsung | Rel-18 | r32 agreed. Revised to S2-2201820, merging S2-2200861, S2-2200121, S2-2200131, S2-2200173 and S2-2200228 | Tricci (OPPO): On behalf of the FS_AIMLsys colleagues, submitting the r01 rapporteur merged version of the PCR for WT#1.2 to be used as the baseline to discuss QoS and Policy to enable AI/ML operation. It is proposed to merge S2-2200968, S2-2200121, S2-2200131, S2-2200173, S2-2200228 into this S2-2201118. Aihua(CMCC) provides r02. Tricci (OPPO) thanks Aihua(CMCC) feedback, and would like to alerts Aihua that the wrong revision was provided in the following link. You have provided the 0128 instead fo 1118. Please correct. Belen (Ericsson) provides r03, objects to previos revisions and initial version. David (Samsung) provides r04, comments. Belen (Ericsson) comments on r04 Juan Zhang (Qualcomm) comments on r04 Malla (NTT DOCOMO) provided r05 Belen (Ericsson) objects to r05 and r04. Tricci (OPPO) provides r06 based on Belen (Ericsson) r03. Aihua(CMCC) provides r07. Juan Zhang (Qualcomm) provides r08. Malla (NTT DOCOMO) replies to Belen (Ericsson). David (Samsung) replies to Juan and Belen, provides r09 on top of r08. Ulises (InterDigital Inc.) comments on David's r09 revision and provides r10. Belen (Ericsson) provides r11 David (Samsung) provides r12. Megha(Intel) asks for clarification. Chien-Sheng (MediaTek) provides r13 and comments. Aihua(CMCC) provides r13. Yannick (Nokia): Nokia provides r14. Belen (Ericsson) provides r15. Belen (Ericsson) provides r16 and thanks for spotting this. David (Samsung) notes that changes on r15 are not continuous with previous revisions, wonders if it's the same as r11 already provided by Ericsson. Tricci (OPPO) responds to Chien-Sheng (MediaTek) suggestion and cannot accept revision r13. Aihua(CMCC) provides r17. Yannick (Nokia): Nokia comments on r17. Tricci (OPPO) would like to try to answer Yannick (Nokia) questions Ulises (InterDigital Inc.) proposes rewording to address QoS monitoring duplication in 1st and 4th bullet. Aihua (CMCC) thank Tricci and fine with what Tricci explained. Tricci (OPPO) provides r24 for some clean up and to clarify the FL performance monitoring/exposure aspects. Tricci (OPPO) provides r19 to remove the level 3 header '5.X.1 Description' to align with TR skeleton and to reword 'client' by 'UE' as highlighted in 'yellow' below. David (Samsung) notes that r24 provided below corresponds to S2-2200805, not S2-2201118. Chien-Sheng (MediaTek) thanks Tricci (OPPO)'s comments and provides r20. Yannick (Nokia): Nokia provides r21. Jianning (Xiaomi) provides comments and r22 Tricci (OPPO) responds to Yannick (Nokia) revision for r21. Tricci (OPPO) thanks Belen (Ericsson) and David (Samsung) to catch the wrong email thread posting for r24 which should be corresponds to S2-2200805, not S2-2201118. David (Samsung) provides r23. Belen (Ericsson) provides r24. Aihua(CMCC) provides r25. Chien-Sheng (MediaTek) objects r25 and provides r26. Juan Zhang (Qualcomm) provides r27. Malla (NTT DOCOMO) provides r27 Juan Zhang (Qualcomm) provides r28. David (Samsung) provides r29. Yannick (Nokia): Nokia agrees with Samsung to remove reference to model topology and weights. Belen (Ericsson) objects to r29 is okay with r28 David (Samsung) objects to r28. Belen (Ericsson) asks Samsung to provide acceptable text other than r29 if possible Tricci (OPPO) supports Belen (Ericsson) and rejects r29 based on the arguments from Nokia and Samsung because the arguments are not consistent when certain SA1 requirements can be followed but not the others. David (Samsung) provides r31 and r32, objects to r30 on the server which has not been shared over the reflector. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Liu Liu (China telecom) supports David (samsung) Juan Zhang (Qualcomm) prefers r32. Chien-Sheng (MediaTek) is OK with r31/r32 only under the condition that network conditions are only bitrate, latency and reliability, as specified in 22.261 §6.40. Any other condition is out of scope. Thanks. Jianning (Xiaomi) prefers r32 Yannick (Nokia): Nokia is fine with r32. Wang Yuan (Huawei) also prefers r32. Tricci (OPPO) can live with r32 Megha (Intel) is ok with r32. ==== 8.X, 9.X, 10.X Final Deadline ==== Liu Liu (China Telecom) prefers r32. | Revised |
| 9.21 | S2-2201820 | P-CR | Approval | 23.700-80: KI (WT#1.2): QoS and Policy enhancements. | NTT DOCOMO, Interdigital, Samsung, OPPO, Ericsson | Rel-18 | Revision of S2-2201118r32, merging S2-2200861, S2-2200121, S2-2200131, S2-2200173 and S2-22002. Approved | Approved | |
| 9.21 | S2-2200121 | P-CR | Approval | 23.700-80: FS_AIMLsys TR KIs for WT#1.2 related to QoS and Policy enhancement | OPPO | Rel-18 | Merged into S2-2201820 | Tricci (OPPO) asks for clarifications. Belen (Ericsson) asks if this is merged into S2-2201118 Belen (Ericsson) asks to merge into S2-2201118, provides comments and object to the contribution in the current form Tricci (OPPO) confirms this pCR S2-2200121 is merged into S2-2201118. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.21 | S2-2200131 | P-CR | Approval | 23.700-80: KI (WT#1.2): New KI on enhancement to support AI/ML operations in 5GS | China Telecom | Rel-18 | Merged into S2-2201820 | Belen (Ericsson) asks if this is merged into S2-2201118 Liu Liu (China Telecom) replies Belen (Ericsson) ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== Liu Liu (China Telecom) confirms to merge S2-2200131 into S2-2201118 | Merged |
| 9.21 | S2-2200173 | P-CR | Approval | 23.700-80: New Key Issue on QoS and Policy Enhancements for Handling of Application AI/ML Traffic in 5GS (WT#1.2). | Samsung | Rel-18 | Merged into S2-2201820 | Belen (Ericsson) suggests to mark this paper as merged into S2-2201118 ==== 8.X, 9.X, 10.X Revisions Deadline ==== David (Samsung) confirms merger into S2-2201118 ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.21 | S2-2200228 | P-CR | Approval | 23.700-80: Key issue on QoS and Policy enhancement for AI/ML services. | Lenovo, Motorola Mobility | Rel-18 | Merged into S2-2201820 | Belen (Ericsson) asks if this is merged into S2-2201118 Belen (Ericsson) asks to merge into S2-2201118, provides comments and object to the contribution in the current form ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.21 | S2-2200968 | P-CR | Approval | 23.700-80: New KI on 5G QoS Enhancements for AI/ML Service. | China Mobile | Rel-18 | Merged into S2-2201741 | Belen (Ericsson) asks if this is merged into S2-2201118 Belen (Ericsson) asks to merge into S2-2201118, provides comments and object to the contribution in the current form ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.21 | - | - | - | Key Issue: 5GS Assistance to Federated Learning | - | - | Docs:=7 | - | |
| 9.21 | S2-2200805 | P-CR | Approval | 23.700-80: New key issue on Horizontal Federated Learning. | vivo | Rel-18 | CC#5: r34 + editor's note agreed. Revised to S2-2201821, merging S2-2200457, S2-2201171, S2-2200174, S2-2201099 and S2-2200590 | Tricci (OPPO): On behalf of the FS_AIMLsys colleagues, submitting the r01 rapporteur merged version of the PCR for WT#1.3 to be used as the baseline for FL related KI discussions. It is proposed to merge S2-2200968, S2-2200121, S2-2200131, S2-2200173 and S2-2200228 into this S2-2200805. Jihoon (ETRI) asks Tricci(OPPO) to check the Tdoc numbers. Tricci (OPPO) sincere thanks to Jihoon (ETRI) to spot the mistakes. Here are the corrections. It is proposed to merge S2-2201099, S2-2201071, S2-2200590, S2-2200169 and S2-2200174 into S2-2200805. Tricci (OPPO) provides r02 for further comments to KI for WT#1.3 related to 5GS assistance to FL operation. Jihoon(ETRI) asks a few questions on Tricci(OPPO)'s comments. Tricci (OPPO) thanks Jihoon (ETRI) feedback and provides further comments inline below. Jihoon(ETRI) provides comments inline. Tricci (OPPO) thanks Jihoon (ETRI) further feedback and provides further comments inline below in blue. Wang Yuan (Huawei) provide comments on r03. Tricci (OPPO) thanks Wang Yuan (Huawei) comments and provides feedback inline below in brown and cannot find r03 on server as suggested by HW. Vivian(vivo) replies to Yuan's(Huawei) comments. Wang Yuan (Huawei) clarifies that previous comments are based on r02 provided by OPPO, and no r03 is provided from Huawei. Vivian(vivo) provides r03 based on the following comment and discussion. Chien-Sheng (MediaTek) provides r04. Juan Zhang (Qualcomm) comments and provides r05. Jihoon(ETRI) provides r06. Malla (NTT DOCOMO) provides r07 and fine to merge S2-2201099. Tricci (OPPO) provides r08. David (Samsung) provides r09. Vivian(vivo) provides a cleanup r10 based on r09. Tricci (OPPO) thanks David (Samsung) for providing new revision. OPPO provides r10 to clarify the use of the new term introduced by Samsung. David (Samsung) thanks OPPO and vivo, provides r11. Yannick (Nokia): Nokia provides comments on r11. Jihoon (ETRI) provides comments with some questions. Vivian (vivo) provides r12 based on r11 by considering some but not all comments from Nokia. Tricci (OPPO) thanks Vivian (vivo) for new revisions and provides another new revision r13. Tricci (OPPO) thanks Yannick (Nokia) comments and has already provided r13 to address some of his comment. Please check other email. Thanks. Yannick (Nokia): Nokia provides r14 and comments. Zhang (Ericsson) provides comments Tricci (OPPO) thanks Yannick (Nokia) revision and provides feedback. Tricci (OPPO) thanks Zhang (Ericsson) comments and provides feedback. Zhang (Ericsson) provides r15 David (Samsung) provides r16 Yannick (Nokia): Nokia provides r17. Tricci (OPPO) thanks Yannick (Nokia) revision and proposes r18 for some corrections Jihoon(ETRI) provides comments. Tricci (OPPO) thanks Jihoon(ETRI) comments and provides feedback. Juan Zhang (Qualcomm) provides r19. Yannick (Nokia): Nokia is fine with Oppo's update to FL performance part. Malla (NTT DOCOMO) provides r20. David (Samsung) provides r21 Yannick (Nokia): Nokia provides r23. Also uploaded r22 but withdraw it. Juan Zhang (Qualcomm) provides r25 Jaewook (ETRI) provides comments David (Samsung) replies to Jaewook (ETRI) Tricci (OPPO) thanks Jaewook (ETRI) comment and thanks David (Samsung) response to Jaewook (ETRI). OPPO provides additional justification. Tricci (OPPO) thanks Juan Zhang (Qualcomm) to provide r25 and is okay with r25. Apologize for posting the revision earlier on the wrong email thread. Zhang (Ericsson) is OK with r25 David (Samsung) provides r26 on top of r25 with minor cleanup Tricci (OPPO) thanks again to Wang Yuan's (Huawei) support for this KI and provides r28 to restore the previous version of the note to not to limit the term 'member UE' to apply only FL operation. Tricci (OPPO) cannot agree with Wang Yuan (Huawei) proposed r27 and objects any version of this KI that excludes member UE to apply to general Machine Learning (i.e. ML). Wang Yuan (Huawei) provides r27 and co-signs. Wang Yuan (Huawei) is fine with r28. Tricci (OPPO) thanks Wang Yuan (Huawei) for your kind support for this KI and accepting r28. Xiaoyan (CATT) provides r29. David (Samsung) objects to r29. Yannick (Nokia): Nokia requests for clarification. Tricci (OPPO) responds to Yannick (Nokia) question. David (Samsung) comments. Yannick (Nokia): Nokia wonders why we cannot apply the note to just FL member UEs. R27 is the right version to go with. Tricci (OPPO) responds to Yannick (Nokia) and can NOT accept r27, unfortunately. The term 'member UEs' must be defined correctly unless it is removed as I have provided full technically correct explanation. This is too late to undo the proper definition at the last minute. Besides, HW has withdrawn his comment. David (Samsung) is OK going with r27. Xiaoyan (CATT) requests clarification from David (Samsung) and comments on r28. David (Samsung) asks Tricci a question Yannick (Nokia): Nokia explains that 'FL member UE' is defined in r27 and thus do not see where the issue is and ask Oppo to explain. Also, Nokia reminds about the meeting deadlines, do not understand why it would be too late to provide comments and finalize the key issue description. Malla (NTT DOCOMO) we support Yannick (Nokia) as it is limited to this FL KI, so saying FL member makes sense and I do not find an issue. Tricci (OPPO) confirms once again that OPPO objects r27 because the current concept of the term is incorrect. David (Samsung) agrees with Nokia and NTT Docomo, provides r30 as a way forward. Yannick (Nokia): Nokia is fine with the note as proposed by Samsung. Tricci (OPPO) responds to David (Samsung) with a suggestion as a way forward. Xiaoyan (CATT) provides r31. Tricci (OPPO) cannot accept r27 or r30, and has explained OPPO's concern to consider 'member' related terminology exclusively in this KI which is not acceptable to OPPO. OPPO has proposed an alternative as a way forward. Please kindly consider. Yannick (Nokia): Nokia does not accept alternative as proposed by Oppo. Tricci (OPPO) thanks David (Samsung) for your kind consideration of my proposed way forward. OPPO agrees with David to restore previous descriptions and OPPO will go ahead to update S2-2200166 with the current NOTE in r26 of S2-2200805. David (Samsung) comments on way forward. Tricci (OPPO) fails to understand Yannick (Nokia) implication and will not accept any revision of S2-2200805 with incomplete 'member' related definitions defined anywhere. Zhang (Ericsson) is Ok with r30 and r27 Tricci (OPPO) agrees with David (Samsung) comments that we need a way forward and OPPO has proposed one. David (Samsung) provides r33 (please discard r32). Yannick (Nokia): Nokia provides r34 (based on r30). David (Samsung) can live with r34. Megha (Intel) provides some comments on the member UE selection for FL Tricci (OPPO) responds to Megha (Intel) question. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Megha (Intel) responds to Tricci (OPPO) Tricci (OPPO) thanks Megha (Intel) kind feedback and also would like to provide further clarifications. Vivian (vivo) proposes to go with r34 as a way forward. Xiaoyan (CATT) comments on r34 Zhang (Ericsson) prefers r33 can live with r34 Malla (NTT DOCOMO) fine with both r33 and r34. Tricci (OPPO) can ONLY accept r34 and rejects all other versions. Megha (Intel) is ok with r33, r34. Xiaoyan (CATT) objects to r34, and can only accept r34 with an EN on monitoring Application FL operation. David (Samsung) strongly requests Xiaoyan (CATT) to reconsider her objection, which Samsung and myself as co-rapporteur find unacceptable. Tricci (OPPO) asks Xiaoyan (CATT) is there a way to address your concern in the next meeting? ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.21 | S2-2201821 | P-CR | Approval | 23.700-80: New key issue on 5GS Assistance to Federated Learning Operation. | Vivo, NTT DOCOMO, ETRI, Huawei, Samsung, OPPO, Ericsson, Nokia | Rel-18 | Revision of S2-2200805r34 + editor's note, merging S2-2200457, S2-2201171, S2-2200174, S2-2201099 and S2-2200590. Approved | Approved | |
| 9.21 | S2-2200174 | P-CR | Approval | 23.700-80: New Key Issue on 5GS Support for Application Federated Learning (WT#1.3). | Samsung | Rel-18 | Merged into S2-2201821 | David (Samsung) confirms this paper is merged into S2-2200805. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.21 | S2-2200590 | P-CR | Approval | 23.700-80: New KI: 5GS assisted FL group performance monitoring. | Huawei, HiSilicon | Rel-18 | Merged into S2-2201821 | Wang Yuan (Huawei) confirms this pCR is merged into S2-2200805. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.21 | S2-2200806 | DISCUSSION | Information | Discussion on Horizontal Federated Learning | vivo | Rel-18 | Noted | ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 9.21 | S2-2201071 | P-CR | Approval | 23.700-80: New Key Issues for supporting federated learning. | ETRI | Rel-18 | Merged into S2-2201619 | Yannick (Nokia): Nokia suggests to mark S2-2201071 as merged into S2-2200805. Jihoon (ETRI) agrees with Yannick (Nokia)'s suggestion. ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.21 | S2-2201099 | P-CR | Approval | 23.700-80: KI (WT#1.3): Federated Learning over 5GS. | NTT DOCOMO | Rel-18 | Merged into S2-2201821 | Malla (NTT DOCOMO) confirms this pCR is merged into S2-2200805. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.21 | - | - | - | Documents exceeding quota | - | - | Docs:=7 | - | |
| 9.21 | S2-2201180 | P-CR | Approval | 23.700-80: Definition and terminology . | Xiaomi | Rel-18 | Not Handled | ==== 8.X, 9.X, 10.X Final Deadline ==== | - |
| 9.21 | S2-2200188 | P-CR | Approval | 23.700-80: 23.700-80: Architecture assumptions for AIMLsys. | Nokia, Nokia Shanghai Bell | Rel-18 | Not Handled | ==== 8.X, 9.X, 10.X Final Deadline ==== | - |
| 9.21 | S2-2200224 | P-CR | Approval | 23.700-80: AIMLsys architectural assumptions. | Intel | Rel-18 | Not Handled | ==== 8.X, 9.X, 10.X Final Deadline ==== | - |
| 9.21 | S2-2200848 | P-CR | Approval | 23.700-80: FS_AIMLsys Architecture Assumptions. | Samsung | Rel-18 | Not Handled | ==== 8.X, 9.X, 10.X Final Deadline ==== | - |
| 9.21 | S2-2200122 | P-CR | Approval | 23.700-80: FS_AIMLsys - Proposed Architecture Requirements & Assumptions | OPPO | Rel-18 | Not Handled | Megha(Intel) requests for clarification. Tricci (OPPO) responds to Megha(Intel) questions. Tricci (OPPO) confirms this pCR S2-2200122 is merged into S2-2200166. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | - |
| 9.21 | S2-2201147 | P-CR | Approval | 23.700-80: New Key Issue on Event Notification Enhancements to 5GC to support AI/ML Operations (Objective: 1b). | InterDigital Inc | Rel-18 | Not Handled | ==== 8.X, 9.X, 10.X Final Deadline ==== | - |
| 9.21 | S2-2200169 | P-CR | Approval | 23.700-80: Key issue for assistance to FL member selection and group management. | CATT | Rel-18 | Not Handled | ==== 8.X, 9.X, 10.X Final Deadline ==== | - |
| 9.22 | - | - | - | Study on Enhancement of 5G UE Policy (FS_eUEPO) | - | - | Docs:=32 | - | |
| 9.22 | - | - | - | TR Skeleton and Scope | - | - | Docs:=2 | - | |
| 9.22 | S2-2200665 | P-CR | Approval | 23.700-85: FS_eUEPO TR Skeleton | Intel | Rel-18 | 23.700-85 TR Skeleton. Approved | ==== 8.X, 9.X, 10.X Final Deadline ==== | Approved |
| 9.22 | S2-2200662 | P-CR | Approval | 23.700-85: Scope of FS_eUEPO TR. | Intel | Rel-18 | Approved | ==== 8.X, 9.X, 10.X Final Deadline ==== | Approved |
| 9.22 | - | - | - | Architectural Assumption | - | - | Docs:=2 | - | |
| 9.22 | S2-2200663 | P-CR | Approval | 23.700-85: Architectural Assumption of FS_eUEPO. | Intel | Rel-18 | Approved | ==== 8.X, 9.X, 10.X Final Deadline ==== | Approved |
| 9.22 | S2-2201170 | P-CR | Approval | 23.700-85: Architectural Assumptions and principles of FS_eUEPO TR. | NEC | Rel-18 | Merged into S2-2201560 | Changhong (Intel) proposes to merge it into S2-2200663. Kundan (NEC) fine with Changhong proposal to merge it in S2-2200663. Haiyang (Huawei) provides comments. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.22 | - | - | - | Key Issues for WT#1 | - | - | Docs:=5 | - | |
| 9.22 | S2-2200272 | P-CR | Approval | 23.700-85: New KI on WT1 for URSP roaming. | Huawei, HiSilicon | Rel-18 | r19 agreed. Revised to S2-2201362, merging S2-2200405 and S2-2201046 | Haiyang (Huawei) provides r01. Krisztian (Apple) provides r02. Changhong (Intel) provides r03. Wen (vivo) comments on r03. Pallab (Nokia) provides r04. Hong (Qualcomm) comments. Changhong (Intel) replies to Wen's comments. Belen (Ericsson) provides r05 objects to previous revisions and initial version Dimitris (Lenovo) provides r06 based on r05 Hong (Qualcomm) provides r07. Wen (vivo) provides r08. Yang (OPPO) provides question to r07. Krisztian (Apple) has a concern on the wording in r07. Hong (Qualcomm) replies to Yang. Hong (Qualcomm) replies to Krisztian (Apple). Yang (OPPO) replies to Hong Dimitris (Lenovo) provides r09 Pallab (Nokia) objects to all revisions starting from r05. i.e. r05, r06, r07, r08, r09 Jicheol (Samsung) provides r10, and only accepts r08, r09 and r10. Wen (vivo) doesn't agree with any version that the VPLMN generates/updates URSP for UE directly. Jicheol (Samsung) comments. Wen (vivo) replies to Jicheol (Samsung). Belen (Ericsson) asks to Dimitris on r09 Belen (Ericsson) replies to Vivo Haiyang (Huawei) comments and provides r11 Dimitris (Lenovo) does not support r11 responds to Belen on r09 Changhong (Intel) proposes to go with r09 or r10. Pallab (Nokia) supports the view from Vivo Pallab (Nokia) also does not support r11. Haiyang (Huawei) responds Pallab (Nokia) objects to any revision that indicates VPLMN can provide URSP rules. Provides r12. Belen (Ericsson) objects to r12 and any revisions that restricts the study as those that cannot study the role of the VPLMN Pallab (Nokia) points out that r12 does not restrict role of VPLMN. It only keeps the control in HPLMN. Besides the text in r12 is aligned with agreed SID. Belen (Ericsson) mantains objection to r12, support r11. Yang (OPPO) provides r13. Neutral on HPLMN v.s. VPLMN control of URSP provisioning Belen (Ericsson) responds to Pallab Wen (vivo) comments. Pallab (Nokia) responds to Belen (Ericsson) Belen (Ericsson) disagree with Nokia Pallab (Nokia) disagrees. We cannot allow VPLMN to decide URSP rule under any circumstances. Hong (Qualcomm) comments and prefers r13 wording. Krisztian (Apple) prefers the wording in r12 over r13. Belen (Ericsson) provides r14, objects to r13 and r12. Yang (OPPO) provides r15 based on r14 Belen (Ericsson) provides r16 Dimitris (Lenovo) supports r16 Hong (Qualcomm) provides r17. Changhong (Intel) provides r18, cosigns and proposes to go with r18. Jicheol (Samsung) is okay with r17 and r18 Yang (OPPO) provides concern to r17, 18 and upload r19. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Krisztian (Apple) suggests to move forward with r18. Yang (OPPO) sustains the objection to r17 and r18, suggest to move forward with r19 Jicheol (Samsung) also suggests to go with r19. Wen (vivo) prefers to r19. Belen (Ericsson) prefers r18 Dimitris (Lenovo) prefers r18 Pallab (Nokia) prefers r19 Changhong (Intel) prefers r18 but is OK with approving r19. ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.22 | S2-2201362 | P-CR | Approval | 23.700-85: New KI on WT1 for URSP roaming. | Huawei, HiSilicon, Vivo, Samsung, Nokia, Nokia Shanghai Bell, Qualcomm, Ericsson, Intel | Rel-18 | Revision of S2-2200272r19, merging S2-2200405, merging S2-2200405 and S2-2201046. Approved | Approved | |
| 9.22 | S2-2200620 | P-CR | Approval | 23.700-85: Key Issue: URSP rule provisioning and updating with V-PLMN consideration . | vivo | Rel-18 | Merged into S2-2201757 | Changhong (Intel) proposes to merge it into S2-2200272. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.22 | S2-2200731 | P-CR | Approval | 23.700-85: Key Issue: VPLMN URSP rules in roaming. | Samsung | Rel-18 | Merged into S2-2201757 | Changhong (Intel) proposes to merge it into S2-2200272. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.22 | S2-2200829 | P-CR | Approval | 23.700-85: Key Issue for supporting VPLMN URSP update. | Nokia, Nokia Shanghai Bell | Rel-18 | Merged into S2-2201757 | Changhong (Intel) proposes to merge it into S2-2200272. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.22 | - | - | - | Key Issues for WT#4 | - | - | Docs:=4 | - | |
| 9.22 | S2-2200810 | P-CR | Approval | 23.700-85: Key Issue: 5GC awareness of URSP enforcement. | OPPO | Rel-18 | r15 agreed. Revised to S2-2201363, merging S2-2200185, S2-2200944 and S2-2200694 | Yang (OPPO) provides a merged version as r01 for WT#4 in eUEPO Yang (OPPO) resend the email with updating the title Krisztian (Apple) comments and raises concerns on the Key issue proposal. Changhong (Intel) provides r02. Yang (OPPO) provides r03. Huazhang (vivo) provides r04 based on r03 Dimitris (Lenovo) provides r05 Yang (OPPO) is okay with r04 but disagree with r05 Dimitris (Lenovo) provides clarifications. Does not support r04 or previous versions Hong (Qualcomm) comments and support r05. Krisztian (Apple) provides r06. Yang(OPPO) provides r07. Do not agree r05 and r06. Jicheol (Samsung) provides r08, and cosigned this version. Haiyang (Huawei) is also OK with r08, and please add Huawei as a co-signer for this version. Dimitris (Lenovo) has a question for clarification on r08 Antoine (Orange) provides r09. Yang (OPPO) replies Dimitris (Lenovo) responds to Yang (OPPO). Haiyang (Huawei) has question on r09. Yang (OPPO) provides r10 and open to see bullet-3 added by Orange. Antoine (Orange) replies to Haiyang and provides r11. Belen (Ericsson) provides r12. Antoine (Orange) cannot agree to r12. Iskren (NEC) - Please add NEC as a co-signer. Dieter (Deutsche Telekom) cannot agree to r12. Yang (OPPO) provides r15. Changhong (Intel) provides r13 and r14, cosigns and proposes to go with r14. Jicheol(Samsung) supports r15. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Huazhang (vivo) supports r15, we need to have a general description of KI. Thanks Yang for your supports Changhong (Intel) proposes to approve r15. Haiyang (Huawei) is OK with r15. ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.22 | S2-2201363 | P-CR | Approval | 23.700-85: Key Issue: 5GC awareness of URSP enforcement. | OPPO, Samsung, China Telecom, Orange, Vivo, Huawei, Ericsson, NEC, Intel | Rel-18 | Revision of S2-2200810r15, merging S2-2200185, S2-2200944 and S2-2200694. Approved | Approved | |
| 9.22 | S2-2200944 | P-CR | Approval | 23.760: Key Issue: Verification of applications routed to a specific network connection. | China Telecom, Orange | Rel-17 | Merged into S2-2201363 | Changhong (Intel) proposes to merge it into S2-2200810. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.22 | S2-2200618 | P-CR | Approval | 23.700-85: Key Issue on verification of URSP rule enforcement in UE. | vivo | Rel-18 | Merged into S2-2201625 | Changhong (Intel) proposes to merge it into S2-2200810. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.22 | - | - | - | Key Issues for WT#5 | - | - | Docs:=3 | - | |
| 9.22 | S2-2200664 | P-CR | Approval | 23.700-85: New Key Issue: Provision URSP to UE in EPS. | Intel, Qualcomm, NEC | Rel-18 | r05 agreed. Revised to S2-2201364, merging S2-2201237 | Changhong (Intel) provides r01 merging other papers for WT#5. Belen (Ericsson) provides r02. Changhong (Intel) provides r03 in response to Belen's comment. Changhong (Intel) replies to Dimitris. Dimitris (Lenovo) has a question on r03 Belen (Ericsson) provides r04 Krisztian (Apple) provides r05 to co-sign the Key Issue. Belen (Ericsson) provides r05. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Changhong (Intel) proposes to approve r05. ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.22 | S2-2201364 | P-CR | Approval | 23.700-85: New Key Issue: Provision URSP to UE in EPS. | Intel, Qualcomm, NEC, Nokia, OPPO, Ericsson, Apple, Deutsche Telekom | Rel-18 | Revision of S2-2200664r05, merging S2-2201237. Approved | Approved | |
| 9.22 | S2-2200187 | P-CR | Approval | 23.700-85: WT#5: URSP Rules in EPC. | Ericsson | Rel-18 | Merged into S2-2201768 | Changhong (Intel) proposes to merge it into S2-2200664. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.22 | - | - | - | Key Issue for WT#6 | - | - | Docs:=9 | - | |
| 9.22 | S2-2200828 | P-CR | Approval | 23.700-85: Key Issue for supporting Traffic Category in URSP rules. | Nokia, Nokia Shanghai Bell, Apple, Intel | Rel-18 | CC#5: r17 + changes agreed. Revised to S2-2201858, merging S2-2200271, S2-2200657 and S2-2200797. | Pallab (Nokia) provides r01 merging 0271, 0619, 0657, 0797 Serge (T-Mobile USA) provides r02 adding MNO-specific traffic categories. Farooq (AT&T) comments and provides a revision to add a bullet to KI Farooq (AT&T) respond to Haiyang (Huawei) question DongYeon (Samsung) comments and provides r04 to add the missing parts proposed in 0657. Haiyang (Huawei) provides questions to Farooq (AT&T) Yang (OPPO) provides r06 which further removed the 2nd sentence in bullet-3 based on r05. Krisztian (Apple) responds to DongYeon (Samsung) and provides r05. Krisztian (Apple) responds to Farooq (AT&T) and provides r05. Huazhang (vivo) provides r07 based on r06, combine the bullet of definition of traffic category together Farooq (AT&T) disagrees with deletion in r05, suggests rewording. Susana (Vodafone) agrees with Farooq (AT&T) and provides r08 reinstating the bullet. Farooq(AT&T) responds to Huazhang (vivo) question. Huazhang (vivo) ask a question about: How to avoid app misclassification and hence ensure only the apps belonging to that category get included. DongYeon (Samsung) responds to Yang (OPPO) and provides r09 based on r08, reinstated the 2nd sentence in bullet-3. Yang (OPPO) asks a question about the same bullet raised by vivo Krisztian (Apple) comments and provides r10. Yang (OPPO) responds to DongYeon(Samsung). DongYeon (Samsung) can accept r10. DongYeon (Samsung) replies to Huazhang (vivo) and Yang (OPPO). Huazhang (vivo) replies to DongYeon(Samsung) and Farooq Yang (OPPO) comments to r10 Farooq (AT&T) can accept reworded bullet as provided by Krisztian (Apple) in r10. Susana (Vodafone) is ok with the rewording in r10 Pallab (Nokia) comments on r10 Huazhang (vivo) reply to Pallab (Nokia) and agree this wording changes Haiyang (Huawei) comments. We will not specify how to match a TD. Provides r11. Haiyang (Huawei) responds to Farooq (AT&T) Serge (T-Mobile USA) provides r12 with compromise text. Farooq (AT&T) provides a consolidated response to multiple emails. Accepts only initial text proposed for the bullet or one in r10. Suggests a new requirement as a compromise. Serge (T-Mobile USA) provides r12 with a link this time. Farooq (AT&T) thanks Serge (T-Mobile USA) and Haiyang(Huawei) but cannot agree to r12 or r11. Serge (T-Mobile USA) comments. Haiyang (Huawei) agrees with Serge (T-Mobile USA) and suggests to move forward with r12 Farooq (AT&T) provides r13. Farooq (AT&T) suggests to move forward with r13. Changhong (Intel) proposes to move forward with r13. Krisztian (Apple) provides r14. Belen (Ericsson) comments on r14 Masaharu (KDDI) comments on r14. And please add KDDI as co-signer Serge (T-Mobile USA) is OK to move forward with r14. Farooq (AT&T) provides r15. Pallab(Nokia) provides r16 based on r15. Huazhang (vivo) provides r17 based on r16, and changes the words from Farooq as a note ==== 8.X, 9.X, 10.X Revisions Deadline ==== Huazhang (vivo) is ok to move the sentence in yellow in r16 into a note, and my intention is that when we design solution, that we consider this Changhong (Intel) comments on r17 and proposes to go with r16 with proposed changes. Krisztian (Apple) can accept r17. Changhong (Intel) provides r18 as the compromised version and proposes to move forward with it. Huazhang (vivo) is ok to go ahead r18 and thanks for Changhong's help. Pallab (Nokia) is ok with the proposal in r18. Proposes to mark this for CC#4 for approval as r18 was provided after revision deadline. Haiyang (Huawei) is OK with R18. Changhong (Intel) agrees with Pallab and proposes to mark this for CC#4 approval as r18 was provided after revision deadline. Antoine (Orange) asks what will be proposed for approval at CC#4. Krisztian (Apple) is OK to approve r18 in CC#4 ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.22 | S2-2201858 | P-CR | Approval | 23.700-85: Key Issue for supporting Traffic Category in URSP rules. | Nokia, Nokia Shanghai Bell, Apple, Intel, Huawei, HiSilicon, vivo, Samsung, Lenovo, Motorola Mobility, T-Mobile USA, KDDI | Rel-18 | Revision of S2-2200828r17 + changes, merging S2-2200271, S2-2200657 and S2-2200797. Approved | Approved | |
| 9.22 | S2-2200271 | P-CR | Approval | 23.700-85: New KI for WT#6 on URSP traffic category. | Huawei, HiSilicon | Rel-18 | Merged into S2-2201858 | Changhong (Intel) proposes to merge it into S2-2200828. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.22 | S2-2200657 | P-CR | Approval | 23.700-85: Key Issue on WT6: Support Traffic Category in URSP. | Samsung | Rel-18 | Merged into S2-2201858 | Changhong (Intel) proposes to merge it into S2-2200828. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.22 | S2-2200797 | P-CR | Approval | 23.700-85: Key Issue for supporting traffic categories. | Lenovo, Motorola Mobility | Rel-18 | Merged into S2-2201858 | Changhong (Intel) proposes to merge it into S2-2200828. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.22 | S2-2200005 | LS In | Action | LS from GSMA 5GJA: LS on Traffic Categories in URSP | GSMA 5GJA (5GJA17_104) | - | Revision of Postponed S2-2108257 from S2#148E. Responses drafted in S2-2200270 and S2-2201191. Final response in S2-2201365 | ==== 8.X, 9.X, 10.X Final Deadline ==== | Replied to |
| 9.22 | S2-2201191 | LS OUT | Approval | [DRAFT] Reply LS to GSMA NG 5GJA on Traffic Categories in URSP | Apple | Rel-18 | Revision of (Noted) S2-2108979 from S2#148E. Response to S2-2200005. r05 agreed. Revised to S2-2201365, merging S2-2200270 | Pallab (Nokia) provides r01 Yang (OPPO) provides concern on r01 Pallab (Nokia) clarifies that the reply is going to ENSWI group because 5GJA does not exist anymore and the corresponding work is now happening in ENSWI Yang (OPPO) comments and provide r02 Masaharu (KDDI) comments on to which the reply sends. Yang (OPPO) is fine with r03. Thanks for KDDI's explanation. Pallab (Nokia) comments on r02, r03 and provides r04 Huazhang (vivo) has concerns on r04 and prefer to use r03 Yang (OPPO) has concern to r04, suggest to agree r03 Pallab (Nokia) responds to Yang (OPPO), Huazhang (vivo) and comments that r04 is correct. Krisztian (Apple) provides r05. Pallab (Nokia) is OK with r05. Yang (OPPO) is ok to r5. Changhong (Intel) proposes to go with r05. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.22 | S2-2201365 | LS OUT | Approval | Reply LS to GSMA on Traffic Categories in URSP | SA WG2 | Rel-18 | Revision of S2-2201191r05, merging S2-2200270. Approved | Approved | |
| 9.22 | S2-2200270 | LS OUT | Approval | [DRAFT] Reply LS to GSMA NG 5GJA on Traffic Categories in URSP | Huawei, HiSilicon | Rel-18 | Response to S2-2200005. Merged into S2-2201365 | Changhong (Intel) proposes to merge it into S2-2200191. Pallab (Nokia) points that the correct merged document is S2-2201191 (just to correct chairs notes) ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.22 | - | - | - | Documents exceeding quota | - | - | Docs:=7 | - | |
| 9.22 | S2-2201160 | P-CR | Approval | 23.700-85: TR 23.700-85: New key issue on roaming support for 5G UE Policy. | Qualcomm Incorporated | Rel-18 | Not Handled | ==== 8.X, 9.X, 10.X Final Deadline ==== | - |
| 9.22 | S2-2200859 | P-CR | Approval | 23.700-85: Key issue for WT#4. | Huawei, HiSilicon | Rel-18 | Not Handled | ==== 8.X, 9.X, 10.X Final Deadline ==== | - |
| 9.22 | S2-2200803 | P-CR | Approval | 23.700-85: Key Issue: consistent URSP across 5GC and EPC. | OPPO | Rel-18 | Not Handled | ==== 8.X, 9.X, 10.X Final Deadline ==== | - |
| 9.22 | S2-2200830 | P-CR | Approval | 23.700-85: Key Issue for supporting URSP in EPS. | Nokia, Nokia Shanghai Bell | Rel-18 | Not Handled | ==== 8.X, 9.X, 10.X Final Deadline ==== | - |
| 9.22 | S2-2200619 | P-CR | Approval | 23.700-85: Key Issue on introducing traffic categories in URSP rules. | vivo | Rel-18 | Not Handled | ==== 8.X, 9.X, 10.X Final Deadline ==== | - |
| 9.22 | S2-2200838 | P-CR | Approval | 23.700-85: 23.700-85: Solution for URSP provisioning when a UE is not served by its home operator. | Nokia, Nokia Shanghai Bell | Rel-18 | Not Handled | ==== 8.X, 9.X, 10.X Final Deadline ==== | - |
| 9.22 | S2-2200860 | P-CR | Approval | 23.700-85: Solution for WT#4. | Huawei, HiSilicon | Rel-18 | Not Handled | ==== 8.X, 9.X, 10.X Final Deadline ==== | - |
| 9.23 | - | - | - | Study on Enablers for Network Automation for 5G - Phase 3 (FS_eNA_Ph3) | - | - | Docs:=61 | - | |
| 9.23 | - | - | - | TR skeleton, scope, etc | - | - | Docs:=4 | - | |
| 9.23 | S2-2201066 | P-CR | Approval | 23.700-81: FS_eNA_Ph3 TR Skeleton. | China Mobile, vivo | Rel-18 | Approved | ==== 8.X, 9.X, 10.X Final Deadline ==== | Approved |
| 9.23 | S2-2201073 | P-CR | Approval | 23.700-81: Scope for FS_eNA_Ph3. | China Mobile, vivo | Rel-18 | r01 agreed. Revised to S2-2201617. | Thomas (Nokia) provides r01, objects against r00 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.23 | S2-2201617 | P-CR | Approval | 23.700-81: Scope for FS_eNA_Ph3. | China Mobile, vivo | Rel-18 | Revision of S2-2201073r01. Approved | Approved | |
| 9.23 | S2-2200821 | P-CR | Approval | 23.700-81: Architecture Assumption of TR 23.700-81. | vivo, China mobile | Rel-18 | Approved | ==== 8.X, 9.X, 10.X Final Deadline ==== | Approved |
| 9.23 | - | - | - | WT#1.2: correctness improvements | - | - | Docs:=5 | - | |
| 9.23 | S2-2201136 | P-CR | Decision | 23.700-81: KI: Key Issue for WT#1.2. | Nokia, Nokia Shanghai Bell | Rel-18 | r17 agreed. Revised to S2-2201618, merging S2-2200284, S2-2200354 and S2-2200355 | Fabio Giust (Nokia): Nokia provides r01 Wang Yuan (Huawei) provides comments. Vivian (vivo) provides comments. Aihua(CMCC) provides comments. Mike (InterDigital) provides r02 Malla (NTT DOCOMO) provided comment. Fabio Giust (Nokia): Nokia provides r03. Belen (Ericsson) provides r03, agrees to merge S2-2200284 into this one. Yang (OPPO) objects r04 and support r03. Fabio Giust (Nokia): Nokia objects to r04 Soohwan provides r05 with comments Dimitris (Lenovo) requests clarifications on r05 Manuel (Sandvine): Sandvine provides r06 Aihua(CMCC) provides r10 and co-signs the PCR, and suggests marking S2-2200972 as 'merged' into S2-22001136. Sooohwan (ETRI) provides r09 and replies to Wang Yuan (Huawei) Wang Yuan (Huawei) has concerns on previous versions and provides r08 and co-sign it. Sooohwan (ETRI) provides r07 and replies to Dimitris (Lenovo) and Manuel (Sandvine). Belen (Ericsson) provides r11 and asks a question to ETRI Soohwan (ETRI) replies to Ericsson Fabio Giust (Nokia): Nokia provides r12 Soohwan (ETRI) okay with r12. Jiahui (China Telecom) provides r13 and suggests marking S2-2200809 as 'merged' into S2-22001136. Manuel (Sandvine) provides comments to Jiahui (China Telecom) on r13. To all, we are OK with r12 and co-sign. Vivian (vivo) is OK with r12 and r13, and provides r14 based on r13. And we would like to co-sign. Jiahui (China Telecom) replies to Sandvine. Manuel (Sandvine) provides r16 and would like to confirm co-sign. Leo (Deutsche Telekom) provides r15 and would like to co-sign. Belen (Ericsson) asks a question for clarification Fabio Giust (Nokia): Nokia provides r17 and replies to Belen (Ericsson). Belen (Ericsson) asks a question to Nokia on r17 Manuel (Sandvine) Provides comments to Belen (Ericsson) ==== 8.X, 9.X, 10.X Revisions Deadline ==== Fabio Giust (Nokia) replies to Belen (Ericsson) Manuel (Sandvine) provides r18 Yang (OPPO) confirm co-signing r17 ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.23 | S2-2201618 | P-CR | Decision | 23.700-81: KI: Key Issue for WT#1.2. | Nokia, Nokia Shanghai Bell, Oppo, Vivo, China Telecom, China Mobile, Huawei, HiSilicon, InterDigital, Ericsson, ETRI, Sandvine, Deutsche Telekom | Rel-18 | Revision of S2-2201136r17, merging S2-2200284, merging S2-2200284 and S2-2200354, merging S2-2200284, S2-2200354 and S2-2200355. Approved | Approved | |
| 9.23 | S2-2200284 | P-CR | Approval | 23.700-81: Pseudo-CR on New Key Issue on Mechanisms for Improved Correctness of NWDAF Analytics . | Ericsson | Rel-18 | Merged into S2-2201618 | Wang Yuan (Huawei) asks whether it would be merged to 1136 and also provides comments. Belen (Ericsson) agrees to merge to 1136 Wang Yuan (Huawei) thanks for the clarification and would like to further discuss this in 1136. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.23 | S2-2200354 | P-CR | Approval | 23.700-81: New Key Issues to improve the accuracy of ML model . | ETRI | Rel-18 | Merged into S2-2201618 | Leo (Deutsche Telekom) proposes to merge this pCR into S2-2201136. Soohwan (ETRI) okay to merge this pCR into S2-2201136. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.23 | S2-2200355 | P-CR | Approval | 23.700-81: New Key Issues for enhancement to improve the correctness of NWDAF analytics. | ETRI | Rel-18 | Merged into S2-2201618 | Soohwan (ETRI) proposes to merge this pCR into S2-2201136. Leo (Deutsche Telekom) suggests that this comment will be ignored as it is to the wrong TD. Soohwan (ETRI) suggests to discard this thread. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Soohwan (ETRI) informs that this pCR is merged into S2-2201136. ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.23 | - | - | - | WT#2.1: Application detection | - | - | Docs:=3 | - | |
| 9.23 | S2-2200807 | P-CR | Approval | 23.700-81: New KI on NWDAF involved application detection. | OPPO, Tencent | Rel-18 | r12 agreed. Revised to S2-2201619, merging S2-2201071 | Yang (OPPO) provides a merged version as r01 for WT#2.2 of application detection Wang Yuan (Huawei) provides r02 and co-signs this pCR. Yang (OPPO) asks for clarification. Wang Yuan (Huawei) replies to Yang (OPPO). Yang (OPPO) thanks Yuan's response and provide r03 Belen (Ericsson) provides r04, objects to r03 and previous versions Yang (OPPO) responds to Belen (Ericsson) and propose r05 Aihua(CMCC) provides r05. Aihua(CMCC) provides r06. Belen (Ericsson) provides r07, objects to r05 and r06 Yang (OPPO) is ok with r07. Thomas(Nokia) provides r08. Yang (OPPO) provides r09. Leo (Deutsche Telekom) provides r10. Belen (Ericsson) provides r11 Thomas (Nokia) provides r12 ==== 8.X, 9.X, 10.X Revisions Deadline ==== Yang (OPPO) is fine to agree r12. ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.23 | S2-2201619 | P-CR | Approval | 23.700-81: New KI on NWDAF involved application detection. | OPPO, Tencent, China Mobile, vivo, Huawei, Deutsche Telekom, Ericsson | Rel-18 | Revision of S2-2200807r12, merging S2-2201071. Approved | Approved | |
| 9.23 | S2-2200185 | P-CR | Approval | 23.700-81: WT#3.3: NWDAF assisted application detection. | Ericsson | Rel-18 | Merged into S2-2201363 | Yang (OPPO) proposes to merge it to S2-2200807. Make the discussion in one thread. Belen (Ericsson) agrees to merge this contribution into S2-2200807 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.23 | - | - | - | WT#2.2: Roaming | - | - | Docs:=3 | - | |
| 9.23 | S2-2200935 | P-CR | Approval | 23.700-81: New key issue on data and analytics exchange in roaming case . | vivo, Nokia, Nokia Shanghai Bell | Rel-18 | r11 agreed. Revised to S2-2201620, merging S2-2201120 | Vivian (vivo) provides r01 Zhang (Ericsson) provides comments Farooq (AT&T) provides r02, adding a note to consult GSMA on sharing of user data while roaming Thomas(Nokia) replies to Zhang (Ericsson) Vivian(vivo) replies to Zhang (Ericsson) and provides alternative r03 to choose. Malla (NTT DOCOMO) provides r04. Wang Yuan (Huawei) supports the simplifications which are done in r04 and provide r05 based on r04 with some further simplifications. Zhang (Ericsson) provides r06 and co-sign Zhang (Ericsson) provides comments on r09 and r10 Xiaoyan (CATT) replies to Zhang (Ericsson) and asks for clarification. Vivian(vivo) takes Xiaoyan(CATT) and Zhang(Ericsson) comments into account, and provides r11 trying to make forward. Zhang (Ericsson) is with r11 Xiaoyan (CATT) can live with r11. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.23 | S2-2201620 | P-CR | Approval | 23.700-81: New key issue on data and analytics exchange in roaming case . | Vivo, Nokia, Nokia Shanghai Bell, Ericsson, ZTE, CATT | Rel-18 | Revision of S2-2200935r11, merging S2-2201120. Approved | Approved | |
| 9.23 | S2-2201038 | P-CR | Approval | 23.700-81: FS_eNA_Ph3: Key Issue: data collection and analytic s exchange in roaming case. | ZTE | Rel-18 | Merged into S2-2201834 | Thomas (Nokia) suggests to merge this contribution into S2-2200935 and provides comments Jinguo (ZTE) is ok to merge into 935 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.23 | - | - | - | WT#3.1: Data collection enhancement | - | - | Docs:=4 | - | |
| 9.23 | S2-2201072 | P-CR | Decision | 23.700-81: KI: Key Issue for WT#3.1. | Nokia, Nokia Shanghai Bell, NTT Docomo | Rel-18 | r08 agreed. Revised to S2-2201621. | Fabio Giust (Nokia): Nokia provides r01 Zhang (Ericsson) provides r02 and co-sign Malla (NTT DOCOMO) replies to Zhang (Ericsson). Fabio Giust (Nokia): Nokia objects to r02 and provides comments Xiaoyan (CATT) provides r03 Zhang (Ericsson) provides comments Fabio Giust (Nokia): Nokia provided r04 Vivian (vivo) is OK with r04, and provides r05 trying to merge S2-2200818 with this paper. Juan Zhang (Qualcomm) objects r05. Zhang (Ericsson) provides comments on r04 Vivian replies to comment from Juan Zhang (Qualcomm) . Fabio Giust (Nokia): Nokia replies to Zhang's comments. Xiaoyan (CATT) provides comments to r04. Juan Zhang (Qualcomm) replies to Vivian (vivo). Fabio Giust (Nokia): Nokia replies to comments from Xiaoyan (CATT) Zhang (Ericsson) provides r06 Vivian (vivo) provides r07 with some editorial changes and adds vivo as co-signer. Fabio Giust (Nokia): Nokia provides r08 Fabio Giust (Nokia) provides comments. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Fabio Giust (Nokia) replies to Ericsson Juan Zhang (Qualcomm) is OK with r08. Fabio Giust (Nokia) replies to comments from Ericsson. Zhang (Ericsson) is OK with r07 and object r08 ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.23 | S2-2201621 | P-CR | Decision | 23.700-81: KI: Key Issue for WT#3.1. | Nokia, Nokia Shanghai Bell, NTT DOCOMO, CATT, Ericsson, vivo | Rel-18 | Revision of S2-2201072r08. Approved. CC#5: S2-2201072r07 agreed instead. Revised to S2-2201861. | Revised | |
| 9.23 | S2-2201861 | P-CR | Decision | 23.700-81: KI: Key Issue for WT#3.1. | Nokia, Nokia Shanghai Bell, NTT Docomo | Rel-18 | Revision of S2-2201621 (S2-2201072r07). Approved | Approved | |
| 9.23 | S2-2200818 | P-CR | Approval | 23.700-81: New key issue on data collection enhancement from the UE Application. | vivo | Rel-18 | Noted | Juan Zhang (Qualcomm) provides comment. Mehrdad (Samsung) agrees with Qualcomm. Xiaobo (vivo) provide the clarification. Juan Zhang (Qualcomm) provides comments. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Juan Zhang (Qualcomm) proposes to note the proposal. ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 9.23 | - | - | - | WT#3.2: Model sharing for different vendors | - | - | Docs:=3 | - | |
| 9.23 | S2-2201076 | P-CR | Approval | 23.700-81: KI(WT#3.2): Enhance trained ML Model sharing. | NTT DOCOMO | Rel-18 | r08 agreed. Revised to S2-2201622, merging S2-2200985 and S2-2200345 | Malla (NTT DOCOMO) provides r01 which includes inputs from Vivo (S2-2200817), CATT (S2-2200253) and Ericsson (S2-2200345). Vivian (vivo) provides r02 and adds vivo as co-signer. Zhang (Ericsson) ask for clarification Malla (NTT DOCOMO) replies to Zhang (Ericsson). Wang Yuan (Huawei) provides comments. Vivian provides comments. Dimitris (Lenovo) comments Fabio Giust (Nokia): Nokia provides r03 and adds Nokia as co-signer Vivian (Vivo) provides r04 . Xiaoyan (CATT) provides r05 Hyesung (Samsung) provides r06 Vivian(vivo) provides r07 Vivian (vivo) provides r07 Zhang (Ericsson) provides comments Wang Yuan (Huawei) has concern on previous revisions and provides r08. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Zhang (Ericsson) supports r08 Xiaoyan (CATT) is fine with r08. Malla (NTT DOCOMO) is fine with r08. ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.23 | S2-2201622 | P-CR | Approval | 23.700-81: KI(WT#3.2): Enhance trained ML Model sharing. | NTT DOCOMO, vivo, Nokia, CATT, Samsung | Rel-18 | Revision of S2-2201076r08, merging S2-2200985 and S2-2200345. Approved | Approved | |
| 9.23 | S2-2200345 | P-CR | Approval | 23.700-81: New Key Issue on Whether and how to enhance trained ML Model sharing for different vendors. | Ericsson | Rel-18 | Merged into S2-2201622 | Zhang (Ericsson) indicate the paper can marked as merged into S2-2201076 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.23 | - | - | - | WT#3.3: UPF data reporting | - | - | Docs:=1 | - | |
| 9.23 | S2-2200254 | P-CR | Approval | 23.700-81: Key issue on UPF reporting data to NWDAF. | CATT | Rel-18 | Noted | Thomas (Nokia) objects against this P-CR as no time budget to study the related WT 3.3 was allocated in the SID, only time for normative work Yingying(CATT) replies to Thomas(Nokia) and won't discuss solutions for WT 3.3. Yingying(CATT) provides the r01 in the previous email. Belen (Ericsson) objects to this contributions, all revisions. Thomas(Nokia) maintains the objection, also for r01. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 9.23 | - | - | - | WT#3.7: NWDAF assisted URSP | - | - | Docs:=2 | - | |
| 9.23 | S2-2200801 | P-CR | Approval | 23.700-81: FS_eNA_ph3 KI for WT#3.7: NWDAF-assisted URSP. | China Telecom, vivo | Rel-18 | CC#5: r12 + changes agreed. Revised to S2-2201632. | Jiahui (China Telecom) provides r01. Mehrdad (Samsung) provides r02. Belen (Ericsson) provides r03. Yang (OPPO) provides r04. Dimitris (Lenovo) provides r05 based on r04 Mehrdad (Samsung) suggests to mark S2-2200501 as merged into S2-2200801. Thomas (Nokia) provides r06 Wang Yuan (Huawei) provides r07 and co-signs this KI. Mehrdad (Samsung) provides r08. Thomas (Nokia) provides r09 Jiahui (China Telecom) prefers r08 and provides comment on r09. Yang (OPPO) share the view that use case is important to identify what and how much we need to do in this KI. But no strong opinion on r08 or r09, OPPO would like to co-sign the contribution in next version. Huazhang (vivo) provides r10 based on r09, that add: how to define the new interactions. Mehrdad (Samsung) thinks output should be added on top of r09. Jiahui (China Telecom) provides r11 based on r08, r09 and r10. Thomas (Nokia) accepts r11. Mehrdad (Samsung) is also OK with r11. Belen (Ericsson) provides r12 Mehrdad (Samsung) clarifies that we are also OK with r12. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Thomas (Nokia) objects against r12 Belen (Ericsson) is okay with any revision from the initial version to r05 and r12. Objects to r06,r07,r08,r09,r10 and r11 Mehrdad (Samsung) is also OK with both r11 and r12. We object to r06, r07 and r09. Thomas (Nokia) objects against r00 to r05. OK with revisions from r06 onwards to r11. Asks Belen to reconsider objection against r012 Suggest a NOTE on top of r11 as compromise. Belen (Ericsson) still objects to r12 and ask Thomas to reconsider his objection as well. Proposed NOTE is not acceptable Belen (Ericsson) states that her previous email was incorrect.r12 is okay Belen (Ericsson) is okay with any revision from the initial version to r05 and r12. Objects to r06,r07,r08,r09,r10 and r11 Xiaobo (vivo) proposes a way forward to make progress. Belen (Ericsson) cannot accept Vivo proposal for compromise Xiaobo (vivo) comments and propose to go with the second proposal from Belen(Ericsson). Mehrdad (Samsung) suggests we go with either r11 or r12 based on the change proposed by Ericsson in CC#4 or CC#5. Jiahui(China Telecom) agrees with Belen and proposes to make progress. Thomas(Nokia) can accept proposal of Belen on top of r11 Thomas(Nokia) confirms that compromise is acceptable and suggest that Andy approves r11 (or r12, result is exactly the same) plus proposed change. Then there is no need to waist CC time. Mehrdad (Samsung) suggests to VC please if possible approve r12 and capture in your note that this sentence will be updated Jiahui (China Telecom) provides r13 as the final version. ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.23 | S2-2201632 | P-CR | Approval | 23.700-81: FS_eNA_ph3 KI for WT#3.7: NWDAF-assisted URSP. | China Telecom, vivo, Ericsson, Samsung, Huawei, OPPO | Rel-18 | Revision of S2-2200801r12 + changes. Approved | Approved | |
| 9.23 | - | - | - | KI’s for WT#3.8: QoS sustainability enhancement | - | - | Docs:=3 | - | |
| 9.23 | S2-2200016 | LS In | Action | LS from 5GAA: LS on Enhancements on QoS Sustainability analytics in the context of the Study on Enablers for Network Automation for 5G - phase 3 (FS_eNA_Ph3) | 5GAA (5GAA_S-210186) | Revision of Postponed S2-2108993 from S2#148E. Postponed | LaeYoung (LGE) replies to Yuan (Huawei) and prefers to POSTPONE this LS to prepare a reply LS in the next meeting. Wang Yuan (Huawei) asks for the opinions on how to handle this LS and provides draft LS OUT for S2-2200016. Malla (NTT DOCOMO) agrees with LaeYoung (LGE) to POSTPONE this LS to prepare a reply LS in the next meeting. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Wang Yuan (Huawei) is fine to postpone this LS. ==== 8.X, 9.X, 10.X Final Deadline ==== | Postponed | |
| 9.23 | S2-2200587 | P-CR | Approval | 23.700-81: New KI: QoS Sustainability analytics enhancement on finer granularity area and additional input data. | Huawei, HiSilicon, Tencent, Tencent Cloud | Rel-18 | r16 agreed. Revised to S2-2201623. | Wang Yuan (Huawei) provides r01. LaeYoung (LGE) comments on r01. Antoine (Orange) provides r02 to address LaeYoung's comment. Wang Yuan (Huawei) replies to LaeYoung (LGE). LaeYoung (LGE) cannot accept the last bullet in r01 and r02. Mehrdad (Samsung) provides r03. Juan Zhang (Qualcomm) provides r04. Wang Yuan (Huawei) is fine with r04 and proposes to draft an LS OUT for S2-2200016 from 5GAA when the KI is stable. Malla (NTT DOCOMO) provided a comment. Mehrdad (Samsung) provides r05 and suggests to mark S2-2200502 as merged into S2-2200587 and co-signs the PCR. LaeYoung (LGE) provides r06. Wang Yuan (Huawei) thanks the support and is fine with r05. Wang Yuan (Huawei) thanks for the support and is fine with r06. Fabio Giust (Nokia): Nokia provides r07 and adds Nokia to the co-signers. Wang Yuan (Huawei) thanks the support and is fine with r07, and further provides r08 and r09 based on Malla (NTT DOCOMO)'s comments. We prefer r08, and can live with r09. LaeYoung (LGE) is fine with r08 and r09. Vivian (vivo) provides r11 based on r09 (sorry for some mistake and the invalid r10) and adds vivo as co-signer. Jihoon(ETRI) provides r12. Mehrdad (Samsung) can not agree with r09, r11 or r12. r10 is also invalid. Samsung suggests to add any changes of r11 or r 12 on top of r08 Mehrdad (Samsung) provides r13 based on r12. Malla (NTT DOCOMO) provides r14. Jihoon (ETRI) replies to Mehrdad (Samsung). Boren (OPPO) confirms r14 is OK, would like to co-sign. Mehrdad (Samsung) is also OK with r14 Wang Yuan (Huawei) provides r15 to add OPPO as co-signer, thanks Boren (OPPO). Fabio Giust (Nokia) provides r16 and replies to Malla (Docomo) ==== 8.X, 9.X, 10.X Revisions Deadline ==== LaeYoung (LGE) is fine with r16. Juan Zhang (Qualcomm) is fine with r16. Wang Yuan (Huawei) is fine with r16. Mehrdad (Samsung) is also OK with r16 or r15 or r14. But we object to r09, r10, r11, r12 Malla (NTT DOCOMO) is fine with r16. ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.23 | S2-2201623 | P-CR | Approval | 23.700-81: New KI: QoS Sustainability analytics enhancement on finer granularity area and additional input data. | Huawei, HiSilicon, Tencent, Tencent Cloud, Samsung, LG Electronics, Nokia, Nokia Shanghai Bell, vivo, ETRI, OPPO | Rel-18 | Revision of S2-2200587r16. Approved | Approved | |
| 9.23 | - | - | - | WT#4.1: Federated learning | - | - | Docs:=6 | - | |
| 9.23 | S2-2200346 | P-CR | Approval | 23.700-81: New Key Issue on Study whether and how to enhance architecture to support federated learning in the 5GC. | Ericsson | Rel-18 | Merged into S2-2201624 | Aihua (CMCC) proposes to merge it to S2-2200973. Keep the discussion of the same topic just in one thread. Zhang (Ericsson) confirms the paper is merged into S2-2200973 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.23 | S2-2200784 | P-CR | Approval | 23.700-81: Key Issue for supporting federated learning. | Lenovo, Motorola Mobility | Rel-18 | Merged into S2-2201624 | Soohwan (ETRI) asks for clarification. Dimitris (Lenovo) propose to merge contents in S2-2200973 responds to Soohwan (ETRI) ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.23 | S2-2200984 | P-CR | Approval | 23.700-81: Key issue on support for federated learning in 5GC. | Samsung | Rel-18 | Merged into S2-2201351 (withdrawn). CC#5: Postponed | Aihua (CMCC) proposes to merge it to S2-2200973. Keep the discussion of the same topic just in one thread. David (Samsung) confirms merger into S2-2200973. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Postponed |
| 9.23 | S2-2200815 | P-CR | Approval | 23.700-81: New key issue on Vertical Federated Learning. | vivo | Rel-18 | Merged into S2-2201624 | Vivian (vivo) proposes to merge this pCR into S2-2200973. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.23 | S2-2200973 | P-CR | Approval | 23.700-81: New KI on Supporting Federated Learning among Multiple NWDAF containing MTLFs. | China Mobile, ETRI | Rel-18 | r11 agreed. Revised to S2-2201624, merging S2-2200589, S2-2200346, S2-2200784 and S2-2200815 | Aihua (CMCC) provides r01. Aihua (CMCC) provides r01 with the right link. Yang (OPPO) provides two comments for the change in r01 Zhang (Ericsson) provides comments David (Samsung) provides r02 proposing to merge S2-2200984 into S2-2200973 Farooq (AT&T) provides r03 to add a new bullet. Also adds AT&T as a supporting company. Soohwan (ETRI) provides r04. Juan Zhang (Qualcomm) provides comment. Aihua (CMCC) replies to the comments. Malla (NTT DOCOMO) provided r05. Xiaobo (vivo) provide comments on vertical FL. Farooq (AT&T) provides response to Juan Zhang (Qualcomm). Wang Yuan (Huawei) provides r06. Dimitris (Lenovo) comments Yang (OPPO) comments to Horizontal FL v.s. Vertical FL Xiaobo (vivo) provide comments on vertical FL vs horizontal FL. David (Samsung) comments. Zhang (Ericsson) against to study the FL in general David (Samsung) thanks Zhang for clarifying Ericsson's position, asks questions on HFL definition David (Samsung) thanks Zhang (Ericsson) for his reply Xiaobo (vivo) would like to understand how to only study horizontal FL with current general KI description. Juan Zhang (Qualcomm) provides r07 Zhang (Ericsson) provides r08 David (Samsung) prefers r07 Yang (OPPO) also prefer r07 and suggest to add a NOTE if needed Dimitris (Lenovo) provides r09 based on r07 David (Samsung) cannot accept r09 Dimitris (Lenovo) replies to David (Samsung) David (Samsung) provides r10 Xiaoyan (CATT) asks for clarifications on performance monitoring of FL. Xiaobo (vivo) prefers r10 and would like to co-sign it. David (Samsung) replies to Ericsson Zhang (Ericsson) provides r11 David (Samsung) thanks Zhang (Ericsson) for r11, can live with it Aihua (CMCC): r11 is acceptable for us. Xiaobo (vivo) is ok with r11. Fabio Giust (Nokia) is OK with r11 ==== 8.X, 9.X, 10.X Revisions Deadline ==== Xiaoyan (CATT) is fine with r11 and would like to cosign. Juan Zhang (Qualcomm) is OK with r11 Wang Yuan (Huawei) is OK with r11 Dimitris (Lenovo) is ok with r11 and cosigns ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.23 | S2-2201624 | P-CR | Approval | 23.700-81: New KI on Supporting Federated Learning . | China Mobile, ETRI, vivo, ZTE, Samsung, Lenovo, AT&T, CATT | Rel-18 | Revision of S2-2200973r11, merging S2-2200589, merging S2-2200589 and S2-2200346, merging S2-2200589, S2-2200346 and S2-2200784, merging S2-2200589, S2-2200346, S2-2200784 and S2-2200815. Approved | Approved | |
| 9.23 | - | - | - | WT#4.2: analytics enhancement based on finer granularity of location | - | - | Docs:=3 | - | |
| 9.23 | S2-2200819 | P-CR | Approval | 23.700-81: New KI on enhancement of NWDAF with the benefit from location service. | vivo, CATT, China Telecom, China Mobile, Inspur | Rel-18 | r18 agreed. Revised to S2-2201625, merging S2-2200618 and S2-2200795 | Vivian (vivo) provides comment. Dimitris (Lenovo) provides r02 with questions Vivian (vivo) replies to Dimitris (Lenovo) Juan Zhang (Qualcomm) provides r03. David (Samsung) provides r04. Vivian (vivo) provides comments and gives r05. David (Samsung) confirms r05 is OK, would like to co-sign. Malla (NTT DOCOMO) provides r06. David (Samsung) requests clarification from Docomo. Wang Yuan (Huawei) provides r07 and would like to co-sign this KI. Aoken (Rakuten Mobile) provide the comment would like to co-sign this KI. Vivian(vivo)provides a cleanup r08 and replies to the comment from Aoken (Rakuten Mobile). Malla (NTT DOCOMO) replies to David (Samsung). Dimitris (Lenovo) provides r09 and cosigns David(Samsung)provides r10 Thomas(Nokia)provides r11 Vivian(vivo) provides r12 and replies to comments from Thomas(Nokia). Dimitris (Lenovo) provides r13 Thomas(Nokia)provides r16 Xiaoyan (CATT) provides r15 Vivian(vivo) sorry for the crossed email and my r16, and now provides r17 based on the r16 from Thomas(Nokia) . Vivian(vivo) thanks Xiaoyan (CATT) for providing r15 and raises a comments on it, and provides r16. David(Samsung)provides r18 ==== 8.X, 9.X, 10.X Revisions Deadline ==== Xiaoyan (CATT) is fine with r18 Xiaoyan (CATT) is fine with r18. Vivian (vivo) is also fine with r18. Juan Zhang (Qualcomm) is fine with r18 and askes to add QC as co-signer. Dimitris (Lenovo) ok with r18 ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.23 | S2-2201625 | P-CR | Approval | 23.700-81: New KI on enhancement of NWDAF with the benefit from location service. | Vivo, CATT, China Telecom, China Mobile, Inspur, NTT DOCOMO, Samsung, Huawei, Rakuten Mobile, Lenovo. | Rel-18 | Revision of S2-2200819r18, merging S2-2200618 and S2-2200795. Approved | Approved | |
| 9.23 | S2-2200795 | P-CR | Approval | 23.700-81: Key Issue for WT#4.2. | Lenovo, Motorola Mobility, Toyota | Rel-18 | Merged into S2-2201625 | Thomas (Nokia) suggest to merge this contribution into S2-2200819 ==== 8.X, 9.X, 10.X Revisions Deadline ==== Dimitris (Lenovo) confirms 795 is merged into 819 ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.23 | - | - | - | Documents exceeding quota | - | - | Docs:=24 | - | |
| 9.23 | S2-2200276 | P-CR | Approval | 23.700-81: New KI on Detection of Improved Correctness of an Analytics (WT1.2). | Huawei, HiSilicon | Rel-18 | Not Handled | Wang Yuan (Huawei) confirms this pCR is merged into S2-2201136. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | - |
| 9.23 | S2-2200799 | P-CR | Approval | 23.700-81: New Key Issue: correctness of NWDAF analytics . | OPPO | Rel-18 | Not Handled | ==== 8.X, 9.X, 10.X Final Deadline ==== | - |
| 9.23 | S2-2200809 | P-CR | Approval | 23.700-81: FS_eNA_ph3 KI for WT#1.2: Study possible mechanisms for improved correctness of NWDAF analytics. | China Telecom | Rel-18 | Not Handled | Jiahui (China Telecom) confirms to merge this pCR into S2-2201136. ==== 8.X, 9.X, 10.X Final Deadline ==== | - |
| 9.23 | S2-2200812 | DISCUSSION | Information | Discussion on NWDAF analytics correctness improving | vivo | Rel-18 | Not Handled | ==== 8.X, 9.X, 10.X Final Deadline ==== | - |
| 9.23 | S2-2200813 | P-CR | Approval | 23.700-81: New key issue on NWDAF analytics correctness improving. | vivo | Rel-18 | Not Handled | Vivian (vivo) confirms to merge this pCR into S2-2201136. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | - |
| 9.23 | S2-2200972 | P-CR | Approval | 23.700-81: New KI on possible mechanisms for improved correctness of NWDAF analytics. | China Mobile, InterDigital Inc. | Rel-18 | Not Handled | Aihua (CMCC) confirms this pCR is merged into S2-2201136. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | - |
| 9.23 | S2-2200974 | P-CR | Approval | 23.700-81: New KI on NWDAF-assisted application detection. | China Mobile, vivo | Rel-18 | Not Handled | Aihua (CMCC) confirms this pCR is merged into S2-2200807. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | - |
| 9.23 | S2-2200088 | P-CR | Approval | 23.700-81: Key issue on roaming | Nokia, Nokia Shanghai Bell | Rel-18 | Not Handled | Zhang (Ericsson) asks if this is merged into S2-2200935 Thomas(Nokia) replies ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | - |
| 9.23 | S2-2200251 | P-CR | Approval | 23.700-81: Key issue for support of network analytics in roaming scenarios. | CATT | Rel-18 | Not Handled | Zhang (Ericsson) suggest to merge this CR into S2-2200935 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | - |
| 9.23 | S2-2200252 | P-CR | Approval | 23.700-81: Key issue for data collection and data storage enhancements. | CATT | Rel-18 | Not Handled | Zhang (Ericsson) suggest to merge the paper into S2-2201072 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | - |
| 9.23 | S2-2200253 | P-CR | Approval | 23.700-81: Key issue for enhancing trained ML model sharing for different vendors. | CATT | Rel-18 | Not Handled | Xiaoyan (CATT) confirms that the pCR is merged into S2-2201076 ==== 8.X, 9.X, 10.X Final Deadline ==== | - |
| 9.23 | S2-2200816 | DISCUSSION | Information | Discussion on ML model sharing for different vendors | vivo | Rel-18 | Not Handled | ==== 8.X, 9.X, 10.X Final Deadline ==== | - |
| 9.23 | S2-2200817 | P-CR | Approval | 23.700-81: New key issue on ML model sharing for different vendors . | vivo | Rel-18 | Not Handled | Vivian (vivo) confirms to merge this pCR into S2-2201076. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | - |
| 9.23 | S2-2200588 | P-CR | Approval | 23.700-81: New KI: how to minimize UPF performance degradation due to UPF data reporting. | Huawei, HiSilicon | Rel-18 | WITHDRAWN | Wang Yuan (Huawei) confirms this pCR can be marked as withdrawn. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Withdrawn |
| 9.23 | S2-2200183 | P-CR | Approval | 23.700-81: WT#3.7: NWDAF-assisted URSP. | Ericsson | Rel-18 | Not Handled | ==== 8.X, 9.X, 10.X Final Deadline ==== | - |
| 9.23 | S2-2200501 | P-CR | Approval | 23.700-81: New Key Issue on NWDAF-assisted URSP (WT#3.7). | Samsung | Rel-18 | Not Handled | ==== 8.X, 9.X, 10.X Final Deadline ==== | - |
| 9.23 | S2-2200502 | P-CR | Approval | 23.700-81: New Key Issue on enhancements on QoS Sustainability analytics (WT#3.8). | Samsung, Sandvine | Rel-18 | Not Handled | ==== 8.X, 9.X, 10.X Final Deadline ==== | - |
| 9.23 | S2-2200594 | P-CR | Approval | 23.700-81: New KI for enhancements on QoS Sustainability analytics. | OPPO | Rel-18 | Not Handled | ==== 8.X, 9.X, 10.X Final Deadline ==== | - |
| 9.23 | S2-2200814 | P-CR | Approval | 23.700-81: KI on predictive QoS enhancement in FS_eNA_Ph3. | vivo | Rel-18 | Not Handled | Vivian (vivo) confirms to merge this pCR into S2-2200587. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | - |
| 9.23 | S2-2201036 | P-CR | Approval | 23.700-81: FS_eNA_Ph3: Key Issue for supporting Federated Learning. | ZTE | Rel-18 | Not Handled | ==== 8.X, 9.X, 10.X Final Deadline ==== | - |
| 9.23 | S2-2200250 | P-CR | Approval | 23.700-81: New KI: Support finer granularity of location information. | Qualcomm Incorporated | Rel-18 | Not Handled | ==== 8.X, 9.X, 10.X Final Deadline ==== | - |
| 9.23 | S2-2200823 | P-CR | Approval | 23.700-81: New Key Issue on accuracy enhancements for location analytics (WT#4.2). | Samsung | Rel-18 | Not Handled | ==== 8.X, 9.X, 10.X Final Deadline ==== | - |
| 9.23 | S2-2201078 | P-CR | Approval | 23.700-81: KI (WT#4.2): Finer granular location information. | NTT DOCOMO | Rel-18 | Not Handled | ==== 8.X, 9.X, 10.X Final Deadline ==== | - |
| 9.23 | S2-2201037 | P-CR | Approval | 23.700-81: FS_eNA_Ph3: Key Issue: support of finer granularity location. | ZTE | Rel-18 | Not Handled | ==== 8.X, 9.X, 10.X Final Deadline ==== | - |
| 9.24 | - | - | - | Study on satellite access Phase 2 (FS_5GSAT_Ph2) | - | - | Docs:=18 | - | |
| 9.24 | - | - | - | TR skeleton, scope, etc | - | - | Docs:=6 | - | |
| 9.24 | S2-2200452 | P-CR | Approval | 23.700-28: FS_5GSAT_Ph2 TR Skeleton. | Thales, Xiaomi | Rel-18 | r02 agreed. Revised to S2-2201626. | Haris(Qualcomm) provides comment Stefan (Ericsson) provides comments Jean Yves (Thales) provides r01 integrating Haris and Stefan remarks Sherry (Xiaomi) provides r02. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Jean Yves (Thales) is OK with r02. ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.24 | S2-2201626 | P-CR | Approval | 23.700-28: FS_5GSAT_Ph2 TR Skeleton. | Thales, Xiaomi | Rel-18 | Revision of S2-2200452r02. Approved | Approved | |
| 9.24 | S2-2200453 | P-CR | Approval | 23.700-28: FS_5GSAT_Ph2 TR Scope. | Thales, Xiaomi | Rel-18 | r02 agreed. Revised to S2-2201627. | Haris(Qualcomm) provides r01 Jean Yves(Thales) is ok with r01 Sherry(Xiaomi) provides r02. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Jean Yves(Thales) is ok with r02 ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.24 | S2-2201627 | P-CR | Approval | 23.700-28: FS_5GSAT_Ph2 TR Scope. | Thales, Xiaomi | Rel-18 | Revision of S2-2200453r02. Approved | Approved | |
| 9.24 | S2-2200454 | P-CR | Approval | 23.700-28: FS_5GSAT_Ph2 TR architectural assumptions. | Thales, Xiaomi | Rel-18 | r02 agreed. Revised to S2-2201628. | Haris(Qualcomm) provides r01 Jean Yves (Thales) comments on r01and ask questions to Haris Steve (Huawei) provide r02 Haris(Qualcomm) comments Steve (Huawei) comments Sherry (Xiaomi) provides r03. Jean Yves (Thales) is fine with r03. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Haris(Qualcomm) r03 is not acceptable, suggests to approve r02 at this meeting and fine tune the EPC interworking text later Sherry (Xiaomi) can accept r02 for the progress, but would prefer to discuss about definition of discontinuous coverage issue later. Jean Yves (Thales) can accept also r02 for the progress but is in line with Sherry's comment. Steve (Huawei) is ok with r02 ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.24 | S2-2201628 | P-CR | Approval | 23.700-28: FS_5GSAT_Ph2 TR architectural assumptions. | Thales, Xiaomi | Rel-18 | Revision of S2-2200454r02. Approved | Approved | |
| 9.24 | - | - | - | KI’s related to WT#1.1 | - | - | Docs:=4 | - | |
| 9.24 | S2-2200455 | P-CR | Approval | 23.700-28: FS_5GSAT_Ph2 TR KI related to paging in discontinuous coverage. | Thales, Xiaomi | Rel-18 | Noted | Jean Yves (Thales) comments that this S2-2200455 is proposed as way forward for Key Issue description for discontinuity modelling (title need to be changed). Yuxin (Xiaomi) provides S2-2200455r01 as proposed by rapporteur for Key Issue description for discontinuity modelling. Stefan (Ericsson) provides comments Yuxin (Xiaomi) replies to Stefan (Ericsson) Jean Yves (Thales) comment on introduction of a KI dedicated for Modelling of discontinuous coverage and propose to companies to provide their views Stefan (Ericsson) replies to Jean Yves Steve (Huawei) comments Jean Yves (Thales) agrees with Steve and propose to keep the KI Haris(Qualcomm) provides r02 Stefan (Ericsson) proposes to note the proposal ==== 8.X, 9.X, 10.X Revisions Deadline ==== Jean Yves (Thales) comments on r02 , provides r03 (based on r01),and request co-signers view Jean Yves (Thales) not OK with r02 , OK for r01, request co-signers view to keep or note the KI according the discussion thread Lalith(Samsung) comments Stefan (Ericsson) objects to all revisions ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 9.24 | S2-2200786 | P-CR | Approval | 23.700-28: New key issues on Paging with discontinuous satellite coverage. | vivo | Rel-18 | r04 agreed. Revised to S2-2201629, merging S2-2201040 and S2-2200621 | Jean Yves (Thales) comments that this S2-2200786 is proposed as way forward for Key Issue in relation with mobility management (title need to be changed) Haris(Qualcomm) provides comments Lufeng (vivo) S2-2200786r01 is provided as proposed by rapporteur for Key Issue in relation with mobility management Lufeng (vivo) S2-2200786r02 is provided. Lalith(Samsung) comments. Lufeng (vivo) response to Lalith(Samsung) comments. Stefan (Ericsson) comments Steve (Huawei) comments Lufeng(vivo) response to Steve (Huawei) comments and provide r03 based on the initial 0786 version. Lufeng(vivo) response to Stefan (Ericsson) comments and provide r03. Haris(Qualcomm) provides r04 Lufeng(vivo) response to Haris(Qualcomm) and provides r05 Haris(Qualcomm) responds ==== 8.X, 9.X, 10.X Revisions Deadline ==== Jean Yves (Thales) For the log, Ok for r05 as outcome of the mail thread Yuxin (Xiaomi) can agree the r05 Hannu (Nokia) can live with r05 even though ideally all Key Issues should be solution independent. Lufeng(vivo) response to Haris(Qualcomm) and Dan(Iplook) comment. Steve (Huawei) similar view to Hannu (Nokia), but can live with it. Haris(Qualcomm) accepts r04, r05 contains a lot of incorrect and unecessary text Stefan (Ericsson) supports agreeing r04. Objects to r05. Lufeng(vivo) prefer r05, and can live with r04. ==== 8.X, 9.X, 10.X Final Deadline ==== Jean Yves(Thales) comments on objecting KIs for SID during this meeting | Revised |
| 9.24 | S2-2201629 | P-CR | Approval | 23.700-28: New key issues on Mobility Management enhancement with discontinuous satellite coverage. | Vivo, Thales, Xiaomi, Samsung | Rel-18 | Revision of S2-2200786r04, merging S2-2201040, merging S2-2201040 and S2-2200621. Approved | Approved | |
| 9.24 | S2-2201171 | P-CR | Approval | 23.700-28: Key Issue on WT1.1: Mobility enhancement to support discontinuous coverage. | Samsung | Rel-18 | Merged into S2-2201821 | Jean Yves (Thales) proposes to merge S2-2201171 into S2-2000786 for KI description in relation with mobility management. Stephen (Qualcomm) comments ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.24 | - | - | - | KI’s related to WT#1.2 | - | - | Docs:=6 | - | |
| 9.24 | S2-2200456 | P-CR | Approval | 23.700-28: FS_5GSAT_Ph2 TR KI related to UE power saving in discontinuous coverage. | Thales, Xiaomi | Rel-18 | Merged into S2-2201630 | Jean Yves (Thales) proposes to merge S2-2200456 relevant parts into S2-2000942, for Key Issue description in relation with power saving, and into S2-2000786 for parts in relation with mobility management. Stephen (Qualcomm) comments ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.24 | S2-2200457 | P-CR | Approval | 23.700-28: FS_5GSAT_Ph2 TR KI related with Signalling/data traffic optimization in discontinuous coverage. | Thales, Xiaomi | Rel-18 | Merged into S2-2201821 | Jean Yves (Thales) proposes to merge S2-2200457 relevant parts into S2-2000786 for KI description in relation with mobility management. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.24 | S2-2200787 | P-CR | Approval | 23.700-28: New key issues on Power saving with discontinuous satellite coverage. | vivo | Rel-18 | Merged into S2-2201806 | Jean Yves (Thales) proposes to merge S2-2200787 relevant parts into S2-2000942, for Key Issue description in relation with power saving Stephen (Qualcomm) comments Lufeng(vivo) replies to Stephen (Qualcomm) ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.24 | S2-2200942 | P-CR | Approval | 23.700-28: Key Issue: Power saving enhancement for UE in discontinuous coverage. | Huawei, HiSilicon | Rel-18 | r06? agreed. Revised to S2-2201630, merging S2-2201243 and S2-2200456 | Jean Yves (Thales) comments that this S2-2200942 is proposed as way forward for Key Issue description for power saving. Haris(Qualcomm) asks question for clarification Steve (Huawei) provides r01 as a baseline for further discussion merging the related inputs. Lalith(Samsung) comments on r01 Stephen (Qualcomm) provides an r02 Stefan (Ericsson) provides r03 Haris(Qualcomm) provides r04 Steve (Huawei) comments Haris(Qualcomm) comments Steve (Huawei) provides r05 Chris (Vodafone) provides a more neutral r06 ==== 8.X, 9.X, 10.X Revisions Deadline ==== Jean Yves (Thales) For the log, Ok for r06 as outcome of the mail thread Haris(Qualcomm) r06 is acceptable, r04 is preferred Hannu (Nokia) supports r04 but can also live with r06 even though it needs further work to remove solution specific aspects from the KI later. Lufeng(vivo) is OK for r06. Stefan (Ericsson) proposes to go with r04. Can live with r06. Steve (Huawei) prefers the neutral r06. ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.24 | S2-2201630 | P-CR | Approval | 23.700-28: Key Issue: Power saving enhancement for UE in discontinuous coverage. | Huawei, HiSilicon, Thales, Xiaomi, vivo | Rel-18 | Revision of S2-2200942r06?, merging S2-2201243, merging S2-2201243 and S2-2200456. Approved | Approved | |
| 9.24 | S2-2200941 | P-CR | Approval | 23.700-28: Key Issue: CN awareness of coverage information for UE in discontinuous coverage. | Huawei, HiSilicon | Rel-18 | Merge into revision of S2-2200455 (Noted). Noted | Jean Yves (Thales) proposes to merge S2-2200941 into S2-2000455, for Key Issue description in relation with Modelling of discontinuity ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 9.24 | - | - | - | Solutions | - | - | Docs:=2 | - | |
| 9.24 | S2-2200943 | P-CR | Approval | 23.700-28: Solution for Power Saving based on AMF awareness of coverage information . | Huawei, HiSilicon | Rel-18 | r02 agreed. Revised to S2-2201631. | Haris(Qualcomm) provides comments Stefan (Ericsson) provides comments Steve (Huawei) provides r01 Stefan (Ericsson) replies to Stephen Steve (Huawei) provides r02 ==== 8.X, 9.X, 10.X Revisions Deadline ==== Jean Yves (Thales) For the log, r02 is OK as technically valid idea ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.24 | S2-2201631 | P-CR | Approval | 23.700-28: Solution for Power Saving based on AMF awareness of coverage information . | Huawei, HiSilicon | Rel-18 | Revision of S2-2200943r02. Approved | Approved | |
| 9.25 | - | - | - | Study on UPF enhancement for Exposure And SBA (FS_UPEAS) | - | - | Docs:=24 | - | |
| 9.25 | - | - | - | General (skeleton, scope) | - | - | Docs:=2 | - | |
| 9.25 | S2-2200094 | P-CR | Approval | 23.700-62: TR 23.700-62 FS_UPEAS skeleton | China Mobile | Rel-18 | 23.700-62 TR Skeleton. Approved | ==== 8.X, 9.X, 10.X Final Deadline ==== | Approved |
| 9.25 | S2-2200095 | P-CR | Approval | 23.700-62: Scope of TR 23.700-62 FS_UPEAS | China Mobile | Rel-18 | Approved | ==== 8.X, 9.X, 10.X Final Deadline ==== | Approved |
| 9.25 | - | - | - | Architectural Assumption and requirements | - | - | Docs:=3 | - | |
| 9.25 | S2-2200100 | P-CR | Approval | 23.700-62: TR 23.700-62 FS_UPEAS Architectural assumptions and requirements | China Mobile | Rel-18 | r13 agreed. Revised to S2-2201822, merging S2-2200783 and S2-2201172 | Yan (China Mobile) propose to use this paper as baseline for Arch assumptions and provide r01 merging S2-2201172 Laurent (Nokia): provides r02. OK to merge in 1172 Kefeng Zhang (Qualcomm): provides r03. Yan (China Mobile) is OK with r02 and r03 Fenqin (Huawei):ask a question for clarification Yan (China Mobile) replies Yoohwa (ETRI) asks a question for clarification. Kisuk (Samsung) asks a question for clarification. Kisuk (Samsung) provides comments. Laurent (Nokia): answers Magnus (Ericsson) provides r04 Fenqin (Huawei): ask further question Yan (China Mobile) provides r05 Kefeng Zhang (Qualcomm) objects to r05 Fenqin (Huawei) provides r06 Fenqin (Huawei) provides r07 Fenqin (Huawei) provides r08 Magnus H (Ericsson) provides r09 Fenqin (Huawei) ask a question. Magnus H (Ericsson) answers Fenqin Fenqin (Huawei) provides response. Magnus H (Ericsson) comments Fenqin (Huawei) provides r10. Laurent (Nokia): provides r11 Yan (China Mobile) provides r12 merging S2-2200783 into it Fenqin (Huawei) provides r13. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Yan (China Mobile) is OK with r13 Laurent (Nokia): R13 best version then R12; objects to any other version. ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.25 | S2-2201822 | P-CR | Approval | 23.700-62: TR 23.700-62 FS_UPEAS Architectural assumptions and requirements. | China Mobile | Rel-18 | Revision of S2-2200100r13, merging S2-2200783 and S2-2201172. Approved | Approved | |
| 9.25 | S2-2201172 | P-CR | Approval | 23.700-62: FS_UPEAS Architectural assumptions . | Nokia, Nokia Shanghai Bell | Rel-18 | Merged into S2-2201822 | Yan (China Mobile) propose to merge this paper into S2-2200100 Laurent (Nokia): OK to merge 1172 within 0100; ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.25 | - | - | - | Key Issues | - | - | Docs:=13 | - | |
| 9.25 | S2-2200099 | P-CR | Approval | 23.700-62: Key issue of supporting UPF expose information to other NFs | China Mobile | Rel-18 | r18 agreed. Revised to S2-2201823, merging S2-2200622, S2-2200798, S2-2200994, S2-2201174 and S2-2200822 | Yan (China Mobile) proposes to use this paper as baseline for KI of WT2 and provide r01 Huazhang (vivo) proposes to have an independent part to discuss the NWDAF consumes UPF services and data collection in S2-2200822 Kefeng Zhang (Qualcomm), response to comments from Huazhang and provides r02. Yan (China Mobile) is agree with Kefeng(Qualcomm) and OK with r02 Vivian(vivo) comments on r02 and responses to Kefeng Zhang (Qualcomm). Laurent (Nokia): provides r03 merging in 1174 (I'll propose to merge my 1174 into 099) Vivian (vivo): provides r04 to merge 0822 into 0099. Yoohwa (ETRI) asks a question for my clarification. Yan (China Mobile) replies to Yoohwa(ETRI) Yan (China Mobile) asks clarification on 'direct subscription' Yan (China Mobile) provides r05 Magnus (Ericsson) provides r06 Fenqin (Huawei) comments Dan (China Mobile) comments and provide r07 Yoohwa (ETRI) provides r08. Fenqin (Huawei) comments and provide r09 Yan (China Mobile) provides r10 Magnus H (Ericsson) provides r11 Laurent (Nokia): provides r12 Yan (China Mobile) provides r13 Huazhang (vivo) provides r14 based on r13 that cannot accept the wording of NWDAF related in r12 - r13 Magnus (Ericsson) provides r15 Huazhang (vivo) provides r16 based on r15 Laurent (Nokia): provides r17 Yan (China Mobile) provides r18 ==== 8.X, 9.X, 10.X Revisions Deadline ==== Huazhang (vivo) supports to go with r18 Laurent (Nokia): Prefers R17. Can live with R18.Objects to any other version including R00 Yan (China Mobile) suggests to go with r18 ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.25 | S2-2201823 | P-CR | Approval | 23.700-62: Key issue of supporting UPF expose information to other NFs. | China Mobile, Ericsson, Nokia, Nokia Shanghai Bell | Rel-18 | Revision of S2-2200099r18, merging S2-2200622, S2-2200798, S2-2200994, S2-2201174 and S2-22008. Approved | Approved | |
| 9.25 | S2-2200225 | P-CR | Approval | 23.700-62: KI, WT#1: UPF event exposure service registration, deregistration for discovery with NRF. | Intel | Rel-18 | Merged into S2-2201824 | Yan (China Mobile) propose to merge this S2-2200225 into S2-2201173 Megha(Intel) is ok to merge S2-2200225 into S2-2201173. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.25 | S2-2200621 | P-CR | Approval | 23.700-62: Key Issue on architecture impact of introducing UPF event exposure service. | vivo | Rel-18 | Merged into S2-2201629 | Josep (DT) requests clarification on the intention and objectives of this KI. Sees no result from proposed KI. Yan (China Mobile) proposes to merge this S2-2200621 into S2-2200783 to get a Note sentance that can be added into KI(s) of WT2 Megha(Intel) requests for clarification. Yan (China Mobile) has similar questions and provides some suggestions Huazhang (vivo) reply to Megha(Intel) Laurent (Nokia): Supports Yan to merge this Tdoc into 0099 Yan (China Mobile) replies Fenqin (Huawei) propose to merge this paper with other paper and continue discussion at 0783 thread. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.25 | S2-2200622 | P-CR | Approval | 23.700-62: Key Issue on UPF supported event exposure service. | vivo | Rel-18 | Merged into S2-2201823 | Josep (DT) comments. Yan (China Mobile) proposes to merge this S2-2200622 into S2-2200099 Laurent (Nokia): Supports Yan to merge this Tdoc into 0099 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.25 | S2-2200714 | P-CR | Approval | 23.700-62: KI related with UPF event exposure service(s) to CHF. | Samsung | Rel-18 | Noted | Yan (China Mobile) proposes to merge this S2-2200714 into S2-2200099 Laurent (Nokia): objects to this Tdoc as it sort assumes a non existing requirement Fenqin (Huawei): share the same view as Laurent and not understand where this requirement from. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 9.25 | S2-2200783 | P-CR | Approval | 23.700-62: Key issue on usage and architectural impacts of UPF event exposure service(s). | China Telecom | Rel-18 | Merged into S2-2201822 | Yan (China Mobile) proposes to use S2-2200783 as baseline for WT3 to get a Note sentance that can be added into KI(s) of WT2 and provides r01 Josep (DT) comments. Yan (China Mobile) replies to Josep(DT) Yan (China Mobile) provides r02 Laurent (Nokia): provides r03 Yan (China Mobile) comments on r03 and provides r04 Fenqin (Huawei) comments and propose to merge this paper with 0100. Yan (China Mobile) replies to Fenqin (Huawei) Laurent (Nokia): provides r05 Yan (China Mobile) proposes to merge this S2-2200783 into S2-2200100 ==== 8.X, 9.X, 10.X Revisions Deadline ==== Laurent (Nokia): objects for the sake of merging (per the rapporteur suggestion) to any version of this Tdoc ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.25 | S2-2200798 | P-CR | Approval | 23.700-62: Subscription to UPF event exposure service(s) via Nupf. | Samsung | Rel-18 | Merged into S2-2201823 | Yan (China Mobile) proposes to merge this S2-2200798 into S2-2200099 Laurent (Nokia): Suggests to merge in 1173 instead Yan (China Mobile) replies to Laurent(Nokia) and still suggests to merge in 0099 Fenqin (Huawei) propose to merge to 1173 Yan (China Mobile) asks for Kisuk's suggestion Huazhang (vivo) prefers to merge this paper to 2200099 Yan (China Mobile) agrees with Huazhang (vivo) and proposes to merge this S2-2200798 into S2-2200099 ==== 8.X, 9.X, 10.X Revisions Deadline ==== Kisuk (Samsung) agrees with merging into S2-2200099 ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.25 | S2-2201173 | P-CR | Approval | 23.700-62: FS_UPEAS new KI: study direct subscription to the UPF for UPF event exposure services. | Nokia, Nokia Shanghai Bell | Rel-18 | r11 agreed. Revised to S2-2201824, merging S2-2200225 | Yan (China Mobile) propose to use this paper as baseline for KI of WT1 and provide r01 Magnus H (Ericsson) comments Huazhang (vivo) comments Yan (China Mobile) agrees with Huazhang and provides r02 Yan (China Mobile) comments Magnus (Ericsson) provides r03 Kefeng Zhang (Qualcomm) asks a question to Magnus (Ericsson). Laurent (Nokia): provides r04 Kefeng Zhang (Qualcomm) provides r05 Huazhang (vivo) provides r06 to delete the overlap parts of UPF event exposure in 0099 Magnus H (Ericsson) ask question Saso (Intel) asks clarification on 'certain UE'. Yan (China Mobile) provides r07 Kefeng Zhang (Qualcomm) reply to Magnus H (Ericsson) Magnus H (Ericsson) answers Saso (Intel) Fenqin (Huawei) provides r08. Magnus H (Ericsson) provides r09 Laurent (Nokia): provides r10 Yan (China Mobile) provides r11 with editorial update and proposes to merge S2-2200098 into this S2-2201173 ==== 8.X, 9.X, 10.X Revisions Deadline ==== Huazhang (vivo) prefers to go with provides r11 Megha(Intel) ok with r11. ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.25 | S2-2201824 | P-CR | Approval | 23.700-62: FS_UPEAS new KI: study UPF event exposure service registration and discovery. | Nokia, Nokia Shanghai Bell, China Mobile | Rel-18 | Revision of S2-2201173r11, merging S2-2200225. Approved | Approved | |
| 9.25 | S2-2201174 | P-CR | Approval | 23.700-62: FS_UPEAS new KI: define requirements of UPF event exposure service(s). | Nokia, Nokia Shanghai Bell | Rel-18 | Merged into S2-2201823 | Megha(Intel) provides r01. Yan (China Mobile) provides r02 Yan (China Mobile) proposes to merge this S2-2201174r02 into S2-2200099 Megha(Intel) provides comments. Yan (China Mobile) replies to Megha(Intel) Magnus H (Ericsson) supports to merge this 1174r02 into 0099 Laurent (Nokia): ok and proposes to merge (my) 1174 into 0099 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.25 | S2-2200822 | P-CR | Approval | 23.700-62: New key issue on UPF data collecting for NWDAF. | vivo | Rel-18 | Merged into S2-2201823 | Yan (China Mobile) proposes to merge this S2-2200822 into S2-2200099 Huazhang (vivo) proposes to keep this paper alone to discuss the NWDAF consume UPF's service and data collection Magnus H (Ericsson) Supports Yan to merge 0822 into 0099 Laurent (Nokia): Supports Yan and Magnus to merge 0822 into 0099 Kefeng Zhang (Qualcomm): Supports to merge 0822 into 0099 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.25 | S2-2200994 | P-CR | Approval | 23.700-62: New key issue: UPF exposure service for reporting measured data . | ETRI | Rel-18 | Merged into S2-2201823 | Yan (China Mobile) proposes to merge this S2-2200994 into S2-2200099 Magnus H (Ericsson) proposes to merge 0994 into 0099 Kefeng Zhang (Qualcomm) supports to merge 0994 into 0099. Yoohwa (ETRI) agrees to merge 0994 into 0099. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.25 | - | - | - | Solutions | - | - | Docs:=4 | - | |
| 9.25 | S2-2200226 | P-CR | Approval | 23.700-62: KI, WT#1, Solution: UPF Event Exposure Service Framework. | Intel | Rel-18 | r07 agreed. Revised to S2-2201825. | Stefan (Ericsson) provides comments and questions Megha(Intel) replies to questions from Stefan(Ericsson). Yan (China Mobile) asks clarification on ' Event Exposure support indicator' Yan (China Mobile) corrects the name mistake and sends again Megha(Intel) replies to Yan(China Mobile). Fenqin (Huawei) comments Yan (China Mobile) comments Stefan (Ericsson) comments and provides r01 Megha provides r02 and comments. Stefan (Ericsson) provides comments on r02 Megha provides r03 and comments. Fenqin (Huawei) provides r04 Magnus H (Ericsson) comments Megha provides r05 and comments. Stefan (Ericsson) provides r06 (please ignore) and r07 ==== 8.X, 9.X, 10.X Revisions Deadline ==== Megha(Intel) is ok with r03,r05,r07. Fenqin (Huawei) is ok with r07 Yan (China Mobile) suggests to go with r07 ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.25 | S2-2201825 | P-CR | Approval | 23.700-62: KI, WT#1, Solution: UPF Event Exposure Service Framework. | Intel | Rel-18 | Revision of S2-2200226r07. Approved | Approved | |
| 9.25 | S2-2201175 | P-CR | Approval | 23.700-62: FS_UPEAS Analysis of requirements of UPF event exposure service(s). | Nokia, Nokia Shanghai Bell | Rel-18 | r02 agreed. Revised to S2-2201826. | Stefan (Ericsson) provides comments Laurent (Nokia): provides r01 Megha(Intel) provides comments Fenqin (Huawei) provides comments Yan (China Mobile) suggests to put this S2-2201175 into the Annex clause and provides r02 Laurent (Nokia): answers, agrees to create an Annex ==== 8.X, 9.X, 10.X Revisions Deadline ==== Megha(Intel) is ok with r02. Yan (China Mobile) suggests to go with r02 Fenqin (Huawei) is ok with r02 ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.25 | S2-2201826 | P-CR | Approval | 23.700-62: FS_UPEAS: Annex for NWDAF requirements of UPF event exposure service(s). | Nokia, Nokia Shanghai Bell | Rel-18 | Revision of S2-2201175r02. Approved | Approved | |
| 9.25 | - | - | - | Not Handled | - | - | Docs:=2 | - | |
| 9.25 | S2-2200098 | P-CR | Approval | 23.700-62: Key issue of UPF event exposure service registration and discovery through NRF | China Mobile | Rel-18 | Not Handled | Yan (China Mobile) propose to merge this S2-2200098 into S2-2201173 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | - |
| 9.25 | S2-2200623 | P-CR | Approval | 23.700-62: Key Issue on registration and discovery of service-based UPF. | vivo | Rel-18 | Not Handled | Yan (China Mobile) propose to merge this S2-2200623 into S2-2201173 Magnus H (Ericsson) supports the propose to merge 0623 into 1173 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | - |
| 9.26 | - | - | - | Study on Proximity-based Services in 5GS Phase 2 (FS_5G_ProSe_Ph2) | - | - | Docs:=47 | - | |
| 9.26 | - | - | - | General | - | - | Docs:=8 | - | |
| 9.26 | S2-2200739 | P-CR | Approval | 23.700-33: Skeleton for TR 23.700-33 | OPPO, CATT | Rel-18 | 23.700-33 TR Skeleton. Approved | ==== 8.X, 9.X, 10.X Final Deadline ==== | Approved |
| 9.26 | S2-2200740 | P-CR | Approval | 23.700-33: Scope for 5G_ProSe Ph2 TR. | OPPO, CATT | Rel-18 | Approved | ==== 8.X, 9.X, 10.X Final Deadline ==== | Approved |
| 9.26 | S2-2200677 | P-CR | Approval | 23.700-33: Architectural Assumption for Layer-3 U2N Relay with N3IWF. | Sony | Rel-18 | Noted | Lars (Sony) asks as author of the tdoc to mark it NOTED. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 9.26 | S2-2200741 | P-CR | Approval | 23.700-33: Architecture Requirement and Assumption for FS_5G_ProSe_Ph2. | OPPO, CATT | Rel-18 | r04 agreed. Revised to S2-2201366, merging S2-2200748 | Fei (OPPO) provides r01 which has merged S2-2201186. Judy (Ericsson) ask a question Hong (Qualcomm) comments. Fei (OPPO) provides r02 and responds to Hong (Qualcomm) and Judy (Ericsson) Steve (Huawei) Hannu (Nokia) provides r03 and comments. Steve (Huawei) comments, r03 is not acceptable. Fei (OPPO) provides r04. Hannu (Nokia) supports r04. Steve (Huawei) provides r05 ==== 8.X, 9.X, 10.X Revisions Deadline ==== Hannu (Nokia) proposes to go back to r04 accepting that the corresponding note on scope limitation will be removed from the KI (in another document) Steve (Huawei) prefers r04, objects to all other revisions (for clarity) Judy (Ericsson) comments. ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.26 | S2-2201366 | P-CR | Approval | 23.700-33: Architecture Requirement and Assumption for FS_5G_ProSe_Ph2. | OPPO, CATT | Rel-18 | Revision of S2-2200741r04, merging S2-2200748. Approved | Approved | |
| 9.26 | S2-2201186 | P-CR | Approval | 23.700-33: Architecture Assumption for FS_5G_ProSe_Ph2. | Xiaomi | Rel-18 | Merged into S2-2201334 | Fei (OPPO) proposes to merge this paper to S2-2200741. Jianning (Xiaomi) is ok to merge into S2-2200741. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.26 | S2-2200375 | P-CR | Approval | 23.700-33: Terms related to U2U relay. | LG Electronics | Rel-18 | r02 agreed. Revised to S2-2201367. | Fei (OPPO) provides r01. LaeYoung (LGE) is OK with r01 and asks a Q about how to reflect these terms to the pCRs for U2U relay. Fei (OPPO) responds to LaeYoung (LGE) LaeYoung (LGE) replies to Fei (OPPO). Steve (Huawei) comments Judy (Ericsson) comments. Hao Dong (ZTE) comments. LaeYoung (LGE) provides r02. Deng Qiang (CATT) provides r03. LaeYoung (LGE) comments on r03. Xiaoyan Shi (Interdigital) agrees with LaeYoung and we should be careful to extent Remote UE terminology for U2U relay. Fei (OPPO) also agree with the comment of extending the remote UE. Hannu (Nokia) proposes to note r03 and to approve r02 instead. Fei (OPPO) is ok with r02. LaeYoung (LGE) also proposes to go with r02. Deng Qiang (CATT) is ok with r02. Xiaoyan Shi (Interdigital) is ok with r02. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.26 | S2-2201367 | P-CR | Approval | 23.700-33: Terms related to U2U relay. | LG Electronics | Rel-18 | Revision of S2-2200375r02. Approved | Approved | |
| 9.26 | - | - | - | New Key Issue1- UE-to-UE relay | - | - | Docs:=4 | - | |
| 9.26 | S2-2200463 | P-CR | Approval | 23.700-33: New Key Issue on Support of UE-to-UE Relay. | Ericsson | Rel-18 | Merged into S2-2201368 | Steve (Huawei) It is suggested this is marked as merged into S2-2200932, as per rapporteur suggestion. Zhang (Ericsson) confirms to merge this paper into S2-2200932 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.26 | S2-2200932 | P-CR | Approval | 23.700-33: KI proposal for U2U Relay. | Huawei, HiSilicon, vivo | Rel-18 | r08 agreed. Revised to S2-2201368, merging S2-2200718 and S2-2200463 | Steve (Huawei) provides r01, merging S2-2200463 & S2-2201120 LaeYoung (LGE) asks some questions on r01. Fei (OPPO) asks question on the below bullet Steve (Huawei) comments Xiaoyan Shi (Interdigital) replies and provide r02. LaeYoung (LGE) asks a Q. Deng Qiang (CATT) comments. Zhang (Ericsson) provides comments Fei (OPPO) comments. Mehrdad (Samsung) provides r03 Steve (Huawei) provides r04 Zhang (Ericsson) provides r05 and co-sign Mehrdad (Samsung) comments on r4 and r05 Fei (OPPO) provides comments on top of Zhang's comment Wen (vivo) comments Walter (Philips) proposes r06 Steve (Huawei) asks a question Mehrdad (Samsung) provides r08 and co-signs the PCR. Steve (Huawei) provides r07 ==== 8.X, 9.X, 10.X Revisions Deadline ==== Mehrdad (Samsung) is OK with r08 but we object to all other revisions of the PCR. Hannu (Nokia) shares Steve's question but can live with r08. Mehrdad (Samsung) replies to Nokia. Steve (Huawei) comments, I believe r07 says what you mean. Zhang (Ericsson) prefers r07, can live with r08 Xiaoyan Shi (Interdigital) prefers r07, can live with r08 Wen (vivo) prefers r07, can live with r08 as well ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.26 | S2-2201368 | P-CR | Approval | 23.700-33: KI proposal for U2U Relay. | Huawei, HiSilicon, vivo, Interdigital Inc., Ericsson, Samsung, CATT | Rel-18 | Revision of S2-2200932r08, merging S2-2200718, merging S2-2200718 and S2-2200463. Approved | Approved | |
| 9.26 | S2-2201120 | P-CR | Approval | 23.700-33: New KI: Support of UE-to-UE Relay. | Interdigital | Rel-18 | Merged into S2-2201620 | Steve (Huawei) It is suggested this is marked as merged into S2-2200932, as per rapporteur suggestion. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.26 | - | - | - | Solutions for Key Issue 1 - UE-to-UE relay | - | - | Docs:=6 | - | |
| 9.26 | S2-2200139 | P-CR | Approval | 23.700-33: TR 23.700-33: Moving UE-to-UE Relay interim conclusions from TR 23.752 into TR 23.700-33 | CATT, OPPO | Rel-18 | Postponed | Lars (Sony) It is too early to start adding text to the conclusion clause. Xiaoyan Shi (Interdigital) share same view with Lars and proposes to postpone this contribution. Mehrdad (Samsung) shares similar view as InterDigital and Sony. Steve (Huawei) supports the intention of the pCR Mehrdad (Samsung) suggests to postpone this PCR. Jianning (Xiaomi) shares view that it is too early to start the conclusion Hannu (Nokia) supports the proposal to postpone this document Deng Qiang (CATT) is fine to be postponed and collects views on handling of Rel-17 UE-UE Relay solutions. Changhong (Intel) shares same view with Samsung and Nokia, proposes to postpone this paper. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Postponed |
| 9.26 | S2-2200624 | P-CR | Approval | 23.700-33: Consolidated solution for UE-to-UE Relay discovery and selection based on Model A and Model B discovery. | OPPO | Rel-18 | Postponed | Zhang (Ericsson) provides comments Yali (OPPO) replies to Zhang (Ericsson) and provides r01 Steve (Huawei) comments Xiaoyan Shi (Interdigital) comments Yali (OPPO) provides r02 Mehrdad (Samsung) suggests to postpone this PCR. Fei suggests to agree some solutions for U2U relay an Path swithing between PC5 and Uu in this meeting. Mehrdad (Samsung) thinks agreeing on any solution during KI discussion is not procedurally correct and also not fair to others. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Mehrdad (Samsung) objects to all revisions of this PCR and suggests to postpone. ==== 8.X, 9.X, 10.X Final Deadline ==== | Postponed |
| 9.26 | S2-2200625 | P-CR | Approval | 23.700-33: Consolidated solution for L3 UE-to-UE Relay communication setup after Model A and Model B discovery. | OPPO | Rel-18 | Postponed | Zhang (Ericsson) provides comments Yali (OPPO) replies to Zhang (Ericsson) and provides r01 Steve (Huawei) comments Yali (OPPO) replies to Steve (Huawei) Mehrdad (Samsung) suggests to postpone this PCR. Fei suggests to agree some solutions for U2U relay an Path swithing between PC5 and Uu in this meeting. Yali (OPPO) provides r02 to address the comments from Zhang (Ericsson) and Steve (Huawei). Zhang (Ericsson) thanks Yali (OppO) and provides r03 and co-sign Mehrdad (Samsung) thinks agreeing on any solution during KI discussion is not procedurally correct and also not fair to others. Xiaoyan Shi (interdigital) asks question for clarification. Hong (Qualcomm) comments. Yali (OPPO) provides r04. Zhang (Ericsson) provides comments on r04 Yali (OPPO) replies to Zhang and provides r05 Zhang (Ericsson) provides r06 Yali (OPPO) replies to Hong(Qualcomm) ==== 8.X, 9.X, 10.X Revisions Deadline ==== Yali (OPPO) asks Mehrdad and others, whether possible to agree this pCR in this meeting. Mehrdad (Samsung) objects to all revisions of this PCR and suggests to postpone. ==== 8.X, 9.X, 10.X Final Deadline ==== | Postponed |
| 9.26 | S2-2200632 | DISCUSSION | Agreement | Discussion for UE-to-UE Relay discovery integrated into PC5 unicast link establishment. | OPPO | Rel-18 | Noted | ==== 8.X, 9.X, 10.X Final Deadline ==== | Noted |
| 9.26 | S2-2201121 | P-CR | Approval | 23.700-33: Solution: UE-to-UE Relay Reselection. | Interdigital | Rel-18 | Postponed | Yali (OPPO) prefer don't copy the U2U solutions which are already captured in TR 23.752 to the new TR. Mehrdad (Samsung) suggests to postpone this PCR. Xiaoyan Shi (interdigital) would ask whether all solutions are postponed and whether not allowed to moved solutions in R17 to R18. If there is any agreement, then it's fine that this contribution will follow the agreement. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Mehrdad (Samsung) objects to all revisions of this PCR and suggests to postpone. ==== 8.X, 9.X, 10.X Final Deadline ==== | Postponed |
| 9.26 | S2-2201227 | P-CR | Approval | 23.700-33: TR 23.700-33 New solution to support Layer-3 UE-to-UE Relay. | Qualcomm Incorporated | Rel-18 | Postponed | Steve (Huawei) comments Yali (OPPO) comments Mehrdad (Samsung) suggests to postpone this PCR. Fei suggests to agree some solutions for U2U relay an Path swithing between PC5 and Uu in this meeting. Mehrdad (Samsung) thinks agreeing on any solution during KI discussion is not procedurally correct and also not fair to others. Mehrdad (Samsung) thinks all solutions should be postponed to the next meeting Hong (Qualcomm) asks for clarification on procedures and whether all solutions should be NOTED this meeting. Fei clarified Changhong (Intel) shares same view with Samsung, proposes to postpone this paper. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Mehrdad (Samsung) objects to all revisions of this PCR and suggests to postpone. ==== 8.X, 9.X, 10.X Final Deadline ==== | Postponed |
| 9.26 | - | - | - | New Key Issue 2 -Path switch between two indirect network communication paths | - | - | Docs:=2 | - | |
| 9.26 | S2-2200706 | P-CR | Approval | 23.700-33: KI#X: Support of path switch between two indirect network communication paths for UE-to-Network Relay with service continuity consideration. | vivo | Rel-18 | r04 agreed. Revised to S2-2201369. | Judy (Ericsson) provides r01 Wen (vivo) is ok with the changes in r01 Deng Qiang (CATT) provides r02. Fei (OPPO) comments and provides r03. Lars (Sony) comments do we need all combinations. Wen (vivo) comments. Deng Qiang (CATT) prefers focused scenarios. Wen (vivo) replies. Lars (Sony) comments. Steve (Huawei) comments Wen (vivo) replies and provides r04 ==== 8.X, 9.X, 10.X Revisions Deadline ==== Deng Qiang (CATT) is ok with r04. Hannu (Nokia) can live with r04. The list of use cases is a bit of an overkill, but the list of topics for study looks good. ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.26 | S2-2201369 | P-CR | Approval | 23.700-33: KI#X: Support of path switch between two indirect network communication paths for UE-to-Network Relay with service continuity consideration. | Vivo, Ericsson, CATT | Rel-18 | Revision of S2-2200706r04. Approved | Approved | |
| 9.26 | - | - | - | New Key Issue 3- path switching between direct Uu path and direct PC5 path | - | - | Docs:=7 | - | |
| 9.26 | S2-2200136 | P-CR | Approval | 23.700-33: TR 23.700-33: Key Issue on path switching between direct Uu path and direct PC5 path | CATT | Rel-18 | Merged into S2-2201370 | Fei (OPPO) proposed to mark merged into S2-2200540 Deng Qiang (CATT) confirmed this paper can be merged into S2-2200540 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.26 | S2-2200464 | P-CR | Approval | 23.700-33: New Key Issue on Support Path Switching between PC5 and Uu (non-relay case). | Ericsson | Rel-18 | Merged into S2-2201370 | Fei (OPPO) proposed to mark merged into S2-2200540 Judy (Ericsson) confirmed this paper is merged to S2-2200540. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.26 | S2-2200499 | P-CR | Approval | 23.700-33: New Key Issue on path switching between direct Uu path and direct PC5 path. | Samsung | Rel-18 | Merged into S2-2201370 | Fei (OPPO) proposed to mark merged into S2-2200540 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.26 | S2-2200540 | P-CR | Approval | 23.700-33: TR 23.700-33: Rel18 ProSe_Ph2 KI on direct path switching. | China Telecom | Rel-18 | r12 agreed. Revised to S2-2201370, merging S2-2200977, S2-2200136, S2-2200464, S2-2200499 and S2-2200716 | Changzheng (China Telecom) provides r01 merging S2-2200136, S2-2200464, S2-2200499, S2-2200716 and S2-2200933, using S2-2200540 as a baseline. Fei (OPPO) corrects the title and link of r01 provided Changzheng (China Telecom). Xiaoyan Shi (Interdigital) provides r02. Judy (Ericsson) provides r03. Mehrdad (Samsung) provides r04 and confirms merging S2-2200499 into S2-2200540r04. Steve (Huawei) provides r05 LaeYoung (LGE) provides r08. Xiaoyan Shi (Interdigital) provides r07. Deng Qiang (CATT) provides r06. Changzheng (China Telecom) supports r05. Judy (Ericsson) provide r09. Steve (Huawei) comments Mehrdad (Samsung) supports removing NOTE 3. Changzheng (China Telecom) provide r10. Mehrdad (Samsung) comments on r10 and clarifies to China Telecom that several companies expected a version of NOTE 2 to be included. It is not OK to remove it. Steve (Huawei) provides r11 and cosigns. Judy (Ericsson) comments Deng Qiang (CATT) comments. Steve (Huawei) provides r12 Mehrdad (Samsung) is fine with r11 and also can live with r12 if the NOTE is covered in the Architecture Requirements. Hannu (Nokia) proposes to go back to r11 ==== 8.X, 9.X, 10.X Revisions Deadline ==== Hannu (Nokia) changes his mind following the discussion on S2-2200741. Now prefers r12 (can still live with r11, but assumes Steve does not like it?) Steve (Huawei) prefers r12, objects to all other revisions (for clarity) Xiaoyan Shi (Interdigital) prefers r12, but can live with r11. ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.26 | S2-2201370 | P-CR | Approval | 23.700-33: TR 23.700-33: Rel18 ProSe_Ph2 KI on direct path switching. | China Telecom, ZTE, Ericsson, Samsung, CATT, Interdigital Inc., Huawei, HiSilicon | Rel-18 | Revision of S2-2200540r12, merging S2-2200977, merging S2-2200977 and S2-2200136, merging S2-2200977, S2-2200136 and S2-2200464, merging S2-2200977, S2-2200136, S2-2200464 and S2-2200499, merging S2-2200977, S2-2200136, S2-2200464, S2-2200499 and S2-22007 | Approved | |
| 9.26 | S2-2200716 | P-CR | Approval | 23.700-33: Key Issue on Path Switch between Uu and PC5 for Direct Communication. | ZTE | Rel-18 | Merged into S2-2201370 | Fei (OPPO) proposed to mark merged into S2-2200540 Hao Dong (ZTE) confirms this paper is merged into S2-2200540. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.26 | S2-2200933 | P-CR | Approval | 23.700-33: KI proposal for path switch between Uu and PC5. | Huawei, HiSilicon | Rel-18 | Merged into S2-2201350 | Fei (OPPO) proposed to mark merged into S2-2200540 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.26 | - | - | - | Solutions for Key Issue 3- path switching between direct Uu path and direct PC5 path | - | - | Docs:=2 | - | |
| 9.26 | S2-2200137 | P-CR | Approval | 23.700-33: TR 23.700-33: New solution on direct communication path switching between PC5 and Uu reference points | CATT | Rel-18 | Postponed | LaeYoung (LGE) provides comment. Hao Dong (ZTE) supports the LGE's suggestion and provides r01. Xiaoyan Shi (Interdigital) provides r02. Judy (Ericsson) provides r03 Mehrdad (Samsung) suggests to postpone this PCR. Steve (Huawei) comments Fei suggests to agree some solutions for U2U relay an Path swithing between PC5 and Uu in this meeting. Mehrdad (Samsung) thinks agreeing on any solution during KI discussion is not procedurally correct and also not fair to others. Changhong (Intel) shares same view with Samsung, proposes to postpone this paper. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Mehrdad (Samsung) objects to all revisions of this PCR and suggest to postpone ==== 8.X, 9.X, 10.X Final Deadline ==== | Postponed |
| 9.26 | S2-2200934 | P-CR | Approval | 23.700-33: Solution for path switching between PC5 and Uu communication paths. | Huawei, HiSilicon | Rel-18 | Postponed | LaeYoung (LGE) asks some questions. Fei (OPPO) also asks questions regarding step 5 Zhang (Ericsson) provides comments Deng Qiang (CATT) provides comments. Wen (vivo) provides comments Mehrdad (Samsung) suggests to postpone this PCR. Steve (Huawei) provides r01. LaeYoung (LGE) provides r02. Fei suggests to agree some solutions for U2U relay an Path swithing between PC5 and Uu in this meeting. Mehrdad (Samsung) thinks agreeing on any solution during KI discussion is not procedurally correct and also not fair to others. Changhong (Intel) shares same view with Samsung, proposes to postpone this paper. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Mehrdad (Samsung) objects to all revisions of this PCR and suggests to postpone. ==== 8.X, 9.X, 10.X Final Deadline ==== | Postponed |
| 9.26 | - | - | - | New Key Issue 4 - Path switch for Layer- 2 UE-to-Network Relay | - | - | Docs:=2 | - | |
| 9.26 | S2-2200707 | P-CR | Approval | 23.700-33: KI X: Support of path switch between direct network communication path and indirect network communication path for Layer-2 UE-to-Network Relay. | vivo | Rel-18 | r04 agreed. Revised to S2-2201371. | Sudeep (Apple) provides r01. Judy (Ericsson) provide r02. Fei (OPPO) asks questions on the relay UE id management Sudeep (Apple) responds to comments. Deng Qiang (CATT) provides r03. Fei (OPPO) responds to Sudeep (Apple) Steve (Huawei) comments Heng (China Telecom) comments Wen (vivo) replies and provides r04 Fei (OPPO) comments on r04. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.26 | S2-2201371 | P-CR | Approval | 23.700-33: KI X: Support of path switch between direct network communication path and indirect network communication path for Layer-2 UE-to-Network Relay. | vivo | Rel-18 | Revision of S2-2200707r04. Approved | Approved | |
| 9.26 | - | - | - | New Key Issue 5 - Support of multi-path for UE-to-Network Relay | - | - | Docs:=4 | - | |
| 9.26 | S2-2200709 | P-CR | Approval | 23.700-33: KI#X: Support of multi-path for UE-to-Network Relay to improve the reliability or data rate. | vivo | Rel-18 | Merged into S2-2201372 | Steve (Huawei) It is suggested this is marked as merged into S2-2200931, as per rapporteur suggestion. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.26 | S2-2200718 | P-CR | Approval | 23.700-33: Key Issue on Support of Multiple Path Transmission. | ZTE | Rel-18 | Merged into S2-2201368 | Steve (Huawei) It is suggested this is marked as merged into S2-2200931, as per rapporteur suggestion. Hao Dong (ZTE) confirms this paper is merged into S2-2200931. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Merged |
| 9.26 | S2-2200931 | P-CR | Approval | 23.700-33: KI proposal for multi-path transmission using U2N Relay. | Huawei, HiSilicon | Rel-18 | r06 agreed. Revised to S2-2201372, merging S2-2200709 and S2-2200719 | Steve (Huawei) provides r01, merging S2-2200709 & S2-2200718 Zhang (Ericsson) provides comments Hao Dong (ZTE) responds to Zhang (Ericsson). Deng Qiang (CATT) provides r02. Fei (OPPO) comments and provides r03. Zhang (Ericsson) provides r04 and co-sign Steve (Huawei) provides r05 Fei (OPPO) responds to Changhong (Intel) ==== 8.X, 9.X, 10.X Revisions Deadline ==== Steve (Huawei) is ok with r06. ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.26 | S2-2201372 | P-CR | Approval | 23.700-33: KI proposal for multi-path transmission using U2N Relay. | Huawei, HiSilicon, Interdigital Inc., ZTE, vivo, Ericsson, CATT | Rel-18 | Revision of S2-2200931r06, merging S2-2200709 and S2-2200719. Approved | Approved | |
| 9.26 | - | - | - | New Key Issue 6- Support of emergency services over UE-to-Network Relay | - | - | Docs:=4 | - | |
| 9.26 | S2-2200221 | P-CR | Approval | 23.700-33: New Key Issue on Support of Emergency Services for UE to Network Relaying. | Ericsson | Rel-18 | CC#5: Postponed | Judy (Ericsson), based on offline proposal, provides r01 merging 0500 (Samsung), 0708 (vivo) and 1010 (Nokia) for further discussion/revision. Note that the merged r01 does not imply company position. Wen (vivo) comments. Fei (OPPO) comments. Steve (Huawei) comments Mehrdad (Samsung) provides r02 Fei (OPPO) provides r03. Wen (vivo) comments and provides r04. Xiaoyan Shi (Interdigital) asks question for clarification on r04. Hong (Qualcomm) replies to Wen. Wen (vivo) replies to Xiaoyan Shi (Interdigital). Judy (Ericsson) comment that priority services are not included in SID yet and need clarification what priority services are Wen (vivo) replies and provides r05. Mehrdad (Samsung) replies to Ericsson Judy (Ericsson) responds to Mehrdad (Samsung) and ask Wen (vivo) a question. Wen (vivo) replies to Judy (Ericsson) . Wen (vivo) replies to Steve (Huawei) Fei (OPPO) provides comments. Fei (OPPO) responded to Steve (Huawei) Steve (Huawei) thanks Fei (OPPO), perhaps lets keep it simple then. Mehrdad (Samsung) provides r06 Judy (Ericsson) provides r07. Hannu (Nokia) provides r08. Mehrdad (Samsung) cannot agree with r07 or8 and provides r09. Hannu (Nokia) can't agree r09. Hannu would still prefer r08 but offers r10 as possible compromise. Mehrdad (Samsung) cannot agree with r10. Fei (OPPO) provides views. Hannu (Nokia) comments. Steve (Huawei) asks a question about the first 2 bullets ==== 8.X, 9.X, 10.X Revisions Deadline ==== Mehrdad (Samsung) suggests we move forward with r06 with the understanding that the SID will be clarified during the next SA plenary. Judy (Ericsson) proposes to move forward with r10, accept r07 & r08, cannot agree with other revisions. Priority services if included in SID need a separate KI due to its difference from emergency service. Some bullets 00221 are not applicable for priority services. Deng Qiang (CATT) suggests we move forward with r10. Fei (OPPO) suggestes to go with r10. Fei (OPPO) responds to Mehrdad. Judy (Ericsson) comments that r06 is not technically correct as some contents are applicable only for emergency but not for priority services. Wen (vivo) also agrees with r10. Tao(VC) it reads r10 most favorable. Let's double check Mehrdad can live with r10 or not Mehrdad (Samsung) cannot agree with r10. We object to r07, r08 and r10, original revision and r01. Hannu (Nokia) prefers r10, can also agree r07 and r08. Hannu points out that the controversial part in r10 uses the wording from TSG SA approved SID. If that SID needs to be updated, that discussion must go via TSG SA and until then SA2 should plan according to the approved work items. Fei (OPPO) can we discuss it at CC#4 or CC#5. Deng Qiang (CATT) request to discuss this pCR at CC#4. Mehrdad is not clear what to be discussed over CC#4 or CC#5. When there is no agreement, the PCR is postponed and we get back to this in the next meeting Mehrdad (Samsung) is not clear what to be discussed over CC#4. When there is no agreement, the PCR is postponed and we get back to this in the next meeting. We sustain objection to r07, r08 and r10, original revision and r01 Fei (OPPO) responds. Judy (Ericsson) is fine with r07&r08&r10, objects to other revisions, support the proposal to discuss at CC and responds to Mehrdad (Samsung) Mehrdad (Samsung) replies to OPPO. Steve (Huawei) looks like no acceptable versions, lets come back next meeting. ==== 8.X, 9.X, 10.X Final Deadline ==== | Postponed |
| 9.26 | S2-2200500 | P-CR | Approval | 23.700-33: New Key Issue on Support of Emergency Services for Remote UE over UE-to-Network Relay. | Samsung | Rel-18 | Merge into S2-2200221 (Postponed). Postponed | Judy (Ericsson) comments that this paper has been merged to 00221 ==== 8.X, 9.X, 10.X Revisions Deadline ==== Mehrdad (Samsung) is ok to mark this paper as merged into 00221 ==== 8.X, 9.X, 10.X Final Deadline ==== | Postponed |
| 9.26 | S2-2200708 | P-CR | Approval | 23.700-33: KI#X: Support of Emergency Services for UE-to-Network relay. | vivo | Rel-18 | Merge into S2-2200221 (Postponed). Postponed | Judy (Ericsson) comments that this paper has been merged to 00221 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Postponed |
| 9.26 | S2-2201010 | P-CR | Approval | 23.700-33: New Key Issue emergency. | Nokia, Nokia Shanghai Bell | Rel-18 | Merge into S2-2200221 (Postponed). Postponed | Judy (Ericsson) comments that this paper has been merged to 00221 Hannu (Nokia) agrees with Judy that this paper can be considered as merged to 0221 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Postponed |
| 9.26 | - | - | - | New Key Issue 7 - Support of PC5 Service Authorization and Policy/Parameter Provisioning | - | - | Docs:=2 | - | |
| 9.26 | S2-2200661 | P-CR | Approval | 23.700-33: New Key Issue: Support of PC5 Service Authorization and Policy/Parameter Provisioning. | Intel | Rel-18 | r01 agreed. Revised to S2-2201373. | Zhang (Ericsson) provides comments Deng Qiang (CATT) provides comments. Changhong (Intel) answers to Zhang and Qiang's comments. Steve (Huawei) what is this trying to solve? Changhong replies to Steve. Mehrdad (Samsung) provides r01 and supports this PCR. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.26 | S2-2201373 | P-CR | Approval | 23.700-33: New Key Issue: Support of PC5 Service Authorization and Policy/Parameter Provisioning. | Intel, Samsung | Rel-18 | Revision of S2-2200661r01. Approved | Approved | |
| 9.26 | - | - | - | Documents exceeding quota | - | - | Docs:=6 | - | |
| 9.26 | S2-2200138 | P-CR | Approval | 23.700-33: TR 23.700-33: New solution on path switching between two indirect network communication paths for UE-to-Network Relay | CATT | Rel-18 | Not Handled | ==== 8.X, 9.X, 10.X Final Deadline ==== | - |
| 9.26 | S2-2201007 | P-CR | Approval | 23.700-33: Solution for switching between two indirect L3 UE-to-Network Relay paths using N3IWF. | Nokia, Nokia Shanghai Bell | Rel-18 | Not Handled | ==== 8.X, 9.X, 10.X Final Deadline ==== | - |
| 9.26 | S2-2201224 | P-CR | Approval | 23.700-33: TR 23.700-33 New solutions to support UE-to-Network Relay work tasks. | Qualcomm Incorporated | Rel-18 | Not Handled | ==== 8.X, 9.X, 10.X Final Deadline ==== | - |
| 9.26 | S2-2200986 | P-CR | Approval | 23.700-33: New solution to Key Issue of multi-path to improve reliability. | China Telecom | Rel-18 | Not Handled | ==== 8.X, 9.X, 10.X Final Deadline ==== | - |
| 9.26 | S2-2201230 | P-CR | Approval | 23.700-33: TR 23.700-33 pCR New solutions to support multi-path transmission. | Qualcomm Incorporated | Rel-18 | Not Handled | ==== 8.X, 9.X, 10.X Final Deadline ==== | - |
| 9.26 | S2-2200742 | P-CR | Approval | 23.700-33: Key issue on emergency service support over U2N relay. | OPPO | Rel-18 | Not Handled | ==== 8.X, 9.X, 10.X Final Deadline ==== | - |
| 9.27 | - | - | - | Study on Seamless UE context recovery (FS_SUECR) | - | - | Docs:=7 | - | |
| 9.27 | S2-2201195 | P-CR | Approval | 23.700-61: FS_SUECR TR 23.700-61 Skeleton. | Samsung (Rapporteur) | Rel-18 | 23.700-61 TR Skeleton. Approved | ==== 8.X, 9.X, 10.X Final Deadline ==== | Approved |
| 9.27 | S2-2201202 | P-CR | Approval | 23.700-61: TR Scope and References. | Samsung | Rel-18 | r01 agreed. Revised to S2-2201827. | Lalith(Samsung) provides r01. Miguel (Qualcomm) expresses concerns about the scope wording ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.27 | S2-2201827 | P-CR | Approval | 23.700-61: TR Scope and References. | Samsung | Rel-18 | Revision of S2-2201202r01. Approved | Approved | |
| 9.27 | S2-2201203 | P-CR | Approval | 23.700-61: FS_SUECR architectural assumptions. | Samsung | Rel-18 | r03 agreed. Revised to S2-2201828. | Miguel (Qualcomm) has concerns with some of the architectural assumptions Lalith(Samsung) comments. Yannick (Nokia): Nokia provides r01. Lalith(Samsung) is OK r01. Ulises (InterDigital Inc.) provides r02 Lalith(Samsung) provides r03 ==== 8.X, 9.X, 10.X Revisions Deadline ==== Qian (Ericsson) is fine with r03 ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.27 | S2-2201828 | P-CR | Approval | 23.700-61: FS_SUECR architectural assumptions. | Samsung | Rel-18 | Revision of S2-2201203r03. Approved | Approved | |
| 9.27 | S2-2201205 | P-CR | Approval | 23.700-61: KI for FS_SUECR. | Samsung | Rel-18 | r06 agreed. Revised to S2-2201829. | Lalith(Samsung) replies to Miguel (Qualcomm) Miguel (Qualcomm) has big concerns with this Key issue, suggests to either NOTE or have complete rewording Yannick (Nokia): Nokia share concerns expressed by Qualcomm. We provide r01 to at least remove parts that we think hint towards some sort of solution already. Lalith(Samsung) expresses he is open to remove the words which other companies think is solution oriented and is OK with r01. Huan(vivo) asks for clarifications Lalith(Samsung) replies to Huan(vivo) Qian (Ericsson) comments and provide r02 Miguel (Qualcomm) provides r03 Yannick (Nokia): Nokia provides r04. Lalith (Samsung) comments and indicate r03 looks OK. Lalith(Samsung) provides r05 Patrice (Huawei) provides minor revisions in r06. Lalith(Samsung) is fine with r06. ==== 8.X, 9.X, 10.X Revisions Deadline ==== Qian (Ericsson) is fine with r06. ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 9.27 | S2-2201829 | P-CR | Approval | 23.700-61: KI for FS_SUECR. | Samsung, KDDI | Rel-18 | Revision of S2-2201205r06. Approved | Approved | |
| 10 | - | - | - | Project Planning and Management | - | - | Docs:=0 | - | |
| 10.1 | - | - | - | New and Revised Work Items, TS/TR Cover sheets | - | - | Docs:=12 | - | |
| 10.1 | S2-2200330 | SID REVISED | Approval | Revised SID: Study on RedCap Phase 2. | Ericsson | Rel-18 | Revision of (Approved) SP-211635 from SP#94E. Revised to S2-2201687. | ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 10.1 | S2-2201687 | SID REVISED | Approval | Revised SID: Study on RedCap Phase 2. | Ericsson | Rel-18 | Revision of S2-2200330. Approved | Approved | |
| 10.1 | S2-2200536 | SID REVISED | Approval | Revised SID on Enhancement to the 5GC LoCation Services Phase 3. | CATT, Huawei | Rel-18 | Revision of SP-211637. Revised to S2-2201688. | ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 10.1 | S2-2201688 | SID REVISED | Approval | Revised SID on Enhancement to the 5GC LoCation Services Phase 3. | CATT, Huawei | Rel-18 | Revision of S2-2200536. Approved | Approved | |
| 10.1 | S2-2200608 | SID REVISED | Approval | Revised SID: Study on 5G multicast-broadcast services Phase 2. | Huawei, CBN | Rel-18 | r01 agreed. Revised to S2-2201830. | LiMeng (Huawei) provides r01. LiMeng (Huawei) correct the AI of this email thread. ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 10.1 | S2-2201830 | SID REVISED | Approval | Revised SID: Study on 5G multicast-broadcast services Phase 2. | Huawei, CBN | Rel-18 | Revision of S2-2200608r01. Approved | Approved | |
| 10.1 | S2-2200765 | SID REVISED | Approval | Revised SID on Enhancement of support for Edge Computing in 5G Core network — phase 2 . | Huawei, HiSilicon | Rel-18 | Revised to S2-2201689. | ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 10.1 | S2-2201689 | SID REVISED | Approval | Revised SID on Enhancement of support for Edge Computing in 5G Core network — phase 2 . | Huawei, HiSilicon | Rel-18 | Revision of S2-2200765. Approved | Approved | |
| 10.1 | S2-2201031 | SID REVISED | Approval | Revised WID for FS_eNS_Ph3. | ZTE (Rapporteur) | Rel-18 | r01 agreed. Revised to S2-2201831. | Myungjune (LGE) provides r01 ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 10.1 | S2-2201831 | SID REVISED | Approval | Revised WID for FS_eNS_Ph3. | ZTE (Rapporteur) | Rel-18 | Revision of S2-2201031r01. Approved | Approved | |
| 10.1 | S2-2201206 | SID REVISED | Approval | Revised SID on System Support for AI/ML-based Services. | OPPO, Samsung | Rel-18 | Revised to S2-2201690. | ==== 8.X, 9.X, 10.X Final Deadline ==== | Revised |
| 10.1 | S2-2201690 | SID REVISED | Approval | Revised SID on System Support for AI/ML-based Services. | OPPO, Samsung | Rel-18 | Revision of S2-2201206. Approved | Approved | |
| 10.2 | - | - | - | Review of the Work Plan, Rel-17/Rel-18 WID Status Reports | - | - | Docs:=64 | - | |
| 10.2 | - | - | - | Rel-17 status report | - | - | Docs:=18 | - | |
| 10.2 | S2-2200249 | WI STATUS REPORT | Information | MINT Status Report | LG Electronics | Rel-17 | Revised to S2-2201900. | Revised | |
| 10.2 | S2-2201900 | WI STATUS REPORT | Information | MINT Status Report | LG Electronics | Rel-17 | Revision of S2-2200249. Noted | Noted | |
| 10.2 | S2-2200485 | WI STATUS REPORT | Information | eNPN Status Report | Ericsson (rapporteur) | Rel-17 | Revised to S2-2201901. | Revised | |
| 10.2 | S2-2201901 | WI STATUS REPORT | Information | eNPN Status Report | Ericsson (Rapporteur) | Rel-17 | Revision of S2-2200485. Noted | Noted | |
| 10.2 | S2-2201902 | WI STATUS REPORT | Information | eEdge_5GC Status Report | Huawei (Rapporteur) | Rel-17 | Noted | Noted | |
| 10.2 | S2-2201903 | WI STATUS REPORT | Information | 5G_ProSe Status Report | CATT | Rel-17 | Noted | Noted | |
| 10.2 | S2-2201904 | WI STATUS REPORT | Information | 5MBS Status Report | Huawei | Rel-17 | Noted | Noted | |
| 10.2 | S2-2201905 | WI STATUS REPORT | Information | eNS_Ph2 Status Report | ZTE | Rel-17 | Noted | Noted | |
| 10.2 | S2-2201906 | WI STATUS REPORT | Information | MPS2 Status Report | Perspecta Labs | Rel-17 | Noted | Noted | |
| 10.2 | S2-2201907 | WI STATUS REPORT | Information | eLCS_Ph2 Status Report | CATT | Rel-17 | Noted | Noted | |
| 10.2 | S2-2201908 | WI STATUS REPORT | Information | IIoT Status report | Nokia | Rel-17 | Noted | Noted | |
| 10.2 | S2-2201909 | WI STATUS REPORT | Information | ARCH_NR_REDCAP Status Report | China Mobile | Rel-17 | Noted | Noted | |
| 10.2 | S2-2201910 | WI STATUS REPORT | Information | ID_UAS Status Report | Qualcomm | Rel-17 | Noted | Noted | |
| 10.2 | S2-2201911 | WI STATUS REPORT | Information | eV2XARC_Ph2 Status Report | LG Electronics | Rel-17 | Noted | Noted | |
| 10.2 | S2-2201912 | WI STATUS REPORT | Information | eNA_Ph2 Status Report | vivo | Rel-17 | Noted | Noted | |
| 10.2 | S2-2201913 | WI STATUS REPORT | Information | MUSIM Status Report | Intel (rapporteur) | Rel-17 | Noted | Noted | |
| 10.2 | S2-2201914 | WI STATUS REPORT | Information | IoT_SAT_ARCH_EPS Status Report | MediaTek Inc. | Rel-17 | Noted | Guillaume (MediaTek Inc.) provides the draft SR in the drafts folder | Noted |
| 10.2 | S2-2201915 | WI STATUS REPORT | Information | 5GSAT_ARCH Status Report | Thales | Rel-17 | Noted | Noted | |
| 10.2 | - | - | - | Rel-18 status report | - | - | Docs:=42 | - | |
| 10.2 | S2-2200770 | WI STATUS REPORT | Information | ATSSS_Ph3 Status Report | Lenovo, Motorola Mobility | Rel-18 | Revised to S2-2201880. | Revised | |
| 10.2 | S2-2201880 | WI STATUS REPORT | Information | ATSSS_Ph3 Status Report | Lenovo, Motorola Mobility | Rel-18 | Revision of S2-2200770. Noted | Noted | |
| 10.2 | S2-2200308 | WI STATUS REPORT | Information | FS_DetNet Status Report | Ericsson | Rel-18 | Revised to S2-2201874. | Revised | |
| 10.2 | S2-2201874 | WI STATUS REPORT | Information | FS_DetNet Status Report | Ericsson | Rel-18 | Revision of S2-2200308. Noted | Noted | |
| 10.2 | S2-2200331 | WI STATUS REPORT | Information | Status Report FS_REDCAP_Ph2 | Ericsson (Rapporteur) | Rel-18 | Revised to S2-2201875. | Revised | |
| 10.2 | S2-2201875 | WI STATUS REPORT | Information | Status Report FS_REDCAP_Ph2 | Ericsson (Rapporteur) | Rel-18 | Revision of S2-2200331. Noted | Noted | |
| 10.2 | S2-2201077 | WI STATUS REPORT | Information | FS_SFC Work Plan and Status Report | Intel | Rel-18 | Revised to S2-2201883. | Revised | |
| 10.2 | S2-2201883 | WI STATUS REPORT | Information | FS_SFC Work Plan and Status Report | Intel | Rel-18 | Revision of S2-2201077. Noted | Noted | |
| 10.2 | S2-2200107 | WI STATUS REPORT | Information | SA WG2 Status report for 5WWC | Nokia, Nokia Shanghai Bell | Rel-18 | Revised to S2-2201872. | Fabio Giust (Nokia): Nokia provides r01 Laurent (Nokia): Provides r01 Laurent (Nokia): Provides r01 with now the correct link | Revised |
| 10.2 | S2-2201872 | WI STATUS REPORT | Information | SA WG2 Status report for 5WWC | Nokia, Nokia Shanghai Bell | Rel-18 | Revision of S2-2200107. Noted | Noted | |
| 10.2 | S2-2200140 | WI STATUS REPORT | Information | FS_5G_ProSe_Ph2 Status Report | CATT, OPPO | Rel-18 | Revised to S2-2201873. | Revised | |
| 10.2 | S2-2201873 | WI STATUS REPORT | Information | FS_5G_ProSe_Ph2 Status Report | CATT, OPPO | Rel-18 | Revision of S2-2200140. Noted | Noted | |
| 10.2 | S2-2200486 | WI STATUS REPORT | Information | FS_eNPN_Ph2 Status Report | Ericsson (rapporteur) | Rel-18 | Revised to S2-2201876. | Revised | |
| 10.2 | S2-2201876 | WI STATUS REPORT | Information | FS_eNPN_Ph2 Status Report | Ericsson (rapporteur) | Rel-18 | Revision of S2-2200486. Noted | Noted | |
| 10.2 | S2-2200598 | WI STATUS REPORT | Information | Status Report of FS_5MBS_Ph2 | Huawei | Rel-18 | Revised to S2-2201877. | Revised | |
| 10.2 | S2-2201877 | WI STATUS REPORT | Information | Status Report of FS_5MBS_Ph2 | Huawei | Rel-18 | Revision of S2-2200598. Noted | Noted | |
| 10.2 | S2-2200656 | WI STATUS REPORT | Information | FS_GMEC Status Report | Huawei, HiSilicon | Rel-18 | Revised to S2-2201878. | Revised | |
| 10.2 | S2-2201878 | WI STATUS REPORT | Information | FS_GMEC Status Report | Huawei, HiSilicon | Rel-18 | Revision of S2-2200656. Noted | Noted | |
| 10.2 | S2-2200768 | WI STATUS REPORT | Information | FS_EDGE_Ph2 status report | Huawei (Rapporteur) | Rel-18 | Revised to S2-2201879. | Revised | |
| 10.2 | S2-2201879 | WI STATUS REPORT | Information | FS_EDGE_Ph2 status report | Huawei (Rapporteur) | Rel-18 | Revision of S2-2200768. Noted | Noted | |
| 10.2 | S2-2200840 | WI STATUS REPORT | Information | SA WG2 report for FS_AIMLsys for SA WG2#149e | OPPO, Samsung | Rel-18 | Revised to S2-2201881. | Revised | |
| 10.2 | S2-2201881 | WI STATUS REPORT | Information | SA WG2 report for FS_AIMLsys for SA WG2#149e | OPPO, Samsung | Rel-18 | Revision of S2-2200840. Noted | Noted | |
| 10.2 | S2-2201032 | WI STATUS REPORT | Information | Status report for FS_eNS_Ph3 | ZTE | Rel-18 | Revised to S2-2201882. | Revised | |
| 10.2 | S2-2201882 | WI STATUS REPORT | Information | Status report for FS_eNS_Ph3 | ZTE | Rel-18 | Revision of S2-2201032. Noted | Noted | |
| 10.2 | S2-2201107 | WI STATUS REPORT | Information | FS_Ranging_SL Status Report | Xiaomi | Rel-18 | Revised to S2-2201884. | Revised | |
| 10.2 | S2-2201884 | WI STATUS REPORT | Information | FS_Ranging_SL Status Report | Xiaomi | Rel-18 | Revision of S2-2201107. Noted | Noted | |
| 10.2 | S2-2201194 | WI STATUS REPORT | Information | FS_SUECR Status Report | Samsung | Rel-18 | Revised to S2-2201885. | Revised | |
| 10.2 | S2-2201885 | WI STATUS REPORT | Information | FS_SUECR Status Report | Samsung | Rel-18 | Revision of S2-2201194. Noted | Noted | |
| 10.2 | S2-2201886 | WI STATUS REPORT | Information | Status Report for MPS_WLAN | Peraton Labs | Rel-18 | Noted | Noted | |
| 10.2 | S2-2201887 | WI STATUS REPORT | Information | Status Report for FS_UAS_Ph2 | Qualcomm | Rel-18 | Noted | Noted | |
| 10.2 | S2-2201888 | WI STATUS REPORT | Information | Status Report for FS_5TRS_URLLC | Nokia | Rel-18 | Noted | Noted | |
| 10.2 | S2-2201889 | WI STATUS REPORT | Information | Status Report for FS_VMR | Qualcomm | Rel-18 | Noted | Noted | |
| 10.2 | S2-2201890 | WI STATUS REPORT | Information | Status Report for FS_eLCS_Ph3 | CATT | Rel-18 | Noted | Noted | |
| 10.2 | S2-2201891 | WI STATUS REPORT | Information | Status Report for FS_5GSATB | CATT | Rel-18 | Noted | Noted | |
| 10.2 | S2-2201892 | WI STATUS REPORT | Information | Status Report for FS_5GSAT_Ph2 | Thales | Rel-18 | Noted | Noted | |
| 10.2 | S2-2201893 | WI STATUS REPORT | Information | Status Report for FS_AMP | China Telecom | Rel-18 | Noted | Noted | |
| 10.2 | S2-2201894 | WI STATUS REPORT | Information | Status Report for FS_PIN | Vivo | Rel-18 | Noted | Noted | |
| 10.2 | S2-2201895 | WI STATUS REPORT | Information | Status Report for FS_NG_RTC | China Mobile | Rel-18 | Noted | Noted | |
| 10.2 | S2-2201896 | WI STATUS REPORT | Information | Status Report for FS_XRM | China Mobile | Rel-18 | Noted | Noted | |
| 10.2 | S2-2201897 | WI STATUS REPORT | Information | Status Report for FS_eUEPO | Intel | Rel-18 | Noted | Noted | |
| 10.2 | S2-2201898 | WI STATUS REPORT | Information | Status Report for FS_eNA_Ph3 | China Mobile | Rel-18 | Noted | Noted | |
| 10.2 | S2-2201899 | WI STATUS REPORT | Information | Status Report for FS_UPEAS | China Mobile | Rel-18 | Noted | Noted | |
| 10.2 | - | - | - | SA WG2 Work Planning | - | - | Docs:=4 | - | |
| 10.2 | S2-2201217 | WORK PLAN | Endorsement | SA WG2 Work Planning Sheet | SA WG2 Chair | Endorsed | . ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== ==== 8.X, 9.X, 10.X Revisions Deadline ==== ==== 8.X, 9.X, 10.X Final Deadline ==== | Endorsed | |
| 10.2 | S2-2201218 | WORK PLAN | Endorsement | SA WG2 work planning | SA WG2 Chair | CC#2: Revised to S2-2201683. | . ==== 4.X, 5.X, 6.X, 7.X, 8.29, 10.2 (Work Plan) Revisions Deadline ==== Patrice (Huawei) comments on the work plan, is OK to endorse the first bullet of page 10 (2022 planning), but would like further discussion on 2023-Q1 January meeting before endorsing. Leo (Deutsche Telekom) comments on the work plan. Patrice (Huawei) clarifies that it is not possible to make a decision regarding Jan 2023 ad-hoc meeting until the details of the meeting are settled, for reasons explained in the mail (object to make a decision in one way or another during this meeting). | Revised | |
| 10.2 | S2-2201683 | WORK PLAN | Endorsement | SA WG2 work planning | SA WG2 Chair | - | Revision of S2-2201218. CC#2: Endorsed | Endorsed | |
| 10.2 | S2-2201684 | OTHER | Presentation | 3GPP SA WG2 Excellence Award 2021 | SA WG2 Chair | Presented at CC#3. Noted | Noted | ||
| 10.3 | - | - | - | Planning future meetings | - | - | Docs:=0 | - | |
| 11 | - | - | - | Close of e-meeting | - | - | Docs:=0 | - | |
| 99 | - | - | - | Withdrawn and Reserved documents | - | - | Docs:=170 | - | |
| 99 | S2-2201258 | LS In | Action | LS from RAN WG2: LS on UE location during initial access in NTN | RAN WG2 (R2-2202057) | Rel-17 | Same as S2-2200079. WITHDRAWN | Withdrawn | |
| 99 | S2-2200832 | P-CR | Approval | 23.700-58: 23.700-58: KI on loss of UAV control due to network-initiated events | Nokia, Nokia Shanghai Bell | Rel-18 | WITHDRAWN | Withdrawn | |
| 99 | S2-2200181 | CR | Approval | 23.288 CR0495 (Rel-17, 'F'): Removing File address of the ML model(s) from AnalyticsSubscription_Transfer | Nokia, Nokia Shanghai Bell | Rel-17 | WITHDRAWN | Withdrawn | |
| 99 | S2-2201229 | CR | Approval | 23.247 CR0099 (Rel-17, 'F'): Stage 3 allignment for MB-SMF discovery | Nokia, Nokia Shanghai-Bell | Rel-17 | WITHDRAWN | Withdrawn | |
| 99 | S2-2201155 | P-CR | Approval | 23.700-05: TR 23.700-05: new solution proposal on provisioning and policy control for FS_VMR | Qualcomm Incorporated | Rel-18 | WITHDRAWN | Withdrawn | |
| 99 | S2-2201219 | P-CR | Approval | 23.700-17: FS_5WWC_Ph2: Solution for providing differentiated service for non-3GPP devices behind a 5G RG | CableLabs | Rel-18 | WITHDRAWN | Withdrawn | |
| 99 | S2-2201220 | P-CR | Approval | 23.700-17: FS_5WWC_Ph2: Solution for providing differentiated service for 3GPP devices behind a 5G RG | CableLabs | Rel-18 | WITHDRAWN | Withdrawn | |
| 99 | S2-2201226 | P-CR | Approval | 23.700-17: FS_5WWC_Ph2: KI and Solution for providing differentiated service for UE and non-3GPP devices behind a 5G RG | CableLabs | Rel-18 | WITHDRAWN | Withdrawn | |
| 99 | S2-2200148 | DISCUSSION | Approval | Discussion on how to split WTs into Kis | vivo | WITHDRAWN | Withdrawn | ||
| 99 | S2-2200403 | WORK PLAN | Endorsement | Workplan | Samsung | Rel-18 | WITHDRAWN | Withdrawn | |
| 99 | S2-2200447 | CR | Approval | 23.501 CR3506 (Rel-17, 'F'): Enforcement of VPLMN QoS policies | Ericsson | Rel-17 | WITHDRAWN | Withdrawn | |
| 99 | S2-2200955 | CR | Approval | 23.502 CR3393 (Rel-17, 'F'): Correction for remote provisioning | Ericsson Inc. | Rel-17 | WITHDRAWN | Withdrawn | |
| 99 | S2-2200855 | CR | Approval | 23.503 CR0699 (Rel-17, 'F'): Correction to AF-triggered dynamically changing AM policies | Huawei, HiSilicon | Rel-17 | WITHDRAWN | Withdrawn | |
| 99 | S2-2200184 | P-CR | Approval | 23.700-81: WT#3.3: UPF data report to NWDAF | Ericsson | Rel-18 | WITHDRAWN | Withdrawn | |
| 99 | S2-2200820 | P-CR | Approval | 23.700-81: New key issue on data and analytics exchange in roaming case . | Vivo, Nokia, Nokia Shanghai Bell | Rel-18 | WITHDRAWN | Withdrawn | |
| 99 | S2-2201068 | P-CR | Approval | 23.700-81: KI: Key Issue for WT | Nokia, Nokia Shanghai Bell | Rel-18 | WITHDRAWN | Withdrawn | |
| 99 | S2-2200209 | CR | Approval | 23.502 CR3326 (Rel-17, 'F'): Correction related EHE in EC architecture | Ericsson | Rel-17 | WITHDRAWN | Withdrawn | |
| 99 | S2-2200085 | DRAFTCR | Approval | Correction to DNAI in Service Experience analytics output | Sandvine Incorporated | Rel-16 | WITHDRAWN | Withdrawn | |
| 99 | S2-2200086 | DRAFTCR | Approval | Correction to DNAI in Service Experience analytics output | Sandvine Incorporated | Rel-17 | WITHDRAWN | Withdrawn | |
| 99 | S2-2200070 | LS In | Action | LS from SA WG3: LS on conclusions of authentication methods for initial access for onboarding. | SA WG3 (S3-214541) | Rel-17 | Same as S2-2200029. WITHDRAWN | Withdrawn | |
| 99 | S2-2200286 | CR | Approval | 23.501 CR3483 (Rel-16, 'F'): Handover of a PDU Session from 3GPP to untrusted non-3GPP access (I-SMF case) | Nokia, Nokia Shanghai Bell | Rel-16 | WITHDRAWN | Withdrawn | |
| 99 | S2-2200287 | CR | Approval | 23.501 CR3484 (Rel-17, 'A'): Handover of a PDU Session from 3GPP to untrusted non-3GPP access (I-SMF case) | Nokia, Nokia Shanghai Bell | Rel-17 | WITHDRAWN | Withdrawn | |
| 99 | S2-2200322 | CR | Approval | 23.288 CR0501 (Rel-17, 'F'): Conveying UPF FQDN to IMS nodes | Nokia, Nokia Shanghai-Bell | Rel-17 | WITHDRAWN | Withdrawn |